Bug 539539 - [abrt] crash detected in gvfs-1.4.1-3.fc12
Summary: [abrt] crash detected in gvfs-1.4.1-3.fc12
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c27a291c2521c94723609225eb0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-20 14:12 UTC by Sijo George
Modified: 2015-03-03 22:41 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-04 03:06:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.03 KB, text/plain)
2009-11-20 14:12 UTC, Sijo George
no flags Details

Description Sijo George 2009-11-20 14:12:24 UTC
abrt detected a crash.

Attached file: backtrace
cmdline: /usr/libexec/gvfsd-metadata
component: gvfs
executable: /usr/libexec/gvfsd-metadata
kernel: 2.6.31.5-127.fc12.i686.PAE
package: gvfs-1.4.1-3.fc12
rating: 2
reason: Process was terminated by signal 11

Comment 1 Sijo George 2009-11-20 14:12:27 UTC
Created attachment 372496 [details]
File: backtrace

Comment 2 Tomáš Bžatek 2009-11-20 14:20:51 UTC
Can you please install gvfs-debuginfo and try catching better backtrace?

Comment 3 Sijo George 2009-11-21 10:51:45 UTC
Hi Tomas:
 

   The bug was submitted through the abrt tool. I will install the debuginfo to get a better backtrace. I have observed that the crash happens when the selinux is turned on. When the selinux policy is set to permissive, it has stop happening. Anyways I will keep my system ready to get a better trace by installing the debuginfo.

Thanks:
Sijo George

Comment 4 Tomáš Bžatek 2009-11-23 10:25:23 UTC
(In reply to comment #3)
> I have observed that the crash happens when the selinux is turned on. 
> When the selinux policy is set to permissive, it has stop happening.
I'd be interested in that selinux warning as well, would help us to find the problem. This is quite important as the denial can be cause of data corruption, can you please try getting that information and attaching it here? 

There should be selinux denial icon in the notification area, clicking it will spawn a browser (sealert --browser) and there you should be able to find more information.

Comment 5 Bug Zapper 2010-11-04 05:56:54 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2010-12-04 03:06:12 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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