Description of problem: A few hours (or sometimes some tens of minutes) after boot, my desktop freezes and I can't even open a new tty to see what's happening. The only solution is to switch off/on the computer. /var/log/messages shows a lot of errors in plasmashell. I join an extract of /var/log/messages just before switching off. Version-Release number of selected component (if applicable): How reproducible: Every tens of minutes or hours. Steps to Reproduce: 1. boot and begin to work 2. 3.
Created attachment 11594 [details] /var/log/messages extract just before I restart the frozen computer
See also bug 26490 of which this one may be a duplicate. I do not have a /var/log/messages ! But the output looks like that from journalctl. As you say, "a lot of errors in plasmashell" ; in fact 4809/6553 lines come from that. We recommend compressing large attachments with 'xz'. Can you say when this started to happen? After installation? After a recent update?
CC: (none) => lewyssmith
Sorry being late to respond to this. Are you still affected by this bug, as like Lewis mentioned early, similar to bug 26490? In meantime, you're logs doesn't reveal too much. I suggest you to add the following lines temporarily in /etc/environment : su -c 'echo "QT_LOGGING_RULES='*=false'" >> /etc/environment' This will considerably reduce unnecessary QT/KDE logging to journal in order to turn in it more readable and help us pinpoint if this bug is not KDE related. Reboot your computer and try report a new journal here by issue : su -c 'journalctl -b -1 --no-hostname >> /log.txt && xz /log.txt' Copy and paste these commands carefully by double-check them. Last command will write a log.txt file from your system journal and will be compressed by xz. File will belong to root user. After, to restore qt logging, do: su -c 'sed -i -e "/QT_LOGGING_RULES/d" /etc/environment' This command will restore QT logging by removing line in /etc/environment.
Keywords: (none) => NEEDINFOSource RPM: plasma-workspace-5.15.4-1.1.mga7 => (none)
Severity: critical => major
Reporter, could you please reply to the previous question? If you don't reply within two weeks from now, I will have to close this bug as OLD. Thank you.
CC: (none) => ouaurelien
This problem has been regularly reported both here and more importantly at KDE; just go to KDE and search "plasma freezes" (see e.g. bug 4525250). From the comments this appears to be a Plasma problem, not a Mageia problem. Further from my experience the "plasma freeze" is a random event, i.e. it occurs after certain actions and sometimes without any action aside from switching desktops. High usage applications or low usage does not seem to matter It does not seem to be reproducible at will. It was worse in Mageia 7 than 6. I thought at first it was the chipset, but the same problems occurred after I changed them. Even proposed "solutions" related to plasma do not provided a consistent resolution Solution: Ask KDE to fix Plasma. There is no use Mageia wasting their time.
CC: (none) => roger
This may be a duplicate of Bug 21184.
Hi, I suggest removing of all KDE/Plasma related config files in your home directory when you are logged in a tty (Console and not in X) in ~/.config feel free to remove all KDE or Plasma related files. This must be done on a tty and not in a graphical session.
There is nothing in the attached logs a Plasma nor a computer freeze. Meanwhile, sometime, a peripheral or a bad configured graphic card can freeze the entire system without mentioning whatever clue in system log. Also, and that can annoy me the most is the unnecessary and messy QT logging facility that can spam a lot a system journal. (See Bug 27115, Bug 27054, Bug 26900). Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Resolution: (none) => OLDStatus: NEW => RESOLVED