Thus quoth David Izquierdo at 19:16 on Tue, May 09 2017:
>
> I don't know how to see that process' logs. Maybe some magic journalctl
> option. Is it possible that it's starting as a systemd user service?
> Then `journalctl --user -eu pulseaudio` would work... But starting pulse
> like that
I don't know how to see that process' logs. Maybe some magic journalctl
option. Is it possible that it's starting as a systemd user service?
Then `journalctl --user -eu pulseaudio` would work... But starting pulse
like that doesn't seem to work for me.
On 09/05/17 21:13, Mark Gardner wrote:
David,
On Tue, May 9, 2017 at 2:59 PM, David Izquierdo wrote:
> If you run `pulseaudio -k`, does it kill it?
No:
$ pulseaudio -k
E: [pulseaudio] main.c: Failed to kill daemon: No such process
But the daemon is running as me:
$ ps aux | grep pulseaudio
user
2572
If you run `pulseaudio -k`, does it kill it? Once dead, what does it log
if you run `pulseaudio` and then try to use pavucontrol or other program?
On 09/05/17 20:58, Mark Gardner wrote:
On Tue, May 9, 2017 at 2:32 PM, Sergiu Ivanov wrote:
I suppose you tried rebooting
On Tue, May 9, 2017 at 2:32 PM, Sergiu Ivanov wrote:
> I suppose you tried rebooting after installing the packages?
>
Yes. I did that before doing the above actions. I even upgraded to 17.03
(from 16.09) in case that helped. It didn't.
> I'm afraid I'm running out of
Thus quoth Mark Gardner at 18:05 on Tue, May 09 2017:
> On Tue, May 9, 2017 at 1:50 PM, Sergiu Ivanov wrote:
>
>> What happens if you install pavucontrol and pamixer in a user environment?
>
[...]
> $ pavucontrol
>
> ** (pavucontrol:8551): WARNING **: Error retrieving
Thanks for your prompt reply Sergiu.
On Tue, May 9, 2017 at 1:50 PM, Sergiu Ivanov wrote:
> What happens if you install pavucontrol and pamixer in a user
>
environment?
>
$ nix-env -iA nixos.pavucontrol
installing ‘pavucontrol-3.0’
building path(s)
Hello Mark,
Thus quoth Mark Gardner at 17:38 on Tue, May 09 2017:
>
> I am having trouble getting PulseAudio to work. I added the following to
> configuration.nix, executed nixos-rebuild switch, and rebooted:
>
> hardware.pulseaudio = {
> enable = true;
> package =
`man default.pa` has to say:
The PulseAudio sound server interprets the file
~/.config/pulse/default.pa on startup, and when that file doesn't exist
/etc/pulse/default.pa.
Just out of curiosity I checked the source and it seems that this line
was already there in 2007 and the code that
On Mon, Jan 26, 2015 at 6:46 PM, Peter Jones mli...@pmade.com wrote:
From what I understand, there's no way to use `startx' with systemd.
There might be some NixOS-specific issues here, I’m not sure. But in
general there _is_ a way: you just login on the text console and run
`startx`.
That's
On Tue, Jan 27, 2015 at 11:57 AM, Michael Raskin 7c6f4...@mail.ru wrote:
From what I understand, there's no way to use `startx' with systemd.
There might be some NixOS-specific issues here, I’m not sure. But in
general there _is_ a way: you just login on the text console and run
`startx`.
No.
Kirill Elagin kirela...@gmail.com writes:
Do you use a desktop manager or start your X session manually? The
important thing is to make sure that your X server is running on _the same
virtual terminal_ your logind session was opened on, otherwise you won’t
get permissions to access hardware.
As Benno said this means that most likely something is wrong with your
session and you don’t get access to audio devices.
What’s strange is that 14.12 uses xorg-server-1.16-* and this should run as
user by default and as a result should crash with insufficient permissions
to access video devices
PulseAudio should get its permissions from systemd logind. You can use
loginctl to view of you're properly assigned a seat.
Regards,
Benno
Peter Jones mlists mli...@pmade.com@ mli...@pmade.compmade.com
mli...@pmade.com schrieb am So., 25. Jan. 2015 19:40:
Peter Jones mli...@pmade.com writes:
Peter Jones mli...@pmade.com writes:
Pulseaudio stopped working for me after upgrading to 14.12. It seems
that all PA clients start their own server, which eventually fails
because the pulseaudio daemon is already running.
I just noticed that pulseaudio
Kirill Elagin kirela...@gmail.com writes:
What exactly do you mean by “disabling” pulseaudio?
Do you have a system-wide instance of pulseaudio running (e.g. by setting
`pulseAudio.systemWide = true` in the configuration.nix)? If yes, then do
you have any good reasons for doing so? If no, then
Peter Jones mli...@pmade.com writes:
Pulseaudio stopped working for me after upgrading to 14.12. It seems
that all PA clients start their own server, which eventually fails
because the pulseaudio daemon is already running.
I just noticed that pulseaudio doesn't see my sound cards:
$ pacmd
What exactly do you mean by “disabling” pulseaudio?
Do you have a system-wide instance of pulseaudio running (e.g. by setting
`pulseAudio.systemWide = true` in the configuration.nix)? If yes, then do
you have any good reasons for doing so? If no, then disable the system-wide
instance.
Normally,
18 matches
Mail list logo