Created attachment 333596 [details] /var/log/Xorg.0.log After today updates Plazma buzzies immediately after launch konsole from right-click menu
rpm -q kdelibs kdebase-workspace please. And what does "buzzies" mean exactly?
rpm -q kdelibs kdebase-workspace kdelibs-4.2.0-17.fc11.i586 kdebase-workspace-4.2.0-16.fc11.i586 Panel, kicker. taskbar, Desktop not response on clicks (Alt+Tab and Alt+F2 work only). I has tried remove ~/.kde too
Created attachment 333642 [details] screenshot
Comment on attachment 333642 [details] screenshot Taskbar and panel are not response (new launch application do not display on taskbar)
*** Bug 489268 has been marked as a duplicate of this bug. ***
We've seen a plethora of nvidia-related issues, all due to driver bugs. Please try to reproduce without the nvidia drivers, and if so, we'd be happy to explore this further.
In my case it is reproducable on binary NVidia and regular nv as well.
(In reply to comment #7) > In my case it is reproducable on binary NVidia and regular nv as well. I can't confirm that. Changing the driver in xorg.conf from 'nvidia' to 'nv' wasn't enough for me, the freezing persisted. But after completely removing the nvidia binary driver from my system (running the installer with the '--uninstall' option), plasma seems to be stable with the nv driver.
True, My understanding is that nvidia's driver installs custom (opengl and other?) libraries, which override the default fedora ones. So, even if the driver isn't currently enabled, it's mere presence can still have a debilitating effect on system stability.
Right, especially if you use the broken installer from NVidia's web page. Never use that installer! The only safe way to clean up its mess is to reinstall Fedora. RPM Fusion's packages are more respectful of Fedora's system libraries, so at least they uninstall properly. But neither Fedora (which doesn't even ship the buggy driver) nor RPM Fusion (which can only ship the binaries NVidia provides and has no access to the source code) can fix your issue, because it's a driver bug. Please report to NVidia.