Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#38726 - [ratpoison] Spurious "XGetWMName failed" messages
Attached to Project:
Community Packages
Opened by Hest Snorre (h3st) - Thursday, 30 January 2014, 14:51 GMT
Last edited by Kyle Keen (keenerd) - Sunday, 02 February 2014, 00:22 GMT
Opened by Hest Snorre (h3st) - Thursday, 30 January 2014, 14:51 GMT
Last edited by Kyle Keen (keenerd) - Sunday, 02 February 2014, 00:22 GMT
|
DetailsDescription:
ratpoison fills the system logs with ratpoison:manage.c:236: error: XGetWMName failed This appears to be due to a dev forgetting to set it to PRINT_DEBUG rather than PRINT_ERROR. Additional info: * ratpoison 1.4.6 * there is a patch: http://openbsd.7691.n7.nabble.com/PATCH-get-rid-of-nasty-quot-XGetWMName-failed-quot-error-message-td227418.html Steps to reproduce: Use ratpoison 1.4.6. Attempt to view logs, i.e. journalctl. See window filled with "XGetWMName failed" messages. |
This task depends upon
Closed by Kyle Keen (keenerd)
Sunday, 02 February 2014, 00:22 GMT
Reason for closing: Fixed
Additional comments about closing: 1.4.6-2
Sunday, 02 February 2014, 00:22 GMT
Reason for closing: Fixed
Additional comments about closing: 1.4.6-2
Comment by Kyle Keen (keenerd) -
Sunday, 02 February 2014, 00:21 GMT
That link 404s for me.