GNOME Bugzilla – Bug 450569
crash in Panel: gnome was starting
Last modified: 2007-06-24 10:24:35 UTC
Version: 2.18.1 What were you doing when the application crashed? gnome was starting Distribution: Mandriva Linux release 2007.1 (Official) for i586 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.17-13mdv #1 SMP Fri Mar 23 19:03:31 UTC 2007 i686 X Vendor: The X.Org Group X Vendor Release: 6600 Selinux: No Accessibility: Disabled GTK+ Theme: Ia Ora Blue Icon Theme: gnome Memory status: size: 35766272 vsize: 35766272 resident: 13099008 share: 10067968 rss: 13099008 rss_rlim: 4294967295 CPU usage: start_time: 1182678868 rtime: 21 utime: 19 stime: 2 cutime:0 cstime: 0 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/i686/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226778944 (LWP 5640)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 143304
Thread 1 (Thread -1226778944 (LWP 5640))
----------- .xsession-errors --------------------- SIOCETHTOOL: Operacja niedozwolona SIOCETHTOOL: Operacja niedozwolona Nie ustawiono wartości dla "/desktop/gnome/interface/document_font_name" Nie ustawiono wartości dla "/system/proxy/mode" Nie ustawiono wartości dla "/system/proxy/mode" Nie ustawiono wartości dla "/system/proxy/mode" Nie ustawiono wartości dla "/system/proxy/mode" Nie ustawiono wartości dla "/system/proxy/mode" Nie ustawiono wartości dla "/system/proxy/mode" Nie ustawiono wartości dla "/system/proxy/mode" Nie ustawiono wartości dla "/system/proxy/mode" Nie ustawiono wartości dla "/system/proxy/mode" Nie ustawiono wartości dla "/system/proxy/mode" Nie ustawiono wartości dla "/system/proxy/mode" Nie ustawiono wartości dla "/system/proxy/mode" --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 419622 ***