Re: Failed to contact configuration server



Hi,

The problem is that "cron" does not run stuff inside your login
session, so your script can't notify nautilus that configuration has
changed from "cron"

The most obvious solution is to just write a program to run inside
your login session. A quite simple pygtk app could do this, for
example. It would start up, add a timeout every however often, enter
main loop; in the timeout just make a couple of gconf API calls.
Probably a 100-line python script or less. Then drop that (well, a
.desktop file pointing to it) in the autostart folder.

Havoc


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]