Firefox does not open from taskbar

[TJKwispy]

Describe the bug

Firefox occasionally fails to open from taskbar. Icon responds to click.... then reverts to un-interacted state.

Firefox DOES open from alt+space menu or "start" menu

What did you expect to happen?

Click firefox icon on taskbar > firefox opens.

Output of rpm-ostree status

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
                   Digest: 
sha256:
                  Version: 40.20240922.0 (2024-09-23T05:09:18Z)
          LayeredPackages: xinput

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
                   Digest: 
sha256:
                  Version: 40.20240922.0 (2024-09-23T05:09:18Z)

Hardware

Extra information or context

No response

[ZWx4]

I think I might be having the same issue. For me, both Firefox and LibreWolf intermittently fail to launch from both the application launcher and the task manager. Launching them with the flatpak run command from the terminal seems to work for me every time though; not sure why.

01:58:29.093 UTC [email protected] app-io.gitlab.librewolf\[email protected]: Main process exited, code=exited, status=1/FAILURE
01:58:29.093 UTC [email protected] app-io.gitlab.librewolf\[email protected]: Failed with result 'exit-code'.

01:59:09.052 UTC [email protected] [email protected]: Main process exited, code=exited, status=1/FAILURE
01:59:09.052 UTC [email protected] [email protected]: Failed with result 'exit-code'.

The above is the only thing I see in the Journald Browser when it happens.
I noticed that it didn't happen to Brave. That clue eventually led me to disable the X11 fallback for Firefox/LibreWolf in Flatseal as a workaround; disabling Wayland instead also seems to do the trick for me.
While they now seem to launch successfully every time, the error in the Journald Browser has now changed to this:

02:02:54.042 UTC [email protected] dbus-:[email protected]: Main process exited, code=exited, status=1/FAILURE
02:02:54.042 UTC [email protected] dbus-:[email protected]: Failed with result 'exit-code'.
02:02:54.240 UTC [email protected] kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11

I also see it whenever I launch Brave. Is it safe to ignore?

Additional info

Operating System: Bazzite 40
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2
Kernel Version: 6.9.12-205.fsync.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 31,2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2
Manufacturer: ASUS

$ rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
                   Digest: sha256:f0a715ec44064ebfa14504db0c72b3790542ce3bcd3d7f3b9fb068e6a04197e7
                  Version: 40.20240930.0 (2024-09-30T15:25:37Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
                   Digest: sha256:7714620ce66e84806949720204c07da491b6b31bc6304a27ca620893bf1508b9
                  Version: 40.20240922.0 (2024-09-23T05:09:18Z)

[Mighty-Professional]

You can open flatseal and disable the Wayland Windowing System tab to have it open again. However that worked for a month or so and now I have graphical issues after the latest update.

[TheInfamousAlk]

I also have this issue. I was trying out bazzite to see if I'd like to switch, and this is one of the first interactions I had with the system. Not a great first look. Other applications opened okay, but firefox didn't, about half the time. Ended up not continuing with the distro because of this issue, which happened out of the box with 0 configuration changes.

[Mighty-Professional]

I wish they would fix this, my only major problem with bazzite.

[TheUnimpossible]

Still a problem on my system as well! Just installed yesterday and got it fully up to date.

[TJKwispy]

Issue has not occured since changing from NVidia GPU to AMD GPU. Unknown if this is the resolution, but since i'm no longer experiencing the issue, im calling this closed.

[TheInfamousAlk]

I am still experiencing this issue.

[vmazi]

I solved this by keeping wayland windowing system ON and ENABLING GPU acceleration for firefox in Flatseal

Guessing Wayland needs some access to gpu stuff to let it be stable