debxo ohmd error

Lee Loncosky lloncosky200 at
Tue Apr 21 17:18:32 EDT 2009

I have an error with the ohmd, see below. Things seemed to work with pw button although I did not have a blinking power light for some reason.  The error may have happened when I closed the lid.  At least suspend did not work then either and then I noticed the debug error.

[ohm_conf_set_key_internal] ohm-conf.c:307 (20:55:20):	 set existing key 'button.power' : 0
[ohm_conf_set_key_internal] ohm-conf.c:316 (20:55:20):	 emit key-changed : button.power
[key_changed_cb] ohm-module.c:94 (20:55:20):	 key changed! button.power : 0
[key_changed_cb] ohm-module.c:104 (20:55:20):	 found watched key button.power
[key_changed_cb] ohm-module.c:109 (20:55:20):	 notify suspend with id:0
[ohm_plugin_conf_set_key] ohm-plugin.c:162 (21:05:17):	 plugin buttons setting key button.lid to 1
[ohm_conf_set_key_internal] ohm-conf.c:307 (21:05:17):	 set existing key 'button.lid' : 1
[ohm_conf_set_key_internal] ohm-conf.c:316 (21:05:17):	 emit key-changed : button.lid
[key_changed_cb] ohm-module.c:94 (21:05:17):	 key changed! button.lid : 1
[key_changed_cb] ohm-module.c:104 (21:05:17):	 found watched key button.lid
[key_changed_cb] ohm-module.c:109 (21:05:17):	 notify display with id:2
[ohm_plugin_conf_set_key] ohm-plugin.c:162 (21:05:17):	 plugin display setting key backlight.state to 0
[ohm_conf_set_key_internal] ohm-conf.c:307 (21:05:17):	 set existing key 'backlight.state' : 0
[ohm_conf_set_key_internal] ohm-conf.c:316 (21:05:17):	 emit key-changed : backlight.state
[key_changed_cb] ohm-module.c:94 (21:05:17):	 key changed! backlight.state : 0
[key_changed_cb] ohm-module.c:104 (21:05:17):	 found watched key backlight.state
[key_changed_cb] ohm-module.c:109 (21:05:17):	 notify dpms with id:0
** (ohmd:2136): DEBUG: Setting DPMS state
The program 'ohmd' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 11 error_code 8 request_code 137 minor_code 6)
  (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.)

Using Opera's revolutionary e-mail client:

More information about the Devel mailing list