Your message dated Tue, 04 Apr 2017 20:06:39 +0000 with message-id <e1cvuit-000akl...@fasolo.debian.org> and subject line Bug#858681: Removed package(s) from unstable has caused the Debian Bug report #171353, regarding tk crash if widget accessed from wrong thread 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.) -- 171353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=171353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: tk8.4 Version: 8.4.1 Severity: important After the change to build python with tk8.4.1 instead of tk8.3, many tkinter based applications crash. One of them is pydoc -g same behaviour with python versions 2.1, 2.2 and 2.3 (experimental). If this is due to the configuration of tk for thread support, we may need a version without thread support. $ gdb /usr/bin/python2.2 GNU gdb 5.2.90_2002-11-20-cvs-debian Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"...(no debugging symbols found)... (gdb) set args /usr/bin/pydoc2.2 -g (gdb) run Starting program: /usr/bin/python2.2 /usr/bin/pydoc2.2 -g (no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 29797)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 32769 (LWP 29798)] [New Thread 16386 (LWP 29799)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 32771 (LWP 29803)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 32771 (LWP 29803)] 0x403493f9 in Tk_FreeGC () from /usr/lib/libtk8.4.so.0 (gdb) bt #0 0x403493f9 in Tk_FreeGC () from /usr/lib/libtk8.4.so.0 #1 0x40374f74 in TkButtonWorldChanged () from /usr/lib/libtk8.4.so.0 #2 0x40374e96 in Tk_RadiobuttonObjCmd () from /usr/lib/libtk8.4.so.0 #3 0x40374449 in Tk_RadiobuttonObjCmd () from /usr/lib/libtk8.4.so.0 #4 0x404072d4 in TclEvalObjvInternal () from /usr/lib/libtcl8.4.so.0 #5 0x4040748b in Tcl_EvalObjv () from /usr/lib/libtcl8.4.so.0 #6 0x401f709e in _init () from /usr/lib/python2.2/lib-dynload/_tkinter.so #7 0x080784d6 in PyEval_CallObjectWithKeywords () #8 0x08076c76 in _PyExc_Fini () #9 0x08077c1d in PyEval_EvalCodeEx () #10 0x08079c98 in PyEval_EvalCode () #11 0x08076ce1 in _PyExc_Fini () #12 0x08077c1d in PyEval_EvalCodeEx () #13 0x08079c98 in PyEval_EvalCode () #14 0x08076ce1 in _PyExc_Fini () #15 0x08077c1d in PyEval_EvalCodeEx () #16 0x08079c98 in PyEval_EvalCode () #17 0x08076ce1 in _PyExc_Fini () #18 0x08077c1d in PyEval_EvalCodeEx () #19 0x080bcef9 in PyFunction_New () #20 0x080ab0c0 in PyObject_Call () #21 0x080b19ff in PyInstance_New () #22 0x080ab0c0 in PyObject_Call () #23 0x08079d19 in PyEval_EvalCode () #24 0x08076cff in _PyExc_Fini () #25 0x08077c1d in PyEval_EvalCodeEx () #26 0x080bcef9 in PyFunction_New () #27 0x080ab0c0 in PyObject_Call () #28 0x080b19ff in PyInstance_New () #29 0x080ab0c0 in PyObject_Call () #30 0x080783ff in PyEval_CallObjectWithKeywords () #31 0x080ae20e in PyInstance_New () #32 0x080ab0c0 in PyObject_Call () #33 0x08079d19 in PyEval_EvalCode () #34 0x08076cff in _PyExc_Fini () #35 0x08077c1d in PyEval_EvalCodeEx () #36 0x080bcef9 in PyFunction_New () #37 0x080ab0c0 in PyObject_Call () #38 0x080783ff in PyEval_CallObjectWithKeywords () #39 0x080ca381 in PyStructSequence_New () #40 0x080c89d4 in PyCFunction_Call () #41 0x08076c43 in _PyExc_Fini () #42 0x08077c1d in PyEval_EvalCodeEx () #43 0x08079c98 in PyEval_EvalCode () #44 0x08076ce1 in _PyExc_Fini () #45 0x08077c1d in PyEval_EvalCodeEx () #46 0x080bcef9 in PyFunction_New () #47 0x080ab0c0 in PyObject_Call () #48 0x080b19ff in PyInstance_New () #49 0x080ab0c0 in PyObject_Call () #50 0x080783ff in PyEval_CallObjectWithKeywords () #51 0x080995a5 in _PyGC_Dump () #52 0x4002906f in pthread_start_thread () from /lib/libpthread.so.0 #53 0x400290b5 in pthread_start_thread_event () from /lib/libpthread.so.0
--- End Message ---
--- Begin Message ---Version: 8.4.20-8+rm Dear submitter, as the package tk8.4 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/858681 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Chris Lamb (the ftpmaster behind the curtain)
--- End Message ---
_______________________________________________ Pkg-tcltk-devel mailing list Pkg-tcltk-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tcltk-devel
