You are not logged in.
Pages: 1
After updating today Firefox is not starting normally. The window remains a plain background color area.
The not depiced closing button is working.
Sometimes after many minutes, the old session is displayed, but the browser is not responsive.
System is up to date and I rebooted. I am using gnome.
I have no clue how to debug this and apparently it seems not to be a general issue, as I couldn't find a relevant topic here.
One thing I saw in journal was:
Feb 04 10:57:45 rahmen gnome-shell[3729]: Received error from D-Bus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatableOffline
https://wiki.archlinux.org/title/Firefo … shoot_Mode
https://wiki.archlinux.org/title/Firefox#Xwayland (try enforcing 0 and 1)
Received error from D-Bus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown
loginctl session-status
echo $DBUS_SESSION_BUS_ADDRESS(Might be completely irrelevant, tough)
Offline
Safe-mode worked today, but I tried this before and then it took long too.
I have `MOZ_ENABLE_WAYLAND=1` in my envvars.
I can check if changing this makes a difference.
If I set this to 0 in terminal and start fireox from terminal it opens normally. But I get a message `ATTENTION: default value of option mesa_glthread overridden by environment.`
If I set it back to 1, it does not start propperly.
Additional info, I installed firefox nightly and it does start normally.
Regarding the dbus topic:
[jacob@rahmen ~]$ loginctl session-status
3 - jacob (1000)
Since: Wed 2026-02-04 10:52:02 CET; 2h 19min ago
State: active
Leader: 3166 (gdm-session-wor)
Seat: seat0; vc2
TTY: tty2
Remote: no
Service: gdm-password
Type: wayland
Class: user
Idle: no
Unit: session-3.scope
├─3166 "gdm-session-worker [pam/gdm-password]"
├─3665 /usr/lib/gdm-wayland-session /usr/bin/gnome-session
└─3693 /usr/lib/gnome-session-init-worker gnome
Feb 04 10:52:03 rahmen gnome-session-i[3693]: Starting GNOME session target: gnome-session-wayland@gnome>
Feb 04 11:49:44 rahmen systemd[1]: session-3.scope: Unit now frozen-by-parent.
Feb 04 11:55:30 rahmen systemd[1]: session-3.scope: Unit now thawed.
Feb 04 11:55:42 rahmen gdm-password][18482]: gkr-pam: unlocked login keyring
Feb 04 12:47:18 rahmen systemd[1]: session-3.scope: Unit now frozen-by-parent.
Feb 04 13:44:33 rahmen systemd[1]: session-3.scope: Unit now thawed.
Feb 04 13:44:38 rahmen gdm-password][58578]: gkr-pam: unlocked login keyring
Feb 04 14:10:40 rahmen systemd[1]: session-3.scope: Unit now frozen-by-parent.
Feb 05 14:27:59 rahmen systemd[1]: session-3.scope: Unit now thawed.
Feb 05 14:28:15 rahmen gdm-password][85537]: gkr-pam: unlocked login keyring
[jacob@rahmen ~]$ echo $DBUS_SESSION_BUS_ADDRESS
unix:path=/run/user/1000/busLast edited by Simaryp (2026-02-05 13:41:19)
Offline
I did a refresh when starting in safe-mode and now it seems to work again.
Offline
In case and please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
Pages: 1