GNOME Bugzilla – Bug 772854
Windows opened by drag and drop to another workspace opens in current workspace
Last modified: 2021-07-05 14:42:59 UTC
On Fedora 25 I'm using drag&droping for opening windows in different workspaces. With 3.21 and 3.22 it seems to broken for every application (tested rhythmbox, terminal, firefox, evolution, nautilus and few others). Whenever I try to drag&drop application from left bar to another workspace it opens on current one. Downstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=1384440
Happens on stock Arch Linux as well using 3.22.1.
Can confirm (Arch Linux 3.22.2)
I always had this issue, already on 3.2 or something. When dropping a starter onto the empty workspace, a new workspace is created, then the target workspace is deleted, and then the window opens on my current workspace.
This is still an issue (Gnome 3.30.1 on Arch Linux 4.14.76 - Wayland). Expected behavior: "You can launch an application in a separate workspace by dragging its icon from the dash, and dropping it onto one of the workspaces on the right-hand side of the screen. The application will open in the chosen workspace." Actual behavior: A new workspace is created, but it quickly disappears and the application launches on the current workspace.
The reason there has never been any movement on this is that this is likely an app issue. When "opening an app on a new workspace", gnome-shell essentially sets a hint when starting the app, but it's up to apps to respect that.
FWIW, Wayland clients has the same problem, and they don't have a say in where they are started.
I get this in journalctl when I start Gnome Files: org.gnome.Shell.desktop[923]: #0 7ffd17d161a0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:327 (7f51bf6dd820 @ 1578) org.gnome.Shell.desktop[923]: == Stack trace for context 0x55f53da13290 == org.gnome.Shell.desktop[923]: #6 55f53e160540 i resource:///org/gnome/shell/ui/tweener.js:182 (7f51bf6d9700 @ 15) org.gnome.Shell.desktop[923]: #5 55f53e1605c0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (7f51bf6b0b80 @ 71) org.gnome.Shell.desktop[923]: #4 55f53e160668 i resource:///org/gnome/shell/ui/tweener.js:207 (7f51bf6d9790 @ 159) org.gnome.Shell.desktop[923]: #3 55f53e1606f8 i resource:///org/gnome/gjs/modules/signals.js:128 (7f51bf6c18b0 @ 386) org.gnome.Shell.desktop[923]: #2 55f53e1607c8 i resource:///org/gnome/gjs/modules/tweener/tweener.js:370 (7f51bf6dd940 @ 10) org.gnome.Shell.desktop[923]: #1 55f53e160840 i resource:///org/gnome/gjs/modules/tweener/tweener.js:355 (7f51bf6dd8b0 @ 100) org.gnome.Shell.desktop[923]: #0 7ffd17d161a0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:281 (7f51bf6dd820 @ 856) org.gnome.Shell.desktop[923]: == Stack trace for context 0x55f53da13290 == gnome-shell[923]: Object St.Bin (0x55f540051f90), has been already deallocated — 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. org.gnome.Shell.desktop[923]: libinput error: client bug: timer event3 debounce short: offset negative (-0ms) systemd[1]: Started Hostname Service. dbus-daemon[335]: [system] Successfully activated service 'org.freedesktop.hostname1' systemd[1]: Starting Hostname Service... dbus-daemon[335]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.560' (uid=1000 pid=4754 comm="/usr/bin/nautilus --gapplication-service ") dbus-daemon[889]: [session uid=1000 pid=889] Successfully activated service 'org.gnome.Nautilus' dbus-daemon[889]: [session uid=1000 pid=889] Activating service name='org.gnome.Nautilus' requested by ':1.12' (uid=1000 pid=923 comm="/usr/bin/gnome-shell ")
(In reply to Jonas Ådahl from comment #6) > FWIW, Wayland clients has the same problem, and they don't have a say in > where they are started. The workspace information is passed via startup notification, which is still very incomplete on wayland.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help.