Description of problem: been working in vscode + phpstorm +chrome+kitty (terminal) in background skype+discord+telegram Version-Release number of selected component: gnome-shell-42.3.1-1.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 3 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell cmdline: /usr/bin/gnome-shell crash_function: meta_bug dso_list: /usr/bin/gnome-shell gnome-shell-42.3.1-1.fc36.x86_64 (Fedora Project) 1657433610 executable: /usr/bin/gnome-shell journald_cursor: s=a9e09189e29f4b928fff4bc926bc073c;i=c40eb;b=0d290b1a3343418983816ffcc87712fb;m=2b100ccec;t=5e44dc1c5c7e5;x=41b7f0a06ad0852e kernel: 5.18.11-200.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 868334
Created attachment 1898415 [details] File: backtrace
Created attachment 1898416 [details] File: core_backtrace
Created attachment 1898417 [details] File: cpuinfo
Created attachment 1898418 [details] File: environ
Created attachment 1898419 [details] File: limits
Created attachment 1898420 [details] File: maps
Created attachment 1898421 [details] File: mountinfo
Created attachment 1898422 [details] File: open_fds
Created attachment 1898423 [details] File: proc_pid_status
Created attachment 1898424 [details] File: var_log_messages
*** Bug 2122309 has been marked as a duplicate of this bug. ***
*** Bug 2135422 has been marked as a duplicate of this bug. ***
*** Bug 2137806 has been marked as a duplicate of this bug. ***
*** Bug 2141146 has been marked as a duplicate of this bug. ***
Similar problem has been detected: 1. Open two applications in different workspaces so the widget at the top of the overview shows the open workspaces. 2. Drag an app (i.e. Gnome's Text Editor) to the space in between the open workspaces and let go so that the app will be created in a new workspace. 3. Watch Gnome Shell freeze up and restart because it seems to try to create the workspace vertically below the current one, rather than in the workspace to the right of the current one. reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell cmdline: /usr/bin/gnome-shell crash_function: meta_bug dso_list: /usr/bin/gnome-shell gnome-shell-42.6-1.fc36.x86_64 (Fedora Project) 1670047470 executable: /usr/bin/gnome-shell journald_cursor: s=09ad0299e84740ec9051db718bfe2d44;i=103665;b=774264957fe74e249c44e3821e2ce74c;m=68c8fce23;t=5ef1f9e16363c;x=e26188aface3fbad kernel: 6.0.10-200.fc36.x86_64 package: gnome-shell-42.6-1.fc36 reason: gnome-shell killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1930320 [details] File: backtrace
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.