https://bugs.kde.org/show_bug.cgi?id=492488
--- Comment #6 from Vijit <vi...@mail.ru> --- Here is more details. I found out, how to start the real krunner - mouse right click on desktop > show KRunner. Then I found out how to identify the process owner the window (based on this arcticle - https://kb.froglogic.com/misc/find-process-for-window/), and I checked: ``` // Opened real Krunner, execute this command and click to the window $ xprop _NET_WM_PID | sed 's/_NET_WM_PID(CARDINAL) = //' 2394781 // Same actions for surrogate $ xprop _NET_WM_PID | sed 's/_NET_WM_PID(CARDINAL) = //' 705568 ``` Ok, we see two different processes. Now lets check the parent process. Same actions this mouse, but a bit different command: ``` // Real krunner $ ps ww -o ppid=,pid=,cmd= -q `xprop _NET_WM_PID | sed 's/_NET_WM_PID(CARDINAL) = //'` 1948 2394781 /usr/bin/krunner // Surrogate $ ps ww -o ppid=,pid=,cmd= -q `xprop _NET_WM_PID | sed 's/_NET_WM_PID(CARDINAL) = //'` 1948 705568 /usr/bin/krunner ``` Same parent! How? What is it? The last check: ``` $ ps aux | grep -E -i '2394781|705568' root 705568 0.0 0.3 1175068 129932 ? Sl сен03 1:13 /usr/bin/krunner vijit 2394781 0.4 0.5 2145516 190784 ? Ssl сен07 0:03 /usr/bin/krunner ``` Surrogate was started by root. It seems, I shot in the leg somehow. I mean, both windows is the same application, but started by different users. I'll keep digging. -- You are receiving this mail because: You are watching all bug changes.
