Bug 3180 - Msec GUI locks with 100% CPU when weekly checks run straight after daily checks
Summary: Msec GUI locks with 100% CPU when weekly checks run straight after daily checks
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: D Morgan
QA Contact:
URL: https://bugs.mageia.org/show_bug.cgi?...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-25 14:50 CEST by claire robinson
Modified: 2012-12-02 14:31 CET (History)
2 users (show)

See Also:
Source RPM: msec-0.80.10-2.3.mga1.src.rpm
CVE:
Status comment:


Attachments

Description claire robinson 2011-10-25 14:50:15 CEST
Description of problem:

This bug has been created to allow and update candidate for msec & msec-gui to be validated. Please also see bug 2255

This occurs in release and updated versions of msec.

When daily checks are run followed straight away by weekly checks, after the weekly checks complete the GUI freezes and msecgui.py sits at 100% CPU.

It requires kill -9 to close it.

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

msec-0.80.10-2.3.mga1.src.rpm & release version too
Florian Hubold 2011-10-25 18:05:00 CEST

CC: (none) => doktor5000

Comment 1 Manuel Hiebel 2011-10-30 02:05:30 CET
Bug assigned to the package maintainer.

Assignee: bugsquad => dmorganec

Comment 2 Marja Van Waes 2012-02-01 07:53:24 CET
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED.


@ D Morgan
Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. Don't change anything if you want to be pinged by me in this report again ;)

CC: (none) => marja11

Comment 3 Marja Van Waes 2012-07-06 15:04:04 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 4 claire robinson 2012-07-06 16:32:12 CEST
I can't reproduce this mga2.

I haven't re-tested mga1 but afaik there have been no updates since this was reported. I'll test it again when I next use the mga1 VM.
Comment 5 Manuel Hiebel 2012-11-05 16:51:44 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

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 prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and 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.

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.

--
Mageia Bugsquad
Comment 6 Manuel Hiebel 2012-12-02 14:31:39 CET
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

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


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