Re: GDM update!

[Timothy Sample]

Hi Ludo,

Ludovic Courtès <address@hidden> writes:

> Hello!
>
> Timothy Sample <address@hidden> skribis:
>
>> Maybe the GDM folks expect that we write a custom “.desktop” file that
>> runs a custom script that checks for “~/.xsession” and runs it.  It
>> could use “TryExec” to figure out if “~/.xsession” exists, and offer it
>> to the user (in the session selector) in that case.  To be concrete, we
>> would create a “user.desktop” session file with the following contents.
>>
>>     [Desktop Entry]
>>     Name=User Session
>>     Comment=Start a user-defined session
>>     Exec=run-user-xsession
>>     TryExec=xsession-exists-p
>>     Icon=
>>     Type=Application
>>
>> Here, “run-user-xsession” and “xsession-exists-p” are custom scripts
>> that we would write.  If this file were somewhere that GDM knows about
>> (e.g., “/run/current-system/profile/share/xsessions”), it should work.
>
> We could do that, or should we just arrange for GDM to honor .xsession
> when it exists just like we do for SLiM?
>
> Specifically I’m thinking of the ‘xinitrd’ procedure in (gnu services
> xorg) and how we pass it to SLiM via ‘slim.cfg’.
>
> WDYT?

Do you mean that we should not use the GDM-provided “Xsession” script
and tell GDM to run an “xinitrc” script generated by the “xinitrc”
procedure?  This would work.  In fact, the way that our “xinitrc” (by
default) looks for session files in user profiles is a major
improvement.  Indeed, it makes more sense to replace the script entirely
than to try and carefully construct everything so that it does what we
want.  This is especially true considering that upstream expects distros
to replace the script anyway.

We will have to pass the script in as a variable.  I will do this on top
of my changes (which I hope to send in today).


-- Tim