From owner-freebsd-questions@freebsd.org Tue Jan 29 21:08:35 2019 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CAF3614CBAD6 for ; Tue, 29 Jan 2019 21:08:35 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5635E6B606 for ; Tue, 29 Jan 2019 21:08:34 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.193.226.69]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPA (Nemesis) id 1MsZBb-1h91BJ3OhP-00u147; Tue, 29 Jan 2019 22:08:18 +0100 Date: Tue, 29 Jan 2019 22:08:17 +0100 From: Polytropon To: byrnejb@harte-lyne.ca Cc: "James B. Byrne via freebsd-questions" Subject: Re: Cannot print from mate desktop Message-Id: <20190129220817.4ba4fec2.freebsd@edvax.de> In-Reply-To: <89d35da1979a0e295bce2d3f272b285c.squirrel@webmail.harte-lyne.ca> References: <89d35da1979a0e295bce2d3f272b285c.squirrel@webmail.harte-lyne.ca> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:kHoT3Hy+pr/B/Xg0YSMPG7tW6yV1unv3iYXjUqPM0ql2eGsnEr0 6nLdPo/rt2qBziStbiQbzKwWFTcM6MPLsZP2eTOS0BGNEDImrS05PBt430c0xhBoN6s4/2+ sdr9aOJPjssMInfTRmj+bLQI3haRqZyXgRiOrbGfJafqw2CXIJaHidY4daBNHrW8TxZLkhv mCgS8nV7wOXkSDXHbDUXw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:poRgqe+hHL0=:cJW08xb3wrcf0EEMwa23Hb /RuJC6OlREJ8QWMKQ034peLdeOgIA9b0OBsl+ru8VCr559cP0mdG9ZsAXUYnzAZdyac1RVMoD AgFMk+DGa/mtkG0slFx9gwUqicltHN6pX4soGO7pkLBo11siNNkTUHccaeFOq2Ihy77Eu1el0 5Oq54kmnVkbDsKMjj5RNPaZ0iGv6+q1GykUoszf+SssDDoWvOAip1AYg6voOabB0AdljGlQ7m QzWpErEx6ebPenVUvAxauyZmCIepybIb7D5NnED8ujGDVW61k/BWFRZBtSh910dE4egkuVc2V 0NlEHOPHrC61KT2urYl/kLDARG6qSnnfBXYcZDERN+vgkvrBDqbaeycql9MsSXLCurThf08LH wuFWPXStOHl4SGWv8BgNn53mWn2swW/auZu12te98OYfu2yHvBjwT1de5xRLmTXbeRDIlADya 2ukXxJxI3BOVqO9FRjopmU1nq/BGKMqn9fI7ZReSRhKpnH/TXKV2Rmg733crO4so7ip27+oqh BSFrpMRj+yVMyMCnSLNhE88RX8vChIEUdB7RLS9rfjveGVzhnA48s39F5NBUFU3olGau31Y5U Rh7kIG+7NO0w8/0ItrsyE6Ar7npfHWlmJR77jMV0RxVxZMW4BMgcvOROYrQKxEPx2tPpiVQ9u V91vmZn96bmYBglM88Q/VEV20PZrSAjUiMO7E8T8NnsKD2ki46qYceMAFnUMHJK8FeBiDgo3u eId6j4r5s9HYYaG6u2sQ+XiuxWJVsZobDwoP2W/1JihkN1vhNIYcMqT2HOA= X-Rspamd-Queue-Id: 5635E6B606 X-Spamd-Bar: +++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [5.21 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[freebsd@edvax.de]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_ORG_HEADER(0.00)[]; MX_GOOD(-0.01)[cached: mx01.schlund.de]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; MIME_TRACE(0.00)[0:+]; RECEIVED_SPAMHAUS_PBL(0.00)[69.226.193.92.zen.spamhaus.org : 127.0.0.10]; ARC_NA(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.59)[0.592,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[edvax.de]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.96)[0.956,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.99)[0.986,0]; MID_CONTAINS_FROM(1.00)[]; RCVD_IN_DNSWL_NONE(0.00)[187.126.227.212.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(0.28)[ipnet: 212.227.0.0/16(-0.71), asn: 8560(2.14), country: DE(-0.01)] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2019 21:08:36 -0000 On Tue, 29 Jan 2019 15:49:50 -0500, James B. Byrne via freebsd-questions wrote: > FreeBSD-11.2p8 > > Following a massive pkg update this morning, followed by a > freebsd-update install and restart, I now discover that I cannot print > from the mate desktop. When I print from any application on the > desktop, libreoffice, pluma, firefox, the printer dialogue shows up, > the print job is generated, but nothing prints on the printer. Nor > can I find any printer management applet in the toolbar. > > I can print test pages from cups web admin. At least that is what the > software claims. But they do not appear on the printer either. Nor > are they reported in the lpr queue or on the CUPS web admin page. The > printer self test page can be generated from CUPS. > > The spooler appears to be working. Do the jobs get stuck in the queue, or do they simply disappear from it? Check CUPS's error log file to see if there is something related to post-queue job handling (like printer filter missing). > # lpstat -a > cups-pdf accepting requests since Thu Nov 22 10:12:47 2018 > np4172 accepting requests since Tue Jan 29 15:31:51 2019 > np4173 accepting requests since Tue Jan 29 14:40:46 2019 > np4174 accepting requests since Mon Jan 14 15:07:11 2019 > np4175 accepting requests since Mon Jan 14 18:06:15 2019 > > But CUPs reports two jobs as stopped and restarting them does not get > to print. Instead they show up in the completed job list as aborted. That is very strange. Make sure you can "cupsenable " and "cupsaccept " the printer. After doing so, check the error log file again. > cat /var/spool/lpd/np4172/status > sending to np4172 > > Enscript from the command line prints, but the duplex option selected > did not have any effect. I reused an earlier command which had > previously printed as duplex. I'm using gs (GhostScript) for this, works quite nicely. > Is there a package required for mate to have printing capabilities? If > what is its name? I think it's not a Mate problem, from what you're describing. Some "moving parts" of CUPS have been disturbed. You should be able to do things like "lpr something.pdf" via CLI, and it should work as expected - job appears in "lpq" output, then printer starts printing, "lpq" output is empty. As you have verified that you can print directly, without using CUPS, the problem won't be the printer. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...