Jump to content
Ultimaker Community of 3D Printing Experts

Cura 2.7.0 crashes when starting


asb
 Share

Recommended Posts

Posted · Cura 2.7.0 crashes when starting

Hi,

today I "upgraded" to Cura 2.7.0 from PPA (Ubuntu 17.04). The software immediately crashes when starting.

Last recorded messages from logfile:

2017-10-11 00:54:42,498 - DEBUG - UM3NetworkPrinting.NetworkPrinterOutputDevicePlugin._onServiceChanged [210]: Bonjour service added: ultimakersystem-ccbdd30030ac._ultimaker._tcp.local.
2017-10-11 00:54:49,665 - DEBUG - UM.Settings.ContainerRegistry.load [214]: Loading data into container registry took 7.361455917358398 seconds
2017-10-11 00:54:49,666 - WARNING - cura.Settings.CuraContainerRegistry._fixupExtruders [405]: Could not find machine Ultimaker 3 Extended for extruder ultimaker3_extended_extruder_left #2
2017-10-11 00:54:49,666 - WARNING - cura.Settings.CuraContainerRegistry._fixupExtruders [405]: Could not find machine Ultimaker 3 Extended for extruder ultimaker3_extended_extruder_right #2
2017-10-11 00:54:49,667 - DEBUG - UM.Backend.Backend._logSocketState [178]: Socket state changed to Connected
2017-10-11 00:54:49,668 - DEBUG - UM.Backend.Backend._onSocketStateChanged [168]: Backend connected on port 49674
2017-10-11 00:54:49,670 - DEBUG - UM.Controller.setActiveView [84]: Setting active view to SolidView
2017-10-11 00:54:50,062 - DEBUG - UM.Qt.Bindings.Theme.load [165]: Loading theme file: /usr/share/cura/resources/themes/cura/theme.json
2017-10-11 00:54:50,117 - DEBUG - UM.Qt.Bindings.Theme.load [232]: Loaded theme /usr/share/cura/resources/themes/cura
2017-10-11 00:54:50,193 - WARNING - cura.Settings.ContainerManager.getContainerMetaDataEntry [184]: Could not get metadata of container  because it was not found.
2017-10-11 00:54:50,524 - WARNING - UM.Preferences.getValue [81]: Tried to get the value of non-existing setting info/automatic_update_check.
2017-10-11 00:54:50,549 - DEBUG - UM3NetworkPrinting.DiscoverUM3Action._createAdditionalComponentsView [138]: Creating additional ui components for UM3.
2017-10-11 00:54:50,569 - DEBUG - UM3NetworkPrinting.DiscoverUM3Action.startDiscovery [38]: Starting printer discovery.
2017-10-11 00:54:50,747 - DEBUG - UM.Qt.QtRenderer._initialize [172]: Support for Vertex Array Objects: True
2017-10-11 00:54:50,751 - DEBUG - UM.View.GL.OpenGL.__init__ [85]: Initialized OpenGL subsystems.
2017-10-11 00:54:50,751 - DEBUG - UM.View.GL.OpenGL.__init__ [86]: OpenGL Version:  4.5 (Core Profile) Mesa 17.0.7
2017-10-11 00:54:50,751 - DEBUG - UM.View.GL.OpenGL.__init__ [87]: OpenGL Vendor:   Intel Open Source Technology Center
2017-10-11 00:54:50,751 - DEBUG - UM.View.GL.OpenGL.__init__ [88]: OpenGL Renderer: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) 
2017-10-11 00:54:50,751 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/uranium/resources/shaders/default.shader]...
2017-10-11 00:54:50,756 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/uranium/resources/shaders/selection.shader]...
2017-10-11 00:54:50,759 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/uranium/resources/shaders/default.shader]...
2017-10-11 00:54:50,761 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/uranium/resources/shaders/composite.shader]...
2017-10-11 00:54:50,769 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/cura/resources/shaders/overhang.shader]...
2017-10-11 00:54:50,778 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/cura/resources/shaders/striped.shader]...
2017-10-11 00:54:50,788 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/uranium/resources/shaders/platform.shader]...
2017-10-11 00:54:54,103 - INFO - cura.Settings.GlobalStack.addExtruder [81]: Extruder[ultimaker3_extended_extruder_left #3] added to [ultimaker 3 Extended] at position [0]
2017-10-11 00:54:54,133 - INFO - cura.Settings.GlobalStack.addExtruder [81]: Extruder[ultimaker3_extended_extruder_right #3] added to [ultimaker 3 Extended] at position [1]
2017-10-11 00:54:54,788 - DEBUG - UM3NetworkPrinting.DiscoverUM3Action.reset [46]: Reset the list of found printers.
2017-10-11 00:54:54,833 - DEBUG - UM.Mesh.MeshData.approximateConvexHull [392]: approximateConvexHull(target_count=1024) Calculating 3D convex hull took 0.018415212631225586 seconds. 121 input vertices. 121 output vertices.
2017-10-11 00:54:54,842 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/uranium/resources/shaders/default.shader]...
2017-10-11 00:54:54,845 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/cura/resources/shaders/grid.shader]...

Any suggestions?

Thanks!

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    There has been some recent crashes with the PPA installation caused by the back end slicer version being out of sync WRT the UI version. Does it crash while loading Cura or when you ask it to slice? If the latter, then it's probably the problem with inconsistent software versions.

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    @smartavionics: The last time I could successfully use Cura was in June 2017. Version 2.6.4 from PPA did not slice anything, but did not crash. It just would not generate something that could be printed.

    The 2.7.0 "upgrade" was rolled out a few days ago. This version crashes when starting the software (splash screen loads, then it tries to "connect to networked printer", then it crashes).

    It's just ridiculous, a €4,500 device that can not be used for over four months because of faulty software and a buggy networking stack.

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    Well, yes, that's sad. But I don't think the PPA is an official release, it's just a snapshot of the development version that has been kindly provided by an individual. Have you tried using the official 2.7 release?

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    The PPA is supposed to be supported by Ultimaker as the programmer is an intern.

    As I mentioned elsewhere, the existence of this repository was the only reason to buy an UM 3 Extended.

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting
    As I mentioned elsewhere, the existence of this repository was the only reason to buy an UM 3 Extended.

    So it is not possible for you to use the official release? The other alternative is to build the program from source.

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    The PPA is supposed to be supported by Ultimaker as the programmer is an intern.

    No, it isn't. The creator of the PPA, thopiekar, has always said that the PPA is not supported by Ultimaker. The only supported release of Cura 2.7 for Linux is the AppImage.

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    Also; Thopiekar is a mechanical engineer intern ;)

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    sooo u guys.. I've kind of the same issue. can't even start cura 2.7...and don't get a fail notification

    working with os x10.11.6, shut the security n privacy on anywhere but it wont start.

    Am i doing something wrong? probably! Pls tell me

    Sorry i'm a total noob.

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    This crap still does not work.

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting
    This crap still does not work.

    Please answer the question, have you tried using the appimage which is the official release? If no, please try that. If yes, how did it fail? Logs, etc.

    • Like 1
    Link to post
    Share on other sites

    Posted (edited) · Cura 2.7.0 crashes when starting

    @ smartavionics: The "Appimage" has never worked, not even remotely. It always failed to do anything but to waste a lot of bandwidth for downloading. There is an older thread from a few months ago about it: https://ultimaker.com/en/community/50064-um3-extended-either-no-network-or-not-slicing-which-cura-version-works

    Thopiekar's PPA is usually magnitudes better, e.g. it actually creates a logfile; and it - so far - mostly worked, except for some "glitches" like losing network connectivity after a couple of hours or sometimes not being able to find a WLAN'd Ultimaker on the network, or (recently) the dead slicer. The "only" problem with the PPA is that it keeps being a moving target; even if there are no updates, different glitches occur erratically. But it basically used to work. The Appimage does not. And as far as I can tell, that faulty slicer is not new, either, it was inherited from Cura 1.x where this has been a major issue for years, long before there even was a PPA.

    The issue with the current Cura 2.7.0 is that it (again) does not migrate settings from Cura 2.6.x and crashes after the splash screen, when asking to select a printer. What the logfile records is just gibberish to me, at least I do not see a fatal error being logged that would explain why the software dies during startup.

    Edited by Guest
  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    Understood. However, a big problem with the PPA is that it is a snapshot of the development version of Cura so it is pretty much guaranteed to be unusable every once in a while due to bugs and inconsistences in the repos.

    If you can't use the appimage and the PPA cannot be relied on for production use, I guess your only option is to build Cura from source and then you will be in 100% control of what you are using.

    Building from source is not hard (not hard for Linux, that is, I don't know about the other platforms).

  • Link to post
    Share on other sites

    Posted (edited) · Cura 2.7.0 crashes when starting

    Appimages are generally crap because they introduce harmful redundundancy to a perfectly fine operating system, are not integrated into Debian's elaborate mechanisms for sane file & package management and updating, they waste disk space and bandwidth, pose an inherent security risk through through outdated software duplicates that will never be updated as an Appimage is not handled by package management, and Appimages are neither integrated into the operating system nor the UI. It is just software engineering at it's worst. Also, the Appimage provided by Ultimaker is horribly slow, which makes using features like the layer view impossible. And worst of all, it simply does not work most of the time.

    To verify these claims I downloaded the current "Cura-2.7.0.AppImage" which has an idiotic size of 107.4 megabytes. After making it executable, it sometimes startes beyond the splash screen; usually it just silently dies. If it manages to go beyond the splash screen, it reproducably fails to communicate with the printer like so:

    ap270-1.thumb.jpg.a0fc1a932b984e39a1056f75664ffd7a.jpg

    Status message: "Unable to start a new print job, printer is busy. Current printer status is booting"

    This is complete nonsense. In this case, the printer was neither busy nor booting. It was started 30 minutes ago.

    ap270-2.thumb.jpg.abeff6cdef575739186573244daff6f5.jpg

    That's what Cura reported after claiming to be unable to start a new print job: "Connection: Connected over the network. State: Waiting for a printjob".

    So the Cura Appimage is not even consistent how to interpret the status messages.

    ap270-3.jpg.599a7deaa725e2f17ff8f72dbdd580b5.jpg

    Next try. Rebooted the printer, waited for about ten minutes, restarted Cura.

    Now Cura reports: "The connection with the printer was lost. Check your printer to see if it is connected."

    That's why I say that the Appimage is crap and why I do not want to start trying to debug the Appimage. It already fails on the most basic level - consistently, over the past months.

    Sorry, compiling and debugging a faulty software is beyond what I am willing to do. I have paid EUR 4,500 to obtain a productive solution for 3d printing, not a development kit for playing.

    Now back to Thopiekar's PPA version which at least justifies debugging attempts.

    Here is the output when starting the debinized Cura 2.7.0 from the shell:

    […]
    Thread 0x00007fb7f4db2700 (most recent call first):
     File "/usr/lib/python3.5/threading.py", line 293 in wait
     File "/usr/lib/python3.5/threading.py", line 424 in acquire
     File "/usr/lib/python3/dist-packages/UM/JobQueue.py", line 86 in _nextJob
     File "/usr/lib/python3/dist-packages/UM/JobQueue.py", line 116 in run
     File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner
     File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap
    Thread 0x00007fb7f55b3700 (most recent call first):
     File "/usr/lib/python3.5/threading.py", line 293 in wait
     File "/usr/lib/python3.5/threading.py", line 424 in acquire
     File "/usr/lib/python3/dist-packages/UM/JobQueue.py", line 86 in _nextJob
     File "/usr/lib/python3/dist-packages/UM/JobQueue.py", line 116 in run
     File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner
     File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap
    Thread 0x00007fb7f5db4700 (most recent call first):
     File "/usr/lib/python3/dist-packages/UM/Backend/Backend.py", line 156 in _storeStderrToLogThread
     File "/usr/lib/python3.5/threading.py", line 862 in run
     File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner
     File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap
    Thread 0x00007fb7f65b5700 (most recent call first):
     File "/usr/lib/python3/dist-packages/UM/Backend/Backend.py", line 148 in _storeOutputToLogThread
     File "/usr/lib/python3.5/threading.py", line 862 in run
     File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner
     File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap
    Thread 0x00007fb7f75b7700 (most recent call first):
     File "/usr/lib/cura/plugins/USBPrinting/USBPrinterOutputDeviceManager.py", line 88 in _updateThread
     File "/usr/lib/python3.5/threading.py", line 862 in run
     File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner
     File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap
    Thread 0x00007fb810ad7700 (most recent call first):
     File "/usr/lib/cura/plugins/RemovableDriveOutputDevice/RemovableDrivePlugin.py", line 58 in _updateThread
     File "/usr/lib/python3.5/threading.py", line 862 in run
     File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner
     File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap
    Thread 0x00007fb8112d8700 (most recent call first):
     File "/usr/lib/python3.5/threading.py", line 297 in wait
     File "/usr/lib/python3/dist-packages/zeroconf.py", line 1569 in wait
     File "/usr/lib/python3/dist-packages/zeroconf.py", line 1153 in run
     File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner
     File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap
    Thread 0x00007fb811ad9700 (most recent call first):
     File "/usr/lib/python3.5/threading.py", line 297 in wait
     File "/usr/lib/python3/dist-packages/zeroconf.py", line 1569 in wait
     File "/usr/lib/python3/dist-packages/zeroconf.py", line 1017 in run
     File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner
     File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap
    Thread 0x00007fb8122da700 (most recent call first):
     File "/usr/lib/python3/dist-packages/zeroconf.py", line 946 in run
     File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner
     File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap
    Current thread 0x00007fb8577a0700 (most recent call first):
     File "/usr/lib/python3/dist-packages/UM/Qt/ListModel.py", line 63 in setItems
     File "/usr/lib/python3/dist-packages/cura/Settings/ExtrudersModel.py", line 224 in __updateExtruders
     File "/usr/lib/python3/dist-packages/cura/CuraApplication.py", line 682 in run
     File "/usr/bin/cura", line 73 in 
    Speicherzugriffsfehler (Speicherabzug geschrieben)

    The last message means: "Memory access error (memory dumped)".

    As the current Appimage, the current PPA is not operational.

    Edited by Guest
  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting
    Sorry, compiling and debugging a faulty software is beyond what I am willing to do.

    I'm not suggesting you debug the software. Compile and install the software, yes. Debugging it should not be necessary if you install a (relatively) stable branch. Anyway, I'm leaving this thread now, I haven't got anything else to say beyond what I have said already.

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    Every single issue that you reported has absolutely nothing to do with the appImage.

    The debian package manager only works in theory; In practice it causes gazillion issues. The whole "your system can handle dependencies" simply moves the responsibility of having the right packages to the OS mainainers. In quite a few cases this made Cura not work at all, leaving us with no power to actually do something about it.

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting
    The debian package manager only works in theory; In practice it causes gazillion issues.

    Really? Last time I checked, it worked perfectly for 51000 software packages. And Debian's package manager works fine on my servers for over a decade.

     

    Every single issue that you reported has absolutely nothing to do with the appImage.

    Among others, the errors I get from the current Appimage of Cura 2.7.0 are:

     

    • Does not accept print jobs - Cura reports "Unable to start a new print job, printer is busy. Current printer status is booting", but printer is not booting. Preferences report inconsistently: "Connection: Connected over the network. State: Waiting for a printjob", but print jobs are not accepted because of the error above.

    • Network connectivity is broken - "The connection with the printer was lost. Check your printer to see if it is connected", but printer is online and can be pinged.

     

    I'd say this acually has something to to with the Appimage and how it incorrectly reads/interprets status messages.

    However, the question is how can I print something on this €4500 device?!

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    However, the question is how can I print something on this €4500 device?!

     

    The same argument as you used can be held here; Thousands of users are able to connect with Cura using the appimage. So are you really sure it's the appimage? We've had this discussion a ton of times; Provide us with logs. Just complaining this don't work isn't going to change the situation.

    We're not going to switch back to .deb images due to a lot of issues with backwards compatibility due to Ubuntu failing to have a proper packager for python related libraries. Unfortunately there aren't enough users on Linux for us to be able to invest into getting those packages up and running.

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    I really can not get these two pieces of information together… you say that "thousands of users are able to connect with Cura using the appimage", but on the other hand you say that "there aren't enough users on Linux for us to be able to invest into getting those packages up and running". Now what is it, "thousends of users" or not enough users on Linux?

    Logfiles and Shell messages have been posted above. So far, nobody bothered to comment on these chunks of information.

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    A thousand users isn't a whole lot. It used to be, but it isn't by a long shot anymore.

    The logs that you posted are partial and regarding another issue. They don't contain the right parts to be able to debug why its going wrong in your case.

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting
    The logs that you posted are partial and regarding another issue. They don't contain the right parts to be able to debug why its going wrong in your case.

    That is exactly my point - that is all what Cura logs to ~/.local/share/cura/2.7/cura.log.

    The logfile ends with "DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/cura/resources/shaders/grid.shader]..."

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    the AppImage (3.0.3) version of cura is the only version that works on my PC perfectly. The Cura (2.7.0) version from the PPA doesen't even start.

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    Cura 3.0.3 Appimage can not even discover my Ultimaker 3 Extended printer anyore. Again, new release, things are getting worse. The 2.7.0 Appimage at least saw the printer, when the software managed to pass the splash screen.

    Excerpt from the last:

    …
    2017-10-23 04:00:34,938 - WARNING - UM.Settings.ContainerStack.addMetaDataEntry [162]: Meta data with key machine was already added.
    2017-10-23 04:00:34,939 - DEBUG - UM.Settings.ContainerRegistry.load [228]: Loading data into container registry took 15.746948003768921 seconds
    2017-10-23 04:00:35,485 - DEBUG - UM.Controller.setActiveView [84]: Setting active view to SolidView
    2017-10-23 04:00:37,902 - DEBUG - UM.Qt.Bindings.Theme.load [163]: Loading theme file: /tmp/.mount_3heCGt/usr/bin/resources/themes/cura-light/theme.json
    2017-10-23 04:00:38,073 - DEBUG - UM.Qt.Bindings.Theme.load [231]: Loaded theme /tmp/.mount_3heCGt/usr/bin/resources/themes/cura-light
    2017-10-23 04:00:39,007 - DEBUG - UM.Controller.setActiveView [84]: Setting active view to SolidView
    2017-10-23 04:00:39,277 - WARNING - UM.Qt.Bindings.Theme.getIcon [109]: No icon tool_icon.svg defined in Theme
    2017-10-23 04:00:39,472 - WARNING - UM.Qt.Bindings.Theme.getIcon [109]: No icon tool_icon.svg defined in Theme
    2017-10-23 04:00:39,473 - WARNING - UM.Qt.Bindings.Theme.getIcon [109]: No icon tool_icon.svg defined in Theme
    2017-10-23 04:00:39,513 - DEBUG - OctoPrintPlugin.DiscoverOctoPrintAction._createAdditionalComponentsView [218]: Creating additional ui components for OctoPrint-connected printers.
    2017-10-23 04:00:39,533 - DEBUG - UM3NetworkPrinting.DiscoverUM3Action._createAdditionalComponentsView [138]: Creating additional ui components for UM3.
    2017-10-23 04:00:39,637 - DEBUG - UM3NetworkPrinting.DiscoverUM3Action.startDiscovery [38]: Starting printer discovery.
    2017-10-23 04:00:39,792 - DEBUG - UM.Mesh.MeshData.approximateConvexHull [392]: approximateConvexHull(target_count=1024) Calculating 3D convex hull took 0.013724803924560547 seconds. 121 input vertices. 121 output vertices.
    2017-10-23 04:00:40,417 - DEBUG - UM.Qt.QtRenderer._initialize [172]: Support for Vertex Array Objects: True
    2017-10-23 04:00:40,426 - DEBUG - UM.View.GL.OpenGL.__init__ [85]: Initialized OpenGL subsystems.
    2017-10-23 04:00:40,427 - DEBUG - UM.View.GL.OpenGL.__init__ [86]: OpenGL Version:  4.5 (Core Profile) Mesa 17.0.7
    2017-10-23 04:00:40,428 - DEBUG - UM.View.GL.OpenGL.__init__ [87]: OpenGL Vendor:   Intel Open Source Technology Center
    2017-10-23 04:00:40,429 - DEBUG - UM.View.GL.OpenGL.__init__ [88]: OpenGL Renderer: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) 
    2017-10-23 04:00:40,430 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/default.shader]...
    2017-10-23 04:00:40,435 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/selection.shader]...
    2017-10-23 04:00:40,438 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/default.shader]...
    2017-10-23 04:00:40,443 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/composite.shader]...
    2017-10-23 04:00:40,452 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/overhang.shader]...
    2017-10-23 04:00:40,463 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/striped.shader]...
    2017-10-23 04:00:40,479 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/default.shader]...
    2017-10-23 04:00:40,484 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/grid.shader]...
    2017-10-23 04:00:40,490 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/platform.shader]...
    2017-10-23 04:00:48,457 - DEBUG - UM3NetworkPrinting.DiscoverUM3Action.reset [46]: Reset the list of found printers.
    2017-10-23 04:00:49,976 - DEBUG - UM3NetworkPrinting.NetworkPrinterOutputDevicePlugin.stop [208]: zeroconf close...
    2017-10-23 04:00:55,441 - DEBUG - AutoSave.AutoSave._onTimeout [48]: Autosaving preferences, instances and profiles
    2017-10-23 04:00:58,759 - INFO - cura.CuraApplication.closeApplication [377]: Close application
    2017-10-23 04:00:58,762 - DEBUG - UM.Qt.QtApplication.windowClosed [300]: Shutting down cura
    2017-10-23 04:00:58,766 - DEBUG - CuraEngineBackend.CuraEngineBackend._terminate [232]: Attempting to kill the engine process
    2017-10-23 04:00:58,766 - DEBUG - CuraEngineBackend.CuraEngineBackend._terminate [238]: Killing engine process
    2017-10-23 04:00:58,767 - DEBUG - CuraEngineBackend.CuraEngineBackend._terminate [241]: Engine process is killed. Received return code -15
    

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    Messages when starting the Appimage from the shell:

    $ ./Cura-3.0.3.AppImage 
    Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 72: non-double matrix element
    Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 72: non-double matrix element
    Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 80: saw unknown, expected number
    Fontconfig warning: "/etc/fonts/conf.d/70-fonts-bpg-georgian.conf", line 12: bad alias
    Fontconfig warning: "/etc/fonts/conf.d/70-fonts-bpg-georgian.conf", line 21: bad alias
    Fontconfig warning: "/etc/fonts/conf.d/70-fonts-bpg-georgian.conf", line 30: bad alias
    QObject::connect: Parentheses expected, signal MainWindow::
    QObject::connect: Parentheses expected, signal MainWindow::
    QObject::connect: Parentheses expected, signal MainWindow::
    QObject::connect: Parentheses expected, signal MainWindow::
    file:///tmp/.mount_siJOmj/usr/bin/resources/themes/cura-light/styles.qml:197:17: QML Item: Binding loop detected for property "width"
    qml: TableViewSelection: index out of range
    qml: TableViewSelection: index out of range
    file:///tmp/.mount_siJOmj/usr/bin/plugins/plugins/UM3NetworkPrinting/DiscoverUM3Action.qml:282: TypeError: Cannot read property 'clusterSize' of null
    qml: TableViewSelection: index out of range
    file:///tmp/.mount_siJOmj/usr/bin/plugins/plugins/UM3NetworkPrinting/DiscoverUM3Action.qml:282: TypeError: Cannot read property 'clusterSize' of null
    

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 crashes when starting

    This is usually a network configuration issue. The discovery system didn't change in 2.7 to 3.0. You could just add the printer manually by IP.

  • Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
     Share

    • Our picks

      • New here? Get ahead with a free onboarding course
        Hi,
         
        Often getting started is the most difficult part of any process. A good start sets you up for success and saves you time and energy that could be spent elsewhere. That is why we have a onboarding course ready for
        Ultimaker S5 Pro Bundle, Ultimaker S5, Ultimaker S3 Ultimaker 2+ Connect.   
        They're ready for you on the Ultimaker Academy platform. All you need to do to gain access is to register your product to gain free access. 
        Ready? Register your product here in just 60 seconds.
          • Like
        • 8 replies
    ×
    ×
    • Create New...