I've upgraded to Xfce 4.6 (from Xfce's site, not XUbuntu) and removed the Xfce 4.4 packages. I am using Xfce's power manager instead of Gnome Power Manager, since it now supports suspending and hibernating when laptop lid is closed, etc.
Whenever I log in, Gnome Power Manager (GPM) is started along side Xfce Power Manager, and I have to manually kill it.
I've checked, and there are no saved sessions in .cache/sessions.
It's not enabled in Xfce's Autostarted Applications (now in the Session Management Applet).
Odd thing is that there is an unchecked reference to it in Autostarted Applications that I am unable to remove. If I manually go to .config/autostart and remove the file gnome-power-manager.desktop (which just says "Hidden=True" and nothing else), then the file is re-added, and is enabled in Autostarted Applications.
So something is adding GPM and enabling it. The question is: what?
What Linux you're using?
It might be an daemon?
I'm using Ubuntu Intrepid. I've updated the original post with more information.
In Ubuntu the start scripts lie in /etc/init.d. The programs that are started in every single runtime is set in /etc/rc0.d to /etc/rc6.d, /etc/rcS.d.
Normally the X Server uses runlevel 5, so take a look in /etc/rc5.d:
Is there something like gpm?
If not, check the other folders too.
If you found it, try to verify that it has really to do with Gnome's Power Manager, by looking inside... And if you're sure, remove it.
Removing files in /etc/ will require root permissions.
I've found a line in /etc/acpi/powerbtn.sh that checks in gnome-power-manager and klaptopdaemon are running, but I' not using the power button. (I have added a check for xfce4-power-manager though, just in case.)
Ah, I found /etc/xdg/autostart/gnome-power-manager, and I've removed it.
That didn't work. It still comes up in login.
I did a grep -R gnome-power-manager in /etc, ~/.conf, ~/.gconf, ~/.gconfd, ~/.cache and there's nothing that comes up (beyond a pidof check to see if it's running).
Any ideas what could be launching it then?
However, it doesn't keep getting added to Autostarted Apps, so the problem is partially solved.
It's probably started by DBUS.
If temporarily removing /usr/share/dbus-1/services/gnome-power-manager.service helps, dig there.
Otherwise, hal, udev and gdm may be responsible.
That seems to have fixed it!