| Summary: | showfoto crash after regular update with zypper | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Wolfhard Langer <wolfhard.langer> |
| Component: | Showfoto-Core | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | crash | CC: | andresbajotierra, caulier.gilles |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.6.0 | |
| Sentry Crash Report: | |||
The reporter sent me an email: ---- because of the crash-mesage of "digiKam" and "showfoto" I opened this bug report. Besides in bug report number 190612 for the same problem from Caulier Gilles I got the answer, that it may be a library of another software package, that causes the error which results in a crash of digiKam or showfoto on my laptop. In the meanwhile kde3-digikam in the version 0.9.5-7.1 is running on my laptop but the crashes did not vanish. Therefore I opened bug report 190645. 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 icon of a picture in an album and digiKam does not crash. If only one item in this segment is activated and if then the cursor is moved over an picture icon in an album 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. Perhaps an updated library of an other software package should be downgraded? Perhaps you can give me a hint and tell me the reasons for your changes in the header of the bug report. I do not know whether this error which results in a crash when using digiKam or showfoto should be treated in a bug report or whether it would be better to open a thread in a forum. Thank you in advance. Kind regards Wolfhard Langer --------- @Wolfhard: sorry, I'm not a Digikam developer nor expert so I can't help you with this. I just reassigned this bug report to the "digikam" category because it will not going to get attention in the "kde" product. I don't know if the KDE3 version of digikam is getting support. You can always ask on forums for people having the same issue, they could have found an answer to the problem. Regards I 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. Regards Wolfhard Langer |
Version: (using KDE 3.5.10) OS: Linux Installed from: SuSE RPMs Hello, the applications "digiKam" and "showfoto" are crashing since a few days ago I performed an regular software update for the software repositories with "zypper". There is no problem to open "digiKam" and "showfoto". In "digiKam" it is possible to open a video with kaffeine or to use the DIA-mode for the pictures in a folder. But as soon as "digiKam" tries to show the picture information ("meta data") when the cursor is over the picture icon in the picture window and changes from the "arrow" symbol to the the "hand" - symbol, "digiKam" will crash. Only if I click as soon as possible on the picture icon, then the picture is shown in "digiKam" but cannot be modified. The crash report shows the following messages: Überprüfung der Systemkonfiguration beim Start deaktiviert. [?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) [Thread debugging using libthread_db enabled] [New Thread 0xb66416d0 (LWP 5255)] [New Thread 0xb6117b90 (LWP 5257)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 0xbc09e8f4 in ?? () #7 0xb18187a9 in KJpegPlugin::readInfo () from /opt/kde3/lib/kde3/kfile_jpeg.so #8 0xb7cbde9a in KFileMetaInfo::init () from /opt/kde3/lib/libkio.so.4 #9 0xb7cbdf82 in KFileMetaInfo::KFileMetaInfo () from /opt/kde3/lib/libkio.so.4 #10 0xb7cbe04f in KFileItem::metaInfo () from /opt/kde3/lib/libkio.so.4 #11 0x080a647a in ?? () #12 0x08094a83 in ?? () #13 0x08094c15 in ?? () #14 0x0807c6bf in ?? () #15 0x0807f9cb in ?? () #16 0xb707f98a in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #17 0xb7081ecb in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #18 0x0813f0bc in ?? () #19 0x0813f711 in ?? () #20 0x08142cb0 in ?? () #21 0xb707f98a in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0xb7081ecb in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #23 0x0813366c in ?? () #24 0x081336a5 in ?? () #25 0x08135152 in ?? () #26 0x08137869 in ?? () #27 0xb707f98a in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #28 0x080daf61 in ?? () #29 0x080dc87e in ?? () #30 0x080da94b in ?? () #31 0xb707fae6 in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #32 0xb701a5bd in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #33 0xb701b5f6 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #34 0xb76fe882 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #35 0xb701c6da in QApplication::sendPostedEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #36 0xb701c836 in QApplication::sendPostedEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #37 0xb6fc4cc5 in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #38 0xb7032f00 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #39 0xb7032d96 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #40 0xb701ac4f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #41 0x08079819 in ?? () #42 0xb6a0b5f5 in __libc_start_main () from /lib/libc.so.6 #43 0x08078b11 in ?? () Till today I used digikam 0.9.3. In bug-report 190612 I got the advice to update digiKam to the higher and stable version 0.9.5 for KDE 3.5 but after the update the applications "digiKam" and "showfoto" continue to crash. Here are some installation information for "digiKam" on my laptop: Informationen für Paket kde3-digikam: Repository: KDE:KDE3 Name: kde3-digikam Version: 0.9.5-6.1 Architektur: i586 Hersteller: openSUSE Build Service Installiert: Ja Status: aktuell Größe (installiert): 26,4 M Betriebssystem: Linux 2.6.25.20-0.1-default i686 System: openSUSE 11.0 (i586) KDE: 3.5.10 "release 46" Can you please check the reason for this problem or give me a hint to solve this problem? Thank you in advance for your support and for your help. Kind regards Wolfhard Langer