-
Notifications
You must be signed in to change notification settings - Fork 261
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
Error: OpenSSL not found on startup #1889
Comments
Looking at the wiki (but an earlier revision, seems people are editing things away) the solution for Fedora is to install openssl. If you had working before though, maybe try to reinstall openssl and restart GNOME? |
Reinstallation worked. However it is rather strange that it just stopped working, timing that lines up fairly well with the last release. |
Cool! |
And you're still on Fedora 40, you haven't upgraded to Fedora 41? Only thing I can think of, then, is that you might have uninstalled whatever DNF package it was that originally pulled in openssl automatically as a dependency on your system. When that happens, DNF will also remove any "unneeded" dependency packages. (Fedora has been steadily eliminating dependencies on openssl in the base install, so it's very possible that your system reached a state where it was no longer required by anything.) Because GSConnect is installed in your That's a guess, but it's my best guess for why that would happen in any situation other than upgrading to a new Fedora release. But the good news is, now that you've installed openssl directly, DNF considers it a user-installed package and won't ever autoremove it when clearing out dependencies. Closing this, as the need to provide better communication to users when there are issues with openssl not being available (among other things) is already being tracked in #862 and #1834. |
Describe the bug
Hi everyone. I have been using GSConnect for months just fine on Fedora 40 (Not 41, yet). Within the last week it has stopped working and I get "Error: OpenSSL not found on startup" every time I start up my laptop. As a result, GSConnect does not work at all.
Steps to reproduce
It happens on start up, there is nothing to reproduce.
Expected behavior
No response
GSConnect version
58
Installed from
GNOME Extensions website
GNOME Shell version
46
Linux distribution/release
Fedora 40
Paired device(s)
No response
KDE Connect app version
1.32.5
Plugin(s)
No response
Support log
No response
Screenshots
No response
Notes
No response
The text was updated successfully, but these errors were encountered: