Activity log for bug #1753873

Date Who What changed Old value New value Message
2018-03-07 02:06:03 Daniel van Vugt bug added bug
2018-03-07 02:06:18 Daniel van Vugt attachment removed JournalErrors.txt https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1753873/+attachment/5071182/+files/JournalErrors.txt
2018-03-07 02:06:24 Daniel van Vugt attachment removed ProcCpuinfoMinimal.txt https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1753873/+attachment/5071183/+files/ProcCpuinfoMinimal.txt
2018-03-07 02:06:29 Daniel van Vugt attachment removed ProcEnviron.txt https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1753873/+attachment/5071184/+files/ProcEnviron.txt
2018-03-07 02:06:34 Daniel van Vugt attachment removed Dependencies.txt https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1753873/+attachment/5071181/+files/Dependencies.txt
2018-03-07 02:06:41 Daniel van Vugt gnome-session (Ubuntu): importance Undecided Low
2018-03-07 02:07:33 Daniel van Vugt description The session title "Ubuntu on Wayland" is misleading. Gnome Shell is not running "on Wayland" at all. If you choose that option then mutter is running on the "eglnative" backend instead of the X11 backend. I'm not suggesting we call the session "Ubuntu on eglnative", as that would make it more confusing. But I wonder if we can find a session title that avoids implying the impossible situation that the shell runs "on Wayland". Because the current title makes many people think that's what's happening. Actually, Wayland doesn't come into the picture at all until you start an app. Only then is "Wayland" used at all as the protocol between the app and the shell. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.27.91-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Wed Mar 7 09:59:25 2018 InstallationDate: Installed on 2017-12-12 (84 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) The session title "Ubuntu on Wayland" is misleading. Gnome Shell is not running "on Wayland" at all. If you choose that option then mutter is running on the "eglnative" backend instead of the X11 backend. I'm not suggesting we call the session "Ubuntu on eglnative", as that would make it more confusing. But I wonder if we can find a session title that avoids implying the impossible situation that the shell runs "on Wayland". Because the current title makes many people think that's what's happening. Actually, Wayland doesn't come into the picture at all until you start an app. Only then is "Wayland" used at all as the protocol between the app and the shell, sometimes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.27.91-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Wed Mar 7 09:59:25 2018 InstallationDate: Installed on 2017-12-12 (84 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install)