Hi,
Running 0.9.3 under KDE 3.5.8 on FreeBSD 6.3 When I connect my Canon EOS400D (PTP Mode) the OS reports it as: ugen0: Canon Inc. Canon Digital Camera, rev 2.00/0.02, addr 2 In digikam I connect to the camera, the camera window opens, displays "Connecting to camera", 'BUSY' appears on the camera LCD screen and the read/write LED flashes. Digikam then displays "Listing Folders....". When digikam has finished, there are no thumbnails displayed but the following appears in the console: digikam: Failed to get folders list from camera! digikam: Libgphoto2 error: Unspecified error (-1) Then, when I click 'Close' in the camera window in digikam, this appears in the console and digikam dies on a SIGSEGV: KCrash: Application 'digikam' crashing... Everything worked OK in 0.9.1 (with the same OS version). The following library versions are being used: libgphoto2 2.4.0 kipi-plugins 0.1.4 exiv2 0.14 lcms 1.17 dcraw 8.81 Can anyone suggest the reason for this? The problem appears to be with libgphoto according to the error message. Regards, Mark _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
2008/1/20, Mark Ovens <[hidden email]>: Gilles CaulierHi, But certainly not the same libgphoto2 version. digiKam do not have camera drivers. GPhoto2 is used for that... Accordingly with reports in this room and in bugzilla, I have seen than libgphoto2 2.4.0 Canon drivers become unstable... I don't have a Canon camera (Minolta Dynax 5D) _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Gilles Caulier wrote:
> But certainly not the same libgphoto2 version. > > digiKam do not have camera drivers. GPhoto2 is used for that... > > Accordingly with reports in this room and in bugzilla, I have seen than > libgphoto2 2.4.0 Canon drivers become unstable... > > I don't have a Canon camera (Minolta Dynax 5D) > Thanks Gilles, I thought that libgphoto would be the problem. It would have been v2.3.1 of libgphoto with digikam 0.9.2 (0.9.1 was a typo in my original post). Will 0.9.3 build/run with version 2.3.1 of libgphoto2 ? Regards, Mark _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Sun, 20 Jan 2008, Mark Ovens wrote:
> Gilles Caulier wrote: > > But certainly not the same libgphoto2 version. > > > > digiKam do not have camera drivers. GPhoto2 is used for that... > > > > Accordingly with reports in this room and in bugzilla, I have seen than > > libgphoto2 2.4.0 Canon drivers become unstable... > > > > I don't have a Canon camera (Minolta Dynax 5D) > > > > Thanks Gilles, I thought that libgphoto would be the problem. It would > have been v2.3.1 of libgphoto with digikam 0.9.2 (0.9.1 was a typo in my > original post). > > Will 0.9.3 build/run with version 2.3.1 of libgphoto2 ? It should (I even only have gphoto2 ver 2.2., because I download images via card-reader). The other option is to ask on the gphoto2 mailing list, after testing the following steps a) connect camera, what is the output of dmesg (only the camera related part) b) gphoto2 -v c) gphoto2 --list ports d) gphoto2 --auto-detect -L e) gphoto2 --abilities f) gphoto2 --list-folders In addition you might try to compile the current svn version of gphoto2 and see if it works better and only then proceed with installing digikam from source... Best, Arnd _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Arnd Baecker wrote:
> On Sun, 20 Jan 2008, Mark Ovens wrote: > >> Will 0.9.3 build/run with version 2.3.1 of libgphoto2 ? > > It should (I even only have gphoto2 ver 2.2., because > I download images via card-reader). > > The other option is to ask on the gphoto2 mailing list, > after testing the following steps > a) connect camera, what is the output of dmesg > (only the camera related part) > b) gphoto2 -v > c) gphoto2 --list ports > d) gphoto2 --auto-detect -L > e) gphoto2 --abilities > f) gphoto2 --list-folders > > In addition you might try to compile the current svn version of gphoto2 > and see if it works better and only then proceed with installing > digikam from source... > Thanks Arnd. I ran all those commands and it all works OK - no errors, and all files/folders listed. I think that I will try 2.3.1 first. Regards, Mark _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Sun, 20 Jan 2008, Mark Ovens wrote:
> Arnd Baecker wrote: > > On Sun, 20 Jan 2008, Mark Ovens wrote: > > > >> Will 0.9.3 build/run with version 2.3.1 of libgphoto2 ? > > > > It should (I even only have gphoto2 ver 2.2., because > > I download images via card-reader). > > > > The other option is to ask on the gphoto2 mailing list, > > after testing the following steps > > a) connect camera, what is the output of dmesg > > (only the camera related part) > > b) gphoto2 -v > > c) gphoto2 --list ports > > d) gphoto2 --auto-detect -L > > e) gphoto2 --abilities > > f) gphoto2 --list-folders > > > > In addition you might try to compile the current svn version of gphoto2 > > and see if it works better and only then proceed with installing > > digikam from source... > > > > Thanks Arnd. I ran all those commands and it all works OK - no errors, > and all files/folders listed. > > I think that I will try 2.3.1 first. Hmm, but if the above works, then I am surprised that it does not work from within digikam. Anyway, maybe 2.3.1 does the job, but it is a bit of work to get everything compiled - good luck! Best, Arnd _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Arnd Baecker wrote:
> Hmm, but if the above works, then I am surprised that > it does not work from within digikam. That's what I thought. > Anyway, maybe 2.3.1 does the job, but it is > a bit of work to get everything compiled - good luck! > Well, I actually installed 2.2.1 rather than 2.3.1 and, as with 2.4.0, the gphoto command line functions all worked, except that it identified the camera as "PTP/IP Camera" rather than by name (possibly because the 400D was not available when 2.2.1 was released?). So, in digikam I had to use PTP/IP rather than EOS 400D and exactly the same thing happened, except that digikam didn't crash with a SIGSEGV when I closed the Camera window. Error in console after trying to List Folders: digikam: Failed to get folders list from camera! digikam: Libgphoto2 error: Unspecified error (-1) So it does appear that the problem is in digikam - or maybe the interaction between digikam and gphoto? I can't see it being an OS-related problem as I haven't updated the OS since 27/10/2007 and I was definitely getting photos off the camera after that date. Any ideas? Could I reinstall digikam 0.9.2 or am I likely to have problems with differences in the database? Regards, Mark _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Gilles Caulier-4
Gilles Caulier wrote:
> > > 2008/1/20, Mark Ovens <[hidden email] > <mailto:[hidden email]>>: > > > Everything worked OK in 0.9.1 (with the same OS version). > > > But certainly not the same libgphoto2 version. > Just a follow up to this. It is quite possible that I _was_ running 0.9.2 with gphoto 2.4.0. I've looked at the CVS logs for the FreeBSD Ports tree to check when things got updated. gphoto got updated to 2.4.0 on 2007/8/13 and although digikam was already at 0.9.2 then, digikam had the _port_ version bumped due to various library updates on 2007/09/18. I don't keep local build/install logs but I use several tools to keep all installed ports up to date that I run usually once a week at least so it is almost certain that digikam would have been rebuilt and reinstalled even though it was the same version of digikam. This may explain why 0.9.3 doesn't work with gphoto 2.2.1 either (see my reply to Arnd). Regards, Mark _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Mark Ovens-2
Gilles/Arnd,
Some more info. I rebuilt gphoto2 with debug logging (--enable-debug arg to configure) and now when I run gphoto2 --debug-logfile=logfile.log --debug --auto-detect -L it puts a lot of useful info into the logfile. Unfortunately I can't figure out how to enable this when called from digikam. I rebuilt digikam after rebuilding gphoto2 and now, although I still get the error digikam: Failed to get folders list from camera! digikam: Libgphoto2 error: Unspecified error (-1) digikam doesn't crash when I close the camera window. Any idea how to enable gphoto2 logging from digikam? Regards, Mark _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Gilles/Arnd,
OK, I've done some debugging and found where it's failing. digikam calls gp_camera_folder_list_folders() in GPCamera::getSubFolders() In gphoto, gp_camera_folder_list_folders() calls gp_filesystem_list_folders() in the macro CHECK_RESULT_OPEN_CLOSE CHECK_RESULT_OPEN_CLOSE (camera, gp_filesystem_list_folders ( camera->fs, folder, list, context), context); gp_filesystem_list_folders() calls fs->folder_list_func() here: CR (fs->folder_list_func (fs, folder, list, fs->list_data, context)); The folder_list_func() that is called is in camlibs/ptp2/library.c Is camlibs/ptp2 not for generic PTP cameras? As mine is a known camera, should it not be calling folder_list_func() in camlibs/canon/library.c??? Anyway, the place where it dies in in the call to ptp_getstorageids() here: PTPStorageIDs storageids; if (ptp_operation_issupported(params,PTP_OC_GetStorageIDs)) { fprintf(stderr, ">> 2\n"); CPR (context, ptp_getstorageids(params, &storageids)); fprintf(stderr, ">> Returned from ptp_getstorageids()\n"); for (i=0; i<storageids.n; i++) { char fname[PTP_MAXSTRLEN]; The fprintf()'s are my debug and it never gets to the second one. This is the output I see in the console: CHECK_NULL (camera && folder && list) CHECK_INIT (camera, context) CR (camera, gp_list_reset (list), context) CHECK_RESULT_OPEN_CLOSE (camera, gp_filesystem_list_folders (camera->fs, folder, list, context), context) In gp_filesystem_list_folders In gp_filesystem_list_folders - CHECK_NULL (fs && folder && list) In gp_filesystem_list_folders - CC (context) In gp_filesystem_list_folders - CA (folder, context) In gp_filesystem_list_folders - gp_list_reset In gp_filesystem_list_folders - CR (x = gp_filesystem_folder_number (fs, folder, context)) In gp_filesystem_list_folders - CR (fs->folder_list_func (fs, folder, list,fs->list_data, context) In ptp2/library.c:folder_list_func() > 1 >> 2 digikam: Failed to get folders list from camera! digikam: Libgphoto2 error: Unspecified error (-1) If it should be calling the folder_list_func() in canon/library.c instead of ptp2/library.c does this mean that digikam is passing incorrect argumants to gphoto? Regards, Mark _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Mark Ovens wrote:
> Gilles/Arnd, > > OK, I've done some debugging and found where it's failing. > [snip] Should have tried this before posting.... I ran ``gphoto2 --auto-detect -L'' from the commandline with my debug messages in and that too uses ptp2/library.c so I guess it is correct. However, it does return from ptp_getstorageids(): /usr/ports/graphics/digikam{119}# gphoto2 --auto-detect -L Model Port ---------------------------------------------------------- Canon EOS 400D (PTP mode) usb: There is no file in folder '/'. CHECK_NULL (camera && folder && list) CHECK_INIT (camera, context) CR (camera, gp_list_reset (list), context) CHECK_RESULT_OPEN_CLOSE (camera, gp_filesystem_list_folders (camera->fs, folder, list, context), context) In gp_filesystem_list_folders In gp_filesystem_list_folders - CHECK_NULL (fs && folder && list) In gp_filesystem_list_folders - CC (context) In gp_filesystem_list_folders - CA (folder, context) In gp_filesystem_list_folders - gp_list_reset In gp_filesystem_list_folders - CR (x = gp_filesystem_folder_number (fs, folder, context)) In gp_filesystem_list_folders - CR (fs->folder_list_func (fs, folder, list,fs->list_data, context) In ptp2/library.c:folder_list_func() > 1 >> 2 >> Returned from ptp_getstorageids() Regards, Mark _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Mark Ovens-2
I've now reinstalled digikam 0.9.2 and it works fine there - even with
v2.4.0 of gphoto2 - so it definitely appears to be a bug in 0.9.3 I've created bug 156420 for this - http://bugs.kde.org/show_bug.cgi?id=156420 If there's anything I can do to help track this down let me know. I really need to do a debug build but the FreeBSD Ports system doesn't make that easy so can anyone tell me how to make a debug build on FreeBSD outside the Ports? Regards, Mark _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Mark Ovens-2
Am Montag, 21. Januar 2008 23:09:56 schrieb Mark Ovens:
Hi Mark, I just wanted to assure you that it's not a camera problem - I also have a 400D and it's working fine here, both with 0.9.2 and the current svn. Hope this helps you in tracking down the problem, best, Gandalf > Mark Ovens wrote: > > Gilles/Arnd, > > > > OK, I've done some debugging and found where it's failing. > > [snip] > > Should have tried this before posting.... > > I ran ``gphoto2 --auto-detect -L'' from the commandline with my debug > messages in and that too uses ptp2/library.c so I guess it is correct. > > However, it does return from ptp_getstorageids(): > > /usr/ports/graphics/digikam{119}# gphoto2 --auto-detect -L > Model Port > ---------------------------------------------------------- > Canon EOS 400D (PTP mode) usb: > There is no file in folder '/'. > CHECK_NULL (camera && folder && list) > CHECK_INIT (camera, context) > CR (camera, gp_list_reset (list), context) > CHECK_RESULT_OPEN_CLOSE (camera, gp_filesystem_list_folders (camera->fs, > folder, list, context), context) > In gp_filesystem_list_folders > In gp_filesystem_list_folders - CHECK_NULL (fs && folder && list) > In gp_filesystem_list_folders - CC (context) > In gp_filesystem_list_folders - CA (folder, context) > In gp_filesystem_list_folders - gp_list_reset > In gp_filesystem_list_folders - CR (x = gp_filesystem_folder_number (fs, > folder, context)) > In gp_filesystem_list_folders - CR (fs->folder_list_func (fs, folder, > list,fs->list_data, context) > In ptp2/library.c:folder_list_func() > > > 1 > > > >> 2 > >> Returned from ptp_getstorageids() > > Regards, > > Mark > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Gandalf Lechner wrote:
> Am Montag, 21. Januar 2008 23:09:56 schrieb Mark Ovens: > > Hi Mark, > > I just wanted to assure you that it's not a camera problem - I also have a > 400D and it's working fine here, both with 0.9.2 and the current svn. Hope > this helps you in tracking down the problem, > Thanks Gandalf. Have you tried it with 0.9.3? I've tried building the svn but it fails on FreeBSD - this seems to be common, need to tweak it for FreeBSD. Regards, Mark _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On 1/22/08, Mark Ovens <[hidden email]> wrote: Gandalf Lechner wrote: Mark, I have the 400D and tried it for the first time today, with excellent results. digiKam 0.9.3 (Using KDE 3.5.8) Using Kipi library version 0.1.5 Using KExiv2 livrary version 0.1.6 Using Exiv2 library version 0.15 Using KDcraw library version 0.1.3 Using Dcraw program version 8.81 Using PNG library version 1.2.15beta5 Using Gphoto2 library version 2.4.0 All running on Debian "etch" with "lenny" ports for the most part. cheers, Ben Moore _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Mark Ovens-2
On Tue, 22 Jan 2008, Mark Ovens wrote:
> I've now reinstalled digikam 0.9.2 and it works fine there - even with > v2.4.0 of gphoto2 - so it definitely appears to be a bug in 0.9.3 > > I've created bug 156420 for this - > http://bugs.kde.org/show_bug.cgi?id=156420 > > If there's anything I can do to help track this down let me know. I > really need to do a debug build but the FreeBSD Ports system doesn't > make that easy so can anyone tell me how to make a debug build on > FreeBSD outside the Ports? I don't know FreeBSD, but usually you will have to compile everything from source, and enable debugging for each package. See: http://www.digikam.org/?q=download/svn ("Install digiKam in your Home Directory") together with http://www.digikam.org/?q=contrib "If you are experiencing crashes with digiKam" HTH, Arnd _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Mark Ovens-2
On Tue, 22 Jan 2008, Mark Ovens wrote:
> Gandalf Lechner wrote: > > Am Montag, 21. Januar 2008 23:09:56 schrieb Mark Ovens: > > > > Hi Mark, > > > > I just wanted to assure you that it's not a camera problem - I also have a > > 400D and it's working fine here, both with 0.9.2 and the current svn. Hope > > this helps you in tracking down the problem, > > > > Thanks Gandalf. Have you tried it with 0.9.3? > > I've tried building the svn but it fails on FreeBSD - this seems to be > common, need to tweak it for FreeBSD. Hmm. If you have a patch to make it compile on FreeBSD (and still on the other OSs ;-), it would make sense to apply it to svn - or what do you think Gilles? Best, Arnd _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Mark Ovens-2
Am Mittwoch, 23. Januar 2008 00:15:45 schrieb Mark Ovens:
> Gandalf Lechner wrote: > > Am Montag, 21. Januar 2008 23:09:56 schrieb Mark Ovens: > > > > Hi Mark, > > > > I just wanted to assure you that it's not a camera problem - I also have > > a 400D and it's working fine here, both with 0.9.2 and the current svn. > > Hope this helps you in tracking down the problem, > > Thanks Gandalf. Have you tried it with 0.9.3? I'm not a 100% sure, but I think I had it also working with 0.9.3. On my laptop I still have 0.9.2 because of compilation issues I haven't solved up to now (there seems to be no kubuntu package yet). But on my desktop computer, where I now have the svn version, I had 0.9.3 before. Actually, I used it only for a quite short period before switching to svn ;-) - but I think I downloaded pictures from my 400D during these days. Best, Gandalf > I've tried building the svn but it fails on FreeBSD - this seems to be > common, need to tweak it for FreeBSD. > > Regards, > > Mark > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Gandalf Lechner wrote:
> I'm not a 100% sure, but I think I had it also working with 0.9.3. On my > laptop I still have 0.9.2 because of compilation issues I haven't solved > up to now (there seems to be no kubuntu package yet). > > But on my desktop computer, where I now have the svn version, I had 0.9.3 > before. Actually, I used it only for a quite short period before switching > to svn ;-) - but I think I downloaded pictures from my 400D during these > days. OK, thanks. This, plus Ben Moore's post it seems that it must be a build issue on FreeBSD. I'll post in the FreeBSD Ports mailing list about it. Thanks for everyone's help. Regards, Mark _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Arnd Baecker
Arnd Baecker wrote:
> I don't know FreeBSD, but usually you will have > to compile everything from source, and enable debugging for each package. > See: > http://www.digikam.org/?q=download/svn > ("Install digiKam in your Home Directory") > together with > http://www.digikam.org/?q=contrib > "If you are experiencing crashes with digiKam" > OK, I've built a debug version of 0.9.3, but it doesn't seem to produce a core file and if I run it from within gdb then gdb itself core dumps (and does produce a core file): /home/mark{102}# gdb /usr/local/bin/digikam GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"... (gdb) run Starting program: /usr/local/bin/digikam Segmentation fault (core dumped) /home/mark{103}# If I start digikam normally, the KDE Crash Handler catches it but displays this message: This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. Segmentation fault (core dumped) and I can't find a core file (does the KDE Crash Handler delete it because it is of no use?). The binary is definitely a debug version: /home/mark{104}# file /usr/local/bin/digikam /usr/local/bin/digikam: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked (uses shared libs), not stripped Also, if I start digikam, then attach gdb to it, gdb dumps core when loading the symbols for libexiv2. I rebuilt libexiv2 (with debug) but the same happens: (gdb) attach 14711 Attaching to program: /usr/local/bin/digikam, process 14711 Reading symbols from /usr/local/lib/libdigikam.so.0...done. Loaded symbols for /usr/local/lib/libdigikam.so.0 Reading symbols from /usr/local/lib/libsqlite3.so.8...done. Loaded symbols for /usr/local/lib/libsqlite3.so.8 Reading symbols from /usr/local/lib/libkabc.so.3...done. Loaded symbols for /usr/local/lib/libkabc.so.3 Reading symbols from /usr/local/lib/libvcard.so.0...done. Loaded symbols for /usr/local/lib/libvcard.so.0 Reading symbols from /usr/local/lib/libkresources.so.3...done. Loaded symbols for /usr/local/lib/libkresources.so.3 Reading symbols from /usr/local/lib/libkhtml.so.6...done. Loaded symbols for /usr/local/lib/libkhtml.so.6 Reading symbols from /usr/local/lib/libkjs.so.3...done. Loaded symbols for /usr/local/lib/libkjs.so.3 Reading symbols from /usr/local/lib/libpcreposix.so.0...done. Loaded symbols for /usr/local/lib/libpcreposix.so.0 Reading symbols from /usr/local/lib/libpcre.so.0...done. Loaded symbols for /usr/local/lib/libpcre.so.0 Reading symbols from /usr/local/lib/libthai.so.0...done. Loaded symbols for /usr/local/lib/libthai.so.0 Reading symbols from /usr/local/lib/libkipi.so.1...done. Loaded symbols for /usr/local/lib/libkipi.so.1 Reading symbols from /usr/local/lib/libkutils.so.3...done. Loaded symbols for /usr/local/lib/libkutils.so.3 Reading symbols from /usr/local/lib/libjasper.so.4...done. Loaded symbols for /usr/local/lib/libjasper.so.4 Reading symbols from /usr/local/lib/libkexiv2.so.3...done. Loaded symbols for /usr/local/lib/libkexiv2.so.3 Reading symbols from /usr/local/lib/libexiv2.so.0...Segmentation fault (core dumped) Is this a clue as to the root of the problem? Regards, Mark _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |