Corrupted Home folder link ?

From time to time I experience this strange behaviour: I have a (Nautilus) home folder on my Desktop that I can open with a double click or from the context list. Now, all of a sudden (after taking a Software update with Yast, for example?), opening the home folder is not opened, but instead the Kaffeine application is started :open_mouth: . What is going on here? How can I correct this?

Precisely this behaviour has propped up from time to time during the various lifetimes of Leap. ‘Show in Files’ works normally and access to the file system is otherwise possible via the Nautilus Files icon, but obviously the strange behaviour isn’t right.
Somehow the Home folder link on the Desktop has become corrupted.

My versions:
Linux 5.3.18-lp152.69-default x86_64
Gnome Version 3.34.7

Unfortunately, there doesn’t seem to be anything relevant in the openSUSE GNOME User Guide – <https://doc.opensuse.org/documentation/leap/gnomeuser/html/book-gnomeuser/index.html&gt; – but –

GNOME uses the user’s ‘~/.cache/’ directory for some things – cleaning out the user’s Cache directory and then logging out and back in again may also alleviate this issue.

The phenomenon has appeared again under Leap 15.3/Gnome 3.34.7. I.e. Opening the ‘home’ folder from Gnome Desktop starts Kaffeine !
What do you mean by cleaning out the /.cache/ directory for some things? What things, for example? My /.cache/ folder contains some 41 items.

Cache is cache is cache – as the name says …

  • Log out from your graphical session.
  • Log in to a VT session – tty1 … tty6 – <Ctrl-Alt-F1> … <Ctrl-Alt-F6>.
  • Remove everything in the ‘~/.cache/’ directory.
    *=2]Possibly leave the ‘~/.cache/mozilla/’ contents intact – Mozilla tends to behave correctly with respect to the contents of cache.
  • Log out.
  • Move back over to the login for your graphical sessions – usually on tty7 – either <Ctrl-Alt-F7> or, <Alt-Left> / <Alt-Right> until you land on graphical login running on tty7.

Interesting…simply opening a VT with <Ctrl-Alt-F1> and closing it again appears to have had the required effect. But I can’t say for sure, since I had not checked immediately prior to that whether the effect was still evident. Thanks anyway. I will try it more systematically should the phenomenon appear again.