Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
Hi Dmitry, same problem for me here when upgrading to 2.12.1-5 :-( I don't know who's going to read this any longer, as this bug-report has been marked resolved. I reported a new bug to inform the maintainers that the bug re-appeared (#484654) with 2.12.1-5. According to Josselin Mouette: [...] you should understand that it [the patch] is not causing the problem, but that it is a part of the solution. ... strange kind of solution to me ... Manuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
Manuel Metz wrote: Hi Dmitry, same problem for me here when upgrading to 2.12.1-5 :-( I don't know who's going to read this any longer, as this bug-report has been marked resolved. I reported a new bug to inform the maintainers that the bug re-appeared (#484654) with 2.12.1-5. According to Josselin Mouette: [...] you should understand that it [the patch] is not causing the problem, but that it is a part of the solution. ... strange kind of solution to me ... Did you read his entire mail??? Now it is obvious that the fix is not enough for meld, and we will try other changes suggested by upstream to fix that, but please refrain from opening new bugs if you don't have useful information to tell us. Cheers, Emilio signature.asc Description: OpenPGP digital signature
Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
Emilio Pozuelo Monfort wrote: Manuel Metz wrote: Hi Dmitry, same problem for me here when upgrading to 2.12.1-5 :-( I don't know who's going to read this any longer, as this bug-report has been marked resolved. I reported a new bug to inform the maintainers that the bug re-appeared (#484654) with 2.12.1-5. According to Josselin Mouette: [...] you should understand that it [the patch] is not causing the problem, but that it is a part of the solution. ... strange kind of solution to me ... Did you read his entire mail??? Now it is obvious that the fix is not enough for meld, and we will try other changes suggested by upstream to fix that, but please refrain from opening new bugs if you don't have useful information to tell us. Cheers, Emilio Hi Emilio, well yes, I did. I don't know/work with meld. So, it might be that there is more that causes trouble with this software, which I can not know of (but according to the bug reports the bug was resolved in 2.12.1-4, wasn't it ?). I was reporting the other bug because the very simple example did not work. I AM MORE THAN HAPPY TO HELP TO IMPROVE Debian, but _excuse me_, I can not understand why to call a patch part of the solution if it causes a problem that was NOT apparent before. And I have not seen any other bug-report that is solved by this patch. So for me, this solution caused a problem, which I was reporting. There might be, of course, another problem which has not not been reported, and the patch might be part of that other problem - that I can not know since it was not talked about. But how can it be a solution to the problem I was reporting, when the former package worked fine ??? Please excuse my lack of understanding on that problem. Manuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
Le jeudi 05 juin 2008 à 17:33 +0200, Manuel Metz a écrit : well yes, I did. I don't know/work with meld. So, it might be that there is more that causes trouble with this software, which I can not know of (but according to the bug reports the bug was resolved in 2.12.1-4, wasn't it ?). No, it was not. The problem is not caused by the patch itself, but by the introduction of wakeupfd in pygtk, which is in use since python2.5 2.5.2-5. I was reporting the other bug because the very simple example did not work. I AM MORE THAN HAPPY TO HELP TO IMPROVE Debian, but _excuse me_, I can not understand why to call a patch part of the solution if it causes a problem that was NOT apparent before. And I have not seen any other bug-report that is solved by this patch. So for me, this solution caused a problem, which I was reporting. There might be, of course, another problem which has not not been reported, and the patch might be part of that other problem - that I can not know since it was not talked about. But how can it be a solution to the problem I was reporting, when the former package worked fine ??? There are applications that lock without the patch. Some lock with this patch, and some lock with the new version that has been proposed by upstream. The wakeupfd stuff is dealing with the main loop's internals, and it is hard to understand the implications - I’m pretty sure I don’t understand half of them. In all cases, I fail to see how you can call the 2.12.1-4 version “working”, since the memory corruption bug causes crashes in most pygtk applications with this version. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
Le jeudi 05 juin 2008 à 17:33 +0200, Manuel Metz a écrit : well yes, I did. I don't know/work with meld. So, it might be that there is more that causes trouble with this software, which I can not know of (but according to the bug reports the bug was resolved in 2.12.1-4, wasn't it ?). No, it was not. The problem is not caused by the patch itself, but by the introduction of wakeupfd in pygtk, which is in use since python2.5 2.5.2-5. I was reporting the other bug because the very simple example did not work. I AM MORE THAN HAPPY TO HELP TO IMPROVE Debian, but _excuse me_, I can not understand why to call a patch part of the solution if it causes a problem that was NOT apparent before. And I have not seen any other bug-report that is solved by this patch. So for me, this solution caused a problem, which I was reporting. There might be, of course, another problem which has not not been reported, and the patch might be part of that other problem - that I can not know since it was not talked about. But how can it be a solution to the problem I was reporting, when the former package worked fine ??? There are applications that lock without the patch. Some lock with this patch, and some lock with the new version that has been proposed by upstream. The wakeupfd stuff is dealing with the main loop's internals, and it is hard to understand the implications - Iâm pretty sure I donât understand half of them. Hi, first thanks for the info - I think I understand a bit better now what's going on. In all cases, I fail to see how you can call the 2.12.1-4 version âworkingâ, since the memory corruption bug causes crashes in most pygtk applications with this version. Well, that's just how it was for _me_ on _my_ machine. I had/have no problems with 2.12.1-4 until now and that's also why I switched back to this version and call it working. It's the first time now that I read about these memory corruption problems, and when I look into the bugreports of those meld and other reports, they were _all_ marked as Fixed in version 2.12.1-4 ... !? Cheers, Manuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
I have just upgraded to 2.12.1-5 on amd64 and the bug is here again :( I there any information/debugging I can do to help resolving the issue? Regards, Dmitry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
On Tue, May 20, 2008, Guillaume Libersat wrote: I confirm what Dmitry Kurochkin says, I've got the same problem here, but only on Amd64 architecture. Works fine on my ia32 computer. Oh! I should have mentioned it from the beginning, I also have amd64. Regards, Dmitry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
On Sun, May 18, 2008, Dmitry Kurochkin wrote: I have upgraded to python-gtk2 2.12.1-3 and the problem is still there. Gajim hangs on startup unless started with /dev/null. I installed gajim, and it worked fine; I'm using python-gobject 2.14.1-6, python2.5 2.5.2-5, and python-gtk2 2.12.1-3; whare your versions? Could you try moving your gajim profile away temporarily, and seeing whether it starts? Thanks, -- Loïc Minier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
On Mon, May 19, 2008 at 11:37 AM, Loïc Minier [EMAIL PROTECTED] wrote: On Sun, May 18, 2008, Dmitry Kurochkin wrote: I have upgraded to python-gtk2 2.12.1-3 and the problem is still there. Gajim hangs on startup unless started with /dev/null. I installed gajim, and it worked fine; I'm using python-gobject 2.14.1-6, python2.5 2.5.2-5, and python-gtk2 2.12.1-3; whare your versions? python-gobject 2.14.1-6 python2.52.5.2-5 python-gtk2 2.12.1-3 Could you try moving your gajim profile away temporarily, and seeing whether it starts? Does not help. strace shows it reads from stdin. Regards, Dmitry Thanks, -- Loïc Minier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
Hello. I have upgraded to python-gtk2 2.12.1-3 and the problem is still there. Gajim hangs on startup unless started with /dev/null. Regards, Dmitry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
Package: python-gtk2 Version: 2.12.1-2 Severity: important The latest update to 2.12.1-2 wasn't very healthy. This updated breaks matplotlib and most likely other applications as well. Starting ipython -pylab and trying to type anything fails; ipython works fine. Keys only occasionally are recognized - most get lost. Starting any matplotlib script doesn't show up the plotting window. Basically, matplotlib is completely broken by this update. Downgrading to python-gtk2 2.12.1-1 everything works fine again. -- System Information: Debian Release: lenny/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25.3 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-gtk2 depends on: ii libatk1.0-0 1.22.0-1 The ATK accessibility toolkit ii libc6 2.7-11 GNU C Library: Shared libraries ii libcairo2 1.6.4-2The Cairo 2D vector graphics libra ii libglib2.0-0 2.16.3-2 The GLib library of C routines ii libgtk2.0-0 2.12.9-4 The GTK+ graphical user interface ii libpango1.0-0 1.20.2-2 Layout and rendering of internatio ii python2.5.2-1An interactive high-level object-o ii python-cairo [python2.5-cairo 1.4.12-1 Python bindings for the Cairo vect ii python-gobject [python2.5-gob 2.14.1-4 Python bindings for the GObject li ii python-numeric [python2.5-num 24.2-8.2 Numerical (matrix-oriented) Mathem ii python-support0.8.1 automated rebuilding support for P pn python2.4-cairo none (no description available) pn python2.4-gobject none (no description available) pn python2.4-numeric none (no description available) python-gtk2 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
Loïc Minier wrote: On Fri, May 16, 2008, Manuel Metz wrote: The latest update to 2.12.1-2 wasn't very healthy. This updated breaks matplotlib and most likely other applications as well. Starting ipython -pylab and trying to type anything fails; ipython works fine. Keys only occasionally are recognized - most get lost. I couldn't reproduce, but I upgraded to python2.5 2.5.2-5. Could you please try: - upgrading to python2.5 2.5.2-5 - upgrading to python2.5 2.5.2-5 and rebuilding pygtk against this python2.5 please tell me whether this helps; thanks Hi, updating to python 2.5.2-5 didn't help. matplotlib still fails with any GTK backend (GTK, GTKCairo, GTKAgg) - without any error message. running this minimum script just stalls without showing up any window; breaking with Ctly-C, the window pops up for a very short moment, that's it. import pylab x = pylab.arange(8) y = x**2 pylab.plot(x,y) pylab.show() Manuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
On Fri, May 16, 2008, Manuel Metz wrote: The latest update to 2.12.1-2 wasn't very healthy. This updated breaks matplotlib and most likely other applications as well. Starting ipython -pylab and trying to type anything fails; ipython works fine. Keys only occasionally are recognized - most get lost. I couldn't reproduce, but I upgraded to python2.5 2.5.2-5. Could you please try: - upgrading to python2.5 2.5.2-5 - upgrading to python2.5 2.5.2-5 and rebuilding pygtk against this python2.5 please tell me whether this helps; thanks -- Loïc Minier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
On Fri, May 16, 2008, Manuel Metz wrote: Minor comment: I didn't re-build pygtk (how can I), I only rebuild matplotlib from svn, but debian matplotlib failed before, too. Please try rebuilding pygtk; we're working on a patch for versions built against older python2.5 too. To rebuild pygtk, see the first steps of e.g.: http://wiki.debian.org/HowToGetABacktrace (apt-get install, apt-get build-dep, and apt-get -b; no need for DEB_BUILD_OPTS) -- Loïc Minier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
Manuel Metz wrote: Loïc Minier wrote: On Fri, May 16, 2008, Manuel Metz wrote: The latest update to 2.12.1-2 wasn't very healthy. This updated breaks matplotlib and most likely other applications as well. Starting ipython -pylab and trying to type anything fails; ipython works fine. Keys only occasionally are recognized - most get lost. I couldn't reproduce, but I upgraded to python2.5 2.5.2-5. Could you please try: - upgrading to python2.5 2.5.2-5 - upgrading to python2.5 2.5.2-5 and rebuilding pygtk against this python2.5 please tell me whether this helps; thanks Hi, updating to python 2.5.2-5 didn't help. matplotlib still fails with any GTK backend (GTK, GTKCairo, GTKAgg) - without any error message. running this minimum script just stalls without showing up any window; breaking with Ctly-C, the window pops up for a very short moment, that's it. import pylab x = pylab.arange(8) y = x**2 pylab.plot(x,y) pylab.show() Minor comment: I didn't re-build pygtk (how can I), I only rebuild matplotlib from svn, but debian matplotlib failed before, too. Manuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
Loïc Minier wrote: On Fri, May 16, 2008, Manuel Metz wrote: Minor comment: I didn't re-build pygtk (how can I), I only rebuild matplotlib from svn, but debian matplotlib failed before, too. Please try rebuilding pygtk; we're working on a patch for versions built against older python2.5 too. To rebuild pygtk, see the first steps of e.g.: http://wiki.debian.org/HowToGetABacktrace (apt-get install, apt-get build-dep, and apt-get -b; no need for DEB_BUILD_OPTS) Nop - this didn't help. I did rebuild the python-gtk2 package with python 2.5.2-5, and additionally also rebuild matplotlib. But no change: any matplotlib script is still blocking. Manuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481457: python-gtk2: 2.12.1-2 breaks matplotlib and likely other apps as well
Loïc Minier wrote: On Fri, May 16, 2008, Manuel Metz wrote: Minor comment: I didn't re-build pygtk (how can I), I only rebuild matplotlib from svn, but debian matplotlib failed before, too. Please try rebuilding pygtk; we're working on a patch for versions built against older python2.5 too. To rebuild pygtk, see the first steps of e.g.: http://wiki.debian.org/HowToGetABacktrace (apt-get install, apt-get build-dep, and apt-get -b; no need for DEB_BUILD_OPTS) ... it's me again ... I can not even run a very simple gtk app: import gtk win = gtk.Window(gtk.WINDOW_TOPLEVEL) win.set_title(GTK Simple Test) win.connect(delete-event, gtk.main_quit) win.realize() win.show_all() gtk.main() It's the same behavior - switching back to python-gtk2: 2.12.1-1 everything works fine again. Manuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
