unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 37545@debbugs.gnu.org
Subject: bug#37545: epiphany and next broken after webkitgtk upgrade to 2.26.1
Date: Wed, 02 Oct 2019 08:51:02 -0700	[thread overview]
Message-ID: <87eezvqh7d.fsf@yucca> (raw)
In-Reply-To: <87wodnibf2.fsf@gnu.org>

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

On 2019-10-02, Ludovic Courtès wrote:
> Vagrant Cascadian <vagrant@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

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

  reply	other threads:[~2019-10-02 15:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-28 21:51 bug#37545: epiphany and next broken after webkitgtk upgrade to 2.26.1 Vagrant Cascadian
2019-09-29  6:55 ` Vagrant Cascadian
2019-10-02 12:23   ` Ludovic Courtès
2019-10-02 15:51     ` Vagrant Cascadian [this message]
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=87eezvqh7d.fsf@yucca \
    --to=vagrant@debian.org \
    --cc=37545@debbugs.gnu.org \
    --cc=ludo@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).