On 08/29/2015 06:42 PM, Slávek Banko wrote: > On Wednesday 26 of August 2015 04:49:04 David C. Rankin wrote: >> >Tim, Slavek, Darrell, All, (whoever is left?) >> > >> > I've checked from time to time to see if >> >http://bugs.pearsoncomputing.net/show_bug.cgi?id=1998 has been resolved to >> >crank up my Arch build system again. When we left, the problem was TDE did >> >not provide user session tracking or a multi-seat implementation for a >> >pure-systemd environment (without ConsoleKit). > TDE provides basic support for systemd - from TDM through kdesktop to > tdepowersave. What is not yet implemented, is support for multi-seat. > > By Darrell is also a proposal to add support into k3b - inhibitor for > suspend / shutdown during recording media (bug 2389). > >> > >> > This resulted in applications being launched, but never terminated after >> >they had been closed by the user. > In this I have again and again oppose. It has already been repeatedly shown > that failure in closing the processes had a different cause and no connection > with systemd. See bug 1902. > Thanks, yes, I know. In all the related bugs we went through the discussion of it not being related to systemd, etc... But whatever the reason, without ConsoleKit, virtually kdeioslave apps and others would never be closed. I guess I'll just have to pull the latest and give it a shot >> > >> > Can anyone confirm correct behavior of TDE in a pure-systemd setting w/o >> >ConsoleKit? Even without multi-seat, it is worth building TDE if the issue >> >described in bug 1998 has been resolved. >> > >> > What says the brain trust? > Systemd is currently used on Debian 8.x (Jessie) and Ubuntu 15.04 (Vivid). I > also do tests on Ubuntu 14.04 (Trusty) with added systemd. For Ubuntu is also > created systemd service for TDM: > > http://git.trinitydesktop.org/cgit/tde-packaging/tree/ubuntu/maverick/tdebase/debian/tdm-trinity.service Michele, Slavek That is all good news. I pull a fresh checkout and build and test. The only thing I need to know is: (1) are there any alternative version distinctions that remain in the git repository (i.e. like the old 14 v. 3.5.13_SRU)? (2) have there been any significant changes to the build process that need to be addressed on my end before I kick-off a build? (I expect changes that will need fixes, but as far as the normal approach and build-order, is that still the same?) I loaded suse 13.1 a year or so ago when I got busy and have just use Ilya and Serghei's packaging for suse sense (suse still included ConsoleKit w/13.1) I haven't tried, but ConsoleKit (ConsoleKit-0.4.6-4.1.4.x86_64.rpm) is still part of the 13.2 release. If you all are running tde on systemd without any ConsoleKit or other wrapper to launch TDE and are having all your apps tdeioslave apps closed, that's great. A pure systemd launch of tdm would be via a systemd tdm.service file such as: [Unit] Description=TDE Display Manager After=systemd-user-sessions.service [Service] ExecStart=/opt/trinity/bin/tdm [Install] Alias=display-manager.service Could those who are running tde on a systemd based system w/o ConsoleKit check how you are launching tde/tdm and let me know. That I believe is one of the critical components. If you are using anything other than systemd to launch tdm from a service file similar to the foregoing, I need to know what you are using. Thanks. -- David C. Rankin, J.D.,P.E.