Hi,
> Hmm looking at your patch I am not really sure why this fixes the issue for
> you, especially not as the top frame in your backtrace is a different
> function than the one that you patched. Though I also don't know what exactly
> menu_frame_visible is.
> I'll forward this upstream.
Actua
Hi,
* Salvatore De Paolis [2010-05-15 23:51]:
> * Andrew Chant [2010-01-06 14:22]:
> > Since upgrading from 3.4.8-1 to 3.4.9-2_amd64.deb
> > I get segfaults if I explore teh openbox menus for ~30seconds -> 1 minute.
> > This appears in .xsession-errors:
> >
> > How are you gentlemen? All your ba
* Andrew Chant [2010-01-06 14:22]:
> Since upgrading from 3.4.8-1 to 3.4.9-2_amd64.deb
> I get segfaults if I explore teh openbox menus for ~30seconds -> 1 minute.
> This appears in .xsession-errors:
>
> How are you gentlemen? All your base are belong to us. (Openbox received
> signal 11)
>
>
Starting program: /usr/bin/openbox
Program received signal SIGSEGV, Segmentation fault.
0x00431eb7 in menu_entry_frame_show_submenu ()
(gdb) bt
#0 0x00431eb7 in menu_entry_frame_show_submenu ()
#1 0x004321e9 in ?? ()
#2 0x0042f7b5 in ob_main_loop_run ()
#3 0x000
Hi,
* Andrew Chant [2010-01-06 14:22]:
> Since upgrading from 3.4.8-1 to 3.4.9-2_amd64.deb
> I get segfaults if I explore teh openbox menus for ~30seconds -> 1 minute.
> This appears in .xsession-errors:
>
> How are you gentlemen? All your base are belong to us. (Openbox received
> signal 11)
>
Package: openbox
Version: 3.4.9-2
Severity: important
Since upgrading from 3.4.8-1 to 3.4.9-2_amd64.deb
I get segfaults if I explore teh openbox menus for ~30seconds -> 1 minute.
This appears in .xsession-errors:
How are you gentlemen? All your base are belong to us. (Openbox received signal
11)
6 matches
Mail list logo