[Old Thread] Calibre exits after checking for updates

[cybmole]

Originally Posted by dwanthny

On my WinXP machine selecting upgrade opens the download page and closes calibre.

same here, with windows 7 - calibre closes itself - or something closes it!

I also have close to system tray preference enabled.

[kovidgoyal]

I'm guessing this has something to do with the system tray.

EDIT: Tried it with the system tray icon enabled and I still cannot reproduce

[Manichean]

I just tried this on another computer with all four combinations of system tray icon on/off and show notification on/off and couldn't reproduce the error. I have to note, though, that calibre-debug didn't open the notification window when I selected it to show, and yes, I did restart Calibre completely after each setting change.

This was 0.7.52 on XP SP3.

[rusky]

Calibre has the close to system tray enabled here.

[cybmole]

Originally Posted by Manichean

I just tried this on another computer with all four combinations of system tray icon on/off and show notification on/off and couldn't reproduce the error. I have to note, though, that calibre-debug didn't open the notification window when I selected it to show, and yes, I did restart Calibre completely after each setting change.

This was 0.7.52 on XP SP3.

the bug/feature/whatever does not bother me but I guess it will only show up in some O/S, when system tray enabled; and that win XP is not one of affected O/S

results so far : that 2 folks with XP cannot reproduce it, 2 folks with WIN 7 can ( 1 x 32 bit, 1 x 64 bit) - & we've yet to hear from any Vista or Mac users

[IcecreamLtDan]

Well, currently I run Windows 7, however I had a Vista machine that I had Calibre running on until about 3 months ago and I've don't recall any issues where Calibre would shut down when checking or downloading an update.

[Manichean]

Originally Posted by IcecreamLtDan

Well, currently I run Windows 7, however I had a Vista machine that I had Calibre running on until about 3 months ago and I've don't recall any issues where Calibre would shut down when checking or downloading an update.

Can you try to replicate the error on Win7? If you can, can you get a debug log? I'm sure that would be of some help for fixing this.

[DoctorOhh]

Originally Posted by cybmole

the bug/feature/whatever does not bother me but I guess it will only show up in some O/S, when system tray enabled; and that win XP is not one of affected O/S

results so far : that 2 folks with XP cannot reproduce it, 2 folks with WIN 7 can ( 1 x 32 bit, 1 x 64 bit) - & we've yet to hear from any Vista or Mac users

I use Windows XP sp3 (32 bit) (as stated in post 7) and it has closed on me at least the last two updates.

I'll start in debug at work tonight and see if it happens there as well.

[IcecreamLtDan]

Originally Posted by Manichean

Can you try to replicate the error on Win7? If you can, can you get a debug log? I'm sure that would be of some help for fixing this.

Sorry, I haven't had the error in Windows 7. Guess I didn't make that clear. Was just adding that I hadn't had the error at all, even when I was using Vista.

[DoctorOhh]

It did not happen on my Work XP machine.

[theducks]

Originally Posted by dwanthny

It did not happen on my Work XP machine.

So what is different
Is this an A/V side effect? A Pro vs Home issue
Interactions are a [ ] to find.

[DoctorOhh]

Originally Posted by theducks

So what is different
Is this an A/V side effect? A Pro vs Home issue
Interactions are a [ ] to find.

I started calibre with
calibre-debug -g 1> log.txt 2>&1
instead of
Start calibre.exe

One difference is I had already installed calibre and all of the updated plugins at home. I use the exact same configuration directory for both machines.

Same OS, same A/V, same delusional user?

[theducks]

Originally Posted by dwanthny

I started calibre with
calibre-debug -g 1> log.txt 2>&1
instead of
Start calibre.exe

One difference is I had already installed calibre and all of the updated plugins at home. I use the exact same configuration directory for both machines.

Same OS, same A/V, same delusional user?

I have started both ways and not seen it happen on update.
Now, I do see random Windows crash messages: I think it has something to do with disconnecting my device and later reconnecting. It does not always happen, so it may be the User held his face wrong.