Peter Humphrey wrote: > On Wednesday, 20 May 2020 16:56:29 BST Dale wrote: > >> Well, I didn't know I could kill that thing. I been logging out and >> back in which annoys the stuffing out of me. I have to close three >> browsers, several file managers plus whatever else I am doing before I >> can logout. Then I have to reopen all that when I log back in. > Why do you have to do that yourself? I'd have thought that sddm would take > care of it for you. It does for me.
I have a saved session but if I restart everything at once, my internet chokes and some tabs fail to load. So, I have the basic stuff in a saved session but still have to do some myself. Of course I close stuff before logging out just to be safe. >> On top of that, I have to wait for a download to stop as well. Yea, it's >> annoying, putting it mildly. lol I thought if I killed it, it would >> take the whole GUI thingy with it . Since it is still chewing away, >> makes me think about the Pacman days, I'll kill that thing in a few >> minutes, after closing important stuff first just in case. > Whenever an update changes a lot of GUI stuff I drop to a VT and tell it > "/etc/ > init.d/xdm restart && logout". That ought to be equivalent to killing sddm > but > kinder. > In this case, just logging out and right back in works. The first time I did it, I switched to a terminal and checked after logging out. The memory sddm was using was already down to almost nothing. I knew then that logging out and right back in was enough. It only takes a few seconds to log out and back in but it is annoying because at times, I may have 40 tabs open. Those have to reload as well which with my DSL, takes a while. After a update, especially a KDE or qt update, I logout and go to boot runlevel and back. That restarts everything KDE plus others that may need restarting as well. I find some stuff is real touchy after updates. Dale :-) :-)
