Hey Pon, the debdiff contains changes to a bunch of files inside .pc
which should not be included.
Can you try generating the debdiff again wtihout these changes?
Once of the ways would be to drop in a patch to d/patches and add it
with quilt or apply it with the "patch" command and then run
** Tags added: se se-sponsor-dgadomski
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/2035061
Title:
uptime -p reports incorrect output after 52 weeks
Status in procps
Bionic verification. Procedure unchanged.
tzdata 2023c-0ubuntu0.18.04
test_2023a (__main__.TestZoneinfo)
Test Egypt uses DST again from 2023a release. ... ok
test_2023c (__main__.TestZoneinfo)
Test Lebanon's reverted DST delay from 2023c release. ... ok
(...)
test_systemv_timezones
Same procedure again, this time for focal.
tzdata 2023c-0ubuntu0.20.04.0
test_2023a (__main__.TestZoneinfo)
Test Egypt uses DST again from 2023a release. ... ok
test_2023c (__main__.TestZoneinfo)
Test Lebanon's reverted DST delay from 2023c release. ... ok
(...)
test_2023a (__main__.TestICU)
Verification for jammy. Same procedure as for kinetic above.
tzdata 2023c-0ubuntu0.22.04.0
test_2023a (__main__.TestZoneinfo)
Test Egypt uses DST again from 2023a release. ... ok
test_2023c (__main__.TestZoneinfo)
Test Lebanon's reverted DST delay from 2023c release. ... ok
(...)
test_2023a
Verification for kinetic.
I've run autopkgtests locally on tzdata from the proposed pocket using [1]. All
newly added tests were successful. Additionally I've run the Egypt DST test
manually, like described for the previously tested version.
test_2023a (__main__.TestZoneinfo)
Test Egypt uses
Bionic verification:
$ sudo timedatectl set-ntp false
$ sudo timedatectl set-timezone "Africa/Cairo"
$ timedatectl set-time "2023-04-27 23:59:58" && sleep 3 && date
Fri Apr 28 00:00:01 EET 2023
After upgrade to 2023b-0ubuntu0.18.04.0:
$ sudo timedatectl set-time "2023-04-27 23:59:58" && sleep 3
Focal verification:
$ sudo timedatectl set-ntp false
$ sudo timedatectl set-timezone "Africa/Cairo"
$ timedatectl set-time "2023-04-27 23:59:58" && sleep 3 && date
Fri Apr 28 00:00:01 EET 2023
After upgrade to 2023b-0ubuntu0.20.04.0:
$ sudo timedatectl set-time "2023-04-27 23:59:58" && sleep 3 &&
Jammy verification:
$ sudo timedatectl set-ntp false
$ sudo timedatectl set-timezone "Africa/Cairo"
$ timedatectl set-time "2023-04-27 23:59:58" && sleep 3 && date
Fri Apr 28 00:00:01 EET 2023
After upgrade to 2023b-0ubuntu0.22.04.0:
$ sudo timedatectl set-time "2023-04-27 23:59:58" && sleep 3 &&
Kinetic verification:
$ sudo timedatectl set-ntp false
$ sudo timedatectl set-timezone "Africa/Cairo"
$ timedatectl set-time "2023-04-27 23:59:58" && sleep 3 && date
Fri Apr 28 00:00:01 EET 2023
After upgrade to 2023b-0ubuntu0.22.10.0:
$ sudo timedatectl set-time "2023-04-27 23:59:58" && sleep 3
Public bug reported:
[ Impact ]
Recently the Egyptian authorities decided to restore DST. The first
switch after the change is expected to take place on last Friday of
April. The upstream tzdata 2023a release already reflects this change.
[ Test Plan ]
* Set system timezone to Egypt (e.g.
I have prepared a patch for bionic and tested it:
# ip link add eth3 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth3; date
śro, 16 lut 2022, 15:20:26 CET
IP-Config: eth3 hardware address ba:e2:3c:e9:db:e4 mtu 1500 DHCP RARP
Lowered timeout to match user request = (2 s)
IP-Config: no
Thanks Iain. Looks like both of us sponsored it for the queue. I'd
appreciate rejecting either one of them.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1930359
** Description changed:
[Impact]
systemd-networkd renames nic just after udev renamed it
e.g
kernel: [ 2.827368] vmxnet3 :0b:00.0 ens192: renamed from eth0
kernel: [ 7.562729] vmxnet3 :0b:00.0 eth0: renamed from ens192
systemd-networkd[511]: ens192: Interface name
I can verify that version 2.20.11-0ubuntu27.8 for focal fixes the issue.
Running on server install:
sudo apt install apport-gtk
apt offers gnome-terminal as dependency.
sudo apt install apport-kde
pulls in konsole as dependency.
** Tags removed: verification-needed verification-needed-focal
** Changed in: apport (Ubuntu Focal)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1881976
Title:
apport-gtk and apport-kde
The fix has been superseded by a security update. In the meantime a
concurrent update of pycodestyle broke the apport build. I have
backported fixes to the build issue from Groovy and uploaded the patch
yesterday. Once the update is reviewed it should be available via the
-proposed pocket.
--
I have verified it for Bionic using ntp 1:4.2.8p10+dfsg-5ubuntu7.2.
No segfault observed:
sudo ntpq -p
remote refid st t when poll reach delay offset jitter
==
0.ubuntu.pool.n .POOL. 16 p - 64 0 0.000 0.000 0.000
I have verified it for Bionic using ntp 1:4.2.8p10+dfsg-5ubuntu7.2.
No segfault observed:
sudo ntpq -p
remote refid st t when poll reach delay offset jitter
==
0.ubuntu.pool.n .POOL. 16
** Tags added: sts-sponsor-dgadomski
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1881976
Title:
apport-gtk and apport-kde install xiterm+thai as dependency (x
** Tags added: sts-sponsor-dgadomski
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1885562
Title:
[fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode
Status in nss
Marking Eoan as Won't fix due to EOL.
** Changed in: libseccomp (Ubuntu Eoan)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
SRU proposal for focal.
** Patch added: "focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1881976/+attachment/5395298/+files/focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in
SRU proposal for groovy
** Patch removed: "groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1881976/+attachment/5395109/+files/groovy.debdiff
** Patch removed: "focal.debdiff"
New => In Progress
** Changed in: apport (Ubuntu)
Importance: Undecided => Medium
** Changed in: apport (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: apport (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
** Changed in: apport (Ubuntu Focal
I tested libnss3 2:3.49.1-1ubuntu1.3 on focal, however this was not done
in FIPS-mode (as there are no FIPS packages for focal available).
I did not find a way to trigger the signature verification outside FIPS
mode, but in normal usecase (FIPS disabled) everything works as
expected, no
Tested with 2:3.35-2ubuntu2.10 on 18.04:
sudo chronyd -d
2020-07-23T08:40:19Z chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC
+PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS +IPV6 -DEBUG)
2020-07-23T08:40:19Z Frequency -1.068 +/- 0.045 ppm read from
/var/lib/chrony/chrony.drift
(no
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1885562
Title:
[fips]
** Also affects: ntp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1884265
Title:
[fips] ntpq segfaults when
** Description changed:
+ [Impact]
+
+ * Prevents using some parts of nss in FIPS mode - e.g.
+ libfreeblpriv3.so (failed asserts). The library during initialization
+ tries to verify it's own binaries against signatures in chk files
+ shipped along with it (created at build time). They are
As discussed with Richard outside LP: we agreed that adding symlinks is
an acceptable solution to this problem.
Debdiffs linked.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
** Changed in: nss (Ubuntu)
Assignee: Richard Maciel Costa (richardmaciel) => Dariusz Gadomski
(dgadomski)
** Changed in: nss (Ubuntu Bionic)
Assignee: Richard Maciel Costa (richardmaciel) => Dariusz Gadomski
(dgadomski)
--
You received this bug notification because you are a
Oh, I have found it: ppa:j-latten/joydevppa
Works perfectly. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1884265
Title:
[fips] Not fully initialized digest
Sure. Sounds good. Do you have it available in a ppa anywhere to give it
a try?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1884265
Title:
[fips] Not fully initialized
@j-latten: please let me know if I can provide any help with this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1884265
Title:
[fips] Not fully initialized digest
@richardmaciel please let me know if I can help you with anything with
regard to this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1885562
Title:
[fips]
The patches I've uploaded implement the Solution B from the description.
It actually applies only to Bionic, but I believe it's worth having it
in Focal if it gets FIPS certification and for Groovy - to keep it for
the future releases.
--
You received this bug notification because you are a
groovy fix
** Patch added: "groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1885562/+attachment/5388751/+files/groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
Focal debdiff reupload
** Patch added: "focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1885562/+attachment/5388755/+files/focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
SRU proposal for bionic
** Patch removed: "focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1885562/+attachment/5388752/+files/focal.debdiff
** Patch removed: "groovy.debdiff"
Bionic debdiff reupload
** Patch added: "bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1885562/+attachment/5388756/+files/bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
Groovy debdiff re-upload
** Patch added: "groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1885562/+attachment/5388754/+files/groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in
SRU proposal for Focal
May be useful if it gets FIPS-certified.
** Patch added: "focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1885562/+attachment/5388752/+files/focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Description changed:
In FIPS mode there are some additional checks performed.
They lead to verifying binaries signatures. Those signatures are shipped
in the libnss3 package as *.chk files installed in
/usr/lib/$(DEB_HOST_MULTIARCH)/nss. Along with those files are the
libraries
I have briefly analyzed nss code - it uses the nspr library for, inter
alia, file access abstraction. From what I saw in the docs it does not
offer any form of symlink resolution, so it may be nontrivial to safely
implement it in nss code.
--
You received this bug notification because you are a
** Description changed:
- When in FIPS mode there some additional checks performed.
+ In FIPS mode there are some additional checks performed.
They lead to verifying binaries signatures. Those signatures are shipped
in the libnss3 package as *.chk files installed in
** Summary changed:
- freebl_fipsSoftwareIntegrityTest fails in FIPS mode
+ [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
*** This bug is a security vulnerability ***
Public security bug reported:
When in FIPS mode there some additional checks performed.
They lead to verifying binaries signatures. Those signatures are shipped
in the libnss3 package as *.chk files installed in
/usr/lib/$(DEB_HOST_MULTIARCH)/nss.
** Description changed:
In FIPS mode on Bionic MD5 is semi-disabled causing some applications to
segfault.
Test case:
sudo apt install ntp
ntpq -p
Segmentation fault (core dumped)
What happens there is ntpq wants to iterate all available digests
(list_digest_names in
Changelog in bug #1553309 mentions "- debian/patches/openssl-1.0.2g-
fips-md5-allow.patch: [PATCH 3/6] Allow md5 in fips mode."
I am however unaware of the context of this change (e.g. MD5 is not
included here: [1])
[1]
** Changed in: openssl (Ubuntu Bionic)
Importance: Undecided => Medium
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
FTR: EVP_add_digest(EVP_md5()); is not present in the Xenial build,
hence there's no crash there.
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1884265
*** This bug is a security vulnerability ***
Public security bug reported:
In FIPS mode on Bionic MD5 is semi-disabled causing some applications to
segfault.
Test case:
sudo apt install ntp
ntpq -p
Segmentation fault (core dumped)
What happens there is ntpq wants to iterate all available
** Changed in: network-manager (Ubuntu Eoan)
Assignee: Dariusz Gadomski (dgadomski) => (unassigned)
** Changed in: network-manager (Ubuntu Focal)
Assignee: Dariusz Gadomski (dgadomski) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Sure Dan, I'm looking into it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1733321
Title:
network-manager ADT tests fail with on ppc64el with artful/linux
** Changed in: network-manager (Ubuntu Eoan)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
** Changed in: network-manager (Ubuntu Focal)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Ubuntu
Similarly for bionic using version 237-3ubuntu10.39 verification was
also successsful:
ubuntu@bionic:~$ groups
ubuntu adm dialout cdrom sudo dip plugdev users lpadmin sambashare vboxsf
** Tags removed: verification-needed verification-needed-bionic
verification-needed-eoan
** Tags added:
I have repeated verification for eoan (242-7ubuntu3.7) with identical
results.
ubuntu@eoan:~$ groups
ubuntu adm dialout cdrom sudo dip plugdev users lpadmin lxd sambashare
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
With identical setup and testcase for eoan I have managed to
successfully verify the patch with version 242-7ubuntu3.3:
ubuntu@eoan:~$ groups
ubuntu adm dialout cdrom sudo dip plugdev users lpadmin lxd sambashare
ubuntu@eoan:~$
** Tags removed: verification-needed-eoan
** Tags added:
I have just verified bionic. With version 237-3ubuntu10.34 after
replaying test case from the description I see the groups from
/etc/security/group.conf (dialout, users) added:
ubuntu@bionic:~$ groups
ubuntu adm dialout cdrom sudo dip plugdev users lpadmin sambashare vboxsf
** Tags removed:
systemd in Xenial differs to much to cleanly apply the upstream fix. It
would require reimplementing it and may be more risky than useful.
Marking Won't fix.
** Changed in: systemd (Ubuntu Xenial)
Status: New => Won't Fix
--
You received this bug notification because you are a member of
SRU proposal for bionic (patches split)
** Patch removed: "bionic_systemd_237-3ubuntu10.34.debdiff"
https://bugs.launchpad.net/systemd/+bug/1762391/+attachment/5321138/+files/bionic_systemd_237-3ubuntu10.34.debdiff
** Patch added: "bionic_systemd_237-3ubuntu10.34.debdiff"
SRU proposal for eoan (patches split)
** Patch removed: "eoan_systemd_242-7ubuntu3.3.debdiff"
https://bugs.launchpad.net/systemd/+bug/1762391/+attachment/5321139/+files/eoan_systemd_242-7ubuntu3.3.debdiff
** Patch added: "eoan_systemd_242-7ubuntu3.3.debdiff"
SRU proposal for eoan.
** Patch added: "eoan_systemd_242-7ubuntu3.3.debdiff"
https://bugs.launchpad.net/systemd/+bug/1762391/+attachment/5321139/+files/eoan_systemd_242-7ubuntu3.3.debdiff
** Description changed:
[Impact]
- pam_setcred call was missing in systemd making it's
SRU proposal for bionic.
** Patch added: "bionic_systemd_237-3ubuntu10.34.debdiff"
https://bugs.launchpad.net/systemd/+bug/1762391/+attachment/5321138/+files/bionic_systemd_237-3ubuntu10.34.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Description changed:
+ [Impact]
+
+ pam_setcred call was missing in systemd making it's implementation of the PAM
protocol problematic. It could manifest in different ways, but one particularly
problematic for enterprise environments was the fact that
+ processes were never getting group
SRU proposal for focal.
Upstream regression has been resolved and the fix is integrated in the
patch.
** No longer affects: gnome-terminal (Ubuntu Eoan)
** Patch removed: "focal_systemd_244-3ubuntu4.debdiff"
** No longer affects: gnome-terminal (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1762391
Title:
pam_group.so is not evaluated by gnome-terminal
Status in
Please hold on with uploading until
https://github.com/systemd/systemd/issues/14567 is resolved.
** Bug watch added: github.com/systemd/systemd/issues #14567
https://github.com/systemd/systemd/issues/14567
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
SRU proposal for Focal (upstream backport).
** Patch added: "focal_systemd_244-3ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1762391/+attachment/5320077/+files/focal_systemd_244-3ubuntu4.debdiff
--
You received this bug notification because you are a member
signee: (unassigned) => Dariusz Gadomski (dgadomski)
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
** Also affects: gnome-terminal (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Eoan)
Importanc
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
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
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
Touch seeded packages, which is
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:
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
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1830022
Title:
DirtyCleanInterval should be 0 by default
Status in cups package in Ubuntu:
Confirmed
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1831021
Title:
Extremely high memory consumption under heavy workload
Status in cups package in Ubuntu:
** 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
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1747765
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
** 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
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
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
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
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
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
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1831021
Title:
Extremely high memory consumption under heavy workload
Status in cups package
.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)
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
Touch seeded
** Also affects: cups (Ubuntu Cosmic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1747765
Title:
PreserveJobHistory and
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
Touch seeded
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
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1830022
Title:
@sponsors: Eoan already has the fix from Debian.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1747765
Title:
PreserveJobHistory and PreserveJobLog do not respect numeric
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
Touch seeded
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
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
Touch seeded
** 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
** 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
Touch seeded packages, which is subscribed to cups in Ubuntu.
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
1 - 100 of 247 matches
Mail list logo
