Comment #34 , jjohansen ,
sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
worked for me amazingly and allowed me to start my viber 21.0.0.1 again!
Thank you a lot!
it started crashing after I upgraded my Linux package from 6.5.0-14.14 to
6.6.0-14.14 on Jan 05th and rebooted.
I am
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1008.8~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
azure-6.5/6.5.0-1007.7~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
azure-6.5' to
This is planned to be fixed in the apparmor package itself in mantic by
proving a suitable profile for chrome - something like the following in
/etc/apparmor.d/opt.google.chrome.chrome
abi ,
include
/opt/google/chrome/chrome flags=(unconfined) {
userns,
# Site-specific additions and
The workarounds here seem to work, but having to do them every time is a
bit annoying. Are there no new updates on the issue ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2017980
Title:
There's also an askubuntu question about this issue:
https://askubuntu.com/questions/1471028/fatalcredentials-cc127
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2017980
Relaying the information from
https://bugs.chromium.org/p/chromium/issues/detail?id=1459821 as it is
not publicly visible:
```
Hmmm this looks like
https://bugs.chromium.org/p/chromium/issues/detail?id=1365674#c8 again. I don't
know why using clone(CLONE_NEWUSER ...) would return EACCES (which
Update from
https://bugs.chromium.org/p/chromium/issues/detail?id=1459821 as it's
not public visible:
```
@Reporter, Thanks for filing the Issue. Please find the magic signature & stack
trace for the crash id# 8e7f32382b1ddc1c
Magic signature :
[Assert] sandbox::`anonymous
I had the same issue with kernel 5.19.0-1010-nvidia-lowlatency
Using the PPA:
deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
the --no-sandbox workaround works
After switching to non Nvidia kernel 5.19.17-051917-the issue has
disappeared
--
You received this bug
I tried to launch it with --no-sandbox, and we have this return :
#/usr/bin/google-chrome-stable --no-sandbox
[69134:69156:0704/101329.358591:ERROR:bus.cc(399)] Failed to connect to the
bus: Could not parse server address: Unknown address type (examples of valid
types are "tcp" and on UNIX
I did an check and can confirm that the chromium-browser as installed by
the usual 22.04 package is *NOT* affected.
But Google chrome well as google-chrome-beta installed by the PPA
deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
do show the bug.
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu.
** Also affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2017980
Title:
The problem seems to come from a wrong suggestion of Nvidia proprietary
driver packages, where Ubuntu logic (likely from the “ubuntu-drivers-
common” package) hints towards drivers that depend on a kernel stack
that’s not installed, which triggers those kernel installations as well,
because
** Summary changed:
- Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission
denied (13)
+ FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
15 matches
Mail list logo
