Hi Francesco, I must have missed your reply...
On Wed, Oct 26, 2011 at 11:49:18PM +0200, Francesco Poli wrote: > tags 646368 + moreinfo > thanks > > > On Mon, 24 Oct 2011 23:55:04 +0200 Francesco Poli wrote: > > [...] > > Hence, apart from the error message that it spits out, it seems that > > apt-listbugs is able to go on and show me the bug report (in a text UI). > > I don't know why you get a different outcome... > [...] > > In summary: > > > > (A) I will probably add the "-u text" option to the querybts > > invocation, but this won't solve your issue > > (B) we have to understand why, in your case, querybts does not use > > the text interface, when invoked by apt-listbugs > > (C) after that, this bug report will be probably better reassigned to > > python-gtk2 and merged with #533824 > > > > Please help me with (B). > > Please help me to understand the behavior you see: when you query a > given bug number (such as 644254) from within the apt-listbugs > interface, do you only get the python-gtk2 warning about the failure to > open a display? > Or is apt-listbugs able to show you the bug report in a text interface, > after spitting out the warning? I am getting a bug report in a text interface but it thinks I'm in standalone mode and many of the functions do not work properly. --Joe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
