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 656559 - gnome-settings-daemon crashed with SIGABRT in __kernel_vsyscall()
gnome-settings-daemon crashed with SIGABRT in __kernel_vsyscall()
Status: RESOLVED FIXED
Product: gnome-settings-daemon
Classification: Core
Component: general
3.1.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2011-08-15 12:05 UTC by Pedro Villavicencio
Modified: 2011-12-29 08:08 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description Pedro Villavicencio 2011-08-15 12:05:11 UTC
this report has been filed here:

https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/817707

".

Comment 1 Bastien Nocera 2011-08-30 16:11:08 UTC
The upstream code doesn't match the line numbers in the stacktrace.

http://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/media-keys/gsd-media-keys-manager.c?id=42e9c7074c9026d77edc7a773ef7133fa334f54a#n1301

Can you still reproduce this on a newer version of gnome-settings-daemon?
Comment 2 Pedro Villavicencio 2011-10-03 18:11:55 UTC
new backtrace with 3.2

".

Thread 1 (Thread 0x7f5c1aab9940 (LWP 1878))

  • #0 __GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #1 __GI_abort
    at abort.c line 92
  • #2 g_assertion_message
    at /build/buildd/glib2.0-2.30.0/./glib/gtestutils.c line 1425
  • #3 do_config_power_action
    at gsd-media-keys-manager.c line 1502
  • #4 do_action
    at gsd-media-keys-manager.c line 1789
  • #5 acme_filter_events
    at gsd-media-keys-manager.c line 1875
  • #6 acme_filter_events
    at gsd-media-keys-manager.c line 1842
  • #7 gdk_event_apply_filters
    at /build/buildd/gtk+3.0-3.2.0/./gdk/x11/gdkeventsource.c line 83
  • #8 gdk_event_source_translate_event
    at /build/buildd/gtk+3.0-3.2.0/./gdk/x11/gdkeventsource.c line 204
  • #9 _gdk_x11_display_queue_events
    at /build/buildd/gtk+3.0-3.2.0/./gdk/x11/gdkeventsource.c line 334
  • #10 gdk_display_get_event
    at /build/buildd/gtk+3.0-3.2.0/./gdk/gdkdisplay.c line 311
  • #11 gdk_event_source_dispatch
    at /build/buildd/gtk+3.0-3.2.0/./gdk/x11/gdkeventsource.c line 356
  • #12 g_main_dispatch
    at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 2441
  • #13 g_main_context_dispatch
    at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3011
  • #14 g_main_context_iterate
    at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3089
  • #15 g_main_loop_run
    at /build/buildd/glib2.0-2.30.0/./glib/gmain.c line 3297
  • #16 gtk_main
    at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkmain.c line 1367
  • #17 main
    at main.c line 466

Comment 4 Bastien Nocera 2011-10-07 14:06:24 UTC
Please check with 3.2.1, or cherry-pick those changes.
Comment 5 Akhil Laddha 2011-11-18 06:04:58 UTC
Pedro, did any downstream reporter confirm that problem has been fixed in 3.2.1 ?
Comment 6 Akhil Laddha 2011-12-29 08:08:04 UTC
Please feel free to reopen the bug if it's not fixed with 3.2.1