Hello @wissamalkahwaji ,
It could be related to Gnome software having to rebuild the cache info after you deleted the contents. This would only apply initially upon the next Gnome Software refreshing data (checking for updates). Can you get to a terminal at the time it happens? ie <ctrl><alt><f2> ?
Unless you mistyped a space between /var/dnf/cache/ and *, the command is no problem, I think it is more or less equivalent to “dnf clean cache”.
That leads to the question: what did you before? Big update?
Have you already tried to boot a previous kenel for the case the latest kernel and your graphic card do not like each other?
For the rest, if the rpm database is intact, all files should be OK thanks dnf reinstall, and you excluded user config problems by creating another user. The gnome error and the “libxcb” in the crash traceback point into the graphics subsystem.
I think “dnf reinstall” has given you a new copy of the cache so this could not lead to a chain of problems within gnome.
According to the log, your running gnome on X11. As workaround, have you already tried gnome/wayland? If you’re running gdm as display manager, there should be a gear where you can switch between gnome/“gnome classic” in Wayland or X11 version.
I recently discovered that you can run “gnome-shell --wayland” in a console. (kill with “killall gnome-shell” from another console).
May be this gives some other info about the problem in the console.
I switched to the KDE framework and the problem was from gnome with an unknown job. I tried many settings and reinstalled them. The problem was the same, so I used KDE and the problem was solved like this.