I can confirm that this bug affects Ubuntu 17.10 (which uses Xwayland).
Moreover, replacing the x_get_default(key) function by a “return NULL”
(from the “#ifndef NOT_X_WINDOWS” branch) allows putty to bring up its
setup dialogue. But clicking on open produces another SEGV, with the
following stack trace (line numbers may be a bit off, due to some
fprintfs):
main () at gtkmain.c: 649
new_session_window () at gtkwin.c: 4380
setup_fonts_ucs () at gtkwin.c: 3586
multifont_create () at gtkfont.c: 2196
unifont_create () at gtkfont.c: 2112
x11font_create () at gtkfont.c: 437
XLoadQueryFont () at libX11.so.6
() at libX11,so.6
XInitFontExtension () at libX11.so.6
XQueryExtension () at libX11.so.6
I do not know how to circumvent this. To me it looks like a long way for
Xwayland to become a replacement for XOrg. For the moment, I definitely
need to learn how to switch back to XOrg.
If Xwayland indents to deprecate functions such as XGetDefault() and
XLoadQueryFont() it might be a good idea to issue a message before
throwing a SIG_SEGV.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720905
Title:
putty crashed with SIGSEGV in XGetDefault() under wayland
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/putty/+bug/1720905/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
