gnome-mount crashed with signal 5 in g_return_if_fail_warning()

Bug #188386 reported by tomcloud
6
Affects Status Importance Assigned to Milestone
gnome-mount (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gnome-mount

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

Plugged in USB thumb drive. Three Nautilus windows opened. Apport popped up. All windows appear functional. Drive is vfat and accessible.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Feb 2 11:39:59 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gnome-mount
NonfreeKernelModules: fglrx
Package: gnome-mount 0.7-1ubuntu1
PackageArchitecture: i386
ProcCmdline: gnome-mount -b -d /dev/sdb1
ProcCwd: /home/tscloud
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=C
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-mount
StacktraceTop:
 g_return_if_fail_warning () from /usr/lib/libglib-2.0.so.0
 g_signal_handlers_destroy ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 ?? ()
Title: gnome-mount crashed with signal 5 in g_return_if_fail_warning()
Uname: Linux tscloud-laptop 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev pulse pulse-access pulse-rt scanner video

Tags: apport-crash
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_return_if_fail_warning (log_domain=0xb7b16a6b "GLib-GObject",
IA__g_signal_handlers_destroy (instance=0x8092860)
g_object_real_dispose (object=0x8092860)
gtk_object_dispose (gobject=0x8092860) at /build/buildd/gtk+2.0-2.12.7/gtk/gtkobject.c:423
gtk_widget_dispose (object=0x8092860) at /build/buildd/gtk+2.0-2.12.7/gtk/gtkwidget.c:7854

Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in gnome-mount:
importance: Undecided → Medium
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.