fluxbox unshade crashing GTK2 applications?
L Campbell
llc2w at virginia.edu
Mon Sep 15 16:07:17 UTC 2008
(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 at 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 :(
More information about the freebsd-ports
mailing list