On 5/29/2022 at 7:43 AM, ahoeben said:In previous versions, where this also happened to people, this could be fixed by unchecking the "Restore window position on start" option in the General preferences. Does that help in Cura 5.0?
I literally tried everything. I stopped after trying to fix their mess in the source code as creating a working development environment is more difficult than writing a complex linux kernel module from scratch.
There is nothing you can do except for disabling all secondary monitors entirely to make it not crash.
I also made a bug report in Beta and I made one for Release version which was never even responded to, that said they don't seem to respond to any of the thousands of reports.
Recommended Posts
Top Posters In This Topic
21
8
8
5
Popular Days
May 24
12
May 18
11
May 17
9
Jun 6
8
Top Posters In This Topic
GregValiant 21 posts
ahoeben 8 posts
Super_paulie 8 posts
Yamie 5 posts
Popular Days
May 24 2022
12 posts
May 18 2022
11 posts
May 17 2022
9 posts
Jun 6 2022
8 posts
Popular Posts
ahoeben
Here's a start: https://gist.github.com/fieldOfView/d3913c610c761fcfbc7fb4f65e77b45c
10r3n20
Thanks @ahoeben for providing this instructions! For people interested in further customising their theme I made an overview explaining the main variables, With 5.0 we hugely reduced the amount o
fvrmr
Hi all, Today we release Ultimaker Cura 5.0! After multiple special beta releases to test our new slicing engine (formerly known as Arachne), the new slicing Engine is finally here. This new eng
Posted Images
gr5 2,229
It might be helpful to publish the log file (cura.log). It can be found here:
%APPDATA%\cura\<Cura version>\cura.log (Windows)
$USER/Library/Application Support/cura/<Cura version>/cura.log (OSX)
$USER/.local/share/cura/<Cura version>/cura.log (Ubuntu/Linux)
Link to post
Share on other sites