https://bugs.kde.org/show_bug.cgi?id=468624
Bug ID: 468624
Summary: Inaccessible remote database causes boot time to take
several minutes without even displaying the startup
splashscreen
Classification: Applications
Product: digikam
Version: 8.0.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Database-Mysql
Assignee: digikam-bugs-n...@kde.org
Reporter: michael2macdon...@gmail.com
Target Milestone: ---
SUMMARY
When the remote MySQL database is inaccessible, Digikam takes several minutes
to boot before it displays an error because of the inaccessible database.
During this time, the startup splash screen does not display and there is no
indication that the program has started which can cause the user to attempt to
start the program again and result in multiple instances of Digikam being
started.
STEPS TO REPRODUCE
1. Setup digikam with a remote database
2. Shutdown the database server, turn off wifi, or do similar action to prevent
a connection to the server
3. Start digikam
OBSERVED RESULT
Digikam starts, but no splash screen is displayed and it takes 1-2 minutes
before the database connection error window appears.
EXPECTED RESULT
Startup splash should show while it is trying to connect to the database. If
possible (I understand practical limitations when it comes to setting the
time-out duration for trying to connect to servers), decrease the duration
before it times out and displays the error. An alternative would be to open a
loading window or display a loading status if the database does not connect
within 2 seconds, but before the connection time-out, to inform the user that
it is trying to connect to the database. For example: "Failed to connect to
database... Retrying for X seconds..."
--
You are receiving this mail because:
You are watching all bug changes.
