1)
user_name@computer:~$ stat /home/department/user_name/
File: /home/department/user_name/
Size: 267 Blocks: 289IO Block: 16384 directory
Device: 27h/39d Inode: 9542Links: 146
Access: (0755/drwxr-xr-x) Uid: (X/user_name) Gid:
(/default_group)
Ac
Reverting snapd fixes it for me too on multiple computers.
--
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/2061981
Title:
chromium fails to start with non-standard home direct
I don't have an encrypted home directory (though it is on a ZFS
filesystem, but that one is also NOT encrypted).
W.
--
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/2061981
Titl
PS: Can't revert as I uninstalled and reinstalled chromium yesterday
when I first encountered the problem.
user_name@computer:~$ sudo snap revert chromium
error: cannot revert "chromium": no revision to revert to
--
You received this bug notification because you are a member of Desktop
Packages,
user_name@computer:~$ snap connections chromium | grep personal-files
personal-fileschromium:chromium-config
:personal-files -
personal-fileschromium:dot-local-share-applications
:personal-files -
personal-filesc
*** This bug is a duplicate of bug 1620771 ***
https://bugs.launchpad.net/bugs/1620771
As far as I can tell, snap and apparmor home directories are set
correctly:
user_name@computer:~$ sudo snap get system homedirs
[sudo] password for user_name:
/home/department/
user_name@computer:/home$ su
*** This bug is a duplicate of bug 1620771 ***
https://bugs.launchpad.net/bugs/1620771
Not a duplicate
It's specific to the latest chromium snap update: it worked fine last week.
(using chromium only for specific sites. The firefox-esr PPA is my daily
driver).
Other snaps don't have this pr
Public bug reported:
chromium 123.0.6312.122 2821 latest/stablecanonical
cannot update snap namespace: cannot expand mount entry (none
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-
dir=$HOME 0 0): cannot use invalid home directory
"/home/department/user_name": permissi
** Also affects: mesa (Debian)
Importance: Undecided
Status: New
** Also affects: mesa (Fedora)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.
Public bug reported:
GLX apps fail to run on Ubuntu LTS 22.04. They used to run fine on
Ubuntu LTS 20.04
USER@COMPUTER:~$ glxgears
X Error of failed request: GLXUnsupportedPrivateRequest
Major opcode of failed request: 143 (GLX)
Minor opcode of failed request: 17 (X_GLXVendorPrivateWithRep
Public bug reported:
do-release-upgrade from bionic (18.04) to focal (20.04) crashes on
chromium snap installation
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: chromium-browser 101.0.4951.64-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 5.4.0-113.127~18.04.1-generic 5.4.181
Uname: Li
Public bug reported:
do-release-upgrade from 20.04 to 22.04
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libreoffice-common 1:7.3.2-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181
Uname: Linux 5.4.0-110-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
Ap
A 'backport' of "nvidia-340_340.106-0ubuntu3_amd64.deb" from Bionic should do
the trick as this is fixed by NVidia in nvidia-340.106:
http://www.nvidia.com/Download/driverResults.aspx/130042/en-us
"Release Highlights: Fixed a compatibility problem between the nvidia.ko's Page
Attribute Table (PAT
13 matches
Mail list logo
