Thanks peter and chris, sounds like the issue is resolved so I'll close
the bug as suggested.
** Changed in: cairo (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
Ayup.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/973932
Title:
Disabling 'below' display does not reposition windows properly
Status in Unity:
Incomplete
Status in
Possibly dupe with #1173915?
I too am seeing 100% cpu on initctl, after a nearly three month uptime
on 14.04:
Linux dorset.bryceharrington.org 3.13.0-35-generic #62-Ubuntu SMP Fri
Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
# cat /proc/1327/stack
[]
** Changed in: systemd (Ubuntu Trusty)
Status: Triaged => In Progress
--
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/1371403
Title:
[PATCH] Please disable USB
While the rules seem to work fine, apparently the syntax checker in the
packaging scripts don't like the use of := for assignment, so I've
change that to just =. I think that should also work fine, but will
test once the package actually is built.
** Tags removed: verification-needed
**
Hrm, well with the := changed to =, the rule doesn't seem to be working.
(I guess it's the := change; I suppose there could be another error
somewhere...)
blackwold:~$ sudo ./disable_avocent_autosuspend
[sudo] password for bryce:
/sys/bus/usb/devices/3-13 on
/sys/bus/usb/devices/3-14 SC
** Changed in: systemd (Ubuntu Trusty)
Status: In Progress => Confirmed
--
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/1371403
Title:
[PATCH] Please disable USB
See #17 for where this is stuck.
--
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/1371403
Title:
[PATCH] Please disable USB autosuspend for Avocent SC Secure KVM
Status in
** Changed in: bash (Ubuntu Bionic)
Status: New => In Progress
** Changed in: bash (Ubuntu Cosmic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
** Description changed:
[Impact]
Long running bash loops that create and reap processes will crash,
hanging at 100% CPU.
+ [Test Case]
- [Test Case]
+ A PPA with the proposed fix included is at:
+
+ https://launchpad.net/~bryce/+archive/ubuntu/bash-sru-19-010-1
+
+ Install the
** Description changed:
[Impact]
TBD
[Test Case]
TBD
[Regression Potential]
+ The fix is just configuring the order of service startup, so is unlikely to
create any regressions. Things to watch would be service related misbehaviors
and general availability of the dnsmasq
** Summary changed:
- dnsmasq doesn't start on boot because its interface isn't up yet
+ [SRU] dnsmasq doesn't start on boot because its interface isn't up yet
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in
** Description changed:
+ [Impact]
+ TBD
+
+ [Test Case]
+ TBD
+
+ [Regression Potential]
+
+ [Fix]
+
+ [Discussion]
+
+ [Original Report]
+
My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is
managed manually in /etc/network/interfaces.
During boot, dnsmasq is
** Also affects: bash (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: bash (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: bash (Ubuntu Bionic)
Assignee: (unassigned) => Bryce Harrington (bryce)
** Also affects: bash (Ubuntu Cosmic)
Impo
** Description changed:
- Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops
- when spawning sub processes and waiting for them. There is a fix:
+ [Impact]
- https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020
+ Long running bash loops that create and reap processes
Hi halfgaar,
Robie asked me to help you with this bug, thanks for reporting it. I
may not be able to get full attention on this until next week due to a
project deadline, but I've had a quick look at the patch and your
problem description, and it looks pretty straightforward. Thanks also
for
** Changed in: bash (Ubuntu Cosmic)
Importance: Undecided => High
** Changed in: bash (Ubuntu Cosmic)
Assignee: (unassigned) => Bryce Harrington (bryce)
** Changed in: bash (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are
Hi Thomas, have you had a chance to re-test this on 18.04? From
Christian's comment #3, sounds like this issue may already be resolved,
but if not we can investigate further.
** Changed in: dnsmasq (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are
Hi Gareth, thanks for following up, and glad to hear you've sorted the
trouble out!
** Changed in: rsync (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
Fixes have been pushed to cosmic-proposed and bionic-proposed.
** Summary changed:
- Apply Bash 4.4.20 to fix cpu spinning on built-in wait
+ [SRU] Apply Bash 4.4.20 to fix cpu spinning on built-in wait
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Oh, one other thing that will be necessary to file an SRU for this would
be a a series of "paint by number" steps to reproduce the issue, and to
verify the fix. For example, something akin to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1810583/comments/12
** Also affects:
Given SRU and backport team policies, having a newer version of
keepalived in bionic seems pretty unlikely. SRU policy favors backports
of specific fixes rather than entire package backports, while the
backports team generally discourages backports of libraries or services
since they can randomly
** Changed in: keepalived (Ubuntu Bionic)
Status: New => Triaged
** Changed in: keepalived (Ubuntu Cosmic)
Status: New => Triaged
** Changed in: keepalived (Ubuntu)
Importance: Undecided => Medium
** Changed in: keepalived (Ubuntu Bionic)
Importance: Undecided => Medium
**
** Tags added: server-next
--
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/1819074
Title:
Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd-
networkd
Thanks for testing so thoroughly! I've gone ahead and set the
verification tags to done, to allow this to now go out. I've also added
your script to the Test Case, for future reference.
** Description changed:
[Impact]
Long running bash loops that create and reap processes will crash,
This issue was fixed in Debian with the attached patch from upstream.
SRU process prohibits version jumps so would reject directly updating
the rsync package on Ubuntu 16.04 to 3.2.2-2.
However, if you can define a test case to reliably reproduce the bug,
then it may be possible to get the
Hi Luke, thanks for reporting this issue. Unfortunately, I am not able
to reproduce it.
Ubuntu 18.04.2 ships openssh-server 1:7.6p1-4ubuntu0.3, not 7.9. Is the
version typo'd in the report or are you running a self-installed version
of openssh perhaps?
In any case, I attempted reproduction on
Hi halfgaar, just checking in on how the testing has been coming along?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1822776
Title:
[SRU] Apply Bash 4.4.20 to fix cpu
The aforementioned link shows there's been work towards a fix in
systemd. Can't say if that suggests what can be done to improve
keepalived, but I've tagged this "server-next" to get it on the Ubuntu
SErver Team's high priority list, as per Robie's earlier comment.
** Tags added: server-next
--
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1841654
Title:
Replace mawk with gawk in main
Status in mawk package in Ubuntu:
New
Bug
** Description changed:
- No se bien lo que acontecio.
+ No se bien lo que acontecio. ("I don't know well what happened")
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: rsync 3.1.1-3ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
Uname: Linux
Hi Leonardo,
It sounds like your upgrade may have been interrupted for some reason,
and rsync didn't finish getting configured. Forcibly removing and
reinstalling rsync might help. There is some advice about fixing half-
installed packages here:
I can't say for certain if the issue resides with ssh-askpass-fullscreen
or is a UI usability issue in unity, gnome, or elsewhere, however this
UI is not driven by OpenSSH itself, so I'll retarget this bugtask to
ssh-askpass-fullscreen as a slightly more likely candidate.
** Package changed:
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1838370
Title:
slapd segfault on filter parse error
Status in openldap:
Fix Released
Status
Debian sees the problem too, at least since mid-June:
http://duck.debian.net/static/sp/p/popt.html
https://tracker.debian.org/pkg/popt
The domain name is still registered, through next year:
https://whois.gandi.net/en/results?search=rpm5.org
>From debian/changelog, looks like the
** Patch added: "Patch mentioned in previous comment"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1838370/+attachment/5280211/+files/0001-ITS-8964-Do-not-free-original-filter.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Description changed:
Impact
--
- Users willing to use the slapd rwm overlay will face a slapd segmentation
fault
- when trying to rewrite some rules. Backporting this fix will allow users using
- stable releases to take advantage of this feature without crashing slapd. This
- issue
** Description changed:
[Impact]
- TBD
+ dnsmasq will fail to respond on network devices that weren't up when its
+ service started, thus not binding as expected.
[Test Case]
TBD
[Regression Potential]
The fix is just configuring the order of service startup, so is unlikely to
Hi Nicholas,
The reason for the error you got is because you had a local
configuration setting for ssh in your /etc/ssh/ssh_config:
-Host *
-UseRoaming no
The upgrader was asking whether to keep your changes or revert to the
vanilla config. Since it timed out without an answer, it
Debian has a patch for the issue:
https://salsa.debian.org/go-
team/packages/notary/commit/b4f024c049b916c4b81fbd1199c86c8b5dfe2934
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nspr in Ubuntu.
Hi csozo,
It looks like your system was under some form of memory pressure prior
to the openssh installation. So I don't think this is a fault
necessarily in openssh itself but rather due to your computer having run
out of memory and gotten into some sort of inconsistent state.
I would
** Description changed:
I don't know.
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: openssh-server 1:8.0p1-6build1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
** Bug watch added: github.com/systemd/systemd/issues #9785
https://github.com/systemd/systemd/issues/9785
** Also affects: systemd via
https://github.com/systemd/systemd/issues/9785
Importance: Unknown
Status: Unknown
** Description changed:
- dnsmasq 2.79 and below omits EDNS0
I've linked to the upstream systemd bug report, although from comment #4
it sounds like it might be a regression caused by a security fix.
As to the dnsmasq patch mentioned in the issue description, what it
appears to be doing is checking if there is a pseudoheader in the
request, and if so adds
Targeting to bionic, since disco/eoan/focal are on 2.80 which, per the
OP, should already be carrying the requested fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Tags added: server-next
--
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/1785383
Title:
missing EDNS0 record confuses systemd-resolved
Status in systemd:
Unknown
Could you clarify the error you're encountering? The error message in
the title of this bug suggests the package was already installed, so
perhaps this is a non-bug? There are no error messages or indication of
a fault being hit in any of the attached logs.
** Changed in: openssh (Ubuntu)
*** This bug is a duplicate of bug 1854023 ***
https://bugs.launchpad.net/bugs/1854023
** This bug has been marked a duplicate of bug 1854023
package openssh-client 1:7.2p2-4ubuntu2.8 failed to install/upgrade: package
openssh-client is already installed and configured
--
You received
Thanks for following up, I'm closing the issue as requested.
** Changed in: rsync (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
I'm able to reproduce the faulty on bionic (not upgraded from xenial),
with GTK_IM_MODULE=xim and an empty .xinputrc.
Can also confirm the workaround suggested by Heiko L seems to fix this
issue, by changing /usr/share/themes/Ambiance/gtk-3.20/gtk.css to this:
> textview text {
>
*** This bug is a duplicate of bug 1862364 ***
https://bugs.launchpad.net/bugs/1862364
** This bug has been marked a duplicate of bug 1862364
mysql-8.0 FTBFS (focal) because of hardcoded date in test
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Bug watch added: Debian Bug tracker #951220
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951220
** Also affects: openssh (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951220
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1861177
Title:
seccomp_rule_add is very slow
Status in snapd:
New
Status in libseccomp
The patch mentioned in the OP is attached for reference. Per [1] it was
proposed for inclusion in Debian last November as patches db-
consolidate-some-of-the-code-which-adds-rules-to-.patch and db-add-
shadow-transactions.patch.
The corresponding bug report upstream is [2].
1:
2.4.1 is currently available from xenial, bionic, disco, eoan; focal
carries 2.4.2. None of these carry the patches for this bug report yet.
** Changed in: libseccomp (Ubuntu)
Importance: Undecided => High
** Changed in: libseccomp (Ubuntu)
Status: New => Triaged
--
You received
Thank you for taking the time to file a bug report.
Unfortunately the collected logs don't indicate what the issue with ldap
is. There don't seem to be other reports of this issue, so it appears
not to be a systemic problem. Best guess, lacking better information,
is that there was a local
Marc's comment #3 seems plausible:
stirling:~/ubuntu/Openssh$ lxc exec u18 -- bash
root@u18:~# md5sum /etc/ssh/sshd_config
203e9b92fe3623aeba277ee44297f7dd /etc/ssh/sshd_config
root@u18:~# grep -c 203e9b92fe3623aeba277ee44297f7dd
/usr/share/openssh/sshd_config.md5sum
0
root@u18:~#
Looking
So, the trivial fix is to simply append 203e9b92fe3623aeba277ee44297f7dd
to openssh-server.ucf-md5sum, as Marc had suggested above.
I can proceed with that as the fix.
---
But this suggests a few direct questions/thoughts:
0. Does the installer use the openssh-server.ucf-md5sum from the new
While the error message mentions dnsmasq, the only errors I'm spotting
in the log file involve corefonts:
Err:1 http://downloads.sourceforge.net/corefonts/impact32.exe
Protocol "http" not supported or disabled in libcurl
0% [Working]
E: Failed to fetch
I'm able to easily reproduce this in lxc using the steps provided.
** Changed in: openssh (Ubuntu)
Importance: Undecided => High
** Changed in: openssh (Ubuntu)
Status: New => Triaged
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
The suggested workaround to put "Set disable_coredump false" into
/etc/sudo.conf appears to work for me for suppressing the warning in
focal lxc containers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
While there was some discussion by the kernel community around this on
the associated bug, it appears to remain unresolved there. But it looks
to me that Robie's assessment still stands that it wouldn't be
appropriate to change this in just the logwatch patch alone. Given the
age of this bug,
Per the PHP bug, this appears not to be in php itself but rather higher
up the stack. Reassigning to ICU for now.
** Also affects: icu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: php7.4 (Ubuntu)
Status: New => Invalid
--
You received this bug notification
Modern df lists the actual fs types for those 'none' devices. E.g.
udev, tmpfs, et al. I'm guessing the reason that '-x none' was not
excluding them in this old df version was because the type wasn't
literally 'none' but perhaps \0 or else was just not being displayed.
In any case, I no longer
I'm not able to reproduce this on focal, with multiple nfs mount points
mounted.
If it is still reproducible on newer versions of Ubuntu, can you provide
the full output of df, as well as log files /etc/fstab and /etc/exports
from the nfs server? The output of dmesg (from boot) from the client
20.04's coreutils still has the behavior described in this bug. /dev is
listed as type 'udev' by df but df -x udev does not exclude it; df -x
devtmpfs does.
I wonder if one way to at least resolve the confusion might be to make
the code that prints the table display devtmpfs devices as
We're no longer looking at backporting fixes for disco.
This looks suitable for SRU so the other proposed series tasks are
valid, and this is already in the server-next queue.
** Changed in: openldap (Ubuntu Disco)
Status: New => Won't Fix
--
You received this bug notification because
** Changed in: openvpn (Ubuntu)
Importance: Undecided => Medium
--
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/1689833
Title:
OpenVPN server does not start properly on
Can you explain the configuration process for saslauthd with slapd? Or
a copy of your config file would do.
** Changed in: openldap (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: sudo (Ubuntu Focal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1857036
Title:
`sudo --login --user USERNAME` throws
** Description changed:
[Impact]
Logging in as a sudo user in a Ubuntu Focal Linux container displays a
warning:
- sudo: setrlimit(RLIMIT_CORE): Operation not permitted
+ sudo: setrlimit(RLIMIT_CORE): Operation not permitted
The warning is entirely unnecessary - the container is
ackage: sudo
UpgradeStatus: No upgrade log present (probably fresh install)
VisudoCheck:
/etc/sudoers: parsed OK
/etc/sudoers.d/90-cloud-init-users: parsed OK
/etc/sudoers.d/README: parsed OK
** Changed in: sudo (Ubuntu Focal)
Assignee: (unassigned) => Bryce Harrington
Closing as expired.
** Changed in: apache2 (Ubuntu)
Status: Incomplete => Invalid
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: coreutils (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1219529
Title:
df -x tmpfs fails to exclude
** Changed in: coreutils (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1756595
Title:
disk space info inadvertently provides all
** Changed in: coreutils (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1827159
Title:
check_all_disks includes squashfs
df no longer shows squashfs mounts by default, as of today's coreutils
update
** Changed in: coreutils (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in
** Also affects: coreutils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1827159
Title:
check_all_disks includes
** Also affects: coreutils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1756595
Title:
disk space info inadvertently
** Also affects: sudo (Ubuntu Groovy)
Importance: Undecided
Status: Confirmed
** Also affects: sudo (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in
Confirmed, I still was able to reproduce this on groovy with sudo
1.8.31-1ubuntu1, but groovy is now updated to 1.9.0-1ubuntu1 and now the
behavior is correct.
>From the bug report mentioned in comment #3, I found the commit with the
corresponding patch.
I've added a focal bug task and marked
** Changed in: sudo (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1857036
Title:
`sudo --login --user USERNAME`
Status: New => In Progress
** Changed in: docker.io (Ubuntu Xenial)
Assignee: (unassigned) => Bryce Harrington (bryce)
** Changed in: docker.io (Ubuntu Xenial)
Importance: High => Critical
** Changed in: docker.io (Ubuntu Bionic)
Importance: Undecided => Critical
** Ch
Hi Huy,
The bug report appears to indicate some sort of syntax error in your
/etc/ssh/sshd_config file. What's on line 13 of that file?
SSHDConfig:
Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255:
/etc/ssh/sshd_config: line 13: Bad configuration option: Include
For the privileged/unprivileged issue mentioned in comment #6, these upstream
comments appears to be pertinent, suggesting patches that may be worth
backporting:
https://github.com/moby/moby/issues/40734#issuecomment-614259072
https://github.com/moby/moby/issues/40734#issuecomment-680250761
** Summary changed:
- apt update fails on docker arm container 20.04
+ apt update fails on unprivileged docker arm container due to inaccessible
clock
** Summary changed:
- apt update fails on unprivileged docker arm container due to inaccessible
clock
+ apt update fails on unprivileged
This sounds like another dupe of
https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1906364
Title:
I'm able to reproduce this in a hirsute lxc container I created today.
Interestingly, another hirsute container I created Friday doesn't
reproduce this issue even when updated to current.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1778073
Title:
dnsmasq and resolvconf hangs on start
Status in dnsmasq package in Ubuntu:
** Also affects: openldap (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: openldap (Ubuntu Bionic)
Status: New => Triaged
** Changed in: openldap (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of
If I understand the work so far, this issue is only present in Bionic,
since later releases already have the release (and the subsequent fix)?
Sounds like the next action here would be to SRU the changes packaged in
https://launchpad.net/~sergiodj/+archive/ubuntu/openldap-
bug1926265/+packages.
This type of error typically occurs because the cached .pyc files are
out of date for some reason. (C.f. https://www.py4u.net/discuss/17141,
https://stackoverflow.com/questions/30861493/how-to-fix-python-
valueerrorbad-marshal-data)
This specific issue is occurring not in python-cryptography
Yes, your referenced bug LP: #1891810 looks like the most likely path
forward for gaining this, given that the ubuntu-security team already
has that staged in their security-proposed PPA (https://launchpad.net
/~ubuntu-security-proposed/+archive/ubuntu/ppa).
Please test that PPA to confirm it
** Also affects: debconf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1914875
Title:
Use of uninitialized value
14.04 has transitioned off Standard Support to Extended Security
Maintenance (https://ubuntu.com/blog/ubuntu-14-04-trusty-tahr) as of
April 2019. Under ESM the focus for changes is more on security
vulnerabilities in non-desktop packages. Since this issue sounds to be
more on the cosmetic side,
** Changed in: unattended-upgrades (Ubuntu Xenial)
Status: New => Triaged
** Changed in: unattended-upgrades (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: unattended-upgrades (Ubuntu Xenial)
Assignee: (unassigned) => Lucas Albuquerque Medeiros de Moura (lamoura)
--
** Description changed:
- == Begin SRU Template ==
[Impact]
+ During an upgrade from trusty to xenial, users will be prompted to make a
decision regarding the diff on unattended-upgrades. This is not a good user
experience, specially because the user can make an uninformed decision of
Since this appears to have just required a fix to autofs, I'm closing
the openldap task. If there actually is any followup work needed for
openldap please reopen with additional detail of what needs done.
** Changed in: openldap (Ubuntu)
Status: New => Fix Released
--
You received this
*** This bug is a duplicate of bug 1914875 ***
https://bugs.launchpad.net/bugs/1914875
** This bug has been marked a duplicate of bug 1914875
Use of uninitialized value $ret in string eq at
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134.
--
You received this bug notification
*** This bug is a duplicate of bug 1914875 ***
https://bugs.launchpad.net/bugs/1914875
** This bug has been marked a duplicate of bug 1914875
Use of uninitialized value $ret in string eq at
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134.
--
You received this bug notification
1 - 100 of 165 matches
Mail list logo
