https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #8 from Jiri Slaby <jirisl...@gmail.com> --- (In reply to Vlad Zahorodnii from comment #7) > Most likely, kwin overwrites the data it shouldn't. It would be great if you > could run kwin with valgrind, but it can make the computer very unusable. You'd have to tell me how. kwin_wayland has cap_sys_nice=ep caps set. So if I wrap it by valgrind I get: > ==31896== > ==31896== Warning: Can't execute setuid/setgid/setcap executable: > /usr/bin/kwin_wayland > ==31896== Possible workaround: remove --trace-children=yes, if in effect > ==31896== > valgrind: /usr/bin/kwin_wayland: Permission denied If I unset those caps and create a wrapper: #!/bin/bash exec valgrind --log-file=/tmp/kwin_valgrind kwin_wayland.exe and set those caps to the wrapper (adding inheritance too): setcap cap_sys_nice=epi kwin_wayland It doesn't start. Changing valgrind to strace in that script shows, that it dies likely due to this: 26687 sched_setscheduler(0, SCHED_RR, 0x7ffd37879530) = -1 EPERM So the caps are not really inherited. Maybe ptrace() in valgrind/strace removes those caps. -- You are receiving this mail because: You are watching all bug changes.
