Bug 532754 - Can't discover network hp printer with hp-setup
Summary: Can't discover network hp printer with hp-setup
Keywords:
Status: CLOSED DUPLICATE of bug 531726
Alias: None
Product: Fedora
Classification: Fedora
Component: hplip
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-03 18:01 UTC by Chris Walker
Modified: 2009-11-05 10:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-11-05 10:13:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Chris Walker 2009-11-03 18:01:55 UTC
Description of problem:

Printer discovery doesn't appear to work.  It was working fine in Fedora 11, but in Fedora 12, my HP Photosmart network printer is not found when search for printers.

Version-Release number of selected component (if applicable):

3.9.8-20

How reproducible:

Happens every time hp-setup run.

Steps to Reproduce:
1. Run hp-setup
2. On Device Discovery page, select "Network" and click Next
  
Actual results:

Displays no devices found message.

Expected results:

Printer is found (as it was in Fedora 11).

Additional info:

I was able to set up the printer manually using system-config-printer and selecting new network printer, appsocket/HP JetDirect (but not if I tried to find it).

Comment 1 Tim Waugh 2009-11-04 11:20:52 UTC
What does 'rpm -q selinux-policy-targeted' say? (presuming you are using the default 'targeted' policy...)

Comment 2 Chris Walker 2009-11-04 16:56:07 UTC
It says:

    selinux-policy-targeted-3.6.32-35.fc12.noarch

Comment 3 Tim Waugh 2009-11-04 17:12:14 UTC
Please re-test with a later version of selinux-policy (current version if 3.6.32-40.fc12).

Comment 4 Chris Walker 2009-11-05 03:29:11 UTC
Tried it with 3.6.32-40.fc12.  The problem is now resolved, thanks.

Comment 5 Tim Waugh 2009-11-05 10:13:44 UTC
Great.  Most likely a duplicate of bug #531726.

*** This bug has been marked as a duplicate of bug 531726 ***


Note You need to log in before you can comment on or make changes to this bug.