I believe that gksu or gksudo should be a part of the gnome ebuild, as without it, many of the items in the default gnome menu are not accessible and are superfluous. I realise that this _might_ not be considered a bug, but I saw a similar discussion re: xscreensaver, and I thought that I would voice my opinion and let you guys decide. Although the decision re: xscreensaver seems to have been to leave it out, in support of my argument I would note that while the lack of xscreensaver produces a fairly comfortable error message, the lack of gksu simply makes these menu items inaccessible entirely, and many users may not know of the existence of these packages. Further, and this is an argument which applies both to this bug and the xscreensaver case (#6113), the command "emerge gnome" brings in loads of packages which may not be wanted or missed (an example is lynx, coming from evolution--scrollkeeper--docbook), while these are packages which actually produce errors when running gnome for ordinary users. Thanks for your time :) Matt Reproducible: Always Steps to Reproduce: 1. Emerge gnome 2. Attempt to run many of the menu items from Applications --> System Tools. 3. Actual Results: Error message: needs to be root. Expected Results: It should give the chance to enter the root password, or to sudo.
>the lack of gksu simply makes these menu items inaccessible entirely, and many users may not know of the existence of these packages. Installing gksu/sudo doesn't change the menu or launchers in any way. The user would still have to edit their menu launchers by hand and prefix them with gksudo, only to have them be overwritten on the next gnome-system-tools upgrade. All gnome-system-tools ask for a root password on startup, so I see no reason why they are "inaccessible entirely". Installing the gksudo package by default does nothing to make the user more aware of its existence.
