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 82968 - gdm shutdown option does not always shutdown
gdm shutdown option does not always shutdown
Product: Red Hat Linux
Classification: Retired
Component: gdm (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Havoc Pennington
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-01-28 22:08 EST by Kevin Range
Modified: 2007-04-18 12:50 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-18 13:00:45 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
gdm config file (2.72 KB, text/plain)
2003-01-28 22:09 EST, Kevin Range
no flags Details

  None (edit)
Description Kevin Range 2003-01-28 22:08:13 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
Apparently under ceratin configurations the gdm System->Halt option does not
work cleanly.

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

How reproducible:

Steps to Reproduce:
1.Enable a second screen on vt8 in gdm.conf
2.Try to power-off with System->Shutdown
4.Ctrl-Alt-F[0-7] once or twice and the things will work

Actual Results:  Step 4 is apparently required beofre shutdown, which seems

Expected Results:  Power-off

Additional info:
Comment 1 Kevin Range 2003-01-28 22:09:29 EST
Created attachment 89673 [details]
gdm config file

This is probably overkill, but here is my gdm.conf file.
Comment 2 Havoc Pennington 2003-02-03 15:09:00 EST
I would guess this is fixed in 8.0
Comment 3 Kevin Range 2003-02-03 16:00:03 EST
I guess I will just have to check it out when I upgrade to 8.x in a couple of
Comment 4 Havoc Pennington 2003-02-18 13:00:45 EST
Confirmed to work in latest

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