Public bug reported: [Impact] Xprop added support for UTF8_STRING back in 2009: http://cgit.freedesktop.org/xorg/app/xprop/commit/?id=eb64005382abf6262c913a46e6186e019a179d59
Unfortunately `xprop -f 8u -set` has been broken until 2012: http://cgit.freedesktop.org/xorg/app/xprop/commit/?id=0d069c0edae83f70ac10fab1a3c04d8197e277c4 That patch has not been backported to Ubuntu 12.04.1 (x11-utils 7.6+4), so it's impossible to use "8u" there. One notable use case is with LTSP, where we're using xprop as an ad-hoc mechanism for server<=>thin clients communication, and we were recently asked to add UTF8 support to it: https://bugs.launchpad.net/ltsp/+bug/1451915 [Test Case] This is how to reproduce the issue on Precise 12.04.1: $ lsb_release -r Release: 12.04 $ dpkg-query -W x11-utils x11-utils 7.6+4ubuntu0.1 $ xprop -root -f LTSP_COMMAND 8u -set LTSP_COMMAND xterm xprop: error: bad format character: u This is what the correct output looks like on Trusty 14.04.2: $ lsb_release -r Release: 14.04 $ dpkg-query -W x11-utils x11-utils 7.7+1 $ xprop -root -f LTSP_COMMAND 8u -set LTSP_COMMAND xterm <no output, no error> $ xprop -root | grep LTSP_COMMAND LTSP_COMMAND(UTF8_STRING) = "xterm" [Regression Potential] Low, the patch comes from upstream and it's already included in all Ubuntu versions after 12.04.1. ** Affects: x11-utils (Ubuntu) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463663 Title: [SRU] Enable setting property of type UTF8_STRING To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1463663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
