Bug 907890

Summary:

[abrt] systemd-197-1.fc18.1: log_assert: Process /usr/lib/systemd/systemd-logind was killed by signal 6 (SIGABRT)

Product:

[Fedora] Fedora

Reporter:

laufor

Component:

systemd

Assignee:

systemd-maint

Status:

CLOSED ERRATA

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

unspecified

Docs Contact:

Priority:

unspecified

Version:

CC:

johannbg, lnykryn, metherid, mschmidt, msekleta, mtoman, notting, plautrba, systemd-maint, vpavlin

Target Milestone:

---

Target Release:

---

Hardware:

x86_64

OS:

Unspecified

Whiteboard:

abrt_hash:dcd05495dd5485efedaf4b0b826f7c8593b8762c

Fixed In Version:

systemd-201-2.fc18.6

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2013-05-16 02:58:14 UTC

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
File: backtrace	none
File: cgroup	none
File: core_backtrace	none
File: dso_list	none
File: environ	none
File: limits	none
File: maps	none
File: open_fds	none
File: proc_pid_status	none
File: smolt_data	none
File: var_log_messages	none

Description laufor 2013-02-05 13:30:54 UTC

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

Comment 1 laufor 2013-02-05 13:30:58 UTC

Created attachment 693365 [details]
File: backtrace

Comment 2 laufor 2013-02-05 13:31:01 UTC

Created attachment 693366 [details]
File: cgroup

Comment 3 laufor 2013-02-05 13:31:04 UTC

Created attachment 693367 [details]
File: core_backtrace

Comment 4 laufor 2013-02-05 13:31:06 UTC

Created attachment 693369 [details]
File: dso_list

Comment 5 laufor 2013-02-05 13:31:08 UTC

Created attachment 693370 [details]
File: environ

Comment 6 laufor 2013-02-05 13:31:12 UTC

Created attachment 693371 [details]
File: limits

Comment 7 laufor 2013-02-05 13:31:18 UTC

Created attachment 693373 [details]
File: maps

Comment 8 laufor 2013-02-05 13:31:20 UTC

Created attachment 693374 [details]
File: open_fds

Comment 9 laufor 2013-02-05 13:31:22 UTC

Created attachment 693375 [details]
File: proc_pid_status

Comment 10 laufor 2013-02-05 13:31:24 UTC

Created attachment 693376 [details]
File: smolt_data

Comment 11 laufor 2013-02-05 13:31:26 UTC

Created attachment 693377 [details]
File: var_log_messages

Comment 12 Michal Schmidt 2013-02-05 13:51:13 UTC

Thanks for the report.
I can reproduce this by causing a hot-unplug of an ACPI button device.

Comment 13 Lennart Poettering 2013-03-07 15:49:28 UTC

Fixed in git.

Comment 14 Harald Hoyer 2013-03-21 11:50:07 UTC

*** Bug 924213 has been marked as a duplicate of this bug. ***

Comment 15 Fedora Update System 2013-04-10 20:12:44 UTC

systemd-201-2.fc18.1 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/systemd-201-2.fc18.1

Comment 16 Fedora Update System 2013-04-11 23:25:46 UTC

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).

Comment 17 Fedora Update System 2013-04-16 00:00:07 UTC

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).

Comment 18 Fedora Update System 2013-04-18 02:37:40 UTC

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).

Comment 19 Fedora Update System 2013-05-07 13:39:48 UTC

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

Comment 20 Fedora Update System 2013-05-09 10:02:15 UTC

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).

Comment 21 Fedora Update System 2013-05-16 02:58:14 UTC

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.