I am having problems getting adesklets to launch when logged in as a non-root user. I have tried several different adesklets and they all behave the same way. The adesklets *will* launch if logged in as root or a non-root user with a local home directory (eg: /home/user1). However, if the user has their home directory mounted over NFS (eg: /net/server1/home/user1 using amd) the adesklet will not launch. Here's what I get:

Do you want to (r)egister this desklet or to (t)est it?
Now testing...
============================================================
If you do not see anything (or just an initial flicker
in the top left corner of your screen), try `--help',
and see the FAQ: `info adesklets'.
============================================================


And nothing appears on the screen. No flicker in the top left corner or anything. When I press CTRL+C to quit I get the following:

Traceback (most recent call last):
File "./asimpleclock.py", line 52, in ?
import adesklets
File "usr/local/lib/python2.4/site-packages/adesklets/__init__.py", line 38, in ?
File "usr/local/lib/python2.4/site-packages/adesklets/initializer.py", line 92, in __init__
File "usr/local/lib/python2.4/site-packages/adesklets/communicator.py", line 99, in err
KeyboardInterrupt
Exception exceptions.AttributeError: <exceptions.AttributeError instance at 0xb7fd12ec> in <bound method _Communicator.__del__ of <adesklets.communicator._Communicator instance at 0xb7cc4a8c>> ignored


The only other thing I noticed is that a .adesklets file is created in the user's home directory but it is empty. Here's the details on my system:

Fedora Core 4
adesklets 0.4.12
Python 2.4 (latest from Python.org)
Fluxbox 0.9.14-1

Any help would be greatly appreciated. Thanks.

Thanks for the *very* quick response to my first post. I tried running the test script and in both cases the script hangs at "Acquiring lock...". I've run through some NFS docs related to locking but haven't been able to get any different results yet. I'll keep diggin g but any othersuggetions would be welcome! Thanks again.

The fact that the first instance of the script hangs indefinitely over NFS without ever acquiring the lock does mean this is indeed a locking problem; just make sure this is only happening over NFS, not system-wide, so you do not lose time over a slightly off-track diagnostic.

The good news is that once the script will work, you have every chance adesklets will work too.

No working locks over NFS is a very usual problem -- you should not have too much difficulties finding appropriate help online; I can only give you the few usual tips:

• 
  
• Know with precision what implementation of NFS is running at both end of the pipe (server and client). A classic joke is spending a whole day trying to fix a very specific incompatibility between server x and client y, when searching for it online give you a usable fix in minutes.
  
• Most common issue is with people (both sysadmin or end-user) just forgetting to start the port mapper, or the separate lock daemon, or both... Check everything is running at both ends.
  

I am sorry I cannot help you much further for now... This is beyond my control. :(

[EDIT]
Glad you sorted it out.