udisks-daemon crashed with signal 5 in g_realloc()

[Nilesh Malode]

udisks-daemon crashed with signal 5 in g_realloc()

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: udisks 1.0.4-7
ProcVersionSignature: Ubuntu 3.8.0-9.18-generic 3.8.1
Uname: Linux 3.8.0-9-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.9-0ubuntu2
Architecture: i386
Date: Sun Mar 3 18:28:19 2013
ExecutablePath: /usr/lib/udisks/udisks-daemon
InstallationDate: Installed on 2013-02-28 (2 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130225)
MachineType: Hewlett-Packard Presario V3000 (GN367PA#ACJ)
MarkForUpload: True
ProcCmdline: /usr/lib/udisks/udisks-daemon
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-9-generic root=UUID=476c7eba-ecd0-4a73-83b9-a602f2e7e0ba ro quiet splash vt.handoff=7
Signal: 5
SourcePackage: udisks
StacktraceTop:
 g_realloc () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_string_insert_len () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_string_append_len () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? ()
Title: udisks-daemon crashed with signal 5 in g_realloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 06/02/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.34
dmi.board.name: 30B2
dmi.board.vendor: Wistron
dmi.board.version: 61.61
dmi.chassis.type: 10
dmi.chassis.vendor: Wistron
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.34:bd06/02/2007:svnHewlett-Packard:pnPresarioV3000(GN367PA#ACJ):pvrF.34:rvnWistron:rn30B2:rvr61.61:cvnWistron:ct10:cvrN/A:
dmi.product.name: Presario V3000 (GN367PA#ACJ)
dmi.product.version: F.34
dmi.sys.vendor: Hewlett-Packard

[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 #1092195, 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.