[digikam] [Bug 472640] Batch Queue Manager Cannot see resize pixel size when Macintosh Widgets are selected
https://bugs.kde.org/show_bug.cgi?id=472640 --- Comment #11 from Geoff King --- Hi. I tried the latest, 8.2.0 prerelease, Build date: 10/19/23 on MacBook M2 with 13.6 (22G120). This issue persists. I see no changes. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467528] Images Locked in Finder are not obvious in Digikam and won't copy or delete.
https://bugs.kde.org/show_bug.cgi?id=467528 --- Comment #3 from Geoff King --- (In reply to Geoff King from comment #2) > Hi. It seems to be the same as before. I need to be aware that some files > can be "Locked" and go into Finder > Right Click File > Get Info, to change > that so they can be moved. forgot to mention this is with the latest, 8.2.0 prerelease, Build date: 10/19/23 on MacBook M2 with 13.6 (22G120). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412894] Import window causes digiKam to hang in macOS
https://bugs.kde.org/show_bug.cgi?id=412894 --- Comment #16 from Geoff King --- Hi. As an updated. I tried the latest, 8.2.0 prerelease, Build date: 10/19/23 on MacBook M2 with 13.6 (22G120). I tried connecting iPhone via cable and Nikon camera via cable. The Import interface just said: Failed to connect to the camera. Please make sure it is connected properly and turned on. Neither the Nikon or iPhone were listed, but the SSD which is part of the library was listed as a drive. It did not crash, scan, hang, or require a force close. It basically did nothing. Just didn't do anything to find images on iPhone or Nikon. So that may be an improvement that it doesn't hang. I have gotten used to importing images in a different way using Finder directly from the Nikon's SD card, so this bug doesn't really affect me now. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467528] Images Locked in Finder are not obvious in Digikam and won't copy or delete.
https://bugs.kde.org/show_bug.cgi?id=467528 --- Comment #2 from Geoff King --- Hi. It seems to be the same as before. I need to be aware that some files can be "Locked" and go into Finder > Right Click File > Get Info, to change that so they can be moved. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470556] Collection Storage Location Unavailable Mac
https://bugs.kde.org/show_bug.cgi?id=470556 --- Comment #10 from Geoff King --- (In reply to Maik Qualmann from comment #9) > Now check whether the digikam.uuid file exists in the removable media in the > root directory of the collection in the .dtrash folder. We then have to wait > until the next macOS update. yes - each collection contains a digikam.uuid -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470556] Collection Storage Location Unavailable Mac
https://bugs.kde.org/show_bug.cgi?id=470556 --- Comment #8 from Geoff King --- (In reply to Maik Qualmann from comment #7) > And the two collections on the removable media were already mounted with the > current digiKam version before? > > Maik Yes. I had used them a few days before. I don’t think I defined ( or created ) those settings on 8.2, not sure if that matters. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470556] Collection Storage Location Unavailable Mac
https://bugs.kde.org/show_bug.cgi?id=470556 --- Comment #6 from Geoff King --- Hello, I had this happen again. Mac updated to 13.6 yesterday. Digikam 8.2 Build Date 9/16/23 12:40 PM As before, had to update the path of the two collections for Collections on Removable Media. The Local Collection folder was unaffected. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472640] Batch Queue Manager Cannot see resize pixel size when Macintosh Widgets are selected
https://bugs.kde.org/show_bug.cgi?id=472640 --- Comment #5 from Geoff King --- It does affect other tools, not just BQM, like Editor, and export dialogs. Resizing the windows does not affect it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472640] Batch Queue Manager Cannot see resize pixel size when Macintosh Widgets are selected
https://bugs.kde.org/show_bug.cgi?id=472640 --- Comment #4 from Geoff King --- Created attachment 160551 --> https://bugs.kde.org/attachment.cgi?id=160551=edit screenshot showing Widget Style Macintosh. Sliders missing numbers like other styles. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472640] New: Batch Queue Manager Cannot see resize pixel size when Macintosh Widgets are selected
https://bugs.kde.org/show_bug.cgi?id=472640 Bug ID: 472640 Summary: Batch Queue Manager Cannot see resize pixel size when Macintosh Widgets are selected Classification: Applications Product: digikam Version: 8.1.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: BatchQueueManager-Core Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- On Mac. I had Widget Style to Macintosh. When using Batch Queue Manager, Resize tool. The slider that contains pixels or percent does not contain any numbers making this tool very hard to use. Just a slider with no numbers is visible. If I switch the Widget Style to Fusion, Breeze, or Windows, then I can see the number of pixels or percentage to resize. SOFTWARE/OS VERSIONS macOS: 13.5. KDE Frameworks Version: 5.106.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470556] Collection Storage Location Unavailable Mac
https://bugs.kde.org/show_bug.cgi?id=470556 --- Comment #2 from Geoff King --- Happened again - Something is changing during Mac updates. Last night updated from Mac 13.4.19(c) to Mac 13.5 and it happened again. The file path was lost. Had to reassign the two folders designated as "Collections on Removable Media". -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470556] New: Collection Storage Location Unavailable Mac
https://bugs.kde.org/show_bug.cgi?id=470556 Bug ID: 470556 Summary: Collection Storage Location Unavailable Mac Classification: Applications Product: digikam Version: 8.0.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- Hello, On my Mac (Air M2. Ventura 13.2) I am loosing the collection settings occasionally. >From Thumbnails double clicking the image shows: "The storage location of this image is currently not available". This has been going on for at least several months, and prior 7.x versions also I think. It will keep the collection settings for maybe a month or more. I'm guessing it may be due to updates being applied by Apple (maybe going from 13.3 to 13.4? and similar with prior versions) since it doesn't happen very often. When this happens, workaround is to go into Collection Settings and re-select the Collections. In this case today, the folder selected for "Local Collections" was okay. What wasn't connecting was the two folders I had listed under "Collections on Removable Media". These are two separate folders on the same external SSD drive. I keep this drive connected 98% of the time. Click the refresh button and re-assign those drives and all is good for another month or so. One thing I thought to try afterwards was to disconnect and re-connect that drive instead of rescanning - can try that next time it happens, but the drive seems to work fine in finder and other apps. STEPS TO REPRODUCE 1. No known steps, just happens periodically. Maybe every month or so. 2. OBSERVED RESULT "The storage location of this image is currently not available". EXPECTED RESULT Don't want images to lose the link to their locations on the disk. SOFTWARE/OS VERSIONS macOS: 13.4 KDE Plasma Version: KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP format.
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #37 from Geoff King --- (In reply to caulier.gilles from comment #32) > Geoff, > > Here you can find the AppImage demo loading a JPEG, editing with GMIC-Qt/B > and exporting to WEBP. As you can see all work as expected and metadata are > there... > > https://drive.google.com/file/d/18VxKzFfXsC02-euPluy1XmemknNfbmr_/ > view?usp=sharing > > I reproduced the same under MacOS without problem... > Hi Gilles, Here is a screencast of MacOS and Digikam 8.0.0 (3/30/2023) editing in GMIC filter and exporting to WEBP. The resulting thumbnail shows an image, but nothing in preview or editor. This affects WEBP and I have had no issues with other formats like PNG or JPEG or other built-in digikam effects. This also looks to affect Windows, but not Linux. I just picked a random photo, it happens to all (several) that I've tried. https://drive.google.com/file/d/1XuLik9J9X8WRuk8Xa761NdWVhAVmRogv/view?usp=share_link I also did another test where I used exiftool to remove all metadata from the WEBP version and then the thumbnail turned transparent. Regards, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP format.
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #36 from Geoff King --- (In reply to Maik Qualmann from comment #33) > The WBMP format probably comes from Qt directly. It's not relevant to us at > all. It comes from old cell phones and is a 1-Bit black and white format. It > has nothing to do with modern Webp. > > Maik Okay. I misunderstood this format. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #29 from Geoff King --- (In reply to caulier.gilles from comment #24) > New test, with test01.jpg open in editor, edited with gmic/B, and exported > to webp, jp2, and wbmp. > > All is fine expected for wbmp which is broken due to a bug in KImageFormats > codecs. > > https://i.imgur.com/Jsd8Gp9.png > > Exif, makernotes, and XMP are here for webp, jp2. The original JPEG file do > not have any GPS data, so... > > Gilles For me there is definitely something wrong with using gmic and exporting to WEBP on MacOS. I have tried several times (GMIC black & white filter and others) and it gives a transparent file exporting to WEBP. I also tried this on Windows and it gave similar results (one quick test). I looked at Ubuntu also, and it doesn't have the gmic plugin in the appimage. If I use the same source file, process using the digikam built in black and white module, then export, it works fine. When exporting to WEBP with or without editing, I lose the EXIF data. I tried several files with same results so don't think is my files. most webp export tests at quality 73 Thanks, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #28 from Geoff King --- WBMP corrupt export file bug filed here: https://bugs.kde.org/show_bug.cgi?id=467950 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 467950] New: Exporting a WBMP file on Digikam MacOS creates corrupt file.
https://bugs.kde.org/show_bug.cgi?id=467950 Bug ID: 467950 Summary: Exporting a WBMP file on Digikam MacOS creates corrupt file. Classification: Frameworks and Libraries Product: frameworks-kimageformats Version: 5.102.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alex.me...@kde.org Reporter: gski...@gmail.com CC: aa...@kde.org, kdelibs-b...@kde.org Target Milestone: --- SUMMARY WBMP file is created when exporting from Digikam, but is corrupt and small. See Digikam bug report thread here: https://bugs.kde.org/show_bug.cgi?id=467675#c25 STEPS TO REPRODUCE 1. Digikam 8.0.0 beta1. > Image Editor > Open a JPG for editing. 2. Click Export and select WBMP format 3. Export file. OBSERVED RESULT A file is exported, but is unusable. When trying to open it Digikam says it is corrupt. EXPECTED RESULT An image file. SOFTWARE/OS VERSIONS Windows: macOS: 12.6.3 Intel Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.15.8 ADDITIONAL INFORMATION Digikam Build date: 3/26/23 8:24 AM -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #27 from Geoff King --- Created attachment 157710 --> https://bugs.kde.org/attachment.cgi?id=157710=edit add missing jp2 test file from prior message Cannot attached test1.png and test4.jpg since they are too big. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #51 from Geoff King --- Hi Gilles, I created an account, forked, edited the text, saved 2 patch/commit files, and made a merge request. I got a message "Merge blocked: fast-forward merge is not possible. To merge this request, first rebase locally." Reading through the help file, I tried /rebase in a comment, but not sure that did anything. Any recommendations? Sorry to bother you with something like this, I've never used git or this system before so I'm probably missing something simple. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #17 from Geoff King --- Created attachment 157617 --> https://bugs.kde.org/attachment.cgi?id=157617=edit _test5 image -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #16 from Geoff King --- Created attachment 157616 --> https://bugs.kde.org/attachment.cgi?id=157616=edit _test3 image -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #15 from Geoff King --- Created attachment 157615 --> https://bugs.kde.org/attachment.cgi?id=157615=edit _test2 image -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #14 from Geoff King --- Created attachment 157614 --> https://bugs.kde.org/attachment.cgi?id=157614=edit _test0 image I am sharing the files from my tests and some new observations below. This is on digiKam-8.0.0-20230326T082403-MacOS-x86-64-debug.pkg with MacBook Pro Intel. -new issue noticed - metadata not being carried over to exported files, including comments and gps on Mac, I also tried on Ubuntu and the metadata does carry over. -new issue noticed - linux appimage doesn't include g'mic. -sorry forgot to capture the debug log _test0.jpg - original source use for all tests, opened in Image editor, and exported to the formats below. _test1.webp - no edits to original, just export as webp lossless, seems okay except no metadata or coordinates _test2.webp - no edits to original, just export as webp quality 65, no edits to original file, seems okay except no metadata or coordinates _test3.wbmp - no edits to original, just export as wbmp - corrupt, but 1.3 MB _test4.jp2 - edited in gmic with black and white filter before exporting, jpeg2000, no metadata carried over, but otherwise looks okay, _test5.webp - edited in gmic with black and white filter before exporting, small file created, image is missing, and shows transparent checkerboard pattern thumbnail _test6.jpg, edited in gmic with black and white filter before exporting, missing gps metadata, other metadata is present -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #49 from Geoff King --- Hi Gilles, I read through the G'MIC-Qt chapter in the digiKam online documentation and it looks good to me. I didn’t see any obvious errors. I could suggest a few minor grammatical or style changes if we want to be picky, but that may be just regional language use preference. If you would like me to suggest edits what is the best way to do that? Thanks, Geoff On Sun, Mar 26, 2023 at 4:28 AM wrote: > https://bugs.kde.org/show_bug.cgi?id=422996 > > --- Comment #48 from caulier.gil...@gmail.com --- > Hi Geoff, > > I write a G'MIC-Qt chapter in the digiKam online documentation. If you can > take > a look and give me a feedback, it will be very appreciate: > > > https://docs.digikam.org/en/image_editor/enhancement_tools.html#g-mic-qt-tool > > Thanks in advance > > 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 467675] digiKam fail to export to WEBP and WBMP formats
https://bugs.kde.org/show_bug.cgi?id=467675 Geoff King changed: What|Removed |Added Attachment #157579|0 |1 is obsolete|| --- Comment #11 from Geoff King --- Created attachment 157594 --> https://bugs.kde.org/attachment.cgi?id=157594=edit debug log for _test1 to _test 5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #10 from Geoff King --- Created attachment 157593 --> https://bugs.kde.org/attachment.cgi?id=157593=edit screenshot showing issues -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #9 from Geoff King --- Hi, I tried this new version. It is improved, but there are still issues. I don't have time to test more right now, but will get back to it. Results in short: -I think this is related to the gmic filter at times -can now export to webp (if make no gmic edits to image, other non-gmic edits cause no issue). -see screen capture _test1 -export as webp lossless 3, no edits to original file _test2 export as webp quality 65, no edits to original file _test 4 gmic.jp2 - okay, edited in gmic with black and white filter before exporting _test 5 gmic.webp - small file created, and shows transparent thumbnail -exporting to wbmp now creates a file, but that cannot be opened. The thumbnail shown is a generic WBMP icon. _test3 export as wbmp - corrupt, but 1.3 MB, no edits to original file. -If I edit image using gmic plugin before exporting the webp file is exported, but entirely transparent and small file size. See screenshot and text file. I can test some more if needed. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #5 from Geoff King --- Created attachment 157579 --> https://bugs.kde.org/attachment.cgi?id=157579=edit terminal log of error Debug output as requested. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #44 from Geoff King --- Hi, To add to my note about alpha transparency. If I start with png that I know has alpha transparency created in Affinity, it works fine. I can see with the transparency in digikam. GmicQT edits and exports image back into digikam with alpha transparency as png just fine. Maybe original starting image needs to have alpha transparency? Regards, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP and WEBMP formats
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #2 from Geoff King --- Hi Maik, I see WBMP and WEBP listed as Type-Mimes under ImageMagick loader and QImage loader. Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #43 from Geoff King --- Hi Gilles, GmicQT seems to be working really good now. I messed with it for a good while tonight and found crash issues with g'mic in testing. Now trying with a 2015 MacBook and MacOS 12.6.3. (In reply to caulier.gilles from comment #41) > > Now, as the plugin can be called more than once, i see another problem with > the image data. > > 1/ Apply a filter from GMic > 2/ Recall Gmic > 3/ Look the preview is full transparent. > > This happen only with certain kind of images. It's probably relevant of > number of color channels. I will take a look. > I do not see this issue. But see my comment further below about transparency. > Q: do you know if a host application use GmicQt in a batch processing ? > Typically, the idea is to make a digiKam Batch Queue Manager plugin... I don't know much about batch processing with GmicQT. Would be a nice addition I think. One Gmic issue I did see was that within GmicQT for some filters they have transparent areas, but the transparent parts were saved as black. For example the polaroid filter has a transparent outline. When I saved the image in Digikam this area turned black. I tried setting the Image Editor workspace format as PNG and exporting to PNG and TIFF and some other formats. After exporting, I tried opening the saved files in Affinity. Maybe I'm missing something, since I haven't really done a lot of transparency or editing in Digikam, but have done various transparency stuff in the past in other programs. Regards, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] New: Digikam fail to export to WEBP and WEBMP formats
https://bugs.kde.org/show_bug.cgi?id=467675 Bug ID: 467675 Summary: Digikam fail to export to WEBP and WEBMP formats Classification: Applications Product: digikam Version: 8.0.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- SUMMARY I tried exporting as webp from Image Editor and received the message "Failed to save file". In the case of webmp a corrupt file exports. This seems to be Mac specific. STEPS TO REPRODUCE 1. Open Image Editor 2. Export and select webp format. 3. Then prompted for lossless or not. Doesn't matter. Proceed to export OBSERVED RESULT received the message "Failed to save file". No file is exported for webp. A file is exported for webmp, but it is not viewable. EXPECTED RESULT Exported image. SOFTWARE/OS VERSIONS Windows: macOS: digiKam-8.0.0-20230321T050838-MacOS-x86-64 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 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #39 from Geoff King --- Hi Gilles, I tried with latest version today and can confirm those two filters (Colors/Mixer LAB and Color Temperature) do not crash. I also tried opening and closing the plugin several times running different filters and had zero crashes while using it with several edits to a photo. However, it did crash upon closing digikam. Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467528] New: Images Locked in Finder are not obvious in Digikam and won't copy or delete.
https://bugs.kde.org/show_bug.cgi?id=467528 Bug ID: 467528 Summary: Images Locked in Finder are not obvious in Digikam and won't copy or delete. Classification: Applications Product: digikam Version: 8.0.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- SUMMARY My camera has a button to protect images with a little key icon. When I get a good shot, I press that button to protect it from accidental deletion or to be able to find it easier. When the image are on the Mac, these are "Locked" (File Info - General). Images that are Locked are not obvious to see in Digikam. They cannot be moved or deleted. Digikam does not tell us why nothing is happening to these images. Since I am aware of this, I need to go into Finder and uncheck the "Locked" option and then they can be mangaed in Digikam like normal. It would be nice to have an indicator in Digikam to identify these and remind me why they can't be moved or deleted. Maybe an icon on thumbnail view? or other area? Option to unlock the images from within Digikam GUI? STEPS TO REPRODUCE 1. Protect image in camera 2. Finder considers these Locked. 3. Cannot move or delete images within Digikam until unlocked on a system level using Finder. OBSERVED RESULT Cannot move or delete images within Digikam until unlocked on a system level. EXPECTED RESULT GUI option to be able to unlock the images or at least see why these operations cannot be performed AND/OR an icon on the thumbnail telling me that this is a locked file. SOFTWARE/OS VERSIONS Windows: macOS: Only tested on MACOS 12.6.3 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.15.8 ADDITIONAL INFORMATION digiKam-8.0.0-20230318T115132-MacOS-x86-64.pkg -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #34 from Geoff King --- Hi, This is so much better. Thank You. I was able to use it and play with most filters now with no issues. The original report pointed to "Film Simulate" and that now works fine - no crashes after several processed photos with different settings. Also an earlier report pointed to "Artistic > Cartoon" and that now works fine also. I'm now using digiKam-8.0.0-20230318T115132-MacOS-x86-64.pkg on a MacBook Air 2022 12.6.3. However, I still did get a few repeatable crashes but they appear to be filter specific, for example, Colors > Mixer [LAB] or Color Temperature seems to always crash quickly when entering. I can report those separately if you prefer. Should I make a new bug report here or somewhere else? As it is now this is a big improvement and usable, if I stay away from a few specific filters. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407738] MacOS clicking Import causes a need to force quit
https://bugs.kde.org/show_bug.cgi?id=407738 --- Comment #12 from Geoff King --- Hello. Just an update. Same issue on Digikam 7.3.0 and Mac Big Sur 11.6. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430588] export from Image Editor not working on Mac
https://bugs.kde.org/show_bug.cgi?id=430588 --- Comment #26 from Geoff King --- Hello, I tested this and can export using both dialogs. However, I did notice that when using the native system dialog option the Cancel button has no effect. It continues on to prompt for the quality settings. I can then click Cancel again, or continue to Save. Thanks, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430588] export from Image Editor not working on Mac
https://bugs.kde.org/show_bug.cgi?id=430588 --- Comment #24 from Geoff King --- Hello, I tested again on 7.3.0 Build date: 4/23/21 9:12 PM 1) with "Use native file dialogs from system" un-checked it works fine. 2) with "Use native file dialogs from system" checked it silently fails and does not export the file. It never prompts for the Jpeg file quality or chroma settings. This is same as before. Thanks, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382631] View HDR metadata
https://bugs.kde.org/show_bug.cgi?id=382631 --- Comment #3 from Geoff King --- Sounds like a great addition! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407738] MacOS clicking Import causes a need to force quit
https://bugs.kde.org/show_bug.cgi?id=407738 --- Comment #11 from Geoff King --- I don't think this is worth the effort on MacOS. AFAIK all versions of Mac have the "Image Capture.app" so getting images into the system is easy. That is what I use (or the Nikon Transfer app now, that I've switched to Nikon), which works well too. With so ways to do this already, I don't think it is a necessary feature in the MacOS version of Digikam. In it's current state I'd rather see the "Import" feature disabled on MacOS? I wonder if there are people using it successfully on MacOS? Regards, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407738] MacOS clicking Import causes a need to force quit
https://bugs.kde.org/show_bug.cgi?id=407738 --- Comment #9 from Geoff King --- Hello. Just an update. Digikam 7.2.0 and Mac Catalina 10.15.7. Yes this issues is still there. The external USB drive MyBook is 3GB and I think Digikam gets stuck trying to preview/import all the photos. I had to force quit as I'm not sure when it may have finished. Can we have a "blacklist" in the settings that excludes drives like that if we want? Clicking the import triangle selection button I was given two options: -USB Disk MyBook [large USB I use for backups] -USB Disk MyBook [same large USB I use for backups with different name] I would like to be able to exclude this drive. Adding a camera would be nice, but I have multiple other ways to get photos off of the camera and into the filesystem, so it is not essential that digikam does this as well. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #25 from Geoff King --- Hello. Just an update. Still crashes immediately upon clicking gmic in digikam. In Showfoto it can usually run for few minutes but after a bunch of clicks of different settings or filters it will usually crash. rocess: digikam [15239] Path: /Applications/digiKam.org/digikam.app/Contents/MacOS/digikam Identifier:digikam Version: 7.2.0 (7.2.0) Code Type: X86-64 (Native) Parent Process:??? [1] Responsible: digikam [15239] User ID: 501 Date/Time: 2021-04-11 18:39:31.672 -0400 OS Version:Mac OS X 10.15.7 (19H524) Report Version:12 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430924] Mac External Display menus in wrong location
https://bugs.kde.org/show_bug.cgi?id=430924 --- Comment #5 from Geoff King --- Hello, here is an update. Still on Catalina with the 7.2.0-rc Build date: 2/7/21 3:49 PM (target: Debug). In the last few months I've started using multiple windows on Mac a lot more and sometimes see weird window behavior in other applications as well. I've noticed a menu in the wrong spot with Affinity Photo and some others. It usually is when I've dragged and dropped an application to another Display, but the app is still associated with the other original Display (as seen in the app icon, option menu, assign to menu). Maybe I just don't fully understand how Mac handles Displays vs Desktops or maybe it just doesn't work that well??? It does seem a little more easier to navigate when using the trackpad on the MacBook to navigate vs drag and dropping between windows or the Assign to command under the icon. I use a normal 3 button mouse. Some examples of programs that have strange window location issues include: Digikam = Language selection under Captions Description will show up in wrong place on same screen or other screen (this is the most serious looking glitch). Recent Tags under Captions, Tags will show up in different places. It rotates between different screen locations. Tag Manager will show up on the other screen. Handbrake = The Activity, Preview and Queue windows will show up on the other desktop. Affinity Photo = An adjustment layer settings such as Levels dialog will show up on the other desktop. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #23 from Geoff King --- Created attachment 134911 --> https://bugs.kde.org/attachment.cgi?id=134911=edit additional crash info from showfoto. This bug was originally about digikam, but I may also have relevant info from showfoto. Attached is a crash log from Showfoto. This is on Mac with digiKam-7.2.0-rc-20210115T054811-MacOS-x86-64-debug. I have a consistent crash in showfoto after using gmic. In the attached crash log, I had been playing with gmic just before, but had cleanly exited the editor and then closed showfoto. This happens consistently upon closing showfoto. If I run gmic, then showfoto will crash later. showfoto does not normally crash if I do not use gmic. This is significantly different than digikam because, in showfoto you can still used gmic usually, at least for a few minute before it crashes. However, in digikam it is crashing immediately for me now. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #22 from Geoff King --- Created attachment 134899 --> https://bugs.kde.org/attachment.cgi?id=134899=edit lldb log and terminal output for crash from gmic Including this since it is more recent, and I think I did the crash log correctly with more info, and the debug terminal output is also included and looks like it has useful info. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #20 from Geoff King --- Hello. I see that there is a new gmic version out 2.9.4 that includes some bug fixes. Could you please update to that newer version to see if it helps the situation on Mac. Currently it is crashing instantly upon starting the G'Mic effect. Thanks, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #19 from Geoff King --- Created attachment 134629 --> https://bugs.kde.org/attachment.cgi?id=134629=edit crash log BELOW HAD IMAGE IN EDITOR. CLICKED THE G'MIC-QT EFFECT AND IT CRASHED IMMEDIATELY. THIS IS A CHANGE FROM LAST TIME I TRIED IT A FEW DAYS AGO WHERE IT WOULD USUALLY CRASH ONCE IN G'MIC AFTER A FEW CLICKS. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #17 from Geoff King --- Do you need more feedback or crash reports from me? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 431162] New: Change Name of Auto Correction to "Lens Auto-Correction"
https://bugs.kde.org/show_bug.cgi?id=431162 Bug ID: 431162 Summary: Change Name of Auto Correction to "Lens Auto-Correction" Product: digikam Version: 7.2.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- There are two effects labeled as "Auto-Correction"; one for exposure/light/color and the other for lens correction. Would recommend you rename the lens effect as "Lens Auto-Correction". The other may be more descriptive as "Light Auto-Correction". -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #14 from Geoff King --- Hi, I do not see these filter errors on Ubuntu. It seems fine in some short testing. Also this Mac version seems to be noticeable slower to changes to the sliders or applying the effect when compared with a significantly lower spec Ubuntu machine I'm using for comparison. On the Mac, I did just get a crash, when clicking through filters. This was the Artistic > Cartoon filter after clicking the refresh button in the top right corner. I was also getting a "preview error:" in the preview pane which I didn't take a screenshot of. Process 37099 stopped * thread #58, stop reason = EXC_BAD_ACCESS (code=1, address=0x0) frame #0: 0x00013861b2d2 Editor_GmicQt_Plugin.so`gmic& gmic::_run(cimg_library::CImgList const&, unsigned int&, cimg_library::CImgList&, cimg_library::CImgList&, cimg_library::CImgList&, cimg_library::CImgList&, unsigned int const*, bool*, char const*, cimg_library::CImg const*) + 194 Editor_GmicQt_Plugin.so`gmic::_run: -> 0x13861b2d2 <+194>: cmpq %rcx, (%rax) 0x13861b2d5 <+197>: jne0x13861b2e8 ; <+216> 0x13861b2d7 <+199>: movq -0x108(%rbp), %rcx 0x13861b2de <+206>: cmpq %rcx, 0x8(%rax) Target 0: (digikam) stopped. (lldb) bt * thread #58, stop reason = EXC_BAD_ACCESS (code=1, address=0x0) * frame #0: 0x00013861b2d2 Editor_GmicQt_Plugin.so`gmic& gmic::_run(cimg_library::CImgList const&, unsigned int&, cimg_library::CImgList&, cimg_library::CImgList&, cimg_library::CImgList&, cimg_library::CImgList&, unsigned int const*, bool*, char const*, cimg_library::CImg const*) + 194 frame #1: 0x000138772643 Editor_GmicQt_Plugin.so`void* gmic_parallel(void*) + 115 frame #2: 0x7fff6faf0109 libsystem_pthread.dylib`_pthread_start + 148 frame #3: 0x7fff6faebb8b libsystem_pthread.dylib`thread_start + 15 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #12 from Geoff King --- Created attachment 134478 --> https://bugs.kde.org/attachment.cgi?id=134478=edit preview error example 1 I am getting lots of messages like this on various filters. This one was triggered by moving the brightness slider. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430924] Mac External Display menus in wrong location
https://bugs.kde.org/show_bug.cgi?id=430924 --- Comment #4 from Geoff King --- (In reply to caulier.gilles from comment #2) > Geoff, > > Here i can show Desktop1 and Desktop2 annotation on top of screens when i > reduce application windows with 3 fingers move up on the track-pad. This is > what you mean ? > Hi, Using the 3 finger swipe, I have 3 desktops labeled at the top of the screen currently. Desktop 1 = laptop Desktop 2 = laptop (normally unused) Desktop 3 = external monitor A few things to note: -In my original comment the "Desktop on Display 2" would correlate with Desktop 3. -I only get the right click menu on icon, Options, Assign to Desktop on Display X if I have three Desktops or more as shown above. If I only have minimum number of desktops, Desktop 1 (laptop) and Desktop 2 (external), then the right click icon Options menu does not have the Assign ability. > Q: where do you seen the famous pop-up exactly with "Display n" information ? Not sure what you are asking here? But here's a different example, to simplify the problem a little. I now changed the configuration and have 2 Desktops (laptop is Desktop 1 and external Monitor is Desktop 2). Did this through the 3 finger swipe and deleting a desktop. Digikam is on Desktop 2. I click on the Captions-Description-Title language dropdown. It shows up (incorrectly) on the right side of Desktop 1. It's in a location to where it should be if digikam were on Desktop 1. Further moving things around, I right click (longer hold) the green window maximize button and select Move to Built in Retina display. Now that digikam is on Desktop 1, I try the drop down again and it is in the correct location. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430923] EXIF viewer settings not updating EXIF Metadata view
https://bugs.kde.org/show_bug.cgi?id=430923 --- Comment #2 from Geoff King --- I forgot about that option. It works fine if I select custom or Photograph so this can be considered user error. It must have been on No Filter. Sorry about that. However, I notice there is something weird about selecting filters in the dialog. Upon first opening it, there was nothing selected in the filter dialog [so I couldn't tell which one was selected or not] I'm sure of this for IPTC and XMP at least]. So maybe there is a default [No Filter?] that is being used or needs to be initialized to something? Additionally to bring more clarity to this user interface, would recommend that the description in settings be reworded to something like "Select Metadata Fields to be Displayed when using Custom Filters" Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430924] New: Mac External Display menus in wrong location
https://bugs.kde.org/show_bug.cgi?id=430924 Bug ID: 430924 Summary: Mac External Display menus in wrong location Product: digikam Version: 7.2.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- Hello, I have a workaround for this as noted below, but want to point out the issue. I have an external monitor connected to a MacBook running Catalina 10.15.7. The External monitor is "Desktop on Display 2" and the laptop is "Desktop on Display 1". Sometimes certain selection lists that popup from the interface show up in the wrong area when Digikam is on Display 2. First click they are in the right place, next click they are on the wrong desktop or in the wrong place on the correct desktop. For example, dialogs that have this issue are the language selection in the Description Title and Captions, or the Recent Tags selection, and probably a few others. This happens when there is mismatch between what desktop Digikam is on (Display 2) and what is selected/shown in that Dock Menu. For example, the issue arises when Digikam is on Display 2 [external monitor] and dock menu says Display 1 [laptop screen]. The dock menu can be seen by right clicking the icon in the dock and selecting Options. When the Display is manually set, this is not a problem. It seems to be caused by dragging the main window between desktops. To workaround/mitigate this, is to manually make sure the Dock menu matches the display that Digikam is on through the Options menu in the Dock. This can be done by opening the options through the icon in the dock and select Desktop on Display 2 if Digikam is on Display 2. This may be a Mac or QT issue but I wanted to point it out. Thanks, Geoff digiKam-7.2.0-rc-20201228T154340-MacOS-x86-64.pkg -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407738] MacOS clicking Import causes a need to force quit
https://bugs.kde.org/show_bug.cgi?id=407738 --- Comment #7 from Geoff King --- This seems to have gotten worse since my last report. Now with digiKam-7.2.0-rc-20201228T154340-MacOS-x86-64 clicking import causes an immediate crash. This is from the terminal. Not sure if it helps. 020-12-28 16:18:27.341627-0500 digikam[22815:1172850] [digikam.geoiface] "ROADMAP" 2020-12-28 16:18:27.557102-0500 digikam[22815:1172850] [digikam.geoiface] 2020-12-28 16:18:27.682132-0500 digikam[22815:1174946] [digikam.import] Log ( "" "" : "Connecting to camera..." Process 22815 stopped * thread #73, name = 'Digikam::CameraController', stop reason = EXC_BAD_ACCESS (code=1, address=0x302f0) frame #0: 0x7fff6fae1e52 libsystem_platform.dylib`_platform_strlen + 18 libsystem_platform.dylib`_platform_strlen: -> 0x7fff6fae1e52 <+18>: pcmpeqb (%rdi), %xmm0 0x7fff6fae1e56 <+22>: pmovmskb %xmm0, %esi 0x7fff6fae1e5a <+26>: andq $0xf, %rcx 0x7fff6fae1e5e <+30>: orq $-0x1, %rax Target 0: (digikam) stopped. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430923] New: EXIF viewer settings not updating EXIF Metadata view
https://bugs.kde.org/show_bug.cgi?id=430923 Bug ID: 430923 Summary: EXIF viewer settings not updating EXIF Metadata view Product: digikam Version: 7.2.0 Platform: Homebrew (macOS) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Exif Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- When I edit the EXIF viewer template in Preferences-Views-Exif Viewer the changes are not reflected in the Metadata view panel on the right. For example, I remove the "Photographic Information - ApertureValue" and then click OK. I select some photos and the EXIF info still shows "Aperture" and a value for that [F8 in this case] in the panel on the right. Nothing in the EXIF panel seems to be able to be modified anymore. I set these preferences up a few months ago and it worked at that time. However, note that this seems to be only for the EXIF, as Makernote seems to work okay. This is on MacOS Catalina with the latest digiKam-7.2.0-rc-20201228T154340-MacOS-x86-64 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 430589] Want to disable face detection extra download on Mac version
https://bugs.kde.org/show_bug.cgi?id=430589 --- Comment #6 from Geoff King --- I just tried again to be sure and am now having the problem again. To test I deleted the 6 files in the facesengine directory. Started digikam. It downloaded 2 files fine, but got stuck on this third one. I tried restarting digikam a few times, but keep getting this message now. An error occurred during the download. File: deploy.prototxt Insecure redirect The download will continue at the next start. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430588] export from Image Editor not working on Mac
https://bugs.kde.org/show_bug.cgi?id=430588 --- Comment #20 from Geoff King --- Yes. the native dialog was checked. I unchecked it and it now exports correctly. I don’t remember checking that, but maybe I did? Problem solved. Thanks, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430589] Want to disable face detection extra download on Mac version
https://bugs.kde.org/show_bug.cgi?id=430589 --- Comment #4 from Geoff King --- Yes. no issues second time. Thanks, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430588] export from Image Editor not working on Mac
https://bugs.kde.org/show_bug.cgi?id=430588 --- Comment #18 from Geoff King --- Here is the updated output. Looks the same as last time. 2020-12-22 10:00:17.217393-0500 digikam[3282:123620] [digikam.general] startSavingAs called 2020-12-22 10:00:36.147731-0500 digikam[3282:123620] modalSession has been exited prematurely - check for a reentrant call to endModalSession: 2020-12-22 10:00:36.147983-0500 digikam[3282:123620] [digikam.general] File Save Dialog rejected 0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430588] export from Image Editor not working on Mac
https://bugs.kde.org/show_bug.cgi?id=430588 --- Comment #12 from Geoff King --- there was something not working with the new debug version. I removed the whole digikam directory and then re-installed the non-debug version and it is now working like it was yesterday. Images can load, but cannot export like original report. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430588] export from Image Editor not working on Mac
https://bugs.kde.org/show_bug.cgi?id=430588 --- Comment #11 from Geoff King --- I've tried the new debug version and can no longer open images in the Image Editor. digiKam-7.2.0-beta2-20201221T205556-MacOS-x86-64-debug I now get an error Cannot load when trying to load a photo in the Image Editor 2020-12-21 19:22:24.644512-0500 digikam[13800:1640774] [digikam.geoiface] 2020-12-21 19:22:24.657588-0500 digikam[13800:1643155] [digikam.dimg] "/Volumes/MyBook_3TB/Pictures/import/Temp-Share/20150607_IMG_0685.jpeg" : Unknown image format !!! 2020-12-21 19:22:24.657629-0500 digikam[13800:1643155] [digikam.general] Cannot load image for "/Volumes/MyBook_3TB/Pictures/import/Temp-Share/20150607_IMG_0685.jpeg" 2020-12-21 19:22:24.694557-0500 digikam[13800:1640774] [digikam.general] d->image is NULL 2020-12-21 19:22:24.706155-0500 digikam[13800:1640774] [digikam.general] d->image is NULL 2020-12-21 19:22:24.706319-0500 digikam[13800:1640774] [digikam.general] d->image is NULL -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430588] export from Image Editor not working on Mac
https://bugs.kde.org/show_bug.cgi?id=430588 --- Comment #5 from Geoff King --- I have two buttons, Cancel and Save. Both give the same result. Save is the default. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430588] export from Image Editor not working on Mac
https://bugs.kde.org/show_bug.cgi?id=430588 --- Comment #2 from Geoff King --- As requested, See Below. It doesn't matter what format I pick. 2020-12-19 12:52:08.393815-0500 digikam[8488:1121748] [digikam.dimg.jpeg] End Of Image ( 1 ) 2020-12-19 12:52:55.275563-0500 digikam[8488:1119892] [digikam.general] startSavingAs called 2020-12-19 12:53:20.779100-0500 digikam[8488:1119892] modalSession has been exited prematurely - check for a reentrant call to endModalSession: 2020-12-19 12:53:20.779318-0500 digikam[8488:1119892] [digikam.general] File Save Dialog rejected -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #10 from Geoff King --- Unfortunately GMicQT crashes more often than before. The dialog will open, and I can usually select a filter and change some settings. However, it usually crashes when clicking Apply. This is on Catalina 10.5.7 and digiKam-7.2.0-beta2-20201219T112949-MacOS-x86-64 Thanks, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430589] New: Want to disable face detection extra download on Mac version
https://bugs.kde.org/show_bug.cgi?id=430589 Bug ID: 430589 Summary: Want to disable face detection extra download on Mac version Product: digikam Version: 7.2.0 Platform: MacPorts Packages OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- I have two comments about face detection. 1 - I can't download the extra required content on Mac. 2 - I would like an option to disable the requirement for extra content on Mac. I-am having trouble downloading the face detection extra content. I have tried a few times and am getting errors like this: An error occurred during the download. File: openface_nn4.small2.v1.t7 Insecure redirect The download will continue at the next start. An error occurred during the download. File: yolov3-wider_16000.weights Insecure redirect The download will continue at the next start. I have made sure that Digikam has access to the hard drive in settings. However, For me, I don't think I'm going to use this new feature, and would like to disable the requirement to download extra content. I have been clicking cancel, but it keeps asking me at every restart. This on Catalina 10.15.7 and digiKam-7.2.0-beta2-20201219T112949-MacOS-x86-64.pkg Thanks, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407738] MacOS clicking Import causes a need to force quit
https://bugs.kde.org/show_bug.cgi?id=407738 --- Comment #6 from Geoff King --- Hello. Tested on macOS Catalina 10.15.7 and digiKam-7.2.0-beta2-20201219T112949-MacOS-x86-64. I have no changes to my prior comments #3 and #4. My biggest problem is that it defaults to trying to search and load the entire 3GB USB hard drive I have connected most of the time. Thanks and Merry Christmas to you too. Regards, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430588] New: export from Image Editor not working on Mac
https://bugs.kde.org/show_bug.cgi?id=430588 Bug ID: 430588 Summary: export from Image Editor not working on Mac Product: digikam Version: 7.2.0 Platform: MacPorts Packages OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- On digiKam-7.2.0-beta2-20201219T112949-MacOS-x86-64 on Catalina 10.15.7. The Export menu does not export any images. STEPS TO REPRODUCE 1. Open Image Editor with image 2. Optionally edit the image. 3. Click Export Menu 4. user is prompted for save as folder, filename and filetype [defaults to heic which is annoying, but topic of another bug]. Change to JPEG or TIF. 5. Click Save 6. Expect the file to be saved, but it is not saved. I tried this on Ubuntu and it worked fine, it seems to be Mac specific. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372487] BQM says there are unprocessed items even though it completed successfully and all images were processed
https://bugs.kde.org/show_bug.cgi?id=372487 --- Comment #10 from Geoff King --- Hello. Tested on macOS Catalina 10.15.7 and digiKam-7.2.0-beta2-20201219T112949-MacOS-x86-64 I don't see any changes. I still find the dialog a little confusing. I tried it and processed Queue #1. The batch change was successful. Then went to "Remove Queue" and it said there are still unprocessed items. Regards, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414117] Full screen cannot close Image Editor by clicking Close Editor
https://bugs.kde.org/show_bug.cgi?id=414117 --- Comment #12 from Geoff King --- I've tried this on digiKam-7.2.0-beta2-20201219T112949-MacOS-x86-64 on Catalina 10.15.7. I can still get to a point where I cannot close the editor easily. It seems that something has improved and can explain the problem better below. I think there were also complications related to using an external monitor and my inexperience using Apples' Mission Control, which I'm learning better now. To hone in on the issue further 1 - start digikam 3 - click Image Editor, and load selected image. 4 - Maximize Image Editor using Apple Green maximize button. note I'm using multi-monitor and this image is on the second monitor as I like it. 5 - click Close Editor from Full Screen Image Editor. The Image Editor then returns back to normal image windowed size, rather than closing [should have closed]. Additionally, the Exit Full Screen button and Close Editor buttons are both inoperable and do nothing when clicked, but the Close Editor button is highlighted like it is selected. The Exit Full Screen button should not be shown at this point since it returned to windowed size. 6 - I can exit from this inoperable state by reloading the image from the Thumbnail screen. Once that is reloaded, the Close Editor button works and the Exit Full Screen button vanishes [as expected]. Thoughts/Solutions: - There is something going wrong when clicking the Close Editor button when in Full Screen. it comes out of full screen and becomes windowed, but still thinks it's full screen. - Do not show "Close Editor" button when in full screen mode. Enforce that full screen is exited before closing editor. Hope that helps you understand the issue better. Thanks and Merry Christmas to you also. Regards, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429221] New: Digikam Editor White Balance Effect Shadows Slider Not Working
https://bugs.kde.org/show_bug.cgi?id=429221 Bug ID: 429221 Summary: Digikam Editor White Balance Effect Shadows Slider Not Working Product: digikam Version: 7.1.0 Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Plugin-Editor-WB Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- SUMMARY The White Balance Effect Shadows Slider does not appear to do much if anything. When moving it, the histogram shows some small changes but I'm not seeing anything change in the image. Tried this on Windows and Mac Versions. STEPS TO REPRODUCE 1. Editor 2. White Balance Tool 3. Move Shadows slider - don't think it is doing what it is supposed. OBSERVED RESULT Very little change. There does appear to be a little change between Before/After, but not due to the Shadows slider. EXPECTED RESULT More control of shadows from the slider. SOFTWARE/OS VERSIONS Windows: 7.1 macOS: 7.1 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 423993] Allow rightclick on thumbnails in preview mode
https://bugs.kde.org/show_bug.cgi?id=423993 --- Comment #4 from Geoff King --- I find the current behavior un-intuitive. If you select multiple images in the Preview Mode, then you can still do operations on them, but you need to right click on the preview. For example, you select 5 images and want to add them to the batch queue manager. You must first move down to the single preview image and then right click. Or another example is Rotate or Move to Trash in the right click menu would operate on multiple images, where you only right clicked on the big preview. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427312] New: Add right click menu to thumbnails in Preview
https://bugs.kde.org/show_bug.cgi?id=427312 Bug ID: 427312 Summary: Add right click menu to thumbnails in Preview Product: digikam Version: 7.1.0 Platform: macOS (DMG) OS: Other Status: REPORTED Severity: minor Priority: NOR Component: Preview-Image Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- While in Preview Mode. There are thumbnails and the previewed image. If I click on the thumbnail image, I cannot use the right click menu. It would be nice to be able to do that. STEPS TO REPRODUCE 1. Open Preview Mode. 2. Click on one of the thumbnail images (not the previewed image) 3. Right click to bring up the menu. OBSERVED RESULT No menu EXPECTED RESULT see a menu like you do with the previewed image or the Thumbnail mode. 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 407738] MacOS clicking Import causes a need to force quit
https://bugs.kde.org/show_bug.cgi?id=407738 --- Comment #4 from Geoff King --- I'm already updating my long comment a minute before... The SD Flash card did eventually show up and work for importing. It has two entries: "SD Card Reader" and "CANON_DC". Trying to import from "SD Card Reader" gives error saying failed to connect to camera, but the "CANON_DC" works fine. A way to eliminate unneeded import options would be great. In my case if I could not have a default and eliminate the "SD Card Reader" and two MyBook options, that would solve most of my issues with importing. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407738] MacOS clicking Import causes a need to force quit
https://bugs.kde.org/show_bug.cgi?id=407738 --- Comment #3 from Geoff King --- Hello. Tested on macOS Catalina 10.15.6 and Digikam 7.0.0. Yes this issues is still there. The external USB drive MyBook is 3GB and I think Digikam gets stuck trying to preview import all the photos. I had to force quit as I'm not sure when it may have finished. Can we have a "blacklist" in the settings that excludes drives like that if we want? It should probably be that way by default. I'm sure some people do have USB drives they might want to use. I can also select other cameras by clicking the triangle option next to Import, which is a better option. I don't like the default option when clicking Import. However, on the positive side, I was able to add my Fuji camera to the list in the settings using Auto-Detect. I was able to set a download directory in settings. clicking the import button I was given three options: -USB Disk MyBook [large USB I use for backups] -USB Disk MyBook [same large USB I use for backups with different name] -Fuji camera... [newly added] I clicked the Fuji option and was able to download the files correctly. Other issues encountered with Import: -iPhone 8 not detected initially at setup. I learned that can only have 1 camera plugged in at a time during detection. Once I removed the Fuji, the iPhone was detected and was able to be used for import. -Flash SD card from other camera not detected by digikam (didn't try hooking it up via USB, usually easier to just remove the card) Final thoughts. This import feature would be nice for many I think. However, the built in Mac "Image Capture.app" works well too as far as I'm aware all Macs have this. If this feature isn't working fully or still presents problems, I think it should be disabled on Mac and people should be made aware to use the Image Capture app instead if they need guidance. Could it be labeled "experimental" or "beta"? Thanks, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414117] Full screen cannot close Image Editor by clicking Close Editor
https://bugs.kde.org/show_bug.cgi?id=414117 --- Comment #9 from Geoff King --- Hello. Tested on macOS Catalina 10.15.6 and Digikam 7.0.0. This is the same as originally reported. Maybe one minor difference is that to close I had to go to the Dock and right click to close it once it became unresponsive. Thanks, G -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #8 from Geoff King --- Hello. Tested on macOS Catalina 10.15.6 and Digikam 7.0.0. I tried G'Mic on a few files, I did a few tries, and went for about 10 minutes clicking through different filters and changing settings. However, I did get several crashes eventually, which seem to be more prevalent with some of the filters in the Color category, such as Abstraction and CMYK Tone. The crashes happened when selecting the filter. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372487] BQM says there are unprocessed items even though it completed successfully and all images were processed
https://bugs.kde.org/show_bug.cgi?id=372487 --- Comment #8 from Geoff King --- Hello. Tested on macOS Catalina 10.15.6 and Digikam 7.0.0. I don't see any changes. I still find the dialog a little confusing. I tried it and processed Queue #1 twice. Then went to "Remove Queue" and it said there are still 2 unprocessed items. See comment 4, maybe just a clarification of the text would help? Maybe there is a way to make a distinction between already processed and unprocessed queues? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365263] Dragging a image to an Album cannot see which album easily
https://bugs.kde.org/show_bug.cgi?id=365263 --- Comment #4 from Geoff King --- Hello. Tested on macOS Catalina 10.15.6 and Digikam 7.0.0. I see no changes from the previous report. It is still a wishlist item to see the destination album highlighted when moving or copying files by drag and drop. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423847] New: Root Album Tree View could use the right click refresh option
https://bugs.kde.org/show_bug.cgi?id=423847 Bug ID: 423847 Summary: Root Album Tree View could use the right click refresh option Product: digikam Version: 7.0.0 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Albums-TreeView Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- It would be nice to have a right click option to refresh an album root folder. I have a few root album collections (folders). For example one is called Import. If I right click it I get two options, New and Open in File Manager. If I want to refresh it manually, I go to View Menu or F5. However, sub-folders have other right click options like, Refresh. Would it be possible to add Refresh as a right click option to the Album Root Folder? This is with the Digikam 7.0.0-rc and macOS: 10.15.5 Thanks for all you do with digikam. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423033] New: Search for File Size Greater Than 95MB doesn't work and increments must be 0.5MB
https://bugs.kde.org/show_bug.cgi?id=423033 Bug ID: 423033 Summary: Search for File Size Greater Than 95MB doesn't work and increments must be 0.5MB Product: digikam Version: 7.0.0 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Searches-Advanced Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- SUMMARY In using Advanced Search, no results are returned if the second box for File Size is greater than 95.0MB. For example 95.5MB doesn't return any images. Also possibly related. It appears that values must be in exact increments of 0.5MB to be accepted. If I manually type in a value then that may also not return any images, where some should be returned. STEPS TO REPRODUCE 1. Select File Size from (e.g. 41.5MB) to (e.g. 95.5MB) 2. Click Try 3. No results are observed. However, If I set the second box to 95.0MB, then I get 187 results (mostly psd, tif and mov) OBSERVED RESULT No files were observed however, I know there several. Second Example: 1. Select File Size from (e.g. 0.1MB) to (e.g. 0.3MB) by manually typing in values in the boxes. OBSERVED RESULTS No files were returned but there should be many thousands. SOFTWARE/OS VERSIONS Windows: macOS: Mojave 10.14.6 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Build date: Jun 14 2020 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with G'Mic on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #4 from Geoff King --- Hello, I am successfully using the G'MIC-Qt plug-in for GIMP. It is an older version (2.7.3_pre#190929) on 2.10.14. It runs normally with no crashes after several tries today. Thanks, Geoff -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with G'Mic on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #2 from Geoff King --- This is for Mac 10.14.6. I have tried one or two of the earlier versions in the last month or so and they also exhibited this issue. I'm not sure about earlier betas. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] New: Digikam Crash with G'Mic on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 Bug ID: 422996 Summary: Digikam Crash with G'Mic on Mac Mojave Product: digikam Version: 7.0.0 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: ImageEditor Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- I am getting repeatable crashes when using the G'Mic plugin with Digikam 7.0 rc on Mac Mojave. This is with the digikam debug version from 20200614. Editor Open. Opened G'MIC-QT. Took a few tries of opening and closing things, but eventually crashed again. Seemed repeatable with the Film Simulation. I have not tried other OS, as I'm mostly a Mac user. Process 14270 stopped * thread #51, name = 'FilterThread', stop reason = EXC_BAD_ACCESS (code=1, address=0x1624a558c) frame #0: 0x000125a0b52e Editor_GmicQt_Plugin.so`gmic::add_commands(char const*, char const*, unsigned int*, unsigned int*, bool*) + 5630 Editor_GmicQt_Plugin.so`gmic::add_commands: -> 0x125a0b52e <+5630>: movb (%r13), %al 0x125a0b532 <+5634>: testb %al, %al 0x125a0b534 <+5636>: jne0x125a0b2e0 ; <+5040> 0x125a0b53a <+5642>: movq -0x80(%rbp), %r12 Target 0: (digikam) stopped. (lldb) bt * thread #51, name = 'FilterThread', stop reason = EXC_BAD_ACCESS (code=1, address=0x1624a558c) * frame #0: 0x000125a0b52e Editor_GmicQt_Plugin.so`gmic::add_commands(char const*, char const*, unsigned int*, unsigned int*, bool*) + 5630 frame #1: 0x0001259feb76 Editor_GmicQt_Plugin.so`void gmic::_gmic(char const*, cimg_library::CImgList&, cimg_library::CImgList&, char const*, bool, float*, bool*) + 1782 frame #2: 0x000125a0ee91 Editor_GmicQt_Plugin.so`gmic::gmic(char const*, char const*, bool, float*, bool*, float const&) + 673 frame #3: 0x0001259941d1 Editor_GmicQt_Plugin.so`FilterThread::run() + 449 frame #4: 0x000104fa8ad4 QtCore`___lldb_unnamed_symbol473$$QtCore + 248 frame #5: 0x7fff6773b2eb libsystem_pthread.dylib`_pthread_body + 126 frame #6: 0x7fff6773e249 libsystem_pthread.dylib`_pthread_start + 66 frame #7: 0x7fff6773a40d libsystem_pthread.dylib`thread_start + 13 (lldb) -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 322117] Open directory in File Manager and Open directory In Terminal not working under Windows and OSX
https://bugs.kde.org/show_bug.cgi?id=322117 Geoff King changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #7 from Geoff King --- I think this bug can be marked as resolved. I just tried using latest 7.0 beta versions on both Windows 10 and Mac Mojave and was able to use menus to "Open in File Manager". Both worked. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418446] Move Filters menu from right to left side of main window
https://bugs.kde.org/show_bug.cgi?id=418446 --- Comment #2 from Geoff King --- Ok. I see what you mean. thanks for the explanation. regards. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418446] New: Move Filters menu from right to left side of main window
https://bugs.kde.org/show_bug.cgi?id=418446 Bug ID: 418446 Summary: Move Filters menu from right to left side of main window Product: digikam Version: 7.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-Filters Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- The Filters "menu" on the right side of the window seems out of place to me. Items on the right side are generally metadata related for editing and viewing, not searching. I think it would be better placed on the left side of the main window where most other searching or filtering is done (Dates, Timeline, Tags, etc.). Not a bug or issue, I just think a more logical place for this would be on the left. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414117] Full screen cannot close Image Editor by clicking Close Editor
https://bugs.kde.org/show_bug.cgi?id=414117 --- Comment #6 from Geoff King --- Hi . Yes I'm still having problems with this. It is difficult to work in Full-Screen mode when going into and out of Image Editor. Trying this with the latest package "digiKam-7.0.0-beta2-20200120T075420-MacOS-x86-64" I have not seen the transparent window with this version, but I still do get stuck in the image editor and cannot intuitively close it. How to get out of Full-Screen Image Editor un-successfully: From Image Editor, click the Close Editor button. The window minimizes, but stays on the image editor and the Close Editor button does nothing. Then must close Digikam since no other options work. Similar scenario if click the large tab at the top right that corresponds do the Image Editor. If click the large tab at the top left that corresponds do the Thumbnail view, then all Digikam quits. The only way to get out of Full-Screen Image Editor successfully is to first close full-screen: From Image Editor, Exit Fullscreen button, Close Editor Button. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414117] Full screen cannot close Image Editor by clicking Close Editor
https://bugs.kde.org/show_bug.cgi?id=414117 --- Comment #4 from Geoff King --- Created attachment 124036 --> https://bugs.kde.org/attachment.cgi?id=124036=edit transparent window after closing -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414117] Full screen cannot close Image Editor by clicking Close Editor
https://bugs.kde.org/show_bug.cgi?id=414117 --- Comment #3 from Geoff King --- Didn't help. Now after clicking Close Editor in Step #3B it results in #4 coming out of full-screen and all of the window is transparent except for the top tab and the editor operation on the right side. see screenshot -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414115] g'mic plugin not available on Mac
https://bugs.kde.org/show_bug.cgi?id=414115 --- Comment #2 from Geoff King --- Hello. I looked at the location you noted and do NOT see the file Editor_GmicQt_Plugin.so. I do see all the others. Also I do NOT a have a directory called /opt/digikam/lib/plugins/digikam/editor/ but could create one. I searched the /opt/digikam tree and do not see anything Gmic related. On Thu, Nov 14, 2019 at 1:10 AM wrote: > https://bugs.kde.org/show_bug.cgi?id=414115 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > > CC||caulier.gil...@gmail.com > > --- Comment #1 from caulier.gil...@gmail.com --- > The problem is located in Gmic plugin install dir rules. plugin is copied > at > wrong place and not detected at startup. > > As root, move file from: > > /opt/digikam/libexec/qt5/plugins/digikam/editor/Editor_GmicQt_Plugin.so > > to: > > /opt/digikam/lib/plugins/digikam/editor/ > > Restart digiKam: plugin must be listed in setup/plugins/editor view, and > visible in Enhance menu from image editor. > > 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 414117] New: Full screen cannot close Image Editor by clicking Close Editor
https://bugs.kde.org/show_bug.cgi?id=414117 Bug ID: 414117 Summary: Full screen cannot close Image Editor by clicking Close Editor Product: digikam Version: 6.4.0 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Usability-FullScreen Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- I am having issues with the 6.4 on Mac Mojave when switching to "Full-Screen" mode. If once in full-screen AND enter another feature such as Image Editor, it can be hard to get back to thumbnail view. It is not clear how to close the Image Editor because clicking the Close Editor so does not bring you back to the Thumbnail view. STEPS TO REPRODUCE 1. Within Normal Thumbnail view, click Full Screen. App enters full-screen as expected. 2. Select an image and click Image Editor. This is okay. This is where different closing options have different outcomes. 3A. Click Exit Full Screen - This outcome gives you back the two windows in a tabbed interface. You can then close the tab for Image Editor -- This works okay. So option 3A is the workaround. 3B. This is where the issues are. From the Full-screen of step 2. Click Close Editor button. 4. This closes full-screen but gives you only one Image Editor Window. The Thumbnail view is not found. 5. Click Close Editor and nothing happens. 6. Click the close button on the window and Digikam Closes. So by following path 3B, it is not easy to get back to the Thumbnail view without restarting the program. So to recap, there is something going wrong about step 3B when clicking Close Editor. Doing so doesn't work and doesn't bring you back to the Thumbnail view. This also affects the BQM and Light Table SOFTWARE/OS VERSIONS macOS: Mojave -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414115] New: g'mic plugin not available on Mac
https://bugs.kde.org/show_bug.cgi?id=414115 Bug ID: 414115 Summary: g'mic plugin not available on Mac Product: digikam Version: 6.4.0 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Bundle-MacOS Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- I do not see the g'mic plugin as an option on the latest Mac release 6.4. SOFTWARE/OS VERSIONS macOS: Mojavedigikam version 6.4.0 CPU cores: 8 Eigen: 3.3.7 Exiv2: 0.27.2 Exiv2 can write to Jp2: Yes Exiv2 can write to Jpeg: Yes Exiv2 can write to Pgf: Yes Exiv2 can write to Png: Yes Exiv2 can write to Tiff: Yes Exiv2 supports XMP metadata: Yes HEIF encoding support: Yes ImageMagick codecs: 6.9.9 KF5: 5.61.0 LensFun: 0.3.95-0 LibCImg: 130 LibJPEG: 90 LibJasper: 2.0.14 LibLCMS: 2090 LibLqr support: No LibPGF: 7.19.03 LibPNG: 1.6.37 LibRaw: 0.19.5 LibTIFF: 4.0.10 Marble: 0.27.20 Parallelized demosaicing: No Qt: 5.12.4 Qt Webkit support: Yes VKontakte support: No AkonadiContact support: No Baloo support: No Calendar support: Yes DBus support: No Database backend: QSQLITE HTML Gallery support: Yes LibAVCodec: 58.54.100 LibAVFormat: 58.29.100 LibAVUtil: 56.31.100 LibGphoto2: 2.5.23 LibOpenCV: 3.4.7 LibQtAV: 1.13.0 Media player support: Yes Panorama support: Yes -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411902] Interface icons become very large and unusable
https://bugs.kde.org/show_bug.cgi?id=411902 --- Comment #7 from Geoff King --- Still present in 6.4-git (Build date: Sep 14 2019 (target: debugfull)) The scale is about double in both directions for the window. Mouse clicks are in the correct, unscaled places, but the graphical elements are enlarged and scaled to a different part of the window. Only Image Editor and Light Table appear to be affected. I am now also noticing an issue with the Open GL Image Viewer. Upon trying to exit that I get a black screen on the desktop, full-screen. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411902] Interface icons become very large and unusable
https://bugs.kde.org/show_bug.cgi?id=411902 --- Comment #6 from Geoff King --- Attachment added showing the issue. Color Theme: Breeze Dark Theme: FusionGray It is as if the entire window is scaled larger, both icons and image. digikam version 6.3.0 CPU cores: 8 Eigen: 3.3.7 Exiv2: 0.27.2 Exiv2 can write to Jp2: Yes Exiv2 can write to Jpeg: Yes Exiv2 can write to Pgf: Yes Exiv2 can write to Png: Yes Exiv2 can write to Tiff: Yes Exiv2 supports XMP metadata: Yes ImageMagick codecs: 6.9.9 KF5: 5.59.0 LensFun: 0.3.2-0 LibCImg: 130 LibJPEG: 90 LibJasper: 2.0.14 LibLCMS: 2090 LibLqr support: No LibPGF: 7.19.03 LibPNG: 1.6.37 LibRaw: 0.19.5 LibTIFF: 4.0.10 Marble: 0.27.20 Parallelized demosaicing: No Qt: 5.11.3 Qt Webkit support: Yes VKontakte support: No AkonadiContact support: No Baloo support: No Calendar support: Yes DBus support: No Database backend: QSQLITE HTML Gallery support: Yes LibAVCodec: 58.54.100 LibAVFormat: 58.29.100 LibAVUtil: 56.31.100 LibGphoto2: 2.5.23 LibOpenCV: 3.4.7 LibQtAV: 1.13.0 Media player support: Yes Panorama support: Yes -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411902] Interface icons become very large and unusable
https://bugs.kde.org/show_bug.cgi?id=411902 --- Comment #5 from Geoff King --- Created attachment 122651 --> https://bugs.kde.org/attachment.cgi?id=122651=edit upscaled window -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411902] New: Interface icons become very large and unusable
https://bugs.kde.org/show_bug.cgi?id=411902 Bug ID: 411902 Summary: Interface icons become very large and unusable Product: digikam Version: 6.3.0 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: major Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- The interface icons become very large and only the upper left corner of the screen is visible after entering the Image Editor. It also happens occasionally with other clicks, but I can trigger it by going into image editor. STEPS TO REPRODUCE 1. Select an image 2. click the Image Editor button 3. OBSERVED RESULT The image editor opens, but is unusable because it is magnified and only the top left corner of the screen is visible. Also happens with Light Table. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: 10.14.6 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 410240] Icon Theme missing Breeze Dark Icons
https://bugs.kde.org/show_bug.cgi?id=410240 --- Comment #12 from Geoff King --- I tried with 6.2 (July 30) packages on MacOS, Mojave 10.14.6. I am happy to report this is now working as expected. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407235] macOS : digiKam 6.1.0 crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=407235 --- Comment #44 from Geoff King --- I can confirm it still crashes upon close using 6.2-pre (Build date: Jul 25 2019) on Mojave. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 410240] Icon Theme missing Breeze Dark Icons
https://bugs.kde.org/show_bug.cgi?id=410240 --- Comment #8 from Geoff King --- For comment #5. digikam.widgets: Breeze icons resource file found digikam.general: Switch to widget style: "Fusion" digikam.general: AlbumWatch is disabled digikam.general: Database Parameters: Type: "QSQLITE" DB Core Name: "/Users/gsking/Pictures/digikam4.db" DB Thumbs Name: "/Users/gsking/Pictures/thumbnails-digikam.db" DB Face Name: "/Users/gsking/Pictures/recognition.db" DB Similarity Name: "/Users/gsking/Pictures/similarity.db" Connect Options: "" -- You are receiving this mail because: You are watching all bug changes.
