GNOME Bugzilla – Bug 495938
crash on gnome-keyboard-properties
Last modified: 2007-11-11 18:28:38 UTC
Steps to reproduce: 1. 2. 3. Stack trace: Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Nuvola Memory status: size: 169345024 vsize: 169345024 resident: 13987840 share: 9367552 rss: 13987840 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194804910 rtime: 7 utime: 7 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-keyboard-properties' (no debugging symbols found) Using host libthread_db library "/lib/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) [Thread debugging using libthread_db enabled] [New Thread 0x2b9870187f50 (LWP 4196)] (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) 0x00002b986945cc45 in waitpid () from /lib/libpthread.so.0
+ Trace 177058
Thread 1 (Thread 0x2b9870187f50 (LWP 4196))
----------- .xsession-errors (93 sec old) --------------------- Предупреждение менеджера окон: 0xc0002a (Нижня) appears to be one of the offending windows with a timestamp of 810891937. Working around... Предупреждение менеджера окон: 0x1c00003 (Устан) appears to be one of the offending windows with a timestamp of 810899839. Working around... Предупреждение менеджера окон: 0x200000c (oleg@debia) appears to be one of the offending windows with a timestamp of 810866443. Working around... Предупреждение менеджера окон: 0x22000cc (Change you) appears to be one of the offending windows with a timestamp of 810228128. Working around... Предупреждение менеджера окон: 0x1e00043 (Списо) appears to be one of the offending windows with a timestamp of 810159726. Working around... Предупреждение менеджера окон: 0x2400003 (Систе) appears to be one of the offending windows with a timestamp of 810166186. Working around... Предупреждение менеджера окон: 0x2600045 (Inbox - Ic) appears to be one of the offending windows with a timestamp of 810397909. Working around... (time-admin:3913): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. (services-admin:4168): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. (synaptic:4101): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed -------------------------------------------------- Other information: debian:/home/oleg# /usr/bin/gnome-keyboard-properties Невозможно запустить менеджер установок "gnome2-settings-daemon". Без менеджера параметров среды GNOME некоторые настройки могут не иметь эффекта. Либо это проблемы с системой Bonobo, либо иной менеджер установок (например, среды KDE) может быть уже запущен и конфликтовать с менеджером установок среды GNOME.
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!