Last week I reported on a bug introduced in Chrome OS 97 causing Chromebooks to not print to HP printers. The main commonality among the affected devices was they used ARM-based processors. Today, Google merged a fix for the Chrome OS 97 printer bug after testing the solution.
Here’s what caused the problem along with an explanation of why this bug made it out to the Chrome OS 97 Stable Channel:
The configure script always adds python to the list of linked libraries even though hpcups doesn’t need it. On x86, the linker removes the unused dependency, but the arm linker doesn’t. This causes the hpcups filter to crash at startup on production arm images. Since neither hpcups nor hpps need python to build, remove it from the build flags entirely. This wasn’t caught during testing because test images have python installed, so the hpcups filter appeared to work correctly.
Essentially, the test devices weren’t configured exactly like a Chromebook in the field, so the Chrome OS 97 printer bug was missed.
I don’t know if Google will immediately push the fix for the Chrome OS 97 HP printer bug. We’re very close to seeing Chrome OS 98 rollout. It’s been nearly four weeks since Chrome OS 97 arrived and we’re on a four-week software update cycle now.
I’d like to think that a small update does get pushed out sooner since I don’t expect Chrome OS 98 to arrive for about a week or so.
The fix has been merged into Chrome OS versions 98 and 99 as of now so this doesn’t happen again over the next two months. Presumably, test devices will be configured to be more like Chromebooks in the wild as well. However, that’s not always easy to do: Testing efforts often require additional software to actually run automated test cases.
7 Comments
Fun Q for U: Do you think Alphabet is planning any special additions for Chrome OS 100 that will surprise us? Or are they not really into that kind of thing?
Maybe Chrome OS 100 brings Steam gaming to Chromebooks. The only surprise there is which version will deliver it though. We know it’s coming. Other than that, I don’t expect anything special for Chrome OS 100.
The normal 4 week update cycle may be in jeopardy. Canary has been stuck on the same point version for possibly as much as 3 weeks. Canary is usually updated daily and occasionally more often. I reported a camera bug, but I am guessing there was more beyond that issue. A curious thing is that Dev has a slightly higher point version of Chrome OS than Canary. Don’t think I have ever seen that. It has been well over a month since Canary hit 99 so I will expect that things might slip for the future updates.
Not having a test cycle which utilises a production environment seems to be a fundamental flaw.
Version 98.0.4758.91 (Offizieller Build) (32-Bit), acer Spin 513, Qualcomm Snapdragon 7180c lite Prozessor it works again, it is printing!
When will I see the Version 98.0.4758.91 update? I have checked and it is not available yet. I am still having printer problems and I have the Version 97.0.4692.102 and it states that there are not available updates yet.
So I have a Chromebook OS & I cannot print to my HP 8710 wireless printer. I thought I had it fixed by removing an extension, but it’s started back up & not printing again. What’s the deal? How do I fix it?