From: "Ludovic Courtès" <ludo@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 34454@debbugs.gnu.org, Joshua Branson <jbranso@dismail.de>,
Bradley Haggerty <bradigger@gmail.com>,
34528@debbugs.gnu.org, 34658@debbugs.gnu.org
Subject: bug#34454: Gtk upstream bug #1280 causes crashes in IceCat and Emacs
Date: Sun, 31 Mar 2019 12:07:57 +0200 [thread overview]
Message-ID: <87r2an2w76.fsf@gnu.org> (raw)
In-Reply-To: <87muld58gn.fsf@netris.org> (Mark H. Weaver's message of "Fri, 29 Mar 2019 23:47:25 -0400")
Hi Mark,
Mark H Weaver <mhw@netris.org> skribis:
> I looked into this, and I believe all of these bugs are caused by Gtk
> upstream bug #1280:
>
> https://gitlab.gnome.org/GNOME/gtk/issues/1280
>
> which is apparently fixed by the following upstream commit:
>
> https://gitlab.gnome.org/GNOME/gtk/commit/e3a1593a0984cc0156ec1892a46af8f256a64878
Woow, thanks for tracking it down and for pushing a fix!
Ludo’.
next prev parent reply other threads:[~2019-03-31 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 16:01 bug#34528: Icecat is crashing on search Joshua Branson
2019-03-30 3:47 ` bug#34528: Gtk upstream bug #1280 causes crashes in IceCat and Emacs Mark H Weaver
2019-03-30 4:56 ` bug#34454: " Carlo Zancanaro
2019-03-30 6:41 ` Mark H Weaver
2019-03-31 10:07 ` Ludovic Courtès [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-12 10:16 bug#34454: After an update, icecat now segfaults very quickly after opening Bradley Haggerty
2019-03-30 4:22 ` bug#34454: Gtk upstream bug #1280 causes crashes in IceCat and Emacs Mark H Weaver
2019-03-31 8:52 ` Bradley Haggerty
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2an2w76.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=34454@debbugs.gnu.org \
--cc=34528@debbugs.gnu.org \
--cc=34658@debbugs.gnu.org \
--cc=bradigger@gmail.com \
--cc=jbranso@dismail.de \
--cc=mhw@netris.org \
/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/guix.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).