On my work computer I use my company account (using LDAP/Samba) to start my plasma session in a work context. 

However, I sometimes want to be able to look at websites from a personal context. That's why I do have a regular local user account, which I use for personal stuff. The chromium instance that is installed there is also synced with my chromium instance on my home computer via Google account. Therefore, also the support for plasma-browser-integration is active in this instance.

But usually I do not start a second X session with my personal account, but I do start chromium using `kdesu -u <personalaccount> chromium`. In this case, a process called `plasma-browser-integration-host` ist started with my personal account user, which has not started the X session. And this process continuesly reaches 100% cpu time on a single core.

I assume, this is due to the fact, that it probably doesn't have the right to talk to other graphical processes.

STEPS TO REPRODUCE
1. Have two users
2. Start plasma session with first user
3. Start chromium as second user using `kdesu -u seconduser chromium`

OBSERVED RESULT

Have `plasma-browser-integration-host` process, consuming high cpu on single core.

EXPECTED RESULT

If I still have a `plasma-browser-integration-host` process running as seconduser, it should not consume high cpu.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.17.0
KDE Frameworks Version: 5.63.0
Qt Version: 5.13.1

ADDITIONAL INFORMATION