Date: Mon, 15 Sep 2008 15:59:06 -0400 From: Randy Pratt <bsd-unix@embarqmail.com> To: "Jeremy Messenger" <mezz7@cox.net> Cc: freebsd-ports@freebsd.org, L Campbell <llc2w@virginia.edu> Subject: Re: fluxbox unshade crashing GTK2 applications? Message-ID: <20080915155906.5288eaa5.bsd-unix@embarqmail.com> In-Reply-To: <op.uhjclrg39aq2h7@mezz.mezzweb.com> References: <792298050809150907r5f53fa09r433afc176fb4b368@mail.gmail.com> <op.uhjclrg39aq2h7@mezz.mezzweb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 15 Sep 2008 13:35:41 -0500 "Jeremy Messenger" <mezz7@cox.net> wrote: > On Mon, 15 Sep 2008 11:07:09 -0500, L Campbell <llc2w@virginia.edu> wrote: > > > (This probably isn't the right place to ask, but I figured I'd start > > here and head upstream if necessary). > > > > Since updating to fluxbox 1.1.0.1 last night (and x11-toolkits/gtk20 > > to revision 1), attempting to unshade a shaded GUI application is > > causing the application to segfault with a BadAlloc X Window System > > error. This behavior was not observed before updating. Tested with > > www/firefox3, graphics/gimp and graphics/inkscape. For all three > > applications, unshading produces the following error -- > > > > The program 'gimp' received an X Window System error. > > This probably reflects a bug in the program. > > The error was 'BadAlloc (insufficient resources for operation)'. > > (Details: serial 3250 error_code 11 request_code 53 minor_code 0) > > (Note to programmers: normally, X errors are reported asynchronously; > > that is, you will receive the error a while after causing it. > > To debug your program, run it with the --sync command line > > option to change this behavior. You can then get a meaningful > > backtrace from your debugger if you break on the gdk_x_error() > > function.) > > > > I'm not really sure if this is an issue with fluxbox, GTK, or my own > > configuration. It seems like only GTK2 applications crashing -- > > audio/aumix uses GTK 1.2 and doesn't crash on unshade. Relevant > > version information follows, please advise on appropriate course of > > action :( > > > > $ uname -a > > FreeBSD kanaria.desudesudesu.org 7.0-STABLE FreeBSD 7.0-STABLE #4: Fri > > Aug 1 17:05:27 EDT 2008 > > hark@kanaria.desudesudesu.org:/usr/obj/usr/src/sys/KANARIA i386 > > > > x11-wm/fluxbox-1.1.0.1 > > $ fluxbox -version > > Fluxbox 1.1.0.1 : (c) 2001-2008 Fluxbox Team > > > > x11-toolkits/gtk-1.2.10_20 > > x11-toolkits/gtk-2.12.11_1 > > > > www/firefox-3.0.1_1,1 > > $ firefox3 -version > > Mozilla Firefox 3.0.1, Copyright (c) 1998 - 2008 mozilla.org > > > > graphics/gimp-2.4.7,2 > > $ gimp --version > > GNU Image Manipulation Program version 2.4.7 > > > > graphics/inkscape-0.46_3 > > $ inkscape --version > > Inkscape 0.46 (Jul 6 2008) > > > > Let me know if there's anything else I can do to help get this fixed. > > Thanks :( > > Try to fetch this patch and put in x11-wm/fluxbox/files/, then reinstall > fluxbox. It was took from its git. > > http://people.freebsd.org/~mezz/diff/patch-fix_unshading_crash I was seeing the same unshading problem with Sylpheed2 with the new fluxbox. The above patch seems to fix it. Oddly, if I ran sylpheed -sync (as the error message suggested for debugging) then the unshading problem disappeared so I wasn't able to do any debugging. Like the OP, I wasn't sure where the problem originated but reverting to an older version of fluxbox eliminated the problem. Thanks for digging out the patch! Randy --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080915155906.5288eaa5.bsd-unix>