Version: (using KDE KDE 3.2.0) Installed from: Compiled From Sources Compiler: gcc-3.3.2 OS: Linux The Preview works fine till the maximum file setting doesn't change. After it is changed and konquerror is restarted all previews disappear. They appear again after deleting the [PreviewSettings] in kdeglobals file.
This bug exists in Fedora Core 1.0 and ASP Linux 9 (the same as RedHat 9)
Subject: Re: no previews after the maximum file size setting was changed I'm experiencing this too. KDE built from CVS 02 FEB 04 on Gentoo.
same on 3.2.0 compiled from sources with gcc 3.3.3, FreeBSD 5.2-RELEASE: after re-enabling them in system settings, previews work again in existing konqueror filemanager windows, but only until you switch to a different directory; at that point previews are turned off
The same with KDE-3.2.1 on Fedora Core 1
Nothing has changed in KDE-3.2.2 Moreover the same problem exists in Fedora Core Test 1 in the original Fedora's compilation
I can confirm this bug, using KDE 3.2.2 RPMs for SuSE 9.0.
This bug is also reported here: http://bugs.kde.org/show_bug.cgi?id=79994
*** Bug 79994 has been marked as a duplicate of this bug. ***
Hi all, are there news? I just encountered the same problem kde-3.2.2 from source and wasn't able to find anything in the changelog. Or did anybody find a workaround for this problem? Thank you
The problem exists in Fedora Core 2. However, there is no this problem in SUSE 9.1. I don't know how they have done it.
It 's not a bug . If you change the "maximum file setting" , you have to choose a "protocol" (in the same window) :for instance, select "file" in "local protocole" for previews images in your home directory. You have also to choose a "profile" in Setting>>load view profile ( "File Preview" is a good choice for this job )
Oh, you're right. That's a little bit unintuitive. Since we didn't change the protocol settings I would assume that they keep the same as before. Perhaps at least "file" should be selected per default and must be disabled by hand? However, thank you for this hint. :-)
This hint solved the problem for me running Debian testing. The solution is far from intuitive, however. Even google couldn't find the answer for me! The behavior of this settings dialog needs to be reanalyzed, maybe a note at the top?
*** Bug 84106 has been marked as a duplicate of this bug. ***
Cannot reproduce the bug on both KDE 3.5.9 AND 4.1 (trunk r802881)
After some other testing I close the bug.