-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
RuntimeException: "There can only be one Talk backend" on upgrade #34919
Comments
cc @ChristophWurst Seems like apps are loaded/registered twice in the upgrade process, so the backend seems to be registered twice at the end. The server/lib/private/AppFramework/Bootstrap/RegistrationContext.php Lines 423 to 450 in 68d0038
|
For them we want to allow more than one. Hence the registration methods append to an array. For Talk we only expect to find one backend. Do you have a clue why apps register twice? That is what we have to fix |
Were you able to solve this? I added a cron task on the host machine (since I am running nextcloud-aio on docker) to install the spreed app at each reboot to solve it temporarily. @reboot /storage/homelab/system/nextcloud/enable_talk.sh The
|
Issue appeared on NC 26.0.0 upgrade
|
Also happen on NC 27 |
I also just hit this now with nextcloud 28. It only appears to be happening when the spreed/talk app is installed via the occ cli tool via |
I also just hit this now with nextcloud 29 |
I just hit the same issue with Nextcloud 30 as well yesterday.. Yes the |
How to use GitHub
Steps to reproduce
1.Upgraded from NC 24.0.6 to NC 25.0.1 RC1
Browser log
Server configuration
Operating system: Ubuntu/RedHat/...
Ubuntu 22.0.4
Web server: Apache/Nginx
Apache2
Database: MySQL/Maria/SQLite/PostgreSQL
MariaDb
PHP version: 7.4/8.0/8.1
8.1
Nextcloud Version: (see admin page)
25.0.1 RC1
Server log (data/nextcloud.log)
The text was updated successfully, but these errors were encountered: