New subject: [Users] Strange messages at startup for one account

25 Apr 2018

...
  Hi,
 	On one account on my OpenSuSE Leap 42.3 system (the main account, of  course), 
...
  I'm getting these messages after the login screen
and before the desktop 
 appears:

 1)
 > The R14-xdg-update script has been run at least once.
 > The script is not successfully updating.
 > The script will run with each login until corrected.
 > Please contact an administrator or take appropriate administrative action  to

...
   correct the
problem.
 The error code is 9.  
 2)
  Some Trinity profile R14 XDG compliance updates
failed.
 Check applications-tdemenuedit.menu for '<filename>kde-' in
 /var/tmp/kdecache-leslie/r14-xdgupdate-validation-test-9.tct.  
 3)
 > The R14-xdg-update script has been run at least once.
 > The script is not successfully updating.
 > The script will run with each login until corrected.
 > Please contact an administrator or take appropriate administrative action  to

...
   correct the
problem.
 The error code is 9.
 Common failures include file and directory permissions.  
 	(These messages are displayed using xmessage, and can't be copied/pasted 
 since the desktop isn't active, so the above is my hand-copied version,  which

...
  has all the words, but not necessarily on the same
lines.)

 	So I looked into the indicated file, and indeed there are a plethora of  lines 
...
  containing <filename>kde-... (see attached). 
Apparently there are 'file and 
 directory permissions' problems /somewhere./  I have looked at the 
 permissions of all files in ~/.kde and they look okay (but is owner rw- 
 sufficient?)  I looked at the r14-xdg-update script, but the code is opaque 
 (at least to me).  I tried renaming ~/.kde to something else but the problem 
 persists; also tried removing socket-dir and tmp-dir, but that doesn't help 
 either.  The script contains this unhelpful comment:

  # This script should be needed to run only once,
but corner cases
 # and file/directory permissions could cause incomplete updates.
 #
 # TODO: How to handle environments where files/directories are locked
 #       administratively or are owned by root and can't be updated.
 #       The nominal validation checks in this script provide some notice
 #       but no direct remedy.
 #
 # TODO: How to update profile directories not named $HOME/.trinity and   $TDEHOME
  #       is not yet declared when running this
script.  
 	I'm not at all sure where to look and what to look for beyond this.  How  can

...
  I get past this irritating situation?
  Hi Leslie
As root, run r14-xdg-update
When it asks you to continue say yes by pressing Y.

Kate
...

Re: [trinity-users] Strange messages at startup for one account