digikam 0.9 keeps crashing
Locked
 
|
Hello,
My OS is Kanotix (Debian) with Kernel 2.6.17 and KDE 3.5.4. I have two instances of digikam 0.9 on two different computers. One was compiled from the tarballs, one installed with apt-get from debian/experimental. Both instances create the same problems: I start digikam from scratch ( no digikam3.db and no digikamrc). The program asks for the database directory. 1) If I give an existing directory (with subdirectories and images already stored) digikam crashes. 2) If I create a new and empty directory digikam starts fine 2a) If I copy images or subdirectories into this new directory and start digikam the program crashes immediately even before the splash screen appears. 2b) If I import images or directories the files are copied, but during the copying process the programs halts and I have to skip an image file or let the program do the skipping automatically. After copying is finished ALL images are shown, even those which were presumably skipped. If I close digikam and start again, the program sometimes crashes, sometimes not. 3) If I sort (sub) directories in my albumlist with drag and drop some of the albums which were not moved are deleted or at least no longer accessible. Restarting digikam resuklts in a crash. I can't give any specific error messages, because the crash just evokes the KDE-Crashmanager with Signal 11 (SIGSEGV). Back trace is not possible. Any ideas or - better still - solutions. Greetings Udo _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
efpost wrote:
> I can't give any specific error messages, because the crash just evokes > the KDE-Crashmanager with Signal 11 (SIGSEGV). Back trace is not possible. For the compiled version, use this: ./configure --enable-debug=full Then invoke digikam from the command line. a) you'll get console output, and b) you'll get a full core in the kde crash handler. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: digikam 0.9 keeps crashing
|
|
Le Lundi 28 Août 2006 17:56, Duncan Hill a écrit :
> efpost wrote: > > I can't give any specific error messages, because the crash just evokes > > the KDE-Crashmanager with Signal 11 (SIGSEGV). Back trace is not > > possible. > > For the compiled version, use this: > > ./configure --enable-debug=full > > Then invoke digikam from the command line. a) you'll get console > output, and b) you'll get a full core in the kde crash handler. > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users Look in HACKING file. There are instructions to report a backtrace using GDB Gilles Caulier _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by efpost
efpost wrote: > I can't give any specific error messages, because the crash just evokes > the KDE-Crashmanager with Signal 11 (SIGSEGV). Back trace is not possible. Duncan Hill wrote: > For the compiled version, use this: > ./configure --enable-debug=full > Then invoke digikam from the command line. a) you'll get console > output, and b) you'll get a full core in the kde crash handler. -----------Thanks for the info. I recompiled as you said, but the kde crash handler still gives no backtrace. "Backtracing not possible. Debugger "gdb" cannot be found" (<< literally translated from German). But I've got console output as follows digikam: ScanLib: Finding non-existing albums: 6ms digikam: ScanLib: Finding items not in the database or disk: 310 ms digikam: ScanLib: Updating items without date: 0 ms digikam: Cannot parse EXIF metadata using Exiv2 digikam: digikampp: . .. loading all plugins .. digikam: Dirty: / digikam: Dirty: / The above output is from one of the no crashing examples ( 2b in my first post). Greetings Udo _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Gilles Caulier-2
I did. But entering "gdb digikam" into console givesLe Lundi 28 Août 2006 17:56, Duncan Hill a écrit : bash: gdb: command not found. Udo _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
---------------------------- Sorry, I had to install gdb first (never used a debugger before) Now I have the following backtrace from kde crah handler. Situation was type 1 of my first post (clean start into existing database directory) Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1241233728 (LWP 26873)] [KCrash handler] #5 0xb60e62ad in mallopt () from /lib/tls/libc.so.6 #6 0xb60e6942 in free () from /lib/tls/libc.so.6 #7 0xb628a4e1 in operator delete () from /usr/lib/libstdc++.so.6 #8 0xb62661ed in std::string::_Rep::_M_destroy () from /usr/lib/libstdc++.so.6 #9 0xb6268d58 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string () from /usr/lib/libstdc++.so.6 #10 0xb7e4541b in Digikam::DMetadata::convertCommentValue ( exifDatum=@0x815b134) at dmetadata.cpp:1006 #11 0xb7e460f1 in Digikam::DMetadata::getImageComment (this=0xbf827488) at dmetadata.cpp:850 #12 0xb7ce8dab in Digikam::ScanLib::storeItemInDatabase (this=0xbf8277e8, albumURL=@0xbf827528, filename=@0xbf827574, albumID=2) at scanlib.cpp:397 #13 0xb7ce9308 in Digikam::ScanLib::allFiles (this=0xbf8277e8, directory=@0xbf827680) at scanlib.cpp:350 #14 0xb7ce941a in Digikam::ScanLib::allFiles (this=0xbf8277e8, directory=@0xbf827720) at scanlib.cpp:355 #15 0xb7ce9fea in Digikam::ScanLib::findMissingItems (this=0xbf8277e8) at scanlib.cpp:191 #16 0xb7cea56f in Digikam::ScanLib::startScan (this=0xbf8277e8) at scanlib.cpp:91 #17 0xb7c8af92 in Digikam::AlbumManager::setLibraryPath (this=0x8128fc0, path=@0xbf8279e8) at albummanager.cpp:289 #18 0x0804a85c in main (argc=-1209025432, argv=0xb61b0420) at main.cpp:243 Appreciate your help. Udo _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: digikam 0.9 keeps crashing
|
|
In reply to this post by efpost
Le Lundi 28 Août 2006 10:22 PM, efpost a écrit :
> Caulier Gilles schrieb: > >Le Lundi 28 Août 2006 17:56, Duncan Hill a écrit : > >>efpost wrote: > >>>I can't give any specific error messages, because the crash just evokes > >>>the KDE-Crashmanager with Signal 11 (SIGSEGV). Back trace is not > >>>possible. > >> > >>For the compiled version, use this: > >> > >>./configure --enable-debug=full > >> > >>Then invoke digikam from the command line. a) you'll get console > >>output, and b) you'll get a full core in the kde crash handler. > >>_______________________________________________ > >>Digikam-users mailing list > >>[hidden email] > >>https://mail.kde.org/mailman/listinfo/digikam-users > > > >Look in HACKING file. There are instructions to report a backtrace using > > GDB > > > >Gilles Caulier > >_______________________________________________ > >Digikam-users mailing list > >[hidden email] > >https://mail.kde.org/mailman/listinfo/digikam-users > > I did. But entering "gdb digikam" into console gives > > bash: gdb: command not found. > > Udo Install 'gdb' package. GDB is the GNU debugger Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: digikam 0.9 keeps crashing
|
|
In reply to this post by efpost
Le Lundi 28 Août 2006 10:49 PM, efpost a écrit :
> efpost schrieb: > > Caulier Gilles schrieb: > >>Le Lundi 28 Août 2006 17:56, Duncan Hill a écrit : > >>>efpost wrote: > >>>>I can't give any specific error messages, because the crash just evokes > >>>>the KDE-Crashmanager with Signal 11 (SIGSEGV). Back trace is not > >>>>possible. > >>> > >>>For the compiled version, use this: > >>> > >>>./configure --enable-debug=full > >>> > >>>Then invoke digikam from the command line. a) you'll get console > >>>output, and b) you'll get a full core in the kde crash handler. > >>>_______________________________________________ > >> > >>Look in HACKING file. There are instructions to report a backtrace using > >> GDB > >> > >>Gilles Caulier > >>_______________________________________________ > > > > I did. But entering "gdb digikam" into console gives > > > > bash: gdb: command not found. > > > > Udo > > ---------------------------- > > Sorry, > I had to install gdb first (never used a debugger before) > > Now I have the following backtrace from kde crah handler. Situation was > type 1 of my first post (clean start into existing database directory) > > > Using host libthread_db library "/lib/tls/libthread_db.so.1". > [Thread debugging using libthread_db enabled] > [New Thread -1241233728 (LWP 26873)] > [KCrash handler] > #5 0xb60e62ad in mallopt () from /lib/tls/libc.so.6 > #6 0xb60e6942 in free () from /lib/tls/libc.so.6 > #7 0xb628a4e1 in operator delete () from /usr/lib/libstdc++.so.6 > #8 0xb62661ed in std::string::_Rep::_M_destroy () > from /usr/lib/libstdc++.so.6 > #9 0xb6268d58 in std::basic_string<char, std::char_traits<char>, > std::allocator<char> >::~basic_string () from /usr/lib/libstdc++.so.6 > #10 0xb7e4541b in Digikam::DMetadata::convertCommentValue ( > exifDatum=@0x815b134) at dmetadata.cpp:1006 > #11 0xb7e460f1 in Digikam::DMetadata::getImageComment (this=0xbf827488) > at dmetadata.cpp:850 > #12 0xb7ce8dab in Digikam::ScanLib::storeItemInDatabase (this=0xbf8277e8, > albumURL=@0xbf827528, filename=@0xbf827574, albumID=2) at > scanlib.cpp:397 > #13 0xb7ce9308 in Digikam::ScanLib::allFiles (this=0xbf8277e8, > directory=@0xbf827680) at scanlib.cpp:350 > #14 0xb7ce941a in Digikam::ScanLib::allFiles (this=0xbf8277e8, > directory=@0xbf827720) at scanlib.cpp:355 > #15 0xb7ce9fea in Digikam::ScanLib::findMissingItems (this=0xbf8277e8) > at scanlib.cpp:191 > #16 0xb7cea56f in Digikam::ScanLib::startScan (this=0xbf8277e8) > at scanlib.cpp:91 > #17 0xb7c8af92 in Digikam::AlbumManager::setLibraryPath (this=0x8128fc0, > path=@0xbf8279e8) at albummanager.cpp:289 > #18 0x0804a85c in main (argc=-1209025432, argv=0xb61b0420) at main.cpp:243 > > > Appreciate your help. > Udo This problem have been corrected in current implementation. If you use the 0.9.0-beta1, i'm so surprise, because i think it have been fixed just before beta1 release. I all case, current implementation from svn repository is the utimate solution. Look in digiKam web site how to download source code from svn and how to compile it. Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Thanks for the quick answer, Gilles. I had downloaded digikam-0.9.0-beta1-r1.tar.bz2 from sourceforge.net as indicated at the digikam-website.Le Lundi 28 Août 2006 10:49 PM, efpost a écrit : Now I'll try the svn version and will report here tomorrow. Thanks again. Udo _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |