Bug 2159 - no screensaver when X run as root
no screensaver when X run as root
Product: Red Hat Linux
Classification: Retired
Component: xscreensaver (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Cristian Gafton
Depends On:
  Show dependency treegraph
Reported: 1999-04-12 23:39 EDT by David Miller
Modified: 2008-05-01 11:37 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-04-22 16:35:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Miller 1999-04-12 23:39:03 EDT
Run X via 'startx' after a fresh install, xscreensaver
does not run successfully.

Xscreensaver states:
"Cannot connect to screen :0
 session run as root (0/0)
 running as nobody (99/99)

 Problems like this are usually due to authorization
 problems, did you read the manual?"

I also notice that if I run X as a normal user, and
'su' in a terminal, I cannot start any X clients as
root into that session.

The supreme analness of X in RH6.0 is really becomming
frustrating, and I know it will be so for many users.
Comment 1 Preston Brown 1999-04-13 12:00:59 EDT
We are working on having a 'su' command that will do xauth stuff.
What do you want dave?  For us to continue to have a gaping security
hole because we were using xhost for a long time when running X with
startx?  xdm/gdm/kdm have been using xauth for ages.  You learn to

can you please tell me why xscreensaver is being run as root?  I
thought we removed the SUID bit also.
Comment 2 Bill Nottingham 1999-04-13 14:27:59 EDT
um, I think xscreensaver was running as root for him because
he was running as root. :)
Comment 3 Bill Nottingham 1999-04-22 16:35:59 EDT
fixed in a later xscreensaver release

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