Crash in directory browsing (0.9 svn)

[Duncan Hill-2]

URL: svn://anonsvn.kde.org/home/kde/trunk/extragear/graphics/digikam
Repository UUID: 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
Revision: 556535

Steps to reproduce:

Take 1 KM 5D, and shoot a bunch of raw photos.
Mount the CF card for directory browse
Download All using subdirs by date
Delete All
Close.

Digikam crashes on close.

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1240258336 (LWP 5413)]
[KCrash handler]
#6  0x0804ae11 in QValueListIterator<QString>::operator++ (this=0xbfcdd064)
    at qvaluelist.h:121
#7  0x0804aee1 in QValueListPrivate (this=0xb3851f10, _p=@0x83e00b8)
    at qvaluelist.h:272
#8  0x0804af6e in QValueList<QString>::detachInternal (this=0x8321388)
    at qvaluelist.h:631
#9  0x0804af99 in QValueList<QString>::detach (this=0x8321388)
    at qvaluelist.h:562
#10 0x0804afaf in QValueList<QString>::end (this=0x8321388)
    at qvaluelist.h:477
#11 0xb7eb0af7 in Digikam::CameraUI::dialogClosed (this=0x8756918)
    at cameraui.cpp:507
#12 0xb7eb0b9c in Digikam::CameraUI::slotClose (this=0x8756918)
    at cameraui.cpp:469
#13 0xb739f4f2 in KDialogBase::qt_invoke () from /usr/lib/libkdeui.so.4
#14 0xb7eb27c0 in Digikam::CameraUI::qt_invoke (this=0x8756918, _id=80,
    _o=0xbfcdd25c) at cameraui.moc:239
#15 0xb69f3eb9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#16 0xb69f4954 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#17 0xb6d8fd1f in QButton::clicked () from /usr/lib/libqt-mt.so.3
#18 0xb6a8f55e in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3
#19 0xb6a2e68d in QWidget::event () from /usr/lib/libqt-mt.so.3
#20 0xb6989e56 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#21 0xb698a3e0 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#22 0xb711ed7d in KApplication::notify () from /usr/lib/libkdecore.so.4
#23 0xb691b1c5 in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#24 0xb6916873 in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#25 0xb6914d59 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#26 0xb692e4db in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#27 0xb69a2947 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#28 0xb69a286a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#29 0xb6988965 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#30 0x0804a9d1 in main (argc=7, argv=0xbfcddec4) at main.cpp:273
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-2]

Try this patch and give me a feedback. Thanks in advance...



On Monday 03 July 2006 08:32, Duncan Hill wrote:

> URL: svn://anonsvn.kde.org/home/kde/trunk/extragear/graphics/digikam
> Repository UUID: 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
> Revision: 556535
>
> Steps to reproduce:
>
> Take 1 KM 5D, and shoot a bunch of raw photos.
> Mount the CF card for directory browse
> Download All using subdirs by date
> Delete All
> Close.
>
> Digikam crashes on close.
>
> Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
> [Thread debugging using libthread_db enabled]
> [New Thread -1240258336 (LWP 5413)]
> [KCrash handler]
> #6  0x0804ae11 in QValueListIterator<QString>::operator++ (this=0xbfcdd064)
>     at qvaluelist.h:121
> #7  0x0804aee1 in QValueListPrivate (this=0xb3851f10, _p=@0x83e00b8)
>     at qvaluelist.h:272
> #8  0x0804af6e in QValueList<QString>::detachInternal (this=0x8321388)
>     at qvaluelist.h:631
> #9  0x0804af99 in QValueList<QString>::detach (this=0x8321388)
>     at qvaluelist.h:562
> #10 0x0804afaf in QValueList<QString>::end (this=0x8321388)
>     at qvaluelist.h:477
> #11 0xb7eb0af7 in Digikam::CameraUI::dialogClosed (this=0x8756918)
>     at cameraui.cpp:507
> #12 0xb7eb0b9c in Digikam::CameraUI::slotClose (this=0x8756918)
>     at cameraui.cpp:469
> #13 0xb739f4f2 in KDialogBase::qt_invoke () from /usr/lib/libkdeui.so.4
> #14 0xb7eb27c0 in Digikam::CameraUI::qt_invoke (this=0x8756918, _id=80,
>     _o=0xbfcdd25c) at cameraui.moc:239
> #15 0xb69f3eb9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
> #16 0xb69f4954 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
> #17 0xb6d8fd1f in QButton::clicked () from /usr/lib/libqt-mt.so.3
> #18 0xb6a8f55e in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3
> #19 0xb6a2e68d in QWidget::event () from /usr/lib/libqt-mt.so.3
> #20 0xb6989e56 in QApplication::internalNotify () from
> /usr/lib/libqt-mt.so.3 #21 0xb698a3e0 in QApplication::notify () from
> /usr/lib/libqt-mt.so.3 #22 0xb711ed7d in KApplication::notify () from
> /usr/lib/libkdecore.so.4 #23 0xb691b1c5 in
> QApplication::sendSpontaneousEvent ()
>    from /usr/lib/libqt-mt.so.3
> #24 0xb6916873 in QETWidget::translateMouseEvent ()
>    from /usr/lib/libqt-mt.so.3
> #25 0xb6914d59 in QApplication::x11ProcessEvent () from
> /usr/lib/libqt-mt.so.3 #26 0xb692e4db in QEventLoop::processEvents () from
> /usr/lib/libqt-mt.so.3 #27 0xb69a2947 in QEventLoop::enterLoop () from
> /usr/lib/libqt-mt.so.3 #28 0xb69a286a in QEventLoop::exec () from
> /usr/lib/libqt-mt.so.3
> #29 0xb6988965 in QApplication::exec () from /usr/lib/libqt-mt.so.3
> #30 0x0804a9d1 in main (argc=7, argv=0xbfcddec4) at main.cpp:273
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

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

[Duncan Hill-5]

On Monday 03 July 2006 07:56, Gilles Caulier wrote:
> Try this patch and give me a feedback. Thanks in advance...

I'm not sure if the patch, or the svn update caused this:
digikam: Dirty: /
digikam: Dirty: /2006
digikam: Exif autorotate: pict5339.mrw using
(/home/dhill/Images/2006/2006-07-04/.digikam-camera-28184)
digikam: ExifRotate: not a JPEG
file: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184
Warning: Size 5396 of Exif.Minolta.0x0020 exceeds 4096 bytes limit. Not
decoded.
digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==> Author:
Duncan Hill
digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==> Author
Title: Mr
digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==> Credit:
digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==> Source:
digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==>
Copyright: Duncan Hill
KCrash: Application 'digikam' crashing...
QSocketNotifier: invalid socket 20 and type 'Read', disabling...
QSocketNotifier: invalid socket 18 and type 'Read', disabling...
QSocketNotifier: invalid socket 15 and type 'Read', disabling...
QSocketNotifier: invalid socket 12 and type 'Read', disabling...
QSocketNotifier: invalid socket 7 and type 'Read', disabling...
QSocketNotifier: invalid socket 19 and type 'Read', disabling...
QSocketNotifier: invalid socket 13 and type 'Read', disabling...
QSocketNotifier: invalid socket 4 and type 'Read', disabling...
QSocketNotifier: invalid socket 16 and type 'Read', disabling...
QSocketNotifier: invalid socket 9 and type 'Read', disabling...
digikam: Fatal IO error: client killed

URL: svn://anonsvn.kde.org/home/kde/trunk/extragear/graphics/digikam
Repository Root: svn://anonsvn.kde.org/home/kde
Repository UUID: 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
Revision: 558379

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1241184032 (LWP 28184)]
[New Thread -1250796624 (LWP 28209)]
0xb68ae696 in QPtrList<QPostEvent>::current () from /usr/lib/libqt-mt.so.3
#0  0xb68ae696 in QPtrList<QPostEvent>::current () from /usr/lib/libqt-mt.so.3
#1  0xb68a9554 in QApplication::sendPostedEvents ()
   from /usr/lib/libqt-mt.so.3
#2  0xb68a95ae in QApplication::sendPostedEvents ()
   from /usr/lib/libqt-mt.so.3
#3  0xb684c42b in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#4  0xb68c0947 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#5  0xb68c086a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#6  0xb68a6965 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#7  0x0804aacd in main (argc=1, argv=0xbfc088f4) at main.cpp:273
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-2]

No this is not the patch.

This crash appear during downloading with exif autorotate using Exiv2. Are you
sure to have only one Exiv2 version installed on your computer ? Do not mix
old and new released (including current svn).

Gilles


On Wednesday 05 July 2006 12:12, Duncan Hill wrote:

> On Monday 03 July 2006 07:56, Gilles Caulier wrote:
> > Try this patch and give me a feedback. Thanks in advance...
>
> I'm not sure if the patch, or the svn update caused this:
> digikam: Dirty: /
> digikam: Dirty: /2006
> digikam: Exif autorotate: pict5339.mrw using
> (/home/dhill/Images/2006/2006-07-04/.digikam-camera-28184)
> digikam: ExifRotate: not a JPEG
> file: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184
> Warning: Size 5396 of Exif.Minolta.0x0020 exceeds 4096 bytes limit. Not
> decoded.
> digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==>
> Author: Duncan Hill
> digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==>
> Author Title: Mr
> digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==>
> Credit: digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184
> ==> Source: digikam:
> /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==> Copyright:
> Duncan Hill
> KCrash: Application 'digikam' crashing...
> QSocketNotifier: invalid socket 20 and type 'Read', disabling...
> QSocketNotifier: invalid socket 18 and type 'Read', disabling...
> QSocketNotifier: invalid socket 15 and type 'Read', disabling...
> QSocketNotifier: invalid socket 12 and type 'Read', disabling...
> QSocketNotifier: invalid socket 7 and type 'Read', disabling...
> QSocketNotifier: invalid socket 19 and type 'Read', disabling...
> QSocketNotifier: invalid socket 13 and type 'Read', disabling...
> QSocketNotifier: invalid socket 4 and type 'Read', disabling...
> QSocketNotifier: invalid socket 16 and type 'Read', disabling...
> QSocketNotifier: invalid socket 9 and type 'Read', disabling...
> digikam: Fatal IO error: client killed
>
> URL: svn://anonsvn.kde.org/home/kde/trunk/extragear/graphics/digikam
> Repository Root: svn://anonsvn.kde.org/home/kde
> Repository UUID: 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
> Revision: 558379
>
> Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
> [Thread debugging using libthread_db enabled]
> [New Thread -1241184032 (LWP 28184)]
> [New Thread -1250796624 (LWP 28209)]
> 0xb68ae696 in QPtrList<QPostEvent>::current () from /usr/lib/libqt-mt.so.3
> #0  0xb68ae696 in QPtrList<QPostEvent>::current () from
> /usr/lib/libqt-mt.so.3 #1  0xb68a9554 in QApplication::sendPostedEvents ()
>    from /usr/lib/libqt-mt.so.3
> #2  0xb68a95ae in QApplication::sendPostedEvents ()
>    from /usr/lib/libqt-mt.so.3
> #3  0xb684c42b in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
> #4  0xb68c0947 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
> #5  0xb68c086a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
> #6  0xb68a6965 in QApplication::exec () from /usr/lib/libqt-mt.so.3
> #7  0x0804aacd in main (argc=1, argv=0xbfc088f4) at main.cpp:273
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

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

[Gilles Caulier-2]

Ah, forget to said that i cannot reproduce this crash when i want to download
my MRW files from my Dynax 5D (and i download a lot of pictures reguliary
(:=)))...

Gilles


On Wednesday 05 July 2006 12:12, Duncan Hill wrote:

> On Monday 03 July 2006 07:56, Gilles Caulier wrote:
> > Try this patch and give me a feedback. Thanks in advance...
>
> I'm not sure if the patch, or the svn update caused this:
> digikam: Dirty: /
> digikam: Dirty: /2006
> digikam: Exif autorotate: pict5339.mrw using
> (/home/dhill/Images/2006/2006-07-04/.digikam-camera-28184)
> digikam: ExifRotate: not a JPEG
> file: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184
> Warning: Size 5396 of Exif.Minolta.0x0020 exceeds 4096 bytes limit. Not
> decoded.
> digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==>
> Author: Duncan Hill
> digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==>
> Author Title: Mr
> digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==>
> Credit: digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184
> ==> Source: digikam:
> /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==> Copyright:
> Duncan Hill
> KCrash: Application 'digikam' crashing...
> QSocketNotifier: invalid socket 20 and type 'Read', disabling...
> QSocketNotifier: invalid socket 18 and type 'Read', disabling...
> QSocketNotifier: invalid socket 15 and type 'Read', disabling...
> QSocketNotifier: invalid socket 12 and type 'Read', disabling...
> QSocketNotifier: invalid socket 7 and type 'Read', disabling...
> QSocketNotifier: invalid socket 19 and type 'Read', disabling...
> QSocketNotifier: invalid socket 13 and type 'Read', disabling...
> QSocketNotifier: invalid socket 4 and type 'Read', disabling...
> QSocketNotifier: invalid socket 16 and type 'Read', disabling...
> QSocketNotifier: invalid socket 9 and type 'Read', disabling...
> digikam: Fatal IO error: client killed
>
> URL: svn://anonsvn.kde.org/home/kde/trunk/extragear/graphics/digikam
> Repository Root: svn://anonsvn.kde.org/home/kde
> Repository UUID: 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
> Revision: 558379
>
> Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
> [Thread debugging using libthread_db enabled]
> [New Thread -1241184032 (LWP 28184)]
> [New Thread -1250796624 (LWP 28209)]
> 0xb68ae696 in QPtrList<QPostEvent>::current () from /usr/lib/libqt-mt.so.3
> #0  0xb68ae696 in QPtrList<QPostEvent>::current () from
> /usr/lib/libqt-mt.so.3 #1  0xb68a9554 in QApplication::sendPostedEvents ()
>    from /usr/lib/libqt-mt.so.3
> #2  0xb68a95ae in QApplication::sendPostedEvents ()
>    from /usr/lib/libqt-mt.so.3
> #3  0xb684c42b in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
> #4  0xb68c0947 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
> #5  0xb68c086a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
> #6  0xb68a6965 in QApplication::exec () from /usr/lib/libqt-mt.so.3
> #7  0x0804aacd in main (argc=1, argv=0xbfc088f4) at main.cpp:273
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

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

[Teudimundo]

I have the same problem.. with a Dynax 5D and MRW as well. I download
through a mounted dir (the CF in the card reader), then when I close the
download window digikam crashes.. I will send more infos as soon as
possible.

--Tommaso

Gilles Caulier wrote:

>Ah, forget to said that i cannot reproduce this crash when i want to download
>my MRW files from my Dynax 5D (and i download a lot of pictures reguliary
>(:=)))...
>
>Gilles
>
>
>On Wednesday 05 July 2006 12:12, Duncan Hill wrote:
>  
>
>>On Monday 03 July 2006 07:56, Gilles Caulier wrote:
>>    
>>
>>>Try this patch and give me a feedback. Thanks in advance...
>>>      
>>>
>>I'm not sure if the patch, or the svn update caused this:
>>digikam: Dirty: /
>>digikam: Dirty: /2006
>>digikam: Exif autorotate: pict5339.mrw using
>>(/home/dhill/Images/2006/2006-07-04/.digikam-camera-28184)
>>digikam: ExifRotate: not a JPEG
>>file: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184
>>Warning: Size 5396 of Exif.Minolta.0x0020 exceeds 4096 bytes limit. Not
>>decoded.
>>digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==>
>>Author: Duncan Hill
>>digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==>
>>Author Title: Mr
>>digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==>
>>Credit: digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184
>>==> Source: digikam:
>>/home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==> Copyright:
>>Duncan Hill
>>KCrash: Application 'digikam' crashing...
>>QSocketNotifier: invalid socket 20 and type 'Read', disabling...
>>QSocketNotifier: invalid socket 18 and type 'Read', disabling...
>>QSocketNotifier: invalid socket 15 and type 'Read', disabling...
>>QSocketNotifier: invalid socket 12 and type 'Read', disabling...
>>QSocketNotifier: invalid socket 7 and type 'Read', disabling...
>>QSocketNotifier: invalid socket 19 and type 'Read', disabling...
>>QSocketNotifier: invalid socket 13 and type 'Read', disabling...
>>QSocketNotifier: invalid socket 4 and type 'Read', disabling...
>>QSocketNotifier: invalid socket 16 and type 'Read', disabling...
>>QSocketNotifier: invalid socket 9 and type 'Read', disabling...
>>digikam: Fatal IO error: client killed
>>
>>URL: svn://anonsvn.kde.org/home/kde/trunk/extragear/graphics/digikam
>>Repository Root: svn://anonsvn.kde.org/home/kde
>>Repository UUID: 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
>>Revision: 558379
>>
>>Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
>>[Thread debugging using libthread_db enabled]
>>[New Thread -1241184032 (LWP 28184)]
>>[New Thread -1250796624 (LWP 28209)]
>>0xb68ae696 in QPtrList<QPostEvent>::current () from /usr/lib/libqt-mt.so.3
>>#0  0xb68ae696 in QPtrList<QPostEvent>::current () from
>>/usr/lib/libqt-mt.so.3 #1  0xb68a9554 in QApplication::sendPostedEvents ()
>>   from /usr/lib/libqt-mt.so.3
>>#2  0xb68a95ae in QApplication::sendPostedEvents ()
>>   from /usr/lib/libqt-mt.so.3
>>#3  0xb684c42b in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
>>#4  0xb68c0947 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
>>#5  0xb68c086a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
>>#6  0xb68a6965 in QApplication::exec () from /usr/lib/libqt-mt.so.3
>>#7  0x0804aacd in main (argc=1, argv=0xbfc088f4) at main.cpp:273
>>_______________________________________________
>>Digikam-users mailing list
>>[hidden email]
>>https://mail.kde.org/mailman/listinfo/digikam-users
>>    
>>
>_______________________________________________
>Digikam-users mailing list
>[hidden email]
>https://mail.kde.org/mailman/listinfo/digikam-users
>
>  
>

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

[Gilles Caulier-2]

On Wednesday 05 July 2006 12:54, Tommaso Schiavinotto wrote:
> I have the same problem.. with a Dynax 5D and MRW as well. I download
> through a mounted dir (the CF in the card reader), then when I close the
> download window digikam crashes.. I will send more infos as soon as
> possible.

Warning, there is two crash reported by Duncan :

- one when camera dialog is closed (i can reproduce it sometimes).
- one during download when auto-rotation is enable (not reproductible here)

Gilles

>
> --Tommaso
>
> Gilles Caulier wrote:
> >Ah, forget to said that i cannot reproduce this crash when i want to
> > download my MRW files from my Dynax 5D (and i download a lot of pictures
> > reguliary (:=)))...
> >
> >Gilles
> >
> >On Wednesday 05 July 2006 12:12, Duncan Hill wrote:
> >>On Monday 03 July 2006 07:56, Gilles Caulier wrote:
> >>>Try this patch and give me a feedback. Thanks in advance...
> >>
> >>I'm not sure if the patch, or the svn update caused this:
> >>digikam: Dirty: /
> >>digikam: Dirty: /2006
> >>digikam: Exif autorotate: pict5339.mrw using
> >>(/home/dhill/Images/2006/2006-07-04/.digikam-camera-28184)
> >>digikam: ExifRotate: not a JPEG
> >>file: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184
> >>Warning: Size 5396 of Exif.Minolta.0x0020 exceeds 4096 bytes limit. Not
> >>decoded.
> >>digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==>
> >>Author: Duncan Hill
> >>digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==>
> >>Author Title: Mr
> >>digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==>
> >>Credit: digikam: /home/dhill/Images/2006/2006-07-04/.digikam-camera-28184
> >>==> Source: digikam:
> >>/home/dhill/Images/2006/2006-07-04/.digikam-camera-28184 ==> Copyright:
> >>Duncan Hill
> >>KCrash: Application 'digikam' crashing...
> >>QSocketNotifier: invalid socket 20 and type 'Read', disabling...
> >>QSocketNotifier: invalid socket 18 and type 'Read', disabling...
> >>QSocketNotifier: invalid socket 15 and type 'Read', disabling...
> >>QSocketNotifier: invalid socket 12 and type 'Read', disabling...
> >>QSocketNotifier: invalid socket 7 and type 'Read', disabling...
> >>QSocketNotifier: invalid socket 19 and type 'Read', disabling...
> >>QSocketNotifier: invalid socket 13 and type 'Read', disabling...
> >>QSocketNotifier: invalid socket 4 and type 'Read', disabling...
> >>QSocketNotifier: invalid socket 16 and type 'Read', disabling...
> >>QSocketNotifier: invalid socket 9 and type 'Read', disabling...
> >>digikam: Fatal IO error: client killed
> >>
> >>URL: svn://anonsvn.kde.org/home/kde/trunk/extragear/graphics/digikam
> >>Repository Root: svn://anonsvn.kde.org/home/kde
> >>Repository UUID: 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
> >>Revision: 558379
> >>
> >>Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
> >>[Thread debugging using libthread_db enabled]
> >>[New Thread -1241184032 (LWP 28184)]
> >>[New Thread -1250796624 (LWP 28209)]
> >>0xb68ae696 in QPtrList<QPostEvent>::current () from
> >> /usr/lib/libqt-mt.so.3 #0  0xb68ae696 in QPtrList<QPostEvent>::current
> >> () from
> >>/usr/lib/libqt-mt.so.3 #1  0xb68a9554 in QApplication::sendPostedEvents
> >> () from /usr/lib/libqt-mt.so.3
> >>#2  0xb68a95ae in QApplication::sendPostedEvents ()
> >>   from /usr/lib/libqt-mt.so.3
> >>#3  0xb684c42b in QEventLoop::processEvents () from
> >> /usr/lib/libqt-mt.so.3 #4  0xb68c0947 in QEventLoop::enterLoop () from
> >> /usr/lib/libqt-mt.so.3 #5  0xb68c086a in QEventLoop::exec () from
> >> /usr/lib/libqt-mt.so.3 #6  0xb68a6965 in QApplication::exec () from
> >> /usr/lib/libqt-mt.so.3 #7  0x0804aacd in main (argc=1, argv=0xbfc088f4)
> >> at main.cpp:273 _______________________________________________
> >>Digikam-users mailing list
> >>[hidden email]
> >>https://mail.kde.org/mailman/listinfo/digikam-users
> >
> >_______________________________________________
> >Digikam-users mailing list
> >[hidden email]
> >https://mail.kde.org/mailman/listinfo/digikam-users
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

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

[Duncan Hill-5]

On Wednesday 05 July 2006 11:44, Gilles Caulier wrote:
> No this is not the patch.
>
> This crash appear during downloading with exif autorotate using Exiv2. Are
> you sure to have only one Exiv2 version installed on your computer ? Do not
> mix old and new released (including current svn).
>

Exiv2 comes from SVN, and my build scripts are configured to set up the /opt
location as the Exiv2 library area - it's worked for several months.

I can't test the patch at this point, as digiKam goes splat before it finishes
copying the data from the CF card.

ldd /usr/bin/digikam | grep -i exi
        libexiv2-0.9.1.so => /opt/exiv2/lib/libexiv2-0.9.1.so (0xb78ed000)
        libexif.so.12 => /usr/lib/libexif.so.12 (0xb6320000)

I'll respin the lot now and see what happens.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Marcel Wiesweg]

Am Mittwoch 05 Juli 2006 12:58 schrieb Gilles Caulier:
> On Wednesday 05 July 2006 12:54, Tommaso Schiavinotto wrote:
> > I have the same problem.. with a Dynax 5D and MRW as well. I download
> > through a mounted dir (the CF in the card reader), then when I close the
> > download window digikam crashes.. I will send more infos as soon as
> > possible.
>
> Warning, there is two crash reported by Duncan :
>
> - one when camera dialog is closed (i can reproduce it sometimes).

Gilles this is code I wrote so I feel responsible ;-)
I have also had this crash sometimes but not reproducibly.
Is this related to the commit from toma from Monday?
That would make sense for me: If scanlib calls kapp->processEvents() it will
sometimes process the deleteLater() event, so your patch would solve this -
but, we may only call deleteLater if isBusy() is false, your patch calls it
in any case.

It seems ScanLib is written with the initial scan in mind, so if it is called
from the running UI, as from CameraUI, it is another solution to disable
lines 337 and 338 in this case (not in the normal case) and set a busy
cursor.

The second crash reported by Duncan looks like something I got when I tried to
stop a KProcess not from the main thread (then I understood that KProcess is
heavily non-reentrant).

Marcel

> - one during download when auto-rotation is enable (not reproductible here)
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Duncan Hill-5]

On Wednesday 05 July 2006 12:51, Duncan Hill wrote:
> On Wednesday 05 July 2006 11:44, Gilles Caulier wrote:
> > No this is not the patch.
> >
> > This crash appear during downloading with exif autorotate using Exiv2.
> > Are you sure to have only one Exiv2 version installed on your computer ?
> > Do not mix old and new released (including current svn).
>
> Exiv2 comes from SVN, and my build scripts are configured to set up the
> /opt location as the Exiv2 library area - it's worked for several months.

A respin of everything (including Exiv2 - had to add a new setting to LDFLAGS)
has worked, including that patch by the looks.  I've got another batch of
photos to upload when I get home tonght, and will confirm then that the patch
is definitely working.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-2]

Le Mercredi 05 Juillet 2006 02:27 PM, Marcel Wiesweg a écrit :

> Am Mittwoch 05 Juli 2006 12:58 schrieb Gilles Caulier:
> > On Wednesday 05 July 2006 12:54, Tommaso Schiavinotto wrote:
> > > I have the same problem.. with a Dynax 5D and MRW as well. I download
> > > through a mounted dir (the CF in the card reader), then when I close
> > > the download window digikam crashes.. I will send more infos as soon as
> > > possible.
> >
> > Warning, there is two crash reported by Duncan :
> >
> > - one when camera dialog is closed (i can reproduce it sometimes).
>
> Gilles this is code I wrote so I feel responsible ;-)
> I have also had this crash sometimes but not reproducibly.
> Is this related to the commit from toma from Monday?

Well Toma have reported to me a backtrace and he have identified that the
crash is relevant of kapp->processEvent() in scanlib. This is why he have
comment a line in scanlib.cpp

> That would make sense for me: If scanlib calls kapp->processEvents() it
> will sometimes process the deleteLater() event, so your patch would solve
> this - but, we may only call deleteLater if isBusy() is false, your patch
> calls it in any case.
>
> It seems ScanLib is written with the initial scan in mind, so if it is
> called from the running UI, as from CameraUI, it is another solution to
> disable lines 337 and 338 in this case (not in the normal case) and set a
> busy cursor.

Well, i let's you fix this point into svn, if you have the right solution...
If you fix is right the commented line in scanlib.cpp can be un-commented ?

>
> The second crash reported by Duncan looks like something I got when I tried
> to stop a KProcess not from the main thread (then I understood that
> KProcess is heavily non-reentrant).

Well, KProcess is used where exactly ?

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

[Marcel Wiesweg]

> > Gilles this is code I wrote so I feel responsible ;-)
> > I have also had this crash sometimes but not reproducibly.
> > Is this related to the commit from toma from Monday?
>
> Well Toma have reported to me a backtrace and he have identified that the
> crash is relevant of kapp->processEvent() in scanlib. This is why he have
> comment a line in scanlib.cpp
>
> > That would make sense for me: If scanlib calls kapp->processEvents() it
> > will sometimes process the deleteLater() event, so your patch would solve
> > this - but, we may only call deleteLater if isBusy() is false, your patch
> > calls it in any case.
> >
> > It seems ScanLib is written with the initial scan in mind, so if it is
> > called from the running UI, as from CameraUI, it is another solution to
> > disable lines 337 and 338 in this case (not in the normal case) and set a
> > busy cursor.
>
> Well, i let's you fix this point into svn, if you have the right
> solution... If you fix is right the commented line in scanlib.cpp can be
> un-commented ?

If I am right about the reason for this crash, then we can restore the line.
With a not reliably reproducible crash, there is not much we can do but try
it.
I will commit my suggestion of a solution.

>
> > The second crash reported by Duncan looks like something I got when I
> > tried to stop a KProcess not from the main thread (then I understood that
> > KProcess is heavily non-reentrant).
>
> Well, KProcess is used where exactly ?

Actually, the rawloader. But I don't see why the rawloader should be called at
this point, nor do I see a place where it is wrongly calling KProcess
methods.
We'll have to investigate this second crash further if anyone can repoduce it.
It's just that I wanted to say I have seen something like this before. It's
not necessarily KProcess.

Marcel

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

[Gilles Caulier-2]

Le Mercredi 05 Juillet 2006 01:51 PM, Duncan Hill a écrit :

> On Wednesday 05 July 2006 11:44, Gilles Caulier wrote:
> > No this is not the patch.
> >
> > This crash appear during downloading with exif autorotate using Exiv2.
> > Are you sure to have only one Exiv2 version installed on your computer ?
> > Do not mix old and new released (including current svn).
>
> Exiv2 comes from SVN, and my build scripts are configured to set up the
> /opt location as the Exiv2 library area - it's worked for several months.
>
> I can't test the patch at this point, as digiKam goes splat before it
> finishes copying the data from the CF card.
>
> ldd /usr/bin/digikam | grep -i exi
>         libexiv2-0.9.1.so => /opt/exiv2/lib/libexiv2-0.9.1.so (0xb78ed000)

If you use Exiv2 from svn, why digiKam is liked with Exiv2 0.9.1 !!!

I suspect both Exiv2 version on your computer. what's "locate libexiv2" give
on your computer ?

>         libexif.so.12 => /usr/lib/libexif.so.12 (0xb6320000)

Incredible. why digiKam is linked with libexif. Exiv2 do not use libexif, and
i have removed libkexif depency (witch use libexif) since digiKam use Exiv2.

Can you rebuild all digiKam using a fresh svn checkout, and try again with
ldd ?

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

[Gilles Caulier-2]

Le Jeudi 06 Juillet 2006 09:06 PM, Caulier Gilles a écrit :

> Le Mercredi 05 Juillet 2006 01:51 PM, Duncan Hill a écrit :
> > On Wednesday 05 July 2006 11:44, Gilles Caulier wrote:
> > > No this is not the patch.
> > >
> > > This crash appear during downloading with exif autorotate using Exiv2.
> > > Are you sure to have only one Exiv2 version installed on your computer
> > > ? Do not mix old and new released (including current svn).
> >
> > Exiv2 comes from SVN, and my build scripts are configured to set up the
> > /opt location as the Exiv2 library area - it's worked for several months.
> >
> > I can't test the patch at this point, as digiKam goes splat before it
> > finishes copying the data from the CF card.
> >
> > ldd /usr/bin/digikam | grep -i exi
> >         libexiv2-0.9.1.so => /opt/exiv2/lib/libexiv2-0.9.1.so
> > (0xb78ed000)
>
> If you use Exiv2 from svn, why digiKam is liked with Exiv2 0.9.1 !!!
>
> I suspect both Exiv2 version on your computer. what's "locate libexiv2"
> give on your computer ?

Yes, i can confirm that something is wrong in your computer. You must have
this report :

[gilles@portable-gc .libs]$ ldd digikam |grep exi
        libexiv2-0.10.so => /usr/lib/libexiv2-0.10.so (0xb7921000)
        libexif.so.12 => /usr/lib/libexif.so.12 (0xb646a000)

>
> >         libexif.so.12 => /usr/lib/libexif.so.12 (0xb6320000)
>
> Incredible. why digiKam is linked with libexif. Exiv2 do not use libexif,
> and i have removed libkexif depency (witch use libexif) since digiKam use
> Exiv2.

ok, libexif is added by GPHOTO2 flags ! It's normal...

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

[Duncan Hill-2]

On Wednesday 05 July 2006 13:46, Duncan Hill wrote:
> On Wednesday 05 July 2006 12:51, Duncan Hill wrote:
> > Exiv2 comes from SVN, and my build scripts are configured to set up the
> > /opt location as the Exiv2 library area - it's worked for several months.
>
> A respin of everything (including Exiv2 - had to add a new setting to
> LDFLAGS) has worked, including that patch by the looks.  I've got another
> batch of photos to upload when I get home tonght, and will confirm then
> that the patch is definitely working.

Just pulled a pile of images off of a card, and no crash.

I'm going to attribute the other crash to a mucked up build process - I ended
up adding 'make clean' to the build process I use to always ensure a
clean(er) build area.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users