On Sat, Nov 10, 2018 at 5:39 AM Mr riaas mokiem wrote:
> > If you issue a `systemctl --user restart pulseaudio`, does it take a
> long time too?
> This is how I originally verified that it took too long. I don't remember
> exactly whether I tried this "restart" specifically or whether I just
On Sat, Nov 3, 2018 at 2:19 PM Mr riaas mokiem wrote:
> Here's the output:
> $ /usr/lib/rtkit/rtkit-test
> Max realtime priority is: 20
> Min nice level is: -15
> Rttime limit is: 20 ns
> before:
> SCHED_RESET_ON_FORK: no
> SCHED_OTHER with nice level: 0
> Successfully became
On Sat, Oct 13, 2018 at 3:09 AM Mr riaas mokiem wrote:
> I think I've got the log. I had to edit the main pulseaudio.service file
> because it was saying something about "bad unit" when I used the suggested
> command. And I could only find the logs in the main journalctl output (not
> with
Control: severity -1 important
Control: tags -1 moreinfo
Hi,
On Sun, Oct 7, 2018 at 11:21 AM Riaas Mokiem wrote:
> Package: pulseaudio
> Version: 12.2-2
> Severity: grave
> Justification: renders package unusable
>
>
Lowering severity since it does not appear to affect everyone.
> Dear
Package: pulseaudio
Version: 12.2-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Pulseaudio is taking longer to start up than the default 90 seconds that
systemd allows for a service. This means that Pulseaudio does not work on
startup and no matter how much you try
5 matches
Mail list logo
