udisks-daemon crashed with signal 5 in g_udev_marshal_VOID__STRING_OBJECT()

[Arthur Rodrigues]

I just plugged in an external dvd-writer, as I use a netbook, with a blank dvd inside it.
Then, this apport crash was reported.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: udisks 1.0.4-1
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Sat Jan 21 10:58:16 2012
ExecutablePath: /usr/lib/udisks/udisks-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: ASUSTeK Computer INC. 1201T
ProcCmdline: /usr/lib/udisks/udisks-daemon
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-14-generic root=UUID=1ff5cce0-8184-4010-ab17-de5f772ee5a9 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: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 03/11/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0319
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1201T
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0319:bd03/11/2010:svnASUSTeKComputerINC.:pn1201T:pvrx.x:rvnASUSTeKComputerINC.:rn1201T:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1201T
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[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.