Open muckelba opened 1 year ago
The weird thing is: the original file is located at /background.jpg with 185696 bytes, but the failed file located at /var/www/html/apps/theming/background/background.jpg has 145524 bytes and is not even readable by a photo viewer. So i'm not sure whats happening here.
We store custom backgrounds in data/appdata
no there so not sure how yours ended up there.
I can't reproduce this. If you remove the mysterious file then re-run your reproduction steps, does the file re-appear there?
Also, do you have a background
file located in <datadirectory/appdata_<instanceId>/theming/global/
?
⚠️ This issue respects the following points: ⚠️
Bug description
I've followed the docs on how to configure theming with
occ
and set a background image, but after doing that the integrity check fails because of a new file:The weird thing is: the original file is located at
/background.jpg
with 185696 bytes, but the failed file located at/var/www/html/apps/theming/background/background.jpg
has 145524 bytes and is not even readable by a photo viewer. So i'm not sure whats happening here.Note: I'm running Nextcloud in Kubernetes, installed with the official helm chart.
Steps to reproduce
su -p www-data -s /bin/sh -c "php occ theming:config background /background.jpg"
Expected behavior
The integrity check should not fail.
Installation method
Community Docker image
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response