Version-Release number of selected component: systemd-221-1.fc23 Additional info: reporter: libreport-2.6.0 backtrace_rating: 4 cmdline: /usr/lib/systemd/systemd-journald crash_function: log_assert_failed executable: /usr/lib/systemd/systemd-journald global_pid: 567 kernel: 4.1.0-1.fc23.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #2 log_assert_failed at ../src/basic/log.c:773 #3 device_get_id_filename at ../src/libsystemd/sd-device/sd-device.c:1194 #4 device_read_db_aux.constprop.93 at ../src/libsystemd/sd-device/sd-device.c:1256 #5 device_read_db at ../src/libsystemd/sd-device/sd-device.c:1328 #6 sd_device_get_devlink_first at ../src/libsystemd/sd-device/sd-device.c:1406 #7 udev_device_get_devlinks_list_entry at ../src/libudev/libudev-device.c:710 #8 dev_kmsg_record at ../src/journal/journald-kmsg.c:247 #9 server_read_dev_kmsg.lto_priv.253 at ../src/journal/journald-kmsg.c:348 #10 source_dispatch.lto_priv.251 at ../src/libsystemd/sd-event/sd-event.c:2116 #11 sd_event_dispatch at ../src/libsystemd/sd-event/sd-event.c:2472
Created attachment 1045075 [details] File: backtrace
Created attachment 1045076 [details] File: cgroup
Created attachment 1045077 [details] File: core_backtrace
Created attachment 1045078 [details] File: dso_list
Created attachment 1045079 [details] File: environ
Created attachment 1045080 [details] File: limits
Created attachment 1045081 [details] File: maps
Created attachment 1045082 [details] File: mountinfo
Created attachment 1045083 [details] File: namespaces
Created attachment 1045084 [details] File: open_fds
Created attachment 1045085 [details] File: proc_pid_status
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
I have same crash happened to me and this kills Xserver and I can't even responded but ABRT catch the bug and add me to CC but still this is very very problematic bug, because It's killed my Xserver. I was just downgrading my gedit (for reverse bug) and i opened/closed and Selinux warning pop-up and systemd crashed and then X death and force reboot happened. Thank you
Do you need additional data for resolving this bug? It crashed for me even with systemd-222-6.fc23
This has happened to me several times and always got logged out of my user session instantaneously. That's very inconvenient. I see this error line in journal when it happened: systemd-journald[484]: Assertion 'subsystem' failed at src/libsystemd/sd-device/sd-device.c:1194, function device_get_id_filename(). Aborting.
I got this assertion failure today. The upstream fix is: https://github.com/systemd/systemd/commit/bf4c113e179650c07a8f95a14d71f365dbfe66e4
*** Bug 1279007 has been marked as a duplicate of this bug. ***
*** Bug 1247172 has been marked as a duplicate of this bug. ***
I get hit by this bug twice a week, it's frustrating loosing the whole session. Willing to test a package if needed.
I'm working on a batch of patches for F23 now, including this one.
*** Bug 1291115 has been marked as a duplicate of this bug. ***
systemd-222-9.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-76fc543765
systemd-222-10.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-76fc543765
systemd-222-10.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update systemd' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-76fc543765
systemd-222-10.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.