Ugly shadows on menus in Chrome 119.0

[Filip-K]

Hi! I started experiencing the following picom shadow glitch after a recent Chrome update. Some menus (the three-dot, the right-click) have ugly transparent frames with shadows:

Interestingly, some menus are fine:

@kgilmer I remember we removed some shadow exceptions for Chrome in the picom config a while back, because they didn't seem necessary. Maybe it's time to bring them back? 😬 Anybody else experiencing the same issue?

[diffficult]

what shadow exceptions were those?

[Filip-K]

I can't remember and I couldn't find the right commit. I'm not even sure in which repo to look, as the picom config apparently hopped between repos a few times. In either case, these exceptions were (from what I remember) disabling shadows for all Chrome windows, so even if they would solve this issue, it wouldn't be a good long term solution.

[aav]

can confirm the same issue:

[jq-compose]

For others that hit this discussion from a search engine, adding a compositor (e.g. picom) may fix this. I'm seeing the same issue in NixOS / i3 window manager (with no compositor).

Reddit thread with the same problem described:

https://www.reddit.com/r/linuxquestions/comments/17sq1hv/how_to_disable_chrome_context_menu_border/

Quote from a comment in that thread with a solution for Debian:

I had the same problem on Debian 11 KDE and i3-wm.

I solved it by installing picom

(sudo apt-get -y install picom)

and adding this line to the "~/.config/i3/config" file:

exec --no-startup-id picom

to start it automatically

For NixOS, some options may be:

https://rycee.gitlab.io/home-manager/options.html#opt-services.picom.enable

Edit: I can confirm that using picom on NixOS solves my problem. After re-reading this thread, it's probably not related to this specific problem though. Sorry for the noise and getting off topic here.

[Filip-K]

Thanks for chiming in! This is related but not exactly the same issue. Running without picom gives a solid-color frame

And adding picom (but disabling shadows) solves it

But if you run picom with shadows (the default in regolith), you get this and that's mostly what the issue is about

[teaper]

在 /etc/xdg/picom.conf 中设置 menu = { shadow = false; } 可以解决

wintypes:
{
  tooltip = { fade = true; shadow = true; opacity = 0.75; focus = true; full-shadow = false; };
  dock = { shadow = false; clip-shadow-above = true; }
  dnd = { shadow = false; }
  menu        = { shadow = false; }
  popup_menu = { opacity = 0.8; }
  dropdown_menu = { opacity = 0.8; }
};

[p3k]

Still struggling to exclude Chrome browser with the shadow-exclude setting…

I tried these settings and some variations of it:

shadow-exclude = [
  "name *?= 'chrome'";
  "class_i *?= 'chrome'";
  "_NET_WM_NAME@:s *?= 'chrome'";
];

(See https://man.archlinux.org/man/picom.1)

Any more suggestions?

[fahmidbinfarooqui]

I am using Wayland. Will the same thing apply?

[kgilmer]

@fahmidbinfarooqui , no in this case picom is used only by the X11 Regolith session. The wayland session does not utilize this type of component.

[kgilmer]

@teaper & @Filip-K and others interested in this change , would you consider these picom config changes to be generally useful? I opened a PR for comments: regolith-linux/regolith-compositor-picom-glx#11

[fahmidbinfarooqui]

@fahmidbinfarooqui , no in this case picom is used only by the X11 Regolith session. The wayland session does not utilize this type of component.

I have the same problem in Hyprland. Can you tell me what to do?

[waldo2810]

This is working in picom vgit-b700a:

wintypes:
{
  menu = { shadow = false; blur-background = false;}
};

[kbc8090]

yea blur-background = false was it