On Mon, 25 Feb 2008 16:31:36 +0100 Ingo Wardinski <[EMAIL PROTECTED]> wrote:
> I took the patches from http://www.abdn.ac.uk/~u15dm4/fvwm/ > and I tried different setups Mmmm, I can't be sure, but I don't think that those patches can be applied without manually fixing some rejects. Those are the original patches, and were designed to be used against older fvwm versions. So, if you applied some of them, there's a high chance that some of them failed to apply correctly... What amazes me is that it compiled without problems after failing to patch correctly. To be sure, you can look at the fvwm subdir on the source tree, and ls for *.rej files. > 1.) fvwm-2.5.23 + patches + xmms2-0.4DrKosmos + esperanza > 2.) fvwm-2.5.23 + xmms2-0.4DrKosmos + esperanza > 3.) fvwm-2.5.23 + patches + xmms2-0.2DrJekyll + esperanza > 4.) fvwm-2.5.23 + xmms2-0.2DrJekyll + esperanza There's also a chance that the xmms2 stuff is acting in a broken way, just like xmms used to. That shouldn't make fvwm segfault, though. > this used to work fine before I updated to fvwm-2.5.23 in order to > have neat features like translucency etc. I don't know what do you mean. Transparent colorsets on panels and the like were supported on .18 as well. If you are talking about the translucency patch for menus, you need that on .23 as well. That patch has never been integrated into fvwm. So, you need it anyway. > I would appreciate very much any advice on how to debug my fvwm > session. Can I force fvwm to output/log any communication between > applications and X server? I use this in my ~/.xinitrc fvwm &>~/logs/fvwm.log 2>&1 Then I just issue startx on command line. Be sure that the directory ~/logs/ exists. -- Jesús Guerrero <[EMAIL PROTECTED]>
