Hi,
I have this curious behaviour in DigiKam since an systemwide upgrade several days ago (can't tell which upgrade, used YAST). No thumbnails are shown in album view - but they come loud and clear in the other views (Calendar, Tags and first pic is shown in Tools/Viewer). If I hoover over those thumbnails (the image, not textual info), the application crashes. This is probably not a Digikam-only thumbnailing problem since it occurs also when using ShowFoto and Gwenview in thumbnail view. Maybe it's a KIPI thing? I have tried to revert to DK 0.9.4 and all sorts of other downgrades, but no luck. Right now my system is up to date according to my repos, Suse (stable), KDE and Packman being the ones in question. Digikam 0.9.5-7.1_x86_64 from KDE:Backports repo OpenSUSE 11.0 - KDE3.5.10-r46 Using libraries: KExiv2 0.1.8 Exiv 0.16 KDcraw 0.1.8 LibRaw 0.6.13-Release PNG 1.2.26 mplayerthumbs-0.5b-0.pm.1 If you could point me in any direction as to solve this mystery, I'd be grateful. Sveinn í Felli Messages in console: <--------------- sveinki@fellunited:~> digikam Cannot load metadata using Exiv2 (Error #11: /mnt/gogn/myndir/Myndir/Ferðir/2004-Kaldbakur/00013.raw: The file contains data of an unknown image type) Exif color workspace tag set to: 65535 terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc KCrash: Application 'digikam' crashing... ---------------> KCrash traceback: <--------------- Slökkt er á ræsiskoðun kerfisuppsetningar. [?1034h(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 0x7fadcc6b6700 (LWP 30986)] (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] #5 0x00007fadc9dc65c5 in raise () from /lib64/libc.so.6 #6 0x00007fadc9dc7bb3 in abort () from /lib64/libc.so.6 #7 0x00007fadca1b51d4 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib64/libstdc++.so.6 #8 0x00007fadca1b35f6 in ?? () from /usr/lib64/libstdc++.so.6 #9 0x00007fadca1b3623 in std::terminate () from /usr/lib64/libstdc++.so.6 #10 0x00007fadca1b370a in __cxa_throw () from /usr/lib64/libstdc++.so.6 #11 0x00007fadca1b3b61 in operator new () from /usr/lib64/libstdc++.so.6 #12 0x00007fadca191361 in std::string::_Rep::_S_create () from /usr/lib64/libstdc++.so.6 #13 0x00007fadca191c0b in std::string::_Rep::_M_clone () from /usr/lib64/libstdc++.so.6 #14 0x00007fadca1927c4 in std::string::assign () from /usr/lib64/libstdc++.so.6 #15 0x00007fadb611b4ef in KJpegPlugin::readInfo () from /opt/kde3/lib64/kde3/kfile_jpeg.so #16 0x00007fadc789c926 in KFileMetaInfo::init () from /opt/kde3/lib64/libkio.so.4 #17 0x00007fadc789caa2 in KFileItem::metaInfo () from /opt/kde3/lib64/libkio.so.4 #18 0x00007fadcbf8ed74 in Digikam::AlbumFileTip::updateText () from /opt/kde3/lib64/libdigikam.so.0 #19 0x00007fadcbf91650 in Digikam::AlbumFileTip::setIconItem () from /opt/kde3/lib64/libdigikam.so.0 #20 0x00007fadcbf8b56c in Digikam::AlbumIconView::qt_invoke () from /opt/kde3/lib64/libdigikam.so.0 #21 0x00007fadca771f5f in QObject::activate_signal () from /usr/lib/qt3/lib64/libqt-mt.so.3 #22 0x00007fadcbfd22c0 in Digikam::IconView::signalShowToolTip () from /opt/kde3/lib64/libdigikam.so.0 #23 0x00007fadcbfd7400 in Digikam::IconView::qt_invoke () from /opt/kde3/lib64/libdigikam.so.0 #24 0x00007fadca771f5f in QObject::activate_signal () from /usr/lib/qt3/lib64/libqt-mt.so.3 #25 0x00007fadca7742d2 in QObject::activate_signal () from /usr/lib/qt3/lib64/libqt-mt.so.3 #26 0x00007fadca792745 in QTimer::event () from /usr/lib/qt3/lib64/libqt-mt.so.3 #27 0x00007fadca7135d5 in QApplication::internalNotify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #28 0x00007fadca7143ba in QApplication::notify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #29 0x00007fadcb06d952 in KApplication::notify () from /opt/kde3/lib64/libkdecore.so.4 #30 0x00007fadca709e2e in QEventLoop::activateTimers () from /usr/lib/qt3/lib64/libqt-mt.so.3 #31 0x00007fadca6c3f76 in QEventLoop::processEvents () from /usr/lib/qt3/lib64/libqt-mt.so.3 #32 0x00007fadca72a109 in QEventLoop::enterLoop () from /usr/lib/qt3/lib64/libqt-mt.so.3 #33 0x00007fadca729f92 in QEventLoop::exec () from /usr/lib/qt3/lib64/libqt-mt.so.3 #34 0x00000000004030b9 in ?? () #35 0x00007fadc9db2436 in __libc_start_main () from /lib64/libc.so.6 #36 0x0000000000401f49 in ?? () #37 0x00007fffd46f96e8 in ?? () #38 0x000000000000001c in ?? () #39 0x0000000000000001 in ?? () #40 0x00007fffd46fb396 in ?? () #41 0x0000000000000000 in ?? () ---------------> _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Crash appears in KDELibs. Sound like a binary compatibily package
bronken. check your system Gilles Caulier 2009/5/10 Sveinn í Felli <[hidden email]>: > Hi, > > I have this curious behaviour in DigiKam since an systemwide > upgrade several days ago (can't tell which upgrade, used YAST). > > No thumbnails are shown in album view - but they come loud > and clear in the other views (Calendar, Tags and first pic > is shown in Tools/Viewer). If I hoover over those thumbnails > (the image, not textual info), the application crashes. > > This is probably not a Digikam-only thumbnailing problem > since it occurs also when using ShowFoto and Gwenview in > thumbnail view. Maybe it's a KIPI thing? > > I have tried to revert to DK 0.9.4 and all sorts of other > downgrades, but no luck. Right now my system is up to date > according to my repos, Suse (stable), KDE and Packman being > the ones in question. > > Digikam 0.9.5-7.1_x86_64 from KDE:Backports repo > OpenSUSE 11.0 - KDE3.5.10-r46 > Using libraries: > KExiv2 0.1.8 > Exiv 0.16 > KDcraw 0.1.8 > LibRaw 0.6.13-Release > PNG 1.2.26 > mplayerthumbs-0.5b-0.pm.1 > > If you could point me in any direction as to solve this > mystery, I'd be grateful. > > Sveinn í Felli > > > Messages in console: > <--------------- > sveinki@fellunited:~> digikam > Cannot load metadata using Exiv2 (Error #11: > /mnt/gogn/myndir/Myndir/Ferðir/2004-Kaldbakur/00013.raw: The > file contains data of an unknown image type) > Exif color workspace tag set to: 65535 > terminate called after throwing an instance of 'std::bad_alloc' > what(): std::bad_alloc > KCrash: Application 'digikam' crashing... > ---------------> > > KCrash traceback: > <--------------- > Slökkt er á ræsiskoðun kerfisuppsetningar. > > [?1034h(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 0x7fadcc6b6700 (LWP 30986)] > (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] > #5 0x00007fadc9dc65c5 in raise () from /lib64/libc.so.6 > #6 0x00007fadc9dc7bb3 in abort () from /lib64/libc.so.6 > #7 0x00007fadca1b51d4 in > __gnu_cxx::__verbose_terminate_handler () > from /usr/lib64/libstdc++.so.6 > #8 0x00007fadca1b35f6 in ?? () from /usr/lib64/libstdc++.so.6 > #9 0x00007fadca1b3623 in std::terminate () from > /usr/lib64/libstdc++.so.6 > #10 0x00007fadca1b370a in __cxa_throw () from > /usr/lib64/libstdc++.so.6 > #11 0x00007fadca1b3b61 in operator new () from > /usr/lib64/libstdc++.so.6 > #12 0x00007fadca191361 in std::string::_Rep::_S_create () > from /usr/lib64/libstdc++.so.6 > #13 0x00007fadca191c0b in std::string::_Rep::_M_clone () > from /usr/lib64/libstdc++.so.6 > #14 0x00007fadca1927c4 in std::string::assign () from > /usr/lib64/libstdc++.so.6 > #15 0x00007fadb611b4ef in KJpegPlugin::readInfo () > from /opt/kde3/lib64/kde3/kfile_jpeg.so > #16 0x00007fadc789c926 in KFileMetaInfo::init () > from /opt/kde3/lib64/libkio.so.4 > #17 0x00007fadc789caa2 in KFileItem::metaInfo () > from /opt/kde3/lib64/libkio.so.4 > #18 0x00007fadcbf8ed74 in Digikam::AlbumFileTip::updateText () > from /opt/kde3/lib64/libdigikam.so.0 > #19 0x00007fadcbf91650 in Digikam::AlbumFileTip::setIconItem () > from /opt/kde3/lib64/libdigikam.so.0 > #20 0x00007fadcbf8b56c in Digikam::AlbumIconView::qt_invoke () > from /opt/kde3/lib64/libdigikam.so.0 > #21 0x00007fadca771f5f in QObject::activate_signal () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #22 0x00007fadcbfd22c0 in > Digikam::IconView::signalShowToolTip () > from /opt/kde3/lib64/libdigikam.so.0 > #23 0x00007fadcbfd7400 in Digikam::IconView::qt_invoke () > from /opt/kde3/lib64/libdigikam.so.0 > #24 0x00007fadca771f5f in QObject::activate_signal () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #25 0x00007fadca7742d2 in QObject::activate_signal () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #26 0x00007fadca792745 in QTimer::event () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #27 0x00007fadca7135d5 in QApplication::internalNotify () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #28 0x00007fadca7143ba in QApplication::notify () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #29 0x00007fadcb06d952 in KApplication::notify () > from /opt/kde3/lib64/libkdecore.so.4 > #30 0x00007fadca709e2e in QEventLoop::activateTimers () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #31 0x00007fadca6c3f76 in QEventLoop::processEvents () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #32 0x00007fadca72a109 in QEventLoop::enterLoop () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #33 0x00007fadca729f92 in QEventLoop::exec () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #34 0x00000000004030b9 in ?? () > #35 0x00007fadc9db2436 in __libc_start_main () from > /lib64/libc.so.6 > #36 0x0000000000401f49 in ?? () > #37 0x00007fffd46f96e8 in ?? () > #38 0x000000000000001c in ?? () > #39 0x0000000000000001 in ?? () > #40 0x00007fffd46fb396 in ?? () > #41 0x0000000000000000 in ?? () > > ---------------> > > _______________________________________________ > 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 |
In reply to this post by Sveinn í Felli
Hello,
because of this "curious behaviour" in digiKam and showfoto a few days ago I opened bug report 190645 ( http://bugs.kde.org/show_bug.cgi?id=190645 ). In the meanwhile this report has been reassigned from "kde" - category to "digiKam" - category because the report will not get attention in the "kde" category. Unfortunately I can not give you a hint to solve this problem. I only noticed: if in the digiKam settings for the "short infos" the items for the file infos and for the picture infos in the topmost segment are not activated, then I can move the cursor over the thumbnail (image) and digiKam does not crash. If only one item in this segment is activated and if then the cursor is moved over a thumbnail (image) digiKam will crash. Besides anymore it is not possible to change a picture with the help of digiKam and "showfoto" also crashes when opening a picture. Also I opened a thread in "Applications" - forum on forums.opensuse.org ( http://forums.opensuse.org/applications/413271-digikam-showfoto-crash.html ). So, if you find a solution please let me know. Thank you in advance. Wolfhard Langer Sveinn í Felli schrieb: > Hi, > > I have this curious behaviour in DigiKam since an systemwide > upgrade several days ago (can't tell which upgrade, used YAST). > > No thumbnails are shown in album view - but they come loud > and clear in the other views (Calendar, Tags and first pic > is shown in Tools/Viewer). If I hoover over those thumbnails > (the image, not textual info), the application crashes. > > This is probably not a Digikam-only thumbnailing problem > since it occurs also when using ShowFoto and Gwenview in > thumbnail view. Maybe it's a KIPI thing? > > I have tried to revert to DK 0.9.4 and all sorts of other > downgrades, but no luck. Right now my system is up to date > according to my repos, Suse (stable), KDE and Packman being > the ones in question. > > Digikam 0.9.5-7.1_x86_64 from KDE:Backports repo > OpenSUSE 11.0 - KDE3.5.10-r46 > Using libraries: > KExiv2 0.1.8 > Exiv 0.16 > KDcraw 0.1.8 > LibRaw 0.6.13-Release > PNG 1.2.26 > mplayerthumbs-0.5b-0.pm.1 > > If you could point me in any direction as to solve this > mystery, I'd be grateful. > > Sveinn í Felli > > > Messages in console: > <--------------- > sveinki@fellunited:~> digikam > Cannot load metadata using Exiv2 (Error #11: > /mnt/gogn/myndir/Myndir/Ferðir/2004-Kaldbakur/00013.raw: The > file contains data of an unknown image type) > Exif color workspace tag set to: 65535 > terminate called after throwing an instance of 'std::bad_alloc' > what(): std::bad_alloc > KCrash: Application 'digikam' crashing... > ---------------> > > KCrash traceback: > <--------------- > Slökkt er á ræsiskoðun kerfisuppsetningar. > > [?1034h(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 0x7fadcc6b6700 (LWP 30986)] > (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] > #5 0x00007fadc9dc65c5 in raise () from /lib64/libc.so.6 > #6 0x00007fadc9dc7bb3 in abort () from /lib64/libc.so.6 > #7 0x00007fadca1b51d4 in > __gnu_cxx::__verbose_terminate_handler () > from /usr/lib64/libstdc++.so.6 > #8 0x00007fadca1b35f6 in ?? () from /usr/lib64/libstdc++.so.6 > #9 0x00007fadca1b3623 in std::terminate () from > /usr/lib64/libstdc++.so.6 > #10 0x00007fadca1b370a in __cxa_throw () from > /usr/lib64/libstdc++.so.6 > #11 0x00007fadca1b3b61 in operator new () from > /usr/lib64/libstdc++.so.6 > #12 0x00007fadca191361 in std::string::_Rep::_S_create () > from /usr/lib64/libstdc++.so.6 > #13 0x00007fadca191c0b in std::string::_Rep::_M_clone () > from /usr/lib64/libstdc++.so.6 > #14 0x00007fadca1927c4 in std::string::assign () from > /usr/lib64/libstdc++.so.6 > #15 0x00007fadb611b4ef in KJpegPlugin::readInfo () > from /opt/kde3/lib64/kde3/kfile_jpeg.so > #16 0x00007fadc789c926 in KFileMetaInfo::init () > from /opt/kde3/lib64/libkio.so.4 > #17 0x00007fadc789caa2 in KFileItem::metaInfo () > from /opt/kde3/lib64/libkio.so.4 > #18 0x00007fadcbf8ed74 in Digikam::AlbumFileTip::updateText () > from /opt/kde3/lib64/libdigikam.so.0 > #19 0x00007fadcbf91650 in Digikam::AlbumFileTip::setIconItem () > from /opt/kde3/lib64/libdigikam.so.0 > #20 0x00007fadcbf8b56c in Digikam::AlbumIconView::qt_invoke () > from /opt/kde3/lib64/libdigikam.so.0 > #21 0x00007fadca771f5f in QObject::activate_signal () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #22 0x00007fadcbfd22c0 in > Digikam::IconView::signalShowToolTip () > from /opt/kde3/lib64/libdigikam.so.0 > #23 0x00007fadcbfd7400 in Digikam::IconView::qt_invoke () > from /opt/kde3/lib64/libdigikam.so.0 > #24 0x00007fadca771f5f in QObject::activate_signal () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #25 0x00007fadca7742d2 in QObject::activate_signal () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #26 0x00007fadca792745 in QTimer::event () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #27 0x00007fadca7135d5 in QApplication::internalNotify () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #28 0x00007fadca7143ba in QApplication::notify () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #29 0x00007fadcb06d952 in KApplication::notify () > from /opt/kde3/lib64/libkdecore.so.4 > #30 0x00007fadca709e2e in QEventLoop::activateTimers () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #31 0x00007fadca6c3f76 in QEventLoop::processEvents () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #32 0x00007fadca72a109 in QEventLoop::enterLoop () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #33 0x00007fadca729f92 in QEventLoop::exec () > from /usr/lib/qt3/lib64/libqt-mt.so.3 > #34 0x00000000004030b9 in ?? () > #35 0x00007fadc9db2436 in __libc_start_main () from > /lib64/libc.so.6 > #36 0x0000000000401f49 in ?? () > #37 0x00007fffd46f96e8 in ?? () > #38 0x000000000000001c in ?? () > #39 0x0000000000000001 in ?? () > #40 0x00007fffd46fb396 in ?? () > #41 0x0000000000000000 in ?? () > > ---------------> > > _______________________________________________ > 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 |
In reply to this post by Sveinn í Felli
Hi,
Wolfhard Langer wrote: > Hello, > > because of this "curious behaviour" in digiKam and showfoto a few days > ago I opened bug report 190645 ( > http://bugs.kde.org/show_bug.cgi?id=190645 ). In the meanwhile this > report has been reassigned from "kde" - category to "digiKam" - > category because the report will not get attention in the "kde" category. > > Unfortunately I can not give you a hint to solve this problem. I only > noticed: if in the digiKam settings for the "short infos" the items for > the file infos and for the picture infos in the topmost segment are not > activated, then I can move the cursor over the thumbnail (image) and > digiKam does not crash. If only one item in this segment is activated > and if then the cursor is moved over a thumbnail (image) digiKam will > crash. Besides anymore it is not possible to change a picture with the > help of digiKam and "showfoto" also crashes when opening a picture. > > Also I opened a thread in "Applications" - forum on forums.opensuse.org > ( > http://forums.opensuse.org/applications/413271-digikam-showfoto-crash.html > ). So, if you find a solution please let me know. > Thanks for the tip. Gilles supposed a broken binary, I reinstalled everything, no luck. Funny thing is that in the import dialog (from camera) all thumbnails are just fine. I have no troubles in my other DK 0.9.x installs, which include OpenSuse 11.1 (KDE4, 64bit and 32bit), Kubuntu 8.10 32 and 64bit, Mepis 7.0 32bit. I'll let you know if I find something. Sveinn í Felli > Thank you in advance. > > Wolfhard Langer > > Sveinn í Felli schrieb: >> Hi, >> >> I have this curious behaviour in DigiKam since an systemwide >> upgrade several days ago (can't tell which upgrade, used YAST). >> >> No thumbnails are shown in album view - but they come loud >> and clear in the other views (Calendar, Tags and first pic >> is shown in Tools/Viewer). If I hoover over those thumbnails >> (the image, not textual info), the application crashes. >> >> This is probably not a Digikam-only thumbnailing problem >> since it occurs also when using ShowFoto and Gwenview in >> thumbnail view. Maybe it's a KIPI thing? >> >> I have tried to revert to DK 0.9.4 and all sorts of other >> downgrades, but no luck. Right now my system is up to date >> according to my repos, Suse (stable), KDE and Packman being >> the ones in question. >> >> Digikam 0.9.5-7.1_x86_64 from KDE:Backports repo >> OpenSUSE 11.0 - KDE3.5.10-r46 >> Using libraries: >> KExiv2 0.1.8 >> Exiv 0.16 >> KDcraw 0.1.8 >> LibRaw 0.6.13-Release >> PNG 1.2.26 >> mplayerthumbs-0.5b-0.pm.1 >> >> If you could point me in any direction as to solve this >> mystery, I'd be grateful. >> >> Sveinn í Felli >> >> >> Messages in console: >> <--------------- >> sveinki@fellunited:~> digikam >> Cannot load metadata using Exiv2 (Error #11: >> /mnt/gogn/myndir/Myndir/Ferðir/2004-Kaldbakur/00013.raw: The >> file contains data of an unknown image type) >> Exif color workspace tag set to: 65535 >> terminate called after throwing an instance of 'std::bad_alloc' >> what(): std::bad_alloc >> KCrash: Application 'digikam' crashing... >> ---------------> >> >> KCrash traceback: >> <--------------- >> Slökkt er á ræsiskoðun kerfisuppsetningar. >> >> [?1034h(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 0x7fadcc6b6700 (LWP 30986)] >> (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] >> #5 0x00007fadc9dc65c5 in raise () from /lib64/libc.so.6 >> #6 0x00007fadc9dc7bb3 in abort () from /lib64/libc.so.6 >> #7 0x00007fadca1b51d4 in >> __gnu_cxx::__verbose_terminate_handler () >> from /usr/lib64/libstdc++.so.6 >> #8 0x00007fadca1b35f6 in ?? () from /usr/lib64/libstdc++.so.6 >> #9 0x00007fadca1b3623 in std::terminate () from >> /usr/lib64/libstdc++.so.6 >> #10 0x00007fadca1b370a in __cxa_throw () from >> /usr/lib64/libstdc++.so.6 >> #11 0x00007fadca1b3b61 in operator new () from >> /usr/lib64/libstdc++.so.6 >> #12 0x00007fadca191361 in std::string::_Rep::_S_create () >> from /usr/lib64/libstdc++.so.6 >> #13 0x00007fadca191c0b in std::string::_Rep::_M_clone () >> from /usr/lib64/libstdc++.so.6 >> #14 0x00007fadca1927c4 in std::string::assign () from >> /usr/lib64/libstdc++.so.6 >> #15 0x00007fadb611b4ef in KJpegPlugin::readInfo () >> from /opt/kde3/lib64/kde3/kfile_jpeg.so >> #16 0x00007fadc789c926 in KFileMetaInfo::init () >> from /opt/kde3/lib64/libkio.so.4 >> #17 0x00007fadc789caa2 in KFileItem::metaInfo () >> from /opt/kde3/lib64/libkio.so.4 >> #18 0x00007fadcbf8ed74 in Digikam::AlbumFileTip::updateText () >> from /opt/kde3/lib64/libdigikam.so.0 >> #19 0x00007fadcbf91650 in Digikam::AlbumFileTip::setIconItem () >> from /opt/kde3/lib64/libdigikam.so.0 >> #20 0x00007fadcbf8b56c in Digikam::AlbumIconView::qt_invoke () >> from /opt/kde3/lib64/libdigikam.so.0 >> #21 0x00007fadca771f5f in QObject::activate_signal () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #22 0x00007fadcbfd22c0 in >> Digikam::IconView::signalShowToolTip () >> from /opt/kde3/lib64/libdigikam.so.0 >> #23 0x00007fadcbfd7400 in Digikam::IconView::qt_invoke () >> from /opt/kde3/lib64/libdigikam.so.0 >> #24 0x00007fadca771f5f in QObject::activate_signal () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #25 0x00007fadca7742d2 in QObject::activate_signal () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #26 0x00007fadca792745 in QTimer::event () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #27 0x00007fadca7135d5 in QApplication::internalNotify () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #28 0x00007fadca7143ba in QApplication::notify () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #29 0x00007fadcb06d952 in KApplication::notify () >> from /opt/kde3/lib64/libkdecore.so.4 >> #30 0x00007fadca709e2e in QEventLoop::activateTimers () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #31 0x00007fadca6c3f76 in QEventLoop::processEvents () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #32 0x00007fadca72a109 in QEventLoop::enterLoop () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #33 0x00007fadca729f92 in QEventLoop::exec () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #34 0x00000000004030b9 in ?? () >> #35 0x00007fadc9db2436 in __libc_start_main () from >> /lib64/libc.so.6 >> #36 0x0000000000401f49 in ?? () >> #37 0x00007fffd46f96e8 in ?? () >> #38 0x000000000000001c in ?? () >> #39 0x0000000000000001 in ?? () >> #40 0x00007fffd46fb396 in ?? () >> #41 0x0000000000000000 in ?? () >> >> ---------------> >> >> _______________________________________________ >> 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 |
In reply to this post by Sveinn í Felli
Hi,
I suspect this to be an OpenSuse problem, apparently courtesy of Novell Inc... lots of other broken things. A bunch of pages I googled mention Novell having changed the repository structure, making lots of core package updates "uninstallable". No hard evidence, just a feeling... Sveinn Wolfhard Langer wrote: > Hello, > > because of this "curious behaviour" in digiKam and showfoto a few days > ago I opened bug report 190645 ( > http://bugs.kde.org/show_bug.cgi?id=190645 ). In the meanwhile this > report has been reassigned from "kde" - category to "digiKam" - > category because the report will not get attention in the "kde" category. > > Unfortunately I can not give you a hint to solve this problem. I only > noticed: if in the digiKam settings for the "short infos" the items for > the file infos and for the picture infos in the topmost segment are not > activated, then I can move the cursor over the thumbnail (image) and > digiKam does not crash. If only one item in this segment is activated > and if then the cursor is moved over a thumbnail (image) digiKam will > crash. Besides anymore it is not possible to change a picture with the > help of digiKam and "showfoto" also crashes when opening a picture. > > Also I opened a thread in "Applications" - forum on forums.opensuse.org > ( > http://forums.opensuse.org/applications/413271-digikam-showfoto-crash.html > ). So, if you find a solution please let me know. > > Thank you in advance. > > Wolfhard Langer > > Sveinn í Felli schrieb: >> Hi, >> >> I have this curious behaviour in DigiKam since an systemwide >> upgrade several days ago (can't tell which upgrade, used YAST). >> >> No thumbnails are shown in album view - but they come loud >> and clear in the other views (Calendar, Tags and first pic >> is shown in Tools/Viewer). If I hoover over those thumbnails >> (the image, not textual info), the application crashes. >> >> This is probably not a Digikam-only thumbnailing problem >> since it occurs also when using ShowFoto and Gwenview in >> thumbnail view. Maybe it's a KIPI thing? >> >> I have tried to revert to DK 0.9.4 and all sorts of other >> downgrades, but no luck. Right now my system is up to date >> according to my repos, Suse (stable), KDE and Packman being >> the ones in question. >> >> Digikam 0.9.5-7.1_x86_64 from KDE:Backports repo >> OpenSUSE 11.0 - KDE3.5.10-r46 >> Using libraries: >> KExiv2 0.1.8 >> Exiv 0.16 >> KDcraw 0.1.8 >> LibRaw 0.6.13-Release >> PNG 1.2.26 >> mplayerthumbs-0.5b-0.pm.1 >> >> If you could point me in any direction as to solve this >> mystery, I'd be grateful. >> >> Sveinn í Felli >> >> >> Messages in console: >> <--------------- >> sveinki@fellunited:~> digikam >> Cannot load metadata using Exiv2 (Error #11: >> /mnt/gogn/myndir/Myndir/Ferðir/2004-Kaldbakur/00013.raw: The >> file contains data of an unknown image type) >> Exif color workspace tag set to: 65535 >> terminate called after throwing an instance of 'std::bad_alloc' >> what(): std::bad_alloc >> KCrash: Application 'digikam' crashing... >> ---------------> >> >> KCrash traceback: >> <--------------- >> Slökkt er á ræsiskoðun kerfisuppsetningar. >> >> [?1034h(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 0x7fadcc6b6700 (LWP 30986)] >> (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] >> #5 0x00007fadc9dc65c5 in raise () from /lib64/libc.so.6 >> #6 0x00007fadc9dc7bb3 in abort () from /lib64/libc.so.6 >> #7 0x00007fadca1b51d4 in >> __gnu_cxx::__verbose_terminate_handler () >> from /usr/lib64/libstdc++.so.6 >> #8 0x00007fadca1b35f6 in ?? () from /usr/lib64/libstdc++.so.6 >> #9 0x00007fadca1b3623 in std::terminate () from >> /usr/lib64/libstdc++.so.6 >> #10 0x00007fadca1b370a in __cxa_throw () from >> /usr/lib64/libstdc++.so.6 >> #11 0x00007fadca1b3b61 in operator new () from >> /usr/lib64/libstdc++.so.6 >> #12 0x00007fadca191361 in std::string::_Rep::_S_create () >> from /usr/lib64/libstdc++.so.6 >> #13 0x00007fadca191c0b in std::string::_Rep::_M_clone () >> from /usr/lib64/libstdc++.so.6 >> #14 0x00007fadca1927c4 in std::string::assign () from >> /usr/lib64/libstdc++.so.6 >> #15 0x00007fadb611b4ef in KJpegPlugin::readInfo () >> from /opt/kde3/lib64/kde3/kfile_jpeg.so >> #16 0x00007fadc789c926 in KFileMetaInfo::init () >> from /opt/kde3/lib64/libkio.so.4 >> #17 0x00007fadc789caa2 in KFileItem::metaInfo () >> from /opt/kde3/lib64/libkio.so.4 >> #18 0x00007fadcbf8ed74 in Digikam::AlbumFileTip::updateText () >> from /opt/kde3/lib64/libdigikam.so.0 >> #19 0x00007fadcbf91650 in Digikam::AlbumFileTip::setIconItem () >> from /opt/kde3/lib64/libdigikam.so.0 >> #20 0x00007fadcbf8b56c in Digikam::AlbumIconView::qt_invoke () >> from /opt/kde3/lib64/libdigikam.so.0 >> #21 0x00007fadca771f5f in QObject::activate_signal () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #22 0x00007fadcbfd22c0 in >> Digikam::IconView::signalShowToolTip () >> from /opt/kde3/lib64/libdigikam.so.0 >> #23 0x00007fadcbfd7400 in Digikam::IconView::qt_invoke () >> from /opt/kde3/lib64/libdigikam.so.0 >> #24 0x00007fadca771f5f in QObject::activate_signal () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #25 0x00007fadca7742d2 in QObject::activate_signal () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #26 0x00007fadca792745 in QTimer::event () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #27 0x00007fadca7135d5 in QApplication::internalNotify () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #28 0x00007fadca7143ba in QApplication::notify () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #29 0x00007fadcb06d952 in KApplication::notify () >> from /opt/kde3/lib64/libkdecore.so.4 >> #30 0x00007fadca709e2e in QEventLoop::activateTimers () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #31 0x00007fadca6c3f76 in QEventLoop::processEvents () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #32 0x00007fadca72a109 in QEventLoop::enterLoop () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #33 0x00007fadca729f92 in QEventLoop::exec () >> from /usr/lib/qt3/lib64/libqt-mt.so.3 >> #34 0x00000000004030b9 in ?? () >> #35 0x00007fadc9db2436 in __libc_start_main () from >> /lib64/libc.so.6 >> #36 0x0000000000401f49 in ?? () >> #37 0x00007fffd46f96e8 in ?? () >> #38 0x000000000000001c in ?? () >> #39 0x0000000000000001 in ?? () >> #40 0x00007fffd46fb396 in ?? () >> #41 0x0000000000000000 in ?? () >> >> ---------------> >> >> _______________________________________________ >> 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 |
On Friday 15 May 2009 10:53:29, Sveinn í Felli wrote:
> Hi, > > I suspect this to be an OpenSuse problem, apparently > courtesy of Novell Inc... lots of other broken things. A > bunch of pages I googled mention Novell having changed the > repository structure, making lots of core package updates > "uninstallable". > > No hard evidence, just a feeling... > > Sveinn This could be true. I just installed a new user to use that within my photo course this weekend. Entering kde4.2 on openSuse 10.3 and starting digikam showed no thumbnails. Tried to start kde-4-digikam from within kde 3.5 and it crashed. So, I'll have to use the old digikam 0.9.3, that of course will have problems with files of newer cameras. Probably I'll have to use winXP in a virtualbox.... Kde4 is really... well, if you like windows you'll love it, because its useless, resource-consuming and loves to crash - welcome back windows 95, now called kde4... Since all the develpement now goes into kde4, I guess my next update will be a Mac and goodbye to linux... It's a shame. Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
I have a Mac and it sucks, too.
So I installed Linux / KDE4 on it and develop digiKam, my favourite app of all time. I sure could run it natively on the Mac, but I hate OSX. If you are not happy with KDE4 on your system, try another distribution. I don't have such problems, never had, everything is fine. But I heard a lot of complaints of openSUSE and Kubuntu users... There are many distributions that do it right: - Archlinux / Chakra - Mandriva - Gentoo and flavors Well I'm not here to evangelize people, but not everything is KDE4's or digiKam's fault. You could also use Gnome or any other Desktop system if you don't like KDE, and still use digiKam. Andi On Friday 15 May 2009 17:12:24 Daniel Bauer wrote: > On Friday 15 May 2009 10:53:29, Sveinn í Felli wrote: > > Hi, > > > > I suspect this to be an OpenSuse problem, apparently > > courtesy of Novell Inc... lots of other broken things. A > > bunch of pages I googled mention Novell having changed the > > repository structure, making lots of core package updates > > "uninstallable". > > > > No hard evidence, just a feeling... > > > > Sveinn > > This could be true. I just installed a new user to use that within my photo > course this weekend. Entering kde4.2 on openSuse 10.3 and starting digikam > showed no thumbnails. Tried to start kde-4-digikam from within kde 3.5 and > it crashed. > > So, I'll have to use the old digikam 0.9.3, that of course will have > problems with files of newer cameras. Probably I'll have to use winXP in a > virtualbox.... > > Kde4 is really... well, if you like windows you'll love it, because its > useless, resource-consuming and loves to crash - welcome back windows 95, > now called kde4... Since all the develpement now goes into kde4, I guess my > next update will be a Mac and goodbye to linux... It's a shame. > > Daniel _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
I didn't want to say that openSUSE and Kubuntu are crap, they sure are not.
I used Kubuntu 4 years ago, too. And my first distro ever was SuSE 6 or something like that, even bought it in a local store. But in the last months those were the distros that gave us the most bugreports. So to avoid flamewars now: openSUSE and Kubuntu are great!!! :-) Andi On Friday 15 May 2009 17:29:39 Andi Clemens wrote: > I have a Mac and it sucks, too. > So I installed Linux / KDE4 on it and develop digiKam, my favourite app of > all time. I sure could run it natively on the Mac, but I hate OSX. > > If you are not happy with KDE4 on your system, try another distribution. > I don't have such problems, never had, everything is fine. But I heard a > lot of complaints of openSUSE and Kubuntu users... > > There are many distributions that do it right: > - Archlinux / Chakra > - Mandriva > - Gentoo and flavors > > Well I'm not here to evangelize people, but not everything is KDE4's or > digiKam's fault. > You could also use Gnome or any other Desktop system if you don't like KDE, > and still use digiKam. > > Andi > > On Friday 15 May 2009 17:12:24 Daniel Bauer wrote: > > On Friday 15 May 2009 10:53:29, Sveinn í Felli wrote: > > > Hi, > > > > > > I suspect this to be an OpenSuse problem, apparently > > > courtesy of Novell Inc... lots of other broken things. A > > > bunch of pages I googled mention Novell having changed the > > > repository structure, making lots of core package updates > > > "uninstallable". > > > > > > No hard evidence, just a feeling... > > > > > > Sveinn > > > > This could be true. I just installed a new user to use that within my > > photo course this weekend. Entering kde4.2 on openSuse 10.3 and starting > > digikam showed no thumbnails. Tried to start kde-4-digikam from within > > kde 3.5 and it crashed. > > > > So, I'll have to use the old digikam 0.9.3, that of course will have > > problems with files of newer cameras. Probably I'll have to use winXP in > > a virtualbox.... > > > > Kde4 is really... well, if you like windows you'll love it, because its > > useless, resource-consuming and loves to crash - welcome back windows 95, > > now called kde4... Since all the develpement now goes into kde4, I guess > > my next update will be a Mac and goodbye to linux... It's a shame. > > > > Daniel > > _______________________________________________ > 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 |
In reply to this post by Bugzilla from andi.clemens@gmx.net
I didn't mean to start any flamewar; my problem is in
OpenSuse 11.0 with KDE3.5 on it. But from what I have gatered is that Novell has been fiddling with the repos, breaking a lot of dependencies for those who have done automatic or system-wide updates. My VLC is kaput also, along with many other "multimedia" apps. I like KDE4 for some aspects, but since there is another person also using my main box, and she's getting along with KDE3.5, I prefer that over KDE4. And I really like Digikam 0.10 for myself - but presenting that kind of interface to an XP user is a bit like showing someone Blender... Cheers, Sveinn í Felli Andi Clemens wrote: > I didn't want to say that openSUSE and Kubuntu are crap, they sure are not. > I used Kubuntu 4 years ago, too. And my first distro ever was SuSE 6 or > something like that, even bought it in a local store. > But in the last months those were the distros that gave us the most > bugreports. > So to avoid flamewars now: openSUSE and Kubuntu are great!!! :-) > > Andi > > On Friday 15 May 2009 17:29:39 Andi Clemens wrote: >> I have a Mac and it sucks, too. >> So I installed Linux / KDE4 on it and develop digiKam, my favourite app of >> all time. I sure could run it natively on the Mac, but I hate OSX. >> >> If you are not happy with KDE4 on your system, try another distribution. >> I don't have such problems, never had, everything is fine. But I heard a >> lot of complaints of openSUSE and Kubuntu users... >> >> There are many distributions that do it right: >> - Archlinux / Chakra >> - Mandriva >> - Gentoo and flavors >> >> Well I'm not here to evangelize people, but not everything is KDE4's or >> digiKam's fault. >> You could also use Gnome or any other Desktop system if you don't like KDE, >> and still use digiKam. >> >> Andi >> >> On Friday 15 May 2009 17:12:24 Daniel Bauer wrote: >>> On Friday 15 May 2009 10:53:29, Sveinn í Felli wrote: >>>> Hi, >>>> >>>> I suspect this to be an OpenSuse problem, apparently >>>> courtesy of Novell Inc... lots of other broken things. A >>>> bunch of pages I googled mention Novell having changed the >>>> repository structure, making lots of core package updates >>>> "uninstallable". >>>> >>>> No hard evidence, just a feeling... >>>> >>>> Sveinn >>> This could be true. I just installed a new user to use that within my >>> photo course this weekend. Entering kde4.2 on openSuse 10.3 and starting >>> digikam showed no thumbnails. Tried to start kde-4-digikam from within >>> kde 3.5 and it crashed. >>> >>> So, I'll have to use the old digikam 0.9.3, that of course will have >>> problems with files of newer cameras. Probably I'll have to use winXP in >>> a virtualbox.... >>> >>> Kde4 is really... well, if you like windows you'll love it, because its >>> useless, resource-consuming and loves to crash - welcome back windows 95, >>> now called kde4... Since all the develpement now goes into kde4, I guess >>> my next update will be a Mac and goodbye to linux... It's a shame. >>> >>> Daniel >> _______________________________________________ >> 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 |
In reply to this post by Sveinn í Felli
Hello,
I also stopped investigation concerning crashing digiKam 0.9.x running with KDE 3.5.10 and installed KDE 4.1.3 and digiKam 0.10. The main reason not to install KDE 4.1.3 on my laptop till now were the performance issues on http://en.opensuse.org/KDE/KDE4 with respect to fglrx. The main reason to dare installation of KDE 4.1.3 was, that after further updates of packages of vendor "packman" on my laptop in digiKam 0.9.5 the menu bar was lost. I am very content with digiKam 0.10 and KDE 4.1.3 and further updates of software packages or vendor changes I will handle with care. Kind regards Wolfhard Sveinn í Felli schrieb: > Hi, > > I suspect this to be an OpenSuse problem, apparently > courtesy of Novell Inc... lots of other broken things. A > bunch of pages I googled mention Novell having changed the > repository structure, making lots of core package updates > "uninstallable". > > No hard evidence, just a feeling... > > Sveinn > > Wolfhard Langer wrote: > >> Hello, >> >> because of this "curious behaviour" in digiKam and showfoto a few days >> ago I opened bug report 190645 ( >> http://bugs.kde.org/show_bug.cgi?id=190645 ). In the meanwhile this >> report has been reassigned from "kde" - category to "digiKam" - >> category because the report will not get attention in the "kde" category. >> >> Unfortunately I can not give you a hint to solve this problem. I only >> noticed: if in the digiKam settings for the "short infos" the items for >> the file infos and for the picture infos in the topmost segment are not >> activated, then I can move the cursor over the thumbnail (image) and >> digiKam does not crash. If only one item in this segment is activated >> and if then the cursor is moved over a thumbnail (image) digiKam will >> crash. Besides anymore it is not possible to change a picture with the >> help of digiKam and "showfoto" also crashes when opening a picture. >> >> Also I opened a thread in "Applications" - forum on forums.opensuse.org >> ( >> http://forums.opensuse.org/applications/413271-digikam-showfoto-crash.html >> ). So, if you find a solution please let me know. >> >> Thank you in advance. >> >> Wolfhard Langer >> >> Sveinn í Felli schrieb: >> >>> Hi, >>> >>> I have this curious behaviour in DigiKam since an systemwide >>> upgrade several days ago (can't tell which upgrade, used YAST). >>> >>> No thumbnails are shown in album view - but they come loud >>> and clear in the other views (Calendar, Tags and first pic >>> is shown in Tools/Viewer). If I hoover over those thumbnails >>> (the image, not textual info), the application crashes. >>> >>> This is probably not a Digikam-only thumbnailing problem >>> since it occurs also when using ShowFoto and Gwenview in >>> thumbnail view. Maybe it's a KIPI thing? >>> >>> I have tried to revert to DK 0.9.4 and all sorts of other >>> downgrades, but no luck. Right now my system is up to date >>> according to my repos, Suse (stable), KDE and Packman being >>> the ones in question. >>> >>> Digikam 0.9.5-7.1_x86_64 from KDE:Backports repo >>> OpenSUSE 11.0 - KDE3.5.10-r46 >>> Using libraries: >>> KExiv2 0.1.8 >>> Exiv 0.16 >>> KDcraw 0.1.8 >>> LibRaw 0.6.13-Release >>> PNG 1.2.26 >>> mplayerthumbs-0.5b-0.pm.1 >>> >>> If you could point me in any direction as to solve this >>> mystery, I'd be grateful. >>> >>> Sveinn í Felli >>> >>> >>> Messages in console: >>> <--------------- >>> sveinki@fellunited:~> digikam >>> Cannot load metadata using Exiv2 (Error #11: >>> /mnt/gogn/myndir/Myndir/Ferðir/2004-Kaldbakur/00013.raw: The >>> file contains data of an unknown image type) >>> Exif color workspace tag set to: 65535 >>> terminate called after throwing an instance of 'std::bad_alloc' >>> what(): std::bad_alloc >>> KCrash: Application 'digikam' crashing... >>> ---------------> >>> >>> KCrash traceback: >>> <--------------- >>> Slökkt er á ræsiskoðun kerfisuppsetningar. >>> >>> [?1034h(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 0x7fadcc6b6700 (LWP 30986)] >>> (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] >>> #5 0x00007fadc9dc65c5 in raise () from /lib64/libc.so.6 >>> #6 0x00007fadc9dc7bb3 in abort () from /lib64/libc.so.6 >>> #7 0x00007fadca1b51d4 in >>> __gnu_cxx::__verbose_terminate_handler () >>> from /usr/lib64/libstdc++.so.6 >>> #8 0x00007fadca1b35f6 in ?? () from /usr/lib64/libstdc++.so.6 >>> #9 0x00007fadca1b3623 in std::terminate () from >>> /usr/lib64/libstdc++.so.6 >>> #10 0x00007fadca1b370a in __cxa_throw () from >>> /usr/lib64/libstdc++.so.6 >>> #11 0x00007fadca1b3b61 in operator new () from >>> /usr/lib64/libstdc++.so.6 >>> #12 0x00007fadca191361 in std::string::_Rep::_S_create () >>> from /usr/lib64/libstdc++.so.6 >>> #13 0x00007fadca191c0b in std::string::_Rep::_M_clone () >>> from /usr/lib64/libstdc++.so.6 >>> #14 0x00007fadca1927c4 in std::string::assign () from >>> /usr/lib64/libstdc++.so.6 >>> #15 0x00007fadb611b4ef in KJpegPlugin::readInfo () >>> from /opt/kde3/lib64/kde3/kfile_jpeg.so >>> #16 0x00007fadc789c926 in KFileMetaInfo::init () >>> from /opt/kde3/lib64/libkio.so.4 >>> #17 0x00007fadc789caa2 in KFileItem::metaInfo () >>> from /opt/kde3/lib64/libkio.so.4 >>> #18 0x00007fadcbf8ed74 in Digikam::AlbumFileTip::updateText () >>> from /opt/kde3/lib64/libdigikam.so.0 >>> #19 0x00007fadcbf91650 in Digikam::AlbumFileTip::setIconItem () >>> from /opt/kde3/lib64/libdigikam.so.0 >>> #20 0x00007fadcbf8b56c in Digikam::AlbumIconView::qt_invoke () >>> from /opt/kde3/lib64/libdigikam.so.0 >>> #21 0x00007fadca771f5f in QObject::activate_signal () >>> from /usr/lib/qt3/lib64/libqt-mt.so.3 >>> #22 0x00007fadcbfd22c0 in >>> Digikam::IconView::signalShowToolTip () >>> from /opt/kde3/lib64/libdigikam.so.0 >>> #23 0x00007fadcbfd7400 in Digikam::IconView::qt_invoke () >>> from /opt/kde3/lib64/libdigikam.so.0 >>> #24 0x00007fadca771f5f in QObject::activate_signal () >>> from /usr/lib/qt3/lib64/libqt-mt.so.3 >>> #25 0x00007fadca7742d2 in QObject::activate_signal () >>> from /usr/lib/qt3/lib64/libqt-mt.so.3 >>> #26 0x00007fadca792745 in QTimer::event () >>> from /usr/lib/qt3/lib64/libqt-mt.so.3 >>> #27 0x00007fadca7135d5 in QApplication::internalNotify () >>> from /usr/lib/qt3/lib64/libqt-mt.so.3 >>> #28 0x00007fadca7143ba in QApplication::notify () >>> from /usr/lib/qt3/lib64/libqt-mt.so.3 >>> #29 0x00007fadcb06d952 in KApplication::notify () >>> from /opt/kde3/lib64/libkdecore.so.4 >>> #30 0x00007fadca709e2e in QEventLoop::activateTimers () >>> from /usr/lib/qt3/lib64/libqt-mt.so.3 >>> #31 0x00007fadca6c3f76 in QEventLoop::processEvents () >>> from /usr/lib/qt3/lib64/libqt-mt.so.3 >>> #32 0x00007fadca72a109 in QEventLoop::enterLoop () >>> from /usr/lib/qt3/lib64/libqt-mt.so.3 >>> #33 0x00007fadca729f92 in QEventLoop::exec () >>> from /usr/lib/qt3/lib64/libqt-mt.so.3 >>> #34 0x00000000004030b9 in ?? () >>> #35 0x00007fadc9db2436 in __libc_start_main () from >>> /lib64/libc.so.6 >>> #36 0x0000000000401f49 in ?? () >>> #37 0x00007fffd46f96e8 in ?? () >>> #38 0x000000000000001c in ?? () >>> #39 0x0000000000000001 in ?? () >>> #40 0x00007fffd46fb396 in ?? () >>> #41 0x0000000000000000 in ?? () >>> >>> ---------------> >>> >>> _______________________________________________ >>> 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 |
2009/5/16 Wolfhard Langer <[hidden email]>:
> Hello, > > I also stopped investigation concerning crashing digiKam 0.9.x running > with KDE 3.5.10 and installed KDE 4.1.3 and digiKam 0.10. The main > reason not to install KDE 4.1.3 on my laptop till now were the > performance issues on http://en.opensuse.org/KDE/KDE4 with respect to > fglrx. The main reason to dare installation of KDE 4.1.3 was, that after > further updates of packages of vendor "packman" on my laptop in digiKam > 0.9.5 the menu bar was lost. > > I am very content with digiKam 0.10 and KDE 4.1.3 I recommend to use KDE 4.2.x where a lots of bug in KDElibs have been fixed and digiKam is more suitable now. Gilles Caulier _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |