| Summary: | Progress Indicator Spinner in notifications causes 100% CPU usage | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Salvo "LtWorf" Tomaselli <tiposchi> |
| Component: | Notifications | Assignee: | Martin Klapetek <mklapetek> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | kde, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.3.2 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Salvo "LtWorf" Tomaselli
2015-08-28 08:58:11 UTC
Thanks for the report Would it possible to test with Plasma 5.4.0? Also, what is your intel driver version, kernel version and mesa version? I am using 5.4.2-1. Linux hal9000 4.2.1a #1 SMP PREEMPT Mon Sep 28 13:40:48 CEST 2015 x86_64 GNU/Linux ii libegl1-mesa:amd64 11.0.0-1 amd64 free implementation of the EGL API -- runtime ii libgl1-mesa-dri:amd64 11.0.0-1 amd64 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i386 11.0.0-1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 11.0.2-1 amd64 free implementation of the OpenGL API -- GLX runtime ii libgl1-mesa-glx:i386 11.0.2-1 i386 free implementation of the OpenGL API -- GLX runtime ii libglapi-mesa:amd64 11.0.2-1 amd64 free implementation of the GL API -- shared library ii libglapi-mesa:i386 11.0.2-1 i386 free implementation of the GL API -- shared library ii libgles1-mesa:amd64 11.0.2-1 amd64 free implementation of the OpenGL|ES 1.x API -- runtime ii libgles2-mesa:amd64 11.0.2-1 amd64 free implementation of the OpenGL|ES 2.x API -- runtime ii libglu1-mesa:amd64 9.0.0-2.1 amd64 Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1 i386 Mesa OpenGL utility library (GLU) ii libwayland-egl1-mesa:amd64 11.0.0-1 amd64 implementation of the Wayland EGL platform -- runtime ii mesa-utils 8.2.0-1 amd64 Miscellaneous Mesa GL utilities The issue is reproducible. *** This bug has been marked as a duplicate of bug 347237 *** |