Bug 13529 - Update request: GKrellM-gkfreq - CPU frequency plugin for GKrellM - bug fixed
Summary: Update request: GKrellM-gkfreq - CPU frequency plugin for GKrellM - bug fixed
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: All Linux
Priority: Normal normal
Target Milestone: Mageia 4
Assignee: Bruno Cornec
QA Contact: QA Team
URL: http://sourceforge.net/projects/gkrel...
Whiteboard: MGA4-32-OK MGA4-64-OK advisory
Keywords: Triaged, validated_update
Depends on:
Blocks:
 
Reported: 2014-06-16 19:07 CEST by Martin Volf
Modified: 2014-09-05 11:08 CEST (History)
4 users (show)

See Also:
Source RPM: gkrellm-plugins-2.3.5-10.mga4.src.rpm
CVE:
Status comment:


Attachments

Description Martin Volf 2014-06-16 19:07:45 CEST
Hi,

please, can somebody update a plugin gkfreq for GKrellM ?

Description of problem:
In MGA4 32/64bit in GKrellM is not shown an actual CPU frequency if plugin intel_pstate is activated.

How reproducible:
everytime

Steps to Reproduce:
1) Use the computer with Intel Core ix
2) By command "# cpupower frequency-info" be sure you use a plugin intel_pstate
3) open GKrellM
4) go to GKrellM configuration: press F1 key â Plugins â activate CPUfreq
3) in new windows is shown 0MHz for all CPUs

How to solve it:
By updated plugin from http://sourceforge.net/projects/gkrellm-gkfreq/

See bugreport: http://sourceforge.net/p/gkrellm-gkfreq/bugs/3/

Reported also: https://bugs.mageia.org/show_bug.cgi?id=13368#c6

Thank you!
Manuel Hiebel 2014-06-17 22:59:06 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => bruno

Comment 1 Bruno Cornec 2014-07-05 00:40:50 CEST
I have submitted an update which seems to perform as expected. Before pushing to QA, could you confirm it's working for you correctly as I don't have the appropriate HW to test fully.
Available in some minutes unde update_testing

Status: NEW => ASSIGNED

Comment 2 Deri James 2014-07-07 12:51:51 CEST
Tested Ok - working - on X86-64 with Intel Core i5-2500 (intel_pstate). 

However there is a problem in that the plugin in MGA4 is called "CPUfreq" but the updated plugin is "gkrellm-gkfreq". These appear to be two separate projects. So, in order to test the new plugin you need to disable the original CPUfreq (which continues to show 0mhz as per above report) and enable the new plugin.
Comment 3 Martin Volf 2014-07-07 16:03:11 CEST
(In reply to Bruno Cornec from comment #1)
> I have submitted an update which seems to perform as expected. Before
> pushing to QA, could you confirm it's working for you correctly as I don't
> have the appropriate HW to test fully.
> Available in some minutes unde update_testing

I am so sorry for delay. I wanted to write you yesterday that your update works fine on MGA4 64bit. I want to test it on MGA4 32bit with 1 CPU, but that machine I have to update today.

As wrote:
(In reply to Deri James from comment #2)
> Tested Ok - working - on X86-64 with Intel Core i5-2500 (intel_pstate). 
> 
> However there is a problem in that the plugin in MGA4 is called "CPUfreq"
> but the updated plugin is "gkrellm-gkfreq". These appear to be two separate
> projects. So, in order to test the new plugin you need to disable the
> original CPUfreq (which continues to show 0mhz as per above report) and
> enable the new plugin.

This I like to write as well. Same issue found yesterday. For this I do not know, if we have to write a new bug or add it here for you.

Next info: I wrote to Christoph Winkelmann, maintainer for CPUfreq plugin, and I did not get any answer yet. When will be plugin modified (like plugin gkfreq), then I will let you know soon!
Comment 4 Martin Volf 2014-07-08 17:15:07 CEST
So I promised you an answer, I have got the mail:

> Dear Yullaw,
> 
> Thank you for your feedback. I have not had any feedback on gkrellm-cpufreq for 
> more than two years now, and the active development stopped in 2006, with only 
> occasional reactions on bug reports and feature requests after that.
> The problem is, that I'm not using it myself any more, because I have switched 
> from gkrellm to conky - years ago. I will have a look at your remark, but give 
> me some time, I need to install gkrellm first and then try to understand a 
> piece of code that I didn't read for two years and that I started writing more 
> than a decade ago... Of course, this is open source software, so if anyone is 
> willing to take this over and maintain it properly, then this would be just 
> fine for me. Probably I should make a remark in that sense on my homepage...

> Best regards,
> Christoph

I think this gkrellm-CPUfreq plugin can be kept as additional (for users uses /proc/acpi only) and gkrellm-gkfreq plugin as default/major (for /proc/acpi and intel_pstate) till development will start again. Or as you wish...

NOTE: as homepage is written in "Info" of the plugin 
gkrellm2-cpufreq 0.6.1,  http://chw.tks6.net/gkrellm2-cpufreq/

The homepage is not actual, correct is:
http://chw.populus.org/rub/7

NOTE_2: I tested an update gkrellm-plugins-2.3.5-10.1 on MGA4, 32bit, 1 CPU and works fine as on MGA4, 64bit!

Thank you for an update ! For me is an issue closed ;)

Can be pushed to Core Updates ?
Comment 5 Martin Volf 2014-07-08 17:32:50 CEST
ADD: please, gkrellm2-cpufreq can be updated to latest gkrellm2-cpufreq-0.6.4. (10.2.2012) as well, see homepage...
Comment 6 Bruno Cornec 2014-07-24 03:52:28 CEST
Moving to QA to allow for an update on this.

Assignee: bruno => qa-bugs
Target Milestone: --- => Mageia 4
QA Contact: (none) => qa-bugs

Comment 7 Rémi Verschelde 2014-08-01 10:12:16 CEST
Bruno, could you provide a list of RPMs and SRPMs and an advisory to be used with this update?

See e.g. https://wiki.mageia.org/en/Update_Advisory_Announcement_Example

CC: (none) => remi

Comment 8 Rémi Verschelde 2014-08-04 21:07:06 CEST
Here are the packages to test. Still waiting for an advisory, please.

RPMs from 'core-updates_testing'
========================
gkrellm-plugins-2.3.5-10.1.mga4.x86_64.rpm
gkrellm-plugins-kam-2.3.5-10.1.mga4.x86_64.rpm
gkrellm-plugins-shoot-2.3.5-10.1.mga4.x86_64.rpm
gkrellm-plugins-snmp-2.3.5-10.1.mga4.x86_64.rpm
gkrellm-plugins-stock-2.3.5-10.1.mga4.x86_64.rpm

SRPMs from 'core-updates_testing'
========================
gkrellm-plugins-2.3.5-10.1.mga4.src.rpm
Comment 9 Rémi Verschelde 2014-08-12 12:14:12 CEST
Bruno, could you give feedback on comments 2, 3, 4 and 5? It seems the CPUfreq entry is still shown and still broken, even if your update candidate adds a working gkrellm-gkfreq.

IMO it would be best to cater for it in this very update, and either remove the CPUfreq entry or try to update it to a working version (since there are newer versions as per comment 5).

Whiteboard: (none) => feedback

Comment 10 Rémi Verschelde 2014-08-12 12:17:13 CEST
Ah I just see that Bruno was not in CC. Please put yourself in CC when assigning updates to QA Bruno, we need to be able to get feedback from you.

Assignee: qa-bugs => bruno

Comment 11 Bruno Cornec 2014-08-13 01:37:28 CEST
Sorry for that mistake.

I've created the adv.
I think CPUfreq is still useful (for other cases comared to the intel one), so would like to keep it. I'll make an update to it as well. Maybe we can do that for cauldron and not mga4 ?
Comment 12 Martin Volf 2014-08-28 17:45:38 CEST
Hi,

please, leave it and push it for update, works on different types of CPUs (for users uses /proc/acpi (older CPU) = to work has to be enabled plugin gkrellm-CPUfreqfor; for users with CPUs iX Core - intel_pstate = to work has to be enabled plugin gkrellm-gkfreq).

For MGA5 should be nice to have completely update to gkrellm2-cpufreq-0.6.4 - (In reply to Martin Volf from comment #5)
> ADD: please, gkrellm2-cpufreq can be updated to latest
> gkrellm2-cpufreq-0.6.4. (10.2.2012) as well, see homepage...

+ for MGA5: if possible, change a homepage URL in:
> NOTE: as homepage is written in "Info" of the plugin 
> gkrellm2-cpufreq 0.6.1,  http://chw.tks6.net/gkrellm2-cpufreq/
>
> The homepage is not actual, correct is:
> http://chw.populus.org/rub/7

Thank you!
Comment 13 Rémi Verschelde 2014-08-28 18:39:54 CEST
OK, let's push this update. Thanks for the reminder Martin.

Based on Deri's and Martin's tests, the update candidate is already fully tested.

Validating the update. Bruno already updated the advisory, so this can be pushed.

Keywords: (none) => validated_update
Whiteboard: feedback => MGA4-32-OK MGA4-64-OK advisory
CC: (none) => sysadmin-bugs

Comment 14 Rémi Verschelde 2014-08-28 18:40:18 CEST
s/updated/uploaded/
Comment 15 Mageia Robot 2014-09-05 11:08:15 CEST
An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGAA-2014-0167.html

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.