Red Hat Bugzilla – Bug 609251
opening file with su
Last modified: 2011-06-27 15:09:06 EDT
Description of problem:
If I open a file with " su 'gedit filename' " and the root password, this error is printed multiple times in the terminal:
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
It does not prevent me from editing or saving the file.
Version-Release number of selected component (if applicable):
Very consistent, on multiple installations and multiple machines. I'm seeing it now with a fresh installation of Fedora 13 on a LinuxCertified 2210S.
Steps to Reproduce:
1. Open terminal.
2. Type (for instance): su -c 'gedit /boot/grub/grub.conf'
3. Enter root password at prompt.
The file opens in Gedit and the above error message is printed multiple times in the terminal.
The file should open in Gedit with no errors printed in the terminal.
I think I saw this bug reported for a previous release of Fedora, but it was closed because of EOL. It's still happening in Fedora 13.
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:
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.