Unable to use Wayland

Bug #2039711 reported by Chris Casanova
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Purged ubuntu-desktop and gdm3 completely and reinstalled. Unable to login with Wayland, after about a minute or so of giving credentials for login, the login prompt reappears. X11 works, but takes about 3 minutes to actually load to desktop. Started two days ago after an update (I presume is the cause).

If I move .config from home directory, I am able to login to both again but will break within a few hours

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 18 12:05:19 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-02-08 (251 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.9-0ubuntu5
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Chris Casanova (cmcasanova) wrote :
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

We should probably treat the Wayland and X11 issues separately so I'll just focus on the former...

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Run these commands:
    journalctl -b0 > journal.txt
    journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

summary: - Unable to use Wayland; Long login times for X11
+ Unable to use Wayland
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Chris Casanova (cmcasanova) wrote :
Revision history for this message
Chris Casanova (cmcasanova) wrote :
Revision history for this message
Chris Casanova (cmcasanova) wrote :

I have multiple crash files:

_opt_brave.com_brave_brave.1000.crash
_usr_bin_gjs-console.1000.crash
_usr_lib_xorg_Xorg.0.crash
_opt_Signal_signal-desktop.1000.crash
_usr_libexec_goa-daemon.1000.crash

2. I have run the ubuntu-bug command against each (xorg required sudo due to being owned by root), each popped up with a bug submission, so I sent it, but was not provided with any bug IDs. How do I retrieve these? I assume the contents inside the .uploaded files:

0e5027b2-6cfe-11ee-9aee-fa163ec44ecd
7bb73989-6d05-11ee-9aee-fa163ec44ecd
c93998ea-6d12-11ee-9aee-fa163ec44ecd
254444a6-6dd2-11ee-9aef-fa163ec44ecd
06d5f3dc-6e29-11ee-9af3-fa163ec44ecd

3.
https://errors.ubuntu.com/oops/0e5027b2-6cfe-11ee-9aee-fa163ec44ecd
https://errors.ubuntu.com/oops/7bb73989-6d05-11ee-9aee-fa163ec44ecd
https://errors.ubuntu.com/oops/6df4c856-6d0d-11ee-b845-fa163e171f02
https://errors.ubuntu.com/oops/0d81f9c2-6d11-11ee-b846-fa163e171f02
https://errors.ubuntu.com/oops/254444a6-6dd2-11ee-9aef-fa163ec44ecd
https://errors.ubuntu.com/oops/06d5f3dc-6e29-11ee-9af3-fa163ec44ecd

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The problem is xdg-desktop-portal:

Oct 18 12:30:55 framework xdg-desktop-por[2907]: GError set over the top of a previous GError or uninitialized memory.
                                                 This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
                                                 The overwriting error message was: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gtk: Timeout was reached
Oct 18 12:30:55 framework xdg-desktop-por[2907]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached
Oct 18 12:30:55 framework xdg-desktop-por[2907]: No skeleton to export
Oct 18 12:31:08 framework systemd[2479]: <email address hidden>: start operation timed out. Terminating.

which may be a result of "Purged ubuntu-desktop and gdm3 completely and reinstalled". So I'd suggest reinstalling Ubuntu from scratch.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2019143, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.