[digikam] [Bug 285683] Already imported pictures not recognized after daylight savings time
https://bugs.kde.org/show_bug.cgi?id=285683 --- Comment #11 from Nicofo --- Created attachment 102058 --> https://bugs.kde.org/attachment.cgi?id=102058&action=edit Same picture undully imported twice Hi, I reopen this bug because, unlike I thought, it is actually not solved. Last DST was last weekend (30 Oct): all the pictures I made before (and that I had already imported) are not recognized anymore as already imported: if I import "New items" in Digikam, all my pictures imported before DST are re-imported again :( See picture attached (file digikam4.db), with the example of one picture taken before DST (25 Sept 18h35) but now recognized one hour later (25 Sept 19h35) so re-imported by digikam. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 285683] Already imported pictures not recognized after daylight savings time
https://bugs.kde.org/show_bug.cgi?id=285683 Nicofo changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 285683] Already imported pictures not recognized after daylight savings time
https://bugs.kde.org/show_bug.cgi?id=285683 Nicofo changed: What|Removed |Added Version|4.4.0 |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 285683] Already imported pictures not recognized after daylight savings time
https://bugs.kde.org/show_bug.cgi?id=285683 Nicofo changed: What|Removed |Added Version Fixed In|5.1.0 | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 326404] Unable to select picture in map search view
https://bugs.kde.org/show_bug.cgi?id=326404 Nicofo changed: What|Removed |Added Version|4.2.0 |5.3.0 --- Comment #5 from Nicofo --- Hi Gilles, I tried with DK 5.3 and the problem is still there. I.e. the map from the left view does not work like the map from the top menu. - The map from the left menu (besides Albums/Tags/Labels/Fuzzy/People/... buttons): it is not possible to select pictures by clicking on them (which is the most obvious and convenient way to select pictures I think). - While it works well in the map on the top menu (besides Thumbnails and Preview_Image). There just click on a pictures and its easy. I suppose the map view from the left could also work like that to be able to select pictures easily ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329976] SCAN : digiKam does not update database after picture renaming
https://bugs.kde.org/show_bug.cgi?id=329976 Nicofo changed: What|Removed |Added Version|5.0.0 |5.3.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329976] SCAN : digiKam does not update database after picture renaming
https://bugs.kde.org/show_bug.cgi?id=329976 --- Comment #12 from Nicofo --- Hi Gilles, I tested again with DK 5.3. There is progress, this problem is nearly solved, but not with the Tags. I made the same test as in comment #8 I have no problem anymore related to the properties of the pictures (geolocalisation icon is OK, 'modified date' is ok, ...) BUT well with the tags. The tags are not correct anymore. And the behaviour is different depending if I make the renaming while DK is running or not. Say that picture 3 has a tag 'TAG'. If I delete picture 2 and rename the other (picture 3 becomes 2 ...): -> I expect that picture 2 has now the 'TAG', BUT: - if DK is running: now picture 2 and 3 have 'TAG' - if DK is not running: after restart of DK, the tags are 'shifted' to the neighbour picture: now picture 3 has the 'TAG' -> so in both situations it is not good. (hope the explanation is clear ;) ) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370553] Adjust date - not possible to update "digikam timestamp"
https://bugs.kde.org/show_bug.cgi?id=370553 Nicofo changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Version Fixed In|5.4.0 | Resolution|FIXED |--- Version|5.2.0 |5.3.0 --- Comment #8 from Nicofo --- OK, Thanks for the explanations, I agree with you. But therefore, as DK timestamp is automatically updated to EXIF, there is no need to keep the possibility to use it as a reference to adjust the date. This option should be removed from the "Timestamp used" fields (top of screenshot in comment #2). And so totally disappear from UI ? (it's an internal variable, not useful for user I think ?) Note also there are minor problems in the UI: see comment #1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 456512] No sound on AppImage previews
https://bugs.kde.org/show_bug.cgi?id=456512 Nicofo changed: What|Removed |Added Version|7.9.0 |8.0.0 --- Comment #22 from Nicofo --- I have tested with 8.0.0 version (still Appimage on Fedora 37): - now the video and sound are working well - EXCEPTED during the first 2-3 seconds of the video which are laggy (and no sound) Strange ... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 456512] No sound on AppImage previews
https://bugs.kde.org/show_bug.cgi?id=456512 --- Comment #24 from Nicofo --- (In reply to caulier.gilles from comment #23) > I have exactly the same problem here under Kubuntu 22.04 (Plasma desktop). > > Disabling the desktop OpenGL effects fix the problem. Do ask me why... > > Gilles Caulier I tested that as well (I suppose you mean disabling compositing : Alt+Shift+F12 on KDE xorg ?). No effect, same problem under Fedora. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468626] New: Error in the description of the Rename options
https://bugs.kde.org/show_bug.cgi?id=468626 Bug ID: 468626 Summary: Error in the description of the Rename options Classification: Applications Product: digikam Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: AdvancedRename-dialog Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- STEPS TO REPRODUCE 1. In the rename tool window, click on the "Show a list of all available options" button 2. Al the options are listed, amongs other; #[options,start]Sequence number (custom start) #[options,step] Sequence number (custom step) 3. I suppose that second line is wrong (a unique number in brackets is considered as the custom start and not the custom step: example: #[3]) 4. Note: but the following syntax is missing in the description (a sequence number with custom start but without options is valid): #[start] Sequence number (custom start) Note: see image of the error: https://imgur.com/Et6K1BZ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468626] Error in the description of the Rename options
https://bugs.kde.org/show_bug.cgi?id=468626 Nicofo changed: What|Removed |Added Version|unspecified |8.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468626] Error in the description of the Rename options
https://bugs.kde.org/show_bug.cgi?id=468626 --- Comment #3 from Nicofo --- Ah, OK, sorry for my misunderstanding. But it was not so easy to understand I believe --> thank you for the added clarifications. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329976] SCAN : digiKam does not update database after picture renaming
https://bugs.kde.org/show_bug.cgi?id=329976 --- Comment #22 from Nicofo --- (In reply to caulier.gilles from comment #18) > If the file is just > renamed and have been registered previously in the database, the algorithm > will re-detect the previous file as well. It's not a new one. Hi Gilles, Maik. Thanks to continue the bug triage ;) I'm a bit confused with your sentence above: if digikam re-detected the previous file, why is digikam not able to reapply the correct attributes ? - I have well activated the option "Rescan file when files modified". - I suppose that it is why the metadata are well correct after the rename operation (e.g. orientation, Camera model, Geolocalisation, ...) - But I don't see why Database-only information is not correct (Ratings, Label, Captions, ...) See results in screenshots from comment #14 (still valid with DK 8.0) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468775] New: Import files - Preview not available
https://bugs.kde.org/show_bug.cgi?id=468775 Bug ID: 468775 Summary: Import files - Preview not available Classification: Applications Product: digikam Version: 8.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Import-MainView Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- Created attachment 158282 --> https://bugs.kde.org/attachment.cgi?id=158282&action=edit Import window problems When importing pictures from phone (android), I have several problems: 1) Preview mode not available: 1a) "Preview Item" button is disabled (see screenshot) 1b) if I click on the thumbnail -> nothing happens (My settings seems correct: Import Window > Thumbnail Click Action > is well on "Show embedded preview") 2) Thumbnails are not well rotated according to metadata (after import it is OK). (My settings seems correct: Behavior > "Use Metadata (makes connection slower)" is well selected) Is it a bug ? A problem in my settings ? Thanks in advance. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329976] SCAN : digiKam does not update database after picture renaming
https://bugs.kde.org/show_bug.cgi?id=329976 --- Comment #24 from Nicofo --- (In reply to Maik Qualmann from comment #23) > Of course, a re-scan assumes that the information is also available in the > image metadata. I can't reproduce the issue when the color or rating label > metadata is present. You mean that you have color or rating label in the picture's metadata ? Then of course the re-scan (due to "Rescan file when files modified") solves the problem. In my case, color or rating label is NOT in the picture's metadata (only in the database). Can you reproduce the problem with things only in your database ? If well, based on what you write below, I suppose you can close this issue: > From the pure database information, this is difficult > to resolve, as Marcel writes, the name is an important part. If we change > that, we have completely different problems. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413196] Cannot export files with more as 4 MB to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413196 --- Comment #7 from Nicofo --- (In reply to caulier.gilles from comment #6) > We can also add a check about file size before uploading, and refuse to > process file upper to 4Mb by reporting a warning in dialog files list view. > > Gilles No please. Why do you says the limit is 4Mb ? I guess it was the case previously, but it is now much larger. I made some new tests: it is now well possible to export files > 4Mb (I exported a lot of pictures of about 5 - 6Mb). I am even able to export a video of 98.4 Mb. But is does not work with another of 168.5 Mb: following error message is displayed: Error transferring https://graph.microsoft.com/v1.0/me/drive/root:/:/content - server replied: Request Entity Too Large So the limit is somewhere between 98.4 and 168.5 Mb (100Mb maybe ? Possible to check that on Microsoft documentation ?) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 456512] No sound on AppImage previews
https://bugs.kde.org/show_bug.cgi?id=456512 Nicofo changed: What|Removed |Added Version|7.7.0 |7.8.0 CC||nic...@tuxfamily.org --- Comment #4 from Nicofo --- Same problem with appimage 7.7 and 7.8 on Fedora: video plays well, but no sound. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 456512] No sound on AppImage previews
https://bugs.kde.org/show_bug.cgi?id=456512 --- Comment #9 from Nicofo --- (In reply to Maik Qualmann from comment #8) > The current AppImage now plays sound here again. > > Maik There is indeed a change in the last AppImage: - there is some sound, but with a lot of noise - and the video lags a lot (video is jerky). In the previous AppImage: no sound at all, but the video was ok (not jerky). Of course the video plays nice (with sound) outside Digikam (VLC, ...). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 456512] No sound on AppImage previews
https://bugs.kde.org/show_bug.cgi?id=456512 --- Comment #12 from Nicofo --- Indeed Maik, I'm using Fedora with Gnome. "Enable internal debug logging" was already deactivated. And I don't use debug environment variable (AFAIK, unless they are used by default?). Note that I have tested deactivating the option "Disable HW acceleration OpenCL": no effect. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 456512] No sound on AppImage previews
https://bugs.kde.org/show_bug.cgi?id=456512 --- Comment #13 from Nicofo --- Note that as you asked, I have tested with KDE Plasma -> same result. And also Gnome X11 or Wayland does not change anything. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468775] Import files - Preview not available
https://bugs.kde.org/show_bug.cgi?id=468775 --- Comment #4 from Nicofo --- Created attachment 168812 --> https://bugs.kde.org/attachment.cgi?id=168812&action=edit Missing preview of some pictures + wrong label "created" Hi Gilles, I tested with digiKam-8.4.0-20240421T172117-Qt6-x86-64.appimage: Following #comment 0 : 1) Preview mode not available: -> not working. But normal according to Maik's answer #comment 1 2) Thumbnails are not well rotated: -> is now working well, thanks ! But I have other problems (more or less related to original problem, so I keep it on this bug report. Tell me if you prefer a dedicated bug report) 3) Not all pictures have their preview visible: see attachment -> After scrolling up and down, the majority of the pictures have their preview appearing, but for a few of them, the preview never appears. This is really annoying because the preview button is not working and nothing happens when you click on the picture (see problem 1) -> it is hard to guess what is the picture. 4) The reported date (labelled "created" below the preview) seems to be the date of the file (last modification of the file on the camera), but not the creation date : see attachment -> so either rename "created" by "modified" -> or better correct it to be the real "created" date of the picture (info from the metadata). Use case: I want to sort the files according to the moment they were taken, not the date of modification. This is important in this window if you want to select all the pictures from a dedicated date. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413196] Cannot export files with more as 4 MB to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413196 --- Comment #10 from Nicofo --- As stated in #comment 7: > I am even able to export a video of 98.4 Mb. > (...) > So the limit is somewhere between 98.4 and 168.5 Mb (100Mb maybe ? Possible > to check that on Microsoft documentation ?)" So this bug can be closed for me. But you should remove the remark in the documentation that you introduced in #comment 5 : "OneDrive file storage is currently limited to host only files with a size lower than 4Mb." -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468775] Import files - Preview not available
https://bugs.kde.org/show_bug.cgi?id=468775 --- Comment #6 from Nicofo --- (In reply to Maik Qualmann from comment #5) > No preview image, image broken? No: the image is not broken. And when downloaded, they are displayed correctly in digikam. > In order to get a correct creation date in the thumbnail, the metadata must > be read. To do this, the corresponding option must be activated in the > digiKam camera settings, with the addition "makes the connection slower". If > you click on an image, the “live” data will be displayed in the metadata > viewer. > As of digiKam-8.0.0, reading the exact metadata is no longer necessary; all > date operations are now carried out after the download. Yes you are right, I forgot to activate the option "Use file metedata (makes the connection slower)". So the date is correct with this option activated. But not correct with the option deactivated (possible to rename "Cretaed" into "Modified" in this case ?). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413196] Cannot export files with more as 4 MB to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413196 --- Comment #12 from Nicofo --- (In reply to Maik Qualmann from comment #11) > No, according to Microsoft API documentation it is still limited to 4MB in > simple item upload mode. > > Maik I believe you, but try by yourself, this limit is not correct anymore ;) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468775] Import files - Preview not available
https://bugs.kde.org/show_bug.cgi?id=468775 --- Comment #8 from Nicofo --- (In reply to Maik Qualmann from comment #7) > There should be something in the debug output in the terminal if thumbnails > are not created for some images. A log would be interesting. Here is the output of digikam when I click on "Import" > (my Android phone) There are some errors... (this is not the debug version of digikam: tell me if I need to use it) Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot find Xmp key 'Exif.Image.FocalLength' into image with Exiv2: (Error # 7 : "Invalid key 'Exif.Image.FocalLength'" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot find Exif key 'Xmp.exif.ISOSpeedRatings' into image with Exiv2: (Error # 7 : "Invalid key 'Xmp.exif.ISOSpeedRatings'" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot find Exif key 'Xmp.exif.ExposureIndex' into image with Exiv2: (Error # 7 : "Invalid key 'Xmp.exif.ExposureIndex'" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot set Exif data with Exiv2: (Error # 4 : "This does not look like a TIFF image" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot find Xmp key 'Exif.Image.FocalLength' into image with Exiv2: (Error # 7 : "Invalid key 'Exif.Image.FocalLength'" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot find Exif key 'Xmp.exif.ISOSpeedRatings' into image with Exiv2: (Error # 7 : "Invalid key 'Xmp.exif.ISOSpeedRatings'" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot find Exif key 'Xmp.exif.ExposureIndex' into image with Exiv2: (Error # 7 : "Invalid key 'Xmp.exif.ExposureIndex'" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot find Xmp key 'Exif.Image.FocalLength' into image with Exiv2: (Error # 7 : "Invalid key 'Exif.Image.FocalLength'" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot find Exif key 'Xmp.exif.ISOSpeedRatings' into image with Exiv2: (Error # 7 : "Invalid key 'Xmp.exif.ISOSpeedRatings'" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot find Exif key 'Xmp.exif.ExposureIndex' into image with Exiv2: (Error # 7 : "Invalid key 'Xmp.exif.ExposureIndex'" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot find Xmp key 'Exif.Image.FocalLength' into image with Exiv2: (Error # 7 : "Invalid key 'Exif.Image.FocalLength'" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot find Exif key 'Xmp.exif.ISOSpeedRatings' into image with Exiv2: (Error # 7 : "Invalid key 'Xmp.exif.ISOSpeedRatings'" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot find Exif key 'Xmp.exif.ExposureIndex' into image with Exiv2: (Error # 7 : "Invalid key 'Xmp.exif.ExposureIndex'" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot set Exif data with Exiv2: (Error # 4 : "This does not look like a TIFF image" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot set Exif data with Exiv2: (Error # 4 : "This does not look like a TIFF image" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot set Exif data with Exiv2: (Error # 4 : "This does not look like a TIFF image" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot set Exif data with Exiv2: (Error # 4 : "This does not look like a TIFF image" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot set Exif data with Exiv2: (Error # 4 : "This does not look like a TIFF image" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot find Xmp key 'Exif.Image.FocalLength' into image with Exiv2: (Error # 7 : "Invalid key 'Exif.Image.FocalLength'" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot find Exif key 'Xmp.exif.ISOSpeedRatings' into image with Exiv2: (Error # 7 : "Invalid key 'Xmp.exif.ISOSpeedRatings'" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot find Exif key 'Xmp.exif.ExposureIndex' into image with Exiv2: (Error # 7 : "Invalid key 'Xmp.exif.ExposureIndex'" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot set Exif data with Exiv2: (Error # 4 : "This does not look like a TIFF image" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot set Exif data with Exiv2: (Error # 4 : "This does not look like a TIFF image" Digikam::MetaEngine::Private::printExiv2ExceptionError: Cannot set Exif data with Exiv2: (Error # 4 : "This does not look like a TIFF image" Digikam::Me
[digikam] [Bug 468775] Import files - Preview not available
https://bugs.kde.org/show_bug.cgi?id=468775 --- Comment #9 from Nicofo --- I tried with debug version (digiKam-8.4.0-20240512T090210-Qt6-x86-64-debug.appimage) I only have the following message when I click in "Import": Digikam::ExifToolParser::load: Cannot open source file to process with ExifTool... (2 of these lines are written each time I select a picture in the Import window, whatever if the preview is available or not) Note: same result with digikam 8.2.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468775] Import files - Preview not available
https://bugs.kde.org/show_bug.cgi?id=468775 --- Comment #10 from Nicofo --- Sorry, I forgot to enable debugging. Here are the outputs in the Import window: Digikam::GPCamera::getThumbnail: Failed to get camera item! "/store_00010001/DCIM/Camera" "IMG_20240510_101546784_HDR.jpg" Digikam::GPCamera::printGphotoErrorDescription: Libgphoto2 error: Unspecified error ( -1 ) Digikam::CameraController::sendLogMsg: Log ( "IMG_20240510_101546784_HDR.jpg" "/store_00010001/DCIM/Camera" : "Failed to get thumbnail for ‘IMG_20240510_101546784_HDR.jpg’" (appears for each picture without preview) Do you want me to send you one of these pictures ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468775] Import files - Preview not available
https://bugs.kde.org/show_bug.cgi?id=468775 --- Comment #12 from Nicofo --- (In reply to Maik Qualmann from comment #11) > The cause is probably not the image itself. GPhoto2 has a problem with your > camera device/connection. Which camera model is it? This is an android phone (Motorola) > Note that digiKam requires an exclusive connection with GPhoto2 to your > camera. There are now background services on various desktops that display > the status of the camera in the system section of the taskbar. Some do not > release the connection again and digiKam cannot use the USB port via > GPhoto2. Yes, I have noticed that (i.e. if the Android Phone is mounted in file explorer (nautilus in Gnome), digikam cannot load the images. No problem after unmounting the Phone in nautilus). But I don't think this is the problem in my case because: - despite the fact the previews are missing, I can download the files without problem with digikam (and then the preview is OK in the album) - if I unplug / replug the phone and try to reopen the import window, it's always the same pictures whose preview is missing. So it sounds like it is well a problem with some images ? (unless these pictures are tagged as faulty in digikam DB and digikam does not try to display preview anymore ?) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468775] Import files - Preview not available
https://bugs.kde.org/show_bug.cgi?id=468775 --- Comment #14 from Nicofo --- (In reply to Maik Qualmann from comment #13) > The thumbnail from a GPhoto2 device is rendered/created by the phone/camera. > So if the phone/camera doesn't create a thumbnail (for some reason) for a > certain image/file type, digiKam won't be able to display anything. > > Maik So you think it's a GPhoto2 problem and not a digikam problem ? How could I check that ? Is is possible to use gphoto other that with digikam ? For info, nautilus (gnome file manager) displays the tumbnails of pictures from Android phone well (but I don't know if it uses Gphoto2 ?) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425047] Trash icon should reflect if trash is full or empty
https://bugs.kde.org/show_bug.cgi?id=425047 Nicofo changed: What|Removed |Added Version|7.0.0 |7.8.0 Platform|Fedora RPMs |Appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425047] Trash icon should reflect if trash is full or empty
https://bugs.kde.org/show_bug.cgi?id=425047 Nicofo changed: What|Removed |Added Version|7.8.0 |7.7.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451780] New: Appimage 7.6 does not work on Fedora
https://bugs.kde.org/show_bug.cgi?id=451780 Bug ID: 451780 Summary: Appimage 7.6 does not work on Fedora Product: digikam Version: 7.6.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Bundle-AppImage Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- Appimage 7.6 does not start on Fedora: $ ./digiKam-7.6.0-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. Check library libudev.so.0 Check library libxcb-dri3.so.0 Check library libcrypto.so.1.1 Check library libssl.so.1.1 Check library libnss3.so Check library libnssutil3.so Check library libsmime3.so -- Preloading shared libs: :/usr/lib64/libxcb-dri3.so.0:/usr/lib64/libcrypto.so.1.1:/usr/lib64/libssl.so.1.1:/usr/lib64/libnss3.so:/usr/lib64/libnssutil3.so:/usr/lib64/libsmime3.so digikam: symbol lookup error: /lib64/libgio-2.0.so.0: undefined symbol: g_module_open_full WORKAROUND It works however with the following command line: LD_PRELOAD=$LD_PRELOAD:/usr/lib64/libpango-1.0.so.0:/usr/lib64/libpangocairo-1.0.so.0:/usr/lib64/libgmodule-2.0.so.0 ./digiKam-7.6.0-x86-64.appimage Note: I saw bug #451196 but just pre-loading libpango and libpangocairo is not enough on Fedora: libgmodule must also be pre-loaded. SYSTEM Fedora 35 (X, not Wayland) -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 428032] New: Duplicated icons of Elisa in Gnome menu
https://bugs.kde.org/show_bug.cgi?id=428032 Bug ID: 428032 Summary: Duplicated icons of Elisa in Gnome menu Product: elisa Version: 20.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: nic...@tuxfamily.org Target Milestone: --- SUMMARY There are TWO Elisa icons in the Gnome shell menu STEPS TO REPRODUCE 1) Add Elisa in the Favorites of Gnome Shell 2) Launch Elisa ADDITIONAL INFORMATION This problem has already been reported (and solved) with other Applications. See example (and solution) with Digikam: bug #378253 "The issue is the lack of a StartupWMClass entry in your desktop file" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415879] Drag and drop of face to people Tag -> inappropriate popup
https://bugs.kde.org/show_bug.cgi?id=415879 --- Comment #3 from Nicofo --- Created attachment 137304 --> https://bugs.kde.org/attachment.cgi?id=137304&action=edit Inappropriate popup "Assign Tag 'Jack' to Item" A simple screenshot is better to explain the issue ;) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415879] Drag and drop of face to people Tag -> inappropriate popup
https://bugs.kde.org/show_bug.cgi?id=415879 Nicofo changed: What|Removed |Added Version|7.2.0 |7.3.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435303] New: Digikam crashes when selecting 2 times Item opening Web Window in Help menu
https://bugs.kde.org/show_bug.cgi?id=435303 Bug ID: 435303 Summary: Digikam crashes when selecting 2 times Item opening Web Window in Help menu Product: digikam Version: 7.2.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- SUMMARY 1. In Digikam, go to Help menu and select either - Donate - Recipes Book - Contribute - Online Handbook >> Result: a window opens with the requested web page 2. Close that window and repeat step 1 >> Result: digikam crashes XIO: fatal IO error 0 (Success) on X server ":0" after 3465 requests (3465 known processed) with 7 events remaining. /tmp/.mount_digiKajL6bqD/AppRun: line 172: 6723 Segmentation fault (core dumped) digikam $@ If you cannot reproduce the problem, I'll download digikam with debug. NOTE Happens with Appimage 7.2 and 7.1 No problem with Fedora RPM 7.1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415879] Drag and drop of face to people Tag -> inappropriate popup
https://bugs.kde.org/show_bug.cgi?id=415879 Nicofo changed: What|Removed |Added Version|7.3.0 |7.2.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435303] Digikam crashes when selecting 2 times Item opening Web Window in Help menu
https://bugs.kde.org/show_bug.cgi?id=435303 --- Comment #4 from Nicofo --- (In reply to caulier.gilles from comment #3) > You said 2 times opening item menu ? For ex, you open Help/Donate, the web > page is show, you don't close it, and you re-try Help/donate, and in this > case you got a crash ? > > If yes, the problem is a little bit different. > > Gilles Caulier No: 1. Help/Donate, the web page is shown 2. I close the web page 3. Again Help/Donate (or Help/) -> crash Note: If I don't close the web page and open it a second time, no crash (i.e. I have 2 web pages open) I use the proprietary nvidia drivers. But no problem with Fedora RPM (version 7.1; in "Components Information" > Qt WebEngineSupport: Yes). So I suspect a problem with appimage bundle ? OK I'll use debug appimage version and give you the trace later. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435303] Digikam crashes when selecting 2 times Item opening Web Window in Help menu
https://bugs.kde.org/show_bug.cgi?id=435303 Nicofo changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #6 from Nicofo --- (In reply to Maik Qualmann from comment #5) > Git commit 365aacda04047ba38cafcdfd05d84d9994249f22 by Maik Qualmann. > Committed on 03/04/2021 at 14:49. > Pushed by mqualmann into branch 'master'. > > delete WebBrowserDlg when close > > M +2-0core/libs/dialogs/webbrowserdlg.cpp > > https://invent.kde.org/graphics/digikam/commit/ > 365aacda04047ba38cafcdfd05d84d9994249f22 Thank you Maik ! I have just tested with last appimage (digiKam-7.3.0-20210404T082005-x86-64): no more crash ! Note: previously, it crashes every time a web page was opened a second time (not only from Help menu, but also e.g. for login to Onedrive, ...). So your correction will probably prevent a lot of "strange" crashes :-) Strange because it was only the second time it crashed and therefore not always reproducible. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416180] Number of "new items" not updated after face recognition
https://bugs.kde.org/show_bug.cgi?id=416180 Nicofo changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #4 from Nicofo --- I reopen this bug: this is not solved in version 7.0.0. In fact there an improvement compared to original bug report (using 7.0.0 beta2): - after face recognition, counter is still not updated. - But there is no need to click somewhere on the left panel to have the counter updated (as before), you just need to move the mouse over the left panel. But as long as you dont move the mouse, counter is not updated. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329976] SCAN : digiKam does not update database after picture renaming
https://bugs.kde.org/show_bug.cgi?id=329976 Nicofo changed: What|Removed |Added Version|5.8.0 |7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329976] SCAN : digiKam does not update database after picture renaming
https://bugs.kde.org/show_bug.cgi?id=329976 --- Comment #16 from Nicofo --- I tested again with DK 7.0.0: result is exactly the same as in previous comment (comment #14) -> not OK with tags and ratings. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329976] SCAN : digiKam does not update database after picture renaming
https://bugs.kde.org/show_bug.cgi?id=329976 Nicofo changed: What|Removed |Added Version Fixed In|5.1.0 | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415879] Drag and drop of face to people Tag -> inappropriate popup
https://bugs.kde.org/show_bug.cgi?id=415879 --- Comment #2 from Nicofo --- Same behaviour as in comment #1 with DK 7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416180] Number of "new items" not updated after face recognition
https://bugs.kde.org/show_bug.cgi?id=416180 --- Comment #7 from Nicofo --- Sorry, my mistake, you are right. But indeed there is a timer (2-3 seconds) before the counter is updated. I made the test by rejecting a face (in "Unconfirmed" tag). I expected that the treatment of rejecting one face would be immediate. That's why I did not realized there was a timer involved and thought the bug was still present. The timer of 2-3 seconds is in this case "too much visible". There are (at least) 2 use cases where the counter must be updated: (1) in case of a recognition process: I suppose you have implemented this timer so that the counter is not updated for each newly recognized face. That can make sense in this case (to avoid negative impact on the performance). (2) in case of a face rejection or assignement (in "Unconfirmed" tag): here the timer is not relevant -> should be avoided So: as an improvement, thanks to check if you can remove the timer for use case (2). Otherwise, you can close this bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329976] SCAN : digiKam does not update database after picture renaming
https://bugs.kde.org/show_bug.cgi?id=329976 --- Comment #17 from Nicofo --- Hi Gilles, Correct me if I'm wrong: I was wondering why some attributes are correct and others not after the manipulation described in comment #8 (rename pictures outside of digikam). - attributes that are correct after manipulation: orientation, geotagging, ... Seems to be attributes coming file metadata (EXIF) - attributes that are lost after manipulation: tags or ratings, i.e. attributes NOT in file metadata (added in digikam) My guess: after renaming outside of digikam, renamed pictures are seen as new pictures by digikam. So digikam rereads metadata: - attributes from file metadata (EXIF) are therefore correct again - other attributes (tags or ratings) are lost (or "shifted" from neighbor picture depending on the setting "Clean up metadata from the database when rescan files"). I suppose these attributes, in digikam DB, are attached to a picture that digikam does not recognize anymore because of the renaming and are therefore lost ? Is it correct ? If so, I suppose there is nothing more digikam can do, except automatically reread metadata of files whose name has been changed outside of digikam (which was the main issue when I raised this bug report but is solved since comment #12). Do you agree with that ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425047] New: Trash icon should reflect if trash is full or empty
https://bugs.kde.org/show_bug.cgi?id=425047 Bug ID: 425047 Summary: Trash icon should reflect if trash is full or empty Product: digikam Version: 7.0.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-Trash Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- SUMMARY The trash icon in the Albums view always shows an "empty trash". The icon should be a "full trash" if something is inside. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425047] Trash icon should reflect if trash is full or empty
https://bugs.kde.org/show_bug.cgi?id=425047 --- Comment #2 from Nicofo --- Created attachment 130669 --> https://bugs.kde.org/attachment.cgi?id=130669&action=edit Trash icons Really ? Seems empty to me ;) See printscreen, done with 2 themes (Adwaita and Breeze). - Trash of "Desktop" collection is in fact full - Trash of "Photos" collection is in fact empty - both icons are empty :( -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433219] Can't sign into my Microsoft account in order to access OneDrive
https://bugs.kde.org/show_bug.cgi?id=433219 --- Comment #8 from Nicofo --- (In reply to caulier.gilles from comment #7) > @Gilbert, > > What's about this file using current 8.2.0 AppImage Linux bundle ? It's > reproducible ? > > https://files.kde.org/digikam/ > > Thanks in advance > > Gilles Caulier I have no problem anymore to sign into OneDrive. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329976] SCAN : digiKam does not update database after picture renaming
https://bugs.kde.org/show_bug.cgi?id=329976 --- Comment #26 from Nicofo --- Hello Gilles, yes, problem still reproducible. My settings: - Settings > Metadata > "Rescan file when files are modifies" is checked - Settings > Metadata > (Write to metadata) Captions and titles / Rating / ... is NOT checked (I understand that these options replace the old "Clean up the metadata from the database when rescan files" option ?) My pictures: - has no Captions / titles / Rating in the metadata (these are ONLY in digikam DB) After renaming operation (outside of digikam) -> same problem as comment #14 After your explanations and those of Maik, I understand that, since the file name is changed outside of digikam, it is difficult to "reassign" the proper Capions / Rating / ... to the proper pictures. As I said in comment #24, I suppose you can close this issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329390] Auto-rotate Using Exif information: rotates wrong picture
https://bugs.kde.org/show_bug.cgi?id=329390 --- Comment #7 from Nicofo --- No such problem since a long time. Note: probably because bug 329976 does not affect the orientation anymore since a long time (because orientation is reread from the metadata of the file after a renaming - if option 'Rescan file when files modified' activated) So this bug can be closed (it was already in the state "resolved" (duplicate) btw ;-) ) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461469] New: Import file filter not working
https://bugs.kde.org/show_bug.cgi?id=461469 Bug ID: 461469 Summary: Import file filter not working Classification: Applications Product: digikam Version: 7.9.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Import-Settings Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- Created attachment 153498 --> https://bugs.kde.org/attachment.cgi?id=153498&action=edit Help menu not working The following setting does not work as expected: Settings > Configure Digikam > Cameras > Import Filters > (below in 'Always ignore' section) > Ignored file names Or I don't understand how the file filter is supposed to work: - the file names are separated by space I suppose ? (by default there are 2 names separated by a space) - can we use regex, ... ? - (note: the 'Help' button at the bottom left does not work: see screenshot) I want to filter all the files ".trashed-xxx.jpg" from my phone (android renames deleted files that way) but I can't manage that: I tried in the field "Ignored file names": - .trashed-* - .trashed-.* without success. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461469] Import file filter not working
https://bugs.kde.org/show_bug.cgi?id=461469 --- Comment #4 from Nicofo --- (In reply to Maik Qualmann from comment #3) > Note: the name filter accepts wildcards (*). > > Maik Perfect, thank you Maik. If I have well seen, it is possible to add several ignored names separated by a space. Is it possible to specify that (using a hint / tooltip / or something like that) ? (because it is not obvious that the separator must be a space: could have been a coma, ...) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461495] New: 'Help' window does not work
https://bugs.kde.org/show_bug.cgi?id=461495 Bug ID: 461495 Summary: 'Help' window does not work Classification: Applications Product: digikam Version: 7.9.0 Platform: Appimage OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Documentation Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org CC: digikam-bugs-n...@kde.org, metzping...@gmail.com Depends on: 461469 Target Milestone: --- +++ This bug was initially created as a clone of Bug #461469 +++ The 'Help' window does not work (empty window with message "Cannot load page https://docs.kde.org/?application=digikam&branch=trunk5"; ;that message appears after a progess bar going to "100%"): see screenshot https://bugs.kde.org/attachment.cgi?id=153498 Note: that help window can be called from several places: - Help > Online Handbook... - Settings > Configure Digikam > Help button at the bottom left Maybe is this bug specific to appimage ? (I use appimage on Fedora 35) Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=461469 [Bug 461469] Import file filter not working -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461469] Import file filter not working
https://bugs.kde.org/show_bug.cgi?id=461469 Nicofo changed: What|Removed |Added Blocks||461495 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=461495 [Bug 461495] 'Help' window does not work -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425047] Trash icon should reflect if trash is full or empty
https://bugs.kde.org/show_bug.cgi?id=425047 --- Comment #4 from Nicofo --- Hi Gilles and happy new year too ! I tested again -> same result: see attachment in comment #2 Best regards -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425047] Trash icon should reflect if trash is full or empty
https://bugs.kde.org/show_bug.cgi?id=425047
--- Comment #5 from Nicofo ---
Additional info:
I think that the Trash icon's name is:
- user-trash (empty trash)
- user-trash-full (full trash)
I searched in the code for "user-trash" -> several matches
I searched in the code for "user-trash-full" -> no match (except in ChangeLog
file)
--> So I guess digikam does not handle different icons for the Trash depending
if it is full or empty.
In the matches for "user-trash", there is albumthumbnailloader.cpp:
QPixmap AlbumThumbnailLoader::getStandardAlbumTrashIcon(RelativeSize
relativeSize)
{
return loadIcon(QLatin1String("user-trash"),
computeIconSize(relativeSize));
}
Maybe should be changed there ?
QPixmap AlbumThumbnailLoader::getStandardAlbumTrashIcon(RelativeSize
relativeSize)
{
if //trash is empty
return loadIcon(QLatin1String("user-trash"),
computeIconSize(relativeSize));
else
return loadIcon(QLatin1String("user-trash-full"),
computeIconSize(relativeSize));
}
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 446750] New: Can't export to onedrive: unable to login then crash
https://bugs.kde.org/show_bug.cgi?id=446750 Bug ID: 446750 Summary: Can't export to onedrive: unable to login then crash Product: digikam Version: 7.3.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-WebService-OneDrive Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- Created attachment 144405 --> https://bugs.kde.org/attachment.cgi?id=144405&action=edit Empty login window to onedrive SUMMARY When trying to export to Onedrive, an empty window opens (see attachment). Therefore it is not possible to log in into Onedrive account. Besides that, if I close that empty window and click on "Change account" of the "Export to Onedrive" window, Digikam crashes. See logs attached SYSTEM Fedora 35 Appimage digiKam-7.3.0-x86-64.appimage Note: I also tried with latest digiKam-7.4.0-20211209T121203-x86-64.appimage -> but it crashes immediately: $ ./digiKam-7.4.0-20211209T121203-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 libxcb-dri3.so.0 -- Preloading shared libs: :/usr/lib64/libxcb-dri3.so.0 digikam: /tmp/.mount_digiKaJSufa6/usr/lib/libcrypto.so.1.1: version `OPENSSL_1_1_1b' not found (required by /lib64/libk5crypto.so.3) I already had similar problem with Onedrive (see bug #401377) but it was solved 2 years ago. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446750] Can't export to onedrive: unable to login then crash
https://bugs.kde.org/show_bug.cgi?id=446750 --- Comment #1 from Nicofo --- Created attachment 144406 --> https://bugs.kde.org/attachment.cgi?id=144406&action=edit Digikam 7.3.0 crash log When I click on "Change account" (see at the end of attached file): unknown: UNLINK to Onedrive /tmp/.mount_digiKaO9UeHb/AppRun: line 172: 12759 Segmentation fault (core dumped) digikam $@ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446750] Can't export to onedrive: unable to login then crash
https://bugs.kde.org/show_bug.cgi?id=446750 --- Comment #2 from Nicofo --- additional info: digikam appimage 7.4.0 starts with following command line: LD_PRELOAD=/usr/lib64/libssl.so.1.1:/usr/lib64/libcrypto.so.1.1 ./digiKam-7.4.0-20211209T121203-x86-64.appimage But then the behaviour is excatly the same than 7.3.0 (empty log in window and crash if I click on "Change account"). So problem reproducible with 7.3.0 et 7.4.0. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446750] Can't export to onedrive: unable to login then crash
https://bugs.kde.org/show_bug.cgi?id=446750 --- Comment #6 from Nicofo --- (In reply to Maik Qualmann from comment #4) > The problem is known and will not work with the AppImage either. OnDrive > does not work with the outdated QWebKit browser. Here native digiKam with > QWebEngine works. > > Maik How do I know if I have a QWebKit or a QWebEngine version of digikam ? I think I have QWebEngine because in "Help > Components Information" I have: digikam version 7.3.0 ... Qt: 5.14.2 Qt WebEngine support: Yes ... So Onedrive should work isn't ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446750] Can't export to onedrive: unable to login then crash
https://bugs.kde.org/show_bug.cgi?id=446750 --- Comment #8 from Nicofo --- (In reply to caulier.gilles from comment #7) > Yes, Help Components Info dialog show this information. And yes you use > QtWebEngine (Chromium in fact) Thanks Gilles. But then I don't understand Maik's comment: > OnDrive does not work with the outdated QWebKit browser. Here native digiKam > with QWebEngine works. As I don't use QWebKit but QtWebEngine, Onedrive should work on my machine ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447150] New: AppImage 7.4 does not work on Fedora
https://bugs.kde.org/show_bug.cgi?id=447150 Bug ID: 447150 Summary: AppImage 7.4 does not work on Fedora Product: digikam Version: 7.4.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Bundle-AppImage Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- While appimage 7.3 works well, appimage 7.4 does not start on Fedora: $ ./digiKam-7.4.0-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 libxcb-dri3.so.0 -- Preloading shared libs: :/usr/lib64/libxcb-dri3.so.0 digikam: /tmp/.mount_digiKaWHGnVV/usr/lib/libcrypto.so.1.1: version `OPENSSL_1_1_1b' not found (required by /lib64/libk5crypto.so.3) WORKAROUND It works however with the following command line: LD_PRELOAD=/usr/lib64/libssl.so.1.1:/usr/lib64/libcrypto.so.1.1 ./digiKam-7.4.0-x86-64.appimage SYSTEM Fedora 35 (X, not Wayland) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447150] AppImage 7.4 does not work on Fedora
https://bugs.kde.org/show_bug.cgi?id=447150 --- Comment #2 from Nicofo --- (In reply to Maik Qualmann from comment #1) > Wayland or X doesn't matter, the problem has already been reported here: Bug > 445629. > > Maik OK. I saw that bug, but thought it was Wayland-related (that's why I said I'm on X). At least, if it can help, I gave the "LD_PRELOAD" command that workarounds the problem. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447150] AppImage 7.4 does not work on Fedora
https://bugs.kde.org/show_bug.cgi?id=447150 Nicofo changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #5 from Nicofo --- Thanks for trying to fix this, even during Christmas day ;) Unfortunately it is not working yet. With the last appimage version (that includes well your last commit), I still get the following message. It is slighlty different from what I got in the Description of the bug: as you can see, libssl.so.1.1 and libcrypto.so.1.1 are now well displayed (lines <--) - proof that your commit does "something". Again, if I "export LD_PRELOAD=/usr/lib64/libssl.so.1.1:/usr/lib64/libcrypto.so.1.1" before launching the appimage, it will work. $ ./digiKam-7.5.0-20211225T124151-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 libxcb-dri3.so.0 libssl.so.1.1<- libcrypto.so.1.1< -- Preloading shared libs: :/usr/lib64/libxcb-dri3.so.0:/tmp/.mount_digiKa3AXE3R/usr/lib64/libssl.so.1.1:/tmp/.mount_digiKa3AXE3R/usr/lib64/libcrypto.so.1.1 digikam: /tmp/.mount_digiKa3AXE3R/usr/lib64/libcrypto.so.1.1: version `OPENSSL_1_1_1b' not found (required by /lib64/libk5crypto.so.3) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447150] AppImage 7.4 does not work on Fedora
https://bugs.kde.org/show_bug.cgi?id=447150 --- Comment #7 from Nicofo --- Hello Gilles, I made some tests in AppRun file. In "preload_shared_library" function, I see you prioritize the libraries from the bundles instead of those of the system. I suppose there is good reason for that, but for the sake of the test I change that (e.g. change https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/appimage/data/AppRun#L14 : if [ -f "$DIR/usr/slib64/$FILE" ] ; then --->if [ -f "$DIR/usrxxx/slib64/$FILE" ] ; then so that the libraries from the bundle are discarded) As a result, I got the same kind of error, but related to uname function ! (uname called at line L19) (see < below). $ ./AppRun -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 libxcb-dri3.so.0 libssl.so.1.1 libcrypto.so.1.1 uname: /home/nicolas/Downloaded/squashfs-root/usr/lib/libcrypto.so.1.1: version `OPENSSL_1_1_1' not found (required by /usr/lib64/libssl.so.1.1) <= error with uname called by "preload_shared_library libcrypto.so.1.1" !! -- Preloading shared libs: :/usr/lib64/libxcb-dri3.so.0:/usr/lib64/libssl.so.1.1:/home/nicolas/Downloaded/squashfs-root/usr/lib/libcrypto.so.1.1 digikam: /home/nicolas/Downloaded/squashfs-root/usr/lib/libcrypto.so.1.1: version `OPENSSL_1_1_1' not found (required by /usr/lib64/libssl.so.1.1) digikam: /home/nicolas/Downloaded/squashfs-root/usr/lib/libcrypto.so.1.1: version `OPENSSL_1_1_1b' not found (required by /lib64/libk5crypto.so.3) If now I swap the 2 lines https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/appimage/data/AppRun#L119 : preload_shared_library libssl.so.1.1 preload_shared_library libcrypto.so.1.1 --> preload_shared_library libcrypto.so.1.1 preload_shared_library libssl.so.1.1 then digikam starts correctly (no more error with uname neither). Very strange behaviour (but I'm not familiar at all with ssl...). So there seem to be some incompatibilities with openssl of the bundle and the system. Note: in the bundle, there is a broken link: squashfs-root/usr/lib/libssl.so -> libssl.so.1.0.0 : should be libssl.so.1.1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447150] AppImage 7.4 does not work on Fedora
https://bugs.kde.org/show_bug.cgi?id=447150 --- Comment #13 from Nicofo --- Thanks. Yes, I see your last commits in that AppImage. It is still not working, unless like in comment #7 I give priority to system libraries. Here is the result with your last bundle (not changed): $ ./digiKam-7.5.0-20211227T120913-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. Check library libudev.so.0 Check library libxcb-dri3.so.0 Check library libcrypto.so.1.1 Check library libssl.so.1.1 -- Preloading shared libs: :/usr/lib64/libxcb-dri3.so.0:/tmp/.mount_digiKaBl0myc/usr/lib64/libcrypto.so.1.1:/tmp/.mount_digiKaBl0myc/usr/lib64/libssl.so.1.1 digikam: /tmp/.mount_digiKaBl0myc/usr/lib64/libcrypto.so.1.1: version `OPENSSL_1_1_1b' not found (required by /lib64/libk5crypto.so.3) To summarize, to get it work I need to: 1) prioritize system libraries (in preload_shared_library function). I do that for the test, but I understand that it should not be changed 2) OR it works also with the following command: $ LD_PRELOAD=/usr/lib64/libssl.so.1.1:/usr/lib64/libcrypto.so.1.1 ./digiKam-7.5.0-20211227T120913-x86-64.appimage or simply: $ LD_PRELOAD=/usr/lib64/libcrypto.so.1.1 ./digiKam-7.5.0-20211227T120913-x86-64.appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447150] AppImage 7.4 does not work on Fedora
https://bugs.kde.org/show_bug.cgi?id=447150 --- Comment #16 from Nicofo --- Hi Gilles, Great, without surprise, it works with the last Appimage. Let's see if there is no regression for other users/systems... Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447150] AppImage 7.4 does not work on Fedora
https://bugs.kde.org/show_bug.cgi?id=447150 --- Comment #18 from Nicofo --- (In reply to caulier.gilles from comment #17) > Ok, i close this file file. > > Happy new year > > Gilles Best wishes for 2022 for digiKam team 🎄 Always great to see how digiKam continues to evolve version after version and to see the developers so much caring about users comments. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425884] New: GPS Processing Method: "charset=Ascii" to remove
https://bugs.kde.org/show_bug.cgi?id=425884
Bug ID: 425884
Summary: GPS Processing Method: "charset=Ascii" to remove
Product: digikam
Version: 7.1.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Metadata-Exif
Assignee: digikam-bugs-n...@kde.org
Reporter: nic...@tuxfamily.org
Target Milestone: ---
Created attachment 131223
--> https://bugs.kde.org/attachment.cgi?id=131223&action=edit
GPS exif in digikam
SUMMARY
- GPS Processing Method in EXIF panel shows "charset=Ascii " instead of
just "" ("" = "MANUAL" for instance in the attached example).
- GPS Area Information also shows "charset=xxx" or just "binary comment"
Note: GPS Processing Method is a new decoded tag from exiv2 version 0.27.3
Note: GPSProcessingMethod and GPSAreaInformation are both encoded in the same
way as EXIF UserComment. (see details
https://github.com/Exiv2/exiv2/issues/1046#issuecomment-599540926 )
Version: digikam-7.1.0-20200826T123515-x86-64.appimage
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 425884] GPS Processing Method: "charset=Ascii" to remove
https://bugs.kde.org/show_bug.cgi?id=425884 --- Comment #2 from Nicofo --- (In reply to caulier.gilles from comment #1) > And ??? > > What did you expect from digiKam side ? you want to remove what ? The tags > content ? The whole tags as well from the list ? I expect that: charset=Ascii MANUAL is changed to: MANUAL GPSProcessingMethod is an EXIF tag that contains 8 bytes describing the encoding (in my case ASCII) + x bytes containing the value of the GPSProcessingMethod (in my case 6 bytes containing "MANUAL") Exiv2 output gives everything (encoding method + value), but of course only the value is interesting. So no need to display "charset=xxx" Note: > I seen the exiv2 report : > https://github.com/Exiv2/exiv2/issues/1266 This exiv2 report is indeed a bug in exiv2 tool but is not related to this one. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425884] GPS Processing Method: "charset=Ascii" to remove
https://bugs.kde.org/show_bug.cgi?id=425884
--- Comment #3 from Nicofo ---
Useful information:
(In reply to Nicofo from comment #0)
> Note: GPSProcessingMethod and GPSAreaInformation are both encoded in the
> same way as EXIF UserComment. (see details
> https://github.com/Exiv2/exiv2/issues/1046#issuecomment-599540926 )
I check the UserComment tag: it is correctly handled by Digikam (meaning
Digikam removes the "charset=Ascii" before the UserCommment).
As far as I understand digikam code, this is realised:
- in metaengine_exif.cpp ==> function getExifComment ==> call to
convertCommentValue
- in metaengine_p.cpp ==> function convertCommentValue ==> reads the charset
and consequently decode the UserComment:
// libexiv2 will prepend "charset=\"SomeCharset\" " if charset is
specified
// Before conversion to QString, we must know the charset, so we stay
with std::string for a while
if (comment.length() > 8 && comment.substr(0, 8) == "charset=")
{ ...
GPSProcessingMethod and GPSAreaInformation are both encoded in the same way as
EXIF UserComment.
CONCLUSION: you should also use the function convertCommentValue to these Exif
tags.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 415880] Add a way to easily correct a face name
https://bugs.kde.org/show_bug.cgi?id=415880 Nicofo changed: What|Removed |Added Version|7.0.0 |7.2.0 Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #3 from Nicofo --- (In reply to caulier.gilles from comment #2) > Fixed with #415604 Hello, Thanks for releasing DK 7.2 Beta2 for Christmas ;) I have tested it but I don't see how this is fixed: it is still not possible to easily change the name of a face (without leaving the People view). Have I missed something ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415880] Add a way to easily correct a face name
https://bugs.kde.org/show_bug.cgi?id=415880 Nicofo changed: What|Removed |Added Version Fixed In|7.2.0 | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415879] Drag and drop of face to people Tag -> inappropriate popup
https://bugs.kde.org/show_bug.cgi?id=415879 Nicofo changed: What|Removed |Added Version|7.0.0 |7.2.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461495] 'Help' window does not work
https://bugs.kde.org/show_bug.cgi?id=461495 --- Comment #4 from Nicofo --- I tried with digiKam-7.9.0-20221108T161738-x86-64.appimage Unfortunately it does not work under Fedora: digikam: error while loading shared libraries: libpcre.so.3: cannot open shared object file: No such file or directory (on my system, I have only /usr/lib or lib64/libpcre.so.1) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461495] 'Help' window does not work
https://bugs.kde.org/show_bug.cgi?id=461495 --- Comment #5 from Nicofo --- Note: I have a "libpcre.so.3" file coming from Steam runtime. I have tried to preload it with for the sake of the test: LD_PRELOAD=/home//.local/share/Steam/ubuntu12_32/steam-runtime/lib/x86_64-linux-gnu/libpcre.so.3 -> digikam starts, and, good news, the problem of Help window is solved ;-) Thanks. So, this bug can be closed. But there remains a problem with the new appimage on Fedora. I don't know if it is possible to include "libpcre.so.3" inside the appimage (and if it is the proper way to solve this issue). Do you want me to open a new bug report for that ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 455922] Appimage fails to start in Fedora 36 - Missing libnsl.so.1
https://bugs.kde.org/show_bug.cgi?id=455922 Nicofo changed: What|Removed |Added CC||nic...@tuxfamily.org --- Comment #5 from Nicofo --- Hello Maik, Gilles, I installed a fresh Fedora 37 and appimage does not work because of libnsl missing. It seems libnsl is not installed by default on Fedora (and maybe on other distributions ?) Is it possible to include it in the appimage ? Of course we can manually install libnsl on Fedora, but it's a pity digikam does not work out of the box. Best regards -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 456512] No sound on AppImage previews
https://bugs.kde.org/show_bug.cgi?id=456512 Nicofo changed: What|Removed |Added Version|7.8.0 |7.9.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400216] New: Components Information window: no standardized uppercase/lowercase
https://bugs.kde.org/show_bug.cgi?id=400216 Bug ID: 400216 Summary: Components Information window: no standardized uppercase/lowercase Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- Created attachment 115856 --> https://bugs.kde.org/attachment.cgi?id=115856&action=edit Help > Components Information SUMMARY The Components Information window has no standard related to the case (first letter sometimes in lowercase - sometimes in uppercase). It presents yes information as "yes" or "Yes" ; the same for no: "no" or "No" STEPS TO REPRODUCE 1. Go to Help > Components Information 2. See the result in the "Info" column: yes/Yes or no/No is not standardized: sometimes first letter in uppercase, sometimes in lowercase. OBSERVED RESULT See printscreen attached EXPECTED RESULT The case should be standardized -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400217] New: Incorrect Video date/time information: shifted by 2 hours
https://bugs.kde.org/show_bug.cgi?id=400217 Bug ID: 400217 Summary: Incorrect Video date/time information: shifted by 2 hours Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Video Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- Created attachment 115857 --> https://bugs.kde.org/attachment.cgi?id=115857&action=edit DK printscreen SUMMARY The date/time information related to videos is wrong: 2 hours in advance. (Could it be because I'm in CET time zone which is UTC+2 in summer ??) An example to illustrate that: - At 21h42 I make a picture - At 21h43 I make a video - I import these 2 files in Digikam. See the result in the printscreen. * for the picture -> OK (21h42) * for the video -> NOT OK (23h43 instead of 21h43!! However it displays correctly that the modification time is 21h43) There is for sure a difference in the treatment of picture and video. Note 1: the file time stamp is correct for both files (21h4x). Note 2: as a result, mixed directory with pictures AND video cannot be sorted by time: the sorting is not correct. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400217] Incorrect Video date/time information: shifted by 2 hours
https://bugs.kde.org/show_bug.cgi?id=400217 --- Comment #1 from Nicofo --- See original picture and video in attached zip file (too big (8 MB) to upload it in Bugzilla so see in http://nicofo.tuxfamily.org/tmp/example.zip ) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400376] New: Picture with wrong GPS value -> better to display "Unavailable"
https://bugs.kde.org/show_bug.cgi?id=400376 Bug ID: 400376 Summary: Picture with wrong GPS value -> better to display "Unavailable" Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Metadata-Gps Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- Created attachment 115925 --> https://bugs.kde.org/attachment.cgi?id=115925&action=edit Digikam Screenshot with invalid GPS values SUMMARY I have some pictures with no valid GPS data (latitude out of [-90 +90] ; longitude out of [-180 +180]). These invalid GPS data are displayed in the MetaData Panel (Exif part) of Digikam (Right Panel) - see attachment. Should be better to display "Unavailable" (or "Invalid" ...) See an example of picture with invalid GPS data: http://nicofo.tuxfamily.org/tmp/panasonic-tz40-GPS-ACTIVE-BUT-NO-SIGNAL.JPG Note: is someway related to bug #326406 : such image is now no more geolocalised (good) but invalid GPS data is still displayed in Metadata panel. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 378253] Duplicated Icon of Digikam in Gnome shell menu
https://bugs.kde.org/show_bug.cgi?id=378253 Nicofo changed: What|Removed |Added Version|5.6.0 |6.0.0 Platform|Fedora RPMs |unspecified --- Comment #1 from Nicofo --- Still valid with digikam 6.0 Beta2 from Appimage (Note - also valid with Fedora RPM's 5.9) Note that in the panel, with Appimage, these are 2 different icons: * the 1st (DK set in the favourite) is an undefined icon (see bug #381739) * the 2nd (running program) is a digikam icon Expected result: only one digikam icon (underlined in blue when program is running) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400433] New: After visiting 'Trash' folder, it is difficult to select 'Preview' mode (remains in 'Thumbnails' mode)
https://bugs.kde.org/show_bug.cgi?id=400433 Bug ID: 400433 Summary: After visiting 'Trash' folder, it is difficult to select 'Preview' mode (remains in 'Thumbnails' mode) Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- SUMMARY 'Preview' mode not working after visiting Trash folder. STEPS TO REPRODUCE 1. Explore a folder in 'Preview' mode 2. Go to Trash (mode switches to 'Thumbnails') 3. Go back to previous folder: it is now in 'Thumbnails' mode and clicking on 'Preview' does not work (even though the button 'Preview' is selected !!). Double clicking on the selected picture does not work neither. Double clicking on ANOTHER picture may work. Note - not sure it is 100% reproducible, steps may vary a bit. But usually I have the bug. ADDITIONAL INFORMATION Is also present in digikam 5.9 from Fedora RPM's -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400434] New: Trash content disappears after selecting 'Map' or 'Table' view
https://bugs.kde.org/show_bug.cgi?id=400434
Bug ID: 400434
Summary: Trash content disappears after selecting 'Map' or
'Table' view
Product: digikam
Version: 6.0.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: digikam-bugs-n...@kde.org
Reporter: nic...@tuxfamily.org
Target Milestone: ---
STEPS TO REPRODUCE
1. Go to Trash (Mode 'Thumbnails' becomes active) [Trash is not empty]
2a. Select 'Map' mode -> a map appears with no picture
2b. OR Select 'Table' mode -> an empty list appears
3. Select 'Thumbnails' mode again: Trash seems empty !
(It is not: explore another folder and go back to Trash -> content is still
present).
NOTE - QUESTION
Why is the 'Preview' mode disabled in the Trash ? For me it should not be
disabled ! (I mean I don't see any reason for disabling it)
Eventually other modes ('Table' and 'Maps') could be disabled if too
complicated to managed (because these modes require database I suppose ?).
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 400376] Picture with wrong GPS value -> better to display "Unavailable"
https://bugs.kde.org/show_bug.cgi?id=400376 --- Comment #4 from Nicofo --- OK agreed. Thanks for explanations. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400434] Trash content disappears after selecting 'Map' or 'Table' view
https://bugs.kde.org/show_bug.cgi?id=400434 --- Comment #2 from Nicofo --- OK. And what about 'Preview' mode ? Isn't possible to enable it in the Trash (no need for database I suppose: it is like the 'Thumbnails' mode) ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412999] New: Some photos downloaded in previous version of digikam no more recognized as already downloaded
https://bugs.kde.org/show_bug.cgi?id=412999 Bug ID: 412999 Summary: Some photos downloaded in previous version of digikam no more recognized as already downloaded Product: digikam Version: 6.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Import-History Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- SUMMARY With Digikam 6.3, import pictures. Observation: some pictures already imported with previous version of digikam (e.g. 6.1 or older) are not recognized as already downloaded. Note: the opposite is also true: import pictures with Digikam 6.3. In Digikam 6.1, import pictures: observe that some pictures imported with 6.3 are not recognized as already downloaded. If I again import an already unrecognized imported picture, I see in the digikam4.db (DownloadHistory table) that the filedate is not the same for both imports. My guess: with Digikam 6.1 and older, EXIF date was used while with 6.3 filedate is used to store the date in db. As a result, loss of compatibility between 6.1 and 6.3. (I have not tested 6.2) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412999] Some photos downloaded in previous version of digikam no more recognized as already downloaded
https://bugs.kde.org/show_bug.cgi?id=412999 --- Comment #3 from Nicofo --- Hum, indeed, if I play with the setting "Use file metadata (makes connection slower)" in Settings > Camera > Behavior, I have no recognition problem anymore. Something has changed between 6.1 and 6.3 regarding this setting. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413189] New: Status bar text not correct in Trash view
https://bugs.kde.org/show_bug.cgi?id=413189 Bug ID: 413189 Summary: Status bar text not correct in Trash view Product: digikam Version: 6.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-Trash Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- SUMMARY In the Trash view, the status bar bottom left displays text not related to the trash but to the previously selected album. STEPS TO REPRODUCE 1. Select an album (e.g. in Thumbnail mode). Status bar displays something like "picture15.jpg (15 of 78)" 2. Go to the Trash. OBSERVED RESULT Status bar still displays the same text. EXPECTED RESULT Status bar still should display something like "deleted_picture.jpg (1 of )" SOFTWARE/OS VERSIONS Digikam 6.3 appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413196] New: Cannot export "a lot" of pictures to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413196 Bug ID: 413196 Summary: Cannot export "a lot" of pictures to OneDrive Product: digikam Version: 6.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-WebService-OneDrive Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- SUMMARY Using "Export to Onedrive" tool works for a few pictures. When exporting a lot of them (e.g. an entire album of 100 pictures), an error occurs after a few (e.g. 3) pictures have been exported: Error transferring https://graph.microsoft.com/v1.0/me/drive/root://Images/Holliday 003.jpg:/content - server replied: Internal Server Error Note: maybe related to the size of the pictures ? When using the option "Resize photos before uploading", I encounter less problems. SOFTWARE/OS VERSIONS Digikam 6.3 (appimage), but this bug is not new (actually "Export to Onedrive" tool has never worked well for me). Also applicable on Fedora_RPM 6.1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413197] New: Export to Onedrive > Create New Album: improvement when adding album
https://bugs.kde.org/show_bug.cgi?id=413197
Bug ID: 413197
Summary: Export to Onedrive > Create New Album: improvement
when adding album
Product: digikam
Version: 6.3.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: Plugin-WebService-OneDrive
Assignee: digikam-bugs-n...@kde.org
Reporter: nic...@tuxfamily.org
Target Milestone: ---
SUMMARY
In Export to OneDrive, when Creating a new Album, it would be nice that that
newly created album becomes selected.
Indeed, usually, if we create a new album in the "Export to Onedrive" tool, it
is to export the pictures in that newly created folder.
STEPS TO REPRODUCE
1. open the tool "Export to Onedrive"
2. select an album, e.g. "Pictures/2019"
3. create an album ("New Album" button), e.g. "October"
OBSERVED RESULT
1. the selected album is still "Pictures/2019"
EXPECTED RESULT
1. the selected album should be "Pictures/2019/October"
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 413199] New: Error when exporting a video to OneDrive
https://bugs.kde.org/show_bug.cgi?id=413199 Bug ID: 413199 Summary: Error when exporting a video to OneDrive Product: digikam Version: 6.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-WebService-OneDrive Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- SUMMARY Exporting videos (mp4 in my case) to Onedrive produces the following error message: Failed to upload photo to OneDrive. Do you want to continue? STEPS TO REPRODUCE 1. Select pictures+videos to export OBSERVED RESULT 1. For each video, the error message occurs (=popup ; as a result, the export of following files is interrupted until the popup is closed) EXPECTED RESULT Video should be exported. If not possible to export videos, at least the error message should not displayed each time ! SOFTWARE/OS VERSIONS Digikam 6.3 Appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400433] After visiting 'Trash' folder, it is difficult to select 'Preview' mode (remains in 'Thumbnails' mode)
https://bugs.kde.org/show_bug.cgi?id=400433 Nicofo changed: What|Removed |Added Version|6.0.0 |6.3.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406855] Feature request: date from filename
https://bugs.kde.org/show_bug.cgi?id=406855 Nicofo changed: What|Removed |Added CC||nic...@tuxfamily.org --- Comment #10 from Nicofo --- Sorry to interfere in this bug report ;) I have also old pictures without exif whose name contain the date, but the date format varies a lot. After a rapid research I have: _mmdd _mmdd_hhmmss dd_mm (no year) dd_mm yy etc... (I'm sure other users could easily add few more) Also if I have for 'dd_mm' e.g. 03_05, I wonder how you could automatically detect if the format is dd_mm or mm_dd ? So, instead of modifying the code each time a new file format is detected, it should be good if it was possible to manually tell what is the date format in the file name. E.g. a popup where you can manually enter the date template. Just an idea... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404962] New: List of subfolders: incorrect encoding (spaces -> %20, accents)
https://bugs.kde.org/show_bug.cgi?id=404962 Bug ID: 404962 Summary: List of subfolders: incorrect encoding (spaces -> %20, accents) Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-WebService-OneDrive Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- Created attachment 118467 --> https://bugs.kde.org/attachment.cgi?id=118467&action=edit Digikam - list of folders in Onedrive SUMMARY 1. Select files > Export to Onedrive 2. Connect to your account 3. See the list of Albums: the name of the folders itself (after last "/") is correctly displayed, but not the name of the full path. Example: - Images/Images Enregistrées - Images/Images%20Enregistr%C3%A9%es/Test Should be - Images/Images Enregistrées - Images/Images Enregistrées/Test (see screenshot) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #6 from Nicofo --- I found a workaround using LD_PRELOAD: LD_PRELOAD=/usr/lib64/libssl.so.10:/usr/lib64/libcrypto.so.10 ./digikam.appimage According to bug report in openssl, it should however be fixed in appimage (please see https://bugzilla.redhat.com/show_bug.cgi?id=1668916 for details): > Appimage packagers should package their bundled openssl in such way that it > does not depend on system-wide configuration files, because they cannot > depend on what is in them. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #8 from Nicofo --- Great, it seems to work with DK 6.1. There is another (similar ?) appimage issue: $ Downloads/digikam-6.1.0-git-20190304T120153-x86-64.appimage libfreetype.so libudev.so -- digiKam AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application -- Preloading shared libs: digikam: symbol lookup error: /lib64/libfontconfig.so.1: undefined symbol: FT_Done_MM_Var $ As a workaround, the appimage must be launched with LD_PRELOAD=/usr/lib64/libfreetype.so.6:/usr/lib64/libudev.so.1 Could it be solved as well ? (if you prefer, I can open a new bug report) -- You are receiving this mail because: You are watching all bug changes.
