Sawfish as installed in Fisher complains about lack of XINERAMA support: Xlib: extension "XINERAMA" missing on display ":0.0". I suppose this has to do with XFree86 4.x. sawfish still works fine, but this warning message is (very slightly) annoying and, more importantly, could be an indication of something not being built or installed properly. I don't know.
Unless you have two monitors, then it's normal for your display not to support Xinerama. Sawfish is trying to use the extension without calling XineramaQueryExtension() first to be sure it exists. Not really hurting anything, except that it causes the error spew.
I've forwarded this information to the sawmill mailing list.
Sorry for the wasted bandwidth.... I mean sawfish.com, not sawmill....
I've fixed this problem now
*** Bug 26448 has been marked as a duplicate of this bug. ***
Although this bug has been fixed in the latest sawfish, it still appears in Wolverine. This and other bugs have been corrected in 0.37.3.
Upgrading to a new version at this point in the release cycle would make me quite nervous, unless John says 0.37 is bugfixes only and Preston thinks it's a good idea.
0.36 -> 0.37.3 was mostly bug fixes, but a few minor features also snuck in In case you just want to patch your version to fix the Xinerama problem, the patch is here: http://cvs.gnome.org/bonsai/cvsview2.cgi?diff_mode=context&whitespace_mode=show&file=functions.c&root=/cvs/gnome&subdir=sawfish/src&command=DIFF_FRAMESET&rev1=1.85&rev2=1.86
I'm wondering why this bug has not gotten any attention for a long time. It's the only bug I reported against Fisher or Wolverine that hasn't been long-since resolved. Maybe it's because I marked at as low priority? Anyway, since John provided a simple patch to fix this specific problem and since there have been a number of sawfish updates via up2date since wolverine has been out, is there any chance this simple problem could be fixed before 7.1? This is one of these fixes that is so low cost and low risk that it seems silly (to me anyway) not to fix it.
Obviously this didn't make it into 7.1, but no matter -- I'm sure the next release will include an updated sawfish which will include this fix (as jsh fixed it in the real version...) Why doesn't someone just close this out -- maybe marking it deferred?
Normally we would keep a bug open until the fix is actually in the devel tree. I actually had this patch applied to the SRPM on my local hard drive but broke my arm before I could put it in the release - such is life.
Ouch. I hope your arm is recovering well. My solution to this problem is to redirect stdout and stderr of my window manager to ~/tmp/.wm.out. Most people wouldn't see this because their output would go to .xsession-errors, but my startup environment doesn't work this way. Thanks for the reply.
Fixed now