Version: 0.9.0-beta1 (using KDE 3.5.4 "release 62.1" , openSUSE ) Compiler: Target: i586-suse-linux OS: Linux (i686) release 2.6.16.21-0.13-default Using 0.9.0beta1: Choosing an image / icon for a tag consistently crashes Digikam. To reproduce: 1. Create a new tag, (or choose existent tag and Right-Click > Edit Tag). 2. Choose and icon and press EITHER "OK" OR "CANCEL" 3. Crash and the following message ========= Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1239468368 (LWP 16225)] [KCrash handler] #6 0x080502cd in ?? () =========
There is no suitable backtrace into your report. Please compile digiKam using "./configure --enable-debug=full" and running digiKam under "gdb". Gilles Caulier
Downgraded DigiKam to 8.2 - same issue. This did not occure with DigiKam 8.2 prior a recent OpenSuse update. There are also other "icon-set-related" issues in the latest KDE packages for OpenSuse. Will file a bug there and get back to you if this turns out DigiKam-related.
It is very likely related to this: https://bugzilla.novell.com/show_bug.cgi?id=205535 http://bugs.kde.org/show_bug.cgi?id=133976
CHANGES: Upgraded to Digikam 0.9.0-beta2 from http://software.opensuse.org/download/repositories/KDE:/Playground/SUSE_Linux_10.1/i586/ Still, same OpenSuSE 10.1 with latest KDE packages from http://software.opensuse.org/download/repositories/KDE:/KDE3/SUSE_Linux_10.1/ other icon-related issues discussed in https://bugzilla.novell.com/show_bug.cgi?id=205535 http://bugs.kde.org/show_bug.cgi?id=133976 are resolved but DIGIKAM PROBLEM REMAINS DEBUG OUTPUT: Running gdb /opt/kde3/bin/digikam produces the following: (this is a second run from gdb, 1st run took several minutes to figure out what gdb is) (gdb) run The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /opt/kde3/bin/digikam [Thread debugging using libthread_db enabled] [New Thread -1239128400 (LWP 15914)] [New Thread -1242199136 (LWP 15915)] [New Thread -1250591840 (LWP 15916)] [Thread -1242199136 (LWP 15915) exited] [Thread -1250591840 (LWP 15916) exited] QInputContext: cannot create input context for non-toplevel widgets QInputContext: cannot create input context for non-toplevel widgets Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1239128400 (LWP 15914)] 0x080502c8 in ?? () (gdb) cont Continuing. KCrash: Application 'digikam' crashing... Program exited with code 0375. This is KDE Crash window output from running digikam from console: Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1238964560 (LWP 15934)] [KCrash handler] #6 0x080502c8 in ?? () #7 0x080502c8 in ?? () #8 0x0847f3d8 in ?? () #9 0x00000020 in ?? () #10 0x00000031 in ?? () #11 0x00000002 in ?? () #12 0x00000060 in ?? () #13 0x00000060 in ?? () #14 0x00000018 in ?? () #15 0x0000062b in ?? () #16 0x08468a98 in ?? () #17 0x00000000 in ?? () This is the stuff in console: dd@kasper:~> digikam QInputContext: cannot create input context for non-toplevel widgets QInputContext: cannot create input context for non-toplevel widgets KCrash: Application 'digikam' crashing... dd@kasper:~> DISCUSSION: Choosing icons for shortcuts and in other places in KDE works fine. In digicam, the crash occurs after I choose the icon in the dialog, REGARDLES of if I press "OK" or "Cancel"
digikam crashes for me when I select the icon from the browser for system icons, (don't even have to pick OK or cancel. Fedora Core 5, digikam 0.8.2, KDE 3.5.4-0.3.fc5
Filed a report with Novell. It contains more information about versions of DigiKam affected and steps to replicate the problem. https://bugzilla.novell.com/show_bug.cgi?id=211147
(From bugreport on bugzilla.novell) NO, 3.5.5 DOESN'T HELP: Upgraded to KDE 3.5.5 release 19.5. The problem remains with all: DigiKam v 9b2, 8.2 from back ports, 8.1 from the original OpenSuSe 10.1 DVD. This bug affects both of my computers: one with OpenSuse continuously upgraded from 10.1 beta times, the other with OpenSuse 10.1 final DVD installed in mid September and both updated from the same sources as described above. Both exhibit the bug. The problem started on both of them at the same time. The only major difference between you and me: I run OpenSuse 10.1 with Suse's updates for it + KDE from backports et all, NOT FACTORY. Again. the problem only affects digikam's "choose icon" window. Choosing icons in other places in KDE is fine. NEXT STEPS: This is probably beyond KDE. The persistence of the problem despite kde and digikam version change shows it's somewhere deeper in libs, or something. There were a few other, non-kde packages updated right before the bug surfaced... ImageMagic, or, something like that.. None of the digikam versions available seem to produce the "proper" bug report. Could you recommend compile options and set up so I can try to compile digiKam myself and try to get a more sensible crash report out of it?
Daniel, I'm use digikam & co on 2 computers (home + office) under suse 10.1 without problem. Gilles
I'm use digikam & co on 2 computers (home + office) under suse 10.1 without problem. Gilles Gilles, can you tell what version of KDE you are running? Also, what was the last time you updated your suse 10.1? I was also running it fine with Suse 10.1, until mid-september updates of system and KDE.
KDE 3.5.1 without major system update, (only security update). Gilles
I'm running Debian testing/unstable, with KDE 3.5.5a packages. With both 0.8.2 and 0.9.0beta2, I have this problem. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393505
Tested with digikam 0.9 beta 3 (OpenSuse 10.1, KDE 3.5.5 "Release 19.1") Problem IS still PRESENT. I am still unable to get a more meaningfull bug report out of the crash.. :( Changing icons in the rest of KDE is still fine. Can someone suggest compile options for digiKam to ensure that it gives enough info upon crash?
This is fixed in Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393505 Though I can't tell from the changelog if the patch is included in upstream, so I don't know if this can be closed yet here.
Tested with Digikam 0.9.0 Beta 3, on KDE 3.5.5 ("release 39.1" OpenSuse) Problem is still there, but there is new, exciting error: Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1239165264 (LWP 16315)] [KCrash handler] #5 0x080503e8 in ?? () #6 0x080503e8 in ?? () #7 0x085422f0 in ?? () #8 0x00000020 in ?? () #9 0x00000019 in ?? () #10 0x08137f70 in ?? () #11 0x00000031 in ?? () #12 0xb72cb6ae in typeinfo name for QPtrList<QButtonItem> () from /usr/lib/qt3/lib/libqt-mt.so.3 #13 0x00000001 in ?? () #14 0x00000000 in ?? ()
This problem must be fixed before 0.9.0-final release Gilles Caulier
Checking in Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393505 The diff file relevant do not contain a fix in digiKam source code. Question: how Debian team have fixed this bug ? Achim ? Gilles
Also, to have checked with valgrind, I have only see this warning : ==3845== Conditional jump or move depends on uninitialised value(s) ==3845== at 0x1CDB6C4F: QIconView::showEvent(QShowEvent*) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.4) Witch is relevant of Qt library. Gilles
Someone can try to run digiKam under valgrind like it explained at end of HACKING file and report me all messages form the console. Thanks in advance. Gilles
*** Bug 142984 has been marked as a duplicate of this bug. ***
I have built and installed Digikam 0.9.1 from source from digikam.org on Debian testing/unstable, and I don't seem to have this problem.
I check the problem as described in #0, and do not observe any crash with current svn under debian etch. Daniel, could you maybe give it another try (either with svn or 0.9.2.beta3) to see if the problem persists for you? Maybe we are lucky and this can be closed...
Closing this bug now. This does not mean it is invalid by itself, but the positive reports suggest, that the problem is solved Please feel free to re-open if there is any new information. Thanks a lot for your understanding, Arnd