search

malko / battery-indicator-upower

gnome-shell extension to display connected devices battery level as reported by upower
GNU General Public License v2.0
5 stars 5 forks source link

Any plan to port it to GNOME 44? #7

Open iadegesso opened 1 year ago

iadegesso commented 1 year ago

Hi, as in the subject, is there any news about a port to GNOME43/44.x ?

Iade

malko commented 1 year ago

Hi @iadegesso,

I am tied to gnome42 for now, and have no test env for 43/44. I think it should work on 43, and that's why the metadata.json already announce shell-version 43. If you can confirm that it works out of the box with version 44 of gnome, I'll be pleased to add 44 to the list. I'm using linux for more than 20 years now, so you can be confident than when I'll upgrade my env to newer gnome version I'll update to that version (which will occur shortly after an ubuntu LTS release). Is this answer is ok for you ? Are you in need for a specific version support before that ?

iadegesso commented 1 year ago

Hi @iadegesso,

I am tied to gnome42 for now, and have no test env for 43/44. I think it should work on 43, and that's why the metadata.json already announce shell-version 43. If you can confirm that it works out of the box with version 44 of gnome, I'll be pleased to add 44 to the list. I'm using linux for more than 20 years now, so you can be confident than when I'll upgrade my env to newer gnome version I'll update to that version (which will occur shortly after an ubuntu LTS release). Is this answer is ok for you ? Are you in need for a specific version support before that ?

I'm running GNOME 44.1 on my Gentoo... I tryed to force compatibility in metadata.json but the extension falls into an error state... this.aggregateMenu in undefined

Iade

malko commented 1 year ago

What is weird is I don't see any reference to aggregateMenu in the extension code. I'm sorry but without a gnome 44 computer at hand I can't investigate this. You will have to wait either for a PR or for me upgrading my computers which won't be before next ubuntu LTS. In case you can gather more complete stack trace of the error I'll have a look again. Thanks for report anyway