Bug 348283

Summary: Can not suspend PCBSD 10.1 from Kickoff launcher
Product: [Plasma] Powerdevil Reporter: Naomasa Maruyama <kdebugreport>
Component: generalAssignee: Plasma Development Mailing List <plasma-devel>
Status: RESOLVED WORKSFORME    
Severity: normal CC: justin.zobel
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: FreeBSD Ports   
OS: FreeBSD   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Naomasa Maruyama 2015-05-27 03:59:08 UTC 
The KDE version is 4.14.2(on PCBSD 10.1) and 4.14.3(on PCBSD10.1.2),
which I can not find in the version list.

A suspend from the Kickoff Launcher simply locks the screen without suspending
the FreeBSD.  An error message like

kded(48117) PowerDevil::PolicyAgent::setupSystemdInhibition: failed to inhibit systemd powandling

appears in .pcdm-startup.log. 

Reproducible: Always

Steps to Reproduce:
1. Click [Leave]/[Sleep] icon from Kickoff Launcher.
2. 
3.

Actual Results:  
The screen will be locked, but OS will not be suspended.

Expected Results:  
OS will be suspended.

Thanks to the adoption of console vt driver of FreeBSD for PCBSD 10.1,
suspending the system by root privilege with /usr/sbin/zzz works very
well on PCBSD 10.1 and 10.1.2.  But a suspend from the Kickoff
Launcher simply locks the screen without suspending.  This situation
is quite different from PCBSD 9.1 and 9.2. On these versions, kde 4.9.5
and kde 4.10.5 can suspend the OS from the Kickoff Launcher, while OS
support for suspending was not sufficient so that we saw lots of problem after
resuming(at least for Intel graphic chips), as already pointed out by lots of bug
reports.  These were OS problems, not kde problems.  This report is about kde
problem, and for PCBSD 10.1 or later, fixing this problem is very rewarding job
because /usr/sbin/zzz on FreeBSD10.1 +"console vt driver" seems to work
perfectly(at least for Intel graphic machines).

Note that the console vt driver is not standard for genuine FreeBSD10.x yet(as I heard),
just optional, so in order to reproduce my situation on genuine FreeBSD10.1,

kern.vty="vt"

should be included in /boot/loader.conf.  PCBSD10.1 already adopted the driver as default,
as is seen in /boot/grub/grub.cfg and /boot/loader.conf.pcbsd.
Comment 1 Christoph Feck 2015-05-31 18:25:38 UTC 
This bug is likely in the Solid power management.
Comment 2 Justin Zobel 2020-11-22 09:33:50 UTC 
Naomasa, thanks for the bug report, it's been a little while since this was reported.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 3 Bug Janitor Service 2020-12-07 04:34:03 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 2020-12-22 04:34:51 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!