-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
uBuntu & Intellij - No permissions #39
Comments
This is crazy. I can see the file in the terminal and in the file manager. However the selection window in IntelliJ can not see the file. Below is a screen shot. I will mention this. IntelliJ was installed using Flatpak and VisualVM was installed using a Ubuntu (deb) installer. I don't know if this has something to do with it. |
Could be read rights, could be a bug in IntelliJ, that file chooser component is quite special, with filters. |
Also the refresh is quite bugged, clicking reload and reopening the dialog might fix it. |
Here is what I have found so far. Ubuntu and PopOS have an app store. IntelliJ and Android Studio are on this store. However, they are installed with Flatpack instead of a regular Debian file. This is what I now know from trial and error. If I uninstall the flatpak version of android studio and IntelliJ. Restart computer. Then manually install the deb version (by going to intellij website and downloading it) then running it manually, it will FINALLY see the Apparently flatpak installed programs don't have full access to I hope this information can help someone in the future! |
Hi, I'm having a similar problem. Using |
Hello,
I am having difficulties getting Intellij to launch VisualVM using the "Run with VisualVM [ProjectName]."
I can see that it is some type of permission issue. However when I give full read, write, execute permissions to the file, it still doesn't work. The stacktrace is posted below.
Also, is
/usr/share/visualvm/visualvm/lib/deployed/jdk15/linux/libprofilerinterface.so
the correct file to start for Linux users?Thank you!
The text was updated successfully, but these errors were encountered: