Github messages for voidlinux
 help / color / mirror / Atom feed
From: HadetTheUndying <HadetTheUndying@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: OBS28 (QT6) crashing Mutter/Gnome shell 42.4 in Wayland
Date: Wed, 16 Nov 2022 03:49:26 +0100	[thread overview]
Message-ID: <20221116024926.iXldYOm1a2xBeAriVW65VNHa9ONlV8PBB-J5fOpdOj4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40481@inbox.vuxu.org>

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

New comment by HadetTheUndying on void-packages repository

https://github.com/void-linux/void-packages/issues/40481#issuecomment-1316222386

Comment:
> > it's only needed when running in wayland session (obs is wayland native too) otherwise it won't start unless ran with xwayland
> 
> This is one of the dependencies you have to install on your own because they are only useful under some conditions. The handbook covers this in the Wayland section. The only catch here is that you might have had obs and qt5-wayland when obs used qt5 and now with an update, qt6-wayland wasn't installed.

Any chance this needs to be added to the doc or post install message similar to what you get when you install steam?

  parent reply	other threads:[~2022-11-16  2:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-12 10:13 [ISSUE] " yurifuko
2022-11-12 10:43 ` classabbyamp
2022-11-12 11:56 ` yurifuko
2022-11-13 12:11 ` sgn
2022-11-13 13:12 ` yurifuko
2022-11-13 13:14 ` yurifuko
2022-11-13 13:16 ` yurifuko
2022-11-13 14:44 ` paper42
2022-11-13 14:47 ` paper42
2022-11-16  2:49 ` HadetTheUndying [this message]
2022-11-16 19:28 ` HadetTheUndying
2022-11-20 21:40 ` oreo639
2022-11-20 21:41 ` oreo639
2022-11-20 21:45 ` oreo639
2022-11-22 21:44 ` paper42
2022-11-23 10:39 ` yurifuko
2022-11-23 10:46 ` [ISSUE] [CLOSED] " 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=20221116024926.iXldYOm1a2xBeAriVW65VNHa9ONlV8PBB-J5fOpdOj4@z \
    --to=hadettheundying@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).