Summary: | net-misc/vino was hogging my CPU | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Fred Krogh <fkrogh> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | pacho |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://bugzilla.gnome.org/show_bug.cgi?id=579355 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 263083 |
Description
Fred Krogh
2009-07-15 21:30:08 UTC
I just did a reboot, vino is running, and is behaving itself. Well the hog was back. Emerge -C of vino and killing vino job fixed it. Unlike before when Re-emerging vino and rebooting the hog was back. I don't see a need for vino on my system, but there is something fishy with it, or with something it uses. It seems vino got reinstalled again, and after a reboot is causing no problem. I don't seem to have anything useful that might help in tracking this down. I might note that at present /usr/libexec/vino-server is sleeping. When it was hogging the CPU there were two vino things listed by ps, but I don't recall the name of the other one. Well, vino is at it again. When it running ps shows two copies, such as 3110 m /usr/libexec/vino-server -- S 3329 m /usr/libexec/vino-server R On every query with ps the process ID of the one with "R" changes. If the one with "S" is killed the process ID of both changes. If the one with "R" is killed only its ID changes as it does whether it is killed or not. The only way to stop it from hogging the CPU is an "emerge -C vino", and then kill the vino jobs. Perhaps all this will suggest something? Maybe it could be this problem: http://bugzilla.gnome.org/show_bug.cgi?id=167610 what do you get for 'xdpyinfo | grep DAMAGE'? (In reply to comment #5) > Maybe it could be this problem: > http://bugzilla.gnome.org/show_bug.cgi?id=167610 Not exactly the same as I have nvidia drivers. > what do you get for 'xdpyinfo | grep DAMAGE'? I get "DAMAGE" do you use session-saving ? If so I think this is a new bug and should be reported upstream. You'll have to provide vino version, gnome-session version, and a backtrace or a profile to see where vino is looping like crazy. Maybe this hog is caused by vino-server being started lots of times, then, it would be: http://bugzilla.gnome.org/show_bug.cgi?id=579355 (I say this because of comment #4 that says that two processes seems to be being executed) I think comment 8 has the answer. In the gconf editor, I have auto_save_session checked. For the record, vino and gnome-session are both at version 2.26.2. In 2.26.2-r1 with locale installation fix. Thanks for reporting. I just rebooted with vino-2.26.2-r1. ps shows 687 m /usr/libexec/vino-server -- R 3348 m /usr/libexec/vino-server -- S and the CPU is busy. After a "killall vino-server", I have 3646 m /usr/libexec/vino-server -- S and the CPU is taking it easy. Sorry. I just rebooted again, and all seems normal. Maybe it is o.k. |