This happens with xfce4-power-manager 1.0.10 on openSUSE, the details from the downstream report: upgraded 11.4 32bit to 12.1 milestone 5 64bit, [...] xfce4-power-manager --no-daemon (xfce4-power-manager:24940): xfce4-power-manager-WARNING **: could not map keysym 1008ffa8 to keycode The program 'xfce4-power-manager' received an X Window System error. This probably reflects a bug in the program. The error was 'BadName (named color or font does not exist)'. (Details: serial 273 error_code 15 request_code 150 minor_code 11) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) backtrace: #0 gdk_x_error (display=0x645000, error=0x7fffffffcdb0) at gdkmain-x11.c:458 #1 0x00007ffff550c447 in _XError (dpy=0x645000, rep=0x6d1440) at XlibInt.c:1573 #2 0x00007ffff5509301 in handle_error (dpy=0x645000, err=0x6d1440, in_XReply=<optimized out>) at xcb_io.c:166 #3 0x00007ffff550a257 in _XReply (dpy=0x645000, rep=0x7fffffffcf40, extra=0, discard=0) at xcb_io.c:623 #4 0x00007ffff5a1b48b in XRRQueryOutputProperty (dpy=0x645000, output=81, property=376) at XrrProperty.c:99 #5 0x0000000000418170 in xfpm_brightness_xrand_get_limit (brightness=<optimized out>, output=<optimized out>, min=0x7fffffffcfc8, max=0x7fffffffcfcc) at xfpm-brightness.c:69 #6 0x0000000000418489 in xfpm_brightness_setup_xrandr (brightness=0x6a7630 [XfpmBrightness]) at xfpm-brightness.c:187 #7 xfpm_brightness_setup (brightness=0x6a7630 [XfpmBrightness]) at xfpm-brightness.c:521 #8 0x0000000000412716 in xfpm_backlight_init (backlight=0x6c9040 [XfpmBacklight]) at xfpm-backlight.c:381 #9 0x00007ffff614fd83 in g_type_create_instance (type=<optimized out>) at gtype.c:1885 #10 0x00007ffff612f29c in g_object_constructor (type=<optimized out>, n_construct_properties=0, construct_params=0x0) at gobject.c:1629 #11 0x00007ffff6132232 in g_object_newv (object_type=7106960, n_parameters=0, parameters=0x0) at gobject.c:1412 #12 0x00007ffff6132dac in g_object_new (object_type=7106960, first_property_name=0x0) at gobject.c:1322 #13 0x000000000040ad50 in xfpm_manager_start (manager=0x666840 [XfpmManager]) at xfpm-manager.c:543 #14 0x0000000000408f75 in xfpm_start (bus=<optimized out>, client_id=0x0, dump=0) at xfpm-main.c:224 #15 0x00000000004095b3 in main (argc=1, argv=0x7fffffffd7c8) at xfpm-main.c:423 [...] everything was working fine on 11.4 32bit
This bug is critical, it makes the power manager completely unusable, and I've seen bug reports for it in several distribution bug trackers. My system is a x86_64 Arch Linux. I don't know what causes this, but as a temporary fix one can disable brightness control through XRandR, so the power manager falls back to the sysfs interface; I'll attach a patch that does this.
Created attachment 3896 Temporary workaround
Created attachment 3911 trap X errors A better workaround is to trap any X errors which is what gnome-power-manager does as well. Attached is a patch for that by Takashi Iwai from the downstream report.
It seems this wasn't applied for 1.0.11.
Adding Nick on CC: so he can see the patch.
Put traps around some more calls, applied in 5daee77.