Bug 508231 - Google Chrome shows as two applications
Summary: Google Chrome shows as two applications
Status: CONFIRMED
Alias: None
Product: plasma-systemmonitor
Classification: Applications
Component: general (other bugs)
Version First Reported In: 6.4.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-08-14 09:27 UTC by Peter Eszlari
Modified: 2025-08-19 08:14 UTC (History)
4 users (show)

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


Attachments
System Monitor shows two entries for Chrome with two names (181.12 KB, image/png)
2025-08-18 18:42 UTC, TraceyC
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Eszlari 2025-08-14 09:27:19 UTC
SUMMARY

Starting Google Chrome results in two entries under "Applications".

STEPS TO REPRODUCE
1. download Chrome from google.com
2. install the *.deb/*.rpm file
3. start Chrome
4. open plasma-systemmonitor

OBSERVED RESULT

two entries under "Applications"

EXPECTED RESULT

one entry under "Applications"

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.16
Qt Version: 6.9.1

ADDITIONAL INFORMATION
Google Chrome 139.0.7258.127
Comment 1 David Edmundson 2025-08-14 15:05:25 UTC
Can you include output of "systemd-cgls" after starting chrome please.

and then reopen this ticket
Comment 2 Peter Eszlari 2025-08-14 17:24:58 UTC
CGroup /:
-.slice
├─user.slice
│ └─user-1000.slice
│   ├─user@1000.service …
│   │ ├─session.slice
│   │ │ ├─xdg-permission-store.service
│   │ │ │ └─1696 /usr/libexec/xdg-permission-store
│   │ │ ├─dbus-broker.service
│   │ │ │ ├─1602 /usr/bin/dbus-broker-launch --scope user
│   │ │ │ └─1603 dbus-broker --log 11 --controller 10 --machine-id 046b57fc97fc…
│   │ │ ├─xdg-document-portal.service
│   │ │ │ ├─1702 /usr/libexec/xdg-document-portal
│   │ │ │ └─1713 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subt…
│   │ │ ├─xdg-desktop-portal.service
│   │ │ │ └─1686 /usr/libexec/xdg-desktop-portal
│   │ │ ├─plasma-ksmserver.service
│   │ │ │ └─1706 /usr/bin/ksmserver
│   │ │ ├─pipewire-pulse.service
│   │ │ │ └─1763 /usr/bin/pipewire-pulse
│   │ │ ├─wireplumber.service
│   │ │ │ └─1762 /usr/bin/wireplumber -p main
│   │ │ ├─plasma-kwin_x11.service
│   │ │ │ └─1707 /usr/bin/kwin_x11 --replace
│   │ │ ├─plasma-kded6.service
│   │ │ │ ├─1705 /usr/bin/kded6
│   │ │ │ └─1902 /usr/bin/xsettingsd
│   │ │ ├─plasma-xdg-desktop-portal-kde.service
│   │ │ │ └─1923 /usr/libexec/xdg-desktop-portal-kde
│   │ │ ├─plasma-plasmashell.service
│   │ │ │ └─1904 /usr/bin/plasmashell --no-respawn
│   │ │ ├─at-spi-dbus-bus.service
│   │ │ │ ├─2035 /usr/libexec/at-spi2/at-spi-bus-launcher
│   │ │ │ ├─2045 /usr/bin/dbus-broker-launch --config-file=/usr/share/defaults/…
│   │ │ │ └─2046 dbus-broker --log 10 --controller 9 --machine-id 046b57fc97fc4…
│   │ │ └─pipewire.service
│   │ │   └─1761 /usr/bin/pipewire
│   │ ├─background.slice
│   │ │ ├─plasma-kactivitymanagerd.service
│   │ │ │ └─1855 /usr/libexec/kactivitymanagerd
│   │ │ ├─plasma-polkit-agent.service
│   │ │ │ └─1921 /usr/libexec/polkit-kde-authentication-agent-1
│   │ │ ├─plasma-kscreen.service
│   │ │ │ └─1907 /usr/libexec/kf6/kscreen_backend_launcher
│   │ │ ├─plasma-xembedsniproxy.service
│   │ │ │ └─1925 /usr/bin/xembedsniproxy
│   │ │ ├─plasma-kglobalaccel.service
│   │ │ │ └─1676 /usr/libexec/kglobalacceld
│   │ │ ├─plasma-gmenudbusmenuproxy.service
│   │ │ │ └─1918 /usr/bin/gmenudbusmenuproxy
│   │ │ ├─plasma-kaccess.service
│   │ │ │ └─1919 /usr/bin/kaccess
│   │ │ ├─plasma-powerdevil.service
│   │ │ │ └─1922 /usr/libexec/org_kde_powerdevil
│   │ │ ├─kde-baloo.service
│   │ │ │ └─1685 /usr/libexec/kf6/baloo_file
│   │ │ └─plasma-dolphin.service
│   │ │   └─2945 /usr/bin/dolphin --daemon
│   │ ├─app.slice
│   │ │ ├─drkonqi-coredump-pickup.service
│   │ │ │ └─1917 /usr/libexec/drkonqi-coredump-processor --settle-first --picku…
│   │ │ ├─app-org.kde.discover.notifier@autostart.service
│   │ │ │ └─2012 /usr/libexec/DiscoverNotifier --check-delay 20
│   │ │ ├─app-org.kde.konsole-10322.scope
│   │ │ │ └─10322 /usr/bin/konsole
│   │ │ ├─app-org.opensuse.yast.Packager@351b21da91fc480a96f241602fc76587.service
│   │ │ │ └─3523 /usr/libexec/kf6/kdesud
│   │ │ ├─app-dbus\x2d:1.2\x2dorg.kde.kwalletd6.slice
│   │ │ │ └─dbus-:1.2-org.kde.kwalletd6@0.service
│   │ │ │   └─9511 /usr/bin/kwalletd6
│   │ │ ├─app-dbus\x2d:1.56\x2dorg.a11y.atspi.Registry.slice
│   │ │ │ └─dbus-:1.56-org.a11y.atspi.Registry@0.service
│   │ │ │   └─2053 /usr/libexec/at-spi2/at-spi2-registryd --use-gnome-session
│   │ │ ├─dconf.service
│   │ │ │ └─1801 /usr/libexec/dconf-service
│   │ │ ├─app-com.google.Chrome-10367.scope
│   │ │ │ └─10367 /opt/google/chrome/chrome
│   │ │ ├─app-google\x2dchrome@0d20e8d32db14f87b14697b2182a19c0.service
│   │ │ │ ├─10371 cat
│   │ │ │ ├─10372 cat
│   │ │ │ ├─10374 /opt/google/chrome/chrome_crashpad_handler --monitor-self --m…
│   │ │ │ ├─10376 /opt/google/chrome/chrome_crashpad_handler --no-periodic-task…
│   │ │ │ ├─10382 /opt/google/chrome/chrome --type=zygote --no-zygote-sandbox -…
│   │ │ │ ├─10383 /opt/google/chrome/chrome --type=zygote --crashpad-handler-pi…
│   │ │ │ ├─10385 /opt/google/chrome/chrome --type=zygote --crashpad-handler-pi…
│   │ │ │ ├─10413 /opt/google/chrome/chrome --type=gpu-process --ozone-platform…
│   │ │ │ ├─10417 /opt/google/chrome/chrome --type=utility --utility-sub-type=n…
│   │ │ │ ├─10419 /opt/google/chrome/chrome --type=utility --utility-sub-type=s…
│   │ │ │ ├─10445 /opt/google/chrome/chrome --type=renderer --crashpad-handler-…
│   │ │ │ ├─10446 /opt/google/chrome/chrome --type=renderer --crashpad-handler-…
│   │ │ │ └─10677 /opt/google/chrome/chrome --type=renderer --crashpad-handler-…
│   │ │ ├─app-dbus\x2d:1.2\x2dorg.kde.secretservicecompat.slice
│   │ │ │ └─dbus-:1.2-org.kde.secretservicecompat@0.service
│   │ │ │   ├─9535 /usr/bin/ksecretd
│   │ │ │   └─9558 keyboxd --homedir /home/linux/.gnupg --daemon
│   │ │ ├─xdg-desktop-portal-gtk.service
│   │ │ │ └─2004 /usr/libexec/xdg-desktop-portal-gtk
│   │ │ ├─obex.service
│   │ │ │ └─1906 /usr/libexec/bluetooth/obexd
│   │ │ ├─app-org.kde.konsole@b72d0e0c98be4e929c8ffd89a24df9d3.service
│   │ │ │ ├─10331 /bin/bash
│   │ │ │ └─10693 systemd-cgls
│   │ │ └─spice-vdagent.service
│   │ │   └─2002 /usr/bin/spice-vdagent -x
│   │ └─init.scope
│   │   ├─1578 /usr/lib/systemd/systemd --user
│   │   └─1580 (sd-pam)
│   └─session-1.scope
│     ├─1574 /usr/libexec/sddm/sddm-helper --socket /tmp/sddm-auth-ff064c4c-f61…
│     └─1590 /usr/bin/startplasma-x11
├─init.scope
│ └─1 /usr/lib/systemd/systemd --switched-root --system --deserialize=52
└─system.slice
  ├─irqbalance.service
  │ └─1229 /usr/sbin/irqbalance --banmod megaraid_sas
  ├─systemd-udevd.service …
  │ └─udev
  │   └─1036 /usr/lib/systemd/systemd-udevd
  ├─dbus-broker.service
  │ ├─1222 /usr/bin/dbus-broker-launch --scope system --audit
  │ └─1224 dbus-broker --log 10 --controller 9 --machine-id 046b57fc97fc4c9e9ef…
  ├─polkit.service
  │ └─1248 /usr/libexec/polkit-1/polkitd --no-debug
  ├─rtkit-daemon.service
  │ └─1729 /usr/libexec/rtkit/rtkit-daemon
  ├─chronyd.service
  │ └─1432 /usr/sbin/chronyd -n
  ├─auditd.service
  │ └─1192 /usr/sbin/auditd
  ├─display-manager-legacy.service
  │ ├─1546 /usr/bin/sddm
  │ └─1560 /usr/bin/Xorg.bin -nolisten tcp -background none -seat seat0 vt2 -au…
  ├─ModemManager.service
  │ └─1334 /usr/sbin/ModemManager
  ├─systemd-journald.service
  │ └─985 /usr/lib/systemd/systemd-journald
  ├─power-profiles-daemon.service
  │ └─1998 /usr/libexec/power-profiles-daemon
  ├─fwupd.service
  │ └─3005 /usr/libexec/fwupd/fwupd
  ├─NetworkManager.service
  │ └─1407 /usr/sbin/NetworkManager --no-daemon
  ├─switcheroo-control.service
  │ └─1256 /usr/libexec/switcheroo-control
  ├─flatpak-system-helper.service
  │ └─2162 /usr/libexec/flatpak-system-helper
  ├─firewalld.service
  │ └─1339 /usr/bin/python3.13 /usr/sbin/firewalld --nofork --nopid
  ├─qemu-guest-agent.service
  │ └─4062 /usr/bin/qemu-ga -p /dev/virtio-ports/org.qemu.guest_agent.0
  ├─spice-vdagentd.service
  │ └─2066 /usr/sbin/spice-vdagentd
  ├─upower.service
  │ └─1734 /usr/libexec/upower/upowerd
  ├─udisks2.service
  │ └─1695 /usr/libexec/udisks2/udisksd
  ├─system-getty.slice
  │ └─getty@tty1.service
  │   └─1545 /sbin/agetty -o -- \u --noreset --noclear - linux
  ├─avahi-daemon.service
  │ └─1226 avahi-daemon: running [linux.local]
  └─systemd-logind.service
    └─1258 /usr/lib/systemd/systemd-logind
Comment 3 TraceyC 2025-08-15 22:34:07 UTC
I'm not able to reproduce in git-master
Comment 4 Peter Eszlari 2025-08-16 15:02:49 UTC
(In reply to TraceyC from comment #3)
> I'm not able to reproduce in git-master

I can with a build from:
https://en.opensuse.org/SDB:Argon_and_Krypton

git-master build from 2025-08-16, 10:42:
https://download.opensuse.org/repositories/KDE:/Medias/images/iso/?P=*Krypton.*.iso
Comment 5 TraceyC 2025-08-18 18:42:04 UTC
Created attachment 184220 [details]
System Monitor shows two entries for Chrome with two names

I confirm this on git-master on Solus

I'm wondering if this is related to Google packaging two .desktop files, which carries over into the rpm?

https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_139.0.7258.127-1_amd64.deb contains two .desktop files

google-chrome.desktop
com.google.Chrome.desktop
Comment 6 TraceyC 2025-08-18 18:42:14 UTC
.
Comment 7 Arjen Hiemstra 2025-08-19 08:14:45 UTC
> │   │ │ ├─app-com.google.Chrome-10367.scope
> │   │ │ │ └─10367 /opt/google/chrome/chrome
> │   │ │ ├─app-google\x2dchrome@0d20e8d32db14f87b14697b2182a19c0.service
> │   │ │ │ ├─10371 cat
> │   │ │ │ ├─10372 cat
> │   │ │ │ ├─10374 /opt/google/chrome/chrome_crashpad_handler --monitor-self --m…
> │   │ │ │ ├─10376 /opt/google/chrome/chrome_crashpad_handler --no-periodic-task…
> │   │ │ │ ├─10382 /opt/google/chrome/chrome --type=zygote --no-zygote-sandbox -…
> │   │ │ │ ├─10383 /opt/google/chrome/chrome --type=zygote --crashpad-handler-pi…
> │   │ │ │ ├─10385 /opt/google/chrome/chrome --type=zygote --crashpad-handler-pi…
> │   │ │ │ ├─10413 /opt/google/chrome/chrome --type=gpu-process --ozone-platform…
> │   │ │ │ ├─10417 /opt/google/chrome/chrome --type=utility --utility-sub-type=n…
> │   │ │ │ ├─10419 /opt/google/chrome/chrome --type=utility --utility-sub-type=s…
> │   │ │ │ ├─10445 /opt/google/chrome/chrome --type=renderer --crashpad-handler-…
> │   │ │ │ ├─10446 /opt/google/chrome/chrome --type=renderer --crashpad-handler-…
> │   │ │ │ └─10677 /opt/google/chrome/chrome --type=renderer --crashpad-handler-…

Not only does it install two desktop files, it also launches things into a different cgroup with a different name. Since applications are based on cgroups, if the cgroup ends up with a distinctly different name, we consider them separate applications. So this as far as I can tell this is an application bug.

We *might* be able to workaround this in SysMon, but that needs some investigation to make sure we don't break other installation methods of Chrome.