Aaron de Bruyn
2022-Aug-31 16:42 UTC
[Samba] Upgrade to 2:4.16.2+dfsg-1nmu1~deb11.1 borks printing
Apologies?I'm using Shortwave and when I sign my message "-A" it occasionally removes one of the recipients from the list if I don't catch it. I'm still waiting on Shortwave to fix it. ? I checked and the printers weren't disabled. I've tested by submitting test pages from the windows printer properties dialog, from notepad, and from several internal applications we use. When we're running the latest version of Samba, 100% of the sites are affected (~28 locations) and 100% of the printers are affected (~40 printers/copiers). Absolutely nothing prints except a test page submitted directly through the CUPS web GUI. When we roll every site back, all sites and printers work again without problems. I've been combing through logs and haven't found anything that would indicate an error message. Quite literally the situation is: apt-get install samba=2:4.13.13+dfsg-1~deb11u4 Printing from any application on any computer works apt-get install samba=2:4.16.2+dfsg-1nmu1~deb11.1 Printing from any application on any computer fails. In light of that, do you want me to spend time setting a machine up to print directly to one of the copiers? It really seems like an issue involving the Samba/CUPS chain and not something related to the Windows workstations/printers/copiers. Thanks, -A On Wed Aug 31, 2022, 03:01 PM GMT, L. van Belle <mailto:belle at samba.org> wrote:> Hai, > > Please reply to the list, that keeps the thread complete and it might help others. > > Ok. I know lexmark has high quality drivers in general, that?s one I don?t have here. > The HP universal PCL6 Type 3 should also work without problems. > > Also, did you check if cups didn?t disable the printer, I had that few weeks ago out of the blue. > > For that you can use this. > ## RE-Enable all disabled printers, (* optional with excluded filters if set. ) > > for PRINTERS in $(lpstat -p|grep -iEv "idle "|awk '{print $2}') > do > echo "(Re-)enabling printer: ${PRINTERS}" > cupsenable "${PRINTERS}" > done > What are you printing? What works and what not.. > test 1 Via the print server. > print a pdf, don?t change anything, > print a pdf, but in printer settings set, ?print as picture? > print a .doc(x). > print a .txt > > test 2 directly from pc to printer. > Repeast the above test > > which one?s works and which not. > Greetz, > > Louis > Van: Aaron de Bruyn <aaron at heyaaron.com> > Verzonden: woensdag 31 augustus 2022 16:35 > Aan: L. van Belle <belle at samba.org> > Onderwerp: Re: [Samba] Upgrade to 2:4.16.2+dfsg-1nmu1~deb11.1 borks printing > Most of the printers are Lexmark or HP. > -A > On Wed Aug 31, 2022, 06:58 AM GMT, L. van Belle via samba <mailto:samba at lists.samba.org> wrote: >> If its a PDF what your printing, try, enable "print as picture" (at >> Advanced button after you hit print). >> I seen this also but only with some PDF documents. >> >> That a print goes in queue bigger is normal, its allways blownup when >> converted to print language. >> >> whats the printer brand/model and which drivers do you use? >> >> Greetz. >> >> Louis >> >>> -----Oorspronkelijk bericht----- >>> Van: samba <samba-bounces at lists.samba.org <mailto:samba-bounces at lists.samba.org>> Namens Aaron de Bruyn via >>> samba >>> Verzonden: woensdag 31 augustus 2022 03:30 >>> Aan: Rowland penny <rpenny at samba.org <mailto:rpenny at samba.org>>; samba at lists.samba.org <mailto:samba at lists.samba.org> >>> Onderwerp: Re: [Samba] Upgrade to 2:4.16.2+dfsg-1nmu1~deb11.1 borks >>> printing >>> >>> I just installed 2:4.16.4+dfsg-2~bpo11+1 on a test NAS and the same issue >>> occurred. >>> >>> One additional thing I noticed is that when I print a test page, the print >> queue >>> in Windows shows a ~5 MB document, and that document never prints. >>> When I downgrade to 2:4.13.13+dfsg-1~deb11u4 and print a test page it >>> initially goes into the queue as a ~5 MB document, then it refreshes and >>> shows the test page is 308 KB. >>> >>> I'm not familiar with the inner-workings of Windows printing, so this is >> wild >>> speculation...but maybe part of the print process is converting the print >> job >>> into a specific format and that specific format is smaller, but in the >> latest >>> version of Samba the print job submission never makes it that far. >>> >>> -A >>> >>> On Tue Aug 30, 2022, 06:42 PM GMT, Rowland Penny via samba >>> <mailto:samba at lists.samba.org <mailto:samba at lists.samba.org>> wrote: >>> > On Tue, 2022-08-30 at 18:36 +0000, Aaron de Bruyn wrote: >>> >> I looked over the archive for the last two months and didn't see >>> >> anything that appeared related. I must have missed something. >>> >> >>> >> Anyways, apt isn't seeing 4.16.4 which is odd. >>> >> >>> >> I have bullseye-samba416 from van-belle's repo in my list, and I can >>> >> totally see samba_4.16.4+dfsg-2ubuntu1.1~22.04.1_amd64 in his pool >>> >> directory. >>> >> >>> >> # apt-cache madison samba >>> >> samba | 2:4.16.2+dfsg-1nmu1~deb11.1 | http://apt.van-belle.nl/debian <http://apt.van-belle.nl/debian> >>> >> <http://apt.van-belle.nl/debian <http://apt.van-belle.nl/debian>> bullseye-samba416/main amd64 >>> >> Packages samba | 2:4.13.13+dfsg-1~deb11u5 | >>> >> http://security.debian.org <http://security.debian.org> < http://security.debian.org <http://security.debian.org>> >>> >> bullseye-security/main amd64 Packages samba | >>> >> 2:4.13.13+dfsg-1~deb11u4 | http://ftp.us.debian.org/debian <http://ftp.us.debian.org/debian> < >>> >> http://ftp.us.debian.org/debian <http://ftp.us.debian.org/debian>> bullseye/main amd64 Packages # >>> >> >>> >> I better go do some digging. >>> > >>> > Try digging into bullseye backports, it has 4.16.4 >>> > >>> > Rowland >>> > >>> > >>> > >>> > -- >>> > To unsubscribe from this list go to the following URL and read the >>> > instructions: https://lists.samba.org/mailman/options/samba <https://lists.samba.org/mailman/options/samba> >>> -- >>> To unsubscribe from this list go to the following URL and read the >>> instructions: https://lists.samba.org/mailman/options/samba <https://lists.samba.org/mailman/options/samba> >> >> >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: https://lists.samba.org/mailman/options/samba <https://lists.samba.org/mailman/options/samba>
Rowland Penny
2022-Aug-31 17:28 UTC
[Samba] Upgrade to 2:4.16.2+dfsg-1nmu1~deb11.1 borks printing
On Wed, 2022-08-31 at 16:42 +0000, Aaron de Bruyn via samba wrote:> Apologies?I'm using Shortwave and when I sign my message "-A" it > occasionally removes one of the recipients from the list if I don't > catch it. I'm still waiting on Shortwave to fix it. ? > > I checked and the printers weren't disabled. > > I've tested by submitting test pages from the windows printer > properties dialog, from notepad, and from several internal > applications we use. > > When we're running the latest version of Samba, 100% of the sites are > affected (~28 locations) and 100% of the printers are affected (~40 > printers/copiers). Absolutely nothing prints except a test page > submitted directly through the CUPS web GUI. > > When we roll every site back, all sites and printers work again > without problems. I've been combing through logs and haven't found > anything that would indicate an error message. > > Quite literally the situation is: > > apt-get install samba=2:4.13.13+dfsg-1~deb11u4 > Printing from any application on any computer works > > apt-get install samba=2:4.16.2+dfsg-1nmu1~deb11.1 > Printing from any application on any computer fails. > > In light of that, do you want me to spend time setting a machine up > to print directly to one of the copiers? It really seems like an > issue involving the Samba/CUPS chain and not something related to the > Windows workstations/printers/copiers.I knew this came up recently, at the beginning of the month actually and Andreas Schneider posted a solution: rm -f /var/cache/samba/printer_list.tdb Rowland