Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stable version 3.6.0 fails to slice #55

Closed
neildarlow opened this issue Nov 27, 2018 · 18 comments

Comments

@neildarlow
Copy link

commented Nov 27, 2018

It appears that the latest Cura stable packaging at version 3.6.0 contains a cura-engine package at version 3.4.1.

When you attempt to slice a STL file there is no activity reported on the slicing progress bar and the UI remains at Slicing...

The AppImage of the same version works correctly.

Tested on Linux Mint 19 Cinnamon Edition.

@neildarlow

This comment has been minimized.

Copy link
Author

commented Nov 27, 2018

List of available packages shown by Synaptic. Note the highlighted cura-engine version.

cura-3 6 0-packages

@thopiekar

This comment has been minimized.

Copy link
Owner

commented Nov 27, 2018

Good catch. I missed to update the protobuf package.
Triggered to build package for the stable PPA. Should be fixed soon.

@thopiekar

This comment has been minimized.

Copy link
Owner

commented Nov 28, 2018

Currently blocked because of this:
Ultimaker/Cura#4900

@Nihlus

This comment has been minimized.

Copy link

commented Nov 28, 2018

Is there a way to roll back to the previous version? I'm not seeing any previous versions in the PPA.

@thopiekar

This comment has been minimized.

Copy link
Owner

commented Nov 28, 2018

@neildarlow

This comment has been minimized.

Copy link
Author

commented Nov 28, 2018

@Nihlus Until this is resolved you can use the AppImage download from Ultimaker. This is what I am currently doing.

@thopiekar Does a comparison of the stable and master build recipies provide any clues? Could be another added dependency?

@thopiekar

This comment has been minimized.

Copy link
Owner

commented Nov 28, 2018

@neildarlow Well, I tried to build the engine in the master PPA (so all dependencies should be the same), but ended out with the same error. Thus, there must be something with the code released as 3.6.
I mean since the stable PPA is broken anyways now, I can just build the engine from master and see what happens. If it runs, then we have something working at least.
So then all code will be 3.6, but the engine will be newer with the needed fix.

What do you think?

@neildarlow

This comment has been minimized.

Copy link
Author

commented Nov 28, 2018

@thopiekar That sounds reasonable provided we can drop back to stable once things settle. Newer dependency versions in Master could impact that. It is worth trying.

@thopiekar

This comment has been minimized.

Copy link
Owner

commented Nov 28, 2018

The engine is there. Can you update and see whether it works?

@neildarlow

This comment has been minimized.

Copy link
Author

commented Nov 28, 2018

Slicing starts and gets to about 50% then stops. Not successful unfortunately.

@thopiekar

This comment has been minimized.

Copy link
Owner

commented Nov 28, 2018

:(

@Nihlus

This comment has been minimized.

Copy link

commented Nov 29, 2018

Yeah, same here. Is it possible for you to keep one or two older versions in the PPA in the future, so we can avoid lockups like this?

@thopiekar

This comment has been minimized.

Copy link
Owner

commented Nov 29, 2018

Well, I never had these unexpected problems before.
Making this sure would mean that I would have to create another stable PPA for backup. As a consequence this would mean more maintenance and more work.
However, I don't have the time for this and actually need to spend more time on the plugins right now.

@Nihlus

This comment has been minimized.

Copy link

commented Nov 29, 2018

@thopiekar

This comment has been minimized.

Copy link
Owner

commented Nov 29, 2018

@tobie-de-beer

This comment has been minimized.

Copy link

commented Dec 20, 2018

I managed to get all the 3.4 files I needed from the apt cache to get 3.4 up and running again.....

@thopiekar

This comment has been minimized.

Copy link
Owner

commented Dec 20, 2018

Great, I will probably update it soon to the 4.0 beta due to the issues here.
Has anyone tried the ETA, which is currently in the master PPA?

Thanks!

@thopiekar

This comment has been minimized.

Copy link
Owner

commented Dec 26, 2018

Updated to 4.0 - better having a beta, then non-working software.

Merry Christmas!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.