[Bug 2059195] Re: package snapd 2.58+22.04.1 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1
I've opened a related PR to the firefox snap which replaces the problematic interface with system-files https://github.com/canonical/firefox-snap/pull/53 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059195 Title: package snapd 2.58+22.04.1 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2059195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059195] Re: package snapd 2.58+22.04.1 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1
I was able to reproduce this with 22.04, snapd 2.61.1. This is what is reported by findmnt: ``` maciek@vm:~$ findmnt TARGETSOURCE FSTYPE OPTIONS / /dev/vda2 ext4rw,relatime,errors=remount-ro ├─/syssysfs sysfs rw,nosuid,nodev,noexec,relatime │ ├─/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime │ ├─/sys/fs/cgroupcgroup2 cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot │ ├─/sys/fs/pstorepstore pstore rw,nosuid,nodev,noexec,relatime │ ├─/sys/firmware/efi/efivars efivarfs efivarfsrw,nosuid,nodev,noexec,relatime │ ├─/sys/fs/bpf bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 │ ├─/sys/kernel/debug debugfs debugfs rw,nosuid,nodev,noexec,relatime │ ├─/sys/kernel/tracing tracefs tracefs rw,nosuid,nodev,noexec,relatime │ ├─/sys/fs/fuse/connections fusectl fusectl rw,nosuid,nodev,noexec,relatime │ └─/sys/kernel/configconfigfs configfsrw,nosuid,nodev,noexec,relatime ├─/proc proc procrw,nosuid,nodev,noexec,relatime │ └─/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=41325 │ └─/proc/sys/fs/binfmt_miscbinfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime ├─/devudev devtmpfs rw,nosuid,relatime,size=1949512k,nr_inodes=487378,mode=755,inode64 │ ├─/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 │ ├─/dev/shm tmpfs tmpfs rw,nosuid,nodev,inode64 │ ├─/dev/hugepageshugetlbfs hugetlbfs rw,relatime,pagesize=2M │ └─/dev/mqueue mqueue mqueue rw,nosuid,nodev,noexec,relatime ├─/runtmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=397560k,mode=755,inode64 │ ├─/run/lock tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k,inode64 │ ├─/run/credentials/systemd-sysusers.service ramfs ramfs ro,nosuid,nodev,noexec,relatime,mode=700 │ ├─/run/snapd/ns tmpfs[/snapd/ns] tmpfs rw,nosuid,nodev,noexec,relatime,size=397560k,mode=755,inode64 │ │ ├─/run/snapd/ns/firefox.mnt nsfs[mnt:[4026532961]] nsfsrw │ │ ├─/run/snapd/ns/snap-store.mntnsfs[mnt:[4026532962]] nsfsrw │ │ └─/run/snapd/ns/snapd-desktop-integration.mnt nsfs[mnt:[4026532964]] nsfsrw │ └─/run/user/1000tmpfs tmpfs rw,nosuid,nodev,relatime,size=397556k,nr_inodes=99389,mode=700,uid=1000,gid=1000,inode64 │ ├─/run/user/1000/gvfs gvfsd-fuse fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 │ └─/run/user/1000/doc portal fuse.portal rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 ├─/snap/bare/5/dev/loop0 squashfsro,nodev,relatime,errors=continue,threads=single ├─/snap/core22/1122 /dev/loop1 squashfsro,nodev,relatime,errors=continue,threads=single ├─/snap/firefox/3836 /dev/loop2 squashfsro,nodev,relatime,errors=continue,threads=single ├─/snap/gnome-42-2204/141 /dev/loop3 squashfsro,nodev,relatime,errors=continue,threads=single ├─/snap/gtk-common-themes/1535/dev/loop4 squashfsro,nodev,relatime,errors=continue,threads=single ├─/snap/snap-store/959
[Bug 1921289] Re: snap changes exit 1 when no changes found
This was fixed in https://bugs.launchpad.net/snapd/+bug/1823974 and released in 2.51 ** Changed in: snapd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921289 Title: snap changes exit 1 when no changes found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1921289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899794] Re: Error during refresh of snapd leads to unusable system
I believe a problem addressing snap-failure and snapd has been fixed a couple of releases back. Should the problem persist, please leave a comment. ** Changed in: snapd (Ubuntu) Status: New => Fix Released ** Changed in: snapd Status: Triaged => 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/1899794 Title: Error during refresh of snapd leads to unusable system To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1899794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762072] Re: Indicator icons not loading for certain snap applications
** Also affects: snapd-desktop 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/1762072 Title: Indicator icons not loading for certain snap applications To manage notifications about this bug go to: https://bugs.launchpad.net/snapd-desktop/+bug/1762072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874660] Re: Please make an "update in progress" message for snap updates
** Also affects: snapd-desktop 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/1874660 Title: Please make an "update in progress" message for snap updates To manage notifications about this bug go to: https://bugs.launchpad.net/snapd-desktop/+bug/1874660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908159] Re: snapd lost snaps
Do you still experience the problem? If so, can you collect the output of: snap list --all I understand it has been a while since this had happened, but should this happen again, please collect the output of the journal (journalctl --no-pager preferrably). ** 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/1908159 Title: snapd lost snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1908159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873621] Re: package snapd 2.38~14.04 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5
Is this still an issue? 2.38 and 2.42 are very old releases. I'm going to set this to incomplete. Please leave a comment if you still experience the 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/1873621 Title: package snapd 2.38~14.04 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1873621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961791] Re: 2.54.3+21.10.1ubuntu0.1 broke Plasma Desktop when Fish is the default shell
** Changed in: snapd Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961791 Title: 2.54.3+21.10.1ubuntu0.1 broke Plasma Desktop when Fish is the default shell To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1961791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907056] Re: Please add meta/kernel.yaml
** Changed in: snapd 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/1907056 Title: Please add meta/kernel.yaml To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1907056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905272] Re: Can't get h/w video acceleration on rpi4
AFAIU support for pulling in dtbs from the kernel snap is already in snapd. We've recently also fixed a problem with AppArmor profile that blocked access to the GPU device, perhaps that's related. The PR that contains the fix is https://github.com/snapcore/snapd/pull/11822 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905272 Title: Can't get h/w video acceleration on rpi4 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1905272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905272] Re: Can't get h/w video acceleration on rpi4
Can you please pull the latest pi kernel and gadget from 20/stable, snapd from edge and verify if things are working for you? ** Changed in: snapd Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905272 Title: Can't get h/w video acceleration on rpi4 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1905272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968878] Re: systemd-udevd: video4linux: Process '/usr/lib/snapd/snap-device-helper add ... /class/video4linux 0:0' failed with exit code 1.
On top of what Alberto already requested, please provide the output of: udevadm info /sys/class/video4linux and udevadm info /dev/video* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968878 Title: systemd-udevd: video4linux: Process '/usr/lib/snapd/snap-device-helper add ... /class/video4linux 0:0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1968878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968878] Re: systemd-udevd: video4linux: Process '/usr/lib/snapd/snap-device-helper add ... /class/video4linux 0:0' failed with exit code 1.
Device 0:0 and devpath /class/video4linux do not look right. I suspect that the udev rules generated by the camera interface are too broad and they catch /sys/class/video4linux as well as the actual devices. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968878 Title: systemd-udevd: video4linux: Process '/usr/lib/snapd/snap-device-helper add ... /class/video4linux 0:0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1968878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
Can you attach the contents of /etc/os-release? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971955 Title: systemd-udevd call unshare process when attaching nvme volume To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1971955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871148] Re: services start before apparmor profiles are loaded
@eurbah hi, also for the service in question, can you attach the output of `systemctl list-dependencies --after snap..service` AFAICT, all services are to be started after snapd.apparmor.d, which in turn is started after apparmor.service, which should ensure that apparmor profiles are loaded before service startup is attempted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
For the record, does /usr/bin/unshare exist in your system? Can you run the command that Alberto provided in the console? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971955 Title: systemd-udevd call unshare process when attaching nvme volume To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1971955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972910] Re: error: too many arguments for command
** Changed in: snapd (Ubuntu) Status: In Progress => Fix Committed ** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Status: New => Fix Committed ** Changed in: snapd Milestone: None => 2.56 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972910 Title: error: too many arguments for command To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1972910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972871] Re: mosquitto snap produces high CPU load
Are there any denials being logged? Anything in dmesg? Did you move the extracted snap binaries to a container? ** 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/1972871 Title: mosquitto snap produces high CPU load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1972871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972910] Re: error: too many arguments for command
Seems like a low hanging fruit, so I opened a PR to snapd: https://github.com/snapcore/snapd/pull/11776 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972910 Title: error: too many arguments for command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1972910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972910] Re: error: too many arguments for command
** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Maciej Borzecki (maciek-borzecki) ** Changed in: snapd (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972910 Title: error: too many arguments for command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1972910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971491] Re: After reboot firefox refuses to run snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks
AFAIU this happens when appamor.service is disabled and does not start during the boot or there is no apparmor profile for snap-confine. Can you make sure that `systemctl show apparmor.service` shows that it's enabled, and attach the output of `sudo aa-status |grep snap-confine` ? ** 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/1971491 Title: After reboot firefox refuses to run snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1971491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970025] Re: Tried to update Snapd from the GUI, it logged me out
I suspect this was caused by udev reload, which we have observed previously and I believe it was fixed in gdm by https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/175 ** Also affects: gdm3 (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/1970025 Title: Tried to update Snapd from the GUI, it logged me out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1970025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
FWIW systemd --user is expected to have been started as part of your session. This is supposed to be fully automatic. I don't think you can start it yourself, as it's up to systemd/logind to properly start the process and move it to the right cgroup. I've added systemd to the bug report, so maybe this time it will get some traction. ** Also affects: systemd (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/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967479] Re: snaps lost connections during 22.04 upgrade
@n.buechner no, that's a different problem, most likely: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961898 although in your case it hit a 25s and still did not get a response from systemd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967479 Title: snaps lost connections during 22.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1967479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965682] Re: package snapd 2.54.3+20.04.1ubuntu0.2 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1
Thanks for reporting this. Do I understand correctly that you have moved the content to /var/lib/snapd and bind mounted that location on top of the original path? ** 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/1965682 Title: package snapd 2.54.3+20.04.1ubuntu0.2 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1965682/+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
It appears that the same version of apparmor parser (2.13.3 as reported by Simon), behaves differently when running in the container. Specifically, the command that snapd also executes did not fail in the container, while it should have. Actually there's even an error message but the exit code is still 0. Since it did not fail, then snapd assumes that bpf is supported and generates a snippet for snap-confine apparmor profile. I think the first step here, is to figure out why apparmor_parser did not fail. -- 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 1965328] Re: transient scope could not be started error in bionic lxd container
Let me reiterate what I mentioned in the MM channel. The snap in question apparently uses device access in which case we'll set up device filtering. The host being impish, uses cgroup v2, which percolates to the container. Since it's v2, device filtering is implemented by attaching a BPF program on the cgorup, hence we need to have a separate group otherwise we'd break your session. Snap will ask your systemd --user to create a transient scope for the app, but looking at the logs this fails with: Mar 17 16:13:22 b2 systemd[2487]: snap.snapcraft.snapcraft.237e42c2-4906-439b-a992-743647600bc6.scope: Failed to add PIDs to scope's control Mar 17 16:13:22 b2 systemd[2487]: snap.snapcraft.snapcraft.237e42c2-4906-439b-a992-743647600bc6.scope: Failed with result 'resources'. Mar 17 16:13:22 b2 systemd[2487]: Failed to start snap.snapcraft.snapcraft.237e42c2-4906-439b-a992-743647600bc6.scope. At this point running snap will fail and the sandbox cannot be completed. I think the main problem is why create transient scope fails the way it did, and whether systemd from bionic even works properly on a host with unified hierarchy. ** Also affects: systemd (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/1965328 Title: transient scope could not be started error in bionic lxd container To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1965328/+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
I pulled a clean 20.04 cloud image VM from https://cloud-
images.ubuntu.com/focal/current/
root@ubuntu:/home/guest# grep PRETTY /etc/os-release
PRETTY_NAME="Ubuntu 20.04.4 LTS"
root@ubuntu:/home/guest# uname -a
Linux ubuntu 5.4.0-104-generic #118-Ubuntu SMP Wed Mar 2 19:02:41 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu:/home/guest# echo 'profile snap-test { capability bpf, }' |
apparmor_parser --preprocess
AppArmor parser error, in stdin line 1: Invalid capability bpf.
as expected:
root@ubuntu:/home/guest# cat /var/lib/snapd/apparmor/snap-confine/cap-bpf
cat: /var/lib/snapd/apparmor/snap-confine/cap-bpf: No such file or directory
root@ubuntu:/home/guest# snap list lxd
Name Version RevTracking Publisher Notes
lxd 4.0.922526 4.0/stable/… canonical✓ -
root@ubuntu:/home/guest# lxd init --auto
root@ubuntu:/home/guest# lxc launch images:ubuntu/20.04 c1
Creating c1
Starting c1
root@ubuntu:/home/guest# lxc exec c1 -- apt install snapd -y
..
root@ubuntu:/home/guest# lxc exec c1 -- snap list
No snaps are installed yet. Try 'snap install hello-world'.
As expected bpf isn't supported by apparmor_parser:
root@c1:~# echo 'profile snap-test { capability bpf, }' |
apparmor_parser --preprocess
restarted the guest:
root@ubuntu:/home/guest# lxc restart c1
and it's still the same:
root@ubuntu:/home/guest# lxc exec c1 -t /bin/bash
root@c1:~# echo 'profile snap-test { capability bpf, }' | apparmor_parser
--preprocess
AppArmor parser error, in stdin line 1: Invalid capability bpf.
profile snap-test { capability bpfroot@c1:~#
root@c1:~#
root@c1:~# cat /var/lib/snapd/apparmor/snap-confine/cap-bpf
cat: /var/lib/snapd/apparmor/snap-confine/cap-bpf: No such file or directory
The only difference is that I didn't install or run distrobuilder. So I
proceeded to do it.
root@c1:~# snap install distrobuilder --edge --classic
2022-03-12T09:17:52Z INFO Waiting for automatic snapd restart...
distrobuilder (edge) git-f883431 from Stéphane Graber (stgraber) installed
root@c1:~# echo 'profile snap-test { capability bpf, }' | apparmor_parser
--preprocess
AppArmor parser error, in stdin line 1: Invalid capability bpf.
profile snap-test { capability bpf
root@c1:~# cat /var/lib/snapd/apparmor/snap-confine/cap-bpf
cat: /var/lib/snapd/apparmor/snap-confine/cap-bpf: No such file or directory
and restart:
root@c1:~# exit
root@ubuntu:/home/guest# lxc restart c1
root@ubuntu:/home/guest# lxc exec c1 -t /bin/bash
root@c1:~# echo 'profile snap-test { capability bpf, }' | apparmor_parser
--preprocess
AppArmor parser error, in stdin line 1: Invalid capability bpf.
profile snap-test { capability bpfroot@c1:~#
root@c1:~#
root@c1:~# cat /var/lib/snapd/apparmor/snap-confine/cap-bpf
cat: /var/lib/snapd/apparmor/snap-confine/cap-bpf: No such file or directory
root@c1:~# systemctl status snapd.apparmor
● snapd.apparmor.service - Load AppArmor profiles managed internally by snapd
Loaded: loaded (/lib/systemd/system/snapd.apparmor.service; enabled;
vendor preset: enabled)
Drop-In: /run/systemd/system/service.d
└─zzz-lxc-service.conf
Active: active (exited) since Sat 2022-03-12 09:18:46 UTC; 47s ago
Process: 134 ExecStart=/usr/lib/snapd/snapd-apparmor start (code=exited,
status=0/SUCCESS)
Main PID: 134 (code=exited, status=0/SUCCESS)
Mar 12 09:18:46 c1 systemd[1]: Starting Load AppArmor profiles managed
internally by snapd...
Mar 12 09:18:46 c1 snapd-apparmor[134]: /usr/lib/snapd/snapd-apparmor: 47:
ns_stacked: not found
Mar 12 09:18:46 c1 snapd-apparmor[134]: /usr/lib/snapd/snapd-apparmor: 48:
ns_name: not found
Mar 12 09:18:46 c1 systemd[1]: Finished Load AppArmor profiles managed
internally by snapd.
root@c1:~# exit
root@ubuntu:/home/guest# lxc exec c1 -- distrobuilder
System container image builder for LXC and LXD
Usage:
distrobuilder [command]
Available Commands:
build-dir Build plain rootfs
build-lxc Build LXC image from scratch
build-lxd Build LXD image from scratch
help Help about any command
pack-lxc Create LXC image from existing rootfs
pack-lxd Create LXD image from existing rootfs
repack-windows Repack Windows ISO with drivers included
Flags:
--cache-dir Cache directory
--cleanup Clean up cache directory (default true)
--debug Enable debug output
--disable-overlay Disable the use of filesystem
[Bug 1963861] Re: Can't tell what application will be launched with custom schemes
@alexmurray that code has never listed or show which application would handle given URL scheme. The change affected the implementation of io.snapcraft.Launcher, which is only called as a fallback when a snap calls xdg-open inside it's namespace. The primary handler that is tried goes through the desktop portal https://flatpak.github.io/xdg-desktop- portal/#gdbus-org.freedesktop.portal.OpenURI which AFAIU prompts to select an application for some number of attempts, which then goes away if the user chose consistently chose the same application each time. So if the prompt was originally shows, but now it's not, my guess would be that it's the portal. The fallback code would open an application for which there is a desktop handler registered in the mime db. Perhaps we could improve that to show a prompt? Anyways, this code isn't part of any stable release yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1963861 Title: Can't tell what application will be launched with custom schemes To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1963861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957948] Re: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)
@ytvwld I have 2.54.3+20.04.1ubuntu0.2 version: ``` guest@ubuntu:~$ dpkg -l snapd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===-- ii snapd 2.54.3+20.04.1ubuntu0.2 amd64Daemon and tooling that enable snap packages ``` Which contains this bit in /usr/share/fish/vendor_conf.d/snapd.fish: ``` if not set -q XDG_DATA_DIRS set --global --export XDG_DATA_DIRS $XDG_DATA_DIRS # XDG_DATA_DIRS is not defined, set it to some reasonable defaults set XDG_DATA_DIRS (string join : /usr/local/share /usr/share) end if not contains $snap_xdg_path (string split : "$XDG_DATA_DIRS") set XDG_DATA_DIRS (string join : -- $XDG_DATA_DIRS $snap_xdg_path) end ``` Which does not look like what you pasted. Can you double check you have the right version installed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957948 Title: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1957948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839237] Re: snapd disk write usage very high on 19.04 with snapd 2.39.3
@takeseem unfortunately due to a bug in LP I cannot access the image. Can you rename the image to use latin characters only and upload it again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839237 Title: snapd disk write usage very high on 19.04 with snapd 2.39.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1839237/+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
If this happens again try running `SNAPD_DEBUG=1 snap run telegram- desktop` and collect the log. Since 22.04 is using unified hierarchy, we try to ask your session's systemd to create a transient scope for it. In your case, the log indicates that this operation failed. Looking at the log: Feb 23 15:17:04 d960-ubu2 featherpad[66733]: Failed to load module "appmenu-gtk-module" Feb 23 15:17:19 d960-ubu2 systemd[12489]: snap.chromium.chromium.31faf3af-f659-4425-9943-1a3d21db6861.scope: Couldn't move process 66754 to requested cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/snap.chromium.chromium.31faf3af-f659-4425-9943-1a3d21db6861.scope' (directly or via the system bus): Input/output error Feb 23 15:17:19 d960-ubu2 systemd[12489]: snap.chromium.chromium.31faf3af-f659-4425-9943-1a3d21db6861.scope: Failed to add PIDs to scope's control group: Permission denied Feb 23 15:17:19 d960-ubu2 systemd[12489]: snap.chromium.chromium.31faf3af-f659-4425-9943-1a3d21db6861.scope: Failed with result 'resources'. Feb 23 15:17:19 d960-ubu2 systemd[12489]: Failed to start snap.chromium.chromium.31faf3af-f659-4425-9943-1a3d21db6861.scope. Feb 23 15:17:19 d960-ubu2 chromium_chromium.desktop[66754]: internal error, please report: running "chromium" failed: transient scope could not be started, job /org/freedesktop/systemd1/job/724 finished with result failed Feb 23 15:17:32 d960-ubu2 systemd[1]: systemd-timedated.service: Deactivated successfully. Feb 23 15:17:45 d960-ubu2 rtkit-daemon[56123]: Supervising 3 threads of 2 processes of 1 users. Specifically this one is worrying: systemd[12489]: snap.chromium.chromium.31faf3af-f659-4425-9943-1a3d21db6861.scope: Couldn't move process 66754 to requested cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/snap.chromium.chromium.31faf3af-f659-4425-9943-1a3d21db6861.scope' (directly or via the system bus): Input/output error I'm afraid there's nothing snapd can do about that. I'm adding systemd to the bug. ** Also affects: systemd (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/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 1960702] Re: all snap apps gone after snap upgrade
** This bug is no longer a duplicate of bug 1957948 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960702 Title: all snap apps gone after snap upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1960702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960702] Re: all snap apps gone after snap upgrade
*** This bug is a duplicate of bug 1957948 *** https://bugs.launchpad.net/bugs/1957948 Indeed, I may have acted to fast marking this as a duplicate of the other bugs. The problem is somewhat related to the other bugs in that both go down to fish shell snapd setup and how fragile the desktop session setup is. I pushed a fix in https://github.com/snapcore/snapd/pull/11416 which should be cherry picked to 2.54.3 once it lands. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960702 Title: all snap apps gone after snap upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1960702/+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'
@gsunipipeline it looks like systemd does not operate correctly in your system. This is a prerequisite for even accessing the snapd daemon, since we rely on systemd to provide the socket, then activate snapd daemon, and the snapd daemon directly interacts with systemd to set up snaps. ** Also affects: systemd (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/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'
Does running `systemctl status` work at all? -- 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 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
@lukeweller you probably guessed this is not part of any release yet. Documentation will be there in due time. In the meantime you're welcome to contribute to the discussion in the forum or grab snapd from edge and try it out yourself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
@lukeweller 3 commens up there's: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1575053/comments/308 there's also a forum topic with more details: https://forum.snapcraft.io/t/experimental-flag-for-hiding-snap/28509 -- 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 1961365] Re: 2.54.3+18.04.2ubuntu0.1 update on bionic breaks fish shell
This should work even for fish 2.7: https://github.com/snapcore/snapd/pull/11416 Anyone wants to give it a try? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961365 Title: 2.54.3+18.04.2ubuntu0.1 update on bionic breaks fish shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961365] Re: 2.54.3+18.04.2ubuntu0.1 update on bionic breaks fish shell
Yes, sorry my bad. Fish in bionic is even older, and thus requires more contrived workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961365 Title: 2.54.3+18.04.2ubuntu0.1 update on bionic breaks fish shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960972] Re: All snap applications missing from gnome-search after update
*** This bug is a duplicate of bug 1957948 *** https://bugs.launchpad.net/bugs/1957948 ** This bug has been marked a duplicate of bug 1957948 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960972 Title: All snap applications missing from gnome-search after update To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1960972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960702] Re: all snap apps gone after snap upgrade
*** This bug is a duplicate of bug 1957948 *** https://bugs.launchpad.net/bugs/1957948 ** This bug has been marked a duplicate of bug 1957948 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960702 Title: all snap apps gone after snap upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1960702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961365] Re: 2.54.3+18.04.2ubuntu0.1 update on bionic breaks fish shell
*** This bug is a duplicate of bug 1957948 *** https://bugs.launchpad.net/bugs/1957948 ** This bug has been marked a duplicate of bug 1957948 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961365 Title: 2.54.3+18.04.2ubuntu0.1 update on bionic breaks fish shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957948] Re: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)
** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Status: New => Confirmed ** Changed in: snapd Assignee: (unassigned) => Maciej Borzecki (maciek-borzecki) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957948 Title: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1957948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957948] Re: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)
One more fix for fish https://github.com/snapcore/snapd/pull/11371 seems to work in Focal VM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957948 Title: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1957948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960492] Re: Snapd incompatible with fish, breaking x2go
*** This bug is a duplicate of bug 1957948 *** https://bugs.launchpad.net/bugs/1957948 ** This bug has been marked a duplicate of bug 1957948 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960492 Title: Snapd incompatible with fish, breaking x2go To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1960492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959417] Re: unable to use jupyter-notebook package with snap'd browsers like firefox or chromium
> I wonder if we should make an exception for "~/.local/" or "~/.local/share/", though, since that generally contains data which could potentially be useful for applications. I think that's risky. Off the top of my head ~/.local/share/Trash is where files go when you remove then in Nautilus, or the fish shell stores history under ~/.local/share/fish. I'm pretty sure digging harder you could find more potentially interesting files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959417 Title: unable to use jupyter-notebook package with snap'd browsers like firefox or chromium To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1959417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
The error indicates that snapd is still in the process of early init & setting up device. Ideally it's enough to wait for seed.loaded event, (snap wait system seed.loaded). This is what snapd.seeded.service does, but from the piece of log you provided, the service did not start, because its dependencies failed. So by the time `snap install core22` ran snapd was still not ready. Getting the contents of the journal to see what exactly failed would be great. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958676 Title: error: too early for operation, device not yet seeded or device model not acknowledged Install failed To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957948] Re: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)
** 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/1957948 Title: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1957948/+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 bug is a duplicate of bug 1957948 *** https://bugs.launchpad.net/bugs/1957948 ** This bug has been marked a duplicate of bug 1957948 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) -- 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 1957948] Re: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)
This was fixed in https://bugs.launchpad.net/snapd/+bug/1957155 which so far is available only in snapd master. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957948 Title: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1957948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956942] Re: snap can not start chromium-browser with cgroup v2 and hierarchy
*** This bug is a duplicate of bug 1951491 *** https://bugs.launchpad.net/bugs/1951491 2022/01/10 12:58:44.388636 tracking.go:185: DEBUG: using session bus 2022/01/10 12:58:44.393780 tracking.go:290: DEBUG: StartTransientUnit failed with "org.freedesktop.DBus.Error.Spawn.ChildExited": [Process org.freedesktop.systemd1 exited with status 1] 2022/01/10 12:58:44.393815 cmd_run.go:1187: DEBUG: snapd cannot track the started application Indicates that snap asked systemd to create a new scope for the application (since establishing device filtering in your current cgroup would break your session), but that failed. Judging by the error message, `systemd --user` exited or was restarted, hard to tell. Unfortunately there is nothing snapd can do about that. ** This bug has been marked a duplicate of bug 1951491 Can't run snaps: .slice/session-1.scope is not a snap cgroup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956942 Title: snap can not start chromium-browser with cgroup v2 and hierarchy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1956942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956942] Re: snap can not start chromium-browser with cgroup v2 and hierarchy
Please attach the output of `SNAPD_DEBUG=1 snap run chromium-browser`. ** 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/1956942 Title: snap can not start chromium-browser with cgroup v2 and hierarchy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1956942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
No, it just means that the journal is not collecting any user session logs. I'm afraid this is beyond snapd scope at this point. Perhaps you can try to make you openbox session to be more like what GNOME and KDE set up, that is with systemd user instance that can be accessed via dbus. I don't know how you log in, maybe to need to tweak the PAM config so that pam_systemd is included, though I'm far from being expert here and the user sesion setup has become crazy complicated. Anyways, the snapd part is working as expected, such that if a separate cgroup for the snap cannot be created it stops before breaking the one your session is in. ** Changed in: snapd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
Ok, so the logs you attached earlier are: 2021/12/03 15:21:45.540312 tracking.go:45: DEBUG: creating transient scope snap.chromium.chromium 2021/12/03 15:21:45.543273 tracking.go:185: DEBUG: using session bus 2021/12/03 15:21:45.547127 tracking.go:290: DEBUG: StartTransientUnit failed with "org.freedesktop.DBus.Error.Spawn.ChildExited": [Process org.freedesktop.systemd1 exited with status 1] 2021/12/03 15:21:45.547174 cmd_run.go:1187: DEBUG: snapd cannot track the started application 2021/12/03 15:21:45.547199 cmd_run.go:1188: DEBUG: snap refreshes will not be postponed by this process When snap starts the /usr/bin/snap binary tries to create a scope for the application. The scope is needed so that the app can run in a separate cgroup which is then confined to access specific devices. Unfortunately this is the only way to set this up on a cgroup v2 system. The setup is done by talking to your `systemd --user` instance. In the log it's clearly indicated that it failed and systemd exited, thus no scope and the app cannot be run, because the confinement would break your session cgroup (.slice/session-1.scope). I'm afraid I don't know enough about your setup to guess what could be wrong there and why the user instance may have exited. Perhaps reviewing the user logs (journalctl --user) could help uncover the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+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
Valentin has 2 PRs up to address this on the snapd/core20 side: https://github.com/snapcore/snapd/pull/9 and https://github.com/snapcore/core20/pull/124 ** Changed in: snapd Assignee: (unassigned) => Valentin David (valentin.david) ** Changed in: snapd Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
Can you run `systemctl --user`? Does it work at all? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
Snapd needs to talk to systemd user instance to setup a scope for the snap. This is done over a session bus. Is DBUS_SESSION_BUS_ADDRESS set in your environment? Run `echo $DBUS_SESSION_BUS_ADDRESS`, the output should be like `unix:path=/run/user/NNN/bus` (where NNN is your uid). Can you then run `ls -l /run/user/NNN/bus` and check if the socket file is there? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
** 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/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
Can you run `SNAPD_DEBUG=1 snap run firefox` and attach the output? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950855] Re: Can't enable snap to print on a usb printer
You can collect a strace of the app by running: snap run --strace='-vf -s 256' cura-slicer.cura And yes, as @alexmurray indicated, this may be something with device cgroups. The problem with those is there is nothing logged if access is denied, making the debugging process complicated. Assuming that you have not unplugged the printer, and it's still the same USB device inside the kernel, IOW this device: > Bus 001 Device 003: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter Can you do `ls -l /dev/bus/usb/001/003` and attach the output? It should look like this: crw-rw-r-- 1 root root 189, 2 11-17 07:36 /dev/bus/usb/001/003 The column right next to root:root is the major and minor numbers of this device. Having this, please check whether /sys/fs/cgroup/devices/snap.cura-slicer.cura/devices.list contains an entry 'c 189:2'. Next, you can run `udevadm info /dev/bus/usb/001/003` and attach the output. However, since it's a USB serial device, I suspect that the actual communication happens over one of the /dev/ttyUSB* devices. Please check whether any /dev/ttyUSB* devices exist and attach the output of `udevadm info /dev/ttyUSB*`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950855 Title: Can't enable snap to print on a usb printer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1950855/+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 run `sudo systemctl restart apparmor.service snapd.apparmor.service` and see if that fixes your problem? -- 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 1947203] Re: Snap applications cannot start
I see this in the attached journal:
Oct 14 22:53:56 audit[1790]: AVC apparmor="DENIED" operation="open"
profile="snap-update-ns.lxd" name="/proc/1790/cgroup" pid=1790 comm="5"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Which is unexpectd as reading own /proc//cgroup is allowed by the profile
generated by snapd.
Can you confirm that /var/lib/snapd/apparmor/profiles/snap-update-ns.lxd exist
in your system, and that in contains the following snippet?
```
# Allow reading own cgroups
@{PROC}/@{pid}/cgroup r,
```
--
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
There don't appear to be any AppArmor denials in the logs provided. From snap debug seeding output, looks like the command `udevadm trigger --subsystem-nomatch=input` failed when invoked during installation of the snapd, which was done outside of confinement. -- 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 1946086] Re: systemd user daemon fails with Permission denied when creating transient scope
Possibly related: https://github.com/systemd/systemd/issues/3388 ** Bug watch added: github.com/systemd/systemd/issues #3388 https://github.com/systemd/systemd/issues/3388 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946086 Title: systemd user daemon fails with Permission denied when creating transient scope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1946086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946086] [NEW] systemd user daemon fails with Permission denied when creating transient scope
Public bug reported:
Observed on 18.04. Systemd user instance fails when trying to create a
transient scope when logged in through ssh as a regular user
Specifically this fails:
$ systemd-run --user --scope ls
Job for run-rc78f932ad730440490bd7bc17f9d5c8c.scope failed.
See "systemctl status run-rc78f932ad730440490bd7bc17f9d5c8c.scope" and
"journalctl -xe" for details.
Inspecting journal shows:
Oct 05 10:38:16 ubuntu systemd[1437]:
run-rc78f932ad730440490bd7bc17f9d5c8c.scope: Failed to add PIDs to scope's
control group: Permission denied
Oct 05 10:38:16 ubuntu systemd[1437]:
run-rc78f932ad730440490bd7bc17f9d5c8c.scope: Failed with result 'resources'.
Oct 05 10:38:16 ubuntu systemd[1437]: Failed to start /bin/ls.
Oct 05 10:38:16 ubuntu polkitd(authority=local)[1244]: Unregistered
Authentication Agent for unix-process:7425:200857 (system bus name :1.106,
object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale
en_US.UTF-8) (disconnected from bus)
Further strace shows that there is an EACCES when writing the PID of the forked
process to cgroup procs:
1437 openat(AT_FDCWD,
"/sys/fs/cgroup/pids/user.slice/user-999.slice/user@999.service/run-r067b0361ac97410886bbb3eec1c3848d.scope/pids.max",
O_WRONLY|O_NOCTTY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
1437 newfstatat(AT_FDCWD, "/sys/fs/cgroup/unified", {st_dev=makedev(0, 32),
st_ino=1, st_mode=S_IFDIR|0555, st_nlink=5, st_uid=0, st_gid=0,
st_blksize=4096, st_blocks=0, st_size=0, st_atime=1633428300 /*
2021-10-05T10:05:00.33600+ */, st_atime_nsec=33600,
st_mtime=1633428300 /* 2021-10-05T10:05:00.33600+ */,
st_mtime_nsec=33600, st_ctime=1633428300 /*
2021-10-05T10:05:00.33600+ */, st_ctime_nsec=33600},
AT_SYMLINK_NOFOLLOW) = 0
1437 openat(AT_FDCWD,
"/sys/fs/cgroup/unified/user.slice/user-999.slice/user@999.service/run-r067b0361ac97410886bbb3eec1c3848d.scope/cgroup.procs",
O_WRONLY|O_NOCTTY|O_CLOEXEC) = 34
1437 fcntl(34, F_GETFL)= 0x8001 (flags O_WRONLY|O_LARGEFILE)
1437 fstat(34, {st_dev=makedev(0, 32), st_ino=2358, st_mode=S_IFREG|0644,
st_nlink=1, st_uid=999, st_gid=999, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=1633430486 /* 2021-10-05T10:41:26.701277147+ */,
st_atime_nsec=701277147, st_mtime=1633430486 /*
2021-10-05T10:41:26.701277147+ */, st_mtime_nsec=701277147,
st_ctime=1633430486 /* 2021-10-05T10:41:26.701277147+ */,
st_ctime_nsec=701277147}) = 0
1437 write(34, "7461\n", 5)= -1 EACCES (Permission denied)
1437 close(34) = 0
Full strace of the failed attempt:
https://paste.ubuntu.com/p/4vwtYQ7mww/
When executing the same command from a gnome terminal, the scope is
created successfuly. Full trace of successful execution:
https://paste.ubuntu.com/p/XjJ8mfxSXn/
The relevant bit from the happy execution path:
openat(AT_FDCWD,
"/sys/fs/cgroup/pids/user.slice/user-999.slice/user@999.service/run-rd9ebe0f0326b482e82ca374c5ae613cd.scope/pids.max",
O_WRONLY|O_NOCTTY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/sys/fs/cgroup/unified", {st_dev=makedev(0, 32),
st_ino=1, st_mode=S_IFDIR|0555, st_nlink=5, st_uid=0, st_gid=0,
st_blksize=4096, st_blocks=0, st_size=0, st_atime=1633428300 /*
2021-10-05T10:05:00.33600+ */, st_atime_nsec=33600,
st_mtime=1633428300 /* 2021-10-05T10:05:00.33600+ */,
st_mtime_nsec=33600, st_ctime=1633428300 /*
2021-10-05T10:05:00.33600+ */, st_ctime_nsec=33600},
AT_SYMLINK_NOFOLLOW) = 0
openat(AT_FDCWD,
"/sys/fs/cgroup/unified/user.slice/user-999.slice/user@999.service/run-rd9ebe0f0326b482e82ca374c5ae613cd.scope/cgroup.procs",
O_WRONLY|O_NOCTTY|O_CLOEXEC) = 34
fcntl(34, F_GETFL) = 0x8001 (flags O_WRONLY|O_LARGEFILE)
fstat(34, {st_dev=makedev(0, 32), st_ino=2298, st_mode=S_IFREG|0644,
st_nlink=1, st_uid=999, st_gid=999, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=1633429609 /* 2021-10-05T10:26:49.619626843+ */,
st_atime_nsec=619626843, st_mtime=1633429609 /*
2021-10-05T10:26:49.619626843+ */, st_mtime_nsec=619626843,
st_ctime=1633429609 /* 2021-10-05T10:26:49.619626843+ */,
st_ctime_nsec=619626843}) = 0
write(34, "7410\n", 5) = 5
close(34) = 0
23838 write(31, "24075\n", 6) = -1 EACCES (Permission denied)
$ lsb_release -rd
Description:Ubuntu 18.04.6 LTS
Release:18.04
$ dpkg -l systemd\*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Architecture Description
+++-=-=-=-
ii systemd
[Bug 1934147] Re: systemd leaks abandoned session scopes
** Changed in: snapd Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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 1925507] Re: grub-common: snapd autopkgtests fail on s390x
** Changed in: snapd Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925507 Title: grub-common: snapd autopkgtests fail on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1925507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943853] Re: Ubuntu update disconnected all snaps
Any chance you could collect the journal logs from 2021-09-16. I think this command should provide the output: `journalctl --since 2021-09-16 --until 2021-09-17`. I'm switching this bug to Fix Committed, as we landed a fix to not loose connections if the snaps happen to be unavailable and it was also cherry-picked for 2.52. ** Changed in: snapd Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943853 Title: Ubuntu update disconnected all snaps 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 1894115] Re: After upgrade of packages cannot open applications installed through snap
Please attach the output of `snap list --all`, and then the output of `snap connections libreoffice`. ** 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/1894115 Title: After upgrade of packages cannot open applications installed through snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1894115/+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
The PR is up: https://github.com/snapcore/snapd/pull/10839 also needs +1 from security ** Changed in: snapd (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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 1944004] Re: snapd.seeded.service never finishes on non-amd64
Thanks to @mwhudson for arranging access to the test host. Per his
comments I launched both 20210903 and 20210904 snapshots of impish.
Debugging, I noticed that there was an apparmor denial logged when snap
(the snap binary from snapd) was transitioning to snap-confine. While
snap-confine runs under an apparmor profile that's coming from the
package, or the core snap, or the snapd snap.
The denial is:
audit: type=1400 audit(1632477434.031:8902): apparmor="DENIED"
operation="file_mmap"
namespace="root//lxd-happy-impish_"
profile="/snap/snapd/12886/usr/lib/snapd/snap-confine"
name="/usr/lib/aarch64-linux-gnu/ld-linux-aarch64.so.1"
pid=1101743 comm="snap-confine" requested_mask="m" denied_mask="m"
fsuid=100 ouid=100
I've switched the container to privileged and disabled the confinement
at lxd level via `lxc config set broken-impish raw.lxc
"lxc.apparmor.profile=unconfined"`, so I was only left with the apparmor
profile shipped by snapd.
Looking at what we have in the profile for snap-confine in the snapd
source tree:
/{,usr/}lib{,32,64,x32}/{,@{multiarch}/{,atomics/}}ld-*.so mrix,
So /usr/lib/aarch64-linux-gnu/ld-linux-aarch64.so.1 does not match the
expected pattern and things fail in a weird and funny way.
I've updated the profile to
/{,usr/}lib{,32,64,x32}/{,@{multiarch}/{,atomics/}}ld-*.so* mrix, and
things are working again.
I was told that this is an upstream change, so I'll open a PR for snapd
to update the profile.
--
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 1944004] Re: snapd.seeded.service never finishes on non-amd64
Adding SNAP_CONFINE_DEBUG=1 in the env will produce more debugging output. -- 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 1943853] Re: Recent update DELETED SNAP PROGRAMS
I suspect that for gimp and chromium you need to run those again, but swap authy for either "gimp" or "chromium": sudo snap connect authy:gnome-3-28-1804 gnome-3-28-1804 sudo snap connect authy:gtk-3-themes gtk-common-themes:gtk-3-themes sudo snap connect authy:icon-themes gtk-common-themes:icon-themes sudo snap connect authy:sound-themes gtk-common-themes:sound-themes -- 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
At least to get authy back you can try running the following commands: for iface in browser-support desktop desktop-legacy gsettings home network opengl unity7 wayland x11; do sudo snap connect authy:$iface system; done sudo snap connect authy:gnome-3-28-1804 gnome-3-28-1804 sudo snap connect authy:gtk-3-themes gtk-common-themes:gtk-3-themes sudo snap connect authy:icon-themes gtk-common-themes:icon-themes sudo snap connect authy:sound-themes gtk-common-themes:sound-themes -- 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
This doesn't look right. Can you attach the output of `snap changes`. If there is a change that has an error status, can you also attach the output `snap change ` for each one? IDs are in the leftmost column in snap changes output. -- 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
Can you attach the output of `snap connections` and `snap list` commands? -- 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
We also have a change in snapd source code that will no longer show these messages: https://github.com/snapcore/snapd/pull/10756 -- 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/ubuntu/+source/language-pack-pt-base/+bug/1932579/+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
** 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/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 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!
I do not see this problem with snapd-2.49.2+20.04 installed from the archive. Please check on you system after running an update. ** 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/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 1925810] Re: Bashism in snapd.sh (aka apps-in-path.sh) breaks dash
** 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/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 1935701] Re: package snapd 2.48.3+20.04 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1
Waiting until unit snap-gnome\x2d3\x2d34\x2d1804-66.mount is stopped [attempt 19] Running in chroot, ignoring request: is-active Waiting until unit snap-gnome\x2d3\x2d34\x2d1804-66.mount is stopped [attempt 20] Running in chroot, ignoring request: is-active Removing snap gnome-3-34-1804 and revision 66 The log says that you tried to remove snapd when running Ubuntu in a chroot? ** 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/1935701 Title: package snapd 2.48.3+20.04 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1935701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938897] Re: snapd 2.51.1+21.10 autotest segfault on ppc64
segfault happens in `go tool compile` process ** Also affects: golang (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd (Ubuntu Impish) Status: New => Won't Fix ** Changed in: snapd (Ubuntu) Status: New => 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/1938897 Title: snapd 2.51.1+21.10 autotest segfault on ppc64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1938897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943008] Re: snapd autopkgtest smoke/sandbox failure on impish
AFAIU the extra line in the output (libgcc_s.so.1 must be installed for pthread_cancel to work) appears when mksquashfs is invoked as squashfs- tools is missing a dependency on libgc-s1 (previously libgcc1). ** Also affects: squashfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd (Ubuntu) Status: New => 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/1943008 Title: snapd autopkgtest smoke/sandbox failure on impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1943008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889067] Re: Error logging in snapd: (most recent call last): (snapd-error-quark, 10) when trying to log in from settings
** Changed in: snapd (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889067 Title: Error logging in snapd: (most recent call last): (snapd-error-quark, 10) when trying to log in from settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1889067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889318] Re: install chromium in lxc container for 20.04 fails
** Changed in: snapd (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889318 Title: install chromium in lxc container for 20.04 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1889318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930179] Re: Advantech CAN driver not recognized in Ubuntu Core 20
** Also affects: linux (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/1930179 Title: Advantech CAN driver not recognized in Ubuntu Core 20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930179] Re: Advantech CAN driver not recognized in Ubuntu Core 20
The kernel is provided by a kernel snap which is most commonly a rebuilt deb. Which kernel are you referring to? Is the driver part of the mainline kernel? I'll let whoever maintains the right kernel sprek, but I'm doubtful we can include a random driver, with unclear licensing. ** 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/1930179 Title: Advantech CAN driver not recognized in Ubuntu Core 20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1930179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714941] Re: mounts should hint ignore
AFAIU this bug is already fixed. Snapd adds x-gdu.hide to mount options for snaps, and they are no longer visible in gnome disks utility. Not sure why, but with udisks 2.9.2 I still see HintIgnore as false in my system. However, the `udisksctl status` only shows the actual disks so maybe it's handled elsewhere. Please reopen if this is still a problem. ** Changed in: snapd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: snapd Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714941 Title: mounts should hint ignore To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1714941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915156] Re: sudoers file ignored
Yes, it looks like dpkg sets up the file to be tracked as part of snapd package. $ dpkg -l snapd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==-- ii snapd 2.45.1+20.04.2 amd64Daemon and tooling that enable snap packages $ dpkg -L snapd |grep sudoer /etc/sudoers.d /etc/sudoers.d/99-snapd.conf $ apt upgrade snapd -y ... $ dpkg -l snapd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
[Bug 1915156] Re: sudoers file ignored
Can you double check the package version? The bug was fixed in 2.46+. It was still in 2.45.1 which got originally shipped in 20.04, but has since been replaced by newer versions of the snapd package without the sudoers drop in file. ** 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/1915156 Title: sudoers file ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1915156/+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
Can you try running `sudo snap set system experimental.robust-mount- namespace-updates=false` ? -- 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 1903967] Re: Can't purge snapd: rm: cannot remove '/snap': Device or resource busy
** Changed in: snapd (Ubuntu) Status: In Progress => Fix Committed ** Summary changed: - Can't purge snapd: rm: cannot remove '/snap': Device or resource busy + Can't purge snapd: rm: cannot remove '/snap': Device or resource busy under LXD -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903967 Title: Can't purge snapd: rm: cannot remove '/snap': Device or resource busy under LXD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1903967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903967] Re: Can't purge snapd: rm: cannot remove '/snap': Device or resource busy
I've proposed a fix for snapd inside containers right here: https://github.com/snapcore/snapd/pull/9812 ** Changed in: snapd (Ubuntu) Status: Incomplete => In Progress ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Maciej Borzecki (maciek-borzecki) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903967 Title: Can't purge snapd: rm: cannot remove '/snap': Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1903967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903967] Re: Can't purge snapd: rm: cannot remove '/snap': Device or resource busy
@stgraber thanks for the pointers. I was pretty sure we have the right code in postrm to handle that and we do. However it looks like for the container case, the first attempt to remove /snap is tried before umount is executed. I'll look into addressing this shortly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903967 Title: Can't purge snapd: rm: cannot remove '/snap': Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1903967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903967] Re: Can't purge snapd: rm: cannot remove '/snap': Device or resource busy
AFAIK, /snap being busy in an lxd container is expected, as /snap appears to be a bind mount: root@purgefail:~# findmnt /snap TARGET SOURCE FSTYPE OPTIONS /snap /dev/sda1[/var/snap/lxd/common/lxd/storage-pools/default/containers/purgefail/rootfs/snap] ext4 rw,relatime Perhaps the lxd can comment on whether this can be addressed. In any case it's a separate issue. As for the problem with Bionic, I cannot reproduce that locally, in GCP or as part the snapd CI. Please confirm that there are no snap applications running (eg. snap-store), and that your shell is not somewhere under /snap. Try running `lsof |grep ' /snap'` to check for any processes. ** Also affects: lxd (Ubuntu) Importance: Undecided Status: New ** 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/1903967 Title: Can't purge snapd: rm: cannot remove '/snap': Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1903967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907650] Re: Snapd stuck forever on refresh if services starting indefinitely
There's a TimeoutStartSec which snapd sets when start-timeout present in the snap.yaml file for that daemon. Otherwise it is set to the DefaultTimeoutStartSec which may vary across distros, but defaults to 90s (which is AFAICT is also true for Ubuntu). However, lxd.activate is a oneshot service, which has the timeout disabled by default. Perhaps it should be set to some value, even a large one like 600s. ** Also affects: lxd (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/1907650 Title: Snapd stuck forever on refresh if services starting indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1907650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901444] Re: mount --rbind /var/tmp /tmp/snap.rootfs_1DwCoc//var/tmp: Permission denied)
** 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/1901444 Title: mount --rbind /var/tmp /tmp/snap.rootfs_1DwCoc//var/tmp: Permission denied) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1901444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901847] Re: snapd fails to shut down, gets killed after 1m30s during reboot
I can confirm that I've seen this on systems other than Ubuntu. Probably needs further investigation. ** Changed in: snapd Status: New => Triaged ** Changed in: snapd Importance: Undecided => Medium ** Changed in: snapd (Ubuntu) Status: New => Incomplete ** Changed in: snapd (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/1901847 Title: snapd fails to shut down, gets killed after 1m30s during reboot To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1901847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
