Description of problem:
I'm trying to troubleshoot problem with HP-LaserJet-Professional-P-1102w printer. When using troubleshooting using s-c-p, it asked me to run journalctl command to get logs, because of using unprivileged user.
The command was:
su -c 'journalctl -u cups.service --since="None" --until="2018-05-11 09:31:37"' > troubleshoot-logs.txt
I changed it to:
sudo journalctl -u cups.service --since="None" --until="2018-05-11 09:31:37" > troubleshoot-logs.txt
However journalctl says that it does not know timestamp None.
$ sudo journalctl -u cups.service --since="None" --until="2018-05-11 09:31:37" > troubleshoot-logs.txt
[sudo] password for xxx:
Failed to parse timestamp: None
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. described above
s-c-p provides command which is obviously wrong.
s-c-p should provide command that works
I'm experiencing this on F26, but reporting it against rawhide, because I don't see any relevant change in RPM changelog in recent versions. And I would like to make sure this bug is not mass-closed soon.
thank you for reporting this issue! I was able to reproduce the issue. I'll look into it.
Traceback, which is related to the error:
/usr/share/system-config-printer/timedops.py:82: Warning: Source ID 1184 was not found when attempting to remove it
File "/usr/share/system-config-printer/troubleshoot/__init__.py", line 316, in _collect_answer
answer = question.collect_answer ()
File "/usr/share/system-config-printer/troubleshoot/ErrorLogCheckpoint.py", line 143, in collect_answer
File "/usr/share/system-config-printer/timedops.py", line 211, in run
return self.thread.collect_result ()
File "/usr/share/system-config-printer/timedops.py", line 164, in collect_result
File "/usr/share/system-config-printer/timedops.py", line 152, in run
self.result = self.target (*self.args, **self.kwargs)
File "/usr/share/system-config-printer/authconn.py", line 227, in <lambda>
return lambda *args, **kwds: self._authloop (fname, fn, *args, **kwds)
File "/usr/share/system-config-printer/authconn.py", line 245, in _authloop
result = fn.__call__ (*args, **kwds)
File "/usr/share/system-config-printer/cupspk.py", line 422, in getFile
File "/usr/share/system-config-printer/cupspk.py", line 112, in _call_with_pk_and_fallback
return fallback_function(*args, **kwds)
TypeError: argument 2 must be str, not _io.BufferedRandom
There should be timestamp instead of value None. This timestamp is taken when troubleshooter starts, but it doesn't do that for a reason.
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 29 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.