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 84351 - crash when using modify in the tools menu
crash when using modify in the tools menu
Status: RESOLVED DUPLICATE of bug 52836
Product: dia
Classification: Other
Component: general
0.88.x
Other other
: Normal normal
: ---
Assigned To: Dia maintainers
Dia maintainers
Depends on:
Blocks:
 
 
Reported: 2002-06-06 09:56 UTC by bcohen
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description bcohen 2002-06-06 09:41:24 UTC 
Package: dia
Severity: normal
Version: 0.88.1
Synopsis: crash when using modify in the tools menu
Bugzilla-Product: dia
Bugzilla-Component: general

Description:
when right clicking on an object and selecting any option in the tools menu, the application craches


Debugging Information:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x405c4669 in __wait4 () from /lib/i686/libc.so.6

+ Trace 23397

  • #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>
  • #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>
  • #0 __strtol_internal
    at eval.c line 36 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-06-06 05:41 -------

The original reporter (bcohen@ens.uvsq.fr) 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, dia-maint@bugzilla.gnome.org.
Comment 1 Lars Clausen 2002-06-06 10:23:49 UTC 

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