However, this bug is fixed in 15.04's python3-xlib 0.14+20091101-1ubuntu3. The date (17 Mar 2015) suggests it would have shipped with 15.04 (i.e. not be a later update), but I guess it could be.
Can anyone confirm they see this bug with 15.04 or later with up-to-date packages?
I'm now using the LTS vivid X stack on my 14.04 machine and am getting this error, which appears to be caused by a python3-xlib bug: https:/ /github. com/LiuLang/ python3- xlib/issues/ 6
However, this bug is fixed in 15.04's python3-xlib 0.14+20091101- 1ubuntu3. The date (17 Mar 2015) suggests it would have shipped with 15.04 (i.e. not be a later update), but I guess it could be.
Can anyone confirm they see this bug with 15.04 or later with up-to-date packages?