gvfsd-computer crashed with SIGSEGV

Bug #195976 reported by will_in_wi
20
Affects Status Importance Assigned to Milestone
gvfs
Expired
Critical
gvfs (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gvfs

I tried to open my Sansa E260 and I got this error.

Ubuntu Hardy

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Tue Feb 26 19:11:48 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/gvfs/gvfsd-computer
NonfreeKernelModules: fglrx
Package: gvfs-backends 0.1.8-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: /usr/lib/gvfs/gvfsd-computer --spawner :1.7 /org/gtk/gvfs/exec_spaw/5
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
 ?? () from /usr/lib/gio/modules/libgvfsdbus.so
 ?? ()
 ?? ()
Title: gvfsd-computer crashed with SIGSEGV
Uname: Linux 2.6.24-8-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy kvm libvirtd lpadmin netdev plugdev polkituser powerdev scanner video

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

StacktraceTop:g_mount_operation_dbus_wrap (op=0x638590, connection=0x67b0e0)
g_daemon_file_mount_enclosing_volume (location=0x636cf0,
g_hal_volume_mount (volume=0x63a9b0, flags=<value optimized out>,
try_mount_mountable (backend=<value optimized out>, job=0x6900b0,
g_vfs_daemon_queue_job (daemon=0x635800, job=0x6900b0) at gvfsdaemon.c:453

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gvfs:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, is this reproducible everytime you try to see your device?

Changed in gvfs:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :
Revision history for this message
will_in_wi (will-in-wi) wrote :

It used to. Now it just fails with this error:

Unable to mount SanDisk Corp. Sansa E200 series
Error initializing camera: -1: Unspecified error

The interesting thing is that this is just is a media player set up as a mass storage device. No camera stuff should be loading.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Ok, thanks for the feedback.

Changed in gvfs:
status: Incomplete → Triaged
Changed in gvfs:
status: Unknown → New
Revision history for this message
Fabien Tassin (fta) wrote :

I'm having the same issue as in comment #6 with my camera, that used to work up to a few days ago.

Unable to mount Panasonic (Matsushita) Lumix DMC-FZ10 Camera
Error initializing camera: -1: Unspecified error

No crash at this point.

I can get a crash that way:
1/ open computer:/// in Nautilus
2/ double click on the camera
3/ click Cancel in the error dialog saying 'Opening "Panasonic (Matsushita) Lumix DMC-FZ10 Camera". You can stop this operation by clicking cancel'

This is 100% reproducible.

Changed in gvfs:
status: New → Incomplete
Revision history for this message
Fabien Tassin (fta) wrote :

The crash is fixed but the feature is still broken. i.e. my description in #8 is still valid except it no longer crashes.
Do we need another bug ?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you run "gvfs-mount -li" before plugging the camera and after getting the opening dialog?

Revision history for this message
will_in_wi (will-in-wi) wrote :

I got the crash again when I did this. I think the crash happens once a reboot. Iran the command before and after inserting my media player (note the problem is that it is not a camera) and here is the diff:

--- before 2008-03-06 08:07:05.432750323 -0600
+++ after 2008-03-06 08:07:38.864750379 -0600
@@ -61,3 +61,9 @@
   is_media_check_automatic=1
   can_poll_for_media=0
   can_eject=0
+Volume(0): SanDisk Corp. Sansa E200 series
+ ids:
+ hal-udi: '/org/freedesktop/Hal/devices/usb_device_781_7421_00000000_00000000_4878b387_0010ed01_00000000_if0'
+ unix-device: '/dev/bus/usb/008/007'
+ can_mount=1
+ can_eject=0

Revision history for this message
Fabien Tassin (fta) wrote :

30a31,36
> Volume(1): Panasonic (Matsushita) Lumix DMC-FZ10 Camera
> ids:
> hal-udi: '/org/freedesktop/Hal/devices/usb_device_4da_2372_noserial_if0'
> unix-device: '/dev/bus/usb/001/002'
> can_mount=1
> can_eject=0

(btw, my camera is a DMC-FX9)

I've removed from /usr/share/hal/fdi/preprobe/10osvendor/20-libgphoto2.fdi all the entries matching usb.vendor_id = 1242 (0x4da), restarted hal and now, I can see my camera in nautilus and extract my pictures, yet, gphoto is no longer proposed during the automount.

Revision history for this message
Yuriy Tkachenko (yuriytk) wrote :

> I'm having the same issue as in comment #6 with my camera, that used to work up to a few days ago.
> Unable to mount Panasonic (Matsushita) Lumix DMC-FZ10 Camera
> Error initializing camera: -1: Unspecified error

This bug also presents in Ubuntu 8.10.

> I've removed from /usr/share/hal/fdi/preprobe/10osvendor/20-libgphoto2.fdi all the entries matching
> usb.vendor_id = 1242 (0x4da), restarted hal and now, I can see my camera in nautilus and extract my pictures,
> yet, gphoto is no longer proposed during the automount.

It also helps to mount camera in Ubuntu 8.10.

Revision history for this message
Bernhard Reiter (ockham-razor) wrote :

Same problem as of #6 here with an
HP PhotoSmart R507
using Ubuntu 8.10:

> Unable to mount Hewlett-Packard PhotoSmart 720 / PhotoSmart 935 (storage)
> Error initializing camera: -1: Unspecified error

According to some other related bugs, it might have to do with the camera's mass storage mode (being switched on here).
Note that the camera icon and name are displayed in computer:///
Double clicking on it there gives an error message à la "Unable to mount location. Error initializing camera: -1: Unspecified error" (German: Einhängen des Ortes nicht möglich. Error initializing camera: -1: Unspecified error). No crash, though.
Stuff used to work some time before 8.10.

Haven't tried workaround from #12 yet, but could it be that this suggests that gphoto (something related to mass storage vs PTP mode handling) is to blame?

dmesg:
[ 1240.072277] usb 7-1: new full speed USB device using uhci_hcd and address 2
[ 1240.237839] usb 7-1: configuration #1 chosen from 1 choice
[ 1240.451387] usbcore: registered new interface driver libusual
[ 1240.474611] Initializing USB Mass Storage driver...
[ 1240.474817] scsi6 : SCSI emulation for USB Mass Storage devices
[ 1240.475026] usbcore: registered new interface driver usb-storage
[ 1240.475033] USB Mass Storage support registered.
[ 1240.475296] usb-storage: device found at 2
[ 1240.475301] usb-storage: waiting for device to settle before scanning

gvfs-mount -li (diff):
> Volume(0): Hewlett-Packard PhotoSmart 720 / PhotoSmart 935 (storage)
> ids:
> unix-device: '/dev/bus/usb/007/004'
> hal-udi: '/org/freedesktop/Hal/devices/usb_device_3f0_4002_4C434E34394D39383031500_if0'
> activation_root=gphoto2://[usb:007,004]/
> themed icons: [camera-photo]
> can_mount=1
> can_eject=0

uname -a:
Linux razor 2.6.27-11-generic #1 SMP Fri Dec 19 16:29:35 UTC 2008 x86_64 GNU/Linux

Changed in gvfs:
status: Incomplete → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you try if that's still an issue in intrepid or jaunty?

Changed in gvfs:
status: Triaged → Incomplete
Revision history for this message
Chris Franklin (jcfranklin) wrote :

I am having this issue. Intrepid 2.6.27-11-generic

It is an HP Photosmart 733
[ 2872.877839] usb 2-4.3.3: new full speed USB device using ohci_hcd and address 9
[ 2873.234701] usb 2-4.3.3: configuration #1 chosen from 1 choice
[ 2873.267416] scsi5 : SCSI emulation for USB Mass Storage devices
[ 2873.272260] usb-storage: device found at 9
[ 2873.272265] usb-storage: waiting for device to settle before scanning

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you get a gdb stacktrace on intrepid or jaunty?

Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in gvfs (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Chris Franklin (jcfranklin) wrote : Re: [Bug 195976] Re: gvfsd-computer crashed with SIGSEGV

I had replied with a request - "how do I provide that information?" and
never received a response. I would love to help any way I can to get
this resolved.
-

JC Franklin
jc_franklin - Yahoo IM

-----Original Message-----
From: Sebastien Bacher <email address hidden>
Reply-to: Bug 195976 <email address hidden>
To: <email address hidden>
Subject: [Bug 195976] Re: gvfsd-computer crashed with SIGSEGV
Date: Mon, 06 Apr 2009 16:06:40 -0000

We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.

** Changed in: gvfs (Ubuntu)
       Status: Incomplete => Invalid

Revision history for this message
Sebastien Bacher (seb128) wrote :

there has been no respond after the request to get a stacktrace on intrepid or jaunty, on what version did you try, could you describe what you do exactly and what error you get?

Revision history for this message
Chris Franklin (jcfranklin) wrote :

I am using 8.10 Intrepid.
When I connect my HP Photosmart 733 I get "Unable to mount
Hewlett-Packard Photosmart 720/ Photosmart 935 (storage) Error
initializing camera: -1: Unspecified error" when I click on
Hewlett-Packard Photosmart 720/ Photosmart 935 (storage) under "Places".
The camera itself shows "Connected to computer" and the read/write LED
illuminates as if it was reading the SD card. When I click on OK the LED
on the camera shuts off.

Attached is a screen grab of the error.

The LED flashes a couple of times when I connect the camera in Windows
and then I can open the SD card like a Mass Storage Device.

What do I need to do to provide a stacktrace?
-

JC Franklin
jc_franklin - Yahoo IM

-----Original Message-----
From: Sebastien Bacher <email address hidden>
Reply-to: Bug 195976 <email address hidden>
To: <email address hidden>
Subject: [Bug 195976] Re: gvfsd-computer crashed with SIGSEGV
Date: Mon, 06 Apr 2009 20:23:46 -0000

there has been no respond after the request to get a stacktrace on
intrepid or jaunty, on what version did you try, could you describe what
you do exactly and what error you get?

Revision history for this message
Sebastien Bacher (seb128) wrote :

the current comment seems to be a different issue than the one described there which is a computer: location crasher

Changed in gvfs:
importance: Unknown → Critical
status: Invalid → Expired
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.