Message: previous - next
Month: May 2017

Re: [trinity-users] Trinity and multiple screens (in X sense)

From: Nick Koretsky <nick_koretsky@...>
Date: Thu, 11 May 2017 07:31:57 +0300
On Thu, 11 May 2017 02:03:51 +0300
Nick Koretsky <nick_koretsky@...> wrote:

> Hi!
> I decided to connect my TV as second monitor and am trying different
> configurations. First i tried a "normal" xrandr approach and didnt liked
> the result - no negative coordinates (0x0 is always a left most screen -
> so i would have to learn to switch to left screen by moving mouse to the
> right if i want my TV located physically to the left act as an secondary
> monitor) and virtual desktops switching on both monitors (afaik trinity
> have no support for separate virtual desktops in different monitors? i
> hope i am wrong but doesnt looks so :( ). So i wanted to try a multiple
> screens (in X sense) approach but hit a roadblock. As soon as i add 
> Screen  1       "Philips" LeftOf "ZR24w"
> line to my xorg.conf and do tdm-trinity restart i am greeted with "this
> computer is locked enter password to unlock" on a TV and there is no
> escape from it other than killing X. Entering password just make it blink
> for a second and return back.
> Can this be somehow avoided or trinity is incapable of working on multiple
> screens?

A little more info from some experimentation.
I get the same "session locked" if i start a second x session via startx
manually, but this time it can be unlocked. And i am presented with
this "session locked" every time i switch between sessions. So i believe
what is happening is that when i try to run multiple screens config is that
it tries to lock my "inactive" screen constantly.
So the real question is how to disable automatic locking of inactive X
session? I looked in TDE Control Center but didnt found anything.

P.S. Reading logs - everything is the same as normal in all of them except
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 113 requests (113 known processed) with 5 events remaining.
at the end of tdm.log

  Nick Koretsky (nick.koretsky@...)