Collection of feedback and bugs around the stable PPA (no support for master PPA!)

gazhay commented 8 years ago

Seeing as I wasn't clear and the last bug I reported was closed....

You cannot install any of the newer DEBs on Ubuntu16.04 because cura depends on an older version than the default one shipped in UBUNTU16.04.

Even forcing the install sees cura installed, but crashes on launch with python errors.

I had a previous version installed before the upgrade, and it has stopped slicing since the upgrade. "Show slicer log..." does nothing, so I can only assume it is also a python related error.

thopiekar commented 8 years ago

What is actually the problem? Do you get an error when trying to install the DEB found on Ultimaker's homepage? Please make a screenshot of that error dialog or take a terminal and run sudo dpkg -i <path to DEB>. This will often return a more useful error message than the most GUI tools.

Thanks

thopiekar commented 8 years ago

Ah, now I remember. The problem is that there is no Python 3.4 on Ubuntu 16.04 anymore. There are two different solutions:

Make a mixed installation using apt-pinning. There are instructions on the internet which give you instructions (often for Debian) how to do that. In our case we need to add Ubuntu Wily again with a low priority. So when you tell to install Cura it will install Python 3.4 from Wily because there is no Python 3.4 on Xenial. All the other packages won't be affected as APT will always try to take dependencies from Xenial as possible (and like we want here.)
Another alternative: Install Cura from my personal PPA (unsupported by Ultimaker). For this go to https://launchpad.net/~thopiekar/+archive/ubuntu/cura and follow the instructions. All stable releases of Cura will land there. Currently I'm using another PPA built on the master codebase, so I won't notice if there are problems in the stable PPA. So just report problems here, but don't for get to say that you are using my PPA! Oh, and don't forget to uninstall (purge) the old cura package by Ultimaker before using my PPA.

Feel free to give feedback about your experience here :wink:

Ghostkeeper commented 8 years ago

We're having trouble upgrading to Python 3.5 due to the Windows build. It needs to compile Python plug-ins with a more modern version of Visual Studio that is not working properly with Qt.

gazhay commented 8 years ago

thopiekar, thanks, I tried your repo but unfortunately I'm stuck using older versions of cura as I have a delta printer (Dreammaker overlord) and cannot configure it for cura 2.

Slicing did start happening again in 15.02 but hasn't persisted across reboots.

Thanks for your help

thopiekar commented 8 years ago

Oh, I'm sorry about that. Maybe you can take your time and try to convert the settings for your printer which come with 15.02 to the latest cura (aka master). Just take a look at the available JSON files, make first changes and create a pull request. Then you can discuss with the developers there about missing parameters, etc.

No problem and best regards :wink:

BerndJM commented 8 years ago

Please excause this maybe stupid question, but I'm quite a greenhorn in using PPA's. I've seen there was a update today but the version is still 2.1.0.... where the official beta is 2.1.1 Could you please enlighten me about this?

thopiekar commented 8 years ago

I simply didn't increased the version number. But you can find the build date/time on the launchpad page. It is even appended to the version number, I guess. So everytime I update the code hosted at launchpad with GitHub (sadly have to do this manually) a build is triggered.

So in short: The packages say they are 2.1.0, but in truth they come with 2.1.1. 😉

BerndJM commented 8 years ago

Thank you for clearing up. So I can be sure that occuring bugs are "actual" bugs :-))

thopiekar commented 8 years ago

Yes, I hope so :smile: The only difference between the .deb provided by Ultimaker and my PPA is that:

All dependencies, like Qt5, etc. and Uranium, libArcus, etc. are provided in one *.deb as an software bundle. My PPA provides all dependencies separated into different packages. So e.g. the installed Qt5 libraries provided by Ubuntu are used and not another copy (BUT: the one provided in Ultimaker's .deb is tested and known to work well).
Ultimaker's .deb comes with a Updater Plugin, which notifies you about new updates, but this plugin is removed in my PPA as APT should do this job very well (as long as I update the codebase on launchpad).

So in case of bugs, don't forget to mention that you are using my PPA :wink:

PS: I updated the version of my packages now.

awhiemstra commented 8 years ago

So e.g. the installed Qt5 libraries provided by Ubuntu are used and not another copy (BUT: the one provided in Ultimaker's .deb is tested and known to work well).

One thing to note here is that there is a known issue with PyQt < 5.6 where destruction of QML items will trigger a deadlock in PyQt. This is one of the reasons why we ship our own version of Qt these days.

thopiekar commented 8 years ago

@BerndJM I noticed that the splash screen still shows "master" on 2.1. I made a little addition to the packaging files, so the package version, here 2.1.2 will be shown instead.

The PR I added is not needed for me actually anymore, but the reason that "master" still shows up.

BerndJM commented 8 years ago

@thopiekar would like to say thanks for your work, without that I've been not able to play along with the new cura on my actual Ubuntu system.

it's a shame, with the 15.09.xx and 1.99 versions we poor Ubuntu users had an soooo much to "old" sytem with the 14.04LTS - and now with the 2.1.x versions we have a to "new" system with the 16.04LTS @awhiemstra ... where destruction of QML items ... could you please shortly explain (for a not python programmer) what this means, so I can better estimate if it's a bug when something strange happens?

sedwards2009 commented 8 years ago

@BerndJM I can answer your question about the QML related bug. To hit it you need to do something which changes the settings in right sidebar, such as switching to different machine. When you hit it the application will hang and become unresponsive. It is quite nasty.

MCWeid commented 8 years ago

Hi @thopiekar, I am new to Linux and tried to follow your instructions. I added your PPA, purged the cura package and installed it again using apt get commands. Unfortunately it is still not starting and gives the following error messages <file:///usr/share/cura/resources/qml/Cura.qml:7 module "QtQuick.Layouts" is not installed file:///usr/share/cura/resources/qml/Cura.qml:4 module "QtQuick" is not installed file:///usr/share/cura/resources/qml/Cura.qml:8 module "QtQuick.Dialogs" is not installed file:///usr/share/cura/resources/qml/Cura.qml:6 module "QtQuick.Controls.Styles" is not installed file:///usr/share/cura/resources/qml/Cura.qml:5 module "QtQuick.Controls" is not installed file:///usr/share/cura/resources/qml/Cura.qml:7 module "QtQuick.Layouts" is not installed file:///usr/share/cura/resources/qml/Cura.qml:4 module "QtQuick" is not installed file:///usr/share/cura/resources/qml/Cura.qml:8 module "QtQuick.Dialogs" is not installed file:///usr/share/cura/resources/qml/Cura.qml:6 module "QtQuick.Controls.Styles" is not installed file:///usr/share/cura/resources/qml/Cura.qml:5 module "QtQuick.Controls" is not installed file:///usr/share/cura/resources/qml/Cura.qml:7 module "QtQuick.Layouts" is not installed file:///usr/share/cura/resources/qml/Cura.qml:4 module "QtQuick" is not installed file:///usr/share/cura/resources/qml/Cura.qml:8 module "QtQuick.Dialogs" is not installed file:///usr/share/cura/resources/qml/Cura.qml:6 module "QtQuick.Controls.Styles" is not installed file:///usr/share/cura/resources/qml/Cura.qml:5 module "QtQuick.Controls" is not installed file:///usr/share/cura/resources/qml/Cura.qml:7 module "QtQuick.Layouts" is not installed file:///usr/share/cura/resources/qml/Cura.qml:4 module "QtQuick" is not installed file:///usr/share/cura/resources/qml/Cura.qml:8 module "QtQuick.Dialogs" is not installed file:///usr/share/cura/resources/qml/Cura.qml:6 module "QtQuick.Controls.Styles" is not installed file:///usr/share/cura/resources/qml/Cura.qml:5 module "QtQuick.Controls" is not installed file:///usr/share/cura/resources/qml/Cura.qml:7 module "QtQuick.Layouts" is not installed file:///usr/share/cura/resources/qml/Cura.qml:4 module "QtQuick" is not installed file:///usr/share/cura/resources/qml/Cura.qml:8 module "QtQuick.Dialogs" is not installed file:///usr/share/cura/resources/qml/Cura.qml:6 module "QtQuick.Controls.Styles" is not installed file:///usr/share/cura/resources/qml/Cura.qml:5 module "QtQuick.Controls" is not installed

QQmlComponent: Component is not ready Traceback (most recent call last): File "/usr/bin/cura", line 30, in app.run() File "/usr/lib/python3/dist-packages/cura/CuraApplication.py", line 205, in run self.initializeEngine() File "/usr/lib/python3/dist-packages/UM/Qt/QtApplication.py", line 130, in initializeEngine self.engineCreatedSignal.emit() File "/usr/lib/python3/dist-packages/UM/Signal.py", line 102, in emit func(dest, _args, *_kargs) File "/usr/lib/cura/plugins/ChangeLogPlugin/ChangeLog.py", line 90, in _onEngineCreated self.showChangelog() File "/usr/lib/cura/plugins/ChangeLogPlugin/ChangeLog.py", line 96, in showChangelog self._changelog_window.show() AttributeError: 'NoneType' object has no attribute 'show'

What am I doing wrong?

Thank you for your help!

Kind regards Marc.

Ghostkeeper commented 8 years ago

It seems that the Qt package in that PPA doesn't have the plug-ins we require.

thopiekar commented 8 years ago

That's correct. Looks like I've missed an package that is already installed, when using KDE 5.

Try to: sudo apt install qml-module-qtquick-dialogs qml-module-qtquick-controls

@Ghostkeeper: I guess Uranium needs them most of all?

Ghostkeeper commented 8 years ago

Both Uranium and Cura create those dialogues and controls.

MCWeid commented 8 years ago

Hi @thopiekar, this worked for me. Cura is now starting and slicing. Thank you for your help.

thopiekar commented 8 years ago

No problem. Will add the missing dependencies to the packages later. Thank you for your feedback 👍

hulkco commented 8 years ago

Hi i Tried to add you PPA but my system dont work: W: El repositorio «http://ppa.launchpad.net/gwibber-daily/ppa/ubuntu xenial Release» no tiene un fichero de Publicación. N: Los datos de un repositorio como este no se pueden autenticar y por tanto su uso es potencialmente peligroso. N: Vea la página de manual apt-secure(8) para los detalles sobre la creación de repositorios y la configuración de usuarios. E: Fallo al obtener http://ppa.launchpad.net/gwibber-daily/ppa/ubuntu/dists/xenial/main/binary-amd64/Packages 404 Not Found E: No se han podido descargar algunos archivos de índice, se han omitido, o se han utilizado unos antiguos en su lugar. Can you helpme ?

Ghostkeeper commented 8 years ago

An attempt to translate for someone who might be able to debug:

Warning: The repository "http://ppa.launchpad.net/gwibber-daily/ppa/ubuntu xenial Release" doesn't have a publication date. The data from a such a repository couldn't be authenticated so it could be dangerous to use. See the manual page "apt-secure(8)" for details on creating and configuring repositories. Error: Couldn't obtain http://ppa.launchpad.net/gwibber-daily/ppa/ubuntu/dists/xenial/main/binary-amd64/Packages 404 Not Found Error: Some index files couldn't be downloaded, were omitted, or have been deprecated.

hulkco commented 8 years ago

Regards...

thopiekar commented 8 years ago

Good morning,

you've got an old PPA enabled, which has been disabled. Just take 'sudo software-properties-gtk' and remove the URL, which mentions "gwibber".

After that "apt-get update" should work again.

thopiekar commented 8 years ago

Oh, and you can easily translate every application by adding the prefix "LANG=C" 😉 So this would result into "LANG=C sudo apt-get update"..

nickthetait commented 8 years ago

That's a handy translation switch to know about :+1:

thopiekar commented 8 years ago

I'm sure you could even ask me this while sleeping. Almost need it every time I have to read others console outputs :smile:

HyGy commented 8 years ago

Will it work with the ubuntu 16.04 with the downloaded version from the original site? (I tried 2.3).

gazhay commented 8 years ago

If its the same issue - some of us have tried pull requests to get the thing fixed, but none seem to get accepted.

For reference, the line I needed to change to make things work was documented here https://github.com/daid/LegacyCura/issues/1461

thopiekar commented 8 years ago

The problem at the moment is not the same. Currently more recent Ubuntu versions come with Python 3.5 only, but our DEB needs 3.4 (nothing lower or higher).

In the future we'll use AppImages, which means everything will be bundled into one executable binary file. So no DEB's anymore. Just 'chmod a+x ' and double click on it. The only alternative to that is my personal PPA where I provide 'traditional' DEB packages.

I've been working on these AppImages and they are working now. It only needs a review next week and hopefully get releases on the next Beta release (if there are no further problems with it).

Regards

HyGy commented 8 years ago

@thopiekar Can I test this bundle on my ubuntu 16.04?

thopiekar commented 7 years ago

@HyGy: The usage of AppImage has been moved into future sprints. Can't decide on that, but you can try to use my PPA. It comes with 2.3 now.

Or are you using a non-Debian system?

HyGy commented 7 years ago

Hi @thopiekar,

Thanks, testing it.

thopiekar commented 7 years ago

@HyGy : There are instructions on the PPA page, see "Adding this PPA to your system". In short you can add the PPA by:

sudo add-apt-repository ppa:thopiekar/cura

or using the URL:

http://ppa.launchpad.net/thopiekar/cura/ubuntu

in your sources.list.

HyGy commented 7 years ago

Meanwhile I found it, thanks. :) I just wake up :) sorry.

thopiekar commented 7 years ago

No problem :smile: Have a nice day :wink:

HyGy commented 7 years ago

Where can I set the diameter of the filament? In the materials I cant set anything.

@thopiekar it was just an afternoon sleeping :) Thanks anyway. :)))

HyGy commented 7 years ago

Okay, I found it I need to duplicate one material and I can edit it, but I think all the other materials is not necessary for me, couse I'm using 1.75mm filament.

HyGy commented 7 years ago

My first test print is running (okay, the second, first I forget put the autobedlevel g code to start gcode.

thopiekar commented 7 years ago

Great! :+1:

HyGy commented 7 years ago

The installation is good with your ppa with ubuntu 16.04. The test print is success.

When I press open folder after slicing and saving to disk, it open 3 times the folder. :)

I printed an lm8uu bearing with a prusa i3:

the outter surface is very good
the first layer is a little bit bigger
i want to pull it to a 8mm road, but it is very hard, and I can't move it on the road with my hand. (Sliced with slic3r I can move it).

Thanks for your work. I print a treefrog now. ;)

HyGy

KlausHans commented 7 years ago

Hello @thopiekar, i have troubles to get Cura to work on Ubuntu Gnome 16.04. First i tried the .deb from the Ultimaker website and run in the Python 3.4 problem. Then i tried your ppa. It starts, but i am not able to save settings, edit profiles etc. When i close it and reopen cura, then it asks me again wich printer i use (tried it a few times). Starting it with sudo did not changed the behavior. Besides that it seems quite unstable, crashed two times in a short period of time. What am i missing? Thanks.

thopiekar commented 7 years ago

Hey @KlausHans,

rule no. 1: never ever use 'sudo' if it is really needed. If there are problems (same for other applications) take a terminal instead and run your application manually. Often there is a error message which mention which problem is present.

Now back to your problem here: For me it sounds like you've messed up the directory/file permissions by using sudo (by using sudo on Cura or using sudo on another application). Please google how to repair your $HOME's permissions. You will find guides easily, I'm sure. When that's done, I'll take another look on that for sure. (However it doesn't seem to be a software or packaging related problem so far.)

Regards

BerndJM commented 7 years ago

For the rule #1 and the permissions @thopiekar has right (i tried this unintented gg). Running Cura as sudo and all the config folders belong to the user "root" so you're afterwards not able to save any configs as the normal user ...

thopiekar commented 7 years ago

Thank you for confirmation. I'm sure resetting all permissions of the whole $HOME directory is wise here, as @KlausHans probably already played with sudo in the past.

KlausHans commented 7 years ago

Thanks, this was indeed the problem, never experienced it before. It works now.

The sudo-thing was just for testing after it did not work in the first place.

BerndJM commented 7 years ago

For me the question came in mind: why the hell writes Cura - started as root (via sudo) - the config files to "/home/user" and not to "/root" ???

thopiekar commented 7 years ago

If I'm not wrong, running 'sudo' keeps your environment variables and they say that $HOME is at your home directory. So Cura will use your home directory at the end, too. In comparison running 'sudo bash' and then cura will use root's home. But not sure whether bash adopts the old environment variables again..

sanderux commented 7 years ago

@thopiekar any chance you could update your PPA to include the ultimaker 3?

probonopd commented 7 years ago

@thopiekar any chance we'll eventually see the AppImages?

thopiekar commented 7 years ago

@sanderux Yes, the sources for the UM3NetworkPrintingPlugin are now open. I was on vacation and now I'm back home. It should be available "soon".

@probonopd Can't say anything about it. Didn't take a look at the cura-build code for a while, but it is planned for 2.4 afaik.

Ultimaker / Cura

Collection of feedback and bugs around the stable PPA (no support for master PPA!) #718