abrt 1.0.3 detected a crash. How to reproduce: 1. I was just running this quite big query Comment: I was just running this quite big query Attached file: backtrace cmdline: /usr/bin/python /usr/bin/bugzilla query --reporter=jhutar '--outputformat=%{bug_id} --outputformat' component: python-bugzilla executable: /usr/bin/bugzilla kernel: 2.6.31.9-174.fc12.x86_64 package: python-bugzilla-0.5.1-3.fc12 uuid: c67713d8
Created attachment 386730 [details] File: backtrace
The bugzilla CLI doesn't handle the socket.error exception cleanly; this is now fixed in git. This won't fix the error you encountered, which was errno 110 - socket timeout (i.e. the server stopped responding). But it won't be considered a crash anymore.
How to reproduce ----- 1. when the bugzilla was down and I tried to login it via python-bugzilla, this crash happened 2. $ bugzilla login 3.
This is fixed in python-bugzilla-0.6.0, which will be in Fedora 13. Since the crash is purely cosmetic, it probably won't be backported to python-bugzilla-0.5.1 (F11/F12).