Most potential error paths don't allow gnome-shell to know which
extension is to blame for a bug. But certainly during
activate/deactivate it seems reasonable that gnome-shell should know
which one to blame.
** Summary changed:
- No gnome-shell extensions after lock screen
+ No gnome-shell unloads all extensions if only one fails during
activate/deactivate
** Changed in: gnome-shell (Ubuntu)
Status: Invalid => New
** Summary changed:
- No gnome-shell unloads all extensions if only one fails during
activate/deactivate
+ gnome-shell unloads all extensions if only one fails during
activate/deactivate
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2085873
Title:
gnome-shell unloads all extensions if only one fails during
activate/deactivate
Status in gnome-shell package in Ubuntu:
New
Bug description:
I have gnome extensions installed and working.
jgr@dragon:~$ gnome-shell --version; lsb_release -r; echo $XDG_SESSION_TYPE;
gnome-extensions list
GNOME Shell 46.0
No LSB modules are available.
Release: 24.04
x11
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
After a blank screen, the extensions are gone.
After the blank screen, the extensions do not work. However, the "Use
Extensions" option is enabled when opening the extension manager.
If I disable and enable the extensions again, it works. So I have to
disable and enable extensions after any blank screen event.
jgr@dragon:~$ journalctl -f /usr/bin/gnome-shell
out 27 12:49:05 dragon.geomaster.pt gnome-shell[5046]: Unhandled promise
rejection. To suppress this warning, add an error handler to your promise chain
with .catch() or a try-catch block around your await expression. Stack trace of
the failed promise:
_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:833:26
ExtensionManager/<@resource:///org/gnome/shell/ui/extensionSystem.js:49:18
_callHandlers@resource:///org/gnome/gjs/modules/core/_signals.js:130:42
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:119:10
_sync@resource:///org/gnome/shell/ui/sessionMode.js:211:14
pushMode@resource:///org/gnome/shell/ui/sessionMode.js:173:14
activate@resource:///org/gnome/shell/ui/screenShield.js:661:34
SetActive@resource:///org/gnome/shell/ui/shellDBus.js:530:32
_handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:329:38
_wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:408:34
@resource:///org/gnome/shell/ui/init.js:21:20
out 27 12:49:09 dragon.geomaster.pt gnome-shell[5046]:
meta_dbus_session_manager_uninhibit: assertion 'priv->inhibit_count > 0' failed
out 27 12:49:09 dragon.geomaster.pt gnome-shell[5046]:
meta_dbus_session_manager_uninhibit: assertion 'priv->inhibit_count > 0' failed
out 27 12:49:09 dragon.geomaster.pt gnome-shell[5046]:
meta_dbus_session_manager_uninhibit: assertion 'priv->inhibit_count > 0' failed
out 27 12:49:09 dragon.geomaster.pt gnome-shell[5046]: Window manager
warning: Event has no timestamp! You may be using a broken program such as xse.
Please ask the authors of that program to fix it.
out 27 12:49:09 dragon.geomaster.pt gnome-shell[5046]: Unhandled promise
rejection. To suppress this warning, add an error handler to your promise chain
with .catch() or a try-catch block around your await expression. Stack trace of
the failed promise:
_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:833:26
ExtensionManager/<@resource:///org/gnome/shell/ui/extensionSystem.js:49:18
_callHandlers@resource:///org/gnome/gjs/modules/core/_signals.js:130:42
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:119:10
_sync@resource:///org/gnome/shell/ui/sessionMode.js:211:14
popMode@resource:///org/gnome/shell/ui/sessionMode.js:182:14
_continueDeactivate@resource:///org/gnome/shell/ui/screenShield.js:588:30
deactivate/<@resource:///org/gnome/shell/ui/screenShield.js:579:44
finish@resource:///org/gnome/shell/ui/unlockDialog.js:927:13
deactivate@resource:///org/gnome/shell/ui/screenShield.js:579:26
_onUserBecameActive@resource:///org/gnome/shell/ui/screenShield.js:378:18
@resource:///org/gnome/shell/ui/init.js:21:20
out 27 12:52:54 dragon.geomaster.pt gnome-shell[5046]: Window manager
warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0
for 0x5600004
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-shell 46.0-0ubuntu6~24.04.5
ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12
Uname: Linux 6.8.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 29 20:44:46 2024
DisplayManager: gdm3
InstallationDate: Installed on 2021-04-13 (1296 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to noble on 2024-09-26 (33 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-07-22T15:59:07
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2085873/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
