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
*systemctl status cups.service* sez ??
what about
* journalctl -u cups.service -xe*
On Fri, Mar 8, 2019 at 2:55 PM ToddAndMargo via users < users@lists.fedoraproject.org> 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 _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
On Fri, Mar 8, 2019 at 2:55 PM ToddAndMargo via users <users@lists.fedoraproject.org mailto:users@lists.fedoraproject.org> 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
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?
On Fri, Mar 8, 2019 at 6:28 PM ToddAndMargo via users < users@lists.fedoraproject.org> wrote:
On Fri, Mar 8, 2019 at 2:55 PM ToddAndMargo via users <users@lists.fedoraproject.org mailto:users@lists.fedoraproject.org> 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@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
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@lists.fedoraproject.org mailto:users@lists.fedoraproject.org> wrote:
>> On Fri, Mar 8, 2019 at 2:55 PM ToddAndMargo via users >> <users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> <mailto:users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org>>> >> 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@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> To unsubscribe send an email to users-leave@lists.fedoraproject.org <mailto:users-leave@lists.fedoraproject.org> 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@lists.fedoraproject.org
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
naturally, you reviewed the following, what did it reveal?
https://fedoraproject.org/wiki/How_to_debug_printing_problems
On Fri, Mar 8, 2019 at 7:08 PM ToddAndMargo via users < users@lists.fedoraproject.org> wrote:
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@lists.fedoraproject.org mailto:users@lists.fedoraproject.org> wrote:
>> On Fri, Mar 8, 2019 at 2:55 PM ToddAndMargo via users >> <users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> <mailto:users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org>>> >> 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@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> To unsubscribe send an email to users-leave@lists.fedoraproject.org <mailto:users-leave@lists.fedoraproject.org> 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@lists.fedoraproject.org
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
--
Computers are like air conditioners. They malfunction when you open windows
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
probly should also kick log level up & restart service until you get this sorted, ...
*LogLevel *debug2
On Fri, Mar 8, 2019 at 7:12 PM Jack Craig jack.craig.aptos@gmail.com wrote:
naturally, you reviewed the following, what did it reveal?
https://fedoraproject.org/wiki/How_to_debug_printing_problems
On Fri, Mar 8, 2019 at 7:08 PM ToddAndMargo via users < users@lists.fedoraproject.org> wrote:
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,
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@lists.fedoraproject.org mailto:users@lists.fedoraproject.org> wrote:
>> On Fri, Mar 8, 2019 at 2:55 PM ToddAndMargo via users >> <users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> <mailto:users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org>>> >> 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@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> To unsubscribe send an email to users-leave@lists.fedoraproject.org <mailto:users-leave@lists.fedoraproject.org> 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@lists.fedoraproject.org
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
--
Computers are like air conditioners. They malfunction when you open windows
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
On 3/8/19 7:12 PM, Jack Craig wrote:
naturally, you reviewed the following, what did it reveal?
https://fedoraproject.org/wiki/How_to_debug_printing_problems
I am looking at it now.
CUPS-PDF works
On 3/8/19 7:27 PM, ToddAndMargo via users wrote:
On 3/8/19 7:12 PM, Jack Craig wrote:
naturally, you reviewed the following, what did it reveal?
https://fedoraproject.org/wiki/How_to_debug_printing_problems
I am looking at it now.
CUPS-PDF works
A new laser jet iiP did not work
On 3/8/19 7:30 PM, ToddAndMargo via users wrote:
On 3/8/19 7:27 PM, ToddAndMargo via users wrote:
On 3/8/19 7:12 PM, Jack Craig wrote:
naturally, you reviewed the following, what did it reveal?
https://fedoraproject.org/wiki/How_to_debug_printing_problems
I am looking at it now.
CUPS-PDF works
A new laser jet iiP did not work
sending a text file with lpr gave "printer busy" in CUps admin
On 3/9/19 11:33 AM, ToddAndMargo via users wrote:
On 3/8/19 7:30 PM, ToddAndMargo via users wrote:
On 3/8/19 7:27 PM, ToddAndMargo via users wrote:
On 3/8/19 7:12 PM, Jack Craig wrote:
naturally, you reviewed the following, what did it reveal?
https://fedoraproject.org/wiki/How_to_debug_printing_problems
I am looking at it now.
CUPS-PDF works
A new laser jet iiP did not work
sending a text file with lpr gave "printer busy" in CUps admin
Anything in /var/log/cups/error_log or any of the others?
On 3/8/19 7:40 PM, Ed Greshko wrote:
On 3/9/19 11:33 AM, ToddAndMargo via users wrote:
On 3/8/19 7:30 PM, ToddAndMargo via users wrote:
On 3/8/19 7:27 PM, ToddAndMargo via users wrote:
On 3/8/19 7:12 PM, Jack Craig wrote:
naturally, you reviewed the following, what did it reveal?
https://fedoraproject.org/wiki/How_to_debug_printing_problems
I am looking at it now.
CUPS-PDF works
A new laser jet iiP did not work
sending a text file with lpr gave "printer busy" in CUps admin
Anything in /var/log/cups/error_log or any of the others?
Figured out where the problem lies: the upgrade knocked out 'parallel:/dev/lp0". My printer also work (like crap) on a USB port. And I am able to print through USB.
parallel:/dev/lp0 does not even show up on my list of ports in CUPS admin anymore.
Now how to fix?
On 3/9/19 11:33 AM, ToddAndMargo via users wrote:
On 3/8/19 7:30 PM, ToddAndMargo via users wrote:
On 3/8/19 7:27 PM, ToddAndMargo via users wrote:
On 3/8/19 7:12 PM, Jack Craig wrote:
naturally, you reviewed the following, what did it reveal?
https://fedoraproject.org/wiki/How_to_debug_printing_problems
I am looking at it now.
CUPS-PDF works
A new laser jet iiP did not work
sending a text file with lpr gave "printer busy" in CUps admin
Oh, never mind my last question. I forgot they moved those all to journal.
On 3/8/19 2:55 PM, ToddAndMargo via users 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
I just ran my upgrades on my boot stick and now it has the problem too.
:'(
On 3/9/19 10:48 AM, ToddAndMargo via users wrote:
I just ran my upgrades on my boot stick and now it has the problem too.
When you updated, did you only update the cups stuff or other things as well?
If other things were updated, have you considered doing
dnf downgrade cups*
to verify that it is indeed a cups issue and not something else?
On 3/9/19 3:22 AM, Ed Greshko wrote:
On 3/9/19 10:48 AM, ToddAndMargo via users wrote:
I just ran my upgrades on my boot stick and now it has the problem too.
When you updated, did you only update the cups stuff or other things as well?
If other things were updated, have you considered doing
dnf downgrade cups*
to verify that it is indeed a cups issue and not something else?
yup. no symptom change
On 3/9/19 7:32 PM, ToddAndMargo via users wrote:
On 3/9/19 3:22 AM, Ed Greshko wrote:
On 3/9/19 10:48 AM, ToddAndMargo via users wrote:
I just ran my upgrades on my boot stick and now it has the problem too.
When you updated, did you only update the cups stuff or other things as well?
If other things were updated, have you considered doing
dnf downgrade cups*
to verify that it is indeed a cups issue and not something else?
yup. no symptom change
Sorry, I'm not quite understanding what you mean?
Was more than cups updated?
And, you did downgrade cups and still have issues? After rebooting?
On 3/9/19 3:37 AM, Ed Greshko wrote:
On 3/9/19 7:32 PM, ToddAndMargo via users wrote:
On 3/9/19 3:22 AM, Ed Greshko wrote:
On 3/9/19 10:48 AM, ToddAndMargo via users wrote:
I just ran my upgrades on my boot stick and now it has the problem too.
When you updated, did you only update the cups stuff or other things as well?
If other things were updated, have you considered doing
dnf downgrade cups*
to verify that it is indeed a cups issue and not something else?
yup. no symptom change
Sorry, I'm not quite understanding what you mean?
lp0 still busy
Was more than cups updated?
And, you did downgrade cups and still have issues? After rebooting?
I typically did a restart on cups, but I did it again with a reboot. No symptom change. lp0 still busy
On 3/9/19 7:57 PM, ToddAndMargo via users wrote:
I typically did a restart on cups, but I did it again with a reboot. No symptom change. lp0 still busy
So, with cups packages downgraded to 2.2.8-5 it still is broken?
Again, did the update update other things as well?
If you've downgraded and it still fails, then maybe cups isn't to blame?
If you've also updated the kernel at the same time, have you tried booting to an earlier one?
On 3/9/19 4:02 AM, Ed Greshko wrote:
On 3/9/19 7:57 PM, ToddAndMargo via users wrote:
I typically did a restart on cups, but I did it again with a reboot. No symptom change. lp0 still busy
So, with cups packages downgraded to 2.2.8-5 it still is broken?
Yes. I don't think it is cups doing
Again, did the update update other things as well?
about 500 MB of stuff.
If you've downgraded and it still fails, then maybe cups isn't to blame?
My thoughts as well
If you've also updated the kernel at the same time, have you tried booting to an earlier one?
tried three different kernels
On Sat, Mar 9, 2019, 21:01 ToddAndMargo via users < users@lists.fedoraproject.org> wrote:
On 3/9/19 4:02 AM, Ed Greshko wrote:
On 3/9/19 7:57 PM, ToddAndMargo via users wrote:
I typically did a restart on cups, but I did it again with a reboot. No symptom change. lp0 still busy
So, with cups packages downgraded to 2.2.8-5 it still is broken?
Yes. I don't think it is cups doing
Again, did the update update other things as well?
about 500 MB of stuff.
If you've downgraded and it still fails, then maybe cups isn't to blame?
My thoughts as well
If you've also updated the kernel at the same time, have you tried
booting to an earlier one?
tried three different kernels
You may have to get a list from dnf history and start selectively downgrading.
this may be foolish, but have you swapped out cable & printer to rule them out?
On Sat, Mar 9, 2019 at 4:10 PM Ed Greshko ed.greshko@greshko.com wrote:
On Sat, Mar 9, 2019, 21:01 ToddAndMargo via users < users@lists.fedoraproject.org> wrote:
On 3/9/19 4:02 AM, Ed Greshko wrote:
On 3/9/19 7:57 PM, ToddAndMargo via users wrote:
I typically did a restart on cups, but I did it again with a reboot. No symptom change. lp0 still busy
So, with cups packages downgraded to 2.2.8-5 it still is broken?
Yes. I don't think it is cups doing
Again, did the update update other things as well?
about 500 MB of stuff.
If you've downgraded and it still fails, then maybe cups isn't to blame?
My thoughts as well
If you've also updated the kernel at the same time, have you tried
booting to an earlier one?
tried three different kernels
You may have to get a list from dnf history and start selectively downgrading.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
On 3/9/19 4:49 PM, Jack Craig wrote:
this may be foolish, but have you swapped out cable & printer to rule them out?
Hi Jack,
I booted of a Flash a drive I have Fedora 29 installed on. The printer printed perfectly over lp0.
Then whilst still being booted into the flash drive, I did my updates, which I had ignored for a long time. After that the flash drive would not print either and with the same symptom.
And yes, before that, I did check the cables. They were attached very securely. Life should be so easy.
And the printer does print off its USB interface, but it is one of those old printers where the USB was done really poorly and it can get through printing an single invoice. And I need to get my billing out so as I can put food on the table.
Something is buggering up lp0. I doubt it is CUPS either.
-T
you looked at this link? https://fedoraproject.org/wiki/How_to_debug_printing_problems#Which_driver_a...
ok, so i had a recent network printer problem. i would ctrl p, fill in parm & print. the job simply evaporated!
i traced it to a munch filter path name, but didnt use the above link & wish i had...
what do you have in ...
*ls -l /etc/cups/ppd*
*??*
On Sat, Mar 9, 2019 at 5:15 PM ToddAndMargo via users < users@lists.fedoraproject.org> wrote:
On 3/9/19 4:49 PM, Jack Craig wrote:
this may be foolish, but have you swapped out cable & printer to rule them out?
Hi Jack,
I booted of a Flash a drive I have Fedora 29 installed on. The printer printed perfectly over lp0.
Then whilst still being booted into the flash drive, I did my updates, which I had ignored for a long time. After that the flash drive would not print either and with the same symptom.
And yes, before that, I did check the cables. They were attached very securely. Life should be so easy.
And the printer does print off its USB interface, but it is one of those old printers where the USB was done really poorly and it can get through printing an single invoice. And I need to get my billing out so as I can put food on the table.
Something is buggering up lp0. I doubt it is CUPS either.
-T
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
On Sat, Mar 9, 2019 at 5:15 PM ToddAndMargo via users <users@lists.fedoraproject.org mailto:users@lists.fedoraproject.org> wrote:
On 3/9/19 4:49 PM, Jack Craig wrote: > this may be foolish, but have you swapped out cable & printer to rule > them out? Hi Jack, I booted of a Flash a drive I have Fedora 29 installed on. The printer printed perfectly over lp0. Then whilst still being booted into the flash drive, I did my updates, which I had ignored for a long time. After that the flash drive would not print either and with the same symptom. And yes, before that, I did check the cables. They were attached very securely. Life should be so easy. And the printer does print off its USB interface, but it is one of those old printers where the USB was done really poorly and it can get through printing an single invoice. And I need to get my billing out so as I can put food on the table. Something is buggering up lp0. I doubt it is CUPS either.
On 3/9/19 11:57 PM, Jack Craig wrote:
you looked at this link? https://fedoraproject.org/wiki/How_to_debug_printing_problems#Which_driver_a...
ok, so i had a recent network printer problem. i would ctrl p, fill in parm & print. the job simply evaporated!
i traced it to a munch filter path name, but didnt use the above link & wish i had...
what do you have in ... *ls -l /etc/cups/ppd*
*??*
Hi Jack,
CUPS is not causing it. I can NOT write directly to the port:
# echo -ne abc \f > /dev/lp0 bash: /dev/lp0: Device or resource busy
# lsof | grep lp0 parallel 14949 lp 5w CHR 6,0 0t0 26621 /dev/lp0
# kill -9 14949
# echo -ne abc \f > /dev/lp0 ^C bash: history: write error: Success
# lsof | grep lp0 <nothing>
Note that the redirect to lp0 hanged and had to be <ctrl><C>'ed. And then it said success. Hmmmm...
-T
*/etc/cups/ppd/Epson-WP-4530.ppd.orig: *cupsFilter: "application/vnd.cups-raster 0 /opt/epson-inkjet-printer-escpr/cups/lib/filter/epson-escpr-wrapper"*
so, my problem was a munged path in this file, instead of a coherent path, the middle of the /opt/epson-.../path corrupted. fixed the path, restarted cups and voila.
did you try making cups logging more verbose?
On Sat, Mar 9, 2019 at 5:15 PM ToddAndMargo via users < users@lists.fedoraproject.org> wrote:
On 3/9/19 4:49 PM, Jack Craig wrote:
this may be foolish, but have you swapped out cable & printer to rule them out?
Hi Jack,
I booted of a Flash a drive I have Fedora 29 installed on. The printer printed perfectly over lp0.
Then whilst still being booted into the flash drive, I did my updates, which I had ignored for a long time. After that the flash drive would not print either and with the same symptom.
And yes, before that, I did check the cables. They were attached very securely. Life should be so easy.
And the printer does print off its USB interface, but it is one of those old printers where the USB was done really poorly and it can get through printing an single invoice. And I need to get my billing out so as I can put food on the table.
Something is buggering up lp0. I doubt it is CUPS either.
-T
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
On Sun, 10 Mar 2019 at 01:16, ToddAndMargo via users users@lists.fedoraproject.org wrote:
On 3/9/19 4:09 PM, Ed Greshko wrote:
You may have to get a list from dnf history and start selectively downgrading.
That may be what I have to ultimately do.
May I be a mooch and ask what the history command is?
sudo dnf history
Did the upgrades break without a restart? I'm wondering if you've updated the kernel and that has the issue. If so you should be able to select the previous kernel on boot.
On 3/9/19 5:22 PM, Anthony F McInerney wrote:
May I be a mooch and ask what the history command is?
sudo dnf history
That was easy. Thank you!
Did the upgrades break without a restart?
On my main machine, no idea. I only print doing bill paying, banking, and invoices, which is twice a week. I completely power off (outlet strip) every night.
On the bootable flash drive, it happened immediately.
I'm wondering if you've updated the kernel and that has the issue. If so you should be able to select the previous kernel on boot.
The prior two kernels show the same problem. And after doing a dnf downgrade on the kernel, I am defaulting to the previous kernel now anyway.
I noticed that lsof does not show anything attached to it until the first print attempts to go through.
Something is buggering up lp0.
On 3/10/19 9:15 AM, ToddAndMargo via users wrote:
On 3/9/19 4:09 PM, Ed Greshko wrote:
You may have to get a list from dnf history and start selectively downgrading.
That may be what I have to ultimately do.
May I be a mooch and ask what the history command is?
Sure...
This needs to be done a root.
dnf history gives you a list of all dnf transactions.
You can then do a "dnf history info ID" where ID is the most recent transaction. It will show you a list of what was done.
On 3/9/19 5:27 PM, Ed Greshko wrote:
On 3/10/19 9:15 AM, ToddAndMargo via users wrote:
On 3/9/19 4:09 PM, Ed Greshko wrote:
You may have to get a list from dnf history and start selectively downgrading.
That may be what I have to ultimately do.
May I be a mooch and ask what the history command is?
Sure...
This needs to be done a root.
dnf history gives you a list of all dnf transactions.
You can then do a "dnf history info ID" where ID is the most recent transaction. It will show you a list of what was done.
Thank you!
On 3/8/19 2:55 PM, ToddAndMargo via users 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
Fresh reboot: # lsof | grep lp0 <nothing>
After sending a CUPS test print # lsof | grep lp0 parallel 11981 lp 5w CHR 6,0 0t0 26621 /dev/lp0
After removing the CUPS test print # lsof | grep lp0 parallel 11981 lp 5w CHR 6,0 0t0 26621 /dev/lp0
# kill -9 11981 # lsof | grep lp0
So is "parallel" the culprit?
On 3/10/19 9:57 AM, ToddAndMargo via users wrote:
On 3/8/19 2:55 PM, ToddAndMargo via users 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
Fresh reboot: # lsof | grep lp0
<nothing>
After sending a CUPS test print # lsof | grep lp0 parallel 11981 lp 5w CHR 6,0 0t0 26621 /dev/lp0
After removing the CUPS test print # lsof | grep lp0 parallel 11981 lp 5w CHR 6,0 0t0 26621 /dev/lp0
# kill -9 11981 # lsof | grep lp0
So is "parallel" the culprit?
lsof -p 11981 and what is PID 11981 running
On 3/9/19 6:04 PM, Ed Greshko wrote:
On 3/10/19 9:57 AM, ToddAndMargo via users wrote:
On 3/8/19 2:55 PM, ToddAndMargo via users 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
Fresh reboot: # lsof | grep lp0
<nothing>
After sending a CUPS test print # lsof | grep lp0 parallel 11981 lp 5w CHR 6,0 0t0 26621 /dev/lp0
After removing the CUPS test print # lsof | grep lp0 parallel 11981 lp 5w CHR 6,0 0t0 26621 /dev/lp0
# kill -9 11981 # lsof | grep lp0
So is "parallel" the culprit?
lsof -p 11981 and what is PID 11981 running
Fired up another test print, got a new pid for parallel
# lsof | grep lp0 parallel 12803 lp 5w CHR 6,0 0t0 26621 /dev/lp0
# ps ax | grep 12803 12803 ? S 0:00 parallel:/dev/lp0 894 anonymous Test Page 1 job-uuid=urn:uuid:074c6a6a-836c-3b6b-77f7-17df15686f34 job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1552185108 time-at-processing=1552185108 12837 pts/1 S+ 0:00 grep --color=auto 12803
On 3/9/19 6:33 PM, ToddAndMargo via users wrote:
On 3/9/19 6:04 PM, Ed Greshko wrote:
On 3/10/19 9:57 AM, ToddAndMargo via users wrote:
On 3/8/19 2:55 PM, ToddAndMargo via users 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
Fresh reboot: # lsof | grep lp0
<nothing>
After sending a CUPS test print # lsof | grep lp0 parallel 11981 lp 5w CHR 6,0 0t0 26621 /dev/lp0
After removing the CUPS test print # lsof | grep lp0 parallel 11981 lp 5w CHR 6,0 0t0 26621 /dev/lp0
# kill -9 11981 # lsof | grep lp0
So is "parallel" the culprit?
lsof -p 11981 and what is PID 11981 running
Fired up another test print, got a new pid for parallel
# lsof | grep lp0 parallel 12803 lp 5w CHR 6,0 0t0 26621 /dev/lp0
# ps ax | grep 12803 12803 ? S 0:00 parallel:/dev/lp0 894 anonymous Test Page 1 job-uuid=urn:uuid:074c6a6a-836c-3b6b-77f7-17df15686f34 job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1552185108 time-at-processing=1552185108 12837 pts/1 S+ 0:00 grep --color=auto 12803
I take it this is not the same parallel?
# dnf provides parallel parallel-20180322-2.fc29.noarch : Shell tool for executing jobs in parallel Repo : fedora Matched from: Provide : parallel = 20180322-2.fc29
On 3/10/19 10:33 AM, ToddAndMargo via users wrote:
Fired up another test print, got a new pid for parallel
# lsof | grep lp0 parallel 12803 lp 5w CHR 6,0 0t0 26621 /dev/lp0
# ps ax | grep 12803 12803 ? S 0:00 parallel:/dev/lp0 894 anonymous Test Page 1 job-uuid=urn:uuid:074c6a6a-836c-3b6b-77f7-17df15686f34 job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1552185108 time-at-processing=1552185108 12837 pts/1 S+ 0:00 grep --color=auto 12803
parallel:/dev/lp0 is the URI of the printer, I believe.
It seems to be in S state or "interruptible sleep (waiting for an event to complete)"
I'm reinstalling a VM with a Parallel Port and it shows in http://localhost:631 when adding a printer.
I'll see what happens after install and update.
On 3/10/19 12:31 PM, Ed Greshko wrote:
On 3/10/19 10:33 AM, ToddAndMargo via users wrote:
Fired up another test print, got a new pid for parallel
# lsof | grep lp0 parallel 12803 lp 5w CHR 6,0 0t0 26621 /dev/lp0
# ps ax | grep 12803 12803 ? S 0:00 parallel:/dev/lp0 894 anonymous Test Page 1 job-uuid=urn:uuid:074c6a6a-836c-3b6b-77f7-17df15686f34 job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1552185108 time-at-processing=1552185108 12837 pts/1 S+ 0:00 grep --color=auto 12803
parallel:/dev/lp0 is the URI of the printer, I believe.
It seems to be in S state or "interruptible sleep (waiting for an event to complete)"
I'm reinstalling a VM with a Parallel Port and it shows in http://localhost:631 when adding a printer.
I'll see what happens after install and update.
Well, I installed an F29 system and everything seems OK before and after updates.
My Cups interface looks like this when adding a printer.
https://drive.google.com/file/d/1vZpkSqEQHmC4kZqWeurr9kxTvz8TH1Ul/view?usp=s...
But, if I remove the Parallel Port from the VM's hardware then the LPT #1 line is absent.
This seems to be saying that for some reason your HW isn't being detected.
But I can't replicate your issue.
On 3/9/19 9:16 PM, Ed Greshko wrote:
On 3/10/19 12:31 PM, Ed Greshko wrote:
On 3/10/19 10:33 AM, ToddAndMargo via users wrote:
Fired up another test print, got a new pid for parallel
# lsof | grep lp0 parallel 12803 lp 5w CHR 6,0 0t0 26621 /dev/lp0
# ps ax | grep 12803 12803 ? S 0:00 parallel:/dev/lp0 894 anonymous Test Page 1 job-uuid=urn:uuid:074c6a6a-836c-3b6b-77f7-17df15686f34 job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1552185108 time-at-processing=1552185108 12837 pts/1 S+ 0:00 grep --color=auto 12803
parallel:/dev/lp0 is the URI of the printer, I believe.
It seems to be in S state or "interruptible sleep (waiting for an event to complete)"
I'm reinstalling a VM with a Parallel Port and it shows in http://localhost:631 when adding a printer.
I'll see what happens after install and update.
Well, I installed an F29 system and everything seems OK before and after updates.
My Cups interface looks like this when adding a printer.
https://drive.google.com/file/d/1vZpkSqEQHmC4kZqWeurr9kxTvz8TH1Ul/view?usp=s...
But, if I remove the Parallel Port from the VM's hardware then the LPT #1 line is absent.
This seems to be saying that for some reason your HW isn't being detected.
But I can't replicate your issue.
In my qemu-kvm VM of Fedora 29, that has not been updates in ages, I added LPT1 (their name for lp0) and created a printer to it. Still didn't print. And, dang!, the job showed up in the host's CUPS. I was hoping to write around CUPS.
On 3/10/19 1:28 PM, ToddAndMargo via users wrote:
In my qemu-kvm VM of Fedora 29, that has not been updates in ages, I added LPT1 (their name for lp0) and created a printer to it. Still didn't print. And, dang!, the job showed up in the host's CUPS. I was hoping to write around CUPS.
Install "lshw" and run it as root.
You should find the device with the driver configured to be parport_pc.
On 3/9/19 9:37 PM, Ed Greshko wrote:
On 3/10/19 1:28 PM, ToddAndMargo via users wrote:
In my qemu-kvm VM of Fedora 29, that has not been updates in ages, I added LPT1 (their name for lp0) and created a printer to it. Still didn't print. And, dang!, the job showed up in the host's CUPS. I was hoping to write around CUPS.
Install "lshw" and run it as root.
You should find the device with the driver configured to be parport_pc.
Already installed. Does this tell you anything?
*-pci:0 description: PCI bridge product: 100 Series/C230 Series Chipset Family PCI Express Root Port #1 vendor: Intel Corporation physical id: 1c bus info: pci@0000:00:1c.0 version: f1 width: 32 bits clock: 33MHz capabilities: pci pciexpress msi pm normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:16 ioport:e000(size=4096) memory:ac000000-da0fffff ioport:60000000(size=1241513984) *-communication description: Parallel controller product: Oxford Semiconductor Ltd vendor: Oxford Semiconductor Ltd physical id: 0 bus info: pci@0000:01:00.0 version: 00 width: 32 bits clock: 33MHz capabilities: pm msi pciexpress ecp cap_list configuration: driver=parport_pc latency=0 resources: irq:16 ioport:e010(size=8) ioport:e000(size=4)
On 3/10/19 1:59 PM, ToddAndMargo via users wrote:
Already installed. Does this tell you anything?
*-pci:0 description: PCI bridge product: 100 Series/C230 Series Chipset Family PCI Express Root Port #1 vendor: Intel Corporation physical id: 1c bus info: pci@0000:00:1c.0 version: f1 width: 32 bits clock: 33MHz capabilities: pci pciexpress msi pm normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:16 ioport:e000(size=4096) memory:ac000000-da0fffff ioport:60000000(size=1241513984) *-communication description: Parallel controller product: Oxford Semiconductor Ltd vendor: Oxford Semiconductor Ltd physical id: 0 bus info: pci@0000:01:00.0 version: 00 width: 32 bits clock: 33MHz capabilities: pm msi pciexpress ecp cap_list configuration: driver=parport_pc latency=0 resources: irq:16 ioport:e010(size=8) ioport:e000(size=4)
Not really. Seems the HW is there. One thing you can try is to create a parport.conf in /etc/modprobe.d containing:
alias parport_lowlevel parport_pc options parport_pc io=0xe010,0xe000 irq=16,auto
Other than that, I'm out of ideas. :-(
On 3/9/19 10:55 PM, Ed Greshko wrote:
Not really. Seems the HW is there. One thing you can try is to create a parport.conf in /etc/modprobe.d containing:
alias parport_lowlevel parport_pc options parport_pc io=0xe010,0xe000 irq=16,auto
Other than that, I'm out of ideas.:-(
Didn't help. Rats! Thank you anyway.
I just opened
On 3/8/19 2:55 PM, ToddAndMargo via users 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
Hi All,
Figured it out.
AHHHHHH [expletive deleted] !!!!
It turns out that I have an "INTERMITTENT" parallel port add on card (Star Tech PEX1P). I would poop out when booted normally, but work when booted from a live USB, UNTIL IT DIDN'T. Took me FOREVER to figure out what was going on.
I have a new card on the way.
Much appreciation for all the help and tips.
-T
Excuse me for top posting but HAHA, HAHA. 😁
On Mon, Mar 11, 2019, 19:00 ToddAndMargo via users < users@lists.fedoraproject.org> wrote:
On 3/8/19 2:55 PM, ToddAndMargo via users 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
Hi All,
Figured it out.
AHHHHHH [expletive deleted] !!!!
It turns out that I have an "INTERMITTENT" parallel port add on card (Star Tech PEX1P). I would poop out when booted normally, but work when booted from a live USB, UNTIL IT DIDN'T. Took me FOREVER to figure out what was going on.
I have a new card on the way.
Much appreciation for all the help and tips.
-T
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org
On 3/11/19 3:59 AM, ToddAndMargo via users wrote:
On 3/8/19 2:55 PM, ToddAndMargo via users 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
Hi All,
Figured it out.
AHHHHHH [expletive deleted] !!!!
It turns out that I have an "INTERMITTENT" parallel port add on card (Star Tech PEX1P). I would poop out when booted normally, but work when booted from a live USB, UNTIL IT DIDN'T. Took me FOREVER to figure out what was going on.
I have a new card on the way.
Much appreciation for all the help and tips.
-T
Parallel card replaced. Happy camping restored!