Hide Forgot
Description of problem: When oprofile is not initialized (via `opcontrol --init`) eclipse-oprofile keeps asking for password. Version-Release number of selected component (if applicable): eclipse-oprofile-0.6.1-1.el6.x86_64 How reproducible: always Actual results: Eclipse asks for a root password, after user inserts correct one, eclipse asks again, and again. Expected results: Eclipse does initialization, if necessary. Asks for a password and does the profiling when password is correct. Additional info: When I initialize manually prio profiling, it works as expected.
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Severin, have you seen this behaviour?
No, I haven't. I'll have a look.
FWIW, the eclipse-oprofile code should handle "opcontrol --init". Michal, sorry but I cannot reproduce. Are you sure you were using the correct root password? consolehelper GUI keeps popping up if the password is incorrect. What version of oprofile/kernel do you have? I have the following: $ uname -r 2.6.32-71.el6.x86_64 $ rpm -q oprofile oprofile-0.9.6-12.el6.x86_64 $ rpm -q eclipse-oprofile eclipse-oprofile-0.6.1-1.el6.x86_64 Thanks!
I just realize that my machine is running in permissive mode (SELinux). Could it be that SELinux is interfering? If I "$ setenforce 1" then I see some audit messages in audit.log, but requests are allowed. What's your SELinux config?
Hmm, can't reproduce it locally nor even on the same box as last time. Perhaps the manual --init "fixed" it. Sorry, for the noise...