Download an up-to-date CVS version of gphoto2 from their anonymous CVS and compile it. That fixed things for me (using a Canon digital camera, via USB, on 5-CURRENT). I came across this solution on the gphoto mailing lists; it is apparently a known problem with the current version. Arjan On Thursday 17 April 2003 22:10, Riccardo Torrini wrote: > On Thu, Apr 17, 2003 at 09:16:37PM +0200, Riccardo Torrini wrote: > > How it is supposed to work? I'm unable to access my CF (tryed also > > on 4.8-STABLE w/out success) and after recompiling world (29 march) > > also gphoto stopped to work. Something related to usb device? > > I forgot to say that I never tested this reader before, because I > luckily used gphoto2, I tryed this CF reader only because gphoto2 > start and immediatly core dump accessing my camera. > Can I (must?) fire up a PR for gphoto2? I don't know if it works > under 4.x tree... > > This happens every time. I'm running gphoto2 as root (as on previous > world of about late january). > > > (sorry for long lines) > > -----8<----- > Program received signal SIGSEGV, Segmentation fault. > 0x28243e4c in gp_filesystem_folder_number () from > /usr/local/lib/libgphoto2.so.2 (gdb) bt > #0 0x28243e4c in gp_filesystem_folder_number () from > /usr/local/lib/libgphoto2.so.2 #1 0x2824406f in > gp_filesystem_folder_number () from /usr/local/lib/libgphoto2.so.2 #2 > 0x28244f34 in gp_filesystem_list_folders () from > /usr/local/lib/libgphoto2.so.2 #3 0x2823e2ed in > gp_camera_folder_list_folders () from /usr/local/lib/libgphoto2.so.2 #4 > 0x08053592 in ?? () > #5 0x080530b5 in ?? () > #6 0x080506bf in ?? () > #7 0x282b0477 in invokeCallbacksOPTION () from /usr/local/lib/libpopt.so.0 > #8 0x282b1d35 in poptGetNextOpt () from /usr/local/lib/libpopt.so.0 > #9 0x08051dde in ?? () > #10 0x0804b3a5 in ?? () > (gdb) stop > -----8<-----Received on Thu Apr 17 2003 - 13:18:35 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:03 UTC