Bug 2159

Summary:	no screensaver when X run as root
Product:	[Retired] Red Hat Linux	Reporter:	David Miller <davem>
Component:	xscreensaver	Assignee:	Cristian Gafton <gafton>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0	CC:	gafton, msw, pbrown
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	1999-04-22 20:35:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Miller 1999-04-13 03:39:03 UTC

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 16:00:59 UTC

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
adapt.

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 18:27:59 UTC

um, I think xscreensaver was running as root for him because
he was running as root. :)

Comment 3 Bill Nottingham 1999-04-22 20:35:59 UTC

fixed in a later xscreensaver release