-
-
Notifications
You must be signed in to change notification settings - Fork 163
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
Segfault on wayland #663
Comments
one quick alternative for regular users (non-devs), without having to adjust code and recompile, is to add an environment variable on launch (you can also set this graphically using KDE/Gnome):
You'll need XWayland, but on most distros that will likely be present. If not, you can install it if necessary, or wait for the fix. Or use the normal |
Any updates on this? Im still seeing the segfault on wayland with xwayland installed and the environment variable set and after making changes to the git package listed above and rebuilding/reinstalling the package by deleting the compiled .tar.zst and recompiling and using pacman -U to install the new package (only breaking it down since default makepkg -si behavior is to ignore if there is a package already built in the same directory, would be easy to mistakenly reinstall the same package without edits) |
I encount the same problem:
Need a more convenient way to use qtpass because using Xwayland sucks a little bit if you choose to use Wayland… (it makes no sense 😅 ). |
Opening the application results on a segfault.
$ qtpass util.cpp: 45 "/usr/local/texlive/2023/bin/x86_64-linux:/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/flutter/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/lib/rustup/bin" [1] 2011461 segmentation fault (core dumped) qtpass
I believe the issue comes from wayland :
The line QCursor::pos() always return (0,0) and because it does not find a screen at this location it return NULL which causes the segfault down the line.
A simple fix I used was to add this line :
The text was updated successfully, but these errors were encountered: