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 70910 - nestcape abstürz
nestcape abstürz
Status: RESOLVED DUPLICATE of bug 38666
Product: gnome-core
Classification: Deprecated
Component: general
1.2.x
Other Linux
: Normal normal
: 1.4.1
Assigned To: gnome-core Maintainers
gnome-core Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-02-06 17:57 UTC by nglapah
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description nglapah 2002-02-08 09:43:56 UTC 
Package:  gnome-core
Severity: normal
Version:  1.2.4
Synopsis: nestcape abstürz
Class:    sw-bug

Distribution: Red Hat Linux release 7.1 (Seawolf)
System: Linux 2.4.2-2 i686 unknown
C library: glibc-2.2.2-10
C compiler: 2.96
glib: 1.2.9
GTK+: 1.2.9
ORBit: ORBit 0.5.7
gnome-libs: gnome-libs 1.2.8
libxml: 1.8.10
gnome-print: gnome-print-0.25-9
gnome-core: gnome-core 1.2.4


Description:
 nestcape stürzt jedes mal ab,wenn ich von eine die start seite auf eine
neue seite gehen will und es gibt immer eine fehler meldung über
Speicherzugriff.

mit  freundlichen grüßen .


Debugging information:
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x405bd519 in __wait4 () from /lib/i686/libc.so.6

+ Trace 17490

  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 gnome_segv_handle
    at eval.c line 41
  • #3 <signal handler called>
  • #4 SmsShutdownCancelled
    at eval.c line 41
  • #5 remove_client
    at eval.c line 41
  • #6 remove_client
    at eval.c line 41
  • #7 _SmsProcessMessage
    at eval.c line 41
  • #8 IceProcessMessages
    at eval.c line 41
  • #9 process_ice_messages
    at eval.c line 41
  • #10 gdk_io_invoke
    at eval.c line 41
  • #11 g_io_unix_dispatch
    at eval.c line 41
  • #12 g_main_dispatch
    at eval.c line 41
  • #13 g_main_iterate
    at eval.c line 41
  • #14 g_main_iteration
    at eval.c line 41
  • #15 gtk_main_iteration
    at eval.c line 41
  • #16 save_session
    at eval.c line 41
  • #17 gdk_io_invoke
    at eval.c line 41
  • #18 g_io_unix_dispatch
    at eval.c line 41
  • #19 g_main_dispatch
    at eval.c line 41
  • #20 g_main_iterate
    at eval.c line 41
  • #21 g_main_iteration
    at eval.c line 41
  • #22 gtk_main_iteration
    at eval.c line 41
  • #23 save_session
    at eval.c line 41
  • #24 gdk_io_invoke
    at eval.c line 41
  • #25 g_io_unix_dispatch
    at eval.c line 41
  • #26 g_main_dispatch
    at eval.c line 41
  • #27 g_main_iterate
    at eval.c line 41
  • #28 g_main_run
    at eval.c line 41
  • #29 gtk_main
    at eval.c line 41
  • #30 main
    at eval.c line 41
  • #31 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 gnome_segv_handle
    at eval.c line 41
  • #3 <signal handler called>
  • #4 SmsShutdownCancelled
    at eval.c line 41
  • #5 remove_client
    at eval.c line 41
  • #6 remove_client
    at eval.c line 41
  • #7 _SmsProcessMessage
    at eval.c line 41 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-02-08 04:43 -------

The original reporter (nglapah@yahoo.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 2002-02-09 14:18:35 UTC 
Please try the latest release (1.4.x) and see if that fixes it for you.
Comment 2 Kjartan Maraas 2002-03-14 09:23:47 UTC 
Fixed in a later version. Please upgrade.

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