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 21392 - This fatal error upon every reboot. (gnome-help-browser Crash at 208.211.151.151)
This fatal error upon every reboot. (gnome-help-browser Crash at 208.211.151....
Status: RESOLVED DUPLICATE of bug 9293
Product: gnome-core
Classification: Deprecated
Component: help-browser
unspecified
Other other
: Normal normal
: 1.4.1
Assigned To: gnome-core Maintainers
gnome-core Maintainers
Depends on:
Blocks:
 
 
Reported: 2000-08-22 01:58 UTC by schroed
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description schroed 2001-01-27 20:03:53 UTC
Package: gnome-core
Version: Process 633
Severity: 

>Synopsis: This fatal error upon every reboot.
>Class: sw-bug
System: Linux 6.1 on a Compaq ML350 with 2Gigs of RAM.

>Description:
I get this fatal error upon every reboot.  
It specifically states:

Application "gnome-help-browser" (process 633)
has crashed due to a fatal error.
(Segmentation fault)

Did a server install and then customized it.  Have
partitions on more than one drive.  Compaq ML350
with 2-Gigs of RAM a two SCSI 18 Gig drives.
At this point, I have only installed version 6.1.
Thanks in advance.	

>How-To-Repeat:
Same as above, upon every reboot.




------- Bug moved to this database by debbugs-export@bugzilla.gnome.org 2001-01-27 15:03 -------
This bug was previously known as bug 21392 at http://bugs.gnome.org/
http://bugs.gnome.org/show_bug.cgi?id=21392
Originally filed under the gnome-core product and general component.

The original reporter (schroed@interaccess.com) of this bug does not have an account here.
Reassigning to the exporter, debbugs-export@bugzilla.gnome.org.
Reassigning to the default owner of the component, gnome-core-maint@bugzilla.gnome.org.

Comment 1 Kjartan Maraas 2001-09-17 13:18:04 UTC
Has this been fixed in a later release?

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