Re: Proposal to modify: Working Sound Beta Release Criterion

On Thu, Jan 28, 2021 at 9:13 PM Kevin Fenzi wrote: > pipewire replaces completely pulseaudio and jack _daemons_ > > ie, now you might have jackd or pulseaudio running, after the switch you > will just have pipewire. All the pulseaudio clients and jack clients > talk to pipewire, and think it's th

Re: Proposal to modify: Working Sound Beta Release Criterion

On Fri, Jan 29, 2021 at 3:45 AM Robbi Nespu wrote: > On Arch wiki mentioned "Firefox (84+) supports this method by default, > while on Chromium (73+) one needs to enable WebRTC PipeWire support by > setting the corresponding (experimental) flag" this is for WebRTC screen > sharing, not sure it al

Re: Proposal to modify: Working Sound Beta Release Criterion

On 28/1/2021 9:55 pm, Lukas Ruzicka wrote: Ok, after an offline part of discussion with @Kamil Paral , we both have agreed that: 1. The beta criterion for *Working sound *should remain as is now (no change needed). 2. We would like to introduce a *new final cri

Fedora-IoT-33-20210128.0 compose check report

No missing expected images. Failed openQA tests: 1/15 (aarch64) Old failures (same test failed in Fedora-IoT-33-20210121.0): ID: 764536 Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi URL: https://openqa.fedoraproject.org/tests/764536 Soft failed openQA tests: 1/16 (x86_64) (Tests complet

Re: Proposal to modify: Working Sound Beta Release Criterion

On Thu, Jan 28, 2021 at 02:10:47PM +0100, Lukas Ruzicka wrote: > > > > > > I think there's a misunderstanding in how all the "frameworks" and stacked > > on top of each other. I'm not very knowledgeable in this area, but I think > > the layers are more or less like this: > > > > 6. Totem | Firefox

Re: Proposal to modify: Working Sound Beta Release Criterion

On Thu, 2021-01-28 at 14:55 +0100, Lukas Ruzicka wrote: > Ok, after an offline part of discussion with @Kamil Paral > , we both have agreed that: > > >    1. The beta criterion for *Working sound *should remain as is now (no >    change needed). >    2. We would like to introduce a *new final cri

Re: Proposal to modify: Working Sound Beta Release Criterion

On Thu, 2021-01-28 at 13:27 +0100, Kamil Paral wrote: > On Thu, Jan 28, 2021 at 12:36 PM Lukas Ruzicka wrote: > > > I do understand the audio criterion quite differently. I believe that an > > application is an application, while an audio framework is an audio > > framework. I think that the work

Re: Proposal to modify: Working Sound Beta Release Criterion

On Thu, 2021-01-28 at 12:33 +0100, Lukas Ruzicka wrote: > > The most important change we are facing now is that > * PipeWire is here to support everything and if it does not, the operating > system has major flaws.* ...but for the last several years we've been in effectively the same situation on

Re: Proposal to modify: Working Sound Beta Release Criterion

Sounds good to me. Jan From: Lukas Ruzicka Sent: Thursday, January 28, 2021 3:55 PM To: For testing and quality assurance of Fedora releases ; Kamil Paral Subject: Re: Proposal to modify: Working Sound Beta Release Criterion Ok, after an offline part of discus

Fedora-Rawhide-20210128.n.0 compose check report

Missing expected images: Minimal raw-xz armhfp Xfce raw-xz armhfp Compose FAILS proposed Rawhide gating check! 7 of 43 required tests failed, 4 results missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 34/181 (x86_64), 35/123 (aarch64

Re: Proposal to modify: Working Sound Beta Release Criterion

Ok, after an offline part of discussion with @Kamil Paral , we both have agreed that: 1. The beta criterion for *Working sound *should remain as is now (no change needed). 2. We would like to introduce a *new final criterion *saying*: **"The installed system must be able to record aud

Re: Proposal to modify: Working Sound Beta Release Criterion

> > > I think there's a misunderstanding in how all the "frameworks" and stacked > on top of each other. I'm not very knowledgeable in this area, but I think > the layers are more or less like this: > > 6. Totem | Firefox | Rhythmbox | Audacity > -- > 5. GStreamer | FFmpeg >

Fedora rawhide compose report: 20210128.n.0 changes

OLD: Fedora-Rawhide-20210127.n.1 NEW: Fedora-Rawhide-20210128.n.0 = SUMMARY = Added images:2 Dropped images: 0 Added packages: 0 Dropped packages:1 Upgraded packages: 156 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:53.45

Fedora-IoT-34-20210128.0 compose check report

Missing expected images: Iot dvd aarch64 Iot dvd x86_64 Failed openQA tests: 3/16 (x86_64), 7/15 (aarch64) New failures (same test not failed in Fedora-IoT-34-20210124.0): ID: 763622 Test: x86_64 IoT-dvd_ostree-iso release_identification URL: https://openqa.fedoraproject.org/tests/763622 I

Re: Proposal to modify: Working Sound Beta Release Criterion

On Thu, Jan 28, 2021 at 12:36 PM Lukas Ruzicka wrote: > I do understand the audio criterion quite differently. I believe that an > application is an application, while an audio framework is an audio > framework. I think that the working sound criterion should apply to audio > as in audio framewor

Re: Proposal to modify: Working Sound Beta Release Criterion

On Thu, Jan 28, 2021 at 11:16 AM Kamil Paral wrote: > On Wed, Jan 27, 2021 at 7:35 PM Adam Williamson < > adamw...@fedoraproject.org> wrote: > >> The reason the current criterion specifies "with gstreamer-based >> applications" is to avoid being too broad and vague. It really *means* >> "sound mu

Re: Proposal to modify: Working Sound Beta Release Criterion

On Wed, Jan 27, 2021 at 7:35 PM Adam Williamson wrote: > The reason the current criterion specifies "with gstreamer-based > applications" is to avoid being too broad and vague. It really *means* > "sound must basically work", but we're referring to gstreamer on the > basis that: > > 1. It's the f

Re: Proposal to modify: Working Sound Beta Release Criterion

On Wed, Jan 27, 2021 at 7:39 PM Jan K wrote: > It would be nice to have working sound on virtual machines as well. If you > could add instructions or note(s) whether this would be possible at this > stage it would be appreciated. > If it should work, it could be tested as well. > Hi Jan, unless