-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can no longer launch Wayland Gnome sessions. #18
Comments
I can reproduce this, although as I've never been able to get cosmic-greeter to launch GNOME (wayland) successfully during the life of this project, it's possible my root cause is different (as the original report seems related to a recent-ish change) |
@XV-02 I don't suppose you've tried building a commit from a few months ago (or whenever you last remember it working) and seeing if you can |
Having looked at this recently, I have noted that the issues seem to crop up after 5d0999d or 8d91f3c though I'm unsure which. Beyond that, I don't have issues with launching KDE Plasma as a wayland session, nor Weston. Launching Gnome as an X11 session still works - though it can take a few attempts. I'm fairly certain it isn't Pop specific. Building and installing cosmic on base Ubuntu has the same issues. The first of these is a full log for a boot with two attempts to log in to Ubuntu with Gnome-Wayland before shutting down. The second is the same log with most of the initial boot-time kernel stuff and the shutdown stuff culled, as well as a number of bluetooth errors which didn't seem relevant, but were distracting. |
I'm uncertain when this began to be an issue, but I am finding I can no longer launch Gnome sessions using Wayland. I can launch Xorg Gnome sessions intermittently - though something in how those sessions launch is breaking Pop extensions for Gnome - but when ever I attempt to launch a Wayland session of Gnome, the screen goes black, as though it is launching a session, and immediately returns me to the
greeter
login prompt.The text was updated successfully, but these errors were encountered: