1) Install IDE as root, use as non-root
2) Run IDE, open Tools->Plugins, switch to Installed tab.
Choose any active item, invoke popup menu.
"Deactivate" option is disabled in menu (one issue), "Deactivate" button is also disabled (another issue) and I can`t
check this item (third issue) => can`t deactivate this item at all.
The only option is to deactivate the whole category.
The similar about inactive item.
*** Issue 166748 has been marked as a duplicate of this issue. ***
as mentioned in issue 166748 - this is stopper for NB 6.7
... also please look at patch proposed by jarda in issue 166748
I tested jtulach's patch and it fixes the problem, now plugins that are owned by root can be activated and deactivated
by normal user.
pushed Jarda`s patch to core-main.
So much honor, I am default owner of this P1 now. What am I supposed to do? Just integrate to 6.7 clone? I guess so,
as the review has been done and fix verified.
could you please verify the fix in trunk (I mean check for regressions mainly). Thanks in advance.
please wait for verification from Michael (needs to be integrated into release67 today by 8pm CEST).
The latest trunk builds (from main-silver) failed so we probably we won`t have another build till 8pm CEST.
It's already in core-main :
build available from :
A-ha.. I see. Michael, please verify.
From zip files? Is it okey?
Looks fixed using specified zip on OpenSolaris x86.
BTW I faced another problem, but exception reported claimed it as duplicate.
It's about activating then deactivating plugin without restart then another
attempt to deactivate. Not sure this is due to root/user will check.
I suppose it is a GO for this fix (the exception issue is handled separately in 134595).
zip bundle on OpenSolaris x86.
Integrated into 'main-golden', will be available in build *200906110201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Dmitry Lipin <email@example.com>
Log: Issue #165841 Can`t deactivate particular module in shared installation (Jarda`s patch)
The fix is not in 6.7 release!
and broken link at
*** Issue 170202 has been marked as a duplicate of this issue. ***
Jarda, you are not quite right. The fix is there indeed, check
Well, in that case there's either another similar problem, or a regression in the 6.7.1 release download, as I've been
having problems in a fresh installation of that version (see #170202 for full description)