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]: Volum
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
confi
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1767065/+attachment/5128197/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1767065/+attachment/5128204/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1767065/+attachment/5128201/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchp
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1767065/+attachment/5128203/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1767065/+attachment/5128200/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1767065/+attachment/5128202/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchp
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1767065/+attachment/5128198/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchp
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1767065/+attachment/5128199/+files/Dependencies.txt
** Description changed:
Hello,
I'm a sysadmin and have gotten multiple reports recently from users of
them randomly getting logged out of th
Another update. After truning off pulseaudio yesterday, the system
didn't crash as fast as before, but it did eventually lock up a couple
of times. The logs seems similar even without pulse, still beginning
with the bluetooth service.
After this I completely turned off bluetooth from the BIOS of t
Update,
I noticed the pattern so far and turning off pulseaudio seems to have
stopped the behaviour. I obviously can't leave the system without sound,
so I'm still looking for a permanent fix.
The pattern is allways like this:
Apr 26 15:06:07 ESS-PC26 bluetoothd[11243]: Endpoint registered: send
Went, did step 1 and 2, looked in /var/crash and there was nothing.
There are no crash logs in that location for the event that just
happened.
Attached another printout of journalctl. From what I can tell the system
went in full shutdown mode and logged the user out.
** Attachment added: "journa
** Description changed:
Hello,
I'm a sysadmin and have gotten multiple reports recently from users of
them randomly getting logged out of their machines. From what I can tell
from the journalctl printout this appears immediately after either
bluetoothd or pulsaudio crashes.
This
Public bug reported:
Hello,
I'm a sysadmin and have gotten multiple reports recently from users of
them randomly getting logged out of their machines. From what I can tell
from the journalctl printout this appears immediately after either
bluetoothd or pulsaudio crashes.
This is happening multip
15 matches
Mail list logo