When doing a panorama, everything works fine up to the panorama generation. Then, nothing happens and Digikam is stalled. It is not possible to close the panorama window, and the only way is to quit kill the program. I run it from the terminal, here are the messages I get: philippe@philippe-desktop:~/Bureau$ ./digikam-5.8.0-01-x86-64.appimage -- digiKam AppImage Bundle -- Use 'help' as CLI argument to know all available options QtAV 1.12.0(Jul 20 2017, 17:39:32) Multimedia framework base on Qt and FFmpeg. Distributed under the terms of LGPLv2.1 or later. Shanghai University->S3 Graphics->Deepin->PPTV, Shanghai, China Copyright (C) 2012-2016 Wang Bin (aka. Lucas Wang) wbsecg1@gmail.com Donate: http://qtav.org/donate.html Source: https://github.com/wang-bin/QtAV Home page: http://qtav.org capi::version: 0.6.0 Cannot connect to server socket err = Aucun fichier ou dossier de ce type Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified kf5.kservice.sycoca: Parse error in "/home/philippe/.config/menus/applications-merged/xdg-desktop-menu-dummy.menu" , line 1 , col 1 : "unexpected end of file" The desktop entry file "/usr/share/applications/colorhug-docs.desktop" has Type= "Link" instead of "Application" or "Service" kf5.kservice.sycoca: Invalid Service : "/usr/share/applications/colorhug-docs.desktop" The desktop entry file "/usr/share/applications/unity-lens-photos.desktop" has Type= "Application" but no Exec line kf5.kservice.sycoca: Invalid Service : "/usr/share/applications/unity-lens-photos.desktop" The desktop entry file "/usr/share/applications/org.gnome.ChromeGnomeShell.desktop" has Type= "Application" but no Exec line kf5.kservice.sycoca: Invalid Service : "/usr/share/applications/org.gnome.ChromeGnomeShell.desktop" The desktop entry file "/usr/share/applications/extras-my-weather-indicator.desktop" has Type= " Application" instead of "Application" or "Service" kf5.kservice.sycoca: Invalid Service : "/usr/share/applications/extras-my-weather-indicator.desktop" QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified Cropping... digikam.database: No location could be retrieved for "/tmp/digiKam-panorama-tmp-6omA5q/preview.jpg"
First, which Hugin version do you use ? Second, can you share your pano files to try to reproduce here ? Gilles Caulier
I'm using Hugin: 2017.0.0.eac5e8cc546e I get this problem for example with the pictures you can download here: https://iciouailleurs-photos.mycozy.cloud/public?sharecode=eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJzaGFyZSIsImlhdCI6MTUxOTU1NTY4OSwiaXNzIjoiaWNpb3VhaWxsZXVycy5teWNvenkuY2xvdWQiLCJzdWIiOiJlbWFpbCJ9.8YxqgSbLv88c2gPjVoJcC7aekywZgHPCI2DGJE9L6uwClmk-2kT764z7k8cXZgRoiaakFj98qTtbXRrRvcml7w&id=bad53573fa1a841eb40458a23fe735b0 but it happens most of the time, whatewer are the pictures.
All work as expected with digiKam 6.0.0 git implmeentation and Hugin 2016.2 https://www.flickr.com/photos/digikam/40430534662/in/pool-digikam-labs/ Gilles Caulier
No problem with 5.9.0 pre-release AppImage and Hugin 2016.2 : https://www.flickr.com/photos/digikam/40474079731/in/pool-digikam-labs/ I suspect a problem with your Hugin version. 5.9.0 appimage pre release can be downloaded here : https://files.kde.org/digikam/ ..if you want to test, but i'm not that nothing change between 5.8.0 and 5.9.0 implementation about panorama tool. Gilles Caulier
..if you want to test, but i'm not that nothing change between 5.8.0 and 5.9.0 implementation about panorama tool. ==> ...if you want to test, but i'm sure that nothing has changed between 5.8.0 and 5.9.0 implementation about panorama tool. Sorry for the typo (:=)))...
Hello, thanks for the tests. It is strange, because sometimes it works, once or twice before stalling, and sometimes it stalls immediatly. I'm currently downloading digikam 5.9 prerelease to test. Also, I have noticed that Hugin has released Hugin 2018.0.0. Do you think I should try to install it to test ? Regards.
Hello, I get the same problem with prerelease 5.9.0. Also, after few trials, I finally get the panorama done with the pictures I submitted here, but get the same problem with another set of pictures. When I launch the panorama generation, and look at the processor activity, I notice that it starts the generation (processor at 100 %) and then stops after 10 to 20 seconds, and then Digikam is stalled...
Strange, i cannot reproduce the problem here. I process panorama many time by month without to notice this kind of dysfunction. Please instead to try a fresh release, if you can try with same release than me as 2016.2 which work like a charm here (official package from Mageia6) Note: i remember that i report a dysfunction in Magiea team about hugin, linked with a bugous version of Exiv2 (0.25) which stop the processing quickly without any report in digiKam. I discovered the source of the problem by running Hugin CLI tool by hand on my image and finally to seen an Exiv2 crash while metadata parsing. The reason to not seen any report in digiKam is the way to process Hugin stage in separated and chained threads. Probably a missing exception catch can fix the problem but in all case, using Exiv2 0.26 so far more safe than 0.25. To be sure, run ldd over the hugin executable and look which Exiv2 version is used at linking time. Mine : [gilles@localhost reports]$ ldd /usr/bin/hugin |grep exiv2 libexiv2.so.26 => /lib64/libexiv2.so.26 (0x00007f5c4dc0e000) Gilles Caulier
Hello Gilles, thanks a lot for your help. I follow your advice, but i do not know how to handle the results I get: Hugin is using a very old version of exiv2, this is probably the source of the problem I have: philippe@philippe-desktop:~$ ldd /usr/bin/hugin |grep exiv2 libexiv2.so.14 => /usr/lib/x86_64-linux-gnu/libexiv2.so.14 (0x00007eff8d5fd000) However, when i try to update exiv2, it seems I have the latest release installed: philippe@philippe-desktop:~$ sudo apt-get install exiv2 Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait exiv2 est déjà la version la plus récente (0.25-3.1). So I do not know how to «tell» Hugin to use the latest version of libexiv2. I searched on Google, but did not find any useful information. If you have a suggestion, that would be really useful !
One more information: on the «about» panel in Hugin, I get the following information, saying that Hugin is in fact using exiv2.025. This information is different that the one given by ldd, so I do not know what to think... Système d’exploitation : Linux 4.13.0-37-generic x86_64 Architecture : 64 bits Mémoire libre : 4413052 kio Hugin Version : 2017.0.0.eac5e8cc546e Chemin vers les ressources : /usr/share/hugin/xrc/ Chemin vers les données : /usr/share/hugin/data/ Base de données de l’appareil et de l’objectif de Hugin : /home/philippe/.hugindata/camlens.db Multi-processus utilisant C++11 std::thread et OpenMP Profil du moniteur SyncMaster #1 2017-03-31 07-30 2.2 M-S XYZLUT+MTX Bibliothèques wxWidgets: wxWidgets 3.0.3 wxWidgets Library (wxGTK port) Version 3.0.3 (Unicode: wchar_t, debug level: 1), Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.31. libpano13: 2.9.19 Boost: 1.62.0 Exiv2: 0.25 SQLite3: 3.19.3 Vigra: 1.11.0 LittleCMS2: 2.7
It's Exiv2 0.25, which is full of bug. Hugin must use Exiv2 0.26 now, release since a while with a lots of fix. Report this problem as UPSTREAM to your distro packager. You can also report this problem to Hugin to fix the minimum Exiv2 version to 0.26, as it's do on DK. Gilles Caulier
Hello, it seems that Ubuntu has updated Exiv2, and I do not get this problem since this update. I guess the bug may be closed then. Thanks a lot for your help.