Version-Release number of selected component: systemd-197-1.fc18.1 Additional info: backtrace_rating: 4 cmdline: /usr/lib/systemd/systemd-logind crash_function: log_assert executable: /usr/lib/systemd/systemd-logind kernel: 3.7.4-204.fc18.x86_64 remote_result: NOTFOUND uid: 0 Truncated backtrace: Thread no. 1 (7 frames) #2 log_assert at src/shared/log.c:702 #3 log_assert_failed at src/shared/log.c:707 #4 close_nointr_nofail at src/shared/util.c:209 #6 button_free at src/login/logind-button.c:73 #7 manager_process_button_device at src/login/logind.c:426 #8 manager_dispatch_button_udev at src/login/logind.c:915 #9 manager_run at src/login/logind.c:1661
Created attachment 693365 [details] File: backtrace
Created attachment 693366 [details] File: cgroup
Created attachment 693367 [details] File: core_backtrace
Created attachment 693369 [details] File: dso_list
Created attachment 693370 [details] File: environ
Created attachment 693371 [details] File: limits
Created attachment 693373 [details] File: maps
Created attachment 693374 [details] File: open_fds
Created attachment 693375 [details] File: proc_pid_status
Created attachment 693376 [details] File: smolt_data
Created attachment 693377 [details] File: var_log_messages
Thanks for the report. I can reproduce this by causing a hot-unplug of an ACPI button device.
Fixed in git.
*** Bug 924213 has been marked as a duplicate of this bug. ***
systemd-201-2.fc18.1 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/systemd-201-2.fc18.1
Package systemd-201-2.fc18.2: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.2' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.2 then log in and leave karma (feedback).
Package systemd-201-2.fc18.4: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.4' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.4 then log in and leave karma (feedback).
Package systemd-201-2.fc18.5: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.5 then log in and leave karma (feedback).
systemd-201-2.fc18.6 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6
Package systemd-201-2.fc18.6: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6 then log in and leave karma (feedback).
systemd-201-2.fc18.6 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.