[Bug 2076341] Re: autopkgtest-buildvm-ubuntu-cloud must depend on qemu-utils and qemu-system-x86
*** This bug is a duplicate of bug 2073938 *** https://bugs.launchpad.net/bugs/2073938 Let's keep the dependencies out of it, and focus on checking the correct dependencies are needed before everything explodes later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076341 Title: autopkgtest-buildvm-ubuntu-cloud must depend on qemu-utils and qemu- system-x86 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2076341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076341] [NEW] autopkgtest-buildvm-ubuntu-cloud must depend on qemu-utils and qemu-system-x86
Public bug reported: Usability of autopkgtest-buildvm-ubuntu-cloud is low, as it first pulls a large image from the internet and then crashes on missing tools it should have both depend on in the debian packaging and verified on startup before doing network-heavy work: zyga@x13:~/.spread$ sudo autopkgtest-buildvm-ubuntu-cloud -r bionic Downloading https://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.img... 403.6/405.7 MB (100%) Download successful. Resizing image, adding 20G... Traceback (most recent call last): File "/usr/bin/autopkgtest-buildvm-ubuntu-cloud", line 429, in resize_image(image, args.disk_size) File "/usr/bin/autopkgtest-buildvm-ubuntu-cloud", line 217, in resize_image subprocess.check_call(['qemu-img', 'resize', '-f', 'qcow2', image, '+' + size]) File "/usr/lib/python3.10/subprocess.py", line 364, in check_call retcode = call(*popenargs, **kwargs) File "/usr/lib/python3.10/subprocess.py", line 345, in call with Popen(*popenargs, **kwargs) as p: File "/usr/lib/python3.10/subprocess.py", line 971, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'qemu-img' Some moments later: zyga@x13:~/.spread$ sudo autopkgtest-buildvm-ubuntu-cloud -r bionic Downloading https://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.img... 403.6/405.7 MB (100%) Download successful. Resizing image, adding 20G... Image resized. Building seed image... Booting image to run cloud-init... Traceback (most recent call last): File "/usr/bin/autopkgtest-buildvm-ubuntu-cloud", line 440, in boot_image(image, seed, args.arch, args.qemu_command, File "/usr/bin/autopkgtest-buildvm-ubuntu-cloud", line 363, in boot_image qemu = Qemu( File "/usr/share/autopkgtest/lib/autopkgtest_qemu.py", line 517, in __init__ self.subprocess: Optional[subprocess.Popen[bytes]] = subprocess.Popen( File "/usr/lib/python3.10/subprocess.py", line 971, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'qemu-system-x86_64' In both cases the rather large image was downloaded and discarded. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: autopkgtest 5.32ubuntu3~22.04.1 Uname: Linux 5.15.153.1-microsoft-standard-WSL2 x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Aug 8 14:22:11 2024 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: autopkgtest UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: autopkgtest (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076341 Title: autopkgtest-buildvm-ubuntu-cloud must depend on qemu-utils and qemu- system-x86 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2076341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062173] Re: Apparmor denies updating namespace with ecryptfs
The fix has landed in snapd so it will be available in the latest/edge channel of snapd snap. If you refresh snapd with: snap refresh --edge snapd Then the fix will be immediately active. You should refresh back to stable after the 2.63 release, unless you are comfortable daily-driving possibly unstable software. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062173 Title: Apparmor denies updating namespace with ecryptfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2062173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062173] Re: Apparmor denies updating namespace with ecryptfs
This is fixed by https://github.com/snapcore/snapd/pull/13857 ** Changed in: snapd (Ubuntu) Status: New => In Progress ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062173 Title: Apparmor denies updating namespace with ecryptfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2062173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062330] Re: Chromium fails to start with "invalid home directory"
This is fixed by https://github.com/snapcore/snapd/pull/13857 ** Changed in: chromium-browser (Ubuntu) Status: New => In Progress ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Invalid ** Changed in: snapd (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062330 Title: Chromium fails to start with "invalid home directory" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2062330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062173] Re: Apparmor denies updating namespace with ecryptfs
** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Zygmunt Krynicki (zyga) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062173 Title: Apparmor denies updating namespace with ecryptfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2062173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062330] Re: Chromium fails to start with "invalid home directory"
** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Zygmunt Krynicki (zyga) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062330 Title: Chromium fails to start with "invalid home directory" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2062330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061981] Re: chromium fails to start with non-standard home directory
This bug is now well-understood and a fix is proposed in: https://github.com/snapcore/snapd/pull/13853 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061981 Title: chromium fails to start with non-standard home directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061981] Re: chromium fails to start with non-standard home directory
We are still debugging it, it's not this. It's related to HOMEDIRS tunable and variable expansion, somehow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061981 Title: chromium fails to start with non-standard home directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061981] Re: chromium fails to start with non-standard home directory
We've debugged this issue and the problem is caused by apparmor re- execution and configuration files being loaded from read-only snapd squashfs, thus making HOMEDIRS customization invisible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061981 Title: chromium fails to start with non-standard home directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061832] Re: Firefox startet nicht
I don't speak German very well but if I understand correctly your /home/$LOGNAME is a symbolic link to /Users/$LOGNAME. This arrangement is not supported by snapd as it interferes with the sandbox technology. If you can, modify your system to mount the home directory at /home/baer instead of using symbolic links. This should fix this issue entirely. ** Changed in: snapd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061832 Title: Firefox startet nicht To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2061832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059195] Re: package snapd 2.58+22.04.1 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1
We now believe this bug is understood and we are thinking about a way to address it. The root cause is that the per-distro purge script is unaware of the mounts that need to be stopped and has no way to enumerate them. ** Changed in: snapd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059195 Title: package snapd 2.58+22.04.1 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2059195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059195] Re: package snapd 2.58+22.04.1 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1
Dear reporter. Do you know if the snapd package on your system was customized in any way? Was "snap set ..." used to, for example, allow non-/home home directories? Was snapd and snap packages used for a while or was this a relatively fresh install that was just purged? We're asking because the error that is reported seems to suggest a more serious problem that we would like to understand and fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059195 Title: package snapd 2.58+22.04.1 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2059195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Yes, I think we may be enumerating a directory / statting files. I don't
believe we open anything unless we want to have a look but I _could_ be
wrong and I'm still investigating things (with interruptions to attend
calls).
I don't believe it is related to ubuntu-pro-client, the only reason it
is in the report is that "apt update" hook calls into systemctl so the
warning is printed there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2055239/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Both before and after daemon-reload the units have the same definition:
$ systemctl cat apt-news.service esm-cache.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available to your system.
# This service runs in the background during an `apt update` to download the
# latest news and set it to appear in the output of the next `apt upgrade`.
# The script won't do anything if you've run: `pro config set apt_news=false`.
# The script will limit network requests to at most once per 24 hours.
# You can also host your own aptnews.json and configure your system to use it
# with the command:
# `pro config set apt_news_url=https://yourhostname/path/to/aptnews.json`
[Unit]
Description=Update APT News
[Service]
Type=oneshot
ExecStart=/usr/bin/python3 /usr/lib/ubuntu-advantage/apt_news.py
AppArmorProfile=ubuntu_pro_apt_news
CapabilityBoundingSet=~CAP_SYS_ADMIN
CapabilityBoundingSet=~CAP_NET_ADMIN
CapabilityBoundingSet=~CAP_NET_BIND_SERVICE
CapabilityBoundingSet=~CAP_SYS_PTRACE
CapabilityBoundingSet=~CAP_NET_RAW
PrivateTmp=true
RestrictAddressFamilies=~AF_NETLINK
RestrictAddressFamilies=~AF_PACKET
# These may break some tests, and should be enabled carefully
#NoNewPrivileges=true
#PrivateDevices=true
#ProtectControlGroups=true
# ProtectHome=true seems to reliably break the GH integration test with a lunar
lxd on jammy host
#ProtectHome=true
#ProtectKernelModules=true
#ProtectKernelTunables=true
#ProtectSystem=full
#RestrictSUIDSGID=true
# Unsupported in bionic
# Suggestion from systemd.exec(5) manpage on SystemCallFilter
#SystemCallFilter=@system-service
#SystemCallFilter=~@mount
#SystemCallErrorNumber=EPERM
#ProtectClock=true
#ProtectKernelLogs=true
# /usr/lib/systemd/system/esm-cache.service
# The ESM apt cache will maintain information about what ESM updates are
# available to a system. This information will be presented to users in the apt
# output, or when running pro security-status. These caches are maintained
# entirely outside the system apt configuration to avoid interference with user
# definitions. This service updates those caches. This will only have effect
# on releases where ESM is applicable, starting from Xenial: esm-apps for
# every LTS, and esm-infra for systems in expanded support period after the LTS
# expires.
[Unit]
Description=Update the local ESM caches
[Service]
Type=oneshot
ExecStart=/usr/bin/python3 /usr/lib/ubuntu-advantage/esm_cache.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2055239/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
With a closer look I ended up running this loop while looking at systemd
debug logs:
sudo snap remove --purge snapd && sudo systemctl daemon-reload && sudo
systemctl restart snapd && snap version && sudo apt update && echo
"ALOHA: installing snapd" | systemd-cat && sudo snap install snapd &&
echo "ALOHA: done installing snapd" | systemd-cat
This causes the following log file to show up:
mar 13 13:02:52 ciri systemd[1]: Looking for unit files in (higher priority
first):
mar 13 13:02:52 ciri systemd[1]: /etc/systemd/system.control
mar 13 13:02:52 ciri systemd[1]: /run/systemd/system.control
mar 13 13:02:52 ciri systemd[1]: /run/systemd/transient
mar 13 13:02:52 ciri systemd[1]: /run/systemd/generator.early
mar 13 13:02:52 ciri systemd[1]: /etc/systemd/system
mar 13 13:02:52 ciri systemd[1]: /etc/systemd/system.attached
mar 13 13:02:52 ciri systemd[1]: /run/systemd/system
mar 13 13:02:52 ciri systemd[1]: /run/systemd/system.attached
mar 13 13:02:52 ciri systemd[1]: /run/systemd/generator
mar 13 13:02:52 ciri systemd[1]: /usr/local/lib/systemd/system
mar 13 13:02:52 ciri systemd[1]: /usr/lib/systemd/system
mar 13 13:02:52 ciri systemd[1]: /run/systemd/generator.late
mar 13 13:02:52 ciri systemd[1]: Modification times have changed, need to
update cache.
The message at the bottom of the log comes from systemd's
src/basic/unit-file.c
bool lookup_paths_timestamp_hash_same(const LookupPaths *lp, uint64_t
timestamp_hash, uint64_t *ret_new) {
struct siphash state;
siphash24_init(&state, HASH_KEY.bytes);
STRV_FOREACH(dir, lp->search_path) {
struct stat st;
if (lookup_paths_mtime_exclude(lp, *dir))
continue;
/* Determine the latest lookup path modification time */
if (stat(*dir, &st) < 0) {
if (errno == ENOENT)
continue;
log_debug_errno(errno, "Failed to stat %s, ignoring:
%m", *dir);
continue;
}
siphash24_compress_usec_t(timespec_load(&st.st_mtim), &state);
}
uint64_t updated = siphash24_finalize(&state);
if (ret_new)
*ret_new = updated;
if (updated != timestamp_hash)
log_debug("Modification times have changed, need to update
cache.");
return updated == timestamp_hash;
}
Modification of mtime of any of the directories above is sufficient to
cause this to differ.
I've patched systemd to tell us why systemd thinks it needs to be
reloaded (additional printfs) to get an idea what might be the trigger
that is left stale.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2055239/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Removing ubuntu-pro-client silences this, so that installation of snapd
snap no longer causes any side-effects. While I can see that
installation of snapd has some impact on ubuntu-pro-client, I cannot yet
understand how.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2055239/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Snapd touches neither apt-news.service nor esm-cache.service.
On my system the only mention of esm-cache.service is in
uaclient/actions.py:
zyga@ciri:/$ grep -FR esm-cache.service usr/ 2>/dev/null
usr/lib/python3/dist-packages/uaclient/actions.py:"esm-cache.service",
I've increased systemd logging to debug to see what is replacing the
service but I cannot find any evidence of that in the logs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2055239/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
I've reproduced this and collected forkstat logs from installation of
snapd snap on an otherwise pristine "noble" system. I think what is
going on is that systemd stays in a mode where it knows that units on
disk have changed vs units in memory and will print the warning until
re-loaded. The fact that apt hooks fiddle with systemd units is
sufficient for printing the warning:
apt update causes this thing to execute:
10:37:56 exec 3523 sh -c -- [ ! -e
/run/systemd/system ] || [ $(id -u) -ne 0 ] || systemctl start --no-
block apt-news.service esm-cache.service || true
This is enough for the warning.
The remaining question is where in the installation of snapd do we
modify units after last daemon-reload. I'm focusing on that aspect now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2055239/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.
** Changed in: snapd
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055239
Title:
Warning: The unit file, source configuration file or drop-ins of {apt-
news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
to reload units.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2055239/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039017] Re: [SRU] 2.61.3
The failure of snapd autopkgtest suite looks like infrastructure issue: 1099s - Download snap "go" (10555) from channel "stable" (Get "https://canonical-bos01.cdn.snapcraftcontent.com/download- origin/canonical- lgw01/Md1HBASHzP4i0bniScAjXGnOII9cEK6e_10555.snap?interactive=1&token=1710280800_3e59ace000f75f3bf9d5b52c1de3c09f8aedd5bb": net/http: timeout awaiting response headers) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039017 Title: [SRU] 2.61.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2039017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947046] Re: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
I've experienced this after installing Impish host on Raspberry Pi 4 with an Impish VM. The VM was working correctly up until just a moment ago, as I type this, I've installed `linux-modules-extra-raspi in order to get usb serial adapters to work inside the virtual machine. The package installed normally and initrd was created normally as well. Upon reboot, the only thing I see is the error mentioned in this bug report (you can see it if you do: lxc start --attach) and the VM is spinning at 100% CPU but linux is not booting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947046 Title: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1947046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786699] Re: grub-install command line options incompatible with Debian
This is now fixed upstream https://gitlab.com/larswirzenius/vmdb2/-/merge_requests/83 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786699 Title: grub-install command line options incompatible with Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1786699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944447] Re: refresh-app-awareness=true does not seem to concern dependencies
Updating gnome snap will remove the mount points from the firefox snap mount namespace. It should not be done. I'm afraid r-a-a should be extended to prevent refreshes of any connected snaps with the content interface as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/197 Title: refresh-app-awareness=true does not seem to concern dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933827] Re: Symlink incorrectly installs to a sub-directory related to source name (github: 80)
Updated patch with quilt support :) ** Patch removed: "debdiff with cherry picked fix" https://bugs.launchpad.net/ubuntu/+source/zmk/+bug/1933827/+attachment/5507662/+files/zmk-0.4.2-2-to-0.4.2-2ubuntu1.debdiff ** Patch added: "zmk-0.4.2-2-to-0.4.2-2ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/zmk/+bug/1933827/+attachment/5507663/+files/zmk-0.4.2-2-to-0.4.2-2ubuntu1.debdiff ** Description changed: This bug is a mirror of the GitHub issue https://github.com/zyga/zmk/issues/80 filed for the purpose of SRU The following makefile snippet illustrates the problem: # Symlink: sysota-rauc-hook -> sysotad cmd/sysotad/sysota-rauc-hook.InstallDir = $(cmd/sysotad/sysotad.InstallDir) cmd/sysotad/sysota-rauc-hook.SymlinkTarget = sysotad $(eval $(call ZMK.Expand,Symlink,cmd/sysotad/sysota-rauc-hook)) The result of make install should be ln -s sysotad /usr/lib/sysotad/sysotad-rauc-hook With zmk << 0.5.1 it is ln -s sysotad /usr/lib/sysotad/cmd/sysotad/sysotad-rauc-hook This bug was fixed in zmk 0.5.1 [Impact] The issue is isolated to the ZMK Symlink template and is only visible when the path of the symbolic link, in the development tree, contains a sub-directory, like in the RAUC hook example above. [Test Case] Create a makefile with this content: include z.mk $(eval $(call ZMK.Import,Directories)) subdir/symlink.InstallDir = $(bindir) subdir/symlink.SymlinkTarget = target $(eval $(call ZMK.Expand,Symlink,subdir/symlink)) Issue the command: make -n install. The correct output is: ln -sf target /usr/local/bin/symlink In the broken case, the output is: ln -sf target /usr/local/bin/subdir/symlink + + [Where problems could occur] + Since zmk is only used by my own software, most notably libzt, and libzt does not trigger this error, the regression potential is minimal. ** Description changed: This bug is a mirror of the GitHub issue https://github.com/zyga/zmk/issues/80 filed for the purpose of SRU The following makefile snippet illustrates the problem: # Symlink: sysota-rauc-hook -> sysotad cmd/sysotad/sysota-rauc-hook.InstallDir = $(cmd/sysotad/sysotad.InstallDir) cmd/sysotad/sysota-rauc-hook.SymlinkTarget = sysotad $(eval $(call ZMK.Expand,Symlink,cmd/sysotad/sysota-rauc-hook)) The result of make install should be ln -s sysotad /usr/lib/sysotad/sysotad-rauc-hook With zmk << 0.5.1 it is ln -s sysotad /usr/lib/sysotad/cmd/sysotad/sysotad-rauc-hook - This bug was fixed in zmk 0.5.1 + This bug was fixed in zmk 0.5.1, which is available in Debian Unstable + and Ubuntu Impish as 0.5.1-2 [Impact] The issue is isolated to the ZMK Symlink template and is only visible when the path of the symbolic link, in the development tree, contains a sub-directory, like in the RAUC hook example above. [Test Case] Create a makefile with this content: include z.mk $(eval $(call ZMK.Import,Directories)) subdir/symlink.InstallDir = $(bindir) subdir/symlink.SymlinkTarget = target $(eval $(call ZMK.Expand,Symlink,subdir/symlink)) Issue the command: make -n install. The correct output is: ln -sf target /usr/local/bin/symlink In the broken case, the output is: ln -sf target /usr/local/bin/subdir/symlink [Where problems could occur] Since zmk is only used by my own software, most notably libzt, and libzt does not trigger this error, the regression potential is minimal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933827 Title: Symlink incorrectly installs to a sub-directory related to source name (github: 80) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zmk/+bug/1933827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933827] Re: Symlink incorrectly installs to a sub-directory related to source name (github: 80)
I've attached a debdiff fixing this in the most minimal way possible ** Patch added: "debdiff with cherry picked fix" https://bugs.launchpad.net/ubuntu/+source/zmk/+bug/1933827/+attachment/5507662/+files/zmk-0.4.2-2-to-0.4.2-2ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933827 Title: Symlink incorrectly installs to a sub-directory related to source name (github: 80) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zmk/+bug/1933827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933827] Re: Symlink incorrectly installs to a sub-directory related to source name (github: 80)
** Description changed: This bug is a mirror of the GitHub issue https://github.com/zyga/zmk/issues/80 filed for the purpose of SRU The following makefile snippet illustrates the problem: # Symlink: sysota-rauc-hook -> sysotad cmd/sysotad/sysota-rauc-hook.InstallDir = $(cmd/sysotad/sysotad.InstallDir) cmd/sysotad/sysota-rauc-hook.SymlinkTarget = sysotad $(eval $(call ZMK.Expand,Symlink,cmd/sysotad/sysota-rauc-hook)) The result of make install should be ln -s sysotad /usr/lib/sysotad/sysotad-rauc-hook With zmk << 0.5.1 it is ln -s sysotad /usr/lib/sysotad/cmd/sysotad/sysotad-rauc-hook This bug was fixed in zmk 0.5.1 + + [Impact] + + The issue is isolated to the ZMK Symlink template and is only visible + when the path of the symbolic link, in the development tree, contains a + sub-directory, like in the RAUC hook example above. + + [Test Case] + Create a makefile with this content: + + include z.mk + $(eval $(call ZMK.Import,Directories)) + subdir/symlink.InstallDir = $(bindir) + subdir/symlink.SymlinkTarget = target + $(eval $(call ZMK.Expand,Symlink,subdir/symlink)) + + Issue the command: make -n install. The correct output is: + + ln -sf target /usr/local/bin/symlink + + In the broken case, the output is: + + ln -sf target /usr/local/bin/subdir/symlink -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933827 Title: Symlink incorrectly installs to a sub-directory related to source name (github: 80) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zmk/+bug/1933827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933827] [NEW] Symlink incorrectly installs to a sub-directory related to source name (github: 80)
Public bug reported: This bug is a mirror of the GitHub issue https://github.com/zyga/zmk/issues/80 filed for the purpose of SRU The following makefile snippet illustrates the problem: # Symlink: sysota-rauc-hook -> sysotad cmd/sysotad/sysota-rauc-hook.InstallDir = $(cmd/sysotad/sysotad.InstallDir) cmd/sysotad/sysota-rauc-hook.SymlinkTarget = sysotad $(eval $(call ZMK.Expand,Symlink,cmd/sysotad/sysota-rauc-hook)) The result of make install should be ln -s sysotad /usr/lib/sysotad/sysotad-rauc-hook With zmk << 0.5.1 it is ln -s sysotad /usr/lib/sysotad/cmd/sysotad/sysotad-rauc-hook This bug was fixed in zmk 0.5.1 ** Affects: zmk (Ubuntu) Importance: Undecided Status: New ** Description changed: This bug is a mirror of the GitHub issue https://github.com/zyga/zmk/issues/80 filed for the purpose of SRU The following makefile snippet illustrates the problem: # Symlink: sysota-rauc-hook -> sysotad cmd/sysotad/sysota-rauc-hook.InstallDir = $(cmd/sysotad/sysotad.InstallDir) cmd/sysotad/sysota-rauc-hook.SymlinkTarget = sysotad $(eval $(call ZMK.Expand,Symlink,cmd/sysotad/sysota-rauc-hook)) + The result of make install should be - The result of make install should be ln -s sysotad /usr/lib/sysotad/sysotad-rauc-hook. With zmk 0.5 it is ln -s sysotad /usr/lib/sysotad/cmd/sysotad/sysotad-rauc-hook. + ln -s sysotad /usr/lib/sysotad/sysotad-rauc-hook + + With zmk << 0.5.1 it is + + ln -s sysotad /usr/lib/sysotad/cmd/sysotad/sysotad-rauc-hook + + This bug was fixed in zmk 0.5.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933827 Title: Symlink incorrectly installs to a sub-directory related to source name (github: 80) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zmk/+bug/1933827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930995] Re: snapd too heavy for lubuntu
Snapd does not need to be running to run apps. It is really only required to handle auto-updates. Everything else will auto start on socket activation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930995 Title: snapd too heavy for lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1930995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925810] Re: Bashism in snapd.sh (aka apps-in-path.sh) breaks dash
On a second look, this is fixed by ae84b651f464f297c046b60b82c60ecdd69ce80e - a patch from the 2nd of Feb 2021. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925810 Title: Bashism in snapd.sh (aka apps-in-path.sh) breaks dash To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1925810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925810] Re: Incorrect quote use in apps-bin-path.sh
** Also affects: snapd Importance: Undecided Status: New ** Summary changed: - Incorrect quote use in apps-bin-path.sh + Bashism in snapd.sh (aka apps-in-path.sh) breaks dash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925810 Title: Bashism in snapd.sh (aka apps-in-path.sh) breaks dash To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1925810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918021] Re: Got Setting up libpaper1:amd64 (1.1.28) ... ucf: do not have write privilege to the state data while building simple Docker container
** Changed in: libpaper (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918021 Title: Got Setting up libpaper1:amd64 (1.1.28) ... ucf: do not have write privilege to the state data while building simple Docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpaper/+bug/1918021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714941] Re: mounts should hint ignore
Dear reporter. The mount and loopback device is created by libmount, through systemd. Do you know if there's a way for snapd to indicate that the loop device should be created with that attribute? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714941 Title: mounts should hint ignore To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1714941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643706] Re: snap apps need to be able to browse outside of user $HOME dir. for Desktop installs
Hey Itay Perl. Unfortunately we cannot mount an overlayfs to solve this issue as is is not compatible with apparmor and it would effectively break confinement. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643706 Title: snap apps need to be able to browse outside of user $HOME dir. for Desktop installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1643706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786699] Re: grub-install command line options incompatible with Debian
** Patch added: "This patch is against the vmdb2-0.19 upstream tag" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1786699/+attachment/5453052/+files/0001-Support-grub-compat-setting-for-Ubuntu.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786699 Title: grub-install command line options incompatible with Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1786699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786699] Re: grub-install command line options incompatible with Debian
I've sent a patch to https://gitlab.com/larswirzenius/vmdb2/-/issues/36#note_485816538 which enables support for Ubuntu and Debian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786699 Title: grub-install command line options incompatible with Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1786699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900693] Re: snapd cannot refresh on some SD cards due to uboot bug
I've updated pi gadget to latest/stable and then manually updated the assets by copying files fro the gadget boot assets to the appropriate place on the FAT partition. Upon reboot uboot version was U-Boot> version U-Boot 2019.07+dfsg-1ubuntu4~18.04.1 (Dec 19 2019 - 22:06:27 +) gcc (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0 GNU ld (GNU Binutils for Ubuntu) 2.30 Subsequently I was able to successfully write to FAT from uboot: U-Boot> saveenv Saving Environment to FAT... OK U-Boot> saveenv Saving Environment to FAT... OK I think this worked. Note that without bumping the edition field, this will require manual intervention. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900693 Title: snapd cannot refresh on some SD cards due to uboot bug To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1900693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901444] Re: mount --rbind /var/tmp /tmp/snap.rootfs_1DwCoc//var/tmp: Permission denied)
Is /var/tmp a symbolic link? I think we only handle a case when that is a real directory. ** Also affects: snapd Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901444 Title: mount --rbind /var/tmp /tmp/snap.rootfs_1DwCoc//var/tmp: Permission denied) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1901444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901847] Re: snapd fails to shut down, gets killed after 1m30s during reboot
I wonder what is causing that activity: spal. 28 11:03:26 blynas snapd[1013]: daemon.go:586: WARNING: cannot gracefully shut down in-flight snapd API activity within: 25s This is why we are timing out on shutdown. ** Also affects: snapd Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901847 Title: snapd fails to shut down, gets killed after 1m30s during reboot To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1901847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898869] Re: System slow on booting
Could you provide journal log from the last boot? journalctl -b 0 should do the trick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898869 Title: System slow on booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901578] Re: Cannot remove snap package ubuntu 20.10
I was curious where we do this so I went looking and this is the start of the problem: https://github.com/snapcore/snapd/blob/7ff96a40a7a7a7779db250b087cec9b183540130/overlord/snapshotstate/backend/helpers.go#L145 In absence of other information, we snapshot the state for all the users this way. ** Changed in: snapd Status: Incomplete => Confirmed ** Changed in: snapd Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901578 Title: Cannot remove snap package ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1901578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901578] Re: Cannot remove snap package ubuntu 20.10
This is caused by a bug in the snapshot code, which enumerates users by their HOME entries. We should handle this case better. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901578 Title: Cannot remove snap package ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1901578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662552] Re: snaps don't work with NFS home
Hey Markus. Thank you for providing details about your environment. Unfortunately we don't have any new ideas on how to solve home-at-nearly arbitrary path and we certainly didn't have time to push this idea forward. One idea I had a while ago is to mount whatever the original location of HOME, at /var/home/$LOGNAME, offering unique path for any user. This is assuming the path cannot be represented in the original location. This technically could work, we would have a fixed extension of various key paths and the security subsystem would be able to handle that. What would not be optimal is the disconnect between what a snap application process thinks on the inside of the environment (e.g. HOME is /var/home/zyga) and what the system meta-data says (e.g. /home/zyga). We have a variation of that problem today (/home/zyga for real and /home/zyga/snap/$SNAP_NAME/$SNAP_REVISION) but we wanted to figure out how to avoid that as well. If the end user experience is acceptable, that would be something worth considering, especially if this makes the snap ecosystem usable. I cannot comment on the kerberos details. I think snapd could work in this environment as we have supported root squashing NFS home in /home/$LOGNAME before. I think we could only push forward (e.g. handle more paths via /var/home idea) and see what's missing. I can try proposing an experimental feature for /var/home and see if that helps you out. I could do this assuming you are willing to report back and share your experience and issues you've encountered. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662552 Title: snaps don't work with NFS home To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1662552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
The snapd side of this fix is baking in https://github.com/snapcore/snapd/pull/9530 ** Changed in: snapd Status: Confirmed => In Progress ** Changed in: snapd Assignee: (unassigned) => Zygmunt Krynicki (zyga) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900693] Re: snapd cannot refresh on some SD cards due to uboot bug
This issue is fixed upstream https://github.com/u-boot/u-boot/commit/b1125802a524641ad1ac803b4a617756d26f007d but the corresponding patch is not available in bionic or focal. Groovy u-boot package is recent enough to contain this fix. ** Also affects: u-boot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900693 Title: snapd cannot refresh on some SD cards due to uboot bug To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1900693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898038] Re: docker-support/multipass-support broken with system apparmor3 (20.10)
We took Alexes work on this and ended up using a different strategy to fix it, one he suggested initially. The explanation of the motives are captured by the pull request: https://github.com/snapcore/snapd/pull/9516 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898038 Title: docker-support/multipass-support broken with system apparmor3 (20.10) To manage notifications about this bug go to: https://bugs.launchpad.net/docker/+bug/1898038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662552] Re: snaps don't work with NFS home
@Marc, what is the bug report you've opened? Chromium has no more debian packages as the team supporting it decided that it is exceedingly difficult to maintain (especially for releases other than latest). This is unrelated to snapd. Without snapd it would simply be removed from the archive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662552 Title: snaps don't work with NFS home To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1662552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662552] Re: snaps don't work with NFS home
Marc Kolly, could you please open a new bug with details of your particular configuration please. Commenting on a bug that is fix released is not useful as we have integration tests that verify this particular particular behavior works. I suspect there is something about your setup we are misidentifying, which is causing further issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662552 Title: snaps don't work with NFS home To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1662552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898038] Re: docker-support/multipass-support broken with system apparmor3 (20.10)
We could use snap-update-ns to hide the host's /etc if those specific interfaces are connected. We could then present the relevant file from the base snap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898038 Title: docker-support/multipass-support broken with system apparmor3 (20.10) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1898038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891259] Re: snap installation with core18 fails at 'Ensure prerequisites for "etcd" are available' in air-gapped environments as snapd always requires core(16)
I'm marking the snapd task as invalid as it seems to be a problem with the set of snaps available in offline mode. ** Changed in: snapd Status: New => Invalid ** Changed in: snapd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891259 Title: snap installation with core18 fails at 'Ensure prerequisites for "etcd" are available' in air-gapped environments as snapd always requires core(16) To manage notifications about this bug go to: https://bugs.launchpad.net/charm-etcd/+bug/1891259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878225] Re: Please remove lxd.snap from lxd images, as it fails to seed thus failing the first boot - snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64
I'm marking this as triaged. We should look at the seeding code to ensure it can eventually actually fail and allow systems to continue booting. ** Changed in: snapd Status: New => Triaged ** Changed in: snapd Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878225 Title: Please remove lxd.snap from lxd images, as it fails to seed thus failing the first boot - snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1878225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869629] Re: please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns
I'm marking this as fix released based on the history of the referenced pull request. ** Changed in: snapd Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869629 Title: please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1869629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850282] Re: snap cannot be run while being upgraded − no user feedback
This is still in development but there's some actual progress recently. Complete development history is visible in https://github.com/snapcore/snapd/projects/3 We are aiming to release a, still disabled by default, but much improved version of this as either 2.47 or 2.48, depending on when the reviews arrive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850282 Title: snap cannot be run while being upgraded − no user feedback To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1850282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869024] Re: add support for DynamicUser feature of systemd
I'm marking the snapd task as fix released, for 2.45 based on the history of the referenced pull request. ** Changed in: snapd Milestone: None => 2.45 ** Changed in: snapd Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869024 Title: add support for DynamicUser feature of systemd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1869024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880085] Re: snap userd's OpenURL method allows sandox escape
This was released a while ago, the upstream task was stale. ** Changed in: snapd Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880085 Title: snap userd's OpenURL method allows sandox escape To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1880085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871364] Re: Ubuntu Snap Store can't download resources when proxy is set to "auto"
I'm marking this as fix released based on the history of the referenced pull request. ** Changed in: snapd Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871364 Title: Ubuntu Snap Store can't download resources when proxy is set to "auto" To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1871364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643706] Re: snap apps need to be able to browse outside of user $HOME dir. for Desktop installs
Dear Rajat, please mount your external disk under /mnt/* or using dynamic location in /media. Those locations are not supported. Arbitrary locations cannot be supported, until all applications access files using portals. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643706 Title: snap apps need to be able to browse outside of user $HOME dir. for Desktop installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1643706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891526] Re: snapd.seeded.service hangs lxd container boots for five minutes
That last error about missing slots looks like another error. It may be a race indeed. How can I reproduce it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891526 Title: snapd.seeded.service hangs lxd container boots for five minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1891526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
Those are not fixed locations. You'd have to cope with responding to the settings (that may differ per process) that govern their location. In addition the ~/snap directory is very explicitly, and non-trivially baked into apparmor profiles that are currently global to the system. This setting can vary per user. Lastly .config and .local and .cache are just top-level directories with absolutely no structure inside. Where do you put the per-snap $HOME? Is there a connection between a random dot- file like .vim or .vimrc that the snap writes to, relative to $HOME to .local or .config? All nice solutions have the fatal flaw of being entirely unrealistic in practice. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891259] Re: snap installation with core18 fails at 'Ensure prerequisites for "etcd" are available' in air-gapped environments
Dear reporter, please check if: snap download etcd snap download core18 snap ack *.assert snap install ./core18_*.snap snap install ./etcd_*.snap fixes the problem for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891259 Title: snap installation with core18 fails at 'Ensure prerequisites for "etcd" are available' in air-gapped environments To manage notifications about this bug go to: https://bugs.launchpad.net/charm-etcd/+bug/1891259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891259] Re: snap installation with core18 fails at 'Ensure prerequisites for "etcd" are available' in air-gapped environments
I think that you will find that using `snap ack...` is the right thing to do. I didn't test this manually but the use of `--dangerous` creates quite a different environment than without it. ** Changed in: snapd Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891259 Title: snap installation with core18 fails at 'Ensure prerequisites for "etcd" are available' in air-gapped environments To manage notifications about this bug go to: https://bugs.launchpad.net/charm-etcd/+bug/1891259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643706] Re: snap apps need to be able to browse outside of user $HOME dir. for Desktop installs
@nigels - there is no setting because there's no real way to represent arbitrary location. This is a very hard technical problem, not the lack of a knob to control some setting. There are conventions we could use to get to a state where most users could be happy. Where is your music and videos mounted? Could you mount them in a sub-directory of /mnt perhaps? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643706 Title: snap apps need to be able to browse outside of user $HOME dir. for Desktop installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1643706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866619] Re: OverflowError when machine suspends and resumes after a longer while
Someone with upload access just needs to apply the patch and send it upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866619 Title: OverflowError when machine suspends and resumes after a longer while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dstat/+bug/1866619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
The real priority is on the upstream project. The Ubuntu package priority is irrelevant and I cannot change it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887134] Re: Purging of snapd package should remove all files in / installed by snaps
** Changed in: snapd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887134 Title: Purging of snapd package should remove all files in / installed by snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1887134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir
** Changed in: snapd Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784774 Title: snapd is not autofs aware and fails with nfs home dir To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1784774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir
This is now fixed by https://github.com/snapcore/snapd/pull/8936 ** Changed in: snapd Status: Triaged => In Progress ** Changed in: snapd Milestone: None => 2.46 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784774 Title: snapd is not autofs aware and fails with nfs home dir To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1784774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir
With the additional information in https://bugs.launchpad.net/snapd/+bug/1821193 I think we can fix this issue quickly. 1) The mountinfo parser will now look for an automount point that mentions autofs, an example line is mentioned here: 137 29 0:50 / /home rw,relatime shared:87 - autofs /etc/auto.master.d/home rw,fd=7,pgrp=22588,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=173399 2) We could optionally look at the referenced file (/etc/auto.master.d/home) and parse it, in this case it contains this line (among others) * -fstype=nfs,vers=4,rw,soft,rsize=8192,wsize=8192 prodpeda-samba.domain.fr:/home/& With this information we can enable the workaround reliably. I will not do 2) at first, unless reviewers deem it necessary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784774 Title: snapd is not autofs aware and fails with nfs home dir To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1784774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863255] Re: Programs installed in Snap format do not detect the keyboard
This issue was fixed in snapd 2.43 which was since released to the stable channel. Marking as such. ** Changed in: snapd Milestone: None => 2.43 ** Changed in: snapd Status: Fix Committed => Fix Released ** Changed in: snapd Milestone: 2.43 => 2.44 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863255 Title: Programs installed in Snap format do not detect the keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1863255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863255] Re: Programs installed in Snap format do not detect the keyboard
On closer look it seems that the patch was included in 2.44. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863255 Title: Programs installed in Snap format do not detect the keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1863255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881350] Re: snap seeding fails with libc6-lse
This issue was fixed in snapd 2.45.1 which was released as a part of the snapd snap but not yet as a part of the core snap. Marking as fix released since it's technically out. ** Changed in: snapd Milestone: None => 2.45.1 ** Changed in: snapd Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881350 Title: snap seeding fails with libc6-lse To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865282] Re: Snap chromium - apparmor pulseAudio (and other) error messages (20.04)
I didn't pinpoint the exact release but it seems to have been released to stable sometime in snapd 2.44.*. Marking as released. ** Changed in: snapd Status: Fix Committed => Fix Released ** Changed in: snapd Milestone: None => 2.44 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865282 Title: Snap chromium - apparmor pulseAudio (and other) error messages (20.04) To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor-profiles/+bug/1865282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876083] Re: chromium snap from focal fails DNS lookups, or delays them (ipv6)
I'm marking this as medium as we should handle ipv6 better and this may help to determine if there's a broad issue in the base snaps, either on the configuration side or in the set of packages contained. ** Changed in: snapd Status: New => Triaged ** Changed in: snapd Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876083 Title: chromium snap from focal fails DNS lookups, or delays them (ipv6) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1876083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878377] Re: USB keyboard doesn't work with rpi3 (armhf)
I'm marking the snapd task as invalid as it's really not something that snapd interacts with. Most likely kernel configuration OR core20 snap. If it happens that this is related to kernel modules and their layout in the system please reopen the snapd task. ** Changed in: snapd Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878377 Title: USB keyboard doesn't work with rpi3 (armhf) To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881159] Re: BUG: soft lockup on return from recover to run mode on rpi3a+
** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881159 Title: BUG: soft lockup on return from recover to run mode on rpi3a+ To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682023] Re: snapd/snap-confine leaves behind /etc/apparmor.d/usr.lib.snapd.snap-confine on upgrade
Snapd 2.43 has been released a while ago. Marking as released. ** Changed in: snapd Status: Fix Committed => Fix Released ** Changed in: snapd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682023 Title: snapd/snap-confine leaves behind /etc/apparmor.d/usr.lib.snapd.snap- confine on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1682023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867415] Re: Hardlinking snaps wastes 400 MB tmpfs RAM in live CDs
Snapd 2.45 has been released to stable, marking as released. The Ubuntu package is in the SRU pipe. ** Changed in: snapd Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867415 Title: Hardlinking snaps wastes 400 MB tmpfs RAM in live CDs To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1867415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867415] Re: Hardlinking snaps wastes 400 MB tmpfs RAM in live CDs
** Changed in: snapd Milestone: None => 2.45 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867415 Title: Hardlinking snaps wastes 400 MB tmpfs RAM in live CDs To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1867415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866183] Re: seccomp tests fail in tumbleweed on 2020-03-05 and 20.04
Snapd 2.44 has been released, marking as the bug as such. ** Changed in: snapd Status: Fix Committed => Fix Released ** Changed in: snapd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866183 Title: seccomp tests fail in tumbleweed on 2020-03-05 and 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1866183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881350] Re: snap seeding fails with libc6-lse
I relayed the question to mvo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881350 Title: snap seeding fails with libc6-lse To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881350] Re: snap seeding fails with libc6-lse
** Changed in: snapd Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881350 Title: snap seeding fails with libc6-lse To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881350] Re: snap seeding fails with libc6-lse
This will be fixed with https://github.com/snapcore/snapd/pull/8788 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881350 Title: snap seeding fails with libc6-lse To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881350] Re: snap seeding fails with libc6-lse
Thanks, I'm done with the machine. I left it in a state where it can install snaps but it will likely break on re-exec. I'll send a fix to snapd now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881350 Title: snap seeding fails with libc6-lse To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881350] Re: snap seeding fails with libc6-lse
$ ldd /usr/lib/snapd/snap-confine linux-vdso.so.1 (0xac8e6000) libudev.so.1 => /lib/aarch64-linux-gnu/libudev.so.1 (0xac84e000) libpthread.so.0 => /lib/aarch64-linux-gnu/atomics/libpthread.so.0 (0xac81f000) libc.so.6 => /lib/aarch64-linux-gnu/atomics/libc.so.6 (0xac6b) /lib/ld-linux-aarch64.so.1 (0xac8b6000) I know what to do, please keep the machine around for some more time and I should have a confirmed solution. ** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Status: New => Confirmed ** Changed in: snapd Importance: Undecided => High ** Changed in: snapd Assignee: (unassigned) => Zygmunt Krynicki (zyga) ** Changed in: snapd Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881350 Title: snap seeding fails with libc6-lse To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881350] Re: snap seeding fails with libc6-lse
I'm experimenting there now. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881350 Title: snap seeding fails with libc6-lse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1881350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881350] Re: snap seeding fails with libc6-lse
Dear reporter, can you attach the output of `dmesg | grep DENIED` after a failed attempt please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881350 Title: snap seeding fails with libc6-lse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1881350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879229] Re: pulseaudio/audio-playback are difficult to use
I can fully confirm this, having gone through the exercise myself this weekend. ** Changed in: snapd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879229 Title: pulseaudio/audio-playback are difficult to use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1879229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879229] Re: pulseaudio/audio-playback are difficult to use
Step 2 is difficult to handle in snapd as it interacts with the organization of files in the snap that traditionally snapd does not interact with. Step 3 depends on the implementation of pulse on the host, though I agree this is the correct solution, for now, and that it should *not* be handled by snap packages but by a layer inside snapd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879229 Title: pulseaudio/audio-playback are difficult to use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1879229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878225] Re: snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64
I believe this is really the bug that snapd cannot install "core" or "core18" inside a container without failing on udev. The well-known workaround is to do it twice. I think we should sit down and discuss this but I think this can only be done after core20 beta is out as we simply have no time for another topic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878225 Title: snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878225] Re: snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64
The udev error is the well-known problem that of snapd pulling udev into containers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878225 Title: snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878225] Re: snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64
We've retrieved the OOPS from the ID mentioned in the log you've attached. It seems the error is ERROR run hook "install": cannot perform operation: mount --rbind /snap /snap: Permission denied Can you provide the output of "dmesg | grep DENIED" please? In addition, can you please add "ls -ld /snap" (mainly to check if it's a directory or something else). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878225 Title: snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878225] Re: snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64
This looks like a problem in the seed used to create this image. Can you please attach: /var/lib/snapd/seed/seed.yaml as well as find /var/lib/snapd/seed please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878225 Title: snapd.seeded.service waits forever (?) to have snaps seeded in LXD on s390x and arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876583] Re: "panic: runtime error: slice bounds out of range" while installing any snap package
What's the chance this fails because of i18n? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876583 Title: "panic: runtime error: slice bounds out of range" while installing any snap package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1876583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1643706] snap apps need to be able to browse outside of user $HOME dir. for Desktop installs
> Wiadomość napisana przez Oliver <1643...@bugs.launchpad.net> w dniu > 04.05.2020, o godz. 09:39: > > > @zyga wrote: > >> Allowing access outside of /home is possible but allowing access to arbitrary >> places is not possible for obvious reasons. The work on portals is ongoing >> and >> it will, for cooperating applications, allow to open files from >> user-specified >> locations. > > The reasons don't seem so obvious to me. Could you please elaborate? I > get it, confinement and all. But as a user I have no influence whether a It's not just confinement. To understand the reason you need to build a mental model of how snap applications execute. The root filesystem is not writable. We cannot create arbitrary directories. The root filesystem is the current revision of whatever the "base" snap was picked by the snap developer, or in absence of any declaration, the core snap. That snap as you may know, is an immutable filesystem image, pretty much like a CD-ROM image. Anything we "bring" from the host system, like the /home directory or the /root directory or /var/lib/snapd directory must *already* exist as an empty directory in the base snap. When we "bring" it from the host we create a mount point that shows a portion of the host filesystem inside the filesystem view that the snap applications see. Let's say you want to put your stuff in /data, and you'd like to have a configuration file that makes that directory visible for snaps. To do this you have to solve all of those challenges: - how to create /data so that you can mount (host)/data into (snap)/data? - how to represent /data for security, is it equivalent to the home interface or do you want to special-case it? - what if the location is not /data but actually something that already exists in snap view? say /usr/lib, after all, it is configurable so the user may, without knowing the consequences, choose to do that. > snap comes as strictly confined or not. And so when facing this issue I > am looking to _configure_ this in a way that makes it possible. Why > can't the user (or admin) decide on their own? For example in my case Because to make the system possible at all (i.e. programs execute) we decided that some conventions are sufficient and any data management problem can be framed in the established conventions. Anything you choose to store in /data or /foo or wherever *may* be represented as a directory in your home directory in /home/$LOGNAME. Is it annoying if you were using /data for years? no doubt. But it is possible. We have not found a way that would let us do anything else while keeping snaps executable. > I'd want to add /data/oliver to the list of locations that are available > to this particular snap (vlc) and I may want to make _other_ locations > available to other snaps. Sure, there will probably be users who'd give > some of their snaps free rein, but shouldn't that be their prerogative? It's not a matter of choice but of implementation. I strongly invite you to join us on #snappy on freenode and discuss implementation. If you come up with a way to make it work I would love to help you implement it. > > I'll even take it further: when I would connect _my_ particular > "arbitrary" location to the vlc snap I'd want to do that read-only. I > see no reason for VLC to do more than reading in those locations. This > may vary for others (e.g. to be able to create playlists or so?!), but > I'd simply want my outside location to appear inside the snap read-only. > > Just since @chipaca was trying to elicit use cases ;) The implementation is evolving. As we gain more kernel features and learn of creative ways to use existing features it may become possible to do what you want. Right now we are where we are. I hope you understand where we are coming from. There are lots of use cases and everyone cannot be supported at the same instant in equal amount, as we have finite resources. Best regards ZK -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643706 Title: snap apps need to be able to browse outside of user $HOME dir. for Desktop installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1643706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
To be clear, we've agreed to work on this in our cycle that runs for the next 6 months. It's happening! :) ** Changed in: snapd Importance: Wishlist => High ** Changed in: snapd Assignee: (unassigned) => Zygmunt Krynicki (zyga) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
I understand the sentiment with ~/snap being a fixed location, shared by both yourself and other people who have commented here. The cost of making ~/snap arbitrary is very high but we have some ideas that we are actively exploring as a part of the 20.10 cycle planning and I suspect there will be some exciting updates to share once the plans are more solid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
Hey, a fellow snapd developer here. We do not use XDG locations for the following reasons: 1) They are configurable, per user, which would require per-user confinement that we currently do not support. 2) Ignoring that, the standard locations are not followed by *all* software uniformly so we need a location for things that do not fit XDG anyway. As an example, a snap of something like vim would use ~/.vim and ~/.vimrc outside of confinement. That would need mapping to _a_ path inside the confinement. We would have to have some form of ~/snap/vim/current/.vim anyway. Where would that go? 3) In addition to that, snapd manages application data and creates two distinct locations, the per-revision data set ~/snap/$SNAP_NAME/$SNAP_REVISION and ~/snap/$SNAP_NAME/common. This is essential to handle "snap revert" which rolls back both the application code and application data. There's no clear mapping of that to any of the XDG documented locations. There may be additional reasons, I'd have to go back to my notes from the original design of this location many years ago. As a person who implements the lower-level parts of snapd, I can really say that doing anything about 1) is extremely hard and security sensitive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873004] Re: lxd interaction blocked until snapd was restarted
The system key is only rewritten if this is required. Normally it is not modified. The question now is: what has changed that made the system key differ? One thing we did observe was /snap/core/$current changing without a complete snapd re-start. Perhaps something was pinging snapd over the API and it failed to complete a restart after a core refresh? Can you check with "snap changes" if there was a corresponding refresh of "core" or "snapd" sometime earlier than the system-key rewrite and in close proximity to the moment LXD started hanging? System key contains interesting details of the system including build IDs of "snapd", some kernel and userspace library features. One other possibility is update of seccomp or apparmor that might have happened. Is "/usr/lib/snapd/snap-seccomp" and "/snap/core/current/usr/lib/snapd /snap-seccomp" linked statically on s390x? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873004 Title: lxd interaction blocked until snapd was restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1873004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873004] Re: lxd interaction blocked until snapd was restarted
Snapd restart will notice and re-generate the system-key. Can you please obtain timestamps of /var/lib/snapd/system-key? Can you correlate the timestamps to the moment you restarted snapd? When system key mismatch is detected "snap run" will do two things, make a API call to snapd (triggering socket activation) and wait for the system key to reconcile (waiting for snapd to write the correct system key to disk). During that time all snap programs will appear to hang on startup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873004 Title: lxd interaction blocked until snapd was restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1873004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756793] Re: Can't run snaps on Ubuntu 18.04
Hey, everyone affected. Could you please post the output of "snap version" as a comment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756793 Title: Can't run snaps on Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1756793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
