Spory kłopot z VMWare

[Yattaman]

Witajcie moi drodzy, przychodzę dzisiaj do Was z małym (albo dużym jak kto woli) problemem.
Mianowicie VMWare od jakiegoś czasu (nie pamiętam dokładnie od kiedy) robi mi psikusy w postaci wyłączania interfejsu 😮
Postaram się opisać:
Odpalamy VMWare, uruchamiamy maszynę wirtualną, no i każdorazowe przesuniecie myszką poza obszar "pulpitu" maszyny wirtualnej powoduje wyłączenie interfejsu (znika sobie) i muszę uruchomić ponownie - ale procesy działają dalej, czyli wszystko na niej działa dalej jakby nie wyłączyła się.

Czy to problem Waylanda, czy VMWare samego w sobie, czy może jednak problem KDE, czy CachyOS?
Takie rzeczy wypluwa terminal w momencie zadziałanie tego wyłączenia:

Kod [Zaznacz] Rozwiń

❯ vmware
[2025-11-16 14:10:11.261] [MANGOHUD] [error] [battery.cpp:29] No battery found
[2025-11-16 14:10:11.263] [MANGOHUD] [info] [gpu.cpp:95] Set renderD128 as active GPU (id=1002:7480 pci_dev=0000:03:00.0)

(vmware:68307): Gdk-WARNING **: 14:10:18.752: The program 'vmware' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 24268 error_code 2 request_code 135 (XKEYBOARD) minor_code 8)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Mangohudem się nie przejmować, niechcąco włączyłem :) Nie ma na to wpływu.

[linux4ever]

@Yattaman Aktualizowałeś sterowniki i wayland?

Czy przełączenie na X11 powoduje to samo ?

[Yattaman]

@Yattaman Aktualizowałeś sterowniki i wayland?

Czy przełączenie na X11 powoduje to samo ?

No na CachyOS, raczej wszystko mam aktualne :)
Nie przełączam się na X11, ale jakiś czas wcześniej działało bez zarzutu na Wayland... Coś zepsuli?

[linux4ever]

@Yattaman Niby tak; https://bbs.archlinux.org/viewtopic.php?id=293516

Recent Wayland bugs in KDE include issues with session restoration (like restoring Konsole tabs), graphical glitches (such as lines appearing when sliding windows), and problems with specific applications (like the file dialog for some Flatpaks).

 Additionally, some users have reported critical issues like a black screen upon login, and problems with features like the clipboard and remote gaming pop-ups.
 Session and window management Restoration issues: Applications may not restore to their correct virtual desktop or remember their state, such as Konsole tabs or windows minimized to the system tray.

Window position: There is a known issue where Wayland windows may not save or restore their position correctly.Ctrl+C bug: In some setups, using Ctrl+C in a Wayland session launched with SDDM can cause the environment to crash.

 Graphical issues Sliding windows: Some users have reported seeing flickering lines appear on the desktop when moving windows.Konsole glitch: Since updating to KDE Frameworks 6.10, some users have reported a graphical glitch in the Konsole window, such as a thin vertical gray line.

 Application-specific bugs File/folder selection: The file/folder selection dialog may not show auto-completion suggestions in some situations.Flatpak dialogs: Some Flatpak applications may not show any files in the Open/Save dialog if they specify supported mimetypes using file globbing

.Clipboard: There are reports of a widespread bug where the clipboard is not working as expected.
Remote play pop-ups: When using Steam Remote Play, pop-ups may appear repeatedly, and there's no option to "allow in future sessions".

Critical and display-related issues Black screen: Some users have experienced a black screen upon login, sometimes fixed by reinstalling fingerprint-related drivers.

NVIDIA specific: There have been reports of a bug related to explicit sync drivers, which may affect performance.High CPU usage: Some users reported Wayland running at (1000 %) CPU usage after a recent update.

 Other issues Vietnamese input: Vietnamese input may not work in Wine applications.Power saving: Power saving features may not be active in some Wayland sessions. It's important to note that some bugs might be specific to certain hardware, drivers, or software versions and are being addressed in newer releases of KDE Frameworks and Plasma.

https://community.kde.org/Plasma/Wayland_Known_Significant_Issues

[Yattaman]

No ta, czyli czekać aż naprawią... ehhh Co będzie prawie identycznie wydajne i podobnie się obsługiwało? Virtualbox jest jakiś toporny :)

[linux4ever]

No ta, czyli czekać aż naprawią... ehhh Co będzie prawie identycznie wydajne i podobnie się obsługiwało? Virtualbox jest jakiś toporny :)

Gnome-boxes to oparte o QEMU:

To install GNOME Boxes on Arch Linux, use the command
sudo pacman -S gnome-boxes and then install the necessary virtualization packages qemu and libvirt by running sudo pacman -S qemu libvirt edk2-ovmf virt-manager.
1. Install GNOME Boxes and dependencies

    Open your terminal.
    Run the following command to install GNOME Boxes:

sudo pacman -S gnome-boxes

Install the virtualization backend and other required tools:

sudo pacman -S qemu libvirt edk2-ovmf virt-manager

2. Enable and start the libvirt service

    Enable the libvirtd service to start on boot:
   

sudo systemctl enable libvirtd.service

Start the libvirtd service immediately:


sudo systemctl start libvirtd.service

Tyle ode mnie.