*** This bug is a duplicate of bug 2073938 ***
https://bugs.launchpad.net/bugs/2073938
Let's keep the dependencies out of it, and focus on checking the correct
dependencies are needed before everything explodes later.
--
You received this bug notification because you are a member of Ubuntu
B
Public bug reported:
Usability of autopkgtest-buildvm-ubuntu-cloud is low, as it first pulls
a large image from the internet and then crashes on missing tools it
should have both depend on in the debian packaging and verified on
startup before doing network-heavy work:
zyga@x13:~/.spread$ sudo au
The fix has landed in snapd so it will be available in the latest/edge
channel of snapd snap. If you refresh snapd with:
snap refresh --edge snapd
Then the fix will be immediately active.
You should refresh back to stable after the 2.63 release, unless you are
comfortable daily-driving possibly
This is fixed by https://github.com/snapcore/snapd/pull/13857
** Changed in: snapd (Ubuntu)
Status: New => In Progress
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This is fixed by https://github.com/snapcore/snapd/pull/13857
** Changed in: chromium-browser (Ubuntu)
Status: New => In Progress
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Invalid
** Changed in: snapd (Ubuntu)
Status: New => In Progress
--
You receive
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062173
Title:
Apparmor denies updating namespace with ecryp
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062330
Title:
Chromium fails to start with "inva
This bug is now well-understood and a fix is proposed in:
https://github.com/snapcore/snapd/pull/13853
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061981
Title:
chromium fails to start with non-s
We are still debugging it, it's not this. It's related to HOMEDIRS
tunable and variable expansion, somehow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061981
Title:
chromium fails to start with
We've debugged this issue and the problem is caused by apparmor re-
execution and configuration files being loaded from read-only snapd
squashfs, thus making HOMEDIRS customization invisible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I don't speak German very well but if I understand correctly your
/home/$LOGNAME is a symbolic link to /Users/$LOGNAME. This arrangement
is not supported by snapd as it interferes with the sandbox technology.
If you can, modify your system to mount the home directory at /home/baer
instead of using
We now believe this bug is understood and we are thinking about a way to
address it. The root cause is that the per-distro purge script is
unaware of the mounts that need to be stopped and has no way to
enumerate them.
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
--
You receive
Dear reporter. Do you know if the snapd package on your system was
customized in any way? Was "snap set ..." used to, for example, allow
non-/home home directories? Was snapd and snap packages used for a while
or was this a relatively fresh install that was just purged?
We're asking because the er
Yes, I think we may be enumerating a directory / statting files. I don't
believe we open anything unless we want to have a look but I _could_ be
wrong and I'm still investigating things (with interruptions to attend
calls).
I don't believe it is related to ubuntu-pro-client, the only reason it
is
Both before and after daemon-reload the units have the same definition:
$ systemctl cat apt-news.service esm-cache.service
# /usr/lib/systemd/system/apt-news.service
# APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
# timely information related to apt updates available t
With a closer look I ended up running this loop while looking at systemd
debug logs:
sudo snap remove --purge snapd && sudo systemctl daemon-reload && sudo
systemctl restart snapd && snap version && sudo apt update && echo
"ALOHA: installing snapd" | systemd-cat && sudo snap install snapd &&
echo
Removing ubuntu-pro-client silences this, so that installation of snapd
snap no longer causes any side-effects. While I can see that
installation of snapd has some impact on ubuntu-pro-client, I cannot yet
understand how.
--
You received this bug notification because you are a member of Ubuntu
Bu
Snapd touches neither apt-news.service nor esm-cache.service.
On my system the only mention of esm-cache.service is in
uaclient/actions.py:
zyga@ciri:/$ grep -FR esm-cache.service usr/ 2>/dev/null
usr/lib/python3/dist-packages/uaclient/actions.py:"esm-cache.service",
I've increased systemd
I've reproduced this and collected forkstat logs from installation of
snapd snap on an otherwise pristine "noble" system. I think what is
going on is that systemd stays in a mode where it knows that units on
disk have changed vs units in memory and will print the warning until
re-loaded. The fact t
** Changed in: snapd
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055239
Title:
Warning: The unit file, source configuration file or d
The failure of snapd autopkgtest suite looks like infrastructure issue:
1099s - Download snap "go" (10555) from channel "stable" (Get
"https://canonical-bos01.cdn.snapcraftcontent.com/download-
origin/canonical-
lgw01/Md1HBASHzP4i0bniScAjXGnOII9cEK6e_10555.snap?interactive=1&token=1710280800_3e59a
I've experienced this after installing Impish host on Raspberry Pi 4
with an Impish VM. The VM was working correctly up until just a moment
ago, as I type this, I've installed `linux-modules-extra-raspi in order
to get usb serial adapters to work inside the virtual machine. The
package installed no
This is now fixed upstream
https://gitlab.com/larswirzenius/vmdb2/-/merge_requests/83
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786699
Title:
grub-install command line options incompatible with
Updating gnome snap will remove the mount points from the firefox snap
mount namespace. It should not be done. I'm afraid r-a-a should be
extended to prevent refreshes of any connected snaps with the content
interface as well.
--
You received this bug notification because you are a member of Ubun
Updated patch with quilt support :)
** Patch removed: "debdiff with cherry picked fix"
https://bugs.launchpad.net/ubuntu/+source/zmk/+bug/1933827/+attachment/5507662/+files/zmk-0.4.2-2-to-0.4.2-2ubuntu1.debdiff
** Patch added: "zmk-0.4.2-2-to-0.4.2-2ubuntu1.debdiff"
https://bugs.launchpad
I've attached a debdiff fixing this in the most minimal way possible
** Patch added: "debdiff with cherry picked fix"
https://bugs.launchpad.net/ubuntu/+source/zmk/+bug/1933827/+attachment/5507662/+files/zmk-0.4.2-2-to-0.4.2-2ubuntu1.debdiff
--
You received this bug notification because you
** Description changed:
This bug is a mirror of the GitHub issue
https://github.com/zyga/zmk/issues/80 filed for the purpose of SRU
The following makefile snippet illustrates the problem:
# Symlink: sysota-rauc-hook -> sysotad
cmd/sysotad/sysota-rauc-hook.InstallDir = $(cmd/sysotad
Public bug reported:
This bug is a mirror of the GitHub issue
https://github.com/zyga/zmk/issues/80 filed for the purpose of SRU
The following makefile snippet illustrates the problem:
# Symlink: sysota-rauc-hook -> sysotad
cmd/sysotad/sysota-rauc-hook.InstallDir = $(cmd/sysotad/sysotad.InstallD
Snapd does not need to be running to run apps. It is really only
required to handle auto-updates. Everything else will auto start on
socket activation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/193
On a second look, this is fixed by
ae84b651f464f297c046b60b82c60ecdd69ce80e - a patch from the 2nd of Feb
2021.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925810
Title:
Bashism in snapd.sh (aka
** Also affects: snapd
Importance: Undecided
Status: New
** Summary changed:
- Incorrect quote use in apps-bin-path.sh
+ Bashism in snapd.sh (aka apps-in-path.sh) breaks dash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libpaper (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918021
Title:
Got Setting up libpaper1:amd64 (1.1.28) ... ucf: do not have write
pri
Dear reporter.
The mount and loopback device is created by libmount, through systemd.
Do you know if there's a way for snapd to indicate that the loop device
should be created with that attribute?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hey Itay Perl.
Unfortunately we cannot mount an overlayfs to solve this issue as is is
not compatible with apparmor and it would effectively break confinement.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Patch added: "This patch is against the vmdb2-0.19 upstream tag"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1786699/+attachment/5453052/+files/0001-Support-grub-compat-setting-for-Ubuntu.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've sent a patch to
https://gitlab.com/larswirzenius/vmdb2/-/issues/36#note_485816538 which
enables support for Ubuntu and Debian
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786699
Title:
grub-i
I've updated pi gadget to latest/stable and then manually updated the
assets by copying files fro the gadget boot assets to the appropriate
place on the FAT partition. Upon reboot uboot version was
U-Boot> version
U-Boot 2019.07+dfsg-1ubuntu4~18.04.1 (Dec 19 2019 - 22:06:27 +)
gcc (Ubuntu/Lin
Is /var/tmp a symbolic link? I think we only handle a case when that is
a real directory.
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I wonder what is causing that activity:
spal. 28 11:03:26 blynas snapd[1013]: daemon.go:586: WARNING: cannot
gracefully shut down in-flight snapd API activity within: 25s
This is why we are timing out on shutdown.
** Also affects: snapd
Importance: Undecided
Status: New
--
You recei
Could you provide journal log from the last boot?
journalctl -b 0 should do the trick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898869
Title:
System slow on booting
To manage notifications ab
I was curious where we do this so I went looking and this is the start
of the problem:
https://github.com/snapcore/snapd/blob/7ff96a40a7a7a7779db250b087cec9b183540130/overlord/snapshotstate/backend/helpers.go#L145
In absence of other information, we snapshot the state for all the users
this way.
This is caused by a bug in the snapshot code, which enumerates users by
their HOME entries. We should handle this case better.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901578
Title:
Cannot rem
Hey Markus.
Thank you for providing details about your environment. Unfortunately we
don't have any new ideas on how to solve home-at-nearly arbitrary path
and we certainly didn't have time to push this idea forward.
One idea I had a while ago is to mount whatever the original location of
HOME, a
The snapd side of this fix is baking in
https://github.com/snapcore/snapd/pull/9530
** Changed in: snapd
Status: Confirmed => In Progress
** Changed in: snapd
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
--
You received this bug notification because you are a member of
This issue is fixed upstream
https://github.com/u-boot/u-boot/commit/b1125802a524641ad1ac803b4a617756d26f007d
but the corresponding patch is not available in bionic or focal. Groovy u-boot
package is recent enough to contain this fix.
** Also affects: u-boot (Ubuntu)
Importance: Undecided
We took Alexes work on this and ended up using a different strategy to
fix it, one he suggested initially. The explanation of the motives are
captured by the pull request:
https://github.com/snapcore/snapd/pull/9516
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
@Marc, what is the bug report you've opened?
Chromium has no more debian packages as the team supporting it decided
that it is exceedingly difficult to maintain (especially for releases
other than latest). This is unrelated to snapd. Without snapd it would
simply be removed from the archive.
--
Marc Kolly, could you please open a new bug with details of your
particular configuration please. Commenting on a bug that is fix
released is not useful as we have integration tests that verify this
particular particular behavior works. I suspect there is something about
your setup we are misidenti
We could use snap-update-ns to hide the host's /etc if those specific
interfaces are connected. We could then present the relevant file from
the base snap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
I'm marking the snapd task as invalid as it seems to be a problem with
the set of snaps available in offline mode.
** Changed in: snapd
Status: New => Invalid
** Changed in: snapd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubu
I'm marking this as triaged. We should look at the seeding code to
ensure it can eventually actually fail and allow systems to continue
booting.
** Changed in: snapd
Status: New => Triaged
** Changed in: snapd
Importance: Undecided => Medium
--
You received this bug notification becau
I'm marking this as fix released based on the history of the referenced
pull request.
** Changed in: snapd
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869
This is still in development but there's some actual progress recently.
Complete development history is visible in
https://github.com/snapcore/snapd/projects/3
We are aiming to release a, still disabled by default, but much improved
version of this as either 2.47 or 2.48, depending on when the rev
I'm marking the snapd task as fix released, for 2.45 based on the
history of the referenced pull request.
** Changed in: snapd
Milestone: None => 2.45
** Changed in: snapd
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bug
This was released a while ago, the upstream task was stale.
** Changed in: snapd
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880085
Title:
snap userd's
I'm marking this as fix released based on the history of the referenced
pull request.
** Changed in: snapd
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871
Dear Rajat, please mount your external disk under /mnt/* or using
dynamic location in /media. Those locations are not supported. Arbitrary
locations cannot be supported, until all applications access files using
portals.
--
You received this bug notification because you are a member of Ubuntu
Bug
That last error about missing slots looks like another error. It may be
a race indeed. How can I reproduce it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891526
Title:
snapd.seeded.service hangs
Those are not fixed locations. You'd have to cope with responding to the
settings (that may differ per process) that govern their location. In
addition the ~/snap directory is very explicitly, and non-trivially
baked into apparmor profiles that are currently global to the system.
This setting can v
Dear reporter, please check if:
snap download etcd
snap download core18
snap ack *.assert
snap install ./core18_*.snap
snap install ./etcd_*.snap
fixes the problem for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I think that you will find that using `snap ack...` is the right thing
to do. I didn't test this manually but the use of `--dangerous` creates
quite a different environment than without it.
** Changed in: snapd
Status: New => Incomplete
--
You received this bug notification because you a
@nigels - there is no setting because there's no real way to represent
arbitrary location. This is a very hard technical problem, not the lack
of a knob to control some setting.
There are conventions we could use to get to a state where most users
could be happy. Where is your music and videos mou
Someone with upload access just needs to apply the patch and send it
upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866619
Title:
OverflowError when machine suspends and resumes after a lo
The real priority is on the upstream project. The Ubuntu package
priority is irrelevant and I cannot change it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/sn
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887134
Title:
Purging of snapd package should remove all files in / installed by
snaps
** Changed in: snapd
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784774
Title:
snapd is not autofs aware and fails with nfs home dir
To manage notific
This is now fixed by https://github.com/snapcore/snapd/pull/8936
** Changed in: snapd
Status: Triaged => In Progress
** Changed in: snapd
Milestone: None => 2.46
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
With the additional information in
https://bugs.launchpad.net/snapd/+bug/1821193 I think we can fix this
issue quickly.
1) The mountinfo parser will now look for an automount point that
mentions autofs, an example line is mentioned here:
137 29 0:50 / /home rw,relatime shared:87 - autofs
/etc/aut
This issue was fixed in snapd 2.43 which was since released to the
stable channel. Marking as such.
** Changed in: snapd
Milestone: None => 2.43
** Changed in: snapd
Status: Fix Committed => Fix Released
** Changed in: snapd
Milestone: 2.43 => 2.44
--
You received this bug notif
On closer look it seems that the patch was included in 2.44.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863255
Title:
Programs installed in Snap format do not detect the keyboard
To manage noti
This issue was fixed in snapd 2.45.1 which was released as a part of the
snapd snap but not yet as a part of the core snap. Marking as fix
released since it's technically out.
** Changed in: snapd
Milestone: None => 2.45.1
** Changed in: snapd
Status: Fix Committed => Fix Released
--
I didn't pinpoint the exact release but it seems to have been released
to stable sometime in snapd 2.44.*. Marking as released.
** Changed in: snapd
Status: Fix Committed => Fix Released
** Changed in: snapd
Milestone: None => 2.44
--
You received this bug notification because you ar
I'm marking this as medium as we should handle ipv6 better and this may
help to determine if there's a broad issue in the base snaps, either on
the configuration side or in the set of packages contained.
** Changed in: snapd
Status: New => Triaged
** Changed in: snapd
Importance: Undeci
I'm marking the snapd task as invalid as it's really not something that
snapd interacts with. Most likely kernel configuration OR core20 snap.
If it happens that this is related to kernel modules and their layout in
the system please reopen the snapd task.
** Changed in: snapd
Status: New =
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881159
Title:
BUG
Snapd 2.43 has been released a while ago. Marking as released.
** Changed in: snapd
Status: Fix Committed => Fix Released
** Changed in: snapd (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Snapd 2.45 has been released to stable, marking as released.
The Ubuntu package is in the SRU pipe.
** Changed in: snapd
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Changed in: snapd
Milestone: None => 2.45
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867415
Title:
Hardlinking snaps wastes 400 MB tmpfs RAM in live CDs
To manage notifications about thi
Snapd 2.44 has been released, marking as the bug as such.
** Changed in: snapd
Status: Fix Committed => Fix Released
** Changed in: snapd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I relayed the question to mvo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881350
Title:
snap seeding fails with libc6-lse
To manage notifications about this bug go to:
https://bugs.launchpad.net
** Changed in: snapd
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881350
Title:
snap seeding fails with libc6-lse
To manage notifications about this bu
This will be fixed with https://github.com/snapcore/snapd/pull/8788
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881350
Title:
snap seeding fails with libc6-lse
To manage notifications about this
Thanks, I'm done with the machine.
I left it in a state where it can install snaps but it will likely break
on re-exec. I'll send a fix to snapd now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881
in: snapd
Status: New => Confirmed
** Changed in: snapd
Importance: Undecided => High
** Changed in: snapd
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
** Changed in: snapd
Status: Confirmed => In Progress
--
You received this bug notification because you a
I'm experimenting there now. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881350
Title:
snap seeding fails with libc6-lse
To manage notifications about this bug go to:
https://bugs.launch
Dear reporter, can you attach the output of `dmesg | grep DENIED` after
a failed attempt please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881350
Title:
snap seeding fails with libc6-lse
To ma
I can fully confirm this, having gone through the exercise myself this
weekend.
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879229
Ti
Step 2 is difficult to handle in snapd as it interacts with the
organization of files in the snap that traditionally snapd does not
interact with.
Step 3 depends on the implementation of pulse on the host, though I
agree this is the correct solution, for now, and that it should *not* be
handled by
I believe this is really the bug that snapd cannot install "core" or
"core18" inside a container without failing on udev.
The well-known workaround is to do it twice.
I think we should sit down and discuss this but I think this can only be
done after core20 beta is out as we simply have no time f
The udev error is the well-known problem that of snapd pulling udev into
containers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878225
Title:
snapd.seeded.service waits forever (?) to have snaps
We've retrieved the OOPS from the ID mentioned in the log you've
attached. It seems the error is
ERROR run hook "install": cannot perform operation: mount --rbind /snap
/snap: Permission denied
Can you provide the output of "dmesg | grep DENIED" please? In addition,
can you please add "ls -ld /sn
This looks like a problem in the seed used to create this image. Can you
please attach:
/var/lib/snapd/seed/seed.yaml as well as find /var/lib/snapd/seed
please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
What's the chance this fails because of i18n?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876583
Title:
"panic: runtime error: slice bounds out of range" while installing any
snap package
To m
> Wiadomość napisana przez Oliver <1643...@bugs.launchpad.net> w dniu
> 04.05.2020, o godz. 09:39:
>
>
> @zyga wrote:
>
>> Allowing access outside of /home is possible but allowing access to arbitrary
>> places is not possible for obvious reasons. The work on portals is ongoing
>> and
>> it wi
To be clear, we've agreed to work on this in our cycle that runs for the
next 6 months.
It's happening! :)
** Changed in: snapd
Importance: Wishlist => High
** Changed in: snapd
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
--
You received this bug notification b
I understand the sentiment with ~/snap being a fixed location, shared by
both yourself and other people who have commented here.
The cost of making ~/snap arbitrary is very high but we have some ideas
that we are actively exploring as a part of the 20.10 cycle planning and
I suspect there will be
Hey, a fellow snapd developer here. We do not use XDG locations for the
following reasons:
1) They are configurable, per user, which would require per-user
confinement that we currently do not support.
2) Ignoring that, the standard locations are not followed by *all*
software uniformly so we nee
The system key is only rewritten if this is required. Normally it is not
modified.
The question now is: what has changed that made the system key differ?
One thing we did observe was /snap/core/$current changing without a
complete snapd re-start. Perhaps something was pinging snapd over the
API a
Snapd restart will notice and re-generate the system-key.
Can you please obtain timestamps of /var/lib/snapd/system-key? Can you
correlate the timestamps to the moment you restarted snapd?
When system key mismatch is detected "snap run" will do two things, make
a API call to snapd (triggering soc
Hey, everyone affected. Could you please post the output of "snap
version" as a comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756793
Title:
Can't run snaps on Ubuntu 18.04
To manage notif
1 - 100 of 1426 matches
Mail list logo
