Version: (using KDE 4.1.96) Compiler: gcc 4.2.4 OS: Linux Installed from: Compiled From Sources After disabling GUI effects, KRunner still has GUI effects. I.e.: you type in 'konsole' and it slides the 'Konsole' and 'Run Konsole' items into view. Also the box that contains these two items is slidden into the view instead of just instantly appearing. This is very annoying because I'm using an NVIDIA driver (which is known to be slow with KDE4). Besides it looks like a bug to me because I can't configure the behavior of KRunner in this?
This also disrupts xscreensaver gl hacks. I've gone to System Settings -> Desktop -> Desktop Effects -> General and unchecked "Enable desktop effects", and yet I still can't run hacks or glxgears. Whiskey Tango Foxtrot, over?
I have also disabled components in kwinrc like so: [hennessy@marvin hennessy]$ kreadconfig --file kwinrc --group Compositing --key Enabled false [hennessy@marvin hennessy]$ kreadconfig --file kwinrc --group Compositing --key Backend XRender and restarted X11 and kde.
Ok, so I think some things got mixed up here: 1. GUI effects are not the same as desktop effects. So all compositing related stuff needs to be reported seperately (regarding Mathew's replies). 2. Disabling QT GUI effects doesn't influence KRunner, as KRunner doesn't make use of default qt gui effects. 3. AFAIK, krunner doesn't make use of compositing features for it's animations, so disabling desktop effects of course doesn't effect this. @bughunter2: Do you still have performance issues using a recent KDE version? I use a NVIDIA card myself and have no problems for a long time now. Also, a missing configuration option is not a bug, so please open a wish list item on that.
@Dominik Tritscher: I haven't tested KDE4 lately because I switched to GNOME (no, not only because of this bug). BTW: To me, it looks like a bug in the planning of KDE4, which is why I filed it as a bug report. Though, honestly, do I really have to open a new feature request for this?
You're report was about krunner "ignoring" settings and about krunner lacking a configuration option. So these are two issues, that makes two reports. I'm sorry if that looks a bit bureaucratic to you, but if you look at KDE bug statistics you may agree, that we have to be strict about the organization at b.k.o. Otherways we would end up in a complete mess. As no more info are available at the moment, I close this bug for now. If you're able to reproduce that bug with a more recent KDE version, please leave me note, so I can reopen this report.
Just to defend my position: I made a report about a component (KRunner) 'misbehaving' according to the configuration of the whole (KDE). I proposed two (arguably not equally-satisfactory): making KRunner behave as one could expect (in harmony with the configuration of the whole, i.e. KDE), or making KRunner more configurable. These two are part of the same issue, so there is no need to open two reports.