[Bug 1850754] [NEW] ceph-volume lvm list is O(n^2)

2019-10-31 Thread Dariusz Gadomski
). ** 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

[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-10-10 Thread Dariusz Gadomski
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

[Bug 1836361] Re: Windows guest display is inverted vertically

2019-08-27 Thread Dariusz Gadomski
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

[Bug 1836361] Re: Windows guest display is inverted vertically

2019-07-30 Thread Dariusz Gadomski
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"

[Bug 1836361] Re: Windows guest display is inverted vertically

2019-07-22 Thread Dariusz Gadomski
@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 --

[Bug 1836361] Re: Windows guest display is inverted vertically

2019-07-22 Thread Dariusz Gadomski
** 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

[Bug 1836361] Re: Windows guest display is inverted vertically

2019-07-12 Thread Dariusz Gadomski
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:

[Bug 1836361] Re: Windows guest display is inverted vertically

2019-07-12 Thread Dariusz Gadomski
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

[Bug 1836361] Re: Windows guest display is inverted vertically

2019-07-12 Thread Dariusz Gadomski
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

[Bug 1836361] Re: Windows guest display is inverted vertically

2019-07-12 Thread Dariusz Gadomski
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

[Bug 1836361] Re: Windows guest display is inverted vertically

2019-07-12 Thread Dariusz Gadomski
** 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: sp

[Bug 1836361] Re: Windows guest display is inverted vertically

2019-07-12 Thread Dariusz Gadomski
** 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

[Bug 1836361] Re: Windows guest display is inverted vertically

2019-07-12 Thread Dariusz Gadomski
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

[Bug 1836361] [NEW] Windows guest display is inverted vertically

2019-07-12 Thread Dariusz Gadomski
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

[Bug 1831021] Re: Extremely high memory consumption under heavy workload

2019-06-11 Thread Dariusz Gadomski
** 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:

[Bug 1830022] Re: DirtyCleanInterval should be 0 by default

2019-06-11 Thread Dariusz Gadomski
** 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:

[Bug 1374109] Re: epmd does not support binding to an IPv4 address anymore

2019-06-04 Thread Dariusz Gadomski
** 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 I

[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

2019-06-04 Thread Dariusz Gadomski
** 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:

[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

2019-06-04 Thread Dariusz Gadomski
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

[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

2019-06-04 Thread Dariusz Gadomski
** 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 PreserveJobHist

[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

2019-06-04 Thread Dariusz Gadomski
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

[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

2019-06-04 Thread Dariusz Gadomski
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

[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

2019-06-04 Thread Dariusz Gadomski
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

[Bug 1831021] Re: Extremely high memory consumption under heavy workload

2019-05-31 Thread Dariusz Gadomski
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

[Bug 1831021] Re: Extremely high memory consumption under heavy workload

2019-05-31 Thread Dariusz Gadomski
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

[Bug 1831021] Re: Extremely high memory consumption under heavy workload

2019-05-31 Thread Dariusz Gadomski
** 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:

[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

2019-05-30 Thread Dariusz Gadomski
.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)

[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

2019-05-30 Thread Dariusz Gadomski
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

[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

2019-05-30 Thread Dariusz Gadomski
** 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

[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

2019-05-30 Thread Dariusz Gadomski
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

[Bug 1830022] Re: DirtyCleanInterval should be 0 by default

2019-05-30 Thread Dariusz Gadomski
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

[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

2019-05-30 Thread Dariusz Gadomski
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: Und

[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

2019-05-30 Thread Dariusz Gadomski
@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

[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

2019-05-30 Thread Dariusz Gadomski
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

[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

2019-05-30 Thread Dariusz Gadomski
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

[Bug 1831021] Re: Extremely high memory consumption under heavy workload

2019-05-30 Thread Dariusz Gadomski
** 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

[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

2019-05-30 Thread Dariusz Gadomski
** 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

[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs

2019-05-30 Thread Dariusz Gadomski
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

[Bug 1831021] Re: Extremely high memory consumption under heavy workload

2019-05-30 Thread Dariusz Gadomski
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

[Bug 1831021] [NEW] Extremely high memory consumption under heavy workload

2019-05-30 Thread Dariusz Gadomski
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

[Bug 1830022] Re: DirtyCleanInterval should be 0 by default

2019-05-28 Thread Dariusz Gadomski
** 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:

[Bug 1830022] Re: DirtyCleanInterval should be 0 by default

2019-05-28 Thread Dariusz Gadomski
** 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:

[Bug 1830022] [NEW] DirtyCleanInterval should be 0 by default

2019-05-22 Thread Dariusz Gadomski
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

[Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal

2019-02-20 Thread Dariusz Gadomski
** 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

[Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal

2018-12-18 Thread Dariusz Gadomski
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

[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

2018-12-13 Thread Dariusz Gadomski
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:

[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

2018-12-13 Thread Dariusz Gadomski
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

[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

2018-12-13 Thread Dariusz Gadomski
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

[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

2018-12-13 Thread Dariusz Gadomski
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

[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

2018-12-11 Thread Dariusz Gadomski
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

[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

2018-12-11 Thread Dariusz Gadomski
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"

[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

2018-12-11 Thread Dariusz Gadomski
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

[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

2018-12-06 Thread Dariusz Gadomski
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"

[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

2018-12-06 Thread Dariusz Gadomski
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)

[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

2018-12-06 Thread Dariusz Gadomski
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

[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

2018-12-06 Thread Dariusz Gadomski
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. +

[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

2018-12-06 Thread Dariusz Gadomski
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

[Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never

2018-12-06 Thread Dariusz Gadomski
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

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-12-05 Thread Dariusz Gadomski
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,

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-30 Thread Dariusz Gadomski
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

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-30 Thread Dariusz Gadomski
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

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-30 Thread Dariusz Gadomski
** 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

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-30 Thread Dariusz Gadomski
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:

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-30 Thread Dariusz Gadomski
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

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-30 Thread Dariusz Gadomski
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

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-30 Thread Dariusz Gadomski
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,

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-29 Thread Dariusz Gadomski
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

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-29 Thread Dariusz Gadomski
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:

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-28 Thread Dariusz Gadomski
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:

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-28 Thread Dariusz Gadomski
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

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-27 Thread Dariusz Gadomski
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:

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-27 Thread Dariusz Gadomski
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,

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-27 Thread Dariusz Gadomski
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,

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-27 Thread Dariusz Gadomski
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,

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-27 Thread Dariusz Gadomski
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,

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-23 Thread Dariusz Gadomski
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

[Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center

2018-11-22 Thread Dariusz Gadomski
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:

[Bug 1755490] Re: Incorrect information about display shown in unity-control-center

2018-11-21 Thread Dariusz Gadomski
** 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

[Bug 1755490] Re: Incorrect information about display shown in unity-control-center

2018-11-21 Thread Dariusz Gadomski
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

[Bug 1755490] Re: Incorrect information about display shown in unity-control-center

2018-11-20 Thread Dariusz Gadomski
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

[Bug 1755490] Re: Incorrect information about display shown in unity-control-center

2018-11-20 Thread Dariusz Gadomski
** 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 &

[Bug 1755490] Re: Incorrect information about display shown in unity-control-center

2018-11-20 Thread Dariusz Gadomski
** 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

[Bug 1598183] Re: Operation not permitted while writing to symlinked fuse locations

2018-11-07 Thread Dariusz Gadomski
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

[Bug 1755490] Re: Incorrect information about display shown in unity-control-center

2018-11-05 Thread Dariusz Gadomski
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

[Bug 1749289] Re: Installer stops after pressing Cancel on Select a language screen during OEM install

2018-10-12 Thread Dariusz Gadomski
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

[Bug 1749289] Re: Installer stops after pressing Cancel on Select a language screen during OEM install

2018-10-05 Thread Dariusz Gadomski
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

[Bug 1749289] Re: Installer stops after pressing Cancel on Select a language screen during OEM install

2018-09-26 Thread Dariusz Gadomski
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

[Bug 1749289] Re: Installer stops after pressing Cancel on Select a language screen during OEM install

2018-09-24 Thread Dariusz Gadomski
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

[Bug 1793485] Re: segfault in png to gif conversion

2018-09-20 Thread Dariusz Gadomski
** 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

[Bug 1793485] [NEW] segfault in png to gif conversion

2018-09-20 Thread Dariusz Gadomski
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

[Bug 1786933] Re: New upstream release 3.28.x

2018-09-20 Thread Dariusz Gadomski
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:

[Bug 1786933] Re: New upstream release 3.28.x

2018-09-20 Thread Dariusz Gadomski
** 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

[Bug 1789920] Re: Installation in OEM mode broken on bionic

2018-09-17 Thread Dariusz Gadomski
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

[Bug 1789920] Re: Installation in OEM mode broken on bionic

2018-09-11 Thread Dariusz Gadomski
** 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

[Bug 1789920] Re: Installation in OEM mode broken on bionic

2018-09-11 Thread Dariusz Gadomski
** 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

[Bug 1789920] Re: Installation in OEM mode broken on bionic

2018-09-11 Thread Dariusz Gadomski
As advised by xnox I have retried the installation with adding apt- setup/proposed=true. The result was identical - after rebooting to perform the oem configuration the boot process stucks. Attaching installer logs. -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1789920] Re: Installation in OEM mode broken on bionic

2018-09-11 Thread Dariusz Gadomski
** Attachment added: "lsb-release" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+attachment/5187539/+files/lsb-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789920

[Bug 1789920] Re: Installation in OEM mode broken on bionic

2018-09-11 Thread Dariusz Gadomski
** Attachment added: "initial-status.gz" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+attachment/5187540/+files/initial-status.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1789920] Re: Installation in OEM mode broken on bionic

2018-09-11 Thread Dariusz Gadomski
** Attachment added: "status" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+attachment/5187536/+files/status -- 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:

[Bug 1789920] Re: Installation in OEM mode broken on bionic

2018-09-11 Thread Dariusz Gadomski
** Attachment added: "media-info" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920/+attachment/5187538/+files/media-info -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789920

<    1   2   3   4   5   6   7   8   >