Le mardi 01 avril 2014 à 13:39 -0400, Mike Miller a écrit :
> On Tue, Apr 1, 2014 at 19:26:12 +0200, Sébastien Villemot wrote:
> > Le mardi 01 avril 2014 à 10:57 -0400, Mike Miller a écrit :
> >
> >> This bug affects all Octave users plotting with fltk, which is now the
> >> Octave default, and who
On Tue, Apr 1, 2014 at 19:26:12 +0200, Sébastien Villemot wrote:
> Le mardi 01 avril 2014 à 10:57 -0400, Mike Miller a écrit :
>
>> This bug affects all Octave users plotting with fltk, which is now the
>> Octave default, and who are using the free LLVM-based graphics drivers
>> for AMD and NVIDIA
Le mardi 01 avril 2014 à 10:57 -0400, Mike Miller a écrit :
> This bug affects all Octave users plotting with fltk, which is now the
> Octave default, and who are using the free LLVM-based graphics drivers
> for AMD and NVIDIA cards, the VMware virtual GPU, or the swrast driver.
> Upgrading severi
Control: severity -1 important
On Tue, Apr 01, 2014 at 00:56:53 -0400, Mike Miller wrote:
> On Tue, Apr 01, 2014 at 00:48:38 -0400, Mike Miller wrote:
> > Octave segfaults when plotting anything with the fltk toolkit when
> > Octave is built with JIT and when using one of the Gallium llvmpipe Mesa
On Tue, Apr 01, 2014 at 00:48:38 -0400, Mike Miller wrote:
> Octave segfaults when plotting anything with the fltk toolkit when
> Octave is built with JIT and when using one of the Gallium llvmpipe Mesa
> drivers for direct rendering. JIT does not have to be enabled in Octave
> for the crash to occ
Package: octave
Version: 3.8.1-1+b1
Severity: normal
Octave segfaults when plotting anything with the fltk toolkit when
Octave is built with JIT and when using one of the Gallium llvmpipe Mesa
drivers for direct rendering. JIT does not have to be enabled in Octave
for the crash to occur. This is p
6 matches
Mail list logo
