I found the reason in my case: (see source below)
when there is more than one dcopserver process, powerbtn.sh rudely shuts down
all of them.
this (extra dcopserver) may come from a second kde session, but also (as
in my case) from a "sudo kate powerbtn.sh" (the second dcopserver lives
on!).
i t
I found the reason in my case: (see source below)
when there is more than one dcopserver process, powerbtn.sh rudely shuts down
all of them.
this (extra dcopserver) may come from a second kde session, but also (as
in my case) from a "sudo kate powerbtn.sh" (the second dcopserver lives
on!).
i t
I found the reason in my case: (see source below)
when there is more than one dcopserver process, powerbtn.sh rudely shuts down
all of them.
this (extra dcopserver) may come from a second kde session, but also (as
in my case) from a "sudo kate powerbtn.sh" (the second dcopserver lives
on!).
i t
I found the reason in my case: (see source below)
when there is more than one dcopserver process, powerbtn.sh rudely shuts down
all of them.
this (extra dcopserver) may come from a second kde session, but also (as
in my case) from a "sudo kate powerbtn.sh" (the second dcopserver lives
on!).
i t
I found the reason in my case: (see source below)
when there is more than one dcopserver process, powerbtn.sh rudely shuts down
all of them.
this (extra dcopserver) may come from a second kde session, but also (as
in my case) from a "sudo kate powerbtn.sh" (the second dcopserver lives
on!).
i t
I found the reason in my case: (see source below)
when there is more than one dcopserver process, powerbtn.sh rudely shuts down
all of them.
this (extra dcopserver) may come from a second kde session, but also (as
in my case) from a "sudo kate powerbtn.sh" (the second dcopserver lives
on!).
i t
