Bug 355448

Summary: After Plasma /KDE updates today (11-16-15) Plasma desktop has slowed to a treacle.
Product: [Plasma] kwin Reporter: SP <scp.stjohn>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: grave CC: bhush94, plasma-bugs
Priority: NOR    
Version: 5.4.3   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Output of qdbus org.kde.KWin /KWin supportInformation with various compositing options

Description SP 2015-11-16 19:49:26 UTC
Following Plasma /KDE updates today (11-16-15) Plasma desktop has slowed to a treacle.  Have tried rebooting and deleting cache to no avail.  This occurred immediately after reboot when updates had completed.
Kde Plasma v. 5.43
Qt V. 5.5.0
Kernel 4.2.5-300.fc23.x86_64
Hardware:
Graphics card: AMD Tonga Pro Radeon R9 380 4GB
CPU: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
Memory 16GB  DIMM DDR3 Synchronous 1600 MHz (0.6 ns)




Reproducible: Always

Steps to Reproduce:
1. Reboot after updates 11/16/15
2. Plasma 5 loads very slowly
3. Applications are barely usable as they take are slow to open and text input (even in this form) gets halted.

Actual Results:  
System is so slow following recent update it is unusable.  Everything was fine preceding recent update.

Expected Results:  
System performance should remain the same or have improved.
Comment 1 SP 2015-11-16 22:37:50 UTC
Ok - seems to have been a compositor problem.  Selecting and applying xrender in the compositor seems to resolve the problem - as does reselecting and applying OpenGL 3.1
Comment 2 SP 2015-11-17 02:43:08 UTC
Problem is ongoing.  Seems to be related to compositor and definitely has only occurred even after today's updates.  My other machine has identical hardware/software except that I have not applied today's plasma updates.  That machine works fine.  Even typing this text is extremely difficult as the input gets halted.
Comment 3 Thomas Lübking 2015-11-17 17:24:29 UTC
please attach the output of
    qdbus org.kde.KWin /KWin supportInformation
once obtained with slow GL compositing and once with resolved (when reselecting GL 3.1)
Comment 4 SP 2015-11-17 18:54:53 UTC
Created attachment 95568 [details]
Output of qdbus org.kde.KWin /KWin supportInformation with various compositing options
Comment 5 SP 2015-11-17 19:00:30 UTC
There have been similar problems with slight improvement today 11-17-15 after Qt and other updates.  After selecting EGL and rebooting there has been a vast improvement and return to normal. (This was previously not the case with selecting EGL.)  Even the flickering on my dual monitor setup has disappeared.  I attach the output of qdbus org.kde.KWin /KWin supportInformation with various compositing options.  I did not reboot between compositing changes.  Please let me know if that is required.  Thanks.
Comment 6 Thomas Lübking 2015-11-17 20:07:22 UTC
> OpenGL renderer string: Gallium 0.4 on AMD TONGA (DRM 3.0.0, LLVM 3.7.0)
That would be the new AMDGPU driver, yes?

> Plugin: org.kde.kwin.aurorae
> Theme: __aurorae__svg__air-oxygen

"kcmshell5 kwindecoration", please try the breeze decoration, esp. the air-oxygen theme has cause countless bugreports in the past...

You don't have to reboot between changes, but i'm esp. interested in the supportInformation when it does *not* work.

So what's the status quo? No issues with EGL but GLX is slow unless you change settings?
Does a suspend/resume cycle of the compositor (SHIFT+Alt+F12) help itr. as well?
Comment 7 SP 2015-11-17 21:30:40 UTC
>That would be the new AMDGPU driver, yes?
Yes - the new AMDGPU driver.
 >So what's the status quo?
With EGL everything just works perfectly now.  Do not know why that is - as selecting it previously did not resolve the issue.  Suspending and resuming the compositor (when things did not work) did not resolve the problem.  
I have since updated my other computer which has identical hardware and software.  I selected EGL there first and everything works fine after the updates.
I do not know what it was in 11-16-15 updates that caused the problem (they were mostly Plasma updates) - but having a computer rendered unusable by an update is no fun at all.  It is frustrating that I cannot identify the exact component that caused the problem - but whatever it was - it seems to be remedied now.  Thank you, Thomas.
Comment 8 Thomas Lübking 2015-11-17 21:59:05 UTC
possible causes
- buggy and fixed AMDGPU
- buggy and fixed MESA
- buggy and fixed or wrong X11 driver

The answer is probably in the update logs, notably the second one (may have brought missing package/update or fixed a bug in a package also seen in the faulty update)