18.04 desktop - getting it working again
-
@gizmochicken said in 18.04 desktop - getting it working again:
@alan_g: If Unity8 is installing upstream Mir 0.32, shouldn’t the Mir 0.32.1 RCs from ppa:mir-team/rc be expected to work with Unity8? Or am I missing a step?
I would expect 0.32.1 to be a "drop in" replacement for 0.32.0. (It works that way for egmde.)
We need to understand what is happening, could you leave a message on the 0.32.1 PR? Preferably with informative log messages?
Thanks
-
@alan_g said in 18.04 desktop - getting it working again:
We need to understand what is happening, could you leave a message on the 0.32.1 PR? Preferably with informative log messages?
I posted in this PR for Mir release 0.32.1. I mostly just reiterated what I posted here, but I did add a few minor details regarding my system.
As for posting informative log messages, I’m not sure what to look for, or even where to look. With some guidance, I’d be happy to try. But realistically, the quicker approach would probably be for someone else to confirm what I’m reporting.
Perhaps someone who is also testing Unity8, but who is more technically savvy than me, would be willing to test Unity8 installed as described here along with a Mir 0.32.1 RC installed from ppa:mir-team/rc? Do you know of anyone who fits that description, @pixelr0?
-
@gizmochicken said in 18.04 desktop - getting it working again:
As for posting informative log messages, I’m not sure what to look for, or even where to look. With some guidance, I’d be happy to try.
Thanks for what you done already!
As for guidance, I replied on phone while away from old fashioned computers so couldn't be more specific. I think the following will be helpful:
grep --before 25 --after 75 "mirserver: Starting" /var/log/syslog | tail -n 100Please check the output for anything personal you don't want to share. (This will probably only capture the user name you try to sign in with but the unexpected can happen.)
I'll try to look myself later, but first need to finish other tests and then set up a suitable test environment.
--- update ---
I found one problem, which I fixed by hacking the launch script:
$ cat `which lightdm-unity8-session` ... # {arg} systemctl --user set-environment MIR_SERVER_VT=$XDG_VTNRAfter this, I see the following just before Unity8 crashes:
Jul 12 12:12:35 alan-NUC7i3DNKE unity8-session[4469]: [2018-07-12 12:12:35.775889] mirserver: Using software cursor Jul 12 12:12:35 alan-NUC7i3DNKE unity8-session[4469]: [2018-07-12:12:12:35.776] zero sized software cursor image is invalidWhich is a Unity8 bug I think @mariogrip is aware of.
I'm not sure how either problem was avoided before. Maybe UBports made changes to Mir 0.32.0?
--- update ---
I've checked with @mariogrip - Mir 0.32.0 from the UBports repository is unaltered. I still don't understand how this ever worked.
-
@alan_g said in 18.04 desktop - getting it working again:
I found one problem, which I fixed by hacking the launch script
Just to be sure we're seeing the same problem (which we probably are), I still posted my results in in the PR.
I'm not sure how either problem was avoided before.
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.
-
@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.)
