Home liberachat/#xmonad: Logs Calendar

Logs on 2025-09-09 (liberachat/#xmonad)

02:42:55 × terrorjack quits (~terrorjac@2a01:4f8:c17:9d11::) (Quit: The Lounge - https://thelounge.chat)
02:45:27 terrorjack joins (~terrorjac@2a01:4f8:c17:9d11::)
03:32:55 FadedOften joins (~OftenFade@user/tisktisk)
04:46:34 × L29Ah quits (~L29Ah@wikipedia/L29Ah) (Ping timeout: 256 seconds)
05:29:06 <deebo> hmm something updated with flameshot and now it creates some sort of window that shifts my layout
05:29:09 <deebo> anyone else ran into this?
05:30:30 <deebo> i just have ", ((myModmask .|. shiftMask, xK_s), spawn "flameshot gui")", when i press it now i get the screenshot overlay but my windows are pushed out the top side of the monitor
06:15:58 ChubaDuba joins (~ChubaDuba@5.167.113.60)
06:54:11 × ft quits (~ft@p4fc2a25a.dip0.t-ipconnect.de) (Quit: leaving)
07:43:50 × ChubaDuba quits (~ChubaDuba@5.167.113.60) (Quit: WeeChat 4.6.3)
07:52:19 Solid joins (~slot@xmonad/slotThe)
07:53:08 <haskellbridge> <Solid (@slot-:matrix.org)> Perhaps you need to tell XMonad to not manage the window that flameshot creates?
08:02:24 <deebo> indeed, but it's some new thing, and there's no way to use xprop on it
08:15:33 <deebo> https://github.com/flameshot-org/flameshot/pull/4127 possibly related to this qt6 upgrade
08:21:42 <Solid> Mh, I just downloaded flameshot 13.1.0 (which should include that PR) and I can't reproduce the behaviour you're talking about
08:30:49 <deebo> this is what happens for me https://i.imgur.com/iQgRA8e.png, whole screen is offset somehow
08:31:11 <deebo> but i do have a "weird" monitor layout with two side by side and tv on the wall above the other monitor
08:31:29 <deebo> f42 is on flameshot 13.0.1 so not fixed yet
08:33:37 <Solid> Perhaps you'll have to wait for 13.1.0 then
09:23:55 × Mion quits (~Urist@archlinux/op/MrElendig) (Quit: aliens)
09:24:50 MrElendig joins (~Urist@archlinux/op/MrElendig)
10:05:50 tremon joins (~tremon@83.80.159.219)
12:12:00 × Solid quits (~slot@xmonad/slotThe) (Quit: ERC 5.6.1-git (IRC client for GNU Emacs 31.0.50))
12:23:12 × mkoskar quits (~mkoskar@user/mkoskar) (Ping timeout: 265 seconds)
12:27:52 mkoskar joins (~mkoskar@user/mkoskar)
12:51:13 L29Ah joins (~L29Ah@wikipedia/L29Ah)
13:35:03 hightower2 joins (~hightower@cpe-94-253-244-59.st.cable.xnet.hr)
13:37:07 × hightower4 quits (~hightower@cpe-94-253-190-65.zg.cable.xnet.hr) (Ping timeout: 255 seconds)
15:58:39 ft joins (~ft@p4fc2a25a.dip0.t-ipconnect.de)
16:34:02 × mkoskar quits (~mkoskar@user/mkoskar) (Quit: mkoskar)
16:35:09 mkoskar joins (~mkoskar@user/mkoskar)
16:53:02 × yaslam quits (~yaslam@user/yaslam) (Ping timeout: 256 seconds)
16:53:53 yaslam joins (~yaslam@user/yaslam)
18:55:38 <geekosaur> in light of https://opencollective.com/opensource/updates/public-service-announcement-re-salt-typhoon, can we prune release people on Hackage?
18:56:56 <geekosaur> on the one hand, one might not expect us to be very involved in supply chain attacks… OTOH a window manager is a lovely place to insert code that can do pretty much anything on a system
18:57:27 <geekosaur> (Wayland has some mitigations, but I expect is almost as bad in practice)
19:29:09 <L29Ah> what kind of mitigations does wayland have?
19:29:26 <L29Ah> i expect a wayland compositor having more permissions than X window manager
19:29:53 <L29Ah> as it needs things like direct I/O access unlike the window manager
19:30:30 <geekosaur> right, it's in effect the "X server"
19:31:04 <geekosaur> and the window manager is a plugin to it, and has access to more things than clients do as a result… but can be simpler also, making it easier to audit
19:32:12 <geekosaur> and a lot of stuff that's exposed for client<->window manager and client<->X server intended for window management isn't exposed in a way that lets any other client eavesdrop or potentially inject messages, like it is in X
19:33:03 <geekosaur> ("potentially inject" itself being mitigated by the "send_message" flag, as long as you don't have XTEST or certain other extensions enabled that by default are disabled for very good reason)
19:37:21 <geekosaur> there are ways to restrict those messages, but it's complicated and really easy to get wrong in both directions (that is, restricting either too little or too much)
19:44:35 ximn joins (~ximn@dslb-002-206-034-018.002.206.pools.vodafone-ip.de)
19:44:55 <ximn> Hi is there xmonad on Wayland ? Also is xmonad similar to qtile?
19:45:43 <ximn> I have Debian and would like to try it if it is like qtile any suggestions
19:48:27 <geekosaur> not yet, there was some work going on but it seems to have stalled (you can find it on Discourse)
19:50:40 <ximn> Is xmonad good for gaming?
19:53:45 <ximn> How many months is xmonad on Debian forky behind ?
19:58:30 <ximn> What's the display manager that can open xmonad ?
19:58:33 <ximn> Light dm?
20:07:22 × ximn quits (~ximn@dslb-002-206-034-018.002.206.pools.vodafone-ip.de) (Quit: Client closed)
20:20:59 ximn joins (~ximn@dslb-002-206-034-018.002.206.pools.vodafone-ip.de)
20:25:58 × tremon quits (~tremon@83.80.159.219) (Quit: getting boxed in)
20:31:12 × ximn quits (~ximn@dslb-002-206-034-018.002.206.pools.vodafone-ip.de) (Quit: Client closed)
20:41:01 <L29Ah> i wonder how many of X security critics acutally run their desktops under a MAC
20:57:41 <geekosaur> if you use an OS package then any XDG-compliant display manager should work
20:58:37 <geekosaur> if you install it yourself, there's an example desktop file on the wiki or you can do it the old fashioned way with a "default X session" and .xsession file
20:59:01 <L29Ah> he left
20:59:23 <geekosaur> sigh
21:55:54 Guest65 joins (~Guest65@dslb-002-206-034-018.002.206.pools.vodafone-ip.de)
21:55:59 <Guest65> is there a prefinished xmonad desktop
21:56:00 <Guest65> ?
22:01:35 <geekosaur> not really, the whole idea is that xmonad is a window manager construction toolkit.
22:01:46 <geekosaur> bluetile exists but it's based on a fairly old version
22:12:27 × Guest65 quits (~Guest65@dslb-002-206-034-018.002.206.pools.vodafone-ip.de) (Quit: Client closed)
23:36:01 × ft quits (~ft@p4fc2a25a.dip0.t-ipconnect.de) (Quit: Lost terminal)
23:51:51 ft joins (~ft@p4fc2a25a.dip0.t-ipconnect.de)
23:53:58 × tv quits (~tv@user/tv) (Quit: derp)
23:55:05 tv joins (~tv@user/tv)

All times are in UTC on 2025-09-09.