systemd-logind crashed with SIGABRT in session_start_scope()

Bug #1429544 reported by Paul Ortyl
134
This bug affects 20 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Expired
High
Unassigned

Bug Description

.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
Date: Sun Mar 8 10:13:11 2015
ExecutablePath: /lib/systemd/systemd-logind
InstallationDate: Installed on 2014-11-28 (99 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: LENOVO 2447MU0
ProcCmdline: /lib/systemd/systemd-logind
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-7-generic root=/dev/mapper/ubuntu--vg-root ro "acpi_osi=!Windows 2012" splash
Signal: 6
SourcePackage: systemd
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
SystemdDelta:
 [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED] /lib/systemd/system/graphical.target → /lib/systemd/system/graphical.target.d/xdiagnose.conf

 2 overridden configuration files found.
Title: systemd-logind crashed with SIGABRT
UpgradeStatus: Upgraded to vivid on 2015-03-08 (0 days ago)
UserGroups:

dmi.bios.date: 08/22/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: G5ETA0WW (2.60 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2447MU0
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG5ETA0WW(2.60):bd08/22/2014:svnLENOVO:pn2447MU0:pvrThinkPadW530:rvnLENOVO:rn2447MU0:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2447MU0
dmi.product.version: ThinkPad W530
dmi.sys.vendor: LENOVO

Revision history for this message
Paul Ortyl (ortylp) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 log_assert_failed (text=text@entry=0x7fc7e3236cf5 "s->user->slice", file=file@entry=0x7fc7e322efab "../src/login/logind-session.c", line=line@entry=501, func=func@entry=0x7fc7e3236fd0 <__PRETTY_FUNCTION__.12474> "session_start_scope") at ../src/shared/log.c:753
 session_start_scope (s=0x7fc7e42bea80) at ../src/login/logind-session.c:501
 session_start (s=0x7fc7e42bea80) at ../src/login/logind-session.c:552
 method_create_session.lto_priv.361 (bus=0xecd, message=0x7fc7e42c2f60, userdata=0x7fc7e42bea80, error=0x7fff93ee0228) at ../src/login/logind-dbus.c:794
 method_callbacks_run (found_object=<optimized out>, require_fallback=<optimized out>, c=<optimized out>, m=<optimized out>, bus=<optimized out>) at ../src/libsystemd/sd-bus/bus-objects.c:398

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in systemd (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Martin Pitt (pitti) wrote :

Can you please run

  sudo journalctl -u systemd-logind > /tmp/logind.txt

and attach /tmp/logind.txt here?

I hope you haven't rebooted yet since filing this bug (otherwise this won't be very useful)

information type: Private → Public
summary: - systemd-logind crashed with SIGABRT
+ systemd-logind crashed with SIGABRT in session_start_scope()
Changed in systemd (Ubuntu):
status: New → Incomplete
Revision history for this message
Paul Ortyl (ortylp) wrote :

Sorry, I have rebooted many times since then. (F**ed NVIDIA drivers)

Revision history for this message
Martin Pitt (pitti) wrote :

OK. I'm afraid I need to see the actual assertion message, which will be in the journal. If you can reproduce this assertion (i. e. it happens reasonably often), can you please save the output of "sudo journalctl -u systemd-logind" immediately?

Also, can you please attach /var/log/syslog? Perhaps the error message is still there.

Revision history for this message
Paul Ortyl (ortylp) wrote :

There is nothing in syslog.

Thould this crash repeat, I'll the logs.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]

Changed in systemd (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Brian Murray (brian-murray) wrote :
Changed in systemd (Ubuntu):
status: Expired → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
tags: added: bugpattern-needed
tags: added: wily
Changed in systemd (Ubuntu):
importance: Medium → High
Martin Pitt (pitti)
Changed in systemd (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]

Changed in systemd (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.