Does anyone experience the same? If you start firefox freshly from dash, the browser window comes up and is ready to be used, but Gnome’s top bar keeps on showing the spinning wheel next to firefox application for about 10 seconds (see screenshot):
This is a common issue with several applications - notably also LibreOffice, related to StartupNotify. It sometimes causes an icon to appear in the task switcher only after perhaps 30 seconds after it has loaded. To work around the issue, copy the .desktop launcher to your ~/.local/share/applications directory, and set “StartupNotify=false”.
Thanks, that workaround did its job. I noticed that this issue is also with Terminal.
Bad thing is that if I do a window switch with Meta-Tab, then it happens occasionally that Mutter “forgets” some windows completely – they are not appearing in the Meta-Tab switch popup anymore.
Only these apps for which “StartupNotify=true” in the .desktop launcher may have the issue: the default is “false”. Typically, GTK3/GTK4 apps do not have the issue, so I am surprised to hear you have the issue with Terminal. I do not know of a bug report on this, but the problem, at least on Ubuntu, exists for as long as I use Gnome 3 on Ubuntu (and that is from the beginning). If it is to be filed, it is for Gnome Shell, obviously. It is the shell’s job to have the task switcher right. I am pretty certain that the issue has not been introduced with F37.
Fun thing is that while the wheel is spinning (and, yes, it takes 20-30 seconds), I can logout, the Terminal windows closes, but the entry in the bar plus the spinning wheel stays for those 20-30 seconds.
(I’m pretty sure that I would have noticed this behavior on F36, as it is really annoying )
I am confused now, because your screenshot does not show Terminal. In your first post, you suggested the application immediately opens, yet in the top bar the spinning wheel keeps turning (and in the Alt+Tab switcher, the icon is not (yet) there. Not seeing Gnome Terminal means it is not properly launching.
Second, I suggested to set “StartupNotify=false”, however, you kept it on “true”.
By the way — an easy way to help contribute to the project is to run with “updates testing” enabled, and then hopefully we can catch these issues while they’re still in the update system waiting for feedback.