I was able to confirm the problem exists with snapd 2.56+22.10. I've
also confirmed that it works correctly with snapd from edge as some
fixes were landed in master already.
** Changed in: snapd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a
What is the version of snapd (both the deb and the snapd snap)? There
was a related fix in snapd introduced in
https://github.com/snapcore/snapd/commit/103c652f30089c81d69a89714fb5a076c94ed365
but it is available only in snapd 2.56 and later.
** Changed in: snapd (Ubuntu)
Status: New =>
Please make sure that you have xdg-desktop-portal installed, along with
xdg-desktop-portal-gtk (or xdg-desktop-portal-kde). The hardcoded list
of schemes is a legacy feature which should only be relevant for very
old systems such as 16.04 and should not be getting any updates.
--
You received
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
@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
Can you try running `sudo snap set system experimental.robust-mount-
namespace-updates=false` ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1914918
Title:
The snap being
@ostraaten does running `snap install teams-for-linux` fail for you? If
so, please file a bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1581713
Title:
Ubuntu Software
Probably needs more intricate knowledge of Chromium.
Just for the record, do you see any AppArmor denials when that happens?
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Incomplete
--
You received this bug
Public bug reported:
The hplip 3.17.10 version available in bionic is too old to support
recent low cost, consumer grade HP printers. For example, HP LaserJet
MFP M28 is supported only from hplip version 3.18.3 up. Meaning, the
current LTS release for widely available peripherals.
AFAICT,
Nonetheless it isn't clear whether it's a snapd problem or the actual
libraries. Switching to confirmed in snapd, but needs investigation from
desktop team too.
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
I've seen this happen occasionally with snaps on Arch too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-themes-extra in Ubuntu.
https://bugs.launchpad.net/bugs/1861558
Title:
Snap 'ed applicaitons have garbage on top of the
@sean
The snap command (part of snapd) takes care of
~/snap/packagename/current/, anything below (including .themes) is
handled by the actual snap package. I would look into desktop extensions
added by snapcraft.
--
You received this bug notification because you are a member of Desktop
Not sure whether removing files that came with distro packages is the
best idea long term. I think a better option would be to drop in a
custom rule that runs before the default ones. As usual ArchWiki has
some examples:
https://wiki.archlinux.org/index.php/Polkit#Administrator_identities
I looked at the policy used by PackageKit. I believe gnome-software uses
it as a backend, so can you try installing something that is
specifically not a snap?
At this point, all snapd does is ask PolicyKit whether given the policy,
the user can install a package. PolicyKit responds with yes,
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1850282
Title:
snap cannot be run while being upgraded − no user
** Changed in: snapd
Status: New => In Progress
** Changed in: snapd
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
** Changed in: snapd
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: snapd
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1840925
Title:
[snap] chromium doesn't start under Wayland
I could reproduce this problem using 18.04.3 live CD using Slack and
Atom. However, I don't think the problem is caused by snapd.
Slack, Skype and Atom are all classic snaps so they have full access to
the system. With Slack installed, clicking on the 'get started' link was
enough to get another
18 matches
Mail list logo
