Fedora 31: Gnome crash

[DrCox1911]

Nabend zusammen,

ich habe seit ein paar Wochen das Problem, dass bei meinem Fedora 31 die Gnome-Session abstürzt.
Distro-Info:
Fedora 31
Kernel 5.5.17
GNOME 3.34.5

Hier die Logs über journalctl vom entsprechenden Zeitraum mit dem Error-Filter:

Spoiler: journalctl --boot=-1 --priority=err

Apr 21 08:08:53 monster kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
Apr 21 08:08:56 monster kernel: usb 1-5: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1
Apr 21 08:08:56 monster kernel: usb 1-5: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1
Apr 21 08:08:56 monster kernel: usb 1-5: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1
Apr 21 08:08:56 monster kernel: usb 1-5: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1
Apr 21 08:09:23 monster gdm-password][1997]: gkr-pam: unable to locate daemon control file
Apr 21 08:09:23 monster systemd[2010]: Failed to start Application launched by gnome-session-binary.
Apr 21 08:09:24 monster kernel: usb 1-5: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1
Apr 21 08:09:24 monster kernel: usb 1-5: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1
Apr 21 08:09:24 monster kernel: usb 1-5: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1
Apr 21 08:09:24 monster kernel: usb 1-5: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1
Apr 21 08:09:25 monster systemd[2010]: Failed to start Application launched by gnome-session-binary.
Apr 21 08:14:31 monster kernel: usb 1-5: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1
Apr 21 09:10:01 monster anacron[6908]: Can't write to temporary file: Auf dem Gerät ist kein Speicherplatz mehr verfügbar
Apr 21 09:10:01 monster anacron[6908]: Aborted
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Keyboard handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Wacom handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Power management handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Color management.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Media keys handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Wacom handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Power management handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Keyboard handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Color management.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Media keys handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Color management.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Keyboard handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Power management handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Wacom handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Color management.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Keyboard handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Power management handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Wacom handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Media keys handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Color management.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Keyboard handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Power management handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Wacom handling.
Apr 21 09:41:36 monster systemd[2010]: Failed to start GNOME Media keys handling.
Apr 21 09:41:37 monster systemd[2010]: Failed to start GNOME Color management.
Apr 21 09:41:37 monster systemd[2010]: Failed to start GNOME Color management.
Apr 21 09:41:37 monster systemd[2010]: Failed to start GNOME Keyboard handling.
Apr 21 09:41:37 monster systemd[2010]: Failed to start GNOME Power management handling.
Apr 21 09:41:37 monster systemd[2010]: Failed to start GNOME Wacom handling.
Apr 21 09:41:37 monster kernel: usb 1-5: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1
Apr 21 09:41:37 monster kernel: usb 1-5: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1
Apr 21 09:41:37 monster kernel: usb 1-5: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1
Apr 21 09:41:37 monster kernel: usb 1-5: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1
Apr 21 09:41:40 monster systemd[7699]: Failed to start GNOME Power management handling.
Apr 21 09:41:40 monster systemd[7699]: Failed to start GNOME Keyboard handling.
Apr 21 09:41:40 monster systemd[7699]: Failed to start GNOME Wacom handling.
Apr 21 09:41:40 monster systemd[7699]: Failed to start GNOME Media keys handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Keyboard handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Wacom handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Media keys handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Power management handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Keyboard handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Wacom handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Power management handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Media keys handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Keyboard handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Wacom handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Power management handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Media keys handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Keyboard handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Keyboard handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Media keys handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Power management handling.
Apr 21 09:41:41 monster systemd[7699]: Failed to start GNOME Wacom handling.
Apr 21 09:41:44 monster systemd-coredump[7599]: Process 2109 (gnome-shell) of user 1000 dumped core.
                                                
                                                Stack trace of thread 2109:
                                                #0  0x00007fa392323625 raise (libc.so.6)

Es stürzt immer wieder bei anderen Sachen ab, so kann ich es z.B. reproduzieren, wenn ich mittels OBS mit dem Kodierer FFMPEG VAAPI eine Aufnahme versuche (beim Beenden der Aufnahme) oder so wie im oberen Fall habe ich ein sh-Script von mir, dass sich nur auf meinem Raspi per SSH verbindet, gleichzeitig im Terminal ausgeführt und anschließend im Gedit geöffnet. Parallel dazu war KeepassXC und Firefox offen.

 

[Linuxfreakgraz]

Ich nutze Fedora 31 auch als 3te Distribution auf meinem PC, auch mit Gnome, habe aber kein Problem.
Meine Frage lautet daher, welche Grafikkarte ist verbaut und welche Extensions sind Installiert?

Einmal schnell gegoogelt, könnte mit Wayland zusammenhängen, melde dich ab und wechsel auf xorg, neben dem Benutzernamen gibt es ein Zahnrad.

 

[DrCox1911]

Denke auch, dass es mit Wayland zusammenhängt und muss zugeben, dass ich mich mit Wayland beiweitem nicht so auskenne, wie mit Xorg.

Grafikkarte ist eine AMD Radeon Sapphire RX Vega 64 Nitro+. Mesa ist Version 19.2.8.
Als Gnome Erweiterungen habe ich:

• Background Logo
• Dash to Dock
• User Themes

Mit dem Wechsel zu Xorg könnten die Probleme in der Tat weg sein, aber mich würde immer noch interessieren, was das ist. Dann kann ich es reporten. Bin so auch etwas skeptisch, wie es dann mit Fedora 32 weiter geht. Fedora geht (meiner Meinung nach zurecht) strikt den Weg in Richtung Wayland.

 

[Linuxfreakgraz]

Bei https://bugzilla.redhat.com/ einen Bugreport erstellen.
Hilfreich dabei ist die Ausgabe von folgenden Befehlen.

journalctl SYSLOG_IDENTIFIER=gnome-session-binary -n 5

journalctl SYSLOG_IDENTIFIER=gnome-session -n 5

tail -n 5 ~/.xsession-errors

tail -f messages | grep 'localhost gnome-session'

Und im /var/log/syslog und im .cache/gdm/session.log nach Fehlern suchen.

https://fedoraproject.org/wiki/How_to_debug_Wayland_problems