Bug#963975: blender: Blender crashes on launch (failed assert)

[Antonio Ospite <ao2@ao2.it>]

On Mon, 29 Jun 2020 15:34:36 +0100
Ben Morris <bugs@benmorris.org.uk> wrote:

> Package: blender
> Version: 2.83.1+dfsg-1
> Severity: grave
> Justification: renders package unusable
> 
> Blender 2.83.1+dfsg-1 is crashing on launch with the output shown below. I have
> tested this with and without an existing ~/.config/blender/ directory.
> 
> $ blender
> blf_load_font_default: 'fonts' data path not found for 'droidsans.ttf', will
> not be able to display text
> blf_load_font_default: 'fonts' data path not found for 'bmonofont-i18n.ttf',
> will not be able to display text
> blf_load_font_default: 'fonts' data path not found for 'bmonofont-i18n.ttf',
> will not be able to display text

This is one bug, probably due to some changes in where blender expects
the default fonts, which breaks assumptions in a debian-specific patch,
see:
https://github.com/blender/blender/commit/68e341e9d59ae917eba992591f4f60660f6c58ff
https://github.com/blender/blender/commit/d7514914894e9c96c9eab21fb625a2021aaa71cb

> blender(BLI_system_backtrace+0x33) [0x55751863b4b3]
> blender(BLF_default+0x1c) [0x55751851eddc]
> blender(+0x18262bb) [0x5575168382bb]
> blender(ED_time_scrub_draw+0x1af) [0x5575165eab8f]
> blender(+0x184943d) [0x55751685b43d]
> blender(ED_region_do_draw+0x841) [0x55751656e911]
> blender(wm_draw_update+0x4ba) [0x55751620f4ba]
> blender(WM_main+0x30) [0x55751620d3c0]
> blender(main+0x2b8) [0x557515ee36c8]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f0c01ea0e0b]
> blender(_start+0x2a) [0x557515f303ba]
> BLI_assert failed:
> /build/blender-l5zyJy/blender-2.83.1+dfsg/source/blender/blenfont/intern/blf.c:185,
> BLF_default(), at 'global_font_default != -1'
> Aborted
> 

The crash by itself is another issue with asserts, probably similar to
what reported in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962074

I will hopefully have a fix for both soon.

Ciao,
   Antonio

-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?