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

Issue + workaround for intellij disappearing popups #2640

Closed
randomlurker opened this Issue Feb 17, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@randomlurker

randomlurker commented Feb 17, 2017

Qubes OS version (e.g., R3.2):

R3.2

Affected TemplateVMs (e.g., fedora-23, if applicable):

standalone vm based on debian-8 and upgraded to stretch using qubes doc.


Expected behavior:

Intellij popups (action selection, class search) should open correctly

Actual behavior:

The popups open, but almost always close instantaneously

Steps to reproduce the behavior:

  • Download the community version of intellij.
  • Create a random project
  • try to open the action dialog (ctrl-maj-a), or the class search (ctrl-maj-n)
  • sometimes it works several times in a row at launch, but when you start messing with the ui / running a program, then it no longer works.

Workaround specific to intellij

It's possible to tell intellij to create a different type of popup (that works fine) by using the java option suggested in this thread :
https://youtrack.jetbrains.com/issue/IDEA-160215
This seems to solve all my problems for now.

General notes:

I had almost given up when I found the workaround, and the only information I found was this old discussion that didn't seem to be resolved.
https://groups.google.com/forum/#!msg/qubes-users/6_fIA0wm7QU/DDm2s9i2CW0J

Maybe someone could add this in the doc ? A working IDE is a huge deal for devs, and this could easily put them off Qubes.

@andrewdavidwong andrewdavidwong added this to the Documentation/website milestone Feb 19, 2017

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Feb 19, 2017

Member

Maybe someone could add this in the doc ?

Would you mind submitting a pull request for this? The instructions are here: https://www.qubes-os.org/doc/doc-guidelines/

Member

andrewdavidwong commented Feb 19, 2017

Maybe someone could add this in the doc ?

Would you mind submitting a pull request for this? The instructions are here: https://www.qubes-os.org/doc/doc-guidelines/

@unman

This comment has been minimized.

Show comment
Hide comment
@unman

unman Mar 2, 2017

Member

@andrewdavidwong This doesn't seem to be a Qubes issue at all - that is, it manifests on Qubes but it is an upstream application issue: the solution isn't Qubes specific.
If you really want I can put something in the docs, but it does not seem appropriate to me.

Member

unman commented Mar 2, 2017

@andrewdavidwong This doesn't seem to be a Qubes issue at all - that is, it manifests on Qubes but it is an upstream application issue: the solution isn't Qubes specific.
If you really want I can put something in the docs, but it does not seem appropriate to me.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Mar 2, 2017

Member

@unman: Thanks. Closing as notourbug.

Member

andrewdavidwong commented Mar 2, 2017

@unman: Thanks. Closing as notourbug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment