[Bug 1202388] Re: plymouthd crashed with SIGSEGV in ply_trigger_add_handler()
Apport retracing service
1202388 at bugs.launchpad.net
Fri Jul 19 07:36:55 UTC 2013
*** This bug is a duplicate of bug 864430 ***
https://bugs.launchpad.net/bugs/864430
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.
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1202388/+attachment/3740415/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/1202388/+attachment/3740418/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/1202388/+attachment/3740424/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/1202388/+attachment/3740426/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/1202388/+attachment/3740427/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1202388/+attachment/3740428/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1202388/+attachment/3740429/+files/ThreadStacktrace.txt
** This bug has been marked a duplicate of bug 864430
plymouthd crashed with SIGSEGV in ply_trigger_add_handler()
** Information type changed from Private to Public
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1202388
Title:
plymouthd crashed with SIGSEGV in ply_trigger_add_handler()
Status in “plymouth” package in Ubuntu:
New
Bug description:
Testing Mir for the first time and I get this this crash report.
Probably a duplicate of Bug #1202128 but I'm not sure how to attach my
crash report files so I am submitting a new bug. I would appreciate
someone letting me know if this was the right thing to do; and if not
or what I should do in the future with crash reports automatically
generated by apport.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: plymouth 0.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Wed Jul 17 21:06:17 2013
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-07-17 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130704)
MachineType: System manufacturer System Product Name
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-3-generic root=UUID=4f8b99e8-d8a5-4746-8fac-45b64c094297 ro quiet splash vt.handoff=7
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-3-generic root=UUID=4f8b99e8-d8a5-4746-8fac-45b64c094297 ro quiet splash vt.handoff=7
SegvAnalysis:
Segfault happened at: 0x7f8b462fda4c <ply_trigger_add_handler+28>: mov (%rbx),%rdi
PC (0x7f8b462fda4c) 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/x86_64-linux-gnu/libply.so.2
?? ()
ply_event_loop_process_pending_events () from /lib/x86_64-linux-gnu/libply.so.2
ply_event_loop_run () from /lib/x86_64-linux-gnu/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: 08/13/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2104
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A785TD-M EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1202388/+subscriptions
More information about the foundations-bugs
mailing list