[digikam] [Bug 374302] New: All Images with Geoinfo seem to be at (0°, 0°)

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=374302

--- Comment #18 from Maik Qualmann <[hidden email]> ---
I could also not reproduce the problem by changing the locale.

Maik

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=374302

--- Comment #19 from [hidden email] ---
Maik,

Why the locale will influence the geolocation stuff here ?

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=374302

--- Comment #20 from Lukas Winkler <[hidden email]> ---
I can't test it at the moment, but maybe it is  because I am using German
(DE_AT.UTF). Could it be because of a difference in decimal comma (e.g. comma
instead of dot)

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=374302

--- Comment #21 from Maik Qualmann <[hidden email]> ---
Which database do you use MySQL or MariaDB? The tables longitudeNumber and
latitudeNumber have which field type STRING or REAL?

Maik

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=374302

--- Comment #22 from Lukas Winkler <[hidden email]> ---
I just checked it: I am using MariaDB 10.1.23 on Debian Stretch.

MariaDB [digikamtest]> SELECT * FROM ImagePositions;
+---------+-----------------+--------------------+-----------------+--------------------+----------+-------------+------+------+----------+-------------+
| imageid | latitude        | latitudeNumber     | longitude       |
longitudeNumber    | altitude | orientation | tilt | roll | accuracy |
description |
+---------+-----------------+--------------------+-----------------+--------------------+----------+-------------+------+------+----------+-------------+
|       1 | 48,25.23788333N | 48.420631388888886 | 15,37.13064167E |
15.618844027777778 |      249 |        NULL | NULL | NULL |     NULL | NULL    
   |
+---------+-----------------+--------------------+-----------------+--------------------+----------+-------------+------+------+----------+-------------+
1 row in set (0.00 sec)

MariaDB [digikamtest]> describe ImagePositions;
+-----------------+----------+------+-----+---------+-------+
| Field           | Type     | Null | Key | Default | Extra |
+-----------------+----------+------+-----+---------+-------+
| imageid         | int(11)  | NO   | PRI | NULL    |       |
| latitude        | longtext | YES  |     | NULL    |       |
| latitudeNumber  | double   | YES  |     | NULL    |       |
| longitude       | longtext | YES  |     | NULL    |       |
| longitudeNumber | double   | YES  |     | NULL    |       |
| altitude        | double   | YES  |     | NULL    |       |
| orientation     | double   | YES  |     | NULL    |       |
| tilt            | double   | YES  |     | NULL    |       |
| roll            | double   | YES  |     | NULL    |       |
| accuracy        | double   | YES  |     | NULL    |       |
| description     | longtext | YES  |     | NULL    |       |
+-----------------+----------+------+-----+---------+-------+
11 rows in set (0.00 sec)

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=374302

--- Comment #23 from Lukas Winkler <[hidden email]> ---
Another insight:
I just started Digikam with LANG=C /opt/digikam-5.6.0-01-x86-64.appimage and it
converted the digikam locale to 'US-ASCII' and geodata worked.

But then I started it with LANG=de_AT /opt/digikam-5.6.0-01-x86-64.appimage
(notice that my system locale is de_AT.UTF8) and digikam converted the database
back to UTF-8, but started in English and it still worked.

Finally I started it with LANG=de_AT.UTF8 /opt/digikam-5.6.0-01-x86-64.appimage
and now it started in German and it didn't work anymore.

I think it doesn't have much to do with the database, but some part of Digikam
(KDE? Qt?) is interpreting something wrong with a German locale set.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=374302

Maik Qualmann <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |CONFIRMED
     Ever confirmed|0                           |1

--- Comment #24 from Maik Qualmann <[hidden email]> ---
Strangely, I can actually reproduce the problem with the AppImage. But not with
my compiled and installed version of digiKam.

Maik

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=374302

--- Comment #25 from [hidden email] ---
Maik,

AppImage bundle use a bash script to start the application, depending of CLI
option passed by user.

The script can miss some rules to fix this problem.

The script is here :

https://cgit.kde.org/digikam-software-compilation.git/tree/project/bundles/appimage/data/AppRun

To tune this script without to re-build whole AppImage, it's very simple.
Download last appImage bundle, and mount it in local. In fact AppImage is an
ISO9660 drive loaded in memory. As root :

#mkdir ./test.appimage
#mount ./digikam-5.6.0-01-x86-64.appimage ./test.appimage
mount: /dev/loop0 is write-protected, mounting read-only
#ls ./test.appimage
AppRun*  digikam.desktop*  digikam.png  usr/

As the bundleis mounted as read only, just copy the whole directory somewhere
in your home dir and edit AppRun script. To start application, run this script
as well...

Magic no ?

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=374302

--- Comment #26 from Lukas Winkler <[hidden email]> ---
Hi, sorry it took so long for an answer, but the last month was quite
stressful.

I am not sure how editing the AppRun bash script will solve this.

Hardcoding the LANG env doesn't fix the issue, but only makes it reproducible.

In the meantime I have found out that if I start digikam with LANG=de
/opt/digikam-5.6.0-01-x86-64.appimage
(which is an invalid locale) it starts with an English user interface (because
of that the geodata is working correctly), but it doesn't trigger the "do you
want to convert the database to ASCII" dialog (I am afraid that will create
problems as many of my photos include special characters).

--
You are receiving this mail because:
You are the assignee for the bug.