After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 608337 - Balsa crashes with Gdk:ERROR:gdkregion-generic.c:1108:miUnionNonO: assertion failed: (y1 < y2)
Balsa crashes with Gdk:ERROR:gdkregion-generic.c:1108:miUnionNonO: assertion ...
Status: RESOLVED OBSOLETE
Product: balsa
Classification: Other
Component: general
unspecified
Other Linux
: Normal critical
: ---
Assigned To: Balsa Maintainers
Balsa Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-01-28 13:32 UTC by Ildar
Modified: 2021-06-01 22:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Stack trace (3.90 KB, text/plain)
2010-01-29 15:26 UTC, Peter Bloomfield
Details

Description Ildar 2010-01-28 13:32:16 UTC
Starting with version 2.4.3+ balsa started to crash with following complaints:

> Gdk:ERROR:gdkregion-generic.c:1108:miUnionNonO: assertion failed: (y1 < y2)
> opening Входящие..
> Multiple segmentation faults occurred; can't display error dialog

and sometimes with:
> The program 'balsa' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadMatch (invalid parameter attributes)'.
>   (Details: serial 692723 error_code 8 request_code 59 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.)
> opening Входящие..

These troubles happen when I have --enable-threads.

But with --disable-threads everything looks stable.

Can't gather backtraces as balsa in gdb "just quits" - no SIGnals are caught.
Comment 1 Peter Bloomfield 2010-01-29 00:42:39 UTC
Yeah, I've seen both of those.   I did get a stack trace for the first--it was deep in a GtkStatusBar operation, in GtkLabel if I recall correctly.  No corresponding change in Balsa code, so it looks like a new vulnerability in Gdk or X or...

The second looks like it's plain X.  I don't recall getting a trace.
Comment 2 Ildar 2010-01-29 04:12:10 UTC
I'd be glad to agree.
But other applications to not suffer from such a problems while I'm in GTK/Gnome environment all the time. Or those are just not GUI-intensive?
Comment 3 Peter Bloomfield 2010-01-29 15:26:40 UTC
Created attachment 152585 [details]
Stack trace

Attached stack trace is for the first problem: "assertion failed: (y1 < y2)".
Comment 4 Ildar 2010-02-08 17:08:14 UTC
One more crasher:
> (balsa:6220): GLib-CRITICAL **: g_node_traverse: assertion `root != NULL' failed
It happened when I clicked a mailbox and closed it before it finished opening.
Comment 5 André Klapper 2021-06-01 22:42:29 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new enhancement request ticket at
  https://gitlab.gnome.org/GNOME/balsa/-/issues/

Thank you for your understanding and your help.