https://bugzilla.suse.com/show_bug.cgi?id=1198140 https://bugzilla.suse.com/show_bug.cgi?id=1198140#c1 Markus Kolb <novell@tower-net.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |novell@tower-net.de --- Comment #1 from Markus Kolb <novell@tower-net.de> --- I've a Lenovo Ideapad 5 15ABA7 and with Leap 15.5 there is maybe the same problem. After wakeup from suspend to ram or hibernate and screen lock login, I've always to "turn bluetooth on" via the blueman applet of Xfce. There is on wakeup (reverse order) in journal... Oct 01 19:47:37 15ABA7 systemd-sleep[10349]: System returned from sleep state. Oct 01 19:47:37 15ABA7 systemd[1]: Reached target Bluetooth Support. Oct 01 19:47:37 15ABA7 systemd[1262]: Reached target Bluetooth. Oct 01 19:47:37 15ABA7 systemd[1]: Started Load/Save RF Kill Switch Status. Oct 01 19:47:37 15ABA7 systemd[1]: Stopped target Bluetooth Support. Oct 01 19:47:37 15ABA7 systemd[1262]: Stopped target Bluetooth. Oct 01 19:47:37 15ABA7 systemd[1]: Starting Load/Save RF Kill Switch Status... Oct 01 19:47:37 15ABA7 systemd-logind[819]: Lid opened. As there is nothing bluetooth related before suspend... Oct 01 19:14:02 15ABA7 kernel: Filesystems sync: 0.012 seconds Oct 01 19:14:02 15ABA7 kernel: PM: suspend entry (deep) Oct 01 19:14:02 15ABA7 systemd-sleep[10349]: Entering sleep state 'suspend'... Oct 01 19:14:02 15ABA7 systemd[1]: Starting System Suspend... Oct 01 19:14:02 15ABA7 systemd[1]: Reached target Sleep. [...] Oct 01 19:13:59 15ABA7 systemd-logind[819]: Lid closed. could it be that the bluetooth stop code could not be run before sleep has reached and is continue to run on wakeup without storing the correct bluetooth status?! Shouldn't the lines Oct 01 19:47:37 15ABA7 systemd[1]: Stopped target Bluetooth Support. Oct 01 19:47:37 15ABA7 systemd[1262]: Stopped target Bluetooth. Oct 01 19:47:37 15ABA7 systemd[1]: Starting Load/Save RF Kill Switch Status... be somewhere around 19:14? -- You are receiving this mail because: You are on the CC list for the bug.