Description of problem: When running it regularly takes up to 1900 MB of memory and all the CPU. Finally, it freezes the desktop and the computermust be switched off/on as even a tty can't be opened. Version-Release number of selected component (if applicable): How reproducible: regularly Steps to Reproduce: 1. start kalarm with several alarms 2. 3.
Now, it's 3000 MB taken on 8300.
Hardware: All => x86_64
It is very unlikely that this issue will be fixed for Mageia 5, afaik only security issues are still fixed in Mageia 5. I know upgrading from Mageia 5 to Mageia 6 can still fail, especially when you need to upgrade from KDE4 to Plasma5. If you have a lot of free disk space or even a spare system, I suggest doing a fresh Mageia install (while keeping your Mga5 install) and copying the files and directories that you need from the old home partition to the new home partition.
Assignee: bugsquad => kdeCC: (none) => marja11
>I suggest doing a fresh Mageia install (while keeping your Mga5 install) and >copying the files and directories that you need from the old home partition to >the new home partition. What is the interest of keeping my Mga5 install if I do a fresh Mga6 install ? The problem does not come from my home directory as if I create a new user under mga-6, I get a black screen too (see https://bugs.mageia.org/show_bug.cgi?id=22761)
(In reply to Christian CHEVALIER from comment #3) > > What is the interest of keeping my Mga5 install if I do a fresh Mga6 install > ? That you can keep using Mageia 5 if the Mageia 6 installation doesn't work well, and that, in that case, you can help by supplying requested information (and, if needed, later requested additional information) that is necessary for KDE team to help pinpoint what is wrong and be able to fix the problem. > > The problem does not come from my home directory as if I create a new user > under mga-6, I get a black screen too (see > https://bugs.mageia.org/show_bug.cgi?id=22761) Yes, and you couldn't supply any requested additional information for that bug report, because you no longer had a Mageia 6 install. So that report is useless :-(
>because you no longer had a Mageia 6 install It's not completly true because I backed up my mga-6 install before downgrading to mga-5 and restored it on a spare partition to be able to dual boot but... - In the meantime, kalarm (or something else) became too memory-guzzler and I had to to add 6 GiB swap I had reserved for mga-6 /var partition ; so, to run this install, I should add a new USB partition for mga-6 /var - testing this mga-6 install is very restrictive for I have to close all my apps and connections on mga-5 and reboot on mga-6. So, for the moment, I think the best solution is to use my 2nd computer on which I don't use plasma and connect through SSH
Hi Christian, Thank you for having taken the needed time to report this issue! This bug was filed against Mageia 5. Did it get fixed? If so, please change its status to RESOLVED - FIXED. If it didn't, then we regret that we weren't able to fix it 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 continued to get limited extended support since then, but that support has now ended, too. As a result we are closing this bug report as OLD. If you still see this issue in a newer Mageia version, then please reopen this report and say so.
Resolution: (none) => OLDStatus: NEW => RESOLVED