Closed
Bug 603182
Opened 14 years ago
Closed 2 years ago
Cannot print calendar to network printer
Categories
(Calendar :: Printing, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: carlson.dl, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 Build Identifier: Lightning beta 2 I am using foxyproxy to route Thunderbird e-mail through Polipo on localhost:8118. My system is Windows XP SP3 and I have Thunderbird 3.1.4 with the Lightning beta 2 Calendar. Thunderbird can print e-mails to a printer on my local network while Foxyproxy is enabled, but when I try to print a calendar, the print request goes to Foxyproxy/Polipo instead of the windows printer definition and I get the error 504 Connect to 192.168.1.45:80 failed: General SOCKS server failure from polipo. Reproducible: Always Steps to Reproduce: 1. Open a view of a local calendar in Thunderbird with Lightning 2. Choose File:Print. In the Print Preview window select Print. 3. In the Windows Print Dialog select a network printer that has a locally defined 'Standard TCP/IP Port'. Choose a printer other than the current default printer. 4. Watch the Error 504 pop-up appear from Polipo. Actual Results: Error 504 pops up from Polipo with the printer TCP/IP address. Expected Results: The printer selected in the windows print dialog should print the calendar document If the printer selected in the windows print dialog happens to be the current system default printer, the calendar document prints as expected. Because the printer was not selected prior to showing the preview, pagination details are not shown in the preview.
Reporter | ||
Comment 1•14 years ago
|
||
I was told that this is not the same as bug 351581
Version: unspecified → Lightning 1.0b2
Comment 2•2 years ago
|
||
The reporter is gone, the report is rather old and no other reports on file. Resolving as INCOMPLETE.
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•