| View previous topic :: View next topic |
| Author |
Message |
Goverp
l33t
Joined: 07 Mar 2007
Posts: 639
|
 Posted: Sat Oct 22, 2016 1:21 pm Post subject: [SOLVED] Segfault in digikam 4.4.0-r1 |
 |
|
Following this weeks update, digikam's stopped working. It segfaults immediately after startup - you cant even get as far as "digikam -v" working. No back trace, zilch.
I'm running stable AMD64, with the current hybrid KDE5-with-some-KDE4-apps (such as kdepim, digikam, etc.). Was working fine.
I recompiled digikam for debugging and started it with gdb. It gives:
| Code: | gdb digikam
GNU gdb (Gentoo 7.10.1 vanilla) 7.10.1
Copyright (C) 2015 Free Software Foundation, Inc.
...
This GDB was configured as "x86_64-pc-linux-gnu".
...
Reading symbols from digikam...done.
(gdb) run
Starting program: /usr/bin/digikam
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x00007fffe172e010 in QMetaObject::className() const () from /usr/lib64/libQt5Core.so.5
(gdb) bt
#0 0x00007fffe172e010 in QMetaObject::className() const () from /usr/lib64/libQt5Core.so.5
#1 0x00007fffe2040d2c in qRegisterWidgetsVariant() () from /usr/lib64/libQt5Widgets.so.5
#2 0x00007ffff7de962a in ?? () from /lib64/ld-linux-x86-64.so.2
#3 0x00007ffff7de97bd in ?? () from /lib64/ld-linux-x86-64.so.2
#4 0x00007ffff7ddac7a in ?? () from /lib64/ld-linux-x86-64.so.2
#5 0x0000000000000001 in ?? ()
#6 0x00007fffffffddba in ?? ()
#7 0x0000000000000000 in ?? ()
(gdb) |
My friend Google suggests this may be due to something not liking KDE5 libraries, though it was happy until recently.
A few version levels:
| Code: | media-gfx/digikam-4.4.0-r1
kde-apps/libkipi-16.04.3
dev-qt/qtcore-5.6.1
kde-apps/kdebase-meta-16.04.3 |
I assume something is missing or mis-configured. I'll be grateful for any suggestions.
FWIW, I tried upgrading to media-gfx/digikam-4.14.0-r1but it still segfaults.
media-gfx/digikam-5.1.0-r1 worked-ish, but didn't migrate tags etc. from the internal mysql database, and generally looked like a frightening upgrade prospect
_________________
Greybeard
Last edited by Goverp on Wed Oct 26, 2016 8:02 pm; edited 1 time in total |
|
| Back to top |
|
 |
Apheus
Guru
Joined: 12 Jul 2008
Posts: 418
|
| Posted: Sat Oct 22, 2016 1:52 pm Post subject: |
|
|
Should be fixed by now, if it is the same problem: media-libs/opencv needs to be compiled with qt4, not qt5:
https://bugs.gentoo.org/show_bug.cgi?id=595358
_________________
My phrenologist says I'm stupid. |
|
| Back to top |
|
|
asturm
Developer
Joined: 05 Apr 2007
Posts: 6829
Location: Austria
|
| Posted: Sat Oct 22, 2016 2:14 pm Post subject: |
|
|
Yes, that should be it.
digikam-5.3.0 at the end of October will come with another slew of fixes, including some migration stuff, so it will be a good candidate for stabilisation.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic |
|
| Back to top |
|
|
Goverp
l33t
Joined: 07 Mar 2007
Posts: 639
|
| Posted: Sun Oct 23, 2016 10:46 am Post subject: |
|
|
Thanks for the info guys, I'll give it a try.
_________________
Greybeard |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
