Bug 54934 – Switching on anti-aliasing causes segv

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 54934 - Switching on anti-aliasing causes segv


Summary:	Switching on anti-aliasing causes segv


Status:	RESOLVED DUPLICATE of bug 65985

Product:	dia
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other Linux

Importance:	Normal major
Target Milestone:	---
Assigned To:	James Henstridge
QA Contact:	James Henstridge

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2001-05-19 08:46 UTC by flitney
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description flitney 2001-05-19 07:32:38 UTC

Package:  dia
Severity: grave
Version:  0.84
Synopsis: Switching on anti-aliasing causes segv
Class:    sw-bug

Distribution: Red Hat Linux release 7.0 (Guinness)
System: Linux 2.4.1 i686 unknown
C library: glibc-2.1.92-14
C compiler: 2.96
glib: 1.2.8
GTK+: 1.2.8
ORBit: ORBit 0.5.3
gnome-libs: gnome-libs 1.2.4
libxml: 1.8.9
gnome-print: gnome-print-0.20-8
gnome-core: gnome-core 1.2.1


Description:
I was editing a modest diagram containing various UML elements.
Switching on
the anti-aliased view option caused Dia to crash instantly.


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)...
0x4056a5a9 in __wait4 () from /lib/libc.so.6

+ Trace 5533

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





------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-05-19 03:32 -------

The original reporter (flitney@fmrib.ox.ac.uk) 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-05-19 17:41:48 UTC

This is probably fixed in V0.88 (V0.84 is really old). Anyway, it's a
duplicate.

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

Comment 2 Lars Clausen 2003-02-15 22:04:46 UTC

Finally fixed, marking as duplicate.

Comment 3 Lars Clausen 2003-02-15 22:05:06 UTC


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