search in #devuan for "pulseaudio"
This shows up to 500 results in reverse day order, with "best
match" first for days that match well enough.
Note: it presents the stored timestamp and not adjusted for
timezone. The stored timestamps are mostly UTC, but some are UTC+11,
and some are UTC+10, so please refrain from making bold statements
about the temporal exactness of these logs.
2026-10-19.log [02:17:53] <gnarface> i don't use pipewire or pulseaudio here, but i'm guessing that you need to launch it from the user's session, just like on the host
2026-08-26.log [02:46:55] <boots_> Hi. Using the provided docs for setting up pipewire, wireplumber, and pipewire-pulse, audio seems to not return after computer returns from sleep. Will work again if I log out into the DM and log back in.
2026-08-26.log [02:54:36] <gnarface> no, but i don't let my computers sleep and i don't use pipewire/pulseaudio
2026-08-13.log [00:57:06] <gnarface> ira-peach: i seem to remember debian pulled bluetooth alsa support in favor of embedding it in pulseaudio a long time ago, to get it working without pulseaudio or pipewire now i think you have to build bluez-alsa from out of distro sources... not sure if that's the same as bluez-alsa-utils or not, but i think then you also need to add something to your alsa config that refers to the bluetooth device by mac address
2026-08-13.log [01:01:35] <gnarface> if you're using pulseaudio or pipewire on top of this though, you shouldn't need it
2026-08-13.log [01:09:52] <ira-peach> Hmm... The plot thickens. Originally I moved away from pulseaudio because it often seems to be the cause of my audio glitches. I'll try setting up pipewire. Thanks! :D
2026-08-12.log [15:29:44] <rustyaxe> i have pipewire, pipewire-pulse, and wireplumber running; no pulseaudio. if they arent running, i cant connect it in blueman
2026-08-12.log [15:32:44] <marcfp> i shall install pipewire and pulseaudio server ?
2026-08-12.log [15:33:04] <rustyaxe> you can install one or the other not both. I personally would recommend pipewire over pulseaudio
2026-08-11.log [13:30:37] <Guest96> I think its the pulse audio mixer thing
2026-08-11.log [13:59:02] <fsmithred> assuming you're using pulseaudio
2026-08-11.log [14:06:17] <fsmithred> again, I don't know if it's relevant if you're using pulseaudio or pipewire
2026-08-11.log [14:27:47] <Guest96> basically pulse audio/pavu is incorrectly reading my microphone as dual audio input and output and then defaulting to it for output on reboot
2026-08-11.log [14:44:33] <fsmithred> is pulseaudio set to start in the desktop startup applications?
2026-08-11.log [14:47:01] <fsmithred> are you using pipewire or pulseaudio?
2026-08-07.log [02:29:54] <gnarface> i don't even use pulseaudio or pipewire or jack, i'd much prefer everything was setup to expect bare alsa and we just had better device-specific config files to make it happen, but everyone migrating to devuan lately seems to like it except this one thing that makes us look ghetto, and it's hard to imagine it wasn't orchestrated that way specifically by upstream
2026-07-31.log [19:40:11] <CDBurner> Hi. Me again. Have tried and failed to setup pulseaudio (works but audio adjustment commands automatically mute my audio every time I adjust until I untoggle mute. So following the pipewire recommendations in release notes, I tried that instead. The script to be put in .profile works, but the one for .xsessionrc makes it to where my user account
2026-07-31.log [19:56:13] <gnarface> pipewire should work if you: 1) start it as your user 2) fully removed pulseaudio
2026-07-31.log [19:56:54] <gnarface> i think there might be a howto thread in the forums about it, but i don't use pulseaudio or pipewire here, i prefer bare alsa
2026-07-26.log [18:04:25] <gnarface> did you make sure pipewire was getting started properly, and conflicting pulseaudio stuff was no longer installed or running? (sorry if this was covered, i think i missed your issue prior)
2026-07-26.log [18:05:32] <lottibotti> How do I ensure that pulse audio is not fouling up with pipewire? Please forgive me it has been decades since I last played in Linux
2026-07-26.log [18:06:43] <fsmithred> I think if you install pipewire-audio it will remove all conflicting pulseaudio stuff. You can (and should) keep pavucontrol.
2026-07-26.log [18:08:58] <rustyaxe> pipewire-pulse should replace pulseuadio package, if not manually purge it
2026-07-26.log [18:13:34] <gnarface> yea, that's important, while pulseaudio or pipewire is actually working, you won't actually see alsamixer controls in alsamixer, you'll see puleseaudo/pipewire simplified volumes
2026-07-23.log [12:11:01] <freem> or maybe pulseaudio/pipewire can emulate the feature somehow, or something like that
2026-07-19.log [13:49:49] <gnarface> gross if it actually needs it, but might be a false positive if pulseaudio used to be installed
2026-07-19.log [13:50:38] <gnarface> was pulseaudio or pipewire formerly installed then removed?
2026-07-19.log [13:54:51] <gnarface> oh, or was this a home directory copied from another install that did have pulseaudio/pipewire? does ~/.pulse/ and/or ~/.pulse-cookie exist?
2026-07-19.log [14:07:41] <rustyaxe> joerg: i solved 100% of my pulseaudio problems by replacing it with pipewire/pipewire-pulse ;)
2026-07-19.log [14:58:34] <fsmithred> there are also messages that I think are about pulseaudio, and those have always been there.
2026-07-11.log [04:43:57] <gnarface> if you're using pulseaudio or pipewire you may have to manually add them to your gui startup tasks
2026-07-11.log [04:44:21] <gnarface> i think pulseaudio might be fine but pipewire might need manual starting
2026-07-08.log [17:04:48] <Guest39> Is PipeWire supported on Devuan, or should I use PulseAudio?
2026-07-08.log [17:53:21] <fsmithred> Guest92, are you using pipewire or pulseaudio?
2026-06-29.log [02:51:49] <centurion_dan> @onefang: portaudio is supposed to be the replacement for the vile poetteringware pulseaudio and JACK with even better latency capabilities and just work with all the PA clients... However whether that is true is hard to guage at this point.
2026-05-28.log [19:28:58] <linuxb2> One time it says can't connect to pulse audio at all. The next time it can connec to pulse audio but no card detected, then third time I login and it connects to pulse audio and card detected and sound works.
2026-05-02.log [21:27:05] <rwp> The Debian firefox package is compiled to use either alsa or pulseaudio so if you use the Debian version you don't need apulse. But if you download the self-updating Mozilla version as I do then apulse is needed to work with ALSA without PA installed.
2026-04-17.log [17:18:32] <rustyaxe> i'll be revisiting alsa softmixing on there soonly, but as it sits $software expects pulseaudio (or pipewire-pulse).
2026-04-17.log [17:18:36] <gnarface> rustyaxe: wait, really? what about without pulseaudio/pipewire?
2026-04-17.log [17:19:21] <gnarface> that's supposed to be against the rules for them to do that, because pulseaudio is supposed to be reverse-compatible with alsa and pipewire is supposed to be reverse-compatible with pulseaudio...
2026-04-17.log [17:19:52] <rustyaxe> some soft modem bits. Nah they wrote it using pulseaudio (because it was part of a gui application where it made sense) but i've ripped it out
2026-04-12.log [18:57:37] <goldfishRX> even ading [SDL] audiodrivername=alsa to the config file kdenlive-appimagerc it still trys to use pulse audio
2026-04-12.log [20:23:42] <mtcycler106> I don't have any good ideas, I have pulse audio running, so that works.
2026-04-12.log [20:33:03] <goldfishRX> it be a real shame it has a hard dependancy on pulseaudio
2026-04-02.log [16:55:07] <gnarface> maurice: check if you are using pulseaudio or pipewire, if you're using pipewire you may have to configure it to start yourself
2026-04-01.log [00:12:55] <sadnehs> Hey I'm trying to switch from Pulse Audio to Pipewire, and following this solution: https://github.com/Vencord/Vesktop/issues/500#issuecomment-2094367152 But I of course can't use systemctl. I installed the pipewire commands, but now I can't find any Pipewire nor Pulseaudio services. I know runit uses a system where you sym-link /etc/sv to /var/service, but I don't have any audio services listed in /etc/sv/ to begin with
2026-04-01.log [00:52:16] <sadnehs> yeah I got no audio, I'm not doing that hacky bash script crap. I'm switching back to Pulseaudio for today
2026-04-01.log [04:05:29] <rwp> I just use ALSA for audio. It just works. And then I don't have to mess with pulseaudio.
2026-03-19.log [19:53:55] <sh4> IIRC the debian installer asked me for whether to use pulseaudio or pipewire, where i selected pipewire, but no such question was asked in devuan
2026-01-16.log [16:56:59] <APic> Yes, i guess PulseAudio can use it without ALSA
2026-01-16.log [16:57:27] <APic> With alsamixer i can only select the Devices PulseAudio and HDA Intel PCH
2026-01-04.log [22:30:49] <devuanconsumer> but it's already installed not sure why the sound is not working and pulse audio says "establishing connection" forever...
2026-01-04.log [22:34:08] <gnarface> devuanconsumer: not sure what's going on with that exactly, but some people who have problems with pulseaudio have reported switching to pipewire fixes it, and some people who have problems with pipewire have reported that switching to pulseaudio fixes it (in theory it should work without either, too)
2026-01-04.log [23:14:15] <tempforever> devuanconsumer: probably easiest fix is 'apt install pulseaudio' then reboot. if you'd rather use pipewire there are instructions on the forum on how to get that started
2026-01-04.log [23:18:20] <tempforever> I think cinnamon pulled in pulseaudio (?) don't remember for certain now
2026-01-04.log [23:43:28] <n4dir> probably pipewire-pulse is sufficient, but perhaps pulseaudio is even a dependency of it
2025-12-21.log [21:39:09] <fsmithred> nemo, for pipewire, some manual intervention is required. I'm surprised you got pipewire instead of pulseaudio with mate.
2025-12-16.log [15:58:17] <rknop> For what it's worth, just in case it matters, I've also gone from pulseaudio to pipewire.
2025-12-16.log [19:39:49] <e3d3> happy to announce that I've got my bluetooth working as it should (by replacing pulseaudio-module-bluetooth with libspa-0.2-bluetooth)
2025-12-15.log [16:48:12] <LinuxLuser> Hey, good folks. I have a fresh install of Devuan Excalibur with Gnome desktop. Really happy with most things but I have no sound. Looked into it and there's no sound server running. I guess the default now is PipeWire instead of PulseAudio (Yeah, I haven't really been keeping up with Desktop stuff). Well, there's no PipeWire system service. Which is fine as long as the desktop loads something for the user. But I checked that too and nothing.
2025-12-01.log [02:27:30] <gnarface> pipewire seems to be becoming a popular stand-in for pulseaudio, but i haven't really talked to anyone using it for jack
2025-12-01.log [02:29:38] <gnarface> i know that if you're using pipewire as a stand-in for pulseaudio, the actual pulseaudio install will interfere, but pavucontrol is still used
2025-12-01.log [02:29:55] <n4dir> i don't really care for pulseaudio, to be honest (also that seems to work)
2025-12-01.log [02:38:29] <gnarface> yea i only ended up switching to pipewire on my phone (which previously needed pulseaudio instead) because it seemed that someone upstream in Arch had strategically broken pulseaudio to force a mass migration to pipewire
2025-11-24.log [12:10:46] <gnarface> hacksenwerk: the firefox-esr package should work fine with bare alsa, the pulseaudio/apulse thing should only be needed for the firefox build direct from mozilla
2025-11-23.log [20:54:48] <tomg_> I'm still new to pulseaudio/pipewire stuff. I'm using pipewwire now
2025-11-20.log [01:18:38] <chozorho> hey, uhh, is there any reason why my sound broke after doing an upgrade? It happened weeks ago but I am only just getting around to debugging it. When I try to re-install gnome, I see that it is uninstalling pulseaudio and replacing it with pipewire-audio... but I thought my browser (firefox developer edition) requires pulseaudio. What am I missing?
2025-11-20.log [01:25:34] <rwp> fsmithred, Is "apulse" still relevant for Excalibur? (I don't remember now. I am still using it because I removed pulseaudio.)
2025-11-20.log [01:29:09] <rwp> Don't do any extra work for it. It was just a topical wondering due to the above question. Sound is working for me okay using it without pulseaudio.
2025-11-20.log [01:31:09] <rwp> The Debian packaged browsers don't need it. But the Mozilla self-updating Firefox requires pulse audio. I start it with "apulse firefox" and that works swimmingly.
2025-11-14.log [14:28:19] <fsmithred> maybe pulseaudio, but if so you would see that as the sound card in alsamixer
2025-11-14.log [14:32:38] <jab> fsmithred: I ran dpkg -l | grep pulse -> libcanberra-pulse:ppc64el, libkf6pulseaudioqt5:ppc64el, libpulse-mainloop-glib0:ppc64el, libpulsedsp:ppc64el, pipewire-pulse, pulseaudio-utils
2025-11-14.log [14:34:10] <fsmithred> or you could install pulseaudio. My unscientific analysis is that pipewire sounds better.
2025-11-11.log [01:49:42] <blinux> gnarface, as far as pulseaudio I'm using startx. I'm not sure if that counts as a session manager.
2025-11-11.log [02:07:56] <gnarface> blinux: no, startx doesn't count as a session manager, so i'm not sure how you'd be expected to get pulseaudio running in this case, whether you'd want to start it from the window manager's startup processes or start it the old-fashioned way as a system daemon and somehow give your self permission to access it from its config directly is more effort than i've ever put into figuring it out - someone around here might know
2025-11-11.log [02:25:02] <paculino> blinux, are you by chance starting pulseaudio that way because of the buffer interaction with alsa?
2025-11-11.log [03:15:35] <blinux> I just realized I meant to do pipewire, not pulse audio.
2025-11-11.log [03:21:40] <blinux> That is surprising. So what do you do for sound? These instructions for pipewire? ALSA or what? Pulseaudio was replaced in Debian quote a while ago.
2025-11-11.log [03:23:57] <fsmithred> pulseaudio gets installed by default with the full desktop environment.
2025-11-11.log [03:24:20] <blinux> I'm surprised to hear Devuan is using pulseaudio by default.
2025-11-11.log [03:27:07] <blinux> I had to create it. I'm going to log out/reboot and see if sound works with pipewire. I uninstalled pulse audio too.
2025-11-11.log [03:28:35] <rrq> my default is to use neither pulseaudio, pipewire nor jack; just the plain ALSA audio.
2025-11-10.log [22:25:34] <blinux> I just installed pulse audio for sound. Is there some special way to get it running with Devuan? I tried running pulseaudio and it says "Daemon already running"
2025-11-10.log [22:26:19] <blinux> I tried pulseaudio -k to kill it and pulseaudio -D to start up the daemon again.
2025-11-10.log [22:29:49] <golinux> Usually folks here want to get RID of pulseaudio!
2025-11-10.log [22:36:01] <gnarface> blinux: typically these days pulseaudio is started as your user along with your X session, by the session manager, i think
2025-11-09.log [17:29:49] <rustyaxe> that and lack of random clicks and pops that pulseaudio has ;)
2025-11-09.log [17:29:53] <fsmithred> pavucontrol without p-p-pulseaudio
2025-11-03.log [21:36:01] <gnarface> jab: make sure pulseaudio/pipewire/jack, etc aren't running, make sure you're in the "audio" group, then tell me what you get when you run "speaker-test -c 2 -t wav" but don't paste it in channel (because of the anti-flood protection)
2025-11-03.log [21:41:45] <jab> gnarface: let me take a look. 1 are pulseaudio/pipewire/jack running? I literally just installed ...so let me check... sudo service --status-all
2025-11-03.log [21:50:05] <gnarface> and these days pulseaudio is usually not started as a system process, so it could be running even if your command didn't return anything
2025-11-03.log [22:07:59] <gnarface> "host is down" error usually actually comes from pulseaudio or pipewire used to be installed and then got stopped or uninstalled without necessary configuration being removed
2025-11-03.log [22:08:36] <gnarface> alright, so you probably have the driver, and it's just a pulseaudio or pipewire misconfiguration
2025-11-03.log [22:09:27] <gnarface> if you run pipewire or pulseaudio you can override the selection in pavucontrol
2025-11-03.log [22:16:49] <gnarface> ok, my guess is for whatever reason the debian install managed to get pulseaudio or pipewire running (probably implicitly through systemd dependencies) and the pavucontrol settings overrided alsa's dumb default
2025-11-03.log [22:18:19] <gnarface> if you're more used to pulseaudio/pipewire it's probably a better idea to figure out which of the relevant packages you're missing and just install them
2025-11-01.log [19:52:02] <darwin> 'rustification' sounds bad too, among other things (pulse audio, systemd)
2025-10-29.log [18:14:21] <systemdlete> I did exclude the following: nano cups-common cups sane-utils avahi-daemon pulseaudio connman brltty espeakup
2025-10-13.log [20:26:43] <TorC> Had to fiddle a bit to get sound working on both, easiest option seemed to be installing pulsaudio. This with KDE for DE.
2025-10-06.log [00:10:35] <gnarface> if dustypenguin comes back tell them they've got a pulseaudio config in the way (or if they meant to use pulseaudio it isn't running for whatever reason)
2025-09-18.log [11:52:55] <Erwin-Iosef> Trying to make it work with pulseaudio instead
2025-09-17.log [16:12:50] <Afdal> Yeah, with pulseaudio the timidity daemon starts too early and takes over all the audio sinks so nothing else can play audio
2025-08-31.log [16:59:11] <eyalroz> Oh, and the pulseaudio mixer gui utility, which also seems to take up quite a bit of CPU time when it's on.
2025-08-30.log [17:32:15] <gnarface> (turns out it hates not having pulseaudio)
2025-08-17.log [13:54:52] <tairyu> excalibur issue 4: no audio (because pipewire is missing the kick from systemd), workaround: install pulseaudio
2025-08-14.log [16:15:48] <George> In mine pulseaudio and alsamixer show "Dummy Output"
2025-07-21.log [14:10:18] <matteobin> I'm getting some repeated audio stutters. How do I restart ALSA? I'm not using PulseAudio.
2025-07-21.log [15:44:14] <matteobin> gnarface: I listen to a lot of music and this is the first time it happens. Now I'm listening to music and everything is fine. If it happens again I'll investigate. It could be the chance to understand how audio on Linux works and remove PulseAudio and PipeWire from my other computers. :D
2025-07-21.log [15:46:37] <gnarface> matteobin: i also run without pulseaudio, i'll help however i can
2025-07-21.log [16:05:19] <matteobin> Right now I'm using a computer with just one sound card, so no problem at all. At home I wasn't able to purge PulseAudio, because of a USB microphone and Mumble.
2025-07-21.log [16:33:47] <matteobin> gnarface: Sure do, especially in quest to remove PulseAudio and PipeWire from my home computers!
2025-06-28.log [07:57:20] <gnarface> as for pipewire, no idea, but pulseaudio should work fine without it, and alsa should in most cases work fine without either
2025-06-28.log [07:57:51] <gnarface> (pipewire "works" ostensibly, but i just notice it generates slightly more complaints than pulseaudio lately)
2025-06-28.log [08:01:21] <gnarface> going without pulseaudio/pipewire/jack etc is less difficult in the long run
2025-05-29.log [19:22:57] <gnarface> yea, i figured that, i just wanted to make sure the problem isn't some bug in pulseaudio
2025-05-21.log [14:26:41] <Afdal> It just doesn't work properly with pulseaudio
2025-05-21.log [14:27:41] <Afdal> if the daemon loads before pulse (which it likes to), it'll break all the normal pulseaudio sinks until you stop the service
2025-05-21.log [14:28:17] <gnarface> Afdal: does pulseaudio not have any sort of midi plugin or something like that?
2025-05-21.log [14:28:43] <gnarface> the issue is user access, you have to be running timidity as the same user as pulseaudio
2025-05-21.log [14:29:24] <gnarface> they changed pulseaudio to start from the session manager, so it runs as your user now, but the timidity daemon init scripts still start it as root
2025-04-12.log [10:20:51] <Afdal> interfering with all other pulseaudio sound
2025-04-12.log [10:22:34] <Afdal> hmm, am I not allowed to let sysvinit handle this... or it ends up competing with pulseaudio?
2025-04-12.log [10:37:58] <Afdal> and that gets it to load properly after pulseaudio
2025-04-12.log [18:04:24] <gnarface> (and i'm not even using pulseaudio either, but i'm sure that does complicate the situation more)
2025-04-04.log [01:40:57] <devuanconsumer> is devuan 5 now using pipewire instead of pulse audio? Has anyone test to see if the latency issues are gone?
2025-04-04.log [01:56:14] <devuanconsumer> is there anything similar to the pulse audio volume control interface for pipewire? I'd like to see the input and output devices, recording, configuration and playback with the ability to get fallbacks and control volume
2025-04-04.log [09:43:36] <ximon> alsa-utils pavucontroll and pulseaudio you need
2025-04-03.log [17:09:56] <devuanconsumer> i installed qjackctl and have no uninstalled it and reinstalled pulseaudio, but now when i play a youtube video i can't get any sound. I opened up pulseaudio volume control and it doesn't list my browser under playback. please help
2025-04-03.log [17:11:16] <devuanconsumer> when i connect headphones, the pulse audio interface doesn't detect them either
2025-04-03.log [17:18:26] <devuanconsumer> my output is 6246 ? 00:00:08 pulseaudio
2025-04-03.log [17:19:05] <devuanconsumer> i wonder if uninstalling qjackctl messed up some linked settings because i see all my sound cards in pulse audio interface but it just doesn't show playback ugh
2025-04-03.log [17:27:54] <devuanconsumer> i purged pulseaudio and reinstalled it but its still not showing any playback, also rebooting didn't work
2025-03-15.log [01:37:13] <rrq> .. the changelog also talks about "mysterious stalls in pulseaudio"
2025-02-23.log [01:09:46] <rustyaxe> radio 9444 1.0 0.1 1132688 30876 ? S<l Feb20 27:22 /usr/bin/pulseaudio --start --log-target=syslog
2025-02-23.log [01:10:01] <gnarface> ah, could be a pulseaudio feature then
2025-02-23.log [01:10:25] <rustyaxe> something drug in pulseaudio and clobbered pipewire me thinks
2025-02-20.log [02:05:35] <gnarface> i'm sure it's just a handful of tiny config files referring to or inferring the presence of pulseaudio that you just have to get rid of
2025-02-18.log [03:14:18] <TorC> pulseaudio is definitely not installed, alsa-utils is, but I'm not certain alsa itself is fully installed. pipewire and wireplumber are both installed.
2025-02-18.log [03:16:25] <gnarface> i think there's a choice between pulseaudio and pipewire you can make, one might work better for you than the other
2025-02-18.log [03:22:06] <gnarface> if you switched back to pulseaudio and reported it started working normally again, you wouldn't be the first, but we can narrow it down with a couple of simple tests
2025-02-18.log [03:29:40] <gnarface> so, without intervention from pavucontrol/pulseaudio or whatever pipewire has to select audio devices, alsa itself will just default to the first one it finds
2025-02-18.log [03:52:33] <gnarface> if pavucontrol still doesn't work, switching back to pulseaudio may still be an option
2025-02-18.log [03:54:05] <TorC> Hmmm... Pavucontrol is "Establishing connection to PulseAudio. Please wait..."
2025-02-18.log [03:54:32] <TorC> I guess I'll just try installing pulseaudio and see if I can be done with.
2025-02-18.log [04:02:03] <TorC> Maybe somewhere in the KDE subsystem there should be a pulseaudio dependency, but I don't know as I know enough to verify for modifying a package.
2025-01-19.log [20:48:20] <mason> n4dir: It's not PulseAudio and it more or less works. Mostly it lets me do things like record sound with vokoscreen that's not possible with plain ALSA.
2024-12-26.log [16:02:19] <rustyaxe> been trying to figure out why my sound broke every time i'd pause or stop playing audio; something recently drug in pulseaudio despite having pipewire installed. apt purge pulseaudio; sudo killall -9 pulseaudio then a logout and back in fixed it.
2024-12-26.log [16:59:14] <gnarface> rustyaxe: i still think they only made pipewire because pulseaudio ran out of bugs. the best strategy for now is to switch back, or just ditch them both
2024-12-26.log [17:58:50] <gnarface> in this as well as other channels, a frequent cause of issues has been "upgrading" pulseaudio to pipewire, and rolling back turned out to be the simplest fix
2024-12-26.log [17:59:18] <gnarface> that sequence of events has cropped up a lot, and it coincided with the one pulseaudio system i have here running out of showstopper bugs
2024-11-20.log [01:54:58] <darwin> this prevents start-pulseaudio-x11 from running
2024-11-20.log [02:07:10] <gnarface> that probably explains why pulseaudio isn't starting too
2024-11-20.log [02:13:58] <gnarface> well, on the one system i have here with elogind and lightdm and pulseaudio, i didn't do anything weird to the configuration and this is all working normally
2024-11-20.log [02:14:18] <gnarface> on the other systems where i don't have any login manager, i also don't have pulseaudio
2024-11-20.log [02:18:53] <gnarface> i don't think pulseaudio has to be run as your user, i think that's just the new hot way to do it. i think you might be able to change the pulseaudio config so it can be started directly at startup and just used as a system daemon by any user instead. i think that's actually the way it used to be.
2024-11-20.log [02:28:10] <gnarface> hmm, i just had another idea about pulseaudio... maybe you could just add it to your window manager's startup programs directly instead?
2024-11-20.log [04:56:45] <darwin> i think what I had to do was create /run/user/1000 and then run start-pulseaudio-x11 as root
2024-11-20.log [04:58:51] <AlexLikeRock> i remember pulse audio : no need run as root
2024-11-05.log [00:38:18] <gnarface> you might be able to avoid pulseaudio though
2024-08-16.log [09:57:47] <gnarface> i also had problems getting mic to work without pulseaudio, but presumably if you're using pulseaudio it will work fine
2024-07-12.log [16:26:25] <asz09> Hey guys, just wanted to share what happened. Not sure if anyone from yesterday is here but I had a problem with a crash on my power manager, some GUI options not working on the xfce pannel, pulseaudio not working neither, all this on a fresh daedalus install with sysvinit. I highly suspect that the cause behind all this was a change in the umask value in /etc/init.d/rc to 027. I then reinstalled devuan,
2024-06-19.log [07:10:15] <al1r4d> I got experience when I was trying to connect TWS on Pulseaudio. When i switched to Pipewire, the problem was gone.
2024-06-17.log [05:35:09] <gnarface> peterrooney: a solid 50% of the time, the answer is to just uninstall pulseaudio. what's the actual problem you're having?
2024-06-17.log [19:50:22] <fonky> audacious sadly has pulseaudio dependancy and xmms isnt in the main repos
2024-06-17.log [20:22:58] <fsmithred> audacious works fine without pulseaudio.
2024-06-17.log [20:29:59] <fsmithred> libpulse does nothing if pulseaudio is not installed
2024-06-17.log [20:33:17] <rwp> I have libpulse0 installed. I am not using pulse-audio though.
2024-06-17.log [21:54:32] <gnarface> fonky: uh... afaik audacious does not have a pulseaudio dependency... make sure to use "--no-install-recommends" when you install it
2024-06-17.log [21:54:56] <gnarface> vlc and audacious both work withotu pulseaudio on current stable
2024-06-17.log [22:00:20] <gnarface> fonky: yea you can't get rid of libpulse without rebuilding the actual package but as was mentioned above, it's vestigial if pulseaudio itself isn't installed, so you don't really have to
2024-06-17.log [22:01:10] <buZz> really cuts cpu time down from pulseaudio at least
2024-06-17.log [22:07:04] <buZz> you dont really have to write pulseaudio clients anymore to get 'pulseaudio like benefits' , when having pipewire as host audio setup
2024-05-23.log [02:20:43] <al1r4d> PulseAudio with changing machine-id
2024-05-03.log [00:00:57] <wato> Damn, im checking that Discord also uses pulseaudio for voicechat
2024-05-03.log [00:01:34] <wato> i might be forced to install pulseaudio t-t?
2024-05-03.log [00:05:40] <gnarface> make Discord work for both input and output without pulseaudio, that is
2024-05-03.log [00:06:53] <wato> Will installing pulseaudio "unfix" that?
2024-05-02.log [18:30:26] <gnarface> however, audio is something poorly implemented and poorly understood in Linux, so you may have issues in EVERY distro. if you're more specific about which issues, i can often, but not always help (about 30% of the time it's manufacturer instigated driver issues that will never be fixed but the other 70% of the time it's user error because alsa configs are obtuse and pulseaudio is a hostile player)
2024-05-02.log [18:38:21] <gnarface> if i'm not around for alsa issue, there's always the #alsa channel on this irc network, the alsa-devel mailing list, or... wherever pulseaudio's support is
2024-05-02.log [23:07:29] <gnarface> wato: are you really attached to pipewire? lots of people seem to be having more problems with it than pulseaudio
2024-05-02.log [23:08:01] <wato> pactl info shows that pulseaudio is running on pipewire
2024-05-02.log [23:08:17] <gnarface> yea, but you can also just use bare pulseaudio still (or even bare alsa)
2024-05-02.log [23:10:08] <ted-ious> gnarface: Some of us don't run pulseaudio because it is horrible software and is infinitely more likely to lock up your system than alsa. :)
2024-05-02.log [23:12:28] <wato> gnarface: That's something i will need help with. Im open to uninstall wireplumber/pipewire/pulseaudio if it means that audio will work fine. What do you recommmend?
2024-05-02.log [23:12:40] <gnarface> wato: you do have a couple of other options here, and truthfully i think personally the best one is to ditch both pipewire and pulseaudio and use bare alsa. that's what i do because it's what works for me. secondarily, i'd recommend just using bare pulseaudio and alsa without pipewire, because that's what's working best for everyone else.
2024-05-02.log [23:35:32] <gnarface> (different from pulseaudio which stores per-user and even per-program volume settings)
2024-05-02.log [23:35:51] <gnarface> yea, pavucontrol is basically pulseaudio's alsamixer replacement
2024-05-02.log [23:36:06] <gnarface> at this point you can probably install pulseaudio and it will probably work great in fact
2024-05-02.log [23:36:46] <ted-ious> Pulseaudio reminds me of windows and how you could have 5 different places to mess up your audio settings so your game didn't work right.
2024-05-02.log [23:37:39] <gnarface> Valve's Steam client, has a "Remote Play" feature, which requires pulseaudio just for the audio part
2024-05-02.log [23:38:58] <gnarface> it will however help you use firefox builds that require pulseaudio (the firefox-esr build in current stable isn't one of the ones that need it though)
2024-05-02.log [23:58:34] <gnarface> some of the games on Steam "require" pulseaudio but you can usually get them working by symlinking libpulse-simple.so.0 to /dev/null from the top level of the game dir and putting this in the launch options: LD_LIBRARY_PATH=".:$LD_LIBRARY_PATH" %command%
2024-04-27.log [14:38:54] <X3DRE> How do I get the sound subsystem to work as when I goto sound in the system settings there is no subsystem like alsa or pulseaudio?
2024-04-27.log [14:47:59] <gnarface> X3DRE: you could try installing pulseaudio
2024-04-27.log [14:50:53] <gnarface> you don't always need pulseaudio, but you probably do need it to see the controls you're expecting. for bare alsa you'd usually use alsamixer in a terminal, which doesn't typically show up in desktop gui software
2024-04-27.log [14:52:57] <X3DRE> I get this message when trying to install pulseaudio : The following packages will be REMOVED: gnome gnome-core pipewire-alsa pipewire-audio task-gnome-desktop
2024-04-27.log [14:55:33] <X3DRE> This comes from doing this which I've said no! apt install pulseaudio pavucontrol pavumeter paprefs
2024-04-27.log [15:58:58] <gnarface> X3DRE: definitely sounds like a familiar pipewire issue, but unfortunately i don't know how to fix it. i'd say find out if gnome actually needs pipewire, and if not just install pulseaudio instead; it's possible it can work with pulseaudio but just needs to be reinstalled
2024-04-27.log [16:13:25] <gnarface> more than once, just installing pulseaudio instead worked, but in those cases gnome wasn't involved
2024-04-27.log [16:16:19] <gnarface> that probably didn't use gnome either though, did it? i wonder if it used pipewire or pulseaudio...
2024-04-27.log [16:18:48] <gnarface> notice that one post suggests a 1-line version of the 3-line config i gave you, and another one said he just removed both pulseaudio and pipewire to fix it (which is what i'd do, but i also wouldn't be using gnome)
2024-04-27.log [16:23:58] <gnarface> or, wait, if you switched to plasma does that mean you can switch to pulseaudio too?
2024-04-27.log [16:24:47] <gnarface> try installing pulseaudio and letting it remove pipewire?
2024-04-27.log [16:27:58] <X3DRE> Great I installed apt install -f pulseaudio and presto not rebooted and sound is working :)
2024-04-27.log [16:28:29] <gnarface> thus further supporting my theory that they made pipewire because pulseaudio was working too well
2024-04-18.log [14:37:05] <fonky123> is any desktop-environment besides lxde that does not have pulseaudio dependancy?
2024-04-18.log [14:40:08] <golinux> I have never used pulseaudio on Devuan not ever.
2024-04-18.log [14:41:10] <amarsh04> fonky - I'm on Devuan unstable (Ceres) and am running with pipewire and no actual pulseaudio, just some pulseaudio related stuff for those apps that expect it
2024-04-18.log [14:41:11] <fonky123> but for mate desktop, cinnamon desktop, gnome-desktop, kde prolly aswell the list of 2_be installed is amongst others pulseaudio
2024-04-14.log [22:51:45] <rrq> mmm it's a graphical thingy so depends on those; it merely recommends the bluetooth module for pulseaudio
2024-03-05.log [00:59:10] <gnarface> is qjackctl like pulseaudio's "pavucontrol" ?
2024-03-05.log [01:01:56] <gnarface> oh, so you have pulseaudio and jack together? that might complicate things
2024-03-05.log [01:03:08] <ibanja> it's supposed to work with pulseaudio-module-jack
2024-03-05.log [01:07:50] <gnarface> there's also a fix for Unity games that "require" pulseaudio that i have not considered using outside of Steam before, but might also be relevant to this:
2024-03-05.log [01:09:05] <gnarface> so basically what you do is you make a symlink from libpulse-simple.so.0 to /dev/null, then force the program to load that first, and audio will work with bare alsa again even though the Unity game will think it's using pulseaudio, and that doesn't require apulse
2024-03-05.log [01:10:27] <gnarface> in theory it should work for anything, but i've only seen it discussed in context of making sound work in Unity on linux without pulseaudio
2024-03-05.log [01:17:52] <onefang> Dunno, you have PulseAudio stuff in there, which I do not have installed, so I have no idea how it fits in.
2024-03-02.log [13:44:44] <gnarface> if you use pulseaudio and it's working right, you should be able to fix that alsa output device issue just by running pavucontrol and setting the right outputs
2024-03-02.log [13:45:09] <gnarface> separate to the video problem, during your upgrade pulseaudio probably got hosed somehow
2024-03-02.log [13:45:48] <gnarface> maybe pulseaudio got removed, or maybe the cached config just got hosed
2024-03-02.log [13:46:34] <gnarface> at this point i could only speculate, but normal behavior without pulseaudio would be for alsa to just default to whichever device it finds first unless you've customized your ~/.asoundrc
2024-03-02.log [16:52:53] <CueXXIII> ah, pipewire can act as a jack sink, in pulseaudio you'd have to configure that the other way around…
2024-02-27.log [10:28:48] <djph> oh, no, it's on par with pulse audio and systemd for "stop thinking you know better than me"
2024-02-25.log [10:44:49] <gnarface> ra33: someone else recently had an issue that required adding a startup delay to the pulseaudio server i think... maybe related?
2024-02-25.log [11:41:18] <|cos|> isn't pulseaudio pottering's first take at breaking working stuff unnecessarily? an art-project pre-dating his master piece in manifesting involuntary participary software bug bonanza. stay away from it, and life will be better.
2024-02-25.log [14:40:50] <rustyaxe> people still use pulseaudio? No wonder i still hear crying of sound troubles every now and then
2024-02-25.log [19:16:49] <gnarface> afaik pipewire in fact still depends on pulseaudio directly, so i can't imagine how it could possibly simplify anything
2024-02-25.log [19:17:24] <ted-ious> No it sits on top of alsa and replaces pulseaudio completely.
2024-02-25.log [19:18:13] <ted-ious> n4dir: I don't have pulseaudio on any of my systems so whatever it does it does it without pulseaudio.
2024-02-25.log [19:20:36] <ted-ious> I haven't had any sound related crashes ever since I got rid of pulseaudio.
2024-02-25.log [19:23:29] <|cos|> alsa by itself has always worked flawlessly for me. i assume pulseaudio was created to solve some kind of problem, but frankly that was a problem most people didn't even have.
2024-02-25.log [20:22:02] <ted-ious> I don't have jack or pulseaudio or anything else and I don't need them.
2024-02-25.log [20:26:43] <ted-ious> No I blacklist pulseaudio and I have never installed jack in my life.
2024-02-25.log [20:29:43] <ted-ious> Not only didn't I care for pulseaudio I thought it was junk and I wanted it off my systems.
2024-02-18.log [17:16:52] <gnarface> did pulseaudio get pitched overboard when you were doing installs?
2024-02-18.log [17:18:40] <ski> "did pulseaudio get pitched overboard when you were doing installs?" -- no idea (and no idea how to check)
2024-02-14.log [20:09:21] <gnarface> CEP-stafe: ah, yes i think i do remember seeing you mention that now. glad you got it working. any idea why it needs the delay? a driver problem or a pulseaudio problem?
2024-02-07.log [15:23:58] <buZz> if you want to use the pulseaudio emulation inside pipewire
2024-02-07.log [15:44:44] <gnu_srs1> I'm happy w/o pipewire or pulseaudio. Plain alsa stuff works for me TM :)
2024-02-02.log [02:30:15] <systemdlete> oh. and not running pulseaudio
2024-01-22.log [18:45:06] <ham5urg> rc-update show does not list any pulseaudio oder pipewire daemon.
2024-01-22.log [19:07:20] <gnarface> i don't know if gnome requires pulseaudio but in general it's not a given that you need it
2024-01-22.log [19:10:11] <ham5urg> gnarface, pulseaudio replaces pipewire-audio what removes gnone as a whole.
2024-01-22.log [19:16:50] <gnarface> ham5urg: no, "host is down" isn't a kernel error, that's suggesting you still have part of the pulseaudio/pipewire monstrosity installed, but not the part it needs to work
2024-01-22.log [19:18:18] <gnarface> when this had come up for someone else last time, they had removed pulseaudio but had forgotten to remove some parts of pipewire, i think, but there might be other combinations that cause it
2024-01-22.log [19:20:21] <gnarface> start by removing ALL the pipewire+pulseaudio+jack+esd+sndio+arts+whatever else you might have, and test just bare alsa with speaker-test
2024-01-22.log [19:27:19] <gnarface> (and this is a problem you could still run into with a full working pipewire+pulseaudio stack installed if you don't know to run pavucontrol to change the default output device)
2024-01-22.log [19:37:57] <gnarface> ham5urg: all you should have to do is uninstall pipewire or install pulseaudio with it, afaik, but i don't know about gnome issues other than that most people who used to use gnome switched to mate or cinnamon to avoid gnome's broken power management and sensors implementation
2024-01-22.log [19:45:08] <gnarface> if you install gnome again, does it insist on carrying in pipewire and/or pulseaudio even if you use "--no-install-recommends" ?
2024-01-22.log [19:47:05] <gnarface> damn, so a gnome problem. it might work if you also add pulseaudio, but i'm not sure
2024-01-22.log [19:48:46] <ham5urg> pipewire-alsa and pipewire-audio collide with pulseaudio
2024-01-22.log [19:50:58] <gnarface> only other idea i have is to stick around long enough to talk to someone who knows pulseaudio and pipewire better. mostly i've only practiced doing without them.
2024-01-22.log [19:53:45] <gnarface> the pulseaudio/pipewire mess is common though
2024-01-22.log [19:55:36] <gnarface> kde is very professionally done but will probably force you to use pulseaudio, but at least will probably actually work
2024-01-17.log [00:02:44] <gnarface> "host is down" actually still sounds like a pulseaudio error
2024-01-17.log [00:07:55] <gnarface> but not certain it's a driver issue... since the "host is down" issue kinda makes me wonder if it's still just trying to use pulseaudio
2024-01-17.log [00:09:37] <gnarface> aiui pipewire still uses pulseaudio so i don't know what purpose it serves without it
2024-01-17.log [00:10:43] <ibanja> so I should remove it then. It does have a pipewire-pulse which I thought replaces pulseaudio, that's why I gave it a shot.
2024-01-17.log [00:20:38] <brocashelm> that's good. i had a feeling you still had some pipewire/pulseaudio/jack/etc. crud laying around
2024-01-17.log [00:22:25] <brocashelm> i sanitize such systems with apt autopurge pulseaudio* pipewire* *jack* (note the placement of the asterisks; check the prompts to ensure nothing important gets removed)
2024-01-16.log [22:55:10] <ibanja> does devuan default to pipewire or pulse audio?
2024-01-16.log [22:56:37] <nemo> pulseaudio seems to dynamically update to stupid app tricks more flexibly
2024-01-16.log [22:57:45] <nemo> so I'd go with pulseaudio just for greater reliability
2024-01-16.log [23:05:35] <brocashelm> and if you are not using pulseaudio, i'd just disable/uninstall it completely (that includes pavucontrol;volumecontrol-alsa and alsamixer can be used in its place)
2024-01-16.log [23:06:05] <brocashelm> it's just pulseaudio emulation for alsa
2024-01-16.log [23:07:44] <brocashelm> just don't use jack, pulseaudio, pipewire, or sndiod (better to just install openbsd if you want sndio, but that's OT)
2024-01-07.log [03:44:58] <gnarface> fluffywolf: AIUI pulseaudio absorbed bluetooth audio functionality and they removed bare alsa bluetooth audio support some releases back. (that they apparently re-added it to daedalus is in fact news to me) - data and gamepad inputs should have always been possible through that time with separate packages, but driver support has been so spotty that gambling a pair of devices would work together has been a bad bet in
2024-01-07.log [03:52:13] <brocashelm> oss, alsa, portaudio, jack, pulseaudio, gstreamer, pipewire...
2023-12-31.log [22:57:40] <fifihyperbola> it might be issue with pulseaudio?
2023-12-21.log [00:01:03] <movedToDevuanOnM> i remember using pulseaudio and alsamixer on ubuntu before 5-6 years.. it always worked OOB
2023-12-20.log [22:16:46] <gnarface> sounds like a pulseaudio error? i don't recall seeing that before
2023-12-20.log [22:53:41] <gnarface> it seemed like pipewire sometimes can be set up to depend on pulseaudio and sometimes not? i'm not clear on the whole picture
2023-12-20.log [23:58:46] <movedToDevuanOnM> that worked... removed pipewire audio and install pulseaudio..
2023-12-20.log [23:59:30] <_ds_> Could be that pipewire just needed some configuration, but I've not really played with it (or with pulseaudio, for that matter)
2023-12-09.log [11:27:36] <Besnik_b> The noise disappears with pulseaudio
2023-12-09.log [11:30:43] <gnarface> because you said vlc and pulseaudio also removes it
2023-12-09.log [20:48:39] <sfox> the same company who pushed systemd, pulseaudio, and gtk3
2023-11-22.log [07:13:31] <gnarface> al1r4d: you'd have to bypass the pulseaudio "device" that alsamixer sees by default while pulseaudio is running to access the hardware driver's interface to see it, if it has one (which it may not). it might work to hit F6 and select the device from the list, otherwise you'll have to stop pulseaudio first
2023-11-21.log [04:36:38] <rwp> onefang, The package version should work with either alsa or pulseaudio so running it with apulse would just cause it to use that interface. But that's a clue. Maybe something on your alsa is not yet enabled.
2023-11-21.log [13:03:27] <|cos|> with this being devuan, i presume the first culprit is not around? systemd's older brother pulseaudio? killing that one tends to solve 90% of audio problems.
2023-11-21.log [14:00:20] <gnarface> i think pulseaudio has an equivalent setting
2023-11-19.log [03:44:18] <al1r4d> why devuan still using pulseaudio? 🤔
2023-11-19.log [03:46:46] * blockhead pretty much uses alsa for everything. in devuan you can ignore pulseaudio
2023-11-19.log [03:50:20] <brocashelm> but you could try compiling against pulseaudio
2023-11-19.log [03:56:14] <brocashelm> i prefer that one over pulseaudio, pipewire, or jack if i had to have a layer above alsa
2023-11-06.log [16:25:08] <gnu_srs1> Works with pulseaudio, not with pipewire.
2023-11-06.log [16:25:56] <gnu_srs1> Still no audio in firefox with pulseaudio or standalone (vlc,mplayer)
2023-10-23.log [12:53:11] <[-_-]> no I am not, arch wiki says bluez dropped alsa, onlp pulseaudio is supported now
2023-10-23.log [12:54:54] <gnarface> well, one would think pulseaudio should have control over this too though
2023-10-23.log [12:59:27] <gnarface> i just stopped caring about bluetooth when they tried to make it a pulseaudio exclusive
2023-10-23.log [13:01:55] <gnarface> i know that there's supposed to be some fundamental distinction between them, but to me, pipewire is just pulseaudio2
2023-10-23.log [13:05:42] <rustyaxe> has anyone looked into making the pipewire-pulse package satisfy pulseaudio for other packages? or is that a thing where package maintainers should be putting pulseaudio | pipewire-pulse?
2023-10-23.log [13:06:05] <rustyaxe> ill probably just make an empty pulseaudio package to install for now
2023-10-23.log [13:08:57] <rustyaxe> gnarface: So far i havent found anythings that haven't worked with pipewire-pulse -- the one thing that was messy was no worse off than pulseaudio screwing up audio for everything else
2023-10-21.log [03:42:06] <brocashelm> it offers a more minimal xfce desktop, uses alsa instead of pulseaudio, no metapackages, custom magic sysrq keys, a tor launcher button, firemenu (gui for firejail, for sandboxing your programs), etc.
2023-10-18.log [20:33:36] <brocashelm> i never use pulseaudio or jack when i can get away with it
2023-10-13.log [06:29:37] <gnarface> only other thing i can think of is look for it to be started by the session manager maybe, the way pulseaudio is these days
2023-10-13.log [06:34:14] <gnarface> no, i'm really not. i remember some basic hci tool use, but generally stopped trying to make it work back around kernel 3.1 when they broke the driver for my only bluetooth dongle. since then they've made pulseaudio a requirement so i just haven't bothered.
2023-10-13.log [06:35:48] <onefang> Maybe bluetooth is being started by pulseaudio?
2023-10-13.log [06:36:31] <n4dir> onefang: i just removed pulseaudio, in a wild fury. bluetooth still starts
2023-10-13.log [06:36:41] <gnarface> hmm, as of daedalus maybe it's possible to use it without pulseaudio again, i just haven't actually tried it but some package names look promising; bluez-alsa-utils
2023-10-11.log [15:06:46] <rustyaxe> happened with pulseaudio, still happening with pipewire; using xfce4 desktop -- it's an issue on amd64 and aarch64 both
2023-10-11.log [15:25:12] <gnarface> well if you're not using pulseaudio i'd think you shouldn't be using it
2023-10-10.log [02:08:27] <Xenguy> I have never had an issue with pulseaudio in the past
2023-10-10.log [02:21:18] <brocashelm> ok, so it's pulseaudio on your system not picking them up somehow
2023-10-10.log [02:31:11] <gnarface> Xenguy: if you're using pulseaudio you need to check pavucontrol
2023-10-10.log [02:31:48] <gnarface> (i've seen some misbehavior with pulseaudio on beowulf too)
2023-10-10.log [02:41:26] <gnarface> but that's where i'm not using pulseaudio
2023-10-10.log [02:42:16] <gnarface> where i am using pulseaudio though, i am generally helpless before this type of bug
2023-10-10.log [02:43:09] <Xenguy> As I say, I've always just gone with the default setup (which is pulseaudio) and things just work fine. I'm not opposed to seeking a different setup, but I would rather not go down that road unless clearly necessary...
2023-10-10.log [02:46:47] <gnarface> (the beowulf system is also the only one i'm using pulseaudio on)
2023-10-07.log [07:02:40] <gnarface> cws6969: do you happen to have pulseaudio installed?
2023-10-07.log [07:06:06] <gnarface> there should be a way to make it work without pulseaudio or pipewire, but all the search results only point to fixes for those
2023-10-07.log [07:27:20] <rrq> don't need those now either, but I guess you used pulseaudio before
2023-10-07.log [07:27:30] <gnarface> cws6969: yes, pipewire is new but it's not devuan's invention. that came from upstream. you might be able to do without it and use pulseaudio instead but afaik debian removed support for other methods before devuan existed.
2023-10-07.log [07:28:16] <gnarface> cws6969: yes, pipewire is new but it's not devuan's invention. that came from upstream. you might be able to do without it and use pulseaudio instead but afaik debian removed support for other methods before devuan existed.
2023-10-07.log [07:28:44] <rrq> you don;t need pulseaudi and not pipewire
2023-10-07.log [07:29:57] <gnarface> i thought that was missing without pulseaudio
2023-10-07.log [07:32:07] <rrq> with pulseaudio, the puslaudio server is tunning and in doing so will register an a2p profile with bluez
2023-08-25.log [00:02:46] <critr> heh, it turns out if you purge pulseaudio, pipewire is automatically installed, and shound still just works.
2023-08-24.log [03:17:29] <gnarface> hmm, i wonder if it's supposed to get started by your login manager like pulseaudio
2023-08-24.log [03:18:00] <gnarface> the latest pulseaudio setups would have it get started automatically on login by lightdm or such
2023-08-24.log [03:22:17] <critr> what's the nbst way to remove pulseaudio and install pipwire without screwing up my audio?
2023-08-24.log [03:28:42] <gnarface> CEP: virtualbox may be a complication. i don't use pulseaudio or pipewire here, they may be unnecessary complications
2023-08-24.log [03:33:04] <CEP> critr when I wanted to install pulse-audio , uninstall pipe-audio and even genome, I think the other way around, it would uninstall pulse-audio and genome. but I come from a test version, (the error must come from there.)
2023-08-24.log [23:12:06] <CEP> I had to uninstall pulse-audio, uninstalling pipe in daedalus-guest
2023-08-24.log [23:17:08] <systemdlete> pulseaudio. And it is not installed here.
2023-08-22.log [05:42:27] <gnarface> critr: ^ (without pulseaudio or jackd or pipewire or esd or arts anything like that running)
2023-08-20.log [01:47:12] <fsmithred> do you have pulseaudio installed?
2023-08-14.log [01:55:48] <mason> brocashelm: Slackware included PulseAudio as of 14.2 and elogind as of 15.0.
2023-08-14.log [01:57:15] <brocashelm> mason: i got rid of pulseaudio and replaced it with alsa; elogind, however, is a problem
2023-08-02.log [06:21:56] <gnarface> well pulseaudio and pipewire and the like can significantly complicate this, but they both rely on alsa and any user in the "audio" group should be able to access alsa
2023-08-02.log [06:23:39] <gnarface> pulseaudio and pipewire might react to seatd in some way on later releases, i don't know
2023-08-02.log [06:24:07] <gnarface> the last release i have relevant pulseaudio experience with though is beowulf, and there it's just about whoever is logged in currently
2023-08-02.log [06:24:42] <gnarface> in the default configuration i'd seen, pulseaudio was started by kde as the logged-in user
2023-08-02.log [06:28:30] <gnarface> pulseaudio might obviate that while you're logged in but i'm not sure
2023-08-02.log [20:48:48] <Guest58> hopefully it doesn't fuck up all of my pulseaudio fixes...
2023-08-02.log [20:49:20] <jonadab> Good luck with that. pulseaudio is ridiculously brittle.
2023-08-01.log [14:39:16] <antranigv> mason it works just fine :) I use Chrome on Linux on FreeBSD to watch Netflix and other DRM content :D sometimes the audio craps out, but that seems to be a PulseAudio issue.
2023-07-30.log [02:37:14] <gnarface> but if you're using pulseaudio or pipewire or the like, i'm not sure any of that will work
2023-07-30.log [02:39:54] <gnarface> what i do to avoid the pulseaudio requirement for Steam Remote Play (formerly known as "In-Home Streaming" which is not to be confused with the separate "Broadcast" mode) is set programs to use the Loopback alsa device provided by the snd-aloop kernel module, and then pipe arecord from that over netcat -u... to "aplay --buffer-time=50000..."
2023-07-30.log [04:15:24] <dgriffi> I have pipewire and wireplumber running from .xessionrc. It doesn't seem that MATE sees it as a pulseaudio replacement
2023-07-30.log [04:26:51] <gnarface> it's nice for Steam because otherwise you would need to use pulseaudio to do this, but it's also nice for anything that wouldn't otherwise have network audio support
2023-07-29.log [23:26:30] <rwp> dgriffi, I was literal in that I had not seen a canonical correct way to start it. I am not running anything myself. Just rawdogging alsa here for the moment. But pulseaudio is so much trouble for me that anything would be an improvement.
2023-07-26.log [08:27:49] <kamey> audio, debian package seems to have removed pulseaudio and installed pipewire but I don't know what configuration needs to be done for this to work.
2023-07-26.log [09:03:38] <kamey> trying to install puleseaudio with gnome it doesn't work because then it wants to remove "gnome gnome-core pipewire-alsa pipewire-audio" http://paste.debian.net/1286987/
2023-07-26.log [09:15:49] <schillingklaus> pulseaudio and gnome are systemd-friendly... so I boycott them
2023-07-26.log [18:16:48] <gnarface> i don't know much about pipewire, but i know pulseaudio is started from the user session rather than as a init service
2023-07-26.log [18:23:13] <rwp> I should spend some time learning and using pipewire so that I can help with pipewire questions. Because pulseaudio is so bad that we do need to help people migrate away from it.
2023-07-22.log [01:25:07] <gnarface> do you have pulseaudio, pipewire, or jack running? (or esd or arts or any other such sound daemon in userspace?)
2023-07-22.log [01:40:54] <dgriffi> in its previous life as a Debian machine, I had pulseaudio running. I turned on pulseaudio by typing "pulseaudio" in one xterm and NOW terminal beeps work.
2023-07-22.log [01:41:42] <dgriffi> when I started up pulseaudio just now, it sounded like a mouse running around in a cardboard box.
2023-07-22.log [01:43:41] <dgriffi> seems like it may be a MATE problem. suppose it always wants to send beeps to pulseaudio.
2023-07-22.log [01:44:02] <gnarface> could it be that it just disables the beeps by default as a misguided courtesy, and pulseaudio just re-enables them because it's dumb?
2023-07-22.log [01:56:45] <gnarface> could pulseaudio have been the only difference?
2023-07-22.log [02:02:38] <rustytaco> I like pipewire a lot. It's suitable to do the things; qpwgraph lets you re-arrange connections in a gui way; wireplumber handles automatically plumbing things up; there's pipewire-pulse too to emulate pulseaudio for needful programs
2023-07-22.log [02:05:19] <rustytaco> dgriffi: padsp - PulseAudio OSS Wrapper
2023-07-22.log [02:05:51] <gnarface> dgriffi: try those alsa packages first, if they don't work then maybe resort to pulseaudio stuff
2023-07-22.log [02:08:51] <dgriffi> but I got ERROR: ld.so: object '/usr/16942LIB/pulseaudio/libpulsedsp.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
2023-07-17.log [00:53:16] <gnarface> sfox: it's been fine for me but i don't use pulseaudio
2023-07-17.log [00:54:39] <grayrock> sfox: all i can say is i moved to devuan 5 after i recently put together a new computer, and i've actually had a lot less trouble with devuan 5 than i anticipated. oh, and pulseaudio seems to be working fine on my hardware.
2023-07-16.log [16:00:59] <ecxod> is pulseaudio compatible with devuan ? it does not work any more since I switched
2023-07-16.log [16:03:19] <mason> That said, I don't use PulseAudio so I'm just assuming that's still the advice.
2023-07-16.log [16:08:00] <mason> Remember that PulseAudio doesn't actually do much. It mostly just feeds audio to ALSA.
2023-07-16.log [17:26:23] <nemo> ecxod: no issues over here with pulseaudio
2023-07-16.log [17:35:22] <nemo> buZz: my experience with pipewire on the steamdeck is it is more finicky than pulseaudio.
2023-07-16.log [17:35:53] <nemo> some older games have sucky audio inputs they dump in, and pulseaudio quietly detects and corrects which is nice
2023-07-16.log [17:42:11] <mason> gnarface: I use Steam without PulseAudio.
2023-07-04.log [23:42:47] <rwp> Sounds reasonable enough. I have not used pipewire myself and have no experience with it. I have had the unfortunate experience with pulseaudio and anything must be better.
2023-07-03.log [22:05:58] <latex> Also while my friend was on Fedora, pipewire was completely fucked and pulseaudio programs didn't show up in the JACK graph
2023-06-30.log [15:10:59] <starrcade> Henlo all, I am having an issue with getting no audio from a fresh Chimera install, I removed pulseaudio thinking that'd do it but that didn't work, confirmed Alsamixer did load my intel sound driver, should i reinstall pulse or is it something that's not picking up from the device?
2023-06-30.log [16:35:41] <starrcade> PulseAudio on the other hand, wants to/is forced to use the sp/dif on the intel card itself, so I guess we can rule out Nvidia
2023-06-30.log [16:41:25] <onefang> Dunno, I avoid PulseAudio these days.
2023-06-30.log [17:35:21] <onefang> starrcade: it might be worthwhile trying pipewire instead of pulseaudio, before getting deeply technical with config files.
2023-06-23.log [23:33:46] <LucentW> the recent Red Hat stuff coming up is further proof that relying on Red Hat stuff is going to be the end for Linux as we know it, hopefully this situation works as a canary for all the distros that embraced systemd, PulseAudio, DBus without evaluating the centralization those project brought over the distros landscape
2023-06-12.log [04:52:50] <gnarface> (there are a couple things that expect systemd or pulseaudio that take some clever tricks to work around)
2023-06-12.log [14:37:21] <buZz> guilherm1: the issue is that pulseaudio was always demented and we're finally moving away from it
2023-06-09.log [00:18:23] <gnarface> (also behind the likes of pulseaudio, network-manager, avahi-daemon)
2023-06-01.log [05:40:52] <gnarface> hiddener: you may need to stop pulseaudio first
2023-05-29.log [13:43:38] <AhmedNabil> But devuan still using pulseaudio
2023-05-29.log [13:46:40] <AhmedNabil> when i trying to remove pipewir to install pulseaudi
2023-05-29.log [13:50:07] <phogg> AhmedNabil: I see that gnome-settings-daemon depends on pulseaudio | pipewire-audio, so if you 'apt-get install pulseaudio- pipewire-audio' then it should not break the dep
2023-05-29.log [14:00:32] <AhmedNabil> and full replace pulseaudio with pipewire on devuan
2023-05-29.log [14:01:45] <phogg> AhmedNabil: I have no experience with it (yet), but there should not be anything to change. Pipewire looks like pulseaudio to pulseaudio-aware clients.
2023-05-27.log [20:47:36] <gnarface> rpgguest7098: weird though, because pulseaudio is supposed to emulate alsa for this type of thing, so it's weird that one would work but not the other
2023-05-27.log [20:49:49] <gnarface> i would also want apulse to mimic the network-streaming feature of pulseaudio that Steam relies on for remote-play but i'm sure that's asking more of it than it is capable of delivering
2023-05-27.log [20:51:00] <gnarface> and btw, for whatever it's worth, for firefox-esr on daedalus i still don't need pulseaudio or apulse for output
2023-05-26.log [13:12:49] <fsmithred> I tried pipewire (i.e. installed it) but I couldn't figure out what to do with it, and it seemed like it only worked if pulseaudio was installed.
2023-05-26.log [13:12:55] <latex> I'll still run jack+pulseaudio combo on my main pc
2023-05-26.log [19:30:10] <gnarface> latex: nothing in /etc/init.d/? it could be getting started by the session manager like pulseaudio does now
2023-05-26.log [19:31:57] <gnarface> oh, i see. i'm not sure how to even make pulseaudio work right in that situation these days
2023-05-26.log [19:32:15] <latex> pulseaudio gets automatically started by programs that need it
2023-05-26.log [22:01:53] <latex> I installed pipewire, the uninstalled it, installed jack, pulseaudio
2023-05-25.log [13:25:19] <hacksenwerk> rpgguest1676: I uninstalled pulseaudio to use alsa...
2023-05-25.log [14:16:44] <hacksenwerk> djph: I understand that, but pulseaudio _can_ hanlde it. :(
2023-05-24.log [13:37:14] <hacksenwerk> I don't want to defend pulseaudio here (I removed it because I wanted to get rid of it), but there (in pavucontrol) I selected that usb sound card _once_ and it was always the default sound card pulse was using, no matter how often I had reboot my computer...
2023-05-24.log [14:33:18] <hacksenwerk> djph: I expect to tell alsa "Here this is my sound card, use it. Always." And it is doing it like pulsaudio
2023-05-24.log [21:45:35] <Afdal> right pulse/alsa/whatever audio sink.
2023-05-22.log [18:40:33] <hacksenwerk> Hi. I recently uninstalled pulseaudio and pavucontrol and installed alsa-utils instead. I rebooted the computer after that. However, cmus tells me: "Error: opening audio device: internal error"
2023-05-22.log [18:42:17] <gnarface> and yea, this should work without any alsa config, but pulseaudio may have left behind some cruft that sabotages it
2023-05-22.log [18:45:15] <gnarface> if speaker-test doesn't even work though you need to find that pulseaudio cruft and throw it overboard
2023-05-22.log [18:50:27] <hacksenwerk> /etc/alsa/conf.d/50-pulseaudio.conf and /etc/alsa/conf.d/99-pulseaudio-default.conf.example
2023-05-22.log [18:52:05] <hacksenwerk> o_0.... /etc/gufw/app_profiles/pulseaudio.jhansonx
2023-05-22.log [18:52:22] <hacksenwerk> Why do pulse audio need a firewall profile?
2023-05-22.log [18:52:49] <gnarface> hacksenwerk: maybe because pulseaudio can do network streaming
2023-05-22.log [18:55:51] <gnarface> pulseaudio wasn't ever known to be "good"
2023-05-22.log [18:58:43] <gnarface> damn, i really wish i could remember where pulseaudio leaves that config slug behind. this has come up multiple times before.
2023-05-22.log [19:09:28] <hacksenwerk> Ah I have xfce4-pulseaudio-plugin here too
2023-05-22.log [19:12:26] <gnarface> hacksenwerk: oh, one other thing that occurs to me; many programs store their own persistent audio config and may still be pointing to the now missing pulseaudio. did you ever test it with speaker-test?
2023-05-22.log [19:34:52] <gnarface> well, if it's behaving well it shouldn't need special configs to not use pulseaudio but i'm not familiar enough with this program to know if it's well behaved
2023-05-22.log [19:47:44] <gnarface> seems like it must have stored some pulseaudio stuff in the auto-generated config
2023-05-22.log [20:13:47] <hacksenwerk> And what do we learn: It is better to never install pulseaudio, than uninstall it!!!
2023-04-25.log [20:26:09] <brocashelm> just a few things like no avahi, alsa instead of pulseaudio, tor launcher, firejail, magic sysrq keys, and xfce without metapackages
2023-04-25.log [20:28:41] <brocashelm> i have no need for anything beyond alsa, generally. i just can't get simplescreenrecorder or obs to work without pulseaudio/pipewire, that's all
2023-04-25.log [20:29:55] <brocashelm> if that could be used in areas where alsa would fail, that would be much better imo than pulseaudio/pipewire/jack
2023-04-22.log [14:19:26] <rustyaxe> I've got the weirdest issue after moving my setup from one devuan machine (pi4 64bit) to x86_64 .. same usb sound widget (literally) --on new machine i have to run a script such as while true; do amixer -c 0 sset Speaker 3; sleep 30; done -- bumping the volume back to 25% instead of zero, because *SOMETHING* keeps resetting it to 0... happened with pulseaudio and still happening with pipewire.
2023-04-19.log [09:36:19] <gnarface> the real offenders for me are usually avahi-daemon, network-manager, and pulseaudio, and though they're often installed by default too they're much easier to get rid of
2023-04-16.log [00:26:34] <rustyaxe> Yea then alsa gets softmixing and just works right... and pulseaudio comes along and adds a ton of latency and bugs
2023-04-16.log [01:42:10] <Xenguy> I've never had an issue with pulseaudio, but people complain about it like crazy
2023-04-13.log [22:10:26] <rustyaxe> so.. i really hate pulseaudio.. but i have to use No Machine (giving x2go a try first) so pipewire is tricky.. It wwants the audio dev to exist before the session, the session comes up (pipewiere/wireplumbe startup) after nx is connected sorta mess
2023-04-01.log [14:34:54] <rustyaxe> See also pulseaudio... or this accountsservice junk
2023-03-27.log [20:16:47] <onefang> arecord is for ALSA, PulseAudio or PipeWire may get in the way.
2023-03-24.log [06:27:39] <brocashelm> can't install/use mpv without some dbus, avahi, wayland, pulseaudio "libs"
2023-03-16.log [07:23:08] <brocashelm> fatphil: oh, cool. works well for me so far. what about sndio as an alternative to pulseaudio or pipewire? still on alsa as it just works
2023-03-16.log [07:26:47] <brocashelm> maybe if i wanted to record sound through my screen, so pulseaudio or pipewire would "work" in that regard. i've had usb headsets work with just alsa firmware tinkering
2023-03-10.log [07:11:55] <brocashelm> i am attempting to create a non-dbus/wayland/pipewire/pulseaudio/gvfs/udisks2/avahi/elogind install
2023-02-22.log [06:28:03] <systemdlete> I'm wondering if pulseaudio is required for all sound stuff now.
2023-02-22.log [06:28:44] <onefang> I use ALSA for the HDMI speakers on my main monitor, JACK for everything else, and no pulseaudio installed.
2023-02-21.log [20:45:14] <systemdlete> I am using a few tools to test it, including onlinemictest.com. I am running firefox-esr under apulse (pulseaudio is not installed on my systems). I "ALLOW" the microphone in firefox, but still no audio input. It could be I killed the microphone one day by accident--I dropped the thing about 9-12 inches, which may have been enough to damage
2023-01-10.log [12:06:23] <gnarface> Necrodiver: is pulseaudio running?
2023-01-10.log [12:12:29] <gnarface> double check that you didn't actually get a debian version of pulseaudio pulled in from their repo when you did that
2023-01-10.log [12:22:20] <onefang> I have OBS-studio installed here and no pulseaudio shit. Haven't tried to use it yet though.
2022-12-19.log [23:16:04] <rwp> If all else fails it might be worth a try "apulse solfege ..." to run it that way and see if it needs pulseaudio or not.
2022-12-19.log [23:18:57] <onefang> Solfege doesn't have a pulseaudio option, just ALSA, OSS, and "external MIDI player"
2022-12-04.log [17:17:14] <gnarface> if jack takes over your alsamixer view like pulseaudio does, you'll have to make sure it's not running first
2022-11-25.log [21:06:56] <Afdal> Anyone else have a bunch of junk in filesystem root put there by pulseaudio that normally belongs in $HOME ?
2022-11-25.log [21:42:08] <newdevusr> I am a new user with a clean install of the testing branch (Daedalus). I am using pulse audio on two machines. I do not see anything that indicates a problem with the filesystem (pulse or otherwise)
2022-10-20.log [06:16:24] <debdog> chomwitt: is pulseaudio installed an running?
2022-10-09.log [15:58:32] <Wonka> *sigh* Firefox only does pulseaudio for some while now, that's why I had it installed. Now there's this pipewire stuff. And it led to aptitude uninstalling pulseaudio. And now, firefox is mute.
2022-10-09.log [16:03:41] <Wonka> Currently I'm wondering why it uninstalled pulseaudio at all, because I can install it just fine without any conflicts...
2022-10-09.log [16:05:53] <Hanicef> Wonka: while pipewire and pulseaudio can be installed at the same time, they can't run at the same time. if you try, one of the them will lock the snd block files preventing the other daemons from playing any sounds
2022-10-09.log [16:17:52] <Wonka> well, the one from 'https://download.mozilla.org/?product=firefox-latest-ssl&os=linux64&lang=en-US' at least does not work without pulseaudio
2022-10-09.log [16:30:49] <Wonka> hm. hm. not trivial to get to run currently... I'll postpone that, reinstalling pulseaudio just worked...
2022-10-09.log [17:43:48] <golinux> I have never used pulseaudio and always had sound in Firefox because Devuan has apulse.
2022-10-09.log [18:45:19] <rwp> AFAIK the upstream Mozilla version of Firefox only supports PulseAudio but works with the "apulse firefox" emulator wrapper for ALSA.
2022-10-09.log [18:47:16] <rwp> I imagine PipeWire when it eventually replaces PulseAudio everywhere will make the apulse adaptor obsolete.
2022-10-04.log [15:40:53] <onefang> The thing I find odd about that is that upstream Debian is switching from pulesaudio to pipewire for that version. Maybe they are half way in doing that?
2022-09-24.log [10:04:57] <crhylove> How do I solve pulseaudio being held back in apt?
2022-08-10.log [21:22:34] <EdBoatConnoisseu> eyalroz: if you want to use pipewire to replace pulseaudio, simply starting it on xsession, pipewire will linger after the session is killed, the "reccomended" ways which is checking for the pidof pipewire and either not starting or killing the other instances becomes messy if you want to have multiple x11 sessions, like in another tty or maybe inside xephir, shed guarantees that the instance of pipewire created for the xsession will
2022-08-10.log [21:27:46] <EdBoatConnoisseu> in short pipewire is a more performant replacement for pulseaudio, personally i use it to not have to do the pulseaudio and jack dance when i want to use aurdour and record something from my audio interface, also pipewire is used for screen sharing in wayland
2022-08-10.log [21:30:35] <xisop> never heard of pipewire. i'll have to check it out. i'm not too fond of the whole pulseaudio system
2022-08-10.log [21:40:57] <gnarface> you don't need pulseaudio or pipeire for that
2022-08-10.log [21:43:32] <EdBoatConnoisseu> aurdour really only requires jack, pipewire provides both jack and pulseaudio api emulation, and i don't see myself recording music without a Digital Audio Workstation so i'm okay with that compromise
2022-07-18.log [15:12:15] <systemdlete> another post I found said there was a similar issue (back in ff 60 though) if pulseaudio was disabled
2022-07-18.log [15:12:26] <gnarface> hmm, i DO have pulseaudio disabled
2022-07-18.log [15:15:46] <gnarface> however, an old symlink fix for other crashes that happen when pulseaudio isn't installed worked for that, though i'd be surprised if that helps firefox the trick was just to symlink libpulse-simple.so.0 to /dev/null and then shove that in the program's LD_LIBRARY_PATH
2022-07-03.log [02:16:27] <gnarface> hmm, personally i don't know a lot about pulseaudio but i do think they have some plugins and one might do that, but my guess is you'll probably have to change a config file
2022-07-03.log [02:17:55] <gnarface> some other gui audio processing program might be suitable as a passthrough though, not pulseaudio specific
2022-07-03.log [02:22:14] <gnarface> not my area of expertise again though, you might have better luck with this in the pulseaudio channel
2022-07-03.log [02:27:02] <gnarface> google search suggests a pulseaudio module called "module-echo-cancel" can you check for that?
2022-07-03.log [02:29:50] <gnarface> so, my initial scanning suggests you can enable it in the main pulseaudio config then it will show up in a dropdown menu
2022-07-03.log [02:31:10] <gnarface> so another thing i vaguely recall was something about pulseaudio also not selecting the high quality input by default, though that may just be an old bug it's probably worth checking on too while you're in there
2022-07-03.log [02:34:39] <gnarface> pulseaudio works on top of alsa, so sometimes alsa configuration issues can affect it too
2022-07-03.log [02:46:18] <salloid> but when i list pulseaudio modules it does not
2022-06-29.log [13:35:39] <buZz> 15:31:45 < buZz> i upgraded a install to chimaera and pavucontrol stopped working plus i dont even see pulseaudio running anymore
2022-06-29.log [13:38:19] <rrq> does it work starting pulsaudio manually? "pulseaudio --start"
2022-06-29.log [13:41:28] <fsmithred> are pulseaudio and pavucontrol still installed?
2022-06-29.log [13:42:39] <buZz> kinda feels like pulseaudio now outputs through pipewire
2022-06-29.log [13:45:16] <buZz> rrq: again, i dont need pulseaudio to ever run :P
2022-06-25.log [00:06:07] <gnarface> hmm, i avoid pulseaudio but i think, try this as root: pasuspender -- alsamixer
2022-06-25.log [00:06:42] <gnarface> in general for output, you want to max the volume settings in alsamixer if you're using pulseaudio
2022-06-25.log [00:08:38] <gnarface> if that doesn't work you have to put "autospawn = no" in (i think) ~/.pulse/client.conf and then kill pulseaudio
2022-06-25.log [00:09:45] <gnarface> though previously i couldn't figure out how to properly relaunch pulseaudio in user mode without logging out
2022-06-25.log [00:26:27] <treeofknowledge> i use to use pulseaudio pauvcontrol