| Summary: | digikam floods systemd journal with identical messages on exit | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Vadym Krevs <vkrevs> |
| Component: | Metadata-ExifTool | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | metzpinguin, vkrevs |
| Priority: | NOR | ||
| Version First Reported In: | 8.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.4.0 | |
| Sentry Crash Report: | |||
| Attachments: | Stack trace from gdb attached to digikam | ||
Fixed in digiKam-8.4.0 with commit https://invent.kde.org/graphics/digikam/-/commit/f5dd576832205c5d0a8a2b52bb604282aa198b28 Maik |
Created attachment 169746 [details] Stack trace from gdb attached to digikam SUMMARY openSUSE 15.5 with latest Plasma 5 from openSUSE Build Service KDE repos just before Plasma 6 was pushed there. Start and exit digikam. On exit it floods systemd journal with thousands messages that look like this May 23 18:53:22 <hostname> digikam[16534]: QSocketNotifier: Invalid socket 110 and type 'Read', disabling... causing 100% CPU/fan utilization... Stack trace from gdb attached to digikam when this is happening is attached. STEPS TO REPRODUCE 1. See above. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION