| Summary: | <dev-python/pygtk-2.17: high CPU usage | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | niogic <niogic> |
| Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | matrix47, python |
| Priority: | High | ||
| Version: | 10.1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://bugzilla.gnome.org/show_bug.cgi?id=481569 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 328713 | ||
| Bug Blocks: | |||
| Attachments: | Working dev-python/pygtk-2.17 patch, based upon pygtk-2.16.0 | ||
|
Description
niogic
2010-01-20 19:20:13 UTC
Created attachment 217003 [details] Working dev-python/pygtk-2.17 patch, based upon pygtk-2.16.0 This ebuild is missing 2.6.16.0-r1 gdkcolor-fix patch. Don't know if because it was fixed or not. Ebuild comes from here: http://github.com/init6/init_6 I'd prefer a patch that fixes the problem and/or a link to the upstream bugzilla report that fixes this problem since 2.17 is development cycle release. Well, the only bug I could find is a deluge bug. It's been resolved wontfix, saying it's a (recently fixed) problem in pygtk. http://dev.deluge-torrent.org/ticket/1060 Unluckily, the developer didn't link bug to upstream when he set WONTFIX flag... Maybe I found this one: https://bugzilla.gnome.org/show_bug.cgi?id=481569 Still doesn't apply to pygtk, but same patch should apply ... (In reply to comment #2) > I'd prefer a patch that fixes the problem and/or a link to the upstream > bugzilla report that fixes this problem since 2.17 is development cycle > release. > +1 In the worst case we could rewrite the patch (if it doesn't apply), development cycle : BANG BANG BANG, it's bad ;) Have you verified bumping to pygtk 2.17.0 (and not touching pygobject) fixes your issue? The fix could the in the following commits, would be nice if you could tell us what patch applied to 2.16.0 fixes the issue for you or, at least, tell us how to reproduce the problem http://git.gnome.org/browse/pygtk/commit/?id=3fb3606d803b49e30f4fd492a61f685d6c1540ac http://git.gnome.org/browse/pygtk/commit/?id=482313729f53f417eeb3f8b89268599fee15cba1 http://git.gnome.org/browse/pygtk/commit/?id=f3691203d7405f400a2a731cb4f0ae76488c11ad Are you sure 2.17 is development series? All the other distributions are shipping with it. http://www.archlinux.org/packages/extra/i686/pygtk/ http://cvs.fedoraproject.org/viewvc/rpms/pygtk2/devel/ http://packages.debian.org/sid/python-gtk2 And new media-sound/exaile would need this. It's what upstream says at its homepage: http://www.pygtk.org/ :-| "PyGTK 2.17.0 released Saturday 26 December 2009 by Gian Mario Tagliaretti PyGTK 2.17.0 is the first release in the 2.17.x series. It's unstable, so it should be used with caution. As usual, it's sources can be fetched here. Check out the release announcement and full list of changes." (In reply to comment #6) > Have you verified bumping to pygtk 2.17.0 (and not touching pygobject) fixes > your issue? > No 2.17 bump only didn't fix the issue. I still haven't managed to fix it. You think I need to update pygobject, too? What version should I use? 2.20 is stable (In reply to comment #9) > It's what upstream says at its homepage: http://www.pygtk.org/ :-| > > "PyGTK 2.17.0 released > Saturday 26 December 2009 by Gian Mario Tagliaretti > PyGTK 2.17.0 is the first release in the 2.17.x series. It's unstable, so it > should be used with caution. As usual, it's sources can be fetched here. Check > out the release announcement and full list of changes." > well it's good enough for all the other distros, should be good enough for us too. it was good enough for dbus 1.3 and in the end we had to mask it and go back to 1.2 series. I mailed some days ago to upstream asking them for information related with considering 2.17 "stable enough"... but I have not received any reply from them :-(. If any other can try to contact them, fine :-) (I don't have much time just now) pygtk-2.17 is now in tree. Closing. |
