Jump to content

Cura 2.7.0 and 3.0.3 doesn't start


Dominion

Recommended Posts

Posted · Cura 2.7.0 and 3.0.3 doesn't start

Hello,

currently i use Cura 2.6.2 with Windows 10 (64bit).

If i start 2.7.0 or 3.0.3, the splash screen disappears after "Szene wird geladen..." without error message and Cura doesnt' start.

Has someone an idea what i can do?

Best regards

Frank

  • Link to post
    Share on other sites

    Posted (edited) · Cura 2.7.0 and 3.0.3 doesn't start

    yes still the same only 2.7.0 works on my Windows10/64

    Very very strange App Dev.

    Someone wrote "Delete C:\Benutzer\DeinBenutzerName\AppData\Local\cura "

    But there is no AppData folder in my enviornment

    Edited by Guest
  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 and 3.0.3 doesn't start

    changed in AppData in SubFolder Local and Roaming old "Cura" Folder to "Cura old". Now Cura 3.0.3 starts but then the same error as in the Screen from HappyTin above after selection "other" the Screens appears to adjust Printer Setting for 3sec and then the App crashes

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 and 3.0.3 doesn't start
    Link to post
    Share on other sites

    Posted · Cura 2.7.0 and 3.0.3 doesn't start

    Note that the workaround @Msuurmond points to is strictly fixing a 3.0.3 issue; Cura 2.7 was not affected by this, so if you are dealing with a crashing 2.7 that fix will not work for you.

    • Like 1
    Link to post
    Share on other sites

    Posted (edited) · Cura 2.7.0 and 3.0.3 doesn't start

    Cura 3.0.3 now starts and everything is fine, except, no graphics. No files are displayed. Cannot see what I am doing./H/H/H Correction IT WORKS!

    Edited by Guest
    • Like 1
    Link to post
    Share on other sites

    Posted · Cura 2.7.0 and 3.0.3 doesn't start

    I tried with Cura 3.0.3 with no effort, so i stay at 2.6.2 (and looking for alternative slicer)...

    Best regards

    Frank

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 and 3.0.3 doesn't start

    This should be fixed in 3.0.4 (which can be downloaded from our site now)

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 and 3.0.3 doesn't start

    Hello,

    I'm also having an issue with launching Cura 3.0.4 (The problem started from the 3.7 update). As soon as Cura is launched it exits. The only way I can start the application is by disabling my wifi connection. It then starts normally but the moment I enable wifi again the application exits again.

    I have whitelisted Cura in the Firewall setting but the issue still persists. This is occurring on a MacBook Pro macOS version 10.12.6

    This is the stack trace

    Thread 0 Crashed:

    0 libsystem_kernel.dylib 0x00007fffa6bddd42 __pthread_kill + 10

    1 libsystem_c.dylib 0x00007fffa6af4497 raise + 26

    2 libsystem_platform.dylib 0x00007fffa6cbeb3a _sigtramp + 26

    3 ??? 000000000000000000 0 + 0

    4 com.apple.CFNetwork 0x00007fff905e95c4 PAC::PACClient::invokeClientCallback() + 102

    5 com.apple.CoreFoundation 0x00007fff91347321 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17

    6 com.apple.CoreFoundation 0x00007fff9132821d __CFRunLoopDoSources0 + 557

    7 com.apple.CoreFoundation 0x00007fff91327716 __CFRunLoopRun + 934

    8 com.apple.CoreFoundation 0x00007fff91327114 CFRunLoopRunSpecific + 420

    9 libQt5Network.5.dylib 0x0000000109114d75 0x109070000 + 675189

    10 libQt5Network.5.dylib 0x0000000109115b51 QNetworkProxyFactory::systemProxyForQuery(QNetworkProxyQuery const&) + 17

    11 libQt5Network.5.dylib 0x000000010910b753 0x109070000 + 636755

    12 libQt5Network.5.dylib 0x000000010910d842 QNetworkProxyFactory::proxyForQuery(QNetworkProxyQuery const&) + 50

    13 libQt5Network.5.dylib 0x00000001090a155e 0x109070000 + 202078

    14 libQt5Network.5.dylib 0x00000001090bf329 0x109070000 + 324393

    15 libQt5Network.5.dylib 0x00000001090c4283 0x109070000 + 344707

    16 libQt5Network.5.dylib 0x00000001090bbdee 0x109070000 + 310766

    17 libQt5Network.5.dylib 0x00000001090bba9b 0x109070000 + 309915

    18 libQt5Network.5.dylib 0x000000010909fed5 QNetworkAccessManager::createRequest(QNetworkAccessManager::Operation, QNetworkRequest const&, QIODevice*) + 1653

    19 PyQt5.QtNetwork.so 0x0000000108fccef1 sipQNetworkAccessManager::createRequest(QNetworkAccessManager::Operation, QNetworkRequest const&, QIODevice*) + 129

    20 libQt5Network.5.dylib 0x000000010909e2de QNetworkAccessManager::get(QNetworkRequest const&) + 30

    21 PyQt5.QtNetwork.so 0x0000000108fcdd01 meth_QNetworkAccessManager_get(_object*, _object*) + 113

    22 nl.ultimaker.cura 0x0000000108a9f0a5 PyCFunction_Call + 165

    23 nl.ultimaker.cura

  • Link to post
    Share on other sites

    Posted · Cura 2.7.0 and 3.0.3 doesn't start

     

    @scootersi, do you have an UM3? If not, you could try to disable the UM3NetworkPrinting plugin through the Plugins pane of the preferences.

  • 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
    • Our picks

      • UltiMaker Cura 5.7 stable released
        Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more. 
         
          • Like
        • 18 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
          • Like
        • 0 replies
    ×
    ×
    • Create New...