Bug 608632 - [abrt] crash in gvfs-1.6.2-1.fc13: gdu_device_get_object_path: Process /usr/libexec/gvfs-gdu-volume-monitor was killed by signal 11 (SIGSEGV)
[abrt] crash in gvfs-1.6.2-1.fc13: gdu_device_get_object_path: Process /usr/l...
Status: CLOSED DUPLICATE of bug 597796
Product: Fedora
Classification: Fedora
Component: gvfs (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Tomáš Bžatek
Fedora Extras Quality Assurance
abrt_hash:71bffecc8bc5ac30f22aef7cb12...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-28 06:57 EDT by Jamey
Modified: 2015-03-03 17:50 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-09 11:42:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (6.72 KB, text/plain)
2010-06-28 06:57 EDT, Jamey
no flags Details

  None (edit)
Description Jamey 2010-06-28 06:57:41 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfs-gdu-volume-monitor
component: gvfs
crash_function: gdu_device_get_object_path
executable: /usr/libexec/gvfs-gdu-volume-monitor
global_uuid: 71bffecc8bc5ac30f22aef7cb1292df7f83dbf4d
kernel: 2.6.33.5-112.fc13.x86_64
package: gvfs-1.6.2-1.fc13
rating: 4
reason: Process /usr/libexec/gvfs-gdu-volume-monitor was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Jamey 2010-06-28 06:57:43 EDT
Created attachment 427385 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 11:42:39 EST

*** This bug has been marked as a duplicate of bug 597796 ***
Comment 3 Karel Klíč 2010-11-09 11:42:39 EST
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #597796.

Sorry for the inconvenience.

Note You need to log in before you can comment on or make changes to this bug.