Comment 19 for bug 911507

Ivo Wever (ivo-wever) wrote :

Here's a way to find the offending file:

find ~ -max-depth $N -inum $INUM

where $INUM is the inode number reported in the error message and $N is the depth you want to search. I started searching without depth, but nothing was found after searching for several minutes. When I searched with depth 2, then 3, two Skype config files turned up immediately. Later some chromium config file was the wrongdoer. Replace ~ by / if everything is encrypted and not just your home directory. Adjust as needed.