Bug 8744

Summary: Errors during startup
Product: [Retired] Red Hat Linux Reporter: Tim Waugh <twaugh>
Component: gnome-coreAssignee: Owen Taylor <otaylor>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-02-03 21:02:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Tim Waugh 2000-01-22 11:42:12 UTC
GNOME workstation installation.
Log in as root.  On my 486 with 32Mb I get a dialog box:

"panel
 No response to the SaveYourself command."

Cancel it. Log out.
.xsession-errors contains:

SESSION_MANAGER=local/cocobean.elk.co.uk:/tmp/.ICE-unix/1053,tcp/cocobean.elk.co.uk:1038
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
xscreensaver: Can't open display: :0
xscreensaver: initial effective uid/gid was root/root (0/0)
xscreensaver: running as nobody/nobody (99/99)

xscreensaver: Errors at startup are usually authorization problems.
              Did you read the manual and the FAQ?  Specifically,
              the parts of the manual that talk about XAUTH, XDM,
              and root logins?

              http://www.jwz.org/xscreensaver/man.html

rm: cannot remove `/root/.gnome//gmc-v2LrCF': No such file or directory
subshell.c: couldn't get terminal settings: Inappropriate ioctl for device

GnomeUI-WARNING **: Could not open help topics file NULL

Comment 1 Owen Taylor 2000-02-03 21:02:59 UTC
The second part of the .xsession-errors is simply Xscreensaver
not working as root. See the URL if you want more information
about the issue.

See:

 http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=8996

For more information about the warning dialog and a possible workaround.
(The answer is basically "your machine is too slow to run GNOME"
:-(. It's hard to fix this without adversly impacting the user
experience for users on faster machines.

I am changing this delay from 10 seconds by default to 15 seconds
in our packages. Hopefully this will ameliorate the problem.