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 81993 - panel , again
panel , again
Status: RESOLVED DUPLICATE of bug 59500
Product: gnome-panel
Classification: Other
Component: panel
unspecified
Other other
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-05-16 17:59 UTC by vjimenez
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description vjimenez 2002-05-16 17:58:01 UTC 
Package: gnome-panel
Severity: normal
Version: 1.4.0.6
Synopsis: panel , again
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel

Description:
once opening staroffice



Debugging Information:

(no debugging symbols found)...0x405ab319 in ?? ()

+ Trace 22253

  • #0 ??
  • #1 ??
  • #2 <signal handler called>
  • #3 ??
  • #4 gwmh_task_notifier_remove_func
  • #5 gwmh_task_iconify
  • #6 gwmh_root_put_atom_window
  • #7 gwmh_task_notifier_remove_func
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 panel_clean_applet
  • #14 ??
  • #0 ??
  • #1 ??
  • #2 <signal handler called>
  • #3 ??
  • #4 gwmh_task_notifier_remove_func
  • #5 gwmh_task_iconify
  • #6 gwmh_root_put_atom_window
  • #7 gwmh_task_notifier_remove_func 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-05-16 13:58 -------

The original reporter (vjimenez@cie.com.mx) 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-05-19 07:38:15 UTC 
Please try the latest 1.4.x releases of gnome-libs and gnome-core.
I've made RPMs available at http://www.gnome.org/~kmaraas if you can
make use of those. Also report back here whether the upgrade fixes the
problem for you.


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