do I understand correctly that "flashes" in the sense of an XServer crash?

Are there any information listed in the XOrg log?

If you try "xrandr -q" from Konsole, will it print both monitors?

if there are two kdesktop processes running, each will run a kdesktop_lock process and the two processes will use the same lock file on the disk. The "delete stale file" logs that you see are consistent with that. You need to try to understand why two kdesktop processes are started together.

On Thu July 11 2019 04:35:31 Slávek Banko wrote: 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. 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. 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.

On Thu July 11 2019 04:35:31 Slávek Banko wrote: 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. 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. 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

--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net 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

I have a TDE 14.0.7 with two screens on Debian Wheezy and Debian Stretch.

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.

Sorry, maybe I missed a point, but are you sure Xorg is installed and wayland purged?

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.)

You're right of course but I'm hoping SB can find time to try an empty config on his Stretch 14.0.7 as I don't have a dual monitor test box so I have to downgrade my live laptop which is rather painful.

Is there any switch or other way to get more logging info out of TDE without recompiling?

I've been waiting for you to provide a config supposed to produce your desire, but if you did, I missed it.

Also I don't know what PSB means.

If you will provide the config that worked in 14.0.5, I will try to reproduce here on a PC. Most of mine have Buster with dual or triple head graphics by Intel, ATI or NVidia, plus openSUSE, and some have Fedora or Mageia or Kubuntu, multiboot all, pure FOSS all except for some printer drivers. I've only ever used multihead to expand a single desktop. All my Busters have TDE and IceWM only.

If convenient it would be helpful if you could determine whether two separate non-xinerama X screens and an empty ~/.trinity/share/config works for you in Buster 14.0.7.