plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #761351 reported by Gunnar Hjalmarsson
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: plymouth

No action on my side.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: plymouth 0.8.2-2ubuntu21
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Fri Apr 15 01:16:55 2011
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
MachineType: CLEVO CO. M740TU(N)/M760TU(N)/W7X0TUN
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=787cc8b3-57c3-4a0c-bb5e-e3547deeb2b2 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f7f1b0af000 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f7f1b0af000) ok
 source "$0x1" ok
 destination "(%rdi)" (0x726f207465792079) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 script_obj_deref_direct () from /lib/plymouth/script.so
 script_obj_as_custom () from /lib/plymouth/script.so
 script_execute_object () from /lib/plymouth/script.so
 script_lib_plymouth_on_message () from /lib/plymouth/script.so
 ?? () from /lib/plymouth/script.so
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: Upgraded to natty on 2011-04-14 (0 days ago)
UserGroups:

dmi.bios.date: 12/31/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 1.02.27
dmi.board.asset.tag: Tag 12345
dmi.board.name: M740TU(N)/M760TU(N)/W7X0TUN
dmi.board.vendor: CLEVO Co.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.02.27:bd12/31/2009:svnCLEVOCO.:pnM740TU(N)/M760TU(N)/W7X0TUN:pvrNotApplicable:rvnCLEVOCo.:rnM740TU(N)/M760TU(N)/W7X0TUN:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: M740TU(N)/M760TU(N)/W7X0TUN
dmi.product.version: Not Applicable
dmi.sys.vendor: CLEVO CO.

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) 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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #733453, 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
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.