![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 01/03/2020 14.00, gumb wrote:
On 29/02/2020 23:11, gumb wrote:
On 27/02/2020 15:03, Simon Becherer wrote: ...> Success at last!
Although I'm not 100% sure which of the actions I just performed had the desired effect.
After the first few days of getting nowhere, I'd uninstalled the long list of 76 32-bit dependencies, attached to my original post, keeping just libusb-0_1-4-32bit. When installing using the Brother script it doesn't pull all these in and the only consistent reference I keep seeing is about that libusb file.
I've already tried installing one or two random things in the interim, such as additonal cups backends, to no avail. I was browsing through other associated cups files in YaST and saw libcups2-32bit, so I selected it for install, just on a hunch (I've subsequently noted that that was amongst the 76 previously installed). That pulled in 26 32-bit dependencies, so not as many as the 76 I had originally.
I also decided to search for each of the three Brother rpms already installed, then select them to 'Update Unconditionally'. This indicated that it also wanted to install libgcc_s1-32bit and libstdc++6-32bit. Both of these were amongst those 76 too.
The next time I tried a test print in YaST suddenly it sprang into life, both via wireless and USB. I've subsequently reinstated the firewall, AppArmor and removed my user from the lp group. It continues to print fine.
Either forcibly reinstalling the rpms had some effect or I was missing something else in the config when I originally had the 76 files installed, though I struggle to see what. I'm not inclined to mess about diagnosing it any further, I need to use it urgently over the next couple of days.
Wow :-. So in the end you installed three Brother rpms without using their script, because you already had them, and their dependencies. And did not touch "configuration of printer". -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))