Bug 621408 - [abrt] crash in nautilus-2.30.1-3.fc13: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in nautilus-2.30.1-3.fc13: Process /usr/bin/nautilus was killed ...
Status: CLOSED DUPLICATE of bug 608464
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b948150512d171e8d5427e07c0e...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-04 23:49 UTC by Daniel U. Thibault
Modified: 2015-03-03 22:51 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-11-08 19:11:55 UTC

Attachments (Terms of Use)
File: backtrace (43.66 KB, text/plain)
2010-08-04 23:49 UTC, Daniel U. Thibault 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Daniel U. Thibault 2010-08-04 23:49:08 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: nautilus
comment: See above.
component: nautilus
crash_function: nautilus_icon_canvas_item_get_image
executable: /usr/bin/nautilus
global_uuid: b948150512d171e8d5427e07c0e5d38614270a7f
kernel: 2.6.33.3-85.fc13.i686
package: nautilus-2.30.1-3.fc13
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. No idea.
2. Running Fedora 13 guest in VirtualBox 3.2.6 under Ubuntu 10.04 host.
3. Tried opening my public folder.
Comment 1 Daniel U. Thibault 2010-08-04 23:49:10 UTC 
Created attachment 436703 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 19:11:55 UTC 

*** This bug has been marked as a duplicate of bug 608464 ***
Comment 3 Karel Klíč 2010-11-08 19:11:55 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 #608464.

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