What steps will reproduce the problem? 1. Unpack KeepNote sources 2. Run python -v "C:\path\to\keepnote\bin\keepnote" 3. Quit the application 4. Run python -v "C:\path\to\keepnote\bin\keepnote"

What is the expected output? What do you see instead? A command line window with lots of messages (due to the -v switch) shows up after (2). After (3), the command line window remains visible, showing the following text at end:

cleanup[2] xml.dom

cleanup[2] keepnote.listening

cleanup[2] encodings.mbcs

cleanup[2] keepnote.gui.richtext.richtext_html

cleanup[2] win32con

cleanup sys

cleanup builtin

PyThreadState_Clear: warning: thread still has a frame PyThreadState_Clear: warning: thread still has a frame

cleanup ints: 766 unfreed ints

cleanup floats: 88 unfreed floats

Now, step (4) does not show a KeepNote GUI window, unless the command line window is closed before (or python.exe is killed from the task manager).

What version of the product are you using? On what operating system? 0.6.2 (source) Windows 7, x64

Please provide any additional information below.

Expected output: After (3), command line window disappears (=python.exe terminates), and (4) succeeds immediately.

I do not run keepnote from source in windows, so I do not know why it would not terminate. It does terminate when running from source in Linux.

It does terminate under Linux, it does not under Windows.

I run the following combination of packages:

Python 2.6.4 x86 py2exe 0.6.9 pycairo 1.4.12 pygobject 2.14.2 pygtk 2.12.1 pywin32 214 setuptools 0.6c11

I had similar issue with the latest version (0.7.8).

Here are some observations:

1. The issue is not limited to source case. It also exists while executing the py2exe-packed version, that is, keepnote.exe remains alive while GUI is closed.

2. The issue disappears while I use older pywin32 version (210, as suggested in INSTALL document). People who has the same issue can proceed in this way...

3. The issue also disappears if executing in VirtualBox (the same WIN7 x64 OS). To be clear, the same py2exe-packed version has this issue in my real WIN7 PC and does not have this in VirtualBox WIN7.

Hope these help..