TDM detects most available window manager and desktop environments when it is run. Installing a new one should make it automatically available in the TDM main dialog Session Type:.
If you have a very new window manager, or something that TDM does
not support, the first thing you should check is that the application to be
run is in the PATH
and has not been renamed during the
install into something unexpected.
If the case is that the application is too new and not yet supported by TDM, you can quite simply add a new session.
The sessions are defined in .desktop files in
$
.
You can simply add an appropriately named TDEDIR
/share/apps/tdm/sessions.desktop
file in this directory. The fields
are:
[Desktop Entry] Encoding=UTF-8 This is fixed toUTF-8
and may be omitted Type=XSession This is fixed toXSession
and may be omitted Exec=executable name
Passed to eval exec in a Bourne shell TryExec=executable name
Supported but not required Name=name to show in the TDM session list
There are also three “magic”:
The default session for TDM is normally TDE but can be configured by the system administrator.
The Custom session will run the users ~/.xsession if it exists.
Failsafe will run a very plain session, and is useful only for debugging purposes.
To override a session type, copy the .desktop file from the data dir to the config dir and edit it at will. Removing the shipped session types can be accomplished by “shadowing” them with .desktop files containing Hidden=true. For the magic session types no .desktop files exist by default, but TDM pretends they would, so you can override them like any other type. I guess you already know how to add a new session type by now. ;-)
Would you like to comment or contribute an update to this page?
Send feedback to the TDE Development Team