I just updated kamerka to the upstream KF5 port: https://github.com/dos1/kamerka On my machine, it segfaults on launch: Program received signal SIGSEGV, Segmentation fault. 0x00007fffee80fef4 in _GLOBAL__sub_I_qprinterinfo.cpp () from /lib64/libQtGui.so.4 (gdb) bt #0 0x00007fffee80fef4 in _GLOBAL__sub_I_qprinterinfo.cpp () at /lib64/libQtGui.so.4 #1 0x00007ffff7dec0ca in call_init.part () at /lib64/ld-linux-x86-64.so.2 #2 0x00007ffff7dec1db in _dl_init () at /lib64/ld-linux-x86-64.so.2 #3 0x00007ffff7dddc8a in _dl_start_user () at /lib64/ld-linux-x86-64.so.2 #4 0x0000000000000001 in () #5 0x00007fffffffdf59 in () #6 0x0000000000000000 in () This looks exactly like a segfault I used to have with a libvlc/Qt based app: https://github.com/MBach/Miam-Player/issues/9 It was eventually solved via bug 15311. Here vlc does not seem involved, so I guess the culprit is qimageblitz: $ urpmq --requires lib64qimageblitz4 libQtCore.so.4()(64bit) libQtGui.so.4()(64bit) libc.so.6()(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.4)(64bit) libm.so.6()(64bit) libm.so.6(GLIBC_2.2.5)(64bit) libstdc++.so.6()(64bit) libstdc++.so.6(GLIBCXX_3.4)(64bit) So actually while writing this issue I've debugged it and narrowed down that it's an upstream bug - the dependency on qimageblitz has to be reconsidered, as it has no Qt5 port. While open an issue upstream and just keep this one as a reminder to fix (or drop) kamerka before the release of Mageia 6.
Reported upstream: https://github.com/dos1/kamerka/issues/27
Keywords: (none) => UPSTREAMSee Also: (none) => https://github.com/dos1/kamerka/issues/27
Should be fixed with kamerka-0.12-3.20161002.2.mga6 as it now links against the newly imported qimageblitz5 (Qt5 version of qimageblitz).
Status: NEW => RESOLVEDResolution: (none) => FIXED