Red Hat Bugzilla – Bug 111244
gnome-panel crashes on root X11 login
Last modified: 2007-11-30 17:06:59 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
When logging into X11, Gnome as root, the 'gnome-panel' crashes.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. log into X11 as root
2. wait for session to start
3. panel crashes
Actual Results: gnome panel crashes (repeatedly), clicking 'OK' in
the crash dialog repeatedly will yield after some time a gnome session
Expected Results: a warning window telling the user not to log in as
root, followed by a working Gnome session, panel included
yes, I did tell customer not to log into Gnome as root, still the
panel should not crash.
All other users are fine.
Created attachment 96257 [details]
strace -o /tmp/panel.trace gnome-panel
an strace of root launching the gnome-panel via a Terminal after clicking 'OK'
in the crash dialog repeatedly until the gnome session (minus panel) was up.
I am unable to reproduce this behavior on my own RHEL3 machine
internally. Is this something that you can cause to happen on multiple
machines, or only a specific one?
as I am unablke to be on-site at the moment, could you please attach
the kickstart file we use to install the machine ti this bug?
Can you also please try to reproduce the behaviour on a second machine
(once you have a second machine for testing)?
Patrick: any more information on this bug?
+ Is it generally reproducible for you on a new install
+ If not, how specifically is the panel configured?
+ Could you attempt to get a stack trace of the crash,
preferrably with the debuginfo package installed
Ah, looking at the strace I see that $HOME was set to '/'.
gnome-panel-188.8.131.52-9 fixed a bug at login when $HOME is set to '/'
RHBA-2004:482 is the errata number
Where can I find gnome-panel-184.108.40.206-9???
On RHN there's only gnome-panel-220.127.116.11-8
Hmm, gnome-panel-18.104.22.168-9 seems to have missed the Quaterly Update.
If neccessary, you should be able to ask support for a hotfix package
in advance of the next quaterly update.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.