Bug 111244 - gnome-panel crashes on root X11 login
Summary: gnome-panel crashes on root X11 login
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: gnome-panel
Version: 3.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mark McLoughlin
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-12-01 10:06 UTC by Patrick C. F. Ernzer
Modified: 2007-11-30 22:06 UTC (History)
2 users (show)

Fixed In Version: gnome-panel-2.2.2.1-9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-05-18 14:22:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
strace -o /tmp/panel.trace gnome-panel (711.66 KB, text/plain)
2003-12-01 10:18 UTC, Patrick C. F. Ernzer
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2005:454 0 low SHIPPED_LIVE Updated gnome-panel and metacity packages 2005-05-18 04:00:00 UTC

Description Patrick C. F. Ernzer 2003-12-01 10:06:30 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031023

Description of problem:
When logging into X11, Gnome as root, the 'gnome-panel' crashes.

Version-Release number of selected component (if applicable):
2.2.2.1-4

How reproducible:
Always

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
minux panel.

Expected Results:  a warning window telling the user not to log in as
root, followed by a working Gnome session, panel included

Additional info:

yes, I did tell customer not to log into Gnome as root, still the
panel should not crash.

All other users are fine.

Comment 1 Patrick C. F. Ernzer 2003-12-01 10:18:04 UTC
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.

Comment 2 Suzanne Hillman 2003-12-03 21:43:06 UTC
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?

Comment 3 Patrick C. F. Ernzer 2003-12-05 12:02:56 UTC
Mr Litterst,

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)?

Thank you,

Patrick Ernzer

Comment 4 Mark McLoughlin 2004-02-27 16:25:29 UTC
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

Thanks...

Comment 5 Mark McLoughlin 2004-12-20 13:02:58 UTC
Ah, looking at the strace I see that $HOME was set to '/'.

gnome-panel-2.2.2.1-9 fixed a bug at login when $HOME is set to '/'

RHBA-2004:482 is the errata number

Comment 7 Stephan Litterst 2004-12-28 09:44:19 UTC
Hi Marc,

Where can I find gnome-panel-2.2.2.1-9???
On RHN there's only gnome-panel-2.2.2.1-8

Thanks Stephan

Comment 8 Mark McLoughlin 2005-01-04 15:23:08 UTC
Hmm, gnome-panel-2.2.2.1-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.

Comment 10 Tim Powers 2005-05-18 14:22:55 UTC
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.

http://rhn.redhat.com/errata/RHEA-2005-454.html



Note You need to log in before you can comment on or make changes to this bug.