Hello Dareel: I didt both things. First if i dont suspend the laptop, even kdesktop go runaway. For this reason i start to suspend it.
pc # Top kdesktop 70% kdesktop 80% Firefox etc (is over more than 100% by the dual core)
Under kdesktop runaway: I can use the computer normally (a little more slower than normal), open programs ONLY from menu at bottom left. Close programs. Save the work in my programs. Print, listen sound, navigate on internet, and check emails. I can press ALT+CTRL+F1 to get a console and make reboot on command line. I can press ALT+CTR+BAKSPACE to force a logout
I CANNOT make click on icons on desktop. The computer is with the fan at max speed.
If i press ALT+CTRL+BACKSPACE, and login again, everything start to works
Best Regards Christian
On Thursday 17 April 2025 19:05:38 Darrell Anderson via tde-users wrote:
On 4/17/25 2:06 AM, Christian Schmitz via tde-users wrote:
I have a computer that i didnt turn off, simply put in suspend mode. But i found that sometimes ( i dont know when or why) kdesktop go away. The symptoms are:
- the fan speed up
- two KDESKTOP process take 80% of cpu each one,
- The icons on desktop are not clikable anymore
- the shutdown button on first call open the dialog and i can make click
on suspend
- the shutdown button on second call do nothing.
Pressing ALT+CRL+BAKSPACE i go to login and everyting works again... for one hour, 1 day or one week (randomly)
I have opensuse tumbleweed.
A common suggestion is pop open a terminal window and run top or htop. Often that will show processes using too many CPU cycles.
Might also want to note if any non TDE software is running. The other day I saw this and my laptop was getting quite warm. If I remember correctly I was running two krdc sessions concurrently, but I don't remember if I was using TDE or KDE krdc.
Another approach might be to not suspend the computer. See how often the runaway issue arises. Not suspending removes one variable from the equation.
Another approach when the desktop becomes unusable is toggle to a console with Ctrl+Alt+F[1-6]. Log in as root and run top or htop. Kill any suspect processes and see if that restores desktop usability. If unfamiliar with using alternate consoles, then practice a bit when the system is running okay to get the hang of toggling.
Another option, if available, is use a second system to SSH into the problem box and repeat looking at processes with top.
These types of strategies should reveal whether the problem is the operating system, desktop environment, or something else.
On a less pleasant note, I have seen hardware cause similar issues. I have seen systems where the desktop eventually freezes and no amount of troubleshooting or wizardry finds a remedy. The solution is replace the motherboard.
I hope that helps. :) ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt op.org