 @Wolfenprey, Nope, I just needed to manually run the script.
[07:56] -lugito:#lubuntu-devel- [rBLOGbf9084263cb8: typos in newsletter 10.] Wolfenprey (Tony Cuesta Escobar) committed: https://phab.lubuntu.me/rBLOGbf9084263cb8
 cough  https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1788797
 But why doesn't SDDM have the support? :P
 @tsimonq2, Why was it assumed it did when making that "fix"?
 Because we assumed it had been. :P
 broken/wrong assummptions = bugs
[15:47] <lubot5> <Hans Möller> @wxl my script works now for stretched wallpapers (2 displays environment only). I need to figure out how to do it with fit, centered and zoom. We were thinking in running cron jobs to trigger this script in case the wallpaper was changed, but also need to adress if another monitor has been connected.
[16:59] <wxl> @Hans your cron job should watch for changes to the wallpaper and xrandr for monitor info. should be pretty simple
[17:00] <wxl> @Hans maybe something like `xrandr | grep ' connected ' should be simple enough
[17:02] <wxl> @Hans that should actually give you everything you want since it tells you which is where
[17:02] <wxl> e.g. 
[17:02] <wxl> DVI-0 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 518mm x 320mm
[17:02] <wxl> DVI-1 connected 1920x1080+0+36 (normal left inverted right x axis y axis) 531mm x 299mm
[17:03] <wxl> in this case you can see DVI-1 is 36 pixels lower, and is on the left side
[17:09] <lubot5> <Hans Möller> ok, I'm doing xrandr | grep already.
[17:14] <lubot5> <Hans Möller> to get the screen dimensions.
[19:27] <lubot5> <Hans Möller> Which program will manage the "additional drivers"  in lxqt?
[20:52] <lubot5> <Hans Möller> @Hans Möller, I just wanted to avoid xrandr, since it takes some time in some machines.
[20:57] <wxl> @Hans i'm not sure if there's another way to do it, but you might check related man pages to xrandr and see if you come up with anything
[21:38] <lubot5> <Hans Möller> ok
[21:40] <lubot5> <Hans Möller> I have 2 question, regarding cosmic in general. 1) Where will be "additional drivers" wheren yo can chose nvidia over nouveau and other drivers in lxqt?
[21:40] <lubot5> 2) Are the repositories for cosmic ok? I have problemas with wine
[21:41] <wxl> well i can tell you that the goal is that the repositories should be good by the time it's released
[21:41] <wxl> meanwhile it might all be messed up :)
[21:42] <wxl> let me figure out the answer to the other question
[21:47] <wxl> right off the bat it seems that `ubuntu-drivers` can do the trick
[21:50] <wxl> ah software-properties-qt is actuallyt he right thing. you can get to it from muon i believe
[21:54] <wxl> seems like it's just sitting and spinning for me though
[21:54] <wxl> let me get a new iso
[21:54] <wxl> i haven't updated in a bit
[22:49] <wxl> @tsimonq2: it seems that opening software sources in muon fails to do anything
[23:00] <lubot5> <Hans Möller> software-properties-qt doesn't appear in the menu, and I can't see an additional driver tab. Only: Ubuntu software, Other software, Actualizaction, Autenticacion, statistics (names mught be different I have it in spanish).
 software-properties-kde/qt never did have the drivers tab IIRC
[23:50] <wxl> @acheronuk: what does k use?
 Same thing.
 The driver functionality is there iirc, just not in its own tab
[23:51] <wxl> huuuuuuh
 kubuntu-driver-manager
 can be launched standalone, or used in KCM in systemsettings
[23:53] <wxl> i guess "proprietary drivers for devices (restricted)" is the right repo
[23:53] <wxl> so there's not a separate thing to run
[23:53] <wxl> which is nicer, honestly
[23:54] <wxl> well
[23:54] <wxl> no
[23:54] <wxl> because you don't know what drivers are relevant
[23:57] <wxl> looks like we need to get our own tool for that :(