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 300854 - Crash when dragging uml class
Crash when dragging uml class
Status: RESOLVED DUPLICATE of bug 173031
Product: dia
Classification: Other
Component: general
CVS head
Other All
: High critical
: ---
Assigned To: Dia maintainers
Dia maintainers
Depends on:
Blocks:
 
 
Reported: 2005-04-16 11:23 UTC by nicolas.girard
Modified: 2005-04-20 19:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Diagram that caused the crash (1.50 KB, application/x-dia-diagram)
2005-04-16 11:24 UTC, nicolas.girard
Details

Description nicolas.girard 2005-04-16 11:23:31 UTC
Steps to reproduce:
1. Load the attach diagram 
2. Try to drag the Synonym class in any direction 
3.  
 

Stack trace:
No available stack trace. 

Other information:
Comment 1 nicolas.girard 2005-04-16 11:24:29 UTC
Created attachment 45322 [details]
Diagram that caused the crash
Comment 2 Alan Horkan 2005-04-16 13:58:26 UTC
Not a problem in 0.94
Comment 3 Radek Krahl 2005-04-16 14:54:43 UTC
Crashes in CVS head. Backtrace:

Program received signal SIGSEGV, Segmentation fault.

Thread 16384 (LWP 7122)

  • #0 orthconn_update_data
    at orth_conn.c line 307
  • #1 association_update_data
    at association.c line 618
  • #2 association_move_handle
    at association.c line 296
  • #3 diagram_update_connections_object
    at connectionpoint_ops.c line 117
  • #4 diagram_update_connections_selection
    at connectionpoint_ops.c line 79
  • #5 modify_motion
    at modify_tool.c line 444
  • #6 ddisplay_canvas_events
    at disp_callbacks.c line 670
  • #7 gtk_marshal_VOID__UINT_STRING
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??

Duplicate of a bug #173031.
Comment 4 Hans Breuer 2005-04-20 19:56:58 UTC

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