Skip to content

No context menu #522

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

Closed
fabaff opened this issue May 7, 2020 · 5 comments
Closed

No context menu #522

fabaff opened this issue May 7, 2020 · 5 comments

Comments

@fabaff
Copy link

fabaff commented May 7, 2020

With a right click there is no context menu on Gnome. Text can be marked but not copied. Also, it's not possible to copy content with Ctrl+c.

The console shows:

$ qtpass
QSocketNotifier: Can only be used with threads started with QThread
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

Smells a bit like that there is no proper Wayland support or something is still want X11 (perhaps the QT stack?).

  • qtpass: 1.3.2
  • OS: Fedora 31/32

Could be a duplicate of #515.

@fabaff
Copy link
Author

fabaff commented May 14, 2020

@fabaff
Copy link
Author

fabaff commented May 15, 2020

If the menu is showing up then it's misplaced.

Screenshot-20200515085256-1355x1100

@kparal
Copy link

kparal commented Apr 13, 2022

Every time the menu gets completely lost, I have to start qtpass like this:

QT_QPA_PLATFORM=xcb qtpass

Then the menu starts working properly. And on future starts the menu, even without the variable, it still works. But gradually its position shifts, and eventually disappears completely, and the whole cycle needs to be re-done.

It would be great if qtpass could default to using QT_QPA_PLATFORM=xcb until the Wayland issues are properly resolved.

@FSMaxB
Copy link
Contributor

FSMaxB commented Apr 13, 2022

For me this only happens in two monitor setups.

@kparal
Copy link

kparal commented Apr 13, 2022

I also have two monitors, didn't realize this could be related. The workaround is valid, though.

@annejan annejan closed this as completed Sep 21, 2023
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