GNOME Bugzilla – Bug 393563
When starting ubuntu, panels appears but don't work.
Last modified: 2007-01-06 23:49:32 UTC
Steps to reproduce: 1. uncompress .iso 2. 3. Stack trace: Memory status: size: 66949120 vsize: 0 resident: 66949120 share: 0 rss: 17481728 rss_rlim: 0 CPU usage: start_time: 1168095365 rtime: 0 utime: 71 stime: 0 cutime:63 cstime: 0 timeout: 8 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) (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 -1225038160 (LWP 5746)] (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) (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) (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) (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 99907
Thread 1 (Thread -1225038160 (LWP 5746))
Other information: Bug Buddy keeps appearing several times (depends how many items in panels, I think). Finally no panels at all, after bug buddy stops it's job! Shortcuts like mozilla firefox and all folders are working but game SuperTux didn't work.
Sorry! SuperTux works fine!!! I don't know how to edit original message!
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 358044 ***
I've installed just about everything "libgnomeui" -things and panels are still not working. Bugreport is now shorter than ever. Memory status: size: 64602112 vsize: 0 resident: 64602112 share: 0 rss: 17502208 rss_rlim: 0 CPU usage: start_time: 1168111194 rtime: 0 utime: 67 stime: 0 cutime:61 cstime: 0 timeout: 6 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) [Thread debugging using libthread_db enabled] [New Thread -1225664848 (LWP 5766)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 99961
Thread 1 (Thread -1225664848 (LWP 5766))
What's your version of libgnomeui? The gentoo bug [1] that was fixed in 2.16.0r1 seems to imply that anything >= 2.16.1 should fix this. To get a proper stacktrace please install debugging symbols for glib, gtk+, and gnome-panel, too. [1] http://bugs.gentoo.org/show_bug.cgi?id=149165
I have installed: libgnomeui-0 2.16.1-0ubuntu2 libgnomeui-0-dbg 2.16.1-0ubuntu2 libgnomeui-common 2.16.1-0ubuntu2 libgnomeui-dev 2.16.1-0ubuntu2 also several ****-dbg, anything that indicates to: glib, gtk+ and gnome-panel And still this is the best I can do: Memory status: size: 64757760 vsize: 0 resident: 64757760 share: 0 rss: 17465344 rss_rlim: 0 CPU usage: start_time: 1168123650 rtime: 0 utime: 68 stime: 0 cutime:60 cstime: 0 timeout: 8 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-panel' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225435472 (LWP 5420)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 100020
Thread 1 (Thread -1225435472 (LWP 5420))
Trace is much better now. Only way to improve it further would be to recompile glib and gtk+ without optimizations. Anyway, I'll mark this as a duplicate again, since the bug that's been closed contains a lot of other duplicates, but I'll reopen the other bug. Please add all further info to that bug. Thanks for your help so far. *** This bug has been marked as a duplicate of 358044 ***