If something in ~/.config crashes the session, an efficient way to proceed is
to rename ~/.config:
$ mv ~/.config ~/config.bak
If, really, it is something in ~/.config that crashes the session, then you
should be able to get a graphical desktop (type Alt+F7 to get back to the
graphical session and log in).
All the applications that depend on things in ~/.config will be back to their
default configuration. However you can then copy files from ~/config.bak
back to ~/.config to get your configuration back. You can copy half of those
files, log out, log in, and see if you can still get your desktop. If so,
copy half of the remaining half and so on. If you cannot get your desktop
then the problem is in the last batch of files you copied back to ~/.config:
you can remove half of that batch (from a text session) and see if you can
your desktop back, etc. In the end, you will identify the one file that is
the culprit. All the other files in ~/config.bak can be moved back to
~/.config.
That process takes a number of log in attempts that depend on the base-2
logarithm of the number of files in ~/.config. It is a binary search:
https://en.wikipedia.org/wiki/Binary_search_algorithm
