Bug 1014502

Summary: gnome hangs su to root from other users
Product: [Fedora] Fedora Reporter: lionghostshop
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dkbatson, fmuellner, otaylor, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:27:50 UTC Type: Bug
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
screenshot none

Description lionghostshop 2013-10-02 08:56:20 UTC
Created attachment 806329 [details]
screenshot

Description of problem:


Version-Release number of selected component (if applicable):
gnome-shell-3.8.4-2.fc19.x86_64

How reproducible:


Steps to Reproduce:
1. Login gnome as an ordinary user
2. open a terminal
3. sudo su
4. gedit
5. click the button near "Activities" as shown in the attachment

Actual results:
Hangs

Expected results:
menu pop up

Additional info:

Comment 1 Florian Müllner 2013-10-25 15:33:49 UTC
The underlying problem is that permissions of the mmapped dconf database are changed behind our/dconf's back. Possible fixes would be to let "su" modify XDG_RUNTIME_DIR as well, or be more cautious in dconf when updating permissions. However it's not an issue we can easily work around in gnome-shell, and (in my opinion) we shouldn't in any case.

Comment 2 David Batson 2014-04-02 10:13:31 UTC
I ran into this or a similar problem in F19. Using beesu as per the following bug report solved the problem there. Haven't been able to try it yet in F20 as I do not have access to the internet with my Fedora box ATM to install beesu.

https://bugzilla.redhat.com/show_bug.cgi?id=972600

There are several issues in the bug report. See in particular comment #14 and #23.

Comment 3 Fedora End Of Life 2015-01-09 20:04:43 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 4 Fedora End Of Life 2015-02-17 17:27:50 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.