unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: 37545@debbugs.gnu.org
Subject: bug#37545: epiphany and next broken after webkitgtk upgrade to 2.26.1
Date: Sat, 28 Sep 2019 14:51:52 -0700	[thread overview]
Message-ID: <87lfu8um13.fsf@ponder> (raw)

[-- Attachment #1: Type: text/plain, Size: 1779 bytes --]

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@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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

             reply	other threads:[~2019-09-28 21:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-28 21:51 Vagrant Cascadian [this message]
2019-09-29  6:55 ` bug#37545: epiphany and next broken after webkitgtk upgrade to 2.26.1 Vagrant Cascadian
2019-10-02 12:23   ` Ludovic Courtès
2019-10-02 15:51     ` Vagrant Cascadian
2019-10-06 16:06       ` Marius Bakke
2019-10-08  6:30         ` Vagrant Cascadian
2019-10-08  6:09 ` Bradley Haggerty
2019-10-08  9:01   ` Marius Bakke

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=87lfu8um13.fsf@ponder \
    --to=vagrant@debian.org \
    --cc=37545@debbugs.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 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).