plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

Bug #1057745 reported by qamelian
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

On boot, Plymouth splash screen fails to appear, leaving a blank purple screen. Blank screen remains even when LightDM or GDM should be displaying greeter/login screen. Login appears to be possible, even though screen remains hidden by blank purple screen. User can switch to another TTY using CTRL+ALT+1 (2, 3, etc) and then reboot by pressing CTRL+ALT+DEL. Sometimes takes 2 - 4 reboots like this to get greeter to appear as expected.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: plymouth 0.8.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CurrentDmesg:

Date: Thu Sep 27 17:21:36 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120809.1)
Lsusb:
 Bus 002 Device 002: ID 0402:9665 ALi Corp. Gateway Webcam
 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
MachineType: Acer Aspire One 522
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=01bb2b61-bebb-4e3d-95fe-329856d04c26 ro quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=01bb2b61-bebb-4e3d-95fe-329856d04c26 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fbc31bcdefb <ply_trigger_add_handler+43>: mov (%rbx),%rdi
 PC (0x7fbc31bcdefb) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_trigger_add_handler () from /lib/libply.so.2
 ?? ()
 ply_event_loop_process_pending_events () from /lib/libply.so.2
 ply_event_loop_run () from /lib/libply.so.2
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_trigger_add_handler()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 12/09/2010
dmi.bios.vendor: Acer
dmi.bios.version: V1.03
dmi.board.name: Aspire One 522
dmi.board.vendor: Acer
dmi.board.version: V1.03
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAcer:bvrV1.03:bd12/09/2010:svnAcer:pnAspireOne522:pvrV1.03:rvnAcer:rnAspireOne522:rvrV1.03:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire One 522
dmi.product.version: V1.03
dmi.sys.vendor: Acer

Revision history for this message
qamelian (carl-godfrey) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #864430, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

Other bug subscribers