[Closed] Please help beta test calibre 7

[BetterRed]

Late yesterday, I installed calibre 7 on my Surface Go Win 10, and this morning colleagues installed it on Win 10 and Win 11 laptops, no issues with missing shortcuts, path etc.

Originally Posted by thiago.eec

Now, is anyone else seeing a white rectangle flashing when the GUI is being loaded?

Yep - Win10 Pro - in Light Mode, and with splash screen I see a white rectangle on a larger black rectangle, with no splash, no larger black rectangle. In Dark mode - more-or-less ditto.

BR

[Uncle Robin]

Originally Posted by theducks

Me too. I thought I mentioned it during the beta
Since it appears to be cosmetic, no biggie here.

Oh I agree totally, that's why I nver brought it up. I simply confirmed that I'm seeing it. Does't appear to be having any impact on performance at all

[ownedbycats]

Originally Posted by thiago.eec

Now, is anyone else seeing a white rectangle flashing when the GUI is being loaded?

I saw that in the beta, too, but thought it was just Qt being weird.

[DNSB]

Originally Posted by chaley

Not me, with and without the splash screen. Win 10 pro.

Are you running from source?

[chaley]

Originally Posted by DNSB

Are you running from source?

Nope.

[DNSB]

Originally Posted by DNSB

Are you running from source?

Originally Posted by chaley

Nope.

I just tried on my main computer and I get the same black screen with white box momentarily whether I'm running from binary or from source. It doesn't seem to cause any issues, just a touch annoying.

[Quoth]

Originally Posted by thiago.eec

Windows 11 here. I had the problem with missing icons too. I thought something went wrong with the auto update*, so I ran it again and everything was back to normal.

Now, is anyone else seeing a white rectangle flashing when the GUI is being loaded?


*I use a batch script to keep calibre updated

It's normal on Linux Mint 21.2 with Mate desktop.

[bossanova808]

I too am seeing white screen issues with the main calibre app V7.

I run it on a headless Windows 10 machine that I RDP into. Since installing V7, every time I RDP into this machine (calibre is running, minimsed to the tray) - I get a empty white window (sometimes it's a white square with large black background).

I can not close or minimse this window. I have to right click the Calibre tray icon, choose restore window, and then it comes back normally, and I can then minimise it again.

Bit of an irritant to have to do this every time I login to that machine...

[JSWolf]

Originally Posted by bossanova808

I too am seeing white screen issues with the main calibre app V7.

I run it on a headless Windows 10 machine that I RDP into. Since installing V7, every time I RDP into this machine (calibre is running, minimsed to the tray) - I get a empty white window (sometimes it's a white square with large black background).

I can not close or minimse this window. I have to right click the Calibre tray icon, choose restore window, and then it comes back normally, and I can then minimise it again.

Bit of an irritant to have to do this every time I login to that machine...

Try Teamviewer and see if that works any better.

[dunhill]

Originally Posted by theducks

Me too. I thought I mentioned it during the beta
Since it appears to be cosmetic, no biggie here.

So it's something cosmetic? No need to worry? Thanks to me, they told me this just yesterday.
Although it is annoying.

[DrChiper]

Originally Posted by thiago.eec

Now, is anyone else seeing a white rectangle flashing when the GUI is being loaded?

Yes, today I upgraded my system to Win 11 Pro 23H2, got the very latest display drivers, migrated calibre from 6.29.0 to 7.1.0 and noticed immediately (after the splash screen) the white box issue (see screen shot). I assume it is Qt related, but might also be a case of too quickly enabling the showing of the main canvas before the window initialization is quite finished.

[dunhill]

Originally Posted by DrChiper

Yes, today I upgraded my system to Win 11 Pro 23H2, got the very latest display drivers, migrated calibre from 6.29.0 to 7.1.0 and noticed immediately (after the splash screen) the white box issue (see screen shot). I assume it is Qt related, but might also be a case of too quickly enabling the showing of the main canvas before the window initialization is quite finished.

In Linux this behavior does not occur with the latest version of Calibre

[bossanova808]

Originally Posted by JSWolf

Try Teamviewer and see if that works any better.

I don't want Teamviewer on this server. (It's on a Tailscale VPN so RDP is perfectly safe and provides a much better experience).

I could try it I guess if somehow that info was useful for solving the bug, but it's not a solution to the problem as such - it's definitely a bug with V7 (and still happening with 7.1) - have run Calibre for many years on the same machine without this.

[DrChiper]

Originally Posted by dunhill

In Linux this behavior does not occur with the latest version of Calibre

That is expected as Linux is much faster then Windows: it might also be present there, but us mere mortals are unable to see it.

What I do see on my humble Windows system is that calibre opens up a blank windows frame with empty canvas (black background with centered white rectangle), shows that while doing some background processing (DB access?) and thereafter places the window elements on the canvas as usual.

Due to a new (?) Qt version (behaving differently?), additional processing time (the new calibre features?) this initial build-up delay is now more noticeable.

[JSWolf]

Originally Posted by bossanova808

I don't want Teamviewer on this server. (It's on a Tailscale VPN so RDP is perfectly safe and provides a much better experience).

I could try it I guess if somehow that info was useful for solving the bug, but it's not a solution to the problem as such - it's definitely a bug with V7 (and still happening with 7.1) - have run Calibre for many years on the same machine without this.

I would not say it's a calibre bug until Teamviewer is tried. For all we know, it could be a bug in RDP.