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 79853 - Crash in pannel on opening gnome session
Crash in pannel on opening gnome session
Status: RESOLVED DUPLICATE of bug 59500
Product: gnome-panel
Classification: Other
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-04-25 11:51 UTC by mm
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description mm 2002-04-25 11:52:55 UTC
Package: gnome-panel
Severity: normal
Version: 1.4.0.6
Synopsis: Crash in pannel on opening gnome session
Bugzilla-Product: gnome-panel
Bugzilla-Component: general

Description:
Just while logging on.



Debugging Information:

(no debugging symbols found)...0x405b3319 in __wait4 () from /lib/libc.so.6
  • #0 __wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 gnome_segv_handle
    at gnome-init.c line 664
  • #3 <signal handler called>
  • #4 gstc_parent_delete_watch
  • #5 main
  • #6 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129
  • #0 __wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 gnome_segv_handle
    at gnome-init.c line 664
  • #3 <signal handler called>
  • #4 gstc_parent_delete_watch
  • #5 main
  • #6 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-04-25 07:52 -------

The original reporter (mm@localhost.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-panel-maint@bugzilla.gnome.org.

Comment 1 Kjartan Maraas 2002-06-12 14:40:00 UTC
This is being worked on. 

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