Hello kinky nekoboi,
Am 01.12.2018 um 13:45 schrieb kinky_nekoboi:
> is there any progress on this?
no more progress that I am aware of, just tried to reproduce
and collect some information.
Kind regards,
Bernhard
Hello Bernhard,
thank you for your research and work,
is there any progress on this?
likely i have to test this patch on a VM too like, i dont want to mess
on my workstation at home with these patches.
best regards
kinky nekoboi
Am 23.11.18 um 22:15 schrieb Bernhard Übelacker:
> Dear Maintai
Dear Maintainer, hello Kinky Nekoboi,
just tried to reproduce this issue and there is really a crash.
In a minimal buster amd64 qemu VM,
with installed cantor and cantor-backend-sage packages.
Then follow these steps:
- start cantor
- select Sage backend
- enter in the field below the "Session 1"
Control: reassign -1 cantor-backend-sage
Please provide more information. How can the bug be triggered? I'm not familiar
with cantor. If someone can demonstrate that the segfault is really in sage,
the bug can be reassigned to sagemath.
Best,
Tobias
On 10/15/2018 03:34 PM, Kinky Nekoboi wrote:
Processing control commands:
> reassign -1 cantor-backend-sage
Bug #911084 [sagemath] sagemath crashes as cantor backend
Bug reassigned from package 'sagemath' to 'cantor-backend-sage'.
No longer marked as found in versions sagemath/8.3-3.
Ignoring request to alter fixed versions of bug #911084 to
Package: sagemath
Version: 8.3-3
Severity: serious
Justification: unkown
as above
cantor-sage-backend crashes with Segmentation fault.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-2-amd6
6 matches
Mail list logo