** Changed in: snapd
Assignee: Ian Johnson (anonymouse67) => (unassigned)
--
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/1902748
Title:
ubuntu-seed / ubuntu-b
What is the output of these commands:
ps -o cmd fp 1
sudo ls -lah /proc/1/exe
cat /proc/cmdline
--
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/1961418
Title:
snap failed
So indeed your system is still using upstart, in order to use snapd you
will need to switch your system over to use systemd instead. Likely one
of the upgrade scripts from 10.04 to 16.04 did not transition from
upstart to systemd the way a fresh install of 16.04 would default to.
** Changed in: sn
The message should no longer be shown anymore in snapd as the PR
referenced by Maciej has been merged and should be available on the edge
channel of snapd in the few hours. Please give it a try if you like
with:
```
snap install snapd --edge || snap refresh snapd --edge
# test the snap command to
@iogui could you try again? snapd on the edge channel may not have
finished building by the time you tried, but I see that there was an
update pushed out this morning.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-p
@iogui, hmm it could be that our fix isn't working, can you show the
output of these commands:
snap version
snap list
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-pt-base in
Ubuntu.
https://bugs.launchpad.net
Ah Miguel, thanks for realizing my error, I should have probably just
said something like
sudo snap install snapd --edge; sudo snap refresh snapd --edge
which will ensure that it's always installed and gets refreshed.
--
You received this bug notification because you are a member of Ubuntu
Touc
As seb128 found, the issue is also affecting the debian package of snapd
since when we call mksquashfs, we actually have code which specifically
calls mksquashfs from the "system" snap which is either the snapd snap
or the core snap, this is presumably to ensure that a consistent
mksquashfs is used
Also I'm not sure I agree with jdstrand's apparmor profile which
includes:
/run/snapd.socket rw,
which I don't think we want to grant to any PDF file opened with evince?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ap
Dan, note that although we set the SNAP_REEXEC environment variable in
that integration test, that environment variable is actually not obeyed
when it comes to the mksquashfs command which is called here:
https://github.com/snapcore/snapd/blob/dfba7de59a41bc22786d87f53b20deea14240713/snap/squashfs
@slyon could you make available the core18 snap you built with this
systemd ?
--
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/1949089
Title:
systemd randomly fails to activ
Public bug reported:
While upgrading my Raspberry Pi 3 running 21.04 to 21.10, the upgrade
failed
ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-1011-raspi 5.13.0-1011.13
ProcVersionSignature: Ubuntu 5.11.0-1023.25-raspi 5.11.22
Uname: Linux 5.11.0-1023-raspi aarch64
FWIW I know what the snapd issue is, the issue is that snapd does not
and will not work in a nested LXD container, we need to add code to make
snapd.seeded.service die/exit gracefully in this situation.
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Confirmed
** Changed in: snapd
Importance: Undecided => High
** Changed in: snapd
Assignee: (unassigned) => Maciej Borzecki (maciek-borzecki)
--
You received this bug notificat
Is there any timeline on when this will be considered for SRU'ing back
to focal so it is usable in i.e. UC20?
--
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/1878969
Title:
This systemd bug can be problematic for snapd as well, leading to the
sort of situation in https://bugs.launchpad.net/snapd/+bug/1928806,
where running snap commands frequently leads to many many many leftover
scopes like this
** Also affects: snapd
Importance: Undecided
Status: New
--
Public bug reported:
On Ubuntu 18.04.2 LTS Desktop, after running out of space on my disk, my
system was unable to finish booting and I had to go into recovery mode
and remove a number of files before the system would boot. After doing
so I discovered that now the apparmor.service systemd unit alw
FWIW this could be a snapd bug, because while my system was unable to
boot, I disabled all the snaps I had installed except the core snap, and
then after being able to reboot I now re-enable all the snaps and see
some warnings:
May 25 17:32:16 systemd[1]: Starting AppArmor initialization...
May 25
Well I tried restarting AppArmor using `systemctl start apparmor` while
running `dmesg -w -k` and got the following log:
https://pastebin.ubuntu.com/p/98zXMsr6Sy/ I don't see a stack trace for
apparmor itself, just for chrome and pulseaudio.
Is there anyway to have apparmor.service show what profi
How would you recommend I go about checking which profiles are actually
loaded and which profiles are reported as loaded? I have this from aa-
status: https://pastebin.ubuntu.com/p/c2FbrndDzs/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
So I ran your snippet to determine which profiles weren't loaded and the
only one which wasn't loaded was:
```
$ sudo cat /sys/kernel/security/apparmor/profiles | awk '{ print $1 }' >
/tmp/foo ; sudo apparmor_parser -N /etc/apparmor.d/
/var/lib/snapd/apparmor/profiles/ >> /tmp/foo ; sort /tmp/fo
Ah actually, if I move that profile out of the way, then `systemctl
start apparmor` starts immediately. So the issue must be with that
profile being too large (and indeed it is 4-5 MB).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
Yes, certainly use the profile for whatever you can use it for. Would
you like me to edit the description on this bug to reflect the actual
underlying cause here or should I just close this and file a new bug for
the memory usage of this profile? I'm no expert here but I think 15.4 GB
memory usage
@Jamie yes this was generated by snapd, the original snapcraft.yaml is
attached.
And also yes I fully understand this was an atypical usage of layouts, I
was experimenting with using layouts to make it seem to a snap
application that an additional package was installed in the base snap. I
generate
** Summary changed:
- apparmor fails to start with no parser errors
+ apparmor uses excessive memory leading to oom kill
** Description changed:
+ When attempting to load the profile from comment #7, apparmor uses
+ excessive amounts of memory leading to being killed by the OOM killer
+ and thus
I don't think we have such a capability right now in snapd. If you
locally modify the snap-confine profile, it will be rewritten on at
least core refreshes (and reboots as well if I'm not mistaken), so it
sounds like we need some mechanism to specify additional rules to be
included in the snap-conf
Public bug reported:
I'm not sure if this is an Xorg issue or something else, but basically I
have enabled fractional scaling in my Disco Dingo install and upon
rebooting the scaling and the layout of the monitors is forgotten. I
have 2 identical Samsung monitors + 1 LG monitor where the LG and 1
On the same system on a different disk I have Ubuntu 18.04 Desktop
installed which does not have this issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1835585
Title:
Xor
I've seen this inside an Ubuntu 18.04 lxd container with a poor internet
connection as well. apt is version 1.6.11.
--
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/1375405
Title:
Jamie, is this still an issue? I'm inclined to close this since the
apparmor bug seems to have been released a long time ago.
--
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/
Public bug reported:
the version of busybox in the initramfs of uc20, which derives from
ubuntu 20.04, does not have the less module/applet built into it, so
there is no less command available in the initramfs on uc20.
This is unfortunate as sometimes when debugging problems in the
initramfs it i
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1895144
Title:
ubuntu-server CET gap analysis
Status in golang-
** Changed in: snapd
Status: New => Confirmed
** Changed in: snapd
Importance: Undecided => Medium
** Changed in: snapd
Assignee: (unassigned) => Ian Johnson (anonymouse67)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Tags added: uc20
--
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/1902748
Title:
ubuntu-seed / ubuntu-boot partition detection could be improved
Status in snapd:
Confi
I'll take a look at measuring this with snapd $SOON
** Changed in: snapd
Assignee: (unassigned) => Ian Johnson (anonymouse67)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubunt
I can't seem to assign this bug to Dimitri, but as per
https://github.com/snapcore/core20/issues/48, Dimitri should be
preparing a libseccomp 2.4.2 SRU.
** Bug watch added: github.com/snapcore/core20/issues #48
https://github.com/snapcore/core20/issues/48
--
You received this bug notification
36 matches
Mail list logo
