Version: 0.9.2-final (using KDE 3.5.8) Installed from: Fedora RPMs OS: Linux Reproduce: I open the program. It has already albums in there which I have added. I choose first album and what ever picture with right mouse button and choose "add to light table". Then "Light table" opens as it should. I have two same pictures there. Then choose "colours" from the left side tab. It open a menu which has the first option something like "Channel" (I have finnish version so not usre about the names in english sry). When choosing from channel the first option "Brigthness" or any other (I think its brightness in english but it could be lightness too) digikam just crashes.
Tapani, Can you give us a GDB backtrace to hack source code at the right place ? Thanks in advance Gilles Caulier
Created attachment 23247 [details] KCrash report The report which is given by FC8 KCrash.It also says that it gave signal 11 (SIGSEGV).
here is no debug symbol in you digiKam installation. Backtrace is not really suitable I recommend : - to install debug package of 0.9.2 - if you can install 0.9.3 and try to reproduce the problem. - if problem still exist, checkout code from svn, recompile with full debug info, and give us a full backtrace. Thanks in advance Gilles Caulier
It seems to be that I misinformed you a bit earlier. I had Fedora Core 7. And there wasnt digikam version 0.9.3 rpm for it. So I installed FC8 with 0.9.3 digikam in it. Now it works perfectly. The problem seems to be in older FC7 version with digikam 0.9.2 version. That was the newest version of digikam which came from the fedora repositories for FC7 when tried to update digikam. So the problem might still be on FC7 with digikam 0.9.2 but I cant say it for sure ATM. My config was modified FC7 so the problem might just be only in my computer. Sincererly Tapani Mikkola
Tapani, Are you tried 0.9.3 release on your computer ? Gilles Caulier
Closing this bug now. I could not reproduce it. Without updated information (with full debug gdb backtrace) using the current 0.9.3 version (or current svn) it is not possible to find the root of the problem. Please feel free to re-open if there is any new information. Thanks a lot for your understanding, Arnd