Bug 701904 - After upgrade, network printer no longer accessible
Summary: After upgrade, network printer no longer accessible
Keywords:
Status: CLOSED DUPLICATE of bug 647831
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-printer
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-04 08:53 UTC by Reinout van Schouwen
Modified: 2011-05-04 09:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-04 09:35:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Reinout van Schouwen 2011-05-04 08:53:39 UTC
Description of problem:
In Fedora 14 I had two network printers configured which are no longer accessible from Fedora 15. When trying to print to one of them, a notification comes up saying that the printer may not be connected. 
In the CUPS management web interface, the status of the printers is 'Paused - "/usr/lib/cups/backend/dnssd failed"'

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

How reproducible:
Always

Steps to Reproduce:
1. Configure network printer in Fedora 14
2. Upgrade to current Fedora 15 beta
3. Try to use printer in Fedora 15
  
Actual results:
Printing documents fails

Expected results:
Printing works as it did before

Additional info:
I also was unable to add the printer again, as s-c-p didn't find any network printers at all (repeatable between system restarts). I decided to restart the avahi daemon via system-config-services and after that, the network printers suddenly appeared in s-c-p (and worked!) but the old printer definition was still disabled.

Comment 1 Jiri Popelka 2011-05-04 09:35:02 UTC
Most likely duplicate of bug #647831.

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


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