[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2008-03-28 Thread Launchpad Bug Tracker
This bug was fixed in the package samba - 3.0.28a-1ubuntu3 --- samba (3.0.28a-1ubuntu3) hardy; urgency=low * debian/patches/fix-smbprinting-os2.patch - Fixes printing large documents from OS/2. (LP: #60931) -- Chuck Short <[EMAIL PROTECTED]> Fri, 28 Mar 2008 08:37:31 -0400

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2008-03-28 Thread Chuck Short
Working on intentraging this patch right now. Thanks chuck ** Changed in: samba (Ubuntu) Status: Confirmed => In Progress -- Printing only works for PostScript files or CUPS' own test page https://bugs.launchpad.net/bugs/60931 You received this bug notification because you are a member o

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2008-03-28 Thread Till Kamppeter
Great, TEN, thank you very much for telling us about the patch. Then it is no problem to get this fixed in Hardy. I have milestoned this bug for Hardy now. ** Changed in: samba (Ubuntu) Importance: Medium => High Target: None => ubuntu-8.04 -- Printing only works for PostScript files o

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2008-03-28 Thread TEN
Fix at https://bugzilla.samba.org/show_bug.cgi?id=5326#c3 (patch https://bugzilla.samba.org/attachment.cgi?id=3220&action=view) -- Printing only works for PostScript files or CUPS' own test page https://bugs.launchpad.net/bugs/60931 You received this bug notification because you are a member of U

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2008-03-25 Thread Till Kamppeter
** Changed in: samba (Ubuntu) Sourcepackagename: foomatic-filters => samba -- Printing only works for PostScript files or CUPS' own test page https://bugs.launchpad.net/bugs/60931 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubunt

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2008-03-15 Thread TEN
Reported upstream in https://bugzilla.samba.org/show_bug.cgi?id=5326 -- Printing only works for PostScript files or CUPS' own test page https://bugs.launchpad.net/bugs/60931 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2008-03-14 Thread TEN
According to testing of smbclient print commands against several OS/2 systems (conducted through irc://irc.freenode.net/#samba-os2), larger jobs will be broken in at an (erroneous) upper size limit of 73 to 126kB (the precise figure is apparently machine-dependent). If one is lucky, the printer wi

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2008-03-07 Thread TEN
The following does work, making Samba (alone) an unlikely culprit. smbclient //myhost/myprinter Password: smb: \> print job.ps Error writing file: SUCCESS - 0 putting file job.ps as job.ps (984.4 kb/s) (average 984.4 kb/s) smb: \> quit -- Printing only works for PostScript files or CUPS' own te

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2008-03-07 Thread TEN
It is (presumably depending on the job size) and the above "absolution" for Samba was premature, as some PS files will print through smbclient at least, while most others won't. The Samba part of the issue probably ought to be addressed in #samba- technical and #samba-os2 on the FreeNode.net IRC a

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2008-03-06 Thread TerryG
Marked as Confirmed since this seems to be an intermittent issue. ** Changed in: foomatic-filters (Ubuntu) Status: New => Confirmed -- Printing only works for PostScript files or CUPS' own test page https://bugs.launchpad.net/bugs/60931 You received this bug notification because you are

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2007-10-12 Thread TEN
This issue had been auto-expired unresolved but persists. Any info appreciated on how to proceed for debugging (jobs get lost/garbled somewhere between CUPS and smbclient printing). ** Changed in: foomatic-filters (Ubuntu) Status: Invalid => New -- Printing only works for PostScript file

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2007-09-21 Thread Launchpad Janitor
[Expired for foomatic-filters (Ubuntu) because there has been no activity for 60 days.] -- Printing only works for PostScript files or CUPS' own test page https://bugs.launchpad.net/bugs/60931 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2007-05-18 Thread TEN
The start of each job actually does seem to get sent to the printer, as the HL-1650's LCD shows a green (i.e. informational) message such as "18 user SomeSite", i.e. apparently a job number followed by the user name and job name. Apparently the printer detects and discards the subsequent data as ga

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2007-05-12 Thread TEN
I'm afraid there is currently no way to attach this printer to a local parallel port - the systems are at opposite ends of the network and premises, and rather immobile. Suffice it to say that printing does work from Windows (both PostScript and PCL) as well as from other Linux systems (even ancie

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2007-05-09 Thread Till Kamppeter
Can you try to connect the printer directly to your computer? Does it work then? Can you check the printer settings on the Windows server? For printing from non-Windows clients you need to tuyrn off bi-directional printing on your Windows server. ** Changed in: foomatic-filters (Ubuntu) S

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2007-05-06 Thread Pascal De Vuyst
I think you provided enough information to confirm this bug. ** Changed in: foomatic-filters (Ubuntu) Importance: Undecided => Medium Assignee: Pascal De Vuyst => (unassigned) Status: Needs Info => Confirmed -- Printing only works for PostScript files or CUPS' own test page https:

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2007-05-06 Thread TEN
...whereas using the manufacturer-supplied PPD from http://solutions.brother.com/Library/sol/printer/7050/rpmfiles/brhl16_2-1.0.0-0-noarch.rpm (as referenced by http://openprinting.org/show_printer.cgi?recnum =Brother-HL-1650 - can only be unpacked / opened in "File Roller" / "Archive Manager" afte

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2007-05-06 Thread TEN
Using the PPD recommended above, the print job disappears without any apparent trace (no error recorded anymore in /tmp/foomatic-rip.log). With the alternate driver, the attached log files/dumps are generated (see last entry on each), and a page is printed which reads: PCL XL error

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2007-05-05 Thread Pascal De Vuyst
Please try another driver. Do you have the same problem with the PPD provided by Brother on the CD that came with your printer or can be downloaded from the Brother website according to http://openprinting.org/show_printer.cgi?recnum=Brother-HL-1650. Your printer also supports PCL6 and should the

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2007-05-05 Thread TEN
Attempting to print this very page from within Firefox (having incremented the above debug level) results in a /tmp/foomatic-rip.log containing [...] renderer command: level=0; /usr/bin/printf "%%!PS\n \n<>setpagedevice\n"; if [ $level -gt 0 ]; then if [ $level -lt 99 ]; then level=" -dLa

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2007-05-05 Thread TEN
...as per https://wiki.ubuntu.com/PrintingBugInfoScript ** Attachment added: "printingbuginfo.txt" http://librarian.launchpad.net/7564515/printingbuginfo.txt -- Printing only works for PostScript files or CUPS' own test page https://bugs.launchpad.net/bugs/60931 You received this bug notifica

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2007-05-05 Thread Pascal De Vuyst
Reopening this bug. Reassigning to foomatic-filters. > I [05/May/2007:16:00:49 +0200] Hint: Try setting the LogLevel to "debug" to find out more. Please attach the output of the printingbug info script and your cups error log with LogLevel set to debug as described here: https://wiki.ubuntu.com/D

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2007-05-05 Thread TEN
Problem subsists in Ubuntu 7.04 "Feisty Fawn". /var/log/cups/error_log has this: I [05/May/2007:16:00:49 +0200] Adding start banner page "none" to job 8. I [05/May/2007:16:00:49 +0200] Adding end banner page "none" to job 8. I [05/May/2007:16:00:49 +0200] Job 8 queued on "HL-1650" by "user". I [0

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2007-04-25 Thread Brian Murray
We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future. ** Changed in: cupsys (Ubuntu)

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2007-03-20 Thread Brian Murray
Thanks for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance. ** Changed in: Ubuntu Sourcepackagename: None => cupsys

[Bug 60931] Re: Printing only works for PostScript files or CUPS' own test page

2006-09-17 Thread TEN
The suspects - and indeed they've tried to escape: " vs. ' In /tmp/foomatic-rip.log we have: renderer command: level=0; /usr/bin/printf "%%!\n \n<>setpagedevice\n"; if [ $level -gt 0 ]; then if [ $level -lt 99 ]; then level=" -dLanguageLevel=$level"; else level=""; fi; gs -q -dPARANOIDSAF