On one computer, switch user is slow to impossible to use.
sddm seems to cause Xorg to hang and I don't know how to debug it.
I have to ssh in from a different computer and kill all processes to get into the computer again. Keyboard is useless but mouse pointer moves. Caps and numlock keys don't work either.
On a reboot, it is not bad but after a few hours, it gets really awful and, like tonight, I had to login from a different computer to kill all user processes.
I don't know if this is related to freezes and crashes on other computers using KDE that I am seeing. One computer that has a full screen crash almost weekly, I cannot ssh into as I don't have a second computer allowed on the network.
I had issues on F28 but since the second last kernel update, it has been awful.
As I need to use the cuda processors for some of the programs I am using, I need the closed source nvidia drivers on this computer. The other two computers are using nouveau drivers.
Robin
Am 06.02.19 um 06:21 schrieb Robin Laing:
On one computer, switch user is slow to impossible to use.
sddm seems to cause Xorg to hang and I don't know how to debug it.
I have to ssh in from a different computer and kill all processes to get into the computer again. Keyboard is useless but mouse pointer moves. Caps and numlock keys don't work either.
maybe it's the memory leak i am suffering for months if not years
my machine has 32GB RAM and 4x3.5 Ghz which is maybe the reason "ALT+F2 and type "restart-plasma.sh" is no problem while with less memory likely everything takes ages
after some hours or intense work switch between applications takes ages here and when restart plasma eveyrthing becomes smooth again
[harry@srv-rhsoft:~/downloads]$ cat /scripts/restart-plasma.sh #!/usr/bin/dash killall plasmashell /usr/bin/plasmashell &
Reindl Harald wrote:
[harry@srv-rhsoft:~/downloads]$ cat /scripts/restart-plasma.sh #!/usr/bin/dash killall plasmashell /usr/bin/plasmashell &
I encourage you to adjust your script to do something like this instead (to avoid needless kill):
kquitapp5 plasmashell killall plasmashell /usr/bin/plasmashell &
-- Rex
Am 06.02.19 um 17:59 schrieb Rex Dieter:
Reindl Harald wrote:
[harry@srv-rhsoft:~/downloads]$ cat /scripts/restart-plasma.sh #!/usr/bin/dash killall plasmashell /usr/bin/plasmashell &
I encourage you to adjust your script to do something like this instead (to avoid needless kill):
kquitapp5 plasmashell killall plasmashell /usr/bin/plasmashell &
done - thanks
the first version years ago was a SIGSEGV :-)
On 06/02/2019 04:58, Reindl Harald wrote:
Am 06.02.19 um 06:21 schrieb Robin Laing:
On one computer, switch user is slow to impossible to use.
sddm seems to cause Xorg to hang and I don't know how to debug it.
I have to ssh in from a different computer and kill all processes to get into the computer again. Keyboard is useless but mouse pointer moves. Caps and numlock keys don't work either.
maybe it's the memory leak i am suffering for months if not years
my machine has 32GB RAM and 4x3.5 Ghz which is maybe the reason "ALT+F2 and type "restart-plasma.sh" is no problem while with less memory likely everything takes ages
after some hours or intense work switch between applications takes ages here and when restart plasma eveyrthing becomes smooth again
[harry@srv-rhsoft:~/downloads]$ cat /scripts/restart-plasma.sh #!/usr/bin/dash killall plasmashell /usr/bin/plasmashell & _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
I have 32G and a powerful machine as well but if I switch between users, I cannot type anything at all. I will try the alt+F2 and see if that works.
I will watch memory and maybe try to restart plasma before trying to switch users.
It is time related so a memory leak may be an issue. Once I can switch users, I can switch back and forth almost instantly. Give it time and the time to change gets longer and longer.
I have restarted plasma in the past with the same commands as you used.
I guess this means it points more to plasmashell than sddm or Xorg.
Doing a search on plasmashell memory leak and there are many that have created cron jobs to restart their plasmashell on a regular basis.
In my case, that may be a great idea.
I just noticed that for KDE5.10 and above they now recommend kquitapp5 plasmashell kstart5 plasmashell
I will start to monitor the memory usage with top -b -n 1 |grep plasmashell
Maybe create a script to log the data as well.
Thanks. I will watch this over the next couple of days.
Also testing on a different computer.
Robin
On 09/02/2019 01:07, Robin Laing wrote:
On 06/02/2019 04:58, Reindl Harald wrote:
Am 06.02.19 um 06:21 schrieb Robin Laing:
On one computer, switch user is slow to impossible to use.
sddm seems to cause Xorg to hang and I don't know how to debug it.
I have to ssh in from a different computer and kill all processes to get into the computer again. Keyboard is useless but mouse pointer moves. Caps and numlock keys don't work either.
maybe it's the memory leak i am suffering for months if not years
my machine has 32GB RAM and 4x3.5 Ghz which is maybe the reason "ALT+F2 and type "restart-plasma.sh" is no problem while with less memory likely everything takes ages
after some hours or intense work switch between applications takes ages here and when restart plasma eveyrthing becomes smooth again
[harry@srv-rhsoft:~/downloads]$ cat /scripts/restart-plasma.sh #!/usr/bin/dash killall plasmashell /usr/bin/plasmashell & _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
I have 32G and a powerful machine as well but if I switch between users, I cannot type anything at all. I will try the alt+F2 and see if that works.
I will watch memory and maybe try to restart plasma before trying to switch users.
It is time related so a memory leak may be an issue. Once I can switch users, I can switch back and forth almost instantly. Give it time and the time to change gets longer and longer.
I have restarted plasma in the past with the same commands as you used.
I guess this means it points more to plasmashell than sddm or Xorg.
Doing a search on plasmashell memory leak and there are many that have created cron jobs to restart their plasmashell on a regular basis.
In my case, that may be a great idea.
I just noticed that for KDE5.10 and above they now recommend kquitapp5 plasmashell kstart5 plasmashell
I will start to monitor the memory usage with top -b -n 1 |grep plasmashell
Maybe create a script to log the data as well.
Thanks. I will watch this over the next couple of days.
Also testing on a different computer.
Robin _
I was hoping I was on to something from your suggestions. It is not plasmashell related. I killed plasmashell before trying to switch users and it still took a long time for sddm to display the password prompt.
The first account I restarted, the second account I had to use ALT+F2 and run kstart plasmashell as I had a blank screen.
I have been reading on how to find memory leaks and will keep looking in that direction.
I may look at the kscreenlocker as well as sddm again.
Robin
On 09/02/2019 15:13, Robin Laing wrote:
On 09/02/2019 01:07, Robin Laing wrote:
On 06/02/2019 04:58, Reindl Harald wrote:
Am 06.02.19 um 06:21 schrieb Robin Laing:
On one computer, switch user is slow to impossible to use.
sddm seems to cause Xorg to hang and I don't know how to debug it.
I have to ssh in from a different computer and kill all processes to get into the computer again. Keyboard is useless but mouse pointer moves. Caps and numlock keys don't work either.
maybe it's the memory leak i am suffering for months if not years
my machine has 32GB RAM and 4x3.5 Ghz which is maybe the reason "ALT+F2 and type "restart-plasma.sh" is no problem while with less memory likely everything takes ages
after some hours or intense work switch between applications takes ages here and when restart plasma eveyrthing becomes smooth again
[harry@srv-rhsoft:~/downloads]$ cat /scripts/restart-plasma.sh #!/usr/bin/dash killall plasmashell /usr/bin/plasmashell & _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
I have 32G and a powerful machine as well but if I switch between users, I cannot type anything at all. I will try the alt+F2 and see if that works.
I will watch memory and maybe try to restart plasma before trying to switch users.
It is time related so a memory leak may be an issue. Once I can switch users, I can switch back and forth almost instantly. Give it time and the time to change gets longer and longer.
I have restarted plasma in the past with the same commands as you used.
I guess this means it points more to plasmashell than sddm or Xorg.
Doing a search on plasmashell memory leak and there are many that have created cron jobs to restart their plasmashell on a regular basis.
In my case, that may be a great idea.
I just noticed that for KDE5.10 and above they now recommend kquitapp5 plasmashell kstart5 plasmashell
I will start to monitor the memory usage with top -b -n 1 |grep plasmashell
Maybe create a script to log the data as well.
Thanks. I will watch this over the next couple of days.
Also testing on a different computer.
Robin _
I was hoping I was on to something from your suggestions. It is not plasmashell related. I killed plasmashell before trying to switch users and it still took a long time for sddm to display the password prompt.
The first account I restarted, the second account I had to use ALT+F2 and run kstart plasmashell as I had a blank screen.
I have been reading on how to find memory leaks and will keep looking in that direction.
I may look at the kscreenlocker as well as sddm again.
Robin
FWIW, I found that using SysProf, I was able to confirm that it is not KDE but Xorg and I am suspecting the nVidia kernel driver related to ioctl.
Now to learn how to find what I need to submit a bug report.
Thank you to those that responded.
Hi
Are you also having a noticeably longer delay when logging in after a reboot? For me, first login has a significant delay (since the past few weeks), but unlocking desktop from SDDM screen is fast. I'm not on NVidia. I'm on Intel.
Syam
On Mon, 18 Feb, 2019, 5:52 AM Robin Laing <MeSat@telusplanet.net wrote:
On 09/02/2019 15:13, Robin Laing wrote:
On 09/02/2019 01:07, Robin Laing wrote:
On 06/02/2019 04:58, Reindl Harald wrote:
Am 06.02.19 um 06:21 schrieb Robin Laing:
On one computer, switch user is slow to impossible to use.
sddm seems to cause Xorg to hang and I don't know how to debug it.
I have to ssh in from a different computer and kill all processes to get into the computer again. Keyboard is useless but mouse pointer moves. Caps and numlock keys don't work either.
maybe it's the memory leak i am suffering for months if not years
my machine has 32GB RAM and 4x3.5 Ghz which is maybe the reason "ALT+F2 and type "restart-plasma.sh" is no problem while with less memory
likely
everything takes ages
after some hours or intense work switch between applications takes ages here and when restart plasma eveyrthing becomes smooth again
[harry@srv-rhsoft:~/downloads]$ cat /scripts/restart-plasma.sh #!/usr/bin/dash killall plasmashell /usr/bin/plasmashell & _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
I have 32G and a powerful machine as well but if I switch between users, I cannot type anything at all. I will try the alt+F2 and see if that works.
I will watch memory and maybe try to restart plasma before trying to switch users.
It is time related so a memory leak may be an issue. Once I can switch users, I can switch back and forth almost instantly. Give it time and the time to change gets longer and longer.
I have restarted plasma in the past with the same commands as you used.
I guess this means it points more to plasmashell than sddm or Xorg.
Doing a search on plasmashell memory leak and there are many that have created cron jobs to restart their plasmashell on a regular basis.
In my case, that may be a great idea.
I just noticed that for KDE5.10 and above they now recommend kquitapp5 plasmashell kstart5 plasmashell
I will start to monitor the memory usage with top -b -n 1 |grep plasmashell
Maybe create a script to log the data as well.
Thanks. I will watch this over the next couple of days.
Also testing on a different computer.
Robin _
I was hoping I was on to something from your suggestions. It is not plasmashell related. I killed plasmashell before trying to switch users and it still took a long time for sddm to display the password prompt.
The first account I restarted, the second account I had to use ALT+F2 and run kstart plasmashell as I had a blank screen.
I have been reading on how to find memory leaks and will keep looking in that direction.
I may look at the kscreenlocker as well as sddm again.
Robin
FWIW, I found that using SysProf, I was able to confirm that it is not KDE but Xorg and I am suspecting the nVidia kernel driver related to ioctl.
Now to learn how to find what I need to submit a bug report.
Thank you to those that responded. _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
On 17/02/2019 20:33, Syam wrote:
Hi
Are you also having a noticeably longer delay when logging in after a reboot? For me, first login has a significant delay (since the past few weeks), but unlocking desktop from SDDM screen is fast. I'm not on NVidia. I'm on Intel.
Syam
On Mon, 18 Feb, 2019, 5:52 AM Robin Laing <MeSat@telusplanet.net mailto:MeSat@telusplanet.net wrote:
On 09/02/2019 15:13, Robin Laing wrote: > On 09/02/2019 01:07, Robin Laing wrote: >> On 06/02/2019 04:58, Reindl Harald wrote: >>> >>> >>> Am 06.02.19 um 06:21 schrieb Robin Laing: >>>> On one computer, switch user is slow to impossible to use. >>>> >>>> sddm seems to cause Xorg to hang and I don't know how to debug it. >>>> >>>> I have to ssh in from a different computer and kill all processes to >>>> get >>>> into the computer again. Keyboard is useless but mouse pointer moves. >>>> Caps and numlock keys don't work either. >>> >>> maybe it's the memory leak i am suffering for months if not years >>> >>> my machine has 32GB RAM and 4x3.5 Ghz which is maybe the reason "ALT+F2 >>> and type "restart-plasma.sh" is no problem while with less memory likely >>> everything takes ages >>> >>> after some hours or intense work switch between applications takes ages >>> here and when restart plasma eveyrthing becomes smooth again >>> >>> [harry@srv-rhsoft:~/downloads]$ cat /scripts/restart-plasma.sh >>> #!/usr/bin/dash >>> killall plasmashell >>> /usr/bin/plasmashell & >>> _______________________________________________ >>> kde mailing list -- kde@lists.fedoraproject.org <mailto:kde@lists.fedoraproject.org> >>> To unsubscribe send an email to kde-leave@lists.fedoraproject.org <mailto:kde-leave@lists.fedoraproject.org> >>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >>> List Archives: >>> https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org >>> >>> >> >> I have 32G and a powerful machine as well but if I switch between >> users, I cannot type anything at all. I will try the alt+F2 and see >> if that works. >> >> I will watch memory and maybe try to restart plasma before trying to >> switch users. >> >> It is time related so a memory leak may be an issue. Once I can >> switch users, I can switch back and forth almost instantly. Give it >> time and the time to change gets longer and longer. >> >> I have restarted plasma in the past with the same commands as you used. >> >> I guess this means it points more to plasmashell than sddm or Xorg. >> >> Doing a search on plasmashell memory leak and there are many that have >> created cron jobs to restart their plasmashell on a regular basis. >> >> In my case, that may be a great idea. >> >> I just noticed that for KDE5.10 and above they now recommend >> kquitapp5 plasmashell >> kstart5 plasmashell >> >> I will start to monitor the memory usage with >> top -b -n 1 |grep plasmashell >> >> Maybe create a script to log the data as well. >> >> Thanks. I will watch this over the next couple of days. >> >> Also testing on a different computer. >> >> Robin >> _ > I was hoping I was on to something from your suggestions. It is not > plasmashell related. I killed plasmashell before trying to switch users > and it still took a long time for sddm to display the password prompt. > > The first account I restarted, the second account I had to use ALT+F2 > and run kstart plasmashell as I had a blank screen. > > I have been reading on how to find memory leaks and will keep looking in > that direction. > > I may look at the kscreenlocker as well as sddm again. > > Robin > > > > > > FWIW, I found that using SysProf, I was able to confirm that it is not KDE but Xorg and I am suspecting the nVidia kernel driver related to ioctl. http://www.sysprof.com/ Now to learn how to find what I need to submit a bug report. Thank you to those that responded.
I will have to check. I don't reboot that often but I will test the next time I do. Very busy now and the delay is cutting into my productivity in both waiting and for trying to trace the bug.
Finding that sysprof traces the actual program did help.
I tried today to leave the computer in a tty and then go to a X session with ctrl+alt+# and it took just as long. :(
On 17/02/2019 21:22, Robin Laing wrote:
On 17/02/2019 20:33, Syam wrote:
Hi
Are you also having a noticeably longer delay when logging in after a reboot? For me, first login has a significant delay (since the past few weeks), but unlocking desktop from SDDM screen is fast. I'm not on NVidia. I'm on Intel.
Syam
On Mon, 18 Feb, 2019, 5:52 AM Robin Laing <MeSat@telusplanet.net mailto:MeSat@telusplanet.net wrote:
<SNIP>
I will have to check. I don't reboot that often but I will test the next time I do. Very busy now and the delay is cutting into my productivity in both waiting and for trying to trace the bug.
Finding that sysprof traces the actual program did help.
I tried today to leave the computer in a tty and then go to a X session with ctrl+alt+# and it took just as long. :(
On an AMD laptop, slow to start with, the login process is much slower than it used to be.
Once password is entered, the process seems to drag. Black screen for some time and the mouse pointer, similar to what I am seeing with my problem.
Hum,
Better start to do some checks. Might be related.
Robin
On 2/22/19 11:35 PM, Robin Laing wrote:
On 17/02/2019 21:22, Robin Laing wrote:
On 17/02/2019 20:33, Syam wrote:
Hi
Are you also having a noticeably longer delay when logging in after a reboot? For me, first login has a significant delay (since the past few weeks), but unlocking desktop from SDDM screen is fast. I'm not on NVidia. I'm on Intel.
Syam
On Mon, 18 Feb, 2019, 5:52 AM Robin Laing <MeSat@telusplanet.net mailto:MeSat@telusplanet.net wrote:
<SNIP>
I will have to check. I don't reboot that often but I will test the next time I do. Very busy now and the delay is cutting into my productivity in both waiting and for trying to trace the bug.
Finding that sysprof traces the actual program did help.
I tried today to leave the computer in a tty and then go to a X session with ctrl+alt+# and it took just as long. :(
On an AMD laptop, slow to start with, the login process is much slower than it used to be.
Once password is entered, the process seems to drag. Black screen for some time and the mouse pointer, similar to what I am seeing with my problem.
Hum,
Better start to do some checks. Might be related.
Normal disk or SSD disk? Slow plasma startup after login has been an issue for me on standard drives for a while now. Way quicker on SSD drive.
Robin _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
On an AMD laptop, slow to start with, the login process is much slower than it used to be.
Once password is entered, the process seems to drag. Black screen for some time and the mouse pointer, similar to what I am seeing with my problem.
Hum,
Better start to do some checks. Might be related.
Normal disk or SSD disk? Slow plasma startup after login has been an issue for me on standard drives for a while now. Way quicker on SSD drive.
Normal disk. I may put an SSD into it before summer. It is not a powerful laptop as I got caught with the array of features under HP's model numbers and all the sub letters you needed to know. Ooops.
On 05/02/2019 22:21, Robin Laing wrote:
On one computer, switch user is slow to impossible to use.
sddm seems to cause Xorg to hang and I don't know how to debug it.
I have to ssh in from a different computer and kill all processes to get into the computer again. Keyboard is useless but mouse pointer moves. Caps and numlock keys don't work either.
On a reboot, it is not bad but after a few hours, it gets really awful and, like tonight, I had to login from a different computer to kill all user processes.
I don't know if this is related to freezes and crashes on other computers using KDE that I am seeing. One computer that has a full screen crash almost weekly, I cannot ssh into as I don't have a second computer allowed on the network.
I had issues on F28 but since the second last kernel update, it has been awful.
As I need to use the cuda processors for some of the programs I am using, I need the closed source nvidia drivers on this computer. The other two computers are using nouveau drivers.
Robin
After looking at this for a month, I found the problem. Nothing related to software. I had added a switch box to allow me to connect other devices to one of the monitors. Xorg didn't like it.
Took box out, things back to normal.
Robin
-
Patrick Boutilier -
Reindl Harald -
Rex Dieter -
Robin Laing -
Syam