Bug 588301

Summary: [abrt] crash in nautilus-2.28.4-2.fc12: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Tyler Starke <sirebral>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:b00af5cb7f85daf34b96fa3822dc090cce540dda
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-25 10:22:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
File: backtrace none

Description Tyler Starke 2010-05-03 12:44:58 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: nautilus
component: nautilus
executable: /usr/bin/nautilus
global_uuid: b00af5cb7f85daf34b96fa3822dc090cce540dda
package: nautilus-2.28.4-2.fc12
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

As above.

My guess it is likely a permissions problem with PogoPlug, or, from what the error reads it was attempting to rename folder 'untitled folder' when it had not been correctly named 'untitled folder'. Right away at the top you see 'No such file or directory.', so it is probably an error in the PogoPlug firware.

How to reproduce
1. I am using my pogoplugfs (for Pogo Plug Drive)
2. I created a new folder and named it, it was 'untitled folder'
3. Nautilus asked me if I wanted to change the name, I clicked Yes
4. When I created the folder and let it retain the 'untitled folder' name first, then changed it, the crash did not occur.

Comment 1 Tyler Starke 2010-05-03 12:45:00 UTC
Created attachment 410971 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 10:22:15 UTC

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

Comment 3 Karel Klíč 2010-05-25 10:22:15 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 #556444.

Sorry for the inconvenience.