gvfs-hal-volume-monitor crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECT()

Bug #264080 reported by Phoenix
6
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gvfs

I have a Titanium Stick, which has such a silly U3 feature - thus upon insertion I get two devices. The USB Stick and the "U3 CD-ROM", I don't need the second nor do I want it, so I entered under the Volume options for this volume the mountpoint "no", but now I get this error message.

Nice would be to have a real option to not mount a specific drive or volume.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/gvfs/gvfs-hal-volume-monitor
Package: gvfs-backends 0.99.5-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/gvfs/gvfs-hal-volume-monitor
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__OBJECT ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: gvfs-hal-volume-monitor crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECT()
Uname: Linux 2.6.27-2-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare scanner tape video

Revision history for this message
Phoenix (phoenix-dominion) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
IA__g_cclosure_marshal_VOID__OBJECT (closure=0x90a8730, return_value=0x0,
IA__g_closure_invoke (closure=0x90a8730, return_value=0x0, n_param_values=2,
signal_emit_unlocked_R (node=0x906f310, detail=0, instance=0x906bf20, emission_return=0x0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in gvfs:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Invalid
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.