Bug 673064

Summary: [abrt] nautilus-2.32.2-1.fc14: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: david fabre <dfmonaco>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: ccecchi, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:88355d3cc9d3df9cf8a93d445a55be6b28c96d15
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 16:23:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

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 ***