from the looks of it, its not crashing but rather just starting in the background
can you run this command and start it again see if it works

for the deb version:
echo '{"_id":"bounds","value":{"x":0,"y":136,"width":1200,"height":800,"maximized":true,"fullScreen":false}}' > .config/FreeTube/settings.db

for the flatpak version:
echo '{"_id":"bounds","value":{"x":0,"y":136,"width":1200,"height":800,"maximized":true,"fullScreen":false}}' > .var/app/io.freetubeapp.FreeTube/config/FreeTube/settings.db

and for the dbus errors, a patch will be coming in the next release which will fix that (it originates from upstream. running freetube on my laptop i get the same errors). its harmless either way

This didn't work for me I'm afraid D: same with both deb and flatpack variety's

Hi.

It worked for me with the flatpak version. Thanks to @fakeshell! I did so:

1. install the flatpak version
2. open freetube once. Then it creates the freetube folders and files in /home/furios/.var
3. In Terminal, run : killall freetube , otherwise freetube overrides the ”maximized” parameter at launch. All instances of freetube have to finish before you make the modification.
4. modify the file
   1. open the .var/app/io.freetubeapp.FreeTube/config/FreeTube/settings.db in your text editor and add '{“_id”:”bounds”,”value”:{“x”:0,”y”:136,”width”:1200,”height”:800,”maximized”:true,”fullScreen”:false}' to the file
   2. OR
   3. echo '{“_id”:”bounds”,”value”:{“x”:0,”y”:136,”width”:1200,”height”:800,”maximized”:true,”fullScreen”:false}}' > .var/app/io.freetubeapp.FreeTube/config/FreeTube/settings.db
5. Launch Freetube.
6. If crashes again, check the modified file. The parameter "maximized” has to be set to "true". If not, run close freetube, modify it, and restart.

The forum messes up quotes, so it took a few tries to get freetube to start. So copy and paste did not work.

 `{“_id”:”bounds”,”value”:{“x”:0,”y”:136,”width”:1200,”height”:800,”maximized”:true,”fullScreen”:false}`

I changed the quotes in my last post and detailled a bit more.

yep you were correct, actually typing it fixed my issue

thats not gonna fix it I don't think, the forum actually messes with the characters