jdacronym wrote:
> Well, I'm back running Xfce, and I'm hopeful.  Some things are still
> behaving strangely though:
>
> gnome-power-manager says I have 610697 hours and 25 minutes left on my
> battery.  My other battery life estimates are sane.  I think there are
> several bug reports for that though.
>
> My computer failed to restore from suspend an hour or so ago.  I don't
> know why.  It happened after I installed the latest acpi update, but
> that might be a coincidence.  Since I've rebooted I haven't had a
> hiccup; I'm running one of the WM's that I've known to fail, with all my
> usual applications, and so on.  Suspend/Restore and gnome-screensaver
> remain to be tested.
>
> I've noticed that mythtvbackend, mysqld and a few other mythtv procs are
> running in background.  Is the TV adapter you mentioned mythtv related?
> Should I just kill -9 them, or is there some setting I should try
> fiddling with first?
>
> I can also see the indexer icon in the gnome system tray as well.  I've
> now set it to 50% throttle and told it to use slower indexing.
>
> ksoftirqd/1, klogd and friends seem to be behaving.  Firefox 3 is still
> a resource hog, but hey, whatcha gonna do. :/
>
> Thanks for your help.  When I saw that the latest post on this bug was
> months ago I wasn't holding out much hope of a fix.  At times I was
> considering chucking Ubuntu and converting to Slackware.  I've postponed
> that for now (my Slackolyte friends will not be pleased).
>
>   
Hello
I heard from others that mythtv caused Hardy Heron to lock up.  You 
could try killing it or uninstalling it.  I suspected the Tracker 
indexer but I was wrong. Tracker  has always been very well-behaved on 
my system. 

One program that can cause long-duration CPU hogging is aMule.  If you 
start aMule for the first time or after deleting its log files, it hogs 
CPU time until it has re-indexed and hashed all the files on your system 
that you have permitted it to make available to the world.

Certain regular unix services within Ubuntu are scheduled to run at some 
unearthly hour of the night like 3am. If your machine is not on at that 
time, they will run when you next switch it on after the scheduled time. 
Perhaps one of these us hogging your CPU initially.

Don't give up on Ubuntu. You'll find the culprit soon.
Rob

-- 
Hardy Heron locks up
https://bugs.launchpad.net/bugs/249123
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to