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
Segmentation fault on Blender appdata #337
Comments
And here's the backtrace:
|
I'm mad busy with RHEL 8 at the moment, but I'd gladly merge a PR if you can see the bug :) |
The issue occurred on the latest stable version of Blender 2.8.2 as well. |
Because upstream Blender didn't fix their appdata in that release, only in master. As @hughsie said he was too busy to work on this, and as I didn't say this is way above my C proficiency, so you can see there was no fix in appstream-glib either and this issue is still open. Even if appstream-glib didn't segfault, the upstream appdata would still be invalid, so if this is blocking your Fedora build you need to patch it manually, as I do for Flathub. |
Noted. Manual patch applied. |
I'm trying to update Blender in Flathub, and
appstream-util
crashes on the new appdata:While that's probably a problem with the appdata being invalid, it would be much better if it could handle it gracefully and report the failure.
The problem happens because the new file has a
<p>
tag inside a<ul>
tag in its<release>
-><description>
:The text was updated successfully, but these errors were encountered: