I'm using openSUSE 42.3 with digikam 5.7. Any time I click on map tool, digikam crash. I installed debug package but, for unknown reason, I cannot generate a useful backtrace. The only content that I got is: Application: digiKam (digikam), signal: Segmentation fault From drkonqi: pa_write() failed while trying to wake up the mainloop: Descritor de arquivo inválido Invalid write to eventfd: Descritor de arquivo inválido Code should not be reached at pulsecore/fdsem.c:199, function pa_fdsem_post(). Aborting. KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 Unable to start Dr. Konqi Re-raising signal for core dump handling.
OpenSUSE Leap 42.3 is officially on digiKam-5.5.0. Which beta/extra repository did you add for digiKam-5.7.0? I suspect a package problem with Marble. Maik
I updated to digikam 5.7 using the repository: http://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Leap_42.3/ I'm using the Marble 2.2.20 (KDE version)
Sorry, the right repo for digikam 5.7 is: http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Leap_42.3/
I have openSUSE Leap 42.3 on my service laptop in the company. After updating to digiKam-5.7.0 from the KDE extra repository, I can not reproduce problems with the map. Everything works as expected from this version. Have you possibly installed other updates? Please post the help-> components info. Otherwise, the GDB backtrace would be interesting also without debugging symbols Maik
This is my components info (in Portuguese): digikam version 5.7.0 CPU cores: 8 Eigen: 3.2.9 Exiv2: 0.26 Exiv2 can write to Jp2: Sim Exiv2 can write to Jpeg: Sim Exiv2 can write to Pgf: Sim Exiv2 can write to Png: Sim Exiv2 can write to Tiff: Sim Exiv2 supports XMP metadata: Sim KF5: 5.32.0 LensFun: 0.3.2-0 LibCImg: 130 LibJPEG: 80 LibJasper: 1.900.14 LibLCMS: 2080 LibLqr support: Sim LibPGF: 7.15.32 LibPNG: 1.6.8 LibRaw: 0.18.2 LibTIFF: 4.0.8 Marble: 0.27.1 Parallelized demosaicing: Sim Qt: 5.10.0 Infraestrutura do banco de dados: QSQLITE LibGphoto2: 2.5.13 LibKipi: 5.2.0 LibOpenCV: 3.3.1 LibQtAV: 1.12.0 Plugins do Kipi: 5.7.0 Suporte ao AkonadiContact: Sim Suporte ao Baloo: Sim Suporte ao calendário: sim Suporte para galerias HTML: sim Suporte para leitores multimédia: Sim Suporte para o D-Bus: Sim Suporte à panorâmica: sim I'm not sure if this issue can be result of the other repository mentioned (http://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Leap_42.3/). This repository installed the latest Kde applications (17.12). The Marble works fine (stand alone at least). I already tried to remove the digikamrc but the crash persists.
Qt-5.10.0? This is not a normal openSUSE Leap 42.3 anymore. And Qt will not be updated when installing digiKam-5.7.0. OpenSUSE Tumbleweed is still using Qt-5.9.3 here. Maik
About the GDB, this is what I got: Thread 1 "digikam" received signal SIGSEGV, Segmentation fault. 0x00007fffee951baa in Marble::GeoSceneLayer::backend() const () from /usr/lib64/libmarblewidget-qt5.so.27 I made some tests and I figured out what happened. The problem was the other repo. According the backtrace above, the digikam was compiled with the libmarblewidget-qt5.so.27, provided by KDE Apps 17.04. The new repo provides KDE Apps 17.12, with libmarblewidget-qt5.so.28. This broke the system. I removed the new Marble and installed the old one and the problem was solved. Maik, thank you for your help.
And digiKam-5.7.0 is not really ready for Qt >= 5.9.3. This requires the current git version of digiKam-5.8.0. I do not know if openSUSE has patched the digiKam-5.7.0 version for this. Maik