Created attachment 1714654 [details] dragging firefox from dock to workspaces Description of problem: Workspaces do not pop out when dragging a new app to a workspace from dash in Activities view. Also, once you have dragged an app out to the last workspace, subsequent repeats of this action put the app on the last workspace, not a new one. This is from "QA:Testcase Gnome Shell Activities" test day, test 6: "Drag the icon for a non-running application from the Dash or Applications menu to the last (empty) workspace in the right bar." Version-Release number of selected component (if applicable): gnome-shell-3.37.91-2 How reproducible: Always Steps to Reproduce: 1. Close all apps 2. Open activities (<Super>) 3. Click and drag an app from dock to a workspace on the right Actual results: Workspaces do not pop out and so placement of app is not possible, although you can let it go onto the default workspace (see attachment firefox-drag.jpg) Expected results: Workspaces should pop out from the right and you can choose which workspace to place the app on (i.e. default or create a new one). Additional info: Once you have dragged one app as above, workspace pop out works, but tertiary workspaces for new apps are not created when dragged onto last empty workspace. Steps to Reproduce: 1. Add an app to a workspace (as above) 2. Load activities (<Super>) 3. Click and drag a new app from dock to a new workspace (last empty workspace) 4. Let go of mouse 5. Note new workspace is created and app is loaded there 6. Click and drag a second new app from dock to another new workspace (last empty workspace) (see attachment workspaces-drag.jpg) 7. Let go of mouse Actual results: Second new app loads into previously created workspace, not into a new workspace (see attachment workspaces-drag-result.jpg). Expected results: New workspaces are created and freshly opened app is loaded there.
Created attachment 1714655 [details] dragging photos to a new workspace
Created attachment 1714656 [details] dragging photos to a new workspace result
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.