[digikam] [Bug 372440] New: Wishlist: ability to search for panoramic shots (search by aspect ratio *range*)
https://bugs.kde.org/show_bug.cgi?id=372440 Bug ID: 372440 Summary: Wishlist: ability to search for panoramic shots (search by aspect ratio *range*) Product: digikam Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Searches Assignee: digikam-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- I want to tag all images with aspect ratio greater than 16:9 (~2) as "Panoramic". Currently I can only search for an exact aspect ratio, not for a range (or greater than / smaller than). I would be able to find all such images if the extended search allowed for aspect ratio *ranges* to be entered. Can this be made possible? Thank you! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372485] New: Video thumbnails not created on OS X (Linux works fine since 5.3)
https://bugs.kde.org/show_bug.cgi?id=372485 Bug ID: 372485 Summary: Video thumbnails not created on OS X (Linux works fine since 5.3) Product: digikam Version: 5.3.0 Platform: Other OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: Thumbnails Assignee: digikam-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- I installed the PKG on OS X 10.11.5 (and philip5's packages on Ubuntu 16.04 64bit) and video thumbnails only work on Linux. On OS X, no video thumbnails are created. Is this a known bug? If not, how can I get more detailed console output? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372485] Video thumbnails not created on OS X (Linux works fine since 5.3)
https://bugs.kde.org/show_bug.cgi?id=372485 --- Comment #4 from Jens --- OK thank you :) do you have any plans to do this in the near future? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372701] New: Cannot drag images on map (OSM or Google)
https://bugs.kde.org/show_bug.cgi?id=372701 Bug ID: 372701 Summary: Cannot drag images on map (OSM or Google) Product: digikam Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Geolocation-Editor Assignee: digikam-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Using the Geolocation editor on ubuntu 16.04, I cannot position images onto the map. The cursor always shows the "forbidden" overlay icon as soon as I start dragging. Also, the map does not remember my location between invocations and does not synchronize the location when toggling between OSM and Google. This used to work in 4.x. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370150] Digikam geolocation editor drag and drop works only at the first edit
https://bugs.kde.org/show_bug.cgi?id=370150 --- Comment #5 from Jens --- Not reproducible with the AppImage linked above. Also some other issues seem fixed (application basic font size, missing icons and icon size, etc.) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 102500] ICONVIEW : more space conservative in thumbs view
https://bugs.kde.org/show_bug.cgi?id=102500 --- Comment #25 from Jens --- I consider the "no border around images" part of the bug (which I filed eleven years ago ;) ) as solved, Digikam 5.4.0 as below doesn't show a border any more. Also, overlay icons are shown inside images for portrait which saves some vertical space, very precious for today's 16:9 display world. The same might be possible for the rating stars - they would still be readably as overlay icons. Any chance? About the other ideas mentioned in this bug report, I don't see them as solved yet but most of them are gimmicks, not really providing a lot of advantage. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361467] indicate (shade?) drop target when copying or moving images
https://bugs.kde.org/show_bug.cgi?id=361467 --- Comment #2 from Jens --- Yes. There is no indication as to where the images will actually be dropped. I would expect a background shading or border around the drop target while hovering over each target so you can see where images will be copied / moved before you release the mouse button. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464585] Visually mark hardlinks
https://bugs.kde.org/show_bug.cgi?id=464585 --- Comment #6 from Jens --- I would like to suggest *not* to create a kind of "counter" overlay icon, though it sounds great on first thought. Considerations: – In details/compact view (with smallest icon size) overlay icons are really tiny and a number is almost impossible to read. – In addition this needs to implement quite a lot of different overlay icons (→ mem load). – Alternatively a textual overlay (→ e.g. Unicode square/encircled numbers) would complicate the implementation unnecessarily as this needs to be rendered at least each time you change the directory (→ even more mem load/switch time). – And at last, this most likely will cause a (endless) discussion about, »where should it stop counting?«. Instead I think a different colored overlay icon (with normal file name font style for hardlinks, as suggested by Simone Gaiarin) might be a good "first sight hint" (e.g. symlinks→green / hardlinks→yellow). If colors might be hard(er) to implement, maybe a different position (symlinks→lower right/ hardlinks→upper left) will do. In addition a hardlink counter field in the preview (both pane & tooltip) and *maybe* a column (→ details view) could make it even more customizable. (And *if* this needs another column/field to be replaced, I really wouldn't miss the assessment field.) BTW, I really miss such a feature! It's a pain i.t.a. to create workarounds for this kind of link management. Even Krusader can't help here. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467702] New: When confirming/rejecting faces, the scroll position in faces view jumps to (seemingly) random positions
https://bugs.kde.org/show_bug.cgi?id=467702 Bug ID: 467702 Summary: When confirming/rejecting faces, the scroll position in faces view jumps to (seemingly) random positions Classification: Applications Product: digikam Version: 7.10.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY: see $SUBJECT This seems to be similar to bug 437726 which was supposedly fixed, but I can still observe it. STEPS TO REPRODUCE 1. Go to any detected face in faces view. The face must have a lot of photos associated with it (so that the view scrolls) and there must be new, unconfirmed faces at the top. 2. Select any of these faces, but either a) reject it, and type another name instead so that it is gone from this view b) double click it, to view full size, type the name there (into the faces rectangle label), and return using ESC OBSERVED RESULT This faces view jumps to a seemingly random picture in the view, scrolling far down in most cases. EXPECTED RESULT The faces view scroll position should not change. If a photo must be selected, it should be adjacent (next, or last available) photo to the one that was just removed from this view. SOFTWARE/OS VERSIONS: KDE Neon 22.04, Digikam appimage https://invent.kde.org/graphics/digikam/commit/d366bbdc5f7f4bc0b05fb6a2f3948554a1798a43 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459170] New: kwin resizes all windows to minimum width if multiscreen configuration changes
https://bugs.kde.org/show_bug.cgi?id=459170 Bug ID: 459170 Summary: kwin resizes all windows to minimum width if multiscreen configuration changes Product: kwin Version: 5.25.5 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- STEPS TO REPRODUCE 1. install KDE on multimonitor system (in my case primary right, FullHD, secondary left, QHD) 2. Disconnect the secondary screen. All windows will be moved to the primary screen. So far, so good. 3. Reconnect the secondary screen. OBSERVED RESULT Windows will sometimes be moved halfway (!) to the secondary screen so they are split between screens Windows will always be resized to their minimum possible width (e.g. Dolphin, Konsole, etc). See screenshot. EXPECTED RESULT Windows should be either not moved at all, or (ideally - and this was the case until ~6 months ago) put back to their original position with the dualscreen config. This requires that kwin remembers the window position of each window when the screen config changes, until it is resized or moved, and restores it when a previous screen config is being restored. SOFTWARE/OS VERSIONS: KDE Neon with Frameworks 5.25.5 and all updates applied. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459170] kwin resizes all windows to minimum width if multiscreen configuration changes
https://bugs.kde.org/show_bug.cgi?id=459170 --- Comment #2 from Jens --- Are there KDE Neon packages for 5.26beta? Then it would be no problem to test ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459170] kwin resizes all windows to minimum width if multiscreen configuration changes
https://bugs.kde.org/show_bug.cgi?id=459170 --- Comment #4 from Jens --- Hi, I now have these packages and the problem seems to have been fixed already: ii kwin-addons 4:5.25.5-0xneon+20.04+focal+release+build58amd64additional desktop and window switchers for KWin ii kwin-common 4:5.25.5-0xneon+20.04+focal+release+build77amd64KDE window manager, common files ii kwin-data 4:5.25.5-0xneon+20.04+focal+release+build77all KDE window manager data files ii kwin-style-breeze 4:5.25.5-0xneon+20.04+focal+release+build61amd64KWin Breeze Style ii kwin-wayland 4:5.25.5-0xneon+20.04+focal+release+build77amd64KDE window manager, wayland version, PREVIEW release ii kwin-wayland-backend-drm 4:5.25.5-0xneon+20.04+focal+release+build77amd64KDE window manager drm plugin ii kwin-x11 4:5.25.5-0xneon+20.04+focal+release+build77amd64KDE window manager, X11 version ii libkwineffects13 4:5.25.5-0xneon+20.04+focal+release+build77amd64KDE window manager effects library ii libkwinglutils13 4:5.25.5-0xneon+20.04+focal+release+build77amd64KDE window manager gl utils library ii libkwinxrenderutils13 4:5.25.5-0xneon+20.04+focal+release+build77amd64KDE window manager render utils library I'll also check 5.26 when it appears and then close this bug if the problem is confirmed to be fixed. Thanks!! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469963] New: Keyboard shortcuts not saved
https://bugs.kde.org/show_bug.cgi?id=469963 Bug ID: 469963 Summary: Keyboard shortcuts not saved Classification: Applications Product: digikam Version: 8.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability-Keyboard Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT STEPS TO REPRODUCE 1. Open keyboard shortcuts editor 2. Modify shortcuts, e.g. "Space bar = Preview" and "Next image = PgDown" (instead of Spacebar) 3. Save, and test 4. Quit, restart Digikam, then test again OBSERVED RESULT After step 3, the modified shortcuts work. After step 4, they don't work any more. So they are not saved to disk in a persistent way. EXPECTED RESULT Modified shortcuts should persist across Digikam sessions, reboots, etc. SOFTWARE/OS VERSIONS: KDE Neon with KDE Plasma 22.04 with all updates applied Digikam current Appimage 8.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469963] Keyboard shortcuts not saved
https://bugs.kde.org/show_bug.cgi?id=469963 --- Comment #2 from Jens --- https://invent.kde.org/graphics/digikam/commit/37193a9cf14141ff119ac468dae6c74dd061d8b2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469963] Keyboard shortcuts not saved
https://bugs.kde.org/show_bug.cgi?id=469963 --- Comment #3 from Jens --- digiKam-8.1.0-20230416T171333-x86-64_01d0723f008a295794bb4ed3dde25ca4.appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469963] Keyboard shortcuts not saved
https://bugs.kde.org/show_bug.cgi?id=469963 --- Comment #5 from Jens --- Thanks! I can confirm an Appimage update did the trick. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471015] New: Error messages in Panorama tool incomplete because window contents cannot scroll
https://bugs.kde.org/show_bug.cgi?id=471015 Bug ID: 471015 Summary: Error messages in Panorama tool incomplete because window contents cannot scroll Classification: Applications Product: digikam Version: 8.1.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-Generic-Panorama Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Created attachment 159646 --> https://bugs.kde.org/attachment.cgi?id=159646&action=edit error message output with actual error far down the text SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. Select a few images that cannot be processed as panorama 2. Try it anway 3. Wait for the "hugin_executor" error message display OBSERVED RESULT The error message output is too long for the window content but cannot be scrolled, so it is truncated. Maximizing the window helps, but only to a certain extent and probably only because I have a 27" screen. EXPECTED RESULT The error message should be completely visible, and - possibly - the actual error (see screenshot, it is far down the text) should be highlighted, and/or shown first. SOFTWARE/OS VERSIONS: KDE Neon 22.04 with Digikam appimage 2023-06-13. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417709] Copy/clone common metadata (rating, location, tags, ...) when creating panorama image
https://bugs.kde.org/show_bug.cgi?id=417709 --- Comment #9 from Jens --- Still valid with 8.1.0-git appimage. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384086] Rotation of some images (JPEG, by Samsung S5 smartphone) during import is incorrect
https://bugs.kde.org/show_bug.cgi?id=384086 --- Comment #12 from Jens --- I cannot say, do you still have the images I sent as an example? I don't have the originals any more. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377228] Assign only deepest level reverse geotag to image to avoid tag spam
https://bugs.kde.org/show_bug.cgi?id=377228 --- Comment #13 from Jens --- Yes, still valid. (8.1.0-git appimage) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377857] Ideas to improve usability of image properties sidebar tab.
https://bugs.kde.org/show_bug.cgi?id=377857 --- Comment #38 from Jens --- Thank you, this is definitely going in the right direction! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377228] Assign only deepest level reverse geotag to image to avoid tag spam
https://bugs.kde.org/show_bug.cgi?id=377228 --- Comment #15 from Jens --- Yes, I saw. That's great. How about old images? Was the location metadata also written previously (in addition to tags), or is it possible to write location metadata to all images that have location tags in a batch? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393158] Geolocation Editor does not show existing Location tags
https://bugs.kde.org/show_bug.cgi?id=393158 --- Comment #10 from Jens --- Yes, still valid. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459969] New: Unconfirmed Faces are not grouped correctly when re-running recognition
https://bugs.kde.org/show_bug.cgi?id=459969 Bug ID: 459969 Summary: Unconfirmed Faces are not grouped correctly when re-running recognition Classification: Applications Product: digikam Version: 7.8.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. import some images. Let Digikam detect faces 2. Tag some faces so the engine is trained. 3. Select all detected (unknown) faces and right-click and choose "Detect faces" again so it uses the learned faces. OBSERVED RESULT Faces are (mostly) correctly detected, and groups are created for detected faces, but the grouping by face in the "Unconfirmed" folder of the "Faces" tab on the left side of the screen is completely random. So Digikam detects some faces, and creates the appropriate groups within "Unconfirmed" - but then places the detected face - with the correct suggested tag - into a completely *different* group (of another person). EXPECTED RESULT Within one face group, all faces should have the same suggested tag. Otherwise the grouping does not make sense. SOFTWARE/OS VERSIONS: Digikam 7.8 DMG release for MacOS on a Macbook Pro 15" with macOS 12.6 Monterey. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459969] Unconfirmed Faces are not grouped correctly when re-running recognition
https://bugs.kde.org/show_bug.cgi?id=459969
--- Comment #2 from Jens ---
Can we make this a "re-recognize faces" option instead, without removing and
re-detecting them?
This would be probably much faster and it would fit in the workflow:
"detect_faces; while(detected_but_untagged_faces.count > 0) do {
tag_some_unrecognized_faces, rerun_detection_engine, correct_tags }".
In fact, hiding this in the context menu is maybe even too little - it should
be a prominent button at the bottom of the "Unknown" faces region because it's
such a typical action.
Ideally, if fast enough, re-recognition of unknown but detected faces should
automatically run whenever the faces detection database is updated, i.e. a face
has been tagged or untagged. I think this is how iPhoto used to do it.
What do you think?
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 459969] Unconfirmed Faces are not grouped correctly when re-running recognition
https://bugs.kde.org/show_bug.cgi?id=459969 --- Comment #3 from Jens --- Actually I just found out this is how the "Recognize faces" option is supposed to work... going through the "Unknown" faces and applying the currently learned known faces against those not yet tagged. Right? But it doesn't. If I choose "Recognize faces" here, it'll put *some* faces into "Unconfirmed" but the majority will stay in "Unknown" - even very similar faces of known and tagged people. There's still something going wrong here. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460046] New: Confirming suggested face tags will cause spurious sudden scrolling of window contents
https://bugs.kde.org/show_bug.cgi?id=460046 Bug ID: 460046 Summary: Confirming suggested face tags will cause spurious sudden scrolling of window contents Classification: Applications Product: digikam Version: 7.9.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. Tag some faces, let Digikam make suggestions 2. Go to one of the face tags 3. Confirm or reject these suggestions (there need to be more faces than fit in the window, to enable scrolling) OBSERVED RESULT After a tag has been confirmed and the corresponding face vanishes from the list, the whole list of thumbnails will scroll far down. Maybe to the location where this face is now located? Or to the last selected *confirmed* face thumbnail? I haven't found out yet. EXPECTED RESULT Tagging faces should make selection advance to the next image when the tagged image (correctly) vanishes from the list of suggestions. The window position/scroll location should not move to the image's *new* location (if that is the case). SOFTWARE/OS VERSIONS: KDE Neon 20.04 with all updates applied, Digikam 7.9 Git, appimage from 2022-10-02. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460047] New: Cropping an image with face regions will keep these face regions, even if cropped away
https://bugs.kde.org/show_bug.cgi?id=460047 Bug ID: 460047 Summary: Cropping an image with face regions will keep these face regions, even if cropped away Classification: Applications Product: digikam Version: 7.9.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ImageEditor-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. Tag an image with face regions 2. Crop this image so some of the faces are gone 3. Go to "Faces" area OBSERVED RESULT Image will still be in all the faces "folders" where it previously was. Thumbnails will be incorrect (not updated). EXPECTED RESULT If a person (rectangle) is more than some % (25%? 50%?) cropped away, the corresponding face rectangle should be removed with the crop. SOFTWARE/OS VERSIONS: KDE Neon 20.04 with all updates applied, Digikam appimage v7.9 as of 2022-10-02. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460064] New: Save grouping state (e.g. as "parent item") in the XMP sidecars to allow transfer between Digikam instances
https://bugs.kde.org/show_bug.cgi?id=460064 Bug ID: 460064 Summary: Save grouping state (e.g. as "parent item") in the XMP sidecars to allow transfer between Digikam instances Classification: Applications Product: digikam Version: 7.9.0 Platform: Appimage OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Albums-ItemGroup Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY: see $SUBJECT I use Digikam on a small notebook when abroad or on holiday to tag, describe and rate my photos taken on the road. I then rsync these folders to my home PC with the "main" installation of Digikam. Both installations use XMP sidecars only to store image metadata so this works quite well. However, the way I see it neither album settings (which I can live with) nor image groups survive this transfer because they are *only* stored in the database. The latter is a pain because I use this feature hevaily. Can we add a (possibly digikam specific) tag in the XMP sidecar files which, when set, defines the "parent item" (e.g. by filename) which the current item is grouped into? An XMP "derivedFrom" tag exists and could also be used for this purpose but I'm not sure this is exactly the same thing. I actually asked this back in 2016 for a completely different use case (Digikam importer) but it seems nothing has happened since then. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460064] Save grouping state (e.g. as "parent item") in the XMP sidecars to allow transfer between Digikam instances
https://bugs.kde.org/show_bug.cgi?id=460064 --- Comment #2 from Jens --- I can agree with you for folder settings. But I disagree for file groups. A relationship of a file to another file - like versioning, series shots, edits or "parent/child" relations - should be portable between apps and is actually metadata of the file. So Digikam should (and could) save a kind of "belongs-to" relation in each image's sidecar files. Of course, it should also take care there are no loops or endless recursions when loading sidecars, but that's rather obvious. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459170] kwin resizes all windows to minimum width if multiscreen configuration changes
https://bugs.kde.org/show_bug.cgi?id=459170 Jens changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #7 from Jens --- Hello, with the current installed packages the bug is unfortunately not fixed yet. The issue seems to appear less frequently but it still appears when changing the monitor configuration. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460132] New: Impossible to drag suggested face tag to other face tag in sidebar (for reassignment)
https://bugs.kde.org/show_bug.cgi?id=460132 Bug ID: 460132 Summary: Impossible to drag suggested face tag to other face tag in sidebar (for reassignment) Classification: Applications Product: digikam Version: 7.9.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. Let Digikam detect and suggest face tags 2. Drag a confirmed face tag onto another sidebar tag to reassign it - this works 3. Try to drag a suggested face tag onto a sidebar tag to reassign it OBSERVED RESULT Suggested face tag thumbnails are not draggable. Sometimes, rarely, it works, but most of the time it seems Digikam encounters a race condition between selection (a selection rectangle starts to appear, then freezes), the confirmation box with the label and the three buttons, and dragging. EXPECTED RESULT Suggested face thumbnails should be draggable just like normal face thumbnails. SOFTWARE/OS VERSIONS: KDE Neon 20.04 with Digikam 7.9.0 from the 2022-10-02 appimage. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460132] Impossible to drag suggested face tag to other face tag in sidebar (for reassignment)
https://bugs.kde.org/show_bug.cgi?id=460132 --- Comment #2 from Jens --- Thank you! :-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460064] Save grouping state (e.g. as "parent item") in the XMP sidecars to allow transfer between Digikam instances
https://bugs.kde.org/show_bug.cgi?id=460064 --- Comment #4 from Jens --- Thanks for making this clear. So what alternatives exist? I think that being able to transfer albums / folders / files between Digikam installations including *all* file metadata is a valid use case. But currently, at least the grouping status is not saved anywhere but the database. Can we use a Digikam specific tag to accomplish this? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460064] Save grouping state (e.g. as "parent item") in the XMP sidecars to allow transfer between Digikam instances
https://bugs.kde.org/show_bug.cgi?id=460064 --- Comment #9 from Jens --- > When a collection is rescanned, you cannot ensure the order of the images. > How do you want to match an item to the parent item if the parent item hasn't > even been scanned yet? The easy solution would be to scan twice. In the first round skip all images which have a parent_id. Then scan again, and skip all images already scanned (where parent_id != NULL). This guarantees that you'll get all parents before you scan the first child. The performance hit would probably be small because every image is still only touched once and sorting needs to be done anyway depending on user choice. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460064] Save grouping state (e.g. as "parent item") in the XMP sidecars to allow transfer between Digikam instances
https://bugs.kde.org/show_bug.cgi?id=460064 --- Comment #11 from Jens --- All the better! :-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460439] New: Keep tag, but delete face information
https://bugs.kde.org/show_bug.cgi?id=460439 Bug ID: 460439 Summary: Keep tag, but delete face information Classification: Applications Product: digikam Version: 7.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY: Sometimes face detection finds a view of a person where the face is not very well visible, but I'd like to keep the tag to be able to find this person again (e.g. when wearing a mask, or from behind, or upside down, or ...). In the faces workflow I'd like an option to delete the face tag but keep this same tag on the photo. Maybe as a fourth button below the thumbnail. Is this possible and feasible? SOFTWARE/OS VERSIONS: KDE Neon 20.04 + Digikam Appimage 2022-10-02 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460439] Keep tag, but delete face information
https://bugs.kde.org/show_bug.cgi?id=460439 --- Comment #3 from Jens --- OK, maybe this wasn't entirely clear. I know about "Ignored" - this is for people I do NOT want to tag, at all. But what about images where the face detection found "somebody", and I want to tag this image, but NOT use this face to train the recognition image - maybe because it's blurred, or half obscured, or the person wears a mask? Currently I use non-face tags to do this, but it's suboptimal. Reason: I found that tagging only a few bad images can make face detection performance significantly worse. Of course, in a perfect world, the image recognition engine should not be so easily confused, but being able to tag faces without Digikam using this face for training may also help. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460463] New: Scroll position in Faces view keeps jumping back & forth during face recognition/detection
https://bugs.kde.org/show_bug.cgi?id=460463 Bug ID: 460463 Summary: Scroll position in Faces view keeps jumping back & forth during face recognition/detection Classification: Applications Product: digikam Version: 7.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. Detect and recognize a number of faces so Digikam can make suggestions. 2. Start recognition of a number of new photos with a certain person on them (it should keep Digikam busy for ~1min at least to see the issue) 3. Open the Face view of a person. There should be sufficient faces to make Digikam create a scrollbar for the view, ie. at least 100 or so. 3. Start correcting & reorganizing photos in this face view OBSERVED RESULT When a face is detected and Digikam suggests to put it in the currently opened Face view, the scroll position jumps to the top of the view where the suggested face is added, and then back. Sometimes, it does not jump back, or jumps to a completely different position. Also, during detection, selecting faces for reorganization is hard because the input focus keeps flickering. EXPECTED RESULT Detecting and/or recognizing faces should not change the foreground view, should not cause flickering of input fields. It should be possible to have a detection job in the background and *simultaneously* reorganize & correct existing faces. Except for the progress bar at the bottom of the screen and the CPU load, face detection and recognition should not be noticeable at all. SOFTWARE/OS VERSIONS: KDE Neon 20.04 with Digikam-7.9 appimage with debug enabled from 2022-10-12. Possible duplicate of #402322. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402322] During face detection, the "People" / "Unconfirmed" (or "Unknown") tab content keeps jumping around
https://bugs.kde.org/show_bug.cgi?id=402322 --- Comment #22 from Jens --- See also Bug 460463. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460464] New: "Scan for faces" context menu in Faces view does not trigger scan
https://bugs.kde.org/show_bug.cgi?id=460464 Bug ID: 460464 Summary: "Scan for faces" context menu in Faces view does not trigger scan Classification: Applications Product: digikam Version: 7.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- STEPS TO REPRODUCE 1. Open faces view 2. right-click on any face or several selected faces 3. select "scan for faces" OBSERVED RESULT In digikam-debug.appimage as of 2022-10-12, this finishes at once but doesn't do anything. EXPECTED RESULT In digikam.appimage as of 2022-10-02, this worked (and was translated). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460482] New: Repeated crashes when working in Faces view while face recognition is running in the background
https://bugs.kde.org/show_bug.cgi?id=460482 Bug ID: 460482 Summary: Repeated crashes when working in Faces view while face recognition is running in the background Classification: Applications Product: digikam Version: 7.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY -> $SUBJECT I have a faces database where - for some reason - a lot of face rectangles are bad. Some are shifted, some did not survive rotating the image and some are even outside the image (because of cropping). My workflow to correct this is: STEPS TO REPRODUCE 1. In faces view, select one person 2. Inside this view, repeatedly select some images, right-click "Detect faces" (to find the correct location of faces on this photo) and then immediately with the same selection click on the red (X) icon to delete *this* face region (because it's bad). 3. While face detection is running, repeat this to queue more detection. OBSERVED RESULT Eventually, after 5-10 minutes, Digikam will crash. This is the console output: unknown: RST4 ( 3 ) unknown: RST5 ( 3 ) unknown: RST6 ( 3 ) unknown: RST7 ( 3 ) unknown: RST0 ( 3 ) unknown: RST1 ( 3 ) unknown: RST2 ( 3 ) unknown: RST3 ( 3 ) unknown: RST4 ( 3 ) unknown: RST5 ( 3 ) unknown: RST6 ( 3 ) unknown: RST7 ( 3 ) unknown: RST0 ( 3 ) unknown: RST1 ( 3 ) unknown: RST2 ( 3 ) unknown: RST3 ( 3 ) unknown: RST4 ( 3 ) unknown: RST5 ( 3 ) unknown: RST6 ( 3 ) unknown: RST7 ( 3 ) unknown: RST0 ( 3 ) unknown: RST1 ( 3 ) unknown: RST2 ( 3 ) unknown: RST3 ( 3 ) unknown: RST4 ( 3 ) unknown: RST5 ( 3 ) unknown: RST6 ( 3 ) unknown: RST7 ( 3 ) unknown: RST0 ( 3 ) unknown: RST1 ( 3 ) unknown: RST2 ( 3 ) unknown: RST3 ( 3 ) unknown: RST4 ( 3 ) unknown: RST5 ( 3 ) unknown: RST6 ( 3 ) unknown: RST7 ( 3 ) unknown: RST0 ( 3 ) unknown: RST1 ( 3 ) unknown: RST2 ( 3 ) unknown: RST3 ( 3 ) unknown: RST4 ( 3 ) unknown: RST5 ( 3 ) unknown: RST6 ( 3 ) unknown: RST7 ( 3 ) unknown: RST0 ( 3 ) unknown: RST1 ( 3 ) unknown: RST2 ( 3 ) unknown: RST3 ( 3 ) unknown: RST4 ( 3 ) unknown: RST5 ( 3 ) unknown: RST6 ( 3 ) unknown: RST7 ( 3 ) Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default sRGB ICC profile. unknown: End Of Image ( 1 ) Digikam::DNNFaceExtractor::getFaceEmbedding: Finish computing face embedding in 544 ms Beendet Unfortunately, running this with debug symbols enabled doesn't crash, even after 30 minutes of usage - possibly because of Bug 460464 in the current -debug appimage. So I cannot present a backtrace. EXPECTED RESULT No crash. Consecutively adding (queuing) images to a running face detection process should be handled by Digikam just as if all images are added at once. SOFTWARE/OS VERSIONS: KDE Neon 20.04 with Digikam 64bit appimage 2022-10-12 (with and without debug). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460482] Repeated crashes when working in Faces view while face recognition is running in the background
https://bugs.kde.org/show_bug.cgi?id=460482 --- Comment #4 from Jens --- OK. Yes, I realize this may lead to race conditions. Then can we please have a "Delete this face and rescan image" option? If I decide certain face rectangles are incorrect and want to rescan the corresponding images, I cannot delete the face because then the image is gone from the view. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460464] "Scan for faces" context menu in Faces view does not trigger scan
https://bugs.kde.org/show_bug.cgi?id=460464 --- Comment #3 from Jens --- OK, that makes sense, thanks. It doesn't fit my workflow but that's another issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402322] During face detection, the "People" / "Unconfirmed" (or "Unknown") tab content keeps jumping around
https://bugs.kde.org/show_bug.cgi?id=402322 --- Comment #24 from Jens --- This is not completely solved in Digikam-7.9.0 (appimage 2022-10-12). While face detection and reconition is running, the face thumbnail views still jump around seemingly randomly. Adding and/or removing items from the various faces views should not change the scroll position of the view, this causes a lot of confusion for users. Can we update the thumbnails without the scrollbar moving back and forth? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361467] indicate (shade?) drop target when copying or moving images
https://bugs.kde.org/show_bug.cgi?id=361467 --- Comment #10 from Jens --- No shading visible in current Appimage 7.9.0 as of 2022-10-12 (and also -02) with either FusionGray or ShadeOfGray themes. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460046] Confirming suggested face tags will cause spurious sudden scrolling of window contents
https://bugs.kde.org/show_bug.cgi?id=460046 --- Comment #1 from Jens --- Bug 402322 is related, though not exactly the same issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460464] "Scan for faces" context menu in Faces view does not trigger scan
https://bugs.kde.org/show_bug.cgi?id=460464 --- Comment #4 from Jens --- Actually, I just realized this was my own suggestion. *facepalm* Sorry about the confusion. Bug 459969 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460464] "Scan for faces" context menu in Faces view does not trigger scan
https://bugs.kde.org/show_bug.cgi?id=460464 --- Comment #6 from Jens --- Wait ... now we have both options, is this correct? Re-recognize the currently selected face, and rescan the whole image for faces? I didn't expect you to undo this change, re-recognizing makes more sense here than rescanning. But having both options would of course be the best way to go. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 460626] New: Rename multiple files: offer original name as part of new name
https://bugs.kde.org/show_bug.cgi?id=460626 Bug ID: 460626 Summary: Rename multiple files: offer original name as part of new name Classification: Applications Product: dolphin Version: 22.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de CC: kfm-de...@kde.org Target Milestone: --- SUMMARY: Currently if multiple files are selected and F2 is pressed, Dolphin offers to rename all files to the same basename with a number appended to them (denoted as "#"). It would be much more useful if Dolphin would allow keeping the original name of each file as part of the new one, e.g. denoted as "@", so that users can prepend e.g. a date, or append "_backup", to the file's basename. Similar to mmv: mmv "*.*" "2022.10.02 #1 backup.#2" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460673] New: Ctrl+click should open/close all sibling tree view nodes of the clicked node.
https://bugs.kde.org/show_bug.cgi?id=460673 Bug ID: 460673 Summary: Ctrl+click should open/close all sibling tree view nodes of the clicked node. Classification: Applications Product: digikam Version: 7.9.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY In the left sidebar (folders/albums/tags/timeline/faces), and in the right sidebar in every tree view, Ctrl+mouse click on a ">" or "v" arrow should not just expand or collapse the clicked node, but all nodes on the same level (siblings). This works in many apps, and is a huge time saver if you want to expand/collapse a tree view of any kind. I think this cannot be a configuration option (right?), but I see no reason to not make this the default behaviour. Is this feasible to be implemented in Digikam's tree view widget by default, so that it works in all tree views? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460673] Ctrl+click should open/close all sibling tree view nodes of the clicked node.
https://bugs.kde.org/show_bug.cgi?id=460673 --- Comment #3 from Jens --- My experience comes mainly from (commercial) Windows software. Maybe this is a default feature of some Windows library, WinForms, Win32, whatever .. I don't know. I just think this improves efficiency immensely when navigating through large trees of any kind. Thanks for the hint about the context menu. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460673] Ctrl+click should open/close all sibling tree view nodes of the clicked node.
https://bugs.kde.org/show_bug.cgi?id=460673 --- Comment #4 from Jens --- True. My use case is rather something like this: I have albums called 2009 .. 2022, each full of subalbums, all expanded. I want to collapse all these albums by one level. Right now I can collapse/expand *everything*, and collapse/expand *one* object on all levels, but I cannot collapse/expand *all* sibling objects by *one* level. Also not with the options in the context menu, unless I have overlooked something. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 460626] Rename multiple files: offer original name as part of new name
https://bugs.kde.org/show_bug.cgi?id=460626 --- Comment #2 from Jens --- No, 450303 is slightly different. But we can join the two by introducing a third placeholder: # = number (this already exists) @ = previous name of each file when several are selected (this would fulfill my user story) % = name of right-clicked file when several are selected (same for all files, this would be 450303) We can use different placeholder characters of course. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460746] New: Face rectangle description boxes "fly out of the view" when zooming an image with many faces
https://bugs.kde.org/show_bug.cgi?id=460746 Bug ID: 460746 Summary: Face rectangle description boxes "fly out of the view" when zooming an image with many faces Classification: Applications Product: digikam Version: 7.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. Find photo with lots of faces, most of them unknown/unconfirmed 2. Preview photo and set "show faces" to see all rectangles. Many of them overlap so it is not possible to edit all. 3. Press Ctrl+"." to zoom to 100% to better distinguish the faces. OBSERVED RESULT All text boxes below the face rectangles "fly" out of the visible area. Only the boxes are left. It is not possible to edit the face tags. EXPECTED RESULT Text boxes should not fly away but stay with the face rectangle. Also, (IMHO) while this animation is nice, it is too slow. On my QHD screen this takes >2 seconds during which Digikam is frozen. SOFTWARE/OS VERSIONS: KDE Neon 20.04, Digikam appimage 2022-10-16 64bit -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460761] New: Recent regression Cannot any more reassign faces by dragging them on the left sidebar items
https://bugs.kde.org/show_bug.cgi?id=460761 Bug ID: 460761 Summary: Recent regression Cannot any more reassign faces by dragging them on the left sidebar items Classification: Applications Product: digikam Version: 7.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. Open any "Person" in the left People sidebar. 2. Drag any face thumbnail of that person onto a different "Person" item in the same sidebar. OBSERVED RESULT Context menu appears: "Use this as face thumbnail". EXPECTED RESULT Context menu expected: "Reassign face from PersonA to PersonB". This worked in the 2022-10-02 appimage, so it is a recent regression. SOFTWARE/OS VERSIONS: KDE Neon 20.04, Digikam appimage 64bit 2022-10-16. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460673] Ctrl+click should open/close all sibling tree view nodes of the clicked node.
https://bugs.kde.org/show_bug.cgi?id=460673 --- Comment #6 from Jens --- Yes, and I want to expand and collapse a node with all of its *siblings*, but just one level deep. This is a different feature :-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460761] Recent regression Cannot any more reassign faces by dragging them on the left sidebar items
https://bugs.kde.org/show_bug.cgi?id=460761 --- Comment #1 from Jens --- Correcetion: this only happens if both faces have the same "base name tag" (but are in different folders). If the faces have different base name tags, this feature still works. I did not test this with old Digikam appimages so this may not be a regression. But IMHO still a bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460761] Recent regression Cannot any more reassign faces by dragging them on the left sidebar items
https://bugs.kde.org/show_bug.cgi?id=460761 --- Comment #3 from Jens --- But why not use the full path? Is there a big performance penalty? I have many name duplicates - even two full name duplicates, including surnames - in my tag tree. Reassigning names if I accidentally chose the wrong tag while tagging becomes very difficult this way. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460746] Face rectangle description boxes "fly out of the view" when zooming an image with many faces
https://bugs.kde.org/show_bug.cgi?id=460746 --- Comment #3 from Jens --- That looks correct, but it is not what I observed. I will send you a mp4 file via private mail (because it contains people I didn't ask whether they would want their images to be published on the internet) showing my issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460746] Face rectangle description boxes "fly out of the view" when zooming an image with many faces
https://bugs.kde.org/show_bug.cgi?id=460746 Jens changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460761] Recent regression Cannot any more reassign faces by dragging them on the left sidebar items
https://bugs.kde.org/show_bug.cgi?id=460761 --- Comment #6 from Jens --- Thanks! But wait ... does that mean that for Digikam, faces "/School/Thomas" and "/Work/Thomas" are actually the same person? This would explain the terrible face recognition performance I have with certain people ... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 464613] New: Moving images to another album from fuzzy search copies first file (instead of moving it)
https://bugs.kde.org/show_bug.cgi?id=464613 Bug ID: 464613 Summary: Moving images to another album from fuzzy search copies first file (instead of moving it) Classification: Applications Product: digikam Version: 7.10.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Searches-Similarity Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. Search for some images by similarity 2. Select some of the results 3. Right-click, choose "Move to album ...", select album OBSERVED RESULT All but one images are moved. One is copied. EXPECTED RESULT All images should be moved. SOFTWARE/OS VERSIONS: KDE Neon 22.04 with all updates applied. Digikam appimage 7.10.0. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 464613] Moving images to another album from fuzzy search copies first file (instead of moving it)
https://bugs.kde.org/show_bug.cgi?id=464613 --- Comment #2 from Jens --- Sorry, I have to rephrase. To reproduce: 1. same but limit the similarity search to some folders 2. select 3. move to another album NOT selected (ie. outside the search scope) Result: All images are moved correctly. But one of them (I think always the first) stays in the search view, although it is now out of search scope. Expected: All moved images should disappear from the similarity search window. This is obvious if you have grouping by folder/album activated (thanks for that idea). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 464943] New: Resize Kconsole not possible when Frame disabled
https://bugs.kde.org/show_bug.cgi?id=464943 Bug ID: 464943 Summary: Resize Kconsole not possible when Frame disabled Classification: Applications Product: konsole Version: 22.12.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: jdl_baku...@hotmail.com Target Milestone: --- SUMMARY In Konsole when enabling the option "Remove window titlebar and frame" you cant resize the window with the mous. It is possible to do with the snap points but not manually. STEPS TO REPRODUCE 1. Open konsole 2. Open settings 3. Configure Konsole 4. Enable: "Remove windows titlebar and frame" OBSERVED RESULT Window is not resizable with mouse EXPECTED RESULT Window can be resied with mouse SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernal Version: 6.1.8-arch1-1 (64-bit) Graphics platform: X11 and Wayland -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465332] New: Copy dialog falsely claims file timestamps are different. Also, dialog text is not translated.
https://bugs.kde.org/show_bug.cgi?id=465332 Bug ID: 465332 Summary: Copy dialog falsely claims file timestamps are different. Also, dialog text is not translated. Classification: Applications Product: dolphin Version: 22.12.1 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de CC: kfm-de...@kde.org Target Milestone: --- Created attachment 155971 --> https://bugs.kde.org/attachment.cgi?id=155971&action=edit Screenshot of the bug SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. copy one file over another, files should be identical 2. see screenshot EXPECTED: 1) if the displayed timestamp is same, it should not be reported as different, even if there is a ms or ns difference. 2) The string should be localized. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478649] New: Does not work with several Nextcloud online accounts (shows no files)
https://bugs.kde.org/show_bug.cgi?id=478649 Bug ID: 478649 Summary: Does not work with several Nextcloud online accounts (shows no files) Classification: Applications Product: systemsettings Version: 5.27.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kaccounts Assignee: plasma-b...@kde.org Reporter: jens-bugs.kde@spamfreemail.de CC: ad...@leinir.dk Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Create two Nextcloud accounts, and upload some files to each 2. Create accounts in Online Accounts for these two 3. Try to access them via Dolphins 'Network' OBSERVED RESULT The first one shows all files. The second one shows no files. There is no error message, it just appears empty. If I create the accounts in a different order, the second one will show files, and the first one won't. It does not (seem to) matter whether login happens using App Tokens or using the user password. EXPECTED RESULT Both online accounts should show their respective files. SOFTWARE/OS VERSIONS: KDE Neon 22.04 LTS with all updates applied as of today. ADDITIONAL INFORMATION: I also have one Google Drive account configured in KDE Online Accounts which works flawleessly. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 391186] [kio-gdrive]Access token expires/invalidates after performing a few file operations
https://bugs.kde.org/show_bug.cgi?id=391186 Jens changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem ||ail.de --- Comment #28 from Jens --- I'm getting this too since today. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481288] Gdrive invalid protocol after create a Google account to access Google Drive
https://bugs.kde.org/show_bug.cgi?id=481288
Jens changed:
What|Removed |Added
CC||jens-bugs.kde.org@spamfreem
||ail.de
--- Comment #11 from Jens ---
I am seeing this bug too. Creating a new GDrive connection now works with KDE
6, but using it is not possible:
```
org.kde.kgapi: Bad request, Google replied ' "{\n \"error\": {\n\"code\":
400,\n\"message\": \"Invalid field selection
etag,kind,nextLink,nextPageToken,selfLink,items(labels,exportLinks,lastViewedByMeDate,alternateLink,kind)\",\n
\"errors\": [\n {\n\"message\": \"Invalid field selection
etag,kind,nextLink,nextPageToken,selfLink,items(labels,exportLinks,lastViewedByMeDate,alternateLink,kind)\",\n
\"domain\": \"global\",\n\"reason\": \"invalidParameter\",\n
\"location\": \"fields\",\n\"locationType\": \"parameter\"\n
}\n]\n }\n}\n" '
kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the
"kio_gdrive" KIO worker.
```
Running KDE Neon 22.04 with KDE 6.2, Frameworks 6.7, kio-gdrive 24.05.0-build32
and all available updates applied.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 480779] Can not add Google to Online Accounts anymore
https://bugs.kde.org/show_bug.cgi?id=480779 Jens changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem ||ail.de --- Comment #7 from Jens --- I have he same issue on KDE Neon based on Ubuntu 22.04 with KDE 6 upgraded from KDE 5. Additionally, existing Google accounts do not show any files any more (the loading never stops). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484250] Discover cannot find packages that 'apt search' can find
https://bugs.kde.org/show_bug.cgi?id=484250 --- Comment #2 from Jens --- Both mentioned packages are "applications" (i.e. desktop apps that end users can use). How you distinguish apps from packages? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 484482] New: Dragging an image on a tag does not assign this tag to the image
https://bugs.kde.org/show_bug.cgi?id=484482 Bug ID: 484482 Summary: Dragging an image on a tag does not assign this tag to the image Classification: Applications Product: digikam Version: 8.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Keywords Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. Open right sidebar, select tag tree view 2. Drag an image onto this tag, choose "assign this tag to the image" in the popup context menu OBSERVED RESULT: Tag is not assigned to the image. EXPECTED RESULT: Tag should be assigned to the image. SOFTWARE/OS VERSIONS: KDE Neon 22.04, Digikam appimage 20240324. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 484211] Spectacle should convert old format string in filename
https://bugs.kde.org/show_bug.cgi?id=484211 Jens changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem ||ail.de --- Comment #2 from Jens --- I also just got bitten by this. How about the conversion script actually checks for the "%" placeholder in the filename template, and runs based on that result, instead of the config file timestamp? I think we should still do this, there may be a number of users who have upgraded but haven't used Spectacle yet, and haven't noticed this bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484671] New: WebDAV shared files all show "Jan 1 1970" as modification time since 6.0 upgrade
https://bugs.kde.org/show_bug.cgi?id=484671 Bug ID: 484671 Summary: WebDAV shared files all show "Jan 1 1970" as modification time since 6.0 upgrade Classification: Applications Product: dolphin Version: 24.02.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I have a Nextcloud 28 instance running to share files with other people. I have a shortcut in my Dolphin sidebar to use the Files area of this instance shared using WebDAVs: webdavs://HOSTNAME/remote.php/dav/files/MY_EMAIL/ Since upgrading to KDE 6, all files I can see on this share have the modification time "Jan 1, 1970". This also happens when using `kioclient ls ` on the command line: ``` $ kioclient stat webdavs://../Documents/xx.xls NAME xx.xls SIZE 471552 FILE_TYPE 010 MIME_TYPE application/vnd.ms-excel ACCESS0600 MODIFICATION_TIME Thu Jan 1 00:00:00 1970 CREATION_TIME Sun Mar 24 13:08:26 2024 ``` Using other WebDAV clients (e.g. `cadaver` display the modification time correctly. This also does not happen wit other remote protocols, e.g. `kio_fish`. It sesms to be a regression when moving from KDE 5 to KDE 6. SOFTWARE/OS VERSIONS: KDE Neon 22.04 with all updates applied. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443444] ISOs located on external NTFS disks are only displayed in the hamburger menu after you quit and restart Dolphin.
https://bugs.kde.org/show_bug.cgi?id=443444 Jens changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem ||ail.de --- Comment #4 from Jens --- This bug is still present on Dolphin 24.02.0 as of KDE 6.0.2. I can mount some ISOs from the context menu and they will show up in Dolphin right away, but others don't work. What's more (different bug), if the ISO label contains spaces or special characters (like "Tim's Favorite Documents" :-) ), the ISO will shows up as a disk but a click on it won't mount it, it'll show an error message. And also, if I unmount them using Dolphin, they will stay in the sidebar as unmounted loop devices. Removing the actual loop device does not seem possible using Dolphin yet (I use "gdisks" to do this). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484250] New: Discover cannot find packages that 'apt search' can find
https://bugs.kde.org/show_bug.cgi?id=484250 Bug ID: 484250 Summary: Discover cannot find packages that 'apt search' can find Classification: Applications Product: Discover Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: jens-bugs.kde@spamfreemail.de CC: aleix...@kde.org Target Milestone: --- SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. start discover and konsole 2. Use discover and apt search to find 'xmedcon' and 'sightviewer' packages 3. compare results OBSERVED RESULT Discover cannot find either. ' apt search' finds both. EXPECTED RESULT Search results by apt should be included in Discover's results. SOFTWARE/OS VERSIONS: KDE Neon 22.04 LTS with KDE 6.0.2 and all updates applied -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487285] New: Date/Time correction tool applies corrections twice, and in seemingly random order
https://bugs.kde.org/show_bug.cgi?id=487285 Bug ID: 487285 Summary: Date/Time correction tool applies corrections twice, and in seemingly random order Classification: Applications Product: digikam Version: 8.4.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Date Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY When using the date/time correction tool, there are two small issues that confuse me. 1. When pressing Apply, the correction is not applied in the order the files are listed in but seemingly random. The list selection then jumps around randomly which is confusing. 2. When pressing OK after having pressed Apply, the correction is applied *again*, which causes an unnecessary delay. In both cases I was correcting the timestamp of mp4 video files using the "[x] use Exiftool" option, based on the mp4 filename which was MMDD_HHMMSS_*.mp4. STEPS TO REPRODUCE 1. Get videos named like above 2. Use date/time correction like described above 3. Observe issues like mentioned above EXPECTED RESULT 1. Apply changes in the order the files are listed, or list the files in the order the changes are applied (preferably, the former) 2. Do not re-apply when changes have already been applied, and OK is pressed. SOFTWARE/OS VERSIONS: KDE Neon 24.04 with all updates applied, & Digikam 20240512 appimage 64bit. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 353066] WISHLIST - Add keyframeable speed effect with intact audio (like iPhone slow-motion)
https://bugs.kde.org/show_bug.cgi?id=353066 --- Comment #8 from Jens --- That's perfect, thank you! :-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442303] New: Marking face as "Ignored" is not saved
https://bugs.kde.org/show_bug.cgi?id=442303 Bug ID: 442303 Summary: Marking face as "Ignored" is not saved Product: digikam Version: 7.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. Detect faces. 2. Browse images, let face tags appear so you can edit one. 3. Type "Ignored" (the predefined category which ignores faces that aren't interested) into the tag input box. 4. Go to the next or previous image, then go back. OBSERVED RESULT Face tag is empty again (or shows the previously suggested face tag.) EXPECTED RESULT Face tag should contain "Ignored". SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon / Ubuntu 20.04, Digikam appimage 2021-09-05 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442303] Marking face as "Ignored" is not saved
https://bugs.kde.org/show_bug.cgi?id=442303 --- Comment #3 from Jens --- OK, I get it but this is confusing since there are two meanings for "-". Clicking on "-" while viewing the image will remove the face, but it will be redetected when re-running the deteection algorithm. Clicking on "-" while in the "People" browser will do as you described. Can we maybe unify this experience so that we have - (+) Accept and tag face - (/) Ignore face (& move to "Ignored" category) - (-) Remove this face (& don't detect it again) because this isn't a face in both views? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432140] Cannot reassign face to 'ignored'
https://bugs.kde.org/show_bug.cgi?id=432140 --- Comment #9 from Jens --- Adding to this bug because mine was marked as duplicate. The feature works as described, but the "Ignored" tag is confusing. It should not appear as a dropdown selection option if it cannot be assigned that way. But in this case it should also be available as a third button while viewing the image with its face rectangles to make the user experience consistent. So we have buttons for "add", "ignore" and "delete" a face rectangle. Also, the "Ignored" tag in the left sidebar should be "special (maybe by default in a different color, or with a custom icon, or not be deletable, or ...). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442303] Marking face as "Ignored" is not saved
https://bugs.kde.org/show_bug.cgi?id=442303
--- Comment #4 from Jens ---
Oh, and
- Remove suggestion ("This is somebody else") if there is a suggestion
btw, the button icons are almost invisible when using a dark theme.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 434468] Needs option to move from Unconfirmed to Ignored
https://bugs.kde.org/show_bug.cgi?id=434468 Jens changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem ||ail.de --- Comment #5 from Jens --- I understand his workflow, since mine is quite similar. When I have a bunch of new images, my tagging workflow is like this. 1. select all, choose "Search for faces" context menu 2. while this is running, do geotagging and rating 3. When (1) is finished, look at each image, tag / confirm faces I do not use the "Faces" sidebar to confirm faces after importing, I use it only to find images by face. So while looking at a *photo* I would like to have all four options of a) confirm / tag / correct face tag b) delete this face / this is not a face c) ignore this face right below the rectangle. Currently, I can only "reject" from Unconfirmed, and "ignore" from Unknown faces categories. This surely is one possible workflow, but why not make the options consistently available everywhere and thus also suit other workflows? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442858] New: Renaming files in search results view only works once
https://bugs.kde.org/show_bug.cgi?id=442858 Bug ID: 442858 Summary: Renaming files in search results view only works once Product: dolphin Version: 21.08.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de CC: kfm-de...@kde.org Target Milestone: --- SUMMARY see $SUBJECT STEPS TO REPRODUCE 1. CTRL-F to find some files 2. select any, press F2, rename it 3. try to rename it again OBSERVED RESULT Doesn't work. EXPECTED RESULT Should work. If you press F5 to reload the search results, it works again. System: KDE-Neon based on Ubuntu 20.04 with all updates applied KDE Frameworks 5.86.0 Qt 5.15.3 (kompiliert gegen 5.15.3) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 383651] Custom/image stamp annotations are not saved into the PDF file in a way that can be printed or that other readers can see
https://bugs.kde.org/show_bug.cgi?id=383651 --- Comment #32 from Jens --- I just came across this bug because I wondered why my signature (as a custom stamp) was not printed. I don't actually need custom stamps to be saved in the PDF in a portable way, but they need to be PRINTABLE. Currently, when printing a PDF document (even into another PDF), the custom stamps are missing. Other annotations and marks are kept. Is this a completely different issue or is this an aspect of this bug? -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 144948] [wish] Correctly count hardlinks in Filelight
https://bugs.kde.org/show_bug.cgi?id=144948 Jens changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem ||ail.de --- Comment #8 from Jens --- I was just about to report the same bug. I want to see the space saved due to hardlinking a lot of files, e.g. for an "rsync --link-dest=" - style backup scheme. Currently, Filelight does not do this. Can we please have an implementation like the one proposed by Marting in the mainline branch? Thank you! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 383651] Custom/image stamp annotations are not saved into the PDF file in a way that can be printed or that other readers can see
https://bugs.kde.org/show_bug.cgi?id=383651 --- Comment #35 from Jens --- Thanks for the update. What is the minimum poppler version that we need? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451501] New: Details view: true folder sizes always only includes max 1 subfolder, regardless of settings
https://bugs.kde.org/show_bug.cgi?id=451501 Bug ID: 451501 Summary: Details view: true folder sizes always only includes max 1 subfolder, regardless of settings Product: dolphin Version: 21.12.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: details mode Assignee: dolphin-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de CC: kfm-de...@kde.org Target Milestone: --- SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. start Dolphin in $HOME 2. Go to Settings > Views > Details 3. Set "Folder size shows: content size, up to 20 levels deep" OBSERVED RESULT Folder sizes only reflect files directly inside each folder, not files in subfolders. EXPECTED RESULT Folder sizes should include files in subfolders. Linux/KDE Plasma: 5.24.2 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 451583] New: Crash after downloading a LOT (10 years) of transactions via aqbanking (FinTS, Comdirect)
https://bugs.kde.org/show_bug.cgi?id=451583 Bug ID: 451583 Summary: Crash after downloading a LOT (10 years) of transactions via aqbanking (FinTS, Comdirect) Product: kmymoney Version: 5.1.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Application: kmymoney (5.1.2) Qt Version: 5.15.3 Frameworks Version: 5.91.0 Operating System: Linux 5.13.0-30-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.3 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: In 2018, I tried KmyMoney first, but then gave up on it because it did not do what I needed. Today, I tried it again, and told it to download all my Comidirect bank transations since 2010. It did (or seemed to do so), but then crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMyMoney (kmymoney), signal: Segmentation fault [New LWP 1547263] [New LWP 1547264] [New LWP 1547272] [New LWP 1547431] [New LWP 1547432] [New LWP 1547433] [New LWP 1547567] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f4ec76879cf in __GI___poll (fds=0x7ffd42d634b8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f4ec1ae3300 (LWP 1547261))] Thread 8 (Thread 0x7f4ebabc8700 (LWP 1547567)): #0 __GI___libc_read (nbytes=10, buf=0x7f4ebabc7a1e, fd=24) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=24, buf=0x7f4ebabc7a1e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f4e5be4b975 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #3 0x7f4e5becf416 in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f4e5becfeb4 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f4e5becff70 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f4e5bede11d in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f4e5be7a72c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #8 0x7f4ec60dd609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f4ec7694163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f4eba3c7700 (LWP 1547433)): #0 0x7f4ec76879cf in __GI___poll (fds=0x7f4ea4002a40, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4ec4e7c36e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4ec4e7c4a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4ec7ea071b in QEventDispatcherGlib::processEvents (this=0x7f4ea4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f4ec7e4492b in QEventLoop::exec (this=this@entry=0x7f4eba3c6be0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f4ec7c5e462 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f4ec7c5f643 in QThreadPrivate::start (arg=0x55be10fa9f50) at thread/qthread_unix.cpp:331 #7 0x7f4ec60dd609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f4ec7694163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f4eb93c5700 (LWP 1547432)): #0 0x7f4ec76879cf in __GI___poll (fds=0x7f4ea8003a50, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4ec4e7c36e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4ec4e7c4a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4ec7ea071b in QEventDispatcherGlib::processEvents (this=0x7f4ea8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f4ec7e4492b in QEventLoop::exec (this=this@entry=0x7f4eb93c4be0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f4ec7c5e462 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f4ec7c5f643 in QThreadPrivate::start (arg=0x55be10f40f80) at thread/qthread_unix.cpp:331 #7 0x7f4ec60dd609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f4ec7694163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f4eb9bc6700 (LWP 1547431)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f4ecb8d79b0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55be10f72c40, cond=0x7f4ecb8d7988) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f
[dolphin] [Bug 432944] New: Dolphin crashes when repeatedly trying to read file from disk with I/O errors
https://bugs.kde.org/show_bug.cgi?id=432944 Bug ID: 432944 Summary: Dolphin crashes when repeatedly trying to read file from disk with I/O errors Product: dolphin Version: 20.12.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.12.2) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.4.0-64-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Information about the crash: - What I was doing when the application crashed: - copy files from a floppy disk which had bad sectors - Unusual behavior I noticed: - After 2 or 3 times clickin "Retry", Dolphin showed a "File overwrite?" dialog for a second, where the file to be copied suddenly had 17kb (correct) instead of 0kb (bad), then crashed. It seemed the disk could be read after a few attempts, but this surprised Dolphin too much. :-p The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [New LWP 322783] [New LWP 322784] [New LWP 322785] [New LWP 322786] [New LWP 322787] [New LWP 322788] [New LWP 322789] [New LWP 322790] [New LWP 322791] [New LWP 322792] [New LWP 322793] [New LWP 322797] [New LWP 322798] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f392ed5daff in __GI___poll (fds=0x7fff40dd0368, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f3927dff8c0 (LWP 322782))] Thread 14 (Thread 0x7f39097fa700 (LWP 322798)): #0 0x7f392a85024d in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f392a80271a in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f392a8030bb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f392a8032c3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f392ca95fbb in QEventDispatcherGlib::processEvents (this=0x7f38ec000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f392ca3a1ab in QEventLoop::exec (this=this@entry=0x7f39097f9ce0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7f392c854a12 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7f392c855bac in QThreadPrivate::start (arg=0x55fea96f3a10) at thread/qthread_unix.cpp:329 #8 0x7f392b1d2609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f392ed6a293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f3909ffb700 (LWP 322797)): #0 0x7f392ed5daff in __GI___poll (fds=0x7f38e8004a30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f392a80318e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f392a8032c3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f392ca95fbb in QEventDispatcherGlib::processEvents (this=0x7f38e8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f392ca3a1ab in QEventLoop::exec (this=this@entry=0x7f3909fface0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f392c854a12 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f392c855bac in QThreadPrivate::start (arg=0x55fea94c7f80) at thread/qthread_unix.cpp:329 #7 0x7f392b1d2609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f392ed6a293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f390a7fc700 (LWP 322793)): #0 0x7f392ed5daff in __GI___poll (fds=0x7f38f4005240, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f392a80318e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f392a8032c3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f392ca95fbb in QEventDispatcherGlib::processEvents (this=0x7f38f4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f392ca3a1ab in QEventLoop::exec (this=this@entry=0x7f390a7fbce0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f392c854a12 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f392c855bac in QThreadPrivate::start (arg=0x55fea92fa120) at thread/qthread_unix.cpp:329 #7 0x7f392b1d2609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f392ed6a293 in clone () at ../sysdeps/unix/sysv/l
[digikam] [Bug 440689] Current appimage does not start on KDE Neon Linux (Ubuntu 20.04 based)
https://bugs.kde.org/show_bug.cgi?id=440689 --- Comment #3 from Jens --- OK, but how does this solve the problem? Currently I cannot update to any newer snapshots. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441796] New: Tagging faces in full image view while in "Faces" category is not saved
https://bugs.kde.org/show_bug.cgi?id=441796 Bug ID: 441796 Summary: Tagging faces in full image view while in "Faces" category is not saved Product: digikam Version: 7.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT, using the Digikam 7.3 release appimage. STEPS TO REPRODUCE 1. open Faces / People sidebar 2. select an image with unconfirmed or unkonwn faces 3. double click an unknown/unconfirmed face thumbnail image so the full image shows 4. label faces in this image 5. return to the People view, or to the next image, or to another sidebar tab OBSERVED RESULT Faces are still unlabeled when returning to this image. EXPECTED RESULT Faces should be labeled, the People sidebar should update accordingly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.22, Plasma 5.22.4, based on Ubuntu 20.04 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441796] Tagging faces in full image view while in "Faces" category is not saved
https://bugs.kde.org/show_bug.cgi?id=441796 --- Comment #3 from Jens --- I would love to, but I cannot test 7.4 appimages due to a binary compatibility issue with probably all Ubuntu 20.04 based distros. See #440689. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440689] Current appimage does not start on KDE Neon Linux (Ubuntu 20.04 based)
https://bugs.kde.org/show_bug.cgi?id=440689 --- Comment #7 from Jens --- This does not work. Maybe the libnss3 version of Ubuntu LTS is "too old"? $ LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libnss3.so ./digikam-7.4.0.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 libxcb-dri3.so.0 -- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0 digikam: /usr/lib/x86_64-linux-gnu/libnss3.so: version `NSS_3.65' not found (required by /tmp/.mount_digiKa5ZCWbD/usr/lib/libsmime3.so) $ dpkg -l|grep libnss ... ii libnss3:amd642:3.49.1-1ubuntu1.5amd64 Network Security Service libraries 3.49 < 3.65 which Digikam seems to be compiled against. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440689] Current appimage does not start on KDE Neon Linux (Ubuntu 20.04 based)
https://bugs.kde.org/show_bug.cgi?id=440689 --- Comment #9 from Jens --- $ LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libsmime3.so ./digiKam-7.4.0-20210815T231101-x86-64_e6404739beb09320c2feaf9b9eaf35f0.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 libxcb-dri3.so.0 -- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0 digikam: /usr/lib/x86_64-linux-gnu/libnss3.so: version `NSS_3.65' not found (required by /tmp/.mount_digiKaqecv11/usr/lib/libsmime3.so) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440689] Current appimage does not start on KDE Neon Linux (Ubuntu 20.04 based)
https://bugs.kde.org/show_bug.cgi?id=440689 --- Comment #17 from Jens --- KDE Neon works fine with the new Appimage! Thank you :-) $ ./digiKam-7.4.0-20210901T075400-x86-64_c1deb15bdb096b2b7b1e1ec88cd3a3a7.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 libxcb-dri3.so.0 -- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0 [0901/232251.255895:WARNING:resource_bundle_qt.cpp(115)] locale_file_path.empty() for locale [0901/232251.324030:WARNING:resource_bundle_qt.cpp(115)] locale_file_path.empty() for locale [0901/232251.340549:WARNING:resource_bundle_qt.cpp(115)] locale_file_path.empty() for locale QtAV 1.13.0(Sep 1 2021, 03:26:20) Multimedia framework base on Qt and FFmpeg. Distributed under the terms of LGPLv2.1 or later. Shanghai, China Copyright (C) 2012-2019 Wang Bin (aka. Lucas Wang) wbse...@gmail.com Donate: http://qtav.org/donate.html Source: https://github.com/wang-bin/QtAV Home page: http://qtav.org [0901/232251.920469:WARNING:resource_bundle_qt.cpp(115)] locale_file_path.empty() for locale unknown: Unhandled container to remove : Digikam::DigikamApp -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 439828] New: Link from face rectangle on image to face tags (and back)
https://bugs.kde.org/show_bug.cgi?id=439828 Bug ID: 439828 Summary: Link from face rectangle on image to face tags (and back) Product: digikam Version: 7.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Created attachment 140043 --> https://bugs.kde.org/attachment.cgi?id=140043&action=edit screenshot & mockup of desired features SUMMARY I have a terrible name memory. So when tagging faces I frequently like to be able to preview "the other" face rectangles that belong to a tag, to be sure I am tagging correctly. Currently this makes me jump between "Faces" and "Albums" view all the time which is cumbersome, I have another idea. I made a mockup in an attachment. I can imagine this as a popup which appears when hovering over a name in the face tag selection list for >2 seconds, which displays the N most recent faces which have the same tag. (e.g. 8, see mockup). Nothing else needs to be displayed, just the thumbnails - no ratings or filenames etc. After selecting a face tag, I'd like to have a way of quickly going to this *face* (not to the tag), i.e. seeing all faces tagged with the same tag. I can right-click > "Go To" > Tag > ..., but this is not the face, and it is not as quickly done. SOFTWARE/OS VERSIONS: Linux KDE-Neon 20.04 with all updates applied Appimage of Digikam 7.3-pre -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440689] New: Current appimage does not start on KDE Neon Linux (Ubuntu 20.04 based)
https://bugs.kde.org/show_bug.cgi?id=440689 Bug ID: 440689 Summary: Current appimage does not start on KDE Neon Linux (Ubuntu 20.04 based) Product: digikam Version: 7.4.0 Platform: Appimage OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY ~$ Applications/digiKam-7.4.0-20210806T231120-x86-64_f8309c9fc65df541f73723b09d54de13.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 libxcb-dri3.so.0 -- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0 digikam: /usr/lib/x86_64-linux-gnu/libnss3.so: version `NSS_3.65' not found (required by /tmp/.mount_digiKagCH64f/usr/lib/libsmime3.so) ~$ dpkg -l libnss3 ... ||/ Name Version Architektur Beschreibung +++-==-===--== ii libnss3:amd64 2:3.49.1-1ubuntu1.5 amd64Network Security Service libraries -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436040] Finding collapsed group items by name does not work
https://bugs.kde.org/show_bug.cgi?id=436040 Jens changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #2 from Jens --- I think we are talking about two different situations. All the discussions I heard about so far were about the question "Do you want to find grouped items when the *parent* matches a search term". This is debatable, and this is what all past debates were about. (I also wrote a bug report regarding the display of grouped search results). But I honestly cannot imagine a use case where it makes sense to skip *exact* search results just because the VIEW settings of the icon view are currently hiding them. If this is really intentional, then the question of whether groups are open or closed does not belong into the "View" menu, because it has influence on other parts of the app as well. If you want to make this explicit, add a checkbox / option in the search results "Include closed groups", but I think this would only add to the confusion. So, IMHO: - Do not include group children just because the parent matches. - But DO include group children which match precisely. - In both cases, the view state of the group should not matter, otherwise it would not (just) be a "view" state. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436040] Finding collapsed group items by name does not work
https://bugs.kde.org/show_bug.cgi?id=436040 --- Comment #5 from Jens --- > First of all, for the search it doesn't matter if the group is closed or open This is not true, and that's what my bug report is all about. If a group is closed, exact search matches inside the group won't be found. Use case: I want to know where, if anywhere, a specific image exists in my library. I don't care if it's grouped, tagged, hidden or whatever. I just want to find it. The search tool doesn't do the job properly in this case, if this behaviour is intentional. One would have to walk through all albums and open all groups manually to *really* find all matching images. And this can't be the solution. To indicate that the item is inside a group, but the group parent doesn't match the search parameters, one could e.g. show the group parent with 50% opacity, and be able to open it to reveal the matching child. Just an idea ... -- You are receiving this mail because: You are watching all bug changes.
