From: timsofteng <timsofteng@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Bug: Screen sharing in Chromium on Wayland (sway)
Date: Tue, 12 Oct 2021 17:28:19 +0200 [thread overview]
Message-ID: <20211012152819.F5bo595Iuz7AGvcJbRxHS6_uBVcK0eK-DOM0yQ-hP78@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33179@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
Closed issue by timsofteng on void-packages repository
https://github.com/void-linux/void-packages/issues/33179
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
*Void 5.13.19_1 x86_64 GenuineIntel notuptodate rrFFF*
* package:
*chromium-94.0.4606.61_1*
### Expected behavior
When I launch chromium with specific flags I should have ability to share my screen.
It works in firefox right now on my system.
### Actual behavior
When launch chromium with needed flags I get this error in terminal:
`[30861:30861:0929/144013.555951:ERROR:base_capturer_pipewire.cc(896)] Failed to create a proxy for the screen cast portal: Unknown or unsupported transport “disabled” for address “disabled:”`
### Steps to reproduce the behavior
1. Install wayland, swaywm and wlr portal.
2. Open chromium with next flags:
`chromium --enable-features=UseOzonePlatform,WebRTCPipeWireCapturer --ozone-platform=wayland`
3. Open site to test screensharing (e.g. [webrtc](https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#7152534809036794) ).
### Note
If I open firefox at the same time and share my screen then screensharing starts to work in chromium as well. But when I close firefox then screensharing in chromium stops to work.
prev parent reply other threads:[~2021-10-12 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 11:47 [ISSUE] " timsofteng
2021-09-30 9:17 ` codingHahn
2021-09-30 10:04 ` timsofteng
2021-09-30 11:43 ` codingHahn
2021-09-30 13:12 ` timsofteng
2021-10-12 15:28 ` timsofteng
2021-10-12 15:28 ` timsofteng [this message]
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=20211012152819.F5bo595Iuz7AGvcJbRxHS6_uBVcK0eK-DOM0yQ-hP78@z \
--to=timsofteng@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).