Bugzilla Bug 47074

After emerging (sync, system, world) I am disapointed that gdm-2.4.4.7 does not
propose me to start a wmaker session anymore... reemerging wmaker and
restarting the box dont solve the problem.

Reproducible: Always
Steps to Reproduce:
1. emerge sync
2. emerge system
3. emerge world
4. etc-update
5. close current wmaker session
6. Failure to restart a wmaker session from gdm
Actual Results:  
I get a new fancy looking gdm loging screen, but wmaker is not proposed as one
of the possible sessions anymore.

I can start wmaker by login into a failsafe session, then running wmaker from
the xterm.

Expected Results:  
gdm shoukd have proposed me to loging using my usual default session: wmaker

I was proposed an explanation on freenode.irc, channel gentoo. Please let me
quote and forgive me for not having a deeper understanding of the bug...:

Quote 1)
"[...]the session setup changed... the maintainers knew about that beforehand
and shouldve updated their ebuilds[...]"

Quote 2)
"[wmaker?...] should install a .desktop for gdm >2.4.4 sessions [...]"

i'm not a windowmaker maintainer

This problem also affects kde-sessions. After upgrading GDM to 2.4.4.7-r1, I
now don't have the option of starting kde-3.2.2.

Same for me. Actually none of my wm is in the list: kde-3.2.2, icewm, fluxbox
and evilwm

yeah this is a gdm ebuild bug.

I get the same thing.  I have no idea where its getting
its session info though, as 2.6 does not seem to be
following the information in the man page.

at any rate... i've had to disable gdm, and go back
to using the command line login.

someone please figure this one out, it's annoying!

Okay with some help from a nice guy named Vorplex on IRC
I know how to fix this one.

gdm 2.6 no longer stores shell scripts in /etc/X11/Sessions,
in fact it no longer uses shell scripts at all.

it uses .desktop files which are stored in /usr/share/xsessions

all I did was copy gnome.desktop to say enlightenment.desktop,
delete all the language crap, and fix the rest to do what it
is supposed to.

works great.

This is very evil.  I'm only using gdm for login and there are no .desktop
files on my system (This is something introduced by kde afaik).  This is ugly -
I want the shell scripts back.  If not I'll just stick with 2.4.1 thank you
very much.  I don't see any other new functionality in 2.4.4 which I need, in
fact, I think the config option is broken as well.

Isn't there simply a config option we can use to get the old behaviour?  I
mean, one don't sommer just drop the one way of doing something entirely on the
spot in favour of another unless there is a very good reason, and I don't see
any reasons at all (other than compatibility with kdm).

I don't use gnome so I cannot help on this...
The short, evil answer is: try qingy as session manager ;-PP

Cf last comment of bug 66055, or last 3 comments of bug 15315, for the kde 
side of things.
Briefly we're going to make kdm well-behaved - install a session .desktop file
in /usr/share/xsessions and read the other files from there.

this appears to be gnome's bug

no, wmaker should install a .desktop file for gdm to pick it up.

(In reply to comment #10)
> no, wmaker should install a .desktop file for gdm to pick it up.

sorry, but why is this desktop-misc? windowmaker is gnustep with maintainer of
fafhrd (which seem to be one and the same), and gdm is gnome, neither of which
is desktop-misc

reassigning to gnustep... i could fix this easily, but i don't want to step on
any toes...

Yeah, gnustep herd is me. :-)

If this is easy for you to fix, feel free to do so.

Should windowmaker have a gdm use flag or something, and if so, it installs the
necessary files?  Or should GDM installs the files (with a windowmaker use flag,
or just if it detects it installed?)

Oddly, it seems that windowmaker installs a file at /etc/X11/Sessions/wmaker --
is this not enough?  Regardless, all the file does is "exec wmaker".

WindowMaker is just a window mananger ... maybe at some point I should create a
"GNUstep environment" entry for gdm, but that's for another day.

FYI for users that "can't use GDM to log into wmaker".

If you create a ~/.xinitrc containing "exec wmaker" on the last line, and `ln -s
~/.xinitrc ~/.xsession`, then, IIRC, GDM's "XSession" entry should launch wmaker
for you.

Just a not too terribly hacky suggestion.

since you said i could, i will go ahead and fix it

since you said i could, i will go ahead and fix it

fixed in 0.91.0-r5

fafhrd: you have _way_ too many ebuilds there imho, but i left them alone
(steping on toes  problem again)... i would suggest a cleanup :-)