Bug 681101

Summary: [abrt] ERROR:nautilus-bookmark.c:501:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->details->file))
Product: [Fedora] Fedora Reporter: mrblack
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: brieucd, bugs, ccecchi, livermob, tbzatek, tsmetana, twstickywebb
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard: abrt_hash:050ddc2d9a9bd0f45ec7274f39c090c7b8e45748
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 16:04:46 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 mrblack 2011-03-01 05:25:46 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 26655 bytes
cmdline: nautilus
component: nautilus
Attached file: coredump, 270041088 bytes
crash_function: nautilus_bookmark_connect_file
executable: /usr/bin/nautilus
kernel: 2.6.35.11-83.fc14.x86_64
package: nautilus-2.32.2.1-2.fc14
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1298956564
uid: 500

How to reproduce
-----
1. I work in nautilus
2. And crash
3.

Comment 1 mrblack 2011-03-01 05:25:49 UTC
Created attachment 481513 [details]
File: backtrace

Comment 2 Michael Schwendt 2011-03-07 09:17:46 UTC
*** Bug 673489 has been marked as a duplicate of this bug. ***

Comment 3 Michael Schwendt 2011-03-07 09:17:54 UTC
*** Bug 675624 has been marked as a duplicate of this bug. ***

Comment 4 John Keller 2011-03-07 11:15:05 UTC
Attachment 479868 [details] in bug 553069 is my backtrace of the same error:

Package: nautilus-2.32.2.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
I'm working with a rather tempermental SSH/SFTP service running on a Windows
server (server and service not admin'd by me).

The service used is found at this address:
http://www.kpym.com/2/kpym/index.htm

It seems to be cranky when I have private key and haven't loaded the public key
on the server. The admins added my public key, but the service still seems
cranky: for example, it doesn't like it when I connect to the root when my SFTP
hom is something else. Nautilus reports some sort of error when I do that, but
I can get around it by simply adding the full home path after the usser@server

This crash happened somewhere with all that: I think my private/public key pair
were active, but I hadn't yet added the final path to my "~/.gtk-bookmarks"
file and so was getting the Nautilus error message.

The crash happened when I had pressed the "eject" button next to the mounted
server.

(Sorry, that's the best I can do to give you the context and way to reproduce
the crash. It's almost certainly due to the Windows service, but I wouldn't
expect Nautilus to crash from it.)

Comment 5 abrt-bot 2012-03-20 17:10:13 UTC
*** Bug 781982 has been marked as a duplicate of this bug. ***

Comment 6 Fedora End Of Life 2012-08-16 16:04:49 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping