[Pkg-kde-extras] Bug#605452:
I also have this problem. When, at first stratup, I configure the album's directories and Digikam starts to create the database, it crashesIf I launch digikam from Konsole, I've this output: mirko@darkstar:~$ digikam QLayout: Cannot add null widget to QVBoxLayout/ digikam: Fatal IO error: client killed KCrash: Application 'digikam' crashing... sock_file=/home/mirko/.kde/socket-darkstar/kdeinit4__0 [1]+ Stopped digikam ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#605452: fixed in digikam 2:1.9.0-3
Hi, the official debian squeeze site offers for digikam the package version digikam (2:1.2.0-7). I have also the same problem as described in the bug and I want to suggest to offer the version 2:1.9.0-3 as the official version for debian squeeze (maybe in the backport path). I tried to install the packages from the recommended ftp site with aptitude but I got error messages because of package version dependencies. I don't want to switch to the unstable release to get the digikam package run and I'm not willing to ride an installing version dependency orgy. Best regards Dirk Pankonin -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
Re: [Pkg-kde-extras] Bug#605452: fixed in digikam 2:1.9.0-3
Hello, On penktadienis 10 Birželis 2011 12:39:42 Dirk Pankonin wrote: Hi, the official debian squeeze site offers for digikam the package version digikam (2:1.2.0-7). I have also the same problem as described in the bug and I want to suggest to offer the version 2:1.9.0-3 as the official version for debian squeeze (maybe in the backport path). I tried to install the packages from the recommended ftp site with aptitude but I got error messages because of package version dependencies. I don't want to switch to the unstable release to get the digikam package run and I'm not willing to ride an installing version dependency orgy. It is not possible. Later digikam needs newer KDE. However, squeeze proper or squeeze-backports will not get newer KDE. Sorry. -- Modestas Vainius mo...@debian.org signature.asc Description: This is a digitally signed message part. ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#605452: marked as done (digikam crashes after splash screen)
Your message dated Sat, 28 May 2011 12:17:34 + with message-id e1qqisu-00085k...@franck.debian.org and subject line Bug#605452: fixed in digikam 2:1.9.0-3 has caused the Debian Bug report #605452, regarding digikam crashes after splash screen to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 605452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605452 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: digikam Version: 2:1.2.0-7 Severity: important At first run digikam asks some configuration questions, after all of the questions are answered the application attempts to open, but fails. At every attempt to open the application, it simply crashes after the splash screen. here is a backtrace: Application: digiKam (digikam), signal: Segmentation fault [Current thread is 1 (Thread 0xb23229a0 (LWP 11533))] Thread 2 (Thread 0xb0086b70 (LWP 11534)): [KCrash Handler] #6 Exiv2::ValueTypeunsigned short::toLong (this=0xaf433698, n=0) at value.hpp:1580 #7 0xb6f67eb6 in KExiv2Iface::KExiv2::getImageOrientation() const () from /usr/lib/libkexiv2.so.8 #8 0xb68834e4 in Digikam::DMetadata::getMetadataField (this=0xb0085e2c, field=Digikam::MetadataInfo::Orientation) at /home/max/digikam-1.2.0/libs/dmetadata/dmetadata.cpp:1163 #9 0xb68852ff in Digikam::DMetadata::getMetadataFields (this=0xb0085e2c, fields=...) at /home/max/digikam-1.2.0/libs/dmetadata/dmetadata.cpp:1362 #10 0xb65d5fa9 in Digikam::ImageScanner::scanImageInformation (this=0xb0085e24) at /home/max/digikam-1.2.0/libs/database/imagescanner.cpp:275 #11 0xb65da798 in Digikam::ImageScanner::scanFile (this=0xb0085e24, mode=Digikam::ImageScanner::NewScan) at /home/max/digikam-1.2.0/libs/database/imagescanner.cpp:237 #12 0xb65da9ad in Digikam::ImageScanner::newFile (this=0xb0085e24, albumId=113) at /home/max/digikam-1.2.0/libs/database/imagescanner.cpp:101 #13 0xb6586f74 in Digikam::CollectionScanner::scanNewFile (this=0xb00862b0, info=..., albumId=113) at /home/max/digikam-1.2.0/libs/database/collectionscanner.cpp:756 #14 0xb6587d4a in Digikam::CollectionScanner::scanAlbum (this=0xb00862b0, location=..., album=...) at /home/max/digikam-1.2.0/libs/database/collectionscanner.cpp:665 #15 0xb6587bcc in Digikam::CollectionScanner::scanAlbum (this=0xb00862b0, location=..., album=...) at /home/max/digikam-1.2.0/libs/database/collectionscanner.cpp:683 #16 0xb6587bcc in Digikam::CollectionScanner::scanAlbum (this=0xb00862b0, location=..., album=...) at /home/max/digikam-1.2.0/libs/database/collectionscanner.cpp:683 #17 0xb65889e7 in Digikam::CollectionScanner::scanAlbumRoot (this=0xb00862b0, location=...) at /home/max/digikam-1.2.0/libs/database/collectionscanner.cpp:479 #18 0xb6588d1f in Digikam::CollectionScanner::completeScan (this=0xb00862b0) at /home/max/digikam-1.2.0/libs/database/collectionscanner.cpp:250 #19 0x0832123e in Digikam::ScanController::run (this=0xa30daa8) at /home/max/digikam-1.2.0/digikam/scancontroller.cpp:541 #20 0xb4b01fbe in QThreadPrivate::start (arg=0xa30daa8) at thread/qthread_unix.cpp:248 #21 0xb43ba955 in start_thread () from /lib/i686/cmov/libpthread.so.0 #22 0xb4865e7e in clone () from /lib/i686/cmov/libc.so.6 Thread 1 (Thread 0xb23229a0 (LWP 11533)): #0 0xb77d2424 in __kernel_vsyscall () #1 0xb43bef7f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb4872e0d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6 #3 0xb4b02fb7 in QWaitConditionPrivate::wait (this=0xa3042fc, mutex=0xa3042e8, time=4294967295) at thread/qwaitcondition_unix.cpp:87 #4 QWaitCondition::wait (this=0xa3042fc, mutex=0xa3042e8, time=4294967295) at thread/qwaitcondition_unix.cpp:159 #5 0xb4b02051 in QThread::wait (this=0xa30daa8, time=4294967295) at thread/qthread_unix.cpp:619 #6 0x08322aa7 in Digikam::ScanController::shutDown (this=0xa30daa8) at /home/max/digikam-1.2.0/digikam/scancontroller.cpp:290 #7 0x08323241 in ~ScanController (this=0xa30daa8, __in_chrg=value optimized out) at /home/max/digikam-1.2.0/digikam/scancontroller.cpp:273 #8 0x083233fa in ~ScanControllerCreator () at /home/max/digikam-1.2.0/digikam/scancontroller.cpp:221 #9 destroy () at /home/max/digikam-1.2.0/digikam/scancontroller.cpp:222 #10 0xb47c92bf in ?? () from /lib/i686/cmov/libc.so.6 #11 0xb47c932f in exit () from /lib/i686/cmov/libc.so.6 #12 0xb1c45ef0 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #13 0xb5db960a in KApplication::xioErrhandler (this=0xbf9085c8, dpy=0xa1b4aa0) at ../../kdeui/kernel/kapplication.cpp:408 #14 0xb5db9646 in kde_xio_errhandler (dpy=0xa1b4aa0) at ../../kdeui/kernel/kapplication.cpp:125 #15 0xb45f8ee6
[Pkg-kde-extras] Bug#605452: digikam crashes after splash screen
I realize that I have not accurately described the manner in which digikam crashes. When I first encountered this problem I had reset the digikam configuration, but the old digikam database files were present. Since then, I have attempted to solve the problem by removing both the configuration files, as well as the database files. Now digikam still crashes, but in a slightly different manner than before: at first run digikam attempts to create a database, and after working through a few of the directories it crashes before completing the database. On subsequent runs the digikam splash screen appears quickly followed by a set of progress bars detailing its progress on creating the database, unfortunately it always crashes midway through. -Max ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#605452: digikam crashes after splash screen
Package: digikam Version: 2:1.2.0-7 Severity: important At first run digikam asks some configuration questions, after all of the questions are answered the application attempts to open, but fails. At every attempt to open the application, it simply crashes after the splash screen. here is a backtrace: Application: digiKam (digikam), signal: Segmentation fault [Current thread is 1 (Thread 0xb23229a0 (LWP 11533))] Thread 2 (Thread 0xb0086b70 (LWP 11534)): [KCrash Handler] #6 Exiv2::ValueTypeunsigned short::toLong (this=0xaf433698, n=0) at value.hpp:1580 #7 0xb6f67eb6 in KExiv2Iface::KExiv2::getImageOrientation() const () from /usr/lib/libkexiv2.so.8 #8 0xb68834e4 in Digikam::DMetadata::getMetadataField (this=0xb0085e2c, field=Digikam::MetadataInfo::Orientation) at /home/max/digikam-1.2.0/libs/dmetadata/dmetadata.cpp:1163 #9 0xb68852ff in Digikam::DMetadata::getMetadataFields (this=0xb0085e2c, fields=...) at /home/max/digikam-1.2.0/libs/dmetadata/dmetadata.cpp:1362 #10 0xb65d5fa9 in Digikam::ImageScanner::scanImageInformation (this=0xb0085e24) at /home/max/digikam-1.2.0/libs/database/imagescanner.cpp:275 #11 0xb65da798 in Digikam::ImageScanner::scanFile (this=0xb0085e24, mode=Digikam::ImageScanner::NewScan) at /home/max/digikam-1.2.0/libs/database/imagescanner.cpp:237 #12 0xb65da9ad in Digikam::ImageScanner::newFile (this=0xb0085e24, albumId=113) at /home/max/digikam-1.2.0/libs/database/imagescanner.cpp:101 #13 0xb6586f74 in Digikam::CollectionScanner::scanNewFile (this=0xb00862b0, info=..., albumId=113) at /home/max/digikam-1.2.0/libs/database/collectionscanner.cpp:756 #14 0xb6587d4a in Digikam::CollectionScanner::scanAlbum (this=0xb00862b0, location=..., album=...) at /home/max/digikam-1.2.0/libs/database/collectionscanner.cpp:665 #15 0xb6587bcc in Digikam::CollectionScanner::scanAlbum (this=0xb00862b0, location=..., album=...) at /home/max/digikam-1.2.0/libs/database/collectionscanner.cpp:683 #16 0xb6587bcc in Digikam::CollectionScanner::scanAlbum (this=0xb00862b0, location=..., album=...) at /home/max/digikam-1.2.0/libs/database/collectionscanner.cpp:683 #17 0xb65889e7 in Digikam::CollectionScanner::scanAlbumRoot (this=0xb00862b0, location=...) at /home/max/digikam-1.2.0/libs/database/collectionscanner.cpp:479 #18 0xb6588d1f in Digikam::CollectionScanner::completeScan (this=0xb00862b0) at /home/max/digikam-1.2.0/libs/database/collectionscanner.cpp:250 #19 0x0832123e in Digikam::ScanController::run (this=0xa30daa8) at /home/max/digikam-1.2.0/digikam/scancontroller.cpp:541 #20 0xb4b01fbe in QThreadPrivate::start (arg=0xa30daa8) at thread/qthread_unix.cpp:248 #21 0xb43ba955 in start_thread () from /lib/i686/cmov/libpthread.so.0 #22 0xb4865e7e in clone () from /lib/i686/cmov/libc.so.6 Thread 1 (Thread 0xb23229a0 (LWP 11533)): #0 0xb77d2424 in __kernel_vsyscall () #1 0xb43bef7f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb4872e0d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6 #3 0xb4b02fb7 in QWaitConditionPrivate::wait (this=0xa3042fc, mutex=0xa3042e8, time=4294967295) at thread/qwaitcondition_unix.cpp:87 #4 QWaitCondition::wait (this=0xa3042fc, mutex=0xa3042e8, time=4294967295) at thread/qwaitcondition_unix.cpp:159 #5 0xb4b02051 in QThread::wait (this=0xa30daa8, time=4294967295) at thread/qthread_unix.cpp:619 #6 0x08322aa7 in Digikam::ScanController::shutDown (this=0xa30daa8) at /home/max/digikam-1.2.0/digikam/scancontroller.cpp:290 #7 0x08323241 in ~ScanController (this=0xa30daa8, __in_chrg=value optimized out) at /home/max/digikam-1.2.0/digikam/scancontroller.cpp:273 #8 0x083233fa in ~ScanControllerCreator () at /home/max/digikam-1.2.0/digikam/scancontroller.cpp:221 #9 destroy () at /home/max/digikam-1.2.0/digikam/scancontroller.cpp:222 #10 0xb47c92bf in ?? () from /lib/i686/cmov/libc.so.6 #11 0xb47c932f in exit () from /lib/i686/cmov/libc.so.6 #12 0xb1c45ef0 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #13 0xb5db960a in KApplication::xioErrhandler (this=0xbf9085c8, dpy=0xa1b4aa0) at ../../kdeui/kernel/kapplication.cpp:408 #14 0xb5db9646 in kde_xio_errhandler (dpy=0xa1b4aa0) at ../../kdeui/kernel/kapplication.cpp:125 #15 0xb45f8ee6 in _XIOError () from /usr/lib/libX11.so.6 #16 0xb460021a in ?? () from /usr/lib/libX11.so.6 #17 0xb4600b96 in _XEventsQueued () from /usr/lib/libX11.so.6 #18 0xb45e966b in XEventsQueued () from /usr/lib/libX11.so.6 #19 0xb52f80a5 in x11EventSourceCheck (s=0xa1a5c40) at kernel/qguieventdispatcher_glib.cpp:87 #20 0xb41634a9 in g_main_context_check () from /lib/libglib-2.0.so.0 #21 0xb4163dde in ?? () from /lib/libglib-2.0.so.0 #22 0xb41641c8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #23 0xb4c2a075 in QEventDispatcherGlib::processEvents (this=0xa177e50, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #24 0xb52f7ed5 in QGuiEventDispatcherGlib::processEvents (this=0xa177e50, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #25 0xb4bfcae9 in QEventLoop::processEvents (this=0xa30b770, flags=) at
