Version: 0.10.0-beta5 (using 4.1.2 (KDE 4.1.2), Mandriva Linux release 2009.0 (Official) for i586) Compiler: gcc OS: Linux (i686) release 2.6.27.4-desktop586-2mnb when attaching camera (with Digikam running) I cannot use the 'import / Cameras (Autodetected) / USB Vendor Specific Interface' option. Digikam Crashes. (this didn't crash in Beta3, but didn't work) I can use a manually added camera.
Created attachment 28650 [details] backtrace following crash
(copied from comment #1) Application: digiKam (digikam), signal SIGSEGV [Thread debugging using libthread_db enabled] [KCrash handler] #6 0xb6820657 in QString::fromLatin1_helper () from /usr/lib/libQtCore.so.4 #7 0xb682072e in QString::fromLatin1 () from /usr/lib/libQtCore.so.4 #8 0x0810133e in ?? () #9 0x0821b424 in ?? () #10 0x0822f6c4 in ?? () #11 0xb68e9c8d in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb68eaa95 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #13 0xb5f71785 in QActionGroup::triggered () from /usr/lib/libQtGui.so.4 #14 0xb5f72039 in ?? () from /usr/lib/libQtGui.so.4 #15 0xb5f72297 in QActionGroup::qt_metacall () from /usr/lib/libQtGui.so.4 #16 0xb68e9c8d in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #17 0xb68ea0bb in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #18 0xb5f6c9f5 in QAction::triggered () from /usr/lib/libQtGui.so.4 #19 0xb5f6d3e7 in QAction::activate () from /usr/lib/libQtGui.so.4 #20 0xb636a7c7 in ?? () from /usr/lib/libQtGui.so.4 #21 0xb636c96d in QMenu::keyPressEvent () from /usr/lib/libQtGui.so.4 #22 0xb76d8271 in KMenu::keyPressEvent () from /usr/lib/libkdeui.so.5 #23 0xb5fcd880 in QWidget::event () from /usr/lib/libQtGui.so.4 #24 0xb636d5e4 in QMenu::event () from /usr/lib/libQtGui.so.4 #25 0xb5f72fac in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #26 0xb5f7c367 in QApplication::notify () from /usr/lib/libQtGui.so.4 #27 0xb7607771 in KApplication::notify () from /usr/lib/libkdeui.so.5 #28 0xb68d4853 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #29 0xb5fd64dd in ?? () from /usr/lib/libQtGui.so.4 #30 0xb600c429 in ?? () from /usr/lib/libQtGui.so.4 #31 0xb600e73b in ?? () from /usr/lib/libQtGui.so.4 #32 0xb5fe63b1 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #33 0xb6010204 in ?? () from /usr/lib/libQtGui.so.4 #34 0xb52087ca in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #35 0xb520bee8 in ?? () from /usr/lib/libglib-2.0.so.0 #36 0xb520c0a8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #37 0xb690034a in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #38 0xb600f95a in ?? () from /usr/lib/libQtGui.so.4 #39 0xb68d2ec3 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #40 0xb68d3081 in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #41 0xb68d57f2 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #42 0xb5f72e14 in QApplication::exec () from /usr/lib/libQtGui.so.4 #43 0x0826009e in ?? () #44 0xb58875c5 in __libc_start_main () from /lib/i686/libc.so.6 #45 0x08083ea1 in _start ()
The complete backtrace can be found in bug #175597, with the backtrace provided here digikam objects lack debugging info, but it is clearly the same backtrace. *** This bug has been marked as a duplicate of bug 175597 ***
Fixed with bug 175597