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 

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: How To Test pipewire On F33?

[Garry T. Williams]

On Sunday, January 24, 2021 12:27:38 PM EST 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...

OK, that's what I have been doing.  But...

I get these errors repeated every one second after reboot:

Jan 24 12:44:25 gtw pipewire-pulse[2136]: pulse-server 0x55fea9939530: 
failed to connect client: Host is down
Jan 24 12:44:25 gtw pipewire-pulse[2136]: pulse-server 0x55fea994e880: 
[QPulse] ERROR command:9 (SET_CLIENT_NAME) tag:1 error:6 (Host is down)

I repeated the procedure right after reading your message.  Sound
continued to work fine.  But after reboot, thos errors came back.

The time before trying this, sound was immediately gone and the log
showed those errors.

-- 
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

Re: How To Test pipewire On F33?

[Neal Gompa]

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.





-- 
真実はいつも一つ！/ 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

Re: How To Test pipewire On F33?

[Qiyu Yan]

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 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