** Changed in: fscrypt (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1889416
Title:
pulseaudio.service: Start request repeated
https://github.com/google/fscrypt/issues/270
** Bug watch added: github.com/google/fscrypt/issues #270
https://github.com/google/fscrypt/issues/270
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
** Bug watch added: Debian Bug tracker #964951
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964951
** Also affects: fscrypt (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964951
Importance: Unknown
Status: Unknown
--
You received this bug notification
not a bug in pulseaudio, but confirmed and fixed upstream in fscrypt
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
** Package changed: systemd (Ubuntu) => pulseaudio (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1889416
Title:
pulseaudio.service: Start request repeated
Ehrm. I don't agree with editing the service file that comes from the
package and will get overwritten. Ensuring the correct order in the PAM
configuration is the correct fix here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
As a workaround, you can try to edit the systemd file
"/usr/lib/systemd/user/pulseaudio.service" and add the line:
```
RestartSec=2s
```
Your [Service] section would look like to this:
```
[Service]
ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal
LockPersonality=yes
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: fscrypt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I'm here to just confirm the bug and that your workaround is working.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1889416
Title:
pulseaudio.service: Start
Bug fixed if I move pam_systemd.so below pam_fscrypt.so in /etc/pam.d
/common-session. Need to fix /usr/share/pam-configs/systemd so that
pam_systemd.so always end up after libpam_fscrypt (and potentially
everything else...)
** Package changed: pulseaudio (Ubuntu) => systemd (Ubuntu)
** Also
Or possibly we need to fix this with fscrypt being before other
additional modules. Adding both systemd and fscrypt on the bug :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
The previous version (1:13.99.1-1ubuntu3.4) has the same problem with
trying to create ~/.config/pulse before the home directory is available
(in this case decrypted). The theory at the moment is that the new patch
in 1:13.99.1-1ubuntu3.5 makes the code break earlier and therefor retry
faster.
We
For some reason the latest update (1:3.99.1-1ubuntu3.5) break if the
user has an encrypted home directory, in my case ext4 encryption.
$ journalctl -xe --user-unit pulseaudio
```
-- Reboot --
Jul 29 14:59:18 wendigo systemd[2664]: Starting Sound Service...
-- Subject: A start job for unit UNIT
14 matches
Mail list logo
