Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 651401

Summary: [abrt] nautilus-2.28.4-15.el6: raise: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Product: Red Hat Enterprise Linux 6 Reporter: Mike Khusid <mkhusid>
Component: nautilusAssignee: Carlos Soriano <csoriano>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: bkahn, jofernan
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1e0a08a9c3c9193203e7dbe90b3ae522b89d0087
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 10:37:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Mike Khusid 2010-11-09 14:11:50 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: nautilus
component: nautilus
crash_function: raise
executable: /usr/bin/nautilus
kernel: 2.6.32-71.el6.x86_64
package: nautilus-2.28.4-15.el6
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
release: Red Hat Enterprise Linux Workstation release 6.0 (Santiago)
time: 1289311547
uid: 500

How to reproduce
-----
1. Open a folder in Nautilus via davs:// protocol
2. Create a new folder
3. Run a number of operations, for example add files and delete files
4. Create a new folder and assign name to it (preferrably long name)
5. Crash while renaming folder from "untitled folder" to actual name

Comment 1 Mike Khusid 2010-11-09 14:11:53 UTC
Created attachment 459114 [details]
File: backtrace

Comment 4 Tomáš Bžatek 2011-01-17 17:44:09 UTC
(In reply to comment #0)
> 2. Create a new folder
> 3. Run a number of operations, for example add files and delete files
Are these steps necessary? Is this crash reproducible? Is there a difference between dav and davs? (unlikely)

I'm unable to reproduce it here, this could be one of many async timing issues.

Comment 5 Mike Khusid 2011-01-18 22:59:51 UTC
I am unable to reproduce this bug either, I receive error message "Bad Gateway" when trying to rename.  Not as bad as crash, but still functionality is broken.

I do not have access to dav://, only to davs://

Comment 6 Tomáš Bžatek 2011-01-20 13:32:25 UTC
(In reply to comment #5)
> I am unable to reproduce this bug either, I receive error message "Bad Gateway"
> when trying to rename.  Not as bad as crash, but still functionality is broken.
That looks like another issue - backend specific. Does cadaver work? Is it required to specify a password for the file?

Comment 9 Mike Khusid 2011-06-10 14:10:56 UTC
(In reply to comment #6)
> (In reply to comment #5)
> > I am unable to reproduce this bug either, I receive error message "Bad Gateway"
> > when trying to rename.  Not as bad as crash, but still functionality is broken.
> That looks like another issue - backend specific. Does cadaver work? Is it
> required to specify a password for the file?


Alfresco server is a backend for my davs session. Folder operations are extremely limited in functionality as they produce a number of errors. 

However, I am unable to reproduce a crash. 

Cadaver is not available in RHEL6.1 neither from RHEL nor from EPEL, so I can't test using that.

Comment 13 RHEL Program Management 2012-05-03 04:34:20 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.

Comment 15 Jan Kurik 2017-12-06 10:37:03 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/