https://bugs.kde.org/show_bug.cgi?id=508231
--- Comment #7 from Arjen Hiemstra <[email protected]> --- > │ │ │ ├─app-com.google.Chrome-10367.scope > │ │ │ │ └─10367 /opt/google/chrome/chrome > │ │ │ ├─app-google\[email protected] > │ │ │ │ ├─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. -- You are receiving this mail because: You are watching all bug changes.
