[SOLVED] Another Slackware user with PulseAudio problems

bassmadrigal · 03-17-2017, 11:54 AM

Quote:

Originally Posted by selfprogrammed

XFCE is starting a pulseaudio, so there is one available, but it is not working.
Throws error messages about not being able to find ALSA profile, whatever that is.
I have checked that the /usr/share/pulse files are there.
Being that there was some sound previous (bad, but present), it must have been able to
find the files before. It may be the first pulseaudio was actually handling some sound
and the second started by XFCE cannot find the profile files.
I may be that Slackware is setup only for the system pulseaudio that is started by rc.d/rc.slackware, as Slackware installed that file as executable. The pulseaudio started by XFCE may be a rogue.

I wish someone with Slackware would tell me which pulseaudio they have running and which of these setups is supposed to work.

On my HTPC (full Slackware64 14.2 install, no multilib), running KDE and kodi, I only have one pulseaudio process, and it is started by my user with a PPID of 1. The exact command is:

Code:

/usr/bin/pulseaudio --start --log-target=syslog

I do not have rc.pulseaudio or rc.alsa executable. I have no issues with my sound from kodi (using both passthrough and regular output for stereo or 5.1 surround sound).

Quote:

Originally Posted by selfprogrammed

As of now, I can play midi using the latest TiMidity, without the noise problems it had before.
Part of that may have been priority issue, as it was set to a priority much higher than pulseaudio. If ALSA then redirected the output through pulseaudio, then the driver would be fighting for CPU with TiMidity. With only ALSA handling sound this does not happen.
Setting priority of TiMidity using the TiMidity start command line will always do this as it adds your number to a real-time priority that is much higher than anything else.
To set a lower priority in the rc.d/rc.local you must discover the TiMidity PID and then use system tools to set it directly. I set it to be close to the pulseaudio daemaon priority.

I can also use audacious, as it has an output selection that can select ALSA. Now that it does not redirect through pulseaudio it works and sounds great.

MPlayer sounds horrible and scratchy (same CD and songs as tested on Audacious). It also does not read the CDROM until the buffer is empty, and so the music stops every 10 sec to read more of the CDROM. Cannot find a setting to fix that or reason why there should be one.
KPlayer is a front for MPlayer and behaves exactly the same.

Amarok has gone amok. It was working last week, it would play its default music. Now it just flickers alot, with this little box that goes on and off about 3 to 4 times a second.
The little box has pause and cancel buttons, but you cannot hit them. Also Amarok is not responding so to even close it you must go through the "Program not responding" messages.

Still do not have sound for the Pairs program (which did have sound a couple weeks ago).

SDL sound still does not seem to work. This is in spite of it having worked after killing the pulseaudio daemon during a previous test.
I would be surprised if they managed to route it through pulseaudio, but not too surprised considering what a mess pulseaudio has caused.

I would not be too surprised if it turned out that some programs were using the system pulseaudio and some were using the XFCE pulseaudio. Then the two pulseaudio daemons were fighting to grab the sound devices, so only some programs would work depending on who had grabbed it.

While I can't comment on anything that you've manually switched to alsa, or anything that is having issues due to that switch, I can say that all those programs seem to work fine on my system (except I can't test the playing of CDs with mplayer as I removed my last CD/DVD drive from my desktop a year or so ago). But you seem to have a lot of problems that shouldn't exist with a relatively simple setup like yours. Have you tried reinstalling Slackware to see if those problems still occur?

ppr:kut · 03-17-2017, 12:03 PM

Some things sound very weird here and definitely hint towards some issues specific to your system.

The pulseaudio init script by default is not used, you have to specifically enable it if you have a use case that needs it. Normal recommendation is to not use it.
I'm running KDE and have KDE starts pulseaudio, I have exactly one process running.

Are you starting timidity from an init script? If yes, you might have to change that to start timidity on login of your user instead.

Richard Cranium · 03-17-2017, 06:13 PM

I think that one way to suppress this stuff...

Code:

Mar 16 12:27:00 MySys pulseaudio[825]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="1" card_name="alsa_card.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed.
Mar 16 12:27:00 MySys pulseaudio[1171]: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
Mar 16 12:27:00 MySys pulseaudio[1171]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="1" card_name="alsa_card.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed.
Mar 16 12:27:05 MySys pulseaudio[2037]: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
Mar 16 12:27:05 MySys pulseaudio[2037]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="1" card_name="alsa_card.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed.
Mar 16 12:27:05 MySys pulseaudio[2037]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
Mar 16 12:47:11 MySys pulseaudio[825]: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
Mar 16 12:47:11 MySys pulseaudio[825]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="1" card_name="alsa_card.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed.
Mar 16 12:47:11 MySys pulseaudio[2037]: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
Mar 16 12:47:11 MySys pulseaudio[2037]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="1" card_name="alsa_card.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed.

...would be to comment out...

Code:

### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
### Use the static hardware detection module (for systems that lack udev support)
load-module module-detect
.endif

...in /etc/pulse/default.pa

I haven't tried it on my systems, so I don't know what else will complain if you do it.

selfprogrammed · 03-18-2017, 11:18 AM

Have had some success, but not totally.

Discovered by pure desperation that pacmd has an "info" command that will dump who is connected to it.

I did not find this documented anywhere, not even in the PulseAudio man pages.
So if you are having problems too, write it down or memorize it.
Best way to examine PulseAudio
>> pacmd
>>> help
>>> info
>>> stat
>>> dump

Figured out something about the PulseAudio error messages. Guessing about this because they do not document any of this stuff.
** If you have a built-in sound device on your Motherboard, watch out **
** ALSA has detection that can find it.
** PulseAudio does NOT detect it, so no cards.
** To PulseAudio, ALSA is NOT A CARD, so it does not detect it using udev and does not detect anything using module-alsa-card either.
** You must manually load module-alsa-sink to get sound to go to ALSA NOT-A-CARD.
** After manual configuration, udev detect and many other modules are extraneous. They can be commented out to simplify things (optional).
** You will get the ALSA-sink as an output (but it is not a card).

This is likely a problem for anyone with an AC97 on their motherboard.
This setup is bad enough that there ought to be some menu selection in a setup tool to
select (real card, AC97, other on-board sound device, external device) etc.. and let the
tool set this mess up.

Can play music file using audacious (ALSA), and amarok (pulseaudio).
Amarok has settled down now that there is no CD in the CDROM drive.
Still do not know what it was doing, but have found two songs from the CDROM that mysteriously appeared in my directory.
I can have dragonplayer play simultaneous with audacious playing different music.

The Pairs game has sound again. It still cannot pronounce half of the Linux names, gets stuck. Has a serious defect in its text to speech converter that fails with the shipped game sounds.

ALSA direct does sound better than through PulseAudio.
I can use audacious->ALSA to play a song at much higher volume with full richness than dragonplayer->PulseAudio.
For the same music, PulseAudio seems to clip when set over 110%, a level that is much quieter at the speakers than ALSA direct.

The fuser command does not seem to indicate ownership of the device.
> fuser -v /dev/snd/*
I have seen fuser list three users of one device at the same time. I think they are all mixing through ALSA though. TiMidity is one reported and I know that goes through ALSA.
Have not figured what fuser is actually indicating with that name, or how it gets it.
If it is just a search of what programs think they are outputting to that device (indirectly)
then its meaning is quite different that what I initially would have thought.

Slackware shipped an SDL library that is connecting to pulseaudio. That is why SDL sound was not working (because pulseaudio was not working).
I got sound effects from SDL now, but not SDL MIDI music.

** NO SDL MIDI **
I DO NOT have MIDI music for SDL. Whatever they did does not route MIDI to TiMidity anymore.
I have TiMidity working, I can play songs using aplaymidi, so that is not the problem.

Installing the SDL library for Linux 2.6 may be an answer. I will get better sound and less hassle getting it away from PulseAudio.

Thanks for the help. Will post more later if any more real revelations are discovered.

enorbet · 03-18-2017, 11:29 AM

I don't wish to do anything even remotely like hijacking this thread but it seems OP would be just as happy as I would be to eliminate Pulseaudio altogether. Any benefits it may offer are either of no benefit to me or are not worth the tradeoffs. I have no Bluetooth gear nor do I intend to start. While there is now a version of Jack that will function with Puleaudio they've had to leave out function I prefer to keep and I NEED Jack or I'm back to regular dual-booting to Windows, something I have been happily free from for over 5 years.

I have tried recommended means of removing Pulseaudio but I get errors and erratic behaviour. Can anyone tell me what 14.2 Mutilib has that is currently dependent on Pulseaudio so I can either eliminate or reconfigure it/them and dump this POS.

bassmadrigal · 03-18-2017, 02:26 PM

Quote:

Originally Posted by enorbet

I don't wish to do anything even remotely like hijacking this thread but it seems OP would be just as happy as I would be to eliminate Pulseaudio altogether. Any benefits it may offer are either of no benefit to me or are not worth the tradeoffs. I have no Bluetooth gear nor do I intend to start. While there is now a version of Jack that will function with Puleaudio they've had to leave out function I prefer to keep and I NEED Jack or I'm back to regular dual-booting to Windows, something I have been happily free from for over 5 years.

I have tried recommended means of removing Pulseaudio but I get errors and erratic behaviour. Can anyone tell me what 14.2 Mutilib has that is currently dependent on Pulseaudio so I can either eliminate or reconfigure it/them and dump this POS.

I would imagine it would be the exact same programs that you have to do on the 64bit version. It would probably be easiest to use a 32bit VM and rebuild everything needed in there to remove pulseaudio, then you can take those rebuilt packages, match them up with the multilib ones that Eric provides, then run convertpkg-compat32 on those packages and install (or "upgradepkg --reinstall" if they're already installed) on your multilib system.

Then someone could take those packages and host them so people could use slackpkg+ to install a pulseaudio free system. If no one would be willing to host them, but someone else would be willing to do the work of building the packages, I could host them.

Quote:

Originally Posted by enorbet

...dump this POS.

Seriously, can we stop with the name calling? It might be a "POS" to you, but for many it is a lifesaver (no, I'm not one of them... I'm in the camp that I don't really care, because it hasn't affected me other than slightly simplifying installation so I don't have to specify cards and devices). When we name call, it loses the professionalism I like to think this forum has. Why can't you simply say "get rid of it"?

Gerard Lally · 03-18-2017, 02:46 PM

Quote:

Originally Posted by enorbet

I don't wish to do anything even remotely like hijacking this thread but it seems OP would be just as happy as I would be to eliminate Pulseaudio altogether. Any benefits it may offer are either of no benefit to me or are not worth the tradeoffs. I have no Bluetooth gear nor do I intend to start. While there is now a version of Jack that will function with Puleaudio they've had to leave out function I prefer to keep and I NEED Jack or I'm back to regular dual-booting to Windows, something I have been happily free from for over 5 years.

I have tried recommended means of removing Pulseaudio but I get errors and erratic behaviour. Can anyone tell me what 14.2 Mutilib has that is currently dependent on Pulseaudio so I can either eliminate or reconfigure it/them and dump this POS.

By coincidence I've just noticed my sound gone, and no playback devices in kmix. I think it might have something to do with virtual machines I'm running, but I'm not sure. And I have all the time in the world to chase down this problem and fix it.

So much for pulseaudio multiplexing sound. It can't even handle the startup of a VM. I could be wrong, of course, but this is the first problem I've had with sound since I bought my microphone last year, when pulseaudio in its infinite wisdom decided my microphone was my new playback device.

Didier Spaier · 03-18-2017, 02:59 PM

Quote:

Originally Posted by Gerard Lally

So much for pulseaudio multiplexing sound. It can't even handle the startup of a VM. I could be wrong, of course, but this is the first problem I've had with sound since I bought my microphone last year, when pulseaudio in its infinite wisdom decided my microphone was my new playback device.

pavucontrol

Gerard Lally · 03-18-2017, 03:07 PM

Quote:

Originally Posted by Didier Spaier

pavucontrol

I just did what I used to do with Windows - restarted. Which makes me wonder why I ever dropped Windows and moved to what was supposed to be a superior alternative.

But this pavucontrol is new to me and might come in useful some time, so thanks.

Richard Cranium · 03-18-2017, 04:20 PM

Code:

** If you have a built-in sound device on your Motherboard, watch out **
** ALSA has detection that can find it.
** PulseAudio does NOT detect it, so no cards.
** To PulseAudio, ALSA is NOT A CARD, so it does not detect it using udev and does not detect anything using module-alsa-card either.
** You must manually load module-alsa-sink to get sound to go to ALSA NOT-A-CARD.
** After manual configuration, udev detect and many other modules are extraneous. They can be commented out to simplify things (optional).
** You will get the ALSA-sink as an output (but it is not a card).

Frankly, all of my systems are able to auto-detect my built-in sound cards and pulseaudio uses them just fine.

Code:

lspci reports:
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)

cranium@toshiba:~$ pacmd stat
Memory blocks currently allocated: 2, size: 127.9 KiB.
Memory blocks allocated during the whole lifetime: 6343614, size: 1.8 GiB.
Memory blocks imported from other processes: 0, size: 0 B.
Memory blocks exported to other processes: 0, size: 0 B.
Total sample cache size: 0 B.
Default sample spec: s16le 2ch 44100Hz
Default channel map: front-left,front-right
Default sink name: alsa_output.pci-0000_00_1b.0.analog-stereo
Default source name: alsa_input.pci-0000_00_1b.0.analog-stereo
Memory blocks of type POOL: 2 allocated/3961000 accumulated.
Memory blocks of type POOL_EXTERNAL: 0 allocated/24025 accumulated.
Memory blocks of type APPENDED: 0 allocated/0 accumulated.
Memory blocks of type USER: 0 allocated/0 accumulated.
Memory blocks of type FIXED: 0 allocated/2382614 accumulated.
Memory blocks of type IMPORTED: 0 allocated/0 accumulated.
cranium@toshiba:~$ pacmd dump
### Configuration dump generated at Sat Mar 18 16:18:13 2017

load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore
load-module module-augment-properties
load-module module-switch-on-port-available
load-module module-udev-detect
load-module module-alsa-card device_id="0" name="pci-0000_00_1b.0" card_name="alsa_card.pci-0000_00_1b.0" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1"
load-module module-bluetooth-policy
load-module module-bluetooth-discover
load-module module-bluez5-discover
load-module module-esound-protocol-unix
load-module module-native-protocol-unix
load-module module-gconf
load-module module-default-device-restore
load-module module-rescue-streams
load-module module-always-sink
load-module module-intended-roles
load-module module-suspend-on-idle
load-module module-console-kit
load-module module-position-event-sounds
load-module module-role-cork
load-module module-filter-heuristics
load-module module-filter-apply
load-module module-x11-publish display=:0.0
load-module module-x11-cork-request display=:0.0
load-module module-x11-xsmp display=:0.0 session_manager=local/toshiba:@/tmp/.ICE-unix/4064,unix/toshiba:/tmp/.ICE-unix/4064
load-module module-cli-protocol-unix

set-sink-volume alsa_output.pci-0000_00_1b.0.analog-stereo 0x10000
set-sink-mute alsa_output.pci-0000_00_1b.0.analog-stereo yes
suspend-sink alsa_output.pci-0000_00_1b.0.analog-stereo yes

set-source-volume alsa_output.pci-0000_00_1b.0.analog-stereo.monitor 0x10000
set-source-mute alsa_output.pci-0000_00_1b.0.analog-stereo.monitor no
suspend-source alsa_output.pci-0000_00_1b.0.analog-stereo.monitor yes
set-source-volume alsa_input.pci-0000_00_1b.0.analog-stereo 0x1e2
set-source-mute alsa_input.pci-0000_00_1b.0.analog-stereo yes
suspend-source alsa_input.pci-0000_00_1b.0.analog-stereo yes

set-card-profile alsa_card.pci-0000_00_1b.0 output:analog-stereo+input:analog-stereo

set-default-sink alsa_output.pci-0000_00_1b.0.analog-stereo
set-default-source alsa_input.pci-0000_00_1b.0.analog-stereo

### EOF

enorbet · 03-18-2017, 10:14 PM

Quote:

Originally Posted by bassmadrigal

I would imagine it would be the exact same programs that you have to do on the 64bit version. It would probably be easiest to use a 32bit VM and rebuild everything needed in there to remove pulseaudio, then you can take those rebuilt packages, match them up with the multilib ones that Eric provides, then run convertpkg-compat32 on those packages and install (or "upgradepkg --reinstall" if they're already installed) on your multilib system.

Then someone could take those packages and host them so people could use slackpkg+ to install a pulseaudio free system. If no one would be willing to host them, but someone else would be willing to do the work of building the packages, I could host them.

Seriously, can we stop with the name calling? It might be a "POS" to you, but for many it is a lifesaver (no, I'm not one of them... I'm in the camp that I don't really care, because it hasn't affected me other than slightly simplifying installation so I don't have to specify cards and devices). When we name call, it loses the professionalism I like to think this forum has. Why can't you simply say "get rid of it"?

Thanks for your comments in the first paragraph. I will see if that can help me.

As for the second, can you not understand the need to communicate frustration and even anger for the strong-arm adoption imperative that, at least for some, creates so many more problems than it solves (and mostly to benefit crappy onboard sound, leaving those of us who spend for actual quality in audio, which matters so much to those of us that work in it) that it seems like a solution searching for a problem? Please tell me why it' a good thing to suppress one's honest opinion in some attempt at phony politeness that is far from truthful or accurate. I think OTOH it is important to communicate that some people in fact DO find it a POS. It has certainly cost me many hours of hair pulling nastiness, and for what?

Bottom line - I fully understand and agree with the availability of enough options to suit even the lowest common denominator. What I don't understand nor approve is exclusion where it becomes required to have it AND a huge mess to uninstall and switch. That does not seem at all like the Linux that won me over and kept me pleased for going on decades.

ppr:kut · 03-19-2017, 03:27 AM

Quote:

Originally Posted by selfprogrammed

Figured out something about the PulseAudio error messages. Guessing about this because they do not document any of this stuff.
** If you have a built-in sound device on your Motherboard, watch out **
** ALSA has detection that can find it.
** PulseAudio does NOT detect it, so no cards.
** To PulseAudio, ALSA is NOT A CARD, so it does not detect it using udev and does not detect anything using module-alsa-card either.
** You must manually load module-alsa-sink to get sound to go to ALSA NOT-A-CARD.
** After manual configuration, udev detect and many other modules are extraneous. They can be commented out to simplify things (optional).
** You will get the ALSA-sink as an output (but it is not a card).

This is likely a problem for anyone with an AC97 on their motherboard.
This setup is bad enough that there ought to be some menu selection in a setup tool to
select (real card, AC97, other on-board sound device, external device) etc.. and let the
tool set this mess up.

First time I hear about this, but also the first time someone actually bothered to research his problems, so thank you for that!
Would you mind adding a bit more info about your sound device so we can research a bit more based on that? lspci output should be fine.
dmesg output would also be nice so we can see what udev does on boot with the sound device. This is important because theoretically pulseaudio
should do the same.

Quote:

Originally Posted by selfprogrammed

** NO SDL MIDI **
I DO NOT have MIDI music for SDL. Whatever they did does not route MIDI to TiMidity anymore.
I have TiMidity working, I can play songs using aplaymidi, so that is not the problem.

I think the SDL library shipped with Slackware doesn't provide midi support. There were requests in the past to add fluidsynth and recompile SDL to add that functionality. Likely you'd have to do something similar.

Quote:

Originally Posted by enorbet

I don't wish to do anything even remotely like hijacking this thread but it seems OP would be just as happy as I would be to eliminate Pulseaudio altogether. Any benefits it may offer are either of no benefit to me or are not worth the tradeoffs.

pulseaudio is here to stay, it's not going anywhere. As a matter of fact integration will only get deeper from this point forward.

Quote:

Originally Posted by enorbet

Bottom line - I fully understand and agree with the availability of enough options to suit even the lowest common denominator. What I don't understand nor approve is exclusion where it becomes required to have it AND a huge mess to uninstall and switch. That does not seem at all like the Linux that won me over and kept me pleased for going on decades.

Making pulseaudio optional would've resulted in a situation that made nobody happy. People who hate it would still complain that it's there, and people who need it would complain that it's not the default. Both would've complained that things aren't working properly. Given the trend that pulseaudio was becoming more and more an integral part of that stack that multiple apps would require soon, paired with the fact that it actually worked flawlessly in our testing and that it was relatively easy to switch back from a pulseaudio default to an alsa default (which is not the same as removing pulseaudio), we picked the logical option.

Seriously though, this is not some proprietary shit. This is open source software built by a community that's accessible and trying to help. If this is such a big deal to you, why don't you spend some effort and figure out how to make it better? For example, the pulseaudio <-> jack integration is just waiting for someone to write a SlackBuild and submit it to SlackBuilds.org. I'm pretty sure you'd make a whole bunch of people happy with that.

willysr · 03-19-2017, 05:30 AM

SDL2 now goes into -Current

Code:

Sun Mar 19 05:27:13 UTC 2017
l/SDL2-2.0.5-i586-1.txz: Added.
l/SDL2_gfx-1.0.3-i586-1.txz: Added.
l/SDL2_image-2.0.1-i586-1.txz: Added.
l/SDL2_mixer-2.0.1-i586-1.txz: Added.
l/SDL2_net-2.0.1-i586-1.txz: Added.
l/SDL2_ttf-2.0.14-i586-1.txz: Added.
l/ffmpeg-3.2.4-i586-2.txz: Rebuilt.
       The package now includes ffplay, which required the SDL2 libraries.

bassmadrigal · 03-19-2017, 12:46 PM

Quote:

Originally Posted by enorbet

As for the second, can you not understand the need to communicate frustration and even anger for the strong-arm adoption imperative that, at least for some, creates so many more problems than it solves (and mostly to benefit crappy onboard sound, leaving those of us who spend for actual quality in audio, which matters so much to those of us that work in it) that it seems like a solution searching for a problem? Please tell me why it' a good thing to suppress one's honest opinion in some attempt at phony politeness that is far from truthful or accurate. I think OTOH it is important to communicate that some people in fact DO find it a POS. It has certainly cost me many hours of hair pulling nastiness, and for what?

Bottom line - I fully understand and agree with the availability of enough options to suit even the lowest common denominator. What I don't understand nor approve is exclusion where it becomes required to have it AND a huge mess to uninstall and switch. That does not seem at all like the Linux that won me over and kept me pleased for going on decades.

Yes, I do understand a need to vent frustration, but do you have to do that with name calling? Everything else in that post was venting your frustration, but you had to end it with calling it a POS. Everybody already knew you weren't happy with it based on the previous information on the post, but you had remained relatively professional through it... until the end. Can we just stop that? Why can't we just discuss the removal without losing professionalism?

elcore · 03-19-2017, 02:00 PM

It's easy to remove if you don't have KDE, just get rid of the libpulse package and see what breaks.
I think on my machine it was only mpg123 that depended on it, but I only install like 20% of the system libs and build custom XFCE on that.