[ On Monday, February 25, 2008 at 16:31:36 (+0100), Ingo Wardinski wrote: ] > Subject: Re: FVWM: fvwm patches and esperanza > > [ On Monday, February 25, 2008 at 16:06:32 (+0100), Jesús Guerrero wrote: ] > > Subject: Re: FVWM: fvwm patches and esperanza > > > > On Mon, 25 Feb 2008 04:14:09 -0700 > > Jaimos Skriletz <[EMAIL PROTECTED]> wrote: > > > > > On Mon, Feb 25, 2008 at 11:35:55AM +0100, Ingo Wardinski wrote: > > > > Hi all, > > > > I see some oddities in the behaviour of fvwm after I installed > > > > fvwm-2.5.23 and applied various patches to obtain translucency, > > > > roundcorners, etc. In fact when I start esperanza (xmms2 client) my X > > > > crashes. I checked several logs, but I couldn't find what is causing > > > > the problem. So my primary guess is that it might be related to the > > > > applied patches, because everything was fine before the patches > > > > applied. Does someone else have similar problems? > > > > > > You'll probabaly have to do some debugging to fix your issue. > > > > > > One method might be to use Style statments to ensure esperanza is not > > > using any of the features provided by the patches. If this gives you the > > > stability you can then start applying the styles you want one at a time > > > until you find which one is causing the crash. > > > > > > another option is to figure out what patch(s) are causing the conflict by > > > applying them one at a time and testing the results. > > > > > > Once you figure out what patch(s) are causing the problem then you can > > > direct the bug to the patch matainer and hope he is helpful in solving > > > the issue. > > > > > > these are just suggestions to try to get you up and running. > > > > > > > > > jaimos > > > > > > > > I don't know if you are using the patches that I host at > > jesgue.homelinux.org, > > but if that's the case then you'll probably need to debug a bit. > > > > I just host them, and I modified some of them several times to allow them > > to continue living, but I just did the necessary modifications, and I don't > > understand most of them at all, since the code is not mine and I didn't > > really look too deep at the fvwm source code. > > > > Some structures in fvwm changed/got added, and those patches were planed > > against > > older fvwm versions. It is highly probable that something is seriously > > screwed in > > some of them (specially the fluxbox borders one hehehe). I don't have the > > time > > nor the interest to look into them (otherwise I would probably try to clean > > them to integrate some of them into fvwm properly). > > > > You should try to apply on one of them, and try, and so on, Until you find > > which > > is the responsible for the segfault. Looking into the X logs and output on > > console > > might (or might not) give you some hints on what is causing the problem. > > > > I took the patches from http://www.abdn.ac.uk/~u15dm4/fvwm/ > and I tried different setups > 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 > > all don't work and led to crash the X!! > > 5.) fvwm-2.5.18 + xmms2-0.4DrKosmos + esperanza > > this used to work fine before I updated to fvwm-2.5.23 in order to > have neat features like translucency etc. > > As I mention earlier, I checked the X logs, but there were no > indications what went wrong. The X crashes when I call esperanza via > Fvwmscript or from command line. > > 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 did some further "research" in tcsh I did unlimited coredumpsize and in bash I set ulimit -c 10000 then I called esperanza to get a corefile , but I even do not get a core file. I'm puzzled, any suggestions? ingo
