Bug 593168

Summary: [abrt] crash in nautilus-2.28.4-2.fc12: raise: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: sergeobelare
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: loverboy76, npajkovs, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:062a7bf742f93251f5b2803f9913be15c7a5bfba
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 14:36:13 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 sergeobelare 2010-05-18 03:50:01 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: nautilus --sm-client-id 103f6cba69af5343d8127080711425830500000016880029 --sm-client-state-file /home/george/.config/session-state/nautilus-1274115703.state
component: nautilus
crash_function: raise
executable: /usr/bin/nautilus
global_uuid: 062a7bf742f93251f5b2803f9913be15c7a5bfba
kernel: 2.6.32.11-99.fc12.i686
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)

comment
-----
just try to write some files;

How to reproduce
-----
1.put in a new dvd+r
2. Open with CD/DVD creator
3. Put 4GiB or so of files on
4. Click write to disk.
5 wait for 30 mins while it pretends to be working
6 crash with you don't have sufficient permisions,

Comment 1 sergeobelare 2010-05-18 03:50:05 UTC
Created attachment 414715 [details]
File: backtrace

Comment 2 sergeobelare 2010-05-18 03:51:00 UTC
Package: nautilus-2.28.4-2.fc12
Architecture: i686
OS Release: Fedora release 12 (Constantine)


How to reproduce
-----
1.put in a new dvd+r
2. Open with CD/DVD creator
3. Put 4GiB or so of files on
4. Click write to disk.
5 wait for 30 mins while it pretends to be working
6 crash with you don't have sufficient permisions,


Comment
-----
just try to write some files;

Comment 3 sergeobelare 2010-05-18 03:51:29 UTC
Package: nautilus-2.28.4-2.fc12
Architecture: i686
OS Release: Fedora release 12 (Constantine)


How to reproduce
-----
1.put in a new dvd+r
2. Open with CD/DVD creator
3. Put 4GiB or so of files on
4. Click write to disk.
5 wait for 30 mins while it pretends to be working
6 crash with you don't have sufficient permisions,


Comment
-----
just try to write some files;

Comment 4 sergeobelare 2010-05-18 03:51:52 UTC
Package: nautilus-2.28.4-2.fc12
Architecture: i686
OS Release: Fedora release 12 (Constantine)


How to reproduce
-----
1.put in a new dvd+r
2. Open with CD/DVD creator
3. Put 4GiB or so of files on
4. Click write to disk.
5 wait for 30 mins while it pretends to be working
6 crash with you don't have sufficient permisions,


Comment
-----
just try to write some files;

Comment 5 Nikola Pajkovsky 2010-05-18 08:29:28 UTC
How many times did you try to fill in a bug with abrt?

Comment 6 sergeobelare 2010-05-20 17:37:20 UTC
Just once, but it may have been transmitted more than once. There is a chronic problem with fc12 wireless that causes constant dissassociation and reassociation, lease file parse errors, and others. The result is that I have to reconnect every few minutes.

Comment 7 sergeobelare 2010-05-20 17:46:12 UTC
Sorry, there appears to be no way to delete the duplicates.

The disk did not get written, I rebooted and tried again.
I left in in the writing phase. 
When I got back, the laptop was locked up and had to be power restarted.

The disk was still untouched.

My next attempt is a bit fuzzy -- I remember it asking over and over about Window naming compatibility. Somehow I canceled out of it. I remember seeing an error indicating that the whole process had failed, but this time the disk was actually written and readable.

I'll try it again in FC13 when it comes unless there's more I can provide for this bug.

Comment 8 Karel Klíč 2010-05-25 08:41:14 UTC
*** Bug 573483 has been marked as a duplicate of this bug. ***

Comment 9 Bug Zapper 2010-11-03 14:41:23 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 10 Bug Zapper 2010-12-03 14:36:13 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.