Bug 137958 - 0.9rc1crashes (SIGABRT) when i try to connect to camera (PowerShot G6)
Summary: 0.9rc1crashes (SIGABRT) when i try to connect to camera (PowerShot G6)
Status: RESOLVED NOT A BUG
Alias: None
Product: digikam
Classification: Applications
Component: Import-Gphoto2 (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-27 10:47 UTC by Wilbert Berendsen
Modified: 2017-08-16 06:11 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wilbert Berendsen 2006-11-27 10:47:49 UTC
Version:           0.9.0-rc1 (using KDE 3.5.5, Gentoo)
Compiler:          gcc version 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)
OS:                Linux (i686) release 2.6.16-gentoo-r2

Digikam crashes with signal 6 (SIGABRT) when I start the camera dialog. The camera window appears for a very short time, but then Digikam crashes. A small backtrace is produced by drKonqi, I hope it's useful.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1245341504 (LWP 31959)]
[New Thread -1256735840 (LWP 32119)]
0xb6041277 in pthread_mutex_lock () from /lib/libpthread.so.0
#0  0xb6041277 in pthread_mutex_lock () from /lib/libpthread.so.0
#1  0xb6995843 in QRecursiveMutexPrivate::lock (this=0x80667e8)
    at qmutex_unix.cpp:235
#2  0xb6995d80 in QMutex::lock (this=0x807e598) at qmutex_unix.cpp:464
#3  0xb7dd6266 in QMutexLocker (this=0x806680c, m=0xb6c887f0) at qmutex.h:96
#4  0xb65f8a27 in QApplication::sendPostedEvents (receiver=0x0, event_type=70)
    at qapplication.cpp:3209
#5  0xb65f89f1 in QApplication::sendPostedEvents (receiver=0x0, event_type=0)
    at qapplication.cpp:3203
#6  0xb65f89b8 in QApplication::sendPostedEvents () at qapplication.cpp:3181
#7  0xb6592286 in QEventLoop::processEvents (this=0x80873b0, flags=4)
    at qeventloop_x11.cpp:144
#8  0xb660fb09 in QEventLoop::enterLoop (this=0x80873b0) at qeventloop.cpp:198
#9  0xb660fa24 in QEventLoop::exec (this=0x80873b0) at qeventloop.cpp:145
#10 0xb65f7de9 in QApplication::exec (this=0xbfd24370)
    at qapplication.cpp:2758
#11 0x0804a916 in main (argc=134637580, argv=0x806680c) at main.cpp:269
Comment 1 caulier.gilles 2006-11-27 11:54:31 UTC
Wilbert, 

It's not reproductible here. Are you using Gphoto2 drivers or mount your camera like an UMS ?

Can you start digiKam under gdb and get a backtrace. Look into HACKING file for details.

Thanks in advance.

Gilles Caulier
Comment 2 caulier.gilles 2006-12-12 09:22:35 UTC
Wilbert,

This crash still reproductible using digiKam/DigikamImagePlugins 0.9.0-RC2, Exiv2 0.12, and a fresh update of libgphoto2 ?

Thanks in advance for your feedback.

Gilles Caulier
Comment 3 Arnd Baecker 2007-06-01 18:29:39 UTC
I would suggest to close this bug 
(and other bugs where the original poster
does not respond over such a long period -
Already closing two weeks after an enquiry would be OK in my opinion, as
the bug can always we re-opened)
Comment 4 caulier.gilles 2007-06-01 19:16:24 UTC
Right Arnd,

No need to full B.K.O with unresolvable files (:=)))

Gilles