Firefox fails to open or takes a long time

Very first time on linux ever so maybe the issue is obvious. But when i try to start firefox (from taskbar shortcut if that matters?) it sometimes wont start at all or just takes a long time. I ran a journal that showed the following in the log "bazzite flatpak[4213]: Warning: ConnectToCompositor() try again : Resource temporarily unavailable" not sure what to do to resolve it :S If i need to share more info outside of this or the two images let me know. I did a search and didn't find info that was related but maybe i missed something
9 Replies
termdisc
termdisc•4w ago
run flatpak run org.mozilla.firefox and see if there is an output that helps there
Draegos
DraegosOP•4w ago
first time i did it opened a new firefox instantly faster than ever before. closed that and then to test tried it again and this time got that error spammed again. here is the tailend of the output Warning: ConnectToCompositor() try again : Resource temporarily unavailable Warning: ConnectToCompositor() try again : Resource temporarily unavailable Warning: ConnectToCompositor() try again : Resource temporarily unavailable Error: ConnectToCompositor() connect() failed repeatedly : Resource temporarily unavailable Error: we don't have any display, WAYLAND_DISPLAY='/run/flatpak/wayland-0' DISPLAY='(null)' waited a while and tried it again from the terminal. - first time opened FF instantly - closed FF myself - ran the line again - generated the same error again above
termdisc
termdisc•4w ago
what does your socket settings look like in Flatseal for Firefox?
termdisc
termdisc•4w ago
these are defaults
No description
Draegos
DraegosOP•4w ago
looks to be the same as the default you linked
Draegos
DraegosOP•4w ago
No description
asen23
asen23•4w ago
looks like some regression from firefox https://github.com/Floorp-Projects/Floorp/issues/1452
GitHub
[Bug]: Floorp randomly fails to start due to ConnectToCompositor er...
Pre-Submission Checklist I have checked the existing/closed issues to ensure this issue has not already been reported. I am using the latest supported version of the browser. I have tried disabling...
asen23
asen23•4w ago
maybe try disabling wayland socket in flatseal
Draegos
DraegosOP•4w ago
will try that and keep an eye on that open issue thanks 🙂
Want results from more Discord servers?
Add your server