GNOME Bugzilla – Bug 738511
Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE
Last modified: 2014-10-23 13:35:22 UTC
I am running wnck, bamf together with plank on a plain Openbox system. In my journalctl log I receive hundreds of the following messages: Okt 13 21:53:59 thinkpad org.ayatana.bamf[1140]: (bamfdaemon:1208): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE Okt 13 21:54:41 thinkpad org.ayatana.bamf[1140]: (bamfdaemon:1208): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE Okt 13 21:55:26 thinkpad org.ayatana.bamf[1140]: (bamfdaemon:1208): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE Okt 13 21:56:03 thinkpad org.ayatana.bamf[1140]: (bamfdaemon:1208): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE Okt 13 22:00:38 thinkpad org.ayatana.bamf[1140]: (bamfdaemon:1208): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE I tried to discuss the issue at the bamf bugtracker but have not received any response there yet [1]. [1] https://bugs.launchpad.net/bamf/+bug/1368805 On the Arch Linux bugtracker I was pointed out that this is not a bamf issue but related to wnck [2]. [2] https://bugs.archlinux.org/task/42366#comment128623 As far as I understand the error message correctly, wnck does not support WMs such as Openbox. Could this support be added to avoid these error messages? Additional info: * package version(s) * config and/or log files etc. bamf 0.5.0-3 plank-bzr r1094-1 openbox 3.5.2-7 libwnck 2.30.7-2 libwnck3 3.4.9-1
I don't think this is actually a warning you should care about. This action is not supported but by OpenBox, and there's no much more we should do at libwnck level. So I think is quite safe to ignore it.
@Marco Should/can something be done at the Openbox level? I would be perfectly fine with ignoring it if it was only a few of these warnings, but it is bloating up my journal log extensively,
At our level we might deescalate the message to debug level maybe, but still I guess you just have to set the G_MESSAGE_DEBUG var at the proper level to filter these out.
> At our level we might deescalate the message to debug level maybe, Would be very much appreciated, thank you. > guess you just have to set the G_MESSAGE_DEBUG var at the proper level to filter these out. Could you give me an example how to do this? I checked the web but could not find any relevant information on the proper use of G_MESSAGE_DEBUG.