shutarg
commented
4 months ago Looks like many things can cause this bug. It happens randomly.
Open icedman opened 5 months ago
shutarg
commented
4 months ago Looks like many things can cause this bug. It happens randomly.
icedman
commented
4 months ago When this happens, please do post the log. It happened on my ubuntu setup. unfortunate i wasn't able to save the errors.
shutarg
commented
4 months ago LookingGlass says there are no errors.
shutarg
commented
4 months ago But i am still having this bug.
shutarg
commented
4 months ago Could it be related to the number of icons pinned on the dock? Looks like when i have more than 30 icons on the dock bug starts happening.
icedman
commented
4 months ago Trace the log at the terminal. Enable/Disable the D2DA extension. And post the result. Like below:
shutarg
commented
4 months ago Icon created: org.gnome.Contacts [org.gnome.Contacts] clutter_text_get_text: assertion 'CLUTTER_IS_TEXT (self)' failed st_widget_get_theme_node called on the widget [0x561026ecc2f0 StLabel.dash-label:insensitive ("(null)")] which is not in the stage. clutter_actor_get_preferred_width: assertion 'CLUTTER_IS_ACTOR (self)' failed clutter_text_get_text: assertion 'CLUTTER_IS_TEXT (self)' failed st_widget_get_theme_node called on the widget [0x561026ecc2f0 StLabel.dash-label:insensitive ("(null)")] which is not in the stage. clutter_actor_get_preferred_height: assertion 'CLUTTER_IS_ACTOR (self)' failed Spurious clutter_actor_allocate called for actor 0x561026ecc2f0/unnamed [StLabel] which isn't a descendent of the stage!
Icon created: org.gnome.Calendar [org.gnome.Calendar] clutter_text_get_text: assertion 'CLUTTER_IS_TEXT (self)' failed st_widget_get_theme_node called on the widget [0x561029739bb0 StLabel.dash-label:insensitive ("(null)")] which is not in the stage. clutter_actor_get_preferred_width: assertion 'CLUTTER_IS_ACTOR (self)' failed clutter_text_get_text: assertion 'CLUTTER_IS_TEXT (self)' failed st_widget_get_theme_node called on the widget [0x561029739bb0 StLabel.dash-label:insensitive ("(null)")] which is not in the stage. clutter_actor_get_preferred_height: assertion 'CLUTTER_IS_ACTOR (self)' failed Spurious clutter_actor_allocate called for actor 0x561029739bb0/unnamed [StLabel] which isn't a descendent of the stage!
Icon created: chrome-mmaaoaoaggpeefmeacdpbedbmkchcfbj-Default [chrome-mmaaoaoaggpeefmeacdpbedbmkchcfbj-Default] Icon created: chrome-mmaaoaoaggpeefmeacdpbedbmkchcfbj-Default [chrome-mmaaoaoaggpeefmeacdpbedbmkchcfbj-Default] clutter_text_get_text: assertion 'CLUTTER_IS_TEXT (self)' failed st_widget_get_theme_node called on the widget [0x5610203d0600 StLabel.dash-label:insensitive ("(null)")] which is not in the stage. clutter_actor_get_preferred_width: assertion 'CLUTTER_IS_ACTOR (self)' failed clutter_text_get_text: assertion 'CLUTTER_IS_TEXT (self)' failed st_widget_get_theme_node called on the widget [0x5610203d0600 StLabel.dash-label:insensitive ("(null)")] which is not in the stage. clutter_actor_get_preferred_height: assertion 'CLUTTER_IS_ACTOR (self)' failed Spurious clutter_actor_allocate called for actor 0x5610203d0600/unnamed [StLabel] which isn't a descendent of the stage!
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed clutter_actor_set_child_at_index: assertion 'child->priv->parent == self' failed clutter_actor_set_child_at_index: assertion 'child->priv->parent == self' failed clutter_actor_set_child_at_index: assertion 'child->priv->parent == self' failed clutter_actor_set_child_at_index: assertion 'child->priv->parent == self' failed clutter_actor_set_child_at_index: assertion 'child->priv->parent == self' failed
shutarg
commented
4 months ago This is the exact moment in the log when the bug happens. I am sure it happens when i have 30 icons or more pinned on the dock.
icedman
commented
4 months ago The bug seems to be related to the icon labels - which is causes a fatal error. I added an option to disable labels. It is on the development branch for now. Please check if this helps - this will confirm that labels causes this elusive bug.
shutarg
commented
4 months ago I have 28 icons(with labels) pinned on the dock and the bug does not happen at all. Runs flawless. Everytime i have more than 30 icons pinned the bug kicks in. I am waiting for the next version release.
shutarg
commented
4 months ago Testing extension with the new files. It seems to run flawless with NO LABELS option. Let me test a little bit more.
shutarg
commented
4 months ago Now dock is freezing with no LABELS. Another bug. It does not happen often but it happens.
shutarg
commented
4 months ago glaubercastro@fedora:~$ journalctl /usr/bin/gnome-shell -f -o cat Received error from D-Bus search provider org.gnome.Boxes.desktop: Gio.IOErrorEnum: Cannot invoke method; proxy is for the well-known name org.gnome.Boxes.SearchProvider without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag Received error from D-Bus search provider org.gnome.Terminal.desktop: Gio.IOErrorEnum: Cannot invoke method; proxy is for the well-known name org.gnome.Terminal without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag Received error from D-Bus search provider org.mozilla.firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable Received error from D-Bus search provider org.gnome.Boxes.desktop: Gio.IOErrorEnum: Cannot invoke method; proxy is for the well-known name org.gnome.Boxes.SearchProvider without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag Received error from D-Bus search provider org.mozilla.firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable Received error from D-Bus search provider org.gnome.Terminal.desktop: Gio.IOErrorEnum: Cannot invoke method; proxy is for the well-known name org.gnome.Terminal without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Ignoring length property that isn't a number at line 1791, col 39 Ignoring length property that isn't a number at line 1791, col 46 Ignoring length property that isn't a number at line 1791, col 51 meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Icon created: io.github.alainm23.planify [io.github.alainm23.planify] separator destroyed meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Object St.Icon (0x55e91c67cde0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c67cde0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c6a1ba0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c6a1ba0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91f1b1380), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91f1b1380), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e918c41dc0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e918c41dc0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91f09c170), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91f09c170), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e9193c2d90), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e9193c2d90), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91ed869f0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91ed869f0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e919a218d0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e919a218d0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91631dba0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91631dba0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e919b71110), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e919b71110), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91837f3b0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91837f3b0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91939dd80), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91939dd80), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e9197a4370), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e9197a4370), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91945f1e0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91945f1e0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91f4130d0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91f4130d0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91bedfd70), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91bedfd70), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91beb39c0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91beb39c0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91f7f3940), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91f7f3940), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e919401910), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e919401910), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e9204b68f0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e9204b68f0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91bf16aa0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91bf16aa0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e921154dc0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e921154dc0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c646c60), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c646c60), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c61f3f0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c61f3f0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e916b1c4c0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e916b1c4c0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e919381410), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e919381410), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91dae00a0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91dae00a0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c53be30), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c53be30), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e9193cea90), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e9193cea90), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91d7758a0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91d7758a0), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91bf16460), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91bf16460), 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c67cde0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c6a1ba0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91f1b1380), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e918c41dc0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91f09c170), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e9193c2d90), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91ed869f0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e919a218d0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91631dba0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e919b71110), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91837f3b0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91939dd80), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e9197a4370), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91945f1e0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91f4130d0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91bedfd70), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91beb39c0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91f7f3940), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e919401910), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e9204b68f0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91bf16aa0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e921154dc0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c646c60), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c61f3f0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e916b1c4c0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e919381410), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91dae00a0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c53be30), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e9193cea90), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91d7758a0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91bf16460), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c67cde0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c67cde0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c67cde0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c67cde0), has been already disposed — impossible to set any property on 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c67cde0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c67cde0), has been already disposed — impossible to set any property on 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c67cde0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c67cde0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c67cde0), has been already disposed — impossible to get any property from 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 0x55e915e19eb0 ==
Object St.Icon (0x55e91c67cde0), 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 0x55e915e19eb0 ==
JS ERROR: TypeError: iconContainer is null animate/<@file:///home/glaubercastro/.local/share/gnome-shell/extensions/dash2dock-lite@icedman.github.com/animator.js:535:13 animate@file:///home/glaubercastro/.local/share/gnome-shell/extensions/dash2dock-lite@icedman.github.com/animator.js:315:18 animate@file:///home/glaubercastro/.local/share/gnome-shell/extensions/dash2dock-lite@icedman.github.com/dock.js:1132:21 _beginAnimation/this._animationSeq<@file:///home/glaubercastro/.local/share/gnome-shell/extensions/dash2dock-lite@icedman.github.com/dock.js:1169:20 onUpdate@file:///home/glaubercastro/.local/share/gnome-shell/extensions/dash2dock-lite@icedman.github.com/timer.js:242:13 onUpdate/<@file:///home/glaubercastro/.local/share/gnome-shell/extensions/dash2dock-lite@icedman.github.com/timer.js:141:11 onUpdate@file:///home/glaubercastro/.local/share/gnome-shell/extensions/dash2dock-lite@icedman.github.com/timer.js:139:23 @resource:///org/gnome/shell/ui/init.js:21:20
shutarg
commented
4 months ago With 29 icons on the dock it runs flawless with NO LABELS or WITH LABELS.
reported manjaro, confirmed ubuntu. possibly due to png icons. may also be related to downloads folder bug.