From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id A4E05139083 for ; Thu, 21 Dec 2017 22:46:10 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 55564E0FFA; Thu, 21 Dec 2017 22:46:04 +0000 (UTC) Received: from mail-qk0-f174.google.com (mail-qk0-f174.google.com [209.85.220.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E8D17E0FE6 for ; Thu, 21 Dec 2017 22:46:03 +0000 (UTC) Received: by mail-qk0-f174.google.com with SMTP id q14so20058618qke.7 for ; Thu, 21 Dec 2017 14:46:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:in-reply-to:message-id :mime-version:content-disposition:content-transfer-encoding; bh=gmXmRb5VPxGQYEk6ZpcOXrldk8PS98h9mgXLxtoXHOo=; b=Kdq6ejXKzCAh55QgXmxDEVqrw97Vi8cDTPLkV2QWDw7LsS87pQGy2lQn+jRz2RJLFF HPpHjlIh61PgXndq/InrftdjqDl5SHvqhZefNuQeKl4WtSjk9ZU0jIYn7vJYHsG0xJBR H0dD0/KFmkcFs30Lwg5kUpVcJmDq9r64epl5h3vt97Fit/dPn5yhOa0l4Vj6uwyG+GjW gl0rIJg8BvCzyHAs2CDm0anvrwogRUFpx0Ui01mr49/eNx1mhJzZUYCjhgX25iFOSimD Ff8WWK5jDIkc/L+mR0nFYmPtIP5qAED2PjZe4RuRVCO4PekEwsba44DRVPBV0rZfwlBy dhtw== X-Gm-Message-State: AKGB3mJ0c2Bg9gquV2wOvJALzXQuvPalAR19v3Niy7MX5vxoroixOBTa fp2b3VJbeFIab82MEzwcNQZzNrrJ X-Google-Smtp-Source: ACJfBotcBofRSDrC/TXdsfYLhMV+/3TL3jZzbuO7k25H+U0uwBfam+847EzEu1O+s86W4x8muC6IiQ== X-Received: by 10.55.157.86 with SMTP id g83mr16342793qke.280.1513896362785; Thu, 21 Dec 2017 14:46:02 -0800 (PST) Received: from ffortso4 (c-76-23-130-96.hsd1.ct.comcast.net. [76.23.130.96]) by smtp.gmail.com with ESMTPSA id v73sm2870907qkg.34.2017.12.21.14.46.02 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 21 Dec 2017 14:46:02 -0800 (PST) Date: Thu, 21 Dec 2017 17:46:01 -0500 From: Jack Subject: Re: [gentoo-user] What can cause printer to crop top of page? To: gentoo-user@lists.gentoo.org In-Reply-To: <3688036.gnV2oWbRCy@dell_xps> (from michaelkintzios@gmail.com on Thu Dec 21 17:35:59 2017) X-Mailer: Balsa 2.5.3a-270-g188512be Message-Id: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Archives-Salt: c4e897ea-389e-449d-8b73-512a166a04ab X-Archives-Hash: 3d1b5e6d9f046b65850b5951d57ab119 On 2017.12.21 17:35, Mick wrote: > On Thursday, 21 December 2017 21:24:57 GMT Jack wrote: > > I may be grabbing at straws here, but what happens if you print > > something in landscape? Is the trimmed edge the new top (long =20 > edge) or > > still the same short edge? >=20 > Aha! Good call. In landscape the cropping takes place on the left =20 > (short) > edge, not the top of the page. >=20 >=20 > > Does the same happen with other apps? browser, emacs, gimp (just =20 > make > > a simple line drawing), pdf display, image viewer, ...? I'm =20 > thinking > > of printing things that originate as different image types - maybe =20 > one > > will behave differently and point to something in the process. Can =20 > you > > send a plain text file to the printer with lp? >=20 > I sent a page with Chromium in landscape, it cropped the left hand =20 > short edge > too. >=20 > PDF readers print with cropped top, in portrait. >=20 > I sent a txt file with 'lpr -o fit-to-page' in portrait and the same =20 > cropping > on the top of the page happens. If the actual text was sent to the printer (and not turned into ps or =20 pdf first, then I blame the printer. >=20 > So it is not application specific, but page orientation specific. No, it always happens on the first short edge to come out of the =20 printer, no matter which way the pixels are oriented. That (to me) =20 rules out everything except the printer, and just possibly the printer =20 driver. >=20 > Could it be something has gone wrong with the rollers? This is a =20 > brand new printer! Possibly, but my guess is some internal printer setting. Does the =20 printer itself provide a web interface? If so, hunt through the =20 options. You may find something there. (I'm not familiar with that =20 printer, but all of the few wireless printers I have worked with =20 provide a web interface on their configured IP address.) >=20 > I'll try to print a page with MSWindows tomorrow, if only to prove if =20 > this is > a cups problem or not. >=20 > Thanks for your suggestions! > -- > Regards, > Mick =