Version: 0.9.0 svn (using KDE KDE 3.5.2) Installed from: SuSE RPMs OS: Linux digikam crashes when in color->color management - click on the info-button in the workspace tab, when no profile is selected - trying to select a wrong profile (i.e. a input profile for workspace), to reproduce second case: marked "default" in input tab (EOS 10D linear@lysator.liu.se) marked "selected profile" in workspace tab, then select fuji1.icm (or another input device profile) click "Versuch"-button ("try?") I'll attach the messages from kde crash manager
Created attachment 16200 [details] crash manager messages after click "info" with no profile selected
Created attachment 16201 [details] crash manager text after selecting input profile for workspace
The backtrace from the crash manager hasn't any info, so it's useless. Maybe, you can get some feedback with: >gdb digikam >run . . . <crash> > bt In any case, I'm going to reproduce this bug. Paco
Not sure if my info helps anything, because it seems that I have not been able to make a correct svn install in addition to my existing 0.8.1. So the "bug" is maybe specific only to my "wrong install"... However, after the latest svn update: - "crash after click on the info-button in the workspace tab, when no profile is selected" seems solved now (a message "...there isn't any ... profile" appears, no crash anymore) - "crash after trying to select a wrong profile" still exists on my install: in "color management" I've chosen for input: "selected profile" (eos10d-linear-8apr2004.icc) for workspace: "selected profile" (EOS 10D.icc) click "Versuch": crash I'll send output of gdb as attachement. Daniel
Created attachment 16453 [details] console output of gdb digikam
El Sábado, 3 de Junio de 2006 19:11, Daniel Bauer escribió: [bugs.kde.org quoted mail] Don't worry Daniel, I've reproduced both of them. The first happened under some conditions, but now it's fixed (I think). Actually, I'm working to fix the second. Paco Cruz
This bug is going to be closed, as the SVN commit #554521 seems to fix it.
*** Bug has been marked as fixed ***.