gvfsd-gphoto2 crashed with SIGABRT in raise()

Bug #1050571 reported by hseffler
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Plugging in my Samsung Galaxy SII

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gvfs-backends 1.13.7-0ubuntu6
ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
Uname: Linux 3.5.0-14-generic i686
ApportVersion: 2.5.1-0ubuntu7
Architecture: i386
Date: Thu Sep 13 21:18:24 2012
ExecutablePath: /usr/lib/gvfs/gvfsd-gphoto2
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
ProcCmdline: /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.7 /org/gtk/gvfs/exec_spaw/4
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 g_mutex_clear () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: gvfsd-gphoto2 crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to quantal on 2012-09-13 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
hseffler (hseffler) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #984993, so 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. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
Revision history for this message
hseffler (hseffler) wrote :

Ah, this again. Could someone please stop making this bot mark bugs as duplicates of *private* bugs? I have no idea if this really is a duplicate or what happpens to bug #984993 now. Great!

Revision history for this message
Bruce Pieterse (octoquad) wrote :

Bug #984993 does not exist and therefore does not allow new reports to be submitted.

Removing Duplicate Bug Link.

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
Bruce Pieterse (octoquad) wrote :

I have linked the other bugs to this report. I get this error often when plugging in my Samsung Galaxy SII.

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

bug #984993 exists, you probably just didn't have access (those reports are private by default until somebody from bugsquad review the bug content for private informations), you can retry it has been released

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.