You are not logged in.
Hi!
I have updated the system, including Gnome to 46, a few days ago. Since then, I experience crashes for X11 sessions shortly after log-in -- I might manage to click on Terminal, it appears with some frame artifacts and then dies. Wayland session works well, though I need X11 for certain cases, where Nvidia causes artifacts on Wayland.
Of course, I have disabled all the extensions, the error persists.
Update:
Ok, it seems that if I open any app (e.g. the same terminal) with some delay (~20 sec) after login, it will not crash.
The same way -- adding any app in autostart
~/.config/autostart/
causes the crash.
I believe this is the relevant part of the journal:
Mar 30 09:51:47 werefkinarchi systemd-vconsole-setup[377]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument
Mar 30 09:51:47 werefkinarchi kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Mar 30 09:51:47 werefkinarchi kernel: cfg80211: failed to load regulatory.db
Mar 30 09:51:47 werefkinarchi systemd-vconsole-setup[508]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument
Mar 30 09:51:48 werefkinarchi bluetoothd[630]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 04:CB:88:D5:E8:82: Protocol not available
Mar 30 09:51:48 werefkinarchi bluetoothd[630]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 2C:4D:79:C3:44:F4: Protocol not available
Mar 30 09:51:53 werefkinarchi dbus-broker-launch[564]: Activation request for 'org.freedesktop.Avahi' failed: The systemd unit 'dbus-org.freedesktop.Avahi.service' could not be found.
Mar 30 09:51:53 werefkinarchi dbus-broker-launch[564]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
Mar 30 09:51:54 werefkinarchi /usr/lib/gdm-wayland-session[794]: dbus-daemon[794]: [session uid=120 pid=794] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Mar 30 09:51:55 werefkinarchi /usr/lib/gdm-wayland-session[794]: dbus-daemon[794]: [session uid=120 pid=794] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Mar 30 09:51:55 werefkinarchi org.gnome.Shell.desktop[1081]: libEGL warning: egl: failed to create dri2 screen
Mar 30 09:52:08 werefkinarchi /usr/lib/gdm-x-session[1292]: (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
Mar 30 09:52:08 werefkinarchi /usr/lib/gdm-x-session[1292]: xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted)
Mar 30 09:52:08 werefkinarchi /usr/lib/gdm-x-session[1292]: (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
Mar 30 09:52:09 werefkinarchi goa-daemon[1676]: /org/gnome/OnlineAccounts/Accounts/account_1707862168_0: Setting AttentionNeeded to TRUE because EnsureCredentials() failed with: No credentials found in the keyring (goa-error-quark, 4)
Mar 30 09:52:09 werefkinarchi gnome-software[1632]: Failed to load /usr/lib/gnome-software/plugins-20/libgs_plugin_fwupd.so: failed to open plugin /usr/lib/gnome-software/plugins-20/libgs_plugin_fwupd.so: libfwupd.so.2: cannot open shared object file: No such file or directory
and
Mar 30 09:53:04 werefkinarchi gsd-media-keys[2969]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/gnome/Shell”
Mar 30 09:53:05 werefkinarchi gsd-media-keys[2969]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/gnome/Shell”
Mar 30 09:53:05 werefkinarchi gnome-shell[3465]: Window manager error: Another compositing manager is already running on screen 0 on display “:0”.
Mar 30 09:53:05 werefkinarchi systemd[1240]: org.gnome.Shell@x11.service: Failed with result 'protocol'.
Mar 30 09:53:05 werefkinarchi systemd[1240]: Failed to start GNOME Shell on X11.
Mar 30 09:53:05 werefkinarchi systemd[1240]: org.gnome.Shell@x11.service: Triggering OnFailure= dependencies.
Mar 30 09:53:05 werefkinarchi systemd[1240]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 2.
Mar 30 09:53:05 werefkinarchi systemd[1240]: Started GNOME Session Failed lockdown screen (user).
Mar 30 09:53:05 werefkinarchi systemd[1240]: Reached target GNOME Session Failed.
Last edited by werefkin (2024-04-09 19:44:26)
Offline
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Offline
Hi!
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
I booted to Wayland session to produce it, and here it is: https://0x0.st/XzcH.txt
Offline
You're running Networkmanager, systemd-networkd and dhcpcd concurrently.
Disable the latter two, reboot and see whether the issue remains.
If yes, please don't start a second gnome session, log into a console (ctrl+alt+f3) and post the journal from there to prevent some clutter.
Offline
You're running Networkmanager, systemd-networkd and dhcpcd concurrently.
Disable the latter two, reboot and see whether the issue remains.If yes, please don't start a second gnome session, log into a console (ctrl+alt+f3) and post the journal from there to prevent some clutter.
Uh, my bad. Disabled the services. Though, the issue remains. Not even crash, but freeze. I did as you suggested. here is the journal https://0x0.st/Xzcj.txt, got it from another tty
Offline
@seth
just an important note, the session basically starts, but quickly falls into "Oh no something has gone wrong" state as soon as I open e.g. any program. Though, it is not 100% reproducible, but more then in 50% cases
UPD: cannot boot 3 times after the last successful
Last edited by werefkin (2024-03-30 20:23:23)
Offline
@seth, sorry for spamming, here is a bit more representative case https://0x0.st/Xzcw.txt, as the one before apparently did not contain
Mar 30 21:23:22 main-pc systemd[1241]: org.gnome.Shell@x11.service: Failed with result 'protocol'.
Mar 30 21:23:22 main-pc systemd[1241]: Failed to start GNOME Shell on X11.
Offline
dhcpcd is still running?
sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files'
This here looks suspicious:
Mar 30 21:22:45 main-pc gnome-shell[1426]: Running GNOME Shell (using mutter 46.0) as a X11 window and compositing manager
Mar 30 21:22:45 main-pc systemd[1241]: Starting flatpak document portal service...
Mar 30 21:22:45 main-pc systemd[1241]: Started flatpak document portal service.
Mar 30 21:23:05 main-pc systemd[1241]: Starting flatpak session helper...
Mar 30 21:23:05 main-pc systemd[1241]: Started flatpak session helper.
Mar 30 21:23:05 main-pc systemd[1241]: Started app-flatpak-org.keepassxc.KeePassXC-2395.scope.
Mar 30 21:23:20 main-pc gnome-shell[1426]: Running GNOME Shell (using mutter 46.0) as a X11 window and compositing manager
Mar 30 21:23:21 main-pc gnome-shell[2527]: Running GNOME Shell (using mutter 46.0) as a X11 window and compositing manager
Mar 30 21:23:22 main-pc systemd[1241]: Failed to start GNOME Shell on X11.
Mar 30 21:23:22 main-pc gnome-shell[2565]: Running GNOME Shell (using mutter 46.0) as a X11 window and compositing manager
Mar 30 21:23:24 main-pc systemd[1241]: Failed to start GNOME Shell on X11.
Mar 30 21:23:24 main-pc gnome-shell[2614]: Running GNOME Shell (using mutter 46.0) as a X11 window and compositing manager
Mar 30 21:23:25 main-pc systemd[1241]: Failed to start GNOME Shell on X11.
Mar 30 21:23:25 main-pc systemd[1241]: Failed to start GNOME Shell on X11.
Mar 30 21:24:02 main-pc systemd[1241]: Stopping flatpak session helper...
Mar 30 21:24:02 main-pc systemd[1241]: Stopping flatpak document portal service...
Mar 30 21:24:02 main-pc systemd[1241]: Stopped flatpak document portal service.
Mar 30 21:24:02 main-pc systemd[1241]: Stopped flatpak session helper.
Mar 30 21:24:13 main-pc gnome-shell[3378]: Running GNOME Shell (using mutter 46.0) as a X11 window and compositing manager
Mar 30 21:24:13 main-pc systemd[1241]: Starting flatpak document portal service...
Mar 30 21:24:14 main-pc systemd[1241]: Started flatpak document portal service.
Gnome starts, flatschpak starts, keepassxc starts as flatschpak, and then gnome restarts (same PID) and then enters a restart frenzy.
What if you disable/remove flatpak and esp. don't try to run keepassxc?
Offline
dhcpcd is still running?
Hm, should not be:
[werefkin@main-pc ~]$ sudo systemctl status dhcpcd
○ dhcpcd.service - DHCP/ IPv4LL/ IPv6RA/ DHCPv6 client on all interfaces
Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; disabled; preset: >
Active: inactive (dead)
sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files'
warning: cups: /etc/cups/classes.conf (Permissions mismatch)
warning: cups: /etc/cups/printers.conf (Permissions mismatch)
warning: cups: /etc/cups/subscriptions.conf (Permissions mismatch)
backup file: bluez: /etc/bluetooth/main.conf (Modification time mismatch)
backup file: bluez: /etc/bluetooth/main.conf (Size mismatch)
backup file: bluez: /etc/bluetooth/main.conf (SHA256 checksum mismatch)
backup file: cups: /etc/cups/printers.conf (Modification time mismatch)
backup file: cups: /etc/cups/printers.conf (Size mismatch)
backup file: cups: /etc/cups/printers.conf (SHA256 checksum mismatch)
backup file: cups: /etc/cups/subscriptions.conf (Modification time mismatch)
backup file: cups: /etc/cups/subscriptions.conf (Size mismatch)
backup file: cups: /etc/cups/subscriptions.conf (SHA256 checksum mismatch)
cups: 942 total files, 3 altered files
backup file: filesystem: /etc/fstab (Modification time mismatch)
backup file: filesystem: /etc/fstab (Size mismatch)
backup file: filesystem: /etc/fstab (SHA256 checksum mismatch)
backup file: filesystem: /etc/group (Modification time mismatch)
backup file: filesystem: /etc/group (Size mismatch)
backup file: filesystem: /etc/group (SHA256 checksum mismatch)
backup file: filesystem: /etc/gshadow (Modification time mismatch)
backup file: filesystem: /etc/gshadow (Size mismatch)
backup file: filesystem: /etc/gshadow (SHA256 checksum mismatch)
backup file: filesystem: /etc/passwd (Modification time mismatch)
backup file: filesystem: /etc/passwd (Size mismatch)
backup file: filesystem: /etc/passwd (SHA256 checksum mismatch)
backup file: filesystem: /etc/resolv.conf (Modification time mismatch)
backup file: filesystem: /etc/resolv.conf (Size mismatch)
backup file: filesystem: /etc/resolv.conf (SHA256 checksum mismatch)
backup file: filesystem: /etc/shadow (Modification time mismatch)
backup file: filesystem: /etc/shadow (Size mismatch)
backup file: filesystem: /etc/shadow (SHA256 checksum mismatch)
backup file: filesystem: /etc/shells (Modification time mismatch)
backup file: filesystem: /etc/shells (Size mismatch)
backup file: filesystem: /etc/shells (SHA256 checksum mismatch)
backup file: filesystem: /etc/subgid (Modification time mismatch)
backup file: filesystem: /etc/subgid (Size mismatch)
backup file: filesystem: /etc/subgid (SHA256 checksum mismatch)
backup file: filesystem: /etc/subuid (Modification time mismatch)
backup file: filesystem: /etc/subuid (Size mismatch)
backup file: filesystem: /etc/subuid (SHA256 checksum mismatch)
backup file: gdm: /etc/gdm/custom.conf (Modification time mismatch)
backup file: gdm: /etc/gdm/custom.conf (Size mismatch)
backup file: gdm: /etc/gdm/custom.conf (SHA256 checksum mismatch)
backup file: grub: /etc/default/grub (Modification time mismatch)
backup file: grub: /etc/default/grub (Size mismatch)
backup file: grub: /etc/default/grub (SHA256 checksum mismatch)
warning: intel-ucode: /boot/intel-ucode.img (Permissions mismatch)
intel-ucode: 159 total files, 1 altered file
warning: libutempter: /usr/lib/utempter/utempter (GID mismatch)
warning: libutempter: /usr/lib/utempter/utempter (Permissions mismatch)
libutempter: 20 total files, 1 altered file
backup file: lm_sensors: /etc/sensors3.conf (Modification time mismatch)
backup file: lm_sensors: /etc/sensors3.conf (Size mismatch)
backup file: lm_sensors: /etc/sensors3.conf (SHA256 checksum mismatch)
backup file: mkinitcpio: /etc/mkinitcpio.conf (Modification time mismatch)
backup file: mkinitcpio: /etc/mkinitcpio.conf (Size mismatch)
backup file: mkinitcpio: /etc/mkinitcpio.conf (SHA256 checksum mismatch)
backup file: openssh: /etc/ssh/ssh_config (Modification time mismatch)
backup file: openssh: /etc/ssh/ssh_config (Size mismatch)
backup file: openssh: /etc/ssh/ssh_config (SHA256 checksum mismatch)
backup file: pacman: /etc/pacman.conf (Modification time mismatch)
backup file: pacman: /etc/pacman.conf (Size mismatch)
backup file: pacman: /etc/pacman.conf (SHA256 checksum mismatch)
backup file: pacman-mirrorlist: /etc/pacman.d/mirrorlist (Modification time mismatch)
backup file: pacman-mirrorlist: /etc/pacman.d/mirrorlist (Size mismatch)
backup file: pacman-mirrorlist: /etc/pacman.d/mirrorlist (SHA256 checksum mismatch)
backup file: pam: /etc/security/faillock.conf (Modification time mismatch)
backup file: pam: /etc/security/faillock.conf (Size mismatch)
backup file: pam: /etc/security/faillock.conf (SHA256 checksum mismatch)
warning: shadow: /usr/bin/groupmems (GID mismatch)
warning: shadow: /usr/bin/groupmems (Permissions mismatch)
warning: systemd: /var/log/journal (GID mismatch)
warning: texlive-basic: /etc/texmf/tex/generic/config/language.dat (Modification time mismatch)
warning: texlive-basic: /etc/texmf/tex/generic/config/language.dat (Size mismatch)
warning: texlive-basic: /etc/texmf/tex/generic/config/language.dat (SHA256 checksum mismatch)
warning: texlive-basic: /etc/texmf/tex/generic/config/language.dat.lua (Modification time mismatch)
warning: texlive-basic: /etc/texmf/tex/generic/config/language.dat.lua (Size mismatch)
warning: texlive-basic: /etc/texmf/tex/generic/config/language.dat.lua (SHA256 checksum mismatch)
warning: texlive-basic: /etc/texmf/tex/generic/config/language.def (Modification time mismatch)
warning: texlive-basic: /etc/texmf/tex/generic/config/language.def (Size mismatch)
warning: texlive-basic: /etc/texmf/tex/generic/config/language.def (SHA256 checksum mismatch)
backup file: sane: /etc/sane.d/dll.conf (Modification time mismatch)
backup file: sane: /etc/sane.d/dll.conf (Size mismatch)
backup file: sane: /etc/sane.d/dll.conf (SHA256 checksum mismatch)
shadow: 588 total files, 1 altered file
backup file: sudo: /etc/sudoers (Modification time mismatch)
backup file: sudo: /etc/sudoers (Size mismatch)
backup file: sudo: /etc/sudoers (SHA256 checksum mismatch)
backup file: systemd: /etc/systemd/system.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/system.conf (Size mismatch)
backup file: systemd: /etc/systemd/system.conf (SHA256 checksum mismatch)
systemd: 1449 total files, 1 altered file
backup file: texlive-basic: /etc/texmf/web2c/fmtutil.cnf (Modification time mismatch)
backup file: texlive-basic: /etc/texmf/web2c/fmtutil.cnf (Size mismatch)
backup file: texlive-basic: /etc/texmf/web2c/fmtutil.cnf (SHA256 checksum mismatch)
texlive-basic: 2673 total files, 3 altered files
Gnome starts, flatschpak starts, keepassxc starts as flatschpak, and then gnome restarts (same PID) and then enters a restart frenzy.
What if you disable/remove flatpak and esp. don't try to run keepassxc?
I was super optimistic about it, removed keepassxc completely. it booted ~5 times without issue, but crashed on the 6th again.
here is a new journal:https://0x0.st/XzAL.txt
I don't see the same pattern here.
Offline
@seth
Ok, despite the absence of pattern, is there a way to
disable flatpak
temporary?
Offline
I think I have a similar issue after update to Gnome 46 documented here and I don't have flatpak.
@werefkin: do you also have problems rebooting, ie does sometimes a black screen with a X-shaped cursor come up instead of Gnome?
For me, if I reboot the black screen comes up. I have to shutdown and restart to get Gnome.
Then, if a crash happens in Gnome shortly after restart, this line in the journal comes up:
gnome-shell[708]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
which I have also seen in the journal you posted.
Doesn't this indicate a problem with mesa?
Offline
From the journal in #9
Mar 31 01:14:31 main-pc gnome-shell[1431]: Running GNOME Shell (using mutter 46.0) as a X11 window and compositing manager
Mar 31 01:14:53 main-pc gnome-shell[1431]: Running GNOME Shell (using mutter 46.0) as a X11 window and compositing manager
Mar 31 01:14:54 main-pc gnome-shell[2524]: Running GNOME Shell (using mutter 46.0) as a X11 window and compositing manager
Mar 31 01:14:55 main-pc systemd[1248]: Failed to start GNOME Shell on X11.
Mar 31 01:14:55 main-pc gnome-shell[2562]: Running GNOME Shell (using mutter 46.0) as a X11 window and compositing manager
Mar 31 01:14:56 main-pc systemd[1248]: Failed to start GNOME Shell on X11.
Mar 31 01:14:56 main-pc gnome-shell[2608]: Running GNOME Shell (using mutter 46.0) as a X11 window and compositing manager
Mar 31 01:14:58 main-pc systemd[1248]: Failed to start GNOME Shell on X11.
Mar 31 01:14:58 main-pc systemd[1248]: Failed to start GNOME Shell on X11.
The pattern is still there, it's just not caused by keepassxc.
There're many threads about "gnome46 occasionally doesn't start", there's probably some stupid race condition somewhere. Most of them however show some issue getting the screensaver state.
The problem here looks to be
Mar 31 01:14:31 main-pc gnome-shell[1431]: Running GNOME Shell (using mutter 46.0) as a X11 window and compositing manager
Mar 31 01:14:53 main-pc gnome-shell[1431]: Running GNOME Shell (using mutter 46.0) as a X11 window and compositing manager
Mar 31 01:14:54 main-pc gnome-shell[1431]: Window manager error: Another compositing manager is already running on screen 0 on display “:0”.
Mar 31 01:14:54 main-pc gnome-shell[2524]: Running GNOME Shell (using mutter 46.0) as a X11 window and compositing manager
Look at the PIDs and timestamps.
gnome-shell runs as 1431, then after 22s (which is suspiciously close to the 25s dbus timeout) tries tor run again (with the exact same PID), fails because there's already a compositor (being itself…) and tries to restart (which then subsequently fails and repeats a couple of times)
So this looks like gnome-shell nests itself, but I can't see why - it's not the flatpak and my best guess right now is (still) the collision between NM and dhcpcd.
Please post the output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
----
@tethys, the OP in your thread is probably caused by a bug in libx11, try to downgrade that to 1.8.7
Also Elmo says that S & T are not the same letter
(And the OP runs on nvidia anyway)
Offline
@seth
Hm, I am wondering how dhcpcd is still there, as I disabled the service.
Please post the output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
avahi-daemon.service | multi-user.target.wants
avahi-daemon.socket | sockets.target.wants
bluetooth-autoconnect.service | bluetooth.service.wants
bluetooth.service | bluetooth.target.wants
cups.path | multi-user.target.wants
cups.service | multi-user.target.wants
cups.service | printer.target.wants
cups.socket | sockets.target.wants
dbus-org.bluez.service | system
dbus-org.freedesktop.Avahi.service | system
dbus-org.freedesktop.home1.service | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service | system
dhcpcd@enp0s31f6.service | multi-user.target.wants
display-manager.service | system
gcr-ssh-agent.socket | sockets.target.wants
getty@tty1.service | getty.target.wants
gnome-keyring-daemon.socket | sockets.target.wants
kpbackup.timer | timers.target.wants
lm_sensors.service | multi-user.target.wants
NetworkManager-wait-online.service | network-online.target.wants
NetworkManager.service | multi-user.target.wants
p11-kit-server.socket | sockets.target.wants
pipewire-pulse.socket | sockets.target.wants
pipewire-session-manager.service | user
pipewire.socket | sockets.target.wants
remote-fs.target | multi-user.target.wants
systemd-homed-activate.service | systemd-homed.service.wants
systemd-homed.service | multi-user.target.wants
systemd-resolved.service | sysinit.target.wants
systemd-userdbd.socket | sockets.target.wants
wireplumber.service | pipewire.service.wants
xdg-user-dirs-update.service | default.target.wants
@tethys
Hm. no, i did not have problem with a restart, but with Suspend. Sometimes it is black screen after suspend, sometimes text is elements is gone + some visual artifacts. I am not sure though if the issues are related.
Offline
my best guess right now is (still) the collision between NM and dhcpcd.
@seth
OK, I just remove dhcpcd and test.
Last edited by werefkin (2024-03-31 09:00:55)
Offline
"dhcpcd@enp0s31f6.service" is the service you wanted to have disabled
Offline
"dhcpcd@enp0s31f6.service" is the service you wanted to have disabled
Let me test it within a day.
Last edited by werefkin (2024-03-31 19:21:27)
Offline
"dhcpcd@enp0s31f6.service" is the service you wanted to have disabled
Ah, no, I have removed the dhcpcd completely. It crashes anyways, here is the journal https://0x0.st/XzQu.txt
Was booting into a wayland session by mistake and though it is solved :-D
Offline
"dhcpcd@enp0s31f6.service" is the service you wanted to have disabled
Hm, just again to emphasize (i retested a few times again), I log in well into the X11 session, I can e.g. change the language/see hover over the app icon.
The crash happens only when I try to open any app. Then it the DE is unresponsive for some time (10-30secs), then the app shortly appears with some corrupted frames, and then the errors comes :-/
Offline
When you're not doing that (and wait until the system has "settled") does
Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
still appear?
I see neither timed nor ntp in the journal but there's
Mar 31 21:23:15 main-pc systemd[1204]: Starting GNOME date & time service...
Mar 31 21:23:15 main-pc systemd[1204]: Started GNOME date & time service.
Mar 31 21:23:15 main-pc systemd[1204]: Reached target GNOME date & time target.
Mar 31 21:23:40 main-pc systemd[1204]: Stopped target GNOME date & time target.
Mar 31 21:23:40 main-pc systemd[1204]: Stopping GNOME date & time service...
Mar 31 21:23:40 main-pc systemd[1204]: Stopped GNOME date & time service.
exactly around the crash (starts after your login, stops ~5s after the gnome-shell restart)
Offline
When you're not doing that (and wait until the system has "settled") does
Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
still appear?
I see neither timed nor ntp in the journal but there's
Mar 31 21:23:15 main-pc systemd[1204]: Starting GNOME date & time service... Mar 31 21:23:15 main-pc systemd[1204]: Started GNOME date & time service. Mar 31 21:23:15 main-pc systemd[1204]: Reached target GNOME date & time target. Mar 31 21:23:40 main-pc systemd[1204]: Stopped target GNOME date & time target. Mar 31 21:23:40 main-pc systemd[1204]: Stopping GNOME date & time service... Mar 31 21:23:40 main-pc systemd[1204]: Stopped GNOME date & time service.
exactly around the crash (starts after your login, stops ~5s after the gnome-shell restart)
No, I would not say that there is a "settling time" it is maybe ~50/50 a crash chance, though I did not do statistical analysis. I tried not to wait for a few minutes after each run, it did work in 3 cases, and crashed in 2.
I run out of ideas
Offline
Can (reliably) you head over to a different VT, run "xterm -display :1" from there (afaiu GDM stays on :0 and sets the session on :1) and then run stuff from the xterm inside gnome w/o crashing it?
Offline
Can (reliably) you head over to a different VT, run "xterm -display :1" from there (afaiu GDM stays on :0 and sets the session on :1) and then run stuff from the xterm inside gnome w/o crashing it?
I never user xterm, so not sure about
Xt error: Can't open display :1
and
DISPLAY is not set
btw, i have found that the issue is completely not unique: https://www.reddit.com/r/gnome/comments … n_startup/
Offline
Means there's no X11 server running on :1 - this is after the login?
Mar 31 21:23:14 main-pc /usr/lib/gdm-x-session[1250]: (--) Log file renamed from "/home/werefkin/.local/share/xorg/Xorg.pid-1250.log" to "/home/werefkin/.local/share/xorg/Xorg.0.log"
Might be ":0" after all because you're running GDM on wayland, https://wiki.archlinux.org/title/GDM#Use_Xorg_backend may be worth a shot here…
As previously mentioned there're a lot of these gnome "sometimes crashes on me" threads, but they don't invoke interaction and have different patterns in the journal
(Though ultimately the cause for things being broken is of course the same: you're using gnome )
Offline
Means there's no X11 server running on :1 - this is after the login?
yes, it is,
may be worth a shot here…
I did switch to X11 gdm, it didn't help
As previously mentioned there're a lot of these gnome "sometimes crashes on me" threads, but they don't invoke interaction and have different patterns in the journal
(Though ultimately the cause for things being broken is of course the same: you're using gnome)
I belive here the pattern is the same, though you might be right with such a great experince :-)
Offline
Have you tried "xterm -display :0" (or might now be :1 b/c GDM is on :0 )?
You can otherwise reliably start gnome and just let it sit there and do nothing for a long time?
The vector to merge yours w/ the other bugs is that everyone else is randomly autostarting stuff, b/c
The same way -- adding any app in autostart
[code]~/.config/autostart/[/code]
causes the crash.
Edit: in that light, what do the crashes look like for that condition?
Last edited by seth (2024-04-01 09:03:14)
Offline