Additional details for todays hickup:


% rpm -q --scripts autofs
postinstall scriptlet (using /bin/sh):

if [ $1 -eq 1 ] ; then 
        # Initial installation 
        /usr/bin/systemctl preset autofs.service >/dev/null 2>&1 || : 
fi
preuninstall scriptlet (using /bin/sh):

if [ $1 -eq 0 ] ; then 
        # Package removal, not upgrade 
        /usr/bin/systemctl --no-reload disable autofs.service > /dev/null 2>&1 || : 
        /usr/bin/systemctl stop autofs.service > /dev/null 2>&1 || : 
fi
postuninstall scriptlet (using /bin/sh):

/usr/bin/systemctl daemon-reload >/dev/null 2>&1 || : 
if [ $1 -ge 1 ] ; then 
        # Package upgrade, not uninstall 
        /usr/bin/systemctl try-restart autofs.service >/dev/null 2>&1 || : 
fi

The point of this exercize is to see if putting ~/.kde symlinks elsewhere is

1.  easy without too much fuss
2.  if put on local disk, see if this makes kde less error-prone to $HOME-on-nfs hiccups

Why there has to be duct-tape (symlinks) in the first place? Put that socket directly there.

Per IRC discussion recently...

Turns out patching this will be non-trivial.  But, here's a better/easier/safer test.  Per
http://techbase.kde.org/KDE_System_Administration/KDE_Filesystem_Hierarchy#KDEHOME


# some local (ie, non NFS) dir to use temporarily as a test:
mkdir -p /usr/local/tmp/${USER}

cp -a ~/.kde/ /usr/local/tmp/${USER}/


# create a snippet ~/.kde/env/KDEHOME.sh containing:
KDEHOME=/usr/local/tmp/${USER}/.kde
export KDEHOME


restart kde session.


If doing this fixes the symptoms described here, we have ample evidence to pursue this more.

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

I consider comment #4 probably good enough for sites with less than fully-functional (e.g. broken locking) nfs implementations

Re-open if that doesnt work.

File locks work on NFS. This case was opened to questionize using duct-tape as construction material. That was mentioned in comment #3.

There is no need to proof that it's wrong. Everyone knows it already.

so, can you please test if setting KDEHOME to point to local storage does make things better, per comment #3 request for feedback?

Closing (again), feel free to reopen and provide the requested testing/feedback if able, thanks.

(In reply to Rex Dieter from comment #8)
> so, can you please test if setting KDEHOME to point to local storage does
> make things better, per comment #3 request for feedback?

I guess nick tibbs confirmed, that it does.

Related information: http://fedoraproject.org/wiki/KDE/NFS