Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cura 5.0 hangs/crashes on multi-monitor setup #12379

Closed
2 tasks
usernametakenaaaa opened this issue May 28, 2022 · 7 comments
Closed
2 tasks

Cura 5.0 hangs/crashes on multi-monitor setup #12379

usernametakenaaaa opened this issue May 28, 2022 · 7 comments
Labels
Status: Duplicate Duplicate of another issue. Type: Bug The code does not produce the intended behavior.

Comments

@usernametakenaaaa
Copy link

Application Version

5.0

Platform

Windows 10

Printer

Ultimaker S3

Reproduction steps

Main monitor: Nvidia GPU
Second monitor: Intel onboard GPU

Crash #1

  1. Start Cura 5
  2. Move the window to right side (Intel)
  3. restart Cura 5 and it will permanently crash, also after reinstalling (config file is persistent)

Crash #2

  1. Start Cura 5 (it opens on Main window, left, Nvidia)
  2. Click on Marketplace and Cura will permanently hang/crash

Bug #3

  1. Start Cura 5
    -> A splashscreen will open on 2nd Monitor (Intel) while Cura opens on Primary monitor

Some Dialogs like Settings open correctly, some dialogs like "changes to profile" or "marketplace" open on second monitor with an immediate application crash

Actual results

see reproduction

Expected results

  1. No hard crashes
  2. do not splashscreen on wrong monitor
  3. Uninstallation should also ask to remove configuration

Checklist of files to include

  • Log file
  • Project file

Additional information & file uploads

No logfile entries on the crashes

@usernametakenaaaa usernametakenaaaa added the Type: Bug The code does not produce the intended behavior. label May 28, 2022
@usernametakenaaaa
Copy link
Author

I forgot to add:
To avoid the hard crashes:

  1. Windows + P
  2. Set "Second Monitor only" (windows sees the Intel always as primary even if not set as main)
  3. start cura -> it will work fine now. As long as you don't dare use second screen

@usernametakenaaaa
Copy link
Author

One more update:
I've changed Intel to Nvidia dual GPU which is more common (so it is a normal dual monitor setup)
I also exchanged Monitor 1 and 2 so Windows correctly maps "primary" with "main" and "1"
The crashes are still persistent which means Cura does not work at all as soon as 2 monitors are connected to a PC, you might want to give at least one more monitor to the QA employee for the future

@Ghostkeeper
Copy link
Collaborator

Duplicate of #12264.

Please report only one bug per issue, or it might get confusing which issues have already been fixed and which haven't.

@Ghostkeeper Ghostkeeper added the Status: Duplicate Duplicate of another issue. label Jun 1, 2022
@nallath
Copy link
Member

nallath commented Jul 26, 2022

. Fix this pathetic issue, developers. I would die of shame for putting out something that can't even work with a basic setup like a dual monitor. Pathetic.

Goodbye!

@cmp-nct
Copy link

cmp-nct commented Oct 31, 2022

This has not been completed, it crashes consistently.
Windows 10 as well as Windows 11.

@ataweg
Copy link

ataweg commented May 28, 2023

see also issue #12197 (comment)
I solve the porblem for me.

@PhotoJoeCA
Copy link

Late February 2024 checking in: Three monitors on a desktop (3080). . . this is still an issue as of today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Duplicate Duplicate of another issue. Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

7 participants
@ataweg @Ghostkeeper @nallath @usernametakenaaaa @cmp-nct @PhotoJoeCA and others