 | | | Gnome configuration problem | Gnome configuration problem 2005-04-06 - By Gavin McDonald
Back
I've had similar symptoms when gconf tried to open two concurrent Gnome
sessions for one username. Also, similar "broken" gnome sessions arise when
the permissions on the .gconf directory are incorrectly set. (ie AND w/
700.)
Regards,
Gavin McDonald
-- --Original Message-- --
From: redhat-list-bounces@(protected) [mailto:redhat-list-bounces@(protected)]
On Behalf Of Jeff Boyce
Sent: Wednesday, April 06, 2005 11:44 AM
To: redhat-list@(protected)
Subject: Gnome configuration problem
Greetings -
Dell PE 2600, RHEL3, primarily configured as file server with Samba.
Logging into my server and starting X today resulted in an obvious problem.
I had a black desktop screen that was blank (several icons are normally on a
blue desktop screen) and I was unable to open a file manager window. I am
able to open a terminal window and run my Arkeia tape backup software which
displays in Xwindows. It appears I may have messed up my Gnome
configuration, but am not sure what is wrong, or how to fix it. The only
unique actions that occurred on the system the previous day included the
installation of the NUT (network ups tools) software from source, and the
subsequent uninstallation of NUT. I had never installed from source before
and the installation went fine without errors. There was not a *make
uninstall* for the program so I followed some instructions to review the
*makefile* to see where all the files where installed and delete the
files/directories manually. The following directories were removed
(actually moved to Trash).
/opt/NUT/nut-2.0.1 (contained the unzipped source files)
/usr/local/ups/man
/usr/local/ups/share
/usr/local/ups/bin
/usr/local/ups/sbin
Up2date is not configured to run in an automated fashion, therefore an
updated Gnome could not be the source of the problem. A check of the
logfiles shows the information listed below, but this information was also
logged on previous days prior to the problem occurring, so I am not sure
that it is relevant to the problem. What diagnostic steps can I take to
identify the root cause of the problem, and return my desktop to normal?
Apr 6 10:24:08 bison -- root[30000]: ROOT LOGIN ON tty1
Apr 6 10:24:13 bison modprobe: modprobe: Can't locate module
char-major-10-134
Apr 6 10:24:16 bison gconfd (root-31746): starting (version 2.2.1), pid
31746 user 'root'
Apr 6 10:24:16 bison gconfd (root-31746): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source
at position 0
Apr 6 10:24:16 bison gconfd (root-31746): Resolved address
"xml:readwrite:/root/.gconf" to a writable config source at position 1
Apr 6 10:24:16 bison gconfd (root-31746): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at
position 2
Jeff Boyce
www.meridianenv.com
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@(protected)?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@(protected)?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
Earn $52 per hosting referral at Lunarpages.
|
|
|