on Tue May 06 2008, Adam Nielsen <a.nielsen-HxjuLhO6/OPR7s880joybQ-AT-public.gmane.org> wrote:
>> When I try to do the kill/re-launch as >> part of my resume script, compiz runs, but with different settings than >> the usual that come from fusion-icon. > > It sounds like it's picking up a different config file for whatever > reason. I agree. > What happens if, once you've done a suspend and reloaded Compiz > with the alternate settings, you change them? Next time you resume, do > you end up with the updated alternate settings? Yep. > 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. -- Dave Abrahams Boost Consulting http://boost-consulting.com _______________________________________________ Dev mailing list [email protected] http://lists.compiz-fusion.org/mailman/listinfo/dev
