Caffeine can't connect to display since updating Trusty to Vivid kernel and X (HWE)

There is a fix that can be imported: https://github.com/ntrrgc/python3-xlib/commit/59da8450fdfc4c794307299c378cd7c38efaab9d

Dear whoever subscribed the Debian Python Modules Team to this bug:

Please don't do such a thing again. If there is a bug that's also present in Debian, please file a bug in the Debian BTS and then link it to the Ubuntu bug.

The change I just did to the bug status was not my intention. So thousand times sorry.
I was not aware I could change this status, but I'm not allowed to reverse the change and set the status back to "Fix Committed".
Can the bug supervisor please reverse my change.

This bug was fixed in the package python-xlib - 0.14+20091101-4

---------------
python-xlib (0.14+20091101-4) unstable; urgency=medium

  * Do proper string-bytes conversion (LP: #1482844).
  * Drop README.source.

 -- Andrew Shadura <email address hidden> Tue, 18 Aug 2015 10:30:44 +0200

Fixed package seems to imported into Wily only.

Can someone initiate process of updating Trusty and Vivid packages?

Seems like the problem is solved in python-xlib - 0.14+20091101-4

Those two patches are conflicting: fix-auth-lp1482844.patch and lp1432889.patch.
Each one of them solves the problem when applied without the other.

FWIW, the current version of python-xlib in debian testing (0.14+20091101-4) completely broke the package for me: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796889

FTR, the latest version (0.14+20091101-5) in the Debian Unstable repos appears to have fixed my aforementioned issue.
Thanks, Andrew.

Can this be fixed in Trusty with Vivid kernel and X (HWE - LTS Enablement Stacks) please ?
https://wiki.ubuntu.com/Kernel/LTSEnablementStack

I also have this bug, when are you going to fix it in Trusty with Vivid kernel and X stack?

Will it be fixed in Trusty with Vivid kernel and X stack?

This bug was fixed in the package python-xlib - 0.14+20091101-5

---------------
python-xlib (0.14+20091101-5) unstable; urgency=medium

  * Fix LP: #1482844 properly: lp1432889.patch is incompatible with
    fix-auth-lp1482844.patch (Closes: #796889).

 -- Andrew Shadura <email address hidden> Tue, 25 Aug 2015 16:18:06 +0200

Hello guys,

I'm a Debian Developer, and while I use Ubuntu too, I honestly haven't got any idea how to backport packages from Debian unstable to already released versions of Ubuntu (as opposed to the current release in development, where it usually migrates automatically). If you know who should I prod, please let me know.

The bug report is about Trusty with Vivid kernel and X stack, so the status can't be "Fix Released" until it's released for Trusty with Vivid kernel and X stack.

Can somebody backport the fixed python-xlib package in Trusty with Vivid kernel and X stack please ?

python3-xlib_0.14+20091101-1ubuntu3_all.deb didn't solve the issue. I receive:

Traceback (most recent call last):
  File "/usr/bin/caffeine", line 36, in <module>
    ewmh = EWMH()
  File "/usr/lib/python3/dist-packages/ewmh.py", line 50, in __init__
    self.display = _display or display.Display()
  File "/usr/lib/python3/dist-packages/Xlib/display.py", line 80, in __init__
    self.display = _BaseDisplay(display)
  File "/usr/lib/python3/dist-packages/Xlib/display.py", line 62, in __init__
    display.Display.__init__(*(self, ) + args, **keys)
  File "/usr/lib/python3/dist-packages/Xlib/protocol/display.py", line 129, in __init__
    raise error.DisplayConnectionError(self.display_name, r.reason)
Xlib.error.DisplayConnectionError: Can't connect to display ":0": b'Invalid MIT-MAGIC-COOKIE-1 key'

Old python3-xlib_0.14+20091101-1ubuntu2_all.deb returns:

Traceback (most recent call last):
  File "/usr/bin/caffeine", line 36, in <module>
    ewmh = EWMH()
  File "/usr/lib/python3/dist-packages/ewmh.py", line 50, in __init__
    self.display = _display or display.Display()
  File "/usr/lib/python3/dist-packages/Xlib/display.py", line 80, in __init__
    self.display = _BaseDisplay(display)
  File "/usr/lib/python3/dist-packages/Xlib/display.py", line 62, in __init__
    display.Display.__init__(*(self, ) + args, **keys)
  File "/usr/lib/python3/dist-packages/Xlib/protocol/display.py", line 129, in __init__
    raise error.DisplayConnectionError(self.display_name, r.reason)
Xlib.error.DisplayConnectionError: Can't connect to display ":0": b'No protocol specified\n'

ubuntu 14.04 lts with 3.19.0-30-generic kernel from vivid and xserver-xorg-lts-vivid 1:7.7+7ubuntu3~trusty1

python3-xlib_0.14+20091101-5_all.deb doesn't fix the issue too:

Traceback (most recent call last):
  File "/usr/bin/caffeine", line 36, in <module>
    ewmh = EWMH()
  File "/usr/lib/python3/dist-packages/ewmh.py", line 50, in __init__
    self.display = _display or display.Display()
  File "/usr/lib/python3/dist-packages/Xlib/display.py", line 80, in __init__
    self.display = _BaseDisplay(display)
  File "/usr/lib/python3/dist-packages/Xlib/display.py", line 62, in __init__
    display.Display.__init__(*(self, ) + args, **keys)
  File "/usr/lib/python3/dist-packages/Xlib/protocol/display.py", line 129, in __init__
    raise error.DisplayConnectionError(self.display_name, r.reason)
Xlib.error.DisplayConnectionError: Can't connect to display ":0": b'Invalid MIT-MAGIC-COOKIE-1 key'

rm .Xauthority and relogin has solved the issue. used python3-xlib_0.14+20091101-1ubuntu3_all.deb

Again, can somebody backport the fixed python-xlib package in Trusty with Vivid kernel and X stack please ?

No one can backport the fixed python-xlib package in Trusty with Vivid kernel and X stack ?

I don't think so. Why don't you upgrade to the latest version of the distribution?

Meanwhile, if you have ‘Trusty with Vivid kernel and X stack’ as you say, this is unsupported combination anyway.

The LTS is supported for 5 years (2019) so no need to upgrade. This is not a good advice...

Trusty with Vivid kernel and X stack is a supported combination:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack

In any case, posting here every two weeks won't help your issue. You need to find people responsible for backporting and talk to them directly.

Maybe I will but we should not have to do that. It is the purpose of a bug report.

I'm uploading the vivid 0.14+20091101-1ubuntu3 update to trusty

Hello jeremy, or anyone else affected,

Accepted python-xlib into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python-xlib/0.14+20091101-1ubuntu3~trusty 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!

Hello Brian,

I tested the proposed package and it works !

Thank you very much.

Hello Brian,

I think you can add the package in the ubuntu repo now.

Thanks

This bug was fixed in the package python-xlib - 0.14+20091101-1ubuntu3~trusty

---------------
python-xlib (0.14+20091101-1ubuntu3~trusty) trusty; urgency=medium

  * Upload fix to trusty as well (lp: #1482844)

  [ Marc Deslauriers ]
  * debian/patches/lp1432889.patch: properly decode the xauthority file
    into strings instead of byte arrays in Xlib/xauth.py.

 -- Sebastien Bacher <email address hidden> Tue, 10 Nov 2015 11:46:01 +0100

The verification of the Stable Release Update for python-xlib 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.