search

elementary / wingpanel-indicator-power

Wingpanel Power Indicator
GNU General Public License v3.0
26 stars 15 forks source link

Drop "Apps Using Lots of Power" feature #247

Closed lenemter closed 11 months ago

lenemter commented 1 year ago

Closes #208 Closes #227

This is not Wayland compatible and IMO useless feature. I'm interested is there someone who thinks otherwise and is against removing this feature?

tintou commented 1 year ago

The only thing I liked was to be able to see that one app is the one currently using all my CPU (and thus the power of my laptop) but that's something I'm okay to trade for wayland support

danirabbit commented 1 year ago

Yeah it would be nice if we could do this in a Wayland-compatible way because I think it is handy to be able to see why my fans are going crazy and we don't have any other built-in system monitor feature

TomiOhl commented 1 year ago

we don't have any other built-in system monitor feature

I'd advocate for building a simple system monitor instead, that could be even more useful, albeit arguably it would not provide an "at a glance" answer in all cases. Or maybe just ship gnome's one (although it's design language is very different from elementary). The default keybinding for launching the task manager in windows is Ctrl + Shift + Esc, wondering how many people know about/use this

orowith2os commented 1 year ago

I want to say this feature is able to be implemented on Wayland, just in a different way, but I'm not entirely sure on the technical details.

Here in GNOME, we can see which apps are running in the background reliably by asking Flatpak. If a Flatpak is running in the background (without a window), it'll automatically show in the appropriate menu. This relies on the Flatpak sandbox to work, and so is iffy on native packages; I haven't seen them working with this at all.

Maybe something similar could be looked into for power usage? This would then make it a Flatpak-only feature though, but I don't see much pain in that. Native apps are hell to get working with this anyways.

As for an actual system monitor: basing off of what GNOME has isn't a bad idea. It would definitely help, vs making your own from scratch.

EDIT: never mind, this exists: https://github.com/stsdc/monitor