Bug 149063 - Open tool menu crash
Summary: Open tool menu crash
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Portability-Runtime (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-21 11:20 UTC by alle gabry
Modified: 2022-02-06 05:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.3.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description alle gabry 2007-08-21 11:20:25 UTC
Version:           1.4.1 (using KDE KDE 3.5.7)
Installed from:    Ubuntu Packages
Compiler:          gcc (GCC) 4.1.2 (Ubuntu 4.1.2-0ubuntu4) 
OS:                Linux

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/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)
(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)
(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 -1233213744 (LWP 6335)]
(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)
(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)
(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)
[KCrash handler]
#6  0xffffe410 in __kernel_vsyscall ()
#7  0xb7c93df0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb7c95641 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb7e96270 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#10 0xb7e93ca5 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb7e93ce2 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb7e93e1a in __cxa_throw () from /usr/lib/libstdc++.so.6
#13 0xb62377cb in Exiv2::ExifTags::registerMakerTagInfo ()
   from /usr/lib/libexiv2-0.12.so
#14 0xb6231501 in Exiv2::SigmaMakerNote::RegisterMn::RegisterMn ()
   from /usr/lib/libexiv2-0.12.so
#15 0xb56a239b in ?? () from /usr/lib/libexiv2.so.0
#16 0xb56c03e6 in ?? () from /usr/lib/libexiv2.so.0
#17 0xb7f3fff4 in ?? () from /lib/ld-linux.so.2
#18 0x08324ce0 in ?? ()
#19 0xbfec3688 in ?? ()
#20 0xb5642e19 in _init () from /usr/lib/libexiv2.so.0
Backtrace stopped: frame did not save the PC
Comment 1 Angelo Naselli 2007-08-21 12:19:05 UTC
I'm quite sure it's an Ubuntu issue, could you please
tell me which versions of exiv2 and libkexiv2 and kipi-plugins
you have on your system?
Comment 2 alle gabry 2007-08-22 12:01:27 UTC
the problem is kipi-plugin, I have uninstall kipi-plugin and now is ok.
kipi-plugin 0.1.3-1ubuntu1
exiv2 0.14-1~ach0feisty1
libkexiv2-0 0.1.1-0ubuntu1
libkexiv2-1 0.1.5-1ach0feisty1
Comment 3 Angelo Naselli 2007-08-22 12:09:01 UTC
> the problem is kipi-plugin, I have uninstall kipi-plugin and now is ok.

more or less, but the real problem cause is exiv2, you need the 0.12 for gwenview
and the 0.14 for kipi-plugins, but they are not compatible because they broke binary 
compatibility, so gwenview may (and it does) crash for that, so it could an old
digikam version, for instance.
The best way should be to rebuild gwenview against the same exiv2 library as you
use for your kipi-plugins
> libkexiv2-0 0.1.1-0ubuntu1
> libkexiv2-1 0.1.5-1ach0feisty1

BTW, you shouldn't need two libkexiv2 libraries.

Angelo
 
Comment 4 Angelo Naselli 2007-08-22 12:12:00 UTC
since it is a runtime linker problem it's a workforme by now, Achim we should find a way to avoid it though... maybe on kde4
Comment 5 caulier.gilles 2021-05-09 14:54:05 UTC
Not reproducible with digiKam 7.3.0 and Exiv2 0.27.4