Bug 673064 - [abrt] nautilus-2.32.2-1.fc14: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] nautilus-2.32.2-1.fc14: Process /usr/bin/nautilus was killed by signal...
Keywords:
Status: CLOSED DUPLICATE of bug 657121
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:88355d3cc9d3df9cf8a93d445a5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-27 09:10 UTC by david fabre
Modified: 2015-03-03 22:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 16:23:56 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (45.14 KB, text/plain)
2011-01-27 09:10 UTC, david fabre 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description david fabre 2011-01-27 09:10:52 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: nautilus
comment: nautilus launch but error message stil appear
component: nautilus
executable: /usr/bin/nautilus
kernel: 2.6.35.6-45.fc14.i686
package: nautilus-2.32.2-1.fc14
rating: 3
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1293034167
uid: 500

How to reproduce
-----
1.lanchin nautilus from promp
it start but the prompt give this message
2.** (nautilus:32704): WARNING **: Failed to get the current CK session: GDBus.Error:org.freedesktop.ConsoleKit.Manager.GeneralError: Unable to lookup session information for process '32704'

3.
Comment 1 david fabre 2011-01-27 09:10:55 UTC 
Created attachment 475565 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 16:23:56 UTC 
Backtrace analysis found this bug to be similar to bug #657121, closing as duplicate.

Bugs which were found to be similar to this bug: bug #626691, bug #635313, bug #639050, bug #643649, bug #655308, bug #655370, bug #655589, bug #656288, bug #657121, bug #679402, bug #690027, bug #699446

This comment is automatically generated.

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