Ongoing problems connecting a Canon CanoScan 4400F scanner to Linux Mint

This post is about the experiences I've had connecting a Canon CanoScan 4400F scanner to various computers, primarily focusing on my current laptop which, as of the time of first writing this post, ran Linux Mint 19 "Tara" MATE along with Microsoft Windows 10. For context, I am hoping to scan some of my personal & work notebooks for personal archival. I figured that this scanner, which I've had for a long time, does a good job at rendering images, even though it is quite old & slow, so I should continue using it for as long as it continues to work.

I used to use this scanner regularly with my previous laptop, which is an ASUS U30Jc and, when I last ran it regularly, ran Linux Mint 18.3 "Sylvia" along with Microsoft Windows 7; initially when I connected the scanner to the old laptop (a few years ago), it didn't work with Linux Mint out-of-the-box, so I decided to do all scans in Microsoft Windows and then transfer files between partitions later. I stopped using that laptop approximately 2 years ago, and since then until the beginning of this month, it just sat in a box gathering dust. At the beginning of this month, desirous of using this scanner again for the aforementioned purposes, I brought out the old laptop & scanner, but found out that in the intervening 2 years, the damage to the laptop's screen & hinge had worsened, the battery had completely died due to no charging in that time, and the laptop (on either OS) would randomly overheat & shut off. At this point, I now believe that old laptop should be junked.

My current laptop is an ASUS ZenBook UX331UN. I didn't think the scanner would work with it, because it uses USB 1.1, and I remember having trouble getting this laptop to read an older USB device. Just for the heck of it, I decided to connect the scanner to see what happens. Just as with my old laptop, in Linux Mint, the Simple Scan application didn't find any connected scanners. However, I had the idea to run the command "sudo simple-scan" from the terminal. That showed that the scanner was in fact being recognized, so this was probably a permission problem; I also realized that the earlier problem with another old USB device was specific to that device and not a general issue with this laptop reading any older USB device. That said, when I tried to scan a document, I got a window showing the error "Failed to scan: Unable to connect to scanner". Follow the jump to see more.

Featured Comments: Week of 2010 December 19

Unfortunately, there were no comments on articles from the previous week (2010 December 12), so there was no accompanying "Featured Comments" article. That can be attributed to the fact that I wrote very few posts that week. Anyway, there were a whole bunch of comments this past week, so I can only post a couple.

Review: Slackware 13.1

There were many comments about this, so I'll post a couple, as well as my responses to them.
An anonymous reader writes, "You never even talked about this distro whatsoever. You just complained about what stuff you were used to that slackware didnt have. if every distro was the same then there would be one distro. Slackware is one of the most stable distros still surviving. You want a extremely stable distro here it is. While i agree that there is no dependacy checking, if you are going to slackware you are usually semi good at the command line and usually know how to install a program anyhow. so its "your" job to do it."
Reader Hannes Worst had this to say: "I think it's an ultimately unfair review. It only states the preferences of the writer and nothing about Slackware. It's like someone allergic to fruit writes a review about apples. From the first sentence on prejudice is shown. When you aren't capable of exploring and researching Slackware, don't write a review about it."
To the anonymous reader, I ask, if complaining about what isn't in the distribution isn't saying something about the distribution itself, then what is? Also, the last point leads me into my response to Hannes Worst.
I may not have made it clear in the review itself, but relatively speaking, I am a newbie to Linux. I like using Linux a lot, but I still have neither the skills nor the patience to work with something like Slackware for a long time just to get it working. I had a feeling that my experience wouldn't turn out so well for this very reason. But I wanted to test this feeling, so I did; I then wrote about the experience. Please tell me: what exactly is wrong with that? I figured that I made it abundantly clear that my issues with Slackware were never meant to reflect poorly on Slackware; quite the opposite: they reflect poorly on me as a Linux user.
I hope all that is cleared up. Next!

Familiarity Breeds Fondness, not Contempt

Reader T_Beermonster had this to say: "Probably the big one for me is the package manager. I've just got so used to APT over the years that I find other (probably equally good) systems don't feel right. Kind of like getting into someone else's car, the biting point is wrong and the seat is the wrong hight." I feel the same way as well, but I must ask, what about when familiar front-ends are applied to different back-ends? For example, PCLinuxOS uses RPMs in the back-end, but its GUI package manager is the familiar Synaptic. How would you feel about using that there? Or am I missing the point entirely?

Bad Experiences are Forever

Reader T_Beermonster wrote a long diatribe against Apple's Macs: "I have a visceral loathing of Apple Macs - not the hardware which in recent times has been quite attractive looking (if overpriced/underspecced). It's the OS."

FOLLOW-UP: Linux and Breakfast Cereals

Commenter twitter had this to say: "Diversity and choice are good, restrictions are bad. Despite the differences between distributions, they all share the same core of free software and all of it tailored to a wide variety of hardware architectures. That means that users get the software they want on the platform they want. Skype is difficult because it is not free software and the company has to do all the hard work of packaging things themselves. If you want Skype to work as well as Mozilla, ask Skype to liberate their code and rely on an honest service model that does not demand undue power over users."

Well, that's all for this week. I hope all the confusion surrounding my motivations regarding the Slackware review are cleared up, and I sincerely apologize for not delivering adequately to those who were expecting a more substantive level appropriate for an intermediate or advanced Linux user trying Slackware. As always, if you like the content, please continue commenting and subscribing. Finally, happy holidays!

Bad Experiences are Forever

This is a sort of follow-up and is opposite to the previous post. There are a couple things that I had bad experiences with that I should probably try out again; these things have probably left worse impressions on me emotionally than rationally.
First is Toyota. Toyota has had a rough couple years, starting with issues of premature rusting in its trucks' frames and leading up to the "unintended acceleration" fiasco. Through it all, it's managed to become #1 in sales, but this too has come at the cost of its quality; now, the parts it uses especially in the interiors of its cars are flimsier and aren't assembled with the same attention to detail as before. My family owned a 1988 Toyota Corolla, and it ran beautifully until 2004; it was solidly built, and the attention to detail was striking. Now, no more. That said, the unintended acceleration fiasco (which pushed my skepticism of Toyota over the edge) is finished and its new cars are pretty solidly built and competitive, so I really shouldn't instinctively turn me away from all Toyota products (though I'd still rather wait a few years before recommending their products to anyone again).
Next, Fedora. I tried the Fedora 11 "Leonidas" GNOME live CD about a year ago, and I loved it. I really liked the fact that it, unlike Linux Mint 7 "Gloria", detected all of my hardware out-of-the-box (including my graphics card and monitor at its native 2048 by 1536 resolution). So I decided to install it. That was a terrible idea: not only did it fail to install properly, it also managed to mess up my existing Linux Mint 7 partition at the same time. I tried again, and it still didn't work. I then decided to hold off until the next release. Version 12 "Constantine" was worse; no live CD or live USB I created (the usual way) would boot. That's when I gave up on Fedora. That said, just about a week ago, I and a friend of mine (who is a Red Hat/Fedora guru) installed Fedora 14 "Laughlin" GNOME on a mutual friend's laptop (which was suffering from a slow and malware-ridden installation of Microsoft Windows 7). The installation itself worked flawlessly, and aside from multimedia codecs (which was easily fixed through the handy program Autoten), everything worked out-of-the-box — Skype (i.e. webcam and mic), printing (and scanning), desktop effects, etc. Given this, I really shouldn't hesitate, yet I still do. Maybe it'll happen when Fedora does actually support NVidia's Optimus technology.
Finally come laptop touchpads. Wait, no — those are ergonomically inferior to external mice. Whoops! (Heh heh.)
So what are your thoughts on this? Do you also dislike things more emotionally than rationally? Share your thoughts in the comments below!