Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#61727 - Notifications in Plasma Shell causing 100% load and frozen process

Attached to Project: Arch Linux
Opened by Maxime Carey (werfu) - Monday, 11 February 2019, 21:58 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 05 March 2019, 19:08 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Plasmoid org.kde.plasma.notifications cause the Plasmashell process to become unresponsive and take 100% CPU.

extra/plasma-workspace 5.14.5-2

Steps to reproduce:
Start a Plasma session. As soon as a notification pops-up, the process become unresponsive, taking 100% from a CPU core.

Following error gets spout out:
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:114:13: Unable to assign QJSValue to QImage
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined
This task depends upon

Closed by  Antonio Rojas (arojas)
Tuesday, 05 March 2019, 19:08 GMT
Reason for closing:  No response
Comment by Antonio Rojas (arojas) - Tuesday, 12 February 2019, 18:00 GMT
Which Plasma theme? And can you reproduce with breeze?
Comment by Maxime Carey (werfu) - Tuesday, 12 February 2019, 18:19 GMT
I'm runnning Materia (community/materia-kde 20190117-1) as a theme. Tried with Breeze, it still happen. I tried reinstalling plasma-workspace, it doesn't change a thing. I'll try creating another user profile to see if it could be a problem in my local settings. But it did start to happen after upgrading to 5.14.5-2. I check for update almost daily so the previous version was ok I'm sure.
Comment by Antonio Rojas (arojas) - Tuesday, 12 February 2019, 18:20 GMT
After upgrading what to 5.14.5-2?
Comment by Maxime Carey (werfu) - Tuesday, 12 February 2019, 18:26 GMT
After upgrading Plasma-workspace, and I guess everything thing else KDE related that was released at the same time. I know, not really useful, sorry.
Comment by Antonio Rojas (arojas) - Tuesday, 12 February 2019, 18:30 GMT
plasma-workspace 5.14.5-2 was a bug-fix release for an issue which can't possibly be related to this. Anyway, please report back after testing a clean user with breeze theme and also after updating to 5.15.
Comment by Maxime Carey (werfu) - Tuesday, 12 February 2019, 18:38 GMT
Will do. 5.15 hasn't yet reached the extra repo. I'm looking forward it.
Comment by Antonio Rojas (arojas) - Tuesday, 19 February 2019, 08:02 GMT
Ping?
Comment by Maxime Carey (werfu) - Tuesday, 19 February 2019, 13:21 GMT
Sorry for the delay. The issue still arise using 5.15.0. However I created another user profile and it doesn't happen. I'm trying to pin-point what local configuration might be in cause.
Comment by Antonio Rojas (arojas) - Thursday, 28 February 2019, 16:21 GMT
Any news?

Loading...