Bug 130267 - Fedora-gdm does not recognize the Files in /etc/X11/gdm/Sessions/
Summary: Fedora-gdm does not recognize the Files in /etc/X11/gdm/Sessions/
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm   
(Show other bugs)
Version: 2
Hardware: athlon
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2004-08-18 16:27 UTC by Hanno
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-11-05 23:58:59 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Hanno 2004-08-18 16:27:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
I have installed fvwm2
I have created /etc/X11/gdm/Sessions/FVWM2

-----Begin FVWM2-----
exec /usr/local/bin/fvwm2
-----End FVWM2-----

The new FVWM-Windowmanager can not be choosen at the gdm-Loginscreen.
Only the Gnome-Windowmanager and the Failsafe-Terminal is displayed
during the Choosing-Dialog.
When I start the Gnome-Windowmanager and log-out later, the Monitor
becomes black and the Computer dos not react to Keystrokes.
When I erase /etc/X11/gdm/Sessions/FVWM2, gdm works well.

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

How reproducible:

Steps to Reproduce:
1. install fvwm2
2. creat /etc/X11/gdm/Sessions/FVWM2

  -----Begin FVWM2-----
  exec /usr/local/bin/fvwm2
  -----End FVWM2-----
3.  Try to choose the FVWM. It is not diplayed in the Coosing-Dialog.


Actual Results:  FVWM2 is not diplayed in the Coosing Dialog at the

Expected Results:  The Point FVWM2 should have been displayed, so that
I can choose this Point an then login with the fvwm-Windowmanager.

Additional info:

Comment 1 Hanno 2004-08-19 12:25:03 UTC
The Computer-Crash after logging out has nothing to do with the gdm.
If I change /etc/sysconfig/desktop

-----Begin original File-----
-----End original File-----

-----Begin new File-----
-----End new File-----
(Yes, the real Variablename is DISPLAYMANAGER !. DESKTOP IS WRONG

the kdm (KDE Display Manager) starts and the Computer crashes after
logging out as well.

So the Problem that is left as far as gdm ist concerned, is, that gdm
does not recognize the (executable) Files in the
/etc/X11/gdm/Sessions/ Directory.

Hanno (u13927@gmx.de)

Comment 2 Hanno 2004-08-19 13:00:09 UTC
DESKTOP is not so wrong as I said.
It is used by th Script in

Hanno (u13927@gmx.de)

Comment 3 Hanno 2004-08-19 14:34:52 UTC
I have just found out, that when I create a File
similar to
/etc/X11/dm/Sessions/gnome.desktop (that allready exists from the
rpm-Gnome-Package), I get the Point FVWM2 in the gdm-Session-Menue.

I have installed the original Fedora2-KDE-Package and there is no
/etc/X11/dm/Sessions/kde.desktop. There is only a
Strangely the Point KDE appears in the gdm-Session-Menue. 
So there must be 2 different Ways to let the Menuepoints appear in the

I think, that there schould only be 1 right Way (how it is described
in the gdm-Dokumentation), to "edit" the gdm-Session-Menue.
I think, it is not good, that Fedora "invents" new Things, that differ
from the original gdm-Documentation. It is difficult enough to read
the original gdm-Documentation. I do not have the Time to learn
special Fedorathings.
Hanno (u13927@gmx.de)

P.S. It is the first Time, that I have written Something into the
Errata. It would be helpful, if I could edit my previous Writings,
because there are a lot of Errors from my Side in there. I could so
save the Readers a lot of Time reading senseless Words and the
following Corrections.

Comment 4 Ray Strode [halfline] 2004-11-05 23:58:59 UTC
Hi Hanno,

The second method you found is a new standardized way of adding items
to the session menu (that works with display managers other than GDM).
It is not in anyway Fedora specific. You were probably having problems
using the original method because you may have forgotton to put
execute permissions on your file.

Hope that helps.

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