There are those who would have you believe that Colin Watson wrote: > Andy Bastien <[EMAIL PROTECTED]> wrote: > >There are those who would have you believe that Colin Watson wrote: > >> If you upgrade sawfish to the one in unstable at the moment, don't > >> follow the instruction that says: > >> > >> execute 'kill -9 `pidof sawfish`;sawfish&' in a terminal > >> > >> I did so without thinking, and of course lost all my state. I don't see > >> any reason not to use the old 'sawfish-client -f restart', apart from > >> the cosmetic problem of the spurious error message, but no doubt I'll > >> find out as a result of the bug report I've just filed. 'kill -1' might > >> work, but I've no intention of blowing up my X session again just to > >> find out ... > > > >What do you mean when you say you lost all of your state? FWIW, I did > >this on my laptop and didn't have any problems. > > Maybe you're running something like gnome-session as your session > manager (the last thing in your .xsession). If you're like me and don't > use full-blown GNOME, the last thing your .xsession does is often to run > your window manager, and thus being advised to kill it is bad news. > > Looking before I leaped would have helped, I admit :) >
You're right, that's exactly what I do. I just wanted to be sure I understood what you were saying before I do this on any other machines ;-). How about this instead: pidof gnome-session && kill -9 `pidof sawfish`;sawfish&
