Bug 123214 - BlueCurve gdm theme doesn't support Welcome= from /etc/X11/gdm/gdm.conf
BlueCurve gdm theme doesn't support Welcome= from /etc/X11/gdm/gdm.conf
Status: CLOSED DUPLICATE of bug 126747
Product: Fedora
Classification: Fedora
Component: redhat-artwork (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Alexander Larsson
Depends On:
  Show dependency treegraph
Reported: 2004-05-13 17:05 EDT by Valdis Kletnieks
Modified: 2007-11-30 17:10 EST (History)
0 users

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

Attachments (Terms of Use)
Patch for Bluecurve theme "welcome" banner (640 bytes, text/plain)
2004-05-13 17:06 EDT, Valdis Kletnieks
no flags Details

  None (edit)
Description Valdis Kletnieks 2004-05-13 17:05:14 EDT
Description of problem:
The BlueCurve gdm doesn't define a box for the 'Welcome' message from
gdm.conf.  As a result, this doesn't display for sites that use the
Welcome clause to print an authorized use message or similar.

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

How reproducible:
Define a Welcome message in gdm.conf, watch it not show up..

Steps to Reproduce:
1. Edit /etc/X11/gdm/gdm.conf and add a line:

Welcome=This message will not appear on a BlueCurve themed gdm
2. Get gdm to redisplay the screen and see it not show up.
Actual results:
No Welcome message

Expected results:
The defined message should display

Additional info:
Patch attached.
Comment 1 Valdis Kletnieks 2004-05-13 17:06:37 EDT
Created attachment 100222 [details]
Patch for Bluecurve theme "welcome" banner
Comment 2 Miloslav Trmac 2004-06-28 11:34:15 EDT

*** This bug has been marked as a duplicate of 126747 ***
Comment 3 Red Hat Bugzilla 2006-02-21 14:03:13 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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