Event JSON
{
"id": "b0d9439e30988bc233eba49a303dff67a1572e75e10bcc6988db9de7b8f56620",
"pubkey": "29f1af29594197f4611b67d89d3068f8c0e28e460edd22ab3bd35fb2baf9ac82",
"created_at": 1717346274,
"kind": 1,
"tags": [
[
"p",
"7b2bcff7a3875d812cd5b7c792a467e6c5fedd592da770fffa7ffb154b15259d"
],
[
"e",
"8ef163fd57fecf5634340a34f0c56749c678c904366e1d80295bfae689287fc0",
"",
"root"
],
[
"e",
"eee622812cfe26b9391719015a654400385b36480197aff83ffb35a85096312a",
"",
"reply"
],
[
"p",
"29f1af29594197f4611b67d89d3068f8c0e28e460edd22ab3bd35fb2baf9ac82"
],
[
"proxy",
"https://fosstodon.org/@matthartley/112548005424931996",
"web"
],
[
"proxy",
"https://fosstodon.org/users/matthartley/statuses/112548005424931996",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://fosstodon.org/users/matthartley/statuses/112548005424931996",
"pink.momostr"
]
],
"content": "Lastly as I'm super curious. Which distro and kernel? \n\nopenSUSE for example, has had suspend issues off and on (regression if memory serves, Tumbleweed). Logs will usually indicate why, but yeah, it's a thing. \n\nRegarding the \"works for me crowd\", technically the desktop (whatever it may be) should not be able to inhibit suspend unless something is creating the option to do so.\n\nHowever, config, attached devices, missing services or even a specific KDE setting, can inhibit suspend",
"sig": "fabc065cfa951e746fa3d19e335951ab53d6519eee9efebd73dd3082bebae18691b9dea88ba39bd00e32d064c36999e047cbeed576f354e21eb3d3d7ab2ffd6b"
}