-
-
Notifications
You must be signed in to change notification settings - Fork 98
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
Instantly Signed Out on Linux ARM Flatpak #247
Comments
Looks like a duplicate of #245. That being said, Flatpaks aren't going to be fixed because they're not maintained by me. Most issues on Flatpaks are due sandboxing and I can do nothing about it on my side. As an alternative, for Majaro there're AUR repositories available. I recommend you trying out I'm also trying my best to optimize the |
Actually, that's even more terrifying bug, considering:
If something breaks in completely different browser engine, it could mean the bug is not with both engines or applications. I don't know what could cause that horrible breakages, but I've never experienced something like that, even on more bleeding-edge yet stable Arch Linux distribution. But I would recommend to avoid using Flatpaks anyway (or at least be aware of the consequences of using them) for browsers and web applications, they usually depend on a lot of system resources and can easily break due to the sandboxing. |
Aknowledgements
I have checked that there's no other issue describing the same or
similar problem that I currently have, regardless if it has been
closed or open.
I can confirm that this is not an issue with the Discord website,
but it is a problem specific to the WebCord itself. I have tested
if this bug occurs on Chromium/Chrome or any other Chromium-based
browser that uses unpatched/upstream Chromium engine.
I have tried running the build from the
master
branch and it doesnot have any fixes implemented according to my issue.
My issue describes one of the unstable and/or not fully implemented
features.
I have found a workaround to mitigate or temporarily fix this issue
in affected releases (please write it in Additional context section
below).
Operating System / Platform
🐧️ Linux
Operating system architecture
aarch64 (64-bit ARM)
Electron version
Unable to access that screen
Application version
3.8.1
Bug description
I am able to login successfully. However, after my dashboard with my friends and such appears, I am logged out. In my minimal testing, this also happens on Firefox and Gnome Web. However, randomly, I was able to stay logged in on Firefox.
Additional context
Video showcasing the issue here: https://www.youtube.com/watch?v=buE35LToVQ4
Device: Pine64 PinePhone Pro running Manjaro ARM dev w/Wayland
Firefox Version: 104.0.1-1 (pacman)
Modified User Agent (Firefox): Mozilla/5.0 (Android 10; Mobile; rv:91.0) Gecko/91.0 Firefox/91.0
The text was updated successfully, but these errors were encountered: