You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are still problems with segfaults and various errors being logged.
version bcb39a8 + pull #116, #168, #191, #43 patched in - but I get the same errors with or without them (ie pull #168 makes no difference)
When amulegui is run from commandline I see lots of these:
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
What I hadn't spotted is what was going on in .xsession-errors:
lots of
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
but also:
...
(amulegui:1111269): Gtk-WARNING **: 17:06:09.773: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node tab owner GtkNotebook)
(amulegui:1111269): Gtk-WARNING **: 17:10:44.167: drawing failure for widget 'wxPizza': out of memory
(amulegui:1111269): Gtk-WARNING **: 17:10:44.167: drawing failure for widget 'GtkScrolledWindow': out of memory
There are a number of different runs here and in case It makes any difference I'm using multiheaded X. but it really shouldn't matter - this looks like a GTK declaration problem.
The criticals are almost always "client crashed" events.
The UI throws most of the same error messages when running amule instead of amuled+amulegui, but it doesn't crash and burn
The text was updated successfully, but these errors were encountered:
There are still problems with segfaults and various errors being logged.
version bcb39a8 + pull #116, #168, #191, #43 patched in - but I get the same errors with or without them (ie pull #168 makes no difference)
When amulegui is run from commandline I see lots of these:
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
What I hadn't spotted is what was going on in .xsession-errors:
lots of
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
but also:
...
(amulegui:1111269): Gtk-WARNING **: 17:06:09.773: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node tab owner GtkNotebook)
(amulegui:1111269): Gtk-WARNING **: 17:10:44.167: drawing failure for widget 'wxPizza': out of memory
(amulegui:1111269): Gtk-WARNING **: 17:10:44.167: drawing failure for widget 'GtkScrolledWindow': out of memory
(amulegui:2904074): Gtk-CRITICAL **: 04:24:59.269: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkSpinButton
(amulegui:2817563): Gtk-WARNING **: 02:48:32.861: Negative content width -9 (allocation 1, extents 5x5) while allocating gadget (node entry, owner GtkEntry)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.861: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node border, owner GtkFrame)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.861: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node border, owner GtkFrame)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.861: Negative content width -9 (allocation 1, extents 5x5) while allocating gadget (node entry, owner GtkEntry)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.861: Negative content height -1 (allocation 1, extents 1x1) while allocating gadget (node entry, owner GtkEntry)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.861: Negative content width -9 (allocation 1, extents 5x5) while allocating gadget (node entry, owner GtkEntry)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.861: Negative content height -1 (allocation 1, extents 1x1) while allocating gadget (node entry, owner GtkEntry)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.861: Negative content width -9 (allocation 1, extents 5x5) while allocating gadget (node entry, owner GtkEntry)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.861: Negative content height -1 (allocation 1, extents 1x1) while allocating gadget (node entry, owner GtkEntry)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.861: Negative content width -9 (allocation 1, extents 5x5) while allocating gadget (node entry, owner GtkEntry)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.861: Negative content height -1 (allocation 1, extents 1x1) while allocating gadget (node entry, owner GtkEntry)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.861: Negative content width -9 (allocation 1, extents 5x5) while allocating gadget (node entry, owner GtkEntry)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.862: Negative content height -1 (allocation 1, extents 1x1) while allocating gadget (node entry, owner GtkEntry)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.862: Negative content width -17 (allocation 1, extents 9x9) while allocating gadget (node button, owner GtkButton)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.862: Negative content height -3 (allocation 1, extents 2x2) while allocating gadget (node button, owner GtkButton)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.862: Negative content width -17 (allocation 1, extents 9x9) while allocating gadget (node button, owner GtkButton)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.862: Negative content height -3 (allocation 1, extents 2x2) while allocating gadget (node button, owner GtkButton)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.862: Negative content width -17 (allocation 1, extents 9x9) while allocating gadget (node button, owner GtkButton)
(amulegui:2817563): Gtk-WARNING **: 02:48:32.862: Negative content height -3 (allocation 1, extents 2x2) while allocating gadget (node button, owner GtkButton)
(amulegui:2817563): Gtk-CRITICAL **: 02:48:32.863: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar
...
There are a number of different runs here and in case It makes any difference I'm using multiheaded X. but it really shouldn't matter - this looks like a GTK declaration problem.
The criticals are almost always "client crashed" events.
The UI throws most of the same error messages when running amule instead of amuled+amulegui, but it doesn't crash and burn
The text was updated successfully, but these errors were encountered: