On Fri, 12 Jul 2019 01:18:28 -0700 Mike Bird mgb-trinity@yosemite.net wrote:
OK, for comparison purposes I'm back to 14.0.5 and Stretch. (Something of a struggle as Tim's server became inaccessible again during the downgrade.)
Dual display with first for Trinity and second was intended to be non-TDE as before but TDE won't cooperate on that. However 14.0.5 works without flashing or crashing. The unlock screen dialog pops up two or three or four times after login but things eventually settle down.
Instead of the two lock files in 14.0.7 PSB there is a single lock file in 14.0.5: /tmp/tde-mgb/kdesktop_lock_lockfile
However TDE 14.0.5 is running a second desktop on the second display. Before upgrading to 14.0.7 and rolling back to 14.0.5 the systray randr would allow me to specify which display was primary and which display(s) TDE could or could not use. But now systray randr only shows one screen and doesn't enable those options, despite TDE actually using two displays.
xrandr gives different results in each screen which don't list the other screen. And I can't get kicker to appear in the second display although it says that two instances are running and won't start another.
Behind the scenes, some weirdness is going on:
# ps ax | grep kde 70 ? S 0:00 [kdevtmpfs] 8135 ? SL 0:08 kded [tdeinit] --new-startup 8187 ? Sl 0:01 /opt/trinity/bin/kdesktop 8188 ? Sl 0:00 /opt/trinity/bin/kdesktop 8191 ? S 0:00 /opt/trinity/bin/kdesktop_lock --internal 8188 8193 ? S 0:00 /opt/trinity/bin/kdesktop_lock --internal 8188 8201 ? S 0:00 /opt/trinity/bin/kdesktop_lock --internal 8187 8495 ? S 0:00 /opt/trinity/bin/kdesktop_lock --internal 8187 8536 ? S 0:00 /opt/trinity/bin/kdesktop_lock --internal 8187 8562 ? S 0:00 /opt/trinity/bin/kdesktop_lock --internal 8187 8581 ? S 0:00 /opt/trinity/bin/kdesktop_lock --internal 8187 8582 ? Z 0:00 [kdesktop_lock] <defunct> 12492 pts/3 S+ 0:00 grep kde
Has anyone had success with multiple displays in 14.0.7? Preferably with TDE on one display and the second as an X display unused by TDE?
Yeah, this is exactly the behavior i have reported years ago, and the only way to avoid it is remove the kdesktop_lockn executable (this doesnt not cause any problems except inability to lock obviously, and inability to shutdown directly from TDE session).
Now, about how it worked for you before....
But now systray randr only shows one screen and doesn't enable those options, despite TDE actually using two displays.
Randr not showing other monitor is a correct behavior in case of two X screens, so if it does showed them before you had X configured differently - both monitors were on a single X screen and this bug didnt trigger.