LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
Reload this Page [SOLVED] Samsung SL-C430W refuses to print test page USB/Ethernet/WiFi Debian 10.
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
Page 1 of 2 1 2
  Search this Thread
Old 02-05-2021, 04:08 AM   #1
globetrotterdk
Member
 
Registered: Nov 2006
Posts: 299

Rep: Reputation: 16
Samsung SL-C430W refuses to print test page USB/Ethernet/WiFi Debian 10.

Samsung SL-C430W on clean, new Debian Buster (Cinnamon) refuses to print a test page, regardless of whether using USB, Ethernet or WiFi. A USB connection produces a print out with an SPL error message - error code 11-1114.

With the printer connected either by an Ethernet cable or by WiFi, I get the message:

Processing - Unable to locate printer "SEC8425197B7B79.local". - "Is your printer connected?"

Nothing happens further and my printer at this point is about as useful as a pile of bricks sitting on my desk.

My Debian Buster Cinnamon install does not have a firewall installed, and the system is able to setup the printer for the first time, regardless of connection (except WiFi) without any intervention from me. I adjust the parameters (stationary) as needed and that is it.

The printer has been able to work with an Ethernet connection on a Q4OS KDE install (which is basically a Debian Buster with KDE Plasma) as well as connected to USB with a Fedora 33 Jam install. However, due to other technical issues, I have chosen to stick with Debian Buster Cinnamon - I just don't have a working printer.

Any advice? I have never in all the time I have used Linux, come across a printer problem as frustrating and weird as this one.
Last edited by globetrotterdk; 02-05-2021 at 04:09 AM.
 
Old 02-05-2021, 04:47 AM   #2
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,840

Rep: Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148
See if this helps...
https://h30434.www3.hp.com/t5/Samsun.../6848261#M2103

With respect to the network connectivity, can you ping the printer by its Avahi hostname?
Code:
ping SEC8425197B7B79.local
If not you may need to check that libnss-mdns is installed so that mdns hostname resolution works as it should.
https://packages.debian.org/sid/libnss-mdns
 
Old 02-05-2021, 05:19 AM   #3
globetrotterdk
Member
 
Registered: Nov 2006
Posts: 299

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by ferrari View Post
See if this helps...
https://h30434.www3.hp.com/t5/Samsun.../6848261#M2103

With respect to the network connectivity, can you ping the printer by its Avahi hostname?
Code:
ping SEC8425197B7B79.local
If not you may need to check that libnss-mdns is installed so that mdns hostname resolution works as it should.
https://packages.debian.org/sid/libnss-mdns
Thanks for the reply. libnss-mdns is installed, however these are the outputs that I am receiving:

Code:
$ lpoptions  -p Samsung_C43x_Series_SEC8425197B7B79_ | awk '{for (i=1; i<=NF; i++) {if ($i ~ /device-uri/) {print $i}}}'
device-uri=ipp://Samsung%20C43x%20Series%20(SEC8425197B7B79)._ipp._tcp.local/

$ ping SEC8425197B7B79.local
ping: SEC8425197B7B79.local: Name or service not known
Updating the drivers isn't an option. The Samsung printer division was sold to HP at some point and as far as I can see, the drivers have not been updated since 2014. I am using what are currently considered to be the latest, current drivers - uld_V1.00.39_01.17 available from the HP support site.
 
Old 02-05-2021, 07:29 AM   #4
globetrotterdk
Member
 
Registered: Nov 2006
Posts: 299

Original Poster
Rep: Reputation: 16
OK, I went into Windows 10 and setup the wireless printer connection again. I think it worked, as I get the following in Debian Buster:
Code:
$ ping 192.168.0.102
PING 192.168.0.102 (192.168.0.102) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
I tried to set the printer up manually, using CUPS web localhost interface. I set the printer address to socket://192.168.0.102:9100 and chose the correct driver, everything looked fine, so I tried to print a test page and the printer queue looks like this (shortened):

Samsung_C430W-7 Unknown Withheld 1k 1 processing since Fri 05 Feb 2021 --- "The printer is not responding."
 
Old 02-05-2021, 11:09 AM   #5
cynwulf
Senior Member
 
Registered: Apr 2005
Posts: 2,727

Rep: Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367
Those printers (and the HPs which came after) often required a binary filter "driver". If so, did you install it? Perhaps the other distributions packaged it - Debian does not.
 
Old 02-05-2021, 11:28 AM   #6
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,840

Rep: Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148
Quote:
Originally Posted by globetrotterdk View Post
Thanks for the reply. libnss-mdns is installed, however these are the outputs that I am receiving:

Code:
$ lpoptions  -p Samsung_C43x_Series_SEC8425197B7B79_ | awk '{for (i=1; i<=NF; i++) {if ($i ~ /device-uri/) {print $i}}}'
device-uri=ipp://Samsung%20C43x%20Series%20(SEC8425197B7B79)._ipp._tcp.local/

$ ping SEC8425197B7B79.local
ping: SEC8425197B7B79.local: Name or service not known
Is Avahi even running?
Code:
systemctl status avahi-daemon
What does /etc/nsswitch.conf hosts entry look like?

Mine for reference
Code:
hosts:          files mdns_minimal [NOTFOUND=return] dns
Or it could be a firewall issue.

I note the even pinging by IP address is failing for you....
Code:
$ ping 192.168.0.102
PING 192.168.0.102 (192.168.0.102) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
You appear to be have a firewall issue to sort for sure. If not on your machine then perhaps the AP router you're connected to is blocking and preventing detection.
Last edited by ferrari; 02-05-2021 at 11:36 AM.
 
Old 02-05-2021, 11:50 AM   #7
globetrotterdk
Member
 
Registered: Nov 2006
Posts: 299

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by cynwulf View Post
Those printers (and the HPs which came after) often required a binary filter "driver". If so, did you install it? Perhaps the other distributions packaged it - Debian does not.
Not sure what that is that you are referring to. I have installed the ULD package using the script, however that is the only thing that I am aware of that is needed.
 
Old 02-05-2021, 12:01 PM   #8
globetrotterdk
Member
 
Registered: Nov 2006
Posts: 299

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by ferrari View Post
Is Avahi even running?
Code:
systemctl status avahi-daemon
Code:
$ systemctl status avahi-daemon
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
   Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-02-05 19:45:49 EET; 4min 40s ago
 Main PID: 684 (avahi-daemon)
   Status: "avahi-daemon 0.7 starting up."
    Tasks: 2 (limit: 4915)
   Memory: 2.7M
   CGroup: /system.slice/avahi-daemon.service
           ├─684 avahi-daemon: running [artlink.local]
           └─733 avahi-daemon: chroot helper
Quote:
Originally Posted by ferrari View Post
What does /etc/nsswitch.conf hosts entry look like?

Mine for reference
Code:
hosts:          files mdns_minimal [NOTFOUND=return] dns
Code:
hosts:          files mdns4_minimal [NOTFOUND=return] dns myhostname
Quote:
Originally Posted by ferrari View Post
Or it could be a firewall issue.

I note the even pinging by IP address is failing for you....
Code:
$ ping 192.168.0.102
PING 192.168.0.102 (192.168.0.102) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
You appear to be have a firewall issue to sort for sure. If not on your machine then perhaps the AP router you're connected to is blocking and preventing detection.
Code:
$ sudo systemctl disable iptables
Failed to disable unit: Unit file iptables.service does not exist.
I have had firewalld installed, but I uninstalled it as soon as opening up ports 631 and 9100 didn't help my printer problem. Regarding the router, I don't believe that the router is the problem as I am able to print a test page from a Fedora 33 Cinnamon install (wireless) from a laptop, that I have yet to install Debian Buster on.
Last edited by globetrotterdk; 02-05-2021 at 12:03 PM.
 
Old 02-05-2021, 12:01 PM   #9
cynwulf
Senior Member
 
Registered: Apr 2005
Posts: 2,727

Rep: Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367Reputation: 2367
ULD: Thats the one - but does that version definitely support the printer model you have?
 
Old 02-05-2021, 12:12 PM   #10
globetrotterdk
Member
 
Registered: Nov 2006
Posts: 299

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by cynwulf View Post
ULD: Thats the one - but does that version definitely support the printer model you have?
Yes, been using it for a couple of years now. That is also why I am so surprised that I am having trouble all of a sudden, even though it is a new system...
 
Old 02-06-2021, 02:36 AM   #11
globetrotterdk
Member
 
Registered: Nov 2006
Posts: 299

Original Poster
Rep: Reputation: 16
I received a message from bchemnet, that runs the Samsung Unified Linux Driver Repository, regarding my issue:

Quote:
It appears that the Debian CUPS team backported a problematic change introduced in CUPS 2.2.11 to 2.2.10 (-4 and later). You are running into the issue from this bug:
https://github.com/apple/cups/issues/5562

The bug is fixed in 2.2.12 and 2.3.x, but that particular fix was not backported by Debian to 2.2.10. You can try opening a bug against the Debian package and see if the relevant committ can be backported. Otherwise you will need to revert to an earlier snapshot of CUPS (2.2.10-3 or earlier) or manually update to 2.2.12.
I have CUPS 2.2.10-6+deb10u4 installed on my system. I know that the devs at MXLinux patched their own solution from Debian testing, so I (possibly incorrectly) assume that getting the relevant commit backported isn't an option, so how do I manually update CUPS to 2.2.12? I couldn't find it in buster-backports and testing has 2.3.3op1-7...
Last edited by globetrotterdk; 02-06-2021 at 02:40 AM.
 
Old 02-06-2021, 03:39 AM   #12
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,840

Rep: Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148Reputation: 1148
Quote:
I have had firewalld installed, but I uninstalled it as soon as opening up ports 631 and 9100 didn't help my printer problem. Regarding the router, I don't believe that the router is the problem as I am able to print a test page from a Fedora 33 Cinnamon install (wireless) from a laptop, that I have yet to install Debian Buster on.
Well you need to find out why your pings were not allowed, and this may also be related to to your mdns hostname resolution failure.
 
Old 02-06-2021, 03:57 AM   #13
globetrotterdk
Member
 
Registered: Nov 2006
Posts: 299

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by ferrari View Post
Well you need to find out why your pings were not allowed, and this may also be related to to your mdns hostname resolution failure.
Sounds like a plan, but this is completely outside my limited skill set. What do I need to do to find out what the problem with pinging is all about?

Googling about the /etc/nsswitch.conf hosts entry suggests that mine is setup within parameters (see above).
Last edited by globetrotterdk; 02-06-2021 at 04:03 AM.
 
Old 02-06-2021, 04:28 AM   #14
globetrotterdk
Member
 
Registered: Nov 2006
Posts: 299

Original Poster
Rep: Reputation: 16
OK, I think that I figured out why I was getting a "ping: sendmsg: Operation not permitted" message. I use a VPN. With the VPN disabled, I get the following:

Code:
$ ping 192.168.0.102
PING 192.168.0.102 (192.168.0.102) 56(84) bytes of data.
From 192.168.0.107 icmp_seq=1 Destination Host Unreachable
From 192.168.0.107 icmp_seq=2 Destination Host Unreachable
From 192.168.0.107 icmp_seq=3 Destination Host Unreachable
From 192.168.0.107 icmp_seq=4 Destination Host Unreachable
From 192.168.0.107 icmp_seq=5 Destination Host Unreachable
From 192.168.0.107 icmp_seq=6 Destination Host Unreachable
From 192.168.0.107 icmp_seq=7 Destination Host Unreachable
From 192.168.0.107 icmp_seq=8 Destination Host Unreachable
From 192.168.0.107 icmp_seq=9 Destination Host Unreachable
 
Old 02-06-2021, 08:12 AM   #15
globetrotterdk
Member
 
Registered: Nov 2006
Posts: 299

Original Poster
Rep: Reputation: 16
Hmmm. Interesting. I assumed that the IP address was static on the printer, from when I set it in Win 10. However:

Code:
$ ping SEC8425197B7B79.local
PING SEC8425197B7B79.local (192.168.0.103) 56(84) bytes of data.
64 bytes from 192.168.0.103 (192.168.0.103): icmp_seq=1 ttl=64 time=14.9 ms
64 bytes from 192.168.0.103 (192.168.0.103): icmp_seq=2 ttl=64 time=2.36 ms
64 bytes from 192.168.0.103 (192.168.0.103): icmp_seq=3 ttl=64 time=12.6 ms
64 bytes from 192.168.0.103 (192.168.0.103): icmp_seq=4 ttl=64 time=2.54 ms
64 bytes from 192.168.0.103 (192.168.0.103): icmp_seq=5 ttl=64 time=3.39 ms
64 bytes from 192.168.0.103 (192.168.0.103): icmp_seq=6 ttl=64 time=2.32 ms
64 bytes from 192.168.0.103 (192.168.0.103): icmp_seq=7 ttl=64 time=3.43 ms
64 bytes from 192.168.0.103 (192.168.0.103): icmp_seq=8 ttl=64 time=3.37 ms
64 bytes from 192.168.0.103 (192.168.0.103): icmp_seq=9 ttl=64 time=2.85 ms
64 bytes from 192.168.0.103 (192.168.0.103): icmp_seq=10 ttl=64 time=6.81 ms
64 bytes from 192.168.0.103 (192.168.0.103): icmp_seq=11 ttl=64 time=2.72 ms
64 bytes from 192.168.0.103 (192.168.0.103): icmp_seq=12 ttl=64 time=3.13 ms
64 bytes from 192.168.0.103 (192.168.0.103): icmp_seq=13 ttl=64 time=2.67 ms
64 bytes from 192.168.0.103 (192.168.0.103): icmp_seq=14 ttl=64 time=27.4 ms
Code:
$ ping 192.168.0.103
PING 192.168.0.103 (192.168.0.103) 56(84) bytes of data.
64 bytes from 192.168.0.103: icmp_seq=1 ttl=64 time=4.64 ms
64 bytes from 192.168.0.103: icmp_seq=2 ttl=64 time=2.57 ms
64 bytes from 192.168.0.103: icmp_seq=3 ttl=64 time=4.33 ms
64 bytes from 192.168.0.103: icmp_seq=4 ttl=64 time=2.57 ms
64 bytes from 192.168.0.103: icmp_seq=5 ttl=64 time=2.55 ms
64 bytes from 192.168.0.103: icmp_seq=6 ttl=64 time=2.58 ms
64 bytes from 192.168.0.103: icmp_seq=7 ttl=64 time=2.63 ms
64 bytes from 192.168.0.103: icmp_seq=8 ttl=64 time=2.43 ms
64 bytes from 192.168.0.103: icmp_seq=9 ttl=64 time=2.62 ms
64 bytes from 192.168.0.103: icmp_seq=10 ttl=64 time=3.11 ms
64 bytes from 192.168.0.103: icmp_seq=11 ttl=64 time=2.62 ms
 
  


Reply
Page 1 of 2 1 2

Tags
buster, ethernet, printer, usb, wifi



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Samsung Xpress C430w Printer tommurray Linux - Hardware 2 08-06-2019 10:47 PM
trouble installing samsung sl-c430w on ubuntu studio 18.04 jmsg311bd Linux - Newbie 1 01-21-2019 05:06 AM
mc4695MF prints test page fine, but application print are hazardous (OK/blank page) hardt68 Linux - Hardware 0 04-25-2014 07:44 PM
HP PS7150: text doesn't print in OOO and Abiword!, but I can print test page & w MzFF gabba Mandriva 6 10-31-2005 11:10 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian

All times are GMT -5. The time now is 11:31 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration