James, I assume that debdiff is not symlink-aware and it does produce
the duplicated output. From what I see dpkg-source --commit produced a
correct patch.
Is there a trick to make debdiff skip it? Or simply removing duplicated
lines from debdiff output is the correct way to go?
I'd appreciate an
Thanks Joe.
There has to be another factor coming into play, as my setup contains
"use only for resources on its network".
$ nmcli connection show my-vpn | grep -e ipv4.never-default -e
ipv4.dns-priority
ipv4.dns-priority: -30
ipv4.never-default: yes
Ar
Joe, I still can't reproduce your issue.
Can you please verify against what I'm trying:
1. Setup a VPN that provides DNS via DHCP
2. Connect to that VPN and verify DNS by:
$ systemd-resolve --status
(...)
Link 4 (tun0)
(...)
DNS Servers: X.X.X.X
(...)
3. Disconnect VPN and edit connection:
$ nmcli
Can you connect to that VPN with the same settings, but from a virtual
machine with a freshly installed system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851793
Title:
NetworkManager OpenVPN No
The behavior described in this bug seems to be consistent with what is
the default in Eoan (19.10).
Uros, are you able to check if 19.10 network-manager is also affected
with this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
I examined the differences between bionic and upstream NetworkManager
source around systemd-resolved interactions. I did not see any
significant differences to blame for this.
I have just tested it on a build from nm-1-10 branch of upstream
NetworkManager and the behavior seems to be identical: th
I've checked that and what I see is:
the DNS setting is visible in nmcli output, but it's not propagated to
systemd-resolved (no DNS entry for the VPN connection in systemd-resolved
--status).
Looking into that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** 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/1850754
Title:
ceph-volume lvm list is O(n^2)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ceph/+bug/185
SRU proposal for eoan.
** Patch added: "eoan_ceph_14.2.2-0ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1850754/+attachment/5303258/+files/eoan_ceph_14.2.2-0ubuntu4.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
SRU proposal for bionic.
** Patch added: "bionic_ceph_12.2.12-0ubuntu0.18.04.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1850754/+attachment/5303259/+files/bionic_ceph_12.2.12-0ubuntu0.18.04.4.debdiff
--
You received this bug notification because you are a member of Ubuntu
SRU proposal for focal
** Description changed:
+ [Impact]
+ ceph-volume lvm calls take too much time and the time grows exponentially.
+ A simple call may take several minutes depending on the LV configuration.
+
+ [Test Case]
+ 1. Create a setup with a large number of disks and logical volumes
** Also affects: cloud-archive
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
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 Ubun
** 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.lau
** 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 a
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: verif
** 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
).
** 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
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 buil
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
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_20
@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
--
** 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
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
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 me
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 Ubunt
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
** 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
** 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 us
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
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-websoc
** 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.lau
** 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/ub
** 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
** 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:
PreserveJobHist
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
** 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
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 N
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:
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:
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
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
** 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:
http
ups_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 Cosm
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
** 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 nu
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
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
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
@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
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 s
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 subscr
** 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/cup
** 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
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
Ti
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 con
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;
** 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.la
** 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.laun
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
u
** 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
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.
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:
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:0
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 im
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.bk
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
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/
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
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/ubun
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)
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 subs
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.
+ Th
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
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
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
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 y
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-
** 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/u
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-0ubuntu
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
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 ar
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, w
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 Tes
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: verifi
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
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
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:
I
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, w
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,
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,
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,
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 r
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: h
** 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
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
B
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
Tit
** 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 & hei
** 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
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 Ub
201 - 300 of 789 matches
Mail list logo
