| Summary: | Broken GUI using Plasma on Skylake | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Frédéric "LpSolit" Buclin <LpSolit> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | kde, kernel, lewyssmith, marja11, rolfpedersen |
| Version: | 6 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | screenshot | ||
|
Rolf Pedersen
2018-05-07 14:12:25 CEST
CC:
(none) =>
rolfpedersen Does this happen in another DE than Plasma or with another DM than SDDM, too? CC:
(none) =>
kde, kernel, marja11 (In reply to Marja Van Waes from comment #1) > Does this happen in another DE than Plasma or with another DM than SDDM, too? No idea. I use Plasma only. (In reply to Frédéric Buclin from comment #2) > (In reply to Marja Van Waes from comment #1) > > Does this happen in another DE than Plasma or with another DM than SDDM, too? > > No idea. I use Plasma only. I had a look at your screenshot again... the only problems I see there is in Audacious, a GTK application in Mageia (it can also be built with Qt5 support). Is it only with GTK applications that the problem occurs? Frédéric This bug is for Mageia 6; and you did not answer Marja's questions! Can you say whether it is *still* a problem with Mageia 7? CC:
(none) =>
lewyssmith (In reply to Lewis Smith from comment #4) > Frédéric > This bug is for Mageia 6; and you did not answer Marja's questions! > Can you say whether it is *still* a problem with Mageia 7? Sorry for not replying on time. I forgot this bug when I upgraded to Mageia 7. No, I cannot reproduce this issue with Mageia 7. Closing. Status:
NEW =>
RESOLVED |
Created attachment 10128 [details] screenshot See the screenshot. I had to reboot my machine to get the GUI right. Log out + log in is not enough. I use Plasma + Qt5 stuff in updates_testing + mesa 17.3.9 + kernel 4.14.38. No idea which package is the culprit. This behavior is not new and happens from time to time. A reboot always fixes the problem. My machine is an Intel i5-6500 Skylake machine.