You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
so after the update of the extension to the new gnome, it crashes gnome right away:
Nov 20 02:52:35 tux-2 gnome-shell[8649]: [pano] [extension] extension is initialized
Nov 20 02:52:35 tux-2 gnome-shell[8649]: libsoup3 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported.
Nov 20 02:52:35 tux-2 gnome-shell[8649]: == Stack trace for context 0x55d65cfc37a0 ==
Nov 20 02:52:35 tux-2 gnome-shell[8649]: #0 55d65d08f130 i file:///home/ufk/.local/share/gnome-shell/extensions/pano@elhan.io/extension.js:697 (21fdc42b1600 @ 75)
Nov 20 02:52:35 tux-2 gnome-shell[8649]: #1 55d65d08f0a0 i file:///home/ufk/.local/share/gnome-shell/extensions/pano@elhan.io/extension.js:703 (21fdc42b1650 @ 20)
Nov 20 02:52:35 tux-2 gnome-shell[8649]: #2 55d65d08f010 i file:///home/ufk/.local/share/gnome-shell/extensions/pano@elhan.io/extension.js:3311 (21fdc42b5d30 @ 46)
Nov 20 02:52:35 tux-2 gnome-shell[8649]: #3 55d65d08ef68 i file:///home/ufk/.local/share/gnome-shell/extensions/pano@elhan.io/extension.js:3240 (21fdc42b5970 @ 49)
Nov 20 02:52:35 tux-2 gnome-shell[8649]: #4 7ffdac52ba30 b resource:///org/gnome/shell/ui/extensionSystem.js:252 (20674e1dab0 @ 438)
Nov 20 02:52:35 tux-2 gnome-shell[8649]: #5 7ffdac52bad0 b self-hosted:852 (12f2dc09dc90 @ 15)
Nov 20 02:52:35 tux-2 gnome-shell[8649]: #6 55d65d08eed8 i resource:///org/gnome/shell/ui/init.js:21 (82a6c370ba0 @ 48)
Nov 20 02:52:38 tux-2 gnome-shell[10751]: Running GNOME Shell (using mutter 45.1) as a X11 window and compositing manager
I use Gentoo Linux ~amd64 on Wayland Mutter and gnome-shell 45.1
The text was updated successfully, but these errors were encountered:
so after the update of the extension to the new gnome, it crashes gnome right away:
I use Gentoo Linux ~amd64 on Wayland Mutter and gnome-shell 45.1
The text was updated successfully, but these errors were encountered: