[SRU] Enable setting property of type UTF8_STRING

Bug #1463663 reported by Alkis Georgopoulos
This bug affects 1 person
Affects Status Importance Assigned to Milestone
x11-utils (Ubuntu)
Fix Released
Alberto Milone
Fix Released

Bug Description

Xprop added support for UTF8_STRING back in 2009:

Unfortunately `xprop -f 8u -set` has been broken until 2012:

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:

[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

[Regression Potential]
Low, the patch comes from upstream and it's already included in all Ubuntu versions after 12.04.1.

Changed in x11-utils (Ubuntu):
status: New → In Progress
importance: Undecided → Medium
Revision history for this message
Alberto Milone (albertomilone) wrote :

Please accept x11-utils_7.6+4ubuntu0.2 into the precise-proposed repository.

Revision history for this message
Adam Conrad (adconrad) wrote : Please test proposed package

Hello Alkis, or anyone else affected,

Accepted x11-utils into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/x11-utils/7.6+4ubuntu0.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-needed
Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

I've verified that x11-utils 7.6+4ubuntu0.2 works as expected in Ubuntu 12.04.1, please push it to precise-updates.

tags: added: verification-done
removed: verification-needed
Chris J Arges (arges)
Changed in x11-utils (Ubuntu):
status: In Progress → Fix Released
Changed in x11-utils (Ubuntu Precise):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package x11-utils - 7.6+4ubuntu0.2

x11-utils (7.6+4ubuntu0.2) precise-proposed; urgency=medium

  * Add 101_xprop_bad_format_character_utf8_string.patch: Fix xprop
    bad format character error whn using UTF-8 strings.
    (LP: #1463663)

 -- Alberto Milone <email address hidden> Thu, 11 Jun 2015 09:45:25 +0200

Changed in x11-utils (Ubuntu Precise):
status: Fix Committed → Fix Released
Revision history for this message
Chris J Arges (arges) wrote : Update Released

The verification of the Stable Release Update for x11-utils has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers