Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
*** This bug is a duplicate of bug 1448800 ***
https://bugs.launchpad.net/bugs/1448800
** This bug has been marked a duplicate of bug 1448800
Please update iproute2 to the latest version
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Changed in: iproute2 (Ubuntu)
Importance: Wishlist = Medium
** Changed in: iproute2 (Ubuntu)
Milestone: None = ubuntu-15.08
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
Thanks Niklas, marking Invalid as advised.
** Changed in: ntp (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1372051
Title:
ntp
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Thank you for taking the time to submit this report and helping to make
Ubuntu better.
On Debian and Ubuntu the .so symlinks for build purposes are supplied by
the -dev package. In this case you want libnl-route-3-dev which ships
/usr/lib/x86_64-linux-gnu/libnl-route-3.so on amd64, for example.
This looks like a duplicate of bug 1270189.
--
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/1456112
Title:
Phone doesn't use WiFi DNS when also connected to cell
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This sounds like a kernel or X.org problem - certainly
not openssh - so reassigning.
** Package changed: openssh (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Yes that works - thanks. I wonder if there's anything that can be done
to make it more discoverable? That said, I think I discovered the volume
down thing on Android by accident, so this is no worse.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: ntp (Ubuntu)
Importance: Undecided = Medium
** Changed in: ntp (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1472056
14:02 rbasak pitti: could you please take a look at bug 1455097?
Alleged potential issues since systemd no longer uses /etc/pm/sleep.d/
but packages put stuff in there. Do we have the functionality we need
provided for the systemd mechanisms also?
14:10 pitti rbasak: yes, I checked precise's
So I think this should probably be Invalid or Won't Fix for pm-utils if
the new mechanism should be /lib/systemd/system-sleep/, but we should
have bug tasks for each package that used /etc/pm/sleep.d/ and still
expects it to run, so I won't make that change yet.
--
You received this bug
From log:
Setting up quagga (0.99.22.4-3ubuntu1) ...
debconf: DbDriver config: /var/cache/debconf/config.dat is locked by another
process: Resource temporarily unavailable
dpkg: error processing package quagga (--configure):
subprocess installed post-installation script returned error exit
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
You may find it helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. Please can you
provide steps to reproduce the problem, and then change the bug status
back to
> Doing so would require the CPC team to update /etc/default/lxc-net,
setting USE_LXC_BRIDGE to false.
Note that this would cause a conffile prompt for all users using cloud
images who dist-upgrade to pick up the latest updates after another lxc
SRU, which breaks people doing automatic
I think this might be related to the phone powering on the screen after
a notification. That is: I believe the occurrence is higher after the
phone has woken the screen (and perhaps then timed out), compared to
when there was no notification since I last used it. This is because it
seems to affect
** Changed in: init-system-helpers (Ubuntu)
Status: Triaged => In Progress
** Changed in: init-system-helpers (Ubuntu)
Assignee: (unassigned) => Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
Confirmed. I had the same issue test upgrading from Trusty to Xenial.
activate_insserv() in sysv-rc.postinst calls "insserv -v". However
insserv 1.14.0-5ubuntu3 as in Xenial does not ship a suitable executable
in a standard bin path. In the last merge, insserv 1.14.0-5ubuntu1's
changelog says
Confirmed when test dist-upgrading from Trusty to Xenial. This blocks me
from upgrade testing other packages in Xenial before upload.
** Changed in: init-system-helpers (Ubuntu)
Status: New => Triaged
** Changed in: init-system-helpers (Ubuntu)
Importance: Undecided => High
--
You
I also think this is low priority in Ubuntu as it isn't worth adding a
delta over. It can be sent and addressed upstream, and we'll carry the
fix in Ubuntu when it arrives.
** Package changed: procps (Ubuntu) => bash (Ubuntu)
** Changed in: bash (Ubuntu)
Importance: High => Low
** Changed
Christian has explained to me that the fix would be in the bash builtin,
not in procps.
--
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/1488939
Title:
kill -L behaviour (is
(I understand that if procps' documentation did not match behaviour that
would certainly be more important, but it turns out that it's really
just a mismatch between bash's builtin and procps' documentation and
behaviour, which is certainly a papercut level UX issue but not so
obviously a bug)
--
Anyone can do it. I was just trying to be helpful in identifying what
needed doing. But I have now filed this in Debian for you.
> FYI, Redhat fixed a similar report on Fedora 23 within a few hours,
after their official final freeze.
Have Red Hat released a version of RHEL with tipc support?
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Public bug reported:
On Aquaris 4.5 r26.
Steps to reproduce:
1. Enable silent mode from top edge sound indicator.
2. Take a photo.
Expected results: no sound, or at least not a loud tuneful one.
Actual results: a loud tuneful sound.
** Affects: camera-app (Ubuntu)
Importance: Undecided
Public bug reported:
On Aquaris 4.5 r26.
Steps to reproduce:
1. Pinch zoom to maximum zoom.
2. Take a photo.
3. Press power button to turn screen off.
4. Press power button to turn screen back on.
5. Slide to unlock.
6. Enter pin.
Expected results: camera still on maximum zoom.
Actual results:
According to the Debian bug, this was fixed upstream in 4.2.8p1 and
Debian sid is now on 1:4.2.8p4+dfsg-3 so I think that means this is
fixed in Debian. Ubuntu will pick it up on the next merge which I am
expecting to be done this cycle.
--
You received this bug notification because you are a
** Changed in: openldap (Ubuntu)
Status: Confirmed => Triaged
** Changed in: openldap (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=103401
Importance: Unknown
Status: Unknown
** Summary changed:
- cups: 127.0.0.1:631 - Address already in use.
+ rpcbind grabs ports used by other daemons such as cupsd
--
You received this bug notification
Oh, I'm sorry. In my reproducer the error visible on the screen was
"ValueError: /usr/bin/python3.4 (deleted) does not exist" but apport
reported DpkgTerminalLog with "invoke-rc.d: unknown initscript,
/etc/init.d/lxc not found." so I think they are just one bug.
--
You received this bug
I also get "ValueError: /usr/bin/python3.4 (deleted) does not exist" by
starting with a Vivid cloud image, installing lxc and juju-local from
the archive, and then do-release-upgrade -d to Wily. So this will happen
to every Juju charm developer on upgrade, I think. No PPA required.
Separate from
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I see that libmnl-dev is in universe in Ubuntu so it should be
relatively easy to add the build dependency, but we are in final freeze
right now so this may have to wait until the next release.
This bug also
It seems that I can't create a generic Ubuntu task since other Ubuntu
tasks already exist, so I'll leave this with the docker.io package for
now so we don't lose it.
I think we need a Launchpad project for cloud images if we don't already
have one.
** Also affects: docker.io (Ubuntu)
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Confirmed - I have followed your reproduction steps and hit the same
issue.
The underlying reason however is not in the python3.4 nor mod-wsgi
packages. The issue is that the Docker "ubuntu:trusty" image seems to
** Summary changed:
- Ubuntu Docker images incorrectly include packages from trusty-proposed
+ Ubuntu Docker images include packages deleted from trusty-updates
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3.4 in
** Changed in: openvpn (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
** Changed in: openssh (Ubuntu)
Importance: Undecided => Wishlist
** Tags added: needs-upstream-report
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1501966
Title:
Thank you for reporting this bug and helping to make Ubuntu better.
Can you explain why this is actually a problem please? Won't timesyncd
suffice on a desktop that uses NetworkManager now? Is the time on your
system actually falling out of sync, or is the problem just the noise of
the error
Once you're replied, please change the bug status back to New.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1447142
Title:
systemd: ntpdate is started too soon (before the
** Description changed:
+ [Workaround]
+
+ ssh -O exit hostname # this will kill all ssh connection to that host
+ ssh-copy-id username@hostname # now it works because it's the first connection
+ # continue using ssh as normal.
+
+ Thanks to Ruben Laguna (ecerulm) in comment 7.
+
+ [Original
Laurent,
Thank you for your reply.
> I guess that Ubuntu systems with ntp installed would boot a little
faster if ntp was not doing useless work by getting started before the
network is fully up.
That's reasonable, though then this bug should be of low importance I
think, as the impact to users
On Tue, Oct 13, 2015 at 01:30:57PM -, Sam Bull wrote:
> I would like to be able to send a notification to the user after a set
> amount of time. Additionally, I would like the user to be able to
> respond to the notification with a couple of buttons (e.g. Yes/No or
> similar).
+1. I had
*** This bug is a duplicate of bug 1042275 ***
https://bugs.launchpad.net/bugs/1042275
** Tags removed: needs-upstream-report
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This sounds like a valid bug for a relatively uncommon use case. Does
this bug affect Debian also? In that case, it would be appropriate to
seek a fix there.
** Summary changed:
- Don't put 127.0.0.1 in
Marking Incomplete pending an answer to Simon's question. Once answered,
please change the bug status back to New.
It does sound like a fix would need to go upstream though, rather than
this being fixed in Ubuntu only.
** Changed in: dnsmasq (Ubuntu)
Status: New => Incomplete
--
You
*** This bug is a duplicate of bug 1042275 ***
https://bugs.launchpad.net/bugs/1042275
Thanks Alkis. I didn't realise that Simon is the Debian maintainer. I
just wanted to try and make sure this bug doesn't languish because it
hasn't gone to the right place.
I'm quite happy for this bug to
** Tags added: apparmor
** Changed in: openldap (Ubuntu)
Importance: Undecided = High
--
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/1472639
Title:
apparmor profile
Thank you for your report. This package failure looks like being caused
by system corruption. Try sudo apt-get clean and then try again, in
order to re-download the corrupt file.
Since this looks like local disk corruption or a hardware problem,
rather than a bug in Ubuntu, I'm marking this bug
From log
dpkg: error processing archive
/var/cache/apt/archives/python-six_1.9.0-3_all.deb (--unpack):
cannot access archive: No such file or directory
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to six in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Importance - Low for now, since the only reported user impact is
additional log entries.
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I appreciate the existence of crouton, but from an Ubuntu perspective we
have no steps to reproduce on Ubuntu without crouton so I'm marking this
bug as Incomplete for Ubuntu. Please explain what action needs to
> Does this mean there will be no fix? I and others did NOT change our
configuration. It's that this new update is failing.
It seems more likely to me that some subset of users had some kind of
local configuration problem that would have failed on _any_ update of
openssh (ie. any run of the
** Changed in: openssh (Ubuntu)
Importance: Undecided => Low
** Changed in: openssh (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This sounds reasonable. ssh-copy-id should not be making any assumptions
about the user's default shell on the remote machine. It might be better
for it to call sh explicitly, since sh (compatibility) is more
@Martin
Note that this is bug a regression - previously, before the (I presume)
dh_installinit change, /etc/init.d/foo was a symlink to /lib/init
/upstart-job so a user running /etc/init.d/foo by hand was redirected to
upstart anyway. So while I appreciate that a user might now be getting
desired
I have a UX request when setting the timer. In addition to setting the
time remaining until it expires (as you'd expect), I'd like to also
switch to the ability to setting the clock time that I want it to
expire. This would be very similar to setting an alarm of course, but
the alarm setting UI is
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete. I've
tested slapd from trusty-updates and it does appear to install
I don't really understand the bug task on bind9 packaging here. If you
install the bind9 package, then surely you expect it to listen on IPv6
ports by default? If you don't want this, then presumably you need to
reconfigure bind9?
Setting the bind9 package task Incomplete because as far as I can
** Changed in: iproute2 (Ubuntu)
Status: New => Triaged
** Changed in: iproute2 (Ubuntu)
Importance: Undecided => High
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
That example was on 15.10. It would be useful for hook error handling to
report the apport package version.
--
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/1522849
Title:
Thank you for your report Doug. Let's set this Incomplete pending your
check of 4.4.
** Changed in: pm-utils (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
Public bug reported:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 66, in add_info
check_attachment_for_errors(report, attachment)
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please attach an example sshd_config that fails as you describe, and
then change the bug status back to New. Thanks!
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
You received this bug
(ideally this would be the minimal change from the default
configuration, to make it easiest to identify the cause of the problem)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Which Ubuntu releases and libnl3 package versions are affected, please?
Which upstream release first included these patches? And please could
you provide your failure use cases so that we can decide on importance
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I cannot reproduce this. My log is below. Could this be a
misconfiguration on your system? For example, your lines "debug1:
key_load_private_cert: No such file or directory" suggest to me that you
are running a
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Importance -> Low since "ubuntu 15.04 with upstart and without apparmor"
is an unusual and generally unsupported configuration, except on the
phone (but on the phone AppArmor is enabled).
But thanks for the patch
I also tried with 5ubuntu1.3 and still cannot reproduce. A key
difference might be your:
debug1: kex: server->client aes128-ctr hmac-sha1 none
vs. my:
debug1: kex: server->client aes128-ctr umac-64-...@openssh.com none
$ ssh -v ubuntu@localhost
OpenSSH_6.7p1 Ubuntu-5ubuntu1.3, OpenSSL 1.0.1f 6
> ApportVersion is always included in apport reports from the linked bug
Ah sorry, I missed that. Thank you for the DpkgTerminalLog fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
Thank you for the update.
On looking again I noticed this from the documentation you quoted in
your original report:
"If port is not specified, sshd will listen on the address and all prior
Port options specified."
I'm sorry I didn't notice this the first time round. Given the word
"prior" in
Ryan, please could you take a look at this? I've taken a brief look at
the patches and I follow what they're achieving and why, but I'm not
confident that I follow all possible edge cases introduced by these
patches.
If you're satisfied then please could you prepare an SRU? Thanks!
** Changed
** Also affects: libnl3 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808213
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnl3 in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
*** This bug is a duplicate of bug 1509816 ***
https://bugs.launchpad.net/bugs/1509816
** This bug has been marked a duplicate of bug 1509816
Upgrade from 14.04 to 15.04 missed systemd-sysv and init package init
1.22ubuntu11 failed to install/upgrade: pre-dependency problem - not
** Changed in: libseccomp (Ubuntu)
Status: New => Triaged
--
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/1526358
Title:
adding seccomp rule for socket() fails on
For now I'm marking this Fix Released as it is fixed in Wily, and
opening a task for Trusty (which depending on what we decide may end up
being Won't Fix).
** Changed in: libnl3 (Ubuntu)
Status: New => Fix Released
** Also affects: libnl3 (Ubuntu Trusty)
Importance: Undecided
Thank you for your response. It looks like this is fixed in Wily then,
which is on 3.2.26, so this bug affects 14.04 only?
I'm concerned that this changes library behaviour. How can we be sure
that no existing users of libnl will not be regressed by this change in
behaviour if we backport this to
Public bug reported:
This affects 1.1.5-0ubuntu0.15.10.3 on Wily. I believe it also affects
1.1.5-0ubuntu0.15.04.3 on Vivid.
Downgrading to 1.1.4-0ubuntu1 fixes it, so it does not affect
1.1.4-0ubuntu1 on Wily.
My failure case is that I am running adt-run --apt-pocket=proposed -U
with
Correction. Rather than systemd being upgraded, I think there's
something that fires a trigger in it that sets off the failure.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
I hit what I think might be this issue on Vivid, just doing an upgrade
to the latest lxc in vivid-updates because I was hitting a separate bug
(I'll file next) and thought updating to the latest vivid-updates might
fix it. In my case, "service lxc-net stop" succeeded, but "service lxc-
net start"
"dpkg -s openssh-client" lists "Homepage: http://www.openssh.org/;.
That's usually the best way. From there I see they have instructions at
http://www.openssh.com/report.html. I hope this helps!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
PS. it's also valid to say that the documentation should at least be
clarified, but I think my answer is the same in this case: it should go
upstream and we won't carry a patch, since the benefit doesn't justify
the additional maintenance burden in doing so.
--
You received this bug notification
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I understand that shells generally expand ~ to $HOME, but I'm not sure
that automatically means the documentation is wrong, though I can see
how it could have misled you in this case. I'm also not sure that there
19:48 rbasak: oh - no, I see, the maintainer script gives a
generic error and the real error is in the log. ok. Yes, the postinst
already does "Make sure insserv is in the path", so it just needs
/usr/lib/insserv to be part of that path, I think
--
You received this bug notification because
** Changed in: init-system-helpers (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1511899
Title:
init-system-helpers
** Changed in: sysvinit (Ubuntu)
Status: Triaged => In Progress
** Changed in: sysvinit (Ubuntu)
Assignee: (unassigned) => Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in
** Changed in: sysvinit (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1507151
Title:
sysv-rc.postinst calls insserv
Sorry Charles, but a patch that is known to work just in one case isn't
really sufficient for an SRU. It is useful and I appreciate your
contribution, but alongside it we need to analyse and understand the
regression risk for other valid use cases. This is the "Regression
Potential" section of the
Thanks Gareth!
** Also affects: nss via
https://bugzilla.mozilla.org/show_bug.cgi?id=1277637
Importance: Unknown
Status: Unknown
** Tags removed: needs-upstream-report
** Changed in: nss (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you
rbasak: looks straightforward enough to me; I've never used the vlan
package though, but this looks plausible
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
** Changed in: vlan (Ubuntu)
Importance: Undecided => High
--
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/1519120
Title:
Xenial: VLAN interfaces don't work
** Summary changed:
- authorized_keys using from="hostname" no longer work when upgrading to Xenial
+ UseDNS default changed to no, locking out authorized_keys from="hostname"
users when upgrading to Xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This is certainly worthy of a release note, and I have edited the Xenial
release notes to highlight this issue.
Further discussion: http://irclogs.ubuntu.com/2016/06/06/%23ubuntu-
devel.html#t10:26
Based on this
** Changed in: openldap (Ubuntu)
Assignee: (unassigned) => Ryan Harper (raharper)
--
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/1472639
Title:
apparmor profile
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please could you confirm if downgrading to 2.4.42+dfsg-
2ubuntu3 fixes your problem?
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: vlan (Ubuntu)
Assignee: (unassigned) => Wesley Wiedenmeier (wesley-wiedenmeier)
--
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/1519120
Title:
Thanks Gareth. Is anyone volunteering to report this upstream? If
reporting, please link to the report here.
--
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/1586538
Title:
Thanks Gareth. So upstream have an inconsistency in their docs so
presumably need an upstream bug to fix that? And Ubuntu is currently
consistent between its documentation and behaviour? Is my understanding
accurate?
** Tags added: needs-upstream-report
--
You received this bug notification
Public bug reported:
See bug 1587695 for example. Expected: amavis' failure reason in the
original bug report. Actual: we are only told that it failed, not why,
which systemd knows anyway and which the service correctly reported.
This is a regression from before systemd-boot, since before
101 - 200 of 1200 matches
Mail list logo
