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 112145 - gnome-panel crashed mysteriously
gnome-panel crashed mysteriously
Status: RESOLVED DUPLICATE of bug 105745
Product: gnome-panel
Classification: Other
Component: panel
Other other
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Reported: 2003-04-21 11:01 UTC by Warren Togami
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Warren Togami 2003-05-03 07:32:27 UTC
Package: gnome-panel
Severity: normal
Synopsis: gnome-panel crashed mysteriously
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (

Description of Problem:
After using gnome-panel for about 3 hours, it just crashed for seemingly
no reason while I was using Mozilla.
I am sorry this report isn't more descriptive, submitting the backtraces
just in case they are useful.

Debugging Information:

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

(no debugging symbols found)...[New Thread 1086413856 (LWP 3569)]
0xffffe002 in ?? ()

Thread 1 (Thread 1086413856 (LWP 3569))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/
  • #2 <signal handler called>
  • #3 ??
  • #4 gdk_add_client_message_filter
    from /usr/lib/
  • #5 _gdk_events_queue
    from /usr/lib/
  • #6 _gdk_events_queue
    from /usr/lib/
  • #7 g_get_current_time
    from /usr/lib/
  • #8 g_main_context_dispatch
    from /usr/lib/
  • #9 g_main_context_dispatch
    from /usr/lib/
  • #10 g_main_loop_run
    from /usr/lib/
  • #11 gtk_main
    from /usr/lib/
  • #12 main
  • #13 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 193
  • #0 ??

------- Bug moved to this database by 2003-05-03 03:32 -------

Reassigning to the default owner of the component,

Comment 1 Elijah Newren 2003-05-06 19:39:20 UTC
Setting priority->high & severity->critical.

Warren: This is the same as bug 110984, which you submitted.  A number
of people are getting this (and this seems to be a gtk problem), but
the stack traces are unfortunately useless and we don't know how to
reproduce the problem.  Can you try getting a better stacktrace for
us?  Owen posted the following comment in one of the duplicates on how
to do so:

  Could you install
  and if the problem occurs again, submit the backtrace you get.
  Installing the debuginfo package will make the backtrace much more

I'm adding myself to the cc list so that I can catch any extra info
attached and forward it to where-ever it needs to end up.  Marking as
needinfo for now.
Comment 2 Warren Togami 2003-05-06 19:53:03 UTC
This crash happens so rarely that I haven't been able to reproduce it
since I installed the debuginfo package.  I rebuilt all of the Gnome
SRPMS since April 21st and installed debuginfo.
Comment 3 Elijah Newren 2003-05-06 22:04:22 UTC
Yeah, it seems really rare.  We have approximately 15-30 duplicates of
this spread across at least half a dozen gnome programs.  All of them
describe the bug as "mysterious".  Thanks for trying and let us know
if you ever get a stack trace with debugging symbols.  :)
Comment 4 Alex Duggan 2003-07-02 12:45:51 UTC
If you have any more useful information about these crashes, please
post them in bug 105745.

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