Bug 2257858 - [abrt] systemd: epoll_wait(): systemd killed by SIGABRT
Summary: [abrt] systemd: epoll_wait(): systemd killed by SIGABRT
Keywords:
Status: CLOSED DUPLICATE of bug 2203348
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 39
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:1e9a792b871249f23018c9a7dd2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-01-11 10:41 UTC by demo
Modified: 2024-05-10 06:42 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-10 06:42:59 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: proc_pid_status (1.48 KB, text/plain)
2024-01-11 10:41 UTC, demo 		no flags Details
File: maps (3.95 KB, text/plain)
2024-01-11 10:41 UTC, demo 		no flags Details
File: limits (1.29 KB, text/plain)
2024-01-11 10:41 UTC, demo 		no flags Details
File: environ (357 bytes, text/plain)
2024-01-11 10:42 UTC, demo 		no flags Details
File: open_fds (4.08 KB, text/plain)
2024-01-11 10:42 UTC, demo 		no flags Details
File: mountinfo (3.15 KB, text/plain)
2024-01-11 10:42 UTC, demo 		no flags Details
File: os_info (734 bytes, text/plain)
2024-01-11 10:42 UTC, demo 		no flags Details
File: cpuinfo (3.18 KB, text/plain)
2024-01-11 10:42 UTC, demo 		no flags Details
File: core_backtrace (2.54 KB, text/plain)
2024-01-11 10:42 UTC, demo 		no flags Details
File: dso_list (816 bytes, text/plain)
2024-01-11 10:42 UTC, demo 		no flags Details
File: var_log_messages (10.50 KB, text/plain)
2024-01-11 10:42 UTC, demo 		no flags Details
File: backtrace (19.29 KB, text/plain)
2024-01-11 10:42 UTC, demo 		no flags Details
View All

Description demo 2024-01-11 10:41:51 UTC 
Description of problem:
out of nowhere, while i was leaving my PC to rest, the screen hasn't fully blanked out and still emitted a bit of light. then, i was no longer able to bring the PC back up no matter if i pressed on my keyboard or moved my mouse, and had to do a full restart.

Version-Release number of selected component:
systemd-254.7-1.fc39

Additional info:
reporter:       libreport-2.17.11
type:           CCpp
reason:         systemd killed by SIGABRT
journald_cursor: s=81ba6297123545b7b30bfd90eacbeddc;i=1167d0;b=63824e1859ca422a83d3d902443b048d;m=3107ba41;t=60ea8f4023781;x=2305da74f4ab2cc0
executable:     /usr/lib/systemd/systemd
cmdline:        /usr/lib/systemd/systemd --user
cgroup:         0::/user.slice/user-1000.slice/user/init.scope
rootdir:        /
uid:            1000
kernel:         6.6.9-200.fc39.x86_64
package:        systemd-254.7-1.fc39
runlevel:       N 5
backtrace_rating: 4
crash_function: epoll_wait
comment:        out of nowhere, while i was leaving my PC to rest, the screen hasn't fully blanked out and still emitted a bit of light. then, i was no longer able to bring the PC back up no matter if i pressed on my keyboard or moved my mouse, and had to do a full restart.

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 epoll_wait at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
 #1 epoll_wait_usec at ../src/libsystemd/sd-event/sd-event.c:4567
 #2 process_epoll at ../src/libsystemd/sd-event/sd-event.c:4590
 #3 sd_event_wait at ../src/libsystemd/sd-event/sd-event.c:4713
 #4 sd_event_run at ../src/libsystemd/sd-event/sd-event.c:4862
 #5 manager_loop at ../src/core/manager.c:3224
 #6 invoke_main_loop at ../src/core/main.c:2012


Potential duplicate: bug 2203348
Comment 1 demo 2024-01-11 10:41:55 UTC 
Created attachment 2008229 [details]
File: proc_pid_status
Comment 2 demo 2024-01-11 10:41:57 UTC 
Created attachment 2008230 [details]
File: maps
Comment 3 demo 2024-01-11 10:41:59 UTC 
Created attachment 2008231 [details]
File: limits
Comment 4 demo 2024-01-11 10:42:01 UTC 
Created attachment 2008232 [details]
File: environ
Comment 5 demo 2024-01-11 10:42:03 UTC 
Created attachment 2008233 [details]
File: open_fds
Comment 6 demo 2024-01-11 10:42:04 UTC 
Created attachment 2008234 [details]
File: mountinfo
Comment 7 demo 2024-01-11 10:42:06 UTC 
Created attachment 2008235 [details]
File: os_info
Comment 8 demo 2024-01-11 10:42:07 UTC 
Created attachment 2008236 [details]
File: cpuinfo
Comment 9 demo 2024-01-11 10:42:09 UTC 
Created attachment 2008237 [details]
File: core_backtrace
Comment 10 demo 2024-01-11 10:42:11 UTC 
Created attachment 2008238 [details]
File: dso_list
Comment 11 demo 2024-01-11 10:42:13 UTC 
Created attachment 2008239 [details]
File: var_log_messages
Comment 12 demo 2024-01-11 10:42:15 UTC 
Created attachment 2008240 [details]
File: backtrace
Comment 13 Zbigniew Jędrzejewski-Szmek 2024-01-11 12:28:02 UTC 
Can you attach the logs? 'journalctl -b -X'

It looks like the user manager was aborted because of a timeout. So the problem is most likely on the kernel/driver level.
Comment 14 demo 2024-01-11 14:24:36 UTC 
i have no idea how to paste it onto here sadly, its a long log
Comment 15 Zbigniew Jędrzejewski-Szmek 2024-01-12 09:49:21 UTC 
Redirect the log to a file: 'journalctl -b -X >journal.txt' and then attach 'journal.txt'.
Comment 16 demo 2024-01-12 09:54:54 UTC 
https://gofile.io/d/ydebSd
Comment 17 Zbigniew Jędrzejewski-Szmek 2024-01-12 11:53:20 UTC 
Oh, this is not what is needed. The "-X" is a placeholder for a negative number, to select the right boot. You pasted the output for "-b -x" (lowercase), which gives the output for the current boot (Jan 12th).

Please do the following:
1. run 'journactl --list-boots' and in the list identify the one that ended in the crash (Jan 11th), this gives a number, e.g. 5.
2. run 'journalctl -b NUMBER', e.g. 'journactl -b 5'. Attach this output here.
Comment 18 demo 2024-01-12 11:59:04 UTC 
https://gofile.io/d/SNjRZO

My bad its taking so long, I'm new to Linux and Fedora in general.
If this is the incorrect one, I'll send a different number, the one I used was 23 that sent January 11th.
Comment 19 Zbigniew Jędrzejewski-Szmek 2024-01-12 13:01:01 UTC 
So we have a lot of things going on here: some updates, packagekit and gnome-software are active, discord is downloading an update... At least obs flatpak and gnome-shell segfault. But I'm not sure what is the initial cause. X11 programs often segfault when the graphical session is terminated in an unexpected way, so those crashes could be just a symptop of an earlier issue. It's possible that the failures were triggered by a background update that went wrong.

Once gnome-shell crashes, everything goes down. So the later errors are not really meanigful, they are caused by the X11 session going down. gnome-shell has loaded libnvidia-eglcore.so.545.29.06, and we can't really help with non-open-source software. 

Jan 11 12:23:20 fedora systemd[1]: Started user - User Manager for UID 42.
Jan 11 12:23:20 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=user@42 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 11 12:23:20 fedora systemd[1]: Started session-c2.scope - Session c2 of User gdm.
Jan 11 12:23:20 fedora gdm-launch-environment][7830]: pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=42) by (uid=0)
Jan 11 12:23:20 fedora audit[7830]: USER_START pid=7830 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_keyinit,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_umask acct="gdm" exe="/usr/libexec/gdm-session-worker" hostname=fedora addr=? terminal=/dev/tty1 res=success'
Jan 11 12:23:20 fedora systemd[7876]: Created slice session.slice - User Core Session Slice.
Jan 11 12:23:20 fedora systemd[7876]: Starting dbus-broker.service - D-Bus User Message Bus...
Jan 11 12:23:20 fedora dbus-broker-launch[7900]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Jan 11 12:23:20 fedora dbus-broker-launch[7900]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Jan 11 12:23:20 fedora systemd[7876]: Started dbus-broker.service - D-Bus User Message Bus.
Jan 11 12:23:20 fedora dbus-broker-launch[7900]: Ready
Jan 11 12:23:20 fedora /usr/libexec/gdm-wayland-session[7904]: dbus-daemon[7904]: [session uid=42 pid=7904] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=42 pid=7905 comm="/usr/libexec/gnome-session-binary --autostart /usr" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Jan 11 12:23:20 fedora /usr/libexec/gdm-wayland-session[7904]: dbus-daemon[7904]: [session uid=42 pid=7904] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Jan 11 12:23:20 fedora gnome-session[7905]: gnome-session-binary[7905]: WARNING: Could not check if unit gnome-session-wayland is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Jan 11 12:23:20 fedora gnome-session-binary[7905]: WARNING: Could not check if unit gnome-session-wayland is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Jan 11 12:23:20 fedora gnome-shell[7917]: Running GNOME Shell (using mutter 45.3) as a Wayland display server
Jan 11 12:23:20 fedora rtkit-daemon[1102]: Successfully made thread 7935 of process 7917 (/usr/bin/gnome-shell) owned by '42' RT at priority 20.
Jan 11 12:23:20 fedora gnome-shell[7917]: Made thread 'KMS thread' realtime scheduled
Jan 11 12:23:20 fedora systemd[1]: session-2.scope: Deactivated successfully.
Jan 11 12:23:20 fedora systemd[1]: session-2.scope: Consumed 2min 6.781s CPU time.
Jan 11 12:23:20 fedora systemd-logind[1122]: Removed session 2.
Jan 11 12:23:21 fedora systemd-coredump[7763]: Process 3200 (obs) of user 1000 dumped core.
                                               
                                               Stack trace of thread 11:
                                               #0  0x00007f4b8b2b7747 n/a (/app/lib/libobs.so.30 + 0xe6747)
                                               #1  0x00007f4b8b22cf51 n/a (/app/lib/libobs.so.30 + 0x5bf51)
                                               #2  0x00007f4b8728f25a n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f25a)
                                               #3  0x00007f4b87317fc4 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x117fc4)
                                               ELF object binary architecture: AMD x86-64
Jan 11 12:23:21 fedora systemd[1]: systemd-coredump: Deactivated successfully.
Jan 11 12:23:21 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@1-7723-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 11 12:23:21 fedora systemd[1]: systemd-coredump: Consumed 1.149s CPU time.
Jan 11 12:23:21 fedora audit: BPF prog-id=118 op=UNLOAD
Jan 11 12:23:21 fedora audit: BPF prog-id=117 op=UNLOAD
Jan 11 12:23:21 fedora audit: BPF prog-id=116 op=UNLOAD
Jan 11 12:23:21 fedora systemd-coredump[7722]: Process 4361 (Discord) of user 1000 dumped core.
                                               
                                               Stack trace of thread 177:
                                               #0  0x00007f4b988bee14 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x90e14)
                                               #1  0x00007f4b9886cdce n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x3edce)
                                               #2  0x00007f4b9885483f n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2683f)
                                               #3  0x00007f4b368837a3 n/a (/home/demo/.var/app/com.discordapp.Discord/config/discord/0.0.40/modules/discord_utils/discord_utils.node + 0x837a3)
                                               ELF object binary architecture: AMD x86-64
Jan 11 12:23:21 fedora systemd[1]: systemd-coredump: Deactivated successfully.
Jan 11 12:23:21 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@0-7714-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 11 12:23:21 fedora systemd[1]: systemd-coredump: Consumed 1.585s CPU time.
Jan 11 12:23:21 fedora systemd[2147]: app-flatpak-com.discordapp.Discord-2728.scope: Consumed 55.065s CPU time.
Jan 11 12:23:21 fedora audit: BPF prog-id=115 op=UNLOAD
Jan 11 12:23:21 fedora audit: BPF prog-id=114 op=UNLOAD
Jan 11 12:23:21 fedora audit: BPF prog-id=113 op=UNLOAD
Jan 11 12:23:21 fedora gnome-session[2501]: gnome-session-binary[2501]: WARNING: Could not get session class: No such device or address
Jan 11 12:23:21 fedora gnome-session-binary[2501]: WARNING: Could not get session class: No such device or address
Jan 11 12:23:21 fedora systemd[2147]: Stopped gnome-session-manager - GNOME Session Manager (session: gnome).
Jan 11 12:23:21 fedora systemd[2147]: Stopped target gnome-session-pre.target - Tasks to be run before GNOME Session starts.
Jan 11 12:23:21 fedora systemd[2147]: Stopped target graphical-session-pre.target - Session services which should run early before the graphical session is brought up.
Jan 11 12:23:21 fedora systemd[2147]: Reached target gnome-session-shutdown.target - Shutdown running GNOME Session.
Jan 11 12:23:21 fedora systemd[2147]: Starting gnome-session-restart-dbus.service - Restart DBus after GNOME Session shutdown...
Jan 11 12:23:21 fedora systemd[2147]: Stopped target gnome-session-shutdown.target - Shutdown running GNOME Session.
Jan 11 12:23:21 fedora systemd[2147]: Started gnome-session-restart-dbus.service - Restart DBus after GNOME Session shutdown.
Jan 11 12:23:21 fedora gnome-shell-calendar-server[2593]: gnome-shell-calendar-server[2593]: Lost (or failed to acquire) the name org.gnome.Shell.CalendarServer - exiting
Jan 11 12:23:21 fedora systemd[2147]: Stopping dbus-broker.service - D-Bus User Message Bus...
Jan 11 12:23:21 fedora dbus-broker[2371]: Dispatched 11461 messages @ 4(±7)μs / message.
Jan 11 12:23:21 fedora systemd[2147]: Stopped dbus-broker.service - D-Bus User Message Bus.
Jan 11 12:23:21 fedora systemd[2147]: Starting dbus-broker.service - D-Bus User Message Bus...
...
Jan 11 12:23:38 fedora systemd[2147]: app-flatpak-com.obsproject.Studio-2744.scope: Consumed 3min 42.346s CPU time.
Jan 11 12:23:56 fedora gnome-shell[7917]: Device '/dev/dri/card1' prefers shadow buffer
Jan 11 12:23:56 fedora gnome-shell[7917]: Added device '/dev/dri/card1' (nvidia-drm) using atomic mode setting.
Jan 11 12:23:56 fedora gnome-shell[7917]: Created gbm renderer for '/dev/dri/card1'
Jan 11 12:23:56 fedora gnome-shell[7917]: Boot VGA GPU /dev/dri/card1 selected as primary
Jan 11 12:23:56 fedora gnome-shell[7917]: Obtained a high priority EGL context
Jan 11 12:23:56 fedora gnome-shell[7917]: Obtained a high priority EGL context
Jan 11 12:23:57 fedora gnome-shell[7917]: Disabling DMA buffer screen sharing (implicit modifiers not supported)
Jan 11 12:23:57 fedora /usr/libexec/gdm-wayland-session[7904]: dbus-daemon[7904]: [session uid=42 pid=7904] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=42 pid=7917 comm="/usr/bin/gnome-shell" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Jan 11 12:23:57 fedora /usr/libexec/gdm-wayland-session[7904]: dbus-daemon[7904]: [session uid=42 pid=7904] Successfully activated service 'org.a11y.Bus'
Jan 11 12:23:57 fedora gnome-shell[7917]: Using public X11 display :1024, (using :1025 for managed services)
Jan 11 12:23:57 fedora gnome-shell[7917]: Using Wayland display name 'wayland-0'
Jan 11 12:23:57 fedora /usr/libexec/gdm-wayland-session[8210]: dbus-daemon[8210]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=42 pid=7917 comm="/usr/bin/gnome-shell" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Jan 11 12:23:57 fedora /usr/libexec/gdm-wayland-session[8210]: dbus-daemon[8210]: Successfully activated service 'org.a11y.atspi.Registry'
Jan 11 12:23:57 fedora /usr/libexec/gdm-wayland-session[8215]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jan 11 12:23:57 fedora gnome-shell[7917]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
Jan 11 12:23:57 fedora gnome-shell[7917]: Will monitor session c2
Jan 11 12:23:57 fedora /usr/libexec/gdm-wayland-session[7904]: dbus-daemon[7904]: [session uid=42 pid=7904] Activating service name='org.gnome.Shell.Screencast' requested by ':1.3' (uid=42 pid=7917 comm="/usr/bin/gnome-shell" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Jan 11 12:23:57 fedora /usr/libexec/gdm-wayland-session[7904]: dbus-daemon[7904]: [session uid=42 pid=7904] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=42 pid=7917 comm="/usr/bin/gnome-shell" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Jan 11 12:23:57 fedora /usr/libexec/gdm-wayland-session[7904]: dbus-daemon[7904]: [session uid=42 pid=7904] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
Jan 11 12:23:57 fedora /usr/libexec/gdm-wayland-session[7904]: dbus-daemon[7904]: [session uid=42 pid=7904] Activating service name='org.gnome.Shell.Notifications' requested by ':1.3' (uid=42 pid=7917 comm="/usr/bin/gnome-shell" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Jan 11 12:23:57 fedora gnome-shell[7917]: Extension apps-menu.github.com already installed in /usr/share/gnome-shell/extensions/apps-menu.github.com. /usr/share/gnome-shell/extensions/apps-menu.github.com will not be loaded
Jan 11 12:23:57 fedora gnome-shell[7917]: Extension background-logo already installed in /usr/share/gnome-shell/extensions/background-logo. /usr/share/gnome-shell/extensions/background-logo will not be loaded
Jan 11 12:23:57 fedora gnome-shell[7917]: Extension launch-new-instance.github.com already installed in /usr/share/gnome-shell/extensions/launch-new-instance.github.com. /usr/share/gnome-shell/extensions/launch-new-instance.github.com will not be loaded
Jan 11 12:23:57 fedora gnome-shell[7917]: Extension places-menu.github.com already installed in /usr/share/gnome-shell/extensions/places-menu.github.com. /usr/share/gnome-shell/extensions/places-menu.github.com will not be loaded
Jan 11 12:23:57 fedora gnome-shell[7917]: Extension window-list.github.com already installed in /usr/share/gnome-shell/extensions/window-list.github.com. /usr/share/gnome-shell/extensions/window-list.github.com will not be loaded
Jan 11 12:23:57 fedora gnome-shell[7917]: Extension appindicatorsupport.com already installed in /usr/share/gnome-shell/extensions/appindicatorsupport.com. /usr/share/gnome-shell/extensions/appindicatorsupport.com will not be loaded
Jan 11 12:23:57 fedora gnome-shell[7917]: Extension gamemode.me already installed in /usr/share/gnome-shell/extensions/gamemode.me. /usr/share/gnome-shell/extensions/gamemode.me will not be loaded
Jan 11 12:23:57 fedora gnome-shell[7917]: Extension pomodoro.in already installed in /usr/share/gnome-shell/extensions/pomodoro.in. /usr/share/gnome-shell/extensions/pomodoro.in will not be loaded
Jan 11 12:23:57 fedora gnome-shell[7917]: Extension unite already installed in /usr/share/gnome-shell/extensions/unite. /usr/share/gnome-shell/extensions/unite will not be loaded
Jan 11 12:23:57 fedora org.gnome.Shell.desktop[7917]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm/.config/mutter/sessions/10f5c35bb48ff196f4170496860055759800000079050000.ms”: No such file or directory
Jan 11 12:23:57 fedora systemd[1]: Starting packagekit.service - PackageKit Daemon...
Jan 11 12:23:57 fedora PackageKit[8247]: daemon start
Jan 11 12:23:57 fedora /usr/libexec/gdm-wayland-session[7904]: dbus-daemon[7904]: [session uid=42 pid=7904] Successfully activated service 'org.gnome.Shell.Notifications'
Jan 11 12:23:57 fedora audit: BPF prog-id=119 op=LOAD
Jan 11 12:23:57 fedora audit: BPF prog-id=120 op=LOAD
Jan 11 12:23:57 fedora audit: BPF prog-id=121 op=LOAD
Jan 11 12:23:57 fedora /usr/libexec/gdm-wayland-session[7904]: dbus-daemon[7904]: [session uid=42 pid=7904] Activating service name='org.freedesktop.systemd1' requested by ':1.9' (uid=42 pid=8249 comm="/usr/libexec/gsd-sharing" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Jan 11 12:23:57 fedora systemd[1]: Starting systemd-localed.service - Locale Service...
Jan 11 12:23:57 fedora /usr/libexec/gdm-wayland-session[7904]: dbus-daemon[7904]: [session uid=42 pid=7904] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Jan 11 12:23:57 fedora gsd-sharing[8249]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Jan 11 12:23:57 fedora gsd-sharing[8249]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Jan 11 12:23:57 fedora /usr/libexec/gdm-wayland-session[7904]: dbus-daemon[7904]: [session uid=42 pid=7904] Activating service name='org.freedesktop.portal.IBus' requested by ':1.23' (uid=42 pid=8297 comm="ibus-daemon --panel disable" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Jan 11 12:23:57 fedora /usr/libexec/gdm-wayland-session[7904]: dbus-daemon[7904]: [session uid=42 pid=7904] Successfully activated service 'org.freedesktop.portal.IBus'
Jan 11 12:23:57 fedora audit: BPF prog-id=122 op=LOAD
Jan 11 12:23:57 fedora audit: BPF prog-id=123 op=LOAD
Jan 11 12:23:57 fedora audit: BPF prog-id=124 op=LOAD
Jan 11 12:23:57 fedora systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
Jan 11 12:23:57 fedora systemd[1]: Started systemd-localed.service - Locale Service.
Jan 11 12:23:57 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 11 12:23:57 fedora systemd[1]: Started systemd-hostnamed.service - Hostname Service.
Jan 11 12:23:57 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 11 12:23:57 fedora kernel: rfkill: input handler disabled
Jan 11 12:23:57 fedora polkitd[1092]: Registered Authentication Agent for unix-session:c2 (system bus name :1.227 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jan 11 12:23:57 fedora systemd[1]: Started packagekit.service - PackageKit Daemon.
Jan 11 12:23:57 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=packagekit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 11 12:23:57 fedora gnome-shell[7917]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Jan 11 12:23:57 fedora NetworkManager[1330]: <info>  [1704968637.8768] agent-manager: agent[a478de5fbb8009ca,:1.227/org.gnome.Shell.NetworkAgent/42]: agent registered
Jan 11 12:23:57 fedora systemd[7876]: Started pipewire.service - PipeWire Multimedia Service.
Jan 11 12:23:57 fedora systemd[7876]: Started wireplumber.service - Multimedia Service Session Manager.
Jan 11 12:23:57 fedora systemd[7876]: Started pipewire-pulse.service - PipeWire PulseAudio.
Jan 11 12:23:57 fedora cupsd[1402]: REQUEST localhost - - "POST / HTTP/1.1" 200 359 Create-Printer-Subscriptions successful-ok
Jan 11 12:23:57 fedora gnome-shell[7917]: Failed to open sliced image: Operation was cancelled
Jan 11 12:23:57 fedora gnome-shell[7917]: Failed to open sliced image: Operation was cancelled
Jan 11 12:23:57 fedora wireplumber[8495]: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
Jan 11 12:23:57 fedora wireplumber[8495]: PipeWire's libcamera SPA missing or broken. libcamera not supported.
Jan 11 12:23:57 fedora audit: BPF prog-id=125 op=LOAD
Jan 11 12:23:58 fedora systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Jan 11 12:23:58 fedora systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Jan 11 12:23:58 fedora 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'
Jan 11 12:23:58 fedora systemd[1]: Starting realmd.service - Realm and Domain Configuration...
Jan 11 12:23:58 fedora gnome-shell[7917]: Failed to create offscreen effect framebuffer: Failed to create an OpenGL framebuffer object
Jan 11 12:23:58 fedora gnome-shell[7917]: Failed to create offscreen effect framebuffer: Failed to create an OpenGL framebuffer object
Jan 11 12:23:58 fedora kernel: gnome-shell[7917]: segfault at 1 ip 00007f51592b48b5 sp 00007fff4024e1e0 error 4 in libnvidia-eglcore.so.545.29.06[7f5158e27000+bc3000] likely on CPU 9 (core 4, socket 0)
Jan 11 12:23:58 fedora kernel: Code: 77 18 00 66 90 41 54 55 89 fd 53 48 89 f3 66 48 8d 3d 47 b4 55 01 66 66 48 e8 17 32 b7 ff 4c 8b 20 83 fd 0f 0f 87 94 56 b7 ff <0f> b6 43 01 48 8d 15 40 dd 5b 01 44 0f b6 03 8b 7c 82 34 0f b6 43
Jan 11 12:23:58 fedora audit[7917]: ANOM_ABEND auid=4294967295 uid=42 gid=42 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 pid=7917 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=11 res=1
Comment 20 Tomas Dolezal 2024-01-29 11:06:30 UTC 
normal boot on thunderbolt dock


reporter:       libreport-2.17.11
type:           CCpp
reason:         systemd killed by SIGABRT
journald_cursor: s=9eabd46b87b340f5ab033c592c781e93;i=2d4e946;b=958e7418763e4064afd463f898da2bdb;m=296a787c;t=610135d1bb249;x=fe0ee6851d5af482
executable:     /usr/lib/systemd/systemd
cmdline:        /usr/lib/systemd/systemd --user
cgroup:         0::/user.slice/user-986.slice/user/init.scope
rootdir:        /
uid:            986
kernel:         6.6.14-200.fc39.x86_64
package:        systemd-254.8-2.fc39
runlevel:       N 5
backtrace_rating: 4
crash_function: epoll_wait
comment:        normal boot on thunderbolt dock
Comment 21 Zbigniew Jędrzejewski-Szmek 2024-02-01 11:38:16 UTC 
> crash_function: epoll_wait

So the "crash" is really an abort when the program is stuck, waiting for the kernel to schedule it again.
As I wrote above, it's hard to figure out what is going on. Maybe the system is overloaded,
or maybe there are hardware problems.
Comment 22 alex.anoshkin 2024-03-18 07:18:24 UTC 
i just connected my external monitor and screens turned off


reporter:       libreport-2.17.11
type:           CCpp
reason:         systemd killed by SIGABRT
journald_cursor: s=103c73ee5db3484fb50e980e00bf7a85;i=2562b6;b=e5a1f938824f4a79af5db82e423841e4;m=b209c02;t=61052bca74bb6;x=808b5961183df2f0
executable:     /usr/lib/systemd/systemd
cmdline:        /usr/lib/systemd/systemd --user
cgroup:         0::/user.slice/user-42.slice/user/init.scope
rootdir:        /
uid:            42
kernel:         6.6.13-200.fc39.x86_64
package:        systemd-254.8-2.fc39
runlevel:       N 5
backtrace_rating: 4
crash_function: epoll_wait
comment:        i just connected my external monitor and screens turned off
Comment 23 SharxDC 2024-05-06 08:12:52 UTC 
lenovo yoga 6


reporter:       libreport-2.17.11
journald_cursor: s=a282882c17ae4702a6738da6e2885c79;i=2213c;b=1d68c2077c0f4dfbbb4da6418555e14e;m=89118ad1;t=617bbb57cb07b;x=6ddff15f2cd56adb
uid:            1000
kernel:         6.8.8-200.fc39.x86_64
comment:        lenovo yoga 6
executable:     /usr/lib/systemd/systemd
package:        systemd-254.10-1.fc39
cmdline:        /usr/lib/systemd/systemd --user
reason:         systemd killed by SIGABRT
cgroup:         0::/user.slice/user-1000.slice/user/init.scope
runlevel:       N 5
rootdir:        /
type:           CCpp
backtrace_rating: 4
crash_function: epoll_wait
Comment 24 David Tardon 2024-05-10 06:42:59 UTC 

*** This bug has been marked as a duplicate of bug 2203348 ***
Note You need to log in before you can comment on or make changes to this bug.