Your message dated Mon, 07 Dec 2020 13:19:17 +0800
with message-id <[email protected]>
and subject line Re: Bug#976633: gnome-shell-extension-hamster: crash:
TypeError: this.panelWidget is null
has caused the Debian Bug report #976633,
regarding gnome-shell-extension-hamster: crash: TypeError: this.panelWidget is
null
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
976633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976633
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-shell-extension-hamster
Version: 0.10.0+git20200509-1
Severity: serious
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.
JS ERROR: Extension [email protected]: TypeError: this.panelWidget
is null
_removeWidget@/usr/share/gnome-shell/extensions/[email protected]/extension.js:262:13
disable@/usr/share/gnome-shell/extensions/[email protected]/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
_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:628:18
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:133:47
_sync@resource:///org/gnome/shell/ui/sessionMode.js:195:14
pushMode@resource:///org/gnome/shell/ui/sessionMode.js:156:14
activate@resource:///org/gnome/shell/ui/screenShield.js:583:34
lock@resource:///org/gnome/shell/ui/screenShield.js:632:14
LockAsync@resource:///org/gnome/shell/ui/shellDBus.js:378:28
_handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:371:35
_wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:404:34
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-debug
APT policy: (900, 'testing-debug'), (900, 'testing'), (800,
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700,
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8),
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gnome-shell-extension-hamster depends on:
ii gnome-shell 3.38.2-1
ii hamster-time-tracker 3.0.2-3
gnome-shell-extension-hamster recommends no packages.
gnome-shell-extension-hamster suggests no packages.
-- no debconf information
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
On Sun, 2020-12-06 at 18:30 +0800, Paul Wise wrote:
> Thats entirely plausible, will try to debug after next logout/login.
I logged out and then it worked after login, hmmm. Closing.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
--- End Message ---
