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 61549 - crash with antialiasing
crash with antialiasing
Status: RESOLVED DUPLICATE of bug 65985
Product: dia
Classification: Other
Component: general
unspecified
Other Linux
: Normal critical
: ---
Assigned To: James Henstridge
James Henstridge
Depends on:
Blocks:
 
 
Reported: 2001-10-03 01:12 UTC by cmountford
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description cmountford 2001-10-02 05:13:05 UTC 
Package:  dia
Severity: critical
Version:  0.86
Synopsis: crash with antialiasing
Class:    sw-bug

Distribution: Red Hat Linux release 7.1 (Seawolf)
System: Linux 2.4.2-2 i686 unknown
C library: glibc-2.2.2-10
C compiler: 2.96
glib: 1.2.9
GTK+: 1.2.9
ORBit: ORBit 0.5.7
gnome-libs: gnome-libs 1.2.8
libxml: 1.8.10
gnome-print: gnome-print-0.25
gnome-core: gnome-core 1.2.4


Description:
When I turn antialiasing on, dia dumps core. The antialiasing seems to
redraw correctly, just as soon as it's done though, it falls over. It's
as simple as that.


Debugging information:
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x405ab519 in __wait4 () from /lib/i686/libc.so.6

+ Trace 10989

  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 gnome_segv_handle
    from /usr/lib/libgnomeui.so.32
  • #3 <signal handler called>
  • #4 gdk_rgb_convert_0888
    at eval.c line 41
  • #5 gdk_draw_rgb_image_core
    at eval.c line 41
  • #6 gdk_draw_rgb_image
    at eval.c line 41
  • #7 renderer_libart_copy_to_window
    at eval.c line 41
  • #8 ddisplay_flush
    at eval.c line 41
  • #9 popup_marshal_func
    from /usr/lib/libgnomeui.so.32
  • #10 gtk_handlers_run
    at eval.c line 41
  • #11 gtk_signal_real_emit
    at eval.c line 41
  • #12 gtk_signal_emit
    at eval.c line 41
  • #13 gtk_widget_activate
    at eval.c line 41
  • #14 gtk_menu_shell_activate_item
    at eval.c line 41
  • #15 gtk_menu_shell_button_release
    at eval.c line 41
  • #16 gtk_marshal_BOOL__POINTER
    at eval.c line 41
  • #17 gtk_signal_real_emit
    at eval.c line 41
  • #18 gtk_signal_emit
    at eval.c line 41
  • #19 gtk_widget_event
    at eval.c line 41
  • #20 gtk_propagate_event
    at eval.c line 41
  • #21 gtk_main_do_event
    at eval.c line 41
  • #22 gdk_event_dispatch
    at eval.c line 41
  • #23 g_main_dispatch
    at eval.c line 41
  • #24 g_main_iterate
    at eval.c line 41
  • #25 g_main_run
    at eval.c line 41
  • #26 gtk_main
    at eval.c line 41
  • #27 main
    at eval.c line 41
  • #28 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 gnome_segv_handle
    from /usr/lib/libgnomeui.so.32
  • #3 <signal handler called>
  • #4 gdk_rgb_convert_0888
    at eval.c line 41
  • #5 gdk_draw_rgb_image_core
    at eval.c line 41
  • #6 gdk_draw_rgb_image
    at eval.c line 41
  • #7 renderer_libart_copy_to_window
    at eval.c line 41 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-10-02 01:13 -------

The original reporter (cmountford@e-cademy.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, james@daa.com.au.
Comment 1 Cyrille Chépélov 2001-10-11 22:08:05 UTC 
AA displays a warning in 0.86. Please pay attention to it. It's as
simple as that (please try to upgrade to 0.88.1 or 0.89-test2, and
please don't approach anywhere near AA).
Comment 2 Lars Clausen 2003-02-15 22:02:26 UTC 
Finally fixed, you may now approach AA again.
Marking as duplicate.
Comment 3 Lars Clausen 2003-02-15 22:02:41 UTC 

*** This bug has been marked as a duplicate of 65985 ***