Bug 656749

Summary: [abrt] nautilus-2.32.1-1.fc14: handle_error: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Danubio <nubbao>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: aa.borba, ccecchi, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:f26e77e27b5a1dc1f1f3a0015b2ea9951956acd7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 14:38:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Danubio 2010-11-24 02:00:38 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: nautilus
component: nautilus
crash_function: handle_error
executable: /usr/bin/nautilus
kernel: 2.6.35.6-48.fc14.i686
package: nautilus-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1290561198
uid: 500

How to reproduce
-----
1.aconteceu enquanto usava o empathy e nautilus
2.
3.
Comment 1 Danubio 2010-11-24 02:00:41 UTC 
Created attachment 462504 [details]
File: backtrace
Comment 2 Danubio 2010-11-24 22:34:39 UTC 
Package: nautilus-2.32.1-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.aconteceu enquanto usava o empathy e nautilus
2.
3.
Comment 3 Alexandre A. Borba 2010-12-04 18:14:29 UTC 
Package: nautilus-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Watching a video in totem
2. Close totem
3. Then crash
Comment 4 abrt-bot 2012-03-30 14:38:57 UTC 
Backtrace analysis found this bug to be similar to bug #705357, closing as duplicate.

Bugs which were found to be similar to this bug: bug #649709, bug #672717, bug #705357

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 705357 ***