[Bug]: FreeTube starts, but window is no reachable nor visible

[notalexnot]

Guidelines

• [X] I have encountered this bug in the latest release of FreeTube.
• [X] I have searched the issue tracker for a bug report that matches the one I want to file, without success.
• [X] I have searched the documentation for information that matches the description of the bug I want to file, without success.

Describe the bug

I updated FreeTube from 0.17.0 to 0.17.1. I didn't use it during 0.17.0, so I don't know if it worked by then.

After this, trying to open FreeTube only showed a program running in the taskbar, but the window is not reachable nor visible. I have to close it from the taskbar. I could only find the errors by opening from terminal.

Expected Behavior

FreeTube window is visible and usable.

Issue Labels

usability issue

FreeTube Version

v0.17.1

Operating System Version

Windows 10 Version 21H2

Installation Method

.exe

Primary API used

Local API

Last Known Working FreeTube Version (If Any)

Before 0.17.0 (I think)

Additional Information

TypeError: Cannot destructure property 'value' of 'object null' as it is null.
    at C:\Users\usr\AppData\Local\Programs\FreeTube\resources\app.asar\dist\main.js:1:4801
    at async W (C:\Users\usr\AppData\Local\Programs\FreeTube\resources\app.asar\dist\main.js:1:4757)
    at async App.<anonymous> (C:\Users\usr\AppData\Local\Programs\FreeTube\resources\app.asar\dist\main.js:1:9167)
(node:1628) UnhandledPromiseRejectionWarning: Error: Cannot create a secure cookie from an insecure URL
(Use `FreeTube --trace-warnings ...` to show where the warning was created)
(node:1628) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1628) UnhandledPromiseRejectionWarning: Error: Cannot create a secure cookie from an insecure URL
(node:1628) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
[6316:0820/175855.740:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is disabled, ANGLE is

Nightly Build

• [ ] I have encountered this bug in the latest nightly build.

[efb4f5ff-1298-471a-8973-3d47447115dc]

Is this still an issue on the latest nightly build?

[github-actions[bot]]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

[MaxiMii05]

This is the issue I am always encountering on Wayland.

[MaxiMii05]

Can confirm that this issue is present in the newest nightly AppImage, however in contrast to the Flatpak I'm using, the window doesn't stay blank. Still, the errors are present in the journal.

[efb4f5ff-1298-471a-8973-3d47447115dc]

Just to clarify what build version did u use?

[MaxiMii05]

I was using nightly-2164. The blank window in the Flatpak version might be unrelated to this issue. Also the errors are visible in the journal for the nightly build, but I'm not sure what is 'broken' because of that. Playing a video works like normal, but I didn't do any further testing. Also, [6316:0820/175855.740:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is disabled, ANGLE is is not present in my testing. I'm not sure what to make out of this. Maybe we're dealing with three different issues, maybe some of them were already fixed. Let me know if I can help in any way. For me, the Flatpak version currently not working with Wayland (blank window) is the reason I'm not using Wayland yet.

• Fedora 36
• Nvidia GPU with proprietary drivers version 520

Edit: I'm quite certain my issue is unrelated to this original issue. I get a window, but the content is blank. I just realized the original issue didn't get any window at all. Also, it worked in an earlier version while my issue has been persisting since I started using FreeTube. I've always thought it's because of Wayland+Nvidia, but maybe I'll put in a separate issue if I find the time.

[niboe-boop]

I have just come across this myself and I'd like to add to this. I have the same symptom, the window does not appear at all. See this screenshot of my alt+tab.

I'm running the exact same version of Windows as OP and using nightly build 2568. Once the issue appeared, it now persists across all fresh installations of Freetube that I've tried. For me, it began when I left a video paused in fullscreen for a long time and was using other applications in other windows. Then I left my computer on overnight, closing laptop lid, and when I tried to return to the video in the morning is when I noticed.

The error message I get is slightly different:

Note: Although the nightly build suffers from this bug, whatever changed my OS to become such that it triggers this bug happened while running v0.18.0. I can't try to replicate that change on the nightly build until I can undo whatever this is on the OS side.