From nobody Mon Mar 16 19:13:05 2026 X-Original-To: freebsd-desktop@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4fZPrC5w8yz6Vr0M for ; Mon, 16 Mar 2026 19:13:15 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Received: from mail.flex-it.com.ua (mail.flex-it.com.ua [193.239.74.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4fZPrC0XXYz40jv for ; Mon, 16 Mar 2026 19:13:15 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of shuriku@shurik.kiev.ua designates 193.239.74.7 as permitted sender) smtp.mailfrom=shuriku@shurik.kiev.ua Received: from [176.52.183.123] (helo=[100.66.193.27]) by mail.flex-it.com.ua with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.98.2 (FreeBSD)) (envelope-from ) id 1w2DNC-00000000Gwf-2LlC for freebsd-desktop@freebsd.org; Mon, 16 Mar 2026 21:13:06 +0200 Message-ID: <609dbdd3-0d6c-463d-86a0-3c238acea213@shurik.kiev.ua> Date: Mon, 16 Mar 2026 21:13:05 +0200 List-Id: Using and improving FreeBSD on the desktop List-Archive: https://lists.freebsd.org/archives/freebsd-desktop List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-desktop@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Resume from Suspend when triggered by Lid To: freebsd-desktop@freebsd.org References: <7fab23a7-723b-4857-a732-10238bf46d1f@benhutton.com.au> Content-Language: uk-UA From: Oleksandr Kryvulia In-Reply-To: <7fab23a7-723b-4857-a732-10238bf46d1f@benhutton.com.au> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-ACL-Warn: SPF failed. 176.52.183.123 is not allowed to send mail from shurik.kiev.ua. X-Spamd-Result: default: False [-3.27 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.989]; NEURAL_HAM_MEDIUM(-0.99)[-0.985]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:35297, ipnet:193.239.72.0/22, country:UA]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-desktop@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[shurik.kiev.ua]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4fZPrC0XXYz40jv X-Spamd-Bar: --- 16.03.26 09:29, Ben Hutton: > Hi, > > I have a suspend/resume issue with KDE Plasma that appears on both my > FreeBSD powered laptops. When I suspend by closing the lid and I > resume by opening the lid the laptop will go back into suspend mode, > usually shortly after the desktop has resumed. I usually have just > enough time to enter my lock screen password before it goes back into > suspend. I can resume again by pressing the power button and > everything works as expected after that. > > The suspend on both laptops is triggered by KDE. I have it configured > to go into sleep on closing the lid within the power management > settings. I do not have it configured using sysctl. > > Note that when using Xfce and using the equivalent power management > settings within the desktop environment it works as expected. > > My questions are, do I have this configured correctly or do I have to > use the sysctl way of triggering suspend? Also why does it behave > differently on KDE as opposed to Xfce? > > This issue has occurred over multiple versions of FreeBSD and KDE so I > don't know what to detail about my system. One is with hybrid graphics > and the other not. They are both Intel Thinkpads and 10 years > difference in age. It's not a show stopper at present, just annoying. > > Any ideas on how I can debug this? I had this situation on my previous laptop too. To avoid this I disabled suspend on lid close in the KDE settings, instead configuring it via hw.acpi.lid_switch_state sysctl.