Comment 2 for bug 453115

Under lucid, when I try to choose sawfish via the login screen, it seems that sawfish is indeed started. But none of the other GNOME stuff (panels, nautilus, etc) gets started. So the screen is pretty much blank, which can be confusing.

I would like to use sawfish as my window manager but have the rest of the gnome session running. This worked under dapper and hardy but I have not yet been able to get it working under lucid.

Strangely, the old trick of "killall -HUP metacity && sleep 5 && sawfish &" worked after my first few logins. But then (after I temporarily installed and enabled compiz) it stopped working because metacity is quickly being respawned (by whom?). So I tried "killall -HUP metacity && sawfish &" (without the sleep) to try to give sawfish a chance to start before metacity respawned. This kindof worked (in the sense that sawfish took over as window manager) but metacity continued rapidly trying to respawn, failing each time because a window manager was already running. The result was that one CPU was 100% busy (top showed most of the CPU being consumed by gconfd-2 and Xorg).

I'd love to get sawfish running for its excellent key- and mouse-binding configurability!