https://bugs.kde.org/show_bug.cgi?id=378268
--- Comment #8 from reisenwe...@web.de --- (In reply to Christoph Feck from comment #7) > Do you think you could try creating a patch? We currently have no ksysguard > maintainer. Sorry, not experienced as maintainer, not used to the coding style either. Actually I had no code at hand to analyue, just concluded from strace. I'd *guess* running ksysguardd (or mdadm[wraper]) with the right permissions (suid? yes I know it's deprecated), or setting the right /proc/* and /dev/* file permissions/group that mdadm needs, might fix the issue. The FD leak is just a sleeping bug fallout of the initial issue of mdadm throwing permissions error AIUI -- You are receiving this mail because: You are watching all bug changes.
