-
Notifications
You must be signed in to change notification settings - Fork 455
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
No UI showing on the app & top bar sub menu buttons don't work Flatpak version #3793
Comments
Thanks for reporting. A flatpack binary is very sandboxed, and I have a feeling that frontend/backend communication isn't working correctly. As a note I may add that I saw the Windows version in a similar state when the network was slow - it took about 1minute or more for the empty window to be populated with content. The console showed that it was substituting some fonts as the ones it needed took too long to load (or were still loading, I couldn't tell). Logs might shed some more light on what's going on here, maybe this document helps in finding them. |
Just remembered I can open it in the terminal via the properties in the start menu. This is what I got:
|
Thanks a lot, I think that's helpful! I don't know if it's compounding the issue visible here, but from the logs it seems to have trouble getting anything useful from the project it tries to load. Maybe if you would rename the data-directory it would have a chance to start fresh? What's unclear to me, and probably only local tests can clarify this, is if this issue could also occur on other platforms, or if it is truly specific to the local state in your home directory. |
When you say rename the |
Apologies for the ambiguity - that's exactly what I mean, rename it to something else and restart GitButler to see if fresh metadata does the trick. |
Thanks a lot, I am glad it's 'fixed'! Maybe you could run one more experiment, put back the broken version, and rename just the Thanks a lot! |
Oh, apologies, and thanks so much for your help! Indeed it's a It's strange, as without that folder, the UI should come up blank and one has to recreate everything. |
Could it be because i ran the app image version? Even though (I'm pretty sure) I ran the flatpak > appimage > flatpak on the day i reported this and the flatpak still didn't work so i'm not too sure. Just tested while writing this. Its not working again. I renamed Should I uninstall and reinstall the flatpak version, delete all cache/config files and try again? If so is |
That directory contains all shared data - each project then has a Of course it would also be interesting if the non-flatpack version works better. Thanks again for your help, it's much appreciated! |
I did install it from aur using the gitbutler-bin package, which is using the debian binary. It seems to related to hardware acceleration issues in WebKitGTK.
You can also add it to your shell to make it persistent:
And just pasting here the same error as the person above:
|
Thanks for sharing! Somehow I feel there are two issues at play here - general issues around hardware acceleration, and others about an invalid state on disk that prevents the UI from coming up. Maybe we just got onto the wrong track due to the seeming relevance of the local state directory. |
I downloaded the Flatpak version from Software Manager on my linux mint PC, and when i open it theres nothing there:
And none of the buttons in the top bar do anything within the app itself. If its a button that goes to a website that works, and the quit button in File works but other than that, e.g. 'Share Debug Info...' in help it freezes for a sec and then goes back to the blank app.
This isn't happening on the Appimage version from the git butler website (a welcome-esque screen shows up), only the flatpak version (which i downloaded the Software Manager app that comes with linux mint) doesn't work.
Im not sure what other information is useful so just ask if you need more. Also not sure if this has been reported already, I tried to look but couldn't find anything that was similar, so sorry if its been reported.
The text was updated successfully, but these errors were encountered: