Hi,
I'm using digikam since years on linux (ubuntu), with a mysql/mariadb setup, which works quite well. The last digikam version for ubuntu I got as a installable package is digikam 5.6, with that version I can see the geolocation of my images by simply clicking on the map button on top of the program window. But I would like to go on with newer version and with all AppImage versions I tried the geolocation is working different. With the 5.8 version I can now see my geolocation while I edit my files with its locations, but not wenn I simply click on the map button. Does anyone has an idea what I need to change in the configuration to get the old and most likely still available behaviour? Or is there a ppa for ubuntu around with the latest digikam versions? Also please node that I'm currently using the last LTS version 16.04. Kind Regards Martin |
I think Geolocation was broken in 5.7.0 but it should be back in 5.8.0 I will take a look later Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Martin Bruns <[hidden email]> Date: 2018-01-19 7:29 AM (GMT-07:00) To: [hidden email] Subject: geolocation in AppImage I'm using digikam since years on linux (ubuntu), with a mysql/mariadb setup, which works quite well. The last digikam version for ubuntu I got as a installable package is digikam 5.6, with that version I can see the geolocation of my images by simply clicking on the map button on top of the program window. But I would like to go on with newer version and with all AppImage versions I tried the geolocation is working different. With the 5.8 version I can now see my geolocation while I edit my files with its locations, but not wenn I simply click on the map button. Does anyone has an idea what I need to change in the configuration to get the old and most likely still available behaviour? Or is there a ppa for ubuntu around with the latest digikam versions? Also please node that I'm currently using the last LTS version 16.04. Kind Regards Martin |
yes, exactly. 5.7.0 is broken with Marble component, 5.8.0 restore the feature. I just published the new 5.9.0 pre release AppImage, with all components updated. Please test and give me a feedback. Note: all work as expected here (:=)))... Gilles Caulier 2018-01-20 16:36 GMT+01:00 Andrey Goreev <[hidden email]>:
|
The problem is related to this bug report:
https://bugs.kde.org/show_bug.cgi?id=374302 Due to different system and AppImage locale, it comes by MySQL to a wrong interpretation of the comma / point in double values. I can reproduce it here, but have no solution at the moment, because it only occurs with the AppImage. With my native digiKam version I can set any system locale without any problems. Maik Am Samstag, 20. Januar 2018, 16:40:47 CET schrieb Gilles Caulier: > Hi all, > > For digiKam 6.0.0 i posted only one entry for GoSC 2018 : > > https://community.kde.org/GSoC/2018/Ideas#digiKam > > This one is very important for the future and must be on top level priority. > We must found a student to work on this project. I will prepare the code in > BQM previously to be able to host export tool implementations. See my > previous mail in this room about BQM and export tools for DK 6.0.0... > > Maik, plan to post a second proposal about this bugzilla entry : > > https://bugs.kde.org/show_bug.cgi?id=91562 > > The 2 ones are enough complex to manage for me and Maik, If another > developer want to mentor a student about another topic, please post the > proposal to the KDE community wiki page. > > Voila. Have a good week end. > > Gilles Caulier |
In reply to this post by AndriusWild
I just checked on 5.8.0 from openSUSE graphics repository and it works as expected. If I preview an image it shows up correctly on the map. Best regards, On Sat, Jan 20, 2018 at 8:36 AM, Andrey Goreev <[hidden email]> wrote:
|
In reply to this post by Maik Qualmann
Thanks for the information,
BTW.: I got the same behaviour for digikam 5.6...pre5.9 in case I use the AppImage one. Meaning the geolocation data is only read and displayed when I use the edit geolocation tool, but not when I just mark some images and click on map. So anything I can help with further analysing the problem? My understanding is that it is somewhere in the MySQL <=> digikam communication. M Am 20.01.2018 um 17:13 schrieb Maik Qualmann: > The problem is related to this bug report: > > https://bugs.kde.org/show_bug.cgi?id=374302 > > Due to different system and AppImage locale, it comes by MySQL to a wrong > interpretation of the comma / point in double values. I can reproduce it here, > but have no solution at the moment, because it only occurs with the AppImage. > With my native digiKam version I can set any system locale without any > problems. > > Maik > > Am Samstag, 20. Januar 2018, 16:40:47 CET schrieb Gilles Caulier: >> Hi all, >> >> For digiKam 6.0.0 i posted only one entry for GoSC 2018 : >> >> https://community.kde.org/GSoC/2018/Ideas#digiKam >> >> This one is very important for the future and must be on top level priority. >> We must found a student to work on this project. I will prepare the code in >> BQM previously to be able to host export tool implementations. See my >> previous mail in this room about BQM and export tools for DK 6.0.0... >> >> Maik, plan to post a second proposal about this bugzilla entry : >> >> https://bugs.kde.org/show_bug.cgi?id=91562 >> >> The 2 ones are enough complex to manage for me and Maik, If another >> developer want to mentor a student about another topic, please post the >> proposal to the KDE community wiki page. >> >> Voila. Have a good week end. >> >> Gilles Caulier > |
Try to open the map in the right panel first and click on images after that. That's how it works on my system Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Martin Bruns <[hidden email]> Date: 2018-01-22 6:06 AM (GMT-07:00) To: [hidden email] Subject: Re: geolocation in AppImage BTW.: I got the same behaviour for digikam 5.6...pre5.9 in case I use the AppImage one. Meaning the geolocation data is only read and displayed when I use the edit geolocation tool, but not when I just mark some images and click on map. So anything I can help with further analysing the problem? My understanding is that it is somewhere in the MySQL <=> digikam communication. M Am 20.01.2018 um 17:13 schrieb Maik Qualmann: > The problem is related to this bug report: > > https://bugs.kde.org/show_bug.cgi?id=374302 > > Due to different system and AppImage locale, it comes by MySQL to a wrong > interpretation of the comma / point in double values. I can reproduce it here, > but have no solution at the moment, because it only occurs with the AppImage. > With my native digiKam version I can set any system locale without any > problems. > > Maik > > Am Samstag, 20. Januar 2018, 16:40:47 CET schrieb Gilles Caulier: >> Hi all, >> >> For digiKam 6.0.0 i posted only one entry for GoSC 2018 : >> >> https://community.kde.org/GSoC/2018/Ideas#digiKam >> >> This one is very important for the future and must be on top level priority. >> We must found a student to work on this project. I will prepare the code in >> BQM previously to be able to host export tool implementations. See my >> previous mail in this room about BQM and export tools for DK 6.0.0... >> >> Maik, plan to post a second proposal about this bugzilla entry : >> >> https://bugs.kde.org/show_bug.cgi?id=91562 >> >> The 2 ones are enough complex to manage for me and Maik, If another >> developer want to mentor a student about another topic, please post the >> proposal to the KDE community wiki page. >> >> Voila. Have a good week end. >> >> Gilles Caulier > |
That way only works with the non AppImage version 5.6 I have.
With the others the map is grey when I click the map button on the right panel. M Am 22.01.2018 um 14:11 schrieb Andrey
Goreev:
|
Hi,
I found that when I start the AppImage version with the following it is working. LC_ALL=en_US.UTF-8 ./digikam-5.8.0-01-x86-64.appimage Strangely the menu is still in German, but that way it is only a small start script to workaround the problem. Thanks Martin Am 22.01.2018 um 16:16 schrieb Martin
Bruns:
That way only works with the non AppImage version 5.6 I have. |
Free forum by Nabble | Edit this page |