xsane does not recognize HP

Bug #135194 reported by Spenser Gilliland
22
Affects Status Importance Assigned to Milestone
xsane (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I'm not sure where to report this.

My All in one printer-scanner-copier HP Photosmart C3100 installs the print driver perfectly from the automated plug and play install. However, when I open xsane it does not detect the scanner that was auto installed.

Willing to giving any information you may need to remedy the problem.

Revision history for this message
Vincent Legout (vlegout) wrote :

I associate this bug with xsane.

Guybrush88 (guybrush)
Changed in xsane:
status: New → Confirmed
Revision history for this message
Guybrush88 (guybrush) wrote :

same problem here

Revision history for this message
Dirk Tas (dirk-tas) wrote :

Problem is the same here but now in Hardy Heron Beta, in Gutsy Gibbon my C3170 Printer/Scanner worked perfectly, my printer was recognized and my scanner was recognized and worked well, in Hardy my printer is automaticly recognized when connecting the usb port but the scanner is not recognized and does not appear if I do a lsusb.

Revision history for this message
Mackenzie Morgan (maco.m) wrote :

Problem exists with PSC 1610 as well. Regression from Gutsy to Hardy.

Revision history for this message
Frédéric Petit (fraiddo) wrote :

Same problem with a HP PSC 1410 on hardy. Regression from Gutsy to Hardy.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Works for me with HP 3380 connected to a JetDirect box using Kubuntu and Kooka.

Revision history for this message
Kivech (kivech-deactivatedaccount) wrote :

I had the same problem with my HP PSC 750 and after a lot of research I finally found out that both packages "sane" and "sane-utils" were not installed by default in Hardy. After manually installing both my scanner worked like before.

It might be worth a try to see if this solves your issues with HP scanners.

Revision history for this message
Martin Pitt (pitti) wrote :

I believe this is fixed in the latest hplip package in Hardy, please see bug 195782. Please report back if it still does not work for you.

Changed in xsane:
status: Confirmed → Fix Released
Revision history for this message
Mackenzie Morgan (maco.m) wrote : Re: [Bug 135194] Re: xsane does not recognize HP
  • unnamed Edit (189 bytes, application/pgp-signature; name=signature.asc)

On Wed, 2008-04-09 at 00:42 +0000, Martin Pitt wrote:
> I believe this is fixed in the latest hplip package in Hardy, please see
> bug 195782. Please report back if it still does not work for you.
>
> ** Changed in: xsane (Ubuntu)
> Status: Confirmed => Fix Released
>

My system's fully up to date, and what's installed does not recognize
the scanner. Setting it up on Gutsy with HPLIP worked. The new thing
that's replacing HPLIP doesn't work. When I install hplip-gui and run
hp-toolbox, in the terminal it says:

error: Unable to communicate with device (code=12):
hp:/usb/PSC_1600_series?serial=MY5CAF215KL0
warning: Device not found

I assume it is referring to the printer I setup using the new CUPS GUI.
It seems these two do not play together nicely. The new CUPS thing is
nice in that it shows networked printers. The old HPLIP was nice in
that it could find scanners and report on ink level status. Neither
really does the whole job.

--
Mackenzie Morgan
http://ubuntulinuxtipstricks.blogspot.com
apt-get moo

Revision history for this message
Kivech (kivech-deactivatedaccount) wrote :

Did you check your user's permissions?

There was a bug earlier in beta where the user was not automatically added to the groups "use tape drives", "use scanner" and "send and recieve faxes".

I had the exact same error message and adding those groups to my profile fixed it, the detection part that is. The sane and sane-tools actually allowed my scanner to scan, albeit not always reliably.

Go to: System>Administration>Users & Groups, unlock and enter your password, select your user and click properties, then on the second tab select all groups that haven't been selected. Make sure you relog, and then try to see if your scanner does get detected by the system.

Good luck.

Revision history for this message
Martin Pitt (pitti) wrote :

This is a duplicate of bug 195782 then. Can you please followup there, especially with the debug information I asked on that bug? THank you!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.