Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken with Gnome 46 #2207

Open
migig opened this issue Oct 28, 2024 · 14 comments
Open

Broken with Gnome 46 #2207

migig opened this issue Oct 28, 2024 · 14 comments
Labels

Comments

@migig
Copy link

migig commented Oct 28, 2024

Describe the bug
I upgrade to gnome 46 and now panel is faulty.

It has the problem after sleep/suspend - it disappear or will show but with error.

If I open the extensions application then I see that dash-to-panel extension is automatically disable. This is strange because when booting (before suspend for first time) then gnome is ok... it is only after suspend for first time that it errors.

Sometimes it show and sometime not. And if it show, it has icons, apps, tray and time in incorrect location or maybe not show at all.

Linux distribution and version
Ubuntu 24.04

GNOME Shell version
46.0

Dash-to-Panel version
64

Where was Dash-to-Panel installed from?
The GNOME extensions website

@migig migig added the bug label Oct 28, 2024
@SlavikZ
Copy link

SlavikZ commented Oct 30, 2024

I have a similar behavior on Ubuntu 24.04. After unlocking the screen, the latest version (64) activates the Ubuntu Dock or crashes the entire gnome-shell. After the first login, it works as expected.
The previous version works without any issues.

@amaylunagaria
Copy link

+1

@lonix1
Copy link

lonix1 commented Oct 30, 2024

I suspect all these bugs are somehow related to changes in GNOME 46:

There's a good chance it's a single bug. All these bugs are related to dock or icon visibility, are for gnome 46 and were reported recently - which makes sense as ubuntu 24 (and all "flavours") was released recently, with gnome 46.

@Acknar
Copy link

Acknar commented Nov 5, 2024

I have also pinned down session crashes upon resuming from suspend on ubuntu down to dash to panel extension

@jgrocha
Copy link

jgrocha commented Nov 18, 2024

Same problem here.

$ 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]
[email protected]
jgr@dragon:~$ gnome-extensions info [email protected]
[email protected]
  Name: Dash to Panel
  Description: 
  Path: /home/jgr/.local/share/gnome-shell/extensions/[email protected]
  URL: https://github.com/home-sweet-gnome/dash-to-panel
  Version: 64
  Enabled: Yes
  State: ACTIVE
$ journalctl -f /usr/bin/gnome-shell 
nov 18 23:54:58 dragon.geomaster.pt gnome-shell[6064]: TypeError: SettingsManager.getDefault() is null
                                                       
                                                       Stack trace:
                                                         getDefaultGSettings@file:///home/jgr/.local/share/gnome-shell/extensions/[email protected]/settingsManager.js:54:28
                                                         _updateIconSize@file:///home/jgr/.local/share/gnome-shell/extensions/[email protected]/appIndicator.js:1552:42
                                                         _updateWhenFullyReady@file:///home/jgr/.local/share/gnome-shell/extensions/[email protected]/appIndicator.js:1012:18
                                                         async*_init/<@file:///home/jgr/.local/share/gnome-shell/extensions/[email protected]/appIndicator.js:965:22
                                                         removeChrome@resource:///org/gnome/shell/ui/layout.js:919:22
                                                         disable/<@file:///home/jgr/.local/share/gnome-shell/extensions/[email protected]/panelManager.js:244:32
                                                         disable@file:///home/jgr/.local/share/gnome-shell/extensions/[email protected]/panelManager.js:224:24
                                                         disable@file:///home/jgr/.local/share/gnome-shell/extensions/[email protected]/extension.js:73:22
                                                         _callExtensionDisable@resource:///org/gnome/shell/ui/extensionSystem.js:218:32
                                                         _onEnabledExtensionsChanged@resource:///org/gnome/shell/ui/extensionSystem.js:644:24
                                                         async*_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:835:20
                                                         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
                                                         
nov 18 23:54:58 dragon.geomaster.pt gnome-shell[6064]: 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
nov 18 23:54:59 dragon.geomaster.pt gnome-shell[6064]: no authentication service is enabled, using password authentication
nov 18 23:54:59 dragon.geomaster.pt gnome-shell[6064]: no authentication service is enabled, using password authentication
nov 18 23:55:00 dragon.geomaster.pt gnome-shell[6064]: meta_dbus_session_manager_uninhibit: assertion 'priv->inhibit_count > 0' failed
nov 18 23:55:00 dragon.geomaster.pt gnome-shell[6064]: meta_dbus_session_manager_uninhibit: assertion 'priv->inhibit_count > 0' failed
nov 18 23:55:00 dragon.geomaster.pt gnome-shell[6064]: meta_dbus_session_manager_uninhibit: assertion 'priv->inhibit_count > 0' failed
nov 18 23:55:00 dragon.geomaster.pt gnome-shell[6064]: 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/gdm/authPrompt.js:905:13
                                                       finish@resource:///org/gnome/shell/ui/unlockDialog.js:931:26
                                                       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

@yuvalaviel
Copy link

+1

+1

@antonio24073
Copy link

+1

+1

+1

@roackim
Copy link

roackim commented Nov 29, 2024

+1

+1

+1

+1

@fernandoshinohara
Copy link

+1

+1

+1

+1

+1

@TimFaro
Copy link

TimFaro commented Dec 12, 2024

+1

+1

+1

+1

+1

+1

@arinc9
Copy link

arinc9 commented Dec 21, 2024

+1

+1

+1

+1

+1

+1

+1

@VanilsonFernandes
Copy link

It seems to have been fixed in Ubuntu 24.04.1 LTS after some system updates

@amaylunagaria
Copy link

amaylunagaria commented Jan 7, 2025

yes, i think it has been fixed

Edit: Nope its has not, it worked for a day or two but then i was logged out again and ubuntu kinda crashed.

@MattOnyx
Copy link

I have a similar behavior on Ubuntu 24.04. After unlocking the screen, the latest version (64) activates the Ubuntu Dock or crashes the entire gnome-shell. After the first login, it works as expected. The previous version works without any issues.

Exact same issue on 24.04.1 LTS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests