Sebastien and I exchanged email over this bug and he requested that I check with Jaunty which I did. The applet appeared to work and I sent him email about it.
I have reinstalled Jaunty on the same machine (Dell D630) and the applet has stopped working again. This time I have changed this report to a question rather than a bug and I would like to understand what is not working. Any help in debugging would be most appreciated.
more /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz
stepping : 13
cpu MHz : 2001.000
cache size : 2048 KB
Using cpufreq-selector from the command line, I (logged in as a user who is NOT root and who CANNOT ADMINISTER the system).
cpufreq-selector -f 800000
more /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz
stepping : 13
cpu MHz : 800.000
In other words, I (logged in as amrith, not the root user, not an administrator) am able to use cpufreq-selector to update the scaling. And it works because cpufreq-selector has been setuid'ed correctly.
On the other hand, the CPU performance applet does not give me the ability to change the frequency.
NOTE:
If I login as the root user, the CPU performance applet works correctly.
The difference appears to be that as a non-root user, the CPU Frequency Scaling Monitor applet is not allowing me to adjust the scaling, just view it. But, as a root user, the CPU Frequency Scaling Monitor applet is working correctly.
What have I tried?
1. I tried to suid on /usr/lib/gnome-applets/cpufreq-applet
I can't launch the applet, it gives an error
2. I've tried to strace the applet
When logged in as the non-root user, I see nothing indicating an error.
How should I gather more information to help debug this?
Sebastien and I exchanged email over this bug and he requested that I check with Jaunty which I did. The applet appeared to work and I sent him email about it.
I have reinstalled Jaunty on the same machine (Dell D630) and the applet has stopped working again. This time I have changed this report to a question rather than a bug and I would like to understand what is not working. Any help in debugging would be most appreciated.
What I find now is as follows.
apt-cache policy gnome-applets us.archive. ubuntu. com jaunty-updates/main Packages dpkg/status 26.0-0ubuntu4 0 us.archive. ubuntu. com jaunty/main Packages
gnome-applets:
Installed: 2.26.1-0ubuntu1
Candidate: 2.26.1-0ubuntu1
Version table:
*** 2.26.1-0ubuntu1 0
500 http://
100 /var/lib/
2.
500 http://
ls -l /usr/bin/ cpufreq- selector cpufreq- selector
-rwsr-sr-x 1 root root 30656 2009-04-23 08:28 /usr/bin/
more /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz
stepping : 13
cpu MHz : 2001.000
cache size : 2048 KB
Using cpufreq-selector from the command line, I (logged in as a user who is NOT root and who CANNOT ADMINISTER the system).
cpufreq-selector -f 800000
more /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz
stepping : 13
cpu MHz : 800.000
In other words, I (logged in as amrith, not the root user, not an administrator) am able to use cpufreq-selector to update the scaling. And it works because cpufreq-selector has been setuid'ed correctly.
On the other hand, the CPU performance applet does not give me the ability to change the frequency.
NOTE:
If I login as the root user, the CPU performance applet works correctly.
The difference appears to be that as a non-root user, the CPU Frequency Scaling Monitor applet is not allowing me to adjust the scaling, just view it. But, as a root user, the CPU Frequency Scaling Monitor applet is working correctly.
What have I tried?
1. I tried to suid on /usr/lib/ gnome-applets/ cpufreq- applet
I can't launch the applet, it gives an error
2. I've tried to strace the applet
When logged in as the non-root user, I see nothing indicating an error.
How should I gather more information to help debug this?