On Fri, Dec 30, 2011 at 1:13 PM, Nermin Celik wrote:
>
>> Try killing speech-dispatch and see what happens?
>>
>> It may be a bad install..
>>
>> You could remove it and reinstall
>>
>>
> 1.I killed the speech-dispatch and also the python. CPU usage went to
> normal level.
> 2. Restarted the comp
>
>
> Try killing speech-dispatch and see what happens?
>
> It may be a bad install..
>
> You could remove it and reinstall
>
>
1.I killed the speech-dispatch and also the python. CPU usage went to
normal level.
2. Restarted the computer and CPU usage was normal.
However the screen froze in both i
On 12/30/2011 12:49 PM, Nermin Celik wrote:
Joe, nermin is me the user.
Well, you are taking up all of the CPU time, aren't you?
Seriously, whatever those two processes are is what's wrong. And, it's
probably best not to start out blaming your hardware for slowdowns
instead of checking for
On Sat, Dec 31, 2011 at 7:37 AM, Joe Zeff wrote:
> On 12/30/2011 12:24 PM, Nermin Celik wrote:
>
>> 1947 nermin20 0 12912 656 448 S 90.0 0.0
>> 796:13.37 speech-dispatch
>> 1935 nermin20 0 84488 20m 11m R85.4 0.6
>> 798:50.77 python
>>
>
> There's yo
On Fri, Dec 30, 2011 at 12:37 PM, Joe Zeff wrote:
> On 12/30/2011 12:24 PM, Nermin Celik wrote:
>
>> 1947 nermin20 0 12912 656 448 S 90.0 0.0
>> 796:13.37 speech-dispatch
>> 1935 nermin20 0 84488 20m 11m R85.4 0.6
>> 798:50.77 python
>>
>
> There's y
On 12/30/2011 12:24 PM, Nermin Celik wrote:
1947 nermin20 0 12912 656 448 S 90.0 0.0
796:13.37 speech-dispatch
1935 nermin20 0 84488 20m 11m R85.4 0.6
798:50.77 python
There's your culprit. I don't know what nermin is, but it's taking up
almost
On Sat, Dec 31, 2011 at 1:14 AM, Patrick O'Callaghan
wrote:
> On Fri, 2011-12-30 at 18:00 +1100, Nermin Celik wrote:
> > Just looking at System Monitor > Resources > , it shows that CPU1 and
> > CPU2
> > are 100% used, although l'm not running any programs. Hence it seems
> > that
> > my computer
On Fri, 2011-12-30 at 18:00 +1100, Nermin Celik wrote:
> Just looking at System Monitor > Resources > , it shows that CPU1 and
> CPU2
> are 100% used, although l'm not running any programs. Hence it seems
> that
> my computer hardware is not compatible with F16 (default). Do you
> agree?
Unlikely,
