This bug may have been fixed in Natty, but it's back in Oneiric. I've opened a
new bug:
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/874474
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in Ubuntu.
https://bugs.l
Whoops, I typoed the bug number in the changelog...anyway:
This bug was fixed in the package virt-manager - 0.8.6-1ubuntu2
---
virt-manager (0.8.6-1ubuntu2) natty; urgency=low
* debian/patches/fork_before_using_gconf.patch: fork earlier to resolve
cpu usage issue and appindicat
I think the poll is a red herring...the new version of virt-manager
actually does have a 1000ms timeout when I strace it.
So, oddly the issue doesn't pop up with virt-manager --debug...and
looking though the code, when --debug is not used, it calls this:
def drop_tty():
# We fork and setsid s
** Changed in: virt-manager (Ubuntu Natty)
Milestone: None => natty-alpha-3
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in ubuntu.
https://bugs.launchpad.net/bugs/707313
Title:
[natty] virt-manager use 100% CPU
--
de
Oops, sorry about the noise, the symptoms and location were extremely similar:
python + gtk + main loop + poll = 100% cpu!
Maybe the cause is similar too? (poll misused?)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in ubuntu
I don't believe it is the same issue. I rebuilt pygtk packages with the
patch in gnome bug #640738, and although they fix the issue in that bug,
they don't seem to fix the issue with virt-manager.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subs
I believe this is a dupe of:
https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/664920
Which has more information.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in ubuntu.
https://bugs.launchpad.net/bugs/707313
Title:
[na
I think this may be related to pygtk... note the backtrace (repeated
many times, always stuck at this point:
0x7fe7811dc4b3 in __poll (fds=, nfds=, timeout=)
at ../sysdeps/unix/sysv/linux/poll.c:87
87 in ../sysdeps/unix/sysv/linux/poll.c
(gdb) bt
#0 0x7fe7811dc4b3 in __poll (fds
