Bug 14517

Summary: timer of kdiamond
Product: Mageia Reporter: thierry rouillon <thierry.rouillon>
Component: RPM PackagesAssignee: KDE maintainers <kde>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: marja11, neoclust
Version: 5Keywords: Triaged
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: kdiamond CVE:
Status comment:

Description thierry rouillon 2014-11-12 23:51:57 CET
Description of problem:
The timer of kdiamond is hazardous

Version-Release number of selected component (if applicable):
kde 4-12-5

How reproducible:
all the time

Steps to Reproduce:
1.If you choose a part without timer, the timer is still present
2.If you choose a part with timer, the timing is short or long random way
3.


Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2014-11-14 22:48:09 CET

Keywords: (none) => Triaged
CC: (none) => lmenut, neoclust
Component: Backports => RPM Packages
Assignee: bugsquad => balcaen.john
Source RPM: (none) => kdiamond

Comment 1 Marja Van Waes 2015-04-08 18:09:34 CEST
Mikala is MIA

CC: (none) => marja11
Assignee: balcaen.john => bugsquad

Comment 2 Samuel Verschelde 2015-09-21 13:20:42 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 3 Marja Van Waes 2015-10-27 06:57:52 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 4 thierry rouillon 2015-12-20 15:39:57 CET
I notice that on 5 x86-64 mageia the bug is still present. time varies from 5 "to 15 '

Status: RESOLVED => REOPENED
Resolution: OLD => (none)

Luc Menut 2016-08-25 16:42:37 CEST

CC: lmenut => (none)

Samuel Verschelde 2016-10-31 15:07:59 CET

Version: 4 => 5
Assignee: bugsquad => kde

Comment 5 Marja Van Waes 2018-05-03 07:56:36 CEST
Hi Thierry,

Thank you for having taken the needed time to report this issue!

We regret if this issue didn't get fixed in Mageia 5.

Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed.

I assume this bug doesn't exist in Mageia 6 or later, because KDE and its tools are entirely different there.

Closing as OLD.

Please reopen this report and change its "Version:" at the top left to "6", if the same bug still exists in Mageia 6.

Status: REOPENED => RESOLVED
Resolution: (none) => OLD