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
I've experienced this issue multiple times when accidentally moving either the vesktop (discord) or zoom startup windows using the move gesture. I'm assuming that the move gesture doesn't account for the current window exiting.
Journalctl -r output when moving vesktop is listed below:
Apr 08 22:47:22 fedora kernel: gnome-shell[55741]: segfault at 18 ip 00007ff8302fe6e2 sp 00007ffd7bf10b40 error 4 in libmutter-13.so.0.0.0[7ff830252000+16f000] likely on CPU 10 (core 5, socket 0)
Apr 08 22:47:22 fedora gnome-shell[55741]: Trying to activate unmanaged window 'W5'
Apr 08 22:47:20 fedora dev.vencord.Vesktop.desktop[59591]: [3:0408/224720.681033:ERROR:browser_main_loop.cc(278)] Gtk: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
Apr 08 22:47:20 fedora dev.vencord.Vesktop.desktop[59591]: [arRPC > process] started
Apr 08 22:47:20 fedora dev.vencord.Vesktop.desktop[59591]: [arRPC > websocket] listening on 6463
Apr 08 22:47:20 fedora dev.vencord.Vesktop.desktop[59591]: [arRPC > ipc] listening at /run/user/1000/discord-ipc-0
Apr 08 22:47:20 fedora dev.vencord.Vesktop.desktop[59591]: [3:0408/224720.426742:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Apr 08 22:47:20 fedora dev.vencord.Vesktop.desktop[59591]: [3:0408/224720.426638:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Apr 08 22:47:20 fedora dev.vencord.Vesktop.desktop[59591]: [3:0408/224720.075112:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Apr 08 22:47:20 fedora systemd[2456]: Started app-flatpak-dev.vencord.Vesktop-59609.scope.
Apr 08 22:47:19 fedora systemd[2456]: Started flatpak-portal.service - flatpak portal.
Apr 08 22:47:19 fedora systemd[2456]: Starting flatpak-portal.service - flatpak portal...
Apr 08 22:47:19 fedora dev.vencord.Vesktop.desktop[59590]: Passing the following arguments to Electron: --ozone-platform-hint=auto
Apr 08 22:47:19 fedora systemd[2456]: Started app-flatpak-dev.vencord.Vesktop-59574.scope.
Apr 08 22:47:19 fedora systemd[2456]: Started app-gnome-dev.vencord.Vesktop-59574.scope - Application launched by gnome-shell.
Problem Reporting also reported this for zoom (exported from distrobox):
Apr 08 22:44:06 fedora gnome-shell[51104]: clutter_actor_add_child: assertion 'child->priv->parent == NULL' failed
Apr 08 22:44:06 fedora gnome-shell[51104]: clutter_actor_insert_child_below: assertion 'child->priv->parent == NULL' failed
Apr 08 22:44:07 fedora gnome-shell[51104]: Attempting to add actor of type 'StLabel' to a container of type 'StBoxLayout', but the actor has already a parent of type 'StBoxLayout'.
Apr 08 22:44:07 fedora gnome-shell[51104]: Attempting to add actor of type 'StLabel' to a container of type 'StBoxLayout', but the actor has already a parent of type 'StBoxLayout'.
Apr 08 22:44:07 fedora gnome-shell[51104]: Object St.BoxLayout (0x55c7c157f780), 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 0x55c7bf6239b0 ==
...
Edit: it also occurs when pressing alt + f4 while performing the move gesture on the current window. The move gesture not accounting for the focused window closing is definitely the root of the cause.
The text was updated successfully, but these errors were encountered:
I've experienced this issue multiple times when accidentally moving either the vesktop (discord) or zoom startup windows using the move gesture. I'm assuming that the move gesture doesn't account for the current window exiting.
Journalctl -r output when moving vesktop is listed below:
Problem Reporting also reported this for zoom (exported from distrobox):
Edit: it also occurs when pressing alt + f4 while performing the move gesture on the current window. The move gesture not accounting for the focused window closing is definitely the root of the cause.
The text was updated successfully, but these errors were encountered: