Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

execsnoop fails to process app launched by kde 5.19's launcher #4

Closed
huyz-git opened this issue Jun 11, 2020 · 3 comments
Closed

execsnoop fails to process app launched by kde 5.19's launcher #4

huyz-git opened this issue Jun 11, 2020 · 3 comments

Comments

@huyz-git
Copy link

After kde 5.19 upgrade, apps launched by kde's launcher (e.g. plasmashell's launcher, krunner) will have separate cgroup like this:
Screenshot_20200611_230250
And execsnoop no longer works for this type of apps.
Screenshot_20200611_230723
However, for the same app launched by command line, execsnoop works without any problem.
Screenshot_20200611_230803

@huyz-git
Copy link
Author

For apps launched by kde's launcher, cgnoproxy --pid xxx works, start cgproxy.service after launch the app, (i.e. info: noproxy running process xxx) also works.
Only launch apps by kde's launcher when cgproxy.service is running, execsnoop doesn't work.

@springzfx
Copy link
Owner

KDE moved the process to their predefined scope(cgroup).
However it happened a bit late after cgproxy execsnoop, so the cgroup got override by kde.
https://invent.kde.org/libraries/kcgroups

@springzfx
Copy link
Owner

springzfx commented Jun 11, 2020

fix in bc94e58
For now the solution is to check again after small period(100ms) to avoid kde cgroup override.

Any suggestions are welcomed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants