Bug#907493: ghostscript breaks cups autopkgtest: test times out
Hi Jonas, On 31-08-18 16:19, Jonas Smedegaard wrote: > Currently¹ I cannot (easily) setup a CUPS testing environment, so would > appreciate if someone else can confirm if the version now in testing > _also_ causes this same failure - and if so then please help ensure that > this issue does not block the security fix now in unstable to enter > testing. The cups test with only packages from testing is successfully running. It has been tried two times over the last two days, visible with the trigger "migration-reference/0" here: https://ci.debian.net/packages/c/cups/testing/amd64/ I have requested the cups test in testing with ghostscript from experimental. I hasn't finished yet, albeit it probably started soon after I requested it at 2018-08-31 19:20:50 UTC, so this isn't looking good. Feel free to check in 2:30 hours or so, it should be visible at the page linked above with the trigger "elbrus ghostscript from experimental". If that ran for 2:47 and failed it probably timed out (which you can confirm by looking at the bottom of the test log). Paul signature.asc Description: OpenPGP digital signature
Bug#907493: ghostscript breaks cups autopkgtest: test times out
Hi Jonas, On 31-08-18 01:25, Jonas Smedegaard wrote: > Do the freshly released experimental Ghostscript release help anything? I'll trigger the test shortly and report back with the results. Paul signature.asc Description: OpenPGP digital signature
Bug#907493: ghostscript breaks cups autopkgtest: test times out
Dear all, On 31-08-18 15:48, Till Kamppeter wrote: > On 31/08/18 15:36, Didier 'OdyX' Raboud wrote: >> Le vendredi, 31 août 2018, 01.25:24 h CEST Jonas Smedegaard a écrit : >>> Do the freshly released experimental Ghostscript release help anything? >> >> It doesn't seem to, unfortunately. :-( >> >> To reproduce the issue; just run this as root: >> /usr/share/cups/test-drivers I tried this on my fully up-to-date testing/buster system and it fails for a different reason: lpinfo: Bad file descriptor Not sure yet, what that means for any of this. >> Surprisingly; it will fail when testing the _second_ printer, always. >> Also, it >> doesn't seem to get fixed with the ghostscript from testing. >> >> There's something fishy here, but I can't say with certainty that it's >> ghostscript's fault :-( > > Which driver is this second printer using? As mentioned in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907493#26 DUMMY_PRINTER_NAME=test-printer0 driver=drv:///sample.drv/dymo.ppd > Which version of cups-filters are you using? 1.21.0 has a bug in > foomatic-rip which is fixed in 1.21.1. Please update to 1.21.1 if you > have 1.21.0 currently. I had none installed. I now try with 1.20.4-1 which is in testing, where the bug was reported from and where cups fails with the ghostscript from unstable. The autopkgtest ran successfully with cups-filters/1.21.0-1 and with cups-filters/1.21.1-1 so I assume they are both fine in this respect. On my laptop, lpinfo still fails. Paul signature.asc Description: OpenPGP digital signature
Bug#907703: ghostscript: Bug 699654(2): preserve LockSafetyParams in the nulldevice
Source: ghostscript Version: 9.22~dfsg-3 Severity: grave Tags: patch security upstream Control: found -1 9.20~dfsg-1 There is one more followup fix needed: http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=79cccf641486 https://bugs.ghostscript.com/show_bug.cgi?id=699654 Decoupling this from #907332 as issues there adressed, should ease a bit tracking for fixes. Regards, Salvatore
Processed: ghostscript: Bug 699654(2): preserve LockSafetyParams in the nulldevice
Processing control commands: > found -1 9.20~dfsg-1 Bug #907703 [src:ghostscript] ghostscript: Bug 699654(2): preserve LockSafetyParams in the nulldevice Marked as found in versions ghostscript/9.20~dfsg-1. -- 907703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907493: ghostscript breaks cups autopkgtest: test times out
Quoting Jonas Smedegaard (2018-08-31 15:43:28) > Quoting Didier 'OdyX' Raboud (2018-08-31 15:36:09) > > Le vendredi, 31 août 2018, 01.25:24 h CEST Jonas Smedegaard a écrit : > > > Do the freshly released experimental Ghostscript release help anything? > > > > It doesn't seem to, unfortunately. :-( > > > > To reproduce the issue; just run this as root: > > /usr/share/cups/test-drivers > > > > Surprisingly; it will fail when testing the _second_ printer, always. > > Also, it doesn't seem to get fixed with the ghostscript from testing. > > > > There's something fishy here, but I can't say with certainty that it's > > ghostscript's fault :-( > > Uhm, if the ghostscript in _testing_ causes that test to fail, then this > bug should *not* block the ghostscript in unstable to enter testing!!! Let me try again - I see that my previous message could easily be perceived as aggressive: Not intended at all. Sorry! Thanks, Odyx, for checking against the various versions of Ghostscript. Currently¹ I cannot (easily) setup a CUPS testing environment, so would appreciate if someone else can confirm if the version now in testing _also_ causes this same failure - and if so then please help ensure that this issue does not block the security fix now in unstable to enter testing. - Jonas ¹ I am at MMMfest, a week long festival near Paris. -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#907493: ghostscript breaks cups autopkgtest: test times out
On 31/08/18 15:36, Didier 'OdyX' Raboud wrote: Le vendredi, 31 août 2018, 01.25:24 h CEST Jonas Smedegaard a écrit : Do the freshly released experimental Ghostscript release help anything? It doesn't seem to, unfortunately. :-( To reproduce the issue; just run this as root: /usr/share/cups/test-drivers Surprisingly; it will fail when testing the _second_ printer, always. Also, it doesn't seem to get fixed with the ghostscript from testing. There's something fishy here, but I can't say with certainty that it's ghostscript's fault :-( Which driver is this second printer using? Which version of cups-filters are you using? 1.21.0 has a bug in foomatic-rip which is fixed in 1.21.1. Please update to 1.21.1 if you have 1.21.0 currently. Till
Bug#907493: ghostscript breaks cups autopkgtest: test times out
Quoting Didier 'OdyX' Raboud (2018-08-31 15:36:09) > Le vendredi, 31 août 2018, 01.25:24 h CEST Jonas Smedegaard a écrit : > > Do the freshly released experimental Ghostscript release help anything? > > It doesn't seem to, unfortunately. :-( > > To reproduce the issue; just run this as root: > /usr/share/cups/test-drivers > > Surprisingly; it will fail when testing the _second_ printer, always. > Also, it doesn't seem to get fixed with the ghostscript from testing. > > There's something fishy here, but I can't say with certainty that it's > ghostscript's fault :-( Uhm, if the ghostscript in _testing_ causes that test to fail, then this bug should *not* block the ghostscript in unstable to enter testing!!! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#907493: ghostscript breaks cups autopkgtest: test times out
Le vendredi, 31 août 2018, 01.25:24 h CEST Jonas Smedegaard a écrit : > Do the freshly released experimental Ghostscript release help anything? It doesn't seem to, unfortunately. :-( To reproduce the issue; just run this as root: /usr/share/cups/test-drivers Surprisingly; it will fail when testing the _second_ printer, always. Also, it doesn't seem to get fixed with the ghostscript from testing. There's something fishy here, but I can't say with certainty that it's ghostscript's fault :-( (No more time to investigate this today, sorry) -- OdyX signature.asc Description: This is a digitally signed message part.
