Hi, I am a maintainer of a low latency audio application, Mixxx. I
misunderstood the prior discussion on this issue and thought that Ubuntu
21.04 would be shipping with PipeWire by default for audio. However I
tested 21.04 beta in a VM and pipewire and pulseaudio are both running
by default. It
Is this likely to get backported to 20.04 or will it only be fixed from
21.04 onwards?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
[MIR] pipewire
To manage notifications about
These were the ones component-mismatches-proposed said were required. If
some of them aren't, they'll show for demotion and can be put back to
universe then. Thanks!
laney@dev> ./change-override -s hirsute -S -c main pipewire
Override component to main
pipewire 0.3.19-3 in hirsute: universe/misc
On Mon, Feb 01, 2021 at 10:15:45AM -, Rasmus Eneman wrote:
> As Ubuntu 21.04 won't have Gnome 40, can this be enabled for the current
> version (in 21.04 ofc.)?
>
> It's explicitly disabled for Ubuntu here https://salsa.debian.org/gnome-
> team/mutter/-/blob/debian/master/debian/rules#L41-48
As Ubuntu 21.04 won't have Gnome 40, can this be enabled for the current
version (in 21.04 ofc.)?
It's explicitly disabled for Ubuntu here https://salsa.debian.org/gnome-
team/mutter/-/blob/debian/master/debian/rules#L41-48
--
You received this bug notification because you are a member of
@didrocks Any ETA for the 21.04 channel? I'd like to test this asap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
[MIR] pipewire
To manage notifications about this bug go to:
GNOME Shell will start depending on it in the next release and this is
what is going to pull it in main.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
[MIR] pipewire
To manage
Thank you Christian, that sounds great!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
[MIR] pipewire
To manage notifications about this bug go to:
Hi Rasmus,
this looks soemwhat ready to me - it is on the Desktop team to now integrate
and thereby trigger the component mismatch that will pull it into main.
I've last week pinged seb128 and didrocks about it - AFAIK they will take a
look.
=>
Hello, what is the status of this MIR? Getting screen sharing to work in
Wayland would be a huge improvement in times like these and I'm weary of
the "Unassigned, importance low" status that this currently have.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This second review will only document the areas that some difference was
found from the first review.
I reviewed pipewire 0.3.15-1 as checked into hirsute. This shouldn't be
considered a full audit but rather a quick gauge of maintainability.
- Build-Depends:
debhelper-compat (= 13),
Thank you Liz! I'll see if I have the energy to do that, but with my
company pushing bad remote meeting solutions I might have to :/ Now I at
least know where things stand and what to do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: pipewire (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
[MIR] pipewire
To manage notifications about this bug go to:
That is correct, if you're on amd64. I built only for ARM because that's
what I need for my device running Wayland (sorry!) but you should be
able to clone my PPA and rebuild from source on amd64 if you like.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you Liz. There are no installable packages on your PPA though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
[MIR] pipewire
To manage notifications about this bug go to:
https://launchpad.net/~lizthegrey/+archive/ubuntu/freedesktop -- I
backported, rather than directly installing the Debian packages. You
need to do a formal backport from source to force linking against
Ubuntu's ABI.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@Liz Fong-Jones
What did you do to get xdg-desktop-portal working in Ubuntu?
I installed pipewire (0.3.10-4 avalible in groovy) and tried to pull
xdg-desktop-portal, mutter and mutter-common form Debian but that causes mutter
to immediately crash. After restoring mutter and mutter-common I have
> Reassigning so that necessary work is done to get pipewire updated,
building and working
The new version 0.3 serie in Ubuntu, is building and working,
reassigning back to ubuntu-security for review (there is a minor version
update in Debian but which came a bit late to be synced, it shouldn't
Pipewire 0.3.12 landed in Debian testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
[MIR] pipewire
To manage notifications about this bug go to:
https://tracker.debian.org/news/1175550/pipewire-0310-4-migrated-to-
testing/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
[MIR] pipewire
To manage notifications about this bug go
pipewire 0.3 is in NEW in Debian. Once it's cleared out there, we can
request an FFe to hopefully get into groovy, and then assign back to the
security team for review.
I think it's worth waiting since 0.3 has big changes and this is the
version that GNOME depends on.
--
You received this bug
Reassigning so that necessary work is done to get pipewire updated,
building and working in groovy.
** Changed in: pipewire (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi, security team is wanting to do a MIR audit on pipewire for groovy.
Unfortunately, the current pipewire source downloaded from groovy does
not appear to have been updated nor does it build.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have Pipewire 0.3 working on Focal, with at least a few of its
reverse-depends working correctly (gnome-remote-desktop, mutter, xdg-
desktop-portal)
I'll post a PPA shortly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@cpaelzer, thanks for checking with us. Pipewire is where GNOME is
heading and is already required for e.g screen sharing to work on
Wayland (which isn't our default session at the moment but we still want
that working in Ubuntu). I don't think we are ready to switch the
desktop this cycle but
Thanks for the ping Vlad, The old FAQ declaring it not ready yet these days is
(quote):
"Is PipeWire ready yet?
It is getting ready for broader testing.
The API in master is now declared stable and not expected to change anymore for
the
0.3 release.
The protocol can support older 0.2 version
is there any chance of getting this in Groovy?
it would be nice to start migrating to Wayland-by-default in non-LTS versions,
and being unable to screenshare is a blocker for a lot of users
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags removed: disco
** Tags added: focal groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
[MIR] pipewire
To manage notifications about this bug go to:
+1
It isn't possible to record a screencast with OBS on Wayland
```
error: [OBS XDG] Error creating screencast session:
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface
“org.freedesktop.portal.ScreenCast” on object at path
/org/freedesktop/portal/desktop
```
--
You
Is this going to get done for Focal? It would be a shame to ship an LTS
release without remote desktop support for Wayland. Aren't we at the
point now where Wayland is supposed to people's first choice?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I reviewed pipewire 0.2.5-1 as checked into eoan. This shouldn't be
considered a full audit but rather a quick gauge of maintainability.
pipewire is a multimedia sharing and processing engine. It is comprised of a
server and userspace API to handle multimedia pipelines. The pipewire package
** Changed in: pipewire (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
[MIR] pipewire
To manage
I certainly can't see this as a small and easy package to maintain in
general. Fortunately, right now it is in sync with Debian, but it's a
pretty big codebase. Any issues that might come up, especially security
issues, might be effort-intensive, though at a quick glance I didn't
notice anything
Please also make sure to set a bug subscriber...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
[MIR] pipewire
To manage notifications about this bug go to:
** Changed in: pipewire (Ubuntu)
Status: Confirmed => In Progress
** Changed in: pipewire (Ubuntu)
Importance: Undecided => Critical
** Changed in: pipewire (Ubuntu)
Importance: Critical => Low
** Changed in: pipewire (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre
** Description changed:
Availability
Built for all supported architectures. In sync with Debian.
Rationale
=
GNOME switched to Wayland by default in the 3.22 release 2 years ago. Ubuntu
followed that lead and defaulted to Wayland with 17.10 but switched back
I agree remote VNC is not the only blocker for enabling Wayland by
default for 20.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
[MIR] pipewire
To manage notifications about
@Jeremy, the MIR here is the pipewire one, not about gnome-remote-desktop vs
vino, you maybe commented on the wrong ticket?
(If that was a reply to my comment, the problem with wayland/why we don't
consider if for default is not the service enabling VNC, it's other things
having your session
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pipewire (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
Seb, I believe gnome-remote-desktop offers the same password option that
vino does through the same UI in gnome-control-center's Sharing panel.
vino only supports VNC. (To be fair, you could use some other remote
desktop service with X but VNC is the only thing we've been directly
supporting in
Just comment from a desktop team perspective, that MIR is low priority
for us at the moment.
Rational:
The component is new and only adds unencrypted & withoutpassword VNC support to
the wayland session which is better than nothing but not enough. Having the
feature enabled for our users that
** Description changed:
Availability
Built for all supported architectures. In sync with Debian.
Rationale
=
GNOME switched to Wayland by default in the 3.22 release 2 years ago. Ubuntu
followed that lead and defaulted to Wayland with 17.10 but switched back
** Description changed:
Availability
Built for all supported architectures. In sync with Debian.
Rationale
=
GNOME switched to Wayland by default in the 3.22 release 2 years ago. Ubuntu
followed that lead and defaulted to Wayland with 17.10 but switched back
43 matches
Mail list logo
