Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin Manager: Help button not working on gtk3 #2151

Closed
lpaulsen93 opened this issue May 9, 2019 · 6 comments
Closed

Plugin Manager: Help button not working on gtk3 #2151

lpaulsen93 opened this issue May 9, 2019 · 6 comments

Comments

@lpaulsen93
Copy link
Contributor

I just noticed that the Help button in the Plugin Manager is not working on gtk3. That means, if I click on it nothing happens. Re-compiling Geany and Geany-Plugins for gtk2 made it working again.

The other buttons (Preferences, Keybindings, Close) work without problems.

My environment: Ubuntu 18.04.2, Geany 1.36 (current master), GTK 3.22.30, GLib 2.56.4.

@b4n
Copy link
Member

b4n commented May 9, 2019

Works for me, Debian 9.9, Geany master, GTK 3.22.11, GLib 2.50.3.

@elextr
Copy link
Member

elextr commented May 9, 2019

WFM Mint 19 AKA Ubuntu 18.04, Geany 1.36 (git >= 4bceddb), GTK 3.22.30, GLib 2.56.4

Did you realise help is only available when the plugin is selected?

@kugel-
Copy link
Member

kugel- commented May 10, 2019 via email

@elextr
Copy link
Member

elextr commented May 10, 2019

Also only if the selected plugin implements it.

Yeah that too :)

@lpaulsen93
Copy link
Contributor Author

Did you realise help is only available when the plugin is selected?

Yes, and in that case the button is in-active.

Also only if the selected plugin implements it.

Yes, I know that not all plugins have implemented the help feature. I tried more than one and also re-tried on one which worked on gtk2.

But here is an update:
I just found out that it only happens if I run geany as root. If I work with a normal user login under gtk3 then it works like on gtk2. So I assume this can be closed as it might be caused by some file on my machine having the wrong permission?

@lpaulsen93
Copy link
Contributor Author

Seemed to be a local problem, closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants