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 366658 - gnome-panel crash everytime
gnome-panel crash everytime
Status: RESOLVED DUPLICATE of bug 358044
Product: gnome-panel
Classification: Other
Component: panel
2.16.x
Other All
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-29 05:29 UTC by Chen Xingrun
Modified: 2006-10-29 15:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Chen Xingrun 2006-10-29 05:29:18 UTC 
Steps to reproduce:
1. upgrade from ubuntu dapper to edgy
2. i use the ubuntu6.10.iso as the update source
3. now i can't use gnome-panel at all.


Stack trace:
Memory status: size: 79269888 vsize: 0 resident: 79269888 share: 0 rss: 17108992 rss_rlim: 0
CPU usage: start_time: 1161925040 rtime: 0 utime: 78 stime: 0 cutime:74 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1225058640 (LWP 16826)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 79576

Thread 1 (Thread -1225058640 (LWP 16826))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 *__GI_raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 *__GI_abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_recent_info_get_short_name
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 gtk_recent_info_get_display_name
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_recent_chooser_menu_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #17 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 main
  • #0 __kernel_vsyscall 


Other information:
Comment 1 André Klapper 2006-10-29 15:16:04 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.

Upgrading to libgnomeui-2.16 and libgnomeui-2.16 should fix this.

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