>From the log:
install/upgrade: package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
I can't spot what initially failed for you, but since you are now in a
bad state I'd recommend to follow usual cleanup howtos as in [1] just
adapted to the
Without a sophisticated ipv6 setup I tried the most trivial.
# ssh ip6-localhost
The authenticity of host 'ip6-localhost (::1)' can't be established.
[...]
root@zesty-test:~# ssh -4 ip6-localhost
The authenticity of host 'ip6-localhost (127.0.0.1)' can't be established.
As you can see the -4
Would be profiles/apparmor.d/usr.lib.dovecot.imap in the apparmor package.
But after all the time we might need a check if things still apply.
Also might in a different setup the same entries might be needed in
usr.lib.dovecot.pop3 or such.
And in that case maybe rather
While working on the minor merge for Dovecot I realized that this profile is in
fact part of apparmor profiles :-/
So I flagged wrong last November - adding apparmor now.
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: dovecot (Ubuntu)
--
As discussed on IRC with JJohansen and Tyhicks, this likely is already
part of the work that Tyhicks is doing. So assigning to him for personal
triage.
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Tyler Hicks (tyhicks)
--
You received this bug notification because you are a
For the internet search graveyard I beg a pardon, yes it is a comma not a colon
- the guy that named ";" a semi-colon will forever be hated by me as it is in
some sense also a semi-comma.
Anyway not worth or able to fix the changelogs back in time, but then also not
so important.
--
You
Thanks John for spotting the issue!
I was asked why I usually try to test too much, that is the reason :-/
Rushing it once and failing instantly.
But hey our regular jenkins based testing found it - at least.
Still that means probably overall 1-2 days of broken guests :-/.
Now that this is known
cts: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
--
You received this bug notification because you are a member of U
Public bug reported:
Hi,
we have artful images since a few days - yay!
Unfortunately they run into issues.
I first thought this would be related to our slightly uncommon KVM-in-LXD setup
but I can reproduce in nested KVM as well.
For simplicity I'll not mention the -in-lXD logs here as they are
Public bug reported:
Hi,
in our testing I found an issue that might now surface due to stacked profiles
working.
Our setup is a Xenial (or newer) Host with LXD Containers for all supported
releases.
In that Xenial+ are good but recently the Trusty containers ran into an issue.
After installing
Hi Thomas,
thanks for your ongoing work.
Look at [1] - in this case you'd add verification-done-xenial now.
Once all needed tags are added (+Trusty, +Yakkety) you'd also remove the
verification-needed.
[1]:
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification#Updating_the_bug_report
--
You
I dup'ed another bug onto this, as I think they are essentially the
same.
While Martin worked on the domain-restricted cases the reporter and
others outlined that this is not what this bug is about.
TL;DR:
- anything (like vpn) provides new DNS servers on an extra link
- lets call them
Stephan, it is response time dependent - if your campus has a slow DNS
answer then the others e.g. on your normal uplink will be preferred.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hi Ali,
as I outlined before the fix likely has to take place in accountsservice not in
libvirt.
You assigned yourself, so I wanted to ask what you have in mind to do?
In case this was an accident you might want to unassign yourself, but
"subscribe" [1] you to the bug to stay up to date on this
Usually hooks are called to let everybody suspend, maybe in the Mate
environment there are others active that slow things down?
Maybe debugging along [1] can help to spot the issue in more detail.
In general you'd want to try to track down what activity is running
while this unexpected delay is
With the current information there isn't enough to debug/help more -
setting incomplete for now.
** 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
Thanks YS1 for your check.
There is no clear error in the messages, so it is down trying to log what
activity goes on while it is waking up.
Chances are that the things we set up are too sluggish as well and only start
to report after we unfrozen far enough, yet it is worth a try.
You could run
I found [1] which might help going deeper into this case if needed.
But also [2] which might be a solution for your issue right away.
[1]:
https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues
[2]:
Thank you Sam to make this available!
I agree that you hopefully release before 17.10.
Since the auto sync won't catch it there I checked if things would work out as
intended and they seem good with:
$ syncpackage --distribution=experimental --simulate --verbose krb5
What is needed is:
1.
Thanks Stephane and Christian!
Since we ...
a) have a workaround by manually adding the entry to the apparmor abstraction
(or dropping serial if that is an option)
b) having an explicit serial in the guest profile is not the default
c) KVM in LXD is more a "nice to have" solution than something
Thank John,
as extra info on the ptmx pathing.
Host:
$ ls -laF /dev/ptmx /dev/pts/ptmx
crw-rw-rw- 1 root root 5, 2 Apr 21 2017 /dev/ptmx
c- 1 root root 5, 2 Apr 12 17:36 /dev/pts/ptmx
Container:
$ lxc exec testkvm-xenial-from -- ls -laF /dev/ptmx /dev/pts/ptmx
lrwxrwxrwx 1 root root
Now the abstraction used in this case via:
#include
Held the following statement like for ages just for this use:
/dev/ptmx rw,
Please note the difference since the Deny is on:
/dev/pts/ptmx
That is especially notworthy since the former is just a link to the latter:
$ ll /dev/ptmx
lrwxrwxrwx
** Attachment added: "libvirt-92d3d720-da19-41c4-bd87-563c4ee002ce.files"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684481/+attachment/4865929/+files/libvirt-92d3d720-da19-41c4-bd87-563c4ee002ce.files
--
You received this bug notification because you are a member of Ubuntu
Touch
** Attachment added: "libvirt-qemu-abstraction"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684481/+attachment/4865930/+files/libvirt-qemu-abstraction
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
** Attachment added: "libvirt-92d3d720-da19-41c4-bd87-563c4ee002ce.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684481/+attachment/4865928/+files/libvirt-92d3d720-da19-41c4-bd87-563c4ee002ce.txt
--
You received this bug notification because you are a member of Ubuntu
Touch
Thanks Stephane for outlining the likely related timeline of changes.
Thanks John for picking that up, let me search the profiles for you.
Only when writing that up I realized that there is a path difference
that might as well be the root cause after all - writing it up after the
attachments.
--
apport information
** Attachment added: "OpalElog.tar.gz"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865594/+files/OpalElog.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865596/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865593/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ProcLocks.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865598/+files/ProcLocks.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ProcMisc.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865599/+files/ProcMisc.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865597/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865595/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ApparmorStatusOutput.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865580/+files/ApparmorStatusOutput.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
apport information
** Attachment added: "ApparmorPackages.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865579/+files/ApparmorPackages.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ProcPpc64.tar.gz"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865601/+files/ProcPpc64.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865600/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865603/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "nvram.gz"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865604/+files/nvram.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865602/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Since apport-collect detected this as apparmor for the report I was also
forcing a "linux" apport collect via "sudo apport-collect
--package=linux 1684481" on the host - since the guest is LXD the kernel
there (if any) doesn't matter).
Now logs should be complete.
** Changed in: linux (Ubuntu)
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865592/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "DeviceTree.tar.gz"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865591/+files/DeviceTree.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865589/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865590/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: ".sys.firmware.opal.msglog.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865588/+files/.sys.firmware.opal.msglog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
apport information
** Attachment added: "PstreeP.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865587/+files/PstreeP.txt
** Description changed:
Setup:
- Xenial host
- lxd guests with Trusty, Xenial, ...
- add a LXD profile to allow kvm [3] (inspired by stgraber)
-
apport information
** Attachment added: "ProcLocks.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865584/+files/ProcLocks.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ProcPpc64.tar.gz"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865586/+files/ProcPpc64.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ProcMisc.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865585/+files/ProcMisc.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865582/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "KernLog.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865583/+files/KernLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865581/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: ".sys.firmware.opal.msglog.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865578/+files/.sys.firmware.opal.msglog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Running apport-collect on Host (Xenial) and LXD Container (Xenial as well).
BTW I saw LXD is not in the report, it is at:
*** 2.12-0ubuntu3~ubuntu16.04.1~ppa1 500
500 http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu xenial/main
ppc64el Packages
100 /var/lib/dpkg/status
The latter
apport information
** Attachment added: "ProcPpc64.tar.gz"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865576/+files/ProcPpc64.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "KernLog.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865572/+files/KernLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ProcMisc.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865575/+files/ProcMisc.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ApparmorStatusOutput.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865569/+files/ApparmorStatusOutput.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
apport information
** Attachment added: "ProcLocks.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865574/+files/ProcLocks.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "PstreeP.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865577/+files/PstreeP.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865571/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865573/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Tags added: apport-collected uec-images xenial
** Description changed:
Setup:
- Xenial host
- lxd guests with Trusty, Xenial, ...
- add a LXD profile to allow kvm [3] (inspired by stgraber)
- spawn KVM guests in the LXD guests using the different distro release
apport information
** Attachment added: "ApparmorPackages.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865568/+files/ApparmorPackages.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1684481/+attachment/4865570/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1684481
Title:
KVM guest execution start
Public bug reported:
Setup:
- Xenial host
- lxd guests with Trusty, Xenial, ...
- add a LXD profile to allow kvm [3] (inspired by stgraber)
- spawn KVM guests in the LXD guests using the different distro release versions
- guests are based on the uvtool default template which has a serial console
Also updating the bug status to match current work.
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
** Changed in: apparmor (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@JJohansen - for testing I'd need that for ppc64el if possible.
My x86 machines go often down due to FW bugs if testing these cases.
Any chance to build a test kernel for that arch?
Since you have a test kernel it seems you have found the issue.
What is the way of delivery for this - normal
Also after enabling proposed you can install "just the package and its
dependencies" by instead of running "apt upgrade" just running in this
case "apt install openssh-client".
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because
Prior to the update I had a diff when rehashing like:
$ ssh-keyscan 10.245.71.133 > ~/.ssh/known_hosts; for i in $(seq 1 20); do
ssh-keygen -H; diff -Naur ~/.ssh/known_hosts.old ~/.ssh/known_hosts; done
Removing the known_hosts file and upgrading to proposed version.
After the update I see one
Prior to updating when scanning from a target I still have ports in the
output:
ssh-keyscan -H -p 10.0.4.153
# 10.0.4.153: SSH-2.0-OpenSSH_7.4p1 Ubuntu-10
[|1|nTWrNxylhhwkyicxuuS/5p2Tlts=|ziw5AkY9sg/oRSpkYIuxswDgIf8=]: ssh-ed25519
@Gautier - thanks for trying to verify - I'm currently doing the same.
The known_hosts file you have still has the broken content.
The fix cannot change your existing known_hosts file to be good.
You'd have to remove the broken lines and add them again with ssh-keyscan.
But the fix in keyscan is
Also even when setting the profile to aa-complain I see:
[14406.210381] audit: type=1400 audit(1491482071.335:67): apparmor="ALLOWED"
operation="setrlimit" profile="/usr/sbin/libvirtd" pid=7674 comm="libvirtd"
rlimit=memlock value=2164260864
So far so good, but still the value is not raised.
As
Ok, by the recent insight this bug IS blocking the final resolution of bug
1678322.
I'll work on the other bits of that bug and we will see how this one here turns
out.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Very interesting disabling the profile completely via
$ sudo aa-disable /usr/sbin/libvirtd
makes it working, so apparmor is involved in some way.
I'm still puzzled that the ALLOWED makes it a no-op still.
Anyway waiting for your reply - thanks a lot already jjohansen for the
IRC discussions!
For documentation purpose here an update.
I found that the last thing libvirt calls is "prlimit"
In glibc that is implemented as syscall prlimit64.
That in turn is on 64 bit:
#define __NR_prlimit64 302
According to the doc of prlimit it needs a capability:
To set or get the resources of a
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
+ * using ssh-keyscan while using the port (-p) option of it will create
+bad entries. They will contain the port and thereby be invalid for
+latter use under the purpose of known_hosts.
Leveraging from the original bug this came from when debugging:
As a workaround for the case reported a user might set memtune options for the
guest like this:
16961536
16961536
Needed numbers may vary depending on the case.
Ugly but a workaround at least.
This is still really
We didn't want to diverge until Debian decided to either ship it or fully
remove it.
Now Debian release at least to experimental (but only there so far).
Given the low prio/impact this had overall so far, we will likely pick
it up in the merge for the aa-release and then consider SRUing it back.
** Changed in: logrotate (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: logrotate (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: logrotate (Ubuntu Yakkety)
Importance: Undecided => High
--
You received this bug notification because you are a member of
X/Y/Z uploads are published.
Due to the Freeze on the Zesty they are on unapproved queue there as well now.
Once it migrated into Zesty-Release the SRU Team will start to consider
it for the older releases.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thank you Thomas, the new mail content you referred to is already the fix in
place and working.
Thank you so much for double checking with me on these PPAs.
So we have all in place:
- SRU Template
- Patches reviewed and prepared
- Confidence in the fix by pre-testing ppas
With that they are
** Tags added: server-next
--
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/1670745
Title:
ssh-keyscan : bad host signature when using port option
Status in portable
Hi Seth,
so far confirmed on ppc64el and x86.
I haven't tried more, but usually after two it affects all of them.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1679704
Error in iLO links to
http://h17007.www1.hpe.com/docs/enterprise/servers/gen9/tsg/244937.htm
But since multiple systems trigger it I'd not say "hardware is physically
damaged".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Attachment added: "re-parsed file: apparmor_parser -QT -o file1
/etc/apparmor.d/usr.sbin.libvirtd"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1679704/+attachment/4854331/+files/file1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
The profiles and all the rest of the system is default zesty without
modifications.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1679704
Title:
libvirt profile is
** Attachment added:
"/sys/kernel/security/apparmor/policy/profiles/usr.sbin.libvirtd.13/raw_data"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1679704/+attachment/4854332/+files/usr.sbin.libvirtd.13-raw-data
--
You received this bug notification because you are a member of
Public bug reported:
Hi,
while debugging bug 1678322 I was running along apparmor issues.
Thanks to jjohansen we debugged some of it and eventually I was asked to report
to a bug.
Symptom:
[ 8976.950635] audit: type=1400 audit(1491310016.224:48): apparmor="DENIED"
operation="setrlimit"
I duped a few more bugs onto this one - the reason usually really is only
updating one of the two architectures wich then have colliding content
.
I wonder thou why this sort of issue should pile up especially on libnss3?
Is there any dependency or install guide out there which makes this
*** This bug is a duplicate of bug 1374561 ***
https://bugs.launchpad.net/bugs/1374561
** This bug has been marked a duplicate of bug 1374561
package libnss3 2:3.16.3-1ubuntu1 failed to install/upgrade: trying to
overwrite shared '/usr/share/doc/libnss3/changelog.Debian.gz', which is
*** This bug is a duplicate of bug 1374561 ***
https://bugs.launchpad.net/bugs/1374561
** This bug has been marked a duplicate of bug 1374561
package libnss3 2:3.16.3-1ubuntu1 failed to install/upgrade: trying to
overwrite shared '/usr/share/doc/libnss3/changelog.Debian.gz', which is
*** This bug is a duplicate of bug 1374561 ***
https://bugs.launchpad.net/bugs/1374561
** This bug has been marked a duplicate of bug 1374561
package libnss3 2:3.16.3-1ubuntu1 failed to install/upgrade: trying to
overwrite shared '/usr/share/doc/libnss3/changelog.Debian.gz', which is
FYI as nacc asked, I added samba task to reflect that it showed up there
as well (I dupped another case onto this).
** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.net/bugs/1636205
Title:
NumberFormatter has incorrect currency symbols for certain locales
Status in icu
** Changed in: openssh (Ubuntu Xenial)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
** Changed in: openssh (Ubuntu Yakkety)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
The tests in proposed were mostly good except those of docker.io.
But those issues are unrelated (local to docker.io).
The issues seem to got fixed, please retrigger the tests to pick up testing
against the newer docker.io and pass.
--
You received this bug notification because you are a member
Thanks for clarifying Dimitri!
That said, new cleaned upload diff at
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-2646/2017-03-27_13:18:01/zesty_lvm2_content.diff
The ppa is rebuilding, but since other than changelog it is the same as
the
401 - 500 of 861 matches
Mail list logo
