Bug 495426 - macOS Sequoia’s display remains active when KDE Connect is engaged, preventing the system from entering a sleep state
Summary: macOS Sequoia’s display remains active when KDE Connect is engaged, preventin...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdeconnect
Classification: Applications
Component: macos-application (show other bugs)
Version: unspecified
Platform: macOS (DMG) macOS
: NOR normal
Target Milestone: ---
Assignee: Ruixuan Tu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-27 12:22 UTC by Anwarul Islam
Modified: 2025-01-30 03:47 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Anwarul Islam 2024-10-27 12:22:27 UTC 
BugBug: macOS Sequoia’s display stays on when KDE Connect is active, preventing:  KDE Connect prevents macOS Sequoia from sleeping. Display remains active even when sleep is initiated, or the device is locked, draining battery life.

Steps to reproduce: 
- Open KDE Connect on MacOS
- Connect with a phone
- Click on the power button to lock and see the display doesn't turn off
Comment 1 Anwarul Islam 2024-11-24 03:31:12 UTC 
On macOS Sequoia, KDE Connect lets macOS prevent from sleeping. It doesn't even let the screen turn off. Has anyone noticed this issue?
The issue persists even after forcefully quitting KDE Connect. The only fix is restarting the PC so far I tried. I observed the activity monitor and saw that even after quitting KDE Connect there is a process running which caffinate macOS and prevent sleeping.
MacBook Pro Sequoia 15.1
Comment 2 Simon Redman 2024-12-16 22:12:09 UTC 
Please post the installed KDE Connect version so that others can try to install the same version and reproduce the issue. Please also post more details, like when you first noticed this, what changed around that time, and why you believe this is related to KDE Connect.

This sentence:

> ... even after quitting KDE Connect there is a process running which caffinate macOS ...

Seems to say that you have deduced that this issue is not related to KDE Connect.
Comment 3 Bug Janitor Service 2024-12-31 03:47:24 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Anwarul Islam 2024-12-31 09:50:51 UTC 
(In reply to Simon Redman from comment #2)
> Please post the installed KDE Connect version so that others can try to
> install the same version and reproduce the issue. Please also post more
> details, like when you first noticed this, what changed around that time,
> and why you believe this is related to KDE Connect.
> 
> This sentence:
> 
> > ... even after quitting KDE Connect there is a process running which caffinate macOS ...
> 
> Seems to say that you have deduced that this issue is not related to KDE
> Connect.

I am using latest version of KDE Connect. Built for arm based macOS.
And I experienced this since I updated my OS to Sequoia. In the previous version it was working without any issues.
Comment 5 Bug Janitor Service 2025-01-15 03:47:48 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2025-01-30 03:47:30 UTC 
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.