On 12/17/2013 04:47 AM, Jim Sabatke wrote:
OK, I'm going crazy. I bought a Samsung SCX-4826FN B&W laser printer a few years ago that has always given me fits. After a lot of experimentation, I got it going by installing the Linux drivers from the Samsung support site. A couple months ago I moved and the computer I had it hooked to (12.2) sat for a while because I needed to buy a computer desk. When I got one and set everything up, I couldn't get the printer to work properly no matter what I tried that worked in the past. I've used the Samsung setup to remove and install the drivers and printer several times and generally get the same results:
Are you accessing this printer from the local network, or localhost? They have been doing some funky things with cups lately, especially if you use systemd. Specifically, if you have cups enabled to start at boot, by default, only the cups.socket is activated to accept print jobs from localhost, cupsd doesn't actually start. Therefore, if you are submitting print jobs from the local network, then it won't print. (the funky symptoms you see, may be the result of this). There are two workarounds I have found: (1) start cups again manually after boot with systemd. For whatever reason, this does force cupsd to load and stay resident. Check your service/socket files in /usr/lib/systemd/system/cups*. If your setup is like mine, you will find that cupsd.service is just a softlink to cups.service. So you want to start cupsd with 'systemctl start cups.service' (2) *without* cupsd running from (1) above, you can create a separate /etc/systemd/system/cups.socket file containing: .include /usr/lib/systemd/system/cups.socket [Socket] ListenStream=0.0.0.0:631 ListenDatagram=0.0.0.0:631 BindIPv6Only=ipv6-only Then issue systemctl --system daemon-reload This will enable cups.socket to start automatically and respond to local network print requests and not just those from localhost. See: https://wiki.archlinux.org/index.php/Cups#CUPS.27_systemd_service_does_not_s... (the BindIPv6Only=ipv6-only is fine, see: https://bugzilla.redhat.com/show_bug.cgi?id=737230 ) If you do (1) AND (2), you will get a systemd error: systemd[1]: Failed to reload: Address already in use I don't know whether (1) or (2) is the more correct way to do this. I have always liked having cupsd running personally, but the automagic socket approach may be the new way to go. HTH. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org