GNOME Bugzilla – Bug 455581
libwnck complains about unhandled actions
Last modified: 2018-01-24 13:41:10 UTC
Hi, Kacper Wysocki reported in Debian bug http://bugs.debian.org/431682: """ when using a window manager that uses actions which libwnck doesn't know about, like say openbox 3.4 in combination with rox and TaskTray, libwnck complains very loudly: (TaskTray:9403): Wnck-WARNING **: Unhandled action type (nil) (TaskTray:9403): Wnck-WARNING **: Unhandled action type (nil) (TaskTray:9403): Wnck-WARNING **: Unhandled action type (nil) (TaskTray:9403): Wnck-WARNING **: Unhandled action type (nil) ... ad nauseum AFAIU new actions are being hammered out all the time by the fine folks at xorg and gnome, so I suggest the messages be throttled, or ideally, removed, as in the attached patch. """ The proposed patch simply removes the message, e.g.: - else - { - const char *name = _wnck_atom_name (atoms [i]); - g_warning ("Unhandled action type %s", name ? name: "(nil)"); - } - so I'm not attaching it. Bye,
(In reply to comment #0) > Hi, > > Kacper Wysocki reported in Debian bug http://bugs.debian.org/431682: > """ > when using a window manager that uses actions which libwnck doesn't > know about, like say openbox 3.4 in combination with rox and TaskTray, > libwnck complains very loudly: > > (TaskTray:9403): Wnck-WARNING **: Unhandled action type (nil) > (TaskTray:9403): Wnck-WARNING **: Unhandled action type (nil) > (TaskTray:9403): Wnck-WARNING **: Unhandled action type (nil) > (TaskTray:9403): Wnck-WARNING **: Unhandled action type (nil) > ... ad nauseum > > AFAIU new actions are being hammered out all the time by the fine > folks at xorg and gnome, so I suggest the messages be throttled, or > ideally, removed, as in the attached patch. > """ Hrm, I don't think there are often new actions. It'd be useful to know which atom is triggering those warnings. Is it possible to see the output of "xprop | grep _NET_WM_ALLOWED_ACTIONS" for TaskTray?
Hmm, the problem is better described here, on the openbox mailing list: http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?24:mss:4487:200705:kdlpgelkidhpbhlecegn and it's due to openbox defining its own actions, eg _OB_WM_ACTION_UNDECORATE, and openbox dev Dana Jansens recommends just ignoring the wnck messages. However, running a ROX desktop the X message log is very visible (which is intrusive, but very useful if it's not spammed). Considering the message repeats 1000s of times, and it's not all that useful to know about unhandled actions, the message could be disabled or throttled. The asked-for info: xprop | grep _NET_WM_ALLOWED_ACTIONS (standalone) _NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_CLOSE, _NET_WM_ACTION_MOVE, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_ABOVE, _NET_WM_ACTION_BELOW, _OB_WM_ACTION_UNDECORATE (rox panel applet) _NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_BELOW
Hi, how's it going with this issue? This is in effect an interoperability issue, which several people are having. Is there any problem with the suggested behaviour? _K
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/libwnck/issues/92.