gvfs-gdu-volume-monitor crashed with SIGABRT in raise()

Bug #940031 reported by Lisa Simpson
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

This always seems to happen right when the networking fails -wireless just stops dead and wont come back on no matter what.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gvfs 1.10.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
Uname: Linux 3.0.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 23 20:44:21 2012
ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/lib/gvfs/gvfs-gdu-volume-monitor
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x7f52d8089d40 "gdu_pool_get_presentables", message=0xeb8f90 "assertion failed: (pool != NULL)") at /build/buildd/glib2.0-2.30.0/./glib/gtestutils.c:1425
 g_assertion_message_expr (domain=0x7f52d8086cde "libgdu", file=0x7f52d8088e0c "gdu-pool.c", line=2565, func=0x7f52d8089d40 "gdu_pool_get_presentables", expr=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gtestutils.c:1436
 gdu_pool_get_presentables () from /usr/lib/libgdu.so.0
Title: gvfs-gdu-volume-monitor crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Lisa Simpson (lisa-p) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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

visibility: private → public
visibility: private → public
tags: removed: need-amd64-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.