<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - timesyncd: clock is off"
href="https://bugs.freedesktop.org/show_bug.cgi?id=80582#c20">Comment # 20</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - timesyncd: clock is off"
href="https://bugs.freedesktop.org/show_bug.cgi?id=80582">bug 80582</a>
from <span class="vcard"><a class="email" href="mailto:zbyszek@in.waw.pl" title="Zbigniew Jedrzejewski-Szmek <zbyszek@in.waw.pl>"> <span class="fn">Zbigniew Jedrzejewski-Szmek</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=80582#c19">comment #19</a>)
<span class="quote">> I closed our bug because the package now works.
>
> Perhaps you can take a moment to read my first comment, number 13, where I
> bring the conversation here to determine with systemd developers what the
> underlying problem is. This happened right after closing our bug. </span >
So, even if there's a bug in the timesyncd code, it is only exposed by your
build system. It is pretty obvious from the comments from Kay and others, that
it works for him, and for others, and is unlikely to be fixed except by people
who are using the build in question. I'd try comparing the disassembly of a
failed build with one that works, or maybe run it under gdb and look at the
values, or something. I tried to reproduce this on an arm chromebook without
success.
<span class="quote">> If what I can expect is attacks here, the rug will be used. This is
> ridiculous.</span >
Please don't treat this is as an attack. If your intent is to continue
debugging this, then please consider my comment withdrawn.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>