Bug 549700 - [abrt] crash in nautilus-2.28.4-1.fc12
Summary: [abrt] crash in nautilus-2.28.4-1.fc12
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:93911840661503476a3185051ed...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-22 11:58 UTC by Bernd Braeker
Modified: 2015-03-03 22:42 UTC (History)
30 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-04 01:21:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (18.64 KB, text/plain)
2009-12-22 11:58 UTC, Bernd Braeker
no flags Details
File: backtrace (30.00 KB, text/plain)
2010-01-12 05:02 UTC, Ignasius Denok
no flags Details
Backtrace, deleting of GPG keys, see my comment below. (22.00 KB, text/plain)
2010-02-02 23:31 UTC, Václav Mocek
no flags Details

Description Bernd Braeker 2009-12-22 11:58:20 UTC
abrt 1.0.2 detected a crash.

How to reproduce
-----
1.Select all files in a directory (Ctrl-A)
2.Delete the files (Shift-Del)
3.

Comment: This problem occures occationally and cannot reproduced at will.
Attached file: backtrace
cmdline: nautilus
component: nautilus
executable: /usr/bin/nautilus
kernel: 2.6.31.6-166.fc12.i686
package: nautilus-2.28.4-1.fc12
rating: 3
reason: Process was terminated by signal 11 (Segmentation fault)

Comment 1 Bernd Braeker 2009-12-22 11:58:25 UTC
Created attachment 379810 [details]
File: backtrace

Comment 2 Ignasius Denok 2010-01-12 04:59:23 UTC
In my case, nautilus usually crash if it's use 20% or more RAM and it's (usually) because nautilus make a thumbnails from picture and (maybe comix) from comic book archived / cbz.

Comment 3 Ignasius Denok 2010-01-12 05:02:10 UTC
Created attachment 383172 [details]
File: backtrace

Comment 4 Tomáš Bžatek 2010-01-12 10:32:04 UTC
(In reply to comment #2)
> In my case, nautilus usually crash if it's use 20% or more RAM and it's
> (usually) because nautilus make a thumbnails from picture and (maybe comix)
> from comic book archived / cbz.
Can you describe usual contents in the directory, when it crashes? I.e. images, movies, text files, binaries, archives, etc. I suppose browser mode, list view, visible sidebar on the Information page.

Comment 5 Bernd Braeker 2010-01-12 10:52:06 UTC
(In reply to comment #4)
> (In reply to comment #2)
> > In my case, nautilus usually crash if it's use 20% or more RAM and it's
> > (usually) because nautilus make a thumbnails from picture and (maybe comix)
> > from comic book archived / cbz.
> Can you describe usual contents in the directory, when it crashes? I.e. images,
> movies, text files, binaries, archives, etc. I suppose browser mode, list view,
> visible sidebar on the Information page.    

I use alway list view with visible sidebar. The type of files are mixed. When the crash occures the listing contains 100+ files.

Comment 6 Ignasius Denok 2010-01-12 12:55:21 UTC
(In reply to comment #4)
> (In reply to comment #2)
> > In my case, nautilus usually crash if it's use 20% or more RAM and it's
> > (usually) because nautilus make a thumbnails from picture and (maybe comix)
> > from comic book archived / cbz.
> Can you describe usual contents in the directory, when it crashes? I.e. images,
> movies, text files, binaries, archives, etc. I suppose browser mode, list view,
> visible sidebar on the Information page.    

Using browser mode, places, list view, thumbnail from local only with max size 10MiB, and I always open nautilus and never close it.
And like Bernd Braeker, I always open a directory with 60+ files (mainly cbz).

Comment 7 Václav Mocek 2010-02-02 23:26:18 UTC
I found a similar problem and I am able to reproduce it any time I want.

Steps:
1) Set compact view (Ctrl-3) as default.
2) Download  rpmfusion-free-release-stable.noarch.rpm and rpmfusion-nonfree-release-stable.noarch.rpm (sorry, no joke).
3) Extract these files using the archiver on the desktop, so you have directory ~/Desktop/etc/pki/rpm-gpg/RPM-GPG-*.
4) Open directory ~/Desktop/etc/pki/rpm-gpg/ in Nautilus, there are GPG keys and related symbolic links.
5) Select first one and start pressing button Delete quickly.
6) Nautilus crashes ....

Again, I am able to reproduce it any time, if you need some help, please let me know. (I jiny jazyk by nemel byt problem ;-))

Comment 8 Václav Mocek 2010-02-02 23:31:00 UTC
Created attachment 388399 [details]
Backtrace, deleting of GPG keys, see my comment below.

Comment 9 Bug Zapper 2010-11-04 02:47:42 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-04 01:21:40 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.


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