Check that glibc-32bit is installed…
https://forums.opensuse.org/showthread.php/531271-Brother-printer-driver-installs-but-can-t-print?p=2868403#post2868403
Unfortunately, I’m not convinced that is the complete log. It doesn’t show output concerning a particular print job as expected. In particular, the filter processing is missing.
ls -lh | grep *libc-2.22.so
alex@linux-sdh1:/lib> ls -lh | grep *libm-2.22.so
alex@linux-sdh1:/lib> ls -lh | grep *ld-linux.so.2
lrwxrwxrwx 1 root root 10 Jul 21 23:13 **ld-linux.so.2** -> ld-2.26.so
lrwxrwxrwx 1 root root 13 Jul 21 23:13 ld-lsb.so.3 -> **ld-linux.so.2**
Sorry if I missed some thing. I have run another job and here is what I have SUSE Paste .
Looks like I only have one of these files (the last one):
alex@linux-sdh1:/lib> ls -lh | grep *libc-2.22.so
alex@linux-sdh1:/lib> ls -lh | grep *libm-2.22.so
alex@linux-sdh1:/lib> ls -lh | grep *ld-linux.so.2
lrwxrwxrwx 1 root root 10 Jul 21 23:13 ld-linux.so.2 -> ld-2.26.so
lrwxrwxrwx 1 root root 13 Jul 21 23:13 ld-lsb.so.3 -> ld-linux.so.2
Sorry if I missed some thing. I have run another job and here is what I have SUSE Paste .
Strange, I’m not seeing evidence of a print job here. Is CUPS in debug mode?
sudo grep debug /etc/cups/cupsd.conf
It should return
LogLevel debug
That looks ok to me.
Yes, it looks that way:
alex@linux-sdh1:~> sudo grep debug /etc/cups/cupsd.conf
[sudo] password for root:
LogLevel debug
I have tried to pring from the terminal:
echo "Howdy"| lp
request id is HLL2380DW-41 (0 file(s))
Log:
Ok, it’s late here…time for sleep. Hopefully others can chime in to help progress this further. I did wonder about the printer URI (http://192.168.0.23:631/ipp/) and whether it was correct. You could try using the CUPS socket:// backend (socket://192.168.0.23) instead, although there’s no evidence of an issue with it AFAICS.
Many thanks Deano! Your help is much appreciated!
I have changed it via CUPS web interface and have the following now:
The status said prining and says:
|[HLL2380DW](http://localhost:631/printers/HLL2380DW)-44|Unknown|Withheld|1k|Unknown|processing since
|---|---|---|---|---|
Wed 26 Sep 2018 09:17:51 PM AEST
*"The printer is not responding.*|
Output:
I was thinking, if anyone has a brother printer (any bother printer) set up over Wi-Fi on Leap 15, could you please post your current set up options (under Printers GUI application). Also, any firewall changes?
I just want to compare as I maybe missing something very trivial…
Hi all :-),
I am happy to report that the issue has ben fixed! I just removed the printer and re-added it again via CUPS admin page. This time I used the HTTP (80) port and it worked right away.
Many thanks to everyone who tried to help out!
Cheers,
Alex
Ah, that makes sense. That’s the default port for http protocol. 
Thanks for the update.
Using the Brother installer, try this:
Select the printer model (or enter it). Be sure to select “socket” if the printer is on on a LAN, which is Wi-Fi. My first attempt had the printer installed on the USP port. Don’t select the URI within the installer. When finished, use Yast/hardware/printer to add the printer. The driver should be on the list.
Thank you all for all the great info during this somewhat frustrating process.
I wanted to pass along a URI that worked for me over wifi. I was having trouble getting the exact format correct, and tried various http and https iterations as well as some lpd formats I found in another forum. Many would send a “print test” command to the printer and correctly read status, but the queue would just empty with a successful feedback signal but no printing.
I installed the drivers using the script and selected the brother-hLL2380DW-cups-en.ppd wrapper in /opt/brother/Printers/HLL2380DW/cupswrappers/.
The URI that worked is ipp://printer-ip:80/
Clearly printer-ip is replaced with the printer’s ip. No directory, no queue name. Protocol selected in CUPS was ipp. Hope this helps.
Strange, I only buy brother printers, because of the easy and good Linux support.
While Ubuntu discovers brother printers automatically, on Suse I usually install all printer drivers from yast, do a zyppper install brscan cuspwapper and printer driver, deactivate the firewall, let yast/cups discover the printer and done.
And you actually don’t really need the brother drivers, if you have a network printer.
You can use generic postscript drivers. I found this when I used Android Printershare APP, that prints to most network printers, using a a generic driver.
1 Like
Installed proprietary Brother drivers on several machines and sometimes got puzzling annoyances. Infamous host erlangen still has a proprietary package installed:
erlangen:~ # zypper se -si hll
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+---------------+---------+---------+------+------------------
i+ | hll2350dwpdrv | package | 4.0.0-1 | i386 | (System Packages)
erlangen:~ #
In May I tested driverless printing with the hll2350dw. It works like a charm and I consider removing the proprietary printer:
erlangen:~ # ll /etc/cups/ppd/
total 88
-rw-r----- 1 root lp 10131 May 27 05:51 Brother_HL-L2350DW_series.ppd
-rw-r----- 1 root lp 10131 May 27 05:51 Brother_HL-L2350DW_series.ppd.O
-rw-r----- 1 root lp 22243 Apr 4 12:39 CUPS-PDF.ppd
-rw-r----- 1 root lp 17840 Nov 8 2021 HLL2350DW.ppd
-rw-r----- 1 root lp 17840 Sep 1 2021 HLL2350DW.ppd.O
erlangen:~ #
erlangen:~ # lpstat -d
system default destination: Brother_HL-L2350DW_series
erlangen:~ #
To my experience configuration of driverless printing takes seconds only for pristine cups, but can be cumbersome with an existing installation.