2025/11/07

2025-11-07 01:17:06 +0100hightower2(~hightower@213.186.15.36) hightower2
2025-11-07 02:04:56 +0100weitcis(~quassel@172.91.71.27) (Ping timeout: 265 seconds)
2025-11-07 02:18:08 +0100weitcis(~quassel@172.91.73.15)
2025-11-07 03:57:18 +0100hightower3(~hightower@dh207-112-105.xnet.hr) hightower2
2025-11-07 03:59:57 +0100hightower4(~hightower@cpe-94-253-245-24.st.cable.xnet.hr) (Ping timeout: 244 seconds)
2025-11-07 04:34:38 +0100td_(~td@i53870901.versanet.de) (Ping timeout: 256 seconds)
2025-11-07 04:36:21 +0100td_(~td@i5387093B.versanet.de) td_
2025-11-07 04:51:35 +0100haskellbridge(~hackager@96.28.224.214) (Remote host closed the connection)
2025-11-07 04:52:21 +0100haskellbridge(~hackager@96.28.224.214) hackager
2025-11-07 08:19:16 +0100ft(~ft@p4fc2aaeb.dip0.t-ipconnect.de) (Quit: leaving)
2025-11-07 09:28:23 +0100yecinem_(~yecinem@p200300ee0f2490006b0cdadfcd6535f6.dip0.t-ipconnect.de)
2025-11-07 12:31:52 +0100Guest34(~Guest34@p200300ee97067ed843e1338c6ae2eb70.dip0.t-ipconnect.de)
2025-11-07 12:33:32 +0100Guest34(~Guest34@p200300ee97067ed843e1338c6ae2eb70.dip0.t-ipconnect.de) (Client Quit)
2025-11-07 14:47:17 +0100_qw(~eqw@user/eqw) (Ping timeout: 260 seconds)
2025-11-07 15:04:04 +0100_qw(~eqw@user/eqw) eqw
2025-11-07 15:04:20 +0100hightower4(~hightower@dh207-112-200.xnet.hr) hightower2
2025-11-07 15:06:58 +0100hightower3(~hightower@dh207-112-105.xnet.hr) (Ping timeout: 244 seconds)
2025-11-07 15:15:19 +0100ft(~ft@p4fc2aaeb.dip0.t-ipconnect.de) ft
2025-11-07 17:12:26 +0100xjcj(~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de)
2025-11-07 17:21:59 +0100hightower3(~hightower@dh207-112-73.xnet.hr) hightower2
2025-11-07 17:23:25 +0100hightower4(~hightower@dh207-112-200.xnet.hr) (Ping timeout: 264 seconds)
2025-11-07 17:29:51 +0100xjcj(~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) (Quit: Client closed)
2025-11-07 17:31:46 +0100OftenFad1(~OftenFade@user/OftenFaded) (Ping timeout: 246 seconds)
2025-11-07 17:35:16 +0100 <haskellbridge> <Nexilva> Any update on Xmonad for Wayland? I read the threads on Haskell discord but I haven't heard of any major milestones being achieved.
2025-11-07 17:35:56 +0100 <haskellbridge> <Nexilva> I'm on Ubuntu 22.04. I can stay on it for up to 32.04 so in 2032, I'll need to either leave it on 22.04 or get another distro that would still support X11
2025-11-07 17:36:26 +0100 <geekosaur> both threads seem to have died, so we're back to square one
2025-11-07 17:36:30 +0100 <haskellbridge> <Nexilva> I also manage this patch for KDE https://github.com/xmonad/xmonad/issues/174
2025-11-07 17:36:37 +0100 <geekosaur> and with a hint that this nut is harder to crack than we'd hoped
2025-11-07 17:36:45 +0100xjcj(~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de)
2025-11-07 17:36:48 +0100 <haskellbridge> <Nexilva> So I'll need to patch plasma as well for it.
2025-11-07 17:37:07 +0100 <haskellbridge> <Nexilva> Then we'll just need to figure out a way to keep X11 alive!
2025-11-07 17:37:25 +0100 <haskellbridge> <Nexilva> https://x11libre.net/ I found this while researching
2025-11-07 17:38:40 +0100 <geekosaur> yes, but if you scan back in here you'll find some, uh, potential issues
2025-11-07 17:38:52 +0100 <haskellbridge> <Nexilva> geekosaur: what's your distro?
2025-11-07 17:40:04 +0100 <geekosaur> ubuntu, I'm on 25.04 and resisting moving to 25.10 because gnome loses x11 support there and I may potentially lose google drive support as a result
2025-11-07 17:40:20 +0100 <geekosaur> (mate defers to gnome for authentication for it)
2025-11-07 17:40:51 +0100 <geekosaur> considering moving to debian stable on the theory they'll hold on to x11 a bit longer
2025-11-07 17:41:19 +0100 <haskellbridge> <Nexilva> Sigh. I don't like this situation at all.
2025-11-07 17:42:09 +0100 <haskellbridge> <Nexilva> I use KDE and KDE provides on Kubuntu, X11 session, but not by default, on 25.10 and assumingly next year on 26.04
2025-11-07 17:43:20 +0100 <geekosaur> right, that's why I'm not upgrading to it
2025-11-07 17:44:45 +0100 <geekosaur> and upgrading to a non-LTS version of ubuntu turns out to have been a major mistake; I should have stuck with the LTS. but at the time I don't think we knew the rug was going to be pulled so quickly
2025-11-07 17:45:13 +0100 <haskellbridge> <Nexilva> You can always reinstall with 24.04 LTS. Is that an option for you?
2025-11-07 17:45:49 +0100 <geekosaur> yes, but if I have to reinstall anyway, I figure I might want to reinstall to something more likely to retain X11 support
2025-11-07 17:46:08 +0100 <haskellbridge> <Nexilva> That's also what I'm thinking.
2025-11-07 17:47:52 +0100xjcj(~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) (Quit: Client closed)
2025-11-07 17:48:21 +0100xjcj(~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de)
2025-11-07 17:48:31 +0100 <geekosaur> (and not only for xmonad; there are still a number of things Wayland doesn't handle)
2025-11-07 17:49:13 +0100 <geekosaur> oh, if you checked backscroll liskin mentioned a turbocharged X11-under-wayland that allows X11 window managers to work
2025-11-07 17:49:37 +0100 <geekosaur> with the potential downside of having to hack things up to not autostart wayland versions of e.g. notification daemons
2025-11-07 17:51:06 +0100xjcj(~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) (Client Quit)
2025-11-07 17:52:04 +0100 <geekosaur> since ubuntu gives me a wayland session (that I'm not logged into) I may test liskin's thing at some point
2025-11-07 17:54:01 +0100xjcj(~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de)
2025-11-07 17:54:39 +0100 <haskellbridge> <Nexilva> https://wayland.freedesktop.org/docs/html/ch05.html currently reading up on this
2025-11-07 17:57:07 +0100 <geekosaur> oh, the bigger problem is mroe and more things are going to remove X11 support (gnome already has, which is why ubuntu 25.10 is problematic for me because that version lands then)
2025-11-07 17:58:12 +0100 <haskellbridge> <Nexilva> Hopefully by then some new distros that support X11 will come out. Who knows.
2025-11-07 17:58:37 +0100 <haskellbridge> <Nexilva> But yeah, applications lacking X11 support is going to cause a problem
2025-11-07 17:58:55 +0100xjcj(~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) (Ping timeout: 250 seconds)
2025-11-07 18:01:36 +0100yecinem_(~yecinem@p200300ee0f2490006b0cdadfcd6535f6.dip0.t-ipconnect.de) (Ping timeout: 244 seconds)
2025-11-07 18:09:56 +0100xjcj(~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de)
2025-11-07 18:14:13 +0100xjcj(~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) (Client Quit)
2025-11-07 18:17:30 +0100OpenSource(~OpenSourc@user/OpenSource) OpenSource
2025-11-07 18:18:03 +0100 <OpenSource> geekosaur, It's me Nexilva from Matrix. Have you triex Xwayland or wayland-x11 to run Xmonad? Is that a possibility?
2025-11-07 18:20:36 +0100 <geekosaur> Xwayland won't fly, I'm pretty sure. wayland-x11 is the one liskin mentioned that should be able to do it; as I said, I want to test it at some point
2025-11-07 18:28:40 +0100 <geekosaur> btw you don't need to be on the irc side of the bridge
2025-11-07 18:29:32 +0100 <geekosaur> I'm on both sides because I run the bridge (here and for a number of other Haskell-related channels/rooms) and I want to be able to monitor easily. but I'm a chanop irc-side so I mostly stick to this side
2025-11-07 18:32:24 +0100 <OpenSource> Np. I had to get on IRC to do some research on this matter. I'm asking arch and debian folks about x11 phasing out
2025-11-07 18:32:41 +0100 <OpenSource> I figured I'll join xmonad channel here as well instead of switching windows
2025-11-07 18:41:44 +0100xjcj(~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de)
2025-11-07 18:49:37 +0100xjcj(~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) (Ping timeout: 250 seconds)
2025-11-07 18:54:09 +0100Solitary(~Solitary@user/solitary) (Read error: Connection reset by peer)
2025-11-07 19:07:10 +0100 <liskin> wayback is the one I mentioned
2025-11-07 19:07:18 +0100 <liskin> I believe it uses Xwayland under the hood
2025-11-07 19:09:44 +0100 <liskin> https://gitlab.freedesktop.org/wayback/wayback
2025-11-07 19:10:05 +0100 <liskin> "It is essentially
2025-11-07 19:10:07 +0100 <liskin> a stub compositor which provides just enough Wayland capabilities to host
2025-11-07 19:10:09 +0100 <liskin> a rootful Xwayland server."
2025-11-07 19:10:41 +0100 <liskin> So yeah Xwayland plus wlroots plus a tiny little bit of glue
2025-11-07 19:13:59 +0100 <liskin> Not even exaggerating - it's 3 common header/c files and 3 binaries c files. Quite possibly less code than early xmonad core
2025-11-07 19:14:35 +0100 <liskin> Maybe I should give it a try. Compton/picom gives me headaches
2025-11-07 19:23:07 +0100 <geekosaur> I've found the picom in 25.04 pretty decent
2025-11-07 19:23:14 +0100 <geekosaur> but my head isn't yours
2025-11-07 19:23:44 +0100 <geekosaur> (different things give me headaches. If I'm lucky. More likely my brain just overloads and starts dropping stuff on the floor)
2025-11-07 19:30:21 +0100hightower4(~hightower@cpe-94-253-239-158.st.cable.xnet.hr) hightower2
2025-11-07 19:33:19 +0100hightower3(~hightower@dh207-112-73.xnet.hr) (Ping timeout: 264 seconds)
2025-11-07 21:00:38 +0100yauhsien(~Yau-Hsien@118-168-140-77.dynamic-ip.hinet.net) yauhsien
2025-11-07 22:03:19 +0100hightower3(~hightower@cpe-94-253-237-35.st.cable.xnet.hr) hightower2
2025-11-07 22:06:01 +0100hightower4(~hightower@cpe-94-253-239-158.st.cable.xnet.hr) (Ping timeout: 264 seconds)