zim-wiki team mailing list archive

[Jaap Karssenberg <jaap.karssenberg@xxxxxxxxx>]

On Tue, Oct 9, 2012 at 5:39 PM, Greg Warner <gdwarner@xxxxxxxxx> wrote:
> I probably represent a minority here, but instead of using the standard
> windows installers when they become available, I just do a "bzr pull" and
> "bzr update" (in windows) whenever a new release is announced.
> Interestingly enough, with the 0.57 release, I can no longer get zim to
> start with pythonw.exe.  I get to the screen where I select which notebook I
> want to open, but then the process dies.  Oddly enough, when I run it with
> python.exe, it works fine, though I'm left with a superfluous console window
> in the taskbar.
>
> I was hoping that python.exe wouldn't work so I could get a useful stack
> trace, but it works fine!  Boo!!  And since pythonw.exe doesn't have a
> console window, I don't know why its dieing!  Oh the irony.
>
> I know this isn't a lot to go on, but does anybody have a suggestion?  0.56
> worked fine with pythonw.exe.

Might be due to zim now spawning a new process as soon as it starts.
Maybe pythonw.exe somehow gets confused by that. Try running with
"--standalone".

To get logging, run with "-D" and have a look at "zim.log" in your tmp folder.

Regards,

Jaap