Public bug reported:
Binary package hint: gnome-utils
1) Open gnome-system-log;
2) File->Open: /var/log/moblock.log;
3) Run 'gksu gedit /etc/moblock/allow.p2p', edit, and save;
4) Run 'gksu moblock-control restart';
5) Moblock spits it's restart/useless range output to gnome-system-log window &
window freezes up before spitting it all out; (moblock restarted just fine)
6) Gnome-system-log, in combination with Xorg used 100% cpu for over 1 minute
before I killed it.
Restarted system-log and everything is fine, it even kept moblock.log in
the list.
ProblemType: Bug
Architecture: i386
Date: Tue Oct 7 15:21:10 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gnome-system-log
NonfreeKernelModules: fglrx
Package: gnome-utils 2.20.0.1-1ubuntu5
PackageArchitecture: i386
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-utils
Uname: Linux 2.6.24-19-generic i686
** Affects: gnome-utils (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
