[Solved] Conflict - picom & xfwm4

barnd3 · 2025-07-11 11:32:31

When I start picom, xfwm spams me with .xsession-errors.

(xfwm4:827): GLib-CRITICAL **: 20:33:35.275: g_hash_table_lookup: assertion 'hash_table != NULL' failed

How can I fix the error or prevent logging

Last edited by barnd3 (2025-07-12 15:25:31)

stfischr · 2025-07-11 14:07:29

Hi.
Looks like an error with picom https://github.com/yshui/picom/issues/1441 maybe you can jump in that bug report to move it forward but the project does seem to have very low activity lately.

barnd3 · 2025-07-11 14:39:06

Yes, the message is from me.
I thought no one would care anymore, so I posted here.

seth · 2025-07-11 16:39:22

Did you disable the https://wiki.archlinux.org/title/Xfwm#Composite_manager ?

barnd3 · 2025-07-11 18:32:57

Yes, I have it disabled

seth · 2025-07-11 19:48:53

The bug isn't w/ picom, you'll need to address xwfm4 (which is where the message is coming from)
=> https://gitlab.xfce.org/xfce/xfwm4/-/issues/855
https://gitlab.xfce.org/xfce/xfwm4/-/bl … tor.c#L180 looks suspicious

Do you get this w/o picom and just deactivating the xfwm4 compositor?

barnd3 · 2025-07-11 20:57:59

So if I understand you correctly, the effects with picom are not the same as with xfwm

barnd3 · 2025-07-12 02:19:53

https://gitlab.xfce.org/xfce/xfwm4/-/issues/855
Unfortunately, I can't log in or register there to report my error...

Last edited by barnd3 (2025-07-12 02:21:55)

seth · 2025-07-12 08:11:01

picom is a compositor for X11, xfwm4 is an X11 window manager (from the xfce project) that also happens to have a compositor which might get instantiated despite being disabled.

seth wrote:

Do you get this w/o picom and just deactivating the xfwm4 compositor?

The xfwm4 compositor might check for *an* active compositor (instead of actually this being itself) or just unconditionally activate and I'd like to sort that out to help the xfce4 devs to isolate the bug.

Also, how frequent are those messages? Do they show up 60 times per second or whenever you minimize a window or … etc?

upstream bug wrote:

Moreover, I noticed that each time I change windows, another line like the previous one is written.

In doubt post your xsession errors.

Unfortunately, I can't log in or register there to report my error...

The Xfce maintainer is on this forum, but we'll track this down a bit before pinging him in.

barnd3 · 2025-07-12 08:57:38

So, the xfce compositer, when enabled, doesn't produce any errors. If I disable the compositer and enable picom, this error is logged in the .xsession-errors file every second. The error is logged without any activity. I've tried all possible picom versions out there, and it's always the same.

seth · 2025-07-12 09:01:28

The point is to DISable the xfwm4 compositor and NOT run picom and see whether you STILL get those errors, ie. whether this is down to the xfce4 compositor being disabled or another compositor running.

barnd3 · 2025-07-12 09:26:40

If I have not activated a compositer, i.e. xfwm and picom are not running, no error is generated

seth · 2025-07-12 09:34:10

Of course there will be no xfwm4 error when xfwm4 isn't running at all.
You still need to happily run the WM uncomposited (ie. normal XFCE session w/o any transparency or shadows but nice titlebars)

But looking at the xfwm4 history:
https://gitlab.xfce.org/xfce/xfwm4/-/co … 272db58b3a
This is supposed to be already fixed, it's just that https://archlinux.org/packages/extra/x86_64/xfwm4/ the last release is from last december and the fix only applied this february.
=> https://aur.archlinux.org/packages/xfwm4-git

barnd3 · 2025-07-12 10:03:03

Yes I did - no mistake

seth · 2025-07-12 14:53:38

Did you test whether xfwm4-git already fixes this?

barnd3 · 2025-07-12 15:14:04

It works with xfwm4.git, the bug seems to have been fixed...

seth · 2025-07-12 15:15:23

By the linked commit, yes.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

barnd3 · 2025-07-12 15:25:05

I thank you

Arch Linux

#1 2025-07-11 11:32:31

[Solved] Conflict - picom & xfwm4

#2 2025-07-11 14:07:29

Re: [Solved] Conflict - picom & xfwm4

#3 2025-07-11 14:39:06

Re: [Solved] Conflict - picom & xfwm4

#4 2025-07-11 16:39:22

Re: [Solved] Conflict - picom & xfwm4

#5 2025-07-11 18:32:57

Re: [Solved] Conflict - picom & xfwm4

#6 2025-07-11 19:48:53

Re: [Solved] Conflict - picom & xfwm4

#7 2025-07-11 20:57:59

Re: [Solved] Conflict - picom & xfwm4

#8 2025-07-12 02:19:53

Re: [Solved] Conflict - picom & xfwm4

#9 2025-07-12 08:11:01

Re: [Solved] Conflict - picom & xfwm4

#10 2025-07-12 08:57:38

Re: [Solved] Conflict - picom & xfwm4

#11 2025-07-12 09:01:28

Re: [Solved] Conflict - picom & xfwm4

#12 2025-07-12 09:26:40

Re: [Solved] Conflict - picom & xfwm4

#13 2025-07-12 09:34:10

Re: [Solved] Conflict - picom & xfwm4

#14 2025-07-12 10:03:03

Re: [Solved] Conflict - picom & xfwm4

#15 2025-07-12 14:53:38

Re: [Solved] Conflict - picom & xfwm4

#16 2025-07-12 15:14:04

Re: [Solved] Conflict - picom & xfwm4

#17 2025-07-12 15:15:23

Re: [Solved] Conflict - picom & xfwm4

#18 2025-07-12 15:25:05

Re: [Solved] Conflict - picom & xfwm4

Board footer