GNOME Bugzilla – Bug 518601
gconf-editor crashed with SIGSEGV in gdk_window_set_cursor()
Last modified: 2018-07-01 08:39:53 UTC
This bug has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/gconf-editor/+bug/194692 "How to reproduce the bug: 1. Open gconf-editor 2. Open search dialog (CTRL+F) 3. Type something (for example "desktop") 4. Press the "Search" button 5. During search, close the search dialog" "#0 0xb7b4a359 in IA__gdk_window_set_cursor (window=0xaaaaaaaa, cursor=0x0) at /build/buildd/gtk+2.0-2.12.8/gdk/x11/gdkwindow-x11.c:3119 __t = <value optimized out> impl = <value optimized out> xcursor = <value optimized out> __PRETTY_FUNCTION__ = "IA__gdk_window_set_cursor"
+ Trace 190391
Still valid for gconf-editor 2.28.0.
gconf-editor is not under active development anymore and has not seen code changes for six years. Its codebase has been archived: https://gitlab.gnome.org/Archive/gconf-editor/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.