The extension stops working unpredictably and fails to start again.

[balanza]

Describe the bug
The extension stops working unpredictably and fails to start again.
The switch would remain gray regardless of the position. The reported error is

Error: Argument handler_id: value is out of range for uint64

To Reproduce
Cannot reproduce, yet

Screenshots

Information:

• Tiling Shell version: 16
• GNOME version: 46.2

[domferr]

Hey @balanza thank you for sharing the issue. It does seem strange, since handler_id is not something Tiling Shell has. Hope you can find a way to reproduce the problem! Meanwhile, I'll do some tests

[balanza]

@domferr Thanks for the quick response!

I'm digging a bit into journalctl and I found this:

Jul 09 12:52:22 fedora gnome-shell[2634]: Object St.BoxLayout (0x55ed4bf51bb0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
                                          == Stack trace for context 0x55ed47ec8f80 ==
                                          #0   7fff84fd93b0 b   resource:https:///org/gnome/shell/ui/layout.js:992 (13b5dede510 @ 32)
                                          #1   7fff84fd9470 b   resource:https:///org/gnome/shell/ui/layout.js:999 (13b5dede560 @ 26)
                                          #2   55ed47f900b8 i   file:https:///home/emanuele/.local/share/gnome-shell/extensions/[email protected]/extension.js:2868 (221998c8eab0 @ 66)
                                          #3   55ed47f90028 i   resource:https:///org/gnome/shell/ui/layout.js:613 (13b5dedcb00 @ 127)
                                          #4   55ed47f8ff98 i   resource:https:///org/gnome/shell/ui/init.js:21 (13b5de70bf0 @ 48)
Jul 09 12:52:16 fedora gnome-shell[2634]: Extension [email protected]: Error: Argument handler_id: value is out of range for uint64

                                          Stack trace:
                                            _init/GObject.Object.prototype.disconnect@resource:https:///org/gnome/gjs/modules/core/overrides/GObject.js:702:24
                                            disconnect@file:https:///home/emanuele/.local/share/gnome-shell/extensions/[email protected]/extension.js:1009:31
                                            disconnect/<@file:https:///home/emanuele/.local/share/gnome-shell/extensions/[email protected]/extension.js:1033:35
                                            disconnect@file:https:///home/emanuele/.local/share/gnome-shell/extensions/[email protected]/extension.js:1032:37
                                            destroy@file:https:///home/emanuele/.local/share/gnome-shell/extensions/[email protected]/extension.js:1059:31
                                            disable@file:https:///home/emanuele/.local/share/gnome-shell/extensions/[email protected]/extension.js:4001:17
                                            _callExtensionDisable@resource:https:///org/gnome/shell/ui/extensionSystem.js:217:32
                                            _onEnabledExtensionsChanged@resource:https:///org/gnome/shell/ui/extensionSystem.js:639:24
                                            _sessionUpdated@resource:https:///org/gnome/shell/ui/extensionSystem.js:826:20
                                            ExtensionManager/<@resource:https:///org/gnome/shell/ui/extensionSystem.js:48:18
                                            _callHandlers@resource:https:///org/gnome/gjs/modules/core/_signals.js:130:42
                                            _emit@resource:https:///org/gnome/gjs/modules/core/_signals.js:119:10
                                            _sync@resource:https:///org/gnome/shell/ui/sessionMode.js:207:14
                                            pushMode@resource:https:///org/gnome/shell/ui/sessionMode.js:169:14
                                            activate@resource:https:///org/gnome/shell/ui/screenShield.js:616:34
                                            _onLongLightbox@resource:https:///org/gnome/shell/ui/screenShield.js:340:18
                                            onComplete@resource:https:///org/gnome/shell/ui/lightbox.js:202:18
                                            _makeEaseCallback/<@resource:https:///org/gnome/shell/ui/environment.js:67:13
                                            _easeActor/<@resource:https:///org/gnome/shell/ui/environment.js:154:64
                                            @resource:https:///org/gnome/shell/ui/init.js:21:20

I keep investigating, I let you know.

[domferr]

Thank you for the logs, much appreciated!

Jul 09 12:52:22 fedora gnome-shell[2634]: Object St.BoxLayout (0x55ed4bf51bb0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
                                          == Stack trace for context 0x55ed47ec8f80 ==
                                          #0   7fff84fd93b0 b   resource:https:///org/gnome/shell/ui/layout.js:992 (13b5dede510 @ 32)
                                          #1   7fff84fd9470 b   resource:https:///org/gnome/shell/ui/layout.js:999 (13b5dede560 @ 26)
                                          #2   55ed47f900b8 i   file:https:///home/emanuele/.local/share/gnome-shell/extensions/[email protected]/extension.js:2868 (221998c8eab0 @ 66)
                                          #3   55ed47f90028 i   resource:https:///org/gnome/shell/ui/layout.js:613 (13b5dedcb00 @ 127)
                                          #4   55ed47f8ff98 i   resource:https:///org/gnome/shell/ui/init.js:21 (13b5de70bf0 @ 
                                          

This one is related to another issue (#78) which was solved today.

Speaking about the second one, it seems it happened when the extension got disabled (manually or locking the screen or powering off the device). This log is very useful, thank you! The problem you are facing, is a consequence of another issue but unfortunately the log does not give a glimpse about the cause...

[balanza]

Ok, thanks!

That makes sense. I could try to reproduce it with a screen lock. Do you have any test you would suggest me to do? Can I provide you with some logging?

[domferr]

As far as I know, locking and unlocking may cause the error of issue #78 and maybe the problem you have is caused by doing something before unlocking/locking too!
Unfortunately, the people having the issue #78 were not able to understand the steps to reproduce the bug. Moreover I didn't have that bug and I solved it by just guessing...

Are you currently able to use Tiling Shell? Maybe you can install the bugfix of issue #78 and see if it does fix your bug too!

If you want to try that, you have two options:

• I'm publishing a new update solving the issue Layouts are deleted after unlocking PC #78, if you are able to still use Tiling Shell, you can wait until it gets accepted and hope that solves your bug too
• I already shared the bugfix of issue Layouts are deleted after unlocking PC #78 at the end of that thread, if you prefer you can already try it to understand if it solves your bug

Edit: they just accepted it! 👀 You may already update

[balanza]

I updated to the latest version and the bug it seems not to appear anymore. I tried both suspend and lock.

Kudos 🚀