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 107412 - After clicking to maximize a window in the gnome panel, it crashed.
After clicking to maximize a window in the gnome panel, it crashed.
Status: RESOLVED DUPLICATE of bug 94422
Product: gnome-panel
Classification: Other
Component: panel
unspecified
Other other
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-03-02 20:02 UTC by higgy001
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description higgy001 2003-03-02 19:55:54 UTC
Package: gnome-panel
Severity: major
Version: 2.0.6
Synopsis: After clicking to maximize a window in the gnome panel, it crashed.
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
The panel crashes, sometimes it comes back, but others I have to restart
the computer. (restarting the X server doesn't work)

Steps to reproduce the problem:
1.log into gnome
2.open up Limewire and gaim
3.click to maximize a windows

Actual Results:


Expected Results:


How often does this happen?
Almost every time I boot up with Redhat 8.0, I get this error, often
with different applications or after different actions.

Additional Information:




Debugging Information:

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

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

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

Thread 1 (Thread 8192 (LWP 958))

  • #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 gdk_x11_drawable_get_xid
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 send_xembed_message
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 toplevel_focus_in_handler
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 gtk_signal_emit
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_widget_event_internal
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gdk_event_dispatch
    from /usr/lib/libgdk-x11-2.0.so.0
  • #17 g_main_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #21 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 main
  • #23 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-03-02 14:55 -------

The original reporter (higgy001@hotmail.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 Elijah Newren 2003-03-03 19:49:24 UTC
Thanks for the bug report--this happens to be a duplicate of a bug
that has been rather elusive.  If you could look through bug 94422,
and see if you can answer any so far unanswered questions or provide
any extra information, it would be greatly appreciated.

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