digiKam 7 beta 3 and Geolocation Editor ???

Software digiKam
1

I have just now installed digiKam 7.0 beta3 in Linux Mint Cinnamon 19.3

I put a dozen test images in the digiKam folder.

I have used the Geolocation Editor in Windows/digiKam countless times and am well versed in it’s use.

That being said, (in Linux Mint) I selected my dozen images and sent them to the Geolocation Editor.

One of these images already had the correct GPS coordinates embedded; I copied the coordinates from that image and pasted them to the other images.

When I clicked “Apply”, I got a warning that there was a problem and the information could not be written to the files.

I tried this several times, closing the GPS Editor and starting all over each time, and got the same error every time.

I made certain read/write permissions were in order.

I investigated every nook and cranny of the settings and everything looks in order.

I have closed and restarted digiKam to no avail.

The error box I get says “There is some information that cannot be written to the file” (My wording may not be exact)

Is anyone else experiencing this behavior ?

I have downloaded digiKam 7.0 beta2 win64 and had intended to install it on my Windows 7 machine; but, after the problem that I am having in digiKam/Linux Mint, I believe I will hold off.

Edit: One thing I do really like about this new version = it gave me back the HUGE thumbnails that I used to have way back many versions ago. I know that, when I updated versions years ago and lost the huge thumbnails, I almost went over the hill talking to myself I was so disillusioned about trying to work with the little-bitty thumbnails that the last several versions have had.

2

You can try launching digikam from console and see what digikam prints in there when the error occurs.

You can just open console, type “digikam” and press enter if you use the version from linux mint repo or drag and drop the digikam appimage file to the console and press enter after if you use appimage.

3

x@x-VirtualBox:~$ ‘/home/x/Applications/digikam-7.0.0-beta3-20200422T062854-x86-64_ef1d83a71d96633ac20d81a2cb538e2b.appimage’

qt5ct: using qt5ct plugin

** (AppImageLauncher:14052): WARNING **: 00:11:22.975: Pixbuf theme: Cannot load pixmap file /usr/share/themes/Mint-Y/gtk-2.0/assets/trough-progressbar.png: Failed to load image ‘/usr/share/themes/Mint-Y/gtk-2.0/assets/trough-progressbar.png’: Fatal error in PNG image file: bad parameters to zlib

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:22.985: gdk_pixbuf_get_width: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:22.988: gdk_pixbuf_get_height: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

** (AppImageLauncher:14052): WARNING **: 00:11:22.988: Invalid borders specified for theme pixmap:

    /usr/share/themes/Mint-Y/gtk-2.0/assets/trough-progressbar.png,

borders don’t fit within the image

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:22.989: gdk_pixbuf_get_n_channels: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:22.989: gdk_pixbuf_get_pixels_with_length: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:22.990: gdk_pixbuf_get_rowstride: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:22.991: gdk_pixbuf_get_n_channels: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:22.991: gdk_pixbuf_get_pixels_with_length: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:22.991: gdk_pixbuf_get_rowstride: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:22.991: gdk_pixbuf_get_n_channels: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:22.991: gdk_pixbuf_get_pixels_with_length: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:22.992: gdk_pixbuf_get_rowstride: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:22.992: gdk_pixbuf_get_n_channels: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:22.992: gdk_pixbuf_get_pixels_with_length: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.001: gdk_pixbuf_get_rowstride: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.002: gdk_pixbuf_get_n_channels: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.002: gdk_pixbuf_get_pixels_with_length: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.002: gdk_pixbuf_get_rowstride: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.004: gdk_pixbuf_get_n_channels: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.004: gdk_pixbuf_get_pixels_with_length: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.004: gdk_pixbuf_get_rowstride: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.004: gdk_pixbuf_get_n_channels: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.004: gdk_pixbuf_get_pixels_with_length: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.004: gdk_pixbuf_get_rowstride: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.005: gdk_pixbuf_get_n_channels: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.005: gdk_pixbuf_get_pixels_with_length: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.005: gdk_pixbuf_get_rowstride: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.005: gdk_pixbuf_get_n_channels: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.005: gdk_pixbuf_get_pixels_with_length: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.005: gdk_pixbuf_get_rowstride: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.005: gdk_pixbuf_get_width: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

(AppImageLauncher:14052): GdkPixbuf-CRITICAL **: 00:11:23.005: gdk_pixbuf_get_height: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed

– 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

libnss3.so

– Preloading shared libs: :/tmp/.mount_digikaxMKgPO/usr/lib64/libnss3.so

QtAV 1.13.0(Apr 22 2020, 03:53:50)

Multimedia framework base on Qt and FFmpeg.

Distributed under the terms of LGPLv2.1 or later.

Shanghai, China Copyright (C) 2012-2019 Wang Bin (aka. Lucas Wang) wbsecg1@gmail.com

Donate: http://qtav.org/donate.html

Source: GitHub - wang-bin/QtAV: A cross-platform multimedia framework based on Qt and FFmpeg(https://github.com/wang-bin/avbuild). High performance. User & developer friendly. Supports Android, iOS, Windows store and desktops. 基于Qt和FFmpeg的跨平台高性能音视频播放框架

Home page: http://qtav.org

unknown: Unhandled container to remove : Digikam::DigikamApp

x@x-VirtualBox:~$ export QT_LOGGING_RULES=“digikam*=true”

x@x-VirtualBox:~$

4

I am not sure if you can write metadata to PNG files. Do you write into database only, sidecars or files themselves ?

5

You can write (XMP) metadata to png files, but exif and iptc have charset and length limitations.

But the only png file referenced in the error messages seems to be part of the theme used, not a user file.

Also, remember that any version marked “beta” is not yet finalised and can have bugs.
And if you encounter any, it’s best to report them through the proper channel, so the developers have all bug reports in one place.
If you just want or need to use the program, don’t use beta versions…

6

I don’t know where this PNG business is coming from; digiKam only ever sees my finished jpegs.

The test files that it is refusing to write the GPS info to are definitely jpegs and the ONLY image files that this particular system has ever seen.

7

@BuckSkin
In the output you posted there’s nothing referring to GPS or failure to write to a file, only a bunche of assertion failures, and a reference to a (theme-related) png file…

8

I drag/dropped digiKam onto Terminal, left terminal alone while I tested the GPS editor; I did

  • export QT_LOGGING_RULES=“digikam*=true” - ; and, if it ever did export anything I sure could not find it.
9

Do you have a chance to launch it with ‘debug’ option?

x@x-VirtualBox:~$ /home/x/Applications/digikam-7.0.0-beta3-20200422T062854-x86-64_ef1d83a71d96633ac20d81a2cb538e2b.appimage debug

And then when it happens hit CTRL+C in the console and type ‘bt’ and press enter?

10

Do I just copy/paste that block of text in the Terminal, perform my digiKam Geolocation process, and, with digiKam still up and running, do the CTRL + C/bt Enter bit ?

11

I would try collecting as much info a possible (copy both texts before CTRL-C + bt and after) and submit it here:

https://bugs.kde.org/enter_bug.cgi?product=digikam

I had back luck with Linux Mint and digiKam few years ago as well. Maybe Mint and Qt apps just don’t work well together, I don’t know.

12

When I put

x@x-VirtualBox:~$ /home/x/Applications/digikam-7.0.0-beta3-20200422T062854-x86-64_ef1d83a71d96633ac20d81a2cb538e2b.appimage debug

in Terminal and Enter, it says “Command not Found”