https://bugs.kde.org/show_bug.cgi?id=468624
--- Comment #3 from michael2macdon...@gmail.com --- Created attachment 158199 --> https://bugs.kde.org/attachment.cgi?id=158199&action=edit "Failed to open the database" (Error Window) (In reply to Maik Qualmann from comment #1) > Created attachment 158176 [details] > database-error > > Such a window already exists, which appears for me after less than 1 second. > See the screenshot. > > Maik Thanks for the response. As you pointed out, I was wrong about there not being a reconnecting/loading window. After reproducing the error again, I timed the startup and it took over 2 minutes and 20 seconds before the "reconnecting" window appeared. During this time the startup splash screen was never displayed. After the reconnecting window appears, it continues to attempt to connect to the database for over 20 minutes, only stopping when I pressed the "close" button. After the window closes, nothing happens for 2 minutes (again I timed it) until another "error window" appears (See the screenshot I attached). This new window has an error, instructions to check the database settings in the next window, and an "ok" button to go to the next window. Once the "ok" button is pressed the database settings window immediately opens. The reconnecting window is somewhat misleading because there is no indication to the user that you will be able to change the database settings in a new window after pressing the "close" button. To the user, "close" implies closing the program or window and nothing more. Updated requests: - The database reconnecting window should not take 2 minutes before appearing. - The database reconnecting window should have a second button that takes the user straight to the database settings window and the current close button should close the application without opening the error window or database setting window. - The database loading window should time out after a reasonable duration (if the user does not close it or press the button to skip to the database settings) and then (and only then) present the user with the error window (see attached screenshot). - The error window should not take 2 minutes before appearing Less important, assuming the database loading window appears immediately: - I still believe that the startup splash screen should display earlier (preferably within the first 10 seconds) *no matter what* so that the user knows the application is starting. This could mean fully displaying the startup splash screen before any other startup begins or separating the startup splash screen and other startup code using a non-blocking method such as threads. I can send more details about my system if you can't reproduce the bug where it takes over 2 minutes for the reconnecting and error windows to open. -- You are receiving this mail because: You are watching all bug changes.
