Summary: | gnome-extra/gnome-system-monitor-2.14.1 needs libgksu-1.3.1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mathias Hasselmann <mathias.hasselmann> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | kanelxake |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 119872 | ||
Attachments: | Patch for gnome-system-monitor-2.14.1.ebuild |
Description
Mathias Hasselmann
2006-05-10 02:05:51 UTC
Created attachment 86531 [details, diff]
Patch for gnome-system-monitor-2.14.1.ebuild
My attempt to fix the issue. Don't know if I got the gksu-1.9 issue right.
No, I think we want to disable gksu support in gnome-system-monitor. It falls back to gnomesu, which is what we want anyway. Just unmerge gksu, and re-emerge gnome-system-monitor, as a workaround. gnome-system-monitor-2.16.x seems to dynamically select which to use - gksu or gnomesu via means of dlopen (through GModule). It prefers gksu if libgksu2.so is present, falling back to gnomesu if libgnomesu.so.0 is present and probably failing to do stuff that needs root access if none are present. I cant seem to find how gksu/gnomesu is needed here. It least I couldn't find a clue with 2.18.x and there is no dep on it in 2.14.4 ebuild. Old bug. Still valid? the version of libgksu mentioned here is not even in portage any longer. Nor the verison of gnome-system-monitor. |