wmaker[1147]: (wGetColorForColormap(resources.c:45)): warning: could not allocate color

[pfred1]

I don't know if this is a bug but it sure bugs me. Every time when I start GZDoom I get these messages in my syslog:

Oct 19 11:17:18 box1 wmaker[1147]: (wGetColorForColormap(resources.c:45)): warning: could not allocate color "#000000"
Oct 19 11:17:18 box1 wmaker[1147]: (wGetColorForColormap(resources.c:45)): warning: could not allocate color "#000000"
Oct 19 11:17:18 box1 wmaker[1147]: (wGetColorForColormap(resources.c:45)): warning: could not allocate color "#f3f3f3"

How do I make that stop? I'm sure someone must know. That someone just isn't me. I've looked for a solution. Anyways any help would be appreciated. Thanks.

[crmafra]

On Sat, 19 Oct 2024 at 8:30:23 -0700, pfred1 wrote: I don't know if this is a bug but it sure bugs me. Every time when I start GZDoom I get these messages in my syslog: Oct 19 11:17:18 box1 wmaker[1147]: (wGetColorForColormap(resources.c:45)): warning: could not allocate color "#000000" Oct 19 11:17:18 box1 wmaker[1147]: (wGetColorForColormap(resources.c:45)): warning: could not allocate color "#000000" Oct 19 11:17:18 box1 wmaker[1147]: (wGetColorForColormap(resources.c:45)): warning: could not allocate color "#f3f3f3" How do I make that stop? I'm sure someone must know. That someone just isn't me. I've looked for a solution. Anyways any help would be appreciated. Thanks.

A fix for this has been merged in repo.or.cz/w/wmaker-crm.git commit 67e2f5e Author: David Maciejak ***@***.***> Date: Thu Dec 25 16:19:05 2025 -0500 Prevent XAllocColor() call on TrueColor display As reported in bug #50 X11 XAllocColor() call from wGetColorForColormap() in src/resources.c is returning some errors especially seen when running GZDoom. TrueColor display has been the dominant standard for well over a decade, meaning almost all modern X servers default to a TrueColor visual. The default colormap is predefined and read-only, making allocation with XAllocColor() unnecessary (and meaning no need to free it too). The patch is checking the display visual, and in case the display is truecolor, it does not allocate or free the color, just looking up for it. Once the patch applied, GZDoom is not reporting warnings anymore.