Your message dated Mon, 7 Sep 2009 09:19:05 +0200
with message-id <20090907071905.ga27...@debian.org>
and subject line Re: Bug#536015: Seems Ok here
has caused the Debian Bug report #536015,
regarding python-imaging-tk: python crashes on PIL.ImageTk.PhotoImage call
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
536015: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-imaging-tk
Version: 1.1.6-3
Severity: grave
Justification: renders package unusable
On a fresh new installed debian (using netinst with testing/unstable repos
from the start), I get a crash when running the Duo card game
(http://launchpad.net/duo).
The crash seems to occur only on a call from python-imaging-tk (1.1.6-3), but I
did
not try too much python-imaging functions.
Here is a reproducer. Change 'image' with whatever image you have.
import Tkinter as tk
import PIL.Image
import PIL.ImageTk
canvas = tk.Canvas(None, bg = 'dark green', width = 600, height = 400)
img = PIL.Image.open('image')
img = img.rotate(90)
cache = PIL.ImageTk.PhotoImage(img)
Here is the backtrace I get.
Program terminated with signal 11, Segmentation fault.
#0 0xb67f437d in Tk_GetImageMasterData () from /usr/lib/libtk8.4.so.0
(gdb) bt
#0 0xb67f437d in Tk_GetImageMasterData () from /usr/lib/libtk8.4.so.0
#1 0xb68008ab in Tk_FindPhoto () from /usr/lib/libtk8.4.so.0
#2 0xb802fa92 in ?? () from /usr/lib/python2.5/site-packages/PIL/_imagingtk.so
#3 0x0902d208 in ?? ()
#4 0x0914b440 in ?? ()
#5 0xbfb25188 in ?? ()
#6 0xb79748b5 in Tcl_Alloc () from /usr/lib/libtcl8.5.so.0
#7 0xb6872dfe in TclInvokeStringCommand () from /usr/lib/libtcl8.4.so.0
#8 0xb796e881 in ?? () from /usr/lib/libtcl8.5.so.0
#9 0x091f31e8 in ?? ()
#10 0x0902d208 in ?? ()
#11 0x00000003 in ?? ()
#12 0xbfb25368 in ?? ()
#13 0x00000001 in ?? ()
#14 0xb6e82ed4 in ?? ()
#15 0x00000008 in ?? ()
#16 0xb7cc2158 in ?? () from /usr/lib/python2.5/lib-dynload/_tkinter.so
#17 0xb7a281a9 in ?? () from /usr/lib/libtcl8.5.so.0
#18 0xb7a42da8 in ?? () from /usr/lib/libtcl8.5.so.0
#19 0xbfb252c8 in ?? ()
#20 0x00000000 in ?? ()
(gdb)
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-1-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages python-imaging-tk depends on:
ii libc6 2.9-19 GNU C Library: Shared libraries
ii python 2.5.4-2 An interactive high-level object-o
ii python-central 0.6.11 register and build utility for Pyt
ii python-imaging 1.1.6-3 Python Imaging Library
ii python-tk 2.5.2-1.1 Tkinter - Writing Tk applications
ii tcl8.4 8.4.19-3 Tcl (the Tool Command Language) v8
ii tk8.4 8.4.19-3 Tk toolkit for Tcl and X11, v8.4 -
python-imaging-tk recommends no packages.
Versions of packages python-imaging-tk suggests:
pn python-imaging-doc <none> (no description available)
pn python-imaging-tk-dbg <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.1.6-3.1
David Soulayrol <david.soulay...@gmail.com> (06/09/2009):
> The 1.1.6-3.1 seems to have fixed the bug here. Thanks a lot. I
> guess you can close the bug.
Thanks for confirming; doing so.
Mraw,
KiBi.
signature.asc
Description: Digital signature
--- End Message ---
