-
Notifications
You must be signed in to change notification settings - Fork 62
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
AppImage immediately crashes on fedora with sway #135
Comments
@skewballfox would you be able to test it on a different window manager (something like Gnome would be perfect)? Just so I can narrow down the issue to either Fedora or the window manager itself. Thanks! |
I can't. This system was installed from a net installer and is missing most of the dependencies, I'm also launching my WM from bash_profile rather than using a login manager. I can install it from source if there is some debug info that might provide |
@skewballfox Gotcha! One thing we can try before going in to the dev build would be to install some of the dependencies for Fedora required by tauri. There 3 libraries it would expect are: If the app still has trouble launching, I can walk you through a development build to see where it's going wrong |
I actually installed those yesterday, though the packages have a different
naming convention on fedora the rest of the red hat family
…On Thu, Jul 28, 2022 at 6:26 PM Andrew Huynh ***@***.***> wrote:
@skewballfox <https://github.com/skewballfox> Gotcha! One thing we can
try before going in to the dev build would be to install some of the
dependencies for Fedora required by tauri
<https://tauri.app/v1/guides/getting-started/prerequisites#setting-up-linux>
.
There 3 libraries it would expect are: libwebkit2gtk-4.0-37, libgtk-3-0,
and libappindicator3-1
If the app still has trouble launching, I can walk you through a
development build to see where it's going wrong
—
Reply to this email directly, view it on GitHub
<#135 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG7UDR6MWDVH27GV6O3JO43VWMJIRANCNFSM542K7ZRA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
so after running
|
Thanks for digging into this @skewballfox , I'll report this issue upstream. Seems like Just curious, would running the application w/ superuser rights make that error go away? |
Just looking at that error code, No. X11 and Wayland have very different architectures: under X applications had direct access to keyboard input(like all input, not just the input to their respective window). This was part of the reason why wayland was adopted, because of the inherent security risk of that design feature BTW, looks like this is already reported upstream: |
Is there a way to tell Also, is there a way to interact with spyglass via the command-line? The reason I'm asking is because with sway, generally you create the keybindings in the config. Having a way to call the running application directly via a CLI would be an easy way to get around global shortcut setting being unavailable for the foreseeable future in wayland |
EDIT: nevermind it looks like they stripped out that feature (I cannot find any alternative, it looks like it's impossible to specify the backend now as a user) |
not sure which is the culprit so I added both. I'm assuming that since spyglass app is trying to register a shortcut, this has to do with the window manager I am using. I'm guessing you are trying to communicate with some settings daemon which doesn't exist.
upon launching the app image, an grey X window appears with the text "search" and this text displays to stdout:
afterwords the window crashes, the commandline seems to hang, no system tray icon appears.
about my system:
OS: fedora 36
kernel: 5.18.13-200.fc36.x86_64
window manager: sway 1.7
app image version: spyglass_22.7.4_amd64.AppImage
The text was updated successfully, but these errors were encountered: