Newest at the top
| 2026-01-30 00:12:41 +0100 | Digitteknohippie | Digit |
| 2026-01-29 23:20:25 +0100 | Digit | (~user@user/digit) (Ping timeout: 264 seconds) |
| 2026-01-29 23:20:00 +0100 | Digitteknohippie | (~user@user/digit) Digit |
| 2026-01-29 23:10:18 +0100 | Enrico63 | (~Enrico63@host-79-27-153-69.retail.telecomitalia.it) (Quit: Client closed) |
| 2026-01-29 22:57:17 +0100 | <geekosaur> | (that said, I haven't tested that since I stopped using Macs and vmware fusion) |
| 2026-01-29 22:56:57 +0100 | <geekosaur> | although there's still a comment in my config saying to remove it if I use it under virtualization, because glx made it tank badly in that case |
| 2026-01-29 22:55:53 +0100 | <geekosaur> | fwiw I switched picom to glx backend years ago because it was faster and the default (DAMAGE?) backend had problems like that |
| 2026-01-29 22:52:58 +0100 | <liskin> | L29Ah: intel igpu and modesetting xorg video driver was my setup |
| 2026-01-29 22:20:33 +0100 | <Enrico63> | It's something that I've been observing since I addressed this https://archlinux.org/news/nvidia-590-driver-drops-pascal-support-main-packages-switch-to-open-ker… (I have a 1070ti https://www.amazon.it/-/en/dp/B078MVFXFL) |
| 2026-01-29 22:20:28 +0100 | <L29Ah> | but i never used it with nvidia |
| 2026-01-29 22:20:14 +0100 | <L29Ah> | never had such on picom |
| 2026-01-29 22:16:32 +0100 | <liskin> | Maybe they fixed it in 2024, dunno, but it's been there for ages. Or perhaps it was in X11's damage reporting or something. But I don't see it any more, so I assume it got fixed somehow somewhere |
| 2026-01-29 22:15:15 +0100 | <liskin> | And when I say old I mean basically anything between like 2021 and 2025 or something, lol |
| 2026-01-29 22:14:49 +0100 | <liskin> | Enrico63: old picom used to do this |
| 2026-01-29 21:02:46 +0100 | <Enrico63> | But I don't remember if I asked here or in another room |
| 2026-01-29 21:02:29 +0100 | <Enrico63> | Oh, now that I think about it, recently I had indeed to do something video card related: https://archlinux.org/news/nvidia-590-driver-drops-pascal-support-main-packages-switch-to-open-ker… |
| 2026-01-29 21:00:29 +0100 | <geekosaur> | just placement and size |
| 2026-01-29 21:00:22 +0100 | <geekosaur> | likewise. xmonad doesn't control rendering of client windows in any way |
| 2026-01-29 20:58:02 +0100 | <L29Ah> | pretty sure the flickering will continue if you kill xmonad |
| 2026-01-29 20:57:25 +0100 | <L29Ah> | your gpu{, drivers} |
| 2026-01-29 20:55:15 +0100 | <Enrico63> | The problem not being the terminal, I'm asking here because I use xmonad |
| 2026-01-29 20:54:51 +0100 | <Enrico63> | Anybody has any idea what it could be? |
| 2026-01-29 20:54:50 +0100 | <Enrico63> | avoiding the bug using another terminal, I've realized that UXTerm suffers the same issue, https://streamable.com/tvj4g5, so the problem is not the terminal! |
| 2026-01-29 20:54:50 +0100 | <Enrico63> | Hello. I'm observing a very weird behavior in the terminal, recently, where the text start flickering like shown in this video: https://streamable.com/84cbyw. At the beginning of the video I'm in Vim, but as you can see towards the end, where I quit Vim, the flickering continues. Furthemore, while that screencast shows urxvt, in an attempt of |
| 2026-01-29 19:28:19 +0100 | Enrico63 | (~Enrico63@host-79-27-153-69.retail.telecomitalia.it) Enrico63 |
| 2026-01-29 17:31:05 +0100 | rekahsoft | (~rekahsoft@70.51.99.245) (Remote host closed the connection) |
| 2026-01-29 17:12:03 +0100 | rekahsoft | (~rekahsoft@70.51.99.245) rekahsoft |
| 2026-01-29 16:58:49 +0100 | ft | (~ft@p508db580.dip0.t-ipconnect.de) ft |
| 2026-01-29 15:34:40 +0100 | beastwick | (~brian@user/beastwick) (Quit: WeeChat 4.7.1) |
| 2026-01-29 14:48:56 +0100 | Enrico63 | (~Enrico63@host-79-27-153-69.retail.telecomitalia.it) (Quit: Client closed) |
| 2026-01-29 13:43:14 +0100 | Enrico63 | (~Enrico63@host-79-27-153-69.retail.telecomitalia.it) Enrico63 |
| 2026-01-29 12:16:00 +0100 | tv | (~tv@user/tv) tv |
| 2026-01-29 12:15:42 +0100 | tv | (~tv@user/tv) (Quit: derp) |
| 2026-01-29 11:00:23 +0100 | tremon | (~tremon@83.80.159.219) tremon |
| 2026-01-29 09:49:08 +0100 | Enrico63 | (~Enrico63@host-79-27-153-69.retail.telecomitalia.it) (Quit: Client closed) |
| 2026-01-29 08:44:52 +0100 | Enrico63 | (~Enrico63@host-79-27-153-69.retail.telecomitalia.it) Enrico63 |
| 2026-01-29 07:27:01 +0100 | rekahsoft | (~rekahsoft@70.51.99.245) (Ping timeout: 264 seconds) |
| 2026-01-29 07:24:43 +0100 | ft | (~ft@p508db580.dip0.t-ipconnect.de) (Quit: leaving) |
| 2026-01-29 07:20:12 +0100 | rekahsoft | (~rekahsoft@70.51.99.245) rekahsoft |
| 2026-01-29 06:32:52 +0100 | Solitary | (~Solitary@user/solitary) Solitary |
| 2026-01-29 06:30:09 +0100 | Solitary | (~Solitary@user/solitary) (Read error: Connection reset by peer) |
| 2026-01-29 05:06:19 +0100 | sajenim | (~sajenim@user/sajenim) (Ping timeout: 264 seconds) |
| 2026-01-29 04:44:34 +0100 | terrorjack | (~terrorjac@2a01:4f8:c17:9d11::) terrorjack |
| 2026-01-29 04:42:29 +0100 | terrorjack | (~terrorjac@2a01:4f8:c17:9d11::) (Quit: The Lounge - https://thelounge.chat) |
| 2026-01-29 03:31:47 +0100 | haskellbridge | (~hackager@96.28.224.214) hackager |
| 2026-01-29 03:29:41 +0100 | haskellbridge | (~hackager@96.28.224.214) (Remote host closed the connection) |
| 2026-01-29 00:31:09 +0100 | <geekosaur> | don't think we need to require registration any more |
| 2026-01-29 00:30:43 +0100 | geekosaur | -o geekosaur |
| 2026-01-29 00:30:37 +0100 | geekosaur | -r |
| 2026-01-29 00:30:13 +0100 | ChanServ | +o geekosaur |