Tag Info

New answers tagged

0

By the way you can ask ps to show corresponding systemd unit. [lnykryn@notas]$ ps -o'pid,ppid,args,unit' `pgrep pulse` PID PPID COMMAND UNIT 1345 1 /usr/bin/pulseaudio --start session-1.scope


2

A) Is there a way to determine the systemd unit that caused the creation of a specific process (in my example output, process 2738, the PA daemon)? Sure. You can run systemctl status <pid> and systemd will find you the unit that contains that PID. For example, on my system I find a dnsmasq process: # ps -fe | grep dnsmasq nobody 18834 1193 ...


0

Note, a process having a parent PPID of 1 does not mean it was created by systemd. Any process that loses its parent process is automatically re-assigned the parent 1. You can see the hierarchy of systemd processes with systemctl status which shows for me amongst other stuff (edited): CGroup: |-1 /usr/lib/systemd/systemd --system --deserialize 17 ...


0

I found an answer here: http://www.debianuserforums.org/viewtopic.php?f=55&t=2433#p23869 I just had to enter modprobe snd_hda_codec modprobe snd_hda_intel modprobe snd_hda_intel_codec and now the sound is working


0

Kodibuntu blocks the pulseaudio packages from being installed by apt. You can undo the block by removing/moving the following files: /etc/apt/preferences.d/libasound2-plugins.pref /etc/apt/preferences.d/libasound2-plugins.pref.bak After this you can do another apt-get update and you should be able to install the packages.


0

I don't suggest purging the pulseaudio package. You could remove it's files and then re-install it, if you really want to try that. Things to check: psg () { ps u -p $(pgrep "${@:--u$USER}"); } # define a handy function psg pulse # see if there is a pulseaudio process running cat /proc/asound/card0/pcm0p/sub0/hw_params # see if anything in your ...



Top 50 recent answers are included