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:
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.
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
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,
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,
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]
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,
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;
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
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]
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
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
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
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
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
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
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
17 matches
Mail list logo
