Skip to content
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

Closed
theuser18 opened this issue Nov 13, 2024 · 4 comments
Closed

Error: OpenSSL not found on startup #1889

theuser18 opened this issue Nov 13, 2024 · 4 comments
Labels
duplicate An issue that has already been reported

Comments

@theuser18
Copy link

theuser18 commented Nov 13, 2024

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

@github-actions github-actions bot added the triage An issue that needs confirmation and labeling label Nov 13, 2024
@RodrigoPrestes
Copy link

Looking at the wiki (but an earlier revision, seems people are editing things away) the solution for Fedora is to install openssl.
dnf install openssl for Workstation and rpm-ostree install openssl then reboot for Atomic.

If you had working before though, maybe try to reinstall openssl and restart GNOME?

@theuser18
Copy link
Author

Reinstallation worked. However it is rather strange that it just stopped working, timing that lines up fairly well with the last release.

@RodrigoPrestes
Copy link

Cool!
Looking it up again looks like current wiki has instructions about this: https://github.com/GSConnect/gnome-shell-extension-gsconnect/wiki/Help#openssl-not-found.
Should be fine to close this issue then?

@ferdnyc
Copy link
Member

ferdnyc commented Nov 22, 2024

@theuser18

However it is rather strange that it just stopped working, timing that lines up fairly well with the last release.

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 $HOME/.local/ tree, DNF can't know about it and might therefore conclude that openssl is no longer required by anything.

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.

@ferdnyc ferdnyc closed this as completed Nov 22, 2024
@ferdnyc ferdnyc added duplicate An issue that has already been reported and removed triage An issue that needs confirmation and labeling labels Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate An issue that has already been reported
Projects
None yet
Development

No branches or pull requests

3 participants