-
Notifications
You must be signed in to change notification settings - Fork 70
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
Blank at start, blank and empty windows, cannot connect. #584
Comments
Works for me on Fedora 39/GNOME/Wayland/Mesa drivers/RPM version of Minigalaxy. Please provide more information:
In non-GNOME DE i see webkit-4.1 crash at launch so i suspect this still related to this issue and we need a proper fix. |
Thanks for reporting this. Sorry for the late reply. I'd say the best way to get figure out what's going on here would be to run minigalaxy from a terminal and copy the output like Tim mentioned. Then we can look into this further. |
Hi ! Also i will precise more my environment . I'm on a GTX 970 (Yeah, nvidia.. I think it's certainly the nvidia drivers that do this) so that's why i'm on X.org, because wayland lack some features for me (like, night mode). Also i got a AMD Ryzen 5600. And it's the rpm build. EDIT : I should precise that some issue with armcord on electron version have this kind of similarity of a blank windows for connection, here the issue : ArmCord/ArmCord#454 That also connected to a Electron issue here : electron/electron#39515 But maybe it as nothing to do with what happening here, dunno |
I also on Nvidia. But in some rare cases i could reproduce this on Fedora 39 in clear VM and free GPU drivers. Problem with webkitgtk process crashing. When i will have more time i'll try dig more, but definitely help wanted here. |
A workaround that was mentioned by the reporter on Discord was to run Minigalaxy like this:
After logging in once, doing so again should not be needed for a while, so this does not have to be repeated often. |
I have the same issue. Since the issue first appeared to me when I was using a custom, stripped-down kernel, I thought it was caused by a missing kernel module, but now that I'm running a distro-provided kernel again (with which I had no problems before), the issue persists, so it must be something else. I have the deb package of version 1.2.5 .
By the way, the workaround works for me, so thank you for that. |
Hello, I have the same issue but for me, the workaround:
does not work... |
I have the same issue on Ubuntu Cinnamon 23.04 with Nvidia proprietary drivers. Minigalaxy installed from flathub. Output from terminal:
|
So, just download Minigalaxy on fedora 38 on a X.org session.
And i'm quite disappointed that the program just... don't work and show blank windows to connect to GOG. So nothing work, and i cannot do anything.
Here the result :
![image](https://private-user-images.githubusercontent.com/37407065/270576944-1b6cc957-651f-426d-9c56-56c04408f904.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ3Njg0NDAsIm5iZiI6MTcyNDc2ODE0MCwicGF0aCI6Ii8zNzQwNzA2NS8yNzA1NzY5NDQtMWI2Y2M5NTctNjUxZi00MjZkLTljNTYtNTZjMDQ0MDhmOTA0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODI3VDE0MTU0MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTk5NThkNTA5ODY4MzBjYmQ4MDAxZTE2ZTY3NDAxOThlN2Q3NjgwMjEzZmJmNTRhOGM3MmU5MjFkMDAxMDdjMmEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.S36UQMjmiJNty9oNJWHBO5hyYOsBiipQyeiCzG4F6SI)
I just installed minigalaxy with repo and launch it, that's all what i do.
The text was updated successfully, but these errors were encountered: