-
-
Notifications
You must be signed in to change notification settings - Fork 296
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 becomes unusable if 'Power Saver' power profile is active. #969
Comments
Potentially relevant information was added to another topic here. |
I'm having the same problem. Almost gave up on the app before finding this issue, since I had no idea of what was the problem. Glad I didn't, since the app is great. Thanks for finding and reporting! And I believe it is indeed a low priority bug, but also something that will improve the user experience a lot, since Power Saving mode is great for this app's use case: reading books on your computer. |
Thanks for everyone's efforts identifying this. Would an in-app notification be feasible to alert users to this issue until it is resolved? Foliate is particularly likely to be used by non-technical users who are less likely to be able to find the workaround here. |
Sounds great. The Gtk-banner widget seems the most appropriate way to give this alert, appearing only when Power Saving mode is on. A button to disable Power Saving mode can be made available and be pressed directly from the banner. |
I have the exact same problem on a Librem5 running PureOS. The L5 does not have a Power Saver mode. |
After reading the source code of power profile daemon, I find that by default it use platform profile. I believe that means power saving is implemented by firmware. |
@iiiian thanks for replying. To be honest, I fail to see the relevance of your comment to the topic. Can you please elaborate further? How does the knowledge you shared contribute to resolving this issue? |
Tried the gtk4 branch. Unlike previous versions, it can open and render books normally for the most part. The only thing that's broken now seems to be the new sliding animation (see #188 and #862). This occurs in Epiphany as well. Upon closer examination, it appears that |
This issue seems to be gone now. Here's what I know:
- All morning I've been opening numerous .epub files in Foliate with Power
Profile set to "Power Saver", everything seems to be working as expected;
- The issue was still present 2 weeks at latest when I last checked it;
Some update may have happened that helped.
Can anyone else please try on their end to confirm, or deny me? I'm
reminding of steps to reproduce:
- Activate 'Power Saver' Power Profile (can be done in multiple ways,
for example Ubuntu Settings > Power > Power Profile > Power Saver)
- Run Foliate and load any .epub file (only .epub is tested, possibly
the bug exists for other formats too)
|
I can confirm this seems fixed now on Fedora Silverblue 38.20231015.0 and flatpaks (Foliate + runtime) updated to latest. |
Fixed on Arch updated to latest |
Describe the bug
GNOME version 41 has introduced the Power Profiles feature. One of its presets, 'Power Saver' specifically, causes a number of operation critical issues with Foliate's graphical interface. More information is available in #879.
Workaround
Before running Foliate, select any Power Profile other than 'Power Saver', for example 'Balanced' or 'Performance'.
Steps to reproduce
Expected behavior
Foliate should load the file, display its content, and accept navigation through the loaded file by clicking on respective gui elements and using mouse & keyboard shortcuts/commands.
What happens instead
Version:
Additional context
This bug was first reported in #879 but it took some time to track down the actual causes. The original thread is now closed because it contains a number of outdated and potentially harmful assumptions, and to allow for better prioritisation of debugging.
Since there is an easy workaround, there is no urgency to fix this bug. Also, because GNOME's Power Profile feature is not well documented (we don't know what exactly the "Power Saver" preset does), it is at this time difficult to debug it. For these two reasons, this bug should have a relatively low priority in fixing.
The text was updated successfully, but these errors were encountered: