Hi, guys, My problem is exasperating... I have a canon mf624cw on my network. It has been there for a couple of years and worked well. when I started to work on my tax stuff, downloads etc. it refused to print. I powered down the router and repowered it. This usually worked because I have MANY systems on my home router wirelessly (about 15 at any one time), so occasionally it loses its little bitty mind. Not ofter, maybe once every 4 or 5 months. Now given that this didn't bring the printer up, I then did a ping and the printer responded. Lpq shows the printer not accepting jobs. Brought up settings, and attempted to delete the printer. NO JOY. I would unlock, authorize, delete the printer, close the notification window, close the printer window and settings, reboot just to make sure the settings took, and bring the system back up. The printer was still there. Answered pings etc. OK, maybe the printer has an issue. Powered down the printer, left it over night, reset it and got the network up on it, confirmed I could ping it, but still no printing. OK, maybe the driver or the que is messed up. Again tried to delte the printer while it was off. No joy. Went to Google, but it was not my friend in this case. So after three days of this, I am surrendering to the greaterwisdom. System is AMD FX 8300 at 2.8Ghz, 15.6GiB memory, AMD Oland, Gnome 3.28.2 64bit, lots of disk space. Just updated by dnf. dmesg doesen't show any problems journalctl doesn't show my any printer stuff. Printer shows no errors. printer shows network and can be pinged.
What I think I need is to remove all system references to the printer. I have tried grep on the /etc directory and sub directories, but no joy on locating the entries for the printer. HELPPPP!! If anyone can tell me all the locations where the printer is referenced and how to remove the references, I will probably be able to bumble my way out of this. Or any other suggestions that might work. Remember I have tried the gui from settings, and the cups 631 network page but with no joy on either. If you think I need to try any of those again, please post step by step so I can be sure I do what you say exactly.
Regards, Les H
On 2/15/19 2:11 PM, Howard Howell wrote:
If anyone can tell me all the locations where the printer is referenced and how to remove the references, I will probably be able to bumble my way out of this. Or any other suggestions that might work.
If you look at the printer properties, what is the Device URI? Maybe it's an MDNS discovered printer.
Sorry for the late reply. I was caught up in the AT&T massive slow down which made my service unusable... Where do I look to find the URI? All these unique whatchamacallits don't seem to do much for the systems. Maybe they help with large systems in server farms, but on a personal system it is pretty impersonal.
Anyway, despite the URI issue, the printer had worked on F28 and ubuntu before. I can ping it and the printers menues show it as up.
And I just went to settings-devices-printers and tried to unlock and look at printer details and my system logged me off for some reason. Another symptom?
Regards, Les H On Fri, 2019-02-15 at 16:39 -0800, Samuel Sieb wrote:
On 2/15/19 2:11 PM, Howard Howell wrote:
If anyone can tell me all the locations where the printer is referenced and how to remove the references, I will probably be able to bumble my way out of this. Or any other suggestions that might work.
If you look at the printer properties, what is the Device URI? Maybe it's an MDNS discovered printer. _______________________________________________ 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 2/19/19 8:53 AM, Howard Howell wrote:
And I just went to settings-devices-printers and tried to unlock and look at printer details and my system logged me off for some reason. Another symptom?
That does sound like you have a larger issue. Did you check the journal to see if there is any message about the crash?
The gnome-settings printer panel does not show enough information. Install system-config-printer, that will be more useful. It shows up as "Print Settings" in Activities. If you open your printer there, the Device URI will be in the middle.
On Tue, 2019-02-19 at 09:20 -0800, Samuel Sieb wrote:
On 2/19/19 8:53 AM, Howard Howell wrote:
And I just went to settings-devices-printers and tried to unlock and look at printer details and my system logged me off for some reason. Another symptom?
That does sound like you have a larger issue. Did you check the journal to see if there is any message about the crash?
The gnome-settings printer panel does not show enough information. Install system-config-printer, that will be more useful. It shows up as "Print Settings" in Activities. If you open your printer there, the Device URI will be in the middle.C
That shows "There are no printers configured yet."
going back to settings it shows two versions of Canon MF620C.
I have other webpages up I don't want to lose right now, so I'll forego the cups 631 page for now unless you need to see what that shows.
journalctl shows hundreds of lines of: Feb 19 09:45:49 school dbus-daemon[8303]: [session uid=1000 pid=8303] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract' Feb 19 09:45:49 school systemd[8280]: Started Tracker metadata extractor.
Only a few lines relating to the printer:
Feb 19 09:34:35 school gnome-software[8837]: failed to rescan: Failed to parse /usr/share/applications/system-config-printer.desktop file: cannot process file of type application/x-desktop Feb 19 09:34:35 school gnome-software[8837]: failed to rescan: No valid root node specified Feb 19 09:34:48 school audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? term>
And periodically this shows up: Feb 19 09:35:09 school cupsd[1010]: REQUEST localhost - - "POST / HTTP/1.1" 200 152 Cancel-Subscription successful-ok Feb 19 09:35:09 school gnome-shell[8377]: Object Meta.WindowActor (0x55bfa0f3b340), has been already finalized. Impossible to get any property from it. Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: == Stack trace for context 0x55bf9ef3e340 == Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #0 0x55bf9f382610 i resource:///org/gnome/shell/ui/tweener.js:73 (0x7fa9d86c8cd0 @ 9) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #1 0x55bf9f382590 i resource:///org/gnome/shell/ui/tweener.js:105 (0x7fa9d86c8f78 @ 36) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #2 0x55bf9f382508 i resource:///org/gnome/shell/ui/tweener.js:92 (0x7fa9d86c8de0 @ 52) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #3 0x7fff70e1f1f0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7fa9d86d2918 @ 54) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #4 0x7fff70e1fa80 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7fa9d86d29a0 @ 1626) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #5 0x7fff70e1fb30 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7fa9d86d2a28 @ 100) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #6 0x55bf9f382490 i resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fa9d86d2ab0 @ 10) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #7 0x7fff70e20e80 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7fa9d86cff78 @ 386) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #8 0x55bf9f382400 i resource:///org/gnome/shell/ui/tweener.js:207 (0x7fa9d86cf5e8 @ 159) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #9 0x7fff70e221b0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fa9d86b5de0 @ 71) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #10 0x55bf9f382380 i resource:///org/gnome/shell/ui/tweener.js:182 (0x7fa9d86cf560 @ 15) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: == Stack trace for context 0x55bf9ef3e340 == Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #0 0x55bf9f382610 i resource:///org/gnome/shell/ui/tweener.js:80 (0x7fa9d86c8cd0 @ 82) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #1 0x55bf9f382590 i resource:///org/gnome/shell/ui/tweener.js:105 (0x7fa9d86c8f78 @ 36) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #2 0x55bf9f382508 i resource:///org/gnome/shell/ui/tweener.js:92 (0x7fa9d86c8de0 @ 52) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #3 0x7fff70e1f1f0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7fa9d86d2918 @ 54) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #4 0x7fff70e1fa80 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7fa9d86d29a0 @ 1626) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #5 0x7fff70e1fb30 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7fa9d86d2a28 @ 100) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #6 0x55bf9f382490 i resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fa9d86d2ab0 @ 10) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #7 0x7fff70e20e80 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7fa9d86cff78 @ 386) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #8 0x55bf9f382400 i resource:///org/gnome/shell/ui/tweener.js:207 (0x7fa9d86cf5e8 @ 159) Feb 19 09:35:09 school gnome-shell[8377]: Object Meta.WindowActor (0x55bfa0f3b340), has been already finalized. Impossible to set any property to it. Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #9 0x7fff70e221b0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fa9d86b5de0 @ 71) Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: #10 0x55bf9f382380 i resource:///org/gnome/shell/ui/tweener.js:182 (0x7fa9d86cf560 @ 15) Feb 19 09:35:10 school gnome-shell[8377]: Object St.Widget (0x55bfa159e550), has been already finalized. Impossible to get any property from it. Feb 19 09:35:10 school gnome-shell[8377]: Object St.Widget (0x55bfa159e550), has been already finalized. Impossible to set any property to it. Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: == Stack trace for context 0x55bf9ef3e340 == Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #0 0x55bf9f3826b0 i resource:///org/gnome/shell/ui/tweener.js:73 (0x7fa9d86c8cd0 @ 9) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #1 0x55bf9f382630 i resource:///org/gnome/shell/ui/tweener.js:105 (0x7fa9d86c8f78 @ 36) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #2 0x55bf9f3825a8 i resource:///org/gnome/shell/ui/tweener.js:92 (0x7fa9d86c8de0 @ 52) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #3 0x55bf9f382508 i resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7fa9d86d2918 @ 54) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #4 0x7fff70e20200 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7fa9d86d29a0 @ 1626) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #5 0x7fff70e202b0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7fa9d86d2a28 @ 100) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #6 0x55bf9f382490 i resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fa9d86d2ab0 @ 10) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #7 0x7fff70e21600 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7fa9d86cff78 @ 386) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #8 0x55bf9f382400 i resource:///org/gnome/shell/ui/tweener.js:207 (0x7fa9d86cf5e8 @ 159) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #9 0x7fff70e22220 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fa9d86b5de0 @ 71) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #10 0x55bf9f382380 i resource:///org/gnome/shell/ui/tweener.js:182 (0x7fa9d86cf560 @ 15) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: == Stack trace for context 0x55bf9ef3e340 == Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #0 0x55bf9f3826b0 i resource:///org/gnome/shell/ui/tweener.js:80 (0x7fa9d86c8cd0 @ 82) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #1 0x55bf9f382630 i resource:///org/gnome/shell/ui/tweener.js:105 (0x7fa9d86c8f78 @ 36) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #2 0x55bf9f3825a8 i resource:///org/gnome/shell/ui/tweener.js:92 (0x7fa9d86c8de0 @ 52) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #3 0x55bf9f382508 i resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7fa9d86d2918 @ 54) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #4 0x7fff70e20200 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7fa9d86d29a0 @ 1626) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #5 0x7fff70e202b0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7fa9d86d2a28 @ 100) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #6 0x55bf9f382490 i resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fa9d86d2ab0 @ 10) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #7 0x7fff70e21600 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7fa9d86cff78 @ 386) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #8 0x55bf9f382400 i resource:///org/gnome/shell/ui/tweener.js:207 (0x7fa9d86cf5e8 @ 159) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #9 0x7fff70e22220 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fa9d86b5de0 @ 71) Feb 19 09:35:10 school org.gnome.Shell.desktop[8377]: #10 0x55bf9f382380 i resource:///org/gnome/shell/ui/tweener.js:182 (0x7fa9d86cf560 @ 15)
and journalctl shows 3589296 lines.
Something is really messed up.
On 2/19/19 10:12 AM, Howard Howell wrote:
On Tue, 2019-02-19 at 09:20 -0800, Samuel Sieb wrote:
The gnome-settings printer panel does not show enough information. Install system-config-printer, that will be more useful. It shows up as "Print Settings" in Activities. If you open your printer there, the Device URI will be in the middle.C
That shows "There are no printers configured yet." going back to settings it shows two versions of Canon MF620C.
That suggests that the printer is being picked up from mdns on the network. Having you tried adding the printer yourself?
Only a few lines relating to the printer:
Feb 19 09:34:35 school gnome-software[8837]: failed to rescan: Failed to parse /usr/share/applications/system-config-printer.desktop file: cannot process file of type application/x-desktop
That was from the install of system-config-printer.
Feb 19 09:34:48 school audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? term>
finger print reader daemon.
Feb 19 09:35:09 school gnome-shell[8377]: Object Meta.WindowActor (0x55bfa0f3b340), has been already finalized. Impossible to get any property from it. Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: == Stack trace for context 0x55bf9ef3e340 ==
This is the gnome-shell gjs log spam that has been going on for a long time. Although checking my logs, it seems to have finally stopped in latest F29 on this laptop, but not another one. Some of it might be caused by old extensions.
On Tue, 2019-02-19 at 12:06 -0800, Samuel Sieb wrote:
On 2/19/19 10:12 AM, Howard Howell wrote:
On Tue, 2019-02-19 at 09:20 -0800, Samuel Sieb wrote:
The gnome-settings printer panel does not show enough information. Install system-config-printer, that will be more useful. It shows up as "Print Settings" in Activities. If you open your printer there, the Device URI will be in the middle.C
That shows "There are no printers configured yet." going back to settings it shows two versions of Canon MF620C.
That suggests that the printer is being picked up from mdns on the network. Having you tried adding the printer yourself?
Only a few lines relating to the printer:
Feb 19 09:34:35 school gnome-software[8837]: failed to rescan: Failed to parse /usr/share/applications/system-config-printer.desktop file: cannot process file of type application/x-desktop
That was from the install of system-config-printer.
Feb 19 09:34:48 school audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? term>
finger print reader daemon.
Feb 19 09:35:09 school gnome-shell[8377]: Object Meta.WindowActor (0x55bfa0f3b340), has been already finalized. Impossible to get any property from it. Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: == Stack trace for context 0x55bf9ef3e340 ==
This is the gnome-shell gjs log spam that has been going on for a long time. Although checking my logs, it seems to have finally stopped in latest F29 on this laptop, but not another one. Some of it might be caused by old extensions. _______________________________________________ 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:
I did a clean install of F28. Couldn't get the upgrade to work!! So I don't think it would be old extensions, but then I do a lot of development work and get loads of stuff downloaded from time to time installing the bits I need, and some of that may have imported old stuff.
Should I add the printer using the cups 631 interface or the settings panel? The settings panel just threw me off today when I was attempting to answer your first message.
After seeing the cruft in journalctl, I did a journalctl reset and set it to just keep 2 days worth. I may want to up that later.
/************************* finger stuff ************************** $finger print reader daemon finger: print: no such user. finger: reader: no such user. Login: daemon Name: daemon Directory: /sbin Shell: /sbin/nologin Never logged in. No mail. No Plan.
Login: pulse Name: PulseAudio System Daemon Directory: /var/run/pulse Shell: /sbin/nologin Never logged in. No mail. No Plan.
Login: rpc Name: Rpcbind Daemon Directory: /var/lib/rpcbind Shell: /sbin/nologin Never logged in. No mail. No Plan.
Login: pipewire Name: PipeWire System Daemon Directory: /var/run/pipewire Shell: /sbin/nologin Never logged in. No mail. No Plan.
Login: tss Name: Account used by the trousers package to sandbox the tcsd daemon Directory: /dev/null Shell: /sbin/nologin Never logged in. No mail. No Plan.
On 2/19/19 12:20 PM, Howard Howell wrote:
I did a clean install of F28. Couldn't get the upgrade to work!! So I don't think it would be old extensions, but then I do a lot of development work and get loads of stuff downloaded from time to time installing the bits I need, and some of that may have imported old stuff.
Even with extensions disabled, there were still lots of stack traces. I think it's getting better in F29.
Should I add the printer using the cups 631 interface or the settings panel? The settings panel just threw me off today when I was attempting to answer your first message.
If Gnome settings is crashing your session, you should figure that out. You can add printers using the system-config-printer tool as well. That's usually what I use.
After seeing the cruft in journalctl, I did a journalctl reset and set it to just keep 2 days worth. I may want to up that later.
Unless you're running out of disk space, why limit it?
/************************* finger stuff ************************** $finger print reader daemon
You just found the "finger" command. I haven't used that since university. :-) You can ignore the fprintd log lines.
On Tue, 2019-02-19 at 12:20 -0800, Howard Howell wrote:
On Tue, 2019-02-19 at 12:06 -0800, Samuel Sieb wrote:
On 2/19/19 10:12 AM, Howard Howell wrote:
On Tue, 2019-02-19 at 09:20 -0800, Samuel Sieb wrote:
The gnome-settings printer panel does not show enough information. Install system-config-printer, that will be more useful. It shows up as "Print Settings" in Activities. If you open your printer there, the Device URI will be in the middle.C
That shows "There are no printers configured yet." going back to settings it shows two versions of Canon MF620C.
That suggests that the printer is being picked up from mdns on the network. Having you tried adding the printer yourself?
Only a few lines relating to the printer:
Feb 19 09:34:35 school gnome-software[8837]: failed to rescan: Failed to parse /usr/share/applications/system-config-printer.desktop file: cannot process file of type application/x-desktop
That was from the install of system-config-printer.
Feb 19 09:34:48 school audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? term>
finger print reader daemon.
Feb 19 09:35:09 school gnome-shell[8377]: Object Meta.WindowActor (0x55bfa0f3b340), has been already finalized. Impossible to get any property from it. Feb 19 09:35:09 school org.gnome.Shell.desktop[8377]: == Stack trace for context 0x55bf9ef3e340 ==
This is the gnome-shell gjs log spam that has been going on for a long time. Although checking my logs, it seems to have finally stopped in latest F29 on this laptop, but not another one. Some of it might be caused by old extensions. _______________________________________________ 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:
I did a clean install of F28. Couldn't get the upgrade to work!! So I don't think it would be old extensions, but then I do a lot of development work and get loads of stuff downloaded from time to time installing the bits I need, and some of that may have imported old stuff.
Should I add the printer using the cups 631 interface or the settings panel? The settings panel just threw me off today when I was attempting to answer your first message.
After seeing the cruft in journalctl, I did a journalctl reset and set it to just keep 2 days worth. I may want to up that later.
/************************* finger stuff ************************** $finger print reader daemon finger: print: no such user. finger: reader: no such user. Login: daemon Name: daemon Directory: /sbin Shell: /sbin/nologin Never logged in. No mail. No Plan.
Login: pulse Name: PulseAudio System Daemon Directory: /var/run/pulse Shell: /sbin/nologin Never logged in. No mail. No Plan.
Login: rpc Name: Rpcbind Daemon Directory: /var/lib/rpcbind Shell: /sbin/nologin Never logged in. No mail. No Plan.
Login: pipewire Name: PipeWire System Daemon Directory: /var/run/pipewire Shell: /sbin/nologin Never logged in. No mail. No Plan.
Login: tss Name: Account used by the trousers package to sandbox the tcsd daemon Directory: /dev/null Shell: /sbin/nologin Never logged in. No mail. No Plan.
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:
addendum. Just checked. Printer is now working??? Don't know what did that unless it was cleaning the journalctl files. Is that in a closed volume under F28? I had plenty of diskspace, more than 300GiB.
Should I close this now, or is there something I should check to see what mucked it up in the first place?
Regards, Les H
On 2/19/19 12:45 PM, Howard Howell wrote:
addendum. Just checked. Printer is now working??? Don't know what did that unless it was cleaning the journalctl files. Is that in a closed volume under F28? I had plenty of diskspace, more than 300GiB.
Only if you have /var on a separate partition and that would only affect printing if it got full and couldn't create the spool files. But since the log was still recording, that seems unlikely.
Should I close this now, or is there something I should check to see what mucked it up in the first place?
Probably not possible to find out. Maybe running system-config-printer poked cups in some different way. Hopefully it keeps working.
Allegedly, on or about 19 February 2019, Howard Howell sent:
I did a clean install of F28.
After a new install, you may need to horse around with the firewall, so that the printer is automatically found by the system. Look for an IPP (internet printing protocol) checkbox, and tick the client option if you're printing over the network to a printer (you'd tick the server checkbox if this computer was serving its directly connected printer to the rest of the LAN).
CUPS uses IPP. And there's another service, cups-browsed that needs to be running for it to find printers (start it going, and set it to always be enabled).
systemctl start cups-browsed systemctl enable cups-browsed
For other printer-related networking protocols, look through the rest of the protocols list in the firewall. e.g. You may need to tick mdns if it's involved in finding the printer.
On Tue, 2019-02-19 at 12:55 -0800, Samuel Sieb wrote:
On 2/19/19 12:45 PM, Howard Howell wrote:
addendum. Just checked. Printer is now working??? Don't know what did that unless it was cleaning the journalctl files. Is that in a closed volume under F28? I had plenty of diskspace, more than 300GiB.
Only if you have /var on a separate partition and that would only affect printing if it got full and couldn't create the spool files. But since the log was still recording, that seems unlikely.
Should I close this now, or is there something I should check to see what mucked it up in the first place?
Probably not possible to find out. Maybe running system-config- printer poked cups in some different way. Hopefully it keeps working. _______________________________________________ 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
Thanks for your help Samuel.
On Wed, 2019-02-20 at 17:58 +1030, Tim wrote:
Allegedly, on or about 19 February 2019, Howard Howell sent:
I did a clean install of F28.
After a new install, you may need to horse around with the firewall, so that the printer is automatically found by the system. Look for an IPP (internet printing protocol) checkbox, and tick the client option if you're printing over the network to a printer (you'd tick the server checkbox if this computer was serving its directly connected printer to the rest of the LAN).
CUPS uses IPP. And there's another service, cups-browsed that needs to be running for it to find printers (start it going, and set it to always be enabled).
systemctl start cups-browsed systemctl enable cups-browsed
For other printer-related networking protocols, look through the rest of the protocols list in the firewall. e.g. You may need to tick mdns if it's involved in finding the printer.
That didn't go well at all.... I dnf installed system-config-firewall and invoked it as sudo system-config-firewall:
No protocol specified /usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning) /usr/share/system-config-firewall/fw_gui.py:51: GtkWarning: IA__gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed icon_theme = gtk.icon_theme_get_default() /usr/share/system-config-firewall/fw_gui.py:61: Warning: invalid (NULL) pointer instance xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: Warning: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: GtkWarning: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: Warning: g_object_get: assertion 'G_IS_OBJECT (object)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: Warning: value "TRUE" of type 'gboolean' is invalid or out of range for property 'visible' of type 'gboolean' xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: GtkWarning: IA__gdk_screen_get_display: assertion 'GDK_IS_SCREEN (screen)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: Warning: g_object_ref: assertion 'G_IS_OBJECT (object)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: GtkWarning: IA__gdk_pango_context_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: PangoWarning: pango_context_set_font_description: assertion 'context != NULL' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: PangoWarning: pango_context_set_base_dir: assertion 'context != NULL' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: PangoWarning: pango_context_set_language: assertion 'context != NULL' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: PangoWarning: pango_layout_new: assertion 'context != NULL' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: PangoWarning: pango_layout_set_attributes: assertion 'layout != NULL' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: PangoWarning: pango_layout_set_text: assertion 'layout != NULL' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: PangoWarning: pango_layout_get_unknown_glyphs_count: assertion 'PANGO_IS_LAYOUT (layout)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: GtkWarning: IA__gdk_cursor_new_for_display: assertion 'GDK_IS_DISPLAY (display)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: PangoWarning: pango_layout_set_single_paragraph_mode: assertion 'PANGO_IS_LAYOUT (layout)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: PangoWarning: pango_layout_set_ellipsize: assertion 'PANGO_IS_LAYOUT (layout)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: PangoWarning: pango_layout_set_width: assertion 'layout != NULL' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: PangoWarning: pango_layout_set_wrap: assertion 'PANGO_IS_LAYOUT (layout)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: PangoWarning: pango_layout_set_alignment: assertion 'layout != NULL' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: PangoWarning: pango_layout_get_pixel_extents: assertion 'PANGO_IS_LAYOUT (layout)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: GtkWarning: IA__gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: GtkWarning: IA__gtk_icon_size_lookup_for_settings: assertion 'GTK_IS_SETTINGS (settings)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: GtkWarning: Invalid icon size 1
xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: GtkWarning: IA__gtk_icon_theme_load_icon: assertion 'GTK_IS_ICON_THEME (icon_theme)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: GtkWarning: Error loading theme icon 'edit-find' for stock: xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: GtkWarning: gtkstyle.c:2358: invalid icon size '1' xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: GtkWarning: IA__gtk_style_render_icon: assertion 'pixbuf != NULL' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: GtkWarning: Error loading theme icon 'text-x-generic' for stock: xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) /usr/share/system-config-firewall/fw_gui.py:61: GtkWarning: IA__gtk_icon_theme_lookup_by_gicon: assertion 'GTK_IS_ICON_THEME (icon_theme)' failed xml = gtk.glade.XML(DATADIR + "/" + GLADE_NAME, domain=DOMAIN) Traceback (most recent call last): File "/usr/bin/system-config-firewall", line 36, in <module> import fw_gui File "/usr/share/system-config-firewall/fw_gui.py", line 62, in <module> icon_theme.append_search_path(DATADIR) AttributeError: 'NoneType' object has no attribute 'append_search_path'
Did not expect that at all!!!
regards, Les H
On 2/20/19 9:23 AM, Howard Howell wrote:
That didn't go well at all.... I dnf installed system-config-firewall and invoked it as sudo system-config-firewall:
system-config-firewall is the old way for configuring iptables. If you're running firewalld, you need "firewall-config". Also, you can't run applications as root under Wayland, that's why you got the error.
On Wed, 2019-02-20 at 11:52 -0800, Samuel Sieb wrote:
On 2/20/19 9:23 AM, Howard Howell wrote:
That didn't go well at all.... I dnf installed system-config- firewall and invoked it as sudo system-config-firewall:
system-config-firewall is the old way for configuring iptables. If you're running firewalld, you need "firewall-config". Also, you can't run applications as root under Wayland, that's why you got the error.
Thanks, Samuel, Got firewall-config up and running. I will never understand how things evolve so rapidly and in such arbitrary ways... Guess I'm getting old.
Regards, Les H
On Thu, 2019-02-21 at 10:50 -0800, Howard Howell wrote:
On Wed, 2019-02-20 at 11:52 -0800, Samuel Sieb wrote:
On 2/20/19 9:23 AM, Howard Howell wrote:
That didn't go well at all.... I dnf installed system-config- firewall and invoked it as sudo system-config-firewall:
system-config-firewall is the old way for configuring iptables. If you're running firewalld, you need "firewall-config". Also, you can't run applications as root under Wayland, that's why you got the error.
Thanks, Samuel, Got firewall-config up and running. I will never understand how things evolve so rapidly and in such arbitrary ways
One of the delights of using Fedora. If you want a quiet life, maybe try a different distro :-)
... Guess I'm getting old.
We all are ...
poc
-
Howard Howell -
Patrick O'Callaghan -
Samuel Sieb -
Tim