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 182169 - [69cat] Install of fast debugger to native ruby fails with incorrect admin password
Summary: [69cat] Install of fast debugger to native ruby fails with incorrect admin pa...
Status: RESOLVED DUPLICATE of bug 147024
Alias: None
Product: ruby
Classification: Unclassified
Component: Gems (show other bugs)
Version: 6.x
Hardware: All Linux
: P2 normal (vote)
Assignee: Erno Mononen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-17 07:02 UTC by esmithbss
Modified: 2010-03-23 15:36 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description esmithbss 2010-03-17 07:02:50 UTC 
Product Version = NetBeans IDE Dev (Build 201003160201)
Operating System = Linux version 2.6.32-trunk-686 running on i386
Java; VM; Vendor = 1.6.0_18
Runtime = Java HotSpot(TM) Client VM 16.0-b13

Following an update of the native ruby platform, an attempt to add the fast ruby debugger to the native gems through the IDE failed due to invalid password.
I attempted to enter the proper password 3 separate time, being careful to  enter the password properly each time; however, the sudo/gksu/gksudo call failed each time.
Comment 1 esmithbss 2010-03-17 07:06:27 UTC 
Changed prio to P2.  This error prohibits functionality in the IDE from working; however, a work-around does exist.
Comment 2 Erno Mononen 2010-03-17 07:45:49 UTC 
Are you sure you entered the *root* password? I.e. the 'su' password, not the 'sudo' one. (I know requiring the root password is stupid, but at the moment I don't know how to avoid it, pls see issue #147024).
Comment 3 Erno Mononen 2010-03-23 15:36:22 UTC 
I'm closing this as a dupe of #147024, please reopen if that's not the case here. Thanks.

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