GNU bug report logs - #37545
epiphany and next broken after webkitgtk upgrade to 2.26.1

Previous Next

Package: guix;

Reported by: Vagrant Cascadian <vagrant <at> debian.org>

Date: Sat, 28 Sep 2019 21:53:02 UTC

Severity: normal

Done: Vagrant Cascadian <vagrant <at> debian.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Vagrant Cascadian <vagrant <at> debian.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#37545: closed (epiphany and next broken after webkitgtk
 upgrade to 2.26.1)
Date: Tue, 08 Oct 2019 06:32:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Mon, 07 Oct 2019 23:30:52 -0700
with message-id <87sgo3vjdv.fsf <at> yucca>
and subject line Re: bug#37545: epiphany and next broken after webkitgtk upgrade to 2.26.1
has caused the debbugs.gnu.org bug report #37545,
regarding epiphany and next broken after webkitgtk upgrade to 2.26.1
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
37545: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=37545
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Vagrant Cascadian <vagrant <at> debian.org>
To: bug-guix <at> gnu.org
Cc: Marius Bakke <mbakke <at> fastmail.com>
Subject: epiphany and next broken after webkitgtk upgrade to 2.26.1
Date: Sat, 28 Sep 2019 14:51:52 -0700
[Message part 3 (text/plain, inline)]
Both next and epiphany are very broken for me after the upgrade to
webkitgtk to 2.26.1.

I first noticed when running core-updates, but then also tested on
master (de3896fb79984d545e7fec0b5e4f1ba37983fbce) with the same result.

$ guix describe
Generation 240  Sep 27 2019 20:47:30    (current)
  guix 60643d1
    repository URL: file:///home/vagrant/src/guix
    commit: 60643d1b1930c54789c8262ae68457fe0c85fae0
$ guix package -I epiphany
epiphany        3.30.4  out
/gnu/store/vc6caa4n1jkqkvzjg03d9j5m93k8g6g0-epiphany-3.30.4
$ epiphany

** (epiphany:16759): WARNING **: 21:18:10.796:
   webkit_web_context_set_web_process_count_limit is deprecated and d
wpe_loader_init could not load the library 'libWPEBackend-fdo-1.0.so':
   libWPEBackend-fdo-1.0.so: cannot open shar
wpe: could not load the impl library. Is there any backend installed?:
   libWPEBackend-default.so: cannot open shar
Aborted

I don't have a capture of the "next" browser output handy, but it wasn't
working either.

I also tried building without grafts, just in case, but no difference.


Reverting the following commit causes both browsers to work again.

commit 689b44bc3fe50de86c8c8b8c2ac503b2e82d7975
Author: Marius Bakke <mbakke <at> fastmail.com>
Date:   Thu Sep 26 16:40:45 2019 +0200

    gnu: WebKitGTK: Update to 2.26.1.

    * gnu/packages/webkit.scm (webkitgtk-2.24): Rename to ...
    (webkitgtk-2.26): ... this.  Update to 2.26.1.
    [inputs]: Add BUBBLEWRAP, LIBSECCOMP, LIBWPE, WPEBACKEND-FDO, and
    XDG-DBUS-PROXY.
    * gnu/packages/gnome.scm (eolie, epiphany)[inputs]: Adjust for
    changed
    variable name.
    * gnu/packages/web-browsers.scm (next-gtk-webkit)[inputs]: Likewise.


Maybe libwpe and/or wpebackend-fdo aren't added in (all) the correct
place(s)?


live well,
  vagrant
[signature.asc (application/pgp-signature, inline)]
[Message part 5 (message/rfc822, inline)]
From: Vagrant Cascadian <vagrant <at> debian.org>
To: Marius Bakke <mbakke <at> fastmail.com>, Ludovic Courtès
 <ludo <at> gnu.org>
Cc: 37545-done <at> debbugs.gnu.org
Subject: Re: bug#37545: epiphany and next broken after webkitgtk upgrade to
 2.26.1
Date: Mon, 07 Oct 2019 23:30:52 -0700
[Message part 6 (text/plain, inline)]
On 2019-10-06, Marius Bakke wrote:
> Vagrant Cascadian <vagrant <at> debian.org> writes:
>> It breaks running under wayland, and unsetting WAYLAND_DISPLAY it works
>> fine:
>>
>>   WAYLAND_DISPLAY= epiphany
>>
>> Or switching to an x11 session rather than wayland also worked fine.
>>
>> Does it work for other people under wayland, or just x11?
>>
>> More specifically, I'm running a "sway (wayland)" session from sddm as
>> the login manager.
>
> I believe this is fixed by 1714edc3d4e8d6da1b0cdef300ae882d0885f182.
> Can you confirm?

After that commit it's been working again, thanks!

live well,
  vagrant
[signature.asc (application/pgp-signature, inline)]

This bug report was last modified 5 years and 224 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.