All,
I keep getting the same error repeatedly in .xsession.errors file. What is the problem and how do I fix it. Below is the repeated error. I am using Ubuntu Mate 16.04. I believe this has something to do with Caja and deja dup. But I don’'t use deja dup for my backups.
Thanks all in advance.
** (caja:3982): CRITICAL **: caja_menu_provider_get_background_items: assertion ‘CAJA_IS_MENU_PROVIDER (provider)’ failed
Traceback (most recent call last):
File “/usr/share/caja-python/extensions/deja.py”, line 150, in get_file_items
include_paths = self.dejadup.get_dejadup_paths(‘include-list’)
File “/usr/share/caja-python/extensions/deja.py”, line 64, in get_dejadup_paths
paths = ast.literal_eval([stdout][0]) # Convert shell dump to list
File “/usr/lib/python2.7/ast.py”, line 49, in literal_eval
node_or_string = parse(node_or_string, mode=‘eval’)
File “/usr/lib/python2.7/ast.py”, line 37, in parse
return compile(source, filename, mode, PyCF_ONLY_AST)
File “”, line 1
@as []
^
Lots of linux apps that use the same or similar libraries seem to be kind of… vomitous in the error message department, for example if you run one of them in a terminal you get to see a bunch of diagnostic junk that should have been fixed in the code someplace but wasn’t, because somebody had more work than could comfortably be done before the release-date, and removing non-fatal diagnostics got prioritized off the release list.
Personally my practice is to do my work if i can ignore the messages, and look at no more logs than i can avoid. It’s hard to remember sometimes that linux isn’t finished, it’s a continually advancing prototype, just like all software that has not yet been frozen. It has advanced a long way since i started using it a few years back; me likes it a lot.
Nobody reads the .xsession-errors log except you, as far as i know; if it gets too large, i believe it can safely be erased and it’ll come right back. If you rename it then erase it and log out/in you should worstcase be able to rename it back from a rescue boot, i’d think.