[06:19] <oSoMoN> good morning desktoppers, happy Monday!
[06:24] <didrocks> good morning
[06:25] <oSoMoN> salut didrocks
[06:26] <oSoMoN> bon week-end?
[06:26] <didrocks> salut oSoMoN, bon week-end, et toi ?
[06:29] <oSoMoN> très bon, j’ai passé tout le week-end dehors à prendre l’air et le soleil, ça fait du bien :)
[06:30] <didrocks> super :)
[07:25] <marcustomlinson> morning oSoMoN and didrocks, good weekend?
[07:26] <didrocks> hey marcustomlinson, good, yourself?
[07:27] <marcustomlinson> didrocks: yeah so so. Wife's sick so lots of babysitting
[07:27] <didrocks> not so relaxing thus :(
[07:28] <marcustomlinson> not so much :P
[07:54] <marcustomlinson> morning seb128, good long weekend?
[07:54] <seb128> hey marcustomlinson, indeed! weather was summer like, especially yesterday
[07:54] <marcustomlinson> good!
[07:54] <seb128> how was your w.e?
[07:56] <willcooke> morning all
[07:57] <seb128> hey willcooke! how are you?
[07:58] <marcustomlinson> seb128: my weekend was ok thanks
[08:02] <Laney> hey ho ho ho ho de hi
[08:03] <oSoMoN> good morning marcustomlinson, seb128, willcooke, Laney
[08:03] <jibel> hi all
[08:04] <marcustomlinson> hey Laney willcooke and jibel
[08:04] <seb128> hey Laney, wb jibel had nice holidays?
[08:04] <seb128> lut oSoMoN, en forme ?
[08:04] <Laney> moin oSoMoN jibel marcustomlinson seb128
[08:05] <willcooke> hey seb128, not too bad
[08:05] <oSoMoN> seb128, la forme, et toi?
[08:06] <Laney> yo willcooke
[08:06] <willcooke> sup Laney
[08:06] <Laney> this and/or that
[08:07] <didrocks> hey willcooke, Laney
[08:07] <didrocks> salut jibel, bon retour de vacances
[08:07] <Laney> got a pineberry plant at the weekend, for a bit of novelty fruit
[08:07] <Laney> hey didrocks
[08:09] <seb128> oSoMoN, en forme!
[08:10] <oSoMoN> Laney, never heard of pineberry before, that looks exotic and tasty!
[08:11] <Laney> oSoMoN: I hadn't either until Saturday morning!
[08:18] <jibel> merci didrocks
[08:21] <jibel> merci aussi seb128 , nice holidays despite a couple of rainy days
[08:34] <Wimpress> Morning o/
[11:25] <cpaelzer> hmm, maybe I just don't know what to search for but I can't find it on the net
[11:25] <cpaelzer> with 18.04 when connecting a new screen, the default is to arrange all screens in a row
[11:26] <cpaelzer> that is sort of silly if the sum of screens is wider than the maximum width
[11:26] <cpaelzer> I wonder what to do to avoid that
[11:26] <cpaelzer> xrandr reports "current 5760 x 1080, maximum 8192 x 8192"
[11:27] <cpaelzer> (that is three screens=
[11:27] <cpaelzer> plugging a 2560 wide screen in addition breaks things, as it gets me above the 8192
[11:27] <cpaelzer> arranged in two rows things would work fine
[11:27] <cpaelzer> and actually if getting to a menu to set this in displays it works fine
[11:27] <cpaelzer> but if then I plug another 2560 display it does the same again
[11:28] <cpaelzer> and this time it seems to much, I can't find the display settings in what is left of my desktop
[11:28] <cpaelzer> so I wonder if I could pre-arrange or change the default from row to something else
[11:28] <seb128> hey cpaelzer
[11:28] <cpaelzer> even top-down would work as all the screens are not too high
[11:28] <cpaelzer> hi seb128
[11:28] <seb128> I don't think you can change the default
[11:29] <seb128> but it should remember your configs and when you connect the same screens reapply what you configured last time you were in that setup
[11:29] <cpaelzer> hmm, then I need to "find" my display settings in the 5 display setup
[11:29] <cpaelzer> I only had 1.5 displays left working after pluggin that
[11:30] <cpaelzer> probably the left or right max of the default setup
[11:30] <cpaelzer> I'll let you know what happens seb128
[11:31] <seb128> thx
[11:31] <seb128> that's probably worth an upstream bug report with your suggestions btw
[11:32] <cpaelzer> will do so after I have more data
[11:32] <seb128> thx
[11:32] <cpaelzer> I just checked the journald on the last boot
[11:32] <cpaelzer> there is some crashing/error when applying the config
[11:32] <cpaelzer> I might need to ask or file abug for that as well
[11:34] <cpaelzer> kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:55:pipe B] flip_done timed out
[11:34] <cpaelzer> outch
[11:34] <cpaelzer> lets see how reproducible that part of it will be (I hope not)
[11:34] <seb128> kernel/video driver bug?
[11:34] <cpaelzer> yes
[11:35] <cpaelzer> that seems to be the root cause why my "apply config" with 5 screens just failed
[11:36] <cpaelzer> I'll complete some other work as that seems to include some reboots
[11:58] <cpaelzer> seb128: as an alternative can I raise that default 8192x8192 limit?
[11:59] <seb128> that's a video driver/stack one no?
[12:00] <seb128> would be a question for the kernel team
[12:00] <cpaelzer> I didn't know who set that limit
[12:00] <cpaelzer> if you say so
[12:00] <cpaelzer> any buzzwords that are worth to mention?
[12:01] <cpaelzer> like  tbfkaf = the-buffer-formerly-known-as-framebuffer
[12:01] <cpaelzer> or anything like it
[12:03] <seb128> cpaelzer, I'm not familiar with the topic but https://www.reddit.com/r/linux/comments/6bghzm/increasing_maximum_xorg_virtual_screen_resolution/ has some details
[12:04] <seb128> cpaelzer, the comments suggest that until intel gen7 that was an hardware limitation
[12:05] <seb128> cpaelzer, https://bugs.freedesktop.org/show_bug.cgi?id=102508 seems relevant
[12:33] <marcustomlinson> bah, gitlab is down too often
[12:37] <marcustomlinson> at least not for long thankfully
[13:29] <cpaelzer> seb128: it didn't crash this time and things work fine
[13:29] <cpaelzer> I had opened display settings beforehand and focussed to be able to key-move it to a screen I could see
[13:30] <cpaelzer> never the less I should report the "do not put all in a row" bug
[13:30] <cpaelzer> any suggestion where that would be against?
[13:31] <cpaelzer> I mean who decides that they should be in a row at first - xserver?
[13:31] <cpaelzer> or anything in gnome
[13:34] <seb128> cpaelzer, good question, I don't know for sure, I think it's xorg but maybe GNOME would make sense to put some logic...
[13:34] <seb128> tjaalton, ^ do you know?
[13:37] <tjaalton> seb128: the server has some defaults, but the DE can do whatever
[13:38] <seb128> tjaalton, would it make sense to have the server default changed for that problem though?
[13:38] <cpaelzer> server would be https://gitlab.freedesktop.org/xorg/xserver/issues/new then I guess?
[13:38] <seb128> seems the right place to fix it rather than having every desktop handling
[13:38] <seb128> cpaelzer, yes
[13:38] <tjaalton> I don't think so
[13:38] <tjaalton> having them in a row makes most sense to me
[13:38] <cpaelzer> all I want is a safer default
[13:38] <cpaelzer> as the "all in a row" breaks
[13:38] <cpaelzer> and xorg could have known
[13:38] <tjaalton> you probably want the 8k limit bumped
[13:39] <cpaelzer> there always will be some limit
[13:39] <cpaelzer> isn't something like "start a second row once > limit" better
[13:39] <cpaelzer> whatever the limit will be
[13:39] <tjaalton> for recent enough (intel) hw it'll be 16k in 5.3
[13:39] <cpaelzer> so that still is killed by 5 4k screens (a lot I admit)
[13:40] <tjaalton> you can't connect those to any intel
[13:40] <cpaelzer> I already use i915 + displaylink now
[13:41] <cpaelzer> the maximum did not increase by using that, but then that is kind of a special extra device (compared to a secong real graphics card)
[13:42] <tjaalton> seb128: and what about wayland then? the compositor would "own" the defaults there anyway
[13:43] <tjaalton> anyway, don't get your hopes up for seeing it changed in xserver upstream
[13:43] <tjaalton> pretty sure there are bugs filed already
[13:43] <seb128> k, fair enough
[13:43] <cpaelzer> yep fair
[13:44] <cpaelzer> I haven't found others, but as we all know sometimes they are hard to search for
[13:44] <cpaelzer> I'll file one
[13:44] <cpaelzer> and since I got around it I'm fine
[13:44] <cpaelzer> knowing that 5.3 will give me 15k sounds great as well
[13:44] <cpaelzer> thank tjaalton
[13:44] <seb128> cpaelzer, tjaalton, thx
[13:45] <tjaalton> cpaelzer: depends on your hw though.. it's haswell and up
[13:46] <cpaelzer> "Kaby Lake Refresh" here
[13:46] <tjaalton> good enough
[13:47] <tjaalton> haswell is ~5y old
[13:47] <marlinc> What is the second button for? https://vitux.com/wp-content/uploads/2018/08/word-image-95.png
[13:51] <cpaelzer> seb128: https://gitlab.freedesktop.org/xorg/xserver/issues/822 we will see
[13:51] <gitbot> xorg issue 822 in xserver "Do not default align all displays horizontally if over the maximum width" [Opened]
[13:52] <seb128> cpaelzer, thx!
[13:52] <seb128> marlinc, block screen rotation
[13:52] <marlinc> Oh wow okay
[13:52] <marlinc> Never knew such a thing existed on a laptop
[13:53] <seb128> you probably have a convertible?
[13:55] <marlinc> Not me but a collegue
[13:55] <marlinc> But it is a regular laptop
[14:45] <cyphermox> seb128: hey
[14:46] <cyphermox> re: NetworkManager autopkgtests. I think I've ported most of it, but still having issues with the add-and-activate process for wifis. I'm reasonably certain I'm close to having it working, but I don't know what's missing. It might just be pretty obvious to somehow who has their GLib/gir knowledge more recent and ready than mine. anyone could have a look if I push this to a separate branch?
[15:29] <seb128> cyphermox, hey, thanks for working on that! tkamppeter is looking at n-m for us so he could probably have a look yes
[15:29] <seb128> kenvandine, tkamppeter^
[19:53] <cyphermox> seb128: kenvandine: tkamppeter: https://git.launchpad.net/network-manager/log/?h=gir-nm
[19:53] <seb128> cyphermox, thx
[20:20] <kenvandine> marcustomlinson: collaboration setup on those snaps so CI should be able to publish them