On 01/22/2016 01:34 AM, Carlos E. R. wrote:

On 01/22/2016 01:30 AM, tech@reachthetribes.org wrote:

...

How do I restart this KDE process without rebooting my OS? I already tried logging out of KDE and logging back in.

log out log in, in text mode, as root. init 3 init 5 zyper ps to verify exit log in graphical mode

Sometimes logout, then [Ctrl][Alt][backspace], twice, will do the trick. -- Cheers/Saludos Carlos E. R. (openSUSE Leap 42.1, test at Minas-Anor) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2016-01-22 11:30, Freek de Kruijf wrote:

Op vrijdag 22 januari 2016 01:36:26 schreef Carlos E. R.:

...

On 01/22/2016 01:34 AM, Carlos E. R. wrote:

...

On 01/22/2016 01:30 AM, tech@reachthetribes.org wrote:

...

How do I restart this KDE process without rebooting my OS? I already tried logging out of KDE and logging back in.

log out log in, in text mode, as root. init 3 init 5 zyper ps to verify exit log in graphical mode

Sometimes logout, then [Ctrl][Alt][backspace], twice, will do the trick.

The new way of int 3; init 5 is: systemctl restart display-manager.service

Old dog prefers not to remember new tricks when old tricks work ;-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 2016-01-22 14:58, Patrick Shanahan wrote:

* Carlos E. R. <> [01-22-16 08:54]:

...

...

The new way of int 3; init 5 is: systemctl restart display-manager.service

Old dog prefers not to remember new tricks when old tricks work ;-)

This "Old dog" agrees but... Then when the old ways go away (and they will) the new ways are no longer new and everyone else is speaking a different language :(

So I am pushing myself to utilize the "new" ways :)

I would, but there was a promise to keep this particular trick working for "ever" ;-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 2016-01-22 15:18, Patrick Shanahan wrote:

* Carlos E. R. <> [01-22-16 09:04]:

...

I would, but there was a promise to keep this particular trick working for "ever" ;-)

Don't look now, but "for ever" is just around the corner, maybe as early as yesterday :)

Yeah, I know. :-} -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 01/22/2016 09:58 PM, Patrick Shanahan wrote:

* Carlos E. R. [01-22-16 08:54]:

...

On 2016-01-22 11:30, Freek de Kruijf wrote:

...

Op vrijdag 22 januari 2016 01:36:26 schreef Carlos E. R.:

...

On 01/22/2016 01:34 AM, Carlos E. R. wrote:

...

On 01/22/2016 01:30 AM, tech@reachthetribes.org wrote:

...

How do I restart this KDE process without rebooting my OS? I already tried logging out of KDE and logging back in.

log out log in, in text mode, as root. init 3 init 5 zyper ps to verify exit log in graphical mode

Sometimes logout, then [Ctrl][Alt][backspace], twice, will do the trick.

The new way of int 3; init 5 is: systemctl restart display-manager.service

Old dog prefers not to remember new tricks when old tricks work ;-)

This "Old dog" agrees but... Then when the old ways go away (and they will) the new ways are no longer new and everyone else is speaking a different language :(

So I am pushing myself to utilize the "new" ways :)

I know the systemd guys wanted to make the new commands more descriptive (and hence easier to remember). However, in this case it feels that the simple numbers init 1,2,3,4,5 are actually easier to remember than the longer commands systemctl isolate multi-user.target, systemctl isolate graphical.target, etc. I actually tried twice to put in multi-user.target, but kept forgetting to put the "dash" in there, and put in multiuser.target, and it didn't work. So finally I used "init 3" and it worked. It was only later I realized that the dash was why it didn't work. So yes, I think the simple numbers scheme is a little more intuitive, at least for my ageing brain. And I didn't grow into Linux until I was already well past the impressionable ages, so for me I am an old dog trying to learn how to get along with a whole new master that is changing every year, not just a set of new tricks. But hey, I will always like my new master far better than the old one, even with the changes. -- George Box #1: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Box #2: 13.1 | KDE 4.12 | AMD Athlon X3 | 64 | 4GB Laptop #1: 13.1 | KDE 4.12 | Core i7-2620M | 64 | 8GB Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 01/21/2016 04:46 PM, Patrick Shanahan wrote:

* tech@reachthetribes.org [01-21-16 19:33]:

...

I just ran a zypper patch for openSUSE-SU-2016:0188-1 on my Plasma 5.

I prefer not to have to reboot the computer after a patch. There were a bunch of KDE files that were still in use after running zypper ps, so I logged out of KDE and then logged back in. But I still see this process that is running on a deleted file:

--------------------- # zypper ps The following running processes use deleted files:

PID | PPID | UID | User | Command | Service | Files

------+------+------+--------+----------+---------+---------------------------- 11901 | 1 | 1000 | george | kdeinit4 | | /usr/lib64/libxml2.so.2.9.1

systemctl isolate multi-user.target log in to one of the vtty's, ie: <ctrl><alt><f1> as root run zypper ps kill -9 <pid>

In your case: kill -9 11901

systemctl isolate graphical.target

and you have killed the deleted file process and should have a clean kde(plasma5) start.

If you do this every week, you might remember the sequence. But digging out your notes, and finding the page takes less time than simply restarting the machine, because we all know of blindingly fast systemd is at booting. *cough*. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 01/22/2016 01:46 AM, Patrick Shanahan wrote:

kill -9 <pid>

A "kill 9" should be the last resource. And it is possible that these preoceses depends on other processes started in order. I believe it is better to restart the appropriate service. In this case, stop and start graphics ;-) -- Cheers/Saludos Carlos E. R. (openSUSE Leap 42.1, test at Minas-Anor) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 01/22/2016 03:11 AM, Patrick Shanahan wrote:

kdeinit4 and kuiserver(5) frequently are not stopped by leaving/stopping the graphics target.

I think it dies on its own a bit later. Maybe because there is still a user process that did not die on log-out. -- Cheers/Saludos Carlos E. R. (openSUSE Leap 42.1, test at Minas-Anor) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org