Keepalive does not work on sqldeveloper-4.0.3.16.84

scristalli / sql-developer-keepalive

MIT License

149 stars 21 forks source link

Keepalive does not work on sqldeveloper-4.0.3.16.84 #9

Closed bricomatica closed 8 years ago

bricomatica commented 9 years ago

After installing both 1.00 and 1.02 version of keepalive in the latest version of sqldeveloper (sqldeveloper-4.0.3.16.84) I can see the icon but when I click on that I get the following message:

Error during handleEvent on action 'keepalive' (id=351). None of the attached controllers handled the action.

oracle.ide.controller.IdeAction$ControllerDelegatingController@1ad9584d[oracle.ideimpl.controller.ControllersHook$RuleBasedController@1ad9584d[keepalive.KeepaliveController][always-enabled]].

Best regards from Spain :)

scristalli commented 8 years ago

This is very strange, since the controller will always return true in handleEvent(). I have no ideas, and no ways to reproduce the bug. To work on it, I'm afraid more information is needed. Anyone else having this issue?

seliver commented 8 years ago

In my case, the extension will not appear at all. Steps to reproduce:

I installed from update, but selected no to restart as I had to save some scripts
tried exiting the sqldeveloper through alt+f4 but it failed, so had to kill the process
on starting, the icon did not appear
tried installing again, but now selected to restart
after restarting, the icon kept not appearing.

What do you think happened here?

scristalli commented 8 years ago

@seliver, did you try running SQL Developer as administrator as suggested in some closed issues? If not, please try to re-run the program with privileges, re-install the extension and restart.

seliver commented 8 years ago

Will try that and give feedback.

seliver commented 8 years ago

I did opened sqldeveloper with sudo, installed and indeed it worked, but only when executed under sudo.

scristalli commented 8 years ago

@seliver problem has been solved (duplicate of other issues related to permissions), while the issue pointed out by @bricomatica still has not been reproduce. I'm going to close this for now.