Closing Ghostscript task as the bug report is very old ...
** Changed in: ghostscript (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/25105
Title:
** Branch linked: lp:ubuntu/foomatic-db
--
incorrect test page printing with SAMSUNG ML1210
https://bugs.launchpad.net/bugs/25105
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
I have checked the PPD file which comes with Jaunty and there the
default value for the halftoning algorithm is Standard. In addition,
Jaunty updates the PPDs for existing print queues when updating the
appropriate packages. So everyone installing Jaunty or updating to
Jaunty should have his ML-121
I have a Samsung ML-1210 and am _still_ getting this problem in
Intrepid. In fact, it was a factor in my getting lost on Saturday
(couldn't read the directions). Changing the halftoning algorithm to
Standard sorted it out, which is great, but _please_ can you fix the
problem for all the people who
** Changed in: foomatic-db
Status: In Progress => Fix Released
--
incorrect test page printing with SAMSUNG ML1210
https://bugs.launchpad.net/bugs/25105
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
u
** Changed in: foomatic-db
Status: Confirmed => In Progress
--
incorrect test page printing with SAMSUNG ML1210
https://bugs.launchpad.net/bugs/25105
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubun
"Standard" was always the intended default upstream. I have found a bug
in the upstream foomatic-db now which caused some drivers to default to
"Accurate". This I have fixed now upstream and it will go into Hardy
with the updated foomatic-db package.
--
incorrect test page printing with SAMSUNG M
Till, can't we let the halftoning algorithm of the gdi driver default to
"Standard" instead of "Accurate" for older Samsung printers?
** Also affects: foomatic-db
Importance: Undecided
Status: New
** Changed in: foomatic-db
Status: New => Confirmed
--
incorrect test page printi
I am using Gutsy with Samsung ML-1210. I have the same problem with page
test and pdf documents.
I fix it with the "Till Kamppeter solution" and set halftoning to
standard.
--
incorrect test page printing with SAMSUNG ML1210
https://bugs.launchpad.net/bugs/25105
You received this bug notificatio
Gutsy has the same problem with the "Accurate" halftoning on my ML-1430.
"Standard" halftoning works, at least on the test page I printed.
Unfortunately, "Accurate" (the broken setting) was the default when I
installed.
--
incorrect test page printing with SAMSUNG ML1210
https://bugs.launchpad.n
If you have access to Gutsy (at least a live CD) try whether the problem
simply goes away in Gutsy. Gutsy uses the new Ghostscript and (at least
for not too old Samsung lasers: 1610, 1710, not 1210) uses the new SpliX
driver.
--
incorrect test page printing with SAMSUNG ML1210
https://bugs.launch
I found this bug report while looking to see if others have had problems
with their Samsung ML-1710, and I can confirm it affects this model as
well. I am using Feisty and the Samsung driver.
Till Kamppeter - I stumbled upon this solution during my troubleshooting when
I noticed it only affecte
I have the same glitch on test page with a samsung ML-1610
** Changed in: ghostscript (Ubuntu)
Status: Incomplete => Confirmed
--
incorrect test page printing with SAMSUNG ML1210
https://bugs.launchpad.net/bugs/25105
You received this bug notification because you are a member of Ubuntu
Bu
** Changed in: ghostscript (Ubuntu)
Sourcepackagename: gs-esp => ghostscript
--
incorrect test page printing with SAMSUNG ML1210
https://bugs.launchpad.net/bugs/25105
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
I have uploaded new test packages (after working out a common concept
with Debian's Ghostscript maintainer):
For Gutsy download all packages from
http://www.linux-
foundation.org/~till/tmp/ubuntu/gutsy/ghostscript/binary/
and do
sudo dpkg -i *gs-esp*.deb *gs-afpl*.deb *gs-gpl*.deb *libgs*.deb
Hendrik van den Boogaard wrote:
> I will try this in some days. However I have a AMD 64 machine, the deb's
> are for .386. Can I just dpkg --force-architecture?
>
This would only work if you have compatibility libraries for 32-bit
software installed. Otherwise rebuild the package from source as
Download all packages from
http://www.linux-foundation.org/~till/tmp/ubuntu/gutsy/gs-gpl/binary/
and do
sudo dpkg -i *gs-esp*.deb *gs-gpl*.deb
to replace your ESP Ghostscript by the new GPL Ghostscript.
--
incorrect test page printing with SAMSUNG ML1210
https://bugs.launchpad.net/bugs/25105
Can you try with the new gs-gpl packages from
http://www.linux-foundation.org/~till/tmp/ubuntu/gutsy/gs-gpl/binary/
--
incorrect test page printing with SAMSUNG ML1210
https://bugs.launchpad.net/bugs/25105
You received this bug notification because you are a member of Ubuntu
Bugs, which is a dir
Can you choose "Standard" in the "Halftoning Algorithm" option (with the
standard Ubuntu PPD file) and see whether this makes the problem going
away?
** Summary changed:
- incorrect test page printing with SAMSUNG ML1210 (on breezy)
+ incorrect test page printing with SAMSUNG ML1210
--
incorre
The attachment (A working ML-1430 PPD (from Fedora Core 3) from a few
posts above seems to solve the bar problem on Feisty Fawn (AMD64) for me
as well!
First I gunzipped the driver from the attachment in /tmp. Then I
installed a new printer, choose the option 'Install Driver'. There I
pointed to /
This bug is probably somewhere in the driver and not in the PPD files.
** Changed in: gs-esp (Ubuntu)
Sourcepackagename: foomatic-filters-ppds => gs-esp
--
incorrect test page printing with SAMSUNG ML1210 (on breezy)
https://bugs.launchpad.net/bugs/25105
You received this bug notification becaus
On Feisty [amd64] this problem is still there. I have a Samsung ML1210
which worked perfectly fine under Dapper. I skipped Edgy and I am now
also noticing the same bar on the test page as well as faulty printed
images when I tried to print those on my clean Feisty install!
However I have not insta
I still see the same issues in Dapper, and the same fix (copying over a
working ppd file) fixes the problem.
I'll experiment when I have time to see if any particular settings fix
the problem or make it worse on my Dapper machine - though the
corruption does show up with the default settings.
--
Here Kubuntu Edgy, Samsung ML-1510
tested also in Kubuntu Dapper
Cups test page prints fine, but pictures print out corrupted. With Samsung
closed source driver even large pictures print fine.
There seems to be some other glitch in Samsung PPD that makes test page to
print too left and too up w
Hi, is this still a problem on Dapper or Edgy?
For Breezy, this is backports material I guess.
** Changed in: Ubuntu
Sourcepackagename: None => foomatic-filters-ppds
Status: Unconfirmed => Needs Info
--
incorrect test page printing with SAMSUNG ML1210 (on breezy)
https://launchpad.net/bug
25 matches
Mail list logo
