search

IsmaelMartinez / teams-for-linux

Unofficial Microsoft Teams for Linux client
GNU General Public License v3.0
2.95k stars 240 forks source link

FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) #1401

Closed chWagnr closed 2 months ago

chWagnr commented 2 months ago

Describe the bug Teams for Linux does not start. Getting this error when calling from terminal: 

[303386:0910/165234.028885:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Trace/breakpoint trap (core dumped)

To Reproduce Steps to reproduce the behavior:

  1. Open Terminal
  2. enter 'teams-for-linux'
  3. See error

Expected behavior Teams for Linux should start/open

Desktop (please complete the following information):

Additional context Since the upgrade from Ubuntu 22.04 to 24.04.1 this error message occurs. I removed (purge) the package, installed different versions or rename the .config folder with no success.

IsmaelMartinez commented 2 months ago

I think this is an OS issue. Checking on stackoverflow seems to indicate is some sort of issue with your root/user permissions.

You will probably have more luck asking in there tbh.

https://stackoverflow.com/questions/76165512/fatalcredentials-cc127-check-failed-permission-denied-13-trace-breakpo

(and this post).

Hope helps. Closing as it is not app related.

chWagnr commented 2 months ago

@IsmaelMartinez thank you

setting kernel.apparmor_restrict_unprivileged_userns=0 worked

IsmaelMartinez commented 2 months ago

Glad to hear and thanks for sharing what worked for you. That can help others in the future. Cheers!

Varuna3656 commented 1 week ago

@IsmaelMartinez thank you

setting kernel.apparmor_restrict_unprivileged_userns=0 worked

This works only once for me. After restart again you'll have to do run this command

IsmaelMartinez commented 1 week ago

Have you check if the apparmour solution in https://github.com/IsmaelMartinez/teams-for-linux/issues/1426 works for you? This is a Ubuntu change that is affecting all Electron apps, not only us. Creating an apparmour profile for the app should solve your problem going forward.