Lexmark E260dn Filter Error on MacOS Big Sur

Lexmark E260dn ErrorOver the Summer I got a new MacBook Pro 16 to replace my current MacBook Pro from 2010. Due to the COVID19 pandemic, I had to start working from home full time, so my home office has had to go through a lot of changes to accommodate this change. This has meant, that my new MacBook has been sitting in a box for a couple of months while my desk has been taken over by my work laptop. The other hesitation has been Apple; they have been focused on iOS 14 and product launches around it, that MacOS 11, otherwise known as macOS Big Sur was released in the Fall instead of late Summer. Now with macOS Big Sur 11.1 installed, I have been slowly moving over to the new MacBook.

The first real problem I have encountered has been with my Lexmark E260dn monochrome laser printer. Lexmark no longer provides updates for this printer and since the printer still works fine and I use it sparingly throughout the year; I see no reason to replace it. The E260dn replaced a similar Lexmark printer, which died a few years ago, unexpectedly on the day I needed to print some tax documents. I suspect a power surge or electrical short killed the board. Upon downloading the printer drivers for MacOS X from Lexmark, running the installer, and adding the printer in System Preferences – Printers & Scanners, and then attempting to print an email, I got a Filter Error in the Printer Status.

After researching the problem, I was able to to fix the issue.

Reset Printing System

First open up System Preferences – Printers & Scanners. Hold down the Control key and drag your pointer over the Printers area. The option to Reset Printing System will appear. Go ahead and click on the option.

Download Lexmark Drivers

You will need to get the last updated drivers from Lexmark. Here is the direct link to the download page: Print Driver for 10.6.8 and later Mac OS. Once you agree to the download, open the installer and run through the installation process.

Add Lexmark Printer

In System Preferences – Printers & Scanners, click the plus sign and add your printer. It should come up and you should see it added. If you try to print something, it should result in the Filter Error.

Modify Settings

Use the Go to Folder… option under the Go menu to open the following location: /Library/Printers/Lexmark/filter/

Next you will need to edit the file psoptionreroute with a text editor. I recommend using BBEdit, as it will let you modify system files easily. Right Click on the file and choose Open With – Other and choose BBEdit. In the file psoptionreroute, look for the line:

use POSIX qw(tmpnam);

Comment this line out by adding a pound sign in front of it and then directly underneath add the text below:

use File::Temp qw(tmpnam);

File and Save and close the file. At this point, go ahead and attempt to print something and the error will no longer appear and you should hear your printer turning on and spitting out a page or two. Further discussion on this issue can be found on the Apple Support Forums.

Filed under: Apple, Mac OS X

pfSense 2.4.5 Package Manager Defect

There is a defect with pfSense 2.4.5 and the Package Manager. When installing, upgrading, or removing packages, the process will not complete. For the Squid package, I did the following to upgrade:

  1. Stop the Squid service
  2. Attempt to upgrade the Squid package
  3. Wait until the process stalls
  4. Use Putty to SSH into the pfSense firewall
  5. Select the SSH option
  6. Execute the command to kill the Package Manager and then Exit
killall -9 pkg-static

Reference the following forum post on the Netgate pfSense forum for more info.

Filed under: Networking

CentOS 8.1 Modular Dependency Problems

Some of us prefer the Red Hat flavor of Linux to the Debian and Ubuntu distros. Although CentOS is a very stable system, you do run into issues like any other operating system. Here is an issue that I encountered on my CentOS 8.1 web server, while trying to fix something else.

Modular Dependency Problems with Perl

Running a dnf check would result in the following messages.

#dnf check

Modular dependency problems:

 Problem 1: conflicting requests
  - nothing provides module(perl:5.26) needed by module perl-DBD-MySQL:4.046:8010020191114030811:073fa5fe-0.x86_64
 Problem 2: conflicting requests
  - nothing provides module(perl:5.26) needed by module perl-DBI:1.641:8010020191113222731:16b3ab4d-0.x86_64

The fix was to run the following command:

#yum module enable perl:5.26

After this, I reran the dnf check and the dependency problems were gone.

Filed under: Linux, Webmastering