udisks-daemon crashed with signal 5 in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
udisks (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
always happens at start
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: udisks 1.0.4-3
ProcVersionSign
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
Date: Wed Feb 29 18:50:22 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111229)
Lsusb:
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 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 0ac8:c33f Z-Star Microelectronics Corp. Webcam
MachineType: SAMSUNG ELECTRONICS CO., LTD. R440
ProcCmdline: /usr/lib/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 5
SourcePackage: udisks
StacktraceTop:
?? ()
?? ()
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: udisks-daemon crashed with signal 5 in g_closure_invoke()
UpgradeStatus: Upgraded to precise on 2012-01-13 (47 days ago)
UserGroups:
dmi.bios.date: 06/05/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 03UW.K005.
dmi.board.
dmi.board.name: R440
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: R440
dmi.product.
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
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 #856883, 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.