Jump to content

different behavior if cura 5.1.0 started direct from appimage or gnome menu / cli Linux


sekisback

Recommended Posts

Posted · different behavior if cura 5.1.0 started direct from appimage or gnome menu / cli Linux

no big deal, but i am searching for a solution.

I have a different behavior from cura if i start cura by double clicking the AppImage (everything is like expected)

or if i start cura from command line by using /usr/bin/cura or /opt/cura/Ultimaker-Cura-5.1.0-linux.AppImage


In the second case it seams for me, that the screenresolution is different or maybe the fonts are bigger


I tried this also with cura 5.0,  in cura 5.0 is no different in the display behavior, never mind which start version i choose.

 

Did someone know this behavior.

Using debian.

 

Maybe there is something missing, if i use the cli to start cura 5.1.0 i got this output

Quote

PyInstaller/loader/pyimod03_importers.py:495: DeprecationWarning: the imp module is deprecated in favour of importlib and slated for removal in Python 3.12; see the module's documentation for alternative uses
Gtk-Message: 16:32:50.194: Failed to load module "xapp-gtk3-module"
Cyclic dependency detected between "file:///tmp/.mount_UltimaWG9fTb/share/cura/resources/qml/Actions.qml" and "file:///tmp/.mount_UltimaWG9fTb/share/cura/resources/qml/Actions.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
qt.qml.context: file:///tmp/.mount_UltimaWG9fTb/share/cura/resources/qml/Settings/SettingView.qml:427:16 Parameter "index" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead.

 

 

with cura 5.0 i got this output

Quote

/Ultimaker-Cura-5.0.0-linux.AppImage
PyInstaller/loader/pyimod03_importers.py:495: DeprecationWarning: the imp module is deprecated in favour of importlib and slated for removal in Python 3.12; see the module's documentation for alternative uses
Cyclic dependency detected between "file:///tmp/.mount_UltimajP6F5L/share/cura/resources/qml/Actions.qml" and "file:///tmp/.mount_UltimajP6F5L/share/cura/resources/qml/Actions.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext


qt.qml.context: file:///tmp/.mount_UltimajP6F5L/share/cura/resources/qml/Settings/SettingView.qml:427:16 Parameter "index" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead.

 

 

cura_appimage_start.png

cura_menue_start.png

  • 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...