A Nightly Build with an updated PyQT Library

[Mariska (MariMakes)]

We've received reports that some people have trouble with open/save file dialogs and using Ultimaker Cura on set-ups with multiple monitors or multiple windows. We possibly have a fix for this issue, but it is hard to test. So, we'll need some help with that. 😇

We created a special 🌙 Nightly build 🌙
This is a version of Cura that is a work-in-progress version, with an updated PyQT library.
This version has not passed any of our regular quality checks and we cannot guarantee it's reliability because it is still unfinished even though it may still be quite usable

Download Links
If you are using Windows, you can download a build here:
📁 UltiMaker-Cura-5.4.0-alpha-cura_10389_148-win64.exe

If you are using MacOS, you can download a build here:
📁 UltiMaker-Cura-5.4.0-alpha-cura_10389_148-mac.pkg

If you are using Linux, you can download a build here:
We recommend AppImage. If you run into issues with launching your AppImage, we have modern.AppImage ready as an alternative.
📁 UltiMaker-Cura-5.4.0-alpha-cura_10389_148-linux.AppImage
📁 UltiMaker-Cura-5.4.0-alpha-cura_10389_148-linux.AppImage.asc

📁 UltiMaker-Cura-5.4.0-alpha-cura_10389_148-linux-modern.AppImage
📁 UltiMaker-Cura-5.4.0-alpha-cura_10389_148-linux-modern.AppImage.asc

Please note
Before reporting bugs on this build, please double-check if the issue is also present on the latest Stable Cura version. Right now that is Cura 5.3.0. This Nightly Build looks differently on purpose so we can spot reports done with these builds.

Can you give it a try and let us know which issues are resolved? That would help a lot 😊

[A Mennucc (mennucc)]

First and foremost, I am experiencing a different problem. I click "save" then the save dialog appears, when I type any letter into the widget to specify the save name, the save dialog jumps into "search mode" and then it is almost impossible to specify the save name.
This problem appears in every version of Cura, also in the one listed above. I use Ubuntu 22.04 (with Mate desktop) . This said , adding the option -platformtheme gtk3 solves the problem

[Mariska (MariMakes)]

Thanks for the update, then this fix might not solve your problem but perhaps another one. 👍 🙂

[Jelle Spijker (jellespijker)]

Alternative options for -platformtheme gtk3 are also: gtk2, gnome, kde, qt5ct, xcb, xdgdesktopportal (current default). There could be more, possible values are scattered over the internet; Feel free to complete this list.

Unfortunately it is rather hard to detect which platformtheme or QT_QPA_PLATFORMTHEME value to use with all the different Linux distros and desktop managers, adding to the complexity are also multiple display protocols in use such as Xorg and Wayland (which is still incomplete for some desktop managers).

If anyone has a robust way of detecting and setting this please open up a PR: https://github.com/Ultimaker/Cura/blob/main/packaging/AppImage/AppRun

[Bryan Hunwardsen (bryanhunwardsen)]

Possible progress but not quite there yet.

Detailed feedback:
Setup: 3x monitors (same make and model)
Physically the are set up left to right (A,B,C) but Windows enumerates them backwards (3,2,1) *I know I can change this by switching which port on my grfx card they plug into) just for brevity/clarity sake its what I have right now.

In the [3,2,1] setup I have designated [2] as my "main" monitor in windows.
On a new Computer build with a fresh Windows install including a fresh 5.3 install when launching 5.3:
The initial splash appears on [3] and once complete the main application renders on [1]. Additionally spawned dialogs also open on [3] regardless of which monitor I currently have the main UI on. These initial launch and rendering behaviors do not track to traditional Windows last known state behavior. i.e. If I close an app on [3] it will open on the monitor it was closed on to the position and size it was previously closed on. This behavior has been around on previous iterations of my multi monitor desktop in all of v5 and I think going back to the last several releases of 4 as well.

With nahimic service running (part of ASUS realtek audio + Sonic Suite driver/software install) all versions of 5 hang while rendering main UI on [1]. Disabling nahimic (and losing sonic suite) unblocks the loading hang and 5.3 runs as expected with the non-standard monitor rendering behavior. Running 5.3 in admin mode circumvented this issue but I do not consider that a valid solution/even temporarily, not sure why admin allowed for the change in behavior.

After installing the nightly I tested launching both w/ Nahimic disabled, 5.3 still behaves as described above from a rendering perspective but does not crash. 5.4nightly renders on [2]!!! as would normally be expected/preferred.

I quit both, started nahimic again (no re-login/reboot) Sonic suite launched itself into system tray.
5.3 again repeated the same monitor selection crash, 5.4 launched and ran as expected!!!!! Even dialogs launched on main window as desired.

Then I tried the spice:
With Nahimic enabled I launched 5.4 and it rendered on main [2], then I moved it to [1] and closed it.
I relaunched it, splash rendered on main [2], main UI rendered on [1] but hung (just like like 5.3).

I had to disable nahimic, launch 5.4 to [1], move it back to main [2] close it. enable nahimic, relaunch 5.4 renders on [2] with no crash.

I tried to recover 5.3 w/ the same process but (disable nahmeic, launch to [1] close on [2], enable nahemic, relaunch 5.3 - but this still launched on [1] and hung.

So there is a very minimal improvement over 5.3 but it remembering close state, but is still having issues when not initially rendered to the primary windows display.

I hope the verbosity here helps further toward a more complete fix, keep me in the loop and Ill be happy to retest.

[Daniel M (SugarBooty)]

This update fixed the filename not being filled in but there are some issues:

• the default location is still in my home directory, not the last directory used
• the save portal does not start above the Cura window, I need to alt+tab to get to it
  • might be just a distro problem, happens elsewhere too
• there is a weird transparency on the bed 3d model
  • seems to be more apparent when not fullscreen

I am running Fedora 37 Gnome with an nvidia card

Its awesome that the filename was fixed though! That was the most annoying part. Thank you Devs!

[Jelle Spijker (jellespijker)]

there is a weird transparency on the bed 3d model

Are you using Wayland? I had that same issue on my KDE Wayland Ubuntu and on my KDE Wayland Manjaro. Updating to the latest KDE fixed that for me (earlier on Manjaro, which is a rolling release, then on Ubuntu) So it might be that the KDE people fixed a bug there.

[Mariska (MariMakes)]

Received this reply on the community for someone reporting the following on ChromeOS:. After installing Cura, I tried to slice a sample 3D model, but whenever I click "Open File", nothing happens. I also tried signing into my Ultimaker Account, but when I click "Sign in", nothing happens either.

I suggested a fix in another thread. But you might want to post this as a quick fix for anyone installing the Cura AppImage on ChromeOS. Simply installing a file manager lets Cura access the local filesystem. Perhaps packaging a simple QT file manager with the AppImage would be a better fix...

[Ted (GoguyT3D)]

As it turns out with this new build, the prime tower now prints correctly on the prime tower with both materials in each layer but now the supports included in the model print every other layer. Still more work to do

[Mariska (MariMakes)]

Hey Ted (@GoguyT3D),

I've hidden your other comments because they are off-topic.
The main reason for this nightly build is for people. have trouble with open/save file dialogs and using Ultimaker Cura on set-ups with multiple monitors or multiple windows,

But can I conclude that this build resolves #14945 ?

[Ted (GoguyT3D)]

No problem, thanks again for the help

[Aldo Hoeben (fieldOfView)]

This build seems to fix the performance issues with the combination of the Sidebar GUI plugin and the FancyZones PowerToy. At least, it does for me.

[Mariska (MariMakes)]

Oh! That's great ❤️‍🔥

[Jelle Spijker (jellespijker)]

super glad to hear that

[Aldo Hoeben (fieldOfView)]

Sofar I have not gotten confirmation, but on my system I see a huge difference running them side-by-side.

[Aldo Hoeben (fieldOfView)]

Somewhat unrelated, I find the changed theme refreshing.

[Mariska (MariMakes)]

Ha! I believe we tried to make it boring on purpose 😆🕴️
Mainly the saturation of the colors has been reduced.

[jszymon]

The Appimage crashed immediately on clicking save

The modern.Appimage almost solved the problem. I'm able to type in the file name box, the box is correctly prefilled.
I wrote 'almost solved' because the file dialog shows behind Cura window so it's invisible at first, need to bring it to the front.

[JRWood1981]

Running windows 11, did not solve the non-start issue

[Mariska (MariMakes)]

If you are having trouble with not starting. We do have a few workarounds available.

Could you try these if they are applicable:
Do you have multiple monitors? Does Cura start if you disable one of the monitors?
Do you have GPU Tweak OSD overlay enabled? Does Cura start if you disable that software?
Do you have a Ryzen Graphics card? Can you try this workaround? https://support.makerbot.com/s/article/1667412437627
Do you have the Nahimic audio enhancement service enabled? Can you try this workaround? #12102 (comment)

[Russell-S]

With respect to the Linux file save dialogue issue this appears to be partially fixed in this version.

The filename dialogue is now correctly filled in with the filename and the .gcode extension.
However the file save dialogue still does not default to the folder that the stl file was in which is what Cura 4 did (if I remember correctly).
Also the save window opens up behind the main cura window and so is not visible and you need to select it with either alt-tab or from the taskbar.

So that's great news with the filename being filled in now which was the major pain but if the other two things can also be sorted that would just be perfect.

Great work.

I'm using Linux Mint 20.3

[Mariska (MariMakes)]

Hey Russell-S,

Thanks for the update 😊
We have a ticket for Cura 5 that won't remember the path of the last used folder.
I'll raise it again with the team to make sure it's still on the radar. 👍

[jattie-ire]

I can confirm that this special build improves my Windows installation speed issues, however it is still not on par with 4.13.1. The installer for 4.x installs VS 2015 redistributable.

[Mariska (MariMakes)]

Thanks for the update 👍

[amoulart]

Hello,

I'm on win10 64, Dell studio 1747, I have 2 additional displays; one on HDMI port and another one on a USB2-HDMI Displaylink.
Main graphic board is an ATI Radeon HD4650.
In the past I could get Cura to work by launching it several times. Today, it just stopped working, I can see 5 instances of cura running in memory but nothing displayed and nothing significant (as far as I can say) in the log. Disconnecting the HDMI display or disabling them with WINDOWS+P doesn't help (I've not tested to disconnect the USB-HDMI one).
Clearing memory and launching again doesn't help; I can see sometimes the startup message but it disapears after the "loading UI..." step.

I've tried the nightly build with no success.
I can't find the Nahimic service on my system.

Reinstalling the 3.5.1 allowed me to start it tonight, I hope it will continue to work in the coming days.
I've tested to stop it and restart it with success :-)

Anyway I can't blame the developpers on that issue, I'm happy that this good software is free! :-)

[madhat81]

Thanks for your work. Can you please provide a Mac-Version?!

[Mariska (MariMakes)]

Hey madhat81,

You are right. It seemed to be missing.
I've added a PKG version. It should be exactly the same as the other builds.
Can you try it out and let us know?

[madhat81]

Hey madhat81,

You are right. It seemed to be missing. I've added a PKG version. It should be exactly the same as the other builds. Can you try it out and let us know?

Thank you, the package works and Cura runs great. Would it be possible to compile a version with the profile for the Sovol SV06 Plus? Thanks

[William F. Dudley Jr. (wfdudley)]

This fixes the "open file dialog won't open" bug in all versions 5.x for me.
Running Devuan GNU/Linux 4 (chimaera). Thank you.

[Mariska (MariMakes)]

Thanks for the update. Glad to hear. 😊

[49fl (lf94)]

I just did a pacman -Syu to update my system and didn't plan on doing anything 3D printing related today, but my partner actually brought something up, so I started up Cura and ... I can't open the open file dialog again. Nor save either. I tried this nightly build (after trying 5.2, 5.3) and it segfaults now :D. Before my system update today, it was ok. So I wonder if you'll hear some complaints from Arch users again...

[49fl (lf94)]

Here's a bit of an strace:

ioctl(2, TIOCGPGRP, [308329])           = 0
rt_sigaction(SIGCHLD, {sa_handler=0x55a0f7c9c7e0, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7fd47fd93ab0}, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7fd47fd93ab0}, 8) = 0
prlimit64(0, RLIMIT_NPROC, NULL, {rlim_cur=29308, rlim_max=29308}) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
openat(AT_FDCWD, "/tmp/.mount_UltiMab8kFYB/AppRun", O_RDONLY) = 4
newfstatat(AT_FDCWD, "/tmp/.mount_UltiMab8kFYB/AppRun", {st_mode=S_IFREG|0755, st_size=693, ...}, 0) = 0
ioctl(4, TCGETS, 0x7ffe2e70ea50)        = -1 ENOTTY (Inappropriate ioctl for device)
lseek(4, 0, SEEK_CUR)                   = 0
read(4, "#!/bin/bash\n\nscriptdir=$(dirname"..., 80) = 80
lseek(4, 0, SEEK_SET)                   = 0
prlimit64(0, RLIMIT_NOFILE, NULL, {rlim_cur=1024, rlim_max=512*1024}) = 0
fcntl(255, F_GETFD)                     = -1 EBADF (Bad file descriptor)
dup2(4, 255)                            = 255
close(4)                                = 0
fcntl(255, F_SETFD, FD_CLOEXEC)         = 0
fcntl(255, F_GETFL)                     = 0x8000 (flags O_RDONLY|O_LARGEFILE)
newfstatat(255, "", {st_mode=S_IFREG|0755, st_size=693, ...}, AT_EMPTY_PATH) = 0
lseek(255, 0, SEEK_CUR)                 = 0
read(255, "#!/bin/bash\n\nscriptdir=$(dirname"..., 693) = 693
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
pipe2([4, 5], 0)                        = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
rt_sigprocmask(SIG_BLOCK, [INT TERM CHLD], [], 8) = 0
lseek(255, -656, SEEK_CUR)              = 37
clone(child_stack=NULL, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fd47fce3a10) = 308338
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigaction(SIGCHLD, {sa_handler=0x55a0f7c9c7e0, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7fd47fd93ab0}, {sa_handler=0x55a0f7c9c7e0, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7fd47fd93ab0}, 8) = 0
close(5)                                = 0
rt_sigprocmask(SIG_BLOCK, [INT], [], 8) = 0
read(4, "/tmp/.mount_UltiMab8kFYB\n", 512) = 25
read(4, "", 512)                        = 0
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=308338, si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], WNOHANG, NULL) = 308338
wait4(-1, 0x7ffe2e70d8d0, WNOHANG, NULL) = -1 ECHILD (No child processes)
rt_sigreturn({mask=[INT]})              = 0
close(4)                                = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGINT, {sa_handler=0x55a0f7c9eee0, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fd47fd93ab0}, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fd47fd93ab0}, 8) = 0
rt_sigaction(SIGINT, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fd47fd93ab0}, {sa_handler=0x55a0f7c9eee0, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fd47fd93ab0}, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
read(255, "\nexport PYTHONPATH=\"$scriptdir/l"..., 693) = 656
pipe2([4, 5], 0)                        = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
rt_sigprocmask(SIG_BLOCK, [INT TERM CHLD], [], 8) = 0
lseek(255, -101, SEEK_CUR)              = 592
clone(child_stack=NULL, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fd47fce3a10) = 308339
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigaction(SIGCHLD, {sa_handler=0x55a0f7c9c7e0, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7fd47fd93ab0}, {sa_handler=0x55a0f7c9c7e0, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7fd47fd93ab0}, 8) = 0
close(5)                                = 0
rt_sigprocmask(SIG_BLOCK, [INT], [], 8) = 0
read(4, "UltiMaker-Cura-5.4.0-alpha+cura_"..., 512) = 55
read(4, "", 512)                        = 0
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=308339, si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], WNOHANG, NULL) = 308339
wait4(-1, 0x7ffe2e70d990, WNOHANG, NULL) = -1 ECHILD (No child processes)
rt_sigreturn({mask=[INT]})              = 0
close(4)                                = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGINT, {sa_handler=0x55a0f7c9eee0, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fd47fd93ab0}, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fd47fd93ab0}, 8) = 0
rt_sigaction(SIGINT, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fd47fd93ab0}, {sa_handler=0x55a0f7c9eee0, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fd47fd93ab0}, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
read(255, "if [ -f $scriptdir/$BIN ]; then\n"..., 693) = 101
newfstatat(AT_FDCWD, "/tmp/.mount_UltiMab8kFYB/UltiMaker-Cura-5.4.0-alpha+cura_10389_148-linux-modern", 0x7ffe2e70e5b0, 0) = -1 ENOENT (No such file or directory)
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
rt_sigprocmask(SIG_BLOCK, [INT TERM CHLD], [], 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [INT TERM CHLD], 8) = 0
rt_sigprocmask(SIG_SETMASK, [INT TERM CHLD], NULL, 8) = 0
clone(child_stack=NULL, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fd47fce3a10) = 308340
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGINT, {sa_handler=0x55a0f7c9eee0, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fd47fd93ab0}, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fd47fd93ab0}, 8) = 0
wait4(-1, PyInstaller/loader/pyimod02_importers.py:352: 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_UltiMab8kFYB/share/cura/resources/qml/Actions.qml" and "file:///tmp/.mount_UltiMab8kFYB/share/cura/resources/qml/Actions.qml"
file:///tmp/.mount_UltiMab8kFYB/share/cura/resources/qml/PrintSetupSelector/Recommended/RecommendedPrintSetup.qml:96:17: QML QQuickItem: Binding loop detected for property "height"
file:///tmp/.mount_UltiMab8kFYB/share/cura/resources/qml/PrintSetupSelector/Recommended/RecommendedPrintSetup.qml:96:17: QML QQuickItem: Binding loop detected for property "height"
file:///tmp/.mount_UltiMab8kFYB/share/cura/resources/qml/PrintSetupSelector/Custom/CustomPrintSetup.qml:163:13: QML ProfileWarningReset: Binding loop detected for property "width"
file:///tmp/.mount_UltiMab8kFYB/share/cura/resources/qml/PrintSetupSelector/Custom/CustomPrintSetup.qml:163:13: QML ProfileWarningReset: Binding loop detected for property "width"
file:///tmp/.mount_UltiMab8kFYB/share/cura/resources/qml/PrintSetupSelector/Custom/CustomPrintSetup.qml:163:13: QML ProfileWarningReset: Binding loop detected for property "width"
0x7ffe2e70e580, 0, NULL)      = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
--- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
wait4(-1, [{WIFSIGNALED(s) && WTERMSIG(s) == SIGSEGV && WCOREDUMP(s)}], 0, NULL) = 308340
rt_sigaction(SIGINT, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fd47fd93ab0}, {sa_handler=0x55a0f7c9eee0, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fd47fd93ab0}, 8) = 0
ioctl(2, TIOCGWINSZ, {ws_row=52, ws_col=266, ws_xpixel=1862, ws_ypixel=884}) = 0
ioctl(1, TCGETS, {c_iflag=ICRNL|IXON|IUTF8, c_oflag=NL0|CR0|TAB0|BS0|VT0|FF0|OPOST|ONLCR, c_cflag=B38400|CS8|CREAD, c_lflag=ISIG|ICANON|ECHO|ECHOE|ECHOK|IEXTEN|ECHOCTL|ECHOKE, ...}) = 0
newfstatat(AT_FDCWD, "/usr/lib/kitty/terminfo", {st_mode=S_IFDIR|0755, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/home/lee/.terminfo", 0x55a0f81d6080, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/share/terminfo", {st_mode=S_IFDIR|0755, st_size=4096, ...}, 0) = 0
access("/usr/lib/kitty/terminfo/x/xterm-kitty", R_OK) = 0
openat(AT_FDCWD, "/usr/lib/kitty/terminfo/x/xterm-kitty", O_RDONLY) = 4
newfstatat(4, "", {st_mode=S_IFREG|0644, st_size=3398, ...}, AT_EMPTY_PATH) = 0
read(4, "\32\1\25\0\34\0\17\0i\1\262\5xterm-kitty|KovIdTTY"..., 32768) = 3398
read(4, "", 28672)                      = 0
close(4)                                = 0
ioctl(1, TCGETS, {c_iflag=ICRNL|IXON|IUTF8, c_oflag=NL0|CR0|TAB0|BS0|VT0|FF0|OPOST|ONLCR, c_cflag=B38400|CS8|CREAD, c_lflag=ISIG|ICANON|ECHO|ECHOE|ECHOK|IEXTEN|ECHOCTL|ECHOKE, ...}) = 0
ioctl(1, TCGETS, {c_iflag=ICRNL|IXON|IUTF8, c_oflag=NL0|CR0|TAB0|BS0|VT0|FF0|OPOST|ONLCR, c_cflag=B38400|CS8|CREAD, c_lflag=ISIG|ICANON|ECHO|ECHOE|ECHOK|IEXTEN|ECHOCTL|ECHOKE, ...}) = 0
ioctl(1, TCGETS, {c_iflag=ICRNL|IXON|IUTF8, c_oflag=NL0|CR0|TAB0|BS0|VT0|FF0|OPOST|ONLCR, c_cflag=B38400|CS8|CREAD, c_lflag=ISIG|ICANON|ECHO|ECHOE|ECHOK|IEXTEN|ECHOCTL|ECHOKE, ...}) = 0
ioctl(1, TCGETS, {c_iflag=ICRNL|IXON|IUTF8, c_oflag=NL0|CR0|TAB0|BS0|VT0|FF0|OPOST|ONLCR, c_cflag=B38400|CS8|CREAD, c_lflag=ISIG|ICANON|ECHO|ECHOE|ECHOK|IEXTEN|ECHOCTL|ECHOKE, ...}) = 0
ioctl(1, TIOCGWINSZ, {ws_row=52, ws_col=266, ws_xpixel=1862, ws_ypixel=884}) = 0
ioctl(0, TIOCGWINSZ, {ws_row=52, ws_col=266, ws_xpixel=1862, ws_ypixel=884}) = 0
brk(0x55a0f81fd000)                     = 0x55a0f81fd000
openat(AT_FDCWD, "/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 4
newfstatat(4, "", {st_mode=S_IFREG|0644, st_size=2998, ...}, AT_EMPTY_PATH) = 0
read(4, "# Locale name alias data base.\n#"..., 4096) = 2998
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/usr/share/locale/en_US.UTF-8/LC_MESSAGES/bash.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_US.utf8/LC_MESSAGES/bash.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_US/LC_MESSAGES/bash.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en.UTF-8/LC_MESSAGES/bash.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en.utf8/LC_MESSAGES/bash.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en/LC_MESSAGES/bash.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
newfstatat(2, "", {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0x9), ...}, AT_EMPTY_PATH) = 0
openat(AT_FDCWD, "/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
write(2, "/tmp/.mount_UltiMab8kFYB/AppRun:"..., 118/tmp/.mount_UltiMab8kFYB/AppRun: line 25: 308340 Segmentation fault      (core dumped) $scriptdir/UltiMaker-Cura "$@"
) = 118
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_DUMPED, si_pid=308340, si_uid=1000, si_status=SIGSEGV, si_utime=1245 /* 12.45 s */, si_stime=224 /* 2.24 s */} ---
wait4(-1, 0x7ffe2e70de10, WNOHANG, NULL) = -1 ECHILD (No child processes)
rt_sigreturn({mask=[]})                 = 0
read(255, "", 693)                      = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
exit_group(139)                         = ?
+++ exited with 139 +++

[49fl (lf94)]

For what it's worth, cura -platformtheme gtk3 works perfectly! I got this from the various comments on the Arch packages of Cura.

[Mariska (MariMakes)]

Hey 49fl (@lf94),

Thanks for flagging this!
That's why we ask people to test 😊

I'll bring it up to the team to see what they can do to improve it.
Fingers crossed 🤞

[Joseph Dalrymple (Swivelgames)]

49fl (@lf94) This is actually what I'm using right now to get around this issue. Thanks for this!

[Joseph Dalrymple (Swivelgames)]

Arch Linux.

After attempting to open the dialog, I got a Seg Fault:

PyInstaller/loader/pyimod02_importers.py:352: 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_UltiMa01SEMe/share/cura/resources/qml/Actions.qml" and "file:///tmp/.mount_UltiMa01SEMe/share/cura/resources/qml/Actions.qml"
file:///tmp/.mount_UltiMa01SEMe/share/cura/resources/qml/PrintSetupSelector/Recommended/RecommendedPrintSetup.qml:96:17: QML QQuickItem: Binding loop detected for property "height"
file:///tmp/.mount_UltiMa01SEMe/share/cura/resources/qml/PrintSetupSelector/Recommended/RecommendedPrintSetup.qml:96:17: QML QQuickItem: Binding loop detected for property "height"
/tmp/.mount_UltiMa01SEMe/AppRun: line 25: 256993 Segmentation fault      (core dumped) $scriptdir/UltiMaker-Cura "$@"

[Mariska (MariMakes)]

Hey Joseph Dalrymple (@Swivelgames),

I showed your report to the team but we are missing some information.
Can you reproduce the crash consistently and are you getting this window?
Could you scroll all the way down and share a screenshot with us?

It would also help if you let us know more about your set-up, for example if you have multiple monitors.

[Joseph Dalrymple (Swivelgames)]

Mariska (@MariMakes) Unfortunately I'm not getting the crash dialog at all. It just dies. If I run it via terminal, the output I posted above is what I get.

[Mariska (MariMakes)]

Hey Khronos666,

Извините, я не говорю по-русски, но я думаю, что все еще могу вам помочь.

What you are reporting doesn't seem to be related to the PyQT update.
Do you mind creating a bug report for the individual issues by completing this template:
https://github.com/Ultimaker/Cura/issues/new/choose?

[Khronos666]

Version 5.4.0 has been released ... The bug was never fixed... damn, since version 5.3 alpha pointed out the incorrectness of this setting ...
I am glad that you are developing the project and introducing new functions, but again you are breaking already working ones ...
but this option is very useful...on some plastics, she glues the seam in thin walls ...
is it really only me who has such a bug on all versions of 5.x.x?

it works like this - https://github.com/Ultimaker/Cura/assets/123404675/a7f856ae-6efe-4ddc-8c62-63632c84e4a9

it doesn't work that way correctly - https://github.com/Ultimaker/Cura/assets/123404675/647478df-bbe7-4286-81c0-4ec5dda6ff3f

it doesn't work that way at all - https://github.com/Ultimaker/Cura/assets/123404675/16dc1fea-c4f8-4ec7-9c05-f8ff89aed9d6

[Mariska (MariMakes)]

This issue seems unrelated to this nightly.
I'll close this discussion and continue it here:
#15820

[Bryan Hunwardsen (bryanhunwardsen)]

Since 5.4 releases without addressing multi monitor issues, any chance this completely breaking bug can be picked up in a 5.5 alpha ??? It seems further tracking here is no longer useful?

[Mariska (MariMakes)]

Hey Bryan Hunwardsen (@bryanhunwardsen),

When reading your original comment, I was under the impression your issue was resolved. But after rereading it, I see that you are still encountering some issues.

It would indeed be easier for us to track what is going on if you create a new issue using the given template here:
https://github.com/Ultimaker/Cura/issues/new/choose

Please keep in mind that it's more valuable for us to have multiple separate tickets for separate problems. That way we can address and resolve them individually.

Thanks for reminding us that it's still an issue because I don't encounter this and I was under the impression that this was resolved. 🙈

[Jonas (printingotb)]

THIS FIXED IT FOR ME!!
I haven't read all the comments here or tried this build but I was able to fix the issue by moving this driver to another folder!!
I found it when installing OrcaSlicer and got this warning:
Maybe check if OrcaSlicer detects other incompatible files on other computers which still has issues?

I'm not sure if my system needs it though.