|00:14||book` has joined IRC (firstname.lastname@example.org)|
|01:14||mmarconm has joined IRC (mmarconm!~mmarconm@unaffiliated/mmarconm)|
|02:04||mmarconm has left IRC (mmarconm!~mmarconm@unaffiliated/mmarconm, Quit: Leaving)|
|02:05||oh207 has joined IRC (email@example.com)|
|02:45||thefinn93 has joined IRC (thefinn93!finn@unaffiliated/thefinn93)|
|05:02||statler has joined IRC (statler!~Georg@p54897B60.dip0.t-ipconnect.de)|
|05:37||woernie has joined IRC (woernie!~werner@p5DDECF51.dip0.t-ipconnect.de)|
|06:15||RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro)|
|06:18||statler has left IRC (statler!~Georg@p54897B60.dip0.t-ipconnect.de, Quit: cu @ll)|
|06:42||woernie has left IRC (woernie!~werner@p5DDECF51.dip0.t-ipconnect.de, Ping timeout: 265 seconds)|
|06:43||woernie has joined IRC (firstname.lastname@example.org)|
|07:40||xiphias256 has joined IRC (email@example.com)|
Hi! I have an old ltsp instance that is about to be upgraded. Is XRANDR_COMMAND_[0..9] supported in /etc/ltsp.conf as it was in lts.conf. It is not mentioned in the man page. If not how can I use xrandr commands on different clients?
xiphias256: display managers do not all support hooks to run xrandr commands. You're supposed to use a xorg.conf, when that is necessary
ltsp.conf: Configuration file for LTSP: https://ltsp.org/man/ltsp.conf/
There are instructions there to dynamically create xorg.conf as neeed
Initializing xorg and running xrandr commands afterwards was a hack anyway; it's best to initialize xorg at the target settings at once, not afterwards
Otherwise the dpi get wrong, the max panning size etc
Finally, xrandr won't work at all with wayland
Ok, I used it to define primary screen and to say which screen was left/right. Autodetect didnt work as intented.
xiphias256: sure, a xorg.conf can easily do that
The benefit of xorg.conf vs custom xorg commands, is that it's already documented elsewhere, and that it works without ltsp as well
So you can use the same knowledge in managing ltsp vs non-ltsp labs
I rather stick with defaults (wayland)
Sure, that one is documented too, and will work fine with the new ltsp, while it wouldn't work with the old one
LDM didn't support wayland at all
Yeah, it's great that this new ltsp version is released and that LDM is gone! :) Hmm.. where is wayland config documented?
In upstream wayland :)
That's the good thing, that it's no longer ltsp specific at all
xiphias256: which distro/version are you using?
Ahh...makes sense! Thanks :)
I have been burned to many times with Ubuntu. Dist-upgrade is a mess.
Eh, each one has its benefits. As long as it's deb, I'm fine; I hate snaps :)
|08:00||woernie_ has joined IRC (firstname.lastname@example.org)|
|08:00||woernie has left IRC (email@example.com, Ping timeout: 272 seconds)|
Agree deb is the way to go :)
Btw wayland display settings seem sooooo immature compared to xorg...
They seem to be mostly handled by the compositor, so one would need different instructions based on if he uses kde, gnome, sway, whatever...
|08:06||* alkisg is glad that ltsp doesn't need to worry about all that :D|
Tearing is nearly gone in Wayland / sway for me which is cool, but my chrome sometimes becomes painfully slow to scroll
I think xpresent had made tearing go away in xorg too. Sure a protocol rewrite was needed, but not enough resources were put into it...
Hmm..I will give it a try and see how it goes. I upgraded another ltsp instance recently from debian8 -> Debian10. It worked great. But this was a simpler 1-screen solution
Google says that sway has a "swap monitors" setting, which would do what you want even in wayland
Crap... "SWAY is not included in any of the official Debian installers and is not available in the main stable (Buster) repositories."
I think "gnome display settings" can also do it, from the GUI
Eh you can probably install it from bullseye
|11:09||oh207 has left IRC (firstname.lastname@example.org, Ping timeout: 260 seconds)|
|12:11||xiphias256 has left IRC (email@example.com, Remote host closed the connection)|
|13:10||test has joined IRC (firstname.lastname@example.org)|
|13:10||test is now known as Guest3329|
|13:11||Guest3329 has left IRC (Guest3329email@example.com)|
|14:37||woernie_ has left IRC (firstname.lastname@example.org, Ping timeout: 272 seconds)|
|18:09||RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.)|
|18:44||bcg has left IRC (email@example.com, Quit: bcg)|
|18:45||bcg has joined IRC (firstname.lastname@example.org)|
|18:48||bcg has left IRC (email@example.com, Client Quit)|
|18:49||bcg has joined IRC (firstname.lastname@example.org)|
|23:02||adrianorg has left IRC (email@example.com, Ping timeout: 260 seconds)|
|23:03||adrianorg has joined IRC (firstname.lastname@example.org)|
|23:07||adrianorg has left IRC (email@example.com, Ping timeout: 256 seconds)|
|23:10||thefinn93 has left IRC (thefinn93!finn@unaffiliated/thefinn93)|
|23:10||thefinn93 has joined IRC (thefinn93!finn@unaffiliated/thefinn93)|
|23:33||adrianorg has joined IRC (firstname.lastname@example.org)|