Multiple xdg-script FAILURE dialogs displayed on login (permission or path failure)

All, After rebuilding tdebase, I experienced a set of 'X-dialog' (not k-dialog) errors related to xdg-update-script failures on login. The x-dialog warned that this script would continue to run on each login -- not good. The error said there were permission or path failures involved. There was also a file placed in ~/.trinity named: r14-xdg-update-validation-test9.txt containing: <Filename>kde-kcpuload.desktop</Filename> <Filename>kde-knutclient.desktop</Filename> <Filename>kde-kcpuload.desktop</Filename> <Filename>kde-knutclient.desktop</Filename> <Filename>kde-k3bsetup2.desktop</Filename> <Filename>kde-k3bsetup2.desktop</Filename> <Filename>kde-kcpuload.desktop</Filename> <Filename>kde-knutclient.desktop</Filename> <Filename>kde-k3bsetup2.desktop</Filename> <Filename>kde-konqfilemgr.desktop</Filename> The failure warning about path and permission problems must have occurred before .xsession-error activation. Looking at the .xsession-error, here were some new messages that stood out: [r14-xdg-update] Performing a profile update for Trinity release R14 XDG compliance. [r14-xdg-update] [r14-xdg-update] To run this script against a different user directory, or automated [r14-xdg-update] from within another script, pass the directory path as a parameter. [r14-xdg-update] For example: r14-xdg-update /home/user_dir [r14-xdg-update] Use the user home directory and not the profile directory. [r14-xdg-update] User directory: /home/david [r14-xdg-update] Profile directory: /home/david/.trinity [r14-xdg-update] [r14-xdg-update] Renaming some configuration files and directories. [r14-xdg-update] dockdevtocpluginrc->doctdevtocpluginrc [r14-xdg-update] kdevgrepviewrc->tdevgrepviewrc [r14-xdg-update] kdevsnippetrc->tdevsnippetrc [r14-xdg-update] kdevfileselectorrc->tdevfileselectorrc [r14-xdg-update] kdevdesignerrc->tdevdesignerrc [r14-xdg-update] kdevdocumentation->tdevdocumentation [r14-xdg-update] kdevfileselector->tdevfileselector [r14-xdg-update] kdevabbrev->tdevabbrev WHY WAS RENAMING CONFIG FILES NECESSARY -- NONE OF THESE FILES CONFLICT WITH ANYTHING AT ALL?? Was the approach just a massive sed -e 's/k/tde/g' kdevelop/* and then patching whatever got caught up in the mix? That just seems like a bad idea... Additional messages were: [tdeinit] Got SETENV 'SESSION_MANAGER=local/valhalla:@/tmp/.ICE-unix/635,unix/valhalla:/tmp/.ICE-unix/635,inet6/valhalla:57874,inet/valhalla:36274' from tdelauncher. [tdeinit] Got SETENV 'XCURSOR_THEME=default' from tdelauncher. [tdeinit] Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/david/.gtkrc:/home/david/.trinity/share/config/gtkrc' from tdelauncher. [tdeinit] Got SETENV 'GTK2_RC_FILES=/home/david/.gtkrc-2.0-kde-kde4:/home/david/.trinity/share/config/gtkrc-2.0' from tdelauncher. Huh? Why is anything trying to set a directory on my system with "kde4" in its name?? If we are renaming things to make tde its own, then that is certainly the type of thing that would be OK to rename... -- David C. Rankin, J.D.,P.E.