[Reportbug-maint] Bug#758619: more complete backtrace
smcv at debian.org
Thu Aug 21 09:38:12 UTC 2014
# the real bug is #671785 but it's easy to avoid it in reportbug
reassign 758619 reportbug
tags 758619 + patch
On 21/08/14 09:37, Eric Valette wrote:
> Well instead of correcting the symptom, I would prefer to correct the
> bug itself. If locking mecahnism is hazardous, then it eman beahavior is
> hazardous and that could lead to other bugs later.
Indeed. I think it's pygtk that is getting this wrong, and as you
pointed out in another mail, we have already had a bug to track that,
#671785, since 2012. The upstream bug has had no activity since 2012
either, until today.
However, reportbug can easily work around it, whereas a solution in
pygtk is rather more involved (and might never happen, since pygtk is
deprecated upstream); so I think it would be best if the reportbug
maintainers apply the one-line workaround, which is to turn off the
broken feature with the patch that can be found at
functional part is reproduced at the end of this mail). Let's use bug
number 758619 to track that.
I now realise that the steps to reproduce the bug are:
* you have either GLib from experimental on Linux, or kFreeBSD,
so the locking error is fatal;
* you have python-gtk2 and $DISPLAY is set, so reportbug's gtk2 UI
module can load; as a side-effect, python-gtk2 registers the faulty
* but you *do not* use the gtk2 UI module, so reportbug calls
raw_input(), which results in the PyOS_InputHook being called
and with that information, I can reproduce it in an experimental chroot
with "xvfb-run reportbug reportbug". The patch below fixes it.
As much as I'd like to say "this is release-critical for python-gtk2,
which is also dead upstream, so let's remove it from Debian and tell
everyone to use Gtk 3 via pygi", I don't think the maintainers of its
300 reverse dependencies would be very impressed.
--- gtk2_ui.py.orig 2014-08-21 09:28:45.375375786 +0000
+++ gtk2_ui.py 2014-08-21 09:29:02.843495121 +0000
@@ -35,6 +35,7 @@
has_spell = False
More information about the Reportbug-maint