I've read many threads on this problem and, so far, none have worked to resolve this problem. I have a wireless HP printer with a DHCP assigned ip. I'm running 13.1 and KDE with current updates installed.
After a reboot, I attempt to print and get a communication error. This morning I tried
When that didn't work, I tried
but that didn't work either. I tried to open the cups web page but got a permissions error, so I opened it as root. My user has always been in the lp group, but yesterday I tried
and added my user. That obviously didn't give me access to the cups page. When I get to cups, nothing I try gets the printer communicating. I end up re-installing it through yast and it begins to work.
My computer has a wired connection to my wireless router. I looked at the firewall. There are 2 interfaces displayed. The first is eth0 and that was in the External Zone. The other is the actual card and that has a device name and also an interface designation of enp2s8. That had no zone assigned and I put it into the Internal Zone for no other reason than to see if it worked to get communication established. It did not.
A separate problem: I can't get boinc to connect to the localhost, even after today's update. When boinc was running, I left my computer on 24/7 for months at a time. Now that boinc isn't working, I shut the thing off every night and am faced with the communication error when I reboot in the morning. It's only a few clicks to reinstall the printer but doing it everyday is very annoying. Please help me sort this out.
After a reboot, I attempt to print and get a communication error. This morning I tried
Code:
systemctl restart cups.service
Code:
systemctl restart cups
Code:
lppasswd -a
My computer has a wired connection to my wireless router. I looked at the firewall. There are 2 interfaces displayed. The first is eth0 and that was in the External Zone. The other is the actual card and that has a device name and also an interface designation of enp2s8. That had no zone assigned and I put it into the Internal Zone for no other reason than to see if it worked to get communication established. It did not.
A separate problem: I can't get boinc to connect to the localhost, even after today's update. When boinc was running, I left my computer on 24/7 for months at a time. Now that boinc isn't working, I shut the thing off every night and am faced with the communication error when I reboot in the morning. It's only a few clicks to reinstall the printer but doing it everyday is very annoying. Please help me sort this out.