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 469898 - crash in Panel:
crash in Panel:
Status: RESOLVED DUPLICATE of bug 422966
Product: gnome-panel
Classification: Other
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-24 13:47 UTC by Alexey Morlender
Modified: 2007-09-02 13:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Alexey Morlender 2007-08-24 13:47:07 UTC 
Version: 2.18.3

What were you doing when the application crashed?



Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.18.3 2007-08-23 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-gentoo-r5 #4 SMP Thu Aug 23 12:39:47 EEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 235429888 vsize: 235429888 resident: 37257216 share: 28188672 rss: 37257216 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187881835 rtime: 2589 utime: 2227 stime: 362 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47021739020272 (LWP 5723)]
0x00002ac41748e322 in __libc_waitpid (pid=397, stat_loc=0x7fff99e8fb4c, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:32
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 157593

Thread 1 (Thread 47021739020272 (LWP 5723))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 32
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #2 <signal handler called>
  • #3 IA__g_str_hash
    at gstring.c line 95
  • #4 IA__g_hash_table_remove
    at ghash.c line 231
  • #5 remove_watch
    at menu-monitor-inotify.c line 325
  • #6 inotify_data_pending
    at menu-monitor-inotify.c line 191
  • #7 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #8 g_main_context_iterate
    at gmain.c line 2677
  • #9 IA__g_main_loop_run
    at gmain.c line 2881
  • #10 IA__gtk_main
    at gtkmain.c line 1154
  • #11 main
    at main.c line 98 


----------- .xsession-errors (80137 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
(18:24:34) oscar: unknown short capability: {134c}
(18:24:34) oscar: unknown capability: {563fc809-0b6f-41bd-9f79-422609dfa2f3}
(18:24:34) oscar: unknown capability: {563fc809-0b6f-4151-4950-203230303561}
(18:24:34) oscar: unknown capability: {d3d45319-8b32-403b-acc7-d1a9e2b5813e}
(18:24:34) oscar: unknown capability: {1a093c6c-d7fd-4ec5-9d51-a6474e34f5a0}
(18:24:34) blist: Updating buddy status for 250590371 (ICQ)
(18:24:34) oscar: unknown capability: {0946134c-4c7f-11d1-8222-444553540000}
(18:24:34) oscar: unknown capability: {563fc809-0b6f-41bd-9f79-422609dfa2f3}
(18:24:34) oscar: unknown capability: {563fc809-0b6f-4151-4950-203230303561}
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Vincent Untz 2007-09-02 13:28:03 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 422966 ***