Bug 589694 - [abrt] crash in gvfs-archive-1.6.1-3.fc13: raise: Process /usr/libexec/gvfsd-archive was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gvfs-archive-1.6.1-3.fc13: raise: Process /usr/libexec/gvfsd-...
Status: CLOSED DUPLICATE of bug 583256
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:32f9b586e3d796f1d6b71df8bb0...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-06 17:39 UTC by Michal Schmidt
Modified: 2015-03-03 22:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-25 09:50:21 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (10.37 KB, text/plain)
2010-05-06 17:39 UTC, Michal Schmidt
no flags Details

Description Michal Schmidt 2010-05-06 17:39:17 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-archive file=/tmp/boot.iso
comment: I accidentally attempted to open an ISO file to which I have no permission to read.
component: gvfs
crash_function: raise
executable: /usr/libexec/gvfsd-archive
global_uuid: 32f9b586e3d796f1d6b71df8bb0ae16294fa2a41
package: gvfs-archive-1.6.1-3.fc13
rating: 4
reason: Process /usr/libexec/gvfsd-archive was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
1. Have an ISO file.
2. Make sure your uid does _not_ have read permission for it.
3. Forget about the permissions and attempt to open it using "Archive Mounter" anyway.

Comment 1 Michal Schmidt 2010-05-06 17:39:19 UTC
Created attachment 412127 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 09:50:21 UTC

*** This bug has been marked as a duplicate of bug 583256 ***

Comment 3 Karel Klíč 2010-05-25 09:50:21 UTC
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 #583256.

Sorry for the inconvenience.

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