When restoring after a screen blank (which I had set to 15 minutes), F39 sometimes has a segfault which kills my gnome session.
kernel shows a segfault in gnome-shell, then audit shows an ANOM_ABEND, then coredump dumps core.
The automatic problem reporting links to ABRT Analytics - Report #839457 - gnome-shell in js::HeapSlot::post(js::NativeObject*, js::HeapSlot::Kind, unsigned int, J..., where I’ve added my information.
If I set Screen Blank to never, this doesn’t happen (but I admittedly have not run it forever).
Is there anything else I can or should do?
Thanks,
Fred
Nov 30 13:23:51 mainbox rtkit-daemon[1478]: Successfully made thread 3166 of process 3139 (/usr/bin/gnome-shell) owned by '1000' high priority at nice level 0.
Nov 30 13:23:51 mainbox rtkit-daemon[1478]: Successfully made thread 3166 of process 3139 (/usr/bin/gnome-shell) owned by '1000' RT at priority 20.
Nov 30 13:23:53 mainbox rtkit-daemon[1478]: Successfully made thread 3166 of process 3139 (/usr/bin/gnome-shell) owned by '1000' high priority at nice level 0.
Nov 30 13:23:53 mainbox rtkit-daemon[1478]: Successfully made thread 3166 of process 3139 (/usr/bin/gnome-shell) owned by '1000' RT at priority 20.
Nov 30 13:23:53 mainbox audit: BPF prog-id=86 op=LOAD
Nov 30 13:23:53 mainbox systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Nov 30 13:23:53 mainbox systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Nov 30 13:23:53 mainbox audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 30 13:23:55 mainbox gdm-password][7533]: gkr-pam: unlocked login keyring
Nov 30 13:23:55 mainbox audit[7533]: USER_AUTH pid=7533 uid=0 auid=1000 ses=2 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_usertype,pam_localuser,pam_unix,pam_gnome_keyring acct="dad" exe="/usr/libexec/gdm-session-worker" hostname=mainbox addr=? terminal=/dev/tty1 res=success'
Nov 30 13:23:55 mainbox audit[7533]: USER_ACCT pid=7533 uid=0 auid=1000 ses=2 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="dad" exe="/usr/libexec/gdm-session-worker" hostname=mainbox addr=? terminal=/dev/tty1 res=success'
Nov 30 13:23:55 mainbox audit[7533]: CRED_REFR pid=7533 uid=0 auid=1000 ses=2 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_localuser,pam_unix,pam_gnome_keyring acct="dad" exe="/usr/libexec/gdm-session-worker" hostname=mainbox addr=? terminal=/dev/tty1 res=success'
Nov 30 13:23:55 mainbox gnome-shell[3139]: st_widget_get_theme_node called on the widget [0x5586271a4410 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndicator_WindowPreview.window-list-window-preview] which is not in the stage.
Nov 30 13:23:55 mainbox kernel: show_signal_msg: 53 callbacks suppressed
Nov 30 13:23:55 mainbox kernel: gnome-shell[3139]: segfault at 7fffe0000000 ip 00007f7cef792001 sp 00007ffe07b5ae20 error 4 in libmozjs-115.so.0.0.0[7f7ceeede000+a17000] likely on CPU 11 (core 5, socket 0)
Nov 30 13:23:55 mainbox kernel: Code: fa ff 53 48 83 ec 48 64 48 8b 04 25 28 00 00 00 48 89 44 24 38 48 8b 07 48 39 c2 73 7c 48 ba 00 00 f0 ff ff 7f 00 00 48 21 d0 <4c> 8b 20 4d 85 e4 74 67 49 8b 84 24 00 01 00 00 48 89 f3 48 39 c6
Nov 30 13:23:55 mainbox audit[3139]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=3139 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=11 res=1
Nov 30 13:23:55 mainbox gnome-shell[3139]: st_widget_get_theme_node called on the widget [0x5586271a4410 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndicator_WindowPreview.window-list-window-preview] which is not in the stage.
Nov 30 13:23:55 mainbox gnome-shell[3139]: st_widget_get_theme_node called on the widget [0x5586275c2760 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndicator_WindowPreview.window-list-window-preview] which is not in the stage.
Nov 30 13:23:55 mainbox gnome-shell[3139]: st_widget_get_theme_node called on the widget [0x5586275c2760 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndicator_WindowPreview.window-list-window-preview] which is not in the stage.
Nov 30 13:23:55 mainbox gnome-shell[3139]: st_widget_get_theme_node called on the widget [0x5586269490f0 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndicator_WindowPreview.window-list-window-preview] which is not in the stage.
Nov 30 13:23:55 mainbox gnome-shell[3139]: st_widget_get_theme_node called on the widget [0x5586269490f0 Gjs_window-list_gnome-shell-extensions_gcampax_github_com_workspaceIndicator_WindowPreview.window-list-window-preview] which is not in the stage.
Nov 30 13:23:55 mainbox systemd[1]: Created slice system-systemd\x2dcoredump.slice - Slice /system/systemd-coredump.
Nov 30 13:23:55 mainbox audit: BPF prog-id=87 op=LOAD
Nov 30 13:23:55 mainbox audit: BPF prog-id=88 op=LOAD
Nov 30 13:23:55 mainbox audit: BPF prog-id=89 op=LOAD
Nov 30 13:23:55 mainbox systemd[1]: Started systemd-coredump@0-7547-0.service - Process Core Dump (PID 7547/UID 0).
Nov 30 13:23:55 mainbox audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@0-7547-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 30 13:23:58 mainbox systemd-coredump[7548]: Process 3139 (gnome-shell) of user 1000 dumped core.