[ On Monday, February 25, 2008 at 17:15:43 (+0100), Jesús Guerrero wrote: ] > Subject: Re: FVWM: fvwm patches and esperanza > > On Mon, 25 Feb 2008 16:31:36 +0100 > > 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. >
Currently, there two sets of patches available at the above url, one for 2.5.18 and the other 2.5.23. The author tested tohose against 2.5.18 and 2.5.23, respectively. I took and applied the patches for 2.5.23. > > > 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 meant menutranslucency. > > > 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 Okay, I will give it a try, but I'm afraid my ~/.xinitrc isn't read by gdm. ingo
