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 533580 - crash in Panel: Нажал на кнопку приложен...
crash in Panel: Нажал на кнопку приложен...
Status: RESOLVED DUPLICATE of bug 378854
Product: gnome-panel
Classification: Other
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-17 15:35 UTC by matveiy1
Modified: 2008-05-17 17:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description matveiy1 2008-05-17 15:35:24 UTC 
Version: 2.20.3

What were you doing when the application crashed?
Нажал на кнопку приложения в трее.


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Fri Apr 18 23:08:22 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: black-white_2-Style

Memory status: size: 358486016 vsize: 358486016 resident: 27435008 share: 16171008 rss: 27435008 rss_rlim: 18446744073709551615
CPU usage: start_time: 1210855545 rtime: 5618 utime: 4954 stime: 664 cutime:0 cstime: 8 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 0x2ad7e48dcd40 (LWP 3620)]
[New Thread 0x40040950 (LWP 12517)]
(no debugging symbols found)
0x00002ad7de45cedf in waitpid () from /lib/libpthread.so.0

+ Trace 197968

Thread 1 (Thread 0x2ad7e48dcd40 (LWP 3620))

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


----------- .xsession-errors (182767 sec old) ---------------------
(evolution:3814): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3814): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3814): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3814): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3814): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3814): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3814): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Philip Withnall 2008-05-17 17:10:04 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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