[Bug 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS
Joe, thanks for reporting the bug. I am unable to reproduce the issue in my test env. Can you please provide a step-by-step procedure to reproduce it on a clean 18.04 installation? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851407 Title: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850754] Re: ceph-volume lvm list is O(n^2)
** No longer affects: ceph (Ubuntu Xenial) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850754 Title: ceph-volume lvm list is O(n^2) To manage notifications about this bug go to: https://bugs.launchpad.net/ceph/+bug/1850754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850754] Re: ceph-volume lvm list is O(n^2)
** Also affects: ceph (Ubuntu Eoan) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850754 Title: ceph-volume lvm list is O(n^2) To manage notifications about this bug go to: https://bugs.launchpad.net/ceph/+bug/1850754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
I have just run the test case from this bug description on the bionic-proposed version 1.10.6-2ubuntu1.2. tcpdump does not show any leak of the VPN-specific queries. I have not observed other issues in my tests. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754671 Title: Full-tunnel VPN DNS leakage regression To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850754] Re: ceph-volume lvm list is O(n^2)
** Also affects: ceph (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ceph (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850754 Title: ceph-volume lvm list is O(n^2) To manage notifications about this bug go to: https://bugs.launchpad.net/ceph/+bug/1850754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850754] [NEW] ceph-volume lvm list is O(n^2)
Public bug reported: ceph-volume lvm list calls take very long time due to the fact it has been implemented with O(n^2). This leads to unproportionally long execution time taking under consideration the fact that no complex computation is needed. Steps to reproduce: 1. Create a setup with a large number of disks and logical volumes (e.g. 24) 2. Call ceph-volume lvm list for one of the disks. 3. Wait for the call to finish. Expected result: Call is executed within seconds at most. Actual result: Call may take even minutes in some circumstances (large number of disks, some OSDs stopped). ** Affects: ceph Importance: Unknown Status: Unknown ** Affects: ceph (Ubuntu) Importance: Undecided Assignee: Dariusz Gadomski (dgadomski) Status: New ** Bug watch added: tracker.ceph.com/issues #37490 http://tracker.ceph.com/issues/37490 ** Also affects: ceph via http://tracker.ceph.com/issues/37490 Importance: Unknown Status: Unknown ** Changed in: ceph (Ubuntu) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850754 Title: ceph-volume lvm list is O(n^2) To manage notifications about this bug go to: https://bugs.launchpad.net/ceph/+bug/1850754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
I have backported what was listed as nm-1-10 fix for the bug in the upstream bugzilla [1]. I have also applied fixes for bug #1825946 and bug #1790098 to it. [1] https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=1e486a721de1fec76c81bfc461671a7fbdae531b After testing this build for some time (available at ppa:dgadomski /network-manager) I haven't found any problems. @Till I'd appreciate you having a look at it. Thanks! ** Patch added: "bionic_network-manager_1.10.6-2ubuntu1.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1754671/+attachment/5296236/+files/bionic_network-manager_1.10.6-2ubuntu1.2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754671 Title: Full-tunnel VPN DNS leakage regression To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836361] Re: Windows guest display is inverted vertically
I have checked disco (0.1.7-3ubuntu0.19.04.1) and xenial (0.1.4-1ubuntu1.16.04.1) and I was not able to reproduce the problem. Verification positive. ** Tags removed: verification-needed verification-needed-disco verification-needed-xenial ** Tags added: verification-done verification-done-disco verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836361 Title: Windows guest display is inverted vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836361] Re: Windows guest display is inverted vertically
I confirm bionic-proposed version (0.1.7-2ubuntu1) works as expected. Nothing looks flipped. Screenshot attached. ** Attachment added: "Screenshot_2019-07-30 Spice Javascript client.png" https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+attachment/5279995/+files/Screenshot_2019-07-30%20Spice%20Javascript%20client.png ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836361 Title: Windows guest display is inverted vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836361] Re: Windows guest display is inverted vertically
@ddstreet: I've just checked and Xenial was also affected, attaching debdiff. ** Patch added: "xenial_spice-html5_0.1.4-1ubuntu1.16.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+attachment/5278408/+files/xenial_spice-html5_0.1.4-1ubuntu1.16.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836361 Title: Windows guest display is inverted vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836361] Re: Windows guest display is inverted vertically
** Also affects: spice-html5 (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836361 Title: Windows guest display is inverted vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836361] Re: Windows guest display is inverted vertically
SRU proposal for Eoan. ** Changed in: spice-html5 (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: spice-html5 (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: spice-html5 (Ubuntu Disco) Importance: Undecided => Medium ** Patch added: "eoan_spice-html5_0.1.7-3ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+attachment/5276722/+files/eoan_spice-html5_0.1.7-3ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836361 Title: Windows guest display is inverted vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836361] Re: Windows guest display is inverted vertically
SRU proposal for disco. ** Patch added: "disco_spice-html5_0.1.7-3ubuntu1.19.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+attachment/5276723/+files/disco_spice-html5_0.1.7-3ubuntu1.19.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836361 Title: Windows guest display is inverted vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836361] Re: Windows guest display is inverted vertically
SRU proposal for bionic. ** Patch added: "bionic_spice-html5_0.1.7-2ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+attachment/5276725/+files/bionic_spice-html5_0.1.7-2ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836361 Title: Windows guest display is inverted vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836361] Re: Windows guest display is inverted vertically
SRU proposal for cosmic. ** Patch added: "cosmic_spice-html5_0.1.7-3ubuntu1.18.10.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+attachment/5276724/+files/cosmic_spice-html5_0.1.7-3ubuntu1.18.10.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836361 Title: Windows guest display is inverted vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836361] Re: Windows guest display is inverted vertically
** Also affects: spice-html5 (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: spice-html5 (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: spice-html5 (Ubuntu) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) ** Changed in: spice-html5 (Ubuntu Bionic) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) ** Changed in: spice-html5 (Ubuntu Cosmic) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) ** Changed in: spice-html5 (Ubuntu Disco) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836361 Title: Windows guest display is inverted vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836361] Re: Windows guest display is inverted vertically
** Description changed: [Impact] - * When running a Windows VM using the QXL driver from [1] the display + * When running a Windows VM using the QXL driver from [1] the display is inverted and therefore almost unusable. [Test Case] - * Launch a Windows VM with a QXL display (I used Win2k16 running under libvirt). - * Start websockify - sudo apt install python3-websockify && websockify 5959 localhost:5900 - * Run a HTTP server to spice-html5: -cd /usr/share/spice-html5 && python -m SimpleHTTPServer - * Open a browser and go to http://localhost:8000 - * Enter -host: localhost -port: 5959 - * Click start + * Launch a Windows VM with a QXL display (I used Win2k16 running under libvirt). + * Start websockify + sudo apt install python3-websockify && websockify 5959 localhost:5900 + * Run a HTTP server to spice-html5: + cd /usr/share/spice-html5 && python -m SimpleHTTPServer + * Open a browser and go to http://localhost:8000 + * Enter + host: localhost + port: 5959 + * Click start Expected behaviour: Guest UI is displayed correctly. Actual behaviour: Guest UI gets inverted on refresh. [Regression Potential] - * This component may be used with openstack and it's possible that + * This component may be used with openstack and it's possible that there are workarounds in place, so they may start working incorrectly. [Other Info] - - * This is fixed from cosmic onwards (spice-html5 0.1.7-3). + + * Part of this fixed is included cosmic and onwards (spice-html5 + 0.1.7-3). [1] https://fedorapeople.org/groups/virt/virtio-win/direct-downloads /latest-virtio/virtio-win.iso -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836361 Title: Windows guest display is inverted vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836361] Re: Windows guest display is inverted vertically
Adding an example screenshot. ** Attachment added: "screencapture-localhost-8000-spice-html-2019-07-12-13_08_41.png" https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+attachment/5276684/+files/screencapture-localhost-8000-spice-html-2019-07-12-13_08_41.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836361 Title: Windows guest display is inverted vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836361] [NEW] Windows guest display is inverted vertically
Public bug reported: [Impact] * When running a Windows VM using the QXL driver from [1] the display is inverted and therefore almost unusable. [Test Case] * Launch a Windows VM with a QXL display (I used Win2k16 running under libvirt). * Start websockify sudo apt install python3-websockify && websockify 5959 localhost:5900 * Run a HTTP server to spice-html5: cd /usr/share/spice-html5 && python -m SimpleHTTPServer * Open a browser and go to http://localhost:8000 * Enter host: localhost port: 5959 * Click start Expected behaviour: Guest UI is displayed correctly. Actual behaviour: Guest UI gets inverted on refresh. [Regression Potential] * This component may be used with openstack and it's possible that there are workarounds in place, so they may start working incorrectly. [Other Info] * This is fixed from cosmic onwards (spice-html5 0.1.7-3). [1] https://fedorapeople.org/groups/virt/virtio-win/direct-downloads /latest-virtio/virtio-win.iso ** Affects: spice-html5 (Ubuntu) Importance: Medium Status: New ** Affects: spice-html5 (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: sts ** Changed in: spice-html5 (Ubuntu) Importance: Undecided => Medium ** Tags added: sts ** Also affects: spice-html5 (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836361 Title: Windows guest display is inverted vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-html5/+bug/1836361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831021] Re: Extremely high memory consumption under heavy workload
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831021 Title: Extremely high memory consumption under heavy workload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830022] Re: DirtyCleanInterval should be 0 by default
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830022 Title: DirtyCleanInterval should be 0 by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1830022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1374109] Re: epmd does not support binding to an IPv4 address anymore
** Changed in: erlang (Ubuntu) Assignee: Dariusz Gadomski (dgadomski) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1374109 Title: epmd does not support binding to an IPv4 address anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/erlang/+bug/1374109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Despite some build failures for i386 and s390 which I believe are not related to the scope of the change I have successfully verified it for amd64. apt-cache policy cups-daemon cups: Installed: 2.1.3-4ubuntu0.9 lp -d PDF /usr/share/cups/data/default.pdf PreserveJobHistory 30: I [04/Jun/2019:13:19:56 +] [Job 1] Job completed. D [04/Jun/2019:13:20:27 +] [Job 1] Removing from history. PreserveJobHistory No: I [04/Jun/2019:13:22:32 +] [Job 2] Job completed. D [04/Jun/2019:13:22:32 +] [Job 2] Removing from history. PreserveJobHistory Yes: I [04/Jun/2019:13:23:41 +] [Job 3] Job completed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
** Changed in: cups (Ubuntu Disco) Assignee: Dariusz Gadomski (dgadomski) => (unassigned) ** Description changed: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] 1. Set PreserveJobHistory to 30. Set LogLevel to debug. 2. Schedule a job for printing. 3. Check the error_log. - 4. Set PreserveJobHistory to Yes. Repeat 2-3. - 5. Set PreserveJobHistory to No. Repeat 2-3. + 4. Set PreserveJobHistory to No. Repeat 2-3. + 5. Set PreserveJobHistory to Yes. Repeat 2-3. + Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. + No: Job is removed right after processing. Yes: Job is never removed. - No: Job is removed right after processing. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. + No: Job is removed right after processing. Yes: Job is never removed. - No: Job is removed right after processing. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Verified for cosmic: apt-cache policy cups-daemon cups-daemon: Installed: 2.2.8-5ubuntu1.4 lp -d PDF /usr/share/cups/data/default.pdf PreserveJobHistory 30: I [04/Jun/2019:09:12:13 +] [Job 1] Job completed. D [04/Jun/2019:09:12:44 +] [Job 1] Removing from history. PreserveJobHistory No: I [04/Jun/2019:09:13:03 +] [Job 2] Job completed. D [04/Jun/2019:09:13:03 +] [Job 2] Removing from history. PreserveJobHistory Yes: I [04/Jun/2019:09:13:30 +] [Job 3] Job completed. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Verified for disco: apt-cache policy cups-daemon cups-daemon: Installed: 2.2.10-4ubuntu2 lp -d PDF /usr/share/cups/data/default.pdf PreserveJobHistory 30: I [04/Jun/2019:09:03:14 +] [Job 1] Job completed. D [04/Jun/2019:09:03:45 +] [Job 2] Removing from history. PreserveJobHistory No: I [04/Jun/2019:09:04:06 +] [Job 2] Job completed. D [04/Jun/2019:09:04:06 +] [Job 2] Removing from history. PreserveJobHistory Yes: I [04/Jun/2019:09:04:50 +] [Job 3] Job completed. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Verified for bionic. apt-cache policy cups-daemon cups-daemon: Installed: 2.2.7-1ubuntu2.6 lp -d PDF /usr/share/cups/data/default.pdf PreserveJobHistory 30: I [04/Jun/2019:08:52:25 +] [Job 1] Job completed D [04/Jun/2019:08:52:56 +] [Job 1] Removing from history. PreserveJobHistory No: I [04/Jun/2019:08:53:58 +] [Job 2] Job completed. D [04/Jun/2019:08:53:58 +] [Job 2] Removing from history. PreserveJobHistory Yes: I [04/Jun/2019:08:54:55 +] [Job 5] Job completed. (...) ** Description changed: [Impact] - The documentation allows the following types of arguments for the PreserveJobHistory parameter: + The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds - - The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . + + The value in seconds is treated in the same as 'No' resulting in + immediate removing of jobs from history, while it is supposed to save it + for . [Test Case] - * Set PreserveJobHistory to 300. - * Schedule a job for printing. - * Check the error_log. + 1. Set PreserveJobHistory to 300. + 2. Schedule a job for printing. + 3. Check the error_log. + 4. Set PreserveJobHistory to Yes. Repeat 2-3. + 5. Set PreserveJobHistory to No. Repeat 2-3. + - Expected result: - Job is save for at least 300 seconds. + Expected result (for PreserveJobHistory values): + 300: Job is save for at least 300 seconds. + Yes: Job is never removed. + No: Job is removed right after processing. - Actual results: - Job is immediately removed from history. + + Actual results (for PreserveJobHistory values): + 300: Job is immediately removed from history. + Yes: Job is never removed. + No: Job is removed right after processing. [Regression Potential] - * With the fix the jobs will be saved longer than before, so in tight + * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] - - * Original bug description: + + * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... ** Description changed: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] - 1. Set PreserveJobHistory to 300. + 1. Set PreserveJobHistory to 30. 2. Schedule a job for printing. 3. Check the error_log. - 4. Set PreserveJobHistory to Yes. Repeat 2-3. - 5. Set PreserveJobHistory to No. Repeat 2-3. - + 4. Set PreserveJobHistory to Yes. Repeat 2-3. + 5. Set PreserveJobHistory to No. Repeat 2-3. Expected result (for PreserveJobHistory values): - 300: Job is save for at least 300 seconds. + 300: Job is save for at least 30 seconds. Yes: Job is never removed. No: Job is
[Bug 1831021] Re: Extremely high memory consumption under heavy workload
Thank you for the explanation Till. I believe the lack of previous complaints is because this happens in a pretty unique conditions (very high MaxJobs and large batches of jobs). The test case however was based on a real-life scenario reported to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831021 Title: Extremely high memory consumption under heavy workload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831021] Re: Extremely high memory consumption under heavy workload
In a recent test with MaxJobs of 4 I was easily able to reach over 65 GB of memory consumption within 60 mins, while with LogDebugHistory set to 0 the consumption was below 400 MB. My recommendation is to lower the default LogDebugHistory value back to what is upstream: 200. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831021 Title: Extremely high memory consumption under heavy workload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831021] Re: Extremely high memory consumption under heavy workload
** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831021 Title: Extremely high memory consumption under heavy workload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Thanks Till. I've fixed cosmic debdiff, sorry about the mistake.
** Patch removed: "cosmic_cups_2.2.8-5ubuntu1.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267676/+files/cosmic_cups_2.2.8-5ubuntu1.4.debdiff
** Patch added: "cosmic_cups_2.2.8-5ubuntu1.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267712/+files/cosmic_cups_2.2.8-5ubuntu1.4.debdiff
** Changed in: cups (Ubuntu Xenial)
Assignee: Dariusz Gadomski (dgadomski) => (unassigned)
** Changed in: cups (Ubuntu Cosmic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747765
Title:
PreserveJobHistory and PreserveJobLog do not respect numeric input as
outlined in the docs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
SRU proposal for Cosmic. ** Patch added: "cosmic_cups_2.2.8-5ubuntu1.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267676/+files/cosmic_cups_2.2.8-5ubuntu1.4.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
** Also affects: cups (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
SRU proposal for Xenial. ** Patch added: "xenial_cups_2.1.3-4ubuntu0.9.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267662/+files/xenial_cups_2.1.3-4ubuntu0.9.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830022] Re: DirtyCleanInterval should be 0 by default
Discussion upstream: https://lists.cups.org/pipermail/cups/2019-May/074657.html ** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830022 Title: DirtyCleanInterval should be 0 by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1830022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
The patch doesn't apply cleanly to Xenial, working on backport. ** Changed in: cups (Ubuntu Xenial) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) ** Changed in: cups (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cups (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: cups (Ubuntu Disco) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
@sponsors: Eoan already has the fix from Debian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
SRU proposal for Bionic ** Patch added: "bionic_cups_2.2.7-1ubuntu2.6.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267600/+files/bionic_cups_2.2.7-1ubuntu2.6.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
SRU proposal for Disco ** Patch added: "disco_cups_2.2.10-4ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267599/+files/disco_cups_2.2.10-4ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831021] Re: Extremely high memory consumption under heavy workload
** Description changed: Under heavy workload conditions cups can reach irrationally high memory consumption very quickly (tens of GBs). Test case: 1. Set MaxJobs to 4 in cupsd.conf. 2. sudo apt install cups-pdf 3. Fill the queue with jobs: while [ 1 ]; lp -d PDF /usr/share/cups/data/default.pdf; done 4. Cancel all jobs cancel -a PDF 5. Restart cups. 6. Start filling the queue again (as in step 3). Expected result: Jobs are processed and memory consumption is proportional to the number of jobs. Actual result: - After step 5 or at latest step 6 memory consumption starts to increase exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very easy to get cups killed by OOM killer. + After step 5 or at latest step 6 memory consumption starts to increase exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very easy to get cupsd killed by OOM killer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831021 Title: Extremely high memory consumption under heavy workload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
** Description changed: + [Impact] + + The documentation allows the following types of arguments for the PreserveJobHistory parameter: + PreserveJobHistory Yes + PreserveJobHistory No + PreserveJobHistory seconds + + The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . + + [Test Case] + + * Set PreserveJobHistory to 300. + * Schedule a job for printing. + * Check the error_log. + + Expected result: + Job is save for at least 300 seconds. + + Actual results: + Job is immediately removed from history. + + [Regression Potential] + + * With the fix the jobs will be saved longer than before, so in tight + conditions (low disk space) and heavy workload it may affect memory/disk + space consumption and lead to running out of free space in worst case. + + [Other Info] + + * Original bug description: + 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: - Installed: 2.1.3-4ubuntu0.3 - Candidate: 2.1.3-4ubuntu0.3 - Version table: - *** 2.1.3-4ubuntu0.3 500 - 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages + Installed: 2.1.3-4ubuntu0.3 + Candidate: 2.1.3-4ubuntu0.3 + Version table: + *** 2.1.3-4ubuntu0.3 500 + 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf - PreserveJobFiles Yes + PreserveJobFiles Yes -PreserveJobFiles No + PreserveJobFiles No -PreserveJobFiles seconds - Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved - for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). + PreserveJobFiles seconds + Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved + for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). -PreserveJobHistory Yes + PreserveJobHistory Yes -PreserveJobHistory No + PreserveJobHistory No -PreserveJobHistory seconds - Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for - the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default - is "Yes". + PreserveJobHistory seconds + Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for + the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default + is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 - Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... ** Changed in: cups (Ubuntu) Importance: Undecided => Medium ** Also affects: cups (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
This has been fixed in 19.10 for cups 2.2.10-6 (backport from upstream). ** Changed in: cups (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831021] Re: Extremely high memory consumption under heavy workload
After some analysis I believe the very high default value of LogDebugHistory (9) is to blame for this (attaching massif report from the test case). With a high number of jobs it's very easy to get hunderds-thousands of messages in LogDebugHistory which in turn will lead to enormous memory consumption, e.g. 4 jobs * 2000 lines * (16 bytes for cupsd_joblog_t structure + 50-60 chars per message on average) - 5.66 GB. After setting LogDebugHistory to 0 the memory consumption never exceeded 300 MB in my tests under the same heavy load. That's a very significant difference. The possible workarounds: 1. Decrease LogDebugHistory to a low value (even to 0, upstream it's set to 200 by default). 2. Change LogLevel to debug (it will slow down cupsd operation significantly, but at the price of lower memory consumption as the LogDebugHistory is unused). 3. Make sure jobs are cleaned periodically by setting e.g. PreserveJobHistory 300. I am wondering what was the rationale behind increasing LogDebugHistory to such a high value. ** Attachment added: "massif.out.xz" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+attachment/5267574/+files/massif.out.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831021 Title: Extremely high memory consumption under heavy workload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831021] [NEW] Extremely high memory consumption under heavy workload
Public bug reported: Under heavy workload conditions cups can reach irrationally high memory consumption very quickly (tens of GBs). Test case: 1. Set MaxJobs to 4 in cupsd.conf. 2. sudo apt install cups-pdf 3. Fill the queue with jobs: while [ 1 ]; lp -d PDF /usr/share/cups/data/default.pdf; done 4. Cancel all jobs cancel -a PDF 5. Restart cups. 6. Start filling the queue again (as in step 3). Expected result: Jobs are processed and memory consumption is proportional to the number of jobs. Actual result: After step 5 or at latest step 6 memory consumption starts to increase exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very easy to get cups killed by OOM killer. ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831021 Title: Extremely high memory consumption under heavy workload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830022] Re: DirtyCleanInterval should be 0 by default
** Tags removed: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830022 Title: DirtyCleanInterval should be 0 by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1830022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830022] Re: DirtyCleanInterval should be 0 by default
** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830022 Title: DirtyCleanInterval should be 0 by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1830022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830022] [NEW] DirtyCleanInterval should be 0 by default
Public bug reported: Please consider changing DirtyCleanInterval value to 0 as default. Otherwise if cupsd crashes due to (e.g. OOM killer) under a heavy workload even hundreds of jobs may be lost. This concern is backed up by a real-life scenario and leaves the client sending thousands of jobs unaware that many of them are lost during a crash. After cupsd gets restarted it rewinds it's job counter to the last cached and continues unaware about the jobs accepted and lost. Having DirtyCleanInterval set to 0 will cause some performance impact, but not significant under lighter workloads and a completely justified price for reliability under heavy workloads. Test scenario: 1. sudo apt install printer-driver-cups-pdf 2. while [ 1 ]; do lp -d PDF somepdf.pdf; done; 3. # on other terminal kill -9 $(pidof cupsd) 4. Note last job number and wait for cupsd to be restarted by systemd. 5. Once accepting jobs is resumend the job counter is rewound. Expected behavior: Accepted jobs are queued for processing. Actual behavior: Some accepted jobs are lost. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Affects: cups (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: cups (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: cups (Ubuntu Cosmic) Importance: Undecided Status: New ** Affects: cups (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830022 Title: DirtyCleanInterval should be 0 by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1830022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
** Also affects: gnome-terminal (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: gnome-terminal (Ubuntu Xenial) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762391 Title: pam_group.so is not evaluated by gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1762391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
According to my tests GDM works as expected - checking groups the user belongs to on different terminal emulators (e.g. xterm) proves that the /etc/security/group.conf groups are correctly applied. The problem in this case affects gnome-terminal alone (and the problem is present also if using e.g. LightDM instead of GDM). This is related to the way gnome-terminal-server is started via DBus and executed under systemd --user. It is started under the systemd-user PAM service, so pam_group entry should be added to /etc/pam.d/systemd-user. The problem is systemd will never apply pam_group settings because it does not call pam_setcred. The issue is reported to systemd along with a PR fixing it: https://github.com/systemd/systemd/issues/11198 ** Bug watch added: github.com/systemd/systemd/issues #11198 https://github.com/systemd/systemd/issues/11198 ** Also affects: gnome-terminal via https://github.com/systemd/systemd/issues/11198 Importance: Unknown Status: Unknown ** Project changed: gnome-terminal => systemd ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Invalid ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762391 Title: pam_group.so is not evaluated by gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1762391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
Verification of xenial is positive as well: 2.1.3-4ubuntu0.6 $ grep -i cancel error_log I [13/Dec/2018:09:28:50 +0100] [Job 1] Canceling stuck job after 0 seconds. 2.1.3-4ubuntu0.7 $ grep -i -e cancel -e completed error_log I [13/Dec/2018:09:31:22 +0100] [Job 2] Job completed. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
I have finished verification of cosmic. With 2.2.8-5ubuntu1.1: $ grep -i cancel /var/log/cups/error_log I [13/Dec/2018:09:23:02 +0100] [Job 1] Canceling stuck job after 0 seconds. After upgrading to 2.2.8-5ubuntu1.2: $ grep -i -e cancel -e complete /var/log/cups/error_log I [13/Dec/2018:09:25:00 +0100] Full reload complete. I [13/Dec/2018:09:25:28 +0100] [Job 2] Job completed. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
Of course the above setup should include setting MaxJobTime to 0 in /etc/cups/cupsd.conf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
I have just verified bionic with version 2.2.7-1ubuntu2.3. My testing procedure: 1. Switch cups log level to info. 2. Restart cups. 3. Install printer-driver-cups-pdf to have a virtual printer. 4. Replace imagetopdf filter: sudo mv /usr/lib/cups/filter/imagetopdf /usr/lib/cups/filter/imagetopdf.bkp 5. Install wrapper from comment #6 as replacement: sudo install -m 755 ~/imagetopdf /usr/lib/cups/filter/imagetopdf 6. Print an image (so it gets picked by the filter wrapper): lp -d PDF some_image.tiff With 2.2.7-1ubuntu2.3 (Job 1): $ grep -i cancel /var/log/cups/error_log I [13/Dec/2018:08:49:02 +0100] [Job 1] Canceling stuck job after 0 seconds. After upgrading to 2.2.7-1ubuntu2.3 (please look at Job 2) $ grep -i -e cancel -e complete /var/log/cups/error_log I [13/Dec/2018:08:49:02 +0100] [Job 1] Canceling stuck job after 0 seconds. I [13/Dec/2018:08:50:09 +0100] Full reload complete. I [13/Dec/2018:08:50:41 +0100] [Job 2] Job completed. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
Updated debdiff for xenial. ** Patch added: "xenial_cups_2.1.3-4ubuntu0.7.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5221597/+files/xenial_cups_2.1.3-4ubuntu0.7.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
Updated debdiff for cosmic. ** Patch removed: "cosmic_cups_2.2.8-5ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219665/+files/cosmic_cups_2.2.8-5ubuntu2.debdiff ** Patch removed: "bionic_cups_2.2.7-1ubuntu2.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219666/+files/bionic_cups_2.2.7-1ubuntu2.2.debdiff ** Patch removed: "xenial_cups_2.1.3-4ubuntu0.6.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219667/+files/xenial_cups_2.1.3-4ubuntu0.6.debdiff ** Patch added: "cosmic_cups_2.2.8-5ubuntu1.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5221595/+files/cosmic_cups_2.2.8-5ubuntu1.2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
Updated debdiff for bionic. ** Patch added: "bionic_cups_2.2.7-1ubuntu2.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5221596/+files/bionic_cups_2.2.7-1ubuntu2.3.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
SRU proposal for disco (fixed) ** Patch removed: "disco_cups_2.2.9-3ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219664/+files/disco_cups_2.2.9-3ubuntu1.debdiff ** Patch added: "disco_cups_2.2.9-3ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219720/+files/disco_cups_2.2.9-3ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
imagetopdf filter wrapper I've used for the reproducer: #!/usr/bin/env python import sys import time import subprocess def main(): time.sleep(5) args = ["/usr/lib/cups/filter/imagetopdf.bkp"] + sys.argv[1:] subprocess.call(args, stdin=sys.stdin, stdout=sys.stdout, stderr=sys.stderr) if __name__ == "__main__": main() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
SRU proposal for Cosmic. ** Patch added: "cosmic_cups_2.2.8-5ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219665/+files/cosmic_cups_2.2.8-5ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
SRU proposal for disco. ** Description changed: + [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) ** Tags added: sts ** Patch added: "disco_cups_2.2.9-3ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219664/+files/disco_cups_2.2.9-3ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
SRU proposal for xenial. ** Patch added: "xenial_cups_2.1.3-4ubuntu0.6.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219667/+files/xenial_cups_2.1.3-4ubuntu0.6.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
SRU proposal for bionic. ** Patch added: "bionic_cups_2.2.7-1ubuntu2.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1804576/+attachment/5219666/+files/bionic_cups_2.2.7-1ubuntu2.2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
I have verified the following packages on Trusty: hwdata - 0.249-1ubuntu1 gnome-desktop-3 - 3.8.4-0ubuntu3.3 With the above packages installed from -proposed the labels presented in the 'Displays' panel of u-c-c are correct: when real size is available in EDID data diagonal is displayed, otherwise the model/product name is used. In all cases vendor PNP codes were resolved to vendor names according to hwdata records. ** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-done verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
I have also verified unity-settings-daemon 15.04.1+16.04.20160701-0ubuntu3 for Xenial. After connecting a faulty-EDID display - I saw the product name. With a display device with correct dimensions in EDID - screen diagonal in inches was displayed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
unity-settings-daemon should NOT be nominated for trusty, but I can't fix that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
** Also affects: gnome-desktop3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
gnome-desktop SRU proposal for trusty ** Patch removed: "trusty_gnome-desktop3_3.8.4-0ubuntu3.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+attachment/5217608/+files/trusty_gnome-desktop3_3.8.4-0ubuntu3.3.debdiff ** Patch added: "trusty_gnome-desktop3_3.8.4-0ubuntu3.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+attachment/5217619/+files/trusty_gnome-desktop3_3.8.4-0ubuntu3.3.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
It was brought to my attention by Dan that trusty is also worth fixing. The patch to hwdata is identical, however somewhere between trusty and xenial the make_display_name implementation has been moved from gnome- desktop to u-s-d. Hence, despite display-name.c being almost identical in both cases for trusty patching g-d is needed instead of u-s-d. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
gnome-desktop SRU proposal for trusty. ** Patch added: "trusty_gnome-desktop3_3.8.4-0ubuntu3.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+attachment/5217608/+files/trusty_gnome-desktop3_3.8.4-0ubuntu3.3.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
hwdata SRU proposal for trusty ** Patch added: "trusty_hwdata_0.249-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+attachment/5217607/+files/trusty_hwdata_0.249-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
I checked hwdata output in Unity Settings Displays menu with 2 different devices (vendors: LG and Dell) on LiveCDs for xenial, bionic, cosmic with the proposed patch installed (and with ubuntu-unity-desktop installed from universe in case of bionic and comsmic). Worked as expected (i.e. in the Test Case section of the bug description). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
Run the verifications for: hwdata | 0.267-1ubuntu2 | xenial-proposed hwdata | 0.290-1ubuntu0.18.04.1 | bionic-proposed hwdata | 0.290-1ubuntu0.18.10.1 | cosmic-proposed ** Tags removed: verification-needed-bionic verification-needed-cosmic verification-needed-xenial ** Tags added: verification-done-bionic verification-done-cosmic verification-done-xenial ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
Looks like the latest hwdata update (0.267-1ubuntu1) doesn't have full debdiff applied. The change to hwdata-0.267/pnp.ids is missing, it contains only changes to hwdata-0.267/pnp.ids.patch. It doesn't fix the issue this way. ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial ** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
Brian: afaik disco version of hwdata has been synced with latest upstream by Sebastien. Upstream has this change already applied. With the disco package source: grep GSM hwdata-0.317/pnp.ids* hwdata-0.317/pnp.ids:GSMLG Electronics hwdata-0.317/pnp.ids.patch:-GSM Goldstar Company Ltd hwdata-0.317/pnp.ids.patch:+GSM LG Electronics -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
I have also provided debdiffs for hwdata (disco is already synced with upstream) so that LG devices are not shown under Goldstar label. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
I've just verified it on xenial (15.04.1+16.04.20160701-0ubuntu3). Works as expected. Thanks! ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
hwdata SRU proposal for cosmic. ** Patch added: "cosmic_hwdata_0.290-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+attachment/5216709/+files/cosmic_hwdata_0.290-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
hwdata SRU proposal for xenial. ** Patch added: "xenial_hwdata_0.267-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+attachment/5216711/+files/xenial_hwdata_0.267-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
hwdata SRU proposal for bionic. ** Patch added: "bionic_hwdata_0.290-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+attachment/5216710/+files/bionic_hwdata_0.290-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
Alright, thanks Seb. It makes it verified then. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed ** Tags added: verification-done ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
I have just verified both: bionic (15.04.1+18.04.20180413-0ubuntu1.2) and cosmic (15.04.1+18.04.20180413-0ubuntu3) u-s-d packages. In both cases it calculates the diagonal correctly or puts the model name if the real dimensions are not available. However, there is a problem I didn't see coming: hwdata is not installed by default on bionic & cosmic, so the PNP codes are not resolved to vendor names, e.g. u-s-d returned DEL for Dell and GSM for LG Electronics. What are your thoughts on this Seb? Is it worth pulling in hwdata as dependency of u-s-d? It's clearly safer than changing the implementation to use systemd's hwdb. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in unity-control-center
** Description changed: [Impact] * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). This leads to incorrect calculation of diagonal for the purpose of e.g. Unity settings app. [Test Case] 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). 2. Open the Displays section of Unity settings. 3. Look for the name of the newly connected display in the settings window. Expected result: - Display name should contain it's real diagonal. + Display name should contain its real diagonal or model name (if dimensions are not availabe). Actual result: Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" display). [Regression Potential] * This affects the way the display name will be formatted for any software using unity-settings-daemon. If anything is testing/comparing display names - it may fail. [Other Info] * Original bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in unity-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in unity-control-center
seb128: I checked and sadly none of the releases (including disco) contains the hwdb fix - looks like it hasn't been released yet upstream - latest systemd release (239) has been published before the fix has been comitted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in unity-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in unity-control-center
seb128: it's also fixed in hwdb upstream (https://github.com/systemd/systemd/pull/10051). I need to check if that's already present in Bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in unity-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in unity-control-center
** Description changed: [Impact] - * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). + * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). This leads to incorrect calculation of diagonal for the purpose of e.g. Unity settings app. [Test Case] - 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). - 2. Open the Displays section of Unity settings. - 3. Look for the newly connected display. + 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). + 2. Open the Displays section of Unity settings. + 3. Look for the name of the newly connected display in the settings window. + + Expected result: + Display name should contain it's real diagonal. + + Actual result: + Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" display). [Regression Potential] - * This affects the way the display name will be formatted for any + * This affects the way the display name will be formatted for any software using unity-settings-daemon. If anything is testing/comparing display names - it may fail. [Other Info] - + * Original bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in unity-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in unity-control-center
** Description changed: + [Impact] + + * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). + This leads to incorrect calculation of diagonal for the purpose of e.g. Unity settings app. + + [Test Case] + + 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). + 2. Open the Displays section of Unity settings. + 3. Look for the newly connected display. + + [Regression Potential] + + * This affects the way the display name will be formatted for any + software using unity-settings-daemon. If anything is testing/comparing + display names - it may fail. + + [Other Info] + + * Original bug description: + After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in unity-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598183] Re: Operation not permitted while writing to symlinked fuse locations
There is an upstream patch under consideration to be merged into master. Despite not being the perfect solution for the problem it fixes the issue. Let's wait for it to be merged. https://gitlab.gnome.org/GNOME/gvfs/issues/249 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598183 Title: Operation not permitted while writing to symlinked fuse locations To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1598183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755490] Re: Incorrect information about display shown in unity-control-center
It's still valid. hwdata fixed the "vendor name" part of the issue. u-s-d needs to be patched to fix the "nonsense diagonal calculation" part. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in unity-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749289] Re: Installer stops after pressing Cancel on Select a language screen during OEM install
SRU proposal for Xenial. ** Patch added: "xenial_ubiquity_2.21.63.9.debdiff" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1749289/+attachment/5200383/+files/xenial_ubiquity_2.21.63.9.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749289 Title: Installer stops after pressing Cancel on Select a language screen during OEM install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1749289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749289] Re: Installer stops after pressing Cancel on Select a language screen during OEM install
Michael, is there a release coming for Xenial that could include also a fix for this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749289 Title: Installer stops after pressing Cancel on Select a language screen during OEM install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1749289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749289] Re: Installer stops after pressing Cancel on Select a language screen during OEM install
Yes, definitely. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749289 Title: Installer stops after pressing Cancel on Select a language screen during OEM install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1749289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749289] Re: Installer stops after pressing Cancel on Select a language screen during OEM install
Micheal: yes, that is expected after the patch has been applied. I just filled the gaps the installer was expecting. Before the config just died with AttributeError caused by calling a unimplemented method. Hence, my understanding was that this is the original intention. Simply hiding the cancel button on the first page would be ideal, but I'm not sure if that's possible with the current approach. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749289 Title: Installer stops after pressing Cancel on Select a language screen during OEM install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1749289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793485] Re: segfault in png to gif conversion
** Attachment added: "SH_HL_08_Step1_F029.png" https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1793485/+attachment/5190922/+files/SH_HL_08_Step1_F029.png ** Description changed: Regression between 8:6.8.9.9-7ubuntu5.9 and 8:6.8.9.9-7ubuntu5.12. Test case: 1. Download the attached pngs. 2. Run: /usr/bin/convert -limit memory 512MiB -limit map 0MiB -limit file 10 -delay 16 -loop 0 -coalesce -deconstruct ./*.png ./output.gif Expected result: Process finishes with resulting output.gif. Actual result: Process is aborted with SIGSEGV: Other information: In my tests looks like it has been introduced in 8:6.8.9.9-7ubuntu5.11 and does not occur on Bionic. + + Stack trace: + #0 EncodeImage (image_info=0x645c40, data_size=, + image=0x636890) at ../../coders/gif.c:676 + #1 WriteGIFImage (image_info=0x640700, image=0x636890) + at ../../coders/gif.c:1905 + #2 0x779a5f0f in WriteImage (image_info=image_info@entry=0x618680, + image=image@entry=0x62cb30) at ../../magick/constitute.c:1184 + #3 0x779a684f in WriteImages (image_info=image_info@entry=0x60fcd0, + images=, images@entry=0x62cb30, filename=, + exception=exception@entry=0x602ea0) at ../../magick/constitute.c:1335 + #4 0x7763e84e in ConvertImageCommand (image_info=0x60fcd0, argc=19, + argv=0x6143b0, metadata=0x0, exception=0x602ea0) + at ../../wand/convert.c:3215 + #5 0x776ab527 in MagickCommandGenesis ( + image_info=image_info@entry=0x60aab0, + command=0x4007f0 , argc=argc@entry=19, + argv=argv@entry=0x7fffdc68, metadata=metadata@entry=0x0, + exception=exception@entry=0x602ea0) at ../../wand/mogrify.c:168 + #6 0x00400877 in ConvertMain (argv=0x7fffdc68, argc=19) + at ../../utilities/convert.c:81 + #7 main (argc=19, argv=0x7fffdc68) at ../../utilities/convert.c:92 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793485 Title: segfault in png to gif conversion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1793485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793485] [NEW] segfault in png to gif conversion
Public bug reported: Regression between 8:6.8.9.9-7ubuntu5.9 and 8:6.8.9.9-7ubuntu5.12. Test case: 1. Download the attached pngs. 2. Run: /usr/bin/convert -limit memory 512MiB -limit map 0MiB -limit file 10 -delay 16 -loop 0 -coalesce -deconstruct ./*.png ./output.gif Expected result: Process finishes with resulting output.gif. Actual result: Process is aborted with SIGSEGV: Other information: In my tests looks like it has been introduced in 8:6.8.9.9-7ubuntu5.11 and does not occur on Bionic. Stack trace: #0 EncodeImage (image_info=0x645c40, data_size=, image=0x636890) at ../../coders/gif.c:676 #1 WriteGIFImage (image_info=0x640700, image=0x636890) at ../../coders/gif.c:1905 #2 0x779a5f0f in WriteImage (image_info=image_info@entry=0x618680, image=image@entry=0x62cb30) at ../../magick/constitute.c:1184 #3 0x779a684f in WriteImages (image_info=image_info@entry=0x60fcd0, images=, images@entry=0x62cb30, filename=, exception=exception@entry=0x602ea0) at ../../magick/constitute.c:1335 #4 0x7763e84e in ConvertImageCommand (image_info=0x60fcd0, argc=19, argv=0x6143b0, metadata=0x0, exception=0x602ea0) at ../../wand/convert.c:3215 #5 0x776ab527 in MagickCommandGenesis ( image_info=image_info@entry=0x60aab0, command=0x4007f0 , argc=argc@entry=19, argv=argv@entry=0x7fffdc68, metadata=metadata@entry=0x0, exception=exception@entry=0x602ea0) at ../../wand/mogrify.c:168 #6 0x00400877 in ConvertMain (argv=0x7fffdc68, argc=19) at ../../utilities/convert.c:81 #7 main (argc=19, argv=0x7fffdc68) at ../../utilities/convert.c:92 ** Affects: imagemagick (Ubuntu) Importance: High Status: New ** Tags: regression regression-update ** Attachment added: "SH_HL_08_Step1_F028.png" https://bugs.launchpad.net/bugs/1793485/+attachment/5190921/+files/SH_HL_08_Step1_F028.png ** Changed in: imagemagick (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793485 Title: segfault in png to gif conversion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1793485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786933] Re: New upstream release 3.28.x
I have just verified it and don't see any issues. I tested all use cases listed in the description on metal and in a VM (VirtualBox). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786933 Title: New upstream release 3.28.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786933] Re: New upstream release 3.28.x
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786933 Title: New upstream release 3.28.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1786933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789920] Re: Installation in OEM mode broken on bionic
Michael, I've just tried again today. I have up waiting after 60 minutes. How long does it take in your case? FWIW I used a vm (kvm) for testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789920 Title: Installation in OEM mode broken on bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789920] Re: Installation in OEM mode broken on bionic
** Attachment added: "questions.dat" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+attachment/5187542/+files/questions.dat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789920 Title: Installation in OEM mode broken on bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789920] Re: Installation in OEM mode broken on bionic
** Attachment added: "templates.dat" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+attachment/5187543/+files/templates.dat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789920 Title: Installation in OEM mode broken on bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
