<html style="direction: ltr;">
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body bidimailui-detected-decoding-type="latin-charset"
style="direction: ltr;">
<p><br>
</p>
<div class="moz-cite-prefix">On 12/03/2021 14:08, Shachar Shemesh
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f655ea61-1438-c480-95a8-7a621ee00edc@shemesh.biz">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<style id="bidiui-paragraph-margins" type="text/css">body p { margin-bottom: 0.3cm; margin-top: 0pt; } </style>
<p><br>
</p>
<div class="moz-cite-prefix">On 12/03/2021 12:34, <a
class="moz-txt-link-abbreviated"
href="mailto:borissh1983@gmail.com" moz-do-not-send="true">borissh1983@gmail.com</a>
wrote:<br>
</div>
<blockquote type="cite" cite="mid:4677426.jbxs0lztFJ@beast">
<p
style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><br>
<br>
Would it be possible to monitor both dbus messages (system and
user) AND Xsession errors while you do so ? </p>
</blockquote>
<p>Yes, that provided some progress. At least I can tell the name
of the component that triggers the shutdown. The session dbus
monitor says:<br>
</p>
<p>signal time=1615549109.464622 sender=:1.13 ->
destination=(null destination) serial=832
path=/component/org_kde_powerdevil;
interface=org.kde.kglobalaccel.Component;
member=globalShortcutPressed<br>
string "org_kde_powerdevil"<br>
string "PowerOff"<br>
int64 6630990</p>
<p>I'm not 100% sure what that means. It seems that powerdevil
thinks that someone pressed the power button. More research
necessary, but at least we're finally getting a log admitting
_something_ happened.<br>
</p>
<br>
</blockquote>
<p>I've cracked it!!!</p>
<p>The problem was that my USB-C docking station was incapable of
providing enough power to run the computer. It should not have
been a problem, as I'm guessing the problem was momentary and the
computer's battery would have also sufficed. It did, however,
respond to this situation by sending a power-off key (which is why
the BIOS did not say anything - it wasn't it that initiated the
shutdown).</p>
<p>I've connected the computer's provided power supply, and the
problem is now GONE.</p>
<p>Thank you, everyone.</p>
<p>Shachar<br>
</p>
</body>
</html>