This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 180694 - Installation of Ruby gems fails in Ubuntu because of the ROOT password
Summary: Installation of Ruby gems fails in Ubuntu because of the ROOT password
Status: RESOLVED DUPLICATE of bug 147024
Alias: None
Product: ruby
Classification: Unclassified
Component: Gems (show other bugs)
Version: 6.x
Hardware: PC Linux
: P1 normal (vote)
Assignee: Erno Mononen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-14 07:58 UTC by georgiomic
Modified: 2011-11-16 16:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description georgiomic 2010-02-14 07:58:38 UTC
If a user tries to install a gem using the Gem Manager (and a Ruby installation - have not confirmed whether this is also true with JRuby) in an Ubuntu system, he is prompted for a Root password.

An Ubuntu system has the root password disabled by default. However, for any root task the User account is used (as a sudoer) and their password is enough.

* NetBeans, when installing gem, only asks for a root password (disabled by default) and thus cannot proceed with the gem installation (fails with Any password, unless the root password is enabled in Ubuntu which is not recommended).

- NetBeans and the Gem Manager on a valid ruby 1.8.4 (or other) installation in an Ubuntu system should request for the (sudoer) User's password as any other application would do. This would allow any gems to be installed directly from the NetBeans Platform.
Comment 1 Erno Mononen 2010-02-15 01:53:52 UTC
Thanks for the report. This is a known issue, the problem is that gksu (in sudo mode) or gksudo don't preserve env vars correctly and hence can't be used here (please check the comments in https://netbeans.org/bugzilla/show_bug.cgi?id=147024 for more info). This is of course very unfortunate as most Ubuntu users run into this - if anyone knows a solution for the env vars problem I'd be more than glad to hear it.

*** This bug has been marked as a duplicate of bug 147024 ***