[Bug 166867] New: Digikam crashes when starting

[chipster19]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=166867         
           Summary: Digikam crashes when starting
           Product: digikam
           Version: 0.9.4
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel kde org
        ReportedBy: chipster19 free fr


Version:           0.9.4 (using KDE 3.5.9)
Installed from:    Compiled From Sources
Compiler:          gcc 4.3
OS:                Linux

Following the error message :

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47353108801856 (LWP 2685)]
[KCrash handler]
#5  0x00002b1100000005 in ?? ()
#6  0x00002b113a171e82 in Exiv2::ExifTags::tagList ()
   from /usr/lib/libexiv2.so.4
#7  0x00002b113a171e9a in Exiv2::ExifTags::tagInfo ()
   from /usr/lib/libexiv2.so.4
#8  0x00002b113a1760b6 in Exiv2::ExifTags::tagName ()
   from /usr/lib/libexiv2.so.4
#9  0x00002b113a17650a in Exiv2::ExifKey::makeKey ()
   from /usr/lib/libexiv2.so.4
#10 0x00002b113a179661 in Exiv2::ExifKey::ExifKey ()
   from /usr/lib/libexiv2.so.4
#11 0x00002b113a12f592 in Exiv2::Exifdatum::Exifdatum ()
   from /usr/lib/libexiv2.so.4
#12 0x00002b113a13482e in Exiv2::ExifData::add () from /usr/lib/libexiv2.so.4
#13 0x00002b113a134d51 in Exiv2::ExifData::load () from /usr/lib/libexiv2.so.4
#14 0x00002b113a14c2f9 in Exiv2::JpegBase::readMetadata ()
   from /usr/lib/libexiv2.so.4
#15 0x00002b1139f7b643 in KExiv2Iface::KExiv2::load ()
   from /usr/lib/libkexiv2.so.3
#16 0x00002b1138745bc9 in Digikam::DMetadata::load ()
   from /usr/lib/libdigikam.so.0
#17 0x00002b1138761cab in Digikam::ImagePropertiesTab::setCurrentURL ()
   from /usr/lib/libdigikam.so.0
#18 0x00002b1138750463 in Digikam::ImagePropertiesSideBarDB::slotChangedTab ()
   from /usr/lib/libdigikam.so.0
#19 0x00002b11387507ec in Digikam::ImagePropertiesSideBarDB::itemChanged ()
   from /usr/lib/libdigikam.so.0
#20 0x00002b1138750912 in Digikam::ImagePropertiesSideBarDB::itemChanged ()
   from /usr/lib/libdigikam.so.0
#21 0x00002b11385d8ea0 in Digikam::DigikamView::slotDispatchImageSelected ()
   from /usr/lib/libdigikam.so.0
#22 0x00002b11385dc5c2 in Digikam::DigikamView::qt_invoke ()
   from /usr/lib/libdigikam.so.0
#23 0x00002b113c5ac1ac in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#24 0x00002b113c5ace23 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#25 0x00002b113c5caed5 in QTimer::event () from /usr/lib/libqt-mt.so.3
#26 0x00002b113c5570a5 in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#27 0x00002b113c557c87 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#28 0x00002b113b8eeb1e in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#29 0x00002b113c54d9a2 in QEventLoop::activateTimers ()
   from /usr/lib/libqt-mt.so.3
#30 0x00002b113c50e7e2 in QEventLoop::processEvents ()
   from /usr/lib/libqt-mt.so.3
#31 0x00002b113c56b581 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#32 0x00002b113c56b452 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#33 0x00000000004034a6 in main ()
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=166867         




------- Additional Comments From andi.clemens gmx net  2008-07-17 18:50 -------
What version of libkexiv2 and exiv2 do you have installed?
Make sure to comply with the requirements listed in the README file.

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

[Arnd Baecker]

To me it seems that the crash is happening inside exiv2.
Which version of exiv2 are you using (See "About digikam" menu)?
If it is not 0.17.1, please try that one).

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

[Arnd Baecker]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=166867         




------- Additional Comments From arnd.baecker web de  2008-07-17 18:51 -------
To me it seems that the crash is happening inside exiv2.
Which version of exiv2 are you using (See "About digikam" menu)?
If it is not 0.17.1, please try that one).

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

[chipster19]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=166867         
chipster19 free fr changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WORKSFORME



------- Additional Comments From chipster19 free fr  2008-07-17 19:40 -------
I have re-installed kipi-plugins version 0.1.5 and now digikam works fine !!

i have the following version of :
exiv2 : 0.17.1
kexiv2 : 0.1.7


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

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=166867         
caulier.gilles gmail com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |Metadata
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Jasper]

8~) wrote

To me it seems that the crash is happening inside exiv2.
Which version of exiv2 are you using (See "About digikam" menu)?
If it is not 0.17.1, please try that one).

I have re-installed kipi-plugins version 0.1.5 and now digikam works fine !!

i have the following version of :
exiv2 : 0.17.1
kexiv2 : 0.1.7

 
Strangely digikam crashes with exiv2 17.19 from svn, and not 17.1 from debian.
 Also the dependancies for the kipi plugins are still in the individual plugin folders, as kipiplugins have been merged into digikam surely the dependancies should be listed in the README in digikam root folder (i.e exiv2 = 17.1 etc)

[Arnd Baecker]

On Fri, 18 Jul 2008, Jasper Aorangi wrote:

>
>
> 8~) wrote:
> >
> > To me it seems that the crash is happening inside exiv2.
> > Which version of exiv2 are you using (See "About digikam" menu)?
> > If it is not 0.17.1, please try that one).
> >
> > I have re-installed kipi-plugins version 0.1.5 and now digikam works fine
> > !!
> >
> > i have the following version of :
> > exiv2 : 0.17.1
> > kexiv2 : 0.1.7
> >
> >
>
> Strangely digikam crashes with exiv2 17.19 from svn, and not 17.1 from
> debian.

exiv2 from svn is a major rewrite compared to 0.17.1,
so this is not completely unexpected, see here
http://uk.groups.yahoo.com/group/exiv2/message/1237?var=1&l=1
for mor information.
If you could provide a full backtrace for the crash, this
could help Andreas (exiv2 author) to fix this issue.


>  Also the dependancies for the kipi plugins are still in the individual
> plugin folders, as kipiplugins have been merged into digikam surely the
> dependancies should be listed in the README in digikam root folder (i.e
> exiv2 = 17.1 etc)

digikam now uses exiv2 only indirectly via libkexiv2, where
libexiv2   >= 0.13  (0.17.1 recommended) http://www.exiv2.org
is mentioned in the dependencies.

Gilles, what do you think, should we require:
  libexiv2   = 0.17.1
or is this too strict?

I am not sure about the kipiplugins stuff -
what should be changed where?

Best, Arnd

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

[Gilles Caulier-4]

I recommend to use Exiv2 0.16 or 0.17.1 not 0.17.0 where we have found
some crash with RAW files.

0.17.1 is more stable.

About 0.17.19 (next 0.18 version i fact) it will be fine to post here
the full gdb backtrace. Andreas Huggel (Exiv2 author) is in this room.

To provide a suitabe backtrace, please compile all using debug info
(Exiv2, libkexiv2 and digiKam) and follow the intruction listed here :

http://www.digikam.org/drupal/contrib

Best

Gilles Caulier

2008/7/18, Arnd Baecker <[hidden email]>:

> On Fri, 18 Jul 2008, Jasper Aorangi wrote:
>
>>
>>
>> 8~) wrote:
>> >
>> > To me it seems that the crash is happening inside exiv2.
>> > Which version of exiv2 are you using (See "About digikam" menu)?
>> > If it is not 0.17.1, please try that one).
>> >
>> > I have re-installed kipi-plugins version 0.1.5 and now digikam works
>> > fine
>> > !!
>> >
>> > i have the following version of :
>> > exiv2 : 0.17.1
>> > kexiv2 : 0.1.7
>> >
>> >
>>
>> Strangely digikam crashes with exiv2 17.19 from svn, and not 17.1 from
>> debian.
>
> exiv2 from svn is a major rewrite compared to 0.17.1,
> so this is not completely unexpected, see here
> http://uk.groups.yahoo.com/group/exiv2/message/1237?var=1&l=1
> for mor information.
> If you could provide a full backtrace for the crash, this
> could help Andreas (exiv2 author) to fix this issue.
>
>
>>  Also the dependancies for the kipi plugins are still in the individual
>> plugin folders, as kipiplugins have been merged into digikam surely the
>> dependancies should be listed in the README in digikam root folder (i.e
>> exiv2 = 17.1 etc)
>
> digikam now uses exiv2 only indirectly via libkexiv2, where
> libexiv2   >= 0.13  (0.17.1 recommended) http://www.exiv2.org
> is mentioned in the dependencies.
>
> Gilles, what do you think, should we require:
>   libexiv2   = 0.17.1
> or is this too strict?
>
> I am not sure about the kipiplugins stuff -
> what should be changed where?
>
> Best, Arnd
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>

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

[Jasper]

Bugzilla from [e-mail] wrote

About 0.17.19 (next 0.18 version i fact) it will be fine to post here
the full gdb backtrace. Andreas Huggel (Exiv2 author) is in this room.

To provide a suitabe backtrace, please compile all using debug info
(Exiv2, libkexiv2 and digiKam) and follow the intruction listed here :

http://www.digikam.org/drupal/contrib

Best

Gilles Caulier

 I did this last night, and the problem seems to be resolved. It crashed on first try, then not thereafter.

>
>> I am not sure about the kipiplugins stuff -
>> what should be changed where?
> >
> >Best, Arnd
>
My mistake, kipiplugins has been moved to graphics not into the digikam folder... What I had intened to suggest (had this not been the case) that as kipiplugins is such an integral part of digikam , that the kipiplugins dependancies be listed with the digikam dependancies in README, anyway...