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.8 beta released
        Another Cura release has arrived and in this 5.8 beta release, the focus is on improving Z seams, as well as completing support for the full Method series of printers by introducing a profile for the UltiMaker Method.
          • Like
        • 0 replies
      • Introducing the UltiMaker Factor 4
        We are happy to announce the next evolution in the UltiMaker 3D printer lineup: the UltiMaker Factor 4 industrial-grade 3D printer, designed to take manufacturing to new levels of efficiency and reliability. Factor 4 is an end-to-end 3D printing solution for light industrial applications
          • Thanks
          • Like
        • 3 replies
      • 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
        • 27 replies
    ×
    ×
    • Create New...