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 "dpk
I have checked the s390 and armhf - they seem unrelated to the patch,
look more like infra hiccup (connection issues). I have restarted them.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchp
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. Afr
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 &
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 &&
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 &&
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 &&
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 respo
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 DST
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 (__ma
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)
Test
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 (__main__.Test
** 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 chan
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
T
** 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 pac
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
Touch seeded packag
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 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
Touch seeded pa
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
Touch seeded pa
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 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
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
Touch seeded
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
Touch seeded
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
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
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1804576
Title:
MaxJobTime=0 results i
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
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.
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
** Tags added: rls-nn-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:
DirtyCleanInterval should be 0 by default
Status in cups package in Ubuntu:
Co
** Tags removed: rls-nn-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:
DirtyCleanInterval should be 0 by default
Status in cups package in Ubuntu:
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;
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
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.
https://bugs.launc
** 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
** 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
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 pac
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 packages
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
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1747765
Title:
PreserveJobHistory and PreserveJobLog do not respect numeric in
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:
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 pa
** 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 Preserv
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 pa
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
** 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 in
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
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
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:
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 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
** 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
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
** 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
** 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
Bug
** 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:
T
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 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
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 s
** 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
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
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
u)
Assignee: (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)
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
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 p
** 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 syst
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"
https://bugs.launchpad.net/systemd/+bug/1762391/+attachment/5320077/+files/focal_sys
** 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 mem
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 packages
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 implementati
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"
https://bugs.launchpad.net/sys
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"
https://bugs.lau
Seth: those values were somehow calculated from a number of runs. A
single pyperformance benchmark run took ~20 minutes and I repeated each
of them 3 times.
I still have the 'raw' outputs of pyperformance if needed. From those I
see that there are at least 3 values for each test and also there is
Xenial pyperformance results with -fstack-protector-strong changed to
-fstack-protector.
** Attachment added: "xenial-fsp-01.json"
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+attachment/5015696/+files/xenial-fsp-01.json
--
You received this bug notification because you
SRU proposal for artful.
Previous releases are not affected, as this was introduced with some
refactoring done to cupsGetNamedDest (cups/dest.c).
** Patch added: "artful_cups_2.2.4-7ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1729910/+attachment/5005833/+files/artful_
/etc/cups/printers.conf
2) Execute lpstat -d
3) Above will output default defined in prints.conf instead of
~/cups/lpoptions
** Changed in: cups (Ubuntu Artful)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member
SRU proposal for Artful.
** Patch removed: "artful_cups_2.2.4-7ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1729910/+attachment/5005833/+files/artful_cups_2.2.4-7ubuntu3.debdiff
** Patch added: "artful_cups_2.2.4-7ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/
** Description changed:
[Impact]
- * During some refactoring done to cupsGetNamedDest function used in
+ * During some refactoring done to cupsGetNamedDest function used in
many different parts of the code a regression has been introduced
causing the per-user default printer setting (in
** Tags removed: verification-needed
--
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/1729910
Title:
lp ignores ~/.cups/lpoptions in 17.10
Status in cups package in Ubuntu:
Hello Matthias. Is there any progress with applying those features to
Xenial? Please let me know if you need any testing to be done.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.n
Adding SRU proposal for wily.
** Description changed:
+ [Impact]
+
+ * A lack of proper synchronization in ifupdown causes a race condition
+ resulting in occasional incorrect network interface initialization (e.g.
+ in bonding case - wrong bonding settings, network unavailable because
+ slave<
Adding SRU proposal for Vivid.
** Patch added: "vivid_ifupdown_0.7.48.1ubuntu11.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4501798/+files/vivid_ifupdown_0.7.48.1ubuntu11.debdiff
--
You received this bug notification because you are a member of Ubuntu
Adding SRU proposal for Trusty (to make ifenslave compatible with
ifupdown changes).
** Patch added: "trusty_ifenslave_2.4ubuntu1.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4501800/+files/trusty_ifenslave_2.4ubuntu1.2.debdiff
--
You received this b
Adding SRU proposal for Trusty.
** Patch added: "trusty_ifupdown_0.7.47.2ubuntu4.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4501799/+files/trusty_ifupdown_0.7.47.2ubuntu4.2.debdiff
--
You received this bug notification because you are a member of U
** Description changed:
[Impact]
- * A lack of proper synchronization in ifupdown causes a race condition
+ * Lack of proper synchronization in ifupdown causes a race condition
resulting in occasional incorrect network interface initialization (e.g.
in bonding case - wrong bonding setti
Public bug reported:
There is an error observed when Ubuntu is configured to perform
authentication via pam_vas (Vintela Authentication Services by Dell) in
a disconnected mode (using cached authentication).
Steps to reproduce:
1. Configure pam_vas client authenticating to a remote server.
2. Per
** Changed in: policykit-1 (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1510824
Ti
** Description changed:
There is an error observed when Ubuntu is configured to perform
authentication via pam_vas (Vintela Authentication Services by Dell) in
a disconnected mode (using cached authentication).
Steps to reproduce:
1. Configure pam_vas client authenticating to a remote
** Summary changed:
- PolkitAgentSession ignores multiline output (with pam_vas)
+ PolkitAgentSession incorrectly handles multiline output (with pam_vas)
** Description changed:
There is an error observed when Ubuntu is configured to perform
authentication via pam_vas (Vintela Authentication
** Bug watch added: freedesktop.org Bugzilla #92886
https://bugs.freedesktop.org/show_bug.cgi?id=92886
** Also affects: policykit-1 via
https://bugs.freedesktop.org/show_bug.cgi?id=92886
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a m
Adding SRU proposal for Xenial.
** Patch added: "xenial_ifupdown_0.7.54ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4515989/+files/xenial_ifupdown_0.7.54ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
To
Miroslav, thanks for taking a look.
Sure, I can improve the patch. I'll attach the new version as soon as
it's done.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/15108
Created attachment 119643
Refactoring to use send_to_helper
I have refactored the code to make use of send_to_helper instead of
duplicating the code.
I've chosen to apply it on top of the previous change to keep 2
different actions (escaping PAM_TEXT_INFO and refactoring) on the same
step.
I hav
Typo, what I've meant in the above comment is that I wanted to avoid
doing 2 different actions in the same commit.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1510824
Created attachment 119702
Refactoring to use send_to_helper
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1510824
Title:
PolkitAgentSession incorrectly handles multil
Added SRU proposal for Xenial.
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the uplo
Added SRU proposal for wily.
** Patch added: "wily_policykit-1_0.105-11ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1510824/+attachment/4522624/+files/wily_policykit-1_0.105-11ubuntu3.debdiff
--
You received this bug notification because you are a member of Ubu
Added SRU proposal for trusty.
** Patch added: "trusty_policykit-1_0.105-4ubuntu3.14.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1510824/+attachment/4522626/+files/trusty_policykit-1_0.105-4ubuntu3.14.04.1.debdiff
--
You received this bug notification because you
Added SRU proposal for vivid.
** Patch added: "vivid_policykit-1_0.105-8ubuntu5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1510824/+attachment/4522625/+files/vivid_policykit-1_0.105-8ubuntu5.debdiff
--
You received this bug notification because you are a member of Ub
1 - 100 of 247 matches
Mail list logo
