package euler unarchive 199647 forcemerge 448649 199647 notfound 448649 1.61.0-3 tags 448649 = confirmed help thanks
Hi, On Wednesday 31 October 2007, Mikhail Glagolev wrote: > moving .euler/ solved the problem. > > I found, that on my system the error can be reproduced by setting in > eulerrc: > > gwidth = 350 > gheight = 443 > > (those were in the initial case) > > Error also occurs, for instance, with > > gwidth = 400 > gheight = 600 > > but not > > gwidth = 400 > gheight = 500 > > (other parameters in eulerrc and euler.cfg dafault) Thanks for the information, I was now able to reproduce this bug with euler/1.61.0-1 on an etch system, but it is not reproducible with 1.61.0-3 on my sid development system (and I suspect that it does not occur with testing too). Probably something in the GTK+ libraries changed so that it doesn't occur with the newer versions. Here is what I got from gdb if one builds euler with debugging symbols: | Starting program: /usr/bin/euler | Failed to read a valid object file image from memory. | [Thread debugging using libthread_db enabled] | [New Thread -1218246976 (LWP 21208)] | | (euler:21208): Gdk-CRITICAL **: gdk_char_width: assertion `font != NULL' | failed | | Program received signal SIGSEGV, Segmentation fault. | [Switching to Thread -1218246976 (LWP 21208)] | 0x080824db in gtk_meta_realize () I had a look at the gtk_meta_realize() function in euler, but I'm not well versed enough in GTK+ to fix this without greater effort and since this bug does not occur wiht newer libs, I'm not going to invest time to fix this. However if someone else wants to submit a patch for this bug, I'll apply it to the package of course. BTW: There was also an old bug report about the same error which I closed as I adopted this package because I was unable to reproduce the bug. I'm merging the old report with this new report now. Grüße, Frank
signature.asc
Description: This is a digitally signed message part.
