Bug 835320 - Exit 1 nautilus disappears without user closing
Exit 1 nautilus disappears without user closing
Product: Fedora
Classification: Fedora
Component: nautilus (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Tomáš Bžatek
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-06-25 20:49 EDT by Kerry
Modified: 2015-03-03 18:05 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-13 18:03:13 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Transcript of normal console run and a gdb run (10.01 KB, text/plain)
2012-06-25 20:49 EDT, Kerry
no flags Details

  None (edit)
Description Kerry 2012-06-25 20:49:48 EDT
Created attachment 594318 [details]
Transcript of normal console run and a gdb run

Description of problem:
Run nautilus, do nothing. A minute or two later nautilus has disappeared. It appears to close itself. There is no crash, no core, just an 'exit 1' on the console. It means it is impossible to run nautilus for more than a few minutes.

Version-Release number of selected component (if applicable):
$ rpm -q nautilus

How reproducible:

Steps to Reproduce:
1. Open nautilus
2. Wait a few minutes
Actual results:
Nautilus will close itself after a minute or two

Expected results:
Nautilus shouldn't close until I close it.

Additional info:
Running in gdb it says this before it closes:
[New Thread 0xb7d67b40 (LWP 16092)]
[New Thread 0xb73ffb40 (LWP 16105)]
[Thread 0xb7d67b40 (LWP 16092) exited]
[Thread 0xb73ffb40 (LWP 16105) exited]
[Inferior 1 (process 16077) exited normally]

See attachment for a normal console run and a gdb run.
Comment 1 Fedora End Of Life 2013-01-16 14:02:05 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is 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" 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: 
Comment 2 Fedora End Of Life 2013-02-13 18:03:17 EST
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.