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

Display going nuts #2537

Closed
yeetusdeletus69 opened this issue May 16, 2021 · 2 comments
Closed

Display going nuts #2537

yeetusdeletus69 opened this issue May 16, 2021 · 2 comments
Labels
duplicate This issue or pull request already exists

Comments

@yeetusdeletus69
Copy link

Describe the issue
A clear and concise description of what the issue is. BEFORE SUBMITTING YOUR ISSUE, PLEASE LOOK AT THE PINNED ISSUES AND USE THE SEARCH FUNCTION TO MAKE SURE IT IS NOT ALREADY REPORTED. ALWAYS COMMENT ON AN EXISTING ISSUE INSTEAD OF MAKING A NEW ONE.

Configuration

  • UTM Version: 2.0.28
  • OS Version: 11.3.1
  • Intel or Apple Silicon? Sillicon

Crash log
If the app crashed, you need a crash log. To get your crash log, open Console.app, go to Crash Reports, and find the latest entry for either QEMU, QEMUHelper, or qemu-*. Right click and choose Reveal in Finder. Attach the report here.

Debug log
For all issues, including crashes, you should attach a debug log. Open UTM, and open the settings for the VM you wish to launch. Near the top of the QEMU page is Debug Log. Turn it on and save the VM. After you experience the issue, open the VM settings again and select Export Log... and attach it here. It doesn't crash. it just freezes and never crashes

Upload VM
(Optional) If possible, upload the config.plist inside the .utm. If you do not have this, you can upload the entire .utm but note this contains your personal data. Since Github has an attachment size limit, you may want to upload to another service such as Google Drive. Link it here.

@conath
Copy link
Contributor

conath commented May 16, 2021

Could you please update your issue with a detailed, concise description of the problem? Just a title of "Display going nuts" without any context is not helpful. Thanks!

@osy osy added the duplicate This issue or pull request already exists label Jul 10, 2021
@osy
Copy link
Contributor

osy commented Jul 10, 2021

Duplicate of #2569

@osy osy marked this as a duplicate of #2569 Jul 10, 2021
@osy osy closed this as completed Jul 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

4 participants
@conath @osy @yeetusdeletus69 and others