from:"anomaly256"

[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5

2020-10-19 Thread anomaly256

https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #64 from anomaly256 --- Thanks -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5

2020-09-08 Thread anomaly256

https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #59 from anomaly256 --- I decided to test on kde neon testing, with libkscreenlocker5 5.19.4+p20.04+git20200818.2051-0 and kscreenlocker_greet appears to actually be behaving here. There's a separate issue with plasmashell chewing 200

[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5

2020-09-08 Thread anomaly256

https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #58 from anomaly256 --- (In reply to Nate Graham from comment #55) > It may not still even be a thing; Plasma 5.14.5 is almost two years old at > this point so there's a chance that it's been fixed in a newer version which

[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5

2020-07-23 Thread anomaly256

https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #56 from anomaly256 --- (In reply to Nate Graham from comment #55) > It may not still even be a thing; Plasma 5.14.5 is almost two years old at > this point so there's a chance that it's been fixed in a newer version which

[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5

2020-07-23 Thread anomaly256

https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #54 from anomaly256 --- nb: I see this on many hosts not just ones using nvidia drivers. To be honest I don't believe the earlier assertion that this original bug is specific to nvidia is accurate and has likely been a red herring. S

[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5

2020-07-23 Thread anomaly256

https://bugs.kde.org/show_bug.cgi?id=347772 anomaly256 changed: What|Removed |Added CC||anomaly...@gmail.com --- Comment #53 from

[kdialog] [Bug 381561] getsavefilename broken due to port to QFileDialog

2017-10-18 Thread anomaly256

https://bugs.kde.org/show_bug.cgi?id=381561 --- Comment #14 from anomaly256 --- Actually, I suspect I've only /started/ hitting it since my system upgraded from 17.04 to 17.08 of kdialog -- You are receiving this mail because: You are watching all bug changes.

[kdialog] [Bug 381561] getsavefilename broken due to port to QFileDialog

2017-10-18 Thread anomaly256

https://bugs.kde.org/show_bug.cgi?id=381561 --- Comment #13 from anomaly256 --- I see it's marked as 'resolved fixed' but I seem to be hitting it still in 17.08.2 -- You are receiving this mail because: You are watching all bug changes.