Version: 0.81 (using KDE KDE 3.5.0) Installed from: Gentoo Packages Compiler: Reading specs from /usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.4/specs Configured with: /var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/configure --prefix=/usr --bindir=/usr/powerpc-unknown-linux-gnu/gcc-bin/3.4.4 --includedir=/usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.4/include --datadir=/usr/share/gcc-data/powerpc-unknown-linux-gnu/3.4.4 --mandir=/usr/share/gcc-data/powerpc-unknown-linux-gnu/3.4.4/man --infodir=/usr/share/gcc-data/powerpc-unknown-linux-gnu/3.4.4/info --with-gxx-include-dir=/usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.4/include/g++-v3 --host=powerpc-unknown-linux-gnu --build=powerpc-unknown-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --disable-libunwind-exceptions --disable-multilib --disable-libgcj --enable-languages=c,c++,f77 --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu Thread model: posix gcc version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8) OS: Linux I can only see thumbnails from the images but not the entire images. I get no error message, but performing operations different from edit/view I obtain a wrong format error. I use a Canon Digital IXUS and Gentoo GNU/Linux for PPC. Could it be a little endian/big endian problem? I must note that I can edit/view some images, but I can't do the same for the most of them. I believed it was a problem with EXIF, but it isn't the case since after the last upload (from the camera) I get the same error on ever picture. Now I think that I can see in digikam (and showFoto) only the pictures I modified with some other apps (like kview or gimp). In each other kde component I can see entire images.
I have the same problem. Digikam Image Viewer/showfoto 0.8.1 will not display .jpeg or .png images. You should raise this to critical, because almost all digital camera images are in JPEG format. Without the ability to display JPEG images, digikam is pretty much useless. There are no error messages. But it does display .gif, .ico. I can see .bmp but the don't look correct when compared to the thumbnail. I'm using Slackware 10.2, Linux 2.4.32 kernel.
Using the previous version of digikam (0.7.4-r2 in the Gentoo repository) I can edit and show images (jpg, png and anything else) also if I get worse performances while loading them.
The bug is in the 0.8.1 version of digikam/showfoto. Ibs is correct that version 0.7.4 works fine, I also have no problem with version 0.8.0. But nonetheless, the bug report is for version 0.8.1. Has any developer noticed this problem?
YEs, we have any report about this problem. The current implementation in 'stable' svn branch have been fixed normally. Can you check it please ? Gilles Caulier
I tried the version under svn and it has the same problem! Something happened between version 0.8.0 and 0.8.1 that caused JPEG/PNG images not to be read correctly. I suspect a problem between digikam and imlib2 because when I ran the svn digikam (pre 0.8.2) at printed an imlib2 read error message at the command line.
I'm sure that there is a problem in 0.8.1 about JPEG/RAW detection. I have fixed that. Your report want just mean that we have more than 1 problem. Please give me the console backtrace when you start digikam from the command line. This is what you can try : - Update imlib2. - Trying digikam from trunk branch (0.9.0-alpha). imlib2 have been removed but JPEG/RAW file detection is the same. Nota : here i can reproduce this problem. I develop digikam under MAndriva 2006 and PC intel 32 bits. Gilles Caulier
This is what I get (digikam 0.8.2-svn): James@2znsp01:~/svn/graphics/digikam/digikam$ ./digikam digikam: ScanLib: Finding non-existing Albums: 9 ms digikam: ScanLib: Finding items not in the database or disk: 161 ms digikam: ScanLib: Updating items without date: 0 ms QPainter::begin: Cannot paint null pixmap QPainter::setPen: Will be reset by begin() QPainter::setBrush: Will be reset by begin() QPainter::setBrush: Will be reset by begin() QPainter::setPen: Will be reset by begin() QPainter::end: Missing begin() or begin() failed KIPI (loading): KIPI::PluginLoader: plugin KameraKlient is in the ignore list for host application KIPI (loading): Plugin_JPEGLossless plugin loaded KIPI (loading): KIPI::PluginLoader: Loaded plugin JPEGLossless KIPI (loading): Plugin_CDArchiving plugin loaded KIPI (loading): KIPI::PluginLoader: Loaded plugin CDArchiving KIPI (loading): Plugin_Imagesgallery plugin loaded KIPI (loading): KIPI::PluginLoader: Loaded plugin ImagesGallery KIPI (loading): Plugin_SendImages plugin loaded KIPI (loading): KIPI::PluginLoader: Loaded plugin SendImages KIPI (loading): Plugin_FlickrExport plugin loaded KIPI (loading): KIPI::PluginLoader: Loaded plugin FlickrExport KIPI (loading): Loaded Plugin_Calendar KIPI (loading): KIPI::PluginLoader: Loaded plugin Calendar KIPI (loading): Plugin_Mpegencoder plugin loaded KIPI (loading): KIPI::PluginLoader: Loaded plugin MPEGEncoder KIPI (loading): Plugin_AcquireImages plugin loaded KIPI (loading): KIPI::PluginLoader: Loaded plugin AcquireImages KIPI (loading): Plugin_GalleryExport plugin loaded KIPI (loading): KIPI::PluginLoader: Loaded plugin GalleryExport KIPI (loading): Plugin_TimeAdjust plugin loaded KIPI (loading): KIPI::PluginLoader: Loaded plugin TimeAdjust KIPI (loading): Plugin_FindImages plugin loaded KIPI (loading): KIPI::PluginLoader: Loaded plugin FindImages KIPI (loading): Plugin_PrintWizard plugin loaded KIPI (loading): KIPI::PluginLoader: Loaded plugin PrintWizard KIPI (loading): Plugin_WallPaper plugin loaded KIPI (loading): KIPI::PluginLoader: Loaded plugin WallPaper KIPI (loading): Plugin_SlideShow plugin loaded KIPI (loading): KIPI::PluginLoader: Loaded plugin SlideShow KIPI (loading): Plugin_BatchProcessImages plugin loaded KIPI (loading): KIPI::PluginLoader: Loaded plugin BatchProcessImages KIPI (loading): Loaded RawConverter KIPI (loading): KIPI::PluginLoader: Loaded plugin RawConverter digikam: ImagePlugin_Core plugin loaded digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Core digikam: WARNING: /home/James/Pictures/Test/iss011e05019.jpg : Failed to load image using imlib2: error number: 4
This is not the JPEG/RAW detection problem. I suspect an internal problem in your system. Please, send me your JPEG image to confirm. Also, if you can test the digikam trunk branch from svn... Gilles Caulier
using showfoto (with the version that comes with the svn checkout) alone I can show and edit the images I wasnt able to see before. But with this version of digikam I can't view entire albums since digikamalbums protocol is unknown to my system. I paste the bug I get, also if it isn't related to the original post. excuse me if it's in italian, I think it is easily understandable however. digikam: ERROR: : couldn't create slave : Impossibile creare un io-slave: klauncher ha detto: Protocollo "digikamalbums" sconosciuto. digikam: digikam: WARNING: Failed to list url: Impossibile avviare il processo Impossibile creare un io-slave: klauncher ha detto: Protocollo "digikamalbums" sconosciuto.
This problem have been already reported in B.K.O. I suspect an installation problem. Typicaly, digiKam kioslave haven't installed at the right place in your system. About JPEG/RAW files detection, because the code is the same between stable and trunk branch, we can say that the 0.8.2-svn problem isn't relevant of this code, but certainly depending of a wrong imlib2 installation (or something like that). Have you installed the imlib2 image file loader modules package ? Gilles Caulier
I have tried the version available on the svn (that's the branch I can get using the script on your website). This time I get an error message while I load any album, and it involves a kioslave/schema: digikam: ERROR: : couldn't create slave : Impossibile creare un io-slave: klauncher ha detto: Protocollo "digikamalbums" sconosciuto. digikam: digikam: WARNING: Failed to list url: Impossibile avviare il processo Impossibile creare un io-slave: klauncher ha detto: Protocollo "digikamalbums" sconosciuto. excuse me for pasting it in italian. It does mean that the protocol digikamalbums is unknown, and that's impossible to create an adequate kioslave. I can't try the funcionality for which I posted the bug because it's inaccessible. Gilles Caulier wrote: [bugs.kde.org quoted mail] Created an attachment (id=15008) iago.vcf
I tried the 0.9.0svn version and I can successfully load JPEG (as well as PNG) images again! Hooray! I don't think there was anything wrong with my imlib2 installation as I could successfully load JPEG images with 0.7.4 and 0.8.0 versions of digikam. Only with 0.8.1 and 0.8.2svn did I have the JPEG load image problems.
Ok for the 0.9.0svn version. ...But can you confirm that the problem still again in 0.8.2svn (updating from a fresh svn checkout) ? ...because the file format detection implementation is the same between 0.8.2svn and 0.9.0svn... Gilles Caulier
No, for me the 0.8.2svn has the same JPEG load image problem that I saw with 0.8.1. When you click on one of the images in the album just a black screen pops up with 0x0 (i.e. 0x0 pixel size image) in the bottom corner. When run from the command line I see only the message: Failed to load image using imlib2: error number: 4. I find this odd, because I didn't rebuild imlib2 yet the svn version under trunk 0.9.0svn worked fine. As does 0.8.0 and 0.7.4.
I had the same problems on Suse 10.0 - KDE 3.5.3 I tried digikam 0.7.4 (from the Suse DVD) : worked digikam 0.8.1-1.pm1 form Packman : did not work digikam 0.8.1-22.6 from Suse : did not work During the check of imlib2 with Suse's YAST tool, it showed me that an update was available on Packman but only for the 'imlib2-loaders' lib although both the installed and the new one had the same name, size and date !!! I followed YAST proposition and updated this lib -> it works now... imlib2-loaders 1.2.2-0.pm.0 Regards Thomas
If i following your actions under Suse, To update the right imlib2-loader package solve the digiKam problem! right ? Gilles Caulier
Yes, both Digikam packages 0.8.1-1.pm1 from Packman and 0.8.1-22.6 from Suse work fine now. This seems to be the perfect programmer nightmare : the origin of the bug in the imlib2-loaders lib seems logical as this lib is used to open the various formats of image files, but the fact that all displayed informations belonging to these imlib2-loaders libs were equal is not at all. I dont know which other criteria is used by YAST to suggest an update. Thomas
ok. I can close this file in this case... Note : after to release digiKam 0.8.2, the next digiKam version (0.9.0 from trunk) will don't use imlib2 library. This problem will never appear in the future. Thanks for your investigations Gilles Caulier