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
** 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:
** 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:
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
** 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
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
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
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:
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 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
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
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"
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
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"
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 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
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.
+
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
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
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
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.
** 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:
** 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
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"
in
/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 mem
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"
I have managed to prepare the static build without PIE on top the latest
artful version [1].
I have added the results to the same spreadsheet. What I've found
particularly interesting are the results of the python_startup &
python_startup_no_site tests. In subsequent runs (the result in the
Thanks for the explanation Matthias. I have added the Xenial variant you
asked for to the spreadsheet.
The artful will follow once I'm after a couple of days out.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in
Matthias, I have made a series of pyperformance benchmarks [1] to
compare the influence of the factors listed by Elvis on Xenial and
Artful. All runs were done on the same machine (metal) with a fresh
Ubuntu cloud image.
My observations confirm that both: changing fpectl and fPIC for _math.c
Patch proposal for Artful.
** Patch added: "artful_bluez_5.45-0ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+attachment/4928420/+files/artful_bluez_5.45-0ubuntu3.debdiff
** Patch removed: "artful_bluez_5.45-0ubuntu3.debdiff"
Artful patch proposal.
** Patch added: "artful_bluez_5.45-0ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+attachment/4928336/+files/artful_bluez_5.45-0ubuntu3.debdiff
** Patch removed: "zesty_bluez_5.43-0ubuntu2.debdiff"
Till,
The printer in question is was used completely *outside* CUPS - via the
/dev/usb/lp* nodes only. Although there was also an attempt with using it with
a raw queue - with the same result: whenever CUPS was enabled or the printer
was not blacklisted the output from the printer was
Patch proposal for Artful.
** Patch added: "cups_2.2.3-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1695884/+attachment/4889375/+files/cups_2.2.3-1ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
CUPS USB probing malforms Epson TM-T70 (vendorid: 0x04b8 productid:
0x0202) which is used outside CUPS (via usblp driver).
No matter whether the printer is set up as a CUPS raw printer or it's
not used via CUPS (but rather via a device node under usblp control) the
** Description changed:
+ [Impact]
+
+ * The package contains misleading documentation mentioning the use of
+ /etc/bluetooth/rfcomm.conf for rfcomm setup while the support for config
+ file has been dropped after 14.04 release. I have directly received a
+ question about it from a user mislead
Patch proposal for Zesty.
** Tags added: sts sts-sponsor
** Patch added: "zesty_bluez_5.43-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+attachment/4841667/+files/zesty_bluez_5.43-0ubuntu2.debdiff
--
You received this bug notification because you are a
** Summary changed:
- Dropped rfcomm.conf still mentioned
+ Deprecated rfcomm.conf still mentioned
** Description changed:
Support for config files has been dropped upstream in 2012 (however
version shipped with Trusty still supports it), but the latest versions
(including Xenial and
Public bug reported:
Support for config files has been dropped upstream in 2012 (however
version shipped with Trusty still supports it), but the latest versions
(including Xenial and Zesty) still mention it in the docs and in the
legacy /etc/init/bluetooth.conf file.
** Affects: bluez (Ubuntu)
Of course I meant Xenial and Yakkety. Thanks for noticing that Robie.
The versions I tested:
* Xenial
libgtk-3-0:
Installed: 3.18.9-1ubuntu3.2
* Yakkety:
libgtk-3-0:
Installed: 3.20.9-1ubuntu2.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Thanks Till & Brian.
In the same environment that served as a reproducer the new version
fixes the issue.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I have just verified it for Trusty and Yakkety on the same images that
were used earlier to reproduce it.
The issue is gone.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Tags removed: sts-sponsor
--
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/1665018
Title:
client tools ignore -h option without port number
Status in cups package in
SRU proposal for Trusty.
** Patch added: "trusty_cups_1.7.2-0ubuntu1.8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1665018/+attachment/4819939/+files/trusty_cups_1.7.2-0ubuntu1.8.debdiff
** Tags added: sts-sponsor
--
You received this bug notification because you are a
of the one given by -h option).
If a port number is given (e.g. server2:631) the commands work as
expected.
** Affects: cups (Ubuntu)
Importance: Medium
Assignee: Dariusz Gadomski (dgadomski)
Status: New
** Tags: sts
** Changed in: cups (Ubuntu)
Importance: Undecided => Med
Yakkety SRU proposal with fixed version number.
** Patch removed: "yakkety_gtk+3.0_3.20.9-1ubuntu3.debdiff"
https://bugs.launchpad.net/hundredpapercuts/+bug/1550983/+attachment/4808140/+files/gtk+3.0_3.20.9-1ubuntu3.debdiff
** Patch added: "yakkety_gtk+3.0_3.20.9-1ubuntu2.1.debdiff"
** Description changed:
- [Impact]
+ [Impact]
There are some unlinked calls to libGL.so.1 undetected in the build process
because of using libepoxy. Running an application that does not depend on
libgl1 (directly or indirectly) may lead to aborting the process with an
undefined reference to
SRU proposal for Xenial - backport from Zesty.
** Patch added: "xenial_gtk+3.0_3.18.9-1ubuntu3.2.debdiff"
https://bugs.launchpad.net/hundredpapercuts/+bug/1550983/+attachment/4808141/+files/xenial_gtk+3.0_3.18.9-1ubuntu3.2.debdiff
** Tags added: sts-sru
--
You received this bug
SRU proposal for Yakkety - backport from Zesty.
** Patch added: "gtk+3.0_3.20.9-1ubuntu3.debdiff"
https://bugs.launchpad.net/hundredpapercuts/+bug/1550983/+attachment/4808140/+files/gtk+3.0_3.20.9-1ubuntu3.debdiff
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
+ [Impact]
+ There are some unlinked calls to libGL.so.1 undetected in the build process
because of using libepoxy. Running an application that does not depend on
libgl1 (directly or indirectly) may lead to aborting the process with an
undefined reference to
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1550983
Title:
Fails to start with "Couldn't open libGL.so.1" (missing dependency?)
Status in One
This bug is fixed in Zesty by latest sync with Debian (gtk+3.0
(3.22.7-2)).
** Changed in: gtk+3.0 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
** Changed in: gtk+3.0 (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 gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1550983
Title:
Fails to st
** Bug watch added: Debian Bug tracker #847366
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847366
** Also affects: virt-manager via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847366
Importance: Unknown
Status: Unknown
** Also affects: gtk+3.0 (Ubuntu)
Importance:
Hey David,
Since the upstream issue (as linked in bug #1589401) seems to be stuck and
their last request was to test a clean nm-applet build without Ubuntu patches -
I have prepared such in a ppa:dgadomski/nm-applet.
It's basically a Xenial build with the patches disabled.
Could you please
Stack trace:
#0 0x7f70f7618227 in __GI_raise (sig=sig@entry=6)
at ../sysdeps/unix/sysv/linux/raise.c:55
#1 0x7f70f7619e8a in __GI_abort () at abort.c:89
#2 0x7f70f79bc48f in isc_assertion_failed (
file=file@entry=0x7f70f7a06350 "../../../../lib/isc/unix/socket.c",
Hello,
Do you have an ifupdown crash saved in /var/crash after this incident?
If so, please attach it do this bug.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
Thank you for the report sirswa.
I have analyzed your config and came to some conclusions. You may want to
consider using one of the approaches below:
* giving up on bonding and replacing it with bridging in STP mode (please
consult the man pages at
That's right Andrew, it's backported from Debian so no forwarding
needed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1545302
Title:
wpa-roam broken by fix for ifupdown
@Paul: glad it works for you. Thank you for reporting the issue and the
feedback.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1545302
Title:
wpa-roam broken by fix for
@sirswa I tried to reproduce this in my environment - unsuccessfully.
I created a similar config - please take a look at my it for reference:
http://paste.ubuntu.com/15129899/
Maybe you could spot a difference that I overlooked.
This could mean that this change may be interfering with something
@Mike, @DavidS: thank you for feedback. I'm glad it's working for you.
The official fix will be on it's way.
@Robert: please confirm that your wpa-roam settings below "iface wlan0 inet
manual" is in fact pointing to the right file as DavidS noticed. If it is
please check:
sudo wpa_cli status
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1545302
Title:
wpa-roam broken by fix for ifupdown #1337873
Status in wpa package in Ubuntu:
Confirmed
Adding SRU proposal for Wily.
** Attachment added: "wily_ifupdown_0.7.54ubuntu1.3.dsc"
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545302/+attachment/4574280/+files/wily_ifupdown_0.7.54ubuntu1.3.dsc
--
You received this bug notification because you are a member of Ubuntu
Touch
Adding SRU proposal for Trusty.
** Description changed:
+ [Impact]
+
+ * In some configurations recurrent ifup/down calls are broken due to a
+ false-positive recursion detection.
+
+ * In certain situations it leaves interfaces unconfigured (in this
+ case: WLAN interface connected to WiFi
Paul, the patch looks good.
It's better than making those scripts compatible with new style of
ifstate. Fixing ifstate-based implementation would not cover replacing
one logical iface with another, while your implementation does it.
Good luck with pushing this to Debian.
--
You received this
Hello Paul,
I have identified the cause of the problem and prepared a fix.
My tests show that it solves the issue for Trusty and Wily (while Xenial does
not require a fix since it's ifupdown has been synced with Debian to a version
containing a fix already).
Could you please revert your
Paul, I have finally managed to reproduce this on Trusty. The ifstate
looks to be a false trail.
However, please note that with 0.8.10ubuntu1 on Xenial this problem does
not occur.
I am investigating which change needs to be backported. I will keep you
updated.
--
You received this bug
Paul, I think that the real cause here is that (by looking into
debian/ifupdown/functions.sh) wpasupplicant depends on the previous single-file
ifstate.
Currently, for the sake of the locking mechanism, it has been split into an
individual ifstate.$IFACE per interface, while wpasupplicant still
Hello Paul,
The locking mechanism was implemented to avoid race conditions in ifupdown
(such as the one reported as bug #1337873). Unsetting the variable may lead to
unexpected consequences. I belive a proper solution would be to modify wpa-roam
implementation to play along with ifupdown.
Hello Max,
My guess (supported by a test I made in a test environment) is the cause of the
problem are those lines under iface bond0:
pre-ip ifup eth2
pre-up ifup eth3
Those are most probably causing a deadlock, since the new release aims to fix
the race condition causing the
Since I've added the fix to bug 1532722 and after several days of
testing I did not observe any other issues on Trusty and Wily I'm
tagging this as verified.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of
** Patch removed: "wily_ifupdown_0.7.54ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548423/+files/wily_ifupdown_0.7.54ubuntu3.debdiff
** Patch removed: "trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff"
SRU proposal for Wily (extended with fix to bug #1532722)
** Patch added: "wily_ifupdown_0.7.54ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548423/+files/wily_ifupdown_0.7.54ubuntu3.debdiff
--
You received this bug notification because you
SRU proposal for Trusty (extended with fix to bug #1532722)
** Patch added: "trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548422/+files/trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff
--
You received this bug notification
Updated SRU proposal for Trusty (fix to bug #1532722)
** Patch added: "trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548430/+files/trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff
--
You received this bug notification
New SRU proposal for Wily (with fix to bug #1532722)
** Patch added: "wily_ifupdown_0.7.54ubuntu1.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548431/+files/wily_ifupdown_0.7.54ubuntu1.2.debdiff
--
You received this bug notification because you are
I have verified both Trusty and Wily. The verification was automated
cyclic rebooting of a VM containing 3 NICs - 2 of them were used in
bonding in active-backup. Before the fix has been implemented this test
failed with some interfaces uninitialized or the bonding mode being
wrong (the default
I have backported the fix to trusty in my ppa.
Unfortunately I was not able to reproduce this issue (although my tests
are ongoing). With that being said I would really appreciate anyone that
is affected by this issue to give it a try and let me know whether the
backport fixed that for them.
The
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
ifupdown doesn't bring loopback to state up
Status in ifupdown package in Ubuntu:
Fix
I have prepared a 'broken' pam_unix version printing a multiline text info if
it detects the PAM_SERVICE name is polkit-1.
This allows to reproduce the issue and verify the fix.
I've made this broken version available for Vivid and Wily in
ppa:dgadomski/lp1510824 and performed the verification
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
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
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
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
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
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
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.
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
** 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
** 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
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
** 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
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.
** 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
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
+
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
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
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
** 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
101 - 200 of 241 matches
Mail list logo
