11 Jul
2019
11 Jul
'19
3:33 p.m.
On Thu, 11 Jul 2019 05:56:40 -0700
Mike Bird <mgb-trinity(a)yosemite.net> wrote:
On Thu July 11 2019 04:35:31 Slávek Banko wrote:
Does your two monitor setup as a separated X screens ?
If so your are probably running into this
http://bugs.pearsoncomputing.net/show_bug.cgi?id=2775
--
Nick Koretsky (nick.koretsky(a)gmail.com)
do I understand correctly that
"flashes" in the sense of an XServer
crash?
I don't think XServer is crashing as the .xsession-errors shows errors but
not a restart and Xorg.0.log shows no errors or restart.
My guess is that TDE is encountering serious errors that disrupt TDE
operation but that do not cause X to crash.
Are there any information listed in the XOrg log?
Lots of X startup info but no errors in Xorg.0.log. However
.xsession-errors mostly consists of high-speed repeats of this approx
ten times per second. Sometimes there are a lot more stale lockfile
messages and sometimes a different resource id appears but it's mostly
like this.
There is none of the above when the second display is disabled and TDE
is working fine.
If you try "xrandr -q" from Konsole,
will it print both monitors?
Note that there is no sign of the second display even though TDE is
throwing up a blue background and occasional screen unlock dialogs
on the second display. The second display should be in screen :1
and not used by TDE in :0.
The "screen is locked" dialogs appear randomly on one screen or the
other every half minute or so - much earlier than they should appear.
The flashing stops while the screen unlock dialog is present so I can
type my password and return to the flashing.