generated from electron/electron-quick-start
-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
[BUG] Blank screen on login #203
Comments
Is this still an issue in the latest release? |
I tried the v2.1.0 from git and it works all right! No problem with logging in. Flatpak still installs the old v1.1.3. Many thanks for fixing this issue! |
Perfect, tried and it works fine, appreciate the assistance
…On Sat, Apr 13, 2024 at 9:17 AM sunarowicz ***@***.***> wrote:
Is this still an issue in the latest release?
I tried the v2.1.0 from git and it works all right! No problem with
logging in. Flatpak still installs the old v1.1.3.
Many thanks for fixing this issue!
—
Reply to this email directly, view it on GitHub
<#203 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3KNSSXXMWGSWA3G6MXDNQDY5FLB3AVCNFSM6AAAAAA4UJXG3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJTGY4TCNJUG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When i attempt to log in to my nvidia account, it says "login successful, closing window" then the login tab goes blank, yet does not log me in to the app.
To Reproduce
Screenshots
No response
Operating System
Raspbian 64-bit
Desktop Environment
LXDE-based default Raspberry pi desktop environment.
Display Server
X11
Installation method
flatpak
Version
1.13.0
Is this a fresh install of the app or an update from a past version?
Fresh Install
Did this issue appear right away upon installation/updating, or spontaneously?
Spontaneously
Additional context
No response
The text was updated successfully, but these errors were encountered: