[solved] chrome does not start in gnome wayland session

wuxb · 2021-05-14 21:12:25

Update: now (since gnome 40.1) you have to use gdm to start a good gnome-wayland session.

I have been starting gnome-wayland session from tty1 for a year or so. Maybe it's because the new gnome-40.1? I cannot start chrome. I can still use firefox and most other applications.
What's worse, vim (with gvim support) also hangs! I have to replace gvim with vim to get rid of the X11 hangs.

(g)vim, even running in the terminal, hangs on connecting to "/tmp/.X11-unix/X0". It looks the X11 part of the wayland/gnome is broken.

Here is what I see in journalctl -r
...
May 14 16:00:50 s7 gnome-session-binary[468]: WARNING: App 'pulseaudio.desktop' exited with code 1
May 14 16:00:50 s7 pulseaudio.desktop[648]: Failure: Timeout
May 14 15:59:59 s7 upowerd[553]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1.3/3-1.3:1.2/0003:046D:C52B.0007/0003:046D:406F.000A/power_sup>
May 14 15:59:57 s7 org.gnome.Shell.desktop[802]: Errors from xkbcomp are not fatal to the X server
May 14 15:59:57 s7 org.gnome.Shell.desktop[802]: > X11 cannot support keycodes above 255.
May 14 15:59:57 s7 org.gnome.Shell.desktop[802]: > Warning: Unsupported maximum keycode 569, clipping.
May 14 15:59:57 s7 org.gnome.Shell.desktop[802]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 14 15:59:57 s7 gnome-shell[506]: Failed to init X11 display: Unknown error
May 14 15:59:57 s7 gsd-media-keys[671]: Failed to grab accelerator for keybinding settings:playback-repeat
May 14 15:59:57 s7 gsd-media-keys[671]: Failed to grab accelerator for keybinding settings:hibernate
May 14 15:59:57 s7 gsd-media-keys[671]: Failed to grab accelerator for keybinding settings:rfkill
May 14 15:59:57 s7 gsd-media-keys[671]: Failed to grab accelerator for keybinding settings:playback-random
May 14 15:59:57 s7 geoclue[595]: variant_to_string: assertion 'len < max_len' failed
May 14 15:59:57 s7 geoclue[595]: variant_to_string: assertion 'len < max_len' failed
May 14 15:59:57 s7 gsd-usb-protect[645]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.usbguard1 was not provided by >
May 14 15:59:57 s7 gsd-usb-protect[645]: Failed to get screen saver status: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: GDBus.Error:org.freedesktop.DBus.Error.Servic>
May 14 15:59:57 s7 gnome-session-binary[468]: WARNING: Could not retrieve current screensaver active state: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: GDBus.Error:o>
May 14 15:59:57 s7 gsd-sharing[644]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
May 14 15:59:57 s7 gsd-sharing[644]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
May 14 15:59:57 s7 gsd-sharing[644]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
May 14 15:59:57 s7 gnome-shell[506]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
May 14 15:59:57 s7 geoclue[595]: Failed to connect to avahi service: Daemon not running
May 14 15:59:56 s7 org.gnome.Shell.desktop[540]: glamor: No eglstream capable devices found
May 14 15:59:55 s7 gnome-session-binary[468]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
May 14 15:59:55 s7 gnome-session-binary[468]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name ">
May 14 15:59:55 s7 gnome-session-binary[468]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.syste>
May 14 15:59:55 s7 gnome-session-binary[468]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.sys>

Last edited by wuxb (2021-05-15 19:26:33)

GaKu999 · 2021-05-15 07:34:51

So, pulseaudio is failing, Xwayland failed to start, the screensaver is messed up, and gnome has some other failures hrm...

Post the output of:

uname -r
cat /etc/os-release

Also post the full log to a pastebin server and post the link, preferably a plaintext one like ix.io

wuxb · 2021-05-15 08:11:12

Switching between `linux` and `linux-lts` does not make a difference: 5.10.36-1-lts, 5.12.3.arch1-1
Does this ever matter?:
$ cat /etc/os-release
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://www.archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"
LOGO=archlinux

https://gist.github.com/wuxb45/8a906e2e … c70b1c55e2

Last edited by wuxb (2021-05-15 08:11:40)

GaKu999 · 2021-05-15 09:32:24

What is your init system?
The reason I ask, is because what is happening at this log is not normal, or at least doesn't appear normal for an ArchLinux install.

Otherwise I'm out of ideas.

CarbonChauvinist · 2021-05-15 12:36:21

What's the reasoning for starting from tty1 instead of using gdm? I'm curious because the issues are most likely correlated.

GNOME arch wiki wrote:

GNOME can be started either graphically with a display manager or manually from the console (some features may be missing).

(emphasis mine)

Are you starting using the `dbus-run-session ...` blurb referenced in the wiki? If so, read the talk section further and decide if this is something you still want to do.

Last edited by CarbonChauvinist (2021-05-15 12:37:11)

wuxb · 2021-05-15 18:21:29

Thank you all!
I'm using the default systemd. There was some problem with gdm a few months ago. Was related to Bluetooth or sound I believe. So we switched to manual starting exactly as the wiki says. It has been ok for quite some time. I think I should just try gdm again.

wuxb · 2021-05-15 19:25:02

gdm works. Directly starting a gnome-wayland session is now broken.

Vortex375 · 2021-07-18 00:07:52

I ran into a similar issue today with exactly the same symptoms - can't start chromium browser or other X11 applications.

For me, it turned out that I had added

GDK_BACKEND=wayland

to a file in ~/.config/environment.d, and apparently you are not supposed to set this on Gnome startup - it prevents Xwayland from starting.

The error message that I got was

gnome-shell[873]: Failed to initialize X11 display: Failed to initialize GDK

I don't think gdm is required. I can still launch gnome-session from TTY. Just make sure you don't set GDK_BACKEND in your startup script.

Arch Linux

#1 2021-05-14 21:12:25

[solved] chrome does not start in gnome wayland session

#2 2021-05-15 07:34:51

Re: [solved] chrome does not start in gnome wayland session

#3 2021-05-15 08:11:12

Re: [solved] chrome does not start in gnome wayland session

#4 2021-05-15 09:32:24

Re: [solved] chrome does not start in gnome wayland session

#5 2021-05-15 12:36:21

Re: [solved] chrome does not start in gnome wayland session

#6 2021-05-15 18:21:29

Re: [solved] chrome does not start in gnome wayland session

#7 2021-05-15 19:25:02

Re: [solved] chrome does not start in gnome wayland session

#8 2021-07-18 00:07:52

Re: [solved] chrome does not start in gnome wayland session

Board footer