Summary: | usb camera transfer hangs and works only the second time tried | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | simon |
Component: | Import-UMS | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | marcel.wiesweg |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 0.10.0 |
Description
simon
2008-11-20 14:02:06 UTC
Are you sure to use USB Mass Storage protocol ? Go to Camera Info dialog and look which driver you use. Gilles Caulier yes, i didn't set up a camera in digikam, just used the "usb storage devices" menu and selected "usb disk (DMX-LX2) at /media/disk-1 (1TB)" autodetection in the camera settings dialog also detects as a usb cam but uses "/" as mountpoint and fails also add the backtrace of the crash when closing digikam when it hangs during first usb access (gdb) bt #0 0x0000000000000001 in ?? () #1 0x00000000005cd4c0 in Digikam::DigikamApp::slotOpenSolidUsmDevice () #2 0x00000000005d64b4 in Digikam::DigikamApp::qt_metacall () #3 0x00007fdbba85526c in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #4 0x00007fdbb9b877af in QActionGroup::triggered () from /usr/lib64/qt4/libQtGui.so.4 #5 0x00007fdbb9b87a47 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #6 0x00007fdbb9b88150 in QActionGroup::qt_metacall () from /usr/lib64/qt4/libQtGui.so.4 #7 0x00007fdbba85526c in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4 #8 0x00007fdbb9b82c47 in QAction::triggered () from /usr/lib64/qt4/libQtGui.so.4 #9 0x00007fdbb9b83450 in QAction::activate () from /usr/lib64/qt4/libQtGui.so.4 #10 0x00007fdbb9f147dd in ?? () from /usr/lib64/qt4/libQtGui.so.4 #11 0x00007fdbbbc60371 in KMenu::mouseReleaseEvent () from /usr/lib64/libkdeui.so.5 #12 0x00007fdbb9bd59f5 in QWidget::event () from /usr/lib64/qt4/libQtGui.so.4 #13 0x00007fdbb9f12771 in QMenu::event () from /usr/lib64/qt4/libQtGui.so.4 #14 0x00007fdbb9b892be in QApplicationPrivate::notify_helper () from /usr/lib64/qt4/libQtGui.so.4 #15 0x00007fdbb9b8e2cc in QApplication::notify () from /usr/lib64/qt4/libQtGui.so.4 #16 0x00007fdbbbb9707b in KApplication::notify () from /usr/lib64/libkdeui.so.5 #17 0x00007fdbba8412c8 in QCoreApplication::notifyInternal () from /usr/lib64/qt4/libQtCore.so.4 #18 0x00007fdbb9b8b551 in QApplicationPrivate::sendMouseEvent () from /usr/lib64/qt4/libQtGui.so.4 #19 0x00007fdbb9beb603 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #20 0x00007fdbb9bea273 in QApplication::x11ProcessEvent () from /usr/lib64/qt4/libQtGui.so.4 #21 0x00007fdbb9c0df45 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #22 0x00007fdbba840645 in QEventLoop::processEvents () from /usr/lib64/qt4/libQtCore.so.4 #23 0x00007fdbba8407a8 in QEventLoop::exec () from /usr/lib64/qt4/libQtCore.so.4 #24 0x00007fdbba8424ce in QCoreApplication::exec () from /usr/lib64/qt4/libQtCore.so.4 #25 0x000000000060e353 in main () Sound like a problem in Solid interface. Marcel ? Gilles Caulier SVN commit 887378 by mwiesweg: Fix Solid signal connection, so that the event loop can be ended when the device is mounted. Polish capacity display in Import menu. CCBUG: 175662 M +8 -8 digikamapp.cpp M +1 -1 digikamapp.h WebSVN link: http://websvn.kde.org/?view=rev&revision=887378 works like a charm now and also displays the correct capacity - my sdcard shrinked to only 2GG instead of 1TB ;) |