My bias is anti systemd, just so you know.-- scant documentation and there has never been a security review of its package.

I had a lot of weird issues running Jessie 8.5 and Trinity--it became a very unstable system.  There was no proof (nor was there enough systemd documentation that would let you troubleshoot the issues) but a few clues led me to believe that systemd was involved somehow, in some of my issues.  

I switched to Devuan (Debian Jessie without systemd) a couple of months ago, and a lot of the problems went away...  Devuan just released their Release Canidate 1.0 in the last week or so... so I decided to do a bare metal install of Devuan and Trinity..  

There were a few problems with installing the pair, but nothing serious.   First problem was that the Deuvan Live Install didn't like my UEFI bios and after I attempted  to install grub2's UEFI version using the Live distro.  I then had to manually remove the version of grub2 that it installed, using apt from the console and a grub2 USB rescue stick.  

The second issue was that I used a live USB stick to install Devuan and it put that info in /etc/sources.list as a CD install and when Trinity wanted to install stuff from the ppa it demanded the "distro CD" be mounted and would not pay any attention to my USB stick.  I edited sources.list using nano and commented out  the reference to the CD listing and then everything worked.

So if you can't get your problem solved and or you start having more problems, you might consider installing Devuan.  It can upgrade Debian Jessie in place and that feature worked fine the first time I installed Devuan.  It took about 15 minutes to do the upgrade and kept all of my configurations.  I made a clone of my system (Clonezilla) before I upgraded and I suggest you do too...

Keith



On Sat, Apr 29, 2017 at 2:41 AM, Felix Miata <mrmazda@earthlink.net> wrote:
TDM according to ps -A is "running" when init completes even though multi-user
is default target, and regardless whether 3 or 5 or neither is included on
cmdline. Killall tdm then startx does produce a TDE session, but there's no
.xsession-errors.

There doesn't seem to be any kind of clues I can decipher in any logs:

http://fm.no-ip.com/Tmp/Linux/Xorg/tdm.log-fi965-stretch
http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-fi965-stretch
ii  tdm-trinity  4:14.0.5~pre14-0debian9.0.0+2~a amd64
# inxi -c0 -v1
System:    Host: fi965 Kernel: 4.9.0-2-amd64 x86_64 (64 bit) Desktop: N/A
           Distro: Debian GNU/Linux 9 (stretch)
CPU:       Dual core Intel Core2 6700 (-MCP-) speed: 2668 MHz (max)
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Cedar [Radeon HD
5000/6000/7350/8350 Series]
           Display Server: X.org 1.19.2 drivers: modesetting (unloaded: fbdev,vesa)
           tty size: 111x36 Advanced Data: N/A for root
# systemctl status tdm
â tdm.service - Trinity Display Manager
   Loaded: loaded (/lib/systemd/system/tdm.service; static; vendor preset: enabled)
   Active: inactive (dead)
     Docs: man:tdm-trinity(1)

Is ignoring the default target normal or expected on Debian running systemd?
Searching BZ for comment including systemd and target produced no hits except
for an Ubuntu crasher. Is there some way to get TDM to not start automatically
on Stretch boot?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net
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