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 99030 - Gnome panel crashed after removing Redhat's update icon
Gnome panel crashed after removing Redhat's update icon
Status: RESOLVED DUPLICATE of bug 94422
Product: gnome-panel
Classification: Other
Component: panel
2.0.x
Other Linux
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-11-19 20:44 UTC by Elijah Newren
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Description Elijah Newren 2002-11-19 20:44:29 UTC 
I was surprised to get this, as I've removed Red hat's update icon before
without problems.  Also, there was a one or two second delay between
removing the redhat update icon and when I got the message saying the panel
crashed that sent me here (in other words, I'm not sure if they're actually
related, but if they're not, then this is a spontaneous crash).  After
clicking okay on the popup message that came up, the panel disappeared and
then reappeared and is now running without problems.

I don't have a lot of time at the moment to check if this is a duplicate or
anything.  Anyway, Redhat 8.0 uses gnome-panel-2.0.6.  Let me know if you
need any other information.
Comment 1 Vincent Untz 2002-11-19 20:48:36 UTC 
Elijah: well, a stack trace would be welcomed.
Comment 2 Elijah Newren 2002-11-19 21:59:49 UTC 
Apparently no core file was generated (I tried a 'find / -name
"*core*"' as root and looked through all those files but none of them
was a core dump).  Without that, I have no clue how to get a stack
trace.  I'll try to reproduce when I'm finished with a couple things
I'm running, but since it seemed somewhat spontaneous, I'm not so sure
I'll be able to reproduce the bug.

Feel free to close this if this isn't enough information--I'm not sure
I can provide more and the panel seems to be working now...
Comment 3 Elijah Newren 2002-11-19 22:57:18 UTC 
Well, I reproduced it.  First try too.  This time, I had bug-buddy
installed.  I'll check the simple-dup-finder in a minute to see if
this might be a duplicate.  Here's the stack trace that bug-buddy
obtained:

Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)...(no debugging symbols found)...[New
Thread 8192 (LWP 1001)]

0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 30671

Thread 1 (Thread 8192 (LWP 1001))

  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    from /lib/i686/libpthread.so.0
  • #3 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #4 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #5 <signal handler called>
  • #6 g_type_check_instance_is_a
    from /usr/lib/libgobject-2.0.so.0
  • #7 gdk_x11_drawable_get_xid
    from /usr/lib/libgdk-x11-2.0.so.0
  • #8 send_xembed_message
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 toplevel_focus_out_handler
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 gtk_signal_emit
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_widget_event_internal
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gdk_event_dispatch
    from /usr/lib/libgdk-x11-2.0.so.0
  • #18 g_main_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #21 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #22 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 main
  • #24 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6 






Comment 4


Elijah Newren





          2002-11-19 23:07:26 UTC
        



Sorry for the spam.  The way I know to check for duplicates (the
simple-dup-finder) requires that all the information already be filed
in the bug.  Anyway, the simple-dup-finder lists the bugs #94924 and
#95345, both of which have been marked as duplicates of #94422.  So
I'm marking this as a duplicate of that one.


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