Ubuntu
gvfs package

gvfsd-mtp crashed with SIGFPE in g_hash_table_lookup()

Bug #1210422 reported by yohgaz on 2013-08-09

This bug report is a duplicate of: Bug #1197933: gvfsd-mtp crashed with SIGFPE in g_hash_table_lookup_node(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gvfs (Ubuntu)	New	Undecided	Unassigned

Bug Description

This bug appears when i want eject my tablet ( nexus 7 )

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gvfs-backends 1.17.2-0ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
Uname: Linux 3.11.0-1-generic i686
ApportVersion: 2.12-0ubuntu3
Architecture: i386
Date: Fri Aug 9 08:49:44 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2013-06-24 (45 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release i386 (20130424)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.7 /org/gtk/gvfs/exec_spaw/1
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
PATH=(custom, no user)
LANGUAGE=fr_FR
LANG=fr_FR.UTF-8
Signal: 8
SourcePackage: gvfs
StacktraceTop:
g_hash_table_lookup () from /lib/i386-linux-gnu/libglib-2.0.so.0
?? ()
?? ()
?? () from /usr/lib/i386-linux-gnu/gvfs/libgvfsdaemon.so
g_vfs_job_run () from /usr/lib/i386-linux-gnu/gvfs/libgvfsdaemon.so
Title: gvfsd-mtp crashed with SIGFPE in g_hash_table_lookup()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

yohgaz (yohanngazziero) wrote on 2013-08-09:

Dependencies.txt Edit (8.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2013-08-09: 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 #1197933, 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.