Bug 399744 - Plasma5 PowerDevil (sometimes) fails to start on system start
Summary: Plasma5 PowerDevil (sometimes) fails to start on system start
Status: RESOLVED WORKSFORME
Alias: None
Product: Powerdevil
Classification: Plasma
Component: general (show other bugs)
Version: 5.14.0
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-13 06:22 UTC by PK
Modified: 2022-12-31 05:24 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
two instances of powerdevil (76.50 KB, image/jpeg)
2018-10-13 06:22 UTC, PK
Details

Note You need to log in before you can comment on or make changes to this bug.
Description PK 2018-10-13 06:22:56 UTC
Created attachment 115613 [details]
two instances of powerdevil

SUMMARY
After I start up my Plasma5 system (Neon user edition), half of the time powerdevil doesn't start with the system.

STEPS TO REPRODUCE
1. Start up Plasma5
2. Try system to go into suspension
3. 

OBSERVED RESULT
System can't suspend in half of the cases

EXPECTED RESULT
System can suspend if it is necessary

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.13, 5.14
KDE Frameworks Version: 5.50.0
Qt Version: 5.11

ADDITIONAL INFORMATION
I did a little research... 
- I found out that the reason that powerdevil should start is that there is a desktop file that points to it in the folder /etc/xdg/autostart. There is indeed. In this desktop file I read: Exec=/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil. If I execute this binary from the terminal, powerdevil ALWAYS starts up. So that seems to be correct. Only at system startup it doesn't always,
- It doesn't matter if I run powerdevil from a terminal with or without sudo. Both works fine, (attachement)
- I find it typical that IF powerdevil starts up with the system the way it should, that according to systemmonitor, I am the owner of the process. I would expect root would be because it started up from /etc/xdg/autostart and not from ~/.config/autostart (e.g.). I don't know what this means but these are my observations
Comment 1 PK 2018-10-13 08:06:34 UTC
one more observation:
suppose powerdevil doesn't run after startup of the system. In that situation I can also always get it running by logging out- and in again. This always works.
Comment 2 Justin Zobel 2022-12-01 04:34:30 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-12-16 05:14:18 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2022-12-31 05:24:22 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!