fluxbox unshade crashing GTK2 applications?

Jeremy Messenger mezz7 at cox.net
Mon Sep 15 22:07:25 UTC 2008


On Mon, 15 Sep 2008 14:59:06 -0500, Randy Pratt <bsd-unix at embarqmail.com>  
wrote:

> On Mon, 15 Sep 2008 13:35:41 -0500
> "Jeremy Messenger" <mezz7 at cox.net> wrote:
>
>> On Mon, 15 Sep 2008 11:07:09 -0500, L Campbell <llc2w at 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 :(
>> >
<snip>
>> >
>> > 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!

No problem and thank (include to L Campbell too) for test patch. I shall  
put in ports tree whenever portmgr approves tomorrow or so. I have one  
more patch that I want to test tonight or tomorrow, before I make request  
to portmgr. It's for pixmap resource leak in pixmap menu.

Cheers,
Mezz

> Randy


-- 
mezz7 at cox.net  -  mezz at FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/  -  gnome at FreeBSD.org


More information about the freebsd-ports mailing list