Ubuntu Support Template
Ubuntu Version:
Ubuntu 24.04.4 LTS
Desktop Environment (if applicable):
GNOME 46
`XDG_SESSION_TYPE` is wayland when this problem occurs.
Problem Description:
As the title says, google chrome and any other electron app (vscode, Positron, etc…) fail to start on a wayland session. They run just fine under X11.
Running google-chrome on the terminal doesn’t return anything. It just hangs.
Relevant System Information:
Dell Inc. Precision 5480
If you launch vscode from the terminal, do you get any output?
@RuneHair Please fill out the support template correctly. It will make it much easier for us to help you.
If you really are using 24.04 and GNOME, then please remove Example as it is confusing.
If you are not using 24.04 and GNOME, then tell us what you are using.
Also, show us the output for echo $XDG_SESSION_TYPE
Thanks
Apologies. I’ve updated the OP to make it clear. Yes, I am not 24.04 and GNOME (just default desktop). I also added `XDG_SESSION_TYPE`, which is wayland.
Nope. code and positron just give back the prompt with no message.
ferdium and obsidian (both flatpak) return [2:0805/132944.164861:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory and hang like chrome. They give the same message under X11, though.
slack and mailspring hang the terminal just like chrome.
That quote there contradicts your edit in the original post; your original post says 24.04 and GNOME where you say there NOT 24.04 ?? A typo?
I’m on a newer release, and if I run google-chrome here I see
guiverc@d7050-next:/de2900/lubuntu_64$ google-chrome
[625974:626001:0805/140507.172782:ERROR:nss_util.cc(345)] After loading Root Certs, loaded==false: NSS error code: -8018
Fontconfig error: Cannot load default config file: No such file: (null)
and the browser opens (and continues playing a youtube music video I was likely listening to last time it was running); I’m using GNOME and a Wayland session myself too…
Next place I’d look is likely dmesg; looking for apparmor or other clues/stoppages (systemd journal next). Whilst Ubuntu apps (from Ubuntu repositories) have apparmor profiles setup for us, for third party packages like you mention they need to be added yourself.
Yes, that was a typo. “not” should’ve been “on”.
I don’t know how to do that. Is there any documentation or article I can follow?
Make sure dbys is running with:
sudo systemctl status dbus
if this is stopped, run:
sudo systemctl enable --now dbus
Which will start it and set it to run at boot.
A simple sudo dmesg lists the message on my terminal, and whilst I noted none with google-chrome on my release; an example I see there includes
[1062320.940565] audit: type=1400 audit(1785905624.299:228893): apparmor="DENIED" operation="mknod" class="file" profile="snap.brave.brave" name="/home/guiverc/snap/brave/654/.config/BraveSoftware/Brave-Browser/Default/Sessions/Session_13430379224299348" pid=8627 comm="ThreadPoolForeg" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[1062320.968355] audit: type=1400 audit(1785905624.326:228894): apparmor="DENIED" operation="mknod" class="file" profile="snap.brave.brave" name="/home/guiverc/snap/brave/654/.config/BraveSoftware/Brave-Browser/Default/Sessions/Tabs_13430379224327098" pid=8627 comm="ThreadPoolForeg" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
Timestamps for dmesg are not as readable, as they’re seconds from boot, but in contrast time stamps in the systemd journal are, which I can view with sudo journalctl
Those messages however go back months (don’t start again on reboot), even possibly to install.
Aug 05 14:59:07 d7050-next kernel: audit: type=1400 audit(1785905947.193:229206): apparmor="DENIED" operation="mknod" class="file" profile="snap.brave.brave" name="/home/guiverc/snap/brave/654/.config/BraveSoftware/Brave-Browser/Default/>
Aug 05 14:59:07 d7050-next kernel: audit: type=1400 audit(1785905947.207:229207): apparmor="DENIED" operation="mknod" class="file" profile="snap.brave.brave" name="/home/guiverc/snap/brave/654/.config/BraveSoftware/Brave-Browser/Default/>
( the whole of those lines didn’t fit in my terminal, and I didn’t bother adjusting to make it fit - I can search using standard POSIX search features like any Unix type of box )
If you want, you could try giving the app access to dbus in it’s sandbox. If you run:
flatpak list --app
Look for something like:
org.google.Chrome
and copy it. Then you can run:
flatpak override --socket=system-bus org.google.Chrome
if your ID is different, then adjust. You can then test the app with
flatpak run com.google.Chrome
Is it OK now? If so, repeat with the other apps that don’t run.
Sometimes a Snap update or Ubuntu kernel upgrade leaves the AppArmor profile slightly out of sync. Force Snapd to reload AppArmor profiles:
sudo snap refresh brave
Or disconnect and reconnect the home access interface to regenerate AppArmor rules:
sudo snap disconnect brave:home
sudo snap connect brave:home
I don’t think the dbus message is the issue. The apps seem to work ok on X11 with that message. Chrome and vscode are installed from debs and don’t run either without complaining. I am also not using snaps for any of those apps.
I don’t see any apparmor stuff.
These are messages that mention chrome
[ 344.859004] WARNING: drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/r535/rpc.c:164 at r535_gsp_msgq_wait+0x9d/0xb0 [nouveau], CPU#7: chrome/7280
[ 344.859363] CPU: 7 UID: 1001 PID: 7280 Comm: chrome Tainted: G W O 7.0.0-28-generic #28~24.04.1-Ubuntu PREEMPT(lazy)
[ 344.861900] nouveau 0000:01:00.0: chrome[7280]: VMM allocation failed: -110
[ 382.897731] WARNING: drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/r535/rpc.c:164 at r535_gsp_msgq_wait+0x9d/0xb0 [nouveau], CPU#10: chrome/7418
[ 382.898125] CPU: 10 UID: 1001 PID: 7418 Comm: chrome Tainted: G W O 7.0.0-28-generic #28~24.04.1-Ubuntu PREEMPT(lazy)
[ 382.900674] nouveau 0000:01:00.0: chrome[7418]: VMM allocation failed: -110
Well, I’m loosing my mind a bit here. Having found this, I tried with google-chrome --disable-gpu, which worked (eventually). So gpu seemed to be the issue. I decided to test if changing to the nvidia drivers would solve it, but when I tried, I got this error
So it reverted. After rebooting for good measure, I’m still using the open source drivers as before (so, no change) but chrome and electron apps do work. I have absolutely no idea what happened.
