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 487049 - crash in Panel:
crash in Panel:
Status: RESOLVED INCOMPLETE
Product: gnome-panel
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 487243 493905 498592 503257 503736 504884 505003 508373 508603 518293 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-10-16 05:52 UTC by Cyrille Chépélov
Modified: 2008-02-23 22:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Cyrille Chépélov 2007-10-16 05:52:26 UTC
Version: 2.20.0.1

What were you doing when the application crashed?



Distribution: redhat-4
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22.1 #1 SMP Sun Jul 22 23:41:14 CEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: Lush

Memory status: size: 408805376 vsize: 408805376 resident: 22122496 share: 7544832 rss: 22122496 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191656001 rtime: 291224 utime: 276401 stime: 14823 cutime:0 cstime: 33 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b7e46632ea0 (LWP 27856)]
[New Thread 0x40040950 (LWP 4245)]
(no debugging symbols found)
0x00002b7e40535c7f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b7e46632ea0 (LWP 27856))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_slist_remove
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gnome-panel/libclock-applet.so
  • #5 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #6 ??
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 ??
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/libedataserver-1.2.so.9
  • #14 ??
    from /usr/lib/libORBit-2.so.0
  • #15 ??
    from /usr/lib/libORBit-2.so.0
  • #16 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #17 ??
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 main
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (2474823 sec old) ---------------------
(evolution-2.10:7555): camel-imap-provider-WARNING **: No information for message 13
*** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Connection closed
*** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Connection closed
(evolution-2.10:7555): camel-imap-provider-WARNING **: No information for message 13
(evolution-2.10:7555): camel-imap-provider-WARNING **: No information for message 13
*** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Connection closed
*** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Connection closed
(evolution-2.10:7555): camel-imap-provider-WARNING **: No information for message 13
(evolution-2.10:7555): camel-imap-provider-WARNING **: No information for message 13
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Vincent Untz 2007-10-16 06:10:31 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Philip Withnall 2008-01-11 06:58:00 UTC
*** Bug 508603 has been marked as a duplicate of this bug. ***
Comment 3 Philip Withnall 2008-01-11 06:58:04 UTC
*** Bug 508373 has been marked as a duplicate of this bug. ***
Comment 4 Philip Withnall 2008-01-11 06:58:37 UTC
*** Bug 504884 has been marked as a duplicate of this bug. ***
Comment 5 Philip Withnall 2008-01-11 06:58:58 UTC
*** Bug 487243 has been marked as a duplicate of this bug. ***
Comment 6 Philip Withnall 2008-01-11 07:00:32 UTC
*** Bug 493905 has been marked as a duplicate of this bug. ***
Comment 7 Philip Withnall 2008-01-11 07:00:38 UTC
*** Bug 498592 has been marked as a duplicate of this bug. ***
Comment 8 Philip Withnall 2008-01-11 07:00:42 UTC
*** Bug 503257 has been marked as a duplicate of this bug. ***
Comment 9 Philip Withnall 2008-01-11 07:00:48 UTC
*** Bug 503736 has been marked as a duplicate of this bug. ***
Comment 10 Philip Withnall 2008-01-11 07:01:39 UTC
*** Bug 505003 has been marked as a duplicate of this bug. ***
Comment 11 Philip Withnall 2008-02-23 22:55:42 UTC
*** Bug 518293 has been marked as a duplicate of this bug. ***