| Summary: | Plasma5 PowerDevil (sometimes) fails to start on login | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | John L. ten Wolde <johnltw> |
| Component: | RPM Packages | Assignee: | KDE maintainers <kde> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | andrewsfarm, fri, johnltw, marja11, ouaurelien |
| Version: | 6 | Keywords: | UPSTREAM |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://github.com/NixOS/nixpkgs/issues/24563 | ||
| Whiteboard: | |||
| Source RPM: | powerdevil-5.8.7-1.mga6 | CVE: | |
| Status comment: | |||
|
Description
John L. ten Wolde
2017-09-27 00:18:14 CEST
John L. ten Wolde
2017-09-27 00:18:24 CEST
CC:
(none) =>
johnltw (In reply to John ten Wolde from comment #0) > > I couldn't verify one way or another if upstream is even aware of this issue > or not, but the folks over at NixOS certainly are Assuming it's an upstream issue, then. > and their Thomas Tuegel > offers the following simple workaround: > > "One way to mitigate this temporarily would be to disable session saving. In > System Settings > Startup and Shutdown > Desktop Session choose Start with > an empty session under On Login" > > I've been using it for several days now, and it does seem to do the trick. > > To read the full NixOS bug discussion and analysis see here: > > https://github.com/NixOS/nixpkgs/issues/24563 > > Thanks for the workaround! Keywords:
(none) =>
UPSTREAM Do this problem still occur without the workaround? ( = with session saving ) If still, it would be interesting to see if Plasma 5.12 now in QA fixes it. If not OK in Plasma5.12 maybe it should be put in errata. CC:
(none) =>
fri I'm still seeing it with my HP 6550b laptop. (first generation i3, 8GB, Intel graphics, Intel wifi) Just this morning, in fact. There's been nothing that I can see that's different with the boots where it doesn't work, and I'm not clear on when it started. However, hazy memory is that it started with one of the 4.14 kernels. Something related to Spectre/Meltdown mitigation, perhaps? CC:
(none) =>
andrewsfarm I just checked, and as I thought, I've had the workaround in place for months. Apparently, it no longer, um, works around on this hardware. Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 6's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Best regards, Aurélien Bugsquad Team Resolution:
(none) =>
OLD |