-
Notifications
You must be signed in to change notification settings - Fork 78
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
inline media preview broken since yesterday #395
Comments
I think I could reproduce this for a little while yesterday but not anymore, does it still happen for you? |
The "unrecognized file format" error is still present. The other ones are gone. |
For new media or only old one? Can you |
It still happens even after killing the cache dir |
Wait, we are talking about the current master version, right? |
Yes |
m( The easy short-term fix could be to just append another piece of information to the media path to differentiate them between quote tweets, but long-term we definitely want to just have an in-memory hashmap of the currently downloading files (and, well, maybe not save them to disk at all...). |
What about checking if a file already exists before downloading it? |
That would solve the error messages, but the second tweet would not get signalled when the files are successfully downloaded. |
Is there no way to pass the already downloaded file to the second tweet if both tweets require the same file? |
If the file is already downloaded: Yes. But that's not the interesting case. That should already work (and did in my tests) |
Okay, just made the inline media downloading not download the same file twice at the same time. There's also a unit test to ensure it works (and it does here). Can you make sure it also works for you? |
Okay, the only error-messages I get are:
|
After updating to lastest git-master I only get the following errors:
|
okay that one makes sense. So I can close this one and #271. |
Why? The images are still not displayed |
What images? In what case? Can you just give more inormation? |
BTW: I cleared the cache before starting corebird |
I can't reproduce that issue at all, I tried getting more people to test it but found exactly one who was willing to try and he couldn't reproduce it either. |
Okay, I tried again. Clearing the cache (rm -rf .cache/corebird/) and starting corebird from terminal and this time I only get the "unrecognized file format" error but still no inline preview. I'm running Fedora 23 beta. |
Hey, I don't know if I have exactly the same issue but since 2 or 3 days, I've got segmentation fault which seems to be caused by images:
Hope this help. |
Great, another crash I can only reproduce in a non-debug build. Also, seems like not using --enable-debug seems to reproduce the "no inline media shows up" issue(?) |
It's a corebird built from git, can I add some debug flags while compiling ? Is actually |
It's fine, I can reproduce it. Yes, |
Great, seems like there's some bug in gio/glib, but I don't know where since I don't have debugging symbols and as soon as I compile a version (either master or 2.44) in jhbuild and try that, the bug vanishes. |
Just FYI, I run corebird with glib 2.44.1 |
Just figured it out! It's a bug in gdk-pixbuf. And then I found out I wasn't the first one: https://bugzilla.gnome.org/show_bug.cgi?id=755269 m( This bug should've only been in gdk-pixbuf 2.32 and my local one is 2.31 though, so I'm not sure why it still segfaults... |
Correction: The bug is in 2.31.7 which I have locally installed and 2.32 contains a fix for it. |
Ha! I also have gdk-pixbuf 2.31.7 :) |
@HeikoAdams, can you confirm that gdk-pixbuf version? If you have the same, can you try to downgrade and try it again? |
I've version 2.32.0 |
Since gdk-pixbuf 2.32.1 on ArchLinux, problem fixed. |
Confirming that gdk-pixbuf 2.32.1 on ArchLinux fixes the problem. |
@HeikoAdams Is this stil broken for you? |
No, it seems to be fixed |
Since yesterday it looks like inline mediapreview is broken. When starting corebird from terminal I get the following errors:
The text was updated successfully, but these errors were encountered: