Gnome-shell is crashing but ABRT leads to a dead end (segfault in libnvidia-glcore.so)

gnome-shell has been crashing at least once a day here, but attempts to report the problem through ABRT are leading to an old (Fedora 15!) bug. Apparently libnvidia-glcore.so is segfaullting (I’m using Nouveau driver BTW).

Is it really a dead end? I Or should I try to report it directly to nouveau devs? I could always try the proprietary driver, but for the time being I would like to stick to nouveau if possible.

1 Like

Hello @andre.ocosta ,
Do you have an output of the journal in particular the boot that crashed, and errors or - -priority=3. So journalctl -b -1 --priority=3

Hi @jakfrost , thanks for reaching out. The output follows below, but weirdly enough it shows only entries from yesterday around 8pm and 10pm (even though it also crashed today around 12pm BRT) :thinking:

-- Journal begins at Sun 2021-10-24 11:24:51 -03, ends at Fri 2021-11-12 13:43:10 -03. --
nov 11 20:22:32 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20210604/psargs-330)
nov 11 20:22:32 fedora kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20210604/psparse-529)
nov 11 20:22:32 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20210604/psargs-330)
nov 11 20:22:32 fedora kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20210604/psparse-529)
nov 11 20:22:32 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20210604/psargs-330)
nov 11 20:22:32 fedora kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20210604/psparse-529)
nov 11 20:22:32 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20210604/psargs-330)
nov 11 20:22:32 fedora kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20210604/psparse-529)
nov 11 20:22:32 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20210604/psargs-330)
nov 11 20:22:32 fedora kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20210604/psparse-529)
nov 11 20:22:32 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20210604/psargs-330)
nov 11 20:22:32 fedora kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20210604/psparse-529)
nov 11 20:22:32 fedora systemd[1]: Failed to start Setup Virtual Console.
nov 11 20:22:32 fedora systemd-vconsole-setup[278]: /usr/bin/loadkeys failed with exit status 1.
nov 11 20:22:32 fedora kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 3e6684 [ PRIVRING ]
nov 11 20:22:34 fedora systemd-vconsole-setup[555]: /usr/bin/loadkeys failed with exit status 1.
nov 11 20:22:34 fedora systemd[1]: Failed to start Setup Virtual Console.
nov 11 20:22:36 fedora systemd-vconsole-setup[607]: /usr/bin/loadkeys failed with exit status 1.
nov 11 20:22:36 fedora systemd[1]: Failed to start Setup Virtual Console.
nov 11 20:22:37 fedora /usr/sbin/irqbalance[853]: libcap-ng used by "/usr/sbin/irqbalance" failed due to not having CAP_SETPCAP in capng_apply
nov 11 20:22:37 fedora alsactl[961]: alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model (HDA Intel PCH at 0xf7200000 irq 30)
nov 11 20:22:37 fedora alsactl[961]: alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -6
nov 11 20:22:37 fedora alsactl[961]: alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model (HDA NVidia at 0xf7080000 irq 17)
nov 11 20:22:37 fedora alsactl[961]: alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -6
nov 11 20:22:39 fedora systemd-udevd[619]: vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME="vboxdrv".
nov 11 20:22:39 fedora systemd-udevd[631]: vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME="vboxdrvu".
nov 11 20:22:39 fedora systemd-udevd[619]: vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME="vboxnetctl".
nov 11 20:22:41 fedora gdm-launch-environment][1181]: Unable to get ecryptfs pam data : No module specific data is present
nov 11 20:22:42 fedora systemd[1186]: Unable to get ecryptfs pam data : No module specific data is present
nov 11 20:22:50 fedora gdm-password][1721]: gkr-pam: unable to locate daemon control file
nov 11 20:22:50 fedora gdm-password][1721]: Unable to get ecryptfs pam data : No module specific data is present
nov 11 20:22:50 fedora systemd[1738]: Unable to get ecryptfs pam data : No module specific data is present
nov 11 20:22:51 fedora systemd[1738]: Failed to start Application launched by gnome-session-binary.
nov 11 20:22:51 fedora systemd[1738]: Failed to start Application launched by gnome-session-binary.
nov 11 20:22:51 fedora systemd[1738]: Failed to start Application launched by gnome-session-binary.
nov 11 20:22:53 fedora systemd[1738]: Failed to start Application launched by gnome-session-binary.
nov 11 20:22:53 fedora systemd[1738]: Failed to start Application launched by gnome-session-binary.
nov 11 20:22:53 fedora systemd[1738]: Failed to start Application launched by gnome-session-binary.
nov 11 20:22:53 fedora systemd[1738]: Failed to start Application launched by gnome-session-binary.
nov 11 20:22:55 fedora gdm-launch-environment][1181]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
nov 11 22:25:05 fedora gdm[1154]: Gdm: Failed to list cached users: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer.
nov 11 22:25:05 fedora auditd[818]: plugin /usr/sbin/sedispatch terminated unexpectedly
nov 11 22:25:05 fedora sedispatch[7607]: sedispatch is exiting on stdin EOF

Let me know if you need any additional info. Cheers!

FWIW here’s the ABRT Analytics report for the latest crash (a couple of minutes ago).

Right before the crash, I noticed that Chrome (which was opened but I was not interacting with) showed a weird checkerboard-like pattern. After that, I was thrown to a console, and a couple of seconds later the login screen was shown. However, attempts to login were unsuccessful, it would go directly to the console and then a couple of seconds later back to the login screen again. I had to reboot.

Hello @andre.ocosta ,
Is this a new install or an upgrade? If either, I am assuming you are using Fedora Linux Workstation, if so can you do a sudo dnf update, or if it is Silverblue or Kinoite, or IoT, could you do an rpm-ostree update to make sure everything is okay? It seems to be related to the gnome-session and when I look at the related bug reports, oddly enough it seems the same fonts are also listed along with the gnome-session. I think that old issue is likely carried forward somewhere if it still exists, just may have another name.