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

Flatpak Version 4.7.0 Crashes on startup: Error while decrypting the ciphertext provided to safeStorage.decryptString #78

Open
TynInks opened this issue Feb 7, 2024 · 12 comments

Comments

@TynInks
Copy link

TynInks commented Feb 7, 2024

OS: Fedora 39
Flatpak: 1.15.6
Webcord: 4.7.0

Since updating to 4.7.0, Webcord crashes on startup. I have attempted a reinstall, including purging the folder in .var, but still just crashes.

GUI Launch Result:
GUI Launch

Terminal Launch Result (flatpak run io.github.spacingbat3.webcord ):
Terminal Launch

Let me know if you need any other info from me. Thank you!

@TynInks
Copy link
Author

TynInks commented Feb 9, 2024

I must not have purged the .var file properly in my initial test. From advice on the linuxmint sub-reddit, I deleted one file:

/home/owen/.var/app/io.github.spacingbat3.webcord/config/WebCord/windowState

Upon relaunching Webcord, it regenerates this file and Webcord works properly.

However, this only works once. Subsequent launches of Webcord result in the original error.

@axtloss
Copy link
Collaborator

axtloss commented Feb 9, 2024

This may be fixed with webcord v4.7.1, I will bump the flatpak

@axtloss
Copy link
Collaborator

axtloss commented Feb 9, 2024

While the new version is building and getting published to the main flathub repo, it can be tested with the command here #79 (comment)

@axtloss
Copy link
Collaborator

axtloss commented Feb 9, 2024

If it does not work with that build, please test if the issue occurs with any non-flatpak build (the appimage should work most reliably) from https://github.com/SpacingBat3/WebCord/releases/tag/v4.7.1

@TynInks
Copy link
Author

TynInks commented Feb 9, 2024

The Flatpak of 4.7.1 still has this same bug.

The appimage does not have this bug, it works properly.

@lorecapob
Copy link

I too have the same issue with the Flatpak of 4.7.0. I just downgraded to the 4.6.1 for the moment since it works fine.

OS: Fedora 39
Flatpak version: 1.15.6
Webcord version: 4.7.0

Schermata del 2024-02-09 17-39-20

@axtloss
Copy link
Collaborator

axtloss commented Feb 9, 2024

hm im not sure what the issue could be, nothing really changed on the flatpak side for it to break

@lorecapob
Copy link

This morning Flatpak asked me to update the app to the version 4.7.1 but it still has the same issue. To be honest, it only worked the first time after the update, then it crashed with the same error again.

@TynInks
Copy link
Author

TynInks commented Feb 11, 2024

This error also occurs on my other Fedora system with the same Flatpak version, as well as a Debian 12 system I have with Flatpak 1.14.4. All of these have the default sandboxing permissions as well.

I'm 3-for-3 on the update to either Webcord 4.7.0 or 4.7.1 breaking. Rolling back to 4.6.1 solves the issue on all systems.

@TynInks
Copy link
Author

TynInks commented Feb 11, 2024

I noticed that flathub.json was changed to say, "This application is no longer maintained. Please use the non-flatpak version of webcord or a different discord client."

I hope I'm just misunderstanding the situation, but I take it that means the main developer has stepped away from this project? Is there a way to change ownership / get a new maintainer?

@AzureRaptor
Copy link

I too am concerned about the above message.

If it's only the flatpak version, why?

Snaps are way too dependent on canonical's whims, and every appimage I've ever has the misfortune to try has either been sloppily built or just plain broken. The management infrastructure for them is also way behind flatpak or even snap.

@marcelovbcfilho
Copy link

Version 4.8.0 and the same problem still persists, does anyone found a workaround?
image

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

5 participants