shell-add-wayland-extension=zwp_primary_selection_device_manager_v1 # it isn't obvious why maliit-keyboard needs this It seems this is necessary due to QtWayland requiring it. However, this commit suggests this may no longer be the case in 6.6.0. I don't know if it's been pulled into the KDE patch collection for 5.15 though. Now we just need to get Lomiri fully onto Mir 2.x and Qt 5.15 so we can add the capability to ship the OSK in a confined click.

Thank you very much for all your work @alan_g :folded_hands:

@erlend I've had a first look, and three of those test doubles are unused in the current codebase. There's a PR dropping them for your review. The others are used in a range of tests I've yet to work through.

@arubislander thanks for the explanation !

@jonius said in Introducing Miroil: @jonius next issue is a failing test (ApplicationManager), which fails here. I had a look over the weekend. The test is failing in the branch I based this off, and I didn't see an obvious cause for it. I probably need to find a better base branch for this work. I really find all these QtMir branches a mystery. Maybe the best one is one of those in the gitlab repo?

@alan_g said in Mir 1.x and beyond: Mir doesn’t (yet) have a clean API for adding Wayland protocol extensions in a server and, in any case, those that are needed by Ubuntu Touch are simply exposing existing Mir functionality. So, once the necessary protocol extensions are identified, the Mir code is the place to implement them. Small clarification, that was a year ago. There's now a way to add Wayland extensions to Mir servers.

@GizmoChicken said in 2019: Time to make Unity8 great again?: Given recent progress, how about 2020Q1: Time to make Unity8 great again? I like it! Maybe we can just rename this thread?

Just wanted to share that I had some battery issues (draining too fast, often draining the entire battery within 1 day) with a OnePlus Nord N10 5g. The phone I purchased was an old refurbished one and I'm not sure if the battery was refreshed or if it was the original battery. Nonetheless, my battery issues have seemed to resolved and thought I'd share. It may help others or not. So, take it or leave it. By default, the screen brightness was quite high (to the far right on the slider) and I can't recall if "Adjust automatically" was enabled or not. I manually selected the screen brightness to the lowest level I could tolerate without feeling like I couldn't see the screen. Surprisingly for me, I can move the slider almost all the way to the left. I also unchecked the "Adjust automatically". So, now the screen brightness is using the minimal battery. (I believe this was the biggest gain for me). Furthermore, I am fairly conscious to disable WiFi unless I am actively using it for internet access. That is all I did and now the battery lasts a couple days without charging (vs completely drain in 1 day) and does not drain much at all. One last thing I am mindful of is to only use the charging cable that came with the device. I think the fast chargers that are more modern may easily cycle/overcharge older batteries and reduce the battery's long term life. With all batteries, there is a limited number of charging cycles and you'll notice that each 100% full charge may not last as long as when it was brand new. Overcharging (while at 100%) and/or letting the battery drain completely to 0% may reduce the life of the battery a bit. So, being mindful to unplug when at 100% and to start charging before it gets too low may help in maximizing its life. Hope this helps. Good luck maximizing your device's battery life!

here is a cool one. Check out this idea which could also be a '5 minute task' too https://forums.ubports.com/topic/1687/have-you-told-your-local-national-paper-about-ubports

@wgarcia you're right: https://code.launchpad.net/unity shows 7.5 as "trunk"

@gizmochicken said in 18.04 desktop - getting it working again: Note that, in addition to posting results for Mir 0.32.1 RC4 (installed from ppa:mir-team/rc), I also posted results for Mir 0.32.0 (installed from the UBports repo). Hope that helps. Just to follow up on this here: Unity8 is working for me with (or without) the Mir release 0.32.1 from ppa:mir-team/release. However, it isn't working with the gdm greeter, just lightdm. (I've not experimented with further greeters.)

@gizmochicken said in No more "Mir EGL" on 1804LTS (Bionic): At the risk of revealing the I understand less than I purport to understand, I have one more question: I know this calls for speculation, but do you anticipate that the above mentioned problematic Qt based applications will behave reasonably well (as a stopgap) under the XWayland solution that you are currently developing for Mir? That is a reasonable expectation, although don't expect immediate progress! (We've not started coding yet,) But Qt applications are largely usable already (and Qt 5.9.4 was a significant improvement on 5.9.3).

@webdrake said in Organizing Unity8 work: @alan_g I'll reach out to @mariogrip directly w.r.t. all things UBPorts. You've been more than generous with your time, but is it OK to still ping you about Mir(AL)-related issues w.r.t. the USC refactoring? No worries if not. Yes, I'm still happy to receive pings about Mir(AL) related stuff (USC or otherwise).

All fixed!

@unisuperbox That's good to know.

A few links for tracking Mir's progress since the OP: Wayland support (for some extensions) is available in Mir already and will improve with the next release For non-Wayland applications: there are plans for X11 support (but this come later)