Bug 679819 - [abrt] nautilus-2.32.2.1-2.fc14: g_list_foreach: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] nautilus-2.32.2.1-2.fc14: g_list_foreach: Process /usr/bin/nautilus wa...
Keywords:
Status: CLOSED DUPLICATE of bug 701372
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4e7d456791e6a6203ab23416a10...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-23 15:22 UTC by sly
Modified: 2015-03-03 22:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 15:07:12 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (30.12 KB, text/plain)
2011-02-23 15:22 UTC, sly 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description sly 2011-02-23 15:22:40 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 30847 bytes
cmdline: nautilus --sm-client-id 10dd7f9d2a997a3ee3128882211074180200000018360035 --sm-client-state-file /home/sly/.config/session-state/nautilus-1297706243.state
component: nautilus
Attached file: coredump, 86941696 bytes
crash_function: g_list_foreach
executable: /usr/bin/nautilus
kernel: 2.6.35.9-64.fc14.i686
package: nautilus-2.32.2.1-2.fc14
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: I closed totem and then nautilus crashed. Not sure what caused it.
time: 1298473917
uid: 500
Comment 1 sly 2011-02-23 15:22:42 UTC 
Created attachment 480492 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 15:07:12 UTC 
Backtrace analysis found this bug to be similar to bug #701372, closing as duplicate.

Bugs which were found to be similar to this bug: bug #633921, bug #667723, bug #684437, bug #701372

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 701372 ***
Note You need to log in before you can comment on or make changes to this bug.