Bug#433790: reportbug-ng: Freezes when fetching bugreports

2007-07-19 Thread David
Package: reportbug-ng
Version: 0.2007.07.18
Severity: grave
Justification: renders package unusable

When I enter the name of a package, Reportbug NG stays

Fetching bugreports for package reportbug-ng, please wait

forever and ever.

I also tried with other packages, and the same.

My network is behind a proxy, but previous versions of reportbug-ng used to 
work.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.21-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages reportbug-ng depends on:
ii  python2.4.4-6An interactive high-level object-o
ii  python-central0.5.14 register and build utility for Pyt
ii  python-qt33.17.2-1   Qt3 bindings for Python
ii  python-soappy 0.11.3-1.8 SOAP Support for Python (SOAP.py)
ii  xdg-utils 1.0.1-2Desktop integration utilities from

reportbug-ng recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#433790: reportbug-ng: Freezes when fetching bugreports

2007-07-19 Thread Bastian Venthur
On 19.07.2007 14:59 schrieb David:
 When I enter the name of a package, Reportbug NG stays
 
 Fetching bugreports for package reportbug-ng, please wait
 
 forever and ever.
 
 I also tried with other packages, and the same.

Please start rng in a console (xterm or something similar) with
debug-output enabled:

  rng --loglevel=debug

Then reproduce this bug and send me the console output.

 My network is behind a proxy, but previous versions of reportbug-ng used to 
 work.


There might be something wrong with the proxy-feature I've enabled a few
versions ago. Is the http_proxy environment variable set accordingly?
Please paste the output of

  echo $http_proxy

You can anonymize the IP or the domainname if you want, but I need the
exact output format, especially every occurrence of slashes or other non
alphabetical characters.

You should also try to start rng with the http_proxy variable temporary
unset:

  http_proxy='' rng

and tell me if this works for you.



Cheers,

Bastian


-- 
Bastian Venthur  http://venthur.de
Debian Developer venthur at debian org



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#433790: reportbug-ng: Freezes when fetching bugreports

2007-07-19 Thread David



Please start rng in a console (xterm or something similar) with
debug-output enabled:

  rng --loglevel=debug

Then reproduce this bug and send me the console output.




$ rng --loglevel=debug
root INFO Logger initialized with level debug.
MainWindow   INFO Logger initialized.
MainWindow   DEBUGneg: [], pos: [u'r']
MainWindow   DEBUGneg: [], pos: [u're']
MainWindow   DEBUGneg: [], pos: [u'rep']
MainWindow   DEBUGneg: [], pos: [u'repo']
MainWindow   DEBUGneg: [], pos: [u'repor']
MainWindow   DEBUGneg: [], pos: [u'report']
MainWindow   DEBUGneg: [], pos: [u'reportb']
MainWindow   DEBUGneg: [], pos: [u'reportbu']
MainWindow   DEBUGneg: [], pos: [u'reportbug']
MainWindow   DEBUGneg: [], pos: [u'reportbug-']
MainWindow   DEBUGneg: [], pos: [u'reportbug-n']
MainWindow   DEBUGneg: [], pos: [u'reportbug-ng']
MainWindow   DEBUGneg: [], pos: []
Unhandled exception in thread started by bound method
MyMainWindow.loadAllBugSummaries of ui.MyMainWindow.MyMainWindow object at
0xb64a3a2c
Traceback (most recent call last):
 File /usr/share/reportbug-ng/ui/MyMainWindow.py, line 181, in
loadAllBugSummaries
   bugs = DebianBTS.getBugsByQuery(query)
 File /usr/share/reportbug-ng/lib/DebianBTS.py, line 67, in
getBugsByQuery
   l = __soapGetBugsByQuery(query)
 File /usr/share/reportbug-ng/lib/DebianBTS.py, line 181, in
__soapGetBugsByQuery
   return __soapGetStatus(__soapGetBugs(*__translate_query(query)))
 File /usr/share/reportbug-ng/lib/DebianBTS.py, line 206, in
__soapGetBugs
   return soapServer.get_bugs(*query)
 File /var/lib/python-support/python2.4/SOAPpy/Client.py, line 421, in
__call__
   return self.__r_call(*args, **kw)
 File /var/lib/python-support/python2.4/SOAPpy/Client.py, line 443, in
__r_call
   self.__hd, self.__ma)
 File /var/lib/python-support/python2.4/SOAPpy/Client.py, line 345, in
__call
   config = self.config)
 File /var/lib/python-support/python2.4/SOAPpy/Client.py, line 249, in
call
   raise HTTPError(code, msg)
SOAPpy.Errors.HTTPError: HTTPError 302 Moved Temporarily
MainWindow   DEBUGCloseEvent triggered.


There might be something wrong with the proxy-feature I've enabled a few

versions ago. Is the http_proxy environment variable set accordingly?
Please paste the output of

  echo $http_proxy




It is correct:

$ echo $http_proxy
http://wwwcache..**.**:80**/




You should also try to start rng with the http_proxy variable temporary
unset:

  http_proxy='' rng

and tell me if this works for you.




No, it doesn't work

By the way, if you allow me to abuse, two wishes (basically, two
capabilities of reportbug missing in reportbug-ng):

a) Remind what critical, grave, etc means anytime we report a bug.
b) Allow to send directly through an SMTP, and from the email address we
type, without an email application (very useful if we use a gmail account)

Cheers,

David


Bug#433790: reportbug-ng: Freezes when fetching bugreports

2007-07-19 Thread Bastian Venthur
severity 433790 important
stop

Thanks for you additional information. I downgrade the bug to important
since it has a major effect on the usability of a package, without
rendering it completely unusable to everyone.. In this case only users
behind a http-proxy are affected.


David wrote:
  $ rng --loglevel=debug

 Unhandled exception in thread started by bound method
 MyMainWindow.loadAllBugSummaries of ui.MyMainWindow.MyMainWindow object
 at 0xb64a3a2c

 in call
 raise HTTPError(code, msg)
 SOAPpy.Errors.HTTPError: HTTPError 302 Moved Temporarily

This looks strange, maybe rng isn't the problem, but your proxy? It
looks like rng is able to send the SOAP request via the proxy but
receives this 302 Error as answer. You said that rng worked before for
you? Was it before I added proxy support or after? If it was after I
initially added proxy support, than I strongly assume that your proxy is
the problem, since I haven't touched the http-proxy code afterwards anymore.


Cheers,

Bastian

-- 
Bastian Venthur  http://venthur.de
Debian Developer venthur at debian org



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#433790: reportbug-ng: Freezes when fetching bugreports

2007-07-19 Thread Bastian Venthur
tags 433790 pending
stop


I discovered the problem and will upload as soon as possible. Thanks for
your the report and the information you provided!


Cheers,

Bastian

-- 
Bastian Venthur  http://venthur.de
Debian Developer venthur at debian org



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]