Anno domini 2019 Sat, 7 Dec 19:53:11 -0700 D. R. Evans scripsit: > E. Liddell wrote on 12/7/19 3:48 PM: > > On Fri, 6 Dec 2019 19:27:14 -0700 > > "D. R. Evans" <doc.evans@xxxxxxxxx> wrote: > > > >> Dr. Nikolaus Klepp wrote on 12/6/19 4:34 PM: > >>> Anno domini 2019 Fri, 6 Dec 16:30:14 -0700 > >>> D. R. Evans scripsit: > >>>> D. R. Evans wrote on 12/6/19 2:30 PM: > >>>>> D. R. Evans wrote on 12/6/19 10:54 AM: > >>>>>> I just installed TDE on a new-to-me system running debian stable (buster). > >>>>>> > >>>>>> All the initial system installation was done from a live CD, and it installed > >>>>>> KDE. That installed version of KDE works as well as KDE ever works these days. > >>>>>> In particular, though, the screen looks fine (1920x1200) and everything works > >>>>>> as expected. > >>>>>> > >>>>>> In the newly-installed TDE, though, the desktop flickers wildly and the > >>>>>> desktop is simply unusable: input is lost during the flickers, so most > >>>>>> keyboard/mouse input is not even seen by the desktop. > >>>>>> > >>>>>> Where should I look to try to eliminate all the flickering so that I can get a > >>>>>> usable TDE? > >>>>>> > >>>>> > >>>>> 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. > >>>> > >>> > >>> can you run "top"or "htop" on a console (e.g.: <ctrl>+<alt>+<f1>)? > >>> > >> > >> ---- > >> > >> top -b -n 1 produces (while the flickering is occurring): > >> > > [...] > >> 2808 n7dr 20 0 2388 568 496 S 0.0 0.0 0:00.00 sh > >> 2809 n7dr 20 0 2280 536 476 S 0.0 0.0 0:00.00 kwrapper > >> 2811 n7dr 20 0 78568 20840 13980 S 0.0 0.1 0:00.86 ksmserver > >> 2812 n7dr 20 0 82308 20724 15088 S 0.0 0.1 0:01.61 twin > >> 2813 n7dr 20 0 82936 21308 15020 S 0.0 0.1 0:01.56 twin > >> 2817 n7dr 20 0 157600 24272 18656 S 0.0 0.1 0:18.82 kdesktop > >> 2829 n7dr 20 0 90824 26532 18252 S 0.0 0.1 0:01.68 kicker > >> 2830 n7dr 20 0 90808 26532 18288 S 0.0 0.1 0:02.87 kicker > >> 2832 n7dr 20 0 70840 10676 7480 S 0.0 0.0 0:00.00 tdeio_file > >> 2837 n7dr 20 0 70840 10720 7524 S 0.0 0.0 0:00.00 tdeio_file > >> 2839 n7dr 20 0 70840 10720 7524 S 0.0 0.0 0:00.00 tdeio_file > > [...] > > > > The doubled-up instances of kicker and twin jump out at me as a possible conflict. > > > > OK; so do you have any idea what spawns the twin and kicker processes? I'm > floundering here (as is so often the case). Since this happens immediately I > log in, I'm not starting anything manually. Most likely systemd. > > Doc > -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
