2021/12/11

2021-12-11 01:03:31 +0100seschwar(~seschwar@user/seschwar) (Quit: :wq)
2021-12-11 01:25:15 +0100curiousgay(~curiousga@77-120-141-90.kha.volia.net)
2021-12-11 01:28:29 +0100curiousgay_(~AdminUser@77-120-141-90.kha.volia.net)
2021-12-11 01:37:02 +0100curiousgay(~curiousga@77-120-141-90.kha.volia.net) (Quit: Leaving)
2021-12-11 01:37:46 +0100curiousgay_(~AdminUser@77-120-141-90.kha.volia.net) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
2021-12-11 01:38:07 +0100curiousgay(~AdminUser@77-120-141-90.kha.volia.net)
2021-12-11 01:59:52 +0100cyr4x3(~cyr4x3@139.47.114.87)
2021-12-11 02:00:41 +0100cyr4x3(~cyr4x3@139.47.114.87) (Client Quit)
2021-12-11 02:18:19 +0100mvk(~mvk@2607:fea8:5cdd:f000::9788) (Ping timeout: 252 seconds)
2021-12-11 02:35:38 +0100curiousgay(~AdminUser@77-120-141-90.kha.volia.net) (Ping timeout: 256 seconds)
2021-12-11 03:35:50 +0100catman(~catman@user/catman) (Quit: WeeChat 3.4-dev)
2021-12-11 03:36:45 +0100catman(~catman@user/catman)
2021-12-11 04:04:02 +0100banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 260 seconds)
2021-12-11 04:20:51 +0100banc(banc@gateway/vpn/airvpn/banc)
2021-12-11 04:29:01 +0100td_(~td@94.134.91.156) (Ping timeout: 250 seconds)
2021-12-11 04:30:45 +0100td_(~td@94.134.91.156)
2021-12-11 06:26:39 +0100catman(~catman@user/catman) (Quit: WeeChat 3.4-rc1)
2021-12-11 06:50:42 +0100catman(~catman@user/catman)
2021-12-11 06:51:29 +0100mvk(~mvk@2607:fea8:5cdd:f000::9788)
2021-12-11 10:00:16 +0100Damia0o[m](~damian0om@2001:470:69fc:105::1:2fdc) (Quit: You have been kicked for being idle)
2021-12-11 10:00:16 +0100stsaintwyy[m](~stsaintwy@2001:470:69fc:105::1:3181) (Quit: You have been kicked for being idle)
2021-12-11 10:22:28 +0100curiousgay(~quassel@77-120-141-90.kha.volia.net)
2021-12-11 11:16:57 +0100curiousgay(~quassel@77-120-141-90.kha.volia.net) (Ping timeout: 252 seconds)
2021-12-11 11:21:18 +0100electr0n(~electr0n@about/security/founder/electr0n) (Ping timeout: 260 seconds)
2021-12-11 11:23:37 +0100seschwar(~seschwar@user/seschwar)
2021-12-11 12:54:37 +0100 <Solid> liskin: I guess for the release procedure of x11-xft I can just follow the relevant parts from MAINTAINERS.md?
2021-12-11 13:01:18 +0100 <geekosaur> aplainzetakind, pretty sure yu cannot build xmonad without XRandR support these days. can you do: ghc -e "Graphics.X11.openDisplay [] >>= Graphics.X11.Xinerama.getScreenInfo"
2021-12-11 13:01:58 +0100 <geekosaur> if you're using stack or cabal you may need to use stack exec or cabal exec to do this
2021-12-11 13:02:31 +0100 <Solid> what's a "merged display situation"?
2021-12-11 13:03:57 +0100 <geekosaur> they're getting the bounding box of both their monitors as a single "monitor" in xmonad, as if xmonad were somehow not getting xinerama/XRandR display information
2021-12-11 13:06:26 +0100curiousgay(~curiousga@77-120-141-90.kha.volia.net)
2021-12-11 13:08:05 +0100 <Solid> Oo
2021-12-11 13:08:13 +0100 <Solid> that's certainly very weird
2021-12-11 13:10:21 +0100 <geekosaur> aplainzetakind, also helpful: stack ghci or cabal repl, then: XOpenDisplay [] >>= getCleanedScreenInfo
2021-12-11 13:11:20 +0100 <geekosaur> sorry, that's: openDisplay [] >>= getCleanedScreenInfo
2021-12-11 13:11:49 +0100 <geekosaur> for reference, mine produces: [Rectangle {rect_x = 1920, rect_y = 0, rect_width = 1366, rect_height = 768},Rectangle {rect_x = 0, rect_y = 0, rect_width = 1920, rect_height = 1080}]
2021-12-11 13:17:52 +0100 <geekosaur> also might be interesting to do that with getScreenInfo instead of getCleanedScreenInfo and compare the results
2021-12-11 13:18:16 +0100 <geekosaur> (I would expect that any bugs in nubScreens would have been found by now, but who knows?)
2021-12-11 13:27:21 +0100 <aplainzetakind> geekosaur: I don't have Graphics.X11
2021-12-11 13:27:43 +0100 <aplainzetakind> But, I should probably take into account the xmonad environment.
2021-12-11 13:27:55 +0100 <geekosaur> you wouldn't have xmonad if that were the case. stack user?
2021-12-11 13:28:11 +0100 <geekosaur> or cabal user?
2021-12-11 13:28:32 +0100 <aplainzetakind> Should I also pass -package-env=xmonad? That's where I installed the --lib's.
2021-12-11 13:28:34 +0100 <aplainzetakind> cabal
2021-12-11 13:28:41 +0100 <geekosaur> right, you were asking about cabal and environment files yeterday
2021-12-11 13:29:00 +0100 <geekosaur> so, this will be in cabal's store and you will need to use cabal repl
2021-12-11 13:29:16 +0100 <geekosaur> and yes you'll need --package-env
2021-12-11 13:29:54 +0100 <aplainzetakind> cabal: unrecognized 'repl' option `--package-env=xmonad'
2021-12-11 13:30:01 +0100 <Solid> liskin: it just worked \o/ thank you for making this so easy with the CI workflows
2021-12-11 13:30:05 +0100 <aplainzetakind> repl comes after?
2021-12-11 13:30:08 +0100 <geekosaur> you didn't export the X11 libs soo --package-env won't be enough to access them
2021-12-11 13:30:20 +0100 <geekosaur> comes after, yes
2021-12-11 13:30:23 +0100 <aplainzetakind> No.
2021-12-11 13:30:34 +0100 <aplainzetakind> I mean no to coming after.
2021-12-11 13:30:43 +0100 <aplainzetakind> Both ways it says unrecognized option.
2021-12-11 13:31:12 +0100 <geekosaur> hm
2021-12-11 13:31:33 +0100 <geekosaur> although actually you should not need it here since it's still in the store and cabal repl gives you access to the store
2021-12-11 13:31:39 +0100 <geekosaur> so just go without it
2021-12-11 13:32:13 +0100 <aplainzetakind> Can't import Graphics.X11
2021-12-11 13:32:23 +0100 <aplainzetakind> in a generic repl
2021-12-11 13:32:41 +0100 <geekosaur> mm
2021-12-11 13:33:03 +0100 <aplainzetakind> Should I go to ~/.xmonad and do it there perhaps?
2021-12-11 13:33:17 +0100 <geekosaur> you don't really want a generic one, you want the one in the xmonad directory. but at worst `cabal repl --package=X11` should work
2021-12-11 13:33:48 +0100 <geekosaur> that said, for the other tests you need to be in ~/.xmonad so you get the xmonad and xmonad-contrib libs, so yes go there
2021-12-11 13:34:24 +0100 <aplainzetakind> `cabal repl --package=X11` also can't import Graphics.X11
2021-12-11 13:34:29 +0100 <aplainzetakind> Is my store borked?
2021-12-11 13:37:47 +0100 <geekosaur> blah. this is supposed ti work but it's not working here either
2021-12-11 13:37:53 +0100 <geekosaur> are you in ~/.xmonad?
2021-12-11 13:38:18 +0100 <geekosaur> I guess you have to use cabal repl in a directory that has access to your store
2021-12-11 13:38:25 +0100 <geekosaur> that works for me here
2021-12-11 13:38:32 +0100 <aplainzetakind> I am in ~/.xmonad
2021-12-11 13:39:09 +0100 <geekosaur> uh. no, it doesn't work for me after all :(
2021-12-11 13:39:23 +0100 <geekosaur> I had expected dependencies would be at least visible, but I guess not
2021-12-11 13:40:00 +0100 <aplainzetakind> One question, should I have two X displays or one?
2021-12-11 13:40:14 +0100 <aplainzetakind> When a second monitor is connected that is.
2021-12-11 13:40:43 +0100 <obimod> one display, two screens
2021-12-11 13:40:52 +0100 <obimod> i think
2021-12-11 13:40:55 +0100 <geekosaur> yes
2021-12-11 13:41:00 +0100 <geekosaur> also one X11 Screen
2021-12-11 13:41:36 +0100 <geekosaur> because you can't move windows or workspaces between X11 Screens, because the Screen abstraction dates from a day when each Screen had its own independent video card / framebuffer
2021-12-11 13:41:54 +0100 <geekosaur> which is why X11 uses the hack of carving multiple mnonitors out of a single root window
2021-12-11 13:42:17 +0100 <geekosaur> okay, I guess you ignore that first part and do the other two, which I know work
2021-12-11 13:42:41 +0100 <obimod> geekosaur: good to know :)
2021-12-11 13:43:02 +0100 <geekosaur> [11 12:10:21] <geekosaur> aplainzetakind, also helpful: stack ghci or cabal repl, then: XOpenDisplay [] >>= getCleanedScreenInfo
2021-12-11 13:43:12 +0100 <geekosaur> oh crap that has the other bug
2021-12-11 13:43:18 +0100 <geekosaur> [11 12:10:21] <geekosaur> aplainzetakind, also helpful: stack ghci or cabal repl, then: openDisplay [] >>= getCleanedScreenInfo
2021-12-11 13:43:37 +0100 <geekosaur> used the C name instread of the Haskell one
2021-12-11 13:44:42 +0100 <aplainzetakind> Well, I don't have these names in the repl either.
2021-12-11 13:45:23 +0100 <geekosaur> o.O
2021-12-11 13:45:27 +0100 <aplainzetakind> Running cabal in the environment is not working somehow.
2021-12-11 13:45:37 +0100 <geekosaur> now I wonder how you built this in the first place
2021-12-11 13:45:40 +0100 <aplainzetakind> Can I just run ghci with a flag for the env?
2021-12-11 13:46:02 +0100 <aplainzetakind> As in hvr's comment.
2021-12-11 13:46:04 +0100 <geekosaur> ghci --package-env=xmonad
2021-12-11 13:46:10 +0100 <geekosaur> hopefully
2021-12-11 13:47:07 +0100 <aplainzetakind> single - but it works and I can import XMonad.
2021-12-11 13:47:14 +0100 <aplainzetakind> But not Graphics X11.
2021-12-11 13:47:20 +0100 <aplainzetakind> Because it's not in the env file.
2021-12-11 13:47:31 +0100 <aplainzetakind> Can I still access openDisplay?
2021-12-11 13:47:48 +0100 <aplainzetakind> Which module does it come from?
2021-12-11 13:48:26 +0100 <Solid> Graphics.X11.Xlib.Display
2021-12-11 13:48:35 +0100 <geekosaur> XMonad reexports it and getScreenInfo
2021-12-11 13:48:38 +0100 <Solid> oh but XMonad laso re-exports it
2021-12-11 13:49:08 +0100 <Solid> shouldn't you just be able to execute this in main? this might be the most painless way
2021-12-11 13:50:40 +0100 <geekosaur> well, point is I want to be able to find this out without the config in the way, just dumping server information as xmonad would receive it
2021-12-11 13:50:48 +0100 <aplainzetakind> [Rectangle {rect_x = 0, rect_y = 0, rect_width = 2560, rect_height = 1440}]
2021-12-11 13:51:06 +0100 <geekosaur> guh
2021-12-11 13:51:10 +0100 <aplainzetakind> Currently in arandr the monitors are laid out nested.
2021-12-11 13:51:36 +0100 <geekosaur> so you're getting one screen from xrandr
2021-12-11 13:51:51 +0100 <geekosaur> run xrandr on the command line to see what it says and pastebin the result
2021-12-11 13:51:56 +0100 <geekosaur> @where paste
2021-12-11 13:51:56 +0100 <lambdabot> Help us help you: please paste full code, input and/or output at e.g. https://paste.tomsmeding.com
2021-12-11 13:53:27 +0100 <aplainzetakind> http://dpaste.com//HQS8SQY97
2021-12-11 13:54:21 +0100 <aplainzetakind> The monitors are part of the same screen.
2021-12-11 13:54:35 +0100 <aplainzetakind> Pretty sure this is not an xmonad problem actually.
2021-12-11 13:55:20 +0100 <Solid> `Screen 0: minimum 320 x 200, current 2560 x 1440` tells me that it only recognises one monitor (the HDMI-2 one)
2021-12-11 13:56:13 +0100 <aplainzetakind> No, the "screen" is a composite thing.
2021-12-11 13:56:22 +0100 <aplainzetakind> Let me arrange the monitors side by side.
2021-12-11 13:56:59 +0100 <aplainzetakind> https://dpaste.com//2V57VH55F
2021-12-11 13:57:15 +0100 <aplainzetakind> See, it sets that screen to be the smallest rectangle containing both monitors.
2021-12-11 13:57:38 +0100 <Solid> yes, but 2560x1440 was only the second monitor before, no?
2021-12-11 13:57:59 +0100 <aplainzetakind> The first output was because I arranged the monitors to be nested in arandr.
2021-12-11 13:58:13 +0100 <Solid> oh
2021-12-11 13:58:14 +0100 <aplainzetakind> So The smallest rectangle was the bigger monitor.
2021-12-11 13:58:24 +0100 <aplainzetakind> Otherwise things are unusable.
2021-12-11 14:01:46 +0100 <geekosaur> hm. are they set to be mirrored?
2021-12-11 14:03:48 +0100 <aplainzetakind> Does that mean cloned?
2021-12-11 14:04:05 +0100 <geekosaur> yes
2021-12-11 14:04:14 +0100 <aplainzetakind> No.
2021-12-11 14:04:50 +0100 <aplainzetakind> They show portions of that abstract screen, however they are arranged.
2021-12-11 14:05:02 +0100 <geekosaur> so with the monitors no longer overlapping, try the getCleanedScreenInfo thing again
2021-12-11 14:06:12 +0100 <aplainzetakind> [Rectangle {rect_x = 0, rect_y = 0, rect_width = 6985, rect_height = 4881}]
2021-12-11 14:06:20 +0100 <aplainzetakind> Moved quite a bit apart.
2021-12-11 14:07:06 +0100 <aplainzetakind> I saw an SO question having this issue, edited to say that it got fixed after a system update with newer drivers.
2021-12-11 14:07:15 +0100 <aplainzetakind> Can't find it now unfortunately.
2021-12-11 14:07:52 +0100 <geekosaur> yeh, I'm thinking at this point it's a driver issue
2021-12-11 14:08:16 +0100 <aplainzetakind> Found this: https://stackoverflow.com/questions/63887202/xrandr-two-screens-different-resolution-without-invis…
2021-12-11 14:08:21 +0100 <geekosaur> xmjonad is not being told by the X server that there are two monitors
2021-12-11 14:08:47 +0100 <aplainzetakind> I have nouveau and i915.
2021-12-11 14:09:02 +0100 <aplainzetakind> I could switch which is in use in xorg.conf maybe?
2021-12-11 14:09:15 +0100 <aplainzetakind> Is that a viable approach?
2021-12-11 14:09:38 +0100 <geekosaur> it's worth trying
2021-12-11 14:12:02 +0100 <aplainzetakind> Is there a handholdy guide to get me through without having to grok the entire xorg configuration. I have next to no knowledge on how to do that.
2021-12-11 14:20:51 +0100 <geekosaur> not really
2021-12-11 14:21:04 +0100 <geekosaur> https://bbs.archlinux.org/viewtopic.php?id=243402 may help some
2021-12-11 14:21:18 +0100 <geekosaur> although it's arch-specific
2021-12-11 15:30:39 +0100defjam(~eb0t@90.202.255.10) (Ping timeout: 265 seconds)
2021-12-11 15:32:27 +0100defjam(~eb0t@90.210.94.161)
2021-12-11 16:04:45 +0100 <liskin> Solid: good!
2021-12-11 17:07:39 +0100 <Solid> huh, I didn't know we had X.C.Example
2021-12-11 17:08:01 +0100 <Solid> I wonder if this might be a good place to keep the tutorial config in
2021-12-11 17:22:06 +0100mc47(~mc47@xmonad/TheMC47)
2021-12-11 17:36:01 +0100 <noex> what would be the best way to arrange terminals in a certain configuration on different workspaces on startup?
2021-12-11 17:36:48 +0100 <noex> intuitively, i would think the startup hook, but that runs on restart
2021-12-11 17:37:46 +0100 <Solid> You can use spawnOnce (or spawnOnOnce) if you really only want to spawn these once per session
2021-12-11 17:38:03 +0100 <Solid> ( https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Util-SpawnOnce.html#v:spawnO… )
2021-12-11 17:40:13 +0100 <noex> nice, thanks. i'll give that a shot.
2021-12-11 17:42:03 +0100 <Solid> liskin: any more comments on https://github.com/xmonad/xmonad-contrib/pull/646/files ?
2021-12-11 18:07:15 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Quit: Lost terminal)
2021-12-11 18:29:22 +0100 <MrElendig> or one of the workspace modules maybe
2021-12-11 18:30:32 +0100geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2021-12-11 18:32:14 +0100geekosaur(~geekosaur@xmonad/geekosaur)
2021-12-11 18:35:35 +0100electr0n(~electr0n@about/security/founder/electr0n)
2021-12-11 18:53:44 +0100 <liskin> Solid: looks all right last time I looked
2021-12-11 18:54:33 +0100 <Solid> coolio
2021-12-11 19:05:29 +0100 <liskin> Solid: thanks for taking care of all this and sorry for not being around much
2021-12-11 19:05:38 +0100mvk(~mvk@2607:fea8:5cdd:f000::9788) (Ping timeout: 260 seconds)
2021-12-11 19:06:26 +0100 <Solid> ah that's totally fine; mental health is definitely more important than xmonad :)
2021-12-11 19:06:44 +0100 <liskin> Oh it's not just mental this time :-)
2021-12-11 19:06:52 +0100 <liskin> Although who knows
2021-12-11 19:07:29 +0100 <Solid> Oh right, you also hand some hand troubles (hopefully not more! :o)
2021-12-11 19:07:30 +0100 <liskin> Maybe it's just my body telling me it's time for a proper break, and since the brain wouldn't listen otherwise... ;-)
2021-12-11 19:07:43 +0100 <liskin> Yeah just hands
2021-12-11 19:08:05 +0100 <liskin> Should be fine but I need to make sure it's well enough to not come back
2021-12-11 19:10:13 +0100 <Solid> yeah I developed RSI in my right hand while I was in high school and to this day I can't use mice of a certain shape because in the span of like five minutes my hand will cramp like crazy
2021-12-11 19:10:23 +0100 <Solid> shit is scary
2021-12-11 19:12:36 +0100 <liskin> Oh
2021-12-11 19:13:17 +0100 <liskin> I really really hope it just goes back to its original state :-/
2021-12-11 19:14:10 +0100catman(~catman@user/catman) (Quit: WeeChat 3.4-rc1)
2021-12-11 19:14:22 +0100 <noex> i struggled with that really bad recently as well. it was frustrating, and i even saw a doctor who gave me no useful direction at all.
2021-12-11 19:14:26 +0100 <liskin> I tried moving Ctrl to CapsLock to relieve the pinky a bit but there's not much else I can do without seriously disrupting the way I use the laptop
2021-12-11 19:15:24 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2021-12-11 19:15:30 +0100 <liskin> I'm seeing a physiotherapist next week. And by seeing I mean they booked a phone call. So... probably a waste of time? :-D
2021-12-11 19:16:05 +0100 <noex> so i made a video on what steps i took to cure mine. i have no clue if it could help someone else and i'm sorry if it sucks, but I documented some things I did: https://www.youtube.com/watch?v=Ub6bGTb9wpc
2021-12-11 19:16:36 +0100 <noex> definitely recommend looking at the linked video in the description
2021-12-11 19:17:02 +0100catman(~catman@user/catman)
2021-12-11 19:17:20 +0100 <Solid> Ah, a phone call, the best way to diagnose a physical symptom for sure! :D
2021-12-11 19:24:57 +0100 <liskin> noex: I'm hoping to not need a different keyboard (maybe naive but I haven't had trouble for several decades so maybe?) but those stretches look quite useful, I'll try those for a while, thanks!
2021-12-11 19:26:17 +0100 <ectospasm> I started using a Microsoft Natural Keyboard 4000 about 15 years ago. My RSI is barely noticeable since I switched.
2021-12-11 19:26:55 +0100 <ectospasm> I have numbness/tingling in my ulnar nerve, and since I started using that model keyboard I only notice the problem when I think about it.
2021-12-11 19:27:17 +0100 <noex> liskin: np at least for me those stretches were helpful - although at first quite painful...just take it gradually at first
2021-12-11 19:28:21 +0100 <liskin> noex: I tried those as I watched the video now and it was almost fine
2021-12-11 19:28:33 +0100 <liskin> But then I'm very flexible in the first place
2021-12-11 19:30:29 +0100 <liskin> There's some possibility my pain is related to the broken bone in my wrist that never grew back together. That would be a bit silly as it's not the easiest surgery to fix. :-/
2021-12-11 19:36:24 +0100 <noex> hard to say :/ hopefully the doc can give you some insight
2021-12-11 20:03:02 +0100mvk(~mvk@2607:fea8:5cdd:f000::9788)
2021-12-11 20:05:31 +0100mvk(~mvk@2607:fea8:5cdd:f000::9788) (Remote host closed the connection)
2021-12-11 20:06:29 +0100mvk(~mvk@2607:fea8:5cdd:f000::9788)
2021-12-11 20:09:42 +0100mvk(~mvk@2607:fea8:5cdd:f000::9788) (Client Quit)
2021-12-11 20:11:26 +0100mvk(~mvk@2607:fea8:5cdd:f000::9788)
2021-12-11 20:12:06 +0100mvk(~mvk@2607:fea8:5cdd:f000::9788) (Client Quit)
2021-12-11 20:12:32 +0100mvk(~mvk@2607:fea8:5cdd:f000::9788)
2021-12-11 20:14:11 +0100mvk(~mvk@2607:fea8:5cdd:f000::9788) (Client Quit)
2021-12-11 20:14:34 +0100mvk(~mvk@2607:fea8:5cdd:f000::9788)
2021-12-11 20:43:51 +0100catman(~catman@user/catman) (Ping timeout: 268 seconds)
2021-12-11 20:55:34 +0100catman(~catman@user/catman)
2021-12-11 21:05:50 +0100Guest81(~Guest81@2a01cb0589202e00edc070a9acc1d4bb.ipv6.abo.wanadoo.fr)
2021-12-11 21:49:42 +0100curiousgay(~curiousga@77-120-141-90.kha.volia.net) (Quit: Leaving)
2021-12-11 22:01:38 +0100curiousgay(~curiousga@77-120-141-90.kha.volia.net)
2021-12-11 23:48:26 +0100themc47(~mc47@xmonad/TheMC47)
2021-12-11 23:48:54 +0100mc47(~mc47@xmonad/TheMC47) (Ping timeout: 260 seconds)
2021-12-11 23:49:42 +0100 <aplainzetakind> geekosaur: So I did this https://dpaste.com//68P3DQECT to hopefully end up with two screens but this doesn't do anything either.
2021-12-11 23:51:35 +0100 <geekosaur> why am I not surprised it's intel driver? (probably because mine has bugs too)
2021-12-11 23:53:41 +0100themc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2021-12-11 23:54:12 +0100 <aplainzetakind> Maybe I should just put nouveau there?
2021-12-11 23:54:39 +0100 <geekosaur> you could try it. nouveau has its own share of bugs but messing up multiscreen isn't generally one of them
2021-12-11 23:55:49 +0100 <geekosaur> (I can't hotplug monitors on any of my Intel-based systems, everything gets severely messed up to the point that I can't even run something like arandr to fix it, and xrandr only if I get really lucky with where a terminal ends up)
2021-12-11 23:56:26 +0100 <aplainzetakind> Hmm I think my nouveau may be altogether borked.
2021-12-11 23:57:14 +0100 <aplainzetakind> http://dpaste.com//8YZJS6Z59 This is grepping dmesg for nouveau
2021-12-11 23:59:20 +0100twiclo(~twiclo@166.70.36.40)
2021-12-11 23:59:58 +0100twiclo(~twiclo@166.70.36.40) (Client Quit)