plymouthd crashed with SIGSEGV in exit()

Bug #945802 reported by KrzysiekT
22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

don't know any details

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Mar 3 19:56:13 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
Disassembly: => 0x12088: Cannot access memory at address 0x12088
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 003: ID 5986:01a6 Acer, Inc Lenovo Integrated Webcam
MachineType: LENOVO 05962RU
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=/dev/sda5 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=/dev/sda5 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x12088: Cannot access memory at address 0x12088
 PC (0x00012088) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ?? ()
 ?? () from /lib64/ld-linux-x86-64.so.2
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 exit () from /lib/x86_64-linux-gnu/libc.so.6
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in exit()
UpgradeStatus: Upgraded to precise on 2012-02-29 (3 days ago)
UserGroups: pkcs11
dmi.bios.date: 11/03/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8FET32WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 05962RU
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8FET32WW(1.16):bd11/03/2011:svnLENOVO:pn05962RU:pvrThinkPadX120e:rvnLENOVO:rn05962RU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 05962RU
dmi.product.version: ThinkPad X120e
dmi.sys.vendor: LENOVO

Revision history for this message
KrzysiekT (cytruss-xl) wrote :
KrzysiekT (cytruss-xl)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _fini () from /tmp/tmpAvoiWi/usr/lib/x86_64-linux-gnu/libdrm_intel.so.1
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in plymouth (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libudev0 version 175-0ubuntu5 required, but 175-0ubuntu6 is available
udev version 175-0ubuntu5 required, but 175-0ubuntu6 is available
libglib2.0-0 version 2.31.18-0ubuntu2 required, but 2.31.20-0ubuntu1 is available
libselinux1 version 2.1.0-4ubuntu1 required, but 2.1.0-4.1ubuntu1 is available
upstart version 1.4-0ubuntu9 required, but 1.4-0ubuntu8 is available

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
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.