- User Since
- Jun 9 2015, 11:00 AM (106 w, 4 d)
Sat, Jun 17
Fri, Jun 16
We're going to push this one to devel for the Beta and note in the README in the directory:
Thu, Jun 15
@huffray That build had a known issue that is fixed in the next revision to be pushed (fixed in 2.6.6 linux, but that is actually a slightly newer version with the patch).
Tue, Jun 13
I was able to do a print with 2.6.6 on Debian Stretch.
Mon, Jun 12
I did a patchlet around line 205:
May affect T939
May affect T939
To clarify: it looks like a USB connection is getting established. But the print isn't kicking off. It isn't looking for the wrong device, or not finding it or anything like that, afaict.
AFAICT, this isn't a USB issue, but a gcode issue.
May 5 2017
Apr 30 2017
Mar 31 2017
Mar 17 2017
This is all I found about Cura2 referenced in Fedora's bugzilla:
Ah, the first Stretch workstation was still using the Jessie repos, as it was upgraded to Stretch before the AO Stretch repos existed. So using the correct AO Stretch repo and the correct .deb works now. Doh!
I do have it working on another stretch workstation, so I'll see what the differences are. They have the same numpy and python versions.
Mar 14 2017
Do we want this?
That comment was something I wrote a week ago, but then checked out and it resizes with STL, but not gcode, afaik. But phab kept my text when I re-assigned it. Anyway, I don't think it resizes with gcode automagickally.
I'm pretty sure the current version resizes for the bed automagically.
Mar 10 2017
No other numpy is installed.
Same error with cura-2.4.20-devel.
Mar 7 2017
cj, ya, it would be great if you could build against the -devel branch, which has USB in it.
Mar 6 2017
Version 2.4.14-devel, fails thusly on launch, under Debian Stretch.
Linux spoonbill 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux
In karrad's dmesg:
Do you have a way to trigger it 100% of the time? If so, what steps?
Mar 1 2017
Sounds good, go for it.
Ok, I'll take you off this one then.
Victor, it isn't working in the final build, so we'll need to fix it in the build system if it is working fine on your builds. Alexei?
Feb 28 2017
T699 better covers this bug.