Bug 4552 – Selecting "start X automatically upon bootup" when it already does starts it twice

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 4552 - Selecting "start X automatically upon bootup" when it already does starts it twice

Summary:	Selecting "start X automatically upon bootup" when it already does starts it ...

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	Xconfigurator (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	i386 Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-08-16 15:59 EDT by tmanning
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-08-23 10:50:22 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description tmanning 1999-08-16 15:59:01 EDT

It seems (for me anyway) that if you select the option at
the end of the Xconfigurator session to start X
automagically upon bootup that as soon as you enter your
login and password it re-loads X and you have to login one
more time. This only happens upon first bootup (ie not when
you just logout and back in again), and doesn't seem to
affect Root, only normal users. (?) I'm pretty new at this,
so I may have missed something important.

Comment 1 tmanning 1999-08-16 16:02:59 EDT

I only had this problem when X was already configured to start
automatically (I re-ran Xconfigurator a month after initial install
to set up X for a different monitor...)

Comment 2 Preston Brown 1999-08-23 10:50:59 EDT

we can't duplicate this problem, and have no other reports of similar
difficulties, so we must assume it is user configuration error.

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