Created attachment 850904 [details]
system log - core dump messages

This problem can be reproduced on a fresh installed Tumbleweed (snapshot
20210708), with Gnome as the desktop envrionment (gnome-shell version
40.2-1.1). First, enter the desktop. Then, logout and re-login. At this point,
there are some gnome-shell core dump messages appeared in the system log
(obtained using journalctl -xe). For example:

    org.gnome.Shell@wayland.service: Main process exited, code=dumped,
status=11/SEGV

Also some errors connected to the gnome-shell can be found, like:

    JS ERROR: TypeError: adjustment is null                                     
    goToPage@resource:///org/gnome/shell/ui/iconGrid.js:1395:9                  
    goToPage@resource:///org/gnome/shell/ui/appDisplay.js:1119:20               
    _init/<@resource:///org/gnome/shell/ui/appDisplay.js:152:18                 
    _init/<@resource:///org/gnome/shell/ui/iconGrid.js:1175:59                  
    _removePage@resource:///org/gnome/shell/ui/iconGrid.js:472:14               
    _removeItemData@resource:///org/gnome/shell/ui/iconGrid.js:513:18           
   
_addItemToPage/<.destroyId<@resource:///org/gnome/shell/ui/iconGrid.js:560:59   
    _onDestroy@resource:///org/gnome/shell/ui/appDisplay.js:2469:23

The journalctl log is attached.

Please notice:
1. It only reproducible in the re-login, not in the first time that user
entering the desktop after system starting.
2. The problem happened on both Wayland and X backends.
3. This issue does not affect the starting up and the normal operations of the
desktop. It only leaves some core dumped messages in the system log. Maybe that
is why openQA didn't catch it.
4. A file /run/user/1000/gnome-shell-disable-extension is created after
entering the desktop. This file will be there for about one minutes and then
removed. If you logout and re-login during the time of its existence, all the
gnome extensions are disabled automatically.