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 70795 - Crash in history when closing nautilus windows
Crash in history when closing nautilus windows
Status: RESOLVED DUPLICATE of bug 71179
Product: nautilus
Classification: Core
Component: [obsolete] Backgrounds Emblems and Themes
1.1.x
Other other
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-02-07 10:15 UTC by Alessio Dessi
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Description Alessio Dessi 2002-02-07 10:18:00 UTC 
Package: nautilus
Severity: normal
Version: 1.1.3
Synopsis: Crash when closing nautilus windows
Bugzilla-Product: nautilus
Bugzilla-Component: Backgrounds Emblems and Themes
BugBuddy-GnomeVersion: 2.0 (1.110.1)

Description:
Description of Problem:
I enter in my home folder in the desktop, and when I go out quitting
nautilus I get alwat a nautilus history crash

Steps to reproduce the problem:
1. enter in the home folder
2. exit , quiting the windows
3. 

Actual Results:
crash

Expected Results:
nothing, regular end

How often does this happen?
always

Additional Information:




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-02-07 05:18 -------

Unknown version 1.1.x in product nautilus. Setting version to the default, "unspecified".
The original reporter (alessio.dessi@libero.it) 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, nautilus-maint@bugzilla.gnome.org.
Comment 1 John Fleck 2002-02-07 16:23:59 UTC 
Adding GNOME2 keyword.
Comment 2 Luis Villa 2002-02-07 17:21:25 UTC 
alessio: can you please be sure to submit stack traces when you report
bugs? This is a nearly useless bug report because it does not include
a stack trace.
Comment 3 Luis Villa 2002-02-11 16:31:56 UTC 

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