jaunty 64 loses connection with network printer

Bug #371771 reported by Matthew Asnip
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

I have a small office network consisting of my main computer which dual boots Windows and Jaunty 64, another windows computer, and the brother 4070cdw printer. Connected via usb to my main computer, but inaccessible to the network is an HP 6500 Officejet.

My install of Jaunty was fresh, to a pristine hard drive and is current.

Jaunty is showing both printers as available. But when I try to print to the networked Brother printer, I get 'printer unavailable'.

What I expect to happen is for it to print, much as it did yesterday. What I get is for it not to print.

Tags: jaunty
Revision history for this message
Louis-e (robert-louisetienne) wrote :

I would like to state that I am in the same situation. I have a system76 laptop running on Jaunty 64 bit and connected through university network via Wi-fi. We have an Hp 4200 laserjet printer on the network and when i try to print it also state 'printer unavailable'. I have tried all kind of combinations of printer reinstallation to no avail. The printer was working fine under Hardy Heron on the same computer

attached: Error log in french unfortunately:

Monkey (monkey-libre)
tags: added: jaunty
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
Thanks in advance.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage .

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ubuntu:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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