systemd-logind crashed with SIGABRT in udev_device_get_sysattr_value()

Bug #1431141 reported by cariboo
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I just installed vivid on a Toshiba Satelite C50-B, this error shows up on every restart.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
Uname: Linux 3.19.0-8-generic x86_64
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
Date: Wed Mar 11 18:39:11 2015
ExecutablePath: /lib/systemd/systemd-logind
InstallationDate: Installed on 2015-03-11 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
 Bus 001 Device 003: ID 04f2:b446 Chicony Electronics Co., Ltd
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: TOSHIBA Satellite C50-B
ProcCmdline: /lib/systemd/systemd-logind
ProcEnviron:
 LANG=en_CA.UTF-8
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic root=UUID=dde4b40f-5d21-4e42-a8f9-c45a4c1256ba ro quiet splash
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __read_nocancel () at ../sysdeps/unix/syscall-template.S:81
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: systemd-logind crashed with SIGABRT in __read_nocancel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 12/11/2014
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 1.70
dmi.board.asset.tag: *
dmi.board.name: ZBWAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnTOSHIBA:bvr1.70:bd12/11/2014:svnTOSHIBA:pnSatelliteC50-B:pvrPSCMLC-02Y00T:rvnTOSHIBA:rnZBWAA:rvr1.00:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: Satellite C50-B
dmi.product.version: PSCMLC-02Y00T
dmi.sys.vendor: TOSHIBA

Revision history for this message
cariboo (cariboo) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __read_nocancel () at ../sysdeps/unix/syscall-template.S:81
 __read_alias () at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
 udev_device_get_sysattr_value (udev_device=0x7f8966729660, sysattr=0x7f89655a01c8 "status") at ../src/libudev/libudev-device.c:1486
 manager_count_displays (m=<optimized out>) at ../src/login/logind-core.c:539
 manager_is_docked_or_multiple_displays (m=<optimized out>) at ../src/login/logind-core.c:558

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
Martin Pitt (pitti)
summary: - systemd-logind crashed with SIGABRT in __read_nocancel()
+ systemd-logind crashed with SIGABRT in udev_device_get_sysattr_value()
information type: Private → Public
Revision history for this message
Martin Pitt (pitti) wrote :

This crashes on reading /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/status, but there is no assertion message or similar. Can you please do

   cat /sys/class/drm/card0*/*status

in a terminal? Does that give you any error message? Please copy&paste it here. Thanks!

Changed in systemd (Ubuntu):
status: New → Incomplete
Revision history for this message
Martin Pitt (pitti) wrote :

Also, after this happens the output of

  journalctl -b -u systemd-logind.service

would be helpful.

Revision history for this message
Jason (jasraimondo) wrote :

Hi,
I'm having the same error, here are the results from those commands:

jason@Jason-Laptop:~$ cat /sys/class/drm/card0*/*status
disconnected
connected
disconnected
jason@Jason-Laptop:~$ journalctl -b -u systemd-logind.service
No journal files were found.
jason@Jason-Laptop:~$

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

> $ journalctl -b -u systemd-logind.service
> No journal files were found.

Ah, apparently you are not in the "adm" group. Can you please re-try with

  sudo journalctl -b -u systemd-logind.service

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.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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