[Group.of.nepali.translators] [Bug 1825946] Re: 'nm' autopkgtest fails due to GI stderr output
network-manager 1.10.14-0ubuntu2 witrh the fix for this bug got
transferred to bionic-updates. Thanks to the SRU team for the great
cooperation.
** Changed in: network-manager (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1825946
Title:
'nm' autopkgtest fails due to GI stderr output
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Xenial:
In Progress
Status in network-manager source package in Bionic:
Fix Released
Bug description:
[impact]
'nm' testcase contains:
from gi.repository import NetworkManager, NMClient, GLib
which generates output to stderr:
/tmp/autopkgtest.naU0ts/build.riU/src/debian/tests/nm:23: PyGIWarning:
NetworkManager was imported without specifying a version first. Use
gi.require_version('NetworkManager', '1.0') before import to ensure that the
right version gets loaded.
the gi.require_version call has already been added to cosmic and
disco.
[test case]
see http://autopkgtest.ubuntu.com/packages/network-manager bionic test
results.
[other info]
this only fails intermittently, but the failure is clearly not an
actual problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1825946/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1815339] Re: Printer stopped printing paper size 4"x6" after update ghostscript to 9.26
The fix for this bug got reverted as it caused a regression, bug 1817308. Therefore I am re-opening this bug. A solution for this regression got already committed by the upstream developers of Ghostscript, see the upstream bug report: http://bugs.ghostscript.com/show_bug.cgi?id=700584 ** Changed in: ghostscript (Ubuntu Trusty) Status: Fix Released => Triaged ** Changed in: ghostscript (Ubuntu Xenial) Status: Fix Released => Triaged ** Changed in: ghostscript (Ubuntu Bionic) Status: Fix Released => Triaged ** Changed in: ghostscript (Ubuntu Cosmic) Status: Fix Released => Triaged ** Changed in: ghostscript (Ubuntu Disco) Status: Fix Released => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1815339 Title: Printer stopped printing paper size 4"x6" after update ghostscript to 9.26 Status in GS-GPL: Fix Released Status in ghostscript package in Ubuntu: Triaged Status in ghostscript source package in Trusty: Triaged Status in ghostscript source package in Xenial: Triaged Status in ghostscript source package in Bionic: Triaged Status in ghostscript source package in Cosmic: Triaged Status in ghostscript source package in Disco: Triaged Bug description: I have an issue with Ghostscript and printing. I use Gutenprint for my Canon MG5440, and I cannot print a photo 4"x6" (or 6"x4"), it does not print anything, however I still able to print A4 paper size. I use Ubuntu 18.04 and Gutenprint 5.3.1. The printing fail with message: [Job 143] Start rendering... [Job 143] Processing page 1... [Job 143] Unable to open the initial device, quitting. [Job 143] Rendering completed ... [Job 143] PID 24869 (/usr/lib/cups/filter/gstoraster) stopped with status 1. ... [Job 143] printer-state-message="Filter failed" [Job 143] printer-state-reasons=none The message "Unable to open the initial device, quitting" comes from Ghostscript. When I downgrade Ghostscript to 9.22, I am again able to print 4"x6" paper size. To downgrade: apt install ghostscript=9.22~dfsg+1-0ubuntu1 libgs9=9.22~dfsg+1-0ubuntu1 libgs9-common=9.22~dfsg+1-0ubuntu1 I found similar issue for HP printer at Debian https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=908205 System info: Description: Ubuntu 18.04.1 LTS Release: 18.04 ghostscript: Installed: 9.26~dfsg+0-0ubuntu0.18.04.4 Candidate: 9.26~dfsg+0-0ubuntu0.18.04.4 Versions: *** 9.26~dfsg+0-0ubuntu0.18.04.4 500 500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 9.22~dfsg+1-0ubuntu1 500 500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages cups: Installed: 2.2.7-1ubuntu2.3 Candidate: 2.2.7-1ubuntu2.3 Versions: *** 2.2.7-1ubuntu2.3 500 500 http://ua.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.2.7-1ubuntu2.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.2.7-1ubuntu2 500 500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1815339/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
** Also affects: cups (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: New Status in cups package in Ubuntu: Confirmed Status in cups source package in Xenial: New Status in cups source package in Bionic: New Status in cups source package in Cosmic: New Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1676380] Re: Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script failures
*** This bug is a duplicate of bug 1642966 *** https://bugs.launchpad.net/bugs/1642966 Discussion about that problem is going on in bug 1642966. There is also a fix suggested. Marking this one as duplicate. ** This bug has been marked a duplicate of bug 1642966 package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1676380 Title: Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script failures Status in cups package in Ubuntu: Confirmed Status in cups source package in Xenial: Confirmed Bug description: Even though LP: #1642966 states that this is now fixed, the very update that was SRU'ed in that bug-report caused this error just now. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.10.0-13.15~16.04.2-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CupsErrorLog: Date: Mon Mar 27 12:53:31 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-15 (11 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lpstat: device for iP5200R: usb://Canon/iP5200R?serial=9045C0 MachineType: Dell Inc. Precision 5520 Papersize: a4 PpdFiles: iP5200R: Canon iP5200R series - CUPS+Gutenprint v5.2.11 ProcCmdline: BOOT_IMAGE=/vmlinuz-4.10.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_rev_override vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_rev_override vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 06X96V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676380/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1638986] Re: cups/cups-browsed causing delay in shutdown (16.04)
** Also affects: cups-filters (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cups-filters (Ubuntu Xenial) Milestone: None => xenial-updates ** Changed in: cups-filters (Ubuntu Xenial) Status: New => In Progress ** Changed in: cups-filters (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1638986 Title: cups/cups-browsed causing delay in shutdown (16.04) Status in cups-filters package in Ubuntu: Fix Released Status in cups-filters source package in Xenial: In Progress Bug description: Description: Ubuntu 16.04.1 LTS Release: 16.04 cups-filters: Installed: 1.8.3-2ubuntu3.1 Candidate: 1.8.3-2ubuntu3.1 Version table: *** 1.8.3-2ubuntu3.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.8.3-2ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages Bug description: I have updated to the latest cups-filters version to fix the bug as described by bug report #1579905 but I still get that Ubuntu takes very long to shutdown. For now, I have simply disabled cups-browser and I manually start it up every time I need to print something. It is probably related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832637 as Till has described in #1579905. I tried to download and compile the upstream version at BZR as suggested for Debian but I ended up not being able to print anymore and instead went back to the current version in the package distribution. Hopefully, there is an easy fix for Ubuntu 16.04 as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1638986/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1598300] Re: cups hang after a while
Not having "ListenStream=631" in the systemd cups.socket file is intended. See the answer from Mike Sweet, author of CUPS: -- First, the reason why we don't include "ListenStream=631" is because that exposes cupsd to remote attack. And we don't listen on localhost (which has a similar security issue) because it causes problems when binding to the "any" address on Linux. Second, once cupsd starts it will create the localhost (or "any" address) listener for you, and stay running indefinitely. And cupsd uses a KeepAlive file to tell systemd to start it up on bootup once you enable the web interface, so it should be running right away unless you've added something to manually start/stop cupsd. -- In Yakkety (16.10), CUPS behaves as intended upstream, not automatically shutting down when it shares at least one printer or the web interface is active (turned on via "WebInterface Yes" in cupsd.conf). So there this bug should be fixed. In earlier Ubuntu versions, like Xenial (16.04 LTS), there is a patch which allows for CUPS auto shutdown due to another problem, whgich is fixed in later CUPS versions. This fix needs to get backported so that auto shutdown can be suppressed with active web interface, to match the upstream standard. ** Changed in: cups (Ubuntu) Status: Confirmed => Fix Released ** Also affects: cups (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cups (Ubuntu Xenial) Status: New => Confirmed ** Changed in: cups (Ubuntu Xenial) Milestone: None => xenial-updates -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1598300 Title: cups hang after a while Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Confirmed Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
