https://bugs.kde.org/show_bug.cgi?id=474468
--- Comment #18 from gavsiu ---
Thanks, it was easy. Just `envycontrol --reset`. Sorry for the trouble.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=474468
Natalie Clarius changed:
What|Removed |Added
Summary|Energy saving settings show |Power Management auto
https://bugs.kde.org/show_bug.cgi?id=474468
Natalie Clarius changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=474468
--- Comment #14 from gavsiu ---
Forgot to mention, yes, disabling suspend-then-hibernate in Powerdevil does not
freeze the laptop.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=474468
--- Comment #13 from gavsiu ---
% qdbus --system org.freedesktop.login1 /org/freedesktop/login1
org.freedesktop.login1.Manager.SuspendThenHibernate
Error: org.freedesktop.DBus.Error.InvalidArgs
Invalid arguments '' to call
https://bugs.kde.org/show_bug.cgi?id=474468
--- Comment #12 from Natalie Clarius ---
Good find! Did I understand it correctly that if you have the "hibernate after
a period inactivity" (aka "suspend-then-hibernate") enabled, the freezing
happens, but if you disable it, it does not?
Does the
https://bugs.kde.org/show_bug.cgi?id=474468
--- Comment #11 from gavsiu ---
I found the culprit to be the setting "While asleep, hibernate after a period
of inactivity." Is there a way to enable suspend-to-hibernate?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=474468
--- Comment #10 from gavsiu ---
This is after running killall:
Sep 18 08:21:00 Laptop systemd[882]: Stopping Powerdevil...
Sep 18 08:21:00 Laptop systemd[882]: Stopped Powerdevil.
-- Boot --
Sep 18 08:21:45 Laptop systemd[933]: Starting
https://bugs.kde.org/show_bug.cgi?id=474468
Natalie Clarius changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=474468
--- Comment #8 from Natalie Clarius ---
Another thing you could try is temporarily moving your
> ~/.config/powermanagementprofilesrc
to somewhere else to see if maybe something blew up your energy saving
settings.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=474468
--- Comment #7 from Natalie Clarius ---
Right, that was not very thoroughly thought through by me :) Sorry.
You can turn on logs persistently (without having to restart powerdevil) with
> echo "org.kde.powerdevil=true" >>
https://bugs.kde.org/show_bug.cgi?id=474468
--- Comment #6 from gavsiu ---
(In reply to Natalie Clarius from comment #5)
> Ah, of course.
>
> So it is consistently the triggers in energy saving settings which don't
> work.
>
> Could you please run
>
> > killall org_kde_powerdevil;
https://bugs.kde.org/show_bug.cgi?id=474468
--- Comment #5 from Natalie Clarius ---
Ah, of course.
So it is consistently the triggers in energy saving settings which don't work.
Could you please run
> killall org_kde_powerdevil; QT_LOGGING_RULES="org.kde.powerdevil=true"
>
https://bugs.kde.org/show_bug.cgi?id=474468
--- Comment #4 from gavsiu ---
(In reply to Natalie Clarius from comment #3)
> Ok. And does sleep work if you set it to the power button and hold it
> pressed for long enough?
I figured out the power button worked cause I still had it set to Sleep and
https://bugs.kde.org/show_bug.cgi?id=474468
--- Comment #3 from Natalie Clarius ---
Ok. And does sleep work if you set it to the power button and hold it pressed
for long enough?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=474468
--- Comment #2 from gavsiu ---
(In reply to Natalie Clarius from comment #1)
> Up until now energy saving settings (auto suspend after an amount of time,
> lid close and power button) uses a different code path than the buttons in
> the app launcher,
https://bugs.kde.org/show_bug.cgi?id=474468
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=474468
--- Comment #1 from Natalie Clarius ---
Up until now energy saving settings (auto suspend after an amount of time, lid
close and power button) uses a different code path than the buttons in the app
launcher, so that explains why it can act differently
18 matches
Mail list logo
