After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 520762 - gvfsd-gphoto2 crashed with SIGSEGV in pthread_mutex_lock()
gvfsd-gphoto2 crashed with SIGSEGV in pthread_mutex_lock()
Status: RESOLVED NOTGNOME
Product: gvfs
Classification: Core
Component: gphoto backend
0.1.x
Other Linux
: Normal critical
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2008-03-06 14:41 UTC by Sebastien Bacher
Modified: 2008-03-07 02:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Sebastien Bacher 2008-03-06 14:41:59 UTC 
The bug has been described on https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/199027

"Running Hardy 8.04 alpha with all updates. When I plug in the USB cable connected to my Sansa e240 mp3 player, it doesn't succeed when it tries to automount, and it crashes nautilus. I am also getting an additional error with the crash which reads "Unable to mount SanDisk Corp. Sansa E200 series/Error initializing camera: -1: Unspecified error". Double clicking the Sandisk icon in the My Computer window returns this error: "Unable to mount SanDisk Corp. Sansa E200 series/Error initializing camera: -60: Could not lock the device".
This worked before my upgrade to Hardy. Attached is a screenshot of the error messages I get.

Package: gvfs-backends 0.1.11-0ubuntu1

.

+ Trace 191519

Thread 2 (process 26047)

  • #0 memcpy
    from /lib/tls/i686/cmov/libc.so.6
  • #1 gp_abilities_list_load
    at gphoto2-abilities-list.c line 597
  • #2 gp_camera_init
    at gphoto2-camera.c line 681
  • #3 do_mount
    at gvfsbackendgphoto2.c line 1522
  • #4 run
    at gvfsjobmount.c line 113
  • #5 g_vfs_job_run
    at gvfsjob.c line 198
  • #6 job_handler_callback
    at gvfsdaemon.c line 142
  • #7 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.15.6/glib/gthreadpool.c line 265
  • #8 g_thread_create_proxy
    at /build/buildd/glib2.0-2.15.6/glib/gthread.c line 635
  • #9 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #10 clone
    from /lib/tls/i686/cmov/libc.so.6

Thread 1 (process 26046)

  • #0 pthread_mutex_lock
    from /lib/tls/i686/cmov/libpthread.so.0
  • #1 _hal_device_removed
    at gvfsbackendgphoto2.c line 435
  • #2 filter_func
    at libhal.c line 1033
  • #3 dbus_connection_dispatch
    at dbus-connection.c line 4379
  • #4 dbus_source_dispatch
    at gdbusutils.c line 868
  • #5 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.15.6/glib/gmain.c line 2065
  • #6 g_main_context_iterate
    at /build/buildd/glib2.0-2.15.6/glib/gmain.c line 2698
  • #7 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.15.6/glib/gmain.c line 2906
  • #8 daemon_main
    at daemon-main.c line 270
  • #9 main
    at daemon-main-generic.c line 39
  • #10 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #11 _start 






Comment 1


David Zeuthen (not reading bugmail)





          2008-03-07 02:15:49 UTC
        



I have exactly the same device and the bug is in libgphoto2 reported here

https://sourceforge.net/tracker/?func=detail&atid=108874&aid=1904443&group_id=8874