From: Stephen Berman <stephen.berman@gmx.net>
To: 53654@debbugs.gnu.org
Cc: luangruo@yahoo.com
Subject: bug#53654: 29.0.50; Gtk-CRITICAL warnings with non-Gtk tooltips
Date: Mon, 31 Jan 2022 12:31:06 +0100 [thread overview]
Message-ID: <8735l4b0qt.fsf@gmx.net> (raw)
In-Reply-To: <87ilu0dw95.fsf@yahoo.com> (Po Lu via's message of "Mon, 31 Jan 2022 18:39:50 +0800")
On Mon, 31 Jan 2022 18:39:50 +0800 Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> wrote:
> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> (emacs-master:8307): Gtk-CRITICAL **: 10:52:36.874:
>> gtk_widget_set_app_paintable: assertion 'GTK_IS_WIDGET (widget)'
>> failed
>
> This should now be fixed on master.
>
>> (emacs-master:8307): Gtk-CRITICAL **: 10:52:36.879:
>> gtk_im_context_set_cursor_location: assertion 'GTK_IS_IM_CONTEXT
>> (context)' failed
>
> Likewise.
I confirm the warnings are gone now; thanks.
>> 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
>
> BTW, would people install libXi(-devel), configure with
> `--with-xinput2', and use the resulting Emacs for a while? It should
> be stable enough for daily use, but there are certainly minor bugs
> remaining that have to be ironed out, and I can't do that alone.
Is Xinput2 intended to replace Xinput, or is it only for use with touch
pads, touch screens or mice with multiple buttons?
Steve Berman
next prev parent reply other threads:[~2022-01-31 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 10:13 bug#53654: 29.0.50; Gtk-CRITICAL warnings with non-Gtk tooltips Stephen Berman
2022-01-31 10:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-31 11:31 ` Stephen Berman [this message]
2022-01-31 11:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735l4b0qt.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=53654@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).