FS#63 - "set status_top = 0" segfaults
Attached to Project:
Uzbl
Opened by Michael Arntzenius (rntz) - 2009-07-06 01:49:05 AM
Last edited by Dieter Plaetinck (Dieter_be) - 2009-09-13 12:01:13 PM
Opened by Michael Arntzenius (rntz) - 2009-07-06 01:49:05 AM
Last edited by Dieter Plaetinck (Dieter_be) - 2009-09-13 12:01:13 PM
|
DetailsIn any context except the initial load of the config file (eg: entered interactively via the chain command, echo'd to the control fifo), "set status_top = <foo>" causes a segfault (where <foo> can be anything). This means that, for example, "!reload" causes a segfault if this line is contained in your config file (and it is in the default config file). Error messages printed before segfault follow:
(uzbl:4721): Gdk-CRITICAL **: gdk_window_new: assertion `window != NULL' failed (uzbl:4721): Gdk-CRITICAL **: gdk_window_set_user_data: assertion `GDK_IS_WINDOW (window)' failed (uzbl:4721): Gdk-CRITICAL **: gdk_colormap_get_screen: assertion `GDK_IS_COLORMAP (cmap)' failed (uzbl:4721): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (uzbl:4721): Gdk-CRITICAL **: gdk_colormap_get_visual: assertion `GDK_IS_COLORMAP (colormap)' failed |
This task depends upon
do you still have this issue with latest experimental code? a lot has been fixed/changed recently :)