udisks-daemon crashed with signal 5 in g_realloc()

Bug #1227098 reported by Lukasz Grzesik
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
udisks (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Udisks-daemon crashed on Saucy. Why? I don't know.

Previus I launched a Wine application, and update a OS.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: udisks 1.0.4-8
ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
Uname: Linux 3.11.0-7-generic i686
ApportVersion: 2.12.1-0ubuntu4
Architecture: i386
CustomUdevRuleFiles: 80-canon_mfp.rules
Date: Wed Sep 18 10:15:45 2013
ExecutablePath: /usr/lib/udisks/udisks-daemon
InstallationDate: Installed on 2013-09-17 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130917)
MachineType: LENOVO 20071
MarkForUpload: True
ProcCmdline: /usr/lib/udisks/udisks-daemon
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic root=UUID=af88de84-ce4d-4e00-afea-94b7ae1a4ba3 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/08/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 36CN15WW(V2.01)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Guam
dmi.board.vendor: LENOVO
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnLENOVO:bvr36CN15WW(V2.01):bd06/08/2010:svnLENOVO:pn20071:pvrLenovoG565:rvnLENOVO:rnGuam:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: 20071
dmi.product.version: Lenovo G565
dmi.sys.vendor: LENOVO

Revision history for this message
Lukasz Grzesik (qnebra) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0xb7481d09 in ?? ()
 #1 0xb74c1cae in ?? ()
 #2 0x00000006 in ?? ()
 #3 0xb5c00468 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in udisks (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libudev1: package version 204-0ubuntu12 dbgsym version 204-0ubuntu11
outdated debug symbol package for libsystemd-login0: package version 204-0ubuntu12 dbgsym version 204-0ubuntu11

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.