Bug 613467

Summary:	Nautilus core dumps (segmentation fault) when opened from terminal in super user mode
Product:	[Fedora] Fedora	Reporter:	John Dulaney <jdulaney>
Component:	nautilus	Assignee:	Tomáš Bžatek <tbzatek>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	13	CC:	bwalker, tbzatek, tsmetana
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-29 13:41:12 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:

Description John Dulaney 2010-07-11 21:45:02 UTC

Description of problem:
As far as UI goes, the opened instance of Nautilus seems fine.  However, in Terminal the following is repeated several times:
** (nautilus:11829): WARNING **: Could not inhibit power management: The name org.gnome.SessionManager was not provided by any .service files

Finally:
** (nautilus:11829): CRITICAL **: nautilus_file_get_uri: assertion `NAUTILUS_IS_FILE (file)' failed
Segmentation fault (core dumped)

Version-Release number of selected component (if applicable):
2.30.1-3

How reproducible:
100%

Steps to Reproduce:
1. in Gnome-Terminal, enter super user mode: su -
2. run nautilus
3.after a few minutes, nautilus crashes
  
Actual results:
Core dump

Expected results:
To complete my task and close everything normally.

Comment 1 Tomáš Bžatek 2010-07-21 14:37:31 UTC

Gnome applications should not be started under different user than your active desktop session, otherwise you would experience heavy load of various errors, mostly dbus messages.

However, a backtrace of the crash would greatly help to see what the real problem is.

Comment 2 Bug Zapper 2011-06-01 14:11:55 UTC

This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 3 Bug Zapper 2011-06-29 13:41:12 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.