Hi everyone: 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. Best Regards to all Christian
Be Free, Be Linux
Christian Schmitz via tde-users wrote:
I have opensuse tumbleweed.
very often it is an issue related to underlaying hardware that can not recover from suspend - example graphic card, or network card - and related subsystem. Check for example pulse audio (if you are using it) and the dmsg for errors. Some of these symptoms can be solved by tuning the bios.
Hi, I agree that is some related with power management, maybe ACPI. But the problem is while the system is active. For example, i am working and listen the fan to the max speed...... and after check i verify that kdesktop is broken while the system is up, running and in use. Another times occur while is with the display is open and without use. But never occur at wakeup moment or when i use "suspend" button on TDE. Good hint. I will check dmesg when occur. Best Regards Christian
On Thursday 17 April 2025 10:16:39 deloptes via tde-users wrote:
Christian Schmitz via tde-users wrote:
I have opensuse tumbleweed.
very often it is an issue related to underlaying hardware that can not recover from suspend - example graphic card, or network card - and related subsystem. Check for example pulse audio (if you are using it) and the dmsg for errors. Some of these symptoms can be solved by tuning the bios.
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
On 2025/04/17 04:06 PM, Christian Schmitz via tde-users wrote:
Hi everyone: 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.
Yes, we are aware of a similar issue and it is somehow related to the lock and screensaver code. There may be other reasons, like suspend perhaps, but not sure. We are trying to fixing it up, actually already tried a failed attempt. More work on this is expected in the R14.1.5 window.
Cheers Michele
Dear Michele. I will collaborate with all data that i can get. Today no hangup Best Regards Christian
On Thursday 17 April 2025 16:09:35 Michele Calgaro via tde-users wrote:
On 2025/04/17 04:06 PM, Christian Schmitz via tde-users wrote:
Hi everyone: 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.
Yes, we are aware of a similar issue and it is somehow related to the lock and screensaver code. There may be other reasons, like suspend perhaps, but not sure. We are trying to fixing it up, actually already tried a failed attempt. More work on this is expected in the R14.1.5 window.
Cheers Michele
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. :)
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
Christian Schmitz via tde-users wrote:
pc # Top kdesktop 70% kdesktop 80% Firefox etc (is over more than 100% by the dual core)
First of all why do you have two kdesktop processes running? do you have dual head GPU, or second user?
Secondly I spent some time last year dealing with similar issue. From time to time the PC was becoming unresponsive and was starting to swap like crazy. I ended up installing more ram. It turned out Firefox was consuming more and more RAM until it got exhausted, then it started swapping and was killed by the oomp killer. I have configured monitoring and it showed clearly that it was increasing over time. Now I have 20GB of RAM and I restart firefox when RAM consumption exceeds 80+%.
However in your case it could be another issue.
BR
On 4/18/25 12:59 PM, deloptes via tde-users wrote:
and what says .xsession-errors, dmesg, syslog?
Do you see there something suspicious?
I am not the OP, but my experience is desktop environments (DEs) do a poor job of logging. Logs such as /var/log/messages|syslog|dmesg are primarily at the operating system level.
Historically the user's .xsession-errors log has been the only portal for DEs to record events. If the underlying code doesn't spit out anything to stdout/stderr then nothing is recorded.
Sometimes I have wondered why all DEs don't have a verbose DEBUG environment variable. That would produce some overwhelming logs, but the variable would be enabled only when troubleshooting.
Darrell Anderson via tde-users wrote:
Sometimes I have wondered why all DEs don't have a verbose DEBUG environment variable. That would produce some overwhelming logs, but the variable would be enabled only when troubleshooting.
I think tdedebugdialog is what you mean?
regarding the loggin at system level there is where you find the OoM killer traces.
https://www.kernel.org/doc/html/v6.4/admin-guide/mm/concepts.html#oom-killer https://www.kernel.org/doc/gorman/html/understand/understand016.html https://learn.redhat.com/t5/Platform-Linux/Out-of-Memory-Killer/td-p/48828
On 4/18/25 3:04 PM, deloptes via tde-users wrote:
Sometimes I have wondered why all DEs don't have a verbose DEBUG environment variable. That would produce some overwhelming logs, but the variable would be enabled only when troubleshooting.
I think tdedebugdialog is what you mean?
Possibly! If I ever get my build environment running I'll be able to explore the many missing packages from Slackware. Or get my Debian VM running to explore.
Darrell Anderson via tde-users wrote:
Possibly! If I ever get my build environment running I'll be able to explore the many missing packages from Slackware. Or get my Debian VM running to explore.
not sure if you know tdedebugdialog, it has a nice man page and is part of tdebase the application (dialog) gives you the opportunity to enable or disable debug messages of various tde components. If you check all, you have to rotate .xsession-errors pretty often ;-)
I'm not sure it has anything to do with build environment.
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. :)
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@trinitydeskt op.org
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
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
On 2025/04/20 07:25 PM, Christian Schmitz via tde-users wrote:
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
Thanks Christian (and Happy Easter), That's perfect. It is indeed the problem we are aware of. We have a decent idea of what is happening, since as you can see we found an easy workaround, but we are trying to understand the root cause of it.
A few more questions (apologies for asking if you have already shared the info in previous emails). 1) what distro are you using? 2) what TDE version are you using? 3) if it is a debian based distro, are you on PSB/PTB? are you using home built packages or those provided by TDE website? 4) how many CPU and cores does your computer have?
Just trying to understand why you are seeing this problem so often.
Cheers Michele
Hi people: 1) I use OpenSuse Tumbleweed (rolling version, allways updated), i update last week. All installed of opensuse/packman and few things of third party ( microchip, st, cura, etc etc) 2) TDE 14.1.3 3) I dont know what is PSB/PTB. My usual programs are Desk 1: Kmail Desk 2: Firefox and firefox incognito Libreoffice, Kicad 9 with PCB and shematic, MPlabX, STM32CubeIde, Gimp pdf viewer (KPDF), Konsole, Internet with wifi (i need shut down, and shut up again after 90% of suspends) No extra screen
4) HP 255 g7 2 cores, 16Gb of ram, HDD 1TB AMD Athlon Silver 3050U / 2.3 GHz # lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 48 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Vendor ID: AuthenticAMD Model name: AMD A9-9425 RADEON R5, 5 COMPUTE CORES 2C+3G CPU family: 21 Model: 112 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 2 Stepping: 0 Frequency boost: enabled CPU(s) scaling MHz: 119% CPU max MHz: 3100.0000 CPU min MHz: 1400.0000 BogoMIPS: 6188.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc c puid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xs ave avx f16c lahf_lm cmp_legacy extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xo p skinit wdt lwp fma4 tce nodeid_msr tbm perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate s sbd ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_re cov Caches (sum of all): L1d: 64 KiB (2 instances) L1i: 128 KiB (2 instances) L2: 2 MiB (2 instances) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0,1 Vulnerabilities: Gather data sampling: Not affected Ghostwrite: Not affected Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Reg file data sampling: Not affected Retbleed: Mitigation; untrained return thunk; SMT disabled Spec rstack overflow: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2: Mitigation; Retpolines; IBPB conditional; STIBP disabled; RSB filling; PBRSB-eIBRS Not affected; B HI Not affected Srbds: Not affected Tsx async abort: Not affected
On Sunday 20 April 2025 12:37:09 Michele Calgaro via tde-users wrote:
On 2025/04/20 07:25 PM, Christian Schmitz via tde-users wrote:
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
Thanks Christian (and Happy Easter), That's perfect. It is indeed the problem we are aware of. We have a decent idea of what is happening, since as you can see we found an easy workaround, but we are trying to understand the root cause of it.
A few more questions (apologies for asking if you have already shared the info in previous emails). 1) what distro are you using? 2) what TDE version are you using? 3) if it is a debian based distro, are you on PSB/PTB? are you using home built packages or those provided by TDE website? 4) how many CPU and cores does your computer have?
Just trying to understand why you are seeing this problem so often.
Cheers Michele
On 2025/04/21 12:35 AM, Christian Schmitz via tde-users wrote:
Hi people:
- I use OpenSuse Tumbleweed (rolling version, allways updated), i update last
week. All installed of opensuse/packman and few things of third party ( microchip, st, cura, etc etc) 2) TDE 14.1.3 3) I dont know what is PSB/PTB. My usual programs are Desk 1: Kmail Desk 2: Firefox and firefox incognito Libreoffice, Kicad 9 with PCB and shematic, MPlabX, STM32CubeIde, Gimp pdf viewer (KPDF), Konsole, Internet with wifi (i need shut down, and shut up again after 90% of suspends) No extra screen
Thanks Christian, PSB/PTB are debian specific, they are the TDE rolling versions of the next stable releases. Another question: does the problem happens only when you suspend the computer or also during normal locking/unlocking or running of the screensaver?
Nice set of programs and tools btw :+1:
Cheers Michele
Hi Michele: Never happens when is in suspend the computer. Allways happens while the computer is on, mostly while i am using it. I suspect a memory exhaust, but i discard this because sometimes i am only writing on libreoffice writing text.
One important thing, this happen only this time. I try to open a PDF, and kpdf does not start, few hours after that i see the runaway again. Use KILL -TTIN, and the kpdf open the requested files (one hour after i require it)
Best Regards Christian
On Monday 21 April 2025 06:08:04 Michele Calgaro via tde-users wrote:
On 2025/04/21 12:35 AM, Christian Schmitz via tde-users wrote:
Hi people:
- I use OpenSuse Tumbleweed (rolling version, allways updated), i update
last week. All installed of opensuse/packman and few things of third party ( microchip, st, cura, etc etc) 2) TDE 14.1.3 3) I dont know what is PSB/PTB. My usual programs are Desk 1: Kmail Desk 2: Firefox and firefox incognito Libreoffice, Kicad 9 with PCB and shematic, MPlabX, STM32CubeIde, Gimp pdf viewer (KPDF), Konsole, Internet with wifi (i need shut down, and shut up again after 90% of suspends) No extra screen
Thanks Christian, PSB/PTB are debian specific, they are the TDE rolling versions of the next stable releases. Another question: does the problem happens only when you suspend the computer or also during normal locking/unlocking or running of the screensaver?
Nice set of programs and tools btw :+1:
Cheers Michele
пн, 21 апр. 2025 г., 11:44 Christian Schmitz via tde-users < users@trinitydesktop.org>:
Hi Michele: Never happens when is in suspend the computer. Allways happens while the computer is on, mostly while i am using it. I suspect a memory exhaust, but i discard this because sometimes i am only writing on libreoffice writing text.
One important thing, this happen only this time. I try to open a PDF, and kpdf does not start, few hours after that i see the runaway again. Use KILL -TTIN, and the kpdf open the requested files (one hour after i require it)
Some time ago I had something like this on Slackware + patched kde 3.5.10 so in my case killing gam_server helped.
So I suspect some file monitoring (fanotify?) process goes broke somewhat?
Best Regards Christian
On Monday 21 April 2025 06:08:04 Michele Calgaro via tde-users wrote:
On 2025/04/21 12:35 AM, Christian Schmitz via tde-users wrote:
Hi people:
- I use OpenSuse Tumbleweed (rolling version, allways updated), i
update
last week. All installed of opensuse/packman and few things of third party ( microchip, st, cura, etc etc) 2) TDE 14.1.3 3) I dont know what is PSB/PTB. My usual programs are Desk 1: Kmail Desk 2: Firefox and firefox incognito Libreoffice, Kicad 9 with PCB and shematic, MPlabX, STM32CubeIde, Gimp pdf viewer (KPDF), Konsole, Internet with wifi (i need shut down, and shut up again after 90% of suspends) No extra screen
Thanks Christian, PSB/PTB are debian specific, they are the TDE rolling versions of the
next
stable releases. Another question: does the problem happens only when you suspend the computer or also during normal locking/unlocking or running
of
the screensaver?
Nice set of programs and tools btw :+1:
Cheers Michele
-- Be Free, Be Linux ____________________________________________________ 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@trinitydeskto...
Hi Christian,
Never happens when is in suspend the computer. Allways happens while the computer is on, mostly while i am using it.
What I meant is if it happens after a suspend/resume cycle or not. I thought in some of the previous emails I read that, but perhaps I am confused with some other threads.
One important thing, this happen only this time. I try to open a PDF, and kpdf does not start, few hours after that i see the runaway again. Use KILL -TTIN, and the kpdf open the requested files (one hour after i require it)
The problem stems from the way kdesktop and kdesktop_lock interacts with each other and how this sometimes result in either kdesktop being blocked when it shouldn't (hence the TTIN unblock it) or kdesktop_lock not locking/screensaving the screen.
I didn't check the code, but the problem with kpdf is possibly related to kpdf doing some dcop call to kdesktop and waiting for the call to return. If kdesktop is blocked, the call is blocking. Once kdesktop is unblocked (with TTIN) then the pending call is performed and kpdf can proceed. Or it could be that you tried to click a pdf icon on the desktop when it was blocked, either way the action is performed after kdesktop works again.
Cheers Michele
On 2025/04/19 01:23 AM, Christian Schmitz via tde-users wrote:
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)
Hi Christian, how familiar are you with gdb and attaching processes and print backtraces? If you are, please install the required debug symbols, then when the problem happens again, open a CLI, attached kdesktop from gdb, print a backtrace and send it as attachment. Do the same for kdesktop_lock. I would like to check if your problem is similar to the one noticed by Slavek.
Once you have done this, find the kdesktop pid and run the following command: kill -TTIN <pid of kdesktop> Does kdesktop become responsive and CPU go back to normal levels?
Thanks Michele
-
Andrew Randrianasulu -
Christian Schmitz -
Darrell Anderson -
deloptes -
Michele Calgaro