On 3/8/19 7:00 PM, Jack Craig wrote:
ok, try this, in a terminal or whatever, journalctl -u cups.service -f
then login to cups admin, stop printer, start printer accept jobs, print
test page, now what does journalctl have to say?
Did you see my letter about up]grading my flash drive and the symptom
appeared on it as well?
# journalctl -u cups.service -f
-- Logs begin at Sun 2018-03-11 23:46:44 PDT. --
Mar 08 14:50:47 rn6.rent-a-nerd.local systemd[1]: Starting CUPS Scheduler...
Mar 08 14:50:47 rn6.rent-a-nerd.local systemd[1]: Started CUPS Scheduler.
Mar 08 18:57:45 rn6.rent-a-nerd.local systemd[1]: Stopping CUPS Scheduler...
Mar 08 18:57:45 rn6.rent-a-nerd.local systemd[1]: Stopped CUPS Scheduler.
Mar 08 18:57:45 rn6.rent-a-nerd.local systemd[1]: Starting CUPS Scheduler...
Mar 08 18:57:45 rn6.rent-a-nerd.local systemd[1]: Started CUPS Scheduler.
Mar 08 18:58:05 rn6.rent-a-nerd.local systemd[1]: Stopping CUPS Scheduler...
Mar 08 18:58:05 rn6.rent-a-nerd.local systemd[1]: Stopped CUPS Scheduler.
Mar 08 18:58:09 rn6.rent-a-nerd.local systemd[1]: Starting CUPS Scheduler...
Mar 08 18:58:09 rn6.rent-a-nerd.local systemd[1]: Started CUPS Scheduler.
On Fri, Mar 8, 2019 at 6:28 PM ToddAndMargo via users
<users@xxxxxxxxxxxxxxxxxxxxxxx <mailto:users@xxxxxxxxxxxxxxxxxxxxxxx>>
wrote:
>> On Fri, Mar 8, 2019 at 2:55 PM ToddAndMargo via users
>> <users@xxxxxxxxxxxxxxxxxxxxxxx
<mailto:users@xxxxxxxxxxxxxxxxxxxxxxx>
<mailto:users@xxxxxxxxxxxxxxxxxxxxxxx
<mailto:users@xxxxxxxxxxxxxxxxxxxxxxx>>>
>> wrote:
>>
>> Hi All,
>>
>> Help!
>>
>> Fedora 29
>>
>> cups-1:2.2.8-10.fc29.x86_64
>> cups-client-1:2.2.8-10.fc29.x86_64
>> cups-filesystem-1:2.2.8-10.fc29.noarch
>> cups-ipptool-1:2.2.8-10.fc29.x86_64
>> cups-libs-1:2.2.8-10.fc29.i686
>> cups-libs-1:2.2.8-10.fc29.x86_64
>>
>> This morning I can not longer print.
>>
>> I fired up a Live USB, also Fedora 29, and I can print,
>> so it is not my hardware. (It is not program dependent
>> either.)
>>
>> https://127.0.0.1:631/printers/B4350 tells me "Processing since".
>> I can cancel jobs.
>>
>> This is the error message I am getting:
>>
>> Mar 8 14:47:02 rn6 dbus-daemon[1033]: [system] Rejected send
>> message, 0
>> matched rules; type="method_return", sender=":1.6" (uid=70
pid=1044
>> comm="avahi-daemon: starting up "
label="system_u:system_r:avahi_t:s0")
>> interface="(unset)" member="(unset)" error name="(unset)"
>> requested_reply="0" destination=":1.356" (uid=500 pid=6153
>> comm="/usr/bin/leafpad "
>> label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
>>
>> -T
Everything seems normal !
On 3/8/19 6:12 PM, Jack Craig wrote:
> *systemctl status cups.service*
> sez ??
# systemctl status cups.service
● cups.service - CUPS Scheduler
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled;
vendor preset:
disabled)
Active: active (running) since Fri 2019-03-08 14:50:47 PST; 3h 32m
in ago
Docs: man:cupsd(8)
Main PID: 6734 (cupsd)
Status: "Scheduler is running..."
Tasks: 2 (limit: 4915)
Memory: 7.4M
CGroup: /system.slice/cups.service
└─6734 /usr/sbin/cupsd -l
Mar 08 14:50:47 xxx.yyy.local systemd[1]: Starting CUPS Scheduler...
Mar 08 14:50:47 xxx.yyy.local systemd[1]: Started CUPS Scheduler.
>
> what about
>
> * journalctl -u cups.service -xe*
-- Logs begin at Sun 2018-03-11 23:46:44 PDT, end at Fri 2019-03-08
18:23:42 PST
. --
Apr 24 09:48:07 xxx.yyy.local systemd[1]: Stopping CUPS Scheduler...
-- Subject: Unit cups.service has begun shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit cups.service has begun shutting down.
Apr 24 09:48:07 xxx.yyy.local systemd[1]: Stopped CUPS Scheduler.
-- Subject: Unit cups.service has finished shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit cups.service has finished shutting down.
-- Reboot --
Apr 24 17:45:56 xxx.yyy.local systemd[1]: Starting CUPS Scheduler...
-- Subject: Unit cups.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
# date
Fri Mar 8 18:25:58 PST 2019
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
<mailto:users@xxxxxxxxxxxxxxxxxxxxxxx>
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
<mailto:users-leave@xxxxxxxxxxxxxxxxxxxxxxx>
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
