Hi,
Le mer. 8 mai 2024 à 05:21, Grzesiek11 a écrit :
>
> As mentioned by the NEWS entry, 0.5 replaces the old configuration
> system with a new one utilizing JSON. It also states this should be
> transparent for systems using only Debian configuration, however the
> state format (for files
Hello Sergio and Jeremy,
Le sam. 4 mai 2024 à 05:48, Michael Welsh Duggan a écrit :
After updating my linux kernel to 6.7.12-1, I keep getting the following
message in my syslog, once a second:
pipewire-pulse[]: default: snap_get_audio_permissions: kernel lacks
'fine grained unix mediation';
Hello,
Le lun. 15 janv. 2024 à 22:00, K.Ohta a écrit :
>
> I forwarded to upstream.
> See, https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3790 .
> Thank you for your suggestion.
This bug is marked as fixed upstream, so can we close it here as well
or is it still an issue?
Best
Hello Arnaud,
Le mar. 26 mars 2024 à 09:45, Arnaud Rebillout a écrit :
>
> I have worked with upstream on some details, and they release a v0.2
> version. I update the packaging on Salsa. See below for more details.
Thanks!
> Done, now the package is split in two:
>
> -
Control: reassign -1 asahi-audio
Control: notfound -1 0.4.17-1
Control: found -1 1.7-1
Control: affects -1 wireplumber
Hello,
Thanks for this bug report, I reassign it to asahi-audio since the versioned
dependency is on it and not on wireplumber.
Le lun. 25 mars 2024 à 09:45, Thomas Renard a
Hi Arnaud,
Le mar. 12 mars 2024 à 11:33, Arnaud Rebillout a écrit :
>
> Hi Dylan,
>
> On 12/03/2024 4:16 am, Dylan Aïssi wrote:
>
> I don't know if it's false positive or not (I'm really not familiar with
> dynamic linking).
>
> When I look at the x11 module:
>
Hello Arnaud,
Le jeu. 7 mars 2024 à 04:44, Arnaud Rebillout a écrit :
>
> - https://salsa.debian.org/arnaudr/pipewire-module-xrdp
> - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037111
You are right, it's the first pipewire module outside the main package.
So, let's try to clear the way:
Hello,
Le dim. 3 mars 2024 à 10:24, Chris Joelly a écrit :
> In my point of view it is not clearly understandable fromthe package
> desciptions or package docs how pipewire-jack and libspa-0.2-jack relate. I
> understood that pipewire-jack, aside from being a plugin, is a implementation
> of a
Le jeu. 15 févr. 2024 à 16:03, Sander van Grieken
a écrit :
>
> Using dpkg-divert is fine. Maybe adding a single comment line mentioning
> dpkg-divert in /usr/share/alsa-card-profile/mixer/profile-sets/default.conf,
> just above the include of -custom.conf would be helpful.
>
Patching
Hi,
Le mer. 14 févr. 2024 à 13:45, Sander van Grieken
a écrit :
>
> The file /usr/share/alsa-card-profile/mixer/profile-sets/-custom.conf,
> which is packaged as part of pipewire-bin and intended to be customized by the
> user, is packaged in a way that it is overwritten by upgrades.
>
> The
Hi Ohta,
Le dim. 14 janv. 2024 à 10:24, Kyuma Ohta
a écrit :
>
> Sometimes ...mostly be load growth a lot..., pipe-wire daemon or
> pipewire-pulse daemon crashes with below message [1].
>
> This happens misalign of loading to YMM register [2][3].
>
> This crash seems to happen at "vlddqu
Hi,
Do you still have this problem?
Best regards,
Dylan
___
Pkg-utopia-maintainers mailing list
Pkg-utopia-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
Hi,
Are there still problems here?
I'm tempted to close this bug since wireplumber doesn't conflict with
pulseaudio. If there is a conflict it is between pulseaudio and
pipewire-pulse and/or pipewire-alsa. But installing pipewire-audio
should get ride of pulseaudio to avoid any conflicts
Control: tag -1 wontfix
Le jeu. 24 févr. 2022 à 11:33, Laurent Bigonville a écrit :
>
> Would it be possible to split the configuration and plugins files that
> enable the "audio" part of pipewire to an other package? That way
> pipewire-pulse could depend on that package instead?
I tag this
Control: fixed -1 0.4.13-1
Hi Vincent,
Le lun. 18 déc. 2023 à 23:57, Vincent Lefevre a écrit :
>
> FYI, I have a new laptop, where I use wireplumber 0.4.13-1
> (Debian stable) with the same Bluetooth devices (speakers and
> headphones), and there are no such problems with it.
That is a good
Hi,
Le ven. 8 déc. 2023 à 10:48, arne anka a écrit :
>
>* What led up to the situation?
>
> On Dec 6 I upgraded and since the my BT thingy does not connect to my PC
> anymore.
> I am hearing impaired and need to use a BT thingy called RemoteMic+ (by
> Starkey) to be able to listen to music
Le dim. 12 nov. 2023 à 07:15, Ian Bruce a écrit :
>
> pipewire v0.3.84 broke that. It forced the removal of pulseaudio (except some
> libraries),
There was no change in the packaging of pw 0.3.84 forcing the removal
of pulseaudio.
> and disabled HDMI audio completely. HDMI output can still be
Hi,
Le ven. 3 nov. 2023 à 10:57, Eduard Bloch a écrit :
>
>* What was the outcome of this action?
>
> There is NO SOUND comming out of the speaker anymore!! I still see the
> devices there in pavucontrol, it seems to be in the same state as before
> and "... HDMI output" is selected as
Control: tag -1 wontfix
Le dim. 6 févr. 2022 à 00:15, Martin Mares a écrit :
>
> Is it intentional that the systemd user services for pipewire and
> pipewire-pulse
> (and the related socket services) are WantedBy default.target? This causes
> them to be started even for users logged in via SSH.
Hi,
Le lun. 23 oct. 2023 à 01:03, david a écrit :
>
> After using for two days last pipewire version, sound seems more stable now,
> with usual clicks when changing window focus, for example, but without
> cracking
> in youtube videos or mpv films.
>
I mark the bug as fixed with 0.3.83-1 but
Hi Nicholas,
Le mar. 17 oct. 2023 à 19:59, Nicholas D Steeves a écrit :
>
> Oops! Yes, thank you, I forgot to test a newer pipewire after tiring
> and running out of time during the initial investigation.
>
> 0.3.82-1~bpo12+1 solves the bug :)
Great! :-)
> Rather than close this bug as fixed
Hi Nicholas,
Le dim. 15 oct. 2023 à 23:27, Nicholas D Steeves a écrit :
>
> So yeah, it looks like Pipewire's default sample rate is always
> applied when using pipewire or JACK sinks, despite
> "default.clock.allowed-rates" being set, except with using pulseaudio.
> I'm not sure why this is the
Hi Vuk,
Le mar. 17 oct. 2023 à 16:15, Vuk Mirovic a écrit :
>
> Can we get malloc_trim fix backported to stable?
> It can be applied to 0.3.65 easily and shouldn't mess anything.
Sure, but since it's not a security fix, we will have to follow the
"proposed-updates" mechanism [1]. That means it
Le mar. 26 sept. 2023 à 19:54, Philipp Marek a écrit :
>
> Well, actually I'm not complaining about the process being buggy - what is
> worrying me is that the process runs in the logged-on user's context, but
> without the ulimits (as per /etc/security/limits.conf) or any other limits
> set
Le mar. 26 sept. 2023 à 08:00, S. a écrit :
>
> I am following these instructions to enable module-switch-on-connect for
> pipewire-pulse by adding just the section I want to modify in
> /etc/pipewire/pipewire-pulse.conf.d/my.conf
>
>
Le ven. 22 sept. 2023 à 17:09, Philipp Marek a écrit :
>
> I just got my pipewire process OOM killed:
>
> [62615.563546]
>
Hello all,
The next version of pipewire depends on webrtc-audio-processing-1 >= 1.2 for
its echo-canceller module. Although it is an optional dependencies, upstream
advised me not to disable it to avoid too many complaints. That means, I
won't be able to update pipewire in debian anymore until we
Hello Michael,
Le dim. 3 sept. 2023 à 10:45, Michael Cree a écrit :
>
> pipewire FTBFS on Alpha due to test suite failure. From the build
> log [1]:
>
Upstream has pushed two commits to fix the build on alpha:
-
Hello,
Thank you for this bug report.
Le jeu. 31 août 2023 à 13:42, John Smith a écrit :
>
> Hello, I noticed this line in dmesg after a Bluetooth audio loss:
> [96307.727270] traps: wireplumber[2128] general protection fault
> ip:7f7b0145d29f sp:7f7b03ffe950 error:0 in
>
Hi Boud,
Le mar. 29 août 2023 à 00:27, Boud Roukema a écrit :
>
> PROPOSAL (1):
>
> Should the user be informed when doing the system upgrade? More specifically,
> would a one-line warning to the user be considered acceptable, as a
> post-install
> script? E.g. something like:
>
> "Please
Hello Boud,
Le ven. 25 août 2023 à 13:09, a écrit :
>
> * What outcome did you expect instead?
>
> What I expected was that the dpkg/apt system and/or the systemd system
> should have recognised that the old 'pipewire-pulse' process was invalid
> and should have forced it to restart with the
Le lun. 28 août 2023 à 17:31, Francesco Potortì a écrit :
>
>
> Wow. Thanks for the info.
>
> Should I just install wireplumber and everything should work?
>
Yes that should work after a reboot to be sure pipewire-media-session
doesn't run anymore.
For safety, you can install the meta package
Hello Francesco,
Le lun. 28 août 2023 à 14:09, Francesco Potortì a écrit :
>
> Package: pipewire-media-session
>
> Two strange things in logs by pipewire-media-session.
>
> 1) format of log timestamp is not always the same
>
> 2) repeatedly complains about a missing default device
>
Thanks for
Hi,
Le sam. 5 août 2023 à 11:42, B a écrit :
>
> After removing almost all pulseaudio packages, except those linked to
> other programs, I rebooted and pipewire-pulse was gone (pipewire and
> wireplumber were launched as usual).
Not sure what happened, maybe a package that should have
Hi,
Le ven. 4 août 2023 à 23:21, Jiff a écrit :
>
> Ze error :
> ==
> Uninstall *pulse* except those required by other packages.
>
> Ze cure :
> =
> apt install pavucontrol paprefs
>
I don't understand what is your issue, can you elaborate?
pavucontrol and paprefs are not
Le lun. 31 juil. 2023 à 00:21, Nick a écrit :
>
> On rebooting, a process called wireplumber consumes most of the cpu.
> Sound does work. If I kill the process, cpu usage falls, my fan stops
> spinning and I no longer have sound. I have to kill wireplumber on
> each reboot (or let it try to fry
Hi Sebastien,
Le mar. 4 juil. 2023 à 16:45, Sebastien Bacher a écrit :
>
> The recent update added a depends on libffado, that component is
> currently in Ubuntu universe so it means we need to build without it
> there. Could you consider using the attached patch so we can keep the
> package in
Le lun. 3 juil. 2023 à 18:32, Russell King
a écrit :
>
> On Monday, 3 July 2023 16:36:16 BST Dylan Aïssi wrote:
> > Are you using your Anker Soundcore 2 via bluetooth? It could be a
> > bluetooth issue. Could you try to connect your speaker via a jack
> > wire to dis
Le jeu. 15 juin 2023 à 23:57, AlMa a écrit :
> Jun 15 04:42:15 AnonymizedMachineName wireplumber[1124]:
> GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner
> Jun 15 04:42:15 AnonymizedMachineName dbus-daemon[957]: [system]
> Successfully activated service
Le mar. 4 juil. 2023 à 00:35, AlMa a écrit :
>
> I've never been able to make my TV tuner work in Debian. Even scanning
> the channels has never worked properly. This problem might,
> hypothetically, have its roots partially in the bug here or in the
> corresponding kernel driver. Hence an
Control: fixed -1 0.3.71-2
Hello Julian,
Le mar. 4 juil. 2023 à 08:34, Julian Groß a écrit :
>
> it wasn't a one-time thing, but I cannot reproduce the issue any more on
> the current pipewire package version (0.3.71-2+b2) on Debian Trixie.
> So I would presume that his was fixed in a recent
Le sam. 1 juil. 2023 à 22:50, AlMa a écrit :
>
> > I suspect a bug in the driver handling your /dev/video4 device.
> > Do you have more information about what device is your /dev/video4?
>
> Yes; it seems to be my TV-Tuner Hauppauge WinTV HVR 5525 HD:
>
Since it's not a vital part of pipewire,
Hi,
Le jeu. 22 juin 2023 à 14:16, Remi a écrit :
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
>* What was the outcome of this
Hi,
Le lun. 3 juil. 2023 à 15:39, Russell King
a écrit :
>
> Using pipewire with JuK under Debian Stable (Bookworm) with an Anker
> Soundcore 2 results in the beginning of every track being messed up.
> I've also noticed similar oddities when playing audio from Firefox.
Are you using your Anker
Hi,
Le mer. 11 janv. 2023 à 22:27, Julian Groß a écrit :
>
> my Intel HD Audio device seems to be causing pipewire-pulse to spam syslog
> with "source not ready" and "sink not ready" messages.
>
Is this a one-time bug? Are you able to reproduce it with bookworm? Or
even better with pipewire
Hi,
Le jeu. 6 avr. 2023 à 16:15, Zachary E. Braun a écrit :
>
>First, appologies if this is the wrong package to report this to.
>I have a Tascam Portacapture X8 which is able to work as an audio
> interface. In theory, the built-in microphones should pass to the operating
> system
Le lun. 3 avr. 2023 à 18:54, Itai Shaked a écrit :
>
> I am at a loss since there seems to be zero usable information in the logs,
> just that the service is killed for some (unspecified?) reason.
>
Can you manually start pipewire with an increased verbose level?
The following command should
Le mer. 14 juin 2023 à 17:30, AlMa a écrit :
> Jun 13 21:00:22 AnonymizedMachineName pipewire[1146]: spa.v4l2:
> '/dev/video4' VIDIOC_ENUM_FRAMESIZES: Unpassender IOCTL (I/O-Control)
> für das Gerät
> Jun 13 21:00:22 AnonymizedMachineName pipewire[1146]: spa.v4l2:
> '/dev/video4'
Le mar. 13 juin 2023 à 22:51, AlMa a écrit :
>
> Here, wireplumber 0.4.13-1 and pipewire:amd64 0.3.65-3 are installed. I
> have no idea whether the pipewire issue 3194 at gitlab.freedesktop.org
> resolves it or not.
>
As explained in the upstream bug, these warnings messages have been demote
to
Le mer. 14 juin 2023 à 17:03, AlMa a écrit :
>
> What is SPA? The package pipewire-libcamera is NOT installed; it seems
> to be not recommended or even suggested by any other package. So besides
> a guess based on the name (and pipewire-libcamera may or may not be
> relevant), there's no way of
Hello,
Le dim. 16 avr. 2023 à 01:42, Al Ma a écrit :
>
> $ sudo aptitude show pipewire| grep Version
>
> Version: 0.3.56-1
This version is not available in Bullseye, can you upgrade to the latest version
available in bullseye-backports (i.e. 0.3.65-2~bpo11+1)?
> $ sudo aptitude show
Le sam. 18 mars 2023 à 14:51, graeme vetterlein
a écrit :
>
> I, for one, have had no sound for the past 4 months. Not personally critical
> as it's an unstable dev system, not main dev machine.
>
Do you have no sound at all or choppy sound like you said in [1].
Have you tried using speakers
Hi,
Le mer. 22 févr. 2023 à 18:27, a écrit :
>
> the issue, looks like this description
>
> https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6207
If it is the same bug then it is not a pipewire bug but a gnome-shell
bug which was fixed in gnome-shell 43.3.
This version of gnome-shell has
Hi,
Le mer. 8 févr. 2023 à 13:00, Tomas Janousek a écrit :
>
> Can we please cherry-pick
> https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/5552ff7fdd76116e10911ddedfeb7927db6d500e
> and
>
Package: pipewire-media-session
Severity: important
Tags: trixie
pipewire-media-session is dead upstream and must not be shipped with Trixie.
Wireplumber must be used instead.
https://gitlab.freedesktop.org/pipewire/media-session/-/commit/80dae7e2
___
Hello,
Le sam. 28 janv. 2023 à 12:00, Wouter Verhelst a écrit :
>
>
> I did not install pipewire manually; it was installed through dependencies.
>
It would be great to understand how pipewire pkgs have been pulled on your
system since I don't know which packages are installed by awesome. But
Hello Wouter,
Le ven. 27 janv. 2023 à 11:00, Wouter Verhelst a écrit :
>
> The pipewire upstream troubleshooting guide suggests I look at
> journalctl output as a first step in troubleshooting things. That
> reveals:
>
> wouter@pc220518:~$ journalctl -xe | grep pipewire
> jan 27 11:04:01
Hello,
Le mer. 25 janv. 2023 à 22:13, Simon McVittie a écrit :
>
> Pipewire maintainers: do you have an opinion on whether gnome-core should
> return to depending on the individual dependencies of pipewire-audio,
> rather than on the metapackage?
I intentionally marked pipewire-audio in
Hello Erich,
Le dim. 22 janv. 2023 à 00:45, Erich Eickmeyer a écrit :
>
> The introduction of the "Recommends: pipewire-alsa" line in the debian/control
> file has reintroduced the problem resolved by bug #1020903 in which pipewire-
> pulse is causing a conflict with pulseaudio, albiet
Control: severity -1 normal
Le dim. 22 janv. 2023 à 18:15, Marco d'Itri a écrit :
>
> If I replace pipewire-media-session with wireplumber then playing video
> in browsers (e.g. Youtube and other similar sites, or even just embedded
> tags) stutters and stops. Just pressing the mute button in
Hello,
Le ven. 6 janv. 2023 à 21:48, Dylan Aïssi a écrit :
>
> Le ven. 6 janv. 2023 à 19:57, Bob Hauck a écrit :
> >
> > There was apparently a bug already filed and closed about this. Subsequent
> > to my report I received the following note that there is a commit t
Thanks!
Le ven. 6 janv. 2023 à 19:57, Bob Hauck a écrit :
>
> There was apparently a bug already filed and closed about this. Subsequent to
> my report I received the following note that there is a commit to master that
> fixes the issue.
>> Distro maintainers including the Debian one were
Hi Bob,
Le ven. 6 janv. 2023 à 05:21, Bob Hauck a écrit :
>
>* What was the outcome of this action?
> My adapters support both hfp and a2dp profiles but only a2dp shows up
> in pavucontrol and in KDE audio configuration. The a2dp profile does
> work with LDAC and AptX
Control: found -1 0.3.61-1
Works with 0.3.60-3 but fails with 0.3.61-1. Now, we have the version
introducing this regression.
___
Pkg-utopia-maintainers mailing list
Pkg-utopia-maintainers@alioth-lists.debian.net
Bonjour Patrice,
Le mer. 14 déc. 2022 à 19:27, Patrice Duroux
a écrit :
>
> It would be very nice.
The NEWS.rst file is already installed with each wireplumber binary packages
since 0.4.8-1 [1] as you already reported #1003836 [2] .
Am I missing something?
[1]
Le dim. 4 déc. 2022 à 23:28, James Bottomley
a écrit :
>
> On Sun, 2022-12-04 at 22:42 +0100, Dylan Aïssi wrote:
> > Le sam. 3 déc. 2022 à 15:45, James Bottomley
> > a écrit :
> > >
> > > I just tested this out with the same results as previously reported
>
Hi,
Le dim. 4 déc. 2022 à 15:27, Adam Borowski a écrit :
>
> On a machine with no physical PC honker, I have the x11 bell enabled.
> And that causes random but frequent crashes in pipewire:
>
Random crashes can happen when the module is loaded twice.
And this module is loaded by default conf
Le sam. 3 déc. 2022 à 15:45, James Bottomley
a écrit :
>
> I just tested this out with the same results as previously reported
>
Do you mean you don't have sound at all using pipewire 0.3.61 in a QEMU VM?
___
Pkg-utopia-maintainers mailing list
Hi,
Le mar. 29 nov. 2022 à 15:51, Hans-Christoph Steiner a écrit :
>
> hans@delbin ~$ sudo journalctl | grep wire
> ...
> Nov 26 22:54:40 delbin wireplumber[1092]: stopped by signal: Terminated
> Nov 26 22:54:40 delbin wireplumber[1092]: disconnected from pipewire
>
> Versions of packages
Control: tag -1 wontfix
Le jeu. 24 nov. 2022 à 03:27, Jason Lewis a écrit :
>
> Fix involves adding "{ path = "pactl" args = "load-module
> module-switch-on-connect" }"
>
The switch-on-connect module is disabled by default because too much
agressive in its way to handle switches. I won't
Hi Sebastien
Le lun. 21 nov. 2022 à 21:39, Sebastien Bacher a écrit :
>
> would it make sense to turn the option on?
>
Sure, it's on the top of my todo list.
Best,
Dylan
___
Pkg-utopia-maintainers mailing list
Control: fixed -1 0.4.12-1
Hi,
Le ven. 18 nov. 2022 à 17:30, Eric Cooper a écrit :
>
> It doesn't seem to have happened again.
>
Thanks. I am marking it as fixed since 0.4.12-1, but will keep this bug report
open for a while just in case.
Best,
Dylan
Bonjour Alain,
Es tu le Alain de debian-facile, ici :
https://debian-facile.org/viewtopic.php?pid=388561#p388561
Le sam. 12 nov. 2022 à 10:03, alain a écrit :
>
> yes the conflict between pulse audio and pipewire-pulse is still going on.
> I just updated my sid.
> so pipewire-pulse has been
Hi Francois,
Le jeu. 13 oct. 2022 à 22:21, Francois Le Hir a écrit :
>
> I was able to fix the issue on my side.
> The problem (for my situation) was a conflict between pulseaudio and pipewire
> as both were running on my system at the same time and pipewire-pulse.service
> was masked
Hi Eric,
Le dim. 18 sept. 2022 à 20:03, Eric Cooper a écrit :
>
> I'm not sure wireplumber is at fault here, but this has only started
> happening since I switched from pulseaudio to pipewire a few days ago.
> I usually have my default volume at about 30%, according to
> pavucontrol. But when I
Hello Alexandre,
My apologies for not responding earlier.
Do you still have these problems with pipewire or have they been solved
with the new versions?
Best,
Dylan
___
Pkg-utopia-maintainers mailing list
Hi Chris,
Le jeu. 17 nov. 2022 à 17:21, Chris Nospam a écrit :
>
> As you have suggested, I have made an entry to the upstream bug report that I
> am probably also affected, although the issue seems to be already closed.
>
Thanks!
I received the notification from the upstream bug while I was
Hi Chris,
Le mer. 16 nov. 2022 à 12:27, Chris Nospam a écrit :
>
> I am using a kvm virtualized installation of bookworm (I did not try it yet
> on my bare metal installation). Below see some informations which may help.
> Within syslog I find no spefic entries via 'grep pipewire' which could
Some news regarding an eventual conflict between pulseaudio and pipewire-pulse.
>From time to time upstream discussions arise concerning closed-source software
(mainly old games) which check if the /usr/bin/pulseaudio binary is available
otherwise they fail to output sound [1].
The solution is
Hi Sebastien,
Le lun. 10 oct. 2022 à 14:00, Sebastien Bacher a écrit :
>
> Reopening, I think the decision to revert is unfortunate. Nothing is
> going to remove pulseaudio on upgrade as pipewire-pulse gets pulled in
> as the new default; and the pulseaudio package provides an alsa
>
Le mar. 11 oct. 2022 à 21:27, alain a écrit :
>
> hi :) :) :)
Bonjour Alain,
> i don't know if i post at the right place .
No, I don't think you are talking about the same issue firstly reported here.
It should be better to open a new bug report.
>
> i have no more sound too while using
Le lun. 10 oct. 2022 à 11:00, Ben Morris a écrit :
>
> I have no sound at all on my system. Both my sound devices (the Intel
> sound built in to my motherboard and the HDMI out on my Radeon) show up
> as expected in Plasma, pavucontrol, etc., but nothing seems to be able
> to play audio. Outputs
Control: tags -1 - unreproducible + confirmed
Hi Gabriel,
Le mer. 5 oct. 2022 à 09:00, Gabriel Corona
a écrit :
>
> I collected some stack traces and apparently the problem happens in
> libcanberra-pulse :
> ...
> Apparently clicking on a menu triggers a canberra notification which
> goes
Hi Maurizio,
Le lun. 3 oct. 2022 à 13:48, Maurizio Avogadro a écrit :
>
> while within Gnome I can make the audio subsystem work by manually selecting
> the "Play HiFi quality Music" profile (defined in ALSA UCM) of my onboard
> Realtek ALC4080 USB audio card, in KDE Plasma its only available
Control: fixed -1 0.4.12-1
Hi Vincent,
Le ven. 30 sept. 2022 à 16:30, Dylan Aïssi a écrit :
>
> If this module if not loaded, then your autoswitch is done via a behavior of
> pulseaudio which prioritize previous configured defaults. The same logic has
> just been merged in
Hi Vincent,
Le jeu. 29 sept. 2022 à 12:39, Vincent Lefevre a écrit :
>
> The problem is still there. The headphones autoconnect as usual but
> the audio is not switched to them automatically. I need to manually
> do the switch from pavucontrol. When I switch off the headphones,
> the audio is
Hi,
Le mer. 28 sept. 2022 à 12:03, Daniel Vacek a écrit :
>
> I was wondering, could both services (pulseaudio and pipewire-pulse) still be
> co-installed at the same time?
Yes, both can be installed at the same time. In some (rare?) cases [1],
conflicts can appear, this is why a conflict
Le mar. 27 sept. 2022 à 11:44, Dylan Aïssi a écrit :
> Make wireplumber sending a signal when it is ready seems the proper to way
> to follow. Thanks for your suggestion! These changes should be done directly
> in wireplumber/pipewire, I will report it to upstream.
>
Forwarde
Hi Matthias,
Le lun. 26 sept. 2022 à 12:09, Matthias Heinz a écrit
:
>
> I'm certain now that this is a race-condition between wireplumber and
> pipewire-pulse. Even though wireplumber should be started before pipewire-
> pulse the Type= to start the service is just "simple", which means
Hi,
Le mar. 27 sept. 2022 à 10:51, Samuel Thibault a écrit :
>
> Hello,
>
> Dylan Aïssi, le mar. 27 sept. 2022 10:29:15 +0200, a ecrit:
> > Le lun. 30 mai 2022 à 16:57, Vincent Lefevre a écrit :
> > > On 2021-10-29 18:23:03 +0200, Vincent Lefevre wrote:
>
Le lun. 30 mai 2022 à 16:57, Vincent Lefevre a écrit :
>
> On 2021-10-29 18:23:03 +0200, Vincent Lefevre wrote:
> > I use bluetooth speakers by default. When I connect my bluetooth
> > headphones, I want the system to automatically switch from the
> > speakers to the headphones. This is how it
Hi,
Le ven. 23 sept. 2022 à 16:51, Christophe Lohr
a écrit :
>
>
> The hardware is well detected by the system:
>
> But pipewire does not see the card (only the dummy pulseaudio sink):
>
> What can I do?
>
Please try with pipewire 0.3.58-2 in debian/unstable. This version
should fix this issue.
Le mar. 20 sept. 2022 à 12:45, Julian Andres Klode a écrit :
>
> On Tue, Sep 20, 2022 at 10:18:21AM +0200, Raphaël Hertzog wrote:
>>
> > APT will not let me upgrade pipewire-pulse to the latest version because
> > I have gnome-core installed. It will prefer to deinstall pipewire-pulse:
> >
>
>
H,
Le ven. 16 sept. 2022 à 19:51, Matthias Heinz a écrit
:
>
> after upgrade wireplumber from 0.4.11-3 to 0.4.11-5 it fails to somehow
> realize
> what the target of the last stream was, if it was not the default device.
> pavucontrol just reports it as "Unknown output" then.
>
In Wireplumber
Hi,
Le sam. 17 sept. 2022 à 18:57, Dmitry Nezhevenko a écrit :
>
> Btw is there any reason to do this copy manually? Maybe just put
> /etc/alsa/conf.d/99-pipewire-default.conf to pipewire-alsa?
>
Since pipewire-alsa has been split from the previous
pipewire-audio-client-libraries package, it
Hello Raphaël,
Le lun. 19 sept. 2022 à 14:13, Raphael Hertzog a écrit :
>
> It seems to work now with firefox 104.0-1 and wireplumber 0.4.11-4.
>
I am glad it is solved on your side.
After having discussed with upstream about this issue, there was no
obvious culprit.
I will keep this issue
Hi,
We have two different issues here.
Le dim. 18 sept. 2022 à 18:03, mheyes a écrit :
>
> wireplumber v0.4.11-3 was installed previously, working properly. The latest
> update to v0.4.11-5 resulted in no audio. Reverted to pulseaudio, then tried
> to reinstall wireplumber. But, wireplumber
Hi Clément,
Le jeu. 15 sept. 2022 à 17:33, Clément Hermann a écrit :
>
> I'm a happy user of pipewire since a few month.
>
Glad to see a happy user :-)
> I believe this is an upstream regression:
> https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2671 (fixed in
> 0.3.58 it seems, but
Hi Raphaël,
I tried to reproduce this issue, but I did not succeed.
Le jeu. 9 juin 2022 à 14:51, Raphaël Hertzog a écrit :
>
> When I had the issue, I tried to open "about:support", it also triggered
> one of those freezes but in the end I was able to see that firefox was
> using "alsa" as
Control: tag 978621 moreinfo
Hi Silvério,
Is this crash still reproducible with latest pipewire and KDE versions?
I have seen several issues between pipewire and KDE solved, thus I am
temped to close this bug if it is no longer reproducible.
Best,
Dylan
1 - 100 of 129 matches
Mail list logo
