Bug 643649 - [abrt] nautilus-2.32.0-1.fc14: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] nautilus-2.32.0-1.fc14: Process /usr/bin/nautilus was killed by signal...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 14
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0ea05cc018c9fc0cbf4da474ae2...
: 626691 635313 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-16 19:09 UTC by ricardo.gladwell
Modified: 2015-03-03 22:54 UTC (History)
47 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-28 14:10:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (50.40 KB, text/plain)
2010-10-16 19:09 UTC, ricardo.gladwell
no flags Details

Description ricardo.gladwell 2010-10-16 19:09:24 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: nautilus
component: nautilus
crash_function: nautilus_icon_container_search_preedit_changed
executable: /usr/bin/nautilus
kernel: 2.6.35.6-39.fc14.i686.PAE
package: nautilus-2.32.0-1.fc14
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1286828160
uid: 500

Comment 1 ricardo.gladwell 2010-10-16 19:09:26 UTC
Created attachment 453878 [details]
File: backtrace

Comment 2 Radek Jirovsky 2010-10-31 18:26:13 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Closing video folder (icon view).
2.
3.

Comment 3 Radek Jirovsky 2010-11-02 17:44:24 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Switch to video folder (using sidebar Places)
2. It caches thumbnails.
3. Crash.

Comment 4 alex刺客 2010-11-03 10:17:28 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Open the folder in some cases!
2.
3.

Comment 5 Radek Jirovsky 2010-11-03 12:41:32 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Switching to another directory using sidebar panel Places.
2.
3.

Comment 6 Tomasz Szkółka 2010-11-05 16:01:19 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Click the "Close" button on window titlebar.

Comment
-----
Error message appears after closing Nautilus. Nothing happend.

Comment 7 Lee Dan 2010-11-07 16:27:22 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.open nautilus
2.right click and create a folder
3.press enter, then press F2 to rename it.

Hard to reproduce...

Comment
-----
It's hard to reproduce, hoping the log do help.

Comment 8 Karel Klíč 2010-11-08 19:07:39 UTC
*** Bug 626691 has been marked as a duplicate of this bug. ***

Comment 9 Karel Klíč 2010-11-08 19:07:43 UTC
*** Bug 635313 has been marked as a duplicate of this bug. ***

Comment 10 Lee Dan 2010-11-11 13:45:14 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. open nautilus
2. use a terminal to gzip a pdf document.
3. select the gzipped file and press enter to open it.

Comment 11 cyrushmh 2010-11-11 14:41:05 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.close ibus-pinyin & ibus
2.
3.

Comment 12 ola.polak 2010-11-12 00:20:50 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.I installed wine
2.I tried to run setup file from unreal tournament 2004
3. wine crushed.

Comment 13 Andreas Matzi 2010-11-13 12:38:13 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. ????
2.
3.

Comment 14 Fred 2010-11-17 04:48:58 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Open Nautilus
2. Navigate using keyboard to specific file/folder
3. Click or press Enter key
=> Crash immediately. 


Comment
-----
tends to happens some minutes after loging in. Once it occurs once, it will systematically happen, until logging out and back in.

Comment 15 Kailash 2010-11-17 08:00:04 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Closed nautilus
2.
3.

Comment 16 adriano 2010-11-17 09:24:31 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


Comment
-----
Don't know. Crash at session start...

Comment 17 Tomasz Szkółka 2010-11-17 10:14:46 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Click the "close" button.

Comment
-----
Error message appears after closing nautilus window.

Comment 18 Milan 2010-11-17 12:55:48 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. I closed nautilus with multiple tabs.
2.
3.

Comment 19 Justin O'Brien 2010-11-19 08:24:43 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


Comment
-----
happened when I was moving a file to /usr/share/pixmaps and creating a desktop icon for a shell script

Comment 20 Alfredo Pons Menargues 2011-01-10 12:02:57 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.I don't remeber now
2.
3.

Comment 21 Jarom D Luker 2011-02-03 07:38:09 UTC
Package: nautilus-2.32.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


Comment
-----
The bug just popped up.  It didn't seem to stem from any applications I was using at the time...


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