From: Mark H Weaver <mhw@netris.org>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: 34454@debbugs.gnu.org, Joshua Branson <jbranso@dismail.de>,
Bradley Haggerty <bradigger@gmail.com>
Subject: bug#34454: Gtk upstream bug #1280 causes crashes in IceCat and Emacs
Date: Sat, 30 Mar 2019 02:41:13 -0400 [thread overview]
Message-ID: <87y34w984b.fsf@netris.org> (raw)
In-Reply-To: <87imw155a6.fsf@zancanaro.id.au> (Carlo Zancanaro's message of "Sat, 30 Mar 2019 15:56:33 +1100")
Hi Carlo,
Carlo Zancanaro <carlo@zancanaro.id.au> writes:
> Thanks so much for taking a look at this!
>
> On Sat, Mar 30 2019, Mark H Weaver wrote:
>> If those affected by this issue would like to test this patch and
>> report back, that would be helpful.
>
> I applied your patch to my local Guix, and everything is working fine
> again. I had been working around the problem by using
> emacs-no-x-toolkit, but with your patch I can use the normal emacs
> package again without issues.
Great, thanks for the report! Based on this, I went ahead and pushed a
slightly improved patch, commit bc91562939ee002e84c95d13c907482b6d1e9339
on the master branch.
Joshua and Bradley: you should be able to simply "guix pull" and then
update your IceCat package, and hopefully the problem will be fixed.
Please let us know.
Thanks!
Mark
next prev parent reply other threads:[~2019-03-30 6:43 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 [this message]
2019-03-31 10:07 ` Ludovic Courtès
-- 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y34w984b.fsf@netris.org \
--to=mhw@netris.org \
--cc=34454@debbugs.gnu.org \
--cc=bradigger@gmail.com \
--cc=carlo@zancanaro.id.au \
--cc=jbranso@dismail.de \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.