| Summary: | Crash during initial camera auto detect | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | William Bixby <wbixby> |
| Component: | Import-Gphoto2 | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | 0.9.0 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
gphoto22.lst
gphoto2.lst |
||
|
Description
William Bixby
2007-02-12 06:05:17 UTC
thius is a problem in the avahi mdns compat libraries. as workaround remove the ptpip.so from /usr/lib/libgphoto2_port/2.2..... Thanks for the feedback. removing the Shared library worked (I'm 64 bit, so it was in lib64) However, now when the window comes up to connect to the camera there are no images displayed, If I browse 'storage media' for the USB camera I also do not see the images. I'm on a new installation of Suse 10.2 with avahi 6.5. I found 6.15 in Suse Factory ready for Suse 10.3 and installed that. Now I can connect to the camera WITH the ptpop.so library, but still no images to browse. On Monday 12 February 2007 10:19 am, Marcus Meissner wrote: [bugs.kde.org quoted mail] Hi William, could you try with digikam 0.9.2 and see if things are better now? Somehow it sounds more of a gphoto problem, so could you try the commands to list and download the images just using the gphoto2 command-line application? Also gtkam might be another option. Many thanks for any feedback, Arnd On Tuesday 26 June 2007 3:57 am, Arnd Baecker wrote: [bugs.kde.org quoted mail] Installed digikam 0.9.2 RPM for SUSE 10.2, x64_86 from the packman repository. Same result. Camera can be detected OK w/o a crash, but no images appear. gphoto2 at the command line - debug shows images detected but unable to download the image data. Two debug log files attached. Command #1 created gphoto2.lst: Bill@Bill:~> gphoto2 --auto-detect -P -n --debug --debug-logfile gphoto2.lst Model Port ---------------------------------------------------------- Canon EOS 400D (PTP mode) usb: Number of files in folder '/': 0 Command #2 created gphoto22.lst: Bill@Bill:~> gphoto2 --auto-detect -L -n --debug --debug-logfile gphoto22.lst Model Port ---------------------------------------------------------- Canon EOS 400D (PTP mode) usb: There is no file in folder '/'. There is no file in folder '/store_00000001'. Number of files in folder '/': 0 Command #3 w/o a debug log: Bill@Bill:~> gphoto2 --auto-detect -l -n Model Port ---------------------------------------------------------- Canon EOS 400D (PTP mode) usb: There is 1 folder in folder '/'. - store_00000001 There are 0 folders in folder '/store_00000001'. Number of files in folder '/': 0 Created an attachment (id=20979) gphoto22.lst Created an attachment (id=20980) gphoto2.lst Hi William, thanks a lot for the information - according to gphoto2.lst you have gphoto2 2.3.1.2.trunk which looks pretty recent ;-), but maybe not recent enough for the 400D, see this gphoto2 bug: https://sourceforge.net/tracker/?func=detail&atid=108874&aid=1722091&group_id=8874 So the PTP commands have changed from 350D to 400D and in the link, Marcus Meissner writes: > Date: 2007-06-09 06:37 > capture is working in current SVN. > > configuration is pending. So with the svn version of gphoto2 things *might* work to some extent BTW, have you tried the other mode (forgot the name) - you can change this in the settings of the camera? In any case, digikam should not crash, but lead to a nice warning with a description of the steps to do, to debug the problem ... Best, Arnd just to clarify: Detection and Download from a EOS 400D should work fine as-is. the gphoto bugreport is only about tethered capture. But I see the problem, the EOS 400D is also affected by the "wrong parent" bug. I have flagged it in current libgphoto2 SVN. I added the change and put the new libgphoto2 into the openSUSE buildservice, available in some minutes/hours in: http://software.opensuse.org/download/GPhoto/ ok, sorry, wasn't reading carefully enough. (but obviously it was the pointer in the right direction so that you could help out ;-) - thanks a lot!) On Wednesday 27 June 2007 3:10 am, Marcus Meissner wrote: [bugs.kde.org quoted mail] Installed the new gphoto2 and libgphoto. Works Great! Results from the CLI: Bill@Bill:~> gphoto2 --auto-detect -L -n --debug --debug-logfile gphoto2_Jun27.lst Model Port ---------------------------------------------------------- Canon EOS 400D (PTP mode) usb: There is no file in folder '/'. There is no file in folder '/store_00000001'. There is no file in folder '/store_00000001/DCIM'. There are 4 files in folder '/store_00000001/DCIM/900CANON'. #1 IMG_2022.JPG 3573 KB 3888x2592 image/jpeg #2 IMG_2023.JPG 3633 KB 3888x2592 image/jpeg #3 IMG_2024.JPG 3203 KB 3888x2592 image/jpeg #4 IMG_2025.JPG 3158 KB 3888x2592 image/jpeg Number of files in folder '/': 0 Bill@Bill:~> gphoto2 --auto-detect -P -n --debug --debug-logfile gphoto2_Jun27A.lst Model Port ---------------------------------------------------------- Canon EOS 400D (PTP mode) usb: Downloading 'IMG_2022.JPG' from folder '/store_00000001/DCIM/900CANON'... Saving file as IMG_2022.JPG Downloading 'IMG_2023.JPG' from folder '/store_00000001/DCIM/900CANON'... Saving file as IMG_2023.JPG Downloading 'IMG_2024.JPG' from folder '/store_00000001/DCIM/900CANON'... Saving file as IMG_2024.JPG Downloading 'IMG_2025.JPG' from folder '/store_00000001/DCIM/900CANON'... Saving file as IMG_2025.JPG Number of files in folder '/': 0 Bill@Bill:~> This is good news! Thanks for testing this out.
In principle we could close this bug now, but in my opinion:
> In any case, digikam should not crash,
> but lead to a nice warning with a description
> of the steps to do, to debug the problem ...
Question to the developers: is there a way to fetch such a crash
and come up with a warning instead?
Arnd, Certainly... and it must work as well of course. Do not close this file, i will take a look why camera gui crash in these conditions... Gilles William, Can you give me a fresh backtrace of digiKam crash using last stable 0.9.2 ? I would to solve this issue... Gilles Unable to reproduce the crash with 0.9.2. On Wednesday 22 August 2007 3:31 am, Gilles Caulier wrote: [bugs.kde.org quoted mail] William, Are you updated too libgphoto2 ? Arnd, Without a backtrace, it's not possible to hack what it's wrong in digiKam Gphoto2 interface. We close this file ? Gilles Gilles, yes, closing this one as FIXED. Because it works now (which is good ;-) there is nothing which can be done at this point. However, I would suspect that something like this will come up again at some point and with a proper backtrace it will be possible to find out the origin of the problem. Arnd |