Running on a Gentoo installation w/GCC 4.1, but otherwise x86 stable, if it makes a difference. I set up the swap writer as described in http://gentoo-wiki.com/HOWTO_Software_Suspend_v2. As the hibernate script runs, XFCE and all gtk components revert to standard GTK styling. When the session is resumed successfully, the default the remains. Styling will (quite slowly) return if I run the Window manager settings control panel. -Sud.
Can't be certain, but here's a random idea. Do you have xfce4-mixer installed, and are you using ALSA? If so, it's possible that hibernate unloads your sound modules (or does something else weird) that kills all apps using sound. I believe xfce4-mixer has a MCS plugin, which kills xfce-mcs-manager. So I guess check after you un-hibernate if xfce-mcs-manager is running, and if not, look for a core file to debug.
It seems that is the case. Running a version of xfce4-mixer without alsa functionality built in (what functionality does it have then ..?) and hibernating doesn't show the same problem. Stoping Alsa services is what is doing it. -Sud.
Not sure if this can be fixed or worked around... I'll reassign to Danny since he's the mixer guy.
Same issue here. Any news?
I also am seeing this bug... but I don't have the mixer loaded at all. I'm using XFCE 4.4.1.
This happens to me too when I stop the alsa initscript; when it unloads the modules, mcs-manager nukes itself and I lose all GTK theming. Re-running mcs-manager or one of the Xfce configuration tools gets it all back. See http://planet.gentoo.org/developers/nightmorph/2008/02/03/thinkpad_configuration_part_2 Any news on this?
I'm sorry to say this, but I do not see how this could possibly be avoided. I mean you could try to enable core files and see whether the xfce4-mixer MCS plugin even gets control before hibernating and maybe just does something that it's not supposed to.
added something to 4.4 branch that maybe helps at least the settings manager not to completely freak out... I have no idea whether it works, can't test it. *** This bug has been marked as a duplicate of bug 3374 ***