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 112210 - Crashed when I exited the program - save dialog box remained open.
Crashed when I exited the program - save dialog box remained open.
Status: RESOLVED INCOMPLETE
Product: scaffold
Classification: Deprecated
Component: libanjuta
unspecified
Other other
: Normal normal
: ---
Assigned To: Scaffold Maintainers List
Scaffold Maintainers List
Depends on:
Blocks:
 
 
Reported: 2003-05-04 14:23 UTC by kfarrokhzad
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description kfarrokhzad 2003-05-04 14:19:33 UTC 
Package: anjuta2
Severity: normal
Version: 0.4.3
Synopsis: Crashed when I exited the program - save dialog box remained open.  
Bugzilla-Product: anjuta2
Bugzilla-Component: libanjuta

Description:
Description of Problem:


Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?


Additional Information:




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-05-04 10:19 -------

The original reporter (kfarrokhzad@hotmail.com) 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, anjuta2-maint@bugzilla.gnome.org.
Comment 1 Elijah Newren 2003-05-06 17:41:31 UTC 
Thanks for taking the time to report this bug. This bug report isn't
very useful because it doesn't describe the bug well. If you have time
and can still reproduce the bug, please read
http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how
to reproduce this bug.

You'll also need to add a stack trace; please make sure the package
was compiled with debugging symbols and see
http://bugzilla.gnome.org/getting-traces.cgi for more information
about getting a useful stack trace.

Also, could you tell us which program crashed?  At least half the bugs
filed against anjuta aren't really anjuta bugs.