GNOME Bugzilla – Bug 518637
crash in media keys on resume?
Last modified: 2008-02-28 20:43:46 UTC
It crashes every time I close my laptop (lid). (Actually g-s-d crashes when the lid is opened after being closed) bug buddy trace: --------------------------- System: Linux 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 48476160 vsize: 48476160 resident: 17797120 share: 9482240 rss: 17797120 rss_rlim: 4294967295 CPU usage: start_time: 1203938584 rtime: 285 utime: 220 stime: 65 cutime:28 cstime: 12 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-settings-daemon' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6f0c720 (LWP 5434)] [New Thread 0xb6159b90 (LWP 5444)] 0xb7f60410 in __kernel_vsyscall ()
+ Trace 190406
Thread 1 (Thread 0xb6f0c720 (LWP 5434))
----------- .xsession-errors --------------------- info_labels = map (make_info_label, self.system_infos) File "/usr/bin/gnome-about", line 920, in make_info_label label.set_markup (_("<b>%(name)s:</b> %(value)s") % infos_dict) KeyError: u'nome' checking for valid crashreport now gnome-about checking for valid crashreport now ** ** ERROR:(gsd-media-keys-manager.c:907):do_action: code should not be reached [1203938586,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application warning: .dynamic section for "/usr/lib/libgstreamer-0.10.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgstbase-0.10.so.0" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
That looks like something is seriously broken on your side (tbh, the library warnings you get there don't look that great, either). Still, can you please try to get such a stacktrace from an unoptimized build? Thanks.
I can't see how this would happen, unless the keys structure, or "i" (as used in acme_filter_events()) got trashed. Could you attach gdb to gnome-settings-daemon and when it crashed, check what value "i" has in acme_filter_events(). Also could you check whether the keys structure contains valid data (the structure in in actions/acme.h, and a type is probably changed by something there).
Created attachment 106190 [details] Backtrace that is'nt optimized. This crash is very similar to the reporter, but instead happens when pressing FN-F8 (XF86Display)
Ok, this is very much NOTGNOME. Ubuntu applies a broken patch. Please complain to them.