Comment 6 for bug 1668000

I believe I encountered this bug yesterday will a newly-unboxed
OfficeJet 8710. When I attached the all-in-one via USB for the first
time, it identified itself (in its USB device descriptor) as an
OfficeJet 8500 A909g. (At least, that's what `lsusb -v` said.) At that
point, neither scanning nor printing worked over USB, but I was able to
get both to work by using Ethernet instead.

However, I've since rebooted the printer, and the problem seems to have
resolved itself. `lsusb -v` now shows the correct product name, and
both printing and scanning work over USB now.

I observed the bug after connecting to the printer while it was booting
for the first time, so this may just be a first-start problem. Also,
think I left the printer connected to Ethernet for at least an hour
before rebooting it, so for all I know it may have fetched a firmware
update in that time.

HTH,
Daniel G.