On Fri, 24 Jul 2009, Christopher Roy Bratusek wrote: > On Fri, 24 Jul 2009 23:00:29 +0200 > Christopher Roy Bratusek <[email protected]> wrote: > > > On Fri, 24 Jul 2009 16:42:32 -0400 (EDT) > > Allin Cottrell <[email protected]> wrote: > > > > > Hello all, > > > > > > I've been a big fan of sawfish for several years. Thanks very > > > much to the developers. > > > > > > Today I tried updating from rep-gtk 0.18 and sawfish 1.3.5.1 to > > > rep-gtk 0.18.6r2 and sawfish 1.5.0. Everything built OK but > > > when I restarted X sawfish wasn't there and my X error log > > > contained a complaint about gnome-panel: > > > > > > (gnome-panel:PID) Wnck-CRITICAL **: wnck_workspace_get_number: > > > assertion `WNCK_IS_WORKSPACE (space)' failed > > > > > > I was able to restart sawfish manually, but the desktop was messed > > > up, with icons overlapping panels. I tried deleting my old > > > ~/.sawfish/custom just in case there was anything incompatible in > > > there and started X again. No dice, same problem. > > > > > > I then tried reverting sawfish to 1.3.5.1. Again the broken > > > start-up. Finally I reverted rep-gtk to 0.18 and everything works > > > again. But I'd like to retry the update if I can figure out > > > what's going wrong. > > > > > > I should perhaps mention that my gnome version is rather old: the > > > panel is gnome-panel-2.2.2.2. That's because I feel that recent > > > gnome has been too "dumbed down" -- there are things I can do with > > > the old gnome and that can't with recent releases. But my gtk > > > installation is current, version 2.16.5. > > > > > > > Boah. I would like to help you, but it's rather hard to get your > > setup ... did you also update librep? you should, as sawfish 1.5 > > requires a pretty new one, but you did not mention it. > > > > ... workspace-code did not change for a very long time, I'm pretty > > sure it's GNOME causing the issue, as sawfish works well, standalone, > > with recent GNOME, KDE3 and KDE4. > > > > Chris > > Additionally: > > does your sawfishrc contain (require 'sawmill-defaults)? > if so replace it by (require 'sawfish-defaults) > > try adding (require 'sawfish.wm.gnome.integration)
I've now tried that and it makes no difference. I have narrowed down the backward incompatibility between sawfish and relatively old gnome. The new rep packages (librep-0.90.0 and rep-gtk-0.18.6r2) are not a problem. I have these installed -- though I did not delete the gnome-*.so and libglade.so produced by rep-gtk-0.18.3 nd previously installed in /usr/libexec/rep/i686-pc-linux-gnu/gui/gtk-2 (The gtk.so and types.so in that directory are now the ones installed by rep-0.18.6r2.) The problem lies with session management. >From running sawfish 1.3.5.1 I have a session file in ~/.sawfish/sessions, and sawfish is referenced in the file ~/.gnome2/session. Fine. If I stop X, install sawfish 1.5.0, and restart X (leaving the above mentioned session-related files unchanged) I get an OK desktop (sawfish starts and desktop icons are placed correctly). But the desktop takes several seconds to appear (as opposed to a pretty much instantaneous startup with sawfish 1.3.5.1). Now -- with sawfish 1.5.0 running -- I exit gnome and choose to save the current session on exit. Then (no X running, at the console) I see that there is no longer any file in ~/.sawfish/sessions, and the file ~/.gnome2/session contains no mention of sawfish. Not surprisingly, then, when I restart X/gnome, I have no window manager and everything is screwed up. Allin Cottrell
