[digikam] [Bug 471227] Idea: An option in the Keyword Tag right-click menu to copy the selected tag's heirarchy to the clipboard. This would be very useful and save a ton of time. Thanks.
https://bugs.kde.org/show_bug.cgi?id=471227 --- Comment #2 from Galen Adams --- Sorry/ maybe I wasn't clear in my description. This idea is entirely different than that of Bug #468652. #468652 was to add the option in the right-click menu to COPY the actual tag and all it's children so as to PASTE them in another place in the tags tree. This new idea/request is for an option in the tags right-click menu to COPY the tag's hierarchy, or path if you will, to the clipboard; the tag itself will remain where it is and only the hierarchy/path be copied. Currently, when I choose a tag's Properties, the hierarchy/path is displayed in the Properties dialogue, but with no way that I can find to COPY it to the clipboard. This idea I describe in no way moves or relocates the tag itself. Thanks for your patience with my poor description. On Mon, Jun 19, 2023 at 9:15 AM wrote: > https://bugs.kde.org/show_bug.cgi?id=471227 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > > CC||caulier.gil...@gmail.com > Resolution|--- |DUPLICATE > Status|REPORTED|RESOLVED > > --- Comment #1 from caulier.gil...@gmail.com --- > > > *** This bug has been marked as a duplicate of bug 468652 *** > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471227] New: Idea: An option in the Keyword Tag right-click menu to copy the selected tag's heirarchy to the clipboard. This would be very useful and save a ton of time. Thanks.
https://bugs.kde.org/show_bug.cgi?id=471227 Bug ID: 471227 Summary: Idea: An option in the Keyword Tag right-click menu to copy the selected tag's heirarchy to the clipboard. This would be very useful and save a ton of time. Thanks. Classification: Applications Product: digikam Version: 8.1.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Tags-Keywords Assignee: digikam-bugs-n...@kde.org Reporter: gadams...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports ***Idea: An option in the Keyword Tag right-click menu to copy the selected tag's heirarchy to the clipboard. This would be very useful and save a ton of time. Thanks. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469960] digiKam-8.1.0-20230517T153157-Win64-debug will not Open after Installation
https://bugs.kde.org/show_bug.cgi?id=469960 --- Comment #14 from Galen Adams --- Thank You so very much ! Much appreciated. On Thu, May 25, 2023 at 1:12 PM wrote: > https://bugs.kde.org/show_bug.cgi?id=469960 > > --- Comment #13 from caulier.gil...@gmail.com --- > The crash with debug binary under windows is now fixed. Stripping > executable > was the problem... > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469960] digiKam-8.1.0-20230517T153157-Win64-debug will not Open after Installation
https://bugs.kde.org/show_bug.cgi?id=469960 --- Comment #11 from Galen Adams --- "The Debug version is not required to create the DebugView output." My understanding of the debug version was that digiKam could create/do it's own bug tracking "in-house". If that is not the case, then what is the debug version for ? Thanks for your patience with my poor understanding of such things. On Thu, May 25, 2023 at 8:36 AM wrote: > https://bugs.kde.org/show_bug.cgi?id=469960 > > --- Comment #10 from caulier.gil...@gmail.com --- > It's must be not exactly the same size. The debug must be a little bit > larger. > > But i agree, in fact if all debug symbols are present in all internal libs, > plugins and executable from digiKam (not the dependencies), the size of the > bundle will be largest than 2Gb, and NSIS is not able to package more than > 2GB > (it crash, it's limitation of Windows API used internally, eg the win32 > stuff > of course)... > > So, i created the bundle with just the minimum of debug symbols, using the > mingw-strip tool to drop the object. The error report by windows at run > time is > probably due to a chunk of symbols to much dropped from the binaries. I > will > double check this point this evening. > > Gilles > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469960] digiKam-8.1.0-20230517T153157-Win64-debug will not Open after Installation
https://bugs.kde.org/show_bug.cgi?id=469960 --- Comment #8 from Galen Adams --- " Why are you even using the debug version?" In case I was asked to run a bug trace The debug versions have always worked before. On Thu, May 25, 2023 at 3:14 AM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=469960 > > --- Comment #7 from Maik Qualmann --- > Why are you even using the debug version? > @Gilles, the debug version has the same file size as the normal one, I > think > there is something wrong here. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469960] digiKam-8.1.0-20230517T153157-Win64-debug will not Open after Installation
https://bugs.kde.org/show_bug.cgi?id=469960 --- Comment #6 from Galen Adams --- I tried the 0522 debug version and it behaves no better than the 0517 version. The non-debug mates to these open and run. It puzzles me that the non-debug versions will work and the debug versions will not. [image: digiKam-8.1.0-20230522T042418-Win64-debug.png] On Fri, May 19, 2023 at 9:50 AM Galen Adams wrote: > I am sorry, but this DeBug View business must be way over my head; the > more I search for information, the more confused I become; and, I have been > down a hundred useless rabbit holes. > > The 20230517 win64 Non-DeBug version starts and seems to work fine. > > Immediately upon clicking the TaskBar icon, the Debug version gives a > notice that it cannot open. > > On Thu, May 18, 2023 at 3:59 PM wrote: > >> https://bugs.kde.org/show_bug.cgi?id=469960 >> >> --- Comment #4 from caulier.gil...@gmail.com --- >> yes sure. It's a generic log/events viewer >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469960] digiKam-8.1.0-20230517T153157-Win64-debug will not Open after Installation
https://bugs.kde.org/show_bug.cgi?id=469960 --- Comment #5 from Galen Adams --- I am sorry, but this DeBug View business must be way over my head; the more I search for information, the more confused I become; and, I have been down a hundred useless rabbit holes. The 20230517 win64 Non-DeBug version starts and seems to work fine. Immediately upon clicking the TaskBar icon, the Debug version gives a notice that it cannot open. On Thu, May 18, 2023 at 3:59 PM wrote: > https://bugs.kde.org/show_bug.cgi?id=469960 > > --- Comment #4 from caulier.gil...@gmail.com --- > yes sure. It's a generic log/events viewer > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469960] digiKam-8.1.0-20230517T153157-Win64-debug will not Open after Installation
https://bugs.kde.org/show_bug.cgi?id=469960 --- Comment #3 from Galen Adams --- Windows 7 Pro Can I Debug View even when it will not Open ? On Thu, May 18, 2023 at 3:33 PM wrote: > https://bugs.kde.org/show_bug.cgi?id=469960 > > --- Comment #2 from caulier.gil...@gmail.com --- > For the debugview usage, see the contribute web page : > > https://www.digikam.org/contribute/ > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469960] New: digiKam-8.1.0-20230517T153157-Win64-debug will not Open after Installation
https://bugs.kde.org/show_bug.cgi?id=469960 Bug ID: 469960 Summary: digiKam-8.1.0-20230517T153157-Win64-debug will not Open after Installation Classification: Applications Product: digikam Version: 8.1.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: gadams...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION digiKam-8.1.0-20230517T153157-Win64-debug will not Open after installation; I tried two separate downloads and multiple times and it just will not Open. Also, instead of the normal digiKam taskbar icon, all I get is a white square. I downloaded the non-debug version as well; it also does not show the normal icon AND it takes about twenty minutes to Open. In fact, I decided it was not working and tried to reinstall my previous version, which kept telling me that digiKam was running --- TaskManager did not show it as running; then, after at least twenty minutes, it went ahead and opened. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401542] I am losing more and more thumbnails in the left pane TAGS view. Everything used to work fine.
https://bugs.kde.org/show_bug.cgi?id=401542 --- Comment #14 from Galen Adams --- No, it's not. I haven't been plagued with this in the last several versions. Thanks. On Sat, Apr 29, 2023 at 4:34 AM wrote: > https://bugs.kde.org/show_bug.cgi?id=401542 > > --- Comment #13 from caulier.gil...@gmail.com --- > @Adam, > > digiKam 8.0.0 is out. This entry still valid with this release ? > > Best regards > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468832] Editing an existing Keyword Tag strips away all IPTC information from the image file.
https://bugs.kde.org/show_bug.cgi?id=468832 --- Comment #23 from Galen Adams --- You're welcome! and Thank You guys for being patient with me and my problems. On Mon, Apr 24, 2023 at 2:19 PM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=468832 > > --- Comment #22 from Maik Qualmann --- > Thanks for reporting this important bug and for creating the sample images. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468832] Editing an existing Keyword Tag strips away all IPTC information from the image file.
https://bugs.kde.org/show_bug.cgi?id=468832 --- Comment #17 from Galen Adams --- Sorry, I was sending the previous when another message came in. The GPS is written into the files by the camera. All other data is written into the files; not just floating around in some database. It is all there until I happen to decide to edit a KeyWord Tag and then it disappears. On Sun, Apr 23, 2023 at 3:30 PM Galen Adams wrote: > If that be the case, why then can I view all the data in the BEFOREs and > not see any IPTC or GPS data at all in the AFTERs; the GPS "Globe" > indicator in digiKam even disappears from the AFTERs. > The GPS is completely stripped from Windows "Properties" in the AFTERs and > disappears in FastStone; it is all there in the BEFOREs. > > If digiKam "repaired" the images, why then is that repair not evident in > any other program ? > > I am thoroughly confused and at a loss as I am not doing anything > different than I have been doing for ages and never had this before. > > > > > On Sun, Apr 23, 2023 at 3:08 PM Maik Qualmann > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=468832 >> >> --- Comment #14 from Maik Qualmann --- >> Galen, you're completely confusing something. Please check it out again. >> Your >> IPTC and GPS before images have no metadata whatsoever. >> Your other before images have different metadata errors where Exiv2 fails, >> invalid date format, unexpected GPS info pointer etc. In such a case we >> read >> the metadata with ExifTool. >> All your before pics are more or less broken, your after pics even have >> IPTC >> tags. >> >> Check if ExifTool works for you (ExifTool tab in sidebar shows metadata. >> >> With these sample images, digiKam-8.0.0 repaired your images rather than >> destroying them. >> >> Maik >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468832] Editing an existing Keyword Tag strips away all IPTC information from the image file.
https://bugs.kde.org/show_bug.cgi?id=468832 --- Comment #16 from Galen Adams --- If that be the case, why then can I view all the data in the BEFOREs and not see any IPTC or GPS data at all in the AFTERs; the GPS "Globe" indicator in digiKam even disappears from the AFTERs. The GPS is completely stripped from Windows "Properties" in the AFTERs and disappears in FastStone; it is all there in the BEFOREs. If digiKam "repaired" the images, why then is that repair not evident in any other program ? I am thoroughly confused and at a loss as I am not doing anything different than I have been doing for ages and never had this before. On Sun, Apr 23, 2023 at 3:08 PM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=468832 > > --- Comment #14 from Maik Qualmann --- > Galen, you're completely confusing something. Please check it out again. > Your > IPTC and GPS before images have no metadata whatsoever. > Your other before images have different metadata errors where Exiv2 fails, > invalid date format, unexpected GPS info pointer etc. In such a case we > read > the metadata with ExifTool. > All your before pics are more or less broken, your after pics even have > IPTC > tags. > > Check if ExifTool works for you (ExifTool tab in sidebar shows metadata. > > With these sample images, digiKam-8.0.0 repaired your images rather than > destroying them. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468832] Editing an existing Keyword Tag strips away all IPTC information from the image file.
https://bugs.kde.org/show_bug.cgi?id=468832 --- Comment #5 from Galen Adams --- There are three BEFORE that should still have all data intact and three AFTER that got all IPTC and GPS stripped when editing a KeyWord Tag. Previous versions of digiKam never did this. I am using version digiKam-8.0.0-20230330T081758-Win64-debug I will attempt to get a debug log if I can figure out how. Thanks. [image: 2023-04-22_111500_7DMkII_0001_BEFORE.jpg] [image: 2023-04-22_111501_7DMkII_0002_AFTER.jpg] [image: 2023-04-22_111501_7DMkII_0002_BEFORE.jpg] [image: 2023-04-22_111530_7DMkII_0003_AFTER.jpg] [image: 2023-04-22_111530_7DMkII_0003_BEFORE.jpg] [image: AFTER.jpg] [image: GPS_Before.jpg] [image: IPTC_Before.jpg] [image: 2023-04-22_111500_7DMkII_0001_AFTER.jpg] On Sun, Apr 23, 2023 at 12:03 AM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=468832 > > --- Comment #4 from Maik Qualmann --- > Please also create a DebugView log. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468832] Editing an existing Keyword Tag strips away all IPTC information from the image file.
https://bugs.kde.org/show_bug.cgi?id=468832 --- Comment #6 from Galen Adams --- Created attachment 158364 --> https://bugs.kde.org/attachment.cgi?id=158364&action=edit 2023-04-22_111500_7DMkII_0001_BEFORE.jpg --- Comment #7 from Galen Adams --- Created attachment 158365 --> https://bugs.kde.org/attachment.cgi?id=158365&action=edit 2023-04-22_111501_7DMkII_0002_AFTER.jpg --- Comment #8 from Galen Adams --- Created attachment 158366 --> https://bugs.kde.org/attachment.cgi?id=158366&action=edit 2023-04-22_111501_7DMkII_0002_BEFORE.jpg --- Comment #9 from Galen Adams --- Created attachment 158367 --> https://bugs.kde.org/attachment.cgi?id=158367&action=edit 2023-04-22_111530_7DMkII_0003_AFTER.jpg --- Comment #10 from Galen Adams --- Created attachment 158368 --> https://bugs.kde.org/attachment.cgi?id=158368&action=edit 2023-04-22_111530_7DMkII_0003_BEFORE.jpg --- Comment #11 from Galen Adams --- Created attachment 158369 --> https://bugs.kde.org/attachment.cgi?id=158369&action=edit AFTER.jpg --- Comment #12 from Galen Adams --- Created attachment 158370 --> https://bugs.kde.org/attachment.cgi?id=158370&action=edit GPS_Before.jpg --- Comment #13 from Galen Adams --- Created attachment 158371 --> https://bugs.kde.org/attachment.cgi?id=158371&action=edit IPTC_Before.jpg -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468832] Editing an existing Keyword Tag strips away all IPTC information from the image file.
https://bugs.kde.org/show_bug.cgi?id=468832 --- Comment #2 from Galen Adams --- Which operating system ? 64-bit Windows 7 Pro Which image type ? jpeg Do you use XMP sidecar ? NO Do you enable ExifTool to write metadata in image ? YES I just noticed it is also stripping away all GPS information On Sat, Apr 22, 2023 at 2:51 PM wrote: > https://bugs.kde.org/show_bug.cgi?id=468832 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > > CC||caulier.gil...@gmail.com > Component|Tags-Keywords |Metadata-Iptc > > --- Comment #1 from caulier.gil...@gmail.com --- > Which operating system ? > Which image type ? > Do you use XMP sidecar ? > Do you enable ExifTool to write metadata in image ? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468832] New: Editing an existing Keyword Tag strips away all IPTC information from the image file.
https://bugs.kde.org/show_bug.cgi?id=468832 Bug ID: 468832 Summary: Editing an existing Keyword Tag strips away all IPTC information from the image file. Classification: Applications Product: digikam Version: 8.0.0 Platform: Other OS: Other Status: REPORTED Severity: critical Priority: NOR Component: Tags-Keywords Assignee: digikam-bugs-n...@kde.org Reporter: gadams...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Just noticed this a couple days ago and have had it happen several times since. If I select all images containing a Keyword Tag and then Right-Click the tag > choose Properties > and edit the name of said tag, all IPTC information in it's entirety is stripped away from the image files = quite frustrating. This is a new problem that was not present in previous versions. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422208] digiKam sporadically becomes totally unresponsive (freezes up) when editing Tags
https://bugs.kde.org/show_bug.cgi?id=422208 --- Comment #16 from Galen Adams --- So far; so good. I have not had a freeze-up since switching to 8.0.0 Hopefully that will be the end of it. On Wed, Apr 19, 2023 at 9:55 AM wrote: > https://bugs.kde.org/show_bug.cgi?id=422208 > > --- Comment #15 from caulier.gil...@gmail.com --- > @Adams > > digiKam 8.0.0 is out. Problem still reproducible ? > > Best regards > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468652] Copy Keyword Tag and all of it's children, then Paste it into a target Keyword Tag.
https://bugs.kde.org/show_bug.cgi?id=468652 Galen Adams changed: What|Removed |Added CC||gadams...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468652] New: Copy Keyword Tag and all of it's children, then Paste it into a target Keyword Tag.
https://bugs.kde.org/show_bug.cgi?id=468652 Bug ID: 468652 Summary: Copy Keyword Tag and all of it's children, then Paste it into a target Keyword Tag. Classification: Applications Product: digikam Version: 8.0.0 Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: Tags-Keywords Assignee: digikam-bugs-n...@kde.org Reporter: gadams...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION When working in the Keyword Tag panels, an option in the Right-click menu to "Copy" the chosen Keyword Tag and all of it's child tags; and then, when Right-click the chosen "Target" Keyword Tag, an option to "Paste" the copied tag into the target tag. Basically, a more convenient means of "moving" Keyword Tags when dealing with lengthy tag trees. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468164] New: Collections or Albums = Confusion for Beginners
https://bugs.kde.org/show_bug.cgi?id=468164 Bug ID: 468164 Summary: Collections or Albums = Confusion for Beginners Classification: Applications Product: digikam Version: 8.0.0 Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: gadams...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION As I am a longtime digiKam user, I have gotten used to it and ignore the situation; however, I believe one of the main stumbling blocks to digiKam beginners and which may be cause for many giving up in confusion is the use of the names "Collection" and "Album"; both of which are simple plain old Folders or Directories, depending on your preference. Instead of "Manage Collections" , "Add a Collection" and what not, and then whatever Collection is added is then found as an "Album" in the Albums tree, I believe it would benefit potential new users if both "Collections" and "Albums" were simply called what they actually are = Folders or Directories. It is just an idea - thanks for considering it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468041] Simple Rename of a Collection in Collection list
https://bugs.kde.org/show_bug.cgi?id=468041 --- Comment #9 from Galen Adams --- Awesome, thanks! On Mon, Apr 3, 2023 at 2:53 PM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=468041 > > Maik Qualmann changed: > >What|Removed |Added > > > Latest Commit|| > https://invent.kde.org/grap >| > |hics/digikam/commit/5e28a86 >| > |5905f8340cb961f1af72f4c494c >||a210bd > Resolution|WORKSFORME |FIXED > > --- Comment #8 from Maik Qualmann --- > Git commit 5e28a865905f8340cb961f1af72f4c494ca210bd by Maik Qualmann. > Committed on 03/04/2023 at 19:51. > Pushed by mqualmann into branch 'master'. > > add simple renaming of the virtual album root > Related: bug 468120 > FIXED-IN: 8.0.0 > > M +2-2NEWS > M +1-1core/app/items/utils/contextmenuhelper_albums.cpp > M +1-1core/app/main/digikamapp.cpp > M +27 -4core/libs/album/engine/albummodificationhelper.cpp > M +1-5core/libs/album/treeview/albumselectiontreeview.cpp > > > https://invent.kde.org/graphics/digikam/commit/5e28a865905f8340cb961f1af72f4c494ca210bd > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468041] Simple Rename of a Collection in Collection list
https://bugs.kde.org/show_bug.cgi?id=468041 --- Comment #7 from Galen Adams --- Now I am confused a bit; what I am wanting to be able to easily change is the "virtual" collection name --- not the actual name of the folder in the system. For example, if I am working with three collections whose actual physical folders may be scattered all over, but I want them grouped right side-by-side while I am working with them, I can give all three folders a letter "A" or a letter "Z" as the first character of their virtual name and they will display together while I work with them. When I get the work finished, I can then remove that extra letter and the collections return to their original place in the list. On Mon, Apr 3, 2023 at 12:38 PM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=468041 > > --- Comment #6 from Maik Qualmann --- > Nothing has changed in the behavior, the real renaming of the root folder > is > still not possible and will not be for the reasons mentioned. I just added > the > version number. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468041] Simple Rename of a Collection in Collection list
https://bugs.kde.org/show_bug.cgi?id=468041 --- Comment #5 from Galen Adams --- Awesome, thanks! Yes...Awesome ! Thank you ! On Mon, Apr 3, 2023 at 11:56 AM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=468041 > > Maik Qualmann changed: > >What|Removed |Added > > >Version Fixed In||8.0.0 > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468041] Simple Rename of a Collection in Collection list
https://bugs.kde.org/show_bug.cgi?id=468041 --- Comment #4 from Galen Adams --- Got it, thanks! On Sat, Apr 1, 2023 at 2:38 PM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=468041 > > Maik Qualmann changed: > >What|Removed |Added > > > Resolution|INTENTIONAL |WORKSFORME > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468041] Simple Rename of a Collection in Collection list
https://bugs.kde.org/show_bug.cgi?id=468041 --- Comment #2 from Galen Adams --- The virtual Collection name is the name I was meaning; not the actual folder name in the system. For what it's worth, the only thing on my C-drive is the operating system; no data whatsoever is under C. Thanks. On Sat, Apr 1, 2023 at 12:16 PM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=468041 > > Maik Qualmann changed: > >What|Removed |Added > > > Component|general |Setup-Collections > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468041] New: Simple Rename of a Collection in Collection list
https://bugs.kde.org/show_bug.cgi?id=468041 Bug ID: 468041 Summary: Simple Rename of a Collection in Collection list Classification: Applications Product: digikam Version: 8.0.0 Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: gadams...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Windows machine. In Settings > Configure digiKam > Collections, in the Collection list, at the left end of each listed Collection where the displayed Collection name is visible --- I can double-left-click the Collection name and it becomes editable --- I can edit the name but the change does absolutely nothing and the Collection name never reflects the change I made --- maybe there is a step I am missing. I know I can click the circle thingie at the right end, and very glad that I can, but this is an involved multi-step process to accomplish a simple name change. Thanks; your hard work is much appreciated. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467982] New: Ability to create and apply Keyword Tag templates
https://bugs.kde.org/show_bug.cgi?id=467982 Bug ID: 467982 Summary: Ability to create and apply Keyword Tag templates Classification: Applications Product: digikam Version: 8.0.0 Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: Tags-Keywords Assignee: digikam-bugs-n...@kde.org Reporter: gadams...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Wishlist = the ability to select multiple keyword tags and create templates such that those tags could be added to a selected group of images at a single click . One would also need the ability to mouse over a template and see all the tags it contained, or otherwise be quickly able to do so. Also, have the ability to edit an already established template and either save it over itself or save it under a new name. A lot to ask for, I know. Thanks for all of the good work you guys are doing. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467916] This version has lost the ability to drag/drop image thumbnails onto Smiley Face icons in "People"
https://bugs.kde.org/show_bug.cgi?id=467916 --- Comment #3 from Galen Adams --- Thank you! On Wed, Mar 29, 2023 at 3:24 AM wrote: > https://bugs.kde.org/show_bug.cgi?id=467916 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > > Component|Tags-Keywords |Faces-Workflow > CC||caulier.gil...@gmail.com > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467916] This version has lost the ability to drag/drop image thumbnails onto Smiley Face icons in "People"
https://bugs.kde.org/show_bug.cgi?id=467916 --- Comment #2 from Galen Adams --- Thank you so much for this information. As I will never use Face Tagging, it is wonderful to know that I can get rid of all those annoying smiley faces --- Thank You On Wed, Mar 29, 2023 at 2:42 AM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=467916 > > Maik Qualmann changed: > >What|Removed |Added > > >Version Fixed In||8.0.0 > Resolution|--- |INTENTIONAL > CC||metzping...@gmail.com > Status|REPORTED|RESOLVED > > --- Comment #1 from Maik Qualmann --- > The behavior is intentional. Tag thumbnail with smiley are face tags. You > can > assign a thumbnail to this in the People view. If it is not a face tag, > you can > change it back to a normal tag in the People view. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467916] New: This version has lost the ability to drag/drop image thumbnails onto Smiley Face icons in "People"
https://bugs.kde.org/show_bug.cgi?id=467916 Bug ID: 467916 Summary: This version has lost the ability to drag/drop image thumbnails onto Smiley Face icons in "People" Classification: Applications Product: digikam Version: 8.0.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Tags-Keywords Assignee: digikam-bugs-n...@kde.org Reporter: gadams...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I just now discovered this missing ability. Always before, I have been able to drag/drop an image thumbnail onto a Smiley Face icon under the People tag heading and that image replace the Smiley Face. This version, drag/drop an image thumbnail onto it's appropriate Smiley Face icon does nothing; the Smiley Face stays there. Many, more than half, of my People keyword tag icons have the "normal" icon...; these work and I am able to replace the generic icon with an image thumbnail; it is only the keyword tags with the Smiley Face icons that give me trouble. Thanks for your time in addressing this issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467871] New: When adding thumbnail to parent tag, not require parent tag to be applied.
https://bugs.kde.org/show_bug.cgi?id=467871 Bug ID: 467871 Summary: When adding thumbnail to parent tag, not require parent tag to be applied. Classification: Applications Product: digikam Version: 8.0.0 Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: Tags-Keywords Assignee: digikam-bugs-n...@kde.org Reporter: gadams...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION As things currently are, when one wishes to add an image thumbnail to a parent tag's icon, that parent tag must first be applied to the image; this requires one to first apply the parent tag, then add the thumbnail, then remove the parent tag from the image. What would really be nice would be if any old image, tagged or not, could be applied as the tag's icon. This is just wishful thinking; I know you guys have far more important issues at hand. Thanks so much. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467623] I do "Item > Write Metadata to File" = Erases the Altitude field and leaves Altitude at Zero(0)
https://bugs.kde.org/show_bug.cgi?id=467623 --- Comment #31 from Galen Adams --- These are the BEFORE images - after the recent fix. [image: Before_2022-02-21_135925_D7D_0004_I.jpg] [image: Before_2022-02-21_140020_D7D_0007_I.jpg] [image: Before_2022-04-15_171811_D7D_0030_I.jpg] [image: Before.png] On Sat, Mar 25, 2023 at 12:30 AM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=467623 > > --- Comment #30 from Maik Qualmann --- > Note: With the Geolocation Editor you can remove zero altitudes that have > arisen or fill in the altitude automatically via the web service. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467623] I do "Item > Write Metadata to File" = Erases the Altitude field and leaves Altitude at Zero(0)
https://bugs.kde.org/show_bug.cgi?id=467623 --- Comment #28 from Galen Adams --- Maybe my explanation was unclear - like before, the affected images do have Altitude and not Altitude Reference. When I do Write Metadata to Selected Files, it still changes Altitude to Zero(0) and now it also fills in the Altitude Reference with Above Sea Level (which would be fine if it didn't change the Altitude) I will send more image files soon. On Fri, Mar 24, 2023 at 5:45 PM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=467623 > > --- Comment #27 from Maik Qualmann --- > I can't reproduce the problem. Note that XMP-GPS metadata takes precedence > over > Exif because of sidecars. Your sample images also have GPS metadata in XMP. > Otherwise send me a sample image that should not have any altitude > information > and with which the problem occurs. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467623] I do "Item > Write Metadata to File" = Erases the Altitude field and leaves Altitude at Zero(0)
https://bugs.kde.org/show_bug.cgi?id=467623 Galen Adams changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #26 from Galen Adams --- I have tested the fix = this is what is happening now when Write Metadata to Selected Files: When I choose a file(s) that lacks the Altitude reference, it changes the Altitude to Zero(0) and adds the reference Above Sea Level. Thanks -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467680] Add a Collections Dialogue Behavior
https://bugs.kde.org/show_bug.cgi?id=467680 --- Comment #2 from Galen Adams --- >> (Maik Qualmann)" I ask out of curiosity, why are they adding so many collections? I don't even use it once a year. I hope not they add each subfolder as a collection."<< I hope I can explain --- when images are in the process of having all metadata added and then being converted and edited, I let digiKam "see" that entire working folder. Then, when I have the finished jpegs, I "hide" everything except for the finished images; thus, when I do a keyword tag search, I am not inundated with fifteen versions of the same image; if I can find the finished image, I immediately know where all it's other versions are without having them clutter up my Tags View. I hope that makes sense; Thanks so Much. On Wed, Mar 22, 2023 at 4:02 AM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=467680 > > Maik Qualmann changed: > >What|Removed |Added > > > CC||metzping...@gmail.com > > --- Comment #1 from Maik Qualmann --- > I ask out of curiosity, why are they adding so many collections? I don't > even > use it once a year. I hope not they add each subfolder as a collection. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467680] New: Add a Collections Dialogue Behavior
https://bugs.kde.org/show_bug.cgi?id=467680 Bug ID: 467680 Summary: Add a Collections Dialogue Behavior Classification: Applications Product: digikam Version: 7.10.0 Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: gadams...@gmail.com Target Milestone: --- SUMMARY In digiKam version 5.9 and before, when I did Settings > Configure digiKam > Collections > Add a Collection, the dialogue would remember and open to the last place I had been = very handy = exactly the behavior I need. My next version was 6.4; in every version since, the dialogue always opens at the very beginning of things, forcing me to have to navigate through the entire folder tree to get to where I was just a few seconds before. If it is possible, and not too much trouble, it sure would be nice if the version 5.9 and earlier Add a Collection dialogue replaced the current one. Thanks. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The way I have always used digiKam, I very frequently work in the Add a Collection window, adding new Collections and otherwise manipulating them; the old style Add a Collection dialogue worked a lot better for me. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467669] Disable DNN models download at startup
https://bugs.kde.org/show_bug.cgi?id=467669 --- Comment #2 from Galen Adams --- Awesome, thanks! That will be a great help ! Appreciated ! On Tue, Mar 21, 2023 at 10:40 PM wrote: > https://bugs.kde.org/show_bug.cgi?id=467669 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > > Status|REPORTED|RESOLVED > Resolution|--- |FIXED >Version Fixed In||8.0.0 > > --- Comment #1 from caulier.gil...@gmail.com --- > Already implemented in next 8.0.0. Look at the bottom on this page : > > https://docs.digikam.org/fr/getting_started/quick_start.html > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467669] New: Suggestion for Next and Future Versions
https://bugs.kde.org/show_bug.cgi?id=467669 Bug ID: 467669 Summary: Suggestion for Next and Future Versions Classification: Applications Product: digikam Version: 7.10.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: gadams...@gmail.com Target Milestone: --- SUMMARY In the pop-up box that appears when digiKam opens, asking permission to download something for face recognition, it would be nice to have an option “No Thanks and Please Don’t Ask Me Again” Thank you. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION In the pop-up box that appears when digiKam opens, asking permission to download something for face recognition, it would be nice to have an option “No Thanks and Please Don’t Ask Me Again” Thank you. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467623] I do "Item > Write Metadata to File" = Erases the Altitude field and leaves Altitude at Zero(0)
https://bugs.kde.org/show_bug.cgi?id=467623 --- Comment #25 from Galen Adams --- Got it. Thanks for alerting me as I would probably not have thought about that myself before I messed up. On Tue, Mar 21, 2023 at 2:38 AM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=467623 > > --- Comment #24 from Maik Qualmann --- > Note that if a digiKam version is available with this fix, you will need to > re-read the metadata of images that do not contain an AltitudeRef so that > writing metadata does not result in zero altitude. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467623] I do "Item > Write Metadata to File" = Erases the Altitude field and leaves Altitude at Zero(0)
https://bugs.kde.org/show_bug.cgi?id=467623 --- Comment #23 from Galen Adams --- Awesome, thanks! Much Appreciated On Tue, Mar 21, 2023 at 2:31 AM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=467623 > > Maik Qualmann changed: > >What|Removed |Added > > >Version Fixed In||8.0.0 > Status|REPORTED|RESOLVED > Resolution|--- |FIXED > Latest Commit|| > https://invent.kde.org/grap >| > |hics/digikam/commit/40e0023 >| > |d0c2695f9399d2e939dd41a8925 >||3933ff > > --- Comment #22 from Maik Qualmann --- > Git commit 40e0023d0c2695f9399d2e939dd41a89253933ff by Maik Qualmann. > Committed on 21/03/2023 at 07:30. > Pushed by mqualmann into branch 'master'. > > if AltitudeRef is not present assume above sea level > FIXED-IN: 8.0.0 > > M +1-2NEWS > M +43 -39 core/libs/metadataengine/engine/metaengine_gps.cpp > > > https://invent.kde.org/graphics/digikam/commit/40e0023d0c2695f9399d2e939dd41a89253933ff > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467623] I do "Item > Write Metadata to File" = Erases the Altitude field and leaves Altitude at Zero(0)
https://bugs.kde.org/show_bug.cgi?id=467623 --- Comment #21 from Galen Adams --- >>" With which program or device was the GPS information written into your images?"<< Some were written with ExifToolGUI and some were written with XnViewMP. I checked some that were written with the onboard GPS in my 7DMkII and they work fine in digiKam Map. I would have thought that below sea level altitudes would have negative values; but then, I haven't taken any pictures under the ocean's surface. On Tue, Mar 21, 2023 at 2:10 AM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=467623 > > --- Comment #20 from Maik Qualmann --- > Thanks for the sample images. With which program or device was the GPS > information written into your images? The problem is that > Exif.GPSInfo.GPSAltitudeRef is not present in your images. So the > specification > below or above sea level. Therefore we ignore the altitude in the images > when > importing. We can of course simply assume above sea level as a bug fix if > GPSAltitudeRef is not available. I have never seen that the GPSAltitudeRef > information is missing if altitude is available. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467623] I do "Item > Write Metadata to File" = Erases the Altitude field and leaves Altitude at Zero(0)
https://bugs.kde.org/show_bug.cgi?id=467623 --- Comment #12 from Galen Adams --- Created attachment 157466 --> https://bugs.kde.org/attachment.cgi?id=157466&action=edit 2023-03-09_144748_S90_0002_A.jpg --- Comment #13 from Galen Adams --- Created attachment 157467 --> https://bugs.kde.org/attachment.cgi?id=157467&action=edit 2023-03-09_144807_S90_0003_A.jpg --- Comment #14 from Galen Adams --- Created attachment 157468 --> https://bugs.kde.org/attachment.cgi?id=157468&action=edit 2023-03-09_144709_S90_0001_B.jpg --- Comment #15 from Galen Adams --- Created attachment 157469 --> https://bugs.kde.org/attachment.cgi?id=157469&action=edit 2023-03-09_144748_S90_0002_B.jpg --- Comment #16 from Galen Adams --- Created attachment 157470 --> https://bugs.kde.org/attachment.cgi?id=157470&action=edit 2023-03-09_144807_S90_0003_B.jpg --- Comment #17 from Galen Adams --- Created attachment 157471 --> https://bugs.kde.org/attachment.cgi?id=157471&action=edit 2023-03-09_144709_S90_0001_C.jpg --- Comment #18 from Galen Adams --- Created attachment 157472 --> https://bugs.kde.org/attachment.cgi?id=157472&action=edit 2023-03-09_144748_S90_0002_C.jpg --- Comment #19 from Galen Adams --- Created attachment 157473 --> https://bugs.kde.org/attachment.cgi?id=157473&action=edit 2023-03-09_144807_S90_0003_C.jpg -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467623] I do "Item > Write Metadata to File" = Erases the Altitude field and leaves Altitude at Zero(0)
https://bugs.kde.org/show_bug.cgi?id=467623 --- Comment #11 from Galen Adams --- A suggestion --- use ExifTool, ExifToolGUI, or XnViewMP to add GPS and Altitude values in some test files - NOT in digiKam itself --- and then see if digiKam Map will display the Altitude. Thanks. On Mon, Mar 20, 2023 at 5:17 PM Galen Adams wrote: > Okay, I tested another bunch of jpegs. > Before doing anything in digiKam, embedded GPS data was showing the > correct Altitudes in every of several programs I checked including > ExifToolGUI and in digiKam itself. > These three image files "A" are BEFORE; note that Metadata > Exif > Global > Positioning System GPS Altitude is showing 314.2 m; whereas, in Map, > Altitude is showing "Undefined" > [image: 2023-03-09_144709_S90_0001_A.jpg] > [image: 2023-03-09_144748_S90_0002_A.jpg] > [image: 2023-03-09_144807_S90_0003_A.jpg] > > These are the same files, now "B", after "Item > Write Metadata to > Selected Files" : note that Metadata > Exif > Global Positioning System GPS > Altitude and Map are both now showing Zero (0) m; now, every program I > check shows the Altitude to be Zero (0). > > [image: 2023-03-09_144748_S90_0002_B.jpg] > [image: 2023-03-09_144807_S90_0003_B.jpg] > [image: 2023-03-09_144709_S90_0001_B.jpg] > > Here are the same three files, now "C", after restoring the correct > Altitude in ExifToolGUI and doing "Item > Reread Metadata from Files" ; > correct Altitude is displaying in all programs and MAP is still insisting > Altitude is Zero (0). > > [image: 2023-03-09_144748_S90_0002_C.jpg] > [image: 2023-03-09_144807_S90_0003_C.jpg] > [image: 2023-03-09_144709_S90_0001_C.jpg] > > Last, although the Altitude was displaying correctly in every other > program, I loaded the files in "Item > Edit Geolocation" and manually > entered the Altitude there; it would only allow me to do them one at a > time; then, and only then, did the correct Altitude finally show up in Map. > > This behavior has to be some sort of glitch in digiKam properly > recognizing the Altitude. > > Thanks for taking the time to investigate this. > > > > On Mon, Mar 20, 2023 at 2:46 PM Maik Qualmann > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=467623 >> >> Maik Qualmann changed: >> >>What|Removed |Added >> >> >> CC||metzping...@gmail.com >> >> --- Comment #1 from Maik Qualmann --- >> I can't reproduce the problem here with digiKam-8.0.0. >> The problem can actually only occur if the geolocation metadata has not >> been >> correctly read into the database. First look in the right sidebar in the >> map >> view. Is the altitude displayed correctly? Then perform a metadata write >> operation. Is their altitude actually reset then? If yes, we need a sample >> image with which the problem occurs. >> >> Maik >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467623] I do "Item > Write Metadata to File" = Erases the Altitude field and leaves Altitude at Zero(0)
https://bugs.kde.org/show_bug.cgi?id=467623 --- Comment #2 from Galen Adams --- Okay, I tested another bunch of jpegs. Before doing anything in digiKam, embedded GPS data was showing the correct Altitudes in every of several programs I checked including ExifToolGUI and in digiKam itself. These three image files "A" are BEFORE; note that Metadata > Exif > Global Positioning System GPS Altitude is showing 314.2 m; whereas, in Map, Altitude is showing "Undefined" [image: 2023-03-09_144709_S90_0001_A.jpg] [image: 2023-03-09_144748_S90_0002_A.jpg] [image: 2023-03-09_144807_S90_0003_A.jpg] These are the same files, now "B", after "Item > Write Metadata to Selected Files" : note that Metadata > Exif > Global Positioning System GPS Altitude and Map are both now showing Zero (0) m; now, every program I check shows the Altitude to be Zero (0). [image: 2023-03-09_144748_S90_0002_B.jpg] [image: 2023-03-09_144807_S90_0003_B.jpg] [image: 2023-03-09_144709_S90_0001_B.jpg] Here are the same three files, now "C", after restoring the correct Altitude in ExifToolGUI and doing "Item > Reread Metadata from Files" ; correct Altitude is displaying in all programs and MAP is still insisting Altitude is Zero (0). [image: 2023-03-09_144748_S90_0002_C.jpg] [image: 2023-03-09_144807_S90_0003_C.jpg] [image: 2023-03-09_144709_S90_0001_C.jpg] Last, although the Altitude was displaying correctly in every other program, I loaded the files in "Item > Edit Geolocation" and manually entered the Altitude there; it would only allow me to do them one at a time; then, and only then, did the correct Altitude finally show up in Map. This behavior has to be some sort of glitch in digiKam properly recognizing the Altitude. Thanks for taking the time to investigate this. On Mon, Mar 20, 2023 at 2:46 PM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=467623 > > Maik Qualmann changed: > >What|Removed |Added > > > CC||metzping...@gmail.com > > --- Comment #1 from Maik Qualmann --- > I can't reproduce the problem here with digiKam-8.0.0. > The problem can actually only occur if the geolocation metadata has not > been > correctly read into the database. First look in the right sidebar in the > map > view. Is the altitude displayed correctly? Then perform a metadata write > operation. Is their altitude actually reset then? If yes, we need a sample > image with which the problem occurs. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467623] New: I do "Item > Write Metadata to File" = Erases the Altitude field and leaves Altitude at Zero(0)
https://bugs.kde.org/show_bug.cgi?id=467623 Bug ID: 467623 Summary: I do "Item > Write Metadata to File" = Erases the Altitude field and leaves Altitude at Zero(0) Classification: Applications Product: digikam Version: 7.10.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Maintenance-Metadata Assignee: digikam-bugs-n...@kde.org Reporter: gadams...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Prior to digiKam, all GPS information is embedded in the jpeg file; checking digiKam metadata shows the correct Altitude. I do "Item > Write Metadata to File" = Erases the Altitude field and leaves Altitude at Zero(0) It happens with a single jpeg or a whole batch and it happens every time. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422208] digiKam sporadically becomes totally unresponsive (freezes up) when editing Tags
https://bugs.kde.org/show_bug.cgi?id=422208 --- Comment #6 from Galen Adams --- To the best of my knowledge, I have all rights in all related image and database folders set for full read/write access for all listed Users plus "Everyone", including full LAN access to all of our other machines. Is there some special rights that I must assign specifically for digiKam ? Thanks. On Sun, May 31, 2020 at 2:08 PM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=422208 > > --- Comment #5 from Maik Qualmann --- > DigiKam does not need administrator rights. Your database or images may > have > incorrect user rights. Then the right solution would be to set the correct > file > rights. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422208] digiKam sporadically becomes totally unresponsive (freezes up) when editing Tags
https://bugs.kde.org/show_bug.cgi?id=422208 --- Comment #4 from Galen Adams --- Sunday_31-May-2020 Update on my situation with digiKam freezing-up and crashing when performing operations in the Tags panels (64-bit Windows 7 Pro) I completely uninstalled everything and installed digiKam 6.4 Stable Release and gave it one more try = it froze and crashed with the very first operation I performed = force closed, re-opened, and tried again two more times with the same result. It finally dawned on me to try "Run as Administrator" With digiKam 6.4 running "as Administrator", I was able to successfully Tag and also edit Tags on several hundred images without a single crash. With digiKam opened with "Run as Administrator", everything I did seemed faster and more responsive. I have downloaded the "digiKam-7.0.0-rc-20200531T011237-Win64.exe" and intend to try it as soon as time allows. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422208] digiKam sporadically becomes totally unresponsive (freezes up) when editing Tags
https://bugs.kde.org/show_bug.cgi?id=422208 --- Comment #3 from Galen Adams --- Update on my situation with digiKam freezing-up and crashing when performing operations in the Tags panels (64-bit Windows 7 Pro) I completely uninstalled everything and installed digiKam 6.4 Stable Release and gave it one more try = it froze and crashed with the very first operation I performed = force closed, re-opened, and tried again two more times with the same result. It finally dawned on me to try "Run as Administrator" With digiKam 6.4 running "as Administrator", I was able to successfully Tag and also edit Tags on several hundred images without a single crash. With digiKam opened with "Run as Administrator", everything I did seemed faster and more responsive. I have downloaded the "digiKam-7.0.0-rc-20200531T011237-Win64.exe" and intend to try it as soon as time allows. Thank you. On Sat, May 30, 2020 at 4:17 AM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=422208 > > --- Comment #2 from Maik Qualmann --- > Please give us minimal feedback, otherwise we cannot help. > I see your other messages on PIXLS.US. > It is not a good idea to downgrade from digiKam-6.x.x to digiKam-5.9.0 due > to > database changes. > > If you have a problem that plugins do not appear in the menu, you must > delete > the kxmlgui5 directory (in Windows under "AppData/Local" > > From digiKam-7.0.0 there is a new option in the metadata settings, here the > writing of GPS information in images must be activated. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422208] New: digiKam sporadically becomes totally unresponsive (freezes up) when editing Tags
https://bugs.kde.org/show_bug.cgi?id=422208 Bug ID: 422208 Summary: digiKam sporadically becomes totally unresponsive (freezes up) when editing Tags Product: digikam Version: 6.4.0 Platform: MS Windows OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: Tags-Keywords Assignee: digikam-bugs-n...@kde.org Reporter: gadams...@gmail.com Target Milestone: --- SUMMARY digiKam sporadically becomes totally unresponsive (freezes up) when editing Tags; especially likely when right-clicking a tag to choose "Properties" Sometimes it will crash immediately when I right-click the Tag; other times, it will crash when I click "Properties" in the right-click context menu (Tags) Lately, it also frequently crashes when I drag/drop an image on the tag so as to become the tags thumbnail. I have completely uninstalled and re-installed several times and the problem either immediately returns, or will occur after a bit of use. I have described some of the problem here: https://discuss.pixls.us/t/digikam-freezes-when-right-click-a-tag/18381 It doesn't seem to matter whether it is a parent Tag or a child Tag, and is very random as to which and when it chooses to crash. It has happened in both the Left Tags Search panel and the Right Tags apply panel. When it does crash, everything about digiKam becomes totally unresponsive and never recovers to operable no matter how long I wait. When it crashes, many of the Tags thumbnail images disappear; however, a sure-fire way to make it crash again is to attempt to drag/drop another image - any image - onto any Tag that has had it's thumbnail to disappear. I only ever load jpegs in digiKam; digiKam only ever sees my finished jpegs. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION First, I will say this, in theory, design, and layout, digiKam has the absolute best means of applying and searching Keyword Tags; better than any other program I have ever used and I have many; HOWEVER, when dealing with more than just a handful of Tags, the entire Keyword Tag feature of digiKam is highly problematic and prone to unexpected results and crashes; it is my opinion that the stability of this wonderful Tagging system needs be addressed thoroughly. There are only two features in digiKam that I ever use; the Geolocation Editor and applying and searching Keyword Tags; I wish you guys would build a rock-solid Windows package that had only those two features - the Geolocation Editor and the exact same Tags feature, except rock-solid. Thanks for reading and all help is appreciated. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401542] I am losing more and more thumbnails in the left pane TAGS view. Everything used to work fine.
https://bugs.kde.org/show_bug.cgi?id=401542 --- Comment #8 from Galen Adams --- Created attachment 116745 --> https://bugs.kde.org/attachment.cgi?id=116745&action=edit DeBugView_ 08-Dec-2018_3AM DEBugView started, then started digiKam, switched from Albums View to Tags View in left pane, browsed through a sampling of the tags known to not display properly, replicated the problem with the white rectangles appearing wherever I click the problem thumbnails, switched back to Albums View, closed digiKam. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401542] I am losing more and more thumbnails in the left pane TAGS view. Everything used to work fine.
https://bugs.kde.org/show_bug.cgi?id=401542 --- Comment #6 from Galen Adams --- Created attachment 116672 --> https://bugs.kde.org/attachment.cgi?id=116672&action=edit DeBug View Here is my attempt at DeBug View. No matter what I tried, it would not allow Capture Global Win32; I even tried Run As Administrator. I opened DeBug View, clicked Capture, started digikam, and went back and forth between Albums and Tags View; in Tags View,I right-clicked some of the partially appearing thumbnails and replicated the white rectangles appearing on the thumbnails. I hope this is of some help in solving my problem. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401542] I am losing more and more thumbnails in the left pane TAGS view. Everything used to work fine.
https://bugs.kde.org/show_bug.cgi?id=401542 --- Comment #4 from Galen Adams --- Created attachment 116578 --> https://bugs.kde.org/attachment.cgi?id=116578&action=edit Even more errant Behavior This is new errant behavior that I have just discovered. Under this particular Tags view, there should be a total of 11 Items in two albums. It is only displaying 4 Items from one album that should have 8 Items. The info in the blue bar says only 3 Items, even though it is displaying 4 of the 8 that should be there. It completely ignores the second album that contains 3 Items. Under just this one tag heading, there are more and worse discrepancies each time I view. This behavior holds true for nearly all of my tags. This completely negates my main reason for using digiKam = being able to organize and find images by keyword tags. A few weeks ago, there was not a single flaw in my Tags view and now it is self-destructing. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401542] I am losing more and more thumbnails in the left pane TAGS view. Everything used to work fine.
https://bugs.kde.org/show_bug.cgi?id=401542 --- Comment #2 from Galen Adams --- Created attachment 116570 --> https://bugs.kde.org/attachment.cgi?id=116570&action=edit Third screenshot example of missing thumbnail behavior. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401542] I am losing more and more thumbnails in the left pane TAGS view. Everything used to work fine.
https://bugs.kde.org/show_bug.cgi?id=401542 --- Comment #1 from Galen Adams --- Created attachment 116569 --> https://bugs.kde.org/attachment.cgi?id=116569&action=edit Second screenshot example of missing thumbnail behavior. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401542] New: I am losing more and more thumbnails in the left pane TAGS view. Everything used to work fine.
https://bugs.kde.org/show_bug.cgi?id=401542 Bug ID: 401542 Summary: I am losing more and more thumbnails in the left pane TAGS view. Everything used to work fine. Product: digikam Version: 6.0.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: critical Priority: NOR Component: Tags-Keywords Assignee: digikam-bugs-n...@kde.org Reporter: gadams...@gmail.com Target Milestone: --- Created attachment 116568 --> https://bugs.kde.org/attachment.cgi?id=116568&action=edit Screenshot of example of missing thumbnail behavior. SUMMARY I am losing more and more thumbnails in the left pane TAGS view. Everything used to work fine. This problem started with digiKam 5.6.0; in an effort to repair, I installed 6.0.0Beta3 to no avail. I have rebuilt the thumbnail cache several times to no avail. Each time I open digiKam, I have lost more thumbnails in the TAGS search pane. Blank white space is there where the thumbnails should be. The correct number of tagged items displays in the blue separator bar. Sometimes, but not always, I can right-click the area where a thumbnail should be and it will then appear; however, I cannot perform any normal operations on the re-appeared thumbnail; anywhere that I left-click on the thumbnail will result in a white rectangle that appears and stays there. I can keep left-clicking until the white rectangles have completely obliterated the visible thumbnail. The thumbnails that do appear as they should are able to have normal operations performed on them. The problem started with only a few missing thumbnails; not there are several hundred that are affected. This behavior completely negates the reason for digiKam and Keyword Tagging. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
