On Thursday 11 July 2019 08:56:40 Mike Bird wrote: > On Thu July 11 2019 04:35:31 Slávek Banko wrote: > > 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. > > [2019/07/11 05:09:30.488] [tdecore] Deleting stale > lockfile /tmp/tde-mgb/kdesktop_lock_lockfile.:0.0 > [2019/07/11 05:09:30.489] [tdecore] Deleting stale > lockfile /tmp/tde-mgb/kdesktop_lock_lockfile.:0.1 > [2019/07/11 05:09:30.541] [tdecore] Deleting stale > lockfile /tmp/tde-mgb/kdesktop_lock_lockfile.:0.1 > [2019/07/11 05:09:30.542] [tdecore] Deleting stale > lockfile /tmp/tde-mgb/kdesktop_lock_lockfile.:0.0 > [2019/07/11 05:09:30.544] X Error: BadWindow (invalid Window > parameter) 3 Major opcode: 19 > Minor opcode: 0 > Resource id: 0xc00104 > [2019/07/11 05:09:30.591] [tdecore] Deleting stale > lockfile /tmp/tde-mgb/kdesktop_lock_lockfile.:0.1 > [2019/07/11 05:09:30.591] [tdecore] Deleting stale > lockfile /tmp/tde-mgb/kdesktop_lock_lockfile.:0.0 > [2019/07/11 05:09:30.645] [tdecore] Deleting stale > lockfile /tmp/tde-mgb/kdesktop_lock_lockfile.:0.1 > [2019/07/11 05:09:30.646] [tdecore] Deleting stale > lockfile /tmp/tde-mgb/kdesktop_lock_lockfile.:0.0 > [2019/07/11 05:09:30.648] X Error: BadWindow (invalid Window > parameter) 3 Major opcode: 19 > Minor opcode: 0 > Resource id: 0xc00104 > > 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? > > Here is xrandr -q with the second monitor DISABLED in nvidia-settings > and TDE 14.0.7 PSB working fine on my primary display on DP-2 and the > disabled monitor on HDMI-0. > > Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 > DP-0 disconnected (normal left inverted right x axis y axis) > DP-1 disconnected (normal left inverted right x axis y axis) > HDMI-0 connected (normal left inverted right x axis y axis) > 1600x1200 60.00 + > 1400x1050 74.87 > 1280x1024 85.02 75.02 > 1280x960 85.00 > 1152x864 85.00 > 1024x768 85.00 75.03 70.07 60.00 > 800x600 85.06 75.00 72.19 60.32 56.25 > 640x480 85.01 75.00 72.81 59.94 > DP-2 connected primary 1920x1080+0+0 (normal left inverted right x > axis y axis) 381mm x 214mm > 1920x1080 60.01*+ > DP-3 disconnected (normal left inverted right x axis y axis) > DP-4 disconnected (normal left inverted right x axis y axis) > > Here is the xrandr -q with the second monitor enabled as screen :1 in > nvidia-settings. I had to use Failsafe mode to get this initially but > (see below) after I found I could kill one of the kdesktops and stop > the flashing I got the same randr -q result as in Failsafe mode. > > Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 > DP-0 disconnected (normal left inverted right x axis y axis) > DP-1 disconnected (normal left inverted right x axis y axis) > DP-2 connected primary 1920x1080+0+0 (normal left inverted right x > axis y axis) 381mm x 214mm > 1920x1080 60.01*+ > DP-3 disconnected (normal left inverted right x axis y axis) > DP-4 disconnected (normal left inverted right x axis y axis) > > 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. > > Here is the relevant portion of a Factorio log in the dual monitor > configuration, using a TDE Failsafe login which works fine albeit > it only gives you a root konsole login. Here I have started Factorio > from non-root konsole in Failsafe mode in :0 and told it to run on :1. > > 1.910 Environment: DISPLAY=:0, WAYLAND_DISPLAY=<unset> > 1.927 Display options: [FullScreen: 1] [VSync: 1] [UIScale: system > (100.0%)] > [MultiSampling: OFF] [Screen: 1] [Lang: en] > 1.963 Available display adapters: 2 > 1.963 [0]: resolution 1920x1080px at [0,0] > 1.963 [1]: resolution 1600x1200px at [0,0] > 1.963 Create display on adapter 1. Size 1280x720 at position [150, > 222]. > > You can even start kicker from a non-root konsole in Failsafe and > things mostly work. > > I just discovered that in the two display configuration TDE is running > kdesktop on both screens. If I guess right and kill the unwanted > kdesktop the flashing stops and TDE appears usable. > > tdmrc has the default, unchanged from 14.0.5, including > > StaticServers=:0 > ReserveServers=:1,:2,:3 > > I haven't tried changing this yet. What on earth is an on-demand > (reserve) server? > > --Mike > Buster is using wayland, so not all of the xorg features are present. So its possible that TDE might see problems. > --------------------------------------------------------------------- > 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 Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene> --------------------------------------------------------------------- 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
