Pulseaudio or bluetoothd crashing would not log you out. At most only
audio would stop working, but usually it will automatically restart and
you not notice anything at all.
Pulseaudio or bluetoothd crashing would leave files in /var/crash. So
that's further evidence that they are not crashing in
Spoke too soon, it happened again. Seems to be from pulse and bluetooth.
Why is systemd still trying to start bluetooth when it is off in the
bios and the service is disabled. I really don't understand what I can
try more to debug.
Apr 30 11:31:09 ESS-PC26 org.gtk.vfs.AfcVolumeMonitor[8928]:
I was thinking this bug might not be related to Pulse. But if it is am
happy to keep it open.
I suggest taking log message with a pinch of salt. In most cases the log
messages you see actually have nothing to do with external buggy
behaviours observed around the same time. That would be too
Now this is something really weird. I said for the hell of it to try and
see if this would fix the issue. I was thinking that to save energy
maybe the system tried to power down wifi/bluetooth and such during idle
times.
I added intel_idle.max_cstate=1 to the kernel start options in the grub
** Summary changed:
- pulseaudio+bluetooth crash causing user to be logged out (since pulseaudio
1:8.0-0ubuntu3.9)
+ [regression] pulseaudio+bluetooth crash causing user to be logged out (since
pulseaudio 1:8.0-0ubuntu3.9)
--
You received this bug notification because you are a member of
5 matches
Mail list logo
