After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 518637 - crash in media keys on resume?
crash in media keys on resume?
Product: gnome-settings-daemon
Classification: Core
Component: plugins
Other Linux
: Normal critical
: ---
Assigned To: gnome-settings-daemon-maint
Depends on:
Reported: 2008-02-25 15:30 UTC by Jonh Wendell
Modified: 2008-02-28 20:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22

Backtrace that is'nt optimized. (24.78 KB, text/plain)
2008-02-28 20:12 UTC, Mario Limonciello

Description Jonh Wendell 2008-02-25 15:30:08 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/".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6f0c720 (LWP 5434)]
[New Thread 0xb6159b90 (LWP 5444)]
0xb7f60410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6f0c720 (LWP 5434))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/
  • #2 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.15.5/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.15.5/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/
  • #5 <signal handler called>
  • #6 __kernel_vsyscall
  • #7 raise
    from /lib/tls/i686/cmov/
  • #8 abort
    from /lib/tls/i686/cmov/
  • #9 IA__g_assertion_message
    at /build/buildd/glib2.0-2.15.5/glib/gtestutils.c line 1166
  • #10 acme_filter_events
    at gsd-media-keys-manager.c line 907
  • #11 gdk_event_apply_filters
    at /build/buildd/gtk+2.0-2.12.8/gdk/x11/gdkevents-x11.c line 345
  • #12 gdk_event_translate
    at /build/buildd/gtk+2.0-2.12.8/gdk/x11/gdkevents-x11.c line 984
  • #13 _gdk_events_queue
    at /build/buildd/gtk+2.0-2.12.8/gdk/x11/gdkevents-x11.c line 2285
  • #14 gdk_event_dispatch
    at /build/buildd/gtk+2.0-2.12.8/gdk/x11/gdkevents-x11.c line 2345
  • #15 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.15.5/glib/gmain.c line 2064
  • #16 g_main_context_iterate
    at /build/buildd/glib2.0-2.15.5/glib/gmain.c line 2697
  • #17 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.15.5/glib/gmain.c line 2905
  • #18 IA__gtk_main
    at /build/buildd/gtk+2.0-2.12.8/gtk/gtkmain.c line 1163
  • #19 main
  • #0 __kernel_vsyscall

----------- .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
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/" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/" is not at the expected address (wrong library or version mismatch?)
Comment 1 Jens Granseuer 2008-02-26 21:05:51 UTC
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.
Comment 2 Bastien Nocera 2008-02-28 19:34:04 UTC
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).
Comment 3 Mario Limonciello 2008-02-28 20:12:31 UTC
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)
Comment 4 Jens Granseuer 2008-02-28 20:43:46 UTC
Ok, this is very much NOTGNOME. Ubuntu applies a broken patch. Please complain to them.