I've opened a related PR to the firefox snap which replaces the
problematic interface with system-files
https://github.com/canonical/firefox-snap/pull/53
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I was able to reproduce this with 22.04, snapd 2.61.1. This is what is
reported by findmnt:
```
maciek@vm:~$ findmnt
TARGETSOURCE
FSTYPE OPTIONS
/ /dev/vda2
I had to downgrade my Ubuntu Server to older 20.04 LTS (kernel 5.15) in
order to be able to use my NAS.
** Attachment added: "journalctl_b_1-20240128.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032120/+attachment/5748895/+files/journalctl_b_1-20240128.log
--
You received this
This was fixed in https://bugs.launchpad.net/snapd/+bug/1823974 and
released in 2.51
** Changed in: snapd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I believe a problem addressing snap-failure and snapd has been fixed a
couple of releases back. Should the problem persist, please leave a
comment.
** Changed in: snapd (Ubuntu)
Status: New => Fix Released
** Changed in: snapd
Status: Triaged => Fix Released
--
You received this
** Also affects: snapd-desktop
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762072
Title:
Indicator icons not loading for certain snap applications
To
** Also affects: snapd-desktop
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874660
Title:
Please make an "update in progress" message for snap updates
Do you still experience the problem? If so, can you collect the output
of:
snap list --all
I understand it has been a while since this had happened, but should
this happen again, please collect the output of the journal (journalctl
--no-pager preferrably).
** Changed in: snapd (Ubuntu)
Is this still an issue? 2.38 and 2.42 are very old releases. I'm going
to set this to incomplete. Please leave a comment if you still
experience the problem.
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
** Changed in: snapd
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961791
Title:
2.54.3+21.10.1ubuntu0.1 broke Plasma Desktop when Fish is the default
shell
** Changed in: snapd
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907056
Title:
Please add meta/kernel.yaml
To manage notifications about this bug go to:
AFAIU support for pulling in dtbs from the kernel snap is already in
snapd. We've recently also fixed a problem with AppArmor profile that
blocked access to the GPU device, perhaps that's related. The PR that
contains the fix is https://github.com/snapcore/snapd/pull/11822
--
You received this
Can you please pull the latest pi kernel and gadget from 20/stable,
snapd from edge and verify if things are working for you?
** Changed in: snapd
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On top of what Alberto already requested, please provide the output of:
udevadm info /sys/class/video4linux
and
udevadm info /dev/video*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968878
Device 0:0 and devpath /class/video4linux do not look right. I suspect
that the udev rules generated by the camera interface are too broad and
they catch /sys/class/video4linux as well as the actual devices.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Can you attach the contents of /etc/os-release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971955
Title:
systemd-udevd call unshare process when attaching nvme volume
To manage notifications
@eurbah hi, also for the service in question, can you attach the output
of `systemctl list-dependencies --after snap..service`
AFAICT, all services are to be started after snapd.apparmor.d, which in
turn is started after apparmor.service, which should ensure that
apparmor profiles are loaded
(In reply to Emilio Cobos Álvarez (:emilio) from comment #7)
> How does this compare to the portal service that was recently added for
> Flatpak and so on? Do we really need both?
Portal service is a limited API for Flatpak containers that internally
forwards to Geoclue. Without Flatpak runtime
By the way, WebKitGTK got Geoclue2 support already.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100326
Title:
Location requested by websites should be able to use GPS/mobile
positioning
To
Created attachment 9275622
Bug 1063572 - Geoclue2 geolocation provider. r=emilio
Add a Geoclue (version 2) geolocation provider.
This way Firefox can make use of multiple location sources present in the
system, from GNSS provided by a cellular modem or the current network to
location based on
For the record, does /usr/bin/unshare exist in your system? Can you run
the command that Alberto provided in the console?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971955
Title:
systemd-udevd
** Changed in: snapd (Ubuntu)
Status: In Progress => Fix Committed
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Fix Committed
** Changed in: snapd
Milestone: None => 2.56
--
You received this bug notification because
Are there any denials being logged? Anything in dmesg?
Did you move the extracted snap binaries to a container?
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Seems like a low hanging fruit, so I opened a PR to snapd:
https://github.com/snapcore/snapd/pull/11776
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972910
Title:
error: too many arguments for
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Maciej Borzecki (maciek-borzecki)
** Changed in: snapd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
AFAIU this happens when appamor.service is disabled and does not start
during the boot or there is no apparmor profile for snap-confine. Can
you make sure that `systemctl show apparmor.service` shows that it's
enabled, and attach the output of `sudo aa-status |grep snap-confine` ?
** Changed in:
I suspect this was caused by udev reload, which we have observed
previously and I believe it was fixed in gdm by
https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/175
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
It works ! ^_^ :D nice, thanks ! :D
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942624
Title:
NVMe devices fail to probe due to ACPI power state change
To manage notifications about this bug go
FWIW systemd --user is expected to have been started as part of your
session. This is supposed to be fully automatic. I don't think you can
start it yourself, as it's up to systemd/logind to properly start the
process and move it to the right cgroup. I've added systemd to the bug
report, so maybe
@n.buechner no, that's a different problem, most likely:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961898 although in your
case it hit a 25s and still did not get a response from systemd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for reporting this. Do I understand correctly that you have moved
the content to /var/lib/snapd and bind mounted that location on top of
the original path?
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
It appears that the same version of apparmor parser (2.13.3 as reported
by Simon), behaves differently when running in the container.
Specifically, the command that snapd also executes did not fail in the
container, while it should have. Actually there's even an error message
but the exit code is
Let me reiterate what I mentioned in the MM channel. The snap in
question apparently uses device access in which case we'll set up device
filtering. The host being impish, uses cgroup v2, which percolates to
the container. Since it's v2, device filtering is implemented by
attaching a BPF program
I pulled a clean 20.04 cloud image VM from https://cloud-
images.ubuntu.com/focal/current/
root@ubuntu:/home/guest# grep PRETTY /etc/os-release
PRETTY_NAME="Ubuntu 20.04.4 LTS"
root@ubuntu:/home/guest# uname -a
Linux ubuntu 5.4.0-104-generic #118-Ubuntu SMP Wed Mar 2 19:02:41 UTC 2022
x86_64
@alexmurray that code has never listed or show which application would
handle given URL scheme. The change affected the implementation of
io.snapcraft.Launcher, which is only called as a fallback when a snap
calls xdg-open inside it's namespace. The primary handler that is tried
goes through the
@ytvwld I have 2.54.3+20.04.1ubuntu0.2 version:
```
guest@ubuntu:~$ dpkg -l snapd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
@takeseem unfortunately due to a bug in LP I cannot access the image.
Can you rename the image to use latin characters only and upload it
again?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839237
If this happens again try running `SNAPD_DEBUG=1 snap run telegram-
desktop` and collect the log. Since 22.04 is using unified hierarchy, we
try to ask your session's systemd to create a transient scope for it. In
your case, the log indicates that this operation failed. Looking at the
log:
Feb 23
** This bug is no longer a duplicate of bug 1957948
2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function
`fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1957948 ***
https://bugs.launchpad.net/bugs/1957948
Indeed, I may have acted to fast marking this as a duplicate of the
other bugs. The problem is somewhat related to the other bugs in that
both go down to fish shell snapd setup and how fragile the desktop
@gsunipipeline it looks like systemd does not operate correctly in your
system. This is a prerequisite for even accessing the snapd daemon,
since we rely on systemd to provide the socket, then activate snapd
daemon, and the snapd daemon directly interacts with systemd to set up
snaps.
** Also
Does running `systemctl status` work at all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961418
Title:
snap failed to run with '/usr/bin/snap wait system seed.loaded'
To manage notifications
@lukeweller you probably guessed this is not part of any release yet.
Documentation will be there in due time. In the meantime you're welcome
to contribute to the discussion in the forum or grab snapd from edge and
try it out yourself.
--
You received this bug notification because you are a
@lukeweller 3 commens up there's:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1575053/comments/308
there's also a forum topic with more details:
https://forum.snapcraft.io/t/experimental-flag-for-hiding-snap/28509
--
You received this bug notification because you are a member of Ubuntu
This should work even for fish 2.7:
https://github.com/snapcore/snapd/pull/11416 Anyone wants to give it a
try?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961365
Title:
2.54.3+18.04.2ubuntu0.1
Yes, sorry my bad. Fish in bionic is even older, and thus requires more
contrived workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961365
Title:
2.54.3+18.04.2ubuntu0.1 update on bionic
*** This bug is a duplicate of bug 1957948 ***
https://bugs.launchpad.net/bugs/1957948
** This bug has been marked a duplicate of bug 1957948
2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function
`fish_add_path` which requires fish 3.2 or later (Impish only packages
*** This bug is a duplicate of bug 1957948 ***
https://bugs.launchpad.net/bugs/1957948
** This bug has been marked a duplicate of bug 1957948
2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function
`fish_add_path` which requires fish 3.2 or later (Impish only packages
*** This bug is a duplicate of bug 1957948 ***
https://bugs.launchpad.net/bugs/1957948
** This bug has been marked a duplicate of bug 1957948
2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function
`fish_add_path` which requires fish 3.2 or later (Impish only packages
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Confirmed
** Changed in: snapd
Assignee: (unassigned) => Maciej Borzecki (maciek-borzecki)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
One more fix for fish https://github.com/snapcore/snapd/pull/11371 seems
to work in Focal VM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957948
Title:
2.54.2+21.10 introduces a call in
*** This bug is a duplicate of bug 1957948 ***
https://bugs.launchpad.net/bugs/1957948
** This bug has been marked a duplicate of bug 1957948
2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function
`fish_add_path` which requires fish 3.2 or later (Impish only packages
> I wonder if we should make an exception for "~/.local/" or
"~/.local/share/", though, since that generally contains data which
could potentially be useful for applications.
I think that's risky. Off the top of my head ~/.local/share/Trash is
where files go when you remove then in Nautilus, or
The error indicates that snapd is still in the process of early init &
setting up device. Ideally it's enough to wait for seed.loaded event,
(snap wait system seed.loaded). This is what snapd.seeded.service does,
but from the piece of log you provided, the service did not start,
because its
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957948
Title:
2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish
*** This bug is a duplicate of bug 1957948 ***
https://bugs.launchpad.net/bugs/1957948
** This bug has been marked a duplicate of bug 1957948
2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function
`fish_add_path` which requires fish 3.2 or later (Impish only packages
This was fixed in https://bugs.launchpad.net/snapd/+bug/1957155 which so
far is available only in snapd master.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957948
Title:
2.54.2+21.10 introduces
*** This bug is a duplicate of bug 1951491 ***
https://bugs.launchpad.net/bugs/1951491
2022/01/10 12:58:44.388636 tracking.go:185: DEBUG: using session bus
2022/01/10 12:58:44.393780 tracking.go:290: DEBUG: StartTransientUnit failed
with "org.freedesktop.DBus.Error.Spawn.ChildExited":
Please attach the output of `SNAPD_DEBUG=1 snap run chromium-browser`.
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956942
Title:
No, it just means that the journal is not collecting any user session
logs. I'm afraid this is beyond snapd scope at this point. Perhaps you
can try to make you openbox session to be more like what GNOME and KDE
set up, that is with systemd user instance that can be accessed via
dbus. I don't know
Ok, so the logs you attached earlier are:
2021/12/03 15:21:45.540312 tracking.go:45: DEBUG: creating transient scope
snap.chromium.chromium
2021/12/03 15:21:45.543273 tracking.go:185: DEBUG: using session bus
2021/12/03 15:21:45.547127 tracking.go:290: DEBUG: StartTransientUnit failed
with
Valentin has 2 PRs up to address this on the snapd/core20 side:
https://github.com/snapcore/snapd/pull/9 and
https://github.com/snapcore/core20/pull/124
** Changed in: snapd
Assignee: (unassigned) => Valentin David (valentin.david)
** Changed in: snapd
Status: Confirmed => In
Can you run `systemctl --user`? Does it work at all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't run snaps: .slice/session-1.scope is not a snap cgroup
To manage
Snapd needs to talk to systemd user instance to setup a scope for the
snap. This is done over a session bus.
Is DBUS_SESSION_BUS_ADDRESS set in your environment? Run `echo
$DBUS_SESSION_BUS_ADDRESS`, the output should be like
`unix:path=/run/user/NNN/bus` (where NNN is your uid). Can you then run
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't run snaps: .slice/session-1.scope is not a snap cgroup
To manage
Can you run `SNAPD_DEBUG=1 snap run firefox` and attach the output?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951491
Title:
Can't run snaps: .slice/session-1.scope is not a snap cgroup
To
You can collect a strace of the app by running:
snap run --strace='-vf -s 256' cura-slicer.cura
And yes, as @alexmurray indicated, this may be something with device
cgroups. The problem with those is there is nothing logged if access is
denied, making the debugging process complicated.
I do have a Geoclue2 geolocation provider for gecko-dev right now and
have been using it in Firefox for a few weeks now.
This provider is purely (G)D-Bus based, so it doesn't need any additional
external library as a dependency.
I envision it as a system-wide geolocation source, much like the
Can you run `sudo systemctl restart apparmor.service
snapd.apparmor.service` and see if that fixes your problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947203
Title:
Snap applications
I see this in the attached journal:
Oct 14 22:53:56 audit[1790]: AVC apparmor="DENIED" operation="open"
profile="snap-update-ns.lxd" name="/proc/1790/cgroup" pid=1790 comm="5"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Which is unexpectd as reading own /proc//cgroup is allowed by the
There don't appear to be any AppArmor denials in the logs provided. From
snap debug seeding output, looks like the command `udevadm trigger
--subsystem-nomatch=input` failed when invoked during installation of
the snapd, which was done outside of confinement.
--
You received this bug
Possibly related: https://github.com/systemd/systemd/issues/3388
** Bug watch added: github.com/systemd/systemd/issues #3388
https://github.com/systemd/systemd/issues/3388
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Observed on 18.04. Systemd user instance fails when trying to create a
transient scope when logged in through ssh as a regular user
Specifically this fails:
$ systemd-run --user --scope ls
Job for run-rc78f932ad730440490bd7bc17f9d5c8c.scope failed.
See "systemctl status
** Changed in: snapd
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934147
Title:
systemd leaks abandoned session scopes
To manage notifications about this bug go to:
** Changed in: snapd
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925507
Title:
grub-common: snapd autopkgtests fail on s390x
To manage notifications about this bug
Any chance you could collect the journal logs from 2021-09-16. I think
this command should provide the output: `journalctl --since 2021-09-16
--until 2021-09-17`.
I'm switching this bug to Fix Committed, as we landed a fix to not loose
connections if the snaps happen to be unavailable and it was
Please attach the output of `snap list --all`, and then the output of
`snap connections libreoffice`.
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The PR is up: https://github.com/snapcore/snapd/pull/10839 also needs +1
from security
** Changed in: snapd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks to @mwhudson for arranging access to the test host. Per his
comments I launched both 20210903 and 20210904 snapshots of impish.
Debugging, I noticed that there was an apparmor denial logged when snap
(the snap binary from snapd) was transitioning to snap-confine. While
snap-confine runs
Adding SNAP_CONFINE_DEBUG=1 in the env will produce more debugging
output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944004
Title:
snapd.seeded.service never finishes on non-amd64
To manage
I suspect that for gimp and chromium you need to run those again, but
swap authy for either "gimp" or "chromium":
sudo snap connect authy:gnome-3-28-1804 gnome-3-28-1804
sudo snap connect authy:gtk-3-themes gtk-common-themes:gtk-3-themes
sudo snap connect authy:icon-themes
At least to get authy back you can try running the following commands:
for iface in browser-support desktop desktop-legacy gsettings home network
opengl unity7 wayland x11; do sudo snap connect authy:$iface system; done
sudo snap connect authy:gnome-3-28-1804 gnome-3-28-1804
sudo snap connect
This doesn't look right. Can you attach the output of `snap changes`. If
there is a change that has an error status, can you also attach the
output `snap change ` for each one? IDs are in the leftmost column
in snap changes output.
--
You received this bug notification because you are a member
Can you attach the output of `snap connections` and `snap list`
commands?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943853
Title:
Recent update DELETED SNAP PROGRAMS
To manage notifications
We also have a change in snapd source code that will no longer show
these messages: https://github.com/snapcore/snapd/pull/10756
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932579
Title:
snap
** Changed in: snapd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920754
Title:
FTBFS and autopkgtest failure in hirsute
To manage
I do not see this problem with snapd-2.49.2+20.04 installed from the
archive. Please check on you system after running an update.
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: snapd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925810
Title:
Bashism in snapd.sh (aka apps-in-path.sh) breaks dash
To
Waiting until unit snap-gnome\x2d3\x2d34\x2d1804-66.mount is stopped [attempt
19]
Running in chroot, ignoring request: is-active
Waiting until unit snap-gnome\x2d3\x2d34\x2d1804-66.mount is stopped [attempt
20]
Running in chroot, ignoring request: is-active
Removing snap gnome-3-34-1804 and
segfault happens in `go tool compile` process
** Also affects: golang (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snapd (Ubuntu Impish)
Status: New => Won't Fix
** Changed in: snapd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification
AFAIU the extra line in the output (libgcc_s.so.1 must be installed for
pthread_cancel to work) appears when mksquashfs is invoked as squashfs-
tools is missing a dependency on libgc-s1 (previously libgcc1).
** Also affects: squashfs-tools (Ubuntu)
Importance: Undecided
Status: New
**
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889067
Title:
Error logging in snapd: (most recent call last): (snapd-error-quark,
10)
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889318
Title:
install chromium in lxc container for 20.04 fails
To manage notifications
Public bug reported:
While we are validating the FlexRAN on Ubuntu 20.04 with Low-Latency
kernel one of the long-run stability tests failed, looking for your
comments/support in understanding the problem. At this point, we
believe, some additional platform/OS level fine turning is required for
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930179
Title:
Advantech CAN driver not recognized in Ubuntu Core 20
To
The kernel is provided by a kernel snap which is most commonly a rebuilt
deb. Which kernel are you referring to?
Is the driver part of the mainline kernel? I'll let whoever maintains
the right kernel sprek, but I'm doubtful we can include a random driver,
with unclear licensing.
** Changed in:
Public bug reported:
I cant install apt packet
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.6
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_77
** Summary changed:
- Cannot upgrade to LTS 20.10
+ Cannot upgrade to LTS 20.04
** Description changed:
lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
-
- When I attempt to update to LTS 20.10 I get an unspecified error.
+ When I attempt to update to LTS 20.04 I
Public bug reported:
lsb_release -rd
Description:Ubuntu 18.04.5 LTS
Release:18.04
When I attempt to update to LTS 20.10 I get an unspecified error.
apt log:
cat apt.log | grep Broken
Broken dpkg:amd64 Breaks on libapt-pkg5.0:amd64 < 1.6.13 @ii mK > (< 1.7~b)
Broken
5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu61
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: maciej 1315 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: maciej 1315 F pulseaudio
1 - 100 of 830 matches
Mail list logo
