This is a per-snap feature, snapd doesn't specifically modify any font
features, and we are working towards having as many snaps as possible
use snapcraft's configure hook which sets up a private font cache that
is per-snap and not shared. So if you find this is happening for a snap
which uses that
Yes, I would say that you should file bugs with individual snaps then,
you can suggest to snaps to try upgrading to using the extensions from
modern snapcraft such as kde-neon or gnome-* but it's possible that some
snaps will not be able to switch to using those extensions.
** Changed in: snapd (U
So I disabled both ubuntu-dock and the desktop icons extensions and
still see the freezes, here's a log of gnome-shell:
https://pastebin.ubuntu.com/p/CXCfTVtkMJ/
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell (Ubuntu)
S
Hey so sorry I missed that you wanted me to run those commands before,
but it happened again this morning and here are the requested logs and
lspci output. Note that I stripped out all the messages from snapd since
I have debug mode enabled and it's extremely noisy, but if you think
snapd could be
Here's lspci
** Attachment added: "lspci -kv"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1912246/+attachment/5471916/+files/lspci.txt
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell-extension-ubuntu-dock (U
Public bug reported:
[ placeholder - release in progress ]
This is a new version of snapd.
The changelog is available here
https://github.com/snapcore/snapd/blob/2.51/packaging/ubuntu-16.04/changelog,
the raw git changelog is available here:
https://github.com/snapcore/snapd/commits/2.51 (note t
** Description changed:
- [ placeholder - release in progress ]
-
This is a new version of snapd.
The changelog is available here
https://github.com/snapcore/snapd/blob/2.51/packaging/ubuntu-16.04/changelog,
the raw git changelog is available here:
https://github.com/snapcore/snapd/c
** Description changed:
This is a new version of snapd.
The changelog is available here
https://github.com/snapcore/snapd/blob/2.51/packaging/ubuntu-16.04/changelog,
the raw git changelog is available here:
https://github.com/snapcore/snapd/commits/2.51 (note that the debian
changel
When you have no snaps installed, snapd will exit itself automatically,
but as long as there are snaps installed, snapd needs to be installed in
order to do a few things:
- setup and manage the confinement of snaps
- handle automatic updates to snaps and snapd
- respond to any requests made with t
This was discussed on Mattermost, and the cause of this is not related
to snapd, it is an issue with the snap-store snap.
** Changed in: snapd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
A fix for this is in the beta channel AIUI, you can refresh to try out
the fix with:
```
snap refresh snap-store --beta --ignore-running
```
You can omit the --ignore-running if you do not have refresh app
awareness enabled.
--
You received this bug notification because you are a member of Ubun
As per Ken's comment on the associated forum post, this is actually now
on stable, being phased out. You should automatically get the stable
refresh within 24 hours, if you don't see it automatically, please wait
24 hours and then try again.
--
You received this bug notification because you are a
> I am not too sure if the flash-kernel uboot script actually is
compatible with the snapd's cmdline full / extra functionality.
It is not yet compatible unfortunately, and it's not on our immediate
roadmap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
This has been covered extensively elsewhere, for example on the forum,
etc. but we don't have immediate plans to support symlinked homes, and
bind mounts are an appropriate work-around: https://snapcraft.io/docs
/home-outside-home. I for some reason have lost my permission to change
the snapd debia
** Changed in: snapd
Milestone: None => 2.51
** Changed in: snapd
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925810
Title:
Bashism in snapd.sh (
I continue to see these messages on all UC20 VM's I use, including the
most recently released stable image on cdimage when booted in a VM
** Changed in: snapd
Status: Expired => Confirmed
** Changed in: snapd
Importance: Undecided => Medium
--
You received this bug notification becaus
Can you provide a full build failure log and information on what you
changed when you tried to build snapd?
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Thanks for that
** Changed in: snapd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935667
Title:
Please switch to fuse3
To manage notifications about thi
With the test snap that uses core20 as it's base, test-snapd-rsync-
core20 (installable on the edge channel), I see it segfaulting when
running the snap on both a UC20 system with the core20 snap as a base
snap, as well as on my groovy desktop:
https://pastebin.ubuntu.com/p/qbq86DYw5Q/
You can re
To be clear, the snapd and core snaps for 2.49.2 were not built with the
recently reverted libc6, that was only for focal which affected the
core20 snap, see https://bugs.launchpad.net/snap-core20/+bug/1926355 for
details on that bug. This is a separate issue
--
You received this bug notification
Sure, I was not aware test-snapd-rsync-core20 was shipping glibc, that
is indeed not a good idea.
I went looking on my system for other snaps which experienced the crash,
and it seems that every snap that ships glibc in it crashes with the
beta channel of core20, but snaps that (properly) do not s
Unfortunately I don't know how to easily remove glibc from the snaps in
a way that would confirm that they work, I don't have time to manually
build all of these snaps that are broken, I tried the basic thing of
unpacking the snap and `rm -rf ./lib/x86_64-linux-gnu/libc-2.31.so
./lib/x86_64-linux-g
This happened to me when upgrading from Groovy to Hirsute just now, with
the same symptoms as above - I had `search .` in resolv.conf, but
nothing creating that entry in /etc/netplan or in
/etc/systemd/resolved.conf.
I fixed the broken package by fixing the erroneous entry
/etc/postfix/main.cf (re
** Changed in: snapd
Milestone: None => 2.45
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868894
Title:
[uc18] docker overlayfs* seems broken
To manage notifications about this bug go to:
htt
This will be fixed in 2.50
** Changed in: snapd
Status: New => Fix Committed
** Changed in: snapd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/192
Also to be clear, from jjohansen's comment to me last week, all of the
necessary patches are available in the 5.4 focal kernel, so kernels for
UC20 from canonical snaps should contain this fix on the 20 track.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This systemd bug can be problematic for snapd as well, leading to the
sort of situation in https://bugs.launchpad.net/snapd/+bug/1928806,
where running snap commands frequently leads to many many many leftover
scopes like this
** Also affects: snapd
Importance: Undecided
Status: New
--
For reference, the PR that Zygmunt had which was planned to fix this was
https://github.com/snapcore/snapd/pull/8219, but there were issues with
that approach. We need to pick it up again and rework to get an approach
which matches the comments from Jamie there.
--
You received this bug notificat
** Changed in: docker (Ubuntu)
Assignee: (unassigned) => Ian Johnson (anonymouse67)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814896
Title:
upgrade Docker snap to 18.09.1
To man
The docker snap cannot access directories that start with a "." in the
home folder. This is a generic security mechanism for all snaps. I'd
recommend moving the directory out of ~/.wp-env to somewhere like ~/wp-
env or allow configuring this somehow.
As such, closing this as WontFix for snapd.
**
Note that if you are on focal, you may still not get this fix if you
have the edge channel of the core/snapd snaps installed, as snapd will
re-exec into that channel, and the edge channel currently is lagging
behind the debian package of snapd. We expect the edge channel to be
properly rebuilt soon
This is fixed on snapd master and will be "released" with snapd 2.44.
** Changed in: snapd
Milestone: None => 2.44
** Changed in: snapd
Importance: Undecided => High
** Changed in: snapd
Status: In Progress => Fix Committed
--
You received this bug notification because you are a
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Ian Johnson (anonymouse67)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
*** This bug is a duplicate of bug 1864113 ***
https://bugs.launchpad.net/bugs/1864113
** This bug has been marked a duplicate of bug 1864113
snapd.seeded.service never starts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Ian Johnson (anonymouse67)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
How are these images built? Are they built with the tooling from livecd-
rootfs?
The issue here is that there are no assertions in the image @
/var/lib/snapd/assertions, but I'm not sure what's writing these seeds
so I can't say for sure that this bug is from livecd-rootfs.
If this image is built
Sure, perhaps it's not from that particular bug, but my question still
remains about how these images are built? Are they using livecd-rootfs
to seed the snaps? If so this is not a snapd bug, and is instead a
livecd-rootfs bug.
IMHO this is only a snapd bug if the seed was created with the `snap
p
** Also affects: livecd-rootfs (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/1864113
Title:
snapd.seeded.service never starts
To manage notifica
Just to be clear, the messages:
```
snapd.failure.service is a disabled or a static unit, not starting it.
snapd.snap-repair.service is a disabled or a static unit, not starting it.
```
are normal and harmless.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I can reproduce the issue with my GTX Titan X, proprietary nvidia
drivers at 418 and Ubuntu 19.04 with snapd master. Same error messages
** Changed in: snapd
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I'll take a look at measuring this with snapd $SOON
** Changed in: snapd
Assignee: (unassigned) => Ian Johnson (anonymouse67)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/186117
Hi,
The firefox snap plugs both the unity7 interface and the x11 interface.
For historical reasons, the unity7 interface grants access to parts of
the x11 interface because unity is based on X, and so to deny firefox
access to all things X, you also need to disconnect the unity7
interface. On my m
Jamie, is this still an issue? I'm inclined to close this since the
apparmor bug seems to have been released a long time ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413410
Title:
Unable to m
This seems like a snap specific issue and not a general snapd issue. I
would suggest contacting the author of the snap, see:
```
$ snap info python38 | grep contact
```
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member
Public bug reported:
After an upgrade with focal-proposed this morning, I am unable to set
any scaling for any of my monitors without the monitor turning blank for
15 seconds and reverting to 100% scaling.
I am using X11 with gnome and proprietary nvidia drivers on Focal. I
have 3 monitors attach
Attaching monitors.xml since it doesn't seem that apport picked it up
** Attachment added: "~/.config/monitors.xml from my system"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+attachment/5341610/+files/monitors.xml
--
You received this bug notification because you are a mem
Oddly enough I was able to get 200% scaling to work randomly by not
quite lining up all the monitors and offsetting them from each other in
the settings window.
Is there anything I could try manually to unbreak the situation or is
there a debian package I could downgrade to in order to get scaling
FWIW, if I switch to using the noveau driver and then login via Wayland,
I can enable fractional scaling through Settings and that is successful,
but unfortunately then all the text in some apps becomes rather blurry.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Actually after testing this out, I was able to use fractional scaling
with X11 again by using the nouveau driver instead of the proprietary
nvidia driver, which on my machine is at nvidia-440. This is a
sufficient work-around for me, it's unfortunate I can't use the
proprietary nvidia driver with f
I've seen this inside an Ubuntu 18.04 lxd container with a poor internet
connection as well. apt is version 1.6.11.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375405
Title:
Impossible download s
I don't think we have such a capability right now in snapd. If you
locally modify the snap-confine profile, it will be rewritten on at
least core refreshes (and reboots as well if I'm not mistaken), so it
sounds like we need some mechanism to specify additional rules to be
included in the snap-conf
*** This bug is a duplicate of bug 1828500 ***
https://bugs.launchpad.net/bugs/1828500
Closing as duplicate of https://bugs.launchpad.net/ubuntu/+source
/livecd-rootfs/+bug/1828500
** This bug has been marked a duplicate of bug 1828500
snapd fails always in Optimised Ubuntu Desktop images
I suspect you've been able to resolve this, sorry we never got back to you
about it.
I'm closing it as "Won't fix", because we didn't do anything about this, but if
you're still stuck there's probably a cause for this that isn't necessarily
snapd itself and we can probably figure it out.
Again,
Is this still a problem with snaps in a more recent Ubuntu version and a
more recent snapd version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757303
Title:
Snap apps don't support input method
I suspect you've been able to resolve this, sorry we never got back to you
about it.
I'm closing it as "Won't fix", because we didn't do anything about this, but if
you're still stuck there's probably a cause for this that isn't necessarily
snapd itself and we can probably figure it out.
Again,
I suspect you've been able to resolve this, sorry we never got back to you
about it.
I'm closing it as "Won't fix", because we didn't do anything about this, but if
you're still stuck there's probably a cause for this that isn't necessarily
snapd itself and we can probably figure it out.
Again,
I'm assign Pawel here as he has been working on some first-boot speed
improvements for cloud images specifically. Also, since this was
reported we now have `snap debug timings` command, which would be really
useful to look at for slow first boot. For a first-boot, the first snap
change is always se
(Ubuntu)
Assignee: (unassigned) => Ian Johnson (anonymouse67)
** Changed in: snapd (Ubuntu)
Importance: Undecided => Low
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I tried building your snaps with snapcraft to reproduce the issue, but
unfortunately the vault-snap is missing a consul binary from the consul-
dir part. Can you update the snapcraft.yaml sources and try this with a
more recent snapd? I suspect this bug has been fixed as a number of
mount namespace
I tried building your snaps with snapcraft to reproduce the issue, but
unfortunately the vault-snap is missing a consul binary from the consul-
dir part. Can you update the snapcraft.yaml sources and try this with a
more recent snapd? I suspect this bug has been fixed as a number of
mount namespace
** Changed in: snapd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Michael Vogt (mvo)
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can see the use case here, but I tend to agree with @ogra that it is
not as useful as for debs and the sheer quantity of the output will make
it difficult to actually do anything useful with the output. Setting as
wishlist for now, if there are additional use cases for this feature,
please feel f
Is this still an issue for you?
What is the output of `snap version`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757326
Title:
snaps can't see network
To manage notifications about this bug go
Public bug reported:
On Ubuntu 18.04.2 LTS Desktop, after running out of space on my disk, my
system was unable to finish booting and I had to go into recovery mode
and remove a number of files before the system would boot. After doing
so I discovered that now the apparmor.service systemd unit alw
FWIW this could be a snapd bug, because while my system was unable to
boot, I disabled all the snaps I had installed except the core snap, and
then after being able to reboot I now re-enable all the snaps and see
some warnings:
May 25 17:32:16 systemd[1]: Starting AppArmor initialization...
May 25
Well I tried restarting AppArmor using `systemctl start apparmor` while
running `dmesg -w -k` and got the following log:
https://pastebin.ubuntu.com/p/98zXMsr6Sy/ I don't see a stack trace for
apparmor itself, just for chrome and pulseaudio.
Is there anyway to have apparmor.service show what profi
How would you recommend I go about checking which profiles are actually
loaded and which profiles are reported as loaded? I have this from aa-
status: https://pastebin.ubuntu.com/p/c2FbrndDzs/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
So I ran your snippet to determine which profiles weren't loaded and the
only one which wasn't loaded was:
```
$ sudo cat /sys/kernel/security/apparmor/profiles | awk '{ print $1 }' >
/tmp/foo ; sudo apparmor_parser -N /etc/apparmor.d/
/var/lib/snapd/apparmor/profiles/ >> /tmp/foo ; sort /tmp/fo
Ah actually, if I move that profile out of the way, then `systemctl
start apparmor` starts immediately. So the issue must be with that
profile being too large (and indeed it is 4-5 MB).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Yes, certainly use the profile for whatever you can use it for. Would
you like me to edit the description on this bug to reflect the actual
underlying cause here or should I just close this and file a new bug for
the memory usage of this profile? I'm no expert here but I think 15.4 GB
memory usage
@Jamie yes this was generated by snapd, the original snapcraft.yaml is
attached.
And also yes I fully understand this was an atypical usage of layouts, I
was experimenting with using layouts to make it seem to a snap
application that an additional package was installed in the base snap. I
generate
** Summary changed:
- apparmor fails to start with no parser errors
+ apparmor uses excessive memory leading to oom kill
** Description changed:
+ When attempting to load the profile from comment #7, apparmor uses
+ excessive amounts of memory leading to being killed by the OOM killer
+ and thus
What shows up with `SNAPD_DEBUG=1 snap run go get -u ...`?
Also are there any denials in the system journal at the time of the
segfault? i.e. `journalctl -e --no-pager -k`?
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
** Changed in: snapd (Ubuntu Bionic)
Status: New => I
What does `snap changes` show here?
Also what does `snap known serial` show on this machine?
Typically that error is for when a device has not yet communicated with
the snap store to get a serial assertion, and thus can't install snaps.
Perhaps this device does not have network access to the stor
>From the dpkg terminal log I see this:
```
rm: das Entfernen von '/var/snap' ist nicht möglich: Das Gerät oder die
Ressource ist belegt
```
which google translate tells me means:
```
rm: the removal of `/var/snap` is not possible: The device or resource is busy
```
It looks like this system h
Note that this has been reported on the forum before at
https://forum.snapcraft.io/t/classic-confinement-on-atom-yet-still-getting-denials/4956
and
https://forum.snapcraft.io/t/snapd-2-32-breaks-live-server-installer/4597
--
You received this bug notification because you are a member of Ubuntu
Bu
This is now handled properly, in the case where the snap is classic it
is shown as such, and in the case where the snap is not classic, it
cannot be installed in classic confinement. See for example a classic
snap installed:
```
$ snap info go | grep installed
installed:1.12.9
Multiple speedups for snapd seeding have been implemented since this was
first filed, can you confirm that you still see slow snapd seeding on
boot without any snaps installed on the system?
Also @mpathy, the issue surrounding gnome-calculator being slow to start is a
separate issue that has als
** 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/1664445
Title:
No warning/error when removing dependency
To manage notifications about th
This is because the ubuntu-image snap is not published for arm64.
Transferring to the ubuntu-image project for them to comment on
publishing the ubuntu-image snap for arm64.
** Also affects: ubuntu-image
Importance: Undecided
Status: New
** Changed in: snapd (Ubuntu)
Status: New
The `snap interfaces` command is deprecated, and instead the `snap
connections` command should be used. The `snap connections` command does
auto-complete in this case. See:
```
$ GO_FLAGS_COMPLETION=1 snap connections go
go
```
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
** Cha
Where is the blank line? I don't quite understand what is empty here.
Also this is from an old snapd so unless it's reproducible with a newer
one I'm inclined to close this bug.
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are
Actually, the content for snap try is bind-mounted (or at least it is
now, I'm not sure if that was the case when this was first reported or
not I think it has always been that way but I'm not sure).
You should still be able to edit files in the prime (or whatever dir is
bind-mounted from `snap tr
The `snap interfaces` command has now been deprecated and the `snap
connections` is now the command to use to inspect interface connections.
I cannot reproduce the issue in this bug with the `snap connections`
command, so I'm closing this.
** Changed in: snapd (Ubuntu)
Status: New => Fix Re
Does `snapctl set` during a hook still cause the installation of a snap
to hang for you? I cannot reproduce this behavior with snapd 2.42.
Also have you seen the new documentation for hooks at
https://snapcraft.io/docs/supported-snap-hooks ? If you would like
changes made to that documentation, yo
This at least fails more nicely with the lxd snap:
https://pastebin.ubuntu.com/p/djwrN5nxjT/
I see the following denial in the journal:
Sep 25 18:17:24 kernel: audit: type=1400 audit(1569453444.560:27044):
apparmor="DENIED" operation="mount" info="failed flags match" error=-13
profile="lxd-holy-m
I should also specify - I can ssh into the lxc container and lxc fails
in the same way as with `lxc shell ...`
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777017
Title:
snap install lxd doesn't w
Yes, adding security.nesting works with the lxd snap inside a lxd
container running with the lxd snap. Closing as Fix Released in this
case, thanks @stgraber for the pointer
** Changed in: snapd
Status: New => Fix Released
** Changed in: snapd (Ubuntu)
Status: New => Fix Released
-
** Changed in: docker (Ubuntu)
Assignee: Ian Johnson (anonymouse67) => (unassigned)
** Changed in: docker (Ubuntu)
Assignee: (unassigned) => Tianon Gravi (tianon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: docker (Ubuntu)
Importance: Undecided
Status: New
** Changed in: docker (Ubuntu)
Assignee: (unassigned) => Tianon Gravi (tianon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
*** This bug is a duplicate of bug 1575593 ***
https://bugs.launchpad.net/bugs/1575593
This is a duplicate of the existing bug report about adding man pages
which I have attached to this bug (the other bug has more information on
the situation)
** This bug has been marked a duplicate of bug 1
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Confirmed
** Changed in: snapd
Importance: Undecided => High
** Changed in: snapd
Assignee: (unassigned) => Maciej Borzecki (maciek-borzecki)
--
You received this bug notificat
I think something like this can be implemented with grub fallback menus,
but this is not a high priority bug
** Changed in: snapd
Importance: High => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: snapd
Status: Triaged => Fix Released
** Changed in: snapd
Milestone: None => 2.48.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888691
Title:
[uc20] rpi4 does not boot
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Triaged
** Changed in: snapd
Importance: Undecided => Wishlist
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a
Hi folks, I think the new version of the qemu package in Groovy at least
has regressed an important aspect for us in testing Ubuntu Core 20 VM's
with swtpm. We use the swtpm-mvo snap in conjunction with qemu and OVMF
to run Ubuntu Core 20 VM's, and after upgrading to qemu
1:5.0-5ubuntu9.6, I can no
So I tested the swtpm-mvo snap in a hirsute live image from current/ on
cdimage, using kernel 5.8.0-36-generic (which is only slightly older
than my current groovy kernel at 5.8.0-44-generic), and qemu 1:5.2+dfsg-
3ubuntu1, and it worked for me to use the swtpm from the swtpm-mvo snap.
So I think t
Okay, so this time when it happened at Sun Mar 7 02:44 AM UTC 2021,
here are the logs. I did not find any crash files in /var/crash, and
there were no results for my whoopsie-id either.
The journalctl output is attached
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+s
Here's lspci
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912246
Title:
[nvidia] gnome-shell freezes randomly
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/
Here's lspci
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912246
Title:
[nvidia] gnome-shell freezes randomly
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/
1 - 100 of 289 matches
Mail list logo
