GNOME Bugzilla – Bug 654929
strcmp: Process /usr/bin/gpointing-device-settings was killed by signal 11 (SIGSEGV)
Last modified: 2018-08-17 18:38:37 UTC
Created attachment 192267 [details] [review] fix for strcmp_no_device In function gpds_xinput_utils_get_device_info, the variable device can be a NULL pointer and strcmp will crash at that point. See fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=722770 The attached patch should fix this or can this be fixed somehow different?
By the way, there are some other user warnings, that might be related to the NULL pointer occurrence: (gpointing-device-settings:2722): Gtk-CRITICAL **: gtk_list_store_get_path: assertion `iter->stamp == GTK_LIST_STORE (tree_model)->stamp' failed (gpointing-device-settings:2722): Gtk-CRITICAL **: IA__gtk_icon_view_select_path: assertion `path != NULL' failed
GPointingDeviceSettings is not under active development anymore and saw its last non-cosmetic code changes in 2010. Its codebase has been archived: https://gitlab.gnome.org/Archive/gpointing-device-settings/commits/master Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.