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

Windows 11 24H2 run zed release after build just flash and off #18740

Closed
1 task done
aycact opened this issue Oct 4, 2024 · 5 comments
Closed
1 task done

Windows 11 24H2 run zed release after build just flash and off #18740

aycact opened this issue Oct 4, 2024 · 5 comments
Labels
duplicate Additional reports of an existing issue

Comments

@aycact
Copy link

aycact commented Oct 4, 2024

Check for existing issues

  • Completed

Describe the bug / provide steps to reproduce it

Windows 11 24H2 Enterprise installed on REFS instead of NTFS run zed after cargo build --release from zed->target->release just flash up the terminal and then off although it still exist in task manager
Last Windows install on 23H2 and NTFS still worked normally

Environment

Device name AYCLQT-LAPTOP
Processor AMD Ryzen 5 5500U with Radeon Graphics 2.10 GHz
Installed RAM 24,0 GB (21,8 GB usable)
Device ID 70F026ED-2DD2-4D21-B78B-891C34F85506
Product ID 00328-90000-00000-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Edition Windows 11 Enterprise
Version 24H2
Installed on ‎29/‎09/‎2024
OS build 26100.1876
Experience Windows Feature Experience Pack 1000.26100.23.0

If applicable, add mockups / screenshots to help explain present your vision of the feature

image

If applicable, attach your Zed.log file to this issue.

No response

@aycact aycact added admin read bug [core label] labels Oct 4, 2024
@thelazurite-cell
Copy link

also happening for me on a windows 11 machine. I think it's something to do with the new changes around theme background colors
[2024-10-04T17:34:51+01:00 ERROR fs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
[2024-10-04T17:34:52+01:00 ERROR blade_graphics::hal::init] No composite alpha flag for transparency: OPAQUE | INHERIT
[2024-10-04T17:34:52+01:00 ERROR blade_graphics::hal::init] No composite alpha flag for transparency: OPAQUE | INHERIT
[2024-10-04T17:34:52+01:00 ERROR blade_graphics::hal::init] No composite alpha flag for transparency: OPAQUE | INHERIT
[2024-10-04T17:34:52+01:00 ERROR fs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
[2024-10-04T17:34:52+01:00 ERROR gpui] Error { code: HRESULT(0x80070057), message: "The parameter is incorrect." }
[2024-10-04T17:34:52+01:00 ERROR gpui] Error { code: HRESULT(0x80070057), message: "The parameter is incorrect." }
[2024-10-04T17:34:52+01:00 ERROR assistant] no worktrees when constructing LocalLspAdapterDelegate

@aycact
Copy link
Author

aycact commented Oct 4, 2024

I think it is this issue

@thelazurite-cell
Copy link

thelazurite-cell commented Oct 4, 2024

Yeah, that seems to line up. I think this may be the same issue as described in

@aycact
Copy link
Author

aycact commented Oct 4, 2024

Yeah, that seems to line up. I think this may be the same issue as described in #18610 also?

Yes, it is. #18705 is to fix #18610, what we can do now is wait for merge pull request from #18705

@notpeter
Copy link
Member

notpeter commented Oct 4, 2024

@notpeter notpeter closed this as completed Oct 4, 2024
@notpeter notpeter added duplicate Additional reports of an existing issue and removed bug [core label] triage labels Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Additional reports of an existing issue
Projects
None yet
Development

No branches or pull requests

3 participants