Bug 175662 - usb camera transfer hangs and works only the second time tried
Summary: usb camera transfer hangs and works only the second time tried
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Import-UMS (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-20 14:02 UTC by simon
Modified: 2020-08-26 03:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 0.10.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description simon 2008-11-20 14:02:06 UTC
Version:           0.10.0-beta6 (using 4.1.80 (KDE 4.1.80 (KDE 4.2 Beta1)), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.26-tuxonice

i'm trying to connect my lumix lx2 in usb mode and have a problem here:

when plugged in kde detects the camera ok and offers to do something with the new device. i select "do nothing" here

in digicam i select "import" | "usb mass storege devices" (second menu item) and then the "usb disk ..."

then digikam just hangs and i have to kill digikam and restart it.
now i can access the camera with the same proceeding as above.
Comment 1 caulier.gilles 2008-11-20 14:05:37 UTC
Are you sure to use USB Mass Storage protocol ? Go to Camera Info dialog and look which driver you use.

Gilles Caulier
Comment 2 simon 2008-11-20 14:22:07 UTC
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
Comment 3 simon 2008-11-20 18:41:57 UTC
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 ()
Comment 4 caulier.gilles 2008-11-20 18:47:39 UTC
Sound like a problem in Solid interface. Marcel ?

Gilles Caulier
Comment 5 Marcel Wiesweg 2008-11-21 19:41:19 UTC
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
Comment 6 simon 2008-11-21 22:19:00 UTC
works like a charm now and also displays the correct capacity - my sdcard shrinked to only 2GG instead of 1TB ;)