search

msys2 / MINGW-packages

Package scripts for MinGW-w64 targets to build under MSYS2.
https://packages.msys2.org
BSD 3-Clause "New" or "Revised" License
2.27k stars 1.21k forks source link

Several errors with "zed" command in UCRT64 - unable to open program #21459

Open DarwinsCorn opened 3 months ago

DarwinsCorn commented 3 months ago

Description / Steps to reproduce the issue

Proceeded to type:

pacman -S mingw-w64-ucrt-x86_64-zed

installed succesfully

Expected behavior

Expected to type "zed" on the UCRT64 shell to run Zed.

Actual behavior

Errors showed up when "zed" was typed at the prompt with the following result (I'm including the prompt where I'm trying to reinstall again to ensure nothing was missed, and it did fine and then followed by typing "zed") Also, I see its mentions an unsupported device? I'm including further down my computer info in case this further helps.

dietr@LAPTOP-RNFHFAQS UCRT64 ~
$ pacman -S mingw-w64-ucrt-x86_64-zed
warning: mingw-w64-ucrt-x86_64-zed-0.144.4-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) mingw-w64-ucrt-x86_64-zed-0.144.4-1

Total Installed Size:  106.34 MiB
Net Upgrade Size:        0.00 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                                                           [##################################################] 100%
(1/1) checking package integrity                                                         [##################################################] 100%
(1/1) loading package files                                                              [##################################################] 100%
(1/1) checking for file conflicts                                                        [##################################################] 100%
(1/1) checking available disk space                                                      [##################################################] 100%
:: Processing package changes...
(1/1) reinstalling mingw-w64-ucrt-x86_64-zed                                             [##################################################] 100%

dietr@LAPTOP-RNFHFAQS UCRT64 ~
$ zed
[2024-07-21T13:19:30-04:00 ERROR] The bitmap pixel format is unsupported. (0x88982F80)
[2024-07-21T13:19:30-04:00 ERROR fs.rs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
[2024-07-21T13:19:30-04:00 ERROR fs.rs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
[2024-07-21T13:19:30-04:00 ERROR extension_store.rs] Error("EOF while parsing a value", line: 1, column: 0)
[2024-07-21T13:19:30-04:00 ERROR fs.rs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
[2024-07-21T13:19:30-04:00 ERROR zed::reliability] {
  "thread": "main",
  "payload": "called `Result::unwrap()` on an `Err` value: NoSupportedDeviceFound",
  "location_data": {
    "file": "crates\\gpui\\src\\platform\\windows\\window.rs",
    "line": 971
  },
  "backtrace": [],
  "app_version": "0.144.4",
  "release_channel": "Zed",
  "os_name": "Windows",
  "os_version": "10.0.19045",
  "architecture": "x86_64",
  "panicked_on": 1721582370818,
  "installation_id": "b8280e21-154e-4ccf-a9f4-2cb6c9e41573",
  "session_id": "9b99ea0a-6979-4906-9285-8e29385c9406"
}

Laptop config:

OS Name Microsoft Windows 10 Home
Version 10.0.19045 Build 19045
Other OS Description    Not Available
OS Manufacturer Microsoft Corporation
System Name LAPTOP-RNFHFAQS
System Manufacturer SAMSUNG ELECTRONICS CO., LTD.
System Model    950XCJ/951XCJ/950XCR
System Type x64-based PC
System SKU  SCAI-A5A5-A5A5-A5A5-PRFD
Processor   Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz, 2304 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date   American Megatrends Inc. P10RFD.058.230116.XW, 1/16/2023
SMBIOS Version  3.2
Embedded Controller Version 255.255
BIOS Mode   UEFI
BaseBoard Manufacturer  SAMSUNG ELECTRONICS CO., LTD.
BaseBoard Product   NP950XCJ-K01US
BaseBoard Version   SGLA368A0P-C01-G001-S0001+10.0.18363
Platform Role   Mobile
Secure Boot State   On
PCR7 Configuration  Elevation Required to View
Windows Directory   C:\WINDOWS
System Directory    C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale  United States
Hardware Abstraction Layer  Version = "10.0.19041.3636"
User Name   LAPTOP-RNFHFAQS\dietr
Time Zone   Eastern Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory   7.81 GB
Available Physical Memory   1.03 GB
Total Virtual Memory    31.4 GB
Available Virtual Memory    15.3 GB
Page File Space 23.5 GB
Page File   C:\pagefile.sys
Kernel DMA Protection   On
Virtualization-based security   Running
Virtualization-based security Required Security Properties  
Virtualization-based security Available Security Properties Base Virtualization Support, Secure Boot, DMA Protection, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control
Virtualization-based security Services Configured   
Virtualization-based security Services Running  
Device Encryption Support   Elevation Required to View
A hypervisor has been detected. Features required for Hyper-V will not be displayed.

Verification

Windows Version

MINGW64_NT-10.0-19045

MINGW environments affected

Are you willing to submit a PR?

No response

ognevny commented 3 months ago

reported upstream: https://github.com/zed-industries/zed/issues/13575

aranapatona commented 2 months ago

same problemhere:

`[2024-08-09T16:11:11-07:00 ERROR fs.rs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] } [2024-08-09T16:11:12-07:00 ERROR fs.rs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] } [2024-08-09T16:11:12-07:00 ERROR main.rs] error parsing path argument: The filename, directory name, or volume label syntax is incorrect. (os error 123) [2024-08-09T16:11:12-07:00 ERROR fs.rs] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] } [2024-08-09T16:11:13-07:00 ERROR blade_graphics::hal::init] Missing Vulkan entry points: LibraryLoadFailure(LoadLibraryExW { source: Os { code: 126, kind: Uncategorized, message: "The specified module could not be found." } }) Zed failed to open a window: VulkanLoadingError(LibraryLoadFailure(LoadLibraryExW { source: Os { code: 126, kind: Uncategorized, message: "The specified module could not be found." } })). See https://zed.dev/docs/linux for troubleshooting steps.

OS Name: Microsoft Windows 10 Pro OS Version: 10.0.19045 N/A Build 19045 OS Manufacturer: Microsoft Corporation OS Configuration: Member Workstation OS Build Type: Multiprocessor Free Registered Owner: admin Registered Organization: Microsoft Product ID: 00330-80000-00000-AA490 Original Install Date: 9/20/2023, 12:19:04 PM System Boot Time: 7/22/2024, 8:46:36 AM System Manufacturer: Dell Inc. System Model: Latitude E7450 System Type: x64-based PC `

ognevny commented 2 months ago

there is still nothing to do with that. in some machines zed work, in other not

MaD70 commented 1 month ago

@aranapatona wrote:

same problem here:

[...] [2024-08-09T16:11:13-07:00 ERROR blade_graphics::hal::init] Missing Vulkan entry points: LibraryLoadFailure(LoadLibraryExW { source: Os { code: 126, kind: Uncategorized, message: "The specified module could not be found." } }) Zed failed to open a window: >>VulkanLoadingError<<(LibraryLoadFailure(LoadLibraryExW { source: Os { code: 126, kind: Uncategorized, message: "The specified module could not be found." } })). See https://zed.dev/docs/linux for troubleshooting steps. [...]

I have the same problem and was initially puzzled. I'm not a gamer and so I didn't immediately noticed the importance of that missing Vulkan error. Vulkan is a low-level graphic API usually supported at the device driver level.

The machine were I tried to test Zed is a very old machine and so its graphic card driver doesn't support Vulkan (my NVidia graphic card on that machine broke and so it's using a device driver for the integrated Intel G33/G31 Express chipset which support DirectX 9.0c). I searched for a Vulkan-to-DirectX 9 translation layer but apparently it doesn't exist. But there is at least a DirectX 12-to-Vulkan translation layer, Dozen (repository).

Conclusion: if the device driver for your graphic card/chipset doesn't support Vulkan (or at least DirectX 12 and you know how to compile and install Dozen translation layer) there is no way to run Zed on such machine at the moment.

Update: apparently there is a translation layer called Ashes that should support DirectX 9 (to 11), according to this chart on Vulkan web site, on Vulkan Porting Layers page:

Vulkan

but from what I understand at a glance it's not transparent, a patch to Zed source is needed to use it.

Update 2: this information is NOT correct. See: Are DirectX 9 and 10 actually supported? #282

Ashes only supports DirectX11, so yes, it's a mistake from Vulkan's website

Originally posted by @DragonJoker in https://github.com/DragonJoker/Ashes/issues/282#issuecomment-1818429938