gvfsd-gphoto2 crashed with SIGSEGV in __pthread_mutex_destroy()

Bug #937818 reported by Antonio Batovanja
606
This bug affects 136 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I've got this crash right after connecting my mobile phone (Samsung Galaxy 2) via USB.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gvfs-backends 1.11.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.92-0ubuntu1
Architecture: i386
Date: Tue Feb 21 15:23:56 2012
ExecutablePath: /usr/lib/gvfs/gvfsd-gphoto2
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
ProcCmdline: /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.1 /org/gtk/gvfs/exec_spaw/4
SegvAnalysis:
 Segfault happened at: 0xb738ac74 <pthread_mutex_destroy+4>: testb $0x10,0xc(%edx)
 PC (0xb738ac74) ok
 source "$0x10" ok
 destination "0xc(%edx)" (0x0000000c) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 pthread_mutex_destroy () from /lib/i386-linux-gnu/libpthread.so.0
 g_mutex_clear () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? () from /usr/lib/i386-linux-gnu/gvfs/libgvfsdaemon.so
Title: gvfsd-gphoto2 crashed with SIGSEGV in pthread_mutex_destroy()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Antonio Batovanja (toni-toni) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __pthread_mutex_destroy (mutex=0x0) at pthread_mutex_destroy.c:28
 g_io_unix_read (channel=0x90dd690, buf=0x90e0020 "", count=0, bytes_read=0x8050118, err=0x90dd690) at /build/buildd/glib2.0-2.31.18/./glib/giounix.c:212
 g_get_tmp_name (tmpl=<optimized out>, name_used=<optimized out>, f=0x353030, flags=0, mode=0, error=0x2) at /build/buildd/glib2.0-2.31.18/./glib/gfileutils.c:1581
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gvfs (Ubuntu):
importance: Undecided → Medium
summary: - gvfsd-gphoto2 crashed with SIGSEGV in pthread_mutex_destroy()
+ gvfsd-gphoto2 crashed with SIGSEGV in __pthread_mutex_destroy()
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gvfs (Ubuntu):
status: New → Confirmed
Revision history for this message
RadekB (rrrbbb) wrote :

Got this error after connecting camera.

Revision history for this message
dhyll (wmastercorp) wrote :

Estou com o mesmo problema! :/

Revision history for this message
hchavez555@gmail.com (hchavez555) wrote :

My galaxy nexus does not sync with rythembox either.

Revision history for this message
Carla Sella (carla-sella) wrote :

I got this crash just after an update and reboot.

Revision history for this message
Anders Pamdal (anders-pamdal) wrote :

Got this crash after connecting a samsung galaxy 2.

Revision history for this message
Stephen Burke (steveburkez28) wrote :

Got this crash after mounting Galaxy Nexus and trying to access it in Nautilus. I didn't install any scripts to make it mount, so I'm guessing that 12.04 has native MTP support but it's just buggy? My GNex was never even able to mount in Oneiric.

Revision history for this message
Ron Pike (ron-ronpike) wrote :

connecting a Galaxy Note (AT&T)

Revision history for this message
Rayan Hassanain (rhh1010) wrote :

The same with acer iconia tab a500

Revision history for this message
Michel Schweegmann (michel-schweegmann) wrote :

Connecting Galaxy S2 and Galaxy Tab 10.1N, same error

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Same error in Precise beta 1 when connecting Galaxy Note.

tags: added: apport-collected
Revision history for this message
Marius B. Kotsbak (mariusko) wrote : apport information

ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
DistroRelease: Ubuntu 12.04
EcryptfsInUse: Yes
Package: gvfs 1.11.4-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
 TERM=xterm
 PATH=(custom, user)
 LANG=nb_NO.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Tags: precise
Uname: Linux 3.2.0-18-generic-pae i686
UpgradeStatus: Upgraded to precise on 2012-03-11 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Marius B. Kotsbak (mariusko) wrote : Dependencies.txt

apport information

Revision history for this message
andrey i. mavlyanov (andrey-mavlyanov) wrote :

Galaxy Note (bought in Poland)

Revision history for this message
Philip Khor (philip10khor) wrote :

Same problem after connecting Nokia 500 (Symbian Belle).

Revision history for this message
Matthew Addison (addison-matthewpaul) wrote :

I got this by booting with Samsung Galaxy Nexus mobile Android device connected via USB.

Revision history for this message
Bogdan Marian (bogdanbm11) wrote :

Connecting Kodak EasyShare C190

Revision history for this message
PC Dienstverlening - B. van Munster (bram-pcdienstverlening) wrote :

I got this one after connecting my Samsung GT-S5260 smartphone.
First I got the announcement Ubuntu could not mount the volume because it couldn't lock the phone, then the crash followed.
Afterwards, I cannot view my files so I cannot choose what I would like to transfer or import.

Revision history for this message
Carla Sella (carla-sella) wrote :

I had attached a Asus eee Pad Transformer to usb port.

Revision history for this message
Ron Pike (ron-ronpike) wrote :

new kernel does fix this issue, but I still got a crash error that pointed me back to this bug report.

Revision history for this message
Ron Pike (ron-ronpike) wrote :

still failing, new kernel does not help

Revision history for this message
Sergio Schneider (spsf) wrote :

Any news on this bug?
Samsung Galaxy S2 phone

Revision history for this message
Ariyau (hawaii5o) wrote :

Connets to galacxy nexus but fails when writing. Couple of weeks ago it was able write but unreliable and very slow.

Revision history for this message
Sergio Schneider (spsf) wrote :

Same prob when connecting Samsung Galaxy S2

Revision history for this message
Welington R. Braga (welrbraga) wrote :

Same problem when I've connected my mobile Samsung GT-5260

Revision history for this message
Moba Rob Ber (mobarobber) wrote :

Connected Nokia E-500.. I guess its to do with the USB device not being recognised or needing a separate driver...

Revision history for this message
Audrey Durand (adurand) wrote :

I encountered the same problem when I disconnected my Asus Transformer Prime (TF-201).

Revision history for this message
Carla Sella (carla-sella) wrote :

I had this problem connecting my Asus eee pad Transformer to the USB port.

Revision history for this message
Subhadip Ghosh (subhadip-sky) wrote :

Nokia C2-03

Revision history for this message
RadekB (rrrbbb) wrote :

Kodak EasyShare z915. Happens when I connect camera before launching Shotwell. If Shotwell is already running, it behaves well.

Revision history for this message
Sergio Schneider (spsf) wrote :

Same problem when connecting new ipad (ipad 3)

Revision history for this message
Damien Carcel (damien-carcel) wrote :

Same problem with my Galaxy Nexus.

Revision history for this message
Bram Schellen (bram-schellen) wrote :

I got this bug when connecting my Samsung Galaxy S2 phone to Ubuntu. It happens to me in different versions of Ubuntu (11.10, 11.04 and older). Another thing that happens is that Banshee and Rhythmbox both stall. They dont crash but gray out. Like they are waiting for something.

Revision history for this message
TenLeftFingers (tenleftfingers) wrote :

The exact error I got on the desktop reads:

Unable to mount SAMSUNG_Android
Error initializing camera: -60: Could not lock the device

Revision history for this message
Gareth Williams (gareththered) wrote :

Got this after connecting My Canon EOS 350D.

Revision history for this message
papukaija (papukaija) wrote :

Please use the "this bug affects me too" link instead of commenting with me too comments. Thanks in advance.

Revision history for this message
papukaija (papukaija) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 946255, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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.