I just tested now sharing the whole screen, in that case after I select
the display on the second popup, I see the preview on the first one,
select it, a new popup appears and if I select the screen again then it
does work.
This trick only seems to work for the whole screen thoough, not a single
w
Olivier, if I click "share a window" the following happens:
- the in-app "Share an application window" popup appears (nothing in it)
- the standalone "Screen share" popup appears"
- I select a (wayland-based) window, click ok
- the original "Share an application window" popup is still there, s
Robie: I just tested on jammy, and I'm seeing something different: with
the flag enabled, screen sharing works (although I do get the window
selection pop-up displayed twice, same as on impish). Without the flag,
I'm seeing a black screen with the mouse cursor, like you do.
Could you test again wi
Alberto, could it be the same issue that Robie is describing, that the
window selector pop-up appears twice? I'm seeing this too (on Impish),
although screen sharing only works if I confirm the second popup, not if
I cancel it.
--
You received this bug notification because you are a member of Ubu
I have a slightly different on Impish, with 97.0.4692.99 (1878):
With the pipewire flag enabled, I do get the popup, I can select a
window but then nothing happens, and the initial popup doesn't ever
close, I have to cancel the screen share.
--
You received this bug notification because you are
So I have this sort of working on my machine that's running Impish. The
only annoying thing is that the window selector pop-up appears twice,
and the second one seems superfluous (I have to hit Cancel on it).
On a freshly installed Jammy machine, I had to enable
chrome://flags/#enable-webrtc-pipew
In both cases I'm running:
installed: 98.0.4758.9 (1868) 154MB -
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849478
Title:
[snap] (experimental) pipewire support not availab
Fixed with https://git.launchpad.net/~chromium-team/chromium-
browser/+git/snap-from-
source/commit/?id=9bb2debda802087e3910a720dc63172f1471ed09.
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of
Progress: I managed to get screen capture to partially work by rebasing
my test snap on chromium 96.0.4664.18, which contains the following
commit:
https://source.chromium.org/chromium/_/webrtc/src.git/+/593b4d550d5569997c65dc1226238da04d4ea61a.
This works only partially because it allows sharing
This bug report could be related
"Upgrade pipewire from 0.2 to 0.3 for chromium/webrtc"
https://bugs.chromium.org/p/chromium/issues/detail?id=1146942
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849
Relevant output from pw-dump when sharing the entire screen (which
remains black). The interesting bit is ["state": "suspended"]:
{
"id": 34,
"type": "PipeWire:Interface:Client",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"change-mask": [ "props" ],
> Isn't better to use bindings now instead of those env variables?
> As they tend to be a bit fragile...
I assume you mean layouts?
As long as upstream doesn't remove the ability to customize config/plugins
directories, this should be functionally equivalent to using layouts. I don't
have a stro
This issue bit me last month when conducting a (supervised — I went full
Bad-luck Brian on that one, lol) online class with my students on Google
Meet; they could only see black whenever I shared something other than
Chromium’s window. Luckily I was able to display all my material on
browser tabs,
Isn't better to use bindings now instead of those env variables?
As they tend to be a bit fragile...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849478
Title:
[snap] (experimental) pipewire suppo
… but screen sharing still doesn't work. This requires further
investigation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849478
Title:
[snap] (experimental) pipewire support not available
To ma
The denial goes away if I manually edit the snapd-generated apparmor
profile to add the following rule:
dbus (send)
bus=session
path=/
interface=org.freedesktop.DBus
member=GetConnectionUnixProcessID
peer=(name=org.freedesktop.DBus, label=unconfined),
--
You received this b
More environment variables are needed to adjust paths for pipewire:
SPA_PLUGIN_DIR: $SNAP/usr/lib/$SNAPCRAFT_ARCH_TRIPLET/spa-0.2
PIPEWIRE_CONFIG_NAME: $SNAP/etc/pipewire/pipewire.conf
PIPEWIRE_MODULE_DIR: $SNAP/usr/lib/$SNAPCRAFT_ARCH_TRIPLET/pipewire-0.3
Now seeing an apparmor denia
Setting SPA_PLUGIN_DIR to /snap/chromium/current/usr/lib/x86_64-linux-
gnu/spa-0.2 makes the crash go away, but screen sharing still doesn't
work:
[W][40760.557582][conf.c:243 conf_load()] config 0x559d4c0175d0: error
loading config '/etc/pipewire/client.conf': Permission denied
[W][40760
More info with PIPEWIRE_DEBUG=4:
[D][pipewire.c:257 pw_load_spa_handle()] load lib:'support/libspa-support'
factory-name:'support.log'
[D][pipewire.c:125 open_plugin()] can't load
/usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so:
/usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-suppo
My first shot at it allows me to enable pipewire support in
chrome://flags, but makes the browser crash when actually trying to
share a window in a WebRTC application (e.g. meet.jit.si). I'm seeing
the following messages on stderr with verbose logging:
[71968:71968:0426/182013.480562:INFO:base_cap
Working on this in a branch: https://code.launchpad.net/~chromium-team
/chromium-browser/+git/snap-from-source/+ref/enable-pipewire
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed =>
[continuing]
This is bad, since Ubuntu 21.04 switches from Xorg to Wayland by default
which effectively disables screen sharing on Chromium. User needs to go
back to Xorg to enable screen sharing on Chromium, which is a bit of a
pity since pipewire is already in place and ready to be used.
--
Yo
Starting from Ubuntu 21.04 the pipewire libs are bundled in Ubuntu
itself, to allow screen sharing over webrtc. This allows Firefox to cast
screen properly, which is great :)
However, since the Chromium snap is missing the pipewire support
(currently 90.0.4430.85), it's not possible to set the fla
See also the announcement on the chromium-packagers mailing list:
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-
packagers/oEtkQUfwcus
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
24 matches
Mail list logo
