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

[Alexander Rødseth]

Binary package hint: gvfs

This crash happened by itself while I was away from the computer.

Description: Ubuntu intrepid (development branch)
Release: 8.10

gvfs:
  Installert: 0.99.4-0ubuntu1
  Kandidat: 0.99.4-0ubuntu1
  Versjonstabell:
 *** 0.99.4-0ubuntu1 0
        500 http://no.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/gvfs/gvfs-hal-volume-monitor
NonfreeKernelModules: fglrx
Package: gvfs-backends 0.99.4-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/gvfs/gvfs-hal-volume-monitor
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=nb_NO.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: gvfs-hal-volume-monitor crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.26-5-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse plugdev scanner tape vboxusers video

[Apport retracing service (apport)]

StacktraceTop:g_hal_drive_has_udi (drive=0xe97250,
update_all (monitor=0xe78010, emit_changes=1) at ghalvolumemonitor.c:678
IA__g_closure_invoke (closure=0xe78cd0, return_value=0x0, n_param_values=2, param_values=0xe85c40,
signal_emit_unlocked_R (node=0xe4f0d0, detail=0, instance=0xe4aa40, emission_return=0x0,
IA__g_signal_emit_valist (instance=0xe4aa40, signal_id=<value optimized out>, detail=0,

[Sebastien Bacher (seb128)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=546758

[Ian Gordon (iangordon)]

I have intrepid x86_64 installed on /dev/sdd1 and frugalware on /dev/sda1.
I mounted /dev/sda1 on /mnt/xtrn and the error occurred when I brought up /mnt/xtrn/boot in the file browser.

[Ian Gordon (iangordon)]

Additionally to previous message - sda1, sdb1, and sdc1 drive segments show under Places (top gnome panel) but
can't be selected.

[Sebastien Bacher (seb128)]

do you get the crash every time you do those actions?

[Daniel J Blueman (danielblueman)]

I had this crash with same stacktrace top when plugging in my (gen 3) iPod shuffle.

[Matt Zimmerman (mdz)]

I got one of these shortly after attaching a removable USB drive. I'll see if it happens the next time.

[Miloš Mandarić (mandzo18)]

I get this crash sometimes when I put my flash usbstick. It becomes very hot and when I look at System Log I see these three messages repeating every second(I don't know is it connected with this bug):

[13123.956010] sd 5:0:0:0: ioctl_internal_command return code = 8000002
[13123.956010] : Sense Key : No Sense [current]
[13123.956010] : Add. Sense: No additional sense information

[nullack (nullack)]

Moving status to fix released. Numerous updates have occurred since, and I can no longer replicate the problem on a current Intrepid build 26/09/08.

[electhor (electhor)]

This just happened in karmic alpha 6. I assume the automatic crash report will have uploaded the various files associated.

[Chris Coulson (chrisccoulson)]

You can't be experiencing this in Karmic - gvfs-hal-volume-monitor does not exist in Karmic

[electhor (electhor)]

I see what you are saying, but it was one of those automatic crash notifications and I was using Karmic Koala as far as I recollect. I certainly got the notification - I don't believe I was using jaunty at the time. I only have jaunty or karmic on the computer - so if that doesn't exist in karmic, I have must have changed back to jaunty and forgot about which OS I was using.

> Chris Coulson <email address hidden> wrote:
>
> You can't be experiencing this in Karmic - gvfs-hal-volume-monitor does
> not exist in Karmic
>
> --
> gvfs-hal-volume-monitor crashed with SIGSEGV in g_closure_invoke()
> https://bugs.launchpad.net/bugs/255511
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in gvfs: Fix Released
> Status in “gvfs� package in Ubuntu: Fix Released
>
> Bug description:
> Binary package hint: gvfs
>
> This crash happened by itself while I was away from the computer.
>
> Description: Ubuntu intrepid (development branch)
> Release: 8.10
>
> gvfs:
> Installert: 0.99.4-0ubuntu1
> Kandidat: 0.99.4-0ubuntu1
> Versjonstabell:
> *** 0.99.4-0ubuntu1 0
> 500 http://no.archive.ubuntu.com intrepid/main Packages
> 100 /var/lib/dpkg/status
>
> ProblemType: Crash
> Architecture: amd64
> DistroRelease: Ubuntu 8.10
> ExecutablePath: /usr/lib/gvfs/gvfs-hal-volume-monitor
> NonfreeKernelModules: fglrx
> Package: gvfs-backends 0.99.4-0ubuntu1
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/lib/gvfs/gvfs-hal-volume-monitor
> ProcEnviron:
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/ga
> mes
> LANG=nb_NO.UTF-8
> SHELL=/bin/bash
> Signal: 11
> SourcePackage: gvfs
> StacktraceTop:
> ?? ()
> ?? ()
> ?? ()
> g_closure_invoke ()
> ?? () from /usr/lib/libgobject-2.0.so.0
> Title: gvfs-hal-volume-monitor crashed with SIGSEGV in
> g_closure_invoke()
> Uname: Linux 2.6.26-5-generic x86_64
> UserGroups: adm admin audio cdrom dialout dip fax floppy fuse plugdev
> scanner tape vboxusers video