The printer is a LulzBot Taz 6. For the profile, do you mean the version of Cura I am using? If so, I am using 21.03. In Cura, I change the material ease of us to "Experimental" after which I chose brassFill (colorFab) for the material. If you need any more information, please ask and I'll answer it to the best of my ability.

Looks like this was solved in version 21.08. Thanks!

Which printer and profile?

I still get the issue on that machine using any version newer than the special v19.13 they gave to me during troubleshooting. None of the newer versions they said would be fixed have worked to fix my issue. I never really had the time to troubleshoot it with them anymore and had a working version so it wasn't a big deal. I will open this back up in hopes that they see it for you. Good luck.

Here is the crash log:

I know this thread is nearly a year old, but I'm experiencing the exact same issue as the original poster (switching between full/simple modes, opening printer settings/preferences, etc. all result in an errorless crash to desktop), with V21.04, running on Windows 7, 64 bit. Interestingly, if I delete all the profile .ini files (/users/[myname]/.cura/21.04/) and use the wizard to set up a new machine, everything is OK for that one instance. Closing the program and reopening will bring back the same 'silent' crash to desktop when switching modes/clicking menu items.

What kind of files do you mean, error code files?

This also happened a few times on my MBP on OS X 10.12.5. Cura 21.4 on long 4,6 and 8 hour prints. Alternatively, the Windows version, did all the prints without the app crashing. What files would you want if I have them?

Alright I'll have him add the user in the dialout group and see if that helps.

As a side note, cura shouldn't need to be run as root. Applications that don't have to run as root it is better to have them run as the regular user. So sudo isn't needed. The user would have to be in the correct group that has access to the USB device, such as /dev/ttyACM0. In Debian, that is the "dialout" group.

rCURAee4e9c165fbd Fixed the issue.

rCURAcb1af1a5c26b is applied to master branch of cura also.

@alexei IC3D ABS will go into intermediate

@karrad , which category IC3D profiles should be assigned to?
i.e. Beginner,Intermediate,Advanced or Expert?

This is done with https://code.alephobjects.com/rCURAacabee40161b0d1eda1bfc61436bdc0966be0279

Reporting the same thing on MacOS Sierra 10.12.5.

I believe it has nothing to do with the screen resolution, but HiDPI Window Scaling.
I also have an UHD Screen (3200 x 1800), and the control button works when I reset the Window Scaling to 1 (instead of 2)

I have this exact issue, and I'm running the same version of Cura and macOS.

Flashing 156738 bytes
Verifying 156738 bytes
Unknown M code:907
Unknown M code:907
Unknown M code:18
Unknown M code:300
Flashing 156738 bytes
Verifying 156738 bytes
Unknown M code:907
Unknown M code:907
Unknown M code:18
Unknown M code:300

• Error in `/usr/bin/python': double free or corruption (fasttop): 0x00007f0c7c002240 ***

Aborted