Looks like pipewire-0.3.81-1 has some issues. At first it looked like
it only impacted virtual machines but my laptop turned out to be a
victim also. It fails 100% for me in VirtualBox across a wide range of
hosts for all current Fedora guests (F37, 38, 39 and Rawhide).
https
I find this in bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1983861
>>I think this is entirely normal in f35. The session manager >>is not started
>>by pipewire anymore but by systemd.
>>You probably need to manually enable and start
>>pipewire-media-ses
How to trouble shoot?
I tested the following kernels with fully updated F35 and Gnome-Settings->Sound
shown no sound devices:
vmlinuz-5.12.0-198.fc35.x86_64
vmlinuz-5.13.0-0.rc6.20210617git70585216fe77.48.fc35.x86_64
vmlinuz-5.13.0-58.fc35.x86_64+debug
Hello Stan,
I would say that switching to PulseAudio from PipeWire on F35 is an ugly
hack that you should try to avoid as much as possible. On Fedora 34,
PulseAudio was replaced by PipeWire which is the default sound solution for
Fedora 34. This is the same for Fedora 35.
If you are having
On Sun, 4 Jul 2021 07:38:08 -0700
stan via test wrote:
> As a test, I removed pipewire, and its dozen or so dependencies.
> Sound started working again, and I was able to configure things to my
> preferences. I'll keep an eye on pipewire and its progress, perhaps
> try installin
bug.cgi?id=1931384
> comment 16,
> rm -rf /etc/pipewire
> dnf reinstall pipewire-alsa.x86_64 pipewire-gstreamer.x86_64
> pipewire-pulseaudio.x86_64 pipewire systemctl --user restart pipewire
> pipewire-pulse
>
> but it didn't help. There was no /etc/pipewire to begin with, an
On Fri, 2 Jul 2021 16:48:26 -0700
stan via test wrote:
> On Fri, 02 Jul 2021 14:36:32 -0700
> Adam Williamson wrote:
> > What version of pipewire did you get? pipewire-0.3.31-1.fc35 is
> > known broken. If you got that, get pipewire-0.3.31-2.fc35 instead -
> > https:
On Fri, 02 Jul 2021 14:36:32 -0700
Adam Williamson wrote:
> On Fri, 2021-07-02 at 11:35 -0700, stan via test wrote:
> > I am having trouble with sound in a new rawhide installation. I
> > waited for F35 because I thought the kinks in pipewire would be
> > worked out, b
On Fri, 2021-07-02 at 11:35 -0700, stan via test wrote:
> I am having trouble with sound in a new rawhide installation. I waited
> for F35 because I thought the kinks in pipewire would be worked out,
> but not so much for me. It might be something simple, but when I try to
> tu
I am having trouble with sound in a new rawhide installation. I waited
for F35 because I thought the kinks in pipewire would be worked out,
but not so much for me. It might be something simple, but when I try to
turn off cards, and assign cards to default, etc. it doesn't work. I
can play sound
On Monday, April 19, 2021 10:22:38 AM EDT Garrett LeSage wrote:
> Several weeks ago, while running Fedora 34 pre-beta, I had a bunch
> of PipeWire issues preventing me from successfully doing video
> conferences and listening to music. I reported the issues upstream.
> The problems in
There wasn't an applicable bug open that I could find, so I created
one (BZ 1951072) and nominated it as a blocker so we can discuss it at
the Blocker Review meeting in ~75 minutes.
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
On Mon, Apr 19, 2021 at 02:22:38PM -, Garrett LeSage wrote:
> Could we make this a blocker, so that this newer version (0.3.15) will be
> included in the release?
You can nominate this as a blocker or freeze exception --
https://qa.fedoraproject.org/blockerbugs/propose_bug
is the
Hi, great to hear that problem is solved.
Maybe it's just a FinalFE not necessary a blocker.
Regards
Geraldo
geraldosimao
Em seg, 19 de abr de 2021 11:23, Garrett LeSage
escreveu:
> Hi all,
>
> Several weeks ago, while running Fedora 34 pre-beta, I had a bunch of
> PipeWire issue
Hi all,
Several weeks ago, while running Fedora 34 pre-beta, I had a bunch of PipeWire
issues preventing me from successfully doing video conferences and listening to
music. I reported the issues upstream. The problems included using Bluetooth
headphones (at all), codecs for the headphones
Hello Adam, Yes, the “Not talking installer” as you say, is an issue both with Pipewire and Pulseaudio, although it’s not audio related at all.I personally believe it is something to do with how stuff is displaied, I do not know.Aside from that, everything works fine on Rawhide, so it should work
ess
> the gnome environment is switched to Gnome on xorg, then, it’ll talk
> as expected.
> A workaround is to install the Mate respin, on which the installer
> works beautifully.
> Best regards.
> Francisco
>
Thanks. Is the "not talking in the installer&quo
On Thu, Apr 15, 2021 at 08:54:55AM -0500, Michael Catanzaro wrote:
> Yes, that is not a regression, at least not a recent one. The live
> anaconda is simply not accessible at all. I noticed this for the
> first time last year. It's a shame.
This seems like something worth making a priority for
On Wed, Apr 14, 2021 at 9:28 PM Adam Williamson
wrote:
> Hi folks! Sending to test@ and desktop@, and CCing two folks who
> reported problems.
>
> So I finally got some time today to look into the reports of screen
> reader functionality not working well in F34, with GNOME 40 an
dileepa.tisseraSubject: F34, pipewire and orca (screen reader) Hi folks! Sending to test@ and desktop@, and CCing two folks whoreported problems. So I finally got some time today to look into the reports of screenreader functionality not working well in F34, with GNOME 40 andPipewire. I wrote the latest
Hi folks! Sending to test@ and desktop@, and CCing two folks who
reported problems.
So I finally got some time today to look into the reports of screen
reader functionality not working well in F34, with GNOME 40 and
Pipewire. I wrote the latest F34 nightly live to a USB stick, booted it
on my
[962]: src/service.c:btd_service_connect() a2dp-source profile
connect failed for [mac omitted]: Device or resource busy
pipewire-pulse[2147]: pulse-server 0x55b58a37e700: [Firefox] UNDERFLOW
channel:2 offset:573440 underrun:4096
bluetoothd[962]: plugins/policy.c:reconnect_timeout() Reconnecting
Lukas Ruzicka wrote on Tue, 6 Apr 2021 09:44:22
+0200:
>what happened when you tried to reload the services (or restarting
>computer)?
Ah, the Power-On-Reset panacea. Cures many ills, and cured this one
nicely.
Both prior to pipewire (F33) and with pipewire (F34), it is possible to
obta
Hello,
what happened when you tried to reload the services (or restarting
computer)?
Did it work then or has pipewire been crashing constantly since then?
Let's ignore the Abrt stuff, as it is probably not related to pipewire
anyhow.
Lukas
On Tue, Apr 6, 2021 at 2:37 AM Richard Ryniker wrote
Questions:
1. How can pipewire be configured for 192000 Hz audio output?
2. Are these problems with abrt at this time of Final Freeze
a reason for concern, or normal for the release process?
3. Does the message "Can't find packages for 33 debuginfo files"?
below si
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:
>
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
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
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
>
>
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
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
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
The key appears to be:
>possible to switch between implementations. This will also allow for an
>easy rollback.
Provided this works easily (it should be an explicit part of the test
activity) it is reasonable to accept some instability or missing function
in the PipeWire facility in
e from the beginning. As for
PulseAudio, at this moment I find it is not even noticed, which I take
as a result of it's maturity and stability.
F34 is currently in rawhide state and maybe this is the time to
introduce this change, I am not fully up on the differences between it
and Pipewire to offer a technic
On Mon, 2020-11-23 at 18:20 +0100, Tomasz Torcz wrote:
> On Sun, Nov 22, 2020 at 06:01:18PM +0100, Ralf Corsepius wrote:
> > On 11/20/20 5:26 PM, Ben Cotton wrote:
> >
> > > The pulseaudio package will be uninstalled and pipewire-pulse will be
> > > installed.
On 12/5/19 03:16, Samuel Sieb wrote:
On 12/4/19 12:53 PM, pmkel...@frontier.com wrote:
Is pipewire part of Wayland?
No. It's just necessary for screen casting with Wayland because you
don't have direct access to the screen buffer now. It provides the
"pipe" between the scree
On 12/4/19 20:45, Ed Greshko wrote:
On 2019-12-05 04:53, pmkel...@frontier.com wrote:
I have just recently become aware of pipewire. If my questions are the wrong
ones please feel free to interpret them in a more correct way. I am wondering:
Is pipewire part of Wayland?
From what I've
On 12/4/19 12:53 PM, pmkel...@frontier.com wrote:
Is pipewire part of Wayland?
No. It's just necessary for screen casting with Wayland because you
don't have direct access to the screen buffer now. It provides the
"pipe" between the screen renderer and the application wanti
On 2019-12-05 04:53, pmkel...@frontier.com wrote:
> I have just recently become aware of pipewire. If my questions are the wrong
> ones please feel free to interpret them in a more correct way. I am wondering:
>
> Is pipewire part of Wayland?
>
> From what I've seen so far, it s
I have just recently become aware of pipewire. If my questions are the
wrong ones please feel free to interpret them in a more correct way. I
am wondering:
Is pipewire part of Wayland?
From what I've seen so far, it seems like pipewire will replace
gstreamer, ffmpeg, pulse audio, and jack
40 matches
Mail list logo
