-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Talk Desktop is not running on Ubuntu 24 without AppArmor profile #588
Comments
According to your screenshot all files are owned by So if you run |
I tried it, but encountered another issue stating that the 'chrome-sandbox' needs to be owned by root and have mode 4755. Even after adjusting the ownership and permissions accordingly, I faced the same problem as before. |
Works pretty fine here, without being root. THat being said, on your screenshot |
I have the same problem. The issue there, is when Nextcloud is trying to use zygote_host_impl_linux.cc (library of chrome) but its not available due to permission so that's why it works in root but not in a regular user. Do we have to change the permission of that flie ? if so where is this file suppose to be located if its not static linked ? Our workaround there is simply to use the : |
Got the same problem after updating my working two test VMs to the new Ubuntu 24.04 LTS, currently in beta (no other changes). It seems to be related to the apparmor audit, here's the related dmesg log output:
Trouble ahead... The --no-zygote and --no-sandbox workaround works too. EDIT: Seems to be related to this (Ubuntu) upstream issue: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844 |
Unfortunately, we are still unable to reproduce the issue (but we haven't tried Ubuntu 24 yet). However, I have found some mentions of the error, and it seems it also happens with clean Chromium on some setups. So it could be a chromium compatibility issue in some environments.
We won't get rid of the sandbox mode because of security concerns. This is not a solution. |
The solution is to add a AppArmor profile. Ubuntu 24.04 comes with a lot of new profiles for applications that needs the unprivileged_userns capability, there is even one for other Electron applications like Signal-Desktop. It's time to add an flatpak installer/ RPM|DEB package for Nextcloud Talk Desktop with a proper installation location and AppArmor profile. Here's my working profile:
I've installed it to /opt/ and chowned it to root and chmodded the chrome-sandbox to 4755 too. |
Another temporary solution can be:
So if the file is owned by root and has 4755 permissions it works. |
I too was having the same issue on my Ubuntu 24.04 system. I tried to change the ownership of chrome-sandbox and it did not help. it also caused another one of the programs i use to stop working (Logos10 Bible software) I had to do a timeshift back so I could get back into Logos because I need it today and Talk is just something I would like to have. I am glad you are doing it. and By the way I have this on my Debian 12 based T100 and it works great. I will definitely try to get it to work again. |
You need to change owner and the permissions (in the right order) |
i run into this same issue, i tried @nickvergessen's suggestion but that doesn't seem to work:
|
hmmm granted my original error message is
|
hmm this seems to be an issue with electron v5 electron/electron#17972 |
this allows it to launch for me now: |
looks like electron is looking into how to fix it: electron-userland/electron-builder#8635 |
We don't use |
oh, tho i guess their template could be used to create our own apparmor profile. not that i have managed to get it working, but i suspect that's on my configuration |
🚧 Temporary workaround
After unpacking the files run the following 2 commands:
How to use GitHub
Steps to reproduce
Expected behaviour
Launch Nextcloud
Actual behaviour
but we can't use 'sudo'
Desktop client
Talk Desktop client version: v1.26.0
Operating system: Ubuntu
Operating system version: Ubuntu 20.02
Microphone available: yes/no
Camera available: yes/no
Server
Nextcloud version: (see status page:
/status.php
)Talk app version: (see apps admin page:
/index.php/settings/apps
)Custom Signaling server configured: yes/no and version (see additional admin settings:
/index.php/index.php/settings/admin/talk#signaling_server
)Custom TURN server configured: yes/no (see additional admin settings:
/index.php/settings/admin/talk#turn_server
)Custom STUN server configured: yes/no (see additional admin settings:
/index.php/settings/admin/talk#stun_server
)Logs
Client log
The text was updated successfully, but these errors were encountered: