Hello Jim, I haven't used that printer before, but some things that might be worth trying: 1. Try printing the test page from within cups: http://localhost:631/printers/ 2. Check the printer status in cups (Use URL in #1). The last column is "Status". 3. Make sure that there isn't anything stuck in the print queue: http://localhost:631/jobs/ If there are print jobs, cancel them. 4. If you are printing from within LibreOffice/OpenOffice, set the Printer Language Type to: a. PostScript (Level from driver), OR b. PDF In the print dialogue (File->Print): i. Select the printer in "Printer" ii. Click on "Properties" button iii. Click on the "Device" tab. "Printer Language Type" is a drop down box at the bottom of the "Properties" dialogue that appears. 5. Often I have trouble between A4 and Letter page types. If the document is Letter, make sure the printer isn't setup to print A4. Again, from within LibreOffice/OpenOffice: In the print dialogue (File->Print): i. Select the printer in "Printer" ii. Click on "Properties" button iii. Make sure "Paper size" is set to the same as the document you are trying to print. 6. Test printing from the command line. See if this works (as root and as your user): echo "hello" | lp 7. Is your user account a member of the "lp" group? If not, might want to add it. If you do add it, then log out and log back in. Again, hopefully one of these will help. Cheers, Alvin On 17/12/13 06:47, 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:

The printer is recognized and setup. Printing to the printer the printer acts like it is going to print. Sometimes the printer just blinks and does nothing else. Sometimes after a new setup, it actually prints, but it prints out raw Postscript.

I'm so desperate that if I can't get this working really fast, I'll have to buy another printer because I have some extremely important documents to print out, and will continue to need to be able to do so. I'm disabled, so buying another printer is not a good option.

I'm not even sure what logs to include to help, but I will be happy to provide them.

I see on Google searches that there are other drivers, and 12.2 does include them automatically, but I can't find any instructions online for using them. What concerns me most is that, aside from needing an occasional reboot when the printer started malfunctioning, it was working fine (except that model jams way too easy. I would never buy another Samsung unless I read reliable reports that it works well with Linux). I also see that a lot of people have a lot of problems with Samsung printers, including this one specifically.

Thanks in advance,

Jim

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

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