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 1
** 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 s
** 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 U
** 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 seede
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.
--
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.laun
The verification of the Stable Release Update for software-properties
has completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package software-properties - 0.96.24.7.1
---
software-properties (0.96.24.7.1) yakkety-proposed; urgency=medium
* Add knowledge of OpenStack releases Ocata, Pike and Queens. (LP:
#1670385)
[ Scott Moser & Dimitri John Ledkov ]
* When failing to retrie
The verification of the Stable Release Update for software-properties
has completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package software-properties - 0.96.24.7.1
---
software-properties (0.96.24.7.1) yakkety-proposed; urgency=medium
* Add knowledge of OpenStack releases Ocata, Pike and Queens. (LP:
#1670385)
[ Scott Moser & Dimitri John Ledkov ]
* When failing to retrie
[Expired for apparmor (Ubuntu) because there has been no activity for 60
days.]
** Changed in: apparmor (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https:/
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Hi
Thanks for the update
---
Thanks,
Noam Rathaus
On Apr 21, 2017 04:15, "Tyler Hicks" wrote:
> As a note to any backporters, the original fix for this bug should
> include the following change as well:
>
> https://code.launchpad.net/~tyhicks/lightdm/guest-dir-
> perms/+merge/322906
>
> It i
This bug was fixed in the package systemd - 231-9ubuntu4
---
systemd (231-9ubuntu4) yakkety; urgency=medium
* debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if
resolved is going to be started, make sure this blocks
network-online.target. LP: #1673860.
* de
This bug was fixed in the package systemd - 231-9ubuntu4
---
systemd (231-9ubuntu4) yakkety; urgency=medium
* debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if
resolved is going to be started, make sure this blocks
network-online.target. LP: #1673860.
* de
This bug was fixed in the package systemd - 231-9ubuntu4
---
systemd (231-9ubuntu4) yakkety; urgency=medium
* debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if
resolved is going to be started, make sure this blocks
network-online.target. LP: #1673860.
* de
Confirmed this fix in yakkety. Behavior with systemd 231-9ubuntu3:
# journalctl -o short-precise -u systemd-resolved -u network-online.target
--no-pager
-- Logs begin at Thu 2017-04-20 23:50:20 UTC, end at Fri 2017-04-21 03:22:45 UTC
Apr 20 23:51:06.897218 ubuntu systemd[1]: Starting Network Nam
I have exactly the same. can't access my University's vpn on my new
laptop running 10.04. vpn works without any issue on another laptop
running 14.04.
I am wondering if I can rollback vpnc and the necessary packages back to
14.04? need to use vpn to connect to work computers.
using the above work
I installed Ubuntu 17.04 as a VirtualBox guest and I have the same problem:
syslog output:
systemd-resolved[947]: DNSSEC validation failed for question . in DNSKEY:
missing-key
systemd-resolved[947]: DNSSEC validation failed for question com in DS:
missing-key
systemd-resolved[947]: DNSSEC valida
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: url-dispatcher (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to url-dispatcher in Ubuntu.
https://bu
** Changed in: gnome-online-accounts
Status: Unknown => Confirmed
** Changed in: gnome-online-accounts
Importance: Unknown => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
I'm having the same problem since when I fresh installed Ubuntu (Budgie) 17.04.
I then reinstalled Ubuntu (Unity) 16.04 LTS and having the same problem, LIVE
versions included.
Interestingly this seems happening on my home router only, at work
(always wifi) it works with no issue.
--
You receiv
As a note to any backporters, the original fix for this bug should
include the following change as well:
https://code.launchpad.net/~tyhicks/lightdm/guest-dir-
perms/+merge/322906
It is technically optional but definitely recommended.
--
You received this bug notification because you are a me
Public bug reported:
Once we have systemd-resolved's stub DNS resolver on a solid footing
everywhere (LP: #1682499; LP: #1647031), we should stop using
libnss_resolve.so for name resolution and *only* use the DNS stub
resolver via libnss_dns.so.
The reason is that libnss_resolve.so is non-standar
Even if we don't make this change across the board in SRU, we should
look at changing Ubuntu Core 16 to use only the stub resolver. This
might even turn out to be the root cause of bug #1659195.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Changed in: systemd (Ubuntu Xenial)
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/1673860
Title:
systemd-resolved unit should run Before=
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: software-properties (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
U
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: software-properties (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
U
On 20 Apr 2017 22:20, "Sean Dague" wrote:
For what it's worth, I reported a related issue up to the systemd-devel
mailing list, and it looks like in systemd 233 (the next version) things
work much better with DNSSEC. https://lists.freedesktop.org/archives
/systemd-devel/2017-April/038698.html
I
Ubuntu Core 16 also uses resolved, so this bug also needs to be fixed in
xenial.
** Changed in: systemd (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Xenial)
Status: New => Triaged
** Changed in: systemd (Ubuntu Xenial)
Milestone: None => ubuntu-16.04
Verified by way of a slightly modified test case:
- boot a yakkety cloud image
- verify 127.0.0.53 in /etc/resolv.conf
- sudo sed -i -e's/resolve \[[^]]*\] //' /etc/nsswitch.conf
- ping www.freedesktop.org -> FAIL
- install systemd from -proposed
- ping www.freedesktop.org -> SUCCESS
** Tag
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1685007
Title:
package bluez:i386 5.37-0ubuntu5 failed to install/upgrade:
aliprosessi
There's a lot in this bug report:
- It appears a bluez snap is in use? that'll complicate the distro-provided
bluez
- It appears a bluez package is in use? that'll complicate the snap-provided
bluez
- It appears an i386 build of bluez is reporting errors, but the system
otherwise reports amd64
Hello Carl, thanks for the report; can you please run apport-collect
1684902 to upload some logs that may help diagnose the issue?
Thanks
** Information type changed from Private Security to Public Security
** Package changed: ubuntu => webbrowser-app (Ubuntu)
** Also affects: apparmor (Ubuntu)
*** This bug is a security vulnerability ***
You have been subscribed to a public security bug:
Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2
amd64 (A lightweight web browser tailored for Ubuntu, based on the Oxide
browser engine and using the Ubuntu UI components.), Shown a
Its true there are a few issues with apparmor profiles being loaded as
part of a stack when namespacing is involved. However this does not
appear to be one of them.
However the application may be behaving slightly differently resulting
in the profile needed to be extended. Can you please attach yo
Tobias, sorry for being so long in coming back around to this, but I
followed a pointer to this bug from another one and am now trying to
understand the regression that you're describing.
You described this as "bricking" your servers, but per the SRU
regression analysis:
Running [networkd] befo
Christopher, you don't need to remove the account. You just need to
restart your computer.
** Summary changed:
- Can't add any online accounts
+ GNOME Online Accounts breaks if you log out (until you reboot)
** Changed in: gnome-online-accounts (Ubuntu)
Importance: Undecided => Critical
** C
Ok, so that's an apparmor or apparmor profile problem.
LXD recently changed to also allow for apparmor profiles to be loaded
inside privileged containers. This seems to align with your timeline
above.
Before that change, your kvm process wasn't itself confined when run
inside a privileged LXD con
You say that the resolvconf SRU from #1649931 fixed it /mostly/ but not
in all cases. If you are able to reproduce this problem, can you
provide journalctl output from the affected environment so we can see
what isn't happening in the right order? Do you have step-by-step
instructions we can foll
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mir (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libsdl2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/b
For what it's worth, I reported a related issue up to the systemd-devel
mailing list, and it looks like in systemd 233 (the next version) things
work much better with DNSSEC. https://lists.freedesktop.org/archives
/systemd-devel/2017-April/038698.html
I rebuilt the 233 out of debian experimental,
** Tags removed: need-duplicate-check
--
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/1685022
Title:
package openssh-server 1:7.2p2-4ubuntu2.1 failed to install/upgrade:
Unable to check 16.10 ext4 file-system from 16.04 LTS (!).
Here is log:
sudo fsck -fy /dev/sdc1
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
/dev/sdc1 has unsupported feature(s): metadata_csum
e2fsck: Get a newer version of e2fsck!
--
You received this bug notificatio
Public bug reported:
I messed up the ssh_config file and I need the stock config files for
ssh server.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVer
I apologize, but my comment #9 was wrong :
After more precise testing of 'systemd' version 232-21ubuntu2 from
Ubuntu 17.04 Zesty with 'IdleAction=suspend' and 'IdleActionSec=2min' :
'systemd' does NOT unduly suspend my computer when there is an opened
user session (OK).
But 'systemd' does NOT sy
This bug was fixed in the package systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by defa
This bug was fixed in the package systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by defa
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by defa
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by defa
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by defa
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Also affected by this bug on Ububtu 17.04. Using my computer as a wifi hotspot
I couldn't connect from other devices and the log presented a lot of "inux
wpa_supplicant[1385]: handle_probe_req: send failed
" messages.
The solution presented by Jesse (juderichbourne) on post #1 solved the
issue.
It seems like this is by design, the workaround is to install xserver-
xorg-legacy.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802544
And
http://sources.debian.net/src/xorg-server/2:1.19.3-1/debian/xserver-xorg-core.NEWS/?hl=15#L15
** Bug watch added: Debian Bug tracker #802544
htt
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://
Public bug reported:
While trying to run gdebi-gtk to install a .deb package, program won't
open under Wayland session. Running from terminal produces the
following:
No protocol specified
Unable to init server: Could not connect: Connection refused
No protocol specified
Unable to init server: Cou
This bug was fixed in the package resolvconf - 1.79ubuntu1.1
---
resolvconf (1.79ubuntu1.1) yakkety; urgency=medium
* debian/resolvconf.service: resolvconf service must run before any of the
possible network configuration services (ifupdown, networkd,
NetworkManager) so use
I was able to override it using /etc/systemd/system/apt-
daily.timer.d/override.conf with this config:
###
[Timer]
OnCalendar=
OnCalendar=*-*-* 02:00
RandomizedDelaySec=4h
AccuracySec=1m
Persistent=true
###
Which Means:
OnCalendar | Any day *-*-* at 02:00hrs. NOTE: See the first empty
I have this problem in Xubuntu 17.04 i386 and amd64 versions, in fresh install
and live usb too, with my 2 different dongles (a rtl8187b and a Buffalo
Nintendo WiFi). I tested the i386 iso on 2 computers (one of them is a 64 bit
capable laptop). Ethernet and integrated rtl8188ce wifi adapter are
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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 exec
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.
https://bugs
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.
https://bugs.launchpad.ne
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.
https://bugs.lau
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.
https://bugs.launc
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.
https://bugs
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.
https:
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.
https://bugs
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 Ub
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.
ht
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.
https://bugs
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.
https://bugs.l
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.
https://bugs.launchpad.net/
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.
https://bu
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.
https://bugs.launchpad.
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.
https://
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.
https://
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.
https://bugs.launchpad.net/
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.
https://bu
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 appa
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)
- spaw
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.
https://bugs.lau
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.
https://bu
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.
https://bugs.launc
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.
https://
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.
https://bugs.launchp
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.
https://bu
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 appa
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 sec
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.
https://bu
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.
https://bugs.launchp
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.
https://bugs.launc
1 - 100 of 166 matches
Mail list logo
