Logs: liberachat/#xmonad
| 2023-07-27 00:11:39 | → | Guest667 joins (~lol@211.sub-174-215-144.myvzw.com) |
| 2023-07-27 00:11:41 | × | Guest667 quits (~lol@211.sub-174-215-144.myvzw.com) (Excess Flood) |
| 2023-07-27 00:13:38 | → | Guest667 joins (~lol@211.sub-174-215-144.myvzw.com) |
| 2023-07-27 00:13:59 | <geekosaur[c]> | Hm, voice typing on my watch butchered that a bit |
| 2023-07-27 00:15:27 | <ChaoticMist[m]> | No worries ;) |
| 2023-07-27 00:21:41 | <geekosaur[c]> | Anyway we're all a little broken around here, even if only situationally (mc47 got sandbagged by life) |
| 2023-07-27 00:23:25 | <ChaoticMist[m]> | And that is just part of life I reckon, have yet to find someone who is completely happy in this world.. lol |
| 2023-07-27 00:23:41 | <ChaoticMist[m]> | @absta:matrix.org did you manage to get picom working? |
| 2023-07-27 00:23:41 | <lambdabot> | Unknown command, try @list |
| 2023-07-27 00:23:45 | <absta[m]> | So here's my picom.conf:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/b8b030e25a158e572eca6832e10910734cc4bba9>) |
| 2023-07-27 00:24:12 | <absta[m]> | Could be a bit messy, as I am auto-generating it |
| 2023-07-27 00:24:23 | <ChaoticMist[m]> | absta[m]: Nix? |
| 2023-07-27 00:24:48 | <absta[m]> | No, programming & using my own settings manager program |
| 2023-07-27 00:25:11 | <ChaoticMist[m]> | Nix does all that :P |
| 2023-07-27 00:26:10 | <ChaoticMist[m]> | Did you try ~shadow = false~ ? |
| 2023-07-27 00:26:21 | <absta[m]> | I am trying it now. |
| 2023-07-27 00:31:18 | <absta[m]> | Turns out, shadow was not the culprit.. |
| 2023-07-27 00:32:27 | <absta[m]> | corner-radius wasn't, either. |
| 2023-07-27 00:32:29 | <geekosaur> | you verified it works without picom/pijulius? |
| 2023-07-27 00:33:33 | <absta[m]> | It worked when I fed picom the option -bcCGf, but let me check again. |
| 2023-07-27 00:33:35 | <ChaoticMist[m]> | geekosaur: did not notice that absta was using a picom fork.. mb |
| 2023-07-27 00:34:19 | <absta[m]> | I am using this one: <https://github.com/yshui/picom> |
| 2023-07-27 00:34:24 | <ChaoticMist[m]> | Why not just use https://github.com/dccsillag/picom ? |
| 2023-07-27 00:34:32 | <ChaoticMist[m]> | That picom fork is working fine for me |
| 2023-07-27 00:34:46 | <ChaoticMist[m]> | Can paste my config to for you to test if you want |
| 2023-07-27 00:35:11 | <ChaoticMist[m]> | absta[m]: That is not a fork, that is the official package |
| 2023-07-27 00:35:12 | <geekosaur> | mostly I was checking there in case you actually got stuck with an older xmonad that has a bug in the border color interpolation used by WindowNavigation that nukes the borders |
| 2023-07-27 00:35:40 | <geekosaur> | (0.17.0) |
| 2023-07-27 00:35:43 | <absta[m]> | Oh, because I just downloaded it from package manager. |
| 2023-07-27 00:36:35 | <absta[m]> | My freeze file says any.xmonad ==0.17.2, so it is likely up to date |
| 2023-07-27 00:38:44 | <ChaoticMist[m]> | That is indeed weird.. |
| 2023-07-27 00:39:20 | <ChaoticMist[m]> | Going to test your config brb |
| 2023-07-27 00:39:52 | <ChaoticMist[m]> | It works fine?? |
| 2023-07-27 00:40:19 | <ChaoticMist[m]> | Seems to me like your config is not the culprit of this.. |
| 2023-07-27 00:41:14 | <absta[m]> | picom -bcf --detect-rounded-corners -D 4 -I 0.02 -O 0.02 -e 0.8 works fine, it shows the xmonad's border. |
| 2023-07-27 00:41:39 | <absta[m]> | But when I run picom with the previously specified configuration, it just doesn't. |
| 2023-07-27 00:41:48 | <ChaoticMist[m]> | I only launched it with ~picom --config picom.conf~ |
| 2023-07-27 00:42:35 | <absta[m]> | Is -b option unnecessary? |
| 2023-07-27 00:42:55 | <geekosaur> | -b just puts it in the background. if you're using spawn then it's redundant |
| 2023-07-27 00:43:31 | <absta[m]> | ..So it is equivalent as `picom <options> &`? Hmmm |
| 2023-07-27 00:43:50 | <geekosaur> | the main difference is one you probably don't care about |
| 2023-07-27 00:44:21 | <geekosaur> | (shells track background processes with `&`, so you wouldn't be able to close a terminal you ran `picom … &` in) |
| 2023-07-27 00:44:53 | <ChaoticMist[m]> | I am running it as a systemd service |
| 2023-07-27 00:44:56 | <absta[m]> | Yea, but I spawn the bash script to run this soo |
| 2023-07-27 00:45:15 | <geekosaur> | it's not interactive so `-o monitor` won't be set |
| 2023-07-27 00:45:38 | <absta[m]> | Perhaps it is a fault of glx backend? |
| 2023-07-27 00:45:52 | <ChaoticMist[m]> | There is a new backend btw |
| 2023-07-27 00:45:53 | <absta[m]> | Actually let me try minimal example. |
| 2023-07-27 00:45:55 | <geekosaur> | I use glx backend here with no problems |
| 2023-07-27 00:46:01 | <ChaoticMist[m]> | And IIRC it was supposed to replace glx |
| 2023-07-27 00:46:26 | <ChaoticMist[m]> | egl backend iirc |
| 2023-07-27 00:46:34 | <absta[m]> | My VM does not seem to support egl, and I like testing my configuration in VM first. |
| 2023-07-27 00:47:14 | <geekosaur> | mrrr. have you tried this outside the VM? window borders rely on non-buggy display drivers… |
| 2023-07-27 00:47:40 | <absta[m]> | Ohh, actually |
| 2023-07-27 00:47:43 | <absta[m]> | Let me try that. |
| 2023-07-27 00:47:44 | <ChaoticMist[m]> | I don't even see a reason for using a VM for picom |
| 2023-07-27 00:48:06 | <ChaoticMist[m]> | You can easily kill the process without having xmonad die on you |
| 2023-07-27 00:48:16 | <geekosaur> | if anything I expect VM display drivers to meltdown with compositing |
| 2023-07-27 00:48:26 | <geekosaur> | and especially with compositing via opengl |
| 2023-07-27 00:49:04 | <ChaoticMist[m]> | Nix is wonderful for this tbh! If it goes south, revert to older generation |
| 2023-07-27 00:50:02 | <absta[m]> | I had to switch to xrender backend since picom leaks memory as hell on VM.. |
| 2023-07-27 00:53:11 | <absta[m]> | RIP |
| 2023-07-27 00:53:15 | <absta[m]> | It works on real hardware.. |
| 2023-07-27 00:54:02 | <absta[m]> | But I am experiencing a weird flickering issue. |
| 2023-07-27 00:54:59 | <absta[m]> | I suspect the borders |
| 2023-07-27 00:55:05 | <ChaoticMist[m]> | because? |
| 2023-07-27 00:55:19 | <absta[m]> | The flicker has the color of border. |
| 2023-07-27 00:55:41 | <absta[m]> | That is, white and red on the place with border |
| 2023-07-27 00:55:46 | <absta[m]> | Black on the place without. |
| 2023-07-27 00:56:32 | <geekosaur> | odd |
| 2023-07-27 00:56:36 | <ChaoticMist[m]> | What does picom tell you when you run it from the terminal? |
| 2023-07-27 00:57:11 | <absta[m]> | Well just running picom gives [ 07/27/2023 09:56:53.351 session_init FATAL ERROR ] Another composite manager is already running obviously. |
| 2023-07-27 00:57:25 | <absta[m]> | Or.. could you elaborate? |
| 2023-07-27 00:57:45 | <absta[m]> | Actually let me try enabling vsync |
| 2023-07-27 00:57:47 | <ChaoticMist[m]> | Kill the running picom and run a new one from terminal |
| 2023-07-27 00:58:46 | <geekosaur> | also note if the border flickering stops when you kill it… |
| 2023-07-27 00:59:01 | <absta[m]> | It stops, indeed |
| 2023-07-27 00:59:38 | <geekosaur> | weird |
| 2023-07-27 01:00:47 | <geekosaur> | do you have --use-ewmh-active-win ? |
| 2023-07-27 01:00:50 | <absta[m]> | Launched picom from terminal with just --backend glx. Flickering does not occur as well. |
| 2023-07-27 01:01:37 | <absta[m]> | Yes I have --use-ewmh-active-win in my config file. |
| 2023-07-27 01:02:10 | <ChaoticMist[m]> | hmmm |
| 2023-07-27 01:02:18 | <ChaoticMist[m]> | Does it complain about something? |
| 2023-07-27 01:02:34 | <ChaoticMist[m]> | If not, try enabling disabling stuff and see what triggers it |
| 2023-07-27 01:03:06 | <absta[m]> | It complains a lot, yep |
| 2023-07-27 01:03:22 | <absta[m]> | Things like [ 07/27/2023 10:03:06.610 glx_bind_pixmap ERROR ] Failed to query info of pixmap 0x012006d2. |
| 2023-07-27 01:03:34 | <absta[m]> | Or Xlib: ignoring invalid extension event 161 |
| 2023-07-27 01:04:07 | <ChaoticMist[m]> | I wonder if picom itself is behind this.. |
| 2023-07-27 01:04:35 | <ChaoticMist[m]> | Haven't used latest (master) since I switched to this fork. Because of this, I cannot tell for sure.. |
| 2023-07-27 01:06:07 | <absta[m]> | Currently, I am using picom version 9.1 |
| 2023-07-27 01:06:13 | <absta[m]> | So.. not the latest either. |
| 2023-07-27 01:07:25 | absta[m] | sent a code block: https://libera.ems.host/_matrix/media/v3/download/libera.chat/7d1ec4242d29675ec9d614d71af9f24f52b51452 |
| 2023-07-27 01:07:34 | <absta[m]> | This part is the problem, it starts flickering when I added this. |
| 2023-07-27 01:08:03 | <absta[m]> | And without that part, it does not flicker |
| 2023-07-27 01:08:37 | <ChaoticMist[m]> | Try disabling the shadow |
| 2023-07-27 01:08:56 | <geekosaur> | https://github.com/geekosaur/xmonad.hs/blob/skkukuk/compton.conf#L27-L33 fwiw |
| 2023-07-27 01:09:10 | <geekosaur> | (using with picom as shipped with ubuntu 22.04) |
| 2023-07-27 01:09:21 | <ChaoticMist[m]> | woah |
| 2023-07-27 01:09:23 | <absta[m]> | Pinpointed the culprit:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/6ea56eada8fd3fda0759beb9beab1734e1bbf595>) |
| 2023-07-27 01:09:47 | <absta[m]> | Idk what is wrong with tooltip.. |
All times are in UTC.