search

ewlsh / dynamic-panel-transparency

Adds Transparency To The Gnome Shell Panel
GNU General Public License v2.0
229 stars 30 forks source link

Gnome shell 3.26 crashes on workspace switch #83

Closed jedrzejboczar closed 5 years ago

jedrzejboczar commented 6 years ago

Hi, I'v been getting a strange bug recently, I think it's since Gnome 3.26 but I'm not sure.

My gnome-shell crashes when I switch workspaces quickly. On Wayland it sends me back to login screen, Xorg is softer and it usually gets up after few seconds from the crash. I'v been trying to find a reason for quite a long time and it seems that it crashes only with your extension enabled. It seems like some memory allocations fail, and then the size for another allocation is from some random unallocated memory part. Here I post some system data and logs, hope that it helps.

Extension version: v24 Gnome version: 3.26.1

Extensions from "org.gnome.shell enabled-extensions" (though I would say I haven't installed e.g. maximus or dynamicTopBar, and they won't show in Tweaks):

workspace-grid@mathematical.coffee.gmail.com
System_Monitor@bghome.gmail.com
maximus@mathematical.coffee.gmail.com
battery-power-statistics-shortcut@l300lvl.co.nr
multi-monitors-add-on@spin83
return-to-monitor@aiguofer.github.com
putWindow@clemens.lab21.org
system-monitor@paradoxxx.zero.gmail.com
gnote_integration@awamper.gmail.com
user-theme@gnome-shell-extensions.gcampax.github.com
windowsNavigator@gnome-shell-extensions.gcampax.github.com
remove-activities-button@missoft.fr
activities-config@nls1729
alternate-tab@gnome-shell-extensions.gcampax.github.com
pixel-saver@deadalnix.me
dash-to-dock@micxgx.gmail.com
dynamicTopBar@gnomeshell.feildel.fr
dynamic-panel-transparency@rockon999.github.io

Gnome-shell log (everything since 13:38:00 is the crash):

-- Logs begin at Tue 2017-10-03 16:13:10 CEST, end at Wed 2017-10-18 14:37:09 CEST. --
Oct 18 13:36:59 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:36:59 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:36:59 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:36:59 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:36:59 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:36:59 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:36:59 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:01 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:01 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:01 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:01 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:01 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:01 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:01 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:01 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:01 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:01 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:01 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:01 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:01 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:02 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:04 jjland gnome-shell[5527]: Invalid result meta returned from search provider seahorse.desktop
Oct 18 13:37:04 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:04 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:04 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:04 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:04 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:04 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:05 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:05 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:05 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:05 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:05 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:05 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:05 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:05 jjland gnome-shell[5527]: clutter-actor.c:10050: Actor 'StBin' tried to allocate a size of -9.00 x -1.00
Oct 18 13:37:17 jjland gnome-shell[5527]: [Dynamic Panel Transparency] Using theme data for: Mist
Oct 18 13:38:04 jjland gnome-shell[5527]: ../glib/glib/gmem.c:130: failed to allocate 18446744072098939136 bytes
Oct 18 13:38:06 jjland gnome-shell[9097]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 315]: reference to undefined property "MetaStage"
Oct 18 13:38:06 jjland gnome-shell[9097]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 221]: reference to undefined property "MetaWindowGroup"
Oct 18 13:38:06 jjland gnome-shell[9097]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property "MetaDBusDisplayConfigSkeleton"
Oct 18 13:38:06 jjland gnome-shell[9097]: JS WARNING: [resource:///org/gnome/gjs/modules/tweener/tweener.js 540]: reference to undefined property "isSpecialProperty"
Oct 18 13:38:06 jjland gnome-shell[9097]: Failed to launch ibus-daemon: Failed to execute child process “ibus-daemon” (No such file or directory)
Oct 18 13:38:06 jjland gnome-shell[9097]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property "CallyActor"
Oct 18 13:38:06 jjland gnome-shell[9097]: No permission to trigger offline updates: Polkit.Error: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is not registered
Oct 18 13:38:06 jjland gnome-shell[9097]: Extension "battery-power-statistics-shortcut@l300lvl.co.nr" had error: Error: Strange version number (extension.js:50).
Oct 18 13:38:06 jjland gnome-shell[9097]: Some code accessed the property 'MultiMonitorsDateMenuButton' on the module 'mmcalendar'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:06 jjland gnome-shell[9097]: Enable Multi Monitors Add-On ...
Oct 18 13:38:06 jjland gnome-shell[9097]: Some code accessed the property 'MultiMonitorsLayoutManager' on the module 'mmlayout'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:06 jjland gnome-shell[9097]: Some code accessed the property 'SHOW_PANEL_ID' on the module 'mmlayout'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:06 jjland gnome-shell[9097]: pi:0
Oct 18 13:38:06 jjland gnome-shell[9097]: i:0 x:0 y:0 w:1366 h:768
Oct 18 13:38:06 jjland gnome-shell[9097]: JS WARNING: [resource:///org/gnome/shell/ui/workspacesView.js 527]: reference to undefined property "_restackedNotifyId"
Oct 18 13:38:06 jjland gnome-shell[9097]: Some code accessed the property 'MultiMonitorsWorkspacesDisplay' on the module 'mmoverview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:06 jjland gnome-shell[9097]: Some code accessed the property 'SHOW_APP_MENU_ID' on the module 'mmpanel'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:06 jjland gnome-shell[9097]: Some code accessed the property 'StatusIndicatorsController' on the module 'mmpanel'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:06 jjland gnome-shell[9097]: JS WARNING: [/home/jb/.local/share/gnome-shell/extensions/windowsNavigator@gnome-shell-extensions.gcampax.github.com/extension.js 277]: JavaScript 1.6's for-each-in loops are deprecated; consider using ES6 for-of instead
Oct 18 13:38:07 jjland gnome-shell[9097]: [Dynamic Panel Transparency] Using theme data for: Mist
Oct 18 13:38:08 jjland gnome-shell[9097]: System monitor applet init from /home/jb/.local/share/gnome-shell/extensions/system-monitor@paradoxxx.zero.gmail.com
Oct 18 13:38:08 jjland gnome-shell[9097]: System monitor applet enabling
Oct 18 13:38:08 jjland gnome-shell[9097]: Some code accessed the property 'UPower' on the module 'power'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:08 jjland gnome-shell[9097]: System monitor applet enabling done
Oct 18 13:38:08 jjland gnome-shell[9097]: Some code accessed the property 'KEY_ROWS' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:08 jjland gnome-shell[9097]: Some code accessed the property 'KEY_COLS' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:08 jjland gnome-shell[9097]: Some code accessed the property 'KEY_WRAPAROUND' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:08 jjland gnome-shell[9097]: Some code accessed the property 'KEY_WRAP_TO_SAME' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:08 jjland gnome-shell[9097]: Some code accessed the property 'KEY_MAX_HFRACTION' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:08 jjland gnome-shell[9097]: Some code accessed the property 'KEY_MAX_HFRACTION_COLLAPSE' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:08 jjland gnome-shell[9097]: Some code accessed the property 'KEY_SHOW_WORKSPACE_LABELS' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:08 jjland gnome-shell[9097]: Some code accessed the property 'MAX_THUMBNAIL_SCALE' on the module 'workspaceThumbnail'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:08 jjland gnome-shell[9097]: Some code accessed the property 'ThumbnailState' on the module 'workspaceThumbnail'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:08 jjland gnome-shell[9097]: [pixel-saver]: 'appmenu' is not a valid button.
Oct 18 13:38:08 jjland gnome-shell[9097]: Some code accessed the property 'ICON_FILE' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:08 jjland gnome-shell[9097]: Some code accessed the property 'FIRST_ENABLE' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:08 jjland gnome-shell[9097]: Some code accessed the property 'ORI_TXT' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:08 jjland gnome-shell[9097]: Some code accessed the property 'COLOURS' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:08 jjland gnome-shell[9097]: Some code accessed the property 'TRS_PAN' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:08 jjland gnome-shell[9097]: Some code accessed the property 'BTN_POSITION' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:08 jjland gnome-shell[9097]: loading user theme: /usr/share//themes/Mist/gnome-shell/gnome-shell.css
Oct 18 13:38:08 jjland gnome-shell[9097]: JS WARNING: [/usr/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/utils.js 34]: reference to undefined property Symbol.toPrimitive
Oct 18 13:38:08 jjland gnome-shell[9097]: Extension user-theme@gnome-shell-extensions.gcampax.github.com already installed in /home/jb/.local/share/gnome-shell/extensions/user-theme@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/user-theme@gnome-shell-extensions.gcampax.github.com will not be loaded
Oct 18 13:38:08 jjland gnome-shell[9097]: Extension auto-move-windows@gnome-shell-extensions.gcampax.github.com already installed in /home/jb/.local/share/gnome-shell/extensions/auto-move-windows@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/auto-move-windows@gnome-shell-extensions.gcampax.github.com will not be loaded
Oct 18 13:38:08 jjland gnome-shell[9097]: Extension windowsNavigator@gnome-shell-extensions.gcampax.github.com already installed in /home/jb/.local/share/gnome-shell/extensions/windowsNavigator@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/windowsNavigator@gnome-shell-extensions.gcampax.github.com will not be loaded
Oct 18 13:38:08 jjland gnome-shell[9097]: Extension alternate-tab@gnome-shell-extensions.gcampax.github.com already installed in /home/jb/.local/share/gnome-shell/extensions/alternate-tab@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/alternate-tab@gnome-shell-extensions.gcampax.github.com will not be loaded
Oct 18 13:38:08 jjland gnome-shell[9097]: Extension places-menu@gnome-shell-extensions.gcampax.github.com already installed in /home/jb/.local/share/gnome-shell/extensions/places-menu@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/places-menu@gnome-shell-extensions.gcampax.github.com will not be loaded
Oct 18 13:38:08 jjland gnome-shell[9097]: Extension apps-menu@gnome-shell-extensions.gcampax.github.com already installed in /home/jb/.local/share/gnome-shell/extensions/apps-menu@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/apps-menu@gnome-shell-extensions.gcampax.github.com will not be loaded
Oct 18 13:38:08 jjland gnome-shell[9097]: Failed to load background 'resource:///org/gnome/shell/theme/noise-texture.png': The resource at “/org/gnome/shell/theme/noise-texture.png” does not exist
Oct 18 13:38:09 jjland gnome-shell[9097]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.impl.portal.PermissionStore was not provided by any .service files
Oct 18 13:38:09 jjland gnome-shell[9097]: JS WARNING: [/home/jb/.local/share/gnome-shell/extensions/pixel-saver@deadalnix.me/decoration.js 212]: assignment to undeclared variable success
Oct 18 13:38:09 jjland gnome-shell[9097]: JS WARNING: [/home/jb/.local/share/gnome-shell/extensions/pixel-saver@deadalnix.me/decoration.js 212]: assignment to undeclared variable pid
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'BARRIERS' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'HOTC_PT' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'OVERR_THEME' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'MAX_WIN_EFFECT' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'REMOVED' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'NEW_TXT' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'NEW_ICO' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'NO_HOTC' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'NO_TEXT' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'NO_ICON' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'PAD_TXT' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'PAD_ICO' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'CON_DET' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'HIDE_RC' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'HIDE_APPMBI' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'SHADOW_COLOR' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'SHADOW_TRANS' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'SHADOW_LEN' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'SHADOW_BLUR' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'SHADOW_SPRED' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'SHOW_OVERVIEW' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:09 jjland gnome-shell[9097]: Some code accessed the property 'SHELL_THEME_ID' on the module 'keys'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Oct 18 13:38:10 jjland gnome-shell[9097]: Activities Configurator Enabled
Oct 18 13:38:10 jjland gnome-shell[9097]: GNOME Shell started at Wed Oct 18 2017 13:38:06 GMT+0200 (CEST)

And in the kernel log it throws:

Oct 18 13:38:04 jjland kernel: traps: gnome-shell[5527] trap int3 ip:7f2327544cd2 sp:7ffe36791ab0 error:0

And there is a core dump too, but I think it doesn't say a lot, as I don't have any debug symbols anyway. If you need something more just say.

ewlsh commented 6 years ago

Odd, I will say I also experienced issues with Mutter 3.26.1 crashing whenever certain dialogs opened in Java applications (triggering some sort of window update). Specifically there are bug reports about improper handling of maximized windows causing shell crashes (which in Wayland also leads to a full session crash).

I'm not sure how my extension specifically could be causing this, but I will do more testing. It is possible, however, that as this extension specifically deals with maximized windows it is "triggering" the bugs in Mutter when operating.

This patch/version of mutter fixed my issues with maximization instability: mutter-3.26-fixed while this forum discusses the issue arch forums. There are also reports of newer versions of mutter (released within the past week) fixing numerous maximization/window bugs. If you could supply the full coredump that'd also be useful!

jedrzejboczar commented 6 years ago

Yes, at at the beggining I was trying to find a problem in gnome-shell/mutter, and had even compiled them with debug-symbols, but couldn't find any clue. Then I saw this muter fix but it didn't help (although for a moment I thought it did). I don't know what causes the bug in the first place, but disabling the extension was the only thing that helped, so I've written this issue. Maybe, like you say, the bug is just triggered somehow by dynamic panel transparency.

Anyway here is the corresponding coredump. I will later try to reproduce it with debug symbols if you wish. And will try some different approaches if something comes to my mind. 

           PID: 5527 (gnome-shell)
           UID: 1000 (jb)
           GID: 100 (users)
        Signal: 5 (TRAP)
     Timestamp: Wed 2017-10-18 13:38:04 CEST (5h 39min ago)
  Command Line: /usr/bin/gnome-shell
    Executable: /usr/bin/gnome-shell
 Control Group: /user.slice/user-1000.slice/session-c3.scope
          Unit: session-c3.scope
         Slice: user-1000.slice
       Session: c3
     Owner UID: 1000 (jb)
       Boot ID: b8d72155b5ef43d2ba6c3922bd7595de
    Machine ID: 9fb60ceed3fb4c84bb8373fb25179dda
      Hostname: jjland
       Storage: /var/lib/systemd/coredump/core.gnome-shell.1000.b8d72155b5ef43d2ba6c3922bd7595de.5527.1508326684000000.lz4
       Message: Process 5527 (gnome-shell) of user 1000 dumped core.

                Stack trace of thread 5527:
                #0  0x00007f2327544cd2 n/a (libglib-2.0.so.0)
                #1  0x00007f2327544ecd g_log_default_handler (libglib-2.0.so.0)
                #2  0x000055bc4a9af1b8 n/a (gnome-shell)
                #3  0x00007f23275454ef g_logv (libglib-2.0.so.0)
                #4  0x00007f2327545680 g_log (libglib-2.0.so.0)
                #5  0x00007f232754b093 g_malloc0 (libglib-2.0.so.0)
                #6  0x00007f2325504131 n/a (libst-1.0.so)
                #7  0x00007f2325506324 _st_create_shadow_pipeline (libst-1.0.so)
                #8  0x00007f232550674d _st_create_shadow_pipeline_from_actor (libst-1.0.so)
                #9  0x00007f23255067ae n/a (libst-1.0.so)
                #10 0x00007f232550683f n/a (libst-1.0.so)
                #11 0x00007f2325511298 n/a (libst-1.0.so)
                #12 0x00007f23278222c2 g_signal_emit_valist (libgobject-2.0.so.0)
                #13 0x00007f2327823920 g_signal_emit (libgobject-2.0.so.0)
                #14 0x00007f2325528e8e n/a (libst-1.0.so)
                #15 0x00007f232552912b st_widget_style_changed (libst-1.0.so)
                #16 0x00007f232552a16b n/a (libst-1.0.so)
                #17 0x00007f23278222c2 g_signal_emit_valist (libgobject-2.0.so.0)
                #18 0x00007f2327823920 g_signal_emit (libgobject-2.0.so.0)
                #19 0x00007f2325528e8e n/a (libst-1.0.so)
                #20 0x00007f232552912b st_widget_style_changed (libst-1.0.so)
                #21 0x00007f232552a16b n/a (libst-1.0.so)
                #22 0x00007f23278222c2 g_signal_emit_valist (libgobject-2.0.so.0)
                #23 0x00007f2327823920 g_signal_emit (libgobject-2.0.so.0)
                #24 0x00007f2325528e8e n/a (libst-1.0.so)
                #25 0x00007f232552912b st_widget_style_changed (libst-1.0.so)
                #26 0x00007f232552a16b n/a (libst-1.0.so)
                #27 0x00007f232780a602 g_closure_invoke (libgobject-2.0.so.0)
                #28 0x00007f232781dae2 n/a (libgobject-2.0.so.0)
                #29 0x00007f2327822696 g_signal_emit_valist (libgobject-2.0.so.0)
                #30 0x00007f2327823920 g_signal_emit (libgobject-2.0.so.0)
                #31 0x00007f2325528e8e n/a (libst-1.0.so)
                #32 0x00007f232552912b st_widget_style_changed (libst-1.0.so)
                #33 0x00007f232552a16b n/a (libst-1.0.so)
                #34 0x00007f232780a6f5 g_closure_invoke (libgobject-2.0.so.0)
                #35 0x00007f232781dae2 n/a (libgobject-2.0.so.0)
                #36 0x00007f2327822696 g_signal_emit_valist (libgobject-2.0.so.0)
                #37 0x00007f2327823920 g_signal_emit (libgobject-2.0.so.0)
                #38 0x00007f2325528e8e n/a (libst-1.0.so)
                #39 0x00007f232552912b st_widget_style_changed (libst-1.0.so)
                #40 0x00007f23255292e9 st_widget_remove_style_pseudo_class (libst-1.0.so)
                #41 0x00007f23255298e2 n/a (libst-1.0.so)
                #42 0x00007f232780a6f5 g_closure_invoke (libgobject-2.0.so.0)
                #43 0x00007f232781e0b0 n/a (libgobject-2.0.so.0)
                #44 0x00007f2327822696 g_signal_emit_valist (libgobject-2.0.so.0)
                #45 0x00007f2327823920 g_signal_emit (libgobject-2.0.so.0)
                #46 0x00007f2327810bf6 n/a (libgobject-2.0.so.0)
                #47 0x00007f232780c150 n/a (libgobject-2.0.so.0)
                #48 0x00007f232780d9d1 g_object_setv (libgobject-2.0.so.0)
                #49 0x00007f232780dcaf g_object_set_property (libgobject-2.0.so.0)
                #50 0x00007f23264d85e8 n/a (libgjs.so.0)
                #51 0x00007f231faf7cb7 n/a (libmozjs-52.so.0)
                #52 0x00007f231fb0d68b n/a (libmozjs-52.so.0)
                #53 0x00007f231fb1a46e n/a (libmozjs-52.so.0)
                #54 0x00007f231fd27fc1 n/a (libmozjs-52.so.0)
                #55 0x00003f535f661c06 n/a (n/a)
                #56 0x00003f535f8ec2a5 n/a (n/a)
                #57 0x000055bc516f54c8 n/a (n/a)
                #58 0x00003f535f8ec2a5 n/a (n/a)
                #59 0x000055bc4def0558 n/a (n/a)
                #60 0x00003f535f8ec2a5 n/a (n/a)
ewlsh commented 6 years ago

I'll test this on 3.26 more tonight and see if I can reproduce.

jedrzejboczar commented 6 years ago

Hi, I stopped using your extension for some time, but few days ago I tried again. The problem was still there, but I've found the option "Remove excess panel styling (Fixes theme incompatibilities.)" and yeah, it fixed them ;) So thanks for your awesome extension and I think that the issue can be closed now.

naav commented 6 years ago

I'm hitting the same bug on Debian Testing, but I'm pretty certain it's related to GNOME Shell itself, not this extension. It's only a symptom, not the cause :)

It happens only when switching to a new workspace, but not systematically. It makes the entire GNOME session die.

Nov 14 15:04:44 dimsum gnome-shell[6562]: _cogl_buffer_fini: assertion '!(buffer->flags & COGL_BUFFER_FLAG_MAPPED)' failed
Nov 14 15:04:44 dimsum gnome-shell[6562]: ../../../../glib/gmem.c:130: failed to allocate 18446744072098939136 bytes
Nov 14 15:04:44 dimsum kernel: traps: gnome-shell[6562] trap int3 ip:7f5e0284b911 sp:7ffcbaa60b10 error:0 in libglib-2.0.so.0.5400.1[7f5e027fb000+111000]

(Followed by pretty much everything GNOME-related dying and systemd terminating the session.)

ismay7 commented 6 years ago

This is still happening to me as of today (March 4, 2018). Oddly enough, it seems to be related to the "Enable icon shadowing" toggle. If enabled, switching to a different application on a different workspace by clicking the icon in the panel (dash to panel) or via normal alt+tab, crashes the whole gnome-session (logging out or restarting x). I have only tested this on xorg.

Gnome version: 3.26.2 Extension version: v26

charlesg99 commented 6 years ago

Hey @ismay7, you might be interested by this issue jderose9/dash-to-panel#352. Thanks

ewlsh commented 6 years ago

@charlesg99 @ismay7 I've gotten another report of issues in #88. Unfortunately, I don't have time to fix this right now (It'll be at least a few days before I have the free time...) but I'll give you my initial impressions. Based on what I'm seeing from bug reports and my own system I think this is related to an issue in GJS. 3.26 upgraded GJS from the 38 series to I believe the 52 series. Before this upgrade I can't reproduce the crashes and as the crashes are directly related to the retrieval of certain objects in Gnome Shell I'm guessing this instability results from a bug in GJS. At the very least, we've all implemented transparency in an incorrect way and for some reason 3.26.x is allowed the entire shell to crash as a result. Oh Javascript.

ewlsh commented 6 years ago

Generally it appears there are plenty of issues with the theming APIs under 3.26.x causing the shell to crash where it didn't before.

nnleaf commented 6 years ago

Hi, I'm running Gnome 3.28 with Dash-to-Panel v13 and Dynamic Panel Transparency v25.

It's been a problem for months, as long as I can remember when I started using Dash to Panel in combination with Dynamic Panel Transparency that if I switch workspaces quickly, it'll crash. Turning Dynamic Panel Transparency off has been the only solution to avoid crashes so far. I have tried various settings configs, with nothing working.

If there are any logs or information I can provide to help, I'll gladly do so. Wish it'd work without crashes, I love transparency! :)

Saren-Arterius commented 6 years ago

Hi, I do maintain a patched mutter package on AUR. I have not experienced any crashes for a whole month using mutter 3.28.1 with vanvugt/fix-clock-smoothness-v3, vanvugt/crtc-holds-reference and the mutter-781835-workaround patch. I am now using mutter 3.28.2 with only mutter-781835-workaround patch to test.

This issue may not related to mutter at all, but I have not experienced the crashes since some point of time. I was getting 3-10 crashes per day back then.

Saren-Arterius commented 6 years ago

Not a single crash since 3.28.2.

ewlsh commented 6 years ago

Yes, I've been testing on 3.28.2 and I also appear to have issues fixed. This is good, because I've been struggling to find the issue on earlier platforms. I'll release an update for 3.28 shortly.