Red Hat Bugzilla – Bug 160674
gedit restarts when su on terminal
Last modified: 2007-11-30 17:11:07 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Description of problem:
On using Gnome Terminal 2.10.0, and su + passwd, I get this message alongwith a couple of error windows that says "An error occurred while loading or saving configuration information for gnome_segv. Some of your configuration settings may not work." and another that reads "The Application 'gedit' has quit unexpectedly ..."
The following were the warnings listed on the terminal. I have no clue to what they mean!
(gedit:7528): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
(gedit:7528): Bonobo-WARNING **: Failed to get '/desktop/gnome/interface/menubar_detachable': 'Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0'
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Logging to Terminal as su, then
2. typing gedit
Actual Results: as mentioned in the description
Expected Results: opened the geditor
Have you update somethings? i mean about gtk libs.
I have tryed and in the terminal have only an auth error but gedit works. The
auth error occurred because the gedit use the terminal current user while the
User Interface is another user.
tell me more to reproduce the error and find it.
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.
Setting status to CANTFIX, however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.
Thank you in advance.
(this message is mass message)