Hi,
same problem here: segfault on blender start. I sent that report
to the blender package:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963203
Same problem with openscad, btw:
Jun 21 19:21:47 bob kernel: openscad[31289]: segfault at a0 ip
14bd1303b9b8 sp 7ffd5c895a30 error 4
Control: reassign -1 libgl1-mesa-dri
On 2018-01-24 at 23:29 (+0100), Rob van den Berg wrote:
[...]
> so, where to report the bug ?
Given the file involved, I'd say against libgl1-mesa-dri package.
Doing so for you. Hope this helps.
Cheers.
--
Matteo F. Vescovi || Debian Developer
GnuPG
yeah, seems like the videocard
got a backtrace (couldn't install blender-dbg btw :?: )
```
Thread 1 (Thread 0xa4fbf840 (LWP 13412)):
#0 0xa4c63257 in ?? ()
#1 0x99793148 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#2 0x997936df in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#3
Control: severity -1 important
Control: tag -1 + moreinfo unreproducible
Hi!
On 2018-01-24 at 22:41 (+0100), Rob van den Berg wrote:
[...]
> output of /tmp/blender.crash.txt
> # Blender 2.79 (sub 0), Unknown revision
>
> # backtrace
> blender(BLI_system_backtrace+0x37) [0x19ca067]
>
Package: blender
Version: 2.79+dfsg0-3+b2
Severity: grave
Justification: renders package unusable
output of /tmp/blender.crash.txt
# Blender 2.79 (sub 0), Unknown revision
# backtrace
blender(BLI_system_backtrace+0x37) [0x19ca067]
blender(+0xabb637) [0xf44637]
5 matches
Mail list logo
