Hi, Today at morning kdesktop is runaway at 2025/04/20 08:34 Today only one process with 96% of CPU. After use kill -TTIN <process id> and start to work again without any consequences. The fan slowdown after minutes, the icons on desktop start to work again and i can suspend the computer. I hope that this information help you. Best Regards Christian
On Saturday 19 April 2025 15:54:19 Christian Schmitz via tde-users wrote:
Dear: I know that this is very hard to solve, and count with me. But since we are speaking never fail. I program too, i start with computers on commodore 16 ( around 1985, i am old hahahaha) and i program with they. My specialitazion is hardware so, i program on low level and i cannot write any solution.
Yes i can confirm 2 kdesktop process, and the computer remains 90% operative and i use with runaway more than one week. Programming, libreoffice, firefox etc etc.
Yes i suspect that an exhaust of memory can be the origin, but i discard this. One time after only 10 minutes of a logout/login to restore a previous runaway i get a new runaway.
and what says .xsession-errors, dmesg, syslog?
when fail i will attach. I dont know where move the syslog the opensuse people, the another files are located
Best Regards Christian
On Friday 18 April 2025 19:02:07 Darrell Anderson via tde-users wrote:
On 4/18/25 11:23 AM, Christian Schmitz via tde-users wrote:
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
Do you have another computer available? If you do, SSH into the problem box before starting TDE. Monitor the system with top. You can obtain the process ID (PID) of kdesktop with 'ps aux | grep kdesktop | grep -v grep'. There are two such processes. Note the PIDs before launching top through SSH.
If no second computer is available, toggle to another console and repeat the steps to monitor with top. Seems your keyboard remains functional so toggling to another console should succeed.
Inconvenient, but start TDE and then do not launch any software such as a web browser. Just start TDE and monitor top.
Another troubleshooting option is disable all services in KControl->TDE Components->Service Manager. Some TDE features won't be available but temporarily doing this might remove some variables for the runaway behavior.
Michele Calgaro replied earlier that the devs are aware of a potential runaway issue with kdesktop lock but have not found a root cause. So any way you can troubleshoot to provide observations probably will help everybody.
I have been using computers for more than 40 years and I have seen my share of bugs like this. There is no simple cure, just lots of patience and diligence. Keep trying to eliminate anything that might look like a root cause. I probably am not helping much saying that. :) ____________________________________________________ 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@trinitydes kt op.org
