#1427 Spurious gray bar at the bottom on application start

[Albireo]

Hello, whenever I open a database after starting the application a spurious gray bar appears at the bottom of the window, right above the status bar (see image "1 - before.png").

After collapsing the application to the tray bar and re-expanding it, the bar disappears (see image "2 - after.png").

This happens everytime I start the application, and is not tied to a specific database or to the act of opening a database (opening another database after the application is started does not make the bar appear, neither does closing and then opening a database), and the glitch goes away regularly after minimizing the application.

[MrMe]

As a fellow PasswordSafe user, I could not reproduce this. I also don't recalI ever seening this behavior with a released version. The gray area looks like where the Find toolbar should be if are showing it.

Can you provide more details. What are your configurations in Options (e.g. are you minizing to Tray? Display tab options etc.). Are you using v3.43.0? What version of Wiindows 10?

[Albireo]

The gray area looks like where the Find toolbar should be if are showing it.

That is interesting. I reproduced the problem, then opened the find bar ("Edit" menu, then "Find") and it occupied the exact space of the gray bar (see image "3 - find.png") and when I closed the find bar the gray bar went away too.

What are your configurations in Options

See attached images 4 through 9.

Are you using v3.43.0?

I am, 3.43.0-ga4c5e8f 64-bit. Sowever the problem existed in version 3.42.0 and 3.42.1 (both 32 bit) too at least.

What version of Wiindows 10?

Microsoft Windows 10 Enterprise 2016 LTSB
10.0.14393 Build 14393

[MrMe]

Thanks. You said the issue also occured with v3.42.0 and 3.42.1, was that also under Windows 10 Enterprise?

I only use Windows 10 Home, Windows 7 Pro & Enterprise and Windows 8.1 Pro and all my installs are 'Green' (i.e. don't use Windows Registry) installations. All I can offer is that you try it on a non Windows 10 Enterprise system to see if the issue is related to this Windows version.

[Albireo]

You said the issue also occured with v3.42.0 and 3.42.1, was that also under Windows 10 Enterprise?

Yes, it's the same computer.

All I can offer is that you try it on a non Windows 10 Enterprise system to see if the issue is related to this Windows version.

I can check on my home computer when I get back, but that's a Windows 10 Enterprise LTSB OS too (the LTSB part is important), I don't have another version on hand.

[MrMe]

It's only a guess on my part, but Windows 10 Enterprise LTSB is probably the root cause.

[Rony Shapiro]

Reluctantly marking as won't fix, as I cannot reproduce the problem.