Window manager collapse?

[Eddie]

> I guess you uses save session before, probably right after your update
> failed (see your issue at foresightlinux.org). So for some reason
> (maybe because you ran out of memory and maybe linux kernel killed
> xfwm4, oom sometimes selects the wrong candidate to kill) xfwm4 wasn't
> running when logging off and thus got removed from your session.
> xfwm4 shouldn't be in autostart. you could either delete your sessions
> when not logged into xfce, or just start xfwm4 and save your session
> on exit.

Hi Mark, just to clarify:

1. The Conary memory error -- the one we are discussing on the Foresight
bug tracker -- happened the day before. The computer was off in between,
and Foresight booted up normally; it was later on, during the session,
that the window manager crashed and wouldn't come back.

2. I didn't save the session after the Conary memory error. I am trying
it now because of what Anzan said in the earlier message, but it was
never on by default, and I never saved any session until last night,
after all this.

Something I was doing may well have killed off xfwm4. That makes sense.
It wasn't Conary (Foresight's package manager, if anybody is wondering).
But then I think I should have had xfwm4 back the next time I started up
Foresight, and I didn't. 

Hope this information helps.