gutsy regression: very high temp on turion 64 CPU

Not solved in Tribe 3.

$uname -r
2.6.22-8-generic

Traced back to be caused because X11 output module is the default output module instead of Xv.
Playing video media or entering sites that are rich with Flash media or Java - will cause overheating.

I experience the same on my Dell Inspiron 700m, very inefficient multimedia. Changing the output module in VNC got rid of the problem, but what should be done about Java/Flash? My cpu goes over 170f making it uncomfortable to use. My laptop never got this hot even when working under full load in Fesity.

Same here, running 32bit gutsy 2.6.22-14-generic on a turion processor. The laptop overheats quickly, even when cpu load is small. I've followed the suggestions on this page and installed noscript to disable java and flash, but it doesnt seem to have made a difference.

You should check your cpu cooling ribs, cleaning them lowered the temperature by 10-20 celsius degrees.

Yeah, Ive taken the laptop apart and cleaned it with compressed air. Still
the same issue, windows works fine on it and I wasnt getting this problem
with feisty.

Cheers for the input.

On 11/12/2007, damagedspline <email address hidden> wrote:
>
> You should check your cpu cooling ribs, cleaning them lowered the
> temperature by 10-20 celsius degrees.
>
> --
> gutsy regression: very high temp on turion 64 CPU
> https://bugs.launchpad.net/bugs/124765
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!