gvfsd-trash crashed with SIGABRT in g_mutex_lock()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
ubuntu 13.04
gvfs:
Installed: 1.18.2-0ubuntu1
Candidate: 1.18.2-0ubuntu1
Version table:
*** 1.18.2-0ubuntu1 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gvfs-daemons 1.18.2-0ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-17-generic x86_64
NonfreeKernelMo
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Tue Feb 18 09:05:24 2014
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-08-01 (200 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, user)
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
Signal: 6
SourcePackage: gvfs
StacktraceTop:
?? () from /lib/x86_
g_mutex_lock () from /lib/x86_
?? () from /usr/lib/
g_main_
?? () from /lib/x86_
Title: gvfsd-trash crashed with SIGABRT in g_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse kismet lpadmin plugdev sambashare sudo vboxusers video
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 #1277775, 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.