GNU bug report logs -
#37545
epiphany and next broken after webkitgtk upgrade to 2.26.1
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 37545 in the body.
You can then email your comments to 37545 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#37545
; Package
guix
.
(Sat, 28 Sep 2019 21:53:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Vagrant Cascadian <vagrant <at> debian.org>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Sat, 28 Sep 2019 21:53:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (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)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#37545
; Package
guix
.
(Sun, 29 Sep 2019 06:56:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 37545 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 2019-09-28, Vagrant Cascadian wrote:
> Both next and epiphany are very broken for me after the upgrade to
> webkitgtk to 2.26.1.
...
> $ 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.
Ok, a little further ...
guix environment --ad-hoc epiphany
Still fails in the same way... but!
guix environment --pure --ad-hoc epiphany
Works fine!
So something in the... environment variables is causing problems? XDG*?
More debugging another day...
live well,
vagrant
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#37545
; Package
guix
.
(Wed, 02 Oct 2019 12:24:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 37545 <at> debbugs.gnu.org (full text, mbox):
Hi Vagrant!
Vagrant Cascadian <vagrant <at> debian.org> skribis:
> Ok, a little further ...
>
> guix environment --ad-hoc epiphany
It works for me on ‘core-updates’
ece22ac8ccb6744eaec0320f0c7c9b6680fffa46, but note that my system and
user profile were already on ‘core-updates’, so presumably that avoids
problems with XDG_*.
> Still fails in the same way... but!
>
> guix environment --pure --ad-hoc epiphany
>
> Works fine!
This works fine for me too:
guix environment -E DISPLAY -E XAUTHORITY --ad-hoc epiphany --pure -- epiphany
So… problem solved?
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#37545
; Package
guix
.
(Wed, 02 Oct 2019 15:52:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 37545 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 2019-10-02, Ludovic Courtès wrote:
> Vagrant Cascadian <vagrant <at> debian.org> skribis:
>
>> Ok, a little further ...
>>
>> guix environment --ad-hoc epiphany
>
> It works for me on ‘core-updates’
> ece22ac8ccb6744eaec0320f0c7c9b6680fffa46, but note that my system and
> user profile were already on ‘core-updates’, so presumably that avoids
> problems with XDG_*.
>
>> Still fails in the same way... but!
>>
>> guix environment --pure --ad-hoc epiphany
>>
>> Works fine!
>
> This works fine for me too:
>
> guix environment -E DISPLAY -E XAUTHORITY --ad-hoc epiphany --pure -- epiphany
>
> So… problem solved?
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.
live well,
vagrant
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#37545
; Package
guix
.
(Sun, 06 Oct 2019 16:07:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 37545 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Vagrant Cascadian <vagrant <at> debian.org> writes:
> On 2019-10-02, Ludovic Courtès wrote:
>> Vagrant Cascadian <vagrant <at> debian.org> skribis:
>>
>>> Ok, a little further ...
>>>
>>> guix environment --ad-hoc epiphany
>>
>> It works for me on ‘core-updates’
>> ece22ac8ccb6744eaec0320f0c7c9b6680fffa46, but note that my system and
>> user profile were already on ‘core-updates’, so presumably that avoids
>> problems with XDG_*.
>>
>>> Still fails in the same way... but!
>>>
>>> guix environment --pure --ad-hoc epiphany
>>>
>>> Works fine!
>>
>> This works fine for me too:
>>
>> guix environment -E DISPLAY -E XAUTHORITY --ad-hoc epiphany --pure -- epiphany
>>
>> So… problem solved?
>
> 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?
Thanks!
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#37545
; Package
guix
.
(Tue, 08 Oct 2019 06:10:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 37545 <at> debbugs.gnu.org (full text, mbox):
I also had a broken next. I am on Sway and the suggestion of unsetting
WAYLAND_DISPLAY when launching made it work! I couldn't get it to
launch any other way, including guix environment commands. Is there a
proper fix for this?
Reply sent
to
Vagrant Cascadian <vagrant <at> debian.org>
:
You have taken responsibility.
(Tue, 08 Oct 2019 06:32:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Vagrant Cascadian <vagrant <at> debian.org>
:
bug acknowledged by developer.
(Tue, 08 Oct 2019 06:32:02 GMT)
Full text and
rfc822 format available.
Message #25 received at 37545-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (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)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#37545
; Package
guix
.
(Tue, 08 Oct 2019 09:02:01 GMT)
Full text and
rfc822 format available.
Message #28 received at 37545 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Bradley Haggerty <bradigger <at> gmail.com> writes:
> I also had a broken next. I am on Sway and the suggestion of unsetting
> WAYLAND_DISPLAY when launching made it work! I couldn't get it to
> launch any other way, including guix environment commands. Is there a
> proper fix for this?
The fix only exists on the 'core-updates' branch, which is hopefully
merged today. \o/
[signature.asc (application/pgp-signature, inline)]
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 05 Nov 2019 12:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 years and 194 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.