udisks-daemon crashed with signal 5 in g_udev_marshal_VOID__STRING_OBJECT()

[Luigi Calderone]

Nothing visible happened

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: udisks 1.0.4-3ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CrashCounter: 1
CustomUdevRuleFiles: 10-Huawei-Datacard.rules
Date: Sun Mar 18 21:37:54 2012
ExecutablePath: /usr/lib/udisks/udisks-daemon
InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Dell Computer Corporation Latitude D600
ProcCmdline: /usr/lib/udisks/udisks-daemon
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-19-generic root=UUID=360bea08-7092-46da-856c-a981e3331af1 ro quiet splash vt.handoff=7
Signal: 5
SourcePackage: udisks
StacktraceTop:
 ?? ()
 ?? ()
 g_udev_marshal_VOID__STRING_OBJECT () from /usr/lib/i386-linux-gnu/libgudev-1.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: udisks-daemon crashed with signal 5 in g_udev_marshal_VOID__STRING_OBJECT()
UpgradeStatus: Upgraded to precise on 2012-03-13 (5 days ago)
UserGroups:

dmi.bios.date: 06/29/2005
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A16
dmi.board.name: 0G5152
dmi.board.vendor: Dell Computer Corporation
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComputerCorporation:bvrA16:bd06/29/2005:svnDellComputerCorporation:pnLatitudeD600:pvr:rvnDellComputerCorporation:rn0G5152:rvr:cvnDellComputerCorporation:ct8:cvr:
dmi.product.name: Latitude D600
dmi.sys.vendor: Dell Computer Corporation

[Apport retracing service (apport)]

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 #899757, 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.