Hi all,
1 - I do not know where to post a bug report.
2 - In a previous mail, I tried to explain that kdesu "survived" after some use, requiring then the maximum CPU resources. I understand now in what circumstances: this appens while reopenning a session that was closed when a program is still open and that it was opened with kdesu. - I had this to be clearer (than Google!): press "Alt"+"F2", type "kdesu whatever", Once whatever launched and running, close the session. Reopen the (same user) session, and check the processor activity.
3 - Is there a way to record a session to make it the one that is used at the next re-opening (was an OSS_10.3 feature) ?
Sincerely, Patrick
Sorry about that mail:
On Sunday 18 September 2011 13:54:08 Patrick Serru wrote:
While reopenning a session that was closed when a program is still open and that it was opened with kdesu. - I add this to be clearer (than Google!): press "Alt"+"F2", type "kdesu whatever", Once whatever launched and running, close the session. Reopen the (same user) session, and check the processor(s) activity.
Should I repport that bug on http://bugs.pearsoncomputing.net /buglist.cgi?quicksearch=kdesu ?
Patrick
Sorry about that mail:
On Sunday 18 September 2011 13:54:08 Patrick Serru wrote:
While reopenning a session that was closed when a program is still open and that it was opened with kdesu. - I add this to be clearer (than Google!): press "Alt"+"F2", type "kdesu whatever", Once whatever launched and running, close the session. Reopen the (same user) session, and check the processor(s) activity.
Should I repport that bug on http://bugs.pearsoncomputing.net/buglist.cgi?quicksearch=kdesu ?
Patrick
Are you using the nightly builds or 3.5.12? There was a kdesudo issue that caused 100% CPU usage that *should* have been dealt with in the nightly builds some time ago.
Thanks!
Tim
-
Patrick Serru -
Timothy Pearson