udisks-helper-drive-detach crashed with SIGSEGV in __libc_start_main()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
udisks (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Seems to be the same bug #739849 with 11.04, but it is 12.04
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: udisks 1.0.4-5ubuntu2.1
ProcVersionSign
Uname: Linux 3.2.0-54-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu17.5
Architecture: amd64
CustomUdevRuleF
Date: Sun Oct 20 20:01:17 2013
ExecutablePath: /usr/lib/
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0644:0200 TEAC Corp. All-In-One Multi-Card Reader CA200/B/S
Bus 002 Device 002: ID 413c:3016 Dell Computer Corp. Optical 5-Button Wheel Mouse
Bus 002 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard
MachineType: Dell Inc Dimension E521
MarkForUpload: True
ProcCmdline: udisks-
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f95b6c7ead4: movzbl (%rbx),%eax
PC (0x7f95b6c7ead4) ok
source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: udisks
StacktraceTop:
?? () from /lib/x86_
?? ()
__libc_start_main () from /lib/x86_
?? ()
?? ()
Title: udisks-
UpgradeStatus: Upgraded to precise on 2013-05-30 (143 days ago)
UserGroups: mythtv
dmi.bios.date: 08/02/2007
dmi.bios.vendor: Dell Inc
dmi.bios.version: 1.1.11
dmi.board.name: 0CT103
dmi.board.vendor: Dell Inc
dmi.board.version: A03
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc
dmi.modalias: dmi:bvnDellInc:
dmi.product.name: Dimension E521
dmi.sys.vendor: Dell Inc
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 #739849, 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.