https://bugs.kde.org/show_bug.cgi?id=419847
Bug ID: 419847
Summary: If user/group opens Digikam without write access to
databases, system will hang with high CPU and write
attempts
Product: digikam
Version: 6.4.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Database
Assignee: digikam-bugs-n...@kde.org
Reporter: cshrimpt+...@gmail.com
Target Milestone: ---
SUMMARY
If Digikam is opened without write access to db, CPU will spike to 100% and I/O
writes will completely consume disk capacity. Process and CPU issues persist
even after app is closed. Only a manual kill of the process will stop the
excessive disk and CPU action.
I discovered this after setting up Digikam for group access without setting
group write permissions to the db files.
Would be nice if Digikam could detect write failures and terminate instead of
locking up the PC with excessive CPU and I/O writes.
STEPS TO REPRODUCE
1. Remove write access to database files (user or group).
2. Start Digikam
3.
OBSERVED RESULT
CPU spikes to 100% and I/O writes exceed disk capability thus locking up
system.
EXPECTED RESULT
Digikam should be able to detect improper file permissions.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
