[Bug 1902748] Re: ubuntu-seed / ubuntu-boot partition detection could be improved
** Changed in: snapd Assignee: Ian Johnson (anonymouse67) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902748 Title: ubuntu-seed / ubuntu-boot partition detection could be improved To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1902748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965808] [NEW] [SRU] 2.55
Public bug reported: This is a new version of snapd. NOTE: the links below will become available shortly and this note will be removed when they are all available. The changelog is available here https://github.com/snapcore/snapd/blob/2.55/packaging/ubuntu-16.04/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.55 (note that the debian changelog is auto-generated from the merges of the git commits so there is usually no need to look at the raw git commits). The snappy team released a new release that we want SRU into bionic+. The new process described in https://wiki.ubuntu.com/SnapdUpdates was used and we have done integration-tests on the snappy images, autopkgtests on classic and unit tests. GitHub Actions test runs can be found at https://github.com/snapcore/snapd/actions?query=branch%3Arelease%2F2.55 ** Affects: snapd (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/1965808 Title: [SRU] 2.55 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1965808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964636] Re: Incorrect handling of apparmor `bpf` capability
Snapd does not check for the bpf feature through the kernel, it very explicitly only checks the apparmor_parser support, see https://github.com/snapcore/snapd/blob/master/sandbox/apparmor/apparmor.go#L331-L372 for full details of how we check for features -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964636 Title: Incorrect handling of apparmor `bpf` capability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1964636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964636] Re: Incorrect handling of apparmor `bpf` capability
Thanks for the report, I just tried to reproduce this on both updated impish and updated jammy and couldn't reproduce. I notice on impish specifically that my focal container does not get the /var/lib/snapd/apparmor/snap-confine/cap-bpf file which is expected because the apparmor_parser for focal does not know about the bpf capability. What's confusing is how/why your container saw this, because again snapd actually tries to compile a program with apparmor_parser with "capability bpf," in it and only if that succeeds will it generate that snippet to include in snap-confine's policy. So for this to have happened to you, the apparmor_parser that snapd sees inside the focal container must have been able to successfully compile with that snippet. You mentioned on IRC that this was a privileged container, is there anyway that in addition to being a privileged container somehow it had a newer apparmor_parser in the container too? ** Changed in: snapd (Ubuntu) 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/1964636 Title: Incorrect handling of apparmor `bpf` capability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1964636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961898] Re: chromium-browser is refusing to start
Hi, can you paste the full journalctl output with --no-pager? The output you posted above is cut off right where I would like to see what systemd says. ** Changed in: snapd (Ubuntu) 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/1961898 Title: chromium-browser is refusing to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
So indeed your system is still using upstart, in order to use snapd you will need to switch your system over to use systemd instead. Likely one of the upgrade scripts from 10.04 to 16.04 did not transition from upstart to systemd the way a fresh install of 16.04 would default to. ** Changed in: snapd (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961418 Title: snap failed to run with '/usr/bin/snap wait system seed.loaded' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
What is the output of these commands: ps -o cmd fp 1 sudo ls -lah /proc/1/exe cat /proc/cmdline -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961418 Title: snap failed to run with '/usr/bin/snap wait system seed.loaded' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
Is this system using systemd as it's init system? I see that it was originally installed with 10.04.1 which would not have been using systemd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961418 Title: snap failed to run with '/usr/bin/snap wait system seed.loaded' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
Hi, can you share what version of snapd you have installed? apt show snapd snap version Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961418 Title: snap failed to run with '/usr/bin/snap wait system seed.loaded' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955325] Re: Firefox cannot open files in /usr/local/doc
Read-only access to /usr/local/doc seems fine to me, should be pretty straight forward to extend the system-package-doc interface to also allow this directory too, only question would be if it should instead be a new interface like user-package-doc or something, but we can sort that out in a PR I think ** Changed in: snapd Status: New => Confirmed ** Changed in: snapd Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955325 Title: Firefox cannot open files in /usr/local/doc To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1955325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959845] Re: "firefox --version" problem when run via snap
Hi, this is a bug with the snap packaging of Firefox, not with snapd. Please file a bug with Mozilla upstream at https://bugzilla.mozilla.org/home ** 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/1959845 Title: "firefox --version" problem when run via snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1959845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959599] [NEW] gnome-shell freezes upon trying to login
Public bug reported: On Impish 21.10, gnome-shell freezes up when trying to login, specifically after I have typed in my password and hit enter. I have seen this both when logging in after the display shuts itself off after whatever the automatic timeout is, and also after manually locking the screen. This is the stack trace I see from gnome-shell at the time it freezes up: https://pastebin.ubuntu.com/p/9RcnnT32Nf/ The freeze was at 09:58:16 in the log. In this specific instance I just force rebooted the machine, in the other instance this happened to me, I let it sit and see if it would recover but it had not recovered after an hour or two. ** Affects: gnome-shell (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/1959599 Title: gnome-shell freezes upon trying to login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935667] Re: snapd FTBFS when built with libfuse3-dev
Filed a PR with your suggestion: https://github.com/snapcore/snapd/pull/11276 ** Changed in: snapd (Ubuntu) Status: New => In Progress ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Ian Johnson (anonymouse67) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935667 Title: snapd FTBFS when built with libfuse3-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1935667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958022] Re: fish integration broken in focal
This was introduced in https://github.com/snapcore/snapd/pull/11141 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958022 Title: fish integration broken in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1958022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954545] Re: Cannot boot UC20 with new kernel snaps with 384 MB in VM
apport-collect does not work on Ubuntu core ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954545 Title: Cannot boot UC20 with new kernel snaps with 384 MB in VM To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1954545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954545] Re: test ubuntu-20.04-64:tests/nested/manual/minimal-smoke:secboot_disabled is flaky
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - test ubuntu-20.04-64:tests/nested/manual/minimal-smoke:secboot_disabled is flaky + Cannot boot UC20 with new kernel snaps with 384 MB in VM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954545 Title: Cannot boot UC20 with new kernel snaps with 384 MB in VM To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1954545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955289] Re: EGL-using snaps on impish fail with nvidia driver
The fix for that will be included in snapd 2.54.1 which is making its way through the release process ** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Status: New => Fix Committed ** Changed in: snapd Importance: Undecided => Medium ** Changed in: snapd Milestone: None => 2.54 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955289 Title: EGL-using snaps on impish fail with nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1955289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873550] Re: Snappy daemon reaches 1min30s timeout during shutdown process
Hi @bitterhalt, can you try installing the snapd snap via `snap install snapd` and then see if your system is still affected? As Alberto mentioned, we do expect this to be fixed now with the aforementioned commit. ** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Milestone: None => 2.53 ** Changed in: snapd Status: New => Fix Released ** Changed in: snapd Importance: Undecided => High ** Changed in: snapd (Ubuntu) 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/1873550 Title: Snappy daemon reaches 1min30s timeout during shutdown process To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1873550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901586] Re: [snap] CA Certificates from /usr/local/share/ca-certificates are not used
I mentioned this on the snapcraft forum, but /usr/share/local/ca- certificates for a strict snap will come from the read-only, static base snap of the chromium snap. For classic ubuntu/debian systems running new enough snapd, we will actually mount /etc/ssl from the host into the strict snaps' mount namespace, so the correct thing to suggest folks to do is to put custom certificates into /etc/ssl instead of /usr/local/share/ca-certificates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901586 Title: [snap] CA Certificates from /usr/local/share/ca-certificates are not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1901586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948995] Re: Ubuntu Server should have refresh.retain=3 set by default
** Summary changed: - Allow reverting to older revisions of a snap + Ubuntu Server should have refresh.retain=3 set by default ** Changed in: snapd (Ubuntu) Status: New => Confirmed ** Changed in: snapd (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948995 Title: Ubuntu Server should have refresh.retain=3 set by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1948995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712808] Re: udev interface fails in privileged containers
@Marco, can you reproduce that behavior without creating the directory? I.e. just start a new instance and then run `snap install hello` twice and see if it works? AFAIK, that has always been the workaround of choice is just running it twice initially for some reason... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712808 Title: udev interface fails in privileged containers To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1712808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953171] [NEW] package linux-image-5.13.0-1011-raspi 5.13.0-1011.13 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: While upgrading my Raspberry Pi 3 running 21.04 to 21.10, the upgrade failed ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1011-raspi 5.13.0-1011.13 ProcVersionSignature: Ubuntu 5.11.0-1023.25-raspi 5.11.22 Uname: Linux 5.11.0-1023-raspi aarch64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 CasperMD5CheckResult: unknown Date: Fri Dec 3 03:19:32 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-1011-raspi 5.13.0-1011.13 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to impish on 2021-12-03 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 impish need-duplicate-check uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953171 Title: package linux-image-5.13.0-1011-raspi 5.13.0-1011.13 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1953171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952084] Re: snapd.seeded.service never finishes on s390x when privileged or nested
So snapd doesn't support running inside privileged containers, so any setup requiring snapd to do things in privileged containers is an unsupported setup. We have historically supported nesting however recently numerous things changed there, 1) there was a lxd regression which broke nested containers and 2) there were some changes to udev which we had to adapt to with https://github.com/snapcore/snapd/pull/11058. That PR will be included in the next 2.53.3 release of snapd, but we have not yet prepared that as we need to fix a few other more critical bugs before we can start the 2.53.3 release. So it would be great if someone could test a failing system with an updated image that includes snapd snap from edge which does contain those fixes. ** Changed in: snapd (Ubuntu) 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/1952084 Title: snapd.seeded.service never finishes on s390x when privileged or nested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1952084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949115] Re: default install of focal allows privilege escalation via lxd group
I filed it as a private bug because I wasn't sure how widely known it was that this was exploitable, but sure if the security team thinks this is a well-known issue that is good enough for me ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949115 Title: default install of focal allows privilege escalation via lxd group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/user-setup/+bug/1949115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
@slyon could you make available the core18 snap you built with this systemd ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948995] Re: Allow reverting to older revisions of a snap
You can set the number of revisions to keep with `snap set system refresh.retain=`. The choice for Server is probably unfortunately a victim of inheriting the default choice for Ubuntu Desktop, which is 2. We originally had 3 for Desktop too (which is also still the default on Ubuntu Core), but that was deemed to be too storage intensive for most users so for "non-Ubuntu Core" we changed it to 2 instead, and it seems that Server has gotten bundled into the definition of "non-Ubuntu Core". I think there's a strong case to be made for having a different default on Server vs Desktop, so if you want to open a new bug about changing that (or we could re-use this one I suppose), I think that's a reasonable thing to request be changed. ** Changed in: snapd (Ubuntu) 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/1948995 Title: Allow reverting to older revisions of a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1948995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948995] Re: Allow reverting to older revisions of a snap
Hi @axino, unfortunately I'm not aware of all the details of your system, but if you do not have the desired snap revision available on your system, then I can't advise on how you could get access to a revision which works for your system. You could try reaching out to the publisher to see if they can re-publish the working revision to the stable channel (since it seems like a regression), or maybe they could put the old revision onto a branch for you to temporarily switch to. Finally, you could try rebuilding the snap yourself with the right assets to effectively revert, and then install this revision locally with --dangerous flag. ** Changed in: snapd (Ubuntu) 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/1948995 Title: Allow reverting to older revisions of a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1948995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948995] Re: Allow reverting to older revisions of a snap
It is by design that you cannot revert to a snap that you do not already have installed on a system. You can try using `snap list ruby --all` to get all currently installed revisions on your system (but note that only one revision can be "active" at a time), the revisions listed by this command are all the revisions that you can revert to. You can increase the number of revisions that are kept around on a system to ensure that you are more likely to have the previous revision available by setting the refresh.retain system setting. I believe on Desktop/Server this setting defaults to 2, but on Ubuntu Core for example this setting defaults to 3. ** 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/1948995 Title: Allow reverting to older revisions of a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1948995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947203] Re: Snap applications cannot start
Can you provide the output of running the following command: journalctl --no-pager --no-hostname -b0 | grep audit Thanks ** Changed in: snapd (Ubuntu) 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/1947203 Title: Snap applications cannot start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1947203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
** Changed in: snapd (Ubuntu) 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/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943077] Re: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s
Dan, note that although we set the SNAP_REEXEC environment variable in that integration test, that environment variable is actually not obeyed when it comes to the mksquashfs command which is called here: https://github.com/snapcore/snapd/blob/dfba7de59a41bc22786d87f53b20deea14240713/snap/squashfs/squashfs.go#L524 and the function snapdtool.CommandFromSystemSnap does not observe the SNAP_REEXEC environment variable at all, instead just checking if the snapd or core snaps exist at all, and using the mksquashfs from those snaps instead of what's on the host on $PATH (though we do fallback and if there is no mksquashfs found in the core or snapd snaps (somehow???), then we use $PATH). As I mentioned on IRC, we could potentially someday add a workaround where if mksquashfs from the system snap specifically segfaults then we will fall back to using the host's mksquashfs, but we have chosen for now not to work on that patch. Hope this helps explain things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943077 Title: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1943077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
Okay, so after too much time trying to test this, I confirmed that this change will fix it for both powerpc and for s390x: https://github.com/snapcore/snapd/pull/10898 That PR should be merged to snapd master, then cherry-picked to release/2.53 branch, then we can upload a 2.53.1 deb to impish-proposed and try to get that released to impish proper which will fix the issue. If we can do it in time for the release even better. ** Changed in: snapd (Ubuntu) Status: Fix Released => In Progress ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Ian Johnson (anonymouse67) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Also I'm not sure I agree with jdstrand's apparmor profile which includes: /run/snapd.socket rw, which I don't think we want to grant to any PDF file opened with evince? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
John, the difference between those two that I can see is that now the image was creating with cgroupsv2 present when preseeding (which was the expected change), but the runtime image does not use cgroupsv2 and thus things need to be regenerated. This is sort of expected since the runtime kernel is focal, which is not configured by default to use cgroupsv2. In general, I'm not sure we can solve this problem if we expect to produce one image that when launched everywhere will always be preseeded, since as shown by this output we would need to somehow simultaneously both the runtime system using cgroupsv1 and the runtime system using cgroupsv2. The change you landed is correct in that it will ensure a system using cgroupsv2 (i.e. impish server) will get the best speed, but a system using cgroupsv1 (i.e. focal server) will not get the best possible speed. I'm not sure which case CPC wants to optimize for. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943077] Re: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s
As seb128 found, the issue is also affecting the debian package of snapd since when we call mksquashfs, we actually have code which specifically calls mksquashfs from the "system" snap which is either the snapd snap or the core snap, this is presumably to ensure that a consistent mksquashfs is used always and to avoid snaps from being packed with too old or new mksquashfs's. So the net effect is that the fix for this that was landed into the snapd snap will also probably need to be added to the core snap for completeness, and also means that the only way to avoid snap pack from failing is to have a snapd snap with the fix which is only available on the edge channel currently. So long story short, if you are affected by this today, a short-term workaround is to use the edge channel of the snapd snap by running snap refresh snapd --edge We have already included the fix into the snapd snap that is built on edge and it will be included in the release branch for 2.52, meaning that the next bugfix release on 2.52 will have the fix, we do plan on doing a 2.52.1 release in short order after 2.52 is complete, but it may be a few weeks from now before that is on stable. ** Changed in: snapd Milestone: None => 2.52 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943077 Title: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1943077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945369] Re: memory cgroup disabled on Ubuntu Core 18
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945369 Title: memory cgroup disabled on Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945369] Re: memory cgroup disabled on Ubuntu Core 18
apport-collect is not available on ubuntu core ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945369 Title: memory cgroup disabled on Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945369] Re: memory cgroup disabled on Ubuntu Core 18
Also an interesting datapoint is that on Ubuntu 21.04 Server on my pi, the memory cgroup is enabled: ubuntu@ubuntu:~$ cat /proc/cgroups #subsys_namehierarchy num_cgroups enabled cpuset 7 1 1 cpu 2 125 1 cpuacct 2 125 1 blkio 11 125 1 memory 5 140 1 devices 12 126 1 freezer 8 4 1 net_cls 9 1 1 perf_event 6 1 1 net_prio9 1 1 hugetlb 3 1 1 pids10 132 1 rdma4 1 1 ubuntu@ubuntu:~$ uname -a Linux ubuntu 5.11.0-1017-raspi #18-Ubuntu SMP PREEMPT Mon Aug 23 07:34:31 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945369 Title: memory cgroup disabled on Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945369] [NEW] memory cgroup disabled on Ubuntu Core 18
Public bug reported: On Ubuntu Core 18, the memory cgroup is disabled, it seems that it needs to be manually enabled. I was able to enable it by adding `cgroup_enable=memory cgroup_memory=1` to the kernel command line, but on Ubuntu I think the memory cgroup should be enabled by default shouldn't it? $ cat /proc/cgroups #subsys_namehierarchy num_cgroups enabled cpuset 2 1 1 cpu 4 100 1 cpuacct 4 100 1 blkio 5 100 1 memory 0 109 0 devices 6 100 1 freezer 9 4 1 net_cls 3 1 1 perf_event 10 1 1 net_prio3 1 1 pids8 107 1 rdma7 1 1 I see this with Linux localhost 5.4.0-1043-raspi #47~18.04.1-Ubuntu SMP PREEMPT Mon Aug 23 14:39:46 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux on Ubuntu Core 18, but folks have informed me that the same is true on Ubuntu Core 20 as well. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: On Ubuntu Core 18, the memory cgroup is disabled, it seems that it needs to be manually enabled. I was able to enable it by adding `cgroup_enable=memory cgroup_memory=1` to the kernel command line, but on Ubuntu I think the memory cgroup should be enabled by default shouldn't it? $ cat /proc/cgroups #subsys_name hierarchy num_cgroups enabled cpuset2 1 1 cpu 4 100 1 cpuacct 4 100 1 blkio 5 100 1 memory0 109 0 devices 6 100 1 freezer 9 4 1 net_cls 3 1 1 perf_event10 1 1 net_prio 3 1 1 pids 8 107 1 rdma 7 1 1 + + I see this with + + Linux localhost 5.4.0-1043-raspi #47~18.04.1-Ubuntu SMP PREEMPT Mon Aug + 23 14:39:46 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux + + on Ubuntu Core 18, but folks have informed me that the same is true on + Ubuntu Core 20 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/1945369 Title: memory cgroup disabled on Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945242] Re: Failed to refresh to pi-kernel rev 343 on uc18
apport-collect doesn't work on Ubuntu Core ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945242 Title: Failed to refresh to pi-kernel rev 343 on uc18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
@mwhudson I'm still not convinced that the udev noise is not the problem, but another data point I just went ahead and got to prove this is that when trying to seed another snap which uses interfaces and has an install hook and is available on arm64, the docker snap, it fails the "same" way with udev things in the setup-profiles task: https://pastebin.ubuntu.com/p/ZGQSxpFHm4/ but in this state setup the install hook is never even attempted to be run. I also am attaching the state.json that results: https://pastebin.ubuntu.com/p/j5MbT8XjVb/ You can see that all the udev output is from the setup-profiles task for snapd from the state.json 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/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+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
** Changed in: snapd Status: Incomplete => Confirmed ** Changed in: snapd Importance: Undecided => High ** No longer affects: snapd (Ubuntu) -- 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 1944004] Re: snapd.seeded.service never finishes on non-amd64
So some thoughts: 1. The root failure of snapd failing to finish seeding is that it is trying to run `udevadm trigger --subsystem-nomatch=input` which ends up dying on every write like so: openat(AT_FDCWD, "/sys/devices/virtual/workqueue/writeback/uevent", O_WRONLY|O_NOCTTY|O_NOFOLLOW|O_CLOEXEC) = -1 EACCES (Permission denied) writeback: Failed to write 'change' to '/sys/devices/virtual/workqueue/writeback/uevent': Permission denied which is peculiar to me because that command fails on both the 03 and the 04 image, but only causes snapd to fail to seed on the 04 image for some reason. This is triply peculiar to me because that same command run in a 21.04 container (amd64 and arm64) works fine without issues. Quadruply peculiar is that the same command in a 21.10 daily container on amd64 actually also fails, but again does not cause snapd to fail seeding on the amd64 image. My guess is that maybe snapd doesn't think it needs to run this command on the other 21.10 images and so it doesn't die on this command, but for some reason on the new arm64 images it thinks it has to run this command. Quintuply peculiar is the failure around EACCES. 2. If you diff the manifest between the image you see this change: -libc-bin2.33-0ubuntu9 -libc6:arm642.33-0ubuntu9 +libc-bin2.34-0ubuntu2 +libc6:arm642.34-0ubuntu2 I have no reason to believe that libc6 is the root of this problem, other than the fact that it has been at the root of many other problems that present themselves in weird ways especially when containers are involved. 3. The specific task that snapd is running when the failure happens seems to be either setup-profiles for the snapd snap OR running the install hook for lxd, although I don't think it is related at all to the specific install hook for the lxd snap since that doesn't seem to do anything real and it fails in different ways, sometimes it's a segmentation fault and sometimes it just says the hook exited 1. 4. If I modify the seed.yaml to not seed the lxd snap and then obliterate state.json and restart snapd, it now proceeds to be able to seed properly, so I think there is something about the lxd snap + the state of the system which implies to snapd that it needs to setup the udev backend which runs the failing command, most likely the fact that the lxd snap uses interfaces (even though it's interfaces are rather pointless in that they don't really have any policy). Indeed I can also successfully seed a snap like jq in the seed.yaml which has no interfaces used and it doesn't trigger snapd to run udev things. So part of the story is definitely that snapd thinks it needs to generate udev backend things for the lxd snap while seeding and that causes it to run that udevadm command which fails. Why this doesn't affect amd64 though is unclear to me. 5. The two rootfs' provided above are both preseeded with the same set of snaps with the same assertions and same seed.yaml file, so it doesn't appear to be a snapd regression or some trigger from the snaps themselves. Finally, I also note that this is also reproducible on a Raspberry Pi too if anyone wants to debug on their own, just run on a Pi: lxc launch ubuntu-daily:21.10 impish-testing and then you can see the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+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
@fthx can you show the output of `snap changes` and `snap list gnome-3-38-2004 --all` ? What I suspect made your firefox crash is that the last revision of gnome-3-38-2004 that firefox was launched with was garbage collected out of existence -- 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 1944447] Re: refresh-app-awareness=true does not seem to concern dependencies
Hmm, actually though I cannot reproduce the specific crash/error on my machine, I was running the firefox snap and I tried both refreshing gnome-3-38-2004 from revision 61 -> 76 and the inverse of 76 -> 61, can you describe how the crash happened? Did you do some specific thing in firefox when the refresh happened that made it crash? I was just opening a new tab and browsing to a random news site to try and reproduce the crash. To be clear, I can still see where some snaps may have issues with their dependencies being refreshed, so we will evaluate this for refresh-app- awareness, just that if we can't reproduce it on one of the "lighthouse" snaps like firefox it will be a lower priority for us to address. -- 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 1944447] Re: refresh-app-awareness=true does not seem to concern dependencies
Thanks for that information, for now I think that it is expected that refreshes to dependency snaps are not blocked by active snaps using those dependencies, but that is something I think we should explore doing automatically. We are actively working on hooks which snaps can implement manually which would allow controlling this behavior and being notified of when a dependency is going to be refreshed and the running snap can decide to delay that refresh, but that work is not quite done yet, and would require work from individual snap authors, while the automatic feature I mentioned above would not require that manual work. -- 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 1944447] Re: refresh-app-awareness=true does not seem to concern dependencies
Hi, can you provide the output of snap version snap list Thanks ** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Status: New => Incomplete ** Changed in: snapd (Ubuntu) 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/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 1932579] Re: snap pt_BR locale shows warning every time
Ah Miguel, thanks for realizing my error, I should have probably just said something like sudo snap install snapd --edge; sudo snap refresh snapd --edge which will ensure that it's always installed and gets refreshed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932579 Title: snap pt_BR locale shows warning every time To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1932579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932579] Re: snap pt_BR locale shows warning every time
@iogui, hmm it could be that our fix isn't working, can you show the output of these commands: snap version snap list -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932579 Title: snap pt_BR locale shows warning every time To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1932579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932579] Re: snap pt_BR locale shows warning every time
@iogui could you try again? snapd on the edge channel may not have finished building by the time you tried, but I see that there was an update pushed out this morning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932579 Title: snap pt_BR locale shows warning every time To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1932579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
To be clear you see this behavior with normal containers and not with nested containers? Snapd doesn't support nested containers unfortunately -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943853] Re: Recent update DELETED SNAP PROGRAMS
Can you show the output of `snap connections authy`? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943853 Title: Recent update DELETED SNAP PROGRAMS To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1943853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932579] Re: snap pt_BR locale shows warning every time
The message should no longer be shown anymore in snapd as the PR referenced by Maciej has been merged and should be available on the edge channel of snapd in the few hours. Please give it a try if you like with: ``` snap install snapd --edge || snap refresh snapd --edge # test the snap command to make sure the message no longer appears snap refresh snapd --stable # to go back to tracking stable, as edge sometimes can have unstable changes on it ``` Thanks, Ian ** Changed in: snapd (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: snapd (Ubuntu) Importance: Undecided => Medium ** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Milestone: None => 2.53 ** Changed in: snapd Status: New => Fix Committed ** 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/1932579 Title: snap pt_BR locale shows warning every time To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1932579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943853] Re: Recent update DELETED SNAP PROGRAMS
Can you try rebooting your system to see if the snaps are remounted? it seems like some of the snaps are not properly mounted and the easiest way usually to fix that is to just reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943853 Title: Recent update DELETED SNAP PROGRAMS To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1943853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943853] Re: Recent update DELETED SNAP PROGRAMS
For a snap that does not work can you run `snap run authy` in a terminal window and show us the output? ** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Status: New => Incomplete ** Changed in: snapd (Ubuntu) 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/1943853 Title: Recent update DELETED SNAP PROGRAMS To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1943853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942646] Re: SRU 2.52
** Description changed: - [ placeholder - release in progress ] - This is a new version of snapd. The changelog is available here https://github.com/snapcore/snapd/blob/2.52/packaging/ubuntu-16.04/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.52 (note that the debian changelog is auto-generated from the merges of the git commits so there is usually no need to look at the raw git commits). The snappy team released a new release that we want SRU into xenial. The new process described in https://wiki.ubuntu.com/SnapdUpdates was used and we have done integration-tests on the snappy images, autopkgtests on classic and unit tests. + + GitHub Actions test runs can be found at + https://github.com/snapcore/snapd/actions?query=branch%3Arelease%2F2.52 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942646 Title: SRU 2.52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1942646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942646] [NEW] SRU 2.52
Public bug reported: [ placeholder - release in progress ] This is a new version of snapd. The changelog is available here https://github.com/snapcore/snapd/blob/2.52/packaging/ubuntu-16.04/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.52 (note that the debian changelog is auto-generated from the merges of the git commits so there is usually no need to look at the raw git commits). The snappy team released a new release that we want SRU into xenial. The new process described in https://wiki.ubuntu.com/SnapdUpdates was used and we have done integration-tests on the snappy images, autopkgtests on classic and unit tests. ** Affects: snapd (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/1942646 Title: SRU 2.52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1942646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773515] Re: apparmor fails after removal of snapd
** Changed in: snapd Assignee: Zygmunt Krynicki (zyga) => (unassigned) ** Changed in: snapd Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773515 Title: apparmor fails after removal of snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1773515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927484] Re: Ubuntu 21.04 desktop ISO burned to DVD takes a very long time to start
Can anyone share full logs from such a boot specifically the output of `journalctl --no-pager` would be really helpful in diagnosing this problem. ** Changed in: snapd (Ubuntu) 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/1927484 Title: Ubuntu 21.04 desktop ISO burned to DVD takes a very long time to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1927484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757073] Re: Snap stopped working on Ubuntu 18.04
Is this still reproducible with snapd 2.51? ** Changed in: snapd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757073 Title: Snap stopped working on Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1757073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940467] Re: [snap] Nitrokey FIDO2 does not work with Chromium snap
** Changed in: snapd Status: Confirmed => Fix Committed ** Changed in: snapd Milestone: None => 2.53 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940467 Title: [snap] Nitrokey FIDO2 does not work with Chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1940467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919268] Re: [snap] HyperFIDO Pro U2F security key doesn't work with chromium
** Changed in: snapd Status: In Progress => Fix Released ** Changed in: snapd Milestone: None => 2.51 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919268 Title: [snap] HyperFIDO Pro U2F security key doesn't work with chromium To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1919268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940467] Re: [snap] Nitrokey FIDO2 does not work with Chromium snap
This is because snapd's u2f-devices interface lacks this rule. See my response here: https://forum.snapcraft.io/t/nitrokey-fido2-does-not- work-with-chromium-snap/26098/2 ** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Status: New => 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/1940467 Title: [snap] Nitrokey FIDO2 does not work with Chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1940467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914918] Re: The snap being updated in the background causes both old and new tabs to die to SIGTRAP
** Changed in: snapd (Ubuntu) Assignee: Samuele Pedroni (pedronis) => Ian Johnson (anonymouse67) ** Changed in: snapd (Ubuntu) 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/1914918 Title: The snap being updated in the background causes both old and new tabs to die to SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1914918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934147] Re: systemd leaks abandoned session scopes
This systemd bug can be problematic for snapd as well, leading to the sort of situation in https://bugs.launchpad.net/snapd/+bug/1928806, where running snap commands frequently leads to many many many leftover scopes like this ** Also affects: snapd Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934147 Title: systemd leaks abandoned session scopes To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1934147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890848] Re: 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
Also to be clear, from jjohansen's comment to me last week, all of the necessary patches are available in the 5.4 focal kernel, so kernels for UC20 from canonical snaps should contain this fix on the 20 track. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890848 Title: 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935667] Re: Please switch to fuse3
Thanks for that ** Changed in: snapd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935667 Title: Please switch to fuse3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1935667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935667] Re: Please switch to fuse3
Can you provide a full build failure log and information on what you changed when you tried to build snapd? ** Changed in: snapd (Ubuntu) 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/1935667 Title: Please switch to fuse3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1935667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920107] Re: Failed messages of sd-umount shown with reboot/shutdown
I continue to see these messages on all UC20 VM's I use, including the most recently released stable image on cdimage when booted in a VM ** Changed in: snapd Status: Expired => 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/1920107 Title: Failed messages of sd-umount shown with reboot/shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1920107/+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
** Changed in: snapd Milestone: None => 2.51 ** 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/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 1621102] Re: /home symlink, snaps don't work
This has been covered extensively elsewhere, for example on the forum, etc. but we don't have immediate plans to support symlinked homes, and bind mounts are an appropriate work-around: https://snapcraft.io/docs /home-outside-home. I for some reason have lost my permission to change the snapd debian package priority, but it should also be "Low", like the snapd project here I just added. ** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Status: New => Triaged ** Changed in: snapd Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621102 Title: /home symlink, snaps don't work To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1621102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933093] Re: Drop old UC20 boot args
> I am not too sure if the flash-kernel uboot script actually is compatible with the snapd's cmdline full / extra functionality. It is not yet compatible unfortunately, and it's not on our immediate roadmap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933093 Title: Drop old UC20 boot args To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1933093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931380] Re: Snap-store fails to launch - libgtk-3.so.0: undefined symbol: atk_plug_set_child
As per Ken's comment on the associated forum post, this is actually now on stable, being phased out. You should automatically get the stable refresh within 24 hours, if you don't see it automatically, please wait 24 hours and then try again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931380 Title: Snap-store fails to launch - libgtk-3.so.0: undefined symbol: atk_plug_set_child To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1931380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931380] Re: Snap-store fails to launch - libgtk-3.so.0: undefined symbol: atk_plug_set_child
A fix for this is in the beta channel AIUI, you can refresh to try out the fix with: ``` snap refresh snap-store --beta --ignore-running ``` You can omit the --ignore-running if you do not have refresh app awareness enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931380 Title: Snap-store fails to launch - libgtk-3.so.0: undefined symbol: atk_plug_set_child To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1931380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931380] Re: Snap-store fails to launch - libgtk-3.so.0: undefined symbol: atk_plug_set_child
This was discussed on Mattermost, and the cause of this is not related to snapd, it is an issue with the snap-store snap. ** Changed in: snapd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931380 Title: Snap-store fails to launch - libgtk-3.so.0: undefined symbol: atk_plug_set_child To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1931380/+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
When you have no snaps installed, snapd will exit itself automatically, but as long as there are snaps installed, snapd needs to be installed in order to do a few things: - setup and manage the confinement of snaps - handle automatic updates to snaps and snapd - respond to any requests made with the `snap` command I'm closing this since redesigning snapd to not be a daemon is not within the scope of the project unfortunately. ** Changed in: snapd (Ubuntu) Status: New => Opinion -- 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 1929842] Re: [SRU] 2.51
** Description changed: This is a new version of snapd. The changelog is available here https://github.com/snapcore/snapd/blob/2.51/packaging/ubuntu-16.04/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.51 (note that the debian changelog is auto-generated from the merges of the git commits so there is usually no need to look at the raw git commits). The snappy team released a new release that we want SRU into xenial. The new process described in https://wiki.ubuntu.com/SnapdUpdates was used and we have done integration-tests on the snappy images, autopkgtests on classic and unit tests. + + GitHub Actions test runs can be found at + https://github.com/snapcore/snapd/actions?query=branch%3Arelease%2F2.51 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929842 Title: [SRU] 2.51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1929842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929842] Re: [SRU] 2.51
** Description changed: - [ placeholder - release in progress ] - This is a new version of snapd. The changelog is available here https://github.com/snapcore/snapd/blob/2.51/packaging/ubuntu-16.04/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.51 (note that the debian changelog is auto-generated from the merges of the git commits so there is usually no need to look at the raw git commits). The snappy team released a new release that we want SRU into xenial. The new process described in https://wiki.ubuntu.com/SnapdUpdates was used and we have done integration-tests on the snappy images, autopkgtests on classic and unit tests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929842 Title: [SRU] 2.51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1929842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929842] [NEW] [SRU] 2.51
Public bug reported: [ placeholder - release in progress ] This is a new version of snapd. The changelog is available here https://github.com/snapcore/snapd/blob/2.51/packaging/ubuntu-16.04/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.51 (note that the debian changelog is auto-generated from the merges of the git commits so there is usually no need to look at the raw git commits). The snappy team released a new release that we want SRU into xenial. The new process described in https://wiki.ubuntu.com/SnapdUpdates was used and we have done integration-tests on the snappy images, autopkgtests on classic and unit tests. ** Affects: snapd (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/1929842 Title: [SRU] 2.51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1929842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906970] Re: dpkg hook hostname error
This happened to me when upgrading from Groovy to Hirsute just now, with the same symptoms as above - I had `search .` in resolv.conf, but nothing creating that entry in /etc/netplan or in /etc/systemd/resolved.conf. I fixed the broken package by fixing the erroneous entry /etc/postfix/main.cf (removing the ".." at the end of the hostname) and then running: sudo dpkg-reconfigure --force postfix sudo systemctl reload postfix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906970 Title: dpkg hook hostname error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1906970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926355] Re: Snap applications segfault with new core20 (rev: 1015+)
Unfortunately I don't know how to easily remove glibc from the snaps in a way that would confirm that they work, I don't have time to manually build all of these snaps that are broken, I tried the basic thing of unpacking the snap and `rm -rf ./lib/x86_64-linux-gnu/libc-2.31.so ./lib/x86_64-linux-gnu/libc.so.6` and then repacking and installing these snaps, but then the still segfault and fail with: $ snap run htop *** stack smashing detected ***: terminated Aborted (core dumped) Which I don't know if that's because I didn't fully remove traces of glibc from the snap or if it's because beta version of core20 (snap revision 1015) is still broken. I did try building the matterhorn snap since I found the source for it at https://github.com/popey/matterhorn-snap.git, but that doesn't seem to build at all. Perhaps Sergio can help confirm if these snaps work if rebuilt without libc6 getting staged into the snap? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926355 Title: Snap applications segfault with new core20 (rev: 1015+) To manage notifications about this bug go to: https://bugs.launchpad.net/snap-core20/+bug/1926355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926355] Re: Snap applications segfault with new core20 (rev: 1015+)
Sure, I was not aware test-snapd-rsync-core20 was shipping glibc, that is indeed not a good idea. I went looking on my system for other snaps which experienced the crash, and it seems that every snap that ships glibc in it crashes with the beta channel of core20, but snaps that (properly) do not ship libc6 in them do not crash. For example these other well known snaps ship glibc in them: * matterhorn * okular * htop and some others that are perhaps less well known. So I think it is unfortunately a bit common to do this even though it is not advisable. Sergio, do you know why these snaps would have libc6 staged in them? Matterhorn for example does not declare libc6 as a stage-package, yet it is listed as a primed-stage-packages in the manifest.yaml: ```snapcraft.yaml stage-packages: - libatomic1 - libsecret-tools - libnotify-bin - xclip ``` ```manifest.yaml primed-stage-packages: - libc6=2.31-0ubuntu9.2 ``` ** Also affects: snapcraft 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/1926355 Title: Snap applications segfault with new core20 (rev: 1015+) To manage notifications about this bug go to: https://bugs.launchpad.net/snap-core20/+bug/1926355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926705] Re: insInconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 541: elf_machine_rela_relative: Assertion `ELFW(R_TYPE) (reloc->r_info) == R_X86_64_RELATIVE' failed!
To be clear, the snapd and core snaps for 2.49.2 were not built with the recently reverted libc6, that was only for focal which affected the core20 snap, see https://bugs.launchpad.net/snap-core20/+bug/1926355 for details on that bug. This is a separate issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926705 Title: insInconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 541: elf_machine_rela_relative: Assertion `ELFW(R_TYPE) (reloc->r_info) == R_X86_64_RELATIVE' failed! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1926705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926355] Re: Snap applications segfault with new core20 (rev: 1015+)
With the test snap that uses core20 as it's base, test-snapd-rsync- core20 (installable on the edge channel), I see it segfaulting when running the snap on both a UC20 system with the core20 snap as a base snap, as well as on my groovy desktop: https://pastebin.ubuntu.com/p/qbq86DYw5Q/ You can reproduce this with: ``` snap install core20 --beta || snap refresh core20 --beta snap install test-snapd-rsync-core20 --edge snap run --experimental-gdbserver test-snapd-rsync-core20.rsync ... you will see the gdb command to use to connect to the gdbserver running inside the snap's mount namespace gdb -ex="target remote :33021" -ex=continue -ex="signal SIGCONT" # in another window ``` My gdb output seems to imply the segfault is coming from 0x56287d57a2d4 in time@plt ? I haven't been able to load debug symbols for this gdb version into the snap mount namespace yet so I don't have more info, but presumably you could copy debug symbols into the snap's dir somewhere like $HOME/snap/test-snapd-rsync- core20/current/debug.sym and then load it from the gdb shell. For reference, I've also attached the output of strace too in case that's more useful: https://pastebin.ubuntu.com/p/rpqKrnBHrg/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926355 Title: Snap applications segfault with new core20 (rev: 1015+) To manage notifications about this bug go to: https://bugs.launchpad.net/snap-core20/+bug/1926355/+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
This will be fixed in 2.50 ** Changed in: snapd Status: New => Fix Committed ** Changed in: snapd (Ubuntu) Status: New => 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/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 1868894] Re: [uc18] docker overlayfs* seems broken
** 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/1868894 Title: [uc18] docker overlayfs* seems broken To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1868894/+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
** Changed in: snapd Status: Fix Released => Confirmed -- 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 1849753] Re: AppArmor profile prohibits classic snap from inheriting file descriptors
** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Ian Johnson (anonymouse67) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849753 Title: AppArmor profile prohibits classic snap from inheriting file descriptors To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1849753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849753] Re: AppArmor profile prohibits classic snap from inheriting file descriptors
There is a RFC PR from Jamie up here: https://github.com/snapcore/snapd/pull/10029. We (snapd team) will try to pick this up and get it merged when we have some time (hopefully soon). ** Changed in: snapd (Ubuntu) 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/1849753 Title: AppArmor profile prohibits classic snap from inheriting file descriptors To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1849753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920754] Re: FTBFS and autopkgtest failure in hirsute
We have a fix in a PR: https://github.com/snapcore/snapd/pull/10044 ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Ian Johnson (anonymouse67) ** Changed in: snapd (Ubuntu) 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/1920754 Title: FTBFS and autopkgtest failure in hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1920754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905493] Re: cloud-init status --wait hangs indefinitely in a nested lxd container
FWIW I know what the snapd issue is, the issue is that snapd does not and will not work in a nested LXD container, we need to add code to make snapd.seeded.service die/exit gracefully in this situation. ** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Status: New => Confirmed ** Changed in: snapd Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905493 Title: cloud-init status --wait hangs indefinitely in a nested lxd container To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1905493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903864] Re: qemu-system-x86_64: -device tpm-tis, tpmdev=tpm-tpm0, id=tpm0: Property 'tpm-tis.tpmdev' can't find value 'tpm-tpm0'
Hey Christian, thanks for taking a look at this, indeed this is somehow confinement related and I can make it work by removing the apparmor profile for the swtpm snap. I guess I assumed that this bug was related to that since it had the same exact error message and I definitely remembered doing this setup before only like a month or two ago on Groovy and the swtpm-mvo snap has not been updated in ages so I assumed that updating qemu was to blame. What I actually find now is that it seems actually to be due to https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1849753, since what changed for me to trigger my bug around swtpm and qemu is that I started using VS Code as a snap, and so when I run my qemu commands they are effectively being run from inside a classic snap, and swtpm is a strict snap so it cannot inherit all the FD's that VS code has open. If I run from a normal terminal shell and not from within the VS Code integrated terminal the setup works the same again. So all that is to say that indeed there is no regression here, thanks for the insight that this is confinement related, I should be able to easily work around this for my purposes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903864 Title: qemu-system-x86_64: -device tpm-tis,tpmdev=tpm-tpm0,id=tpm0: Property 'tpm-tis.tpmdev' can't find value 'tpm-tpm0' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1903864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly
** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474126/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912246 Title: [nvidia] gnome-shell freezes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1912246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474125/+files/lspci.txt ** Attachment removed: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474124/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912246 Title: [nvidia] gnome-shell freezes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1912246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly
Here's lspci -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912246 Title: [nvidia] gnome-shell freezes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1912246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly
Here's lspci -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912246 Title: [nvidia] gnome-shell freezes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1912246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly
Okay, so this time when it happened at Sun Mar 7 02:44 AM UTC 2021, here are the logs. I did not find any crash files in /var/crash, and there were no results for my whoopsie-id either. The journalctl output is attached ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474124/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912246 Title: [nvidia] gnome-shell freezes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1912246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903864] Re: qemu-system-x86_64: -device tpm-tis, tpmdev=tpm-tpm0, id=tpm0: Property 'tpm-tis.tpmdev' can't find value 'tpm-tpm0'
So I tested the swtpm-mvo snap in a hirsute live image from current/ on cdimage, using kernel 5.8.0-36-generic (which is only slightly older than my current groovy kernel at 5.8.0-44-generic), and qemu 1:5.2+dfsg- 3ubuntu1, and it worked for me to use the swtpm from the swtpm-mvo snap. So I think that something is related to this is fixed in hirsute which has not been fixed/backported to groovy for our use case of booting UC20 VM's. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903864 Title: qemu-system-x86_64: -device tpm-tis,tpmdev=tpm-tpm0,id=tpm0: Property 'tpm-tis.tpmdev' can't find value 'tpm-tpm0' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1903864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903864] Re: qemu-system-x86_64: -device tpm-tis, tpmdev=tpm-tpm0, id=tpm0: Property 'tpm-tis.tpmdev' can't find value 'tpm-tpm0'
Hi folks, I think the new version of the qemu package in Groovy at least has regressed an important aspect for us in testing Ubuntu Core 20 VM's with swtpm. We use the swtpm-mvo snap in conjunction with qemu and OVMF to run Ubuntu Core 20 VM's, and after upgrading to qemu 1:5.0-5ubuntu9.6, I can no longer run UC20 VM's using the swtpm-mvo snap we use on the snapd team. I see this: ``` $ kvm \ -smp 8 \ -m 8192 \ -machine q35 \ -cpu host \ -global ICH9-LPC.disable_s3=1 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=/usr/share/OVMF/OVMF_CODE.secboot.fd,if=pflash,format=raw,unit=0,readonly=on \ -drive file="$SCRIPT_DIR/OVMF_VARS.ms.fd",if=pflash,format=raw,unit=1 \ -chardev socket,id=chrtpm,path="/var/snap/swtpm-mvo/current/swtpm-sock" -tpmdev emulator,id=tpm0,chardev=chrtpm -device tpm-tis,tpmdev=tpm0 \ -drive file=uc20.img,if=none,format=raw,id=disk1 -device virtio-blk-pci,drive=disk1,bootindex=1 \ -serial mon:stdio qemu-system-x86_64: -tpmdev emulator,id=tpm0,chardev=chrtpm: tpm-emulator: Failed to send CMD_SET_DATAFD: Success qemu-system-x86_64: -device tpm-tis,tpmdev=tpm0: Property 'tpm-tis.tpmdev' can't find value 'tpm0' $ ``` whereas before this worked and we could use the TPM. You can reproduce this by installing the swtpm-mvo snap: ``` $ snap install swtpm-mvo --edge ``` and then using the ubuntu core 20 released image from cdimage: http://cdimage.ubuntu.com/ubuntu-core/20/stable/current/ Note that you have to make a copy of the OVMF_VARS.ms.fd from /usr/share/OVMF/OVMF_VARS.ms.fd (which is from the ovmf package), and then when you are able to boot a VM with the command line enable secure boot via the OVMF EFI setup. At that point with the above command line you should be able to boot UC20 with full disk encryption enabled using the swtpm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903864 Title: qemu-system-x86_64: -device tpm-tis,tpmdev=tpm-tpm0,id=tpm0: Property 'tpm-tis.tpmdev' can't find value 'tpm-tpm0' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1903864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917776] Re: snap install: support installing multiple snaps with `--classic` mode
** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Status: New => Triaged ** Changed in: snapd Importance: Undecided => Wishlist ** 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/1917776 Title: snap install: support installing multiple snaps with `--classic` mode To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1917776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
