KDE tends to freeze momentarily after performing some tasks, like closing a window, pressing a button that should result in an option pane being popped, or simply trying to drag a window around the desktop. It doesn’t happen every single time, but it’s very persistently.
I first noticed that the mouse would freeze sometimes when I do something like close a window and it takes 3~4 seconds for me to get control back, and for the task that I requested (close a window for instance) to be carried out.
During this time, I notice that all of KDE freezes up because my binary clock widget freezes as well.
Is this a known problem with KDE? Can somebody give me some advice as to what might be causing this behaviour?
I recall having similar problems back when I first tried 11.0, but back then it was so bad that I ended up going with Gnome. Now KDE has me hooked again, except for this one niggling issue. If I can get this resolved, then I think I will finally have an absolutely stable linux desktop.
Information that might be helpful:
Freshly installed less than a week ago (11.3 KDE4 from x86_64 DVD)
2 x Opteron 2354 CPUs (8 cores all up)
4GB ECC ram
nVidia GTX260 (using proprietary nvidia driver provided by 1-click install)
2 Monitors using twinview (1920x1200 each)
Disable effects may help
I switched to Gnome too but even there I still get an odd time with what you describe, usually only with applications under wine.
defex wrote:
> KDE tends to freeze momentarily after performing some tasks, like
> closing a window, pressing a button that should result in an option pane
> being popped, or simply trying to drag a window around the desktop. It
> doesn’t happen every single time, but it’s very persistently.
>
same thing here, I experience these 2-5 secs dropouts every few minutes.
Quite annoying.
What’s interesting is that some features still do work and respond, like
desktop switching for example. This indeed suggests that there is some
problem inside KDE.
I tried disabling compiz, and doing so had no effect. Same ol’ problem persisted. I’m keen to get dirty in code and try to debug the problem myself, but I’m still a novice developer and KDE is a BIG project.
I’m glad that someone else is experiencing this problem, as it means I’m not going crazy ;).
Anyhu, I believe I will head over the the KDE abode and ask around there. Might get in contact with somebody who can actually help out. Ta.
The problem we’re experience is short lock ups of the KDE UI (3~4 seconds at a time) when you try to move a window, close a window, minimize a window, etc (always something to do with manipulating windows).
The lock up is of no consequence, since you get control back shortly, but it’s a pain when these occur back to back in a short period of time as launching half a dozen programs (which should only take a few seconds on my 8-core workstation) can take half a minute when you have to wait for the lock ups before being able to even move the mouse to open the next program. Closing programs when your desktop gets a bit cluttered is even more problematic.
Well with me (as surely is the case with 99.9% of the ppl too) it is tracker-extract. Wtf did this come from?? The problem with me started after an upgrade through last week and it starts slowly rising the cpu due a continuous use of 9x % of the cpu 100% of the time (its a desktop computer so restrictions typical for some notebooks do not apply, fans are working and clean, etc) ) until the computer shuts itself down for over temperature. Its NOT a hardware problem and the best guess is that someone screwed up really bad with some patch or whatever the “upgrade” was :. It’s not only an opensuse problem because I can boot sabayon with kde 4.5.1 too (among other OSs) and it does just the same;it started showing a coupla days before it did on opensuse (I guess it’s the typical delay between these two distros to update their repos) What is this tracker-extract (I’ve been using linux for years and had never seen that process running before) supposed to be running for? I know what it does but is it supposed to be a cover up for some other indexer’s failure to deliver what was promised it would?
Shut off the indexing. I myself have never found a real use for it. I supposes a small number of people that need to do periodic searches across many documents may need it but how often does this happen for the average user. And if you need such a thing why not use a real document database system. Trying to do this as a built in to the desktop is a stupid MS idea. One of the first things I do on Windoz is to turn off it’s indexing.
Hi,
I’m new to openSuse, had ubuntu-gnome for a year now and felt like trying some other distro’s. Just installed openSuse yesterday, and it seems real nice (Using enterprise-suse at work)
Experiencing the same symptom as the person who opened the thread -
Did a fresh install of openSuse 64 bit KDE on my HP pavilion7 laptop, intel core 2 duo (T7500 i think), 4GB DDR2, nVidia Geforce 9600M GT, on a 60GB partition (the installer splittled it into 20GB for / and 38GB for /home/ and 2GB for swap).
After running the updater and applying all the patches, I used the one-click to install nVidia proprietary drivers, and enabled all desktop effects.
Whenever the effects are on, I get the 3-4 second freezes occasionally when manipulating a window in some way, although it happens randomly, even when doing the same action again and again. Turning all effects off eliminates the problem.
Is there any quick fix to this issue? Maybe upgrading to KDE 4.5? or 4.6? I guess it’s a KDE issue, maybe related to the video driver (I’m a programmer, but I don’t know much about Linux). I didn’t install any piece of software except the default upgrades and nVidia driver.
Then, take a look at the procedure I use to install the nVidia driver as I install openSUSE 11.3:
During the install, when you have the option to change your booting setup, I add nomodeset to the kernel load command for the normal load/start of openSUSE. This kernel startup option is already present for the Failsafe selection for openSUSE.
During the first start of openSUSE, I download the latest nVidia Video driver to the downloads folder.
I change/save the System/Kernel option NO_KMS_IN_INITRD from “No” to “Yes” in the /etc/sysconfig Editor in Yast.
I do an update of openSUSE on the first run of openSUSE and then a restart/reboot.
In grub OS selection I add the command line option “3” to the openSUSE start line so that I just go to the run level three terminal prompt.
I login in as root and change to the /home/user/Downloads folder.
I run/install the NVIDIA video driver using “sh ./NVIDIA-Linux-x86_64-260.19.29.run” and answer all questions as appropriate for my system.
Type in reboot at terminal prompt to restart the system with new video driver.
I wrote a script to load the nVidia driver the hard way. Look at message #12 for the most recent version of lnvhw.
If you really want to “go all the way”, you might consider a kernel upgrade. If you do this, you wait to load the Video driver after the kernel install is complete. Message #17 has the most recent version of SAKC:
I have found that by loading the nVidia driver and switching to the latest stable kernel (2.6.36.2) has provided many benefits to system operation. Also, you should consider your multimedia setup. It also a component in your over all operation. I have a script for that also call mmcheck. Message #47 has the most recent version of mmcheck:
Instead of re-installing the proprietary driver of nVidia, I upgraded to KDE 4.5 (bruce above suggested it), and now everything works perfect!
I hope this helps other people with this problem.
Instead of re-installing the proprietary driver of nVidia, I upgraded to KDE 4.5 (bruce above suggested it), and now everything works perfect!
I hope this helps other people with this problem.
Upgrading to KDE 4.5 is a big step, if you are used to KDE 4.4, but I am Happy to hear of your success. I must say that I always load the nVidia driver and that I have had the most success when using it, but I never question anyone’s success.