Version: 0.9.3-rc1 (using KDE 3.5.8, Kubuntu (gutsy) 4:3.5.8-0ubuntu3.1) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.22-14-rt When I view an image in the image viewer (tools menu) and change it's size using a right click the image is incorrect. It is only in the lower left corner and has a blurred look in the rest of it. I will attach a screenshot. This has been present for a month or longer (since about when I changed to Gutsy).
Created attachment 22559 [details] screenshot to demonstrate image viewer problem
I think this is the kipi simple viewer at work, right? Which kipi library version are you using (See under "Help/About digikam: About")? I am running 0.1.5 and don't see the problem.
I'm using SVN from yesterday (digikam, kipi libs, exiv2): Kipi 0.1.6, KExiv2 0.1.7, exiv2 0.16-pre1, kdcraw 0.1.3. Not sure if it the simple viewer or not. It shows up under Tools > Image Viewer. If I disable "Kipi Simple Viewer Plugin" in Settings > Configure Digikam the Image Viewer is still there. I noticed that not all pictures have this issue, but most do. Could it be related to file or dimensions size??? Two test pictures are here: http://bacon.no-ip.info/digikam/ IMG_0701-full.JPG = original that has the problem IMG_0701-small.jpg = does not have the problem, resized from original Geoff
Geoff, with your first image I can reproduce the problem (thanks a lot, this is very helpful!). Weird: somehow it first briefly shows the correctly scaled image and then the strange picture as in your screenshot. ((Also I cannot zoom in with +, because pressing SHIFT already triggers the help ..., but that's a different bug ;-)) And: yes, you are right, it is not the simple viewer, but kipi-plugins/imageviewer, because the message about "stopwatch:" is defined there. Note sure what is responsible for the scaling, but it could even be some OpenGL issue then. The code was written by Markus Leuthold, whom I added in CC, most likely he has an idea how to address the issue.
Hi Arnd, Geoff. What video card do you use? Proprietary or opensource driver? I already had a bugreport about this problem with Intel hardware. Unfortunately, I cannot reproduce with my Nvidia card. This looks like a driver issue to me, but I'll investigate further Arnd, thanks for the "SHIFT" bug. I'll address that too
As far as i can say mine is intel on x86_64, and i have that problem Cheers, Angelo
Mine is the intel chip on the motherboard. I think this is a i915. I used to have a nvidia card in this computer a couple months ago, which worked fine. Section "Device" Identifier "Intel Video" Driver "intel" BusID "PCI:0:2:0" Option "UseFBDev" "true" EndSection
Here it is Section "Device" Identifier "Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller" Driver "i810" BusID "PCI:0:2:0" Option "MonitorLayout" "CRT,LFP" Option "Clone" EndSection This is on debian etch. dpkg -l | grep i810 shows: xserver-xorg-video-i810 1.7.2-4 with xserver-xorg 7.1.0-19
Geoff, This file still valid using kipi-plugins 0.1.6 ? Gilles Caulier
Sorry, but I cannot specifically test kipi-plugins 0.1.6 right now on the computer that has this problem. That computer the "intel" video driver and runs the ubuntu packages for digikam 0.9.3. There are no problems on the KDE4 version of digikam and with a nvidia card.
Geoff, Under KDE4, are you installed kipi-plugins with digiKam ? I ask this question because ImageViewer is a plugin, and i need to know if you have tested it as well before to close this file as resolved with KDE4 port... Gilles Caulier
Yes - For KDE4 I have installed the kipi-plugins with digiKam from SVN. The thinking before was that this was related to the video driver so I don't know if this would still affect the KDE3 or KDE4 versions with an "intel" or "i810" video driver. I will upgrade the system running KDE3 digikam (with intel) and test again, but may take a few days. Geoff
Gilles, I just upgraded and this problem is still present on my system running kipi-plugins 0.1.6 and digikam 0.9.5-beta1. Geoff
Geoff, And using KDE4 version of digiKam and kipi-plugins the problem disappear... right ? Gilles Caulier
Maybe - I haven't tested KDE4 version on that computer. My guess would be that it would still be affected due to using the intel video driver as discussed above. To summarize: Computer 1 - intel video, ubuntu hardy, digikam 0.9.5-beta1 - has problem Computer 2 - nvidia video, ubuntu intrepid, digikam 0.10.0-svn - no problems. Probably cannot test KDE4 version on computer 1 until holidays. Maybe some of the others that previously confirmed this have some thoughts?
rendering-related code didn't change since quite a while in the imageviewer. The same opengl code is used for KDE3 and KDE4, so I wouldn't expect the problem to be gone with intel 810 under KDE4, but you can give it a try. I can imagine issues with compositing enabled, since all opengl commands have to be redirected. Did you disable compositing in KDE3? no compitz or anything? As for nvidia, compositing and opengl (even with unusual large textures as in the imageviewer) works smoothly. another point to take into consideration: the code as it is right now is optimized for pics of a 5mpixel camera and 32mb video ram. The 5mp image generates 20mb raw data in texture ram, which should leave enough space for the desktop. However, sometimes even this is not enough. I've seen strange effects on my nvidia hardware when running out of video-memory. I should take videomemory into account for the configuration one day....
I just switched back to intel (from nvidia) and this is still present. It happens on 2 computers. 1) kubuntu 9.10 with kde4.3 and digikam/kipi-plugins 1.0 from packages. This uses i810 video driver. Issue is present. 2) ubuntu 10.04 with kde4.4 and digikam/kipi-plugins 1.1 from packages. This uses intel/i915 driver. Used to have nvidia card that worked fine, but removed it and re-discovered this issue. I'd be glad to do testing or provide more info if requested. Thanks, Geoff
Geoff, This file still valid using kipi-plugins 2.4 ? Gilles Caulier
Geoff, This file still valid using last kipi-plugins 4.10.0 ? Gilles Caulier
Hello, No longer have this bug. Consider it fixed.. My system has changed a lot since it was reported. Built from macports: digiKam version 4.9.0 CPU cores: 4 Demosaic GPL2 pack support: Unknown Demosaic GPL3 pack support: Unknown Exiv2 can write to Jp2: Yes Exiv2 can write to Jpeg: Yes Exiv2 can write to Pgf: Yes Exiv2 can write to Png: Yes Exiv2 can write to Tiff: Yes Exiv2 supports XMP metadata: Yes LibCImg: 130 LibEigen: 3.2.4 LibExiv2: 0.24 LibJPEG: 90 LibJasper: 1.900.1 LibKDE: 4.14.3 LibKExiv2: 2.3.2 LibKGeoMap: 3.1.0 LibKdcraw: 2.4.2 LibLCMS: 119 LibLensFun: 0.3.0-0 LibLqr support: yes LibPGF: 6.14.12 LibPNG: 1.6.17 LibQt: 4.8.6 LibRaw: 0.16.0 LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. Marble Widget: 0.19.2 (stable release) Parallelized demosaicing: Unknown RawSpeed codec support: Unknown Baloo support: no Database backend: QSQLITE Kdepimlibs support: Yes Kipi-Plugins: 4.9.0 LibGphoto2: 2.5.7 LibKface: 3.5.0 LibKipi: 2.1.0 LibOpenCV: 2.4.11 Sqlite2 support: no