apt-listchanges fails when you are not allowed to use the DISPLAY

[Björn Torkelsson]

When running apt-listchanges with $DISPLAY set to an existing display which you
are not allowed to use, it fails with:

ankpelle[~]# /usr/bin/apt-listchanges -v -f pager
/archive/Ubuntu/devilspie_0.10-1_i386.deb
X11 connection rejected because of wrong authentication.
The application 'apt-listchanges' lost its connection to the display localhost:10.0;
most likely the X server was shut down or you killed/destroyed
the application.

and it does not fallback to the pager. AFAICT it fails when doing 'import gtk'.

[Björn Torkelsson (torkel)]

As I suck to write bugreports I forgot to mention that this is with
2.59-0.2ubuntu3, i.e the version currently in breezy and that the frontend is
set to mail.

It does not matter which frontend I use, if $DISPLAY is set to a display I'm not
allowed to use apt-listchanges fails. If $DISPLAY is unset or set to a
non-existant display it works as expected.

[Christian Reis (kiko)]

The hoary version of apt-listchanges didn't depend on gtk+, fwiw.

[Adam Israel (aisrael)]

Confirmed this bug exists in breezy. apt-listchanges always tries to import
pygtk and gtk (in apt_listchanges.py) no matter what frontend is selected

[Adam Israel (aisrael)]

I think pygtk/gtk shouldn't be imported unless the gtk frontend is actually
selected. I'd be happy to write this patch, if mvo doesn't object.

[Michael Vogt (mvo)]

Thanks for your bugreport.

Can you still confirm this problem in the current version of apt-listchanges (
2.59-0.2ubuntu4) in breezy? It should be more carefull about failed X display etc.

Cheers,
 Michael

[Michael Vogt (mvo)]

Just got a confirmation (via irc) that it's still there in ubuntu4.

[Michael Vogt (mvo)]

This problem should be fixed with the upload of:

apt-listchanges_2.59-0.2ubuntu5_source

please reopen if the problem does not go away for you.