Bug 962606
| Summary: | HP Officejet Scanner not detected | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Joshua Rosen <bjrosen> |
| Component: | hplip | Assignee: | Tim Waugh <twaugh> |
| Status: | CLOSED DUPLICATE | QA Contact: | qe-baseos-daemons |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.4 | CC: | jpopelka, nphilipp, repomaint-rhbz |
| Target Milestone: | rc | ||
| Target Release: | 6.4 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-05-17 13:39:27 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Joshua Rosen
2013-05-14 02:40:22 UTC
I've changed the component to hplip as sane-backends hasn't seen an update since GA of RHEL6. The hplip maintainer should be able to tell you the changes made in the package between 6.3 (hplip-3.10.9-3.el6) and 6.4 (hplip-3.12.4-4.el6) and whether this can affect scanning on your device. Another possible error source could be (just speculating) changes in the kernel USB stack. Please check if your problems persists after downgrading alternatively either hplip (and libsane-hpaio) or the kernel packages, or both packages to the versions included in 6.3. I downgraded to 3.10 but the problem persists hpijs-3.10.9-3.el6.x86_64.rpm hplip-common-3.10.9-3.el6.x86_64.rpm hplip-3.10.9-3.el6.x86_64.rpm hplip-libs-3.10.9-3.el6.x86_64.rpm Here is my lsusb output Bus 003 Device 004: ID 03f0:2212 Hewlett-Packard OfficeJet Pro L7600 It's not being detected in Fedora 19 alpha either. Looking back in Bugzilla it looks like I reported this problem in Fedora 17 so it was something that happened around then. BTW the hardware is fine, the webscan function in the HP's web interface works. I did a clean install of 6.2. After the install Xsane and Simplescan worked fine. I updated the kernel, unfortunately kernel upgrades drag a lot of things with them one of which broke scanner detection. After the kernel update the scanner isn't detected by Xsane. It's not the kernel itself, I rebooted into the old kernel and it still doesn't work. I've been running some experiments. I did a clean install of SL 6.2. After the install the scanner was detected and functioned in Xsane and SimpleScan. I then updated the kernel which dragged along a number of other packages but not the hplip packages. After the upgrade the scanner wasn't detected any more. I then did a clean install of 6.3. Once again the scanner worked after the install. I did a couple of reboots and it still worked. I then updated the hplip packages, and only the hplip packages. The scanner was no longer detected by Xsane after the updates. I then downgraded the hplip packages to the original 6.3 packages. That didn't fix the problem, the scanner still isn't detected. I did a reboot and still no scanner. I'm suspecting that it might be a udev file that's getting messed up. It looks like it is hplip or libsane-hpaio. When I downgraded to 3.10 it didn't install libsane-hpaio. When I installed libsane-hpaio and rebooted the scanner worked. Updating to 3.12 breaks it so that's where the problem is. Is there anyway to post a bug do HP? I don't see any means of doing so on the hplip webpage. I removed hplip-3.12 from my 6.4 system and installed the 3.10 RPMS from 6.3, hpijs-3.10.9-3.el6.x86_64.rpm hplip-common-3.10.9-3.el6.x86_64.rpm libsane-hpaio-3.10.9-3.el6.x86_64.rpm hplip-3.10.9-3.el6.x86_64.rpm hplip-libs-3.10.9-3.el6.x86_64.rpm Now the scanner works in 6.4. (In reply to comment #7) > Is there anyway to post a bug do HP? https://bugs.launchpad.net/hplip/+filebug Make sure you are able to reproduce the problem when you remove RHEL's packages and install latest hplip via their 'Automatic Installer' (http://prdownloads.sourceforge.net/hplip/hplip-3.13.5.run) before reporting it, because they'll tell you to do so anyway. One SL 6.4 user with this problem managed to get his scanner detected by adding his unix user name to the 'lp' group in /etc/groups, see: http://scientificlinuxforum.org/index.php?showtopic=2292&view=findpost&p=15475 Maybe this piece of info helps in tracking down the bug. Adding my user name to the lp group fixed the problem. I first tried installing the latest version of hplip (hplip-3.13.5_rhel-6.0.x86_64.rpm) from the launchpad site. That fixed the problem but it wasn't the new code, it was because their RPM installs something that checks to see if a user is a member of the lp group and if not asks to add them to it. On a separate system I did a clean install of 6.4, the scanner didn't work with the default setup. However when I added my user name to the lp group, logged out and then logged back in, the scanner was detected. To me it seems that the device(s) in question aren't recognized by the udev rules as having a scanning function (and permissions aren't opened up to logged in users). By adding yourself to the "lp" group you get the direct access to the device file you need for scanning. Tim, what do you think? This looks like a duplicate of bug #905143. *** This bug has been marked as a duplicate of bug 905143 *** |