Re: Proposal to modify: Working Sound Beta Release Criterion

[Kamil Paral]

On Thu, Jan 21, 2021 at 2:20 PM Lukas Ruzicka  wrote:

> Hello friends of Fedora,
>
> I have been thinking about a proposal to modify the %subj.
>

It's good to link to the existing version, so that people can compare:
https://fedoraproject.org/wiki/Fedora_34_Beta_Release_Criteria#Working_sound


> I have tried several version and I did not like any, so finally I am
> proposing this text:
>
> *Working sound*
>
> *The installed system must be able to play back and record audio.*
>

This probably needs something like "(if relevant hardware is present)"
appended to it (or in a footnote). And we should keep the existing
"System-specific bugs" footnote from the current criterion.

I believe the proposed change is good for two main reasons:
1. I don't see a reason to limit the criterion to just gstreamer-based
applications, as it currently is.
2. Audio recording has grown in importance immensely in the last year due
to teleconferencing and we should cover it in criteria.

So I'm fine with the proposal.

There's a question whether this should stay in Beta or be moved to Final,
since it covers more use cases in the new version. Personally I think it's
OK to keep this in Beta, because, quoting from the footnote, "It is meant
to cover bugs which completely prevent sound playback from working in any
hardware configuration". Less clear-cut cases can be decided as Final
during blocker review, and we also still have the Default application
functionality [1] for Final, which furthermore covers some important apps
by itself.

[1]
https://fedoraproject.org/wiki/Fedora_34_Final_Release_Criteria#Default_application_functionality
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: How To Test pipewire On F33?

[Qiyu Yan]

Neal Gompa  于 2021年1月25日周一 上午1:37写道：

> On Sun, Jan 24, 2021 at 12:28 PM Qiyu Yan 
> wrote:
> >
> > My procedure:
> >
> > 1. sudo swap pulseaudio pipewire-pulseaudio --allowerasing
> --enablerepo=updates-testing
> >
> > If you lost sound:
> >
> > 2. sudo systemctl enable --global pipewire-pulse.socket
> >
> > The second step should be done automatically, but it's not the case for
> me...
> >
>
> It's supposed to be started as a user unit, rather than a system unit.
>
> If it's not working, then "systemctl enable --user
> pipewire-pulse.socket" should fix it.
>
--global means enable user unit for every user on system. This is useful
when you need sound in GDM or something like that.

This should be default as presents, but last time when I test this package
seems post scriptlets disable the socket.

>
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: How To Test pipewire On F33?

[Lukas Ruzicka]

When I swapped pulseaudio with pipewire, I did not use the *swap* argument,
but installed pipewire over it:

   1. dnf install pipewire pipewire-pulseaudio --allowerasing
   2. reboot computer
   3. try that pipewire is running: *pactl info *check that pulseaudio
   server runs (on Pipewire)

I was successful with this on Fedora Rawhide. On Fedora, this brings me the
following journalctl logs:

led 25 10:59:51 vseved rtkit-daemon[1089]: Successfully made thread 1668 of
process 1668 (/usr/bin/pipewire-pulse) owned by '42' high priority at nice
level -11.
led 25 10:59:51 vseved rtkit-daemon[1089]: Successfully made thread 1669 of
process 1668 (/usr/bin/pipewire-pulse) owned by '42' RT at priority 20.
led 25 10:59:51 vseved rtkit-daemon[1089]: Successfully made thread 1727 of
process 1727 (/usr/bin/pipewire) owned by '42' high priority at nice level
-11.
led 25 10:59:52 vseved rtkit-daemon[1089]: Successfully made thread 1729 of
process 1727 (/usr/bin/pipewire) owned by '42' RT at priority 20.
led 25 10:59:52 vseved rtkit-daemon[1089]: Successfully made thread 1840 of
process 1840 (/usr/bin/pipewire-media-session) owned by '42' high priority
at nice level -11.
led 25 10:59:52 vseved rtkit-daemon[1089]: Successfully made thread 1842 of
process 1840 (/usr/bin/pipewire-media-session) owned by '42' RT at priority
20.
led 25 11:00:01 vseved rtkit-daemon[1089]: Successfully made thread 2354 of
process 2354 (/usr/bin/pipewire-pulse) owned by '1000' high priority at
nice level -11.
led 25 11:00:01 vseved rtkit-daemon[1089]: Successfully made thread 2355 of
process 2354 (/usr/bin/pipewire-pulse) owned by '1000' RT at priority 20.
led 25 11:00:02 vseved rtkit-daemon[1089]: Successfully made thread 2593 of
process 2593 (/usr/bin/pipewire) owned by '1000' high priority at nice
level -11.
led 25 11:00:02 vseved rtkit-daemon[1089]: Successfully made thread 2595 of
process 2593 (/usr/bin/pipewire) owned by '1000' RT at priority 20.
led 25 11:00:02 vseved rtkit-daemon[1089]: Successfully made thread 2741 of
process 2741 (/usr/bin/pipewire-media-session) owned by '1000' high
priority at nice level -11.
led 25 11:00:02 vseved rtkit-daemon[1089]: Successfully made thread 2751 of
process 2741 (/usr/bin/pipewire-media-session) owned by '1000' RT at
priority 20.
led 25 11:00:13 vseved systemd[1430]: pipewire-pulse.service: Succeeded.
led 25 11:00:13 vseved systemd[1430]: pipewire.service: Succeeded.
led 25 11:00:13 vseved systemd[1430]: pipewire-pulse.socket: Succeeded.
led 25 11:00:13 vseved systemd[1430]: pipewire.socket: Succeeded.
led 25 11:00:27 vseved pipewire-media-session[2741]: GetManagedObjects()
failed: org.freedesktop.DBus.Error.NoReply
led 25 11:02:00 vseved pipewire-pulse[2354]: pulse-server 0x55ea4eb3b570:
[Ovládání hlasitosti PulseAudio] ERROR command:87 (EXTENSION) tag:12
error:19 (Operation not supported)
led 25 11:02:00 vseved pipewire-pulse[2354]: pulse-server 0x55ea4eb3b570:
[Ovládání hlasitosti PulseAudio] ERROR command:87 (EXTENSION) tag:13
error:19 (Operation not supported)
led 25 11:02:00 vseved pipewire-pulse[2354]: pulse-server 0x55ea4eb3b570:
[Ovládání hlasitosti PulseAudio] ERROR command:87 (EXTENSION) tag:14
error:19 (Operation not supported)
led 25 11:02:00 vseved pipewire-pulse[2354]: pulse-server 0x55ea4eb3b570:
[Ovládání hlasitosti PulseAudio] ERROR command:87 (EXTENSION) tag:15
error:19 (Operation not supported)
led 25 11:02:00 vseved pipewire-pulse[2354]: pulse-server 0x55ea4eb3b570:
[Ovládání hlasitosti PulseAudio] ERROR command:87 (EXTENSION) tag:17
error:19 (Operation not supported)
led 25 11:02:00 vseved pipewire-pulse[2354]: pulse-server 0x55ea4eb3b570:
[Ovládání hlasitosti PulseAudio] ERROR command:87 (EXTENSION) tag:19
error:19 (Operation not supported)
led 25 11:02:00 vseved pipewire-pulse[2354]: pulse-server 0x55ea4eb3b570:
[Ovládání hlasitosti PulseAudio] ERROR command:87 (EXTENSION) tag:21
error:19 (Operation not supported)

Audio works and settings can be still done by pavucontrol, for example.

On Sun, Jan 24, 2021 at 6:28 PM Qiyu Yan  wrote:

> My procedure:
>
> 1. sudo swap pulseaudio pipewire-pulseaudio --allowerasing
> --enablerepo=updates-testing
>
> If you lost sound:
>
> 2. sudo systemctl enable --global pipewire-pulse.socket
>
> The second step should be done automatically, but it's not the case for
> me...
>
> Garry T. Williams  于 2021年1月25日周一 上午12:53写道：
>
>> What is the procedure for testing pipewire on a F33 system?
>>
>> (I'm obviously doing something wrong since the bug seems to not make
>> sense to anyone: https://bugzilla.redhat.com/show_bug.cgi?id=1912150
>> and yet my system will not function at all for audio after I swap in
>> pipewire for pulseaudio.)
>>
>> --
>> Garry T. Williams
>>
>>
>> ___
>> test mailing list -- test@lists.fedoraproject.org
>> To unsubscribe send an email to test-le...@lists.fedoraproject.org
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelin

Re: How To Test pipewire On F33?

[Lukas Ruzicka]

On Sun, Jan 24, 2021 at 5:54 PM Garry T. Williams 
wrote:

> What is the procedure for testing pipewire on a F33 system?
>

I am currently working on several test cases for the qa process against
pipewire, however I am mainly focusing on F34.
If you have ideas how we could test it or what we could test specifically,
let me know.




>
> (I'm obviously doing something wrong since the bug seems to not make
> sense to anyone: https://bugzilla.redhat.com/show_bug.cgi?id=1912150
> and yet my system will not function at all for audio after I swap in
> pipewire for pulseaudio.)
>
> --
> Garry T. Williams
>
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat



Purkyňova 115

612 45 Brno - Královo Pole

lruzi...@redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Testcase Audio Recording Basic (new test case proposal)

[Lukas Ruzicka]

On Fri, Jan 22, 2021 at 11:15 PM Kamil Paral  wrote:

> On Fri, Jan 22, 2021 at 5:21 PM Lukas Ruzicka  wrote:
>
>> The latest version of the proposal:
>>
>> Testcase Audio Recording (change proposal) Description
>>
>> This test case tests whether sound can be recorded on Fedora.
>> Prerequisites
>>
>>- Install any sound recording application you're familiar with. If
>>you've never worked with any, you can try the *Gnome Sound Recorder*
>>(the gnome-sound-recorder package), a very simplistic and lightweight
>>application. Alternatively, you can try other applications, such as
>>*Audacity* (the audacity package).
>>- Make sure the input sound device is correctly connected to your
>>computer, so that you can expect that sound will be recorded, i.e. you 
>> have
>>a microphone (or any sound producing device) connected to the input of 
>> your
>>sound adapter.
>>- Run *Settings* and navigate to the *Sound* tab. Check that your
>>sound device is correctly recognized by the system. In case you have more
>>input sound devices, make sure all of these devices are listed.
>>
>>
> This looks a bit too specific, you can say something like "Open your
> system's sound settings", if you want to provide some universal advice. No
> hard feelings, though.
>

Yeah, will change it.



>
>
>>
>>- Select a preferred device for input and set the input level using
>>the slider and the indicator below to avoid over-excitation of the signal
>>and sound distortion.
>>
>> How to test
>>
>>- Start a sound recording application.
>>- Record a sound clip of about 10 seconds using the microphone (or
>>another sound producing device).
>>- Play back the recorded sound.
>>
>> Expected Results
>>
>>- The recorded sound clip is *correctly* recorded and can be played
>>back. Note that the quality of the recording depends on many factors, such
>>as the quality of the sound adapter, the microphone, the wires used, etc.
>>Therefore the sound quality should not be considered a test failing
>>criterion unless it is much worse than expected.
>>
>>
>>
> LGTM
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat



Purkyňova 115

612 45 Brno - Královo Pole

lruzi...@redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org