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 81036 - panel applets crashed
panel applets crashed
Status: RESOLVED DUPLICATE of bug 76658
Product: gnome-panel
Classification: Other
Component: panel
unspecified
Other other
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 82017 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-05-07 13:30 UTC by bailey
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description bailey 2002-05-07 13:32:09 UTC 
Package: gnome-panel
Severity: normal
Version: 0
Synopsis: panel applets crashed
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (1.116.1)

Description:
Description of Problem:

A couple of panel applets seemed to have crashed and disappeared during
loggin:
gweather
command line
date and time
CPU monitor

I believe that the date and time applet was the only one that was added
to the panel yesterday....




Debugging Information:

Backtrace was generated from
'/home/bailey/garnome/bin/multiload-applet-2'

[New Thread 1024 (LWP 18194)]
0x408441d9 in __wait4 () from /lib/i686/libc.so.6

+ Trace 21828

Thread 1 (Thread 1024 (LWP 18194))

  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 593
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 g_logv
    at gmessages.c line 503 




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

Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.
Comment 1 Heath Harrelson 2002-05-07 15:09:38 UTC 
This appears to be a duplicate of bug 76658.  That bug contains a
possible resolution to your problem.

*** This bug has been marked as a duplicate of 76658 ***
Comment 2 Luis Villa 2002-05-17 03:08:19 UTC 
*** Bug 82017 has been marked as a duplicate of this bug. ***