** Changed in: snapd
Assignee: Ian Johnson (anonymouse67) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902748
Title:
ubuntu-seed / ubuntu-boot partition detection co
Public bug reported:
This is a new version of snapd.
NOTE: the links below will become available shortly and this note will
be removed when they are all available.
The changelog is available here
https://github.com/snapcore/snapd/blob/2.55/packaging/ubuntu-16.04/changelog,
the raw git changelog
Snapd does not check for the bpf feature through the kernel, it very
explicitly only checks the apparmor_parser support, see
https://github.com/snapcore/snapd/blob/master/sandbox/apparmor/apparmor.go#L331-L372
for full details of how we check for features
--
You received this bug notification
Thanks for the report, I just tried to reproduce this on both updated
impish and updated jammy and couldn't reproduce. I notice on impish
specifically that my focal container does not get the
/var/lib/snapd/apparmor/snap-confine/cap-bpf file which is expected
because the apparmor_parser for focal
Hi, can you paste the full journalctl output with --no-pager? The output
you posted above is cut off right where I would like to see what systemd
says.
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
So indeed your system is still using upstart, in order to use snapd you
will need to switch your system over to use systemd instead. Likely one
of the upgrade scripts from 10.04 to 16.04 did not transition from
upstart to systemd the way a fresh install of 16.04 would default to.
** Changed in:
What is the output of these commands:
ps -o cmd fp 1
sudo ls -lah /proc/1/exe
cat /proc/cmdline
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961418
Title:
snap failed to run with '/usr/bin/snap
Is this system using systemd as it's init system? I see that it was
originally installed with 10.04.1 which would not have been using
systemd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961418
Hi, can you share what version of snapd you have installed?
apt show snapd
snap version
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961418
Title:
snap failed to run with '/usr/bin/snap
Read-only access to /usr/local/doc seems fine to me, should be pretty
straight forward to extend the system-package-doc interface to also
allow this directory too, only question would be if it should instead be
a new interface like user-package-doc or something, but we can sort that
out in a PR I
Hi, this is a bug with the snap packaging of Firefox, not with snapd.
Please file a bug with Mozilla upstream at
https://bugzilla.mozilla.org/home
** Changed in: snapd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
On Impish 21.10, gnome-shell freezes up when trying to login,
specifically after I have typed in my password and hit enter. I have
seen this both when logging in after the display shuts itself off after
whatever the automatic timeout is, and also after manually locking the
Filed a PR with your suggestion:
https://github.com/snapcore/snapd/pull/11276
** Changed in: snapd (Ubuntu)
Status: New => In Progress
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Ian Johnson (anonymouse67)
--
You received this bug notification because you are a
This was introduced in https://github.com/snapcore/snapd/pull/11141
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958022
Title:
fish integration broken in focal
To manage notifications about this
apport-collect does not work on Ubuntu core
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954545
Title:
Cannot boot UC20 with
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- test ubuntu-20.04-64:tests/nested/manual/minimal-smoke:secboot_disabled is
flaky
+ Cannot boot UC20 with new kernel snaps with 384 MB in VM
--
You received this bug notification because you are a
The fix for that will be included in snapd 2.54.1 which is making its
way through the release process
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Fix Committed
** Changed in: snapd
Importance: Undecided => Medium
** Changed
Hi @bitterhalt, can you try installing the snapd snap via `snap install
snapd` and then see if your system is still affected? As Alberto
mentioned, we do expect this to be fixed now with the aforementioned
commit.
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in:
I mentioned this on the snapcraft forum, but /usr/share/local/ca-
certificates for a strict snap will come from the read-only, static base
snap of the chromium snap.
For classic ubuntu/debian systems running new enough snapd, we will
actually mount /etc/ssl from the host into the strict snaps'
** Summary changed:
- Allow reverting to older revisions of a snap
+ Ubuntu Server should have refresh.retain=3 set by default
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
** Changed in: snapd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification
@Marco, can you reproduce that behavior without creating the directory?
I.e. just start a new instance and then run `snap install hello` twice
and see if it works? AFAIK, that has always been the workaround of
choice is just running it twice initially for some reason...
--
You received this bug
Public bug reported:
While upgrading my Raspberry Pi 3 running 21.04 to 21.10, the upgrade
failed
ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-1011-raspi 5.13.0-1011.13
ProcVersionSignature: Ubuntu 5.11.0-1023.25-raspi 5.11.22
Uname: Linux 5.11.0-1023-raspi
So snapd doesn't support running inside privileged containers, so any
setup requiring snapd to do things in privileged containers is an
unsupported setup.
We have historically supported nesting however recently numerous things
changed there, 1) there was a lxd regression which broke nested
I filed it as a private bug because I wasn't sure how widely known it
was that this was exploitable, but sure if the security team thinks this
is a well-known issue that is good enough for me
** Information type changed from Private Security to Public Security
--
You received this bug
@slyon could you make available the core18 snap you built with this
systemd ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949089
Title:
systemd randomly fails to activate mount units in Ubuntu
You can set the number of revisions to keep with `snap set system
refresh.retain=`. The choice for Server is probably unfortunately a
victim of inheriting the default choice for Ubuntu Desktop, which is 2.
We originally had 3 for Desktop too (which is also still the default on
Ubuntu Core), but
Hi @axino, unfortunately I'm not aware of all the details of your
system, but if you do not have the desired snap revision available on
your system, then I can't advise on how you could get access to a
revision which works for your system. You could try reaching out to the
publisher to see if they
It is by design that you cannot revert to a snap that you do not already
have installed on a system.
You can try using `snap list ruby --all` to get all currently installed
revisions on your system (but note that only one revision can be
"active" at a time), the revisions listed by this command
Can you provide the output of running the following command:
journalctl --no-pager --no-hostname -b0 | grep audit
Thanks
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: snapd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944004
Title:
snapd.seeded.service never finishes on non-amd64
To manage
Dan, note that although we set the SNAP_REEXEC environment variable in
that integration test, that environment variable is actually not obeyed
when it comes to the mksquashfs command which is called here:
-proposed
and try to get that released to impish proper which will fix the issue.
If we can do it in time for the release even better.
** Changed in: snapd (Ubuntu)
Status: Fix Released => In Progress
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Ian Johnson (anonym
Also I'm not sure I agree with jdstrand's apparmor profile which
includes:
/run/snapd.socket rw,
which I don't think we want to grant to any PDF file opened with evince?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
John, the difference between those two that I can see is that now the
image was creating with cgroupsv2 present when preseeding (which was the
expected change), but the runtime image does not use cgroupsv2 and thus
things need to be regenerated.
This is sort of expected since the runtime kernel
As seb128 found, the issue is also affecting the debian package of snapd
since when we call mksquashfs, we actually have code which specifically
calls mksquashfs from the "system" snap which is either the snapd snap
or the core snap, this is presumably to ensure that a consistent
mksquashfs is
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945369
Title:
memory cgroup disabled on Ubuntu Core 18
To manage notifications
apport-collect is not available on ubuntu core
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945369
Title:
memory cgroup disabled on
Also an interesting datapoint is that on Ubuntu 21.04 Server on my pi,
the memory cgroup is enabled:
ubuntu@ubuntu:~$ cat /proc/cgroups
#subsys_namehierarchy num_cgroups enabled
cpuset 7 1 1
cpu 2 125 1
cpuacct 2 125 1
blkio 11 125 1
Public bug reported:
On Ubuntu Core 18, the memory cgroup is disabled, it seems that it needs
to be manually enabled. I was able to enable it by adding
`cgroup_enable=memory cgroup_memory=1` to the kernel command line, but
on Ubuntu I think the memory cgroup should be enabled by default
shouldn't
apport-collect doesn't work on Ubuntu Core
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945242
Title:
Failed to refresh to
@mwhudson I'm still not convinced that the udev noise is not the
problem, but another data point I just went ahead and got to prove this
is that when trying to seed another snap which uses interfaces and has
an install hook and is available on arm64, the docker snap, it fails the
"same" way with
** Changed in: snapd
Status: Incomplete => Confirmed
** Changed in: snapd
Importance: Undecided => High
** No longer affects: snapd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So some thoughts:
1. The root failure of snapd failing to finish seeding is that it is
trying to run `udevadm trigger --subsystem-nomatch=input` which ends up
dying on every write like so:
openat(AT_FDCWD, "/sys/devices/virtual/workqueue/writeback/uevent",
@fthx can you show the output of `snap changes` and `snap list
gnome-3-38-2004 --all` ? What I suspect made your firefox crash is that
the last revision of gnome-3-38-2004 that firefox was launched with was
garbage collected out of existence
--
You received this bug notification because you are
Hmm, actually though I cannot reproduce the specific crash/error on my
machine, I was running the firefox snap and I tried both refreshing
gnome-3-38-2004 from revision 61 -> 76 and the inverse of 76 -> 61, can
you describe how the crash happened? Did you do some specific thing in
firefox when the
Thanks for that information, for now I think that it is expected that
refreshes to dependency snaps are not blocked by active snaps using
those dependencies, but that is something I think we should explore
doing automatically.
We are actively working on hooks which snaps can implement manually
Hi, can you provide the output of
snap version
snap list
Thanks
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Incomplete
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
Ah Miguel, thanks for realizing my error, I should have probably just
said something like
sudo snap install snapd --edge; sudo snap refresh snapd --edge
which will ensure that it's always installed and gets refreshed.
--
You received this bug notification because you are a member of Ubuntu
@iogui, hmm it could be that our fix isn't working, can you show the
output of these commands:
snap version
snap list
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932579
Title:
snap pt_BR locale
@iogui could you try again? snapd on the edge channel may not have
finished building by the time you tried, but I see that there was an
update pushed out this morning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
To be clear you see this behavior with normal containers and not with
nested containers? Snapd doesn't support nested containers unfortunately
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944004
Can you show the output of `snap connections authy`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943853
Title:
Recent update DELETED SNAP PROGRAMS
To manage notifications about this bug go to:
The message should no longer be shown anymore in snapd as the PR
referenced by Maciej has been merged and should be available on the edge
channel of snapd in the few hours. Please give it a try if you like
with:
```
snap install snapd --edge || snap refresh snapd --edge
# test the snap command
Can you try rebooting your system to see if the snaps are remounted? it
seems like some of the snaps are not properly mounted and the easiest
way usually to fix that is to just reboot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For a snap that does not work can you run `snap run authy` in a terminal
window and show us the output?
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Incomplete
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
** Description changed:
- [ placeholder - release in progress ]
-
This is a new version of snapd.
The changelog is available here
https://github.com/snapcore/snapd/blob/2.52/packaging/ubuntu-16.04/changelog,
the raw git changelog is available here:
Public bug reported:
[ placeholder - release in progress ]
This is a new version of snapd.
The changelog is available here
https://github.com/snapcore/snapd/blob/2.52/packaging/ubuntu-16.04/changelog,
the raw git changelog is available here:
https://github.com/snapcore/snapd/commits/2.52 (note
** Changed in: snapd
Assignee: Zygmunt Krynicki (zyga) => (unassigned)
** Changed in: snapd
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773515
Title:
Can anyone share full logs from such a boot specifically the output of
`journalctl --no-pager` would be really helpful in diagnosing this
problem.
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Is this still reproducible with snapd 2.51?
** Changed in: snapd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757073
Title:
Snap stopped working
** Changed in: snapd
Status: Confirmed => Fix Committed
** Changed in: snapd
Milestone: None => 2.53
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940467
Title:
[snap] Nitrokey FIDO2
** Changed in: snapd
Status: In Progress => Fix Released
** Changed in: snapd
Milestone: None => 2.51
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919268
Title:
[snap] HyperFIDO Pro
This is because snapd's u2f-devices interface lacks this rule. See my
response here: https://forum.snapcraft.io/t/nitrokey-fido2-does-not-
work-with-chromium-snap/26098/2
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Confirmed
**
** Changed in: snapd (Ubuntu)
Assignee: Samuele Pedroni (pedronis) => Ian Johnson (anonymouse67)
** Changed in: snapd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
--
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
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
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.
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
** 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
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
> 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
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 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
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
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
** 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
** 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:
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
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
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
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
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
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
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.
** 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:
** Changed in: snapd
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive location
To
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Ian Johnson (anonymouse67)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849753
Title:
AppArmor profile prohibits classic snap f
There is a RFC PR from Jamie up here:
https://github.com/snapcore/snapd/pull/10029. We (snapd team) will try
to pick this up and get it merged when we have some time (hopefully
soon).
** Changed in: snapd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification
We have a fix in a PR:
https://github.com/snapcore/snapd/pull/10044
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Ian Johnson (anonymouse67)
** Changed in: snapd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a
FWIW I know what the snapd issue is, the issue is that snapd does not
and will not work in a nested LXD container, we need to add code to make
snapd.seeded.service die/exit gracefully in this situation.
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Hey Christian, thanks for taking a look at this, indeed this is somehow
confinement related and I can make it work by removing the apparmor
profile for the swtpm snap.
I guess I assumed that this bug was related to that since it had the
same exact error message and I definitely remembered doing
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474126/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912246
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474125/+files/lspci.txt
** Attachment removed: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474124/+files/prevboot.txt
--
You received
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:
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:
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"
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
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
** 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
1 - 100 of 289 matches
Mail list logo
