Bug 312790

Summary:	Moving a notification is very slow with desktop effects enabled
Product:	[Plasma] plasma4	Reporter:	erik_hahn
Component:	notifications	Assignee:	Marco Martin <notmart>
Status:	RESOLVED UNMAINTAINED
Severity:	minor	CC:	adaptee, plasma-bugs, rockonthemoonfm
Priority:	NOR
Version:	4.9.97 RC2
Target Milestone:	---
Platform:	Chakra
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=312234
Latest Commit:		Version Fixed In:
Attachments:	Output of glxinfo.

Description erik_hahn 2013-01-07 02:00:23 UTC

Moving a notification bubble is very slow when desktop effects are enabled. OpenGL mode is particularily bad.
In Xrender mode performance is bad but usable. With compositing disabled, movement is smooth.

Reproducible: Always

Steps to Reproduce:
1. Enable desktop effects in OpenGL mode
2. Have a notification sent by an application. The notification "bubble" appears
3. Drag it around the screen
Actual Results:  
Unless I move the bubble extremely slowly, it will stay in its place before for a few seconds before jumping to the cursor everytime I move the mouse.

Expected Results:  
The notification bubble should move smoothly like a window

I have no other problems with compositing.

Comment 1 erik_hahn 2013-01-07 02:02:03 UTC

Created attachment 76259 [details]
Output of glxinfo.

I use a ATI HD3850 with the free drivers.

Comment 2 rockonthemoonfm 2013-02-27 16:40:41 UTC

can confirm in arch 64, intel sandy bridge and kde 4.10.
removing opengl2 shaders and vertical sinc in kwin can help reduce (not remove) this desktop freezing effect while dragging  plasma notifications. 
if the movement is too fast, desktop freezes and needs logout.
so bug confirmed and judged a major one.

Comment 3 Nate Graham 2018-06-08 19:41:40 UTC

Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham