--- Begin Message ---
Subject: |
29.0.50; Gtk-CRITICAL warnings with non-Gtk tooltips |
Date: |
Mon, 31 Jan 2022 11:13:38 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
0. emacs -Q
1. evaluate this sexp:
(let ((use-system-tooltips))
(tooltip-show "Test"))
=> The shell outputs the following:
(emacs-master:8307): Gtk-CRITICAL **: 10:52:36.874:
gtk_widget_set_app_paintable: assertion 'GTK_IS_WIDGET (widget)' failed
(emacs-master:8307): Gtk-CRITICAL **: 10:52:36.879:
gtk_im_context_set_cursor_location: assertion 'GTK_IS_IM_CONTEXT (context)'
failed
(emacs-master:8307): Gtk-CRITICAL **: 10:52:36.883:
gtk_im_context_set_cursor_location: assertion 'GTK_IS_IM_CONTEXT (context)'
failed
This does not happen with emacs-28 (and also doesn't happen in master
with non-nil use-system-tooltips).
In GNU Emacs 29.0.50 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.31, cairo
version 1.17.4)
of 2022-01-31 built on strobelfs2
Repository revision: 9a56b4e6864c4e0815bb67805cfa67910ab3eeb5
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12101003
System Description: Linux From Scratch r11.0-115
Configured using:
'configure --with-xwidgets 'CFLAGS=-Og -g3'
PKG_CONFIG_PATH=/opt/qt5/lib/pkgconfig'
Configured features:
ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM GSETTINGS HARFBUZZ JPEG
JSON LCMS2 LIBSYSTEMD LIBXML2 MODULES NOTIFY INOTIFY PDUMPER PNG RSVG
SECCOMP SOUND SQLITE3 THREADS TIFF TOOLKIT_SCROLL_BARS WEBP X11 XDBE XIM
XPM XWIDGETS GTK3 ZLIB
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#53654: 29.0.50; Gtk-CRITICAL warnings with non-Gtk tooltips |
Date: |
Mon, 31 Jan 2022 19:42:20 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.60 (gnu/linux) |
Stephen Berman <stephen.berman@gmx.net> writes:
> I confirm the warnings are gone now; thanks.
Thanks, I'm closing this bug report.
> Is Xinput2 intended to replace Xinput, or is it only for use with
> touch pads, touch screens or mice with multiple buttons?
We never used the original XInput API, but yes, it's supposed to replace
both Core Input (which we did use) and the original XInput on all
supported X servers once it's solid enough.
When building with XInput 2 support, the legacy code will remain for the
foreseeable future, but will be disabled if the X server supports XInput
2.
--- End Message ---