GNOME Bugzilla – Bug 421712
crash in Panel: loading X
Last modified: 2007-03-26 12:38:46 UTC
Version: 2.18.0 What were you doing when the application crashed? loading X Distribution: Unknown Gnome Release: 2.18.0 2007-03-15 (GNOME.Org) BugBuddy Version: 2.18.0 System: Linux 2.6.19.1 #1 Mon Feb 26 18:49:57 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70100000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Crux Memory status: size: 27750400 vsize: 27750400 resident: 16199680 share: 12447744 rss: 16199680 rss_rlim: 4294967295 CPU usage: start_time: 1174591011 rtime: 148 utime: 109 stime: 39 cutime:0 cstime: 0 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 -1226762576 (LWP 17621)] 0xb7fd9410 in __kernel_vsyscall ()
+ Trace 121314
Thread 1 (Thread -1226762576 (LWP 17621))
----------- .xsession-errors (4306621 sec old) --------------------- Call Backtrace : CALL#: ADDRESS: FUNCTION: 0 0xA7DF602F [/usr/lib/libX11.so.6(_XError+0xff) [0xa7df602f]] 1 0xA7DF660F [/usr/lib/libX11.so.6(_XReply+0x18f) [0xa7df660f]] 2 0xA7DDE5E9 [/usr/lib/libX11.so.6(XListProperties+0x69) [0xa7dde5e9]] 3 0x08075EC5 [/usr/bin/WinList(collect_hints+0xa5) [0x8075ec5]] 4 0x08061B70 [/usr/bin/WinList(configure_tbar_icon+0xd0) [0x8061b70]] 5 0x080623A1 [/usr/bin/WinList [0x80623a1]] 6 0x080625B5 [/usr/bin/WinList(refresh_winlist_button+0x55) [0x80625b5]] 7 0x0806283D [/usr/bin/WinList(process_message+0x17d) [0x806283d]] 8 0x0808E400 [/usr/bin/WinList(module_wait_pipes_input+0x180) [0x808e400]] 9 0x08062F5E [/usr/bin/WinList(HandleEvents+0x4e) [0x8062f5e]] 10 0x0806310D [/usr/bin/WinList(main+0x16d) [0x806310d]] 11 0xA7C0EE00 [/lib/libc.so.6(__libc_start_main+0xd0) [0xa7c0ee00]] 12 0x08060701 [/usr/bin/WinList [0x8060701]] --------------------------------------------------
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 413921 ***