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 112396 - Panel crash for no obvious reason
Panel crash for no obvious reason
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 12:05 UTC by David Eriksson
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Eriksson 2003-05-06 12:05:56 UTC
Package: gnome-panel
Severity: normal
Version: 2.2.0.1
Synopsis: Panel crash for no obvious reason
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:

The panel just crashed. I was writing in a terminal at the time.



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 1086397344 (LWP 3382)]

(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 1086397344 (LWP 3382))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gdk_event_get_graphics_expose
    from /usr/lib/libgdk-x11-2.0.so.0
  • #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 08:05 -------

Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.

Comment 1 Elijah Newren 2003-05-06 15:44:23 UTC
Thanks for the bug report. This particular bug has already been
reported into our bug tracking system, but please feel free to report
any further bugs you find.

*** This bug has been marked as a duplicate of 107741 ***
Comment 2 Elijah Newren 2003-05-06 15:47:07 UTC
Doh!  I'm a moron.  Sorry I had two bugs opened and I pasted that and
marked the wrong one.  bug 112413 is a dup of 107741, not this one. 
Reopening so I can mark this one appropriately.
Comment 3 Elijah Newren 2003-05-06 15:50:40 UTC
This is a duplicate of bug 107498, but I'm going to mark it as
needinfo instead since Owen says we really need a stack trace with
Debugging symbols.  David: Any chance you could get us a stack trace
with debugging symbols?  (A little more information about this can be
found at http://bugzilla.gnome.org/getting-traces.cgi).
Comment 4 David Eriksson 2003-05-06 16:12:25 UTC
I'm on a RedHat 9 system so I guess I have to build some RPM:s from
source with -g and make sure that they don't get stripped. I'll start
with the gtk2 and libgnomeui RPMs.

The major problem is that I can do nothing but wait until the crash
occurs again, because I have no clue on how to reproduce it.
Comment 5 Elijah Newren 2003-05-06 22:01:55 UTC
David: you don't actually need to rebuild from source.  RedHat 9
introduced the ability to installing debugging information rpms along
side normal rpms.  Owen added a comment in bug 110032 about how to do
this (note that 110032 is also a duplicate of 107498, just like your
bug).  Here was his comment:

  Could you 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 understand that you're not sure how to reproduce (everyone that has
reported this say that it's a "mysterious crash").  However, we're
starting to get multiple reports from the same people, meaning that it
should eventually happen again.  Just install that debuginfo rpm and
wait.  :)
Comment 6 Alex Duggan 2003-07-02 12:47:18 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 ***