Looking at my local deployment (epoxy branch), the permissions I have on
the directory differ from yours (see below). We are going to need
answers to the above questions to investigate further. If you are
building a custom image with tools other than those provided by
OpenStack, you may need to cor
There have been a number of changes in HAProxy around the external
checks support, so this could be caused by a number of issues.
Can you provide:
Where you got the amphora image?
What OS is being used in the amphora image?
What version of Octavia are you running?
What version of HAProxy is inside
I am by no means a Linux expert but given this information I was able to
get it working on my 24.04 install by doing the following:
#Remove if installed already from package manager
sudo apt remove python3-pyvmomi
#Install latest version
sudo apt install unzip
wget https://github.com/vmware/pyvm
Journal log from 4 Jan 2025
** Attachment added: "250104-journal.txt"
https://bugs.launchpad.net/ubuntu/+bug/2088416/+attachment/5849464/+files/250104-journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Problem related to the nouveau driver.
when right clicking the sub menu flickers, after a few times the system freezes.
I can't find a compatible driver.
david@david-ThinkPad-T510:~$ inxi -G
Graphics:
Device-1: NVIDIA GT218M [NVS 3100M] driver: nouveau v: kernel
Device-2: Lenovo Integrated Web
On Wed, 2024-12-18 at 09:16 +, Daniel van Vugt wrote:
> Thanks for the bug report. Next time the problem starts, please run:
>
> journalctl -b0 > journal.txt
>
> and attach the resulting text file here.
>
>
> ** Tags added: multimonitor nvidia
>
> ** Package changed: xorg (Ubuntu) => ubu
On Wed, 2024-12-18 at 09:16 +, Daniel van Vugt wrote:
> Thanks for the bug report. Next time the problem starts, please run:
>
> journalctl -b0 > journal.txt
>
> and attach the resulting text file here.
>
>
> ** Tags added: multimonitor nvidia
>
> ** Package changed: xorg (Ubuntu) => ubu
On Wed, 2024-12-18 at 09:16 +, Daniel van Vugt wrote:
> Thanks for the bug report. Next time the problem starts, please run:
>
> journalctl -b0 > journal.txt
>
> and attach the resulting text file here.
>
>
> ** Tags added: multimonitor nvidia
>
> ** Package changed: xorg (Ubuntu) => ubu
xtracted old grandad Windows XP machine,
hand-built in Billingshurst, and can get basic Email and some news
sites, but no YouTube at all, and Ebay thinks I am a bot, nowt else.
Please advise if I need a virus-check, or a recovery CD/USB or whatever.
Many thanks, Geoff. Johnson
Email: johns...@y
PS: not sure if this is sent from this old XP machine, usually does a
review first.
Also: after five duff printers, I will be looking at an Epson Eco-tank after
Christmas.
Hope one of those will work with Linux. Cheers.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
It says that mirrors are overloaded
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.23 [origin: unknown]
ProcVersionSignature: Ubuntu 6.8.0-48.48-generic 6.8.12
Uname: Linux 6.8.0-48-generic x86_64
NonfreeKernelModules: nvidia_modese
Public bug reported:
- I have a laptop that I connected two additional monitors to. 1, via USB C,
and the 2nd via HDMI output.
- At some point, the USB C connected monitor froze. The monitor was still
responsive and working normally, but the image on it did not change according
to input / move
Here is a patch for 24.04 (noble). It has been a long time since I've
done any *buntu dev work so I'm sure I screwed something up. If not,
great here is a patch, otherwise let me know what I screwed up or feel
free to tweak/improve it. I just finished testing this and now I can
connect to an old Op
Public bug reported:
I attempted to resume my laptop after closing the lid, and found the
following on the screen:
spd5118 1-0050: Failed to write b = 0: -6
spd5118 1-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
spd5118 1-0050: PM: failed to resume async: error -6
Required a
I had this issue, and thankfully the above suggestions got it - almost -
working on latest Kubuntu 24.04.1 (KDE 5.27.11). However shortcuts don't
show up and thus I am not able to issue any tiling commands, even after
enabling the tiling checkbox.
--
You received this bug notification because you
I have the same issue:
"I cannot geht Ansible Modules from community.vmware to work because of
module 'ssl' has no attribute 'wrap_socket'"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065876
Title
Still an issue in Ubuntu 24.04.1, sheesh! FWIW, also occurs on Ubuntu
Budgie 24.04.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532508
Title:
Screen contents revealed briefly on resume, before
Public bug reported:
Automatic reporting provided by software
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-firmware 20240318.git3b128b60-0ubuntu2.2
ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
Uname: Linux 6.8.0-41-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Arch
In my case, the installer allowed me to remove postgres-14 and complete
the upgrade. Then once running on 24.04 I wondered where my database had
gone. I found the new database postgres-16 on port 5433 but my data was
on the old cluster without a recent backup. The process is clear to me
now, but it
My bad, it looks like the new install is using a different folder inside
.mozilla. So it didn't remove it, not the entire folder anyways, but it
was accessing it and saving to it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Edit: It was until I uninstalled it anyways. When I uninstalled it, it
also removed my .mozilla folder. So thanks? If it can't access it why
is it accessing it? Why is it removing it when it isn't part of the
snap?
For anyone wanting firefox without snap,
https://linux.how2shout.com/how-to-
I don't have much to add to what has already been said, but to break
apps on purpose is ridiculous. To force someone to use a broken package
app... Why do we even need snap? Apt-get works just fine. It's just
ridiculous. Fix Firefox and quit forcing snap, Firefox has no problem
accessing my ho
I filed a bug report at the following URL:
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11797
** Bug watch added: gitlab.freedesktop.org/drm/i915/kernel/-/issues #11797
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11797
--
You received this bug notification because you
I have some updates.
First, I tried kernel 6.10., as @AaronMa requested. Same result. I'll
try filing a bug report via the link Aaron provided.
Second, now that the 6.8 kernel has been backported to Ubuntu 22.04, I
can now safely say that this bug affects the good ol' Jammy Jellyfish as
well. If
For some reason, adding "intel_iommu=off" to my boot parameters seems to
help. I've been using the computer for almost an hour, and haven't had
any crashes yet. Also, I think my HW Specs file disappeared, so I guess
I'll have to re-attach it.
--
You received this bug notification because you are
** Attachment added: "lshw output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073648/+attachment/5798810/+files/hwinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073648
Title:
Public bug reported:
This bug seems to affect kernels "6.8.0-31-generic", "6.8.0-38-generic",
and "6.9.0-0906000-generic". Every single time I try to log into Xorg
(Cinnamon DE + LightDM greeter), the computer freezes within seconds.
IDK whether there is a kernel panic or not, as I can't do anythi
Public bug reported:
I'm trying to upgrade a test partition from Linux Mint 21.x to Mint 22.
Unfortunately, I can't because libc6:amd64 refuses to install. I get the
following errors:
dpkg-divert: error: cannot divert directories
Use --help for help about diverting files.
dpkg: error processing a
Public bug reported:
upgrading from 22.04 LTS to 24.04 LTS threw this error on my Landscape
server
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: rabbitmq-server 3.12.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-113.123-generic 5.15.152
Uname: Linux 5.15.0-113-generic x86_64
ApportVe
** Description changed:
qemu will not start VMs using spice or vnc displays unless there is a
routable IPv4 address on the machine, even though the error relates to
127.0.0.1
root@athens:~# ip addr
- 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default
- link/loopback 00:00
Public bug reported:
```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
OFFLOAD_TAR
upper-constraints was updated in yoga to 2.1.0, so yoga forward this
issue is resolved.
** Changed in: designate
Status: Confirmed => 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/
Night Light was previously working on my hybrid Nvidia laptop before the
recent changes that switched Wayland to X11. I manually switched back to
Wayland, but now Night Light is not working.
Why are the changes that caused these bugs not being rolled back?
--
You received this bug notification b
To clarify, all future installs with hybrid Nvidia graphics will now
default to Wayland? So users won't have to work around this issue by
manually selecting Wayland in the log in screen? Cannot expect the
average user to figure this out.
I am unclear why this bug was not rolled back once it was id
I'm also experiencing the Out of Memory error on a fresh install of
Ubuntu Server 22.04 on an Intel NUC BXNUC10i5FNK1 with 8GB of memory.
After pressing any key it boots to a kernel panic stating not syncing
VFS, unable to mount root fs.
--
You received this bug notification because you are a mem
** Changed in: snapd
Assignee: Ian Johnson (anonymouse67) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902748
Title:
ubuntu-seed / ubuntu-boot partition detection could
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 bec
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 d
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, wh
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: sn
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
Tit
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 t
Public bug reported:
I have several Dell Laptops model Precision 5520. Ubuntu LTS 20.04.2
seems to run fine without issues. After do a software update which
appears to update to LTS 20.04.3, the laptops no longer boot properly. I
end up at a black screen with an underscore cursor blinking at the
Public bug reported:
happened when doing auto updates to ubuntu linux
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3
ProcVersionSignature: Ubuntu 5.4.0-97.110-generic 5.4.162
Uname: Linux 5.4.0-97-generic x86_64
NonfreeKernelModules: wl
ApportVe
Just did a fresh install of 20.04.3 LTS, updated & installed linux-
generic-hwe-20.04 and it booted up just fine. Only difference is
/etc/default/grub on a client's appliance, this is the default/grub on
the machine that freezes:
# If you change this file, run 'update-grub' afterwards to update
#
Same thing, hardware is an Intel NUC NUC10i5FNK. OS: Ubuntu Server
20.04.3 LTS. Kiosk machine, when I select 5.13.0-28 to boot, it just
freezes at loading ramdisk. 5.11.0-46-generic works just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
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 s
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
scr
I believe I'm having the same/similar issue. I cannot shut down or
restart my system unless I hold the power button to force shut down.
I've tried using two different terminal commands in order to shut down
the system, those being `sudo shutdown now' and '$ poweroff'.
Both commands end with the s
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 n
** 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
And with Ubuntu 21.10, it's gotten worse.
The "Executable Text Files" preferences is gone. The dconfg property
executable-text-activation is gone. Double clicking still opens the file
in gedit.
But at least "run as a program" was added to the right-click menu, so
that's good, I guess?
--
You re
The fix for that will be included in snapd 2.54.1 which is making its
way through the release process
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Fix Committed
** Changed in: snapd
Importance: Undecided => Medium
** Changed in
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: s
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' mou
** 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 becau
I also encountered this issue, Ubuntu 21.10. Workaround proposed by
Mario Di Nicola (warp99) worked for me as well (editing the python
script to import GTK 3.0).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Created attachment 144195
New crash information added by DrKonqi
gwenview (21.08.1) using Qt 5.15.2
- What I was doing when the application crashed:
1. used darktable to create a jpg from nef
2. opened jpg with showfoto (success, including metadata)
3. attempted to open jpg with gwenview, immed
@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 n
Public bug reported:
While upgrading my Raspberry Pi 3 running 21.04 to 21.10, the upgrade
failed
ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-1011-raspi 5.13.0-1011.13
ProcVersionSignature: Ubuntu 5.11.0-1023.25-raspi 5.11.22
Uname: Linux 5.11.0-1023-raspi aarch64
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
contain
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 notificati
@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 Co
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 tha
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 ar
Public bug reported:
I couldn't able to update the packages.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: grub-common 2.04-1ubuntu26.13
ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp
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.
Yes, that is what I am asking about.
The configuration setting:
[coordination]
backend_url =
Such that the threads are using the distributed lock manager.
You can also look for this warning message:
https://github.com/openstack/designate/blob/05343d4226822da8b9776201ea18e000d366573d/designate/
** 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 not
Dan, note that although we set the SNAP_REEXEC environment variable in
that integration test, that environment variable is actually not obeyed
when it comes to the mksquashfs command which is called here:
https://github.com/snapcore/snapd/blob/dfba7de59a41bc22786d87f53b20deea14240713/snap/squashfs
-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.
https://bug
Additional helpful insights from osmoticum on the Nvidia forum:
The Xorg modesetting DDX seems to be fighting with the Nvidia DDX for
DRM nodes
[ 463.657] (II) modeset(G0): using drv /dev/dri/card0
but
[ 463.658] (II) Applying OutputClass "nvidia" options to
/dev/dri/card0
Nvidia appears t
John, the difference between those two that I can see is that now the
image was creating with cgroupsv2 present when preseeding (which was the
expected change), but the runtime image does not use cgroupsv2 and thus
things need to be regenerated.
This is sort of expected since the runtime kernel is
As seb128 found, the issue is also affecting the debian package of snapd
since when we call mksquashfs, we actually have code which specifically
calls mksquashfs from the "system" snap which is either the snapd snap
or the core snap, this is presumably to ensure that a consistent
mksquashfs is used
** 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 ab
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
me
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
Created attachment 141971
New crash information added by DrKonqi
gwenview (20.12.3) using Qt 5.15.2
- What I was doing when the application crashed:
This seems to happen reliably on jpg's produced by darktable.
Darktable-rendered pics all cause the crash. These were all NEF (Nikon)
raw processe
apport-collect doesn't work on Ubuntu Core
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945242
Title:
Failed to refresh to pi-
Will new media be available w/ this fix in place?
I ask because running "dkms status" or any dkms command presently
triggers this bug for me, and the only way forward I can see to being
able to fix that system is new media w/ a patched kernel.
--
You received this bug notification because you ar
@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 ud
** Changed in: snapd
Status: Incomplete => Confirmed
** Changed in: snapd
Importance: Undecided => High
** No longer affects: snapd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
So some thoughts:
1. The root failure of snapd failing to finish seeding is that it is
trying to run `udevadm trigger --subsystem-nomatch=input` which ends up
dying on every write like so:
openat(AT_FDCWD, "/sys/devices/virtual/workqueue/writeback/uevent",
O_WRONLY|O_NOCTTY|O_NOFOLLOW|O_CLOEXEC)
@fthx can you show the output of `snap changes` and `snap list
gnome-3-38-2004 --all` ? What I suspect made your firefox crash is that
the last revision of gnome-3-38-2004 that firefox was launched with was
garbage collected out of existence
--
You received this bug notification because you are a
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
whi
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 becaus
Ah Miguel, thanks for realizing my error, I should have probably just
said something like
sudo snap install snapd --edge; sudo snap refresh snapd --edge
which will ensure that it's always installed and gets refreshed.
--
You received this bug notification because you are a member of Ubuntu
Bugs
@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.
https://bugs.launch
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
Tit
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:
h
1 - 100 of 4682 matches
Mail list logo
