>> If so then it looks like the first time Compiz runs (at boot) it's >> being told to look elsewhere for its config files, and this custom >> location isn't being specified when you reload it. > > Maybe, but I still don't understand how that could happen. > > The command initially used to start fusion-icon is invoked as a gnome > session startup program, as simply "fusion-icon." However, the resume script > looks in the process list to decide how to re-invoke it and does: > > sudo -b -H -u dave XAUTHORITY=/home/dave/.Xauthority DISPLAY=:0.0 > /usr/bin/python /usr/bin/fusion-icon > > It doesn't look like any custom locations are being specified, ever.
I don't know what that "fusion-icon" script does (it doesn't exist on my system), so I'd look there for starters. What happens if you run ps aux | grep compiz before and after a resume? What command line options are supplied to the actual compiz binary? Is it running as the same user both times? Maybe something like locate Default.ini | grep compizconfig Will reveal whether there are multiple config files on your system? Cheers, Adam. _______________________________________________ Dev mailing list [email protected] http://lists.compiz-fusion.org/mailman/listinfo/dev
