Digikam started crashing
Locked
 
|
Just as the title says really. I'm using Slackware 11 rc2 with 2.6.15
kernel. Digikam version is 0.8.1 with kde 3.5.4 and my camera is a Fuji DX 10. I tried compiling digikam 0.9.0 beta1 r1 but it has the same problem. I downloaded 1 image ok but then it errored out on the 2nd. Since then it only manages to list folders ok. As soon as it lists files it crashes. I've also found that gphoto2 run from a term seg faults before it finishes downloading images. Backtrace from kde debugger: (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1248422176 (LWP 1932)] [New Thread -1257706576 (LWP 1959)] 0xb6354379 in __lll_mutex_lock_wait () from /lib/tls/libc.so.6 #0 0xb6354379 in __lll_mutex_lock_wait () from /lib/tls/libc.so.6 #1 0xb62e5a1b in _L_mutex_lock_3089 () from /lib/tls/libc.so.6 #2 0xbfc3a870 in ?? () #3 0xbfc3a648 in ?? () #4 0xb6268cd0 in ?? () from /usr/lib/./libstdc++.so.6 #5 0x08350a38 in ?? () #6 0x00000000 in ?? () -- Have an adequate day. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
On (18:50 21/08/06), David Woodfall <[hidden email]> put forth the proposition:
> Just as the title says really. I'm using Slackware 11 rc2 with 2.6.15 > kernel. > > Digikam version is 0.8.1 with kde 3.5.4 and my camera is a Fuji DX 10. I > tried compiling digikam 0.9.0 beta1 r1 but it has the same problem. I should add that I used Digikam successfully for several months and that this just happened today. > > I downloaded 1 image ok but then it errored out on the 2nd. Since then it > only manages to list folders ok. As soon as it lists files it crashes. I've > also found that gphoto2 run from a term seg faults before it finishes > downloading images. > > Backtrace from kde debugger: > > (no debugging symbols found) > Using host libthread_db library "/lib/tls/libthread_db.so.1". > (no debugging symbols found) > [Thread debugging using libthread_db enabled] > [New Thread -1248422176 (LWP 1932)] > [New Thread -1257706576 (LWP 1959)] > 0xb6354379 in __lll_mutex_lock_wait () from /lib/tls/libc.so.6 > #0 0xb6354379 in __lll_mutex_lock_wait () from /lib/tls/libc.so.6 > #1 0xb62e5a1b in _L_mutex_lock_3089 () from /lib/tls/libc.so.6 > #2 0xbfc3a870 in ?? () > #3 0xbfc3a648 in ?? () > #4 0xb6268cd0 in ?? () from /usr/lib/./libstdc++.so.6 > #5 0x08350a38 in ?? () > #6 0x00000000 in ?? () > -- > Have an adequate day. > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users -- Any sufficiently advanced bug is indistinguishable from a feature. -- Rich Kulawiec _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Using gdb supplies:
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1258751056 (LWP 6033)] 0xb61a263d in _int_malloc () from /lib/tls/libc.so.6 This is the same for digikam and gphoto2. Any ideas? On (19:19 21/08/06), David Woodfall <[hidden email]> put forth the proposition: > On (18:50 21/08/06), David Woodfall <[hidden email]> put forth the proposition: > > Just as the title says really. I'm using Slackware 11 rc2 with 2.6.15 > > kernel. > > > > Digikam version is 0.8.1 with kde 3.5.4 and my camera is a Fuji DX 10. I > > tried compiling digikam 0.9.0 beta1 r1 but it has the same problem. > > I should add that I used Digikam successfully for several months and that > this just happened today. > > > > > I downloaded 1 image ok but then it errored out on the 2nd. Since then it > > only manages to list folders ok. As soon as it lists files it crashes. I've > > also found that gphoto2 run from a term seg faults before it finishes > > downloading images. > > > > Backtrace from kde debugger: > > > > (no debugging symbols found) > > Using host libthread_db library "/lib/tls/libthread_db.so.1". > > (no debugging symbols found) > > [Thread debugging using libthread_db enabled] > > [New Thread -1248422176 (LWP 1932)] > > [New Thread -1257706576 (LWP 1959)] > > 0xb6354379 in __lll_mutex_lock_wait () from /lib/tls/libc.so.6 > > #0 0xb6354379 in __lll_mutex_lock_wait () from /lib/tls/libc.so.6 > > #1 0xb62e5a1b in _L_mutex_lock_3089 () from /lib/tls/libc.so.6 > > #2 0xbfc3a870 in ?? () > > #3 0xbfc3a648 in ?? () > > #4 0xb6268cd0 in ?? () from /usr/lib/./libstdc++.so.6 > > #5 0x08350a38 in ?? () > > #6 0x00000000 in ?? () > > -- > > Have an adequate day. > > > > _______________________________________________ > > Digikam-users mailing list > > [hidden email] > > https://mail.kde.org/mailman/listinfo/digikam-users > > -- > Any sufficiently advanced bug is indistinguishable from a feature. > -- Rich Kulawiec > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users -- When the speaker and he to whom he is speaks do not understand, that is metaphysics. -- Voltaire _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Digikam started crashing
|
|
On Monday 21 August 2006 23:24, David Woodfall wrote:
> Using gdb supplies: > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread -1258751056 (LWP 6033)] > 0xb61a263d in _int_malloc () from /lib/tls/libc.so.6 > > This is the same for digikam and gphoto2. Any ideas? Well, something witch common between digiKam and gphoto2 is broken in your computer (a shared library certainly)... Gilles Caulier > > On (19:19 21/08/06), David Woodfall <[hidden email]> put forth the proposition: > > On (18:50 21/08/06), David Woodfall <[hidden email]> put forth the proposition: > > > Just as the title says really. I'm using Slackware 11 rc2 with 2.6.15 > > > kernel. > > > > > > Digikam version is 0.8.1 with kde 3.5.4 and my camera is a Fuji DX 10. > > > I tried compiling digikam 0.9.0 beta1 r1 but it has the same problem. > > > > I should add that I used Digikam successfully for several months and that > > this just happened today. > > > > > I downloaded 1 image ok but then it errored out on the 2nd. Since then > > > it only manages to list folders ok. As soon as it lists files it > > > crashes. I've also found that gphoto2 run from a term seg faults before > > > it finishes downloading images. > > > > > > Backtrace from kde debugger: > > > > > > (no debugging symbols found) > > > Using host libthread_db library "/lib/tls/libthread_db.so.1". > > > (no debugging symbols found) > > > [Thread debugging using libthread_db enabled] > > > [New Thread -1248422176 (LWP 1932)] > > > [New Thread -1257706576 (LWP 1959)] > > > 0xb6354379 in __lll_mutex_lock_wait () from /lib/tls/libc.so.6 > > > #0 0xb6354379 in __lll_mutex_lock_wait () from /lib/tls/libc.so.6 > > > #1 0xb62e5a1b in _L_mutex_lock_3089 () from /lib/tls/libc.so.6 > > > #2 0xbfc3a870 in ?? () > > > #3 0xbfc3a648 in ?? () > > > #4 0xb6268cd0 in ?? () from /usr/lib/./libstdc++.so.6 > > > #5 0x08350a38 in ?? () > > > #6 0x00000000 in ?? () > > > -- > > > Have an adequate day. > > > > > > _______________________________________________ > > > Digikam-users mailing list > > > [hidden email] > > > https://mail.kde.org/mailman/listinfo/digikam-users > > > > -- > > Any sufficiently advanced bug is indistinguishable from a feature. > > -- Rich Kulawiec > > > > _______________________________________________ > > 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 (07:33 22/08/06), Gilles Caulier <[hidden email]> put forth the proposition:
> On Monday 21 August 2006 23:24, David Woodfall wrote: > > Using gdb supplies: > > > > Program received signal SIGSEGV, Segmentation fault. > > [Switching to Thread -1258751056 (LWP 6033)] > > 0xb61a263d in _int_malloc () from /lib/tls/libc.so.6 > > > > This is the same for digikam and gphoto2. Any ideas? > > Well, something witch common between digiKam and gphoto2 is broken in your > computer (a shared library certainly)... > > Gilles Caulier It turned out to be a badly formatted memory card on the camera. Thanks for your input though. > > > > > On (19:19 21/08/06), David Woodfall <[hidden email]> put forth the > proposition: > > > On (18:50 21/08/06), David Woodfall <[hidden email]> put forth the > proposition: > > > > Just as the title says really. I'm using Slackware 11 rc2 with 2.6.15 > > > > kernel. > > > > > > > > Digikam version is 0.8.1 with kde 3.5.4 and my camera is a Fuji DX 10. > > > > I tried compiling digikam 0.9.0 beta1 r1 but it has the same problem. > > > > > > I should add that I used Digikam successfully for several months and that > > > this just happened today. > > > > > > > I downloaded 1 image ok but then it errored out on the 2nd. Since then > > > > it only manages to list folders ok. As soon as it lists files it > > > > crashes. I've also found that gphoto2 run from a term seg faults before > > > > it finishes downloading images. > > > > > > > > Backtrace from kde debugger: > > > > > > > > (no debugging symbols found) > > > > Using host libthread_db library "/lib/tls/libthread_db.so.1". > > > > (no debugging symbols found) > > > > [Thread debugging using libthread_db enabled] > > > > [New Thread -1248422176 (LWP 1932)] > > > > [New Thread -1257706576 (LWP 1959)] > > > > 0xb6354379 in __lll_mutex_lock_wait () from /lib/tls/libc.so.6 > > > > #0 0xb6354379 in __lll_mutex_lock_wait () from /lib/tls/libc.so.6 > > > > #1 0xb62e5a1b in _L_mutex_lock_3089 () from /lib/tls/libc.so.6 > > > > #2 0xbfc3a870 in ?? () > > > > #3 0xbfc3a648 in ?? () > > > > #4 0xb6268cd0 in ?? () from /usr/lib/./libstdc++.so.6 > > > > #5 0x08350a38 in ?? () > > > > #6 0x00000000 in ?? () > > > > -- > > > > Have an adequate day. > > > > > > > > _______________________________________________ > > > > Digikam-users mailing list > > > > [hidden email] > > > > https://mail.kde.org/mailman/listinfo/digikam-users > > > > > > -- > > > Any sufficiently advanced bug is indistinguishable from a feature. > > > -- Rich Kulawiec > > > > > > _______________________________________________ > > > 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 -- Why is the alphabet in that order? Is it because of that song? _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Hi,
I had faced a digikam crash myself. This is the first time I am using the digikam and during the indexing process of photos by the digikam, there was a power fluctuation and the system rebooted. After the reboot, every time I open digikam, it crashes. I checked the backtrace and couldnt find much info from it. I checked the klog and it showed a broken pipe. Uninstalled and reinstalled digikam but the problem still persists. Attached is the log of the back trace and a screen shot of the klog. If anyone had faced this problem before and found a solution, then please pass it on. -- Regards, Riaz Ur Rahaman |
Screenshot.png (59K)
Re: Digikam started crashing
|
|
Hi,
On Thursday 24 August 2006 09:43, Riaz Rahaman wrote: > > After the reboot, every time I open digikam, it crashes. I > checked the backtrace and couldnt find much info from it. I > checked the klog and it showed a broken pipe. Well, the backtrace doesn't tell that much. But maybe some of your images got corrupted due to the power failure? To make sure, digikam itself is working: Can you try to cleanup your configuration? Move $HOME/.kde/share/config/digikamrc to some other place, maybe $HOME/.kde/share/apps/digikam, too. Than start digikam. It will think, that you start it the first time, and ask for you image archive. Enter a clean directory and add some images. If this is working well, either copy the rest of your images into this new archive, or change the archive setting to the old one. Good luck, Heiner -- heiner at heiner-lamprecht dot net GnuPG - Key: 9859E373 Fingerprint: 3770 7947 F917 94EF 8717 BADB 0139 7554 9859 E373 _______________________________________________ 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 |