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 333846 - dia: crash after closed a opened file, then create new one
dia: crash after closed a opened file, then create new one
Status: RESOLVED DUPLICATE of bug 161603
Product: dia
Classification: Other
Component: general
0.94
Other other
: Normal critical
: ---
Assigned To: Dia maintainers
Dia maintainers
Depends on:
Blocks:
 
 
Reported: 2006-03-08 03:50 UTC by qingyou_meng
Modified: 2006-03-10 18:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description qingyou_meng 2006-03-08 03:50:14 UTC
Distribution: Fedora Core release 4 (Stentz)
Package: dia
Severity: critical
Version: GNOME2.10.0 0.94
Gnome-Distributor: Red Hat, Inc
Synopsis: crash after closed a opened file, then create new one
Bugzilla-Product: dia
Bugzilla-Component: general
Bugzilla-Version: 0.94
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. open an existing file, edit, save, close.
2. try creating a new file
3. dia popup a dialog and says it is crashed. the dialog has a restart
dia button

Expected Results:


How often does this happen?

often

Additional Information:

$ uname -a
Linux mqy-notebook 2.6.15-1.1833_FC4 #1 Wed Mar 1 23:41:37 EST 2006 i686
i686 i386 GNU/Linux

$ locale
LANG=zh_CN.UTF-8
LC_CTYPE="zh_CN"
LC_NUMERIC="zh_CN"
LC_TIME="zh_CN"
LC_COLLATE="zh_CN"
LC_MONETARY="zh_CN"
LC_MESSAGES="zh_CN"
LC_PAPER="zh_CN"
LC_NAME="zh_CN"
LC_ADDRESS="zh_CN"
LC_TELEPHONE="zh_CN"
LC_MEASUREMENT="zh_CN"

_________________________________________________________________
\xD3\xEB\xC1\xAA\xBB\xFA\xB5\xC4\xC5\xF3\xD3ѽ\xF8\xD0н\xBB\xC1\xF7\xA3\xAC\xC7\xEBʹ\xD3\xC3 MSN Messenger:  http://messenger.msn.com/cn




------- Bug created by bug-buddy at 2006-03-08 03:50 -------

Comment 1 Lars Clausen 2006-03-10 18:32:12 UTC
Sounds very much like a memory corruption bug we had with closing diagrams, but in a slightly different incarnation.

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