[ BUILD # : 200809111401 ]
[ JDK VERSION : 1.6.0_07 ]
After multiple tries, and being very careful to ensure the password
is typed correctly, I have been unable to install a gem via the
NetBeans Gem panel when the Administrative Password is required.
My user is explicitly specified in the sudoers file and can install
the gems from outside of NetBeans, but I am unable to install using
the gem panel.
You need to enter 'su' password, not 'sudo' one. This is for various technical reason, that 'sudo' or more precisely
'gksu in sudo mode' does not work. I'll either:
- create a wiki page and make it more explicit in the dialog
- or fix it (but likely not for 6.5, since I do not know how, so far)
I've added a note about required root password to the gksu dialog, so it is more obvious now. The rest will be fixed
rather in post-6.5. Might be not fixed at all, since I want to come with some enhancement that NetBeans will not need
root access, until user *really* wants so (in the same way as new RubyGems version using ~/.gems).
Oops, sorry, accidentally closed.
Improvement commit: #57bd1c70081d
The need for a root password could be an issue on some desktop Linuxes.
During installation, Ubuntu creates a root user, but doesn't provide the password to the users. The user's default
account is created with sudo privileges instead.
I know, the current support is still a bit odd, due to some gksu restriction (or my ignorance of gksu). I would like
harness terminal emulator and run real 'sudo' instead.
You mention using gksu. gksu is a frontend to su.
I think you want to use gksudo. gksudo is a frontend to sudo.
Any movement on this. I keep getting bitten by this each time I need to modify my gems.
It doesn't look like it would be terribly difficult to hook up gksudo instead of gksu since they have the same command line.
Yes, it should be simple enough. I'll fix this for 6.7.
Sorry, I have to take that back. gksudo doesn't do any better job in passing the env variables of the parent than gksu
in sudo mode (not even when using '--preserve-env', so e.g. GEM_HOME doesn't get passed to the process which causes
problems as in #141136). Ideas welcome, but please note that as we're entering code freeze tomorrow anything requiring
extensive changes will have to wait for the next release.
*** Bug 180694 has been marked as a duplicate of this bug. ***
*** Bug 182169 has been marked as a duplicate of this bug. ***