Mastodon: Static GIFs not displaying properly, saved as empty files

[duxovni]

Static GIFs (both local and federated) aren't displaying properly on my instance. Looking at the actual files saved on disk, the small versions of GIF attachments are fine, but the original versions are empty files.

---

• [x] I searched or browsed the repo’s other issues to ensure this is not a duplicate.
• [x] This bug happens on a tagged release and not on master (If you're a user, don't worry about this).

[ghost]

I can confirm this bug on my instance

[duxovni]

Still seeing this after upgrading to v2.2.0

[duxovni]

I'm running Debian stretch if that's relevant; @koyuawsmbrtn , are you also running something other than Ubuntu Server 16.04?

[ghost]

@sdukhovni I'm running Ubuntu Server 16.04

[Hanage999]

I have the same issue. I am not sure when the problem started. It still exists on the latest master (ef12a2b). My instance runs on an Ubuntu 16.04 virtual machine hosted by Parallels Desktop, and it is located behind Nginx reverse proxy. It means that proxy_pass to 127.0.0.1:3000 is changed to [ip address of a different node]:3000. I don't know if this makes any difference, though.

[ghost]

+1 here. Mastodon 2.4 on Debian Stretch.

Only static GIF's indeed. My first reaction is that it is some kind of Imagemagick conversion issue.

[Gargron]

People who use S3 storage (AWS, Minio, Wasabi) do not have this issue, I think it's something with file rewinding (and indeed it's only static GIFs that are affected)

[ghost]

@Gargron I can confirm I use local storage. How to fix this?

[Gargron]

As soon as I know I'll submit a fix, but it's not obvious to me. This happens in lib/paperclip/gif_transcoder.rb when non-animated GIF file is forwarded to the default paperclip processor.

[ghost]

@Gargron Do you need an example?