Bug 166418 - gdm *always* says it's booting, even though the early boot feature is supposed to be disabled
Summary: gdm *always* says it's booting, even though the early boot feature is suppose...
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm (Show other bugs)
(Show other bugs)
Version: rawhide
Hardware: All Linux
medium
low
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-08-20 20:41 UTC by Alexandre Oliva
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-08-25 13:26:29 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Alexandre Oliva 2005-08-20 20:41:24 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8b3) Gecko/20050818 Fedora/1.1-0.2.7.deerpark.alpha2.1 Firefox/1.0+

Description of problem:
The gdm login screen says the system is `booting', even though the changelog of the latest build says this feature is disabled.  It already said the system was booting sometimes, particularly on slow systems, the first time gdm started after a boot, but never after the first login, or a simple gdm restart.  Now, it always says it's booting.

Version-Release number of selected component (if applicable):
gdm-2.8.0.2-1

How reproducible:
Always

Steps to Reproduce:
1.Boot the system up
2.Wait for the gdm screen to come up
3.Ctrl-Alt-Backspace to restart gdm
  

Actual Results:  It says the system is booting up after 2, and even 3

Expected Results:  It shouldn't, especially if the feature is disabled

Additional info:

Comment 1 Ray Strode [halfline] 2005-08-20 23:41:16 UTC
Hi,
I have a fix for this locally, but CVS isn't currently working for me.  It
should be fixed before the weekend is over.


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