I was referring to Julian comment which stated df can't ignore this.
If you don't want to this fuse fs to be created then either remove xdg-
desktop-portal package or mask xdg-document-portal.service with:
systemctl --user mask xdg-document-portal.service
--
You received this bug notification
You can silence this with "df -x fuse.portal"
xdg-desktop-portal isn't tied to flatpak.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal in Ubuntu.
https://bugs.launchpad.net/bugs/1905623
Title:
df:
Does it happen on every start or maybe it happened once during snap
refresh?
--
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/1864127
Title:
apparmor denies ~/snap/chromium/
The "denials on /sys/devices/virtual/dmi/id/sys_vendor and product_name"
will be fixed in next snapd release (2.43.4?):
https://github.com/snapcore/snapd/commit/3ad3e7fbba13721eeaab8dd85a5640316b1c1606
The "ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with
multiple threads in process
This module is purely optional and lack of it doesn't cause any harm.
You may ignore this message.
--
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/1862062
Title:
[snap]
"chromium-browser/xenial-updates 78.0.3904.70-0ubuntu0.16.04.2 amd64
[upgradable from: 77.0.3865.120-0ubuntu1~snap1]"
xenial is ubuntu 16.04. It seems that you have mixed repos from
different ubuntu versions and chromium deb from older version overwrote
version from 19.10. Kixing repos from
"note that all snaps today actually use XZ compression, not LZMA."
xz = LZMA2 ( https://tukaani.org/xz/ ) which I guess is what was
referenced above.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
It's not possible to install non-classic snap (like chromium) with
--classic switch.
You can get access to /media/$USER/ through removable-media
interface which you have to manually connect to chromium snap.
https://snapcraft.io/docs/removable-media-interface
--
You received this bug
I can confirm that if "personal-files" slot isn't connected and
"~/.chromium-browser.init" exist then chromium snap fails to start.
The solution is to either connect "personal-files" slot or delete
"~/.chromium-browser.init" (arguably it's pointless to have this file if
access is blocked).
The "proper fix" may never arrive because sandboxing is core feature of
snaps and blocking access to dotfiles is inherent part of sandbox. So
from snap perspective your workflow is invalid.
There are two solutions: adjust your workflow or abandon chromium snap.
It's up to you what you choose.
--
Snaps don't have access to dotfiles in your home dir (anything in
~/.xxx).
The solution for you is to use ~/server instead of ~/.server as mount
point.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
This bug is fixed upstream. Can we get backport to bionic?
https://gitlab.gnome.org/GNOME/glib/issues/1271#note_352412
https://gitlab.gnome.org/GNOME/glib/merge_requests/365
https://gitlab.gnome.org/GNOME/glib/merge_requests/366
--
You received this bug notification because you are a member of
Public bug reported:
Chromium can use two different techniques to sandbox itself:
- SUID sandbox
- User namespaces sandbox
User namespaces sandbox is preferred way and SUID sandbox is considered
as legacy. Debian have to use SUID sandbox because they disable
unprivileged user namespaces but
Public bug reported:
After setuid bit was removed from default installation in cosmic (and
soon in bionic) the description doesn't match actual behavior anymore:
"setuid wrapper for unprivileged chroot and namespace manipulation"
** Affects: bubblewrap (Ubuntu)
Importance: Undecided
I just wanted to point out that after dropping setuid bit the package
description is now wrong.
"setuid wrapper for unprivileged chroot and namespace manipulation"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bubblewrap in Ubuntu.
To add to above: https://www.thunderbird.net/en-
US/thunderbird/60.0/releasenotes/
> Thunderbird version 60.0 is only offered as direct download from
thunderbird.net and not as upgrade from Thunderbird version 52 or
earlier. A future version 60.1 will provide updates from earlier
versions.
This
16 matches
Mail list logo