Created attachment 147537 [details] system_monitor_chrome_1 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Install some apps like chromium, mattermost or slack (via flatpak) 2. Open system monitor applications view 3. See that those apps are duplicated OBSERVED RESULT Some apps, in my case all installed via flatpak, are duplicated in the apps view EXPECTED RESULT The list of running apps only shows one entry per application SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Created attachment 147538 [details] system_monitor_chrome_2
Created attachment 147539 [details] system_monitor_mattermost_1
Created attachment 147540 [details] system_monitor_mattermost_2
Created attachment 147541 [details] system_monitor_slack_1
Created attachment 147542 [details] system_monitor_slack_2
Sorry, forgot to add system info Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i7-7500U CPU @ 2.70GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620
It doesn't look like duplications but actually two instances since they also have two different values? Could you post the about of systemd-cgls when this happens?
Created attachment 148453 [details] Log for systemd-cgls command Here is the output of the command
in user@1000.service (not app.slice!) │ │ ├─app-flatpak-com.slack.Slack-3946.scope │ │ │ ├─3946 bwrap --args 41 /app/bin/zypak-helper child - /app/extra/lib/sla… │ │ │ ├─3969 bwrap --args 41 /app/bin/zypak-helper child - /app/extra/lib/sla… │ │ │ ├─3983 /app/extra/lib/slack/slack --type=zygote --enable-crashpad --ena… │ │ │ └─4385 /app/extra/lib/slack/slack --type=renderer --enable-crashpad --c… │ │ ├─app-flatpak-com.mattermost.Desktop-3948.scope │ │ │ ├─3948 bwrap --args 42 /app/bin/zypak-helper child - /app/main/mattermo… │ │ │ ├─3970 bwrap --args 42 /app/bin/zypak-helper child - /app/main/mattermo… │ │ │ ├─3981 /app/main/mattermost-desktop --type=zygote │ │ │ ├─4211 /app/main/mattermost-desktop --type=renderer --user-data-dir=/ho… │ │ │ ├─4217 /app/main/mattermost-desktop --type=renderer --user-data-dir=/ho… │ │ │ ├─4243 /app/main/mattermost-desktop --type=renderer --user-data-dir=/ho… │ │ │ └─4258 /app/main/mattermost-desktop --type=renderer --user-data-dir=/ho… │ │ ├─app-flatpak-com.mattermost.Desktop-3785.scope │ │ │ ├─3785 bwrap --args 39 mattermost-flatpak │ │ │ ├─3855 bwrap --args 41 xdg-dbus-proxy --args=43 │ │ │ ├─3859 xdg-dbus-proxy --args=43 │ │ │ ├─3875 bwrap --args 39 mattermost-flatpak │ │ │ ├─3877 /app/main/mattermost-desktop │ │ │ ├─3884 cat │ │ │ ├─3885 cat │ │ │ ├─3940 /app/main/mattermost-desktop --type=zygote --no-zygote-sandbox │ │ │ ├─4161 /app/main/mattermost-desktop --type=gpu-process --field-trial-ha… │ │ │ └─4185 /app/main/mattermost-desktop --type=utility --utility-sub-type=n… │ │ ├─app-flatpak-com.slack.Slack-3780.scope │ │ │ ├─3780 bwrap --args 40 slack │ │ │ ├─3857 bwrap --args 42 xdg-dbus-proxy --args=44 │ │ │ ├─3858 xdg-dbus-proxy --args=44 │ │ │ ├─3869 bwrap --args 40 slack │ │ │ ├─3879 /app/extra/lib/slack/slack -s --enable-features=WebRTCPipeWireCa… │ │ │ ├─3888 cat │ │ │ ├─3889 cat │ │ │ ├─3938 /app/extra/lib/slack/slack --type=zygote --no-zygote-sandbox --e… │ │ │ ├─3942 /app/extra/lib/slack/chrome-sandbox /app/extra/lib/slack/slack -… │ │ │ ├─4139 /app/extra/lib/slack/chrome_crashpad_handler --monitor-self-anno… │ │ │ ├─4244 /app/extra/lib/slack/slack --type=gpu-process --enable-crashpad … │ │ │ └─4292 /app/extra/lib/slack/slack --type=utility --utility-sub-type=net… So there are really two different cgroups each. There's no systemmonitor bug here but maybe downstream one?