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 112441 - Panel crashed one me
Panel crashed one me
Status: RESOLVED DUPLICATE of bug 105745
Product: gnome-panel
Classification: Other
Component: panel
unspecified
Other other
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-05-06 21:57 UTC by lindahl
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description lindahl 2003-05-06 21:57:21 UTC
Package: gnome-panel
Severity: normal
Version: 2.2.0.1
Synopsis: Panel crashed one me
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:

I was innocently typing in Netscape when gnome-panel crashed.

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

Actual Results:


Expected Results:


How often does this happen?


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)...
(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)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 1086393248 (LWP 1062)]

(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)...
(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)...
(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)...0xffffe002 in ?? ()

Thread 1 (Thread 1086393248 (LWP 1062))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #5 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #6 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
  • #13 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-05-06 17:57 -------

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-05-06 22:27:59 UTC
This looks like the mysterious gtk+ crash that is showing up
everywhere [See specifically bug 105745 for more info].

A number of people are getting this, but the stack traces are
unfortunately useless and we don't know how to reproduce the problem.
Can you get a stacktrace with symbols for us?

[If you're using RedHat 9, you can do so with the following easy
method; otherwise this will require recompiling from source:

  Install
  http://people.redhat.com/otaylor/tmp/gtk2-debuginfo-2.2.1-4.i386.rpm
  and if the problem occurs again, submit the backtrace you get.
  Installing the debuginfo package will make the backtrace much more
  useful.]

I am adding myself to the cc and marking as needinfo for now.
Comment 2 Greg Lindahl 2003-05-07 00:16:28 UTC
I have installed the debuginfo package, but the bug is infrequent so I
suspect it won't recurr.

By the way, I would be all in favor of having the debuginfo package be
installed by default -- there's no point in mailing you a pointless
bug report. This laptop did get upgraded from 7.1 -> 7.3 -> 8 -> 9,
perhaps it is the default in fresh installs of 9.
Comment 3 Elijah Newren 2003-05-07 03:33:36 UTC
Thanks.  I know they're fairly rare--I've been sending this email to
all of the 20-30 or so people who have reported this kind of stack
trace.  I'm hoping that at least one can get us one with debugging
symbols.

I agree that it seems like a good default to install debuginfo
packages.   I had to install some on my Red Hat 9 systems (fresh
installs, not upgrades) to get some stack traces for other bugs (I was
lucky enough to track down 107741).  However, I'm not a Red Hat
employee so who knows what they'll do.

Thanks for trying this and let us know if you get anything.  Note that
 this is a gtk+ problem, so it could be any app that randomly crashes.
Comment 4 Alex Duggan 2003-07-02 12:47:45 UTC
If you have any more useful information about these crashes, please
post them in bug 105745.
Comment 5 Alex Duggan 2003-07-02 12:48:05 UTC

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