Quoting Rodney Brown ([email protected]): > After a reboot, I lost the Window manager, so no frame, title, > minimize, maximize or close buttons. > > Lots of ineffectual thrashing around with a Ctrl-Alt-F1 console > sessions, system-ctrl session manager restarts. > > xfwm4 --replace provided a window manager, but mouse issues left it > uncomfortable. > > It might have been possible to use another console session and lynx > or w3m to google around, but I was glad of another machine to google > with... > > Finally the right search terms found the advice that a damaged, > cached session could cause this. The recommended rm fixed the > problem. > > I don't know whether this is relevant to other session > manager/window manager combinations. > > rm -r ~/.cache/sessions/
X session managers cause a significant number of problems. Have you considered just not running one? The purpose of an X session manager is to keep track of what graphical applications are running and their approximate state, such that if the X session terminates abnormally, upon launching a new X session, the same applications can be launched with the same state. I actually actively do _not_ want that. In particular, if some application is taking my X session down, the last thing I want to have happen automatically at next X startup is for it to be autolaunched again in the same fashion. Also, as you've seen, if the X session manager's own state data gets fried, it can sabotage X. All of those risks are necessary just to perform a function I don't think is desirable. So, for me, it's an obvious choice; Don't run one. No session manager; no session manager problems. _______________________________________________ luv-main mailing list -- [email protected] To unsubscribe send an email to [email protected]
