Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

interface/screen_inhibit_control: Improve screen inhibit control for use on core #14134

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

er-vin
Copy link
Contributor

@er-vin er-vin commented Jun 26, 2024

  • Make it available on Ubuntu Core
  • Receive notifications for inhibit changes, plugged application could change the inhibit status but had no way to be notified when it actually changes.

@ernestl ernestl requested a review from alexmurray July 3, 2024 19:12
@ernestl ernestl added the Needs security review Can only be merged once security gave a :+1: label Jul 3, 2024
@bboozzoo bboozzoo changed the title interface/screen_inhitib_control: Improve screen inhibit control for use on core interface/screen_inhibit_control: Improve screen inhibit control for use on core Jul 4, 2024
Copy link
Contributor

@alexmurray alexmurray left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@er-vin er-vin force-pushed the improve-screen-inhibit-control-for-use-on-core branch from bd22eba to b6b55ef Compare July 23, 2024 14:30
@ernestl ernestl added this to the 2.66 milestone Sep 1, 2024
@ernestl ernestl closed this Sep 3, 2024
@ernestl ernestl reopened this Sep 3, 2024
@er-vin er-vin force-pushed the improve-screen-inhibit-control-for-use-on-core branch from b6b55ef to 88e6436 Compare September 3, 2024 08:02
@ernestl ernestl removed the Needs security review Can only be merged once security gave a :+1: label Sep 19, 2024
Copy link
Contributor

@jhenstridge jhenstridge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The addition of access to the HasInhibitChanged signal looks fine (it is included in this copy of the spec). Making the interface implicit on core seems suspect.

Checking my KDE Core Desktop VM, org.freedesktop.PowerManagement on the session bus is owned by org_kde_powerdevil running with the AppArmor label snap.plasma-desktop-session.plasma-powerdevil. Similarly org.freedesktop.ScreenSaver is owned by a process with the label snap.plasma-desktop-session.plasma-kwin-wayland. So allowing communication with label=unconfined does not sound like it would actually enable any communication here.

For proper operation on Core, the interface would need to be modified to allow a snap to provide the slot.

@ernestl ernestl modified the milestones: 2.66, 2.67 Sep 27, 2024
@ernestl
Copy link
Collaborator

ernestl commented Sep 27, 2024

Changed milestone to 2.67, needs more time.

This can be provided by a session snap in such a case
Plugged application could change the inhibit status but had no way to be
notified when it actually changes.
@er-vin er-vin force-pushed the improve-screen-inhibit-control-for-use-on-core branch from 88e6436 to 98d006b Compare September 30, 2024 16:58
@er-vin
Copy link
Contributor Author

er-vin commented Sep 30, 2024

For proper operation on Core, the interface would need to be modified to allow a snap to provide the slot.

It has been reworked in this direction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants