Github messages for voidlinux
 help / color / mirror / Atom feed
From: notthewave <notthewave@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: wlroots: update to 0.15.0.
Date: Thu, 03 Feb 2022 02:17:11 +0100	[thread overview]
Message-ID: <20220203011711.FVxUosVR_bd7W4-IBsN8FO0cktkBFcpeDGzYZU47ePs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35017@inbox.vuxu.org>

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

New comment by notthewave on void-packages repository

https://github.com/void-linux/void-packages/pull/35017#issuecomment-1028512436

Comment:
> > I've tested these changes with Sway 1.7 and it seems that google-chrome crashes with wlroots 0.15.0 when using the Wayland flag, probably due to this bug https://bugs.chromium.org/p/chromium/issues/detail?id=1279574
> > We probably need to bump chromium / google-chrome as well.
> 
> Chromium is failing to launch on Wayland with sway 1.6.1 and wlroots 0.14.1.

can't confirm when running
```
chromium --ozone-platform-hint=auto
``` 
as decribed in the arch wiki

  parent reply	other threads:[~2022-02-03  1:17 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 18:57 [PR PATCH] Wlroots ifreund
2022-01-12 19:00 ` [PR PATCH] [Updated] wlroots: update to 0.15.0 ifreund
2022-01-12 19:47 ` ifreund
2022-01-13 14:28 ` ahesford
2022-01-13 19:19 ` [PR PATCH] [Updated] " ifreund
2022-01-22 23:44 ` steinex
2022-01-25  4:21 ` RicArch97
2022-01-25  4:24 ` RicArch97
2022-01-28 15:47 ` [PR PATCH] [Updated] " ifreund
2022-01-28 19:49 ` cennedys
2022-01-28 19:56 ` ifreund
2022-02-03  1:10 ` bluej99
2022-02-03  1:16 ` notthewave
2022-02-03  1:17 ` notthewave [this message]
2022-02-03  1:20 ` RicArch97
2022-02-03  1:21 ` bluej99
2022-02-03 21:44 ` [PR PATCH] [Updated] " ifreund
2022-02-03 21:46 ` [PR PATCH] [Updated] wlroots: update to 0.15.1 ifreund
2022-02-15 13:49 ` KSPAtlas
2022-02-15 13:50 ` KSPAtlas
2022-02-16 17:52 ` cennedys
2022-02-19 12:15 ` KSPAtlas
2022-02-20  6:42 ` cennedys
2022-02-26 21:37 ` [PR PATCH] [Updated] " ifreund
2022-02-26 21:38 ` ifreund
2022-02-26 21:50 ` ifreund
2022-02-26 22:06 ` ifreund
2022-02-26 22:10 ` RicArch97
2022-02-27 10:18 ` [PR PATCH] [Merged]: " paper42
2022-02-27 11:36 ` KSPAtlas
2022-02-27 11:49 ` ram02z
2022-02-27 12:07 ` KSPAtlas
2022-02-27 12:08 ` KSPAtlas
2022-02-27 14:32 ` paper42
2022-02-27 14:32 ` paper42
2022-02-27 15:47 ` KSPAtlas
2022-02-27 19:14 ` cennedys
2022-02-28 19:15 ` paper42

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=20220203011711.FVxUosVR_bd7W4-IBsN8FO0cktkBFcpeDGzYZU47ePs@z \
    --to=notthewave@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).