17 Apr
2025
17 Apr
'25
11:06 a.m.
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
17 Apr
17 Apr
12:16 p.m.
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.
1:28 p.m.
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:
--
Be Free, Be Linux
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(a)trinitydesktop.org
To unsubscribe send an email to users-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt
op.org 
6:09 p.m.
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
7:10 p.m.
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:
--
Be Free, Be Linux
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 
9:05 p.m.
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. :)
18 Apr
18 Apr
8:23 p.m.
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:
--
Be Free, Be Linux
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(a)trinitydesktop.org
To unsubscribe send an email to users-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskt
op.org
8:59 p.m.
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
10:21 p.m.
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.
19 Apr
19 Apr
12:04 a.m.
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
12:17 a.m.
On 4/18/25 3:04 PM, deloptes 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.
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?
2:39 a.m.
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.
18 Apr
18 Apr
9:02 p.m.
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. :)
19 Apr
19 Apr
7:24 a.m.
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
0
days inactive
2
days old
15 comments
4 participants
participants (4)
-
Christian Schmitz -
Darrell Anderson -
deloptes -
Michele Calgaro