all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: guix-devel@gnu.org
Subject: Re: [PATCH] DRAFT: gnu: icecat: Update to 52.0.2-gnu1; add fixes from ESR 52.1.
Date: Fri, 21 Apr 2017 00:23:34 -0400	[thread overview]
Message-ID: <87bmrq1j95.fsf@netris.org> (raw)
In-Reply-To: <877f2e7lda.fsf@netris.org> (Mark H. Weaver's message of "Thu, 20 Apr 2017 18:41:21 -0400")

Mark H Weaver <mhw@netris.org> writes:

> Mark H Weaver <mhw@netris.org> writes:
>> Here's a draft patch to update GNU IceCat to 52.0.2-gnu1, with
>> additional fixes cherry-picked from upstream ESR 52.1.  It seems to work
>> well on my system, except that my GNOME 3 session has locked up a couple
>> of times while testing it[*].
>
> I built a slightly modified version of this package with 'libnotify'
> support removed (removing it from both 'inputs' and from the
> 'arrange-to-link-libxul-with-libraries-it-might-dlopen' phase), and also
> attempting (but failing) to downgrade to gtk+-2.  The resulting IceCat
> still uses gtk+-3, but so far it has not locked up my GNOME session.
>
> My hypothesis is that when 'libnotify' support is enabled, somehow a bug
> in gnome-shell is triggered.

My experiments so far seem to support this hypothesis.  Since removing
'libnotify' support, I've had no problems with IceCat 52 in GNOME 3.

I've now pushed the IceCat 52 update to master, along with the related
security updates for NSS and Graphite2.

      Mark

  reply	other threads:[~2017-04-21  4:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20  7:43 [PATCH] DRAFT: gnu: icecat: Update to 52.0.2-gnu1; add fixes from ESR 52.1 Mark H Weaver
2017-04-20  8:34 ` Mark H Weaver
2017-04-20 13:17 ` Clément Lassieur
2017-04-20 15:12 ` Maxim Cournoyer
2017-04-20 19:44   ` ng0
2017-04-20 22:41 ` Mark H Weaver
2017-04-21  4:23   ` Mark H Weaver [this message]
2017-04-21 16:18 ` Kei Kebreau
  -- strict thread matches above, loose matches on Subject: below --
2017-04-20 17:21 Petter

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=87bmrq1j95.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.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 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.