RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 652607 - segfault in nautilus while deleting two archives and two dirs
Summary: segfault in nautilus while deleting two archives and two dirs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: nautilus
Version: 6.1
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Tomáš Bžatek
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-12 10:27 UTC by Vladimir Benes
Modified: 2018-11-14 15:07 UTC (History)
4 users (show)

Fixed In Version: nautilus-2.28.4-17.el6
Doc Type: Bug Fix
Doc Text:
Cause: A race condition in async code getting information of a file that is being deleted. Consequence: Ocassional crash occured. Fix: A workaround has been placed, checking for NULL objects. Result: No more crashes.
Clone Of:
Environment:
Last Closed: 2011-08-24 10:56:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
backtrace from abrt (23.19 KB, text/plain)
2010-11-12 10:28 UTC, Vladimir Benes 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 602500 0 High RESOLVED Crash in nautilus_file_peek_display_name at nautilus-file.c line 3692 2020-09-07 03:49:59 UTC
Red Hat Product Errata RHBA-2011:1203 0 normal SHIPPED_LIVE nautilus bug fix update 2011-08-24 10:55:53 UTC

Description Vladimir Benes 2010-11-12 10:27:57 UTC 
Description of problem:
I was deleteing two srpm archives together with their content (two dirs) and nautilus crashed

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

nautilus-2.28.4-15.el6.x86_64

How reproducible:
cannot reproduce now

Steps to Reproduce:
1.download libdrm and ibus-chewing srpms
2.extract them both
3.select both srpms and directories and delete them (shift+del)  
  
Actual results:
crash

Expected results:
no crash

Additional info:
don;t know where the problem can be as I cannot reproduce now.. maybe backtrace can tell you more
Comment 1 Vladimir Benes 2010-11-12 10:28:24 UTC 
Created attachment 460007 [details]
backtrace from abrt
Comment 3 Tomáš Bžatek 2011-01-14 17:27:20 UTC 
I think you're seeing a crash in nautilus_file_peek_display_name() though it's
not obvious from the backtrace. Please install debuginfo packages next time :-)

That's bug 664679.

We still didn't have luck in reproducing this issue. Some people report crazy
steps but it never really worked on my machine.
Comment 4 Tomáš Bžatek 2011-01-26 13:17:04 UTC 
Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=602500
Comment 5 Tomáš Bžatek 2011-01-27 10:50:36 UTC 
Workaround committed upstream, going to include it in RHEL6 as well.

Potential steps leading to reproducer:
 1. for i in `seq 1 8`; do dd if=/dev/zero of=file${i} bs=1M count=400; done
 2. run nautilus --browser
 3. switch left pane to Informations
 4. Ctrl+A, Shift+Delete
 5. press left arrow or randomly select some files, that could trigger the crash. Hit rate is awfully low though.
Comment 9 Florian Nadge 2011-02-01 14:38:32 UTC 
Please be so kind and add a few key words to the technical note of this
bugzilla entry using the following structure:

Cause:

Consequence:

Fix:

Result:


For details, see:
https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes

Thanks
Comment 10 Florian Nadge 2011-02-01 14:38:32 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause:

Consequence:

Fix:

Result:
Comment 11 Tomáš Bžatek 2011-02-07 14:32:59 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,7 +1,7 @@
-Cause:
+Cause: A race condition in async code getting information of a file that is being deleted.
 
-Consequence:
+Consequence: Ocassional crash occured.
 
-Fix:
+Fix: A workaround has been placed, checking for NULL objects.
 
-Result:+Result: No more crashes.
Comment 20 errata-xmlrpc 2011-08-24 10:56:12 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-1203.html
Note You need to log in before you can comment on or make changes to this bug.