digikam crash
Locked
 
|
I have just installed a fresh Digikam on my Fedora 7 system (I was
using it a while ago on Slackware) and am trying to use it with my new Fujifilm S800FD camera. First signs were good, the camera is detected as a PTP one and it even transferred the pictures from it. However that's where things went downhill, I tried to copy a picture from the camera and digikam crashed. Here is the output on the terminal where I was running digikam:- home$ digikam kbuildsycoca running... DCOP Cleaning up dead connections. Found dcraw version: 8.60 QImage::pixel: x=0 out of range File 'DSCF0001.JPG' is not readable. File 'DSCF0044.JPG' is not readable. File 'DSCF0044.JPG' is not readable. File 'DSCF0044.JPG' is not readable. File 'DSCF0044.JPG' is not readable. File 'DSCF0044.JPG' is not readable. File 'DSCF0044.JPG' is not readable. File 'DSCF0044.JPG' is not readable. QFile::open: No file name specified QFile::open: No file name specified Exif Orientation: 1 KCrash: Application 'digikam' crashing... Could not find 'drkonqi' executable. KCrash cannot reach kdeinit, launching directly. home$ ICE default IO error handler doing an exit(), pid = 27020, errno = 0 Here is the output of "digikam -v" :- Qt: 3.3.8 KDE: 3.5.8-7.fc7 Fedora digiKam: 0.9.2-final When I re-run digikam it fails to connect to the camera any more. I'll restart everything and have another go. -- Chris Green _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Hi Chris,
On Sat, 17 Nov 2007, Chris G wrote: > I have just installed a fresh Digikam on my Fedora 7 system (I was > using it a while ago on Slackware) and am trying to use it with my new > Fujifilm S800FD camera. > > First signs were good, the camera is detected as a PTP one and it even > transferred the pictures from it. > > However that's where things went downhill, I tried to copy a picture > from the camera and digikam crashed. > > Here is the output on the terminal where I was running digikam:- > > home$ digikam > kbuildsycoca running... > DCOP Cleaning up dead connections. > Found dcraw version: 8.60 > QImage::pixel: x=0 out of range > File 'DSCF0001.JPG' is not readable. > File 'DSCF0044.JPG' is not readable. > File 'DSCF0044.JPG' is not readable. > File 'DSCF0044.JPG' is not readable. > File 'DSCF0044.JPG' is not readable. > File 'DSCF0044.JPG' is not readable. > File 'DSCF0044.JPG' is not readable. > File 'DSCF0044.JPG' is not readable. > QFile::open: No file name specified > QFile::open: No file name specified > Exif Orientation: 1 > KCrash: Application 'digikam' crashing... > Could not find 'drkonqi' executable. > KCrash cannot reach kdeinit, launching directly. > home$ ICE default IO error handler doing an exit(), pid = 27020, errno = 0 > > > Here is the output of "digikam -v" :- > > Qt: 3.3.8 > KDE: 3.5.8-7.fc7 Fedora > digiKam: 0.9.2-final > > > When I re-run digikam it fails to connect to the camera any more. > I'll restart everything and have another go. Well, digikam shouldn't crash in the first place. Still, it seems not unlikely, that this is already a problem of accessing the camera, for which gphoto is used. Could you try the following commands and report their output: 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 and post the output here. Thanks a lot in advance, Arnd _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
On Sat, Nov 17, 2007 at 04:10:49PM +0100, Arnd Baecker wrote:
> Hi Chris, > > On Sat, 17 Nov 2007, Chris G wrote: > > > I have just installed a fresh Digikam on my Fedora 7 system (I was > > using it a while ago on Slackware) and am trying to use it with my new > > Fujifilm S800FD camera. > > > > First signs were good, the camera is detected as a PTP one and it even > > transferred the pictures from it. > > > > However that's where things went downhill, I tried to copy a picture > > from the camera and digikam crashed. > > > > Here is the output on the terminal where I was running digikam:- > > > > home$ digikam > > kbuildsycoca running... > > DCOP Cleaning up dead connections. > > Found dcraw version: 8.60 > > QImage::pixel: x=0 out of range > > File 'DSCF0001.JPG' is not readable. > > File 'DSCF0044.JPG' is not readable. > > File 'DSCF0044.JPG' is not readable. > > File 'DSCF0044.JPG' is not readable. > > File 'DSCF0044.JPG' is not readable. > > File 'DSCF0044.JPG' is not readable. > > File 'DSCF0044.JPG' is not readable. > > File 'DSCF0044.JPG' is not readable. > > QFile::open: No file name specified > > QFile::open: No file name specified > > Exif Orientation: 1 > > KCrash: Application 'digikam' crashing... > > Could not find 'drkonqi' executable. > > KCrash cannot reach kdeinit, launching directly. > > home$ ICE default IO error handler doing an exit(), pid = 27020, errno = 0 > > > > > > Here is the output of "digikam -v" :- > > > > Qt: 3.3.8 > > KDE: 3.5.8-7.fc7 Fedora > > digiKam: 0.9.2-final > > > > > > When I re-run digikam it fails to connect to the camera any more. > > I'll restart everything and have another go. > > Well, digikam shouldn't crash in the first place. > Still, it seems not unlikely, that this is already > a problem of accessing the camera, for which gphoto is used. > > Could you try the following commands and report their output: > a) connect camera, what is the output of dmesg > (only the camera related part) usb 5-1: new full speed USB device using uhci_hcd and address 5 usb 5-1: configuration #1 chosen from 1 choice > b) gphoto2 -v Copyright (c) 2000-2006 Lutz Mueller and others gphoto2 comes with NO WARRANTY, to the extent permitted by law. You may redistribute copies of gphoto2 under the terms of the GNU General Public License. For more information about these matters, see the files named COPYING. This version of gphoto2 is using the following software versions and options: gphoto2 2.3.1 gcc, popt(m), exif, no cdk, no aa, jpeg, readline libgphoto2 2.3.1 gcc, no ltdl, EXIF libgphoto2_port 0.7.1 gcc, no ltdl, USB, serial baudboy locking > c) gphoto2 --list ports It takes a *long* time and then Devices found: 4 Path Description -------------------------------------------------------------- ptpip: PTP/IP Connection usb: Universal Serial Bus usb:005,005 Universal Serial Bus usb:003,004 Universal Serial Bus > d) gphoto2 --auto-detect -L Same long delay (almost 30 seconds) and then Path Description -------------------------------------------------------------- ptpip: PTP/IP Connection usb: Universal Serial Bus usb:005,005 Universal Serial Bus usb:003,004 Universal Serial Bus home$ gphoto2 --auto-detect -L Model Port ---------------------------------------------------------- USB PTP Class Camera usb: USB PTP Class Camera usb:005,005 There is no file in folder '/'. There is no file in folder '/store_00010001'. There is no file in folder '/store_00010001/DCIM'. There are 53 files in folder '/store_00010001/DCIM/100_FUJI'. #1 DSCF0001.JPG 1911 KB 3264x2448 image/jpeg #2 DSCF0002.JPG 1878 KB 3264x2448 image/jpeg #3 DSCF0003.JPG 1823 KB 3264x2448 image/jpeg #4 DSCF0004.JPG 1728 KB 3264x2448 image/jpeg #5 DSCF0005.JPG 1766 KB 3264x2448 image/jpeg #6 DSCF0006.JPG 1680 KB 3264x2448 image/jpeg #7 DSCF0007.JPG 1725 KB 3264x2448 image/jpeg #8 DSCF0008.JPG 1900 KB 3264x2448 image/jpeg #9 DSCF0009.JPG 1883 KB 3264x2448 image/jpeg #10 DSCF0010.JPG 1873 KB 3264x2448 image/jpeg #11 DSCF0011.JPG 1882 KB 3264x2448 image/jpeg #12 DSCF0012.JPG 1893 KB 3264x2448 image/jpeg #13 DSCF0013.JPG 1790 KB 3264x2448 image/jpeg #14 DSCF0014.JPG 1917 KB 3264x2448 image/jpeg #15 DSCF0015.JPG 1904 KB 3264x2448 image/jpeg #16 DSCF0016.JPG 1683 KB 3264x2448 image/jpeg #17 DSCF0017.JPG 1901 KB 3264x2448 image/jpeg #18 DSCF0018.JPG 1887 KB 3264x2448 image/jpeg #19 DSCF0019.JPG 1864 KB 3264x2448 image/jpeg #20 DSCF0020.JPG 1916 KB 3264x2448 image/jpeg #21 DSCF0021.JPG 1731 KB 3264x2448 image/jpeg #22 DSCF0022.JPG 1909 KB 3264x2448 image/jpeg #23 DSCF0023.JPG 1774 KB 3264x2448 image/jpeg #24 DSCF0024.JPG 1958 KB 3264x2448 image/jpeg #25 DSCF0025.JPG 1842 KB 3264x2448 image/jpeg #26 DSCF0026.JPG 1698 KB 3264x2448 image/jpeg #27 DSCF0027.JPG 1822 KB 3264x2448 image/jpeg #28 DSCF0028.JPG 1782 KB 3264x2448 image/jpeg #29 DSCF0029.JPG 1893 KB 3264x2448 image/jpeg #30 DSCF0030.JPG 1799 KB 3264x2448 image/jpeg #31 DSCF0031.JPG 1735 KB 3264x2448 image/jpeg #32 DSCF0032.JPG 1956 KB 3264x2448 image/jpeg #33 DSCF0033.JPG 1801 KB 3264x2448 image/jpeg #34 DSCF0034.JPG 1769 KB 3264x2448 image/jpeg #35 DSCF0035.JPG 1764 KB 3264x2448 image/jpeg #36 DSCF0036.JPG 1817 KB 3264x2448 image/jpeg #37 DSCF0037.JPG 1796 KB 3264x2448 image/jpeg #38 DSCF0038.JPG 1740 KB 3264x2448 image/jpeg #39 DSCF0039.JPG 1857 KB 3264x2448 image/jpeg #40 DSCF0040.JPG 1747 KB 3264x2448 image/jpeg #41 DSCF0041.JPG 1911 KB 3264x2448 image/jpeg #42 DSCF0042.JPG 1936 KB 3264x2448 image/jpeg #43 DSCF0043.JPG 1926 KB 3264x2448 image/jpeg #44 DSCF0044.JPG 1907 KB 3264x2448 image/jpeg #45 DSCF0045.JPG 1685 KB 3264x2448 image/jpeg #46 DSCF0046.JPG 1833 KB 3264x2448 image/jpeg #47 DSCF0047.JPG 1914 KB 3264x2448 image/jpeg #48 DSCF0048.JPG 1764 KB 3264x2448 image/jpeg #49 DSCF0049.JPG 1864 KB 3264x2448 image/jpeg #50 DSCF0050.JPG 1658 KB 3264x2448 image/jpeg #51 DSCF0051.JPG 1755 KB 3264x2448 image/jpeg #52 DSCF0052.JPG 1841 KB 3264x2448 image/jpeg #53 DSCF0053.JPG 1875 KB 3264x2448 image/jpeg > e) gphoto2 --abilities Abilities for camera : USB PTP Class Camera Serial port support : no USB support : yes Capture choices : : Capture not supported by the driver Configuration support : yes Delete selected files on camera : yes Delete all files on camera : no File preview (thumbnail) support : yes File upload support : yes > f) gphoto2 --list-folders There is 1 folder in folder '/'. - store_00010001 There is 1 folder in folder '/store_00010001'. - DCIM There is 1 folder in folder '/store_00010001/DCIM'. - 100_FUJI There are 0 folders in folder '/store_00010001/DCIM/100_FUJI'. All the gphoto2 commands have the long delay of almost 30 seconds before the response comes back, is this normal? By the way when I restarted everything it found the camera again (obviously from the above gphoto2 results) and I transferred the pictures successfully by transferring the all to a new album. After a bit of mucking around I have found what actions cause the crash, it's when you display a selected picture and then click on "Save As", immediate crash. -- Chris Green _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
On Sat, Nov 17, 2007 at 03:45:14PM +0000, Chris G wrote:
> After a bit of mucking around I have found what actions cause the > crash, it's when you display a selected picture and then click on > "Save As", immediate crash. > Just to confirm this, the crash occurs when you have selected a picture direct from the camera (i.e. not from an album), click on "View" to get it in the Image Editor and then select "Save As". Once it has crashed you need to disconnect the camra and reconnect it before digikam can see it again. -- Chris Green _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Hi Chris,
On Sat, 17 Nov 2007, Chris G wrote: > On Sat, Nov 17, 2007 at 03:45:14PM +0000, Chris G wrote: > > After a bit of mucking around I have found what actions cause the > > crash, it's when you display a selected picture and then click on > > "Save As", immediate crash. > > > Just to confirm this, the crash occurs when you have selected a > picture direct from the camera (i.e. not from an album), click on > "View" to get it in the Image Editor and then select "Save As". > > Once it has crashed you need to disconnect the camra and reconnect it > before digikam can see it again. it could be related (or the same) as http://bugs.kde.org/show_bug.cgi?id=134391 http://bugs.kde.org/show_bug.cgi?id=149364 In particular the second one had to be closed because there was no further input. Would you be able to build the current version from svn and activate the debug output? If the crash is still there with the current version, this would hopefully allow us to track that beast down ... Installation instructions are at: http://www.digikam.org/?q=download/svn in particular below "Install digiKam in your Home Directory" To enable debugging, see http://www.digikam.org/?q=contrib under the heading "If you are experiencing crashes with digiKam". Many thanks in advance, Arnd _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
On Sat, Nov 17, 2007 at 05:22:56PM +0100, Arnd Baecker wrote:
> Hi Chris, > > On Sat, 17 Nov 2007, Chris G wrote: > > > On Sat, Nov 17, 2007 at 03:45:14PM +0000, Chris G wrote: > > > After a bit of mucking around I have found what actions cause the > > > crash, it's when you display a selected picture and then click on > > > "Save As", immediate crash. > > > > > Just to confirm this, the crash occurs when you have selected a > > picture direct from the camera (i.e. not from an album), click on > > "View" to get it in the Image Editor and then select "Save As". > > > > Once it has crashed you need to disconnect the camra and reconnect it > > before digikam can see it again. > > it could be related (or the same) as > http://bugs.kde.org/show_bug.cgi?id=134391 > http://bugs.kde.org/show_bug.cgi?id=149364 > > In particular the second one had to be closed because there > was no further input. > > Would you be able to build the current version from svn > and activate the debug output? > If the crash is still there with the current version, > this would hopefully allow us to track that beast down ... > > Installation instructions are at: http://www.digikam.org/?q=download/svn > in particular below "Install digiKam in your Home Directory" > To enable debugging, see http://www.digikam.org/?q=contrib under the > heading "If you are experiencing crashes with digiKam". > and ./configure runs OK and it compiles, but at link time:- /usr/lib/libexpat.so: could not read symbols: File in wrong format collect2: ld returned 1 exit status make[1]: *** [lib] Error 1 make[1]: Leaving directory `/home/chris/tmp/digikam/exiv2-svn/src' make: *** [all] Error 2 Is this an issue with my system being a 64-bit system? BTW the file format is:- home$ file /usr/lib/libexpat.so /usr/lib/libexpat.so: symbolic link to `../../lib/libexpat.so.0.5.0' home$ file /lib/libexpat.so.0.5.0 /lib/libexpat.so.0.5.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), stripped home$ -- Chris Green _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Arnd Baecker
Hi Chris,
concerning the exiv2 compile problem: Did you install the libexpat devel package? (Presumably yes, because otherwise configure would have complained). Independent of this this sounds like a 64 Bit compatibility problem. Maybe there is 64 Bit libexpat which you could install? I suggest to ask on the exiv2 mailing list, see http://www.exiv2.org/support.html Sorry that you have to go through this just to see whether the bug is gone or to get a proper backtrace. Still it would be a big help for us to get a backtrace so that this problem has a chance to be fixed once and for all... Best, Arnd _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
On Sun, Nov 18, 2007 at 05:12:12PM +0100, Arnd Baecker wrote:
> Hi Chris, > > concerning the exiv2 compile problem: > Did you install the libexpat devel package? > (Presumably yes, because otherwise configure would > have complained). > Independent of this this sounds like a 64 Bit compatibility problem. > Maybe there is 64 Bit libexpat which you could install? > > I suggest to ask on the exiv2 mailing list, see > http://www.exiv2.org/support.html > > Sorry that you have to go through this just to see > whether the bug is gone or to get a proper backtrace. > Still it would be a big help for us to get a backtrace > so that this problem has a chance to be fixed once and for all... > family around and I've had a little too much wine! :-) -- Chris Green _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |