[Digikam-devel] Showfoto crashes

[Laurent Rathle]

Hello,

Since yesterday evening checkout, Showfoto always crashes. Here is what I get
from gdb when I use it trought Digikam :

[New Thread -1265054800 (LWP 29707)]
digikam: Cannot parse EXIF metadata using Exiv2
kdeui (KDatePicker): KDatePicker::dateChangedSlot: date changed (2006/4/13).
digikam: enableCMSetting=false
digikam: /home/lolo/Documents/AlbumsPhotos/Atoova/Mes chiffres/99.jpg : JPEG
file identified

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1239230784 (LWP 29691)]
0xb7e9e029 in Digikam::DImgInterface::paintOnDevice (this=0x82e5520,
p=0x81e3ff0, sx=0, sy=0, sw=128,
    sh=128, dx=0, dy=0, dw=128, dh=128) at dimginterface.cpp:610
610         if (d->cmSettings->managedViewSetting)
Current language:  auto; currently c++

and standalone :

kio (KDirListerCache): [void KDirListerCache::forgetDirs(KDirLister*, const
KURL&, bool)] 0x83d56d8 item moved into cache: file:///home/lolo/Photos/Ter
showfoto: enableCMSetting=false
showfoto: /home/lolo/Photos/Ter/le_banc-r4.jpg : JPEG file identified

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1233246528 (LWP 29754)]
0x080f5f0d in ?? ()
Current language:  auto; currently c++

Digikam version is 0.9

Have a nice day,
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-2]

On Thursday 13 April 2006 10:01 am, Laurent Rathle wrote:

> Hello,
>
> Since yesterday evening checkout, Showfoto always crashes. Here is what I
> get from gdb when I use it trought Digikam :
>
> [New Thread -1265054800 (LWP 29707)]
> digikam: Cannot parse EXIF metadata using Exiv2
> kdeui (KDatePicker): KDatePicker::dateChangedSlot: date changed
> (2006/4/13). digikam: enableCMSetting=false
> digikam: /home/lolo/Documents/AlbumsPhotos/Atoova/Mes chiffres/99.jpg :
> JPEG file identified
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1239230784 (LWP 29691)]
> 0xb7e9e029 in Digikam::DImgInterface::paintOnDevice (this=0x82e5520,
> p=0x81e3ff0, sx=0, sy=0, sw=128,
>     sh=128, dx=0, dy=0, dw=128, dh=128) at dimginterface.cpp:610
> 610         if (d->cmSettings->managedViewSetting)
> Current language:  auto; currently c++
>
> and standalone :
>
> kio (KDirListerCache): [void KDirListerCache::forgetDirs(KDirLister*, const
> KURL&, bool)] 0x83d56d8 item moved into cache: file:///home/lolo/Photos/Ter
> showfoto: enableCMSetting=false
> showfoto: /home/lolo/Photos/Ter/le_banc-r4.jpg : JPEG file identified
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1233246528 (LWP 29754)]
> 0x080f5f0d in ?? ()
> Current language:  auto; currently c++
>
> Digikam version is 0.9
>
> Have a nice day,

This is releavant of the screen icc color correction that i have commited
yesterday night. Something is certainly wrong.

To solve it temporally, please unset "Use Colormanaged view" option from setup
icc page.

To investiguate this crash, have you set an icc Monitor profile in setup icc
page ?

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-2]

On Thursday 13 April 2006 12:21 pm, Gilles Caulier wrote:
> To investiguate this crash, have you set an icc Monitor profile in setup
> icc page ?

Laurent,

I have add a test to render image without process icc color correction on the
screen if icc profile name is null. Please checkout and try again to enable
"Use Colormanaged view" option.

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Laurent Rathle]

Le Jeudi 13 Avril 2006 12:21, Gilles Caulier a écrit :
> This is releavant of the screen icc color correction that i have commited
> yesterday night. Something is certainly wrong.
>
> To solve it temporally, please unset "Use Colormanaged view" option from
> setup icc page.
>
> To investiguate this crash, have you set an icc Monitor profile in setup
> icc page ?

In fact Color Management was not even enabled... :-). I've enabled it and no
more crash. I didd'nt set any Monitor profile. But now that I have enabled
Color Management, when I want to go in the configuration panel, I get a
message saying "You must set a default path to color profiles files" before
the windows open. And I can't change any settings of Digikam. I just have the
cancel button activated.

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-2]

On Thursday 13 April 2006 12:46 pm, Laurent Rathle wrote:

> Le Jeudi 13 Avril 2006 12:21, Gilles Caulier a écrit :
> > This is releavant of the screen icc color correction that i have commited
> > yesterday night. Something is certainly wrong.
> >
> > To solve it temporally, please unset "Use Colormanaged view" option from
> > setup icc page.
> >
> > To investiguate this crash, have you set an icc Monitor profile in setup
> > icc page ?
>
> In fact Color Management was not even enabled... :-). I've enabled it and
> no more crash. I didd'nt set any Monitor profile. But now that I have
> enabled Color Management,

ok. i can reproduce it without enable ICC management. I will fix it.

> when I want to go in the configuration panel, I
> get a message saying "You must set a default path to color profiles files"
> before the windows open. And I can't change any settings of Digikam. I just
> have the cancel button activated.
>

If you want to use ICC color management, you need ICC profile files. You can
take some files from digiKam repository :

http://digikam3rdparty.free.fr/ICCPROFILES/

This folders isn't yet sorted properly. Also all contributions welcome to add
other camera profiles at this place.

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-2]

On Thursday 13 April 2006 12:46 pm, Laurent Rathle wrote:

> Le Jeudi 13 Avril 2006 12:21, Gilles Caulier a écrit :
> > This is releavant of the screen icc color correction that i have commited
> > yesterday night. Something is certainly wrong.
> >
> > To solve it temporally, please unset "Use Colormanaged view" option from
> > setup icc page.
> >
> > To investiguate this crash, have you set an icc Monitor profile in setup
> > icc page ?
>
> In fact Color Management was not even enabled... :-). I've enabled it and
> no more crash. I didd'nt set any Monitor profile. But now that I have
> enabled Color Management, when I want to go in the configuration panel, I
> get a message saying "You must set a default path to color profiles files"
> before the windows open. And I can't change any settings of Digikam. I just
> have the cancel button activated.
>

OK. implementation cleanup. checkout svn and try again. Thanks in advance

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Laurent Rathle]

Le Jeudi 13 Avril 2006 12:54, Gilles Caulier a écrit :
> If you want to use ICC color management, you need ICC profile files. You
> can take some files from digiKam repository :
>
> http://digikam3rdparty.free.fr/ICCPROFILES/
>
> This folders isn't yet sorted properly. Also all contributions welcome to
> add other camera profiles at this place.

I've taken Nikon D70 profile and put it in a folder. I've choosen this folder
in the setup dialog. The first time was ok until I tried to click on a Info
button. It crashed. From then, I can't even enter a path for the profiles.
Digikam crashes when I click on the OK button of the folder choice dialog.

kio (KDirListerCache): [void KDirListerCache::forgetDirs(KDirLister*, const
KURL&, bool)] 0x860a910 item moved into cache:
file:///home/lolo/Documents/Nikon_D70/Profils
ASSERT: "it.node != node" in /usr/lib/qt3//include/qvaluelist.h (301)
ASSERT: "it.node != node" in /usr/lib/qt3//include/qvaluelist.h (301)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1239484736 (LWP 4493)]
0xb625cf91 in malloc_usable_size () from /lib/tls/libc.so.6
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Laurent Rathle]

Le Jeudi 13 Avril 2006 13:17, Gilles Caulier a écrit :
> OK. implementation cleanup. checkout svn and try again. Thanks in advance

OK
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Laurent Rathle]

Le Jeudi 13 Avril 2006 13:28, Laurent Rathle a écrit :
> > OK. implementation cleanup. checkout svn and try again. Thanks in advance
>
> OK

I always can't select the profiles folder... Digikam crashes.

Using host libthread_db library "/lib/tls/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its symbols.
0xffffe410 in __kernel_vsyscall ()
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6285790 in ?? ()
#2  0xb62855df in ?? ()
#3  0xbfb4d5a0 in ?? ()
#4  0xbfb4d5a0 in ?? ()
#5  0x00000000 in ?? ()

sur la ligne de commande :

ASSERT: "it.node != node" in /usr/lib/qt3//include/qvaluelist.h (301)
ASSERT: "it.node != node" in /usr/lib/qt3//include/qvaluelist.h (301)
ASSERT: "it.node != node" in /usr/lib/qt3//include/qvaluelist.h (301)
ASSERT: "it.node != node" in /usr/lib/qt3//include/qvaluelist.h (301)
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = digikam path = <unknown> pid = 24266
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-2]

On Thursday 13 April 2006 01:40 pm, Laurent Rathle wrote:

> Le Jeudi 13 Avril 2006 13:28, Laurent Rathle a écrit :
> > > OK. implementation cleanup. checkout svn and try again. Thanks in
> > > advance
> >
> > OK
>
> I always can't select the profiles folder... Digikam crashes.
>
> Using host libthread_db library "/lib/tls/libthread_db.so.1".
> `shared object read from target memory' has disappeared; keeping its
> symbols. 0xffffe410 in __kernel_vsyscall ()
> #0  0xffffe410 in __kernel_vsyscall ()
> #1  0xb6285790 in ?? ()
> #2  0xb62855df in ?? ()
> #3  0xbfb4d5a0 in ?? ()
> #4  0xbfb4d5a0 in ?? ()
> #5  0x00000000 in ?? ()
>
> sur la ligne de commande :
>
> ASSERT: "it.node != node" in /usr/lib/qt3//include/qvaluelist.h (301)
> ASSERT: "it.node != node" in /usr/lib/qt3//include/qvaluelist.h (301)
> ASSERT: "it.node != node" in /usr/lib/qt3//include/qvaluelist.h (301)
> ASSERT: "it.node != node" in /usr/lib/qt3//include/qvaluelist.h (301)
> KCrash: crashing... crashRecursionCounter = 2
> KCrash: Application Name = digikam path = <unknown> pid = 24266

My fixed are donr in image editor core, not setup dialog implementation.

Your crash sounds like whenyou have set only 1 icc profile file (camera ?)
from setup icc dialog page. Right ?

Here on my computer all icc profile file are set because i use all the content
of the digikam profile repository. This is why i don't have a crash.

I will polish icc setup dialog page implementation. But you can test the rest
of image editor core to set all profile file name properlly. We will re-test
setup page later when i will fixed implementation. Let's me anytime (:=))))

Also, read all widget tips avaialble in setup icc dialog if you want learn
more about icc color management. The handbook isn't yet updated about this
part.

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Laurent Rathle]

Le Jeudi 13 Avril 2006 13:45, Gilles Caulier a écrit :
> Also, read all widget tips avaialble in setup icc dialog if you want learn
> more about icc color management. The handbook isn't yet updated about this
> part.

Ok, I'll read all that :-)
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-2]

Le Jeudi 13 Avril 2006 14:05, Laurent Rathle a écrit :
> Le Jeudi 13 Avril 2006 13:45, Gilles Caulier a écrit :
> > Also, read all widget tips avaialble in setup icc dialog if you want
> > learn more about icc color management. The handbook isn't yet updated
> > about this part.
>
> Ok, I'll read all that :-)

There is an indeep bug in Setup icc dialog page. I will trying to fix it
tomorrow.

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-2]

Le Jeudi 13 Avril 2006 18:44, Gilles Caulier a écrit :

> Le Jeudi 13 Avril 2006 14:05, Laurent Rathle a écrit :
> > Le Jeudi 13 Avril 2006 13:45, Gilles Caulier a écrit :
> > > Also, read all widget tips avaialble in setup icc dialog if you want
> > > learn more about icc color management. The handbook isn't yet updated
> > > about this part.
> >
> > Ok, I'll read all that :-)
>
> There is an indeep bug in Setup icc dialog page. I will trying to fix it
> tomorrow.

Laurent, all Setup icc dialog page internal rules have been re-written. I have
tested indeep this implementation. Please, checkout svn and give me a
feedback. Thanks in advance

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel