12 Mar
2013
12 Mar
'13
2:54 p.m.
I'm not sure how to do it if the process is still running, maybe some else
knows?
Does this only occur when the user tries to disconnect?
Is it happening before then?
Kicker has some problems you might want to look through our bug tracker:
Calvin
On 12 March 2013 10:49, Jean Milot <milot.jean(a)gmail.com> wrote:
I don't if it is a crash.
The user is connected (LTSP) and when he deconnect, the process kicker is
here and take 99% CPU and sometimes the process is terminated.
How i can give you a backtrace ?
Jean
Le 12/03/2013 15:47, Calvin Morrison a écrit :
Does it ever crash? A backtrace would be helpful in dissecting the problem
Calvin
On 12 March 2013 10:46, Jean Milot <milot.jean(a)gmail.com> wrote:
Hi Calvin,
I don't use the kickoff menu.
Jean
Le 12/03/2013 15:32, Calvin Morrison a écrit :
Hi Jean,
are you using the kickoff menu instead of the original kicker menu?
It's notoriously buggy even after a host of cleanups done last year. That
might be somewhere to start.
Calvin
On 12 March 2013 10:28, Jean Milot <milot.jean(a)gmail.com> wrote:
Hello,
I have some problem with the process kicker.
For example, it takes 99% CPU.
I have about 10 kde desktop launch on the server (ltsp) and sometime the
process kicker is not terminate at the end.
Thanks four your help.
Sincerely,
Jean
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting