OS>Kernel>Power is for Chrome OS power management. This is a Linux request.

Thanks for the description of the API! device/power_save_blocker/power_save_blocker_x11.cc is where this code lives.

Why do we need a KDE specific one? Last time I checked, KDE supported the Free Desktop API. Power management works fine for me with KDE 4.

https://cs.chromium.org/chromium/src/device/power_save_blocker/power_save_blocker_x11.cc?rcl=0&l=42 says:

FREEDESKTOP_API,  // Use the FreeDesktop API, for KDE4, KDE5, and XFCE.

We don't *need* a KDE-specific one, it's just that KDE's is more versatile compared to the FDO one.

This way we could allow the screen to sleep when just listening to music vs. keeping it on all the time as if we were watching a video. I can see that Chrome treats those inhibitions (I get both "Playing Audio" and "Playing Video") separately already.

The code looks like it believes this distinction exists for fd.o: 

void PowerSaveBlocker::Delegate::ApplyBlock() {
...
    case FREEDESKTOP_API:
      switch (type_) {
        case kPowerSaveBlockPreventDisplaySleep:
          object_proxy = bus_->GetObjectProxy(
              kFreeDesktopAPIScreenServiceName,
              dbus::ObjectPath(kFreeDesktopAPIScreenObjectPath));
          method_call.reset(new dbus::MethodCall(
              kFreeDesktopAPIScreenInterfaceName, "Inhibit"));
          break;
        case kPowerSaveBlockPreventAppSuspension:
          object_proxy = bus_->GetObjectProxy(
              kFreeDesktopAPIPowerServiceName,
              dbus::ObjectPath(kFreeDesktopAPIPowerObjectPath));
          method_call.reset(new dbus::MethodCall(
              kFreeDesktopAPIPowerInterfaceName, "Inhibit"));
          break;
      }

On the other hand, https://www.freedesktop.org/wiki/Specifications/power-management-spec/ says "This is no longer supported in gnome-power-manager. This spec is considered obsolete." and all of the spec links are 404s. If KDE is the only desktop environment supporting the apparently-obsolete fd.o spec (I don't know if this is the case), maybe Chrome should implement the KDE spec rather than the fd.o one.

I guess I should mention that there's a systemd thing too: https://www.freedesktop.org/wiki/Software/systemd/inhibit/

Deprecating UI>OSIntegration in favor of the more generic Internals>PlatformIntegration