Printer not working after update

update
printer

#1

My Brother QL-570 printer was working ok until yesterday that I updated the system.

I have tried all this without success:

  • Reinstalling the printer
  • Reinstalling the drivers for QL-570 from AUR
  • Downgrading CUPS to many versions before (no one works)
  • Using a previous Kernel
  • Using different drivers like a generic driver or QL-580 drivers
  • doing sudo pacman -Syy
  • also sudo pacman -S gtk3-print-backends
  • and restarting the computer many times along the way

I don’t know what else I can do. I use this printer to work at home so it’s very important for me. Any help is appreciated.


#2

I got this message about cups groups.

Note: I did nothing, and printing (from kate on two different laptops to a wireless epson) still worked, but you may have something different.


#3

This is my cups-files.conf file. Could you advice exactly where should I do the changes? Thanks in advance


#
# File/directory/user/group configuration file for the CUPS scheduler.
# See "man cups-files.conf" for a complete description of this file.
#

# List of events that are considered fatal errors for the scheduler...
#FatalErrors config

# Do we call fsync() after writing configuration or status files?
#SyncOnClose No

# Default user and group for filters/backends/helper programs; this cannot be
# any user or group that resolves to ID 0 for security reasons...
User 209
Group 209

# Administrator user group, used to match @SYSTEM in cupsd.conf policy rules...
# This cannot contain the Group value for security reasons...
SystemGroup sys root


# User that is substituted for unauthenticated (remote) root accesses...
#RemoteRoot remroot

# Do we allow file: device URIs other than to /dev/null?
#FileDevice No

# Permissions for configuration and log files...
#ConfigFilePerm 0640
#LogFilePerm 0644

# Location of the file logging all access to the scheduler; may be the name
# "syslog". If not an absolute path, the value of ServerRoot is used as the
# root directory.  Also see the "AccessLogLevel" directive in cupsd.conf.
AccessLog /var/log/cups/access_log

# Location of cache files used by the scheduler...
#CacheDir /var/cache/cups

# Location of data files used by the scheduler...
#DataDir /usr/share/cups

# Location of the static web content served by the scheduler...
#DocumentRoot /usr/share/cups/doc

# Location of the file logging all messages produced by the scheduler and any
# helper programs; may be the name "syslog". If not an absolute path, the value
# of ServerRoot is used as the root directory.  Also see the "LogLevel"
# directive in cupsd.conf.
ErrorLog /var/log/cups/error_log

# Location of fonts used by older print filters...
#FontPath /usr/share/cups/fonts

# Location of LPD configuration
#LPDConfigFile xinetd:///etc/xinetd.d/cups-lpd

# Location of the file logging all pages printed by the scheduler and any
# helper programs; may be the name "syslog". If not an absolute path, the value
# of ServerRoot is used as the root directory.  Also see the "PageLogFormat"
# directive in cupsd.conf.
PageLog /var/log/cups/page_log

# Location of the file listing all of the local printers...
#Printcap /etc/printcap

# Format of the Printcap file...
#PrintcapFormat bsd
#PrintcapFormat plist
#PrintcapFormat solaris

# Location of all spool files...
#RequestRoot /var/spool/cups

# Location of helper programs...
#ServerBin /usr/lib/cups

# SSL/TLS keychain for the scheduler...
#ServerKeychain ssl

# Location of other configuration files...
#ServerRoot /etc/cups

# Location of Samba configuration file...
#SMBConfigFile 

# Location of scheduler state files...
#StateDir /run/cups

# Location of scheduler/helper temporary files. This directory is emptied on
# scheduler startup and cannot be one of the standard (public) temporary
# directory locations for security reasons...
#TempDir /var/spool/cups/tmp

#4

Do you think it can be fixed if I reinstall Manjaro?
I’ve got my /home folder in a different partition.


#5

If 209 is in cups-files.conf then that file is done. Did you run the command to fix ownership?

chgrp -R cups /etc/cups

#6

Yes, I’ve done it before and just now again, just in case. But nothing, it doesn’t work.


#7

Hi, I did a system upgrade the same day and reboot the system I found that I lost connection with the network shared printers, where correctly printing last Friday.

Then, I run

sudo systemctl status org.cups.cupsd.service
org.cups.cupsd.service - CUPS Scheduler
   Loaded: loaded (/usr/lib/systemd/system/org.cups.cupsd.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2018-02-19 11:00:26 -03; 6h ago
     Docs: man:cupsd(8)
 Main PID: 257 (cupsd)
   Status: "Scheduler is running..."
    Tasks: 3 (limit: 3893)
   CGroup: /system.slice/org.cups.cupsd.service
           ├─ 257 /usr/bin/cupsd -l
           ├─1067 /usr/lib/cups/notifier/dbus dbus://
           └─5238 smb://192.168.2.95/HP1006 25 jochoa Test Page 1 job-uuid=urn:uuid:571b3250-4cc7-3717-734c-3bda1482f571 job-origin

feb 19 11:00:20 pcjochoa systemd[1]: Starting CUPS Scheduler...
feb 19 11:00:26 pcjochoa systemd[1]: Started CUPS Scheduler.
feb 19 12:08:20 pcjochoa foo2xqx-wrapper[989]: gs -sPAPERSIZE=a4 -g9920x7016 -r1200x600 -sDEVICE=pbmraw -dCOLORSCREEN -dMaxBitmap=5
feb 19 12:16:57 pcjochoa foo2zjs-wrapper[1225]: gs -sPAPERSIZE=a4 -g9920x7016 -r1200x600 -sDEVICE=pbmraw -dCOLORSCREEN -dMaxBitmap=
feb 19 12:16:57 pcjochoa foo2zjs-wrapper[1226]: foo2zjs -r1200x600 -g9920x7016 -p9 -m1 -n1 -d1 -s7 -z1  -u 192x96 -l 192x96 -L 0  -
feb 19 17:52:16 pcjochoa foo2xqx-wrapper[5188]: gs -sPAPERSIZE=a4 -g9920x7016 -r1200x600 -sDEVICE=pbmraw -dCOLORSCREEN -dMaxBitmap=

I looks okay but when I send jobs they are pending.
The message is Idle - Unable to connect to CIFS host, will retry in 60 seconds…
I also tried to add another network printer through windows samba share I cannot reach the printer. I restart cups service and nothing happened.

I also found in the journalctl this:

feb 19 09:26:13 pcjochoa systemd[1]: Started Samba NetBIOS name server.
feb 19 09:26:13 pcjochoa systemd[1]: Starting Samba SMB/CIFS server...
feb 19 09:26:13 pcjochoa nmbd[291]: [2018/02/19 09:26:13.012762,  0] ../lib/util/become_daemon.c:135(daemon_status)
feb 19 09:26:13 pcjochoa sddm[286]: Initializing...
feb 19 09:26:13 pcjochoa nmbd[291]:   STATUS=daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...NOTE: N
feb 19 09:26:13 pcjochoa sddm[286]: Logind interface found
feb 19 09:26:15 pcjochoa smbd[302]: [2018/02/19 09:26:15.932927,  0] ../lib/util/become_daemon.c:124(daemon_ready)
feb 19 09:26:13 pcjochoa sddm[286]: Starting...
feb 19 09:26:15 pcjochoa smbd[302]:   STATUS=daemon 'smbd' finished starting up and ready to serve connections
feb 19 09:26:13 pcjochoa sddm[286]: Adding new display on vt 1 ...

and this

feb 19 09:26:27 pcjochoa sddm-greeter[466]: Message received from daemon: HostName
feb 19 09:26:28 pcjochoa nmbd[291]: [2018/02/19 09:26:28.024248,  0] ../lib/util/become_daemon.c:124(daemon_ready)
feb 19 09:26:28 pcjochoa nmbd[291]:   STATUS=daemon 'nmbd' finished starting up and ready to serve connections
feb 19 09:26:32 pcjochoa mandb[263]: Purging old database entries in /usr/share/man...
feb 19 09:26:32 pcjochoa

feb 19 10:59:12 pcjochoa ksmserver[630]: ksmserver: KSMServer::completeKilling clients.count()= 5
feb 19 10:59:24 pcjochoa nmbd[291]: [2018/02/19 10:59:24.602497,  0] ../source3/nmbd/nmbd.c:58(terminate)
feb 19 10:59:12 pcjochoa kwin_x11[635]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 32352, resource id: 56623108, major code: 18 (Chan
feb 19 10:59:24 pcjochoa nmbd[291]:   Got SIGTERM: going down...

eb 19 11:00:23 pcjochoa ModemManager[231]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.0/0000:03:00.0': not
feb 19 11:00:20 pcjochoa systemd[1]: Starting Samba NetBIOS name server...
feb 19 11:00:24 pcjochoa avahi-daemon[230]: Joining mDNS multicast group on interface enp3s0.IPv4 with address 192.168.2.102.
feb 19 11:00:20 pcjochoa systemd[1]: Starting Permit User Sessions...
feb 19 11:00:24 pcjochoa avahi-daemon[230]: New relevant interface enp3s0.IPv4 for mDNS.
feb 19 11:00:20 pcjochoa systemd[1]: Starting Network Manager Script Dispatcher Service...
feb 19 11:00:24 pcjochoa avahi-daemon[230]: Registering new address record for 192.168.2.102 on enp3s0.IPv4.
feb 19 11:00:20 pcjochoa systemd[1]: Started Permit User Sessions.
feb 19 11:00:24 pcjochoa nmbd[273]: [2018/02/19 11:00:24.450993,  0] ../lib/util/become_daemon.c:124(daemon_ready)
feb 19 11:00:20 pcjochoa systemd[1]: Started Simple Desktop Display Manager.
feb 19 11:00:24 pcjochoa nmbd[273]:   STATUS=daemon 'nmbd' finished starting up and ready to serve connections

feb 19 11:02:43 pcjochoa nmbd[273]: [2018/02/19 11:02:43.312601,  0] ../source3/nmbd/nmbd_become_lmb.c:418(become_local_master_fail2)
feb 19 11:02:43 pcjochoa nmbd[273]:   become_local_master_fail2: failed to register name WORKGROUP<1d> on subnet 192.168.2.102. Failed to beco
feb 19 11:02:43 pcjochoa nmbd[273]: [2018/02/19 11:02:43.312896,  0] ../source3/nmbd/nmbd_namelistdb.c:320(standard_fail_register)
feb 19 11:02:43 pcjochoa nmbd[273]:   standard_fail_register: Failed to register/refresh name WORKGROUP<1d> on subnet 192.168.2.102

And this is the time when CUPS changed the attributes on the network printers

feb 19 12:09:17 pcjochoa plasmashell[618]: trying to show an empty dialog
feb 19 12:09:19 pcjochoa plasmashell[618]: libkcups: Get-Printer-Attributes last error: 0 successful-ok
feb 19 12:09:19 pcjochoa plasmashell[618]: libkcups: 4 "HP-LaserJet-P1006"
feb 19 12:09:19 pcjochoa plasmashell[618]: libkcups: "Printer \"HP-LaserJet-P1006\" state changed." "ipp://pcjochoa/printers/HP-LaserJet-P1006
feb 19 12:09:19 pcjochoa plasmashell[618]: libkcups: Get-Jobs last error: 0 successful-ok
feb 19 12:09:19 pcjochoa plasmashell[618]: libkcups: 1
feb 19 12:09:19 pcjochoa plasmashell[618]: libkcups: Get-Jobs last error: 0 successful-ok
feb 19 12:09:19 pcjochoa plasmashell[618]: libkcups: 1
feb 19 12:09:19 pcjochoa plasmashell[618]: libkcups: Get-Printer-Attributes last error: 0 successful-ok
feb 19 12:09:19 pcjochoa plasmashell[618]: libkcups: 4 "HP-LaserJet-P1006"
feb 19 12:09:19 pcjochoa plasmashell[618]: libkcups: Get-Printer-Attributes last error: 0 successful-ok
feb 19 12:09:19 pcjochoa plasmashell[618]: libkcups: "Printer \"HP-LaserJet-P1006\" state changed." "ipp://pcjochoa/printers/HP-LaserJet-P1006
lines 6610-6632

But I discovered a minutes ago in the forum that
Processing - Tree connect failed (NT_STATUS_ACCESS_DENIED)
can be reparied with

sudo systemctl status nmbd.service
● nmbd.service - Samba NetBIOS name server
   Loaded: loaded (/usr/lib/systemd/system/nmbd.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2018-02-21 09:02:35 -03; 6h ago
  Process: 265 ExecStart=/usr/bin/nmbd -D (code=exited, status=0/SUCCESS)
 Main PID: 287 (nmbd)
    Tasks: 1 (limit: 3894)
   CGroup: /system.slice/nmbd.service
           └─287 /usr/bin/nmbd -D

feb 21 09:02:31 pcjochoa systemd[1]: Starting Samba NetBIOS name server...
feb 21 09:02:35 pcjochoa systemd[1]: Started Samba NetBIOS name server.
feb 21 09:02:35 pcjochoa nmbd[287]: [2018/02/21 09:02:35.825113,  0] ../lib/util/become_daemon.c:135(daemon_status)
feb 21 09:02:35 pcjochoa nmbd[287]:   STATUS=daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...NOTE: N
feb 21 09:02:40 pcjochoa nmbd[287]: [2018/02/21 09:02:40.826302,  0] ../lib/util/become_daemon.c:124(daemon_ready)
feb 21 09:02:40 pcjochoa nmbd[287]:   STATUS=daemon 'nmbd' finished starting up and ready to serve connections

I print a Test page and a page from an archive I have opened and the problem was solved.

I really do not know whether it could help you. Consider this reply as a guide, only don’t feel alone.
Best regards,


#8

I have just solved it as I’m writing this right now.
But the hard way. I have just resintalled Manjaro.

The problem now is that I have 2 home folders!! One is a whole partition (the original one that I wished to keep) and the new one created by Manjaro during the installation. I wonder how could I unify both of them…


#9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.