I got a very similar bug recently. I am using a rather big application
using the Qt4 backend for matplotlib on a debian testing distribution.
But after a full upgrade last Friday (December the 4th), I suddenly got
segfault everytime I was trying to display a matplotlib figure. After
searching a
severity 556943 minor
thanks
On Sun, Nov 22, 2009 at 14:03, Benjamin Drung wrote:
> Am Mittwoch, den 18.11.2009, 15:01 +0100 schrieb Teemu Ikonen:
>> >>> import matplotlib.pyplot as plt
>> >>> plt.plot([1,2])
>> Segmentation fault
>
> I enabled Qt4Agg backend and tried this example code without a
On Sun, Nov 22, 2009 at 2:03 PM, Benjamin Drung wrote:
> Am Mittwoch, den 18.11.2009, 15:01 +0100 schrieb Teemu Ikonen:
>> >>> import matplotlib.pyplot as plt
>> >>> plt.plot([1,2])
>> Segmentation fault
[...]
> Is your system up-to-date? Where there any PyQt4
> updates since you reported this bug
Am Mittwoch, den 18.11.2009, 15:01 +0100 schrieb Teemu Ikonen:
> >>> import matplotlib.pyplot as plt
> >>> plt.plot([1,2])
> Segmentation fault
I enabled Qt4Agg backend and tried this example code without an
segmentation fault in an up-to-date squeeze environment.
> This is could be a bug in pyth
Package: python-matplotlib
Version: 0.99.0-1
Severity: grave
Justification: renders package unusable
Matplotlib segfaults immediately when trying to create a plot with
the Qt4Agg backend enabled in matplotlibrc. Example:
>>> import matplotlib.pyplot as plt
>>> plt.plot([1,2])
Segmentation fault
5 matches
Mail list logo
