On Wednesday 10 of May 2017 02:24:20 Felix Miata wrote: > Slávek Banko composed on 2017-05-10 01:28 (UTC+0100): > > I think there may be one more problem - a service for systemd is > > called 'tdm', while 'classical' init script is called 'tdm-trinity'. > > I think in your case tdm can be run by a classical init script. This > > would correspond to the fact that tdm service is 'inactive'. > > > > Maybe it's time to rename 'classical' init script to 'tdm' instead of > > the current 'tdm-trinity'. Thanks to the earlier renaming of 'kdm' => > > 'tdm', there is no longer any conflict if the init script is to be > > briefly named 'tdm'. It is only necessary to test whether this will > > help :) > > I renamed /etc/init.d/tdm-trinity /etc/init.d/tdm, then rebooted > several times. This has resulted in expected behavior whether or not 3 > or 5 or neither is included on kernel cmdline, and whether > graphical.target or multi-user.target is set to systemd default. Now > startx can open a TDE session on :0 instead of :1 in Stretch just like > in Fedora and openSUSE! :-D Thanks for performing the test - renaming was done in tde-packaging git in commit 70d1e404 (master) and 5fc04fc9 (r14.0.x). Updated packages are already available in Preliminary Stable Builds repository. Cheers -- Slávek --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-devel-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
