Bug 750479 - [abrt] nautilus-2.28.4-15.el6: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] nautilus-2.28.4-15.el6: Process /usr/bin/nautilus was killed by signal...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: nautilus
Version: 6.3
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Tomáš Bžatek
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-01 09:44 UTC by prashant ingale
Modified: 2018-11-26 18:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 09:33:36 UTC
Target Upstream Version:


Attachments (Terms of Use)
backtrace (5.32 KB, text/plain)
2011-11-01 09:44 UTC, prashant ingale
no flags Details

Description prashant ingale 2011-11-01 09:44:16 UTC
Created attachment 531091 [details]
backtrace

Description of problem:

nautilus was killed by signal 11 in function nautilus_file_peek_display_name
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)

Version-Release number of selected component (if applicable):

architecture: x86_64
cmdline: nautilus
package: nautilus-2.28.4-15.el6
release: Red Hat Enterprise Linux Server release 6.1 (Santiago)

How reproducible:
randomly 

Steps to Reproduce:
1.Its produce randomly
2.
3.
  
Actual results:
nautilus crashed

Expected results:
nautilus should not crashed


Additional info:

Comment 2 Tomáš Bžatek 2011-11-01 14:54:06 UTC
Known issue but so far nobody has come with a good reproducer to be able to debug this issue.

Comment 3 RHEL Program Management 2012-05-03 04:34:14 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.


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