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 60793 - cannot use terminal after changing settings (gnome-terminal Crash at 210.85.221.152)
cannot use terminal after changing settings (gnome-terminal Crash at 210.85.2...
Status: RESOLVED DUPLICATE of bug 17440
Product: gnome-core
Classification: Deprecated
Component: gnome-terminal
1.2.x
Other other
: Normal normal
: ---
Assigned To: gnome-core Maintainers
gnome-core Maintainers
Depends on:
Blocks:
 
 
Reported: 2001-09-20 07:12 UTC by smallin_lin
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description smallin_lin 2001-09-20 07:12:18 UTC 
Package: gnome-core
Version: 1.2.4
Severity: 

>Synopsis: cannot use terminal after changing settings
>Class: sw-bug
System: Intel PIII 733 ,RedHat7.1+CLE1.0 (GNOME)

>Description:
When I chang the terminal settings->prefence->Font , then I cannt use terminal.
The error message is:
Application "GNOME-Terminal" (process1143) has crashed due to a fatal error.(Floating Point exception)

What do I do now?

				smallin

>How-To-Repeat:
step1.change the terminal font setting
step2.click terminal graph
step3.appear error message :
      Application "GNOME-Terminal" (process1143) has crashed due to a fatal error.(Floating Point exception)




------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-20 03:12 -------

The original reporter (smallin_lin@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, gnome-core-maint@bugzilla.gnome.org.
Comment 1 Kjartan Maraas 2001-09-20 07:21:00 UTC 
Try removing ~/.gnome/Terminal. You also should consider upgrading to
a newer release.
Comment 2 Gediminas Paulauskas 2002-03-05 10:20:53 UTC 

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