plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

[DorianDaumiller]

Binary package hint: plymouth

After Grub, which is shown in 1280x800, my native resolution, plymouth doesn't show.
I see some pixel-garbage instead.
After some (normal boot-) time, hdd-activity ends and i'm presented a black screen.
However, in contrary to #559930, i _am_ able to switch to other ttys using CTRL+ALT+F1.
After logging in there, i am able to
$sudo restart gdm
after which i can log in to X normally.

Some time after settling down of X, this apport-error is shown, alongside with one about aptd, which i will deliver the launchpad number later.

I sometimes manage to jump to a certain tty, which causes the startup to be plymouth-free, but interruptionless, but am not able to tell which one (or if it changes).

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: plymouth 0.8.2-2ubuntu21
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
Architecture: i386
Date: Tue Apr 5 19:43:52 2011
DefaultPlymouth: /lib/plymouth/themes/spinfinity/spinfinity.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: SAMSUNG ELECTRONICS CO., LTD. X460
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic-pae root=UUID=62396c5e-75cc-485f-85d1-0fe1bfd1377e ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb783afa8 <ply_trigger_add_handler+56>: mov (%eax),%eax
 PC (0xb783afa8) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" 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: Error: command ['readlink', '/etc/alternatives/text.plymouth'] failed with exit code 1:
Title: plymouthd crashed with SIGSEGV in ply_trigger_add_handler()
UpgradeStatus: Upgraded to natty on 2011-04-11 (0 days ago)
UserGroups:

dmi.bios.date: 11/10/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 06LY.M038.20091110.JIP
dmi.board.name: X460
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr06LY.M038.20091110.JIP:bd11/10/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnX460:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnX460:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: X460
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[DorianDaumiller (dorian-daumiller)]

The Aptd-issue seems to be adressed in Bug #741370 (although i'm not updating anything when i get the error-message).

And for your convenience and my rehearsal:
Bug #559930 is the one i think this one is not a copy of.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #750405, 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.