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

⚠️ 0.9.15 regressions #1792

Closed
Alexays opened this issue Nov 15, 2022 · 15 comments
Closed

⚠️ 0.9.15 regressions #1792

Alexays opened this issue Nov 15, 2022 · 15 comments
Labels
help wanted Extra attention is needed regression
Milestone

Comments

@Alexays
Copy link
Owner

Alexays commented Nov 15, 2022

Hi folks,
I'm creating a new issue to have all the regressions related to 0.9.15 in one place and be able to fix them more easily.
I also thought of revert #1120
What do you think?

#1781
#1786
#1763
#1775
#1778
#1743
#1741
#952
#1761
#1752
#1791
#1765

@Alexays Alexays added help wanted Extra attention is needed regression labels Nov 15, 2022
@Alexays Alexays pinned this issue Nov 15, 2022
@Alexays Alexays added this to the 0.9.16 milestone Nov 15, 2022
@Alexays Alexays changed the title 0.9.15 regressions ⚠️ 0.9.15 regressions Nov 15, 2022
@Estebiu
Copy link

Estebiu commented Nov 15, 2022

I would also like to add that when I upgraded waybar to 0.9.15 the battery indicator is "strange". It shows me the exact half of what my battery capacity is. So if htop says I'm at 100%, waybar will say that I'm at 50%. If I'm at 34%, waybar will say that I'm at 17% and so on.

@grfrederic
Copy link
Contributor

@Estebiu I made changes to the battery calculation recently, could you give more info? What is your exact version? Do you have more than one battery (say, in /sys/class/power_supply/)?

@PowerMan2206
Copy link

I think you should revert #1120.

@Estebiu
Copy link

Estebiu commented Nov 15, 2022

@Estebiu I made changes to the battery calculation recently, could you give more info? What is your exact version? Do you have more than one battery (say, in /sys/class/power_supply/)?

I'm using the latest waybar-hyprland-git from the AUR as I'm on Hyprland. And no, I don't have another battery; my laptop doesn't support it (asus zenbook ux363ea). Just now I tried the standard waybar package and the battery monitor works normally. Very strange.
I would like to add that I was using waybar-hyprland-git until 2/3 days ago without any problems.
EDIT: waybar-hyprland works normally too.

@grfrederic
Copy link
Contributor

@Estebiu Right, that does sound like #1788 might have broken it for you. The tricky part is I only have a laptop with TWO batteries. I can remove one of them once I'm home and see if I can replicate the issue.

@grfrederic
Copy link
Contributor

Oh also before we fix this, as a temporary hack you can probably set full-at to 50% in your config.

@roland-5
Copy link

@grfrederic I tested it now and unplugged my laptop from power source. To 79% falling was normal, and then for few minutes it changed to 43% to change 62% for long time and now it normally show 42%. For me it doesn't matter as I'm always on charger, but if you want me to check something then go ahead - everything that I can do without knowing C. :P

@grfrederic
Copy link
Contributor

grfrederic commented Nov 16, 2022

@roland-rollo thank you for testing, sadly that does not really sound related. I changed the capacity computation to divide by the total number of batteries, and for @Estebiu around that time it starts showing half the capacity. Perhaps the jumps in reported battery level might mean your battery degraded/is not calibrated. In any case, as long as /sys/class/power_supply/BAT0/capacity (on linux) shows the same number as waybar it's probably not an issue with waybar.

@TRPB
Copy link

TRPB commented Nov 16, 2022

Can I suggest reverting back to 0.9.13 as the primary release (possibly release it as 0.9.16) and then the release with these changes as a 0.10 beta so they can be fixed and not upgraded to automatically by users?

0.9.15 broke a lot of stuff to the point where it is unusable for a lot of us.

@grfrederic
Copy link
Contributor

grfrederic commented Nov 16, 2022

@Estebiu I tried with one battery unplugged and -- it works on my machine :) If you would be up for it we can try figuring out together what makes it break on your laptop. I'm not sure this is the best place to do it though, let's move this discussion to the closed PR #1788?

Reverting temporarily #1120 (or more) and fixing things on the side before rerelease sounds reasonable to me. I can help with testing and (perhaps with some pointers from more regular contributors) some coding.

@fubuki4649
Copy link

fubuki4649 commented Nov 18, 2022

I think reverting #1120 is a good idea as it introduces breaking changes for no good reason. Such changes should be avoided in the future

@meemo
Copy link

meemo commented Nov 20, 2022

I think reverting #1120 is introduces breaking changes for no good reason. Such changes should be avoided in the future

It's introducing a breaking change to fix a breaking change which breaks many themes.

For example, here is what my theme (a slightly modified version cjbassi's config) looks like on 0.9.13:

0.9.13

And here is how it looks on 0.9.15:

0.9.15

I had some luck with this comment in #1741, however now everything is tiny:

0.9.15 unset all

I tried several suggestions in other issues and unfortunately have had no luck in getting my theme working again.

@pinselimo
Copy link
Contributor

As the author of #1120 I also think it's better to revert it now, try to fix the issue and introduce it in a more major update after some beta-testing.

On the other hand, a lot of the features using buttons adds over using labels are also available after a shift to Gtk4, so this may be an option for a major version bump as well.

The heterogeneity of configurations is a major issue for quality assurance. It would be great to introduce some guarantees for the users as to which configs are certain to look the same across updates. E.g. have some example configs covering most of the heterogeneity be required to look the same.

@Alexays
Copy link
Owner Author

Alexays commented Nov 23, 2022

Agree with you @pinselimo, do you think you have some time to revert the PR?
I'll try to find some times next week, otherwise.

@pinselimo pinselimo mentioned this issue Nov 24, 2022
@Alexays
Copy link
Owner Author

Alexays commented Nov 24, 2022

Closed as reverted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed regression
Projects
None yet
Development

No branches or pull requests

9 participants