Nick Koretsky wrote on 12/11/19 6:15 AM:
> On Fri, 6 Dec 2019 16:30:14 -0700
> "D. R. Evans" <doc.evans@...> wrote:
>
>>>
>>> More info:
>>>
>>> The background doesn't flicker at all. What is flickering are the panel
>>> and the default icons on the desktop, many times a second.
>>>
>>> If I succeed in bringing up the TDE menu (which, if I click enough
>>> times, eventually does appear when I succeed in timing a click at a
>>> moment when the desktop is accepting input), then the flickering stops
>>> for as long as the menu is visible.
>>
>> More info:
>>
>> After a few minutes of I trying to use this (basically unsable :-( ) TDE,
>> it suddenly popped up a dialog that said that the screen was locked and
>> requested that I enter my password. When I did that, I was returned to
>> the session, but the flickering had stopped.
>>
>> So that suggests the question: what causes the screen to lock and the
>> popup requesting unlocking to appear? Somehow that seems to be related to
>> the flickering problem.
>>
>> Doc
>>
>> PS I have no screensaver set.
>>
>
> By any chance, do you have multiple monitors setup via Xorg.conf (not
> randr)? Anyway, rename /opt/trinity/bin/kdesktop_lock to something (like
> add .NO to it), restart pc and see if it helped.
>
I have only one monitor, but the motherboard appears to support two graphics
ports. And even though only one port has anything attached to it, I realised
that I can change a jumper on the motherboard to disable the one that is
unused (it appears to be dedicated in some way to remote administration;
switching the monitor to that port causes an error message to appear on the
monitor, and I couldn't find a way to actually use a monitor on that port). So
I disabled the unused port by moving the hardware jumper and rebooted... and
magically, now there is only one twin process and the flickering has stopped.
So I am tentatively considering that for my system this issue has been worked
around.
I am fairly sure that there is a bug somewhere in TDE, because the problem
should never have occurred -- and, indeed, doesn't occur with KDE. Somehow, it
seems that if there are two graphics ports on the system, even though one has
logged in via sddm with a monitor attached to just one port, two twin process
are started, and they both try to write to the same port.
Anyway, unless it recurs for some reason, I think it's safe now for me to move
on to the next issue :-)
Doc
--
Web: http://enginehousebooks.com/drevans
Attachments: