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 114546 - The rare random crash of gnome panel strikes again
The rare random crash of gnome panel strikes again
Status: RESOLVED DUPLICATE of bug 113328
Product: gnome-panel
Classification: Other
Component: panel
2.2.x
Other other
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-06-06 05:39 UTC by lindahl
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description lindahl 2003-06-06 05:37:30 UTC 
Package: gnome-panel
Severity: normal
Version: 2.2.0.1
Synopsis: The rare random crash of gnome panel strikes again
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:

I was innocently using my computer, and gnome-panel crashed. The first
time I had this happen,
the response was "that's rare, please install debug symbols and report
it!" The second time, I got
"oh, whatever, we don't care". So this is either very important or
completely useless.

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?

Not very often.

Additional Information:




Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 16384 (LWP 1100)]

0x40924567 in waitpid () from /lib/i686/libpthread.so.0

+ Trace 37546

Thread 1 (Thread 16384 (LWP 1100))

  • #0 waitpid
    from /lib/i686/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #3 <signal handler called>
  • #4 gtk_widget_get_toplevel
    at gtkwidget.c line 5356
  • #5 gtk_main_get_window_group
    at gtkmain.c line 1569
  • #6 gtk_main_do_event
    at gtkmain.c line 1394
  • #7 gdk_event_dispatch
    at gdkevents-x11.c line 2018
  • #8 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #12 gtk_main
    at gtkmain.c line 1092
  • #13 main
  • #14 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 waitpid
    from /lib/i686/libpthread.so.0 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-06 01:37 -------

The original reporter (lindahl@keyresearch.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-06-10 04:31:51 UTC 
Awesome!  Thanks for following up on this.  Hopefully these will be
useful to a maintainer (someone smarter than me will have to look at
it and decide).  I'll mention this bug and bug 113328 (the last one
you submitted--I just found it with a search) in bug 105745 and see if
the people there know what to do with this.

In the mean time, I'm setting version->2.2.x, marking priority->high &
severity->critical (it's a crasher), adding GNOMEVER2.2 & STACKTRACE &
bugsquad keywords, and marking as new.
Comment 2 Owen Taylor 2003-06-10 10:51:13 UTC 

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