[Bug 1802533] Re: [MIR] pipewire
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 seems that PulseAudio is still used by default and PipeWire is only used for video on Ubuntu currently. Is that correct? It seems there is no easy way for Ubuntu users to replace PulseAudio or JACK with PipeWire. I found this page on the Debian wiki: https://wiki.debian.org/PipeWire#Using_as_a_substitute_for_PulseAudio.2FJACK.2FALSA but I'm unclear if it's easy for Ubuntu users to prevent the PulseAudio daemon from running so PipeWire can take its place. Are you planning to use PipeWire for audio by default by the 22.04 LTS release? I really hope by that by that time we can ship a Flatpak and have it just work by default on every common distro. -- 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 -> main gstreamer1.0-pipewire 0.3.19-3 in hirsute amd64: universe/libs/optional/100% -> main gstreamer1.0-pipewire 0.3.19-3 in hirsute arm64: universe/libs/optional/100% -> main gstreamer1.0-pipewire 0.3.19-3 in hirsute armhf: universe/libs/optional/100% -> main gstreamer1.0-pipewire 0.3.19-3 in hirsute ppc64el: universe/libs/optional/100% -> main gstreamer1.0-pipewire 0.3.19-3 in hirsute riscv64: universe/libs/optional/100% -> main gstreamer1.0-pipewire 0.3.19-3 in hirsute s390x: universe/libs/optional/100% -> main libpipewire-0.3-0 0.3.19-3 in hirsute amd64: universe/libs/optional/100% -> main libpipewire-0.3-0 0.3.19-3 in hirsute arm64: universe/libs/optional/100% -> main libpipewire-0.3-0 0.3.19-3 in hirsute armhf: universe/libs/optional/100% -> main libpipewire-0.3-0 0.3.19-3 in hirsute ppc64el: universe/libs/optional/100% -> main libpipewire-0.3-0 0.3.19-3 in hirsute riscv64: universe/libs/optional/100% -> main libpipewire-0.3-0 0.3.19-3 in hirsute s390x: universe/libs/optional/100% -> main libpipewire-0.3-dev 0.3.19-3 in hirsute amd64: universe/libdevel/optional/100% -> main libpipewire-0.3-dev 0.3.19-3 in hirsute arm64: universe/libdevel/optional/100% -> main libpipewire-0.3-dev 0.3.19-3 in hirsute armhf: universe/libdevel/optional/100% -> main libpipewire-0.3-dev 0.3.19-3 in hirsute ppc64el: universe/libdevel/optional/100% -> main libpipewire-0.3-dev 0.3.19-3 in hirsute riscv64: universe/libdevel/optional/100% -> main libpipewire-0.3-dev 0.3.19-3 in hirsute s390x: universe/libdevel/optional/100% -> main libpipewire-0.3-modules 0.3.19-3 in hirsute amd64: universe/libs/optional/100% -> main libpipewire-0.3-modules 0.3.19-3 in hirsute arm64: universe/libs/optional/100% -> main libpipewire-0.3-modules 0.3.19-3 in hirsute armhf: universe/libs/optional/100% -> main libpipewire-0.3-modules 0.3.19-3 in hirsute ppc64el: universe/libs/optional/100% -> main libpipewire-0.3-modules 0.3.19-3 in hirsute riscv64: universe/libs/optional/100% -> main libpipewire-0.3-modules 0.3.19-3 in hirsute s390x: universe/libs/optional/100% -> main libspa-0.2-bluetooth 0.3.19-3 in hirsute amd64: universe/libs/optional/100% -> main libspa-0.2-bluetooth 0.3.19-3 in hirsute arm64: universe/libs/optional/100% -> main libspa-0.2-bluetooth 0.3.19-3 in hirsute armhf: universe/libs/optional/100% -> main libspa-0.2-bluetooth 0.3.19-3 in hirsute ppc64el: universe/libs/optional/100% -> main libspa-0.2-bluetooth 0.3.19-3 in hirsute riscv64: universe/libs/optional/100% -> main libspa-0.2-bluetooth 0.3.19-3 in hirsute s390x: universe/libs/optional/100% -> main libspa-0.2-dev 0.3.19-3 in hirsute amd64: universe/libdevel/optional/100% -> main libspa-0.2-dev 0.3.19-3 in hirsute arm64: universe/libdevel/optional/100% -> main libspa-0.2-dev 0.3.19-3 in hirsute armhf: universe/libdevel/optional/100% -> main libspa-0.2-dev 0.3.19-3 in hirsute ppc64el: universe/libdevel/optional/100% -> main libspa-0.2-dev 0.3.19-3 in hirsute riscv64: universe/libdevel/optional/100% -> main libspa-0.2-dev 0.3.19-3 in hirsute s390x: universe/libdevel/optional/100% -> main libspa-0.2-jack 0.3.19-3 in hirsute amd64: universe/libs/optional/100% -> main libspa-0.2-jack 0.3.19-3 in hirsute arm64: universe/libs/optional/100% -> main libspa-0.2-jack 0.3.19-3 in hirsute armhf: universe/libs/optional/100% -> main libspa-0.2-jack 0.3.19-3 in hirsute ppc64el: universe/libs/optional/100% -> main libspa-0.2-jack 0.3.19-3 in hirsute riscv64: universe/libs/optional/100% -> main libspa-0.2-jack 0.3.19-3 in hirsute s390x: universe/libs/optional/100% -> main libspa-0.2-modules 0.3.19-3 in hirsute amd64: universe/libs/optional/100% -> main libspa-0.2-modules 0.3.19-3 in hirsute arm64: universe/libs/optional/100% -> main libspa-0.2-modules 0.3.19-3 in hirsute armhf: universe/libs/optional/100% -> main libspa-0.2-modules 0.3.19-3 in hirsute ppc64el: universe/libs/optional/100% -> main libspa-0.2-modules 0.3.19-3 in hirsute riscv64: universe/libs/optional/100% -> main libspa-0.2-modules 0.3.19-3 in hirsute s390x: universe/libs/optional/100% -> main pipewire 0.3.19-3 in hirsute amd64: universe/libs/optional/100% -> main pipewire 0.3.19-3 in hirsute arm64: universe/libs/optional/100% -> main pipewire 0.3.19-3 in hirsute armhf: universe/libs/optional/100% -> main pipewire 0.3.19-3 in hirsute ppc64el: universe/libs/optional/100% -> main pipewire 0.3.19-3 in hirsute riscv64: universe/libs/optional/100% -> main pipewire 0.3.19-3 in hirsute s390x: universe/libs/optional/100% -> main pipewire-audio-client-libraries 0.3.19-3 in hirsute amd64: universe/libs/optional/100% -> main pipewire-audio-client-libraries 0.3.19-3 in hirsute arm64: universe/libs/optional/100%
Re: [Bug 1802533] Re: [MIR] pipewire
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 Yes, it will be done for 21.04 :-) -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
@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: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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. => https://irclogs.ubuntu.com/2020/11/19/%23ubuntu-desktop.html#t09:23 -- 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802533 Title: [MIR] pipewire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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), libasound2-dev, libbluetooth-dev, libdbus-1-dev,
libglib2.0-dev (>= 2.32.0), libgstreamer-plugins-base1.0-dev,
libgstreamer1.0-dev, libjack-jackd2-dev (>= 1.9.10), libpulse-dev (>= 11.1),
libsbc-dev, libsdl2-dev, libsndfile1-dev (>= 1.0.20), libsystemd-dev,
libudev-dev, libv4l-dev, meson (>= 0.50.0), pkg-config (>= 0.22), systemd,
xmltoman, doxygen, graphviz
- pre/post inst/rm scripts:
dh_installsystemduser automatically adds postinst scripts to enable the
pipewire.service and pipewire.socket units.
dh_installsystemduser automatically adds a postrm that removes or purges the
pipewire.socket and pipewire.service.
- udev rules : 90-pipewire-alsa.rules
- autopkgtests - 3 bash scripts to test interaction with
gnome,gstreamer and libpipewire. There are also tests integrated into
the source code. They are run during the build cycle. There are also
examples and tests packaged in pipewire.test pkg.
- Build logs: Built successfully. However, because the code contains unusual
characters in comments, there were many "bogus" warnings during the build. i.e.,
/** \class pw_filter
*
* \brief PipeWire filter object class
*
* The filter object provides a convenient way to implement
* processing filters.
*
* See also \ref page_filters and \ref page_core_api
*/
- LINTIAN ran successfully with some errors and warnings:
E: pipewire changes: bad-distribution-in-changes-file unstable
E: pipewire-audio-client-libraries: custom-library-search-path
usr/lib/x86_64-linux-gnu/pipewire-0.3/pulse/libpulse-mainloop-glib.so.0.315.0
/usr/${LIB}/pipewire-0.3/pulse
E: pipewire-audio-client-libraries: custom-library-search-path
usr/lib/x86_64-linux-gnu/pipewire-0.3/pulse/libpulse-simple.so.0.315.0
/usr/${LIB}/pipewire-0.3/pulse
E: pipewire-audio-client-libraries: library-not-linked-against-libc
usr/lib/x86_64-linux-gnu/pipewire-0.3/jack/libjacknet.so.0.315.0
E: pipewire-audio-client-libraries: library-not-linked-against-libc
usr/lib/x86_64-linux-gnu/pipewire-0.3/jack/libjackserver.so.0.315.0
W: pipewire-bin: no-manual-page usr/bin/pipewire-media-session
W: pipewire-bin: no-manual-page usr/bin/pw-reserve
W: pipewire-bin: no-manual-page usr/bin/spa-acp-tool
W: pipewire-bin: no-manual-page usr/bin/spa-inspect
W: pipewire-bin: no-manual-page usr/bin/spa-monitor
W: pipewire-bin: no-manual-page usr/bin/spa-resample
N: 7 tags overridden (7 errors)
- spawns a daemon, code looks ok.
- Memory management:
Quite a bit of malloc|calloc|realloc used without checking return value before
use. Especially in spa/plugins.
- A lot of environment variables. Looking at a random sampling, code-wise looks
ok, but use of
them in some places may be questionable. i.e.
1. - pw-pulse.in and pw-jack.in shell scripts use and modify LD_LIBRARY_PATH so
applications load pipewire's pulseaudio or jack instead of Jack's and
PulseAudio's.
2. The pipewire daemon uses env vars to set alternative name and config ile for
the daemon. The name can also be set with a cmdline option to the daemon. So
can change the name in 2 different places.
3. pw_init() contains env vars when the daemon initializes to change defaults
such as the spa plugin directory. Wonder why not use a config file for some of
these?
- cppcheck reports a lot of uninitialized variables.
Conclusions:
Significant source code growth and changes since first security MIR review.
Code base seems to be transitioning from new development to stability.
Security team ACK for promoting pipewire to main.
** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 Ubuntu. https://bugs.launchpad.net/bugs/1802533 Title: [MIR] pipewire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
** 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: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802533 Title: [MIR] pipewire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802533 Title: [MIR] pipewire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
@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 a usable system again but screen sharing still does not work. -- 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
> 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 make a difference for the review though) ** Changed in: pipewire (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802533 Title: [MIR] pipewire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 Ubuntu. https://bugs.launchpad.net/bugs/1802533 Title: [MIR] pipewire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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. https://bugs.launchpad.net/bugs/1802533 Title: [MIR] pipewire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
@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 might aim for next cycle so getting reviews going again now makes sense. I'm reassigning to ubuntu-security as suggested ** Changed in: pipewire (Ubuntu) Assignee: Sebastien Bacher (seb128) => Ubuntu Security Team (ubuntu-security) -- 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 clients transparently. This means that flatpaks with older PipeWire libraries can connect to a newer daemon." => https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/FAQ#is-pipewire-ready-yet We will need to ping the Desktop Team if this still would be their path of choice and if they want it to re-enter security evaluation. Assigning to seb128 who did the last Desktop-direction statements on this in comment #1. @seb128 - would you mind discussing this with the Desktop Team? - if you think this is important these days and you want it to re-enter security assign it to ubuntu-security please - if changes in the infrastructure happened and this is no more needed/wanted could you explain here why and then set it to a "Won't Fix" which would be more clear in regard to peoples expectations. ** Changed in: pipewire (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) -- 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 Ubuntu. https://bugs.launchpad.net/bugs/1802533 Title: [MIR] pipewire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
** 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: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
+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 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802533 Title: [MIR] pipewire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 contains a library, utilities, a daemon and several plugins. pipewire seems to be relatively new and indications are that while usable, it is still being developed (https://github.com/PipeWire/pipewire/wiki/FAQ). It is meant to overhaul audit/video processing by doing what pulseaudio and Jack do and leveraging Wayland remote screen capabilities. - No CVEs. Also examined git repository in github, https://github.com/PipeWire/pipewire. Seems to be a lot of active development and bugfixing. - Build-Depends: debhelper (>= 11), libasound2-dev, libavcodec-dev, libavfilter-dev, libavformat-dev, libdbus-1-dev, libglib2.0-dev, libgstreamer1.0-dev, libgstreamer-plugins-base1.0-dev, libsbc-dev, libsdl2-dev, libudev-dev, libva-dev, libv4l-dev, libx11-dev, meson (>= 0.47), pkg-config (>= 0.22), systemd, xmltoman, doxygen, graphviz **Note: Uses meson build system - There are no pre/post inst/rm scripts. - No init scripts - There are systemd unit files - There is pipewire.socket, a systemd socket unit for automatic socket activation. Appears to be a AF_Unix socket - There is pipewire.service, a system unit file for the daemon. It requires the pipewire.socket to be active first. - dbus services are used - the rtkit (realtimekit) module uses dbus to talk to RealtimeKit to be allowed permission to take on realtime property. - the flatpak module uses dbus in similar manner to acquire permission to record screen or audio. - the Simple plugin API provides dbus services via D-Bus low-level public API to plugins. - No setuid binaries - Several binaries installed in /usr/bin/ and /usr/lib/x86_64-linux-gnu/ dirs. - No sudo fragments. - No udev rules. However, the ALSA (advanced linux sound architecture) and V4l2 (video) plugins do make udev calls to acquire device info. - No autopkgtests. There are a few tests in spa/test dir but they do not seem to have run. - No cron jobs. - Build logs indicated a successful build. However there was a compile error and many compile warnings pertaining to -Wdepracated-declarations and -Wunused-result. There also appeared to be many failures while generating docs. - No processes spawned. - Quite a bit of memory mgmt. Inspecting a random sampling of memory mgmt routines, the memcpy() seem ok, the return value not checked for any of the asprintf() and a number of calloc()|realloc() did not check the return value for failure. - No File IO issues readily found. Noticed v4l2 plugin open() the playback(video capture) device. The default is /dev/video0. The alsa plugin opens an audio device using snd_pcm_open. The default device is hw:0. - Logging: both pipewire and spa (simple plugin api) define their own logging facilities. Use of vsnprintf seems ok. Noted that except for pw_log_trace, logging appears to go to stderr... pw_log_trace writes to a lockfree ringbuffer which seems to be written out from main thread. - There are environment variables. They appear to be ok. - No File IO issues. The v4l2 plugin uses ioctl cnd xioctl calls on VIDIOC_*, the videocapture device. Look ok. - pipewire uses a random number to generate a random cookie that identifies the instance of pipewire - No temp file issues. - Networking: pipewire seem to use "nodes" which are physical playback and recording points for audio. Nodes can be separate processes that use sockets and filedescriptors to communicate and pass around multimedia data. pipewire opens local sockets and pass around file descriptors to do this. - Does not use WebKit. - Does not use PolicyKit. - cppcheck results: [spa/tests/test-props4.c:147]: (error) va_list 'args' was opened but not closed by va_end(). [spa/tests/test-props4.c:427]: (error) va_list 'args' was opened but not closed by va_end(). - Coverity not run. Misc Notes: Entry from https://github.com/PipeWire/pipewire/wiki/FAQ, "Is PipeWire ready yet? No, it is under heavy development It is currently reasonably safe to use the remote API to connect to a PipeWire daemon and the stream API (stream.h) to send and retrieve data. I do not expect this API to change in incompatible ways. The protocol is not fixed yet; it is not safe to assume I will make backward compatible changes in the future. This means that it is not safe to assume that older versions of the library will be able to communicate with newer versions of the daemon (or vice versa). This is usually not a problem because both client and server share the same version of the library. It can be a problem when dealing with sandboxes that have their own (old) copy of PipeWire." The security team will NAK this for now. The above FAQ entry indicates pipewire is still under heavy development
[Bug 1802533] Re: [MIR] pipewire
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 sensitive popping up -- that said, I only did a quick review of the code -- there's some 260 files of source code. There doesn't appear to be open CVEs, the packaging quality is as one would expect. There appears to be test sources at least for libspa, but those do not seem to get run by the upstream build process when running 'make check'. Do you need all the binaries in main? You do mention "not libspa- ffmpeg", but what of the other binaries? If this is just for pipewire binary itself, then it would only require libpipewire-0.2-1 and pipewire. Assigning to Security Team for a code review. ** Changed in: pipewire (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team (ubuntu-security) ** Changed in: pipewire (Ubuntu) Status: In Progress => Triaged -- 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
** 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 (cyphermox) -- 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
** 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 to X for 18.04 LTS. One key feature that the Ubuntu Desktop team supports with X and wants to continue supporting with Wayland is remote desktop. Therefore, I think this MIR is a blocker to enabling Wayland by default for 20.04 LTS. pipewire is a new ambitious library and service for audio and video. It aims to take PulseAudio to the next level and provide a similar capability for video. One reason it was created was to help with sandboxing for Flatpak and to handle Wayland applications. pipewire is required for GNOME's remote desktop implementation for Wayland. So at this point, we are interested in the video part for remote desktop. The audio part is expected later. I don't think even Fedora is using the audio part yet. + + Also, xdg-desktop-portal (in main) offers a remote-desktop portal that + requires pipewire (so not enabled in Ubuntu yet) + + https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus- + org.freedesktop.portal.RemoteDesktop GNOME Remote Desktop To enable GNOME's remote desktop feature in Ubuntu, you need: - Build mutter with --enable-remote-desktop This has been done in Debian but we need pipewire in Ubuntu main to enable on Ubuntu - Install gnome-remote-desktop (MIR is LP: #1802614) - I suggest uninstalling vino to make sure you will be using gnome- remote-desktop - Restart your computer - Log in to the Ubuntu on Wayland session. I believe it should work on X too but there is a misconfiguration in GNOME: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/212 - Open the Settings app to the Sharing page. Turn on Sharing in the app's top bar. Click Screen Sharing and turn it on. Only VNC is supported at this time. - Use remmina (Ubuntu's default app) or another VNC client like Remmina to connect from another computer. Security No known security issues https://security-tracker.debian.org/tracker/source-package/pipewire https://launchpad.net/ubuntu/+source/pipewire/+cve I expect the Security Team will want to review this MIR. Quality assurance = - Ubuntu Desktop bugs needs to be subscribed https://bugs.launchpad.net/ubuntu/+source/pipewire https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=pipewire https://github.com/PipeWire/pipewire/issues/ No autopkgtests. No build tests. Dependencies NOTE: We don't need libspa-ffmpeg which depends on ffmpeg libraries which are not allowed in main. All the other binary dependencies are already in main. Standards compliance 4.1.3, debhelper compat 11, simple dh7 style rules Maintenance === Maintained in Debian by the Debian Utopia team, which is a small team focused on cross-desktop freedesktop.org stuff. upstream: https://pipewire.org/ https://github.com/PipeWire/pipewire https://wiki.gnome.org/Projects/Mutter/RemoteDesktop Other Info == I think Debian Buster "10" GNOME will include GNOME Remote Desktop by default. Fedora 29 includes pipewire and will probably include gnome-remote-desktop soon (it looks like an oversight that it wasn't done before the 29 release). Once this & the gnome-remote-desktop MIR (LP: #1802614) are approved, we should be able to demote vino to universe. -- 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
@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 closing when the shell it a bug, the lack of xrdp option, etc. And anyway, that bug is not the place to argue about wayland not being the default, that's just the fact today and leads to the comment about priority I was making) -- 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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: [MIR] pipewire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 main.) vino does offer encryption but it doesn't work for several major clients. The troublesome part is that vino enables that encryption by default so users have to use dconf-editor or the command line to disable encryption. See LP: #1281250 I expect vino to be removed from "GNOME Core" for 3.32. -- 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
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 opt in for wayland and need VNC would be nice though, so if MIR/security have enough review capacity to get that done please do still -- 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
** 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 to X for 18.04 LTS. One key feature that the Ubuntu Desktop team supports with X and wants to continue supporting with Wayland is remote desktop. Therefore, I think this MIR is a blocker to enabling Wayland by default for 20.04 LTS. pipewire is a new ambitious library and service for audio and video. It aims to take PulseAudio to the next level and provide a similar capability for video. One reason it was created was to help with sandboxing for Flatpak and to handle Wayland applications. pipewire is required for GNOME's remote desktop implementation for Wayland. So at this point, we are interested in the video part for remote desktop. The audio part is expected later. I don't think even Fedora is using the audio part yet. GNOME Remote Desktop To enable GNOME's remote desktop feature in Ubuntu, you need: - Build mutter with --enable-remote-desktop This has been done in Debian but we need pipewire in Ubuntu main to enable on Ubuntu - - Install gnome-remote-desktop (MIR bug not filed yet) + - Install gnome-remote-desktop (MIR is LP: #1802614) - I suggest uninstalling vino to make sure you will be using gnome- remote-desktop - Restart your computer - Log in to the Ubuntu on Wayland session. I believe it should work on X too but there is a misconfiguration in GNOME: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/212 - Open the Settings app to the Sharing page. Turn on Sharing in the app's top bar. Click Screen Sharing and turn it on. Only VNC is supported at this time. - Use remmina (Ubuntu's default app) or another VNC client like Remmina to connect from another computer. Security No known security issues https://security-tracker.debian.org/tracker/source-package/pipewire https://launchpad.net/ubuntu/+source/pipewire/+cve I expect the Security Team will want to review this MIR. Quality assurance = - Ubuntu Desktop bugs needs to be subscribed https://bugs.launchpad.net/ubuntu/+source/pipewire https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=pipewire https://github.com/PipeWire/pipewire/issues/ No autopkgtests. No build tests. Dependencies NOTE: We don't need libspa-ffmpeg which depends on ffmpeg libraries which are not allowed in main. All the other binary dependencies are already in main. Standards compliance 4.1.3, debhelper compat 11, simple dh7 style rules Maintenance === Maintained in Debian by the Debian Utopia team, which is a small team focused on cross-desktop freedesktop.org stuff. upstream: https://pipewire.org/ https://github.com/PipeWire/pipewire https://wiki.gnome.org/Projects/Mutter/RemoteDesktop Other Info == I think Debian Buster "10" GNOME will include GNOME Remote Desktop by default. Fedora 29 includes pipewire and will probably include gnome-remote-desktop soon (it looks like an oversight that it wasn't done before the 29 release). - Once this & the gnome-remote-desktop MIRs are approved, we should be - able to demote vino to universe. + Once this & the gnome-remote-desktop MIR (LP: #1802614) are approved, we + should be able to demote vino to universe. -- 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
** 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 to X for 18.04 LTS. One key feature that the Ubuntu Desktop team supports with X and wants to continue supporting with Wayland is remote desktop. Therefore, I think this MIR is a blocker to enabling Wayland by default for 20.04 LTS. pipewire is a new ambitious library and service for audio and video. It aims to take PulseAudio to the next level and provide a similar capability for video. One reason it was created was to help with sandboxing for Flatpak and to handle Wayland applications. pipewire is required for GNOME's remote desktop implementation for Wayland. So at this point, we are interested in the video part for remote desktop. The audio part is expected later. I don't think even Fedora is using the audio part yet. GNOME Remote Desktop To enable GNOME's remote desktop feature in Ubuntu, you need: - Build mutter with --enable-remote-desktop This has been done in Debian but we need pipewire in Ubuntu main to enable on Ubuntu - Install gnome-remote-desktop (MIR bug not filed yet) - I suggest uninstalling vino to make sure you will be using gnome- remote-desktop - Restart your computer - Log in to the Ubuntu on Wayland session. I believe it should work on X too but there is a misconfiguration in GNOME: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/212 - Open the Settings app to the Sharing page. Turn on Sharing in the app's top bar. Click Screen Sharing and turn it on. Only VNC is supported at this time. - Use remmina (Ubuntu's default app) or another VNC client like Remmina to connect from another computer. Security No known security issues https://security-tracker.debian.org/tracker/source-package/pipewire https://launchpad.net/ubuntu/+source/pipewire/+cve I expect the Security Team will want to review this MIR. Quality assurance = - Ubuntu Desktop bugs needs to be subscribed https://bugs.launchpad.net/ubuntu/+source/pipewire https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=pipewire https://github.com/PipeWire/pipewire/issues/ No autopkgtests. No build tests. Dependencies NOTE: We don't need libspa-ffmpeg which depends on ffmpeg libraries which are not allowed in main. All the other binary dependencies are already in main. Standards compliance 4.1.3, debhelper compat 11, simple dh7 style rules Maintenance === Maintained in Debian by the Debian Utopia team, which is a small team focused on cross-desktop freedesktop.org stuff. upstream: https://pipewire.org/ https://github.com/PipeWire/pipewire https://wiki.gnome.org/Projects/Mutter/RemoteDesktop Other Info == - Fedora 29 ships GNOME Remote Desktop by default. I think Debian Buster "10" GNOME will include it by default too. + I think Debian Buster "10" GNOME will include GNOME Remote Desktop by default. Fedora 29 includes pipewire and will probably include gnome-remote-desktop soon (it looks like an oversight that it wasn't done before the 29 release). Once this & the gnome-remote-desktop MIRs are approved, we should be able to demote vino to universe. -- 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://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
