<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Wrong command for collecting journalctl info in "Printing troubleshooter" wizard"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=122143#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Wrong command for collecting journalctl info in "Printing troubleshooter" wizard"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=122143">bug 122143</a>
from <span class="vcard"><a class="email" href="mailto:den_lin@posteo.de" title="Denis <den_lin@posteo.de>"> <span class="fn">Denis</span></a>
</span></b>
<pre>(In reply to Julien Nabet from <a href="show_bug.cgi?id=122143#c1">comment #1</a>)
<span class="quote">> Where is this option?</span >
In "Printing troubleshooter" wizard. This is connected to another bug that I
reported: <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - "cups-pki-invalid" error when accessing printer over Avahi"
href="show_bug.cgi?id=122142">https://bugs.documentfoundation.org/show_bug.cgi?id=122142</a>. Repeat
the steps to reproduce the bug. After them appears "Print error" window with
buttons "OK" and "Diagnose". (Note: this window doesn't always appear, you may
have to send another document to the printer). Click "Diagnose". "Printing
troubleshooter" wizard pops up. Forward -> select the printer -> Forward ->
Print test page -> No -> Forward. Here the wizard says "No journal entries were
found" and offers a command to copy and execute in CLI. This command is:
su -c 'journalctl -u cups.service --since="None" --until="2018-12-16 19:50:37"'
<span class="quote">> troubleshoot-logs.txt</span >
See --since="None"
The result of running this command is:
Failed to parse timestamp: None
The man page of journalctl also makes no mention of the option "none" in the
section "--since".</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>