I would like to opine specifically that if $XDG_DATA_DIRS is
specifically not what the shell expects -- for example it might contain
a corrupted character from translating between fish arrays and bash
arrays -- Gnome Shell on Wayland will not start.
On X11, Gnome Shell will start.
This is
I'm not sure how to reproduce this easily. It seems related to snaps and
other system changes. Certainly the rest of us have bash as our default
shells and it's not a problem for other people. So setting low priority
for now.
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
--
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739022
Title:
Wayland session does not start any more when bash is the default
Uploaded the information. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739022
Title:
Wayland session does not start any more when bash is the default shell
To manage notifications about
apport information
** Tags added: apport-collected bionic third-party-packages wayland-
session
** Description changed:
It appears the wayland session does not start on my XPS 13 on Ubuntu
17.10 and 18.04 if I use bash as my default shell. It only works if I
switch my default shell to
