[digikam] [Bug 468879] New: No feedback when importing large collection
https://bugs.kde.org/show_bug.cgi?id=468879 Bug ID: 468879 Summary: No feedback when importing large collection Classification: Applications Product: digikam Version: 8.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-Engine Assignee: digikam-bugs-n...@kde.org Reporter: espinosa...@centrum.cz Target Milestone: --- Created attachment 158375 --> https://bugs.kde.org/attachment.cgi?id=158375&action=edit Digikam shows no user feedback when importing a new large collection SUMMARY There is no feedback back to the user that the import is being done. Import of a large collection can take many minutes and during all this time user is left completely in dark if process failed, or if it still running; if something is happening at all. Very poor UX experience. Can put off people from using Digikam on the very start. Even worse, the import progress dialog announced "Processing is done", duration 00:00:00. Clearly a bug there. Same happens if I do "refresh" of Album during the "invisible" import. The only indication of the import in fact being under way were slowly, very slowly, appearing subdirectories under my new album. I would expect some kind of hour-glass or rotating gears. Even better, explicit indication, ideally in some non-modal view, telling me that import is being done and what directory is being processed right now. STEPS TO REPRODUCE 1. Find a large collection, mine is 237 GiB and with over 47K files. Non-removable media. Even on fast NVMe SSD it can take 15 min for Digikam to import (hart to tell how long exactly for obvious reasons) 2. Settings -> Collections -> Root Album Folders -> Add Collection 3. Hit OK OBSERVED RESULT 4. Import dialog tells you that job is done and soon disappears. But you don't see any of your collection files and directories, leaving you baffled what is happing and if you did something wrong. 5. Album (collection) subdirectories and files start to slowly appear. EXPECTED RESULT I would expect some kind of hour-glass or rotating gears. Even better, explicit indication, ideally in some non-modal view, telling me that import is being done and what directory is being processed right now. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSuse Thumbleweed, all up-to date, all latest versions. (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 (X11) -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 501549] Kompare fails to open valid patch file
https://bugs.kde.org/show_bug.cgi?id=501549 --- Comment #4 from Jan Uhlir --- It would be nice if Kompare put little bit more details why it "Could not parse diff output", including the particular line it disliked, in their error message. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 501549] New: Kompare fails to open patch file
https://bugs.kde.org/show_bug.cgi?id=501549 Bug ID: 501549 Summary: Kompare fails to open patch file Classification: Applications Product: kompare Version: 4.2.24122 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kompare-de...@kde.org Reporter: espinosa...@centrum.cz Target Milestone: --- Created attachment 179436 --> https://bugs.kde.org/attachment.cgi?id=179436&action=edit Patch file Kompare is not able to open Kompare could not open a patch file, instead display error "Could not parse diff output". Patch file attached. Other patch files work. Kompare Version 4.2.24122 System: openSUSE Linux Slowroll. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 501549] Kompare fails to open patch file
https://bugs.kde.org/show_bug.cgi?id=501549 --- Comment #1 from Jan Uhlir --- Created attachment 179437 --> https://bugs.kde.org/attachment.cgi?id=179437&action=edit screenshot of Kompare failinf to open patch file -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 501549] Kompare fails to open patch file
https://bugs.kde.org/show_bug.cgi?id=501549 --- Comment #2 from Jan Uhlir --- FYI: diffstat didn't reveal anything wrong with that file: espinosa@espinosa-asus:~/rpmbuild/patch> diffstat patch3_Revert_drm_amd_display_Use_HW_lock_mgr_for_PSR1.patch dmub_hw_lock_mgr.c | 11 +++ 1 file changed, 11 insertions(+) Same for patch tool: espinosa@espinosa-asus:~/rpmbuild/patch> patch --dry-run -p1 < patch3_Revert_drm_amd_display_Use_HW_lock_mgr_for_PSR1.patch can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- |diff --git a/drivers/gpu/drm/amd/display/dc/dce/dmub_hw_lock_mgr.c b/drivers/gpu/drm/amd/display/dc/dce/dmub_hw_lock_mgr.c |index bf636b28e3e1..6e2fce329d73 100644 |--- a/drivers/gpu/drm/amd/display/dc/dce/dmub_hw_lock_mgr.c |+++ b/drivers/gpu/drm/amd/display/dc/dce/dmub_hw_lock_mgr.c -- File to patch: -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 503497] New: With colors set to default the location toolbar is unusable, white text on white background
https://bugs.kde.org/show_bug.cgi?id=503497 Bug ID: 503497 Summary: With colors set to default the location toolbar is unusable, white text on white background Classification: Applications Product: krusader Version: 2.9.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: espinosa...@centrum.cz CC: krusader-bugs-n...@kde.org Target Milestone: --- Created attachment 180751 --> https://bugs.kde.org/attachment.cgi?id=180751&action=edit Krusader location toolbar is unusable, white text on white background With colors set to default the “location toolbar” is unusable, white text on white background. See the attached screenshot. This bug appeared recently, after very recent upgrade. Distro: openSUSE Slowroll. Krusader version: 2.9.0 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 503497] With colors set to default the location toolbar is unusable, white text on white background
https://bugs.kde.org/show_bug.cgi?id=503497 --- Comment #1 from Jan Uhlir --- It got broken after introducing an new "segmented" Location Bar, same as appeared in Dolphin some time ago. I assume that this "segmented" Location Bar in the most recent 2.9.0 version. Previous versions were fine. Now its white on white for the active panel. The inactive panel is correct, it's gray on white, so the text is legible, as you can also see in the screenshot. Note: Krusader's Location Bar is also sometimes referred as Navigation Bar or Navigation Toolbar. Workaround: Keep Location Bar constantly in the "edit mode". That one stays black on white. It has some minor drawbacks but it's a workable solution. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 503497] With colors set to default the location toolbar is unusable, white text on white background
https://bugs.kde.org/show_bug.cgi?id=503497 --- Comment #2 from Jan Uhlir --- Good news. After today's system update (19/5/2025), it got fixed. Working variant: Krusader: 2.9.0 "Sixth Life" KDE Frameworks: 6.13.0 Qt: Using 6.9.0 and built against 6.9.0 openSUSE Tumbleweed-Slowroll (Wayland) Build ABI: x86_64-little_endian-lp64 Kernel: linux 6.14.6-1.0.4.sr20250501-default espinosa@espinosa-asus:~> rpm -qa | grep krusader krusader-2.9.0-1.2.x86_64 krusader-lang-2.9.0-1.2.noarch You can close this bugreport. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 503497] With colors set to default the location toolbar is unusable, white text on white background
https://bugs.kde.org/show_bug.cgi?id=503497 --- Comment #3 from Jan Uhlir --- Created attachment 181539 --> https://bugs.kde.org/attachment.cgi?id=181539&action=edit 2025-05-19 Krusader with fixed location bar -- You are receiving this mail because: You are watching all bug changes.
