Adobe Acrobat at fault

Adobe Acrobat is the defacto standard for reading pdf documents.  After all, Adobe created the pdf file format.  But the product has recently suffered so many security flaws that many security conscious IT pros won't use it.  However, sometimes you can't get around the fact that Adobe requires the use of their product to read/use documents created by their products.  In other words, their Adobe Creator product embeds proprietary features that make documents unusable with any other reader.  Fillable legal forms put out by the Massachusetts Probate Court are such an example.  This is just wrong.  But I'll leave that discussion to another day.  There are two issues that I wanted to highlight as examples of how bad the Adobe Acrobat software has gotten.

CPU hog

One is that the program consumes way too many resources at idle.  If you merely open Adobe Acrobat, it can and will send your system CPU to full throttle.  I'll upload images that show how my system CPU and temperature sensors spike immediately after opening Adobe Acrobat.  This is bad.  This software doesn't really have to do any heavy lifting, but by using it, you could risk a thermal failure at worst, and at best you'll have a sluggish, unresponsive system.

Bash broken. Adobe Acrobat did it.

The second point is one that I discovered today.  When installing Adobe Acrobat on (Ubuntu) Linux (using Adobe's installer), you get a file called /etc/bash_completion.d/acroread.sh.  This file messes up bash completion so that when trying to use the tab key for normal pathname expansion, it inserts an extra space at the end of the line.  And it removes any backslash escape characters that would normally be inserted automatically.  In other words, Adobe Acrobat breaks your everyday usage of the command line on Linux.  If you have this problem, you can fix it by removing the binary and installing from Canonical sources.  (Yes, Canonical cleans up after the mess that other software vendors create.)  If you need the latest bleeding edge binary straight from Adobe, you can delete the acroread.sh file and then "source" /etc/bash_completion.  

This is a known (easy to fix) bug at Adobe, but after two years in the wild, it doesn't seem like Adobe wants to fix it.  Do you know bash glob setting syntax and can spot why their script is broken?

Tags: