Post #1999408

Few seem to address the issue here : it does not work 100% of the time for you. It might work for everybody else but that doesn’t help you much. You have your setup, no theirs. So… you need to investigate. When it works, great, nothing to learn from. When it fails though… can you find a pattern? Does it always fail after you have use something specific? Check lemmy.ml/post/46800646/25494455 which gives examples of potential failure point and journalctl logs. You can then check what failed and if not you can at least know when then backtrack to others logs, e.g. dmesg. They key take away is that when things do not behave as expected you need to put a detective hat on and you investigate : what’s your crime scene? Your laptop and it’s log files what’s the crime? It didn’t suspend properly where are the traces? In the logs where are the logs? Using journalctl or dmesg and typically in /var/log/ what would a good detective do? Search for specific clues, e.g. places where fingerprints do stick, e.g metal or glass, which here would be error messages. That can be found using grep and other tools You also have limited times because the logs will, just like on a real crime scene, get contaminated or rotated or deleted. So… if you do encounter the problem do not rush to the next tasks at hand because you are wasting an opportunity to learn and there is vanishing window. TL;DR : grep logs