Bug 712365 - [abrt] nautilus-2.30.1-6.fc13: g_bookmark_file_get_uris: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] nautilus-2.30.1-6.fc13: g_bookmark_file_get_uris: Process /usr/bin/nau...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 13
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a2a5eb957d3025a4b676270a567...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-10 12:48 UTC by ipsc-webmaster
Modified: 2015-03-03 23:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 11:41:05 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (26.02 KB, text/plain)
2011-06-10 12:48 UTC, ipsc-webmaster 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description ipsc-webmaster 2011-06-10 12:48:22 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: nautilus
component: nautilus
crash_function: g_bookmark_file_get_uris
executable: /usr/bin/nautilus
kernel: 2.6.34.8-68.fc13.i686
package: nautilus-2.30.1-6.fc13
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1302774418
uid: 500

How to reproduce
-----
1. used regularly, but suddenly nautilus crashed for no reason...
2.
3.
Comment 1 ipsc-webmaster 2011-06-10 12:48:24 UTC 
Created attachment 504099 [details]
File: backtrace
Comment 2 Bug Zapper 2011-06-27 11:41:05 UTC 
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.