Open quequotion opened 5 years ago
@quequotion Can you post an image of your indicator-powersave please
Here's an animated gif; it's a little fast, but you can see two frames: the initial menu ('System Throttle' is clicked), and then a submenu (Back, full, cut).
With 105c1d0, the submenu is blank. No options, no click targets; just empty.
My guess is this commit glitches drawing menus such that only the first tier are rendered.
Oh, if the indicator is outside the three-dot indicator, it's out of scope of this project, I'm sorry.
The screenshot above doesn't show the indicator in a broken state in wingpanel-indicator-namarupa, it shows it in a working state in wingpanel-indicator-ayatana. I uploaded this screenshot as a demonstration of indicator-powersave; not as a demonstration of the bug. I assure you both wingpanel-indicator-namarupa and wingpanel-indicator ayatana have the same problem since commit 105c1d0 in wingpanel.
Oh, I'm sorry, I misread your post. :pray:
Also, I'm sure this will be resolved once the project is taken interest in again.
Thank you. I do hope there's something that can be done about it it in namarupa (and ayatana, for what it's worth as it still works even if it is archived), because I don't think I can convince the wingpanel devs to fix something that breaks unsupported indicators.
This suffers from the same issue as wingpanel-indicator-ayatana.
Ever since commit 105c1d0 in wingpanel, submenus in indicators are not shown.
Indicator-powersave, my own fork of indicator-cpufreq is an example. Have a look at how I make the submenus.
Glippy is another indicator affected by this issue.
My fork of wingpanel's AUR package has a patch to reverse 105c1d0 which resolves this--at the cost of undoing the initial draw delay that was fixed by that commit.