Bug 433328 - Wrong application name is given in the overview's application section
Summary: Wrong application name is given in the overview's application section
Status: RESOLVED UPSTREAM
Alias: None
Product: plasma-systemmonitor
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-20 12:57 UTC by Riccardo Robecchi
Modified: 2021-02-22 15:28 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screenshot of the overview (113.25 KB, image/png)
2021-02-20 12:57 UTC, Riccardo Robecchi
Details
No Telegram process is running (41.28 KB, image/png)
2021-02-20 12:58 UTC, Riccardo Robecchi
Details
systemd-cgls output (15.26 KB, application/octet-stream)
2021-02-22 11:23 UTC, Riccardo Robecchi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Riccardo Robecchi 2021-02-20 12:57:14 UTC
Created attachment 135967 [details]
Screenshot of the overview

SUMMARY
The overview view gives wrong info about the name of running applications. In this case, Firefox is mistakenly labelled as Telegram Desktop even while the latter is not running at all (see screenshots).

STEPS TO REPRODUCE
1. Open System Monitor

OBSERVED RESULT
The wrong application name is used.

EXPECTED RESULT
The correct application name is used.

SOFTWARE/OS VERSIONS
Linux: KDE Neon
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Riccardo Robecchi 2021-02-20 12:58:04 UTC
Created attachment 135968 [details]
No Telegram process is running
Comment 2 Arjen Hiemstra 2021-02-22 10:41:29 UTC
Can you provide the output of systemd-cgls when this happens? We map from cgroup name to desktop file, I'm quite surprised it ends up at telegram.
Comment 3 Riccardo Robecchi 2021-02-22 11:23:15 UTC
Created attachment 136041 [details]
systemd-cgls output

Here is the requested output.
Comment 4 Arjen Hiemstra 2021-02-22 11:43:55 UTC
So, firefox is placed in a cgroup named `app-appimagekit_d98825e589ea79557384fe149efdfbdd\x2dTelegram_Desktop-f9d4173cdb23432da46641d8d924ad4a.scope` which means we end up mapping that to Telegram.

What I suspect happens, and please correct me if I'm wrong: You start Telegram, then from Telegram open a link that starts Firefox. After that, you close Telegram again.

Telegram apparently just starts Firefox blindly instead of going through something like xdg-open which means that Firefox ends up in Telegram's cgroup. So it looks like this is something that needs to be fixed in Telegram as there is no way to influence its launch behaviour currently.
Comment 5 Riccardo Robecchi 2021-02-22 15:27:41 UTC
(In reply to Arjen Hiemstra from comment #4)
> So, firefox is placed in a cgroup named
> `app-appimagekit_d98825e589ea79557384fe149efdfbdd\x2dTelegram_Desktop-
> f9d4173cdb23432da46641d8d924ad4a.scope` which means we end up mapping that
> to Telegram.
> 
> What I suspect happens, and please correct me if I'm wrong: You start
> Telegram, then from Telegram open a link that starts Firefox. After that,
> you close Telegram again.
> 
> Telegram apparently just starts Firefox blindly instead of going through
> something like xdg-open which means that Firefox ends up in Telegram's
> cgroup. So it looks like this is something that needs to be fixed in
> Telegram as there is no way to influence its launch behaviour currently.

I tried closing and opening Firefox again and it seems your intuition is true: Firefox is now shown with its own, correct name. I will open a bug report in Telegram's repo. I am marking this bug as "resolved upstream".
Comment 6 Riccardo Robecchi 2021-02-22 15:28:21 UTC
Also: thank you for your help. Sorry I forgot to include this in the previous message.