Bug 462908

Summary:	Application stuck on panel on startup creates a new instance
Product:	[Plasma] plasmashell	Reporter:	Emanuele <emanu.d3b>
Component:	Panel	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	nate, niccolo.venerandi, nicolas.fella
Priority:	NOR
Version First Reported In:	5.26.3
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	log

Description Emanuele 2022-12-11 14:24:12 UTC

Created attachment 154499 [details]
log

As per the title, every time I start an application blocked on the panel it creates a new instance, this happens especially with Google Chrome from flathub.
attached these are the logs that are generated when I start chrome.
I hope it helps to improve the quality of KDE plasma. :-)
OS: Fedora 37 KDE spin
Session: Wayland
plasma version: 5.26.3
KDE frameworks: 5.100.0
A short video that better explains visually: https://www.youtube.com/watch?v=xDAip74IQ3Y

Comment 1 veggero 2022-12-11 14:43:38 UTC

Hey, one question; I don't get from the video what exactly you mean by "stuck on panel" or "blocked on the panel"? (Nel senso, intendi app pinnatta come mostri, o è proprio "bloccata" in qualche senso?)

Comment 2 Emanuele 2022-12-11 14:54:29 UTC

(In reply to veggero from comment #1)
> Hey, one question; I don't get from the video what exactly you mean by
> "stuck on panel" or "blocked on the panel"? (Nel senso, intendi app pinnatta
> come mostri, o è proprio "bloccata" in qualche senso?)

App pinnata sul pannello, l'applicazione funziona senza problemi è solo un problema di coerenze.
The application works without problems, it's just a consistency problem, in this case the problem is with the Google Chrome application from flathub, it also happens randomly with others.
thank you

Comment 3 veggero 2022-12-11 14:57:49 UTC

Uhm, that makes me think it's an issue of how flatpak installs chrome, rather than plasma's fault? But I'm not sure.

Comment 4 Emanuele 2022-12-11 15:40:53 UTC

(In reply to veggero from comment #3)
> Uhm, that makes me think it's an issue of how flatpak installs chrome,
> rather than plasma's fault? But I'm not sure.

I don't know, but I don't have this problem on GNOME with the dash to dock extension

Comment 5 Nicolas Fella 2022-12-13 16:07:53 UTC

https://github.com/flathub/com.google.Chrome/issues/83 is somewhat relevant here

Comment 6 Nicolas Fella 2022-12-13 16:22:14 UTC

Indeed, adding "StartupWMClass=google-chrome" to the Chrome Flatpak's desktop file makes it work as expected

Comment 7 Nicolas Fella 2022-12-17 15:25:06 UTC

In the Chrome case this is explained by https://github.com/flathub/com.google.Chrome/issues/83

If there are other applications affected the cause will be similar