I apologize, I thought I closed this one out.
Turns out it was a performance issue. When 'moblock-control restart' is
run, it spits out a bunch of (in my mind) useless info to the log. This
sudden influx of data, caused the log viewer to "freeze" while it loads
the text into memory for viewing. I just didn't give it enough
time...chalk this one up to old hardware.
** Changed in: gnome-utils (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned)
Status: Incomplete => Invalid
--
Gnome-System-Log window uses 100% cpu upon 'gksu moblock-control restart' with
moblock.log in viewer.
https://bugs.launchpad.net/bugs/279806
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
