-
Notifications
You must be signed in to change notification settings - Fork 901
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]: Electron window does not open in development mode #6762
Comments
This isnt an issue on our side. Your Wayland/Nvidia system setup could be related to the issue you're experiencing. The logs indicate several warnings related to Wayland and GPU, including things like libva errors and issues with nVidia's nvidia-drm video driver |
If it is a wayland/nvidia problem it is only happening in the dev environment, because if I build locally ( |
Are you sure you havent modified anything else. Im unable to reproduce this at all. |
I have not modified anything aside from enabling electron logging, and disabling gpu compositing as a test for seeing if it was a nvidia problem. The only error I have is the electron one that's in the log above:
|
|
It does seem to be system related; I ran it through sway and Hyprland compositors and both have the problem, but running it through gamescope has no problem. Sorry, for the trouble Edit: Running it in xwayland (using |
Guidelines
Describe the bug
git clone https://github.com/FreeTubeApp/FreeTube.git && cd FreeTube
)yarn install
yarn run dev
Log output is attached in "Additional Information".
Expected Behavior
Electron window opens properly
Issue Labels
only happens in developer mode, causes crash
FreeTube Version
e1000d8
Operating System Version
Linux 6.13.1-arch1-1 #1 SMP PREEMPT_DYNAMIC x86_64 GNU/Linux
Installation Method
other
Primary API used
Local API
Last Known Working FreeTube Version (If Any)
No response
Additional Information
I have a Wayland/Nvidia system (I am using the
--disable-gpu-compositing
flag however).Log Output (Including electron logging)
Nightly Build
The text was updated successfully, but these errors were encountered: