Since nobody in this thread either reported the bug or edited the wiki, I've at least done the former. https://gitlab.archlinux.org/archlinux/packaging/packages/nextcloud/-/issues... Would be nice if someone else fixes the wiki up. Martin On Sun, Jan 14, 2024 at 3:06 AM David C. Rankin <drankinatty@gmail.com> wrote:
On 1/13/24 01:17, Jaron Kent-Dobias wrote:
I had the same warning after upgrading Nextcloud, I made the same steps (installed and enabled sodium in php.ini, restarted php-fpm), and after a minute or so the warning vanished from the Nextcloud admin page. One big difference, however, is that I'm using php and not php-legacy.
Thank you,
Yes, there may be a naming issue with it finding php-legacy-sodium. It's happily running. Checking the phpinfo page:
sodium sodium support enabled libsodium headers version 1.0.19 libsodium library version 1.0.19
The warning does not go away with the install on php-legacy. I'm surprised you have it running on php (8.2). The whole reason I installed php-legacy was the Arch wiki page said there were problems with using php and suggested the downgrade.
Other than the annoying warning, everything is working fine, but the screen real estate issue got worse in Nextcloud 28 with fonts appearing bigger and sparse information per-page in each app. The upside is the page-load times switching apps (e.g. notes to calendar, etc...) are much improved. Not great, but definitely improved.
-- David C. Rankin, J.D.,P.E.