Arch Linux

twelvenight

Member

Registered: 2023-10-22

Posts: 22

Can`t start vmare workstation

I just change DE(x11) to WM(wayland) that use hyprland,but I can`t start my vmware-workstation
my vmware verstion:VMware Workstation 17.0.1 build-21139696

The error is here,
◆ ~ ❯❯❯ vmware
(vmware:37013): Gtk-WARNING **: 12:34:48.913: cannot open display: :0

I search that just change the display 1 to :0, but is still the same error

twelvenight

Member

Registered: 2023-10-22

Posts: 22

Re: Can`t start vmare workstation

I just change DE(x11) to WM(wayland) that use hyprland,but I can`t start my vmware-workstation
my vmware verstion:VMware Workstation 17.0.1 build-21139696

The error is here,
◆ ~ ❯❯❯ vmware
(vmware:37013): Gtk-WARNING **: 12:34:48.913: cannot open display: :0

I search that just change the display 1 to :0, but is still the same error

the change result is even the hyprland can`t start,cause the xbc error

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,616

Re: Can`t start vmare workstation

That message suggest vmware ws is trying to use an X display and there may be something wrong with your Xwayland setup .

What does

$ glxinfo -B   #comes_with_mesa-utils

show ?

Last edited by Lone_Wolf (2023-10-26 07:32:56)

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

twelvenight

Member

Registered: 2023-10-22

Posts: 22

Re: Can`t start vmare workstation

That message suggest vmware ws is trying to use an X display and there may be something wrong with your Xwayland setup .

What does

$ glxinfo -B   #comes_with_mesa-utils

show ?

here

name of display: :1
display: :1  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 6144 MB
    Total available memory: 6144 MB
    Currently available dedicated video memory: 4570 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 535.113.01
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 535.113.01
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 535.113.01
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Last edited by twelvenight (2023-10-27 02:06:43)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,616

Re: Can`t start vmare workstation

is nvidia DRM KMS enabled ?

If yes, does prepending  GDK_BACKEND=x11 to the vmware command help ?

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 12,744

Website

Re: Can`t start vmare workstation

Mod note: Moving to AUR Issues.

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

twelvenight

Member

Registered: 2023-10-22

Posts: 22

Re: Can`t start vmare workstation

is nvidia DRM KMS enabled ?

If yes, does prepending  GDK_BACKEND=x11 to the vmware command help ?

It`s help,but I can just use terminal to open it,something like rofi still can`t open it

Last edited by twelvenight (2023-10-28 11:55:34)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,616

Re: Can`t start vmare workstation

Rofi probably uses a .desktop file provided by the vmware installation .

Read https://wiki.archlinux.org/title/Deskto … ktop_files for info how to find & modify such files.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky