I’m running Nextcloud AIO - version Nextcloud Hub 26 Winter (33.0.5)
Since the last update , my pdf’s no longer have icons.
Not a huge thing, but definitely a bug - I sure didn’t change anything.
I just uploaded a pdf, and sure enough, there is an error in the log at the time:
Exceptionfclose(): supplied resource is not a valid stream resource in file ‘/var/www/html/custom_apps/richdocuments/lib/Service/RemoteService.php’ line 72
So yeah, bug. Dev team, please?
The fix for that was merged a couple of hours ago: https://github.com/nextcloud/richdocuments/pull/5781
I guess the next update of richdocuments will bring the fix.
Thank you for the heads-up!
Hi guys,
Does anyone know if the problem has been fixed in Version 33.0.6 yet?
Best regards!
The fix will be in the app richdocuments.
You have to wait until a new release of that app with the fix is pushed to the app store
(it needs to be > 10.2.0 for NC 33 and > 11.0.0 for NC 34).
What about NC 32? I saw that the automatic backport to NC 32 failed. See GitHub:
main ← nicfab:fix/guard-fclose-converted-stream
offen 03:54PM - 11 Jun 26 UTC
## Summary
Fixes #5743
`convertFileTo()` opens a raw stream and passes it … to `convertTo()`, which hands it to the Guzzle-based HTTP client as the multipart request body. Guzzle wraps it in a PSR-7 stream and closes the underlying resource once the request has been sent. By the time the `finally` block runs, the resource is no longer valid, so `fclose()` logs a warning on every conversion — one per generated preview/thumbnail.
Since Guzzle takes ownership of the stream and `convertTo()` already handles request errors, this PR drops the redundant try/finally block entirely and returns the conversion result directly, as discussed in the review below.
## Testing
The removal of the explicit cleanup has been discussed in the review; the original symptom and its diagnosis were validated independently by multiple users in #5743 on different stacks (Nextcloud 32/33, richdocuments 9.1/10.2, MariaDB/PostgreSQL, Ubuntu/Debian, Collabora 25.x/26.x): conversions and previews keep working as expected and the warning is no longer logged.