Hi, On Sun, 06 Dec 2020, Paul Wise wrote: > When I try to load the Hamster extension, GNOME shell from unstable > prints the following traceback into the systemd user journal, I guess > it isn't compatible with GNOME shell 3.38 at this point in time.
Duh, I am using it with GNOME Shell 3.38 but I have 3.38.1-2+b1 right now and it's what I used to test it before upload. > JS ERROR: Extension cont...@projecthamster.org: TypeError: > this.panelWidget is null > > _removeWidget@/usr/share/gnome-shell/extensions/cont...@projecthamster.org/extension.js:262:13 > > disable@/usr/share/gnome-shell/extensions/cont...@projecthamster.org/extension.js:195:14 > > _callExtensionDisable@resource:///org/gnome/shell/ui/extensionSystem.js:108:32 > > _disableAllExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:611:22 > > _disableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:610:52 It's also weird that we have calls to "disable" and "removeWidget" when you try to load the hamster extension... do you have this when you enable the extension or rather when you lock the system after having enabled the extension ? Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog <hert...@debian.org> ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋ The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄⠀⠀⠀⠀ Debian Long Term Support: https://deb.li/LTS
signature.asc
Description: PGP signature
