ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
glennk has quit [Ping timeout: 480 seconds]
bindu_ has joined #wayland
bindu has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
karenw has quit [Ping timeout: 480 seconds]
Flat has quit [Quit: Rip internet]
Flat has joined #wayland
kts has joined #wayland
glennk has joined #wayland
kts has quit [Ping timeout: 480 seconds]
kts has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
kts has quit [Ping timeout: 480 seconds]
psykose has quit [Remote host closed the connection]
kts has joined #wayland
kts has quit [Read error: No route to host]
alarumbe has quit []
mohan43u has quit [Quit: WeeChat 4.4.2]
dcz has joined #wayland
mohan43u has joined #wayland
WhyNotHugo has quit [Remote host closed the connection]
OrkotravelingMay30[m] is now known as OrkoOootillJun4[m]
rasterman has joined #wayland
lanodan has joined #wayland
kts has joined #wayland
kts has quit [Ping timeout: 480 seconds]
kts has joined #wayland
karmavil[m] has joined #wayland
<karmavil[m]>
<smith1727> "but yeah, when i do it from..." <- I might be wrong but I think the bios rules what the OS can do about hibernation and suspension. Probably which events are allowed to resume too (keyboard, mouse, others).
<karmavil[m]>
I have an encrypted drive and if I exceed the max attempts to unlock, it will try to suspend or hibernate. In my case I can see the message "gave up trying ..."