Closed Darko393 closed 2 years ago
i had this too!
Can confirm as well.
Problem is within prefs.js. I'm not a js programmer so somebody else maybe can see a fix.
It seems that branch 41 was pushed to gnome-extensions and not master. pref.js from master branch fixes this.
Hi all, Can you each give me the version of your gnome-shell?
$ gnome-shell --version GNOME Shell 41.3
Hi @AI-ien; I pushed a new version yesterday, can you test? https://extensions.gnome.org/extension/4085/big-sur-status-area/
Yes, it is the same version 28 that causes error. I don't know if it is relevant, but Website button in extensions app points to 40.rc branch https://github.com/Ordissimo/Big-Sur-StatusArea/tree/40.rc
Hi All, Please excuse me, the migration to the new gnome-shell formalism has been complex. I just tested on gnome-shell 41.3, it works! The Fix https://github.com/Ordissimo/Big-Sur-StatusArea/commit/24ab752a287c03fdd5c3bd29c26ce9b13f7905bb The corrected file : https://raw.githubusercontent.com/Ordissimo/Big-Sur-StatusArea/master/prefs.js I pushed a fix version in the store (It is necessary to wait for the publication): https://extensions.gnome.org/extension/4085/big-sur-status-area/ Thanks for your feedback!
The version 29 fixes this problem, it has just been released in https://extensions.gnome.org/extension/4085/big-sur-status-area/
All good! Thanks for your work.
The settings of extension bigSur-StatusArea@ordissimo.com had an error:
Stack trace: