hamster-shell-extension
hamster-shell-extension copied to clipboard
projecthamster
Important note for users of GNOME > 3.20
hamster-shell-extension on extensions.gnome.org is outdated
The official version of hamster-shell-extension on extensions.gnome.org (e.g.o) is outdated and will not work with any recent GNOME version (it supports GNOME up to 3.20). This can't be fixed easily. For now, please use the manual installation from git.
Where to find hamster-shell-extension for recent GNOME versions
In general, find all releases of the hamster shell extension on the tags page. A tag such as gnome-shell-40 denotes the first version of the extension that works under the respective GNOME shell version. It doesn't necessarily mean that this code won't work with older GNOME shell versions. Information about compatibility with GNOME shell versions is stored in the file metadata.json.in.
Novice users can download and unpack the ZIP files linked in the table below, while advanced users may prefer using git clone and git checkout, using the indicated branches and tags.
| GNOME version | Pull request | tag or Git repo | ZIP file |
|---|---|---|---|
| 3.28 and before | n/a | Release 0.10.0 | download |
| 3.30 | #299 | gnome-shell-3.30 | download |
| 3.32 | #312 | gnome-shell-3.32 | download |
| 3.34, 3.36 | #323 | gnome-shell-3.36 | download |
| 3.38 | #339 | gnome-shell-3.38 | download |
| 3.34-3.38, 40-44 | n/a | gnome-shell-44 | download |
| 45-46 | #364 | "develop" branch | download |
How to run hamster-shell-extension with recent GNOME versions
Follow the instructions in README.rst, section "Manual Installation For Testing and Development". Note: The section "Creating a development environment" in the README can be skipped!
Reporting problems
If you find an issue with the hamster-gnome-extension, please always report the GNOME version you are running, and make sure that you have a version of the extension that supports this GNOME version. If you see problems with the correct version, please report an issue here, your feedback will be welcome.
Removed the link to gnome-shell-3.34, as the 3.36 version runs fine on 3.34, too.
The official extension is still failing to install, the code in develop in the other hand install without problems. I'm in a Gnome 3.38.4 (Debian sid.)
develop branch works great on GS40/wayland/archlinux. To "get in touch": I'm willing to test new features. Just ping me somewhere in the PR or comment.
EDIT: It is working now. Possibly a restart was necessary, otherwise it was not even showing in gnome-extension. Thanks again for this great extension.
First I tried to install from extensions.gnome.org - however, it gave errors. I tried 3.36 version in gnome-shell 40.4 and unfortunately nothing is being shown in gnome-extension. I'm in Manjaro linux with linux 5.13 and Gnome DE. Do anyone have any update about this otherwise amazing tools?
Also, Details about trying install from https://extensions.gnome.org/extension/425/project-hamster-extension/
The settings of extension [email protected] had an error:
SyntaxError: redeclaration of let renderer
Stack trace:
_init@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:206:33
OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:122:28
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:115:22
run@resource:///org/gnome/Shell/Extensions/js/dbusService.js:177:20
main@resource:///org/gnome/Shell/Extensions/js/main.js:19:13
run@resource:///org/gnome/gjs/modules/script/package.js:206:19
start@resource:///org/gnome/gjs/modules/script/package.js:190:8
@/usr/share/gnome-shell/org.gnome.Shell.Extensions:1:17
I'm on Gnome 44 on Fedora 38 running develop branch latest version (commit 75541ac2) and got this error in journalctl -xe when trying to disable the extension by toggling the slider in Extensions app:
May 31 08:52:56 uberneek gnome-shell[294737]: Shutting down hamster-shell-extension.
May 31 08:52:56 uberneek gnome-shell[294737]: Object .Gjs_places-menu_gnome-shell-extensions_gcampax_github_com_extension_PlacesMenu (0x564c9555a770), has been already disposed >
May 31 08:52:56 uberneek gnome-shell[294737]: == Stack trace for context 0x564c943ecc60 ==
May 31 08:52:56 uberneek gnome-shell[294737]: #0 564c9b3b1f58 i /usr/share/gnome-shell/extensions/[email protected]/extension.js:160 (a1b>
May 31 08:52:56 uberneek gnome-shell[294737]: #1 7fff10688f10 b resource:///org/gnome/shell/ui/extensionSystem.js:125 (2af59ea13970 @ 407)
May 31 08:52:56 uberneek gnome-shell[294737]: #2 564c9b3b1dc8 i resource:///org/gnome/shell/ui/extensionSystem.js:565 (2af59ea17150 @ 456)
May 31 08:52:56 uberneek gnome-shell[294737]: #3 564c9b3b1d48 i resource:///org/gnome/shell/ui/extensionSystem.js:627 (2af59ea173d0 @ 12)
May 31 08:52:56 uberneek gnome-shell[294737]: #4 7fff1068ac90 b resource:///org/gnome/gjs/modules/core/overrides/Gio.js:730 (389b78cc90 @ 169)
May 31 08:52:56 uberneek gnome-shell[294737]: #5 564c9b3b1ca0 i resource:///org/gnome/shell/ui/extensionSystem.js:238 (2af59ea13ab0 @ 198)
May 31 08:52:56 uberneek gnome-shell[294737]: #6 564c9b3b1c18 i resource:///org/gnome/shell/ui/shellDBus.js:451 (16d23ed68830 @ 20)
May 31 08:52:56 uberneek gnome-shell[294737]: #7 564c9b3b1b38 i resource:///org/gnome/gjs/modules/core/overrides/Gio.js:329 (389b785f10 @ 185)
May 31 08:52:56 uberneek gnome-shell[294737]: #8 564c9b3b1a88 i resource:///org/gnome/gjs/modules/core/overrides/Gio.js:408 (389b78c0b0 @ 34)
May 31 08:52:56 uberneek gnome-shell[294737]: Window manager warning: Trying to remove non-existent keybinding "show-hamster-dropdown".
May 31 08:52:56 uberneek gnome-shell[294737]: Shutting down hamster-shell-extension.
May 31 08:52:56 uberneek gnome-shell[294737]: JS ERROR: Extension [email protected]: TypeError: this.panelWidget is null
_removeWidget@/home/neek/.local/share/gnome-shell/extensions/[email protected]/extension.js:283:13
disable@/home/neek/.local/share/gnome-shell/extensions/[email protected]/extension.js:195:14
_callExtensionDisable@resource:///org/gnome/shell/ui/extensionSystem.js:125:49
_onEnabledExtensionsChanged@resource:///org/gnome/shell/ui/extensionSystem.js:565:24
_loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:627:18
createCheckedMethod/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:730:46
disableExtension@resource:///org/gnome/shell/ui/extensionSystem.js:238:29
DisableExtension@resource:///org/gnome/shell/ui/shellDBus.js:451:38
_handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:329:38
_wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:408:34
The 'places menu' bit might be irrelevant, but that this.panelWidget is null looks like a Hamster Indicator issue. Should I leave this report here, or raise a new Issue?
@neekfenwick That sounds like a new issue, separate from the one you commented on. I've opened #359 to discuss this issue separately.
develop branch works on Ubuntu 22.04. (GNOME Shell 42.9)
Unclear to me if icon is missing or discontinued.
Correction: icon can be enabled in extension settings. I believe Label and Icon is default for many extensions..
(advice to reload shell using alt+f2 -> r is invalid for wayland, but disable->enable works)
PS. I would suggest adding something about reloading or testing extensions to lower the threshold for potential testers. This Reddit post helped me. Clarifying just how to get in touch would probably also help with tester recruitment. I use this extension every single day, so sign me up! :-)
@Fnordbert, glad to hear you are a satisfied user :-)
Where do you recommend this information to be added? In the README? In this issue here?
"How to reload a GNOME extension" is a generic question, unrelated to this specific extension. Documenting stuff like this is always kind of dangerous because the information is likely to be out of date sooner or later.
@mwilck, well, with the "call to action" at the top of the README I'd find it find it natural to just be a bit more specific there. Or perhaps it's obvious how to get in touch for the kind of testers you are looking for, I don't know. What I do know that using GitHub issues as a forum is often frowned upon :-)
Yeah, I see what you mean about documenting "external" stuff. What I'm saying is that I, as a longtime Linux user, found this surprisingly hard to figure out. I guess this is due to old "taken for granted" stuff, no longer holding true after Wayland etc.
Perhaps some sort of "be aware" notice at the end of "Manual Installation" would be good?
Desktops and window-managers are really outside my comfort zone as a developer, so I'm unsure of exactly what to write, but if I were to play with the JS now, what I'd use is a nested shell: dbus-run-session -- gnome-shell --nested --wayland.
Perhaps there are better ways, but at least a little more handholding to get started would probably be good to get more testers onboard.
As you've been experimenting with this, please propose some text, I'll happily update the issue.
Personally I don't use wayland and thus I can comfortably just use Alt-f2 + r.
Hm. ok, how about:
If you are using Wayland, be aware that alt+f2 -> r no longer reloads gnome-shell and you will have to re-login, or alternatively use a nested session for testing. (dbus-run-session -- gnome-shell --nested --wayland)
Compatibility with Gnome 45 may need new branch https://gjs.guide/extensions/upgrading/gnome-shell-45.html
Oh, how much I love this :-/ And the extensions won't be backward compatible either. Brilliant.
Patches welcome!
Updated the issue text to reflect properly that "develop" supports 3.34 ff., too, and added a link to the experimental GNOME 45 branch.
The issue text still claimed that we'd upload to e.g.o until March, 2020. I removed this misleading statement.
Support for GNOME 45 has been merged into the develop branch.
I updated this issue to reflect the new situation.