Slávek Banko wrote:

On Wednesday 06 of June 2018 23:56:16 mgb-trinity@yosemite.net wrote:

...

Upgraded from Jessie + TDE Stable to Stretch + TDE PSB. Upgraded cleanly. On first attempt TDE ran some kind of XDG compliance enforcer.

TDM starts and I can log in. TDE spends half a minute or so saying "starting desktop" in the usual way but then I'm left with nothing but the cursr and a blue background.

The only anomaly I've found thus far in the logs is (IIRC) an ASSERT of "primary_set" from randr.

Any suggestions, tips, or hints would be welcome. Difficult to answer questions as without KMail it is taking me several attempts to type perfect headers into telnet that the list software will accept.

I have recent backup as a last resort but am hoping for a way forward.

Thanks,

--Mike

Hi Mike,

is something interesting stated in ~/.xsession-errors?

Cheers

Yes exactly. I had same experience and after looking in ~/.xsession-errors it was doing update (internal). I think perhaps a message should be displayed, so that use does not get nervous that nothing is happening.

After waiting for a while, in my case, it completed the update and continued normally, but it took perhaps 2-3 minutes.

regards

On Wed June 6 2018 20:30:13 Mike Bird wrote:

Not sure yet whether this was my mistake or a bug in some package.

TLDR: Not a TDE problem.

This system has an old Nvidia card. The installation is multiarch. When upgrading from Jessie to Stretch the primary arch was converted from nvidia (current) to nvidia-legacy but I forgot to convert a foreign arch to match. This confused the glx-diversions mechanism resulting in the omission of one of the five layers of symlinks for libGL.so.1 for the primary arch. Upon switching the foreign arch to nvidia-legacy the missing primary arch symlink was created.

--Mike