Bug 220731 - cpufreq tooltip always says "cpu 0" even when set to monitor cpu 1
Summary: cpufreq tooltip always says "cpu 0" even when set to monitor cpu 1
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-applets (Show other bugs)
(Show other bugs)
Version: 6
Hardware: All Linux
medium
low
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-12-24 23:23 UTC by Anthony Symons
Modified: 2008-02-02 14:23 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-02-02 14:23:25 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Anthony Symons 2006-12-24 23:23:25 UTC 
Description of problem:

I have a dual core athlon 64. So, I added cpufreq twice (not that you can
control their speed seperatly, but I did it anyway). I set one to monitor cpu 0
and one to monitor cpu 1. When I mouse over the applet both say CPU 0.

Version-Release number of selected component (if applicable):

cpu frequency scaling monitor 2.16.0.1

How reproducible:

always

Steps to Reproduce:
1. Find a dual core system 
2. Add two cpufreqency monitors
3. Pick Preferences on the second one and change cpu to monitor from cpu 0 to cpu 1
4 Hover mouse over both applets, and observe both report cpu 0.

Actual results:

Cpu 0 x2

Expected results:

Cpu 0 and Cpu 1 (just to give me that warm fuzzy feeling that i have a dual core
cpu) :)

Additional info:
Comment 1 Matthias Clasen 2008-02-02 14:23:25 UTC 
This is fixed in later versions.
Note You need to log in before you can comment on or make changes to this bug.