Windows V3.0.0 Restart not working

[DoctorOhh]

I am running Windows 10 Pro (64 bit), version 1703, OS build 15063.413

I used the restart feature successfully on both the portable version and the 64 bit versions of calibre.

[bookmonster]

I'm running Windows 10 Home (64 bit) Version 1703 Build 15063.413

[BetterRed]

Originally Posted by K8HW

I am running Windows 10 Home Version 1703. This PC is a Lenovo All-in-one desktop.

Originally Posted by bookmonster

I'm running Windows 10 Home (64 bit) Version 1703 Build 15063.413

Surely not?

BR

[theducks]

Originally Posted by BetterRed

Surely not?

BR

I run Pro
>ver

Microsoft Windows [Version 10.0.15063]
I believe the level difference now, is just the product KEY used

[BetterRed]

Originally Posted by theducks

I run Pro
>ver

Microsoft Windows [Version 10.0.15063]
I believe the level difference now, is just the product KEY used

Not quite, with Home you get almost no control over updates, i.e. you get them like it or not, and you don't get gpedit - you have to edit the registry instead, and you can't have your settings windows in black (Model T Windows, any colour as long as its white) ಠ_ಠ

I think there are other differences too.

BTW: MS released some security patched for XP! See ==>> June 2017 security update release – MSRC

BR

[theducks]

Originally Posted by BetterRed

Not quite, with Home you get almost no control over updates, i.e. you get them like it or not, and you don't get gpedit - you have to edit the registry instead, and you can't have your settings windows in black (Model T Windows, any colour as long as its white) ಠ_ಠ

I think there are other differences too.

BTW: MS released some security patched for XP! See ==>> June 2017 security update release – MSRC

BR

But those features are there in the code. You just can't access them with the wrong level license.
IIRC Anytime upgrade, is just a new Key

[mbovenka]

I'm having the same issue with 3.1.0 (perhaps with 3.0 also, but didn't try there).

Restart doesn't work, restart in debug mode does.

Windows 10 Home 1703, build 15063.413.

[kovidgoyal]

Seems to be something in windows 10 home -- unfortunately I only have windows 10 pro. I'm surprised though, as I would not think that basic functionality of launching processes would be different between home and pro.

[chaley]

Originally Posted by kovidgoyal

Seems to be something in windows 10 home -- unfortunately I only have windows 10 pro. I'm surprised though, as I would not think that basic functionality of launching processes would be different between home and pro.

I have Win10 Home and I can make it fail. Unfortunately I can't find a way to figure out what is going on. What I know:

• If I start while running from source, restart works.
• If I start using only the binary, restart in debug mode works.
• If I start using only the binary, restart fails.

In all cases I am starting calibre from a DOS shell. The underlying binary is 3.1.1. In the first and third experiments I am using the built-in restart command, added to calibre's menu. In the two cases where it works, I see a spinning "wait" mouse cursor for a second or two, then nothing for a second or two, then calibre restarts. In the case where it doesn't work, that "wait" mouse cursor is up for around 1/4 second and nothing further happens.

@Kovid: I am happy to run any experiments you suggest. I don't have a C/C++ development environment installed.

[kovidgoyal]

@chaley: The restart logic is in gui2/main.py around line 394 you can stick some print statements in there to see what is happening. (You will need to print to a file somewhere, as stdout/stderr are redirected to NUL).

print >>open('c:/log.txt', 'a'), 'some debug stuff'

or

from calibre import prints
prints('some debug stuff', file=open('c:/log.txt', 'a'))

[kovidgoyal]

Oh and since it works runnign from source, you'll have to make your changes to the pylib.zip file in the calibre install folder. Basically fund gui2/main.pyo in there, delete it and replace it with your modified gui2/main.py

[kovidgoyal]

Another thing you can check using processexplorer is to see if the main rpocess is actually launching the child process on restart or dying before that. If the latter I assuem the child process dies, it might be useful to see what it is doing when it dies.

[chaley]

Originally Posted by kovidgoyal

Another thing you can check using processexplorer is to see if the main rpocess is actually launching the child process on restart or dying before that. If the latter I assuem the child process dies, it might be useful to see what it is doing when it dies.

When it works I see:

1. calibre-parallel and conhost die
2. A calibre.exe process appears with a new PID as a child of the original calibre.exe.
3. The original calibre.exe process dies, promoting the child.
4. The calibre-parallel process appears

When it doesn't work the child calibre.exe never appears.

[BetterRed]

Be interesting to know if other restartable programs suffer a similar fate on Win 10 Home version 1703 - firefox comes to mind.

Process Explorer has an option to restart a running task, can it restart calibre 3 on windows 1703 Home. It works fine on Windows 1611 Pro.

BR

[chaley]

Originally Posted by BetterRed

Be interesting to know if other restartable programs suffer a similar fate on Win 10 Home version 1703 - firefox comes to mind.

Never has a problem with firefox or thunderbird or chrome restarting

Process Explorer has an option to restart a running task, can it restart calibre 3 on windows 1703 Home. It works fine on Windows 1611 Pro.

BR

PE restarts just fine.