spice issueshttps://gitlab.freedesktop.org/groups/spice/-/issues2023-04-02T09:11:14Zhttps://gitlab.freedesktop.org/spice/spice-gtk/-/issues/167Audio hasn't worked right for nearly a year+ (pipewire related?)2023-04-02T09:11:14ZCole MickensAudio hasn't worked right for nearly a year+ (pipewire related?)I don't know what's going on but audio hasn't worked right for me for nearly a year or longer.
```
❯ virt-viewer --connect "qemu+ssh://cole@192.168.1.10/system" 'linux2020'
(virt-viewer:300596): GSpice-WARNING **: 12:57:19.200: Warning...I don't know what's going on but audio hasn't worked right for me for nearly a year or longer.
```
❯ virt-viewer --connect "qemu+ssh://cole@192.168.1.10/system" 'linux2020'
(virt-viewer:300596): GSpice-WARNING **: 12:57:19.200: Warning no automount-inhibiting implementation available
(virt-viewer:300596): GSpice-WARNING **: 12:57:26.111: (../src/spice-session.c:2333):spice_session_channel_new: runtime check failed: (s->playback_channel == NULL)
(virt-viewer:300596): GSpice-CRITICAL **: 12:57:26.111: connect_channel: assertion 'p->pchannel == NULL' failed
```
This happens every single time I try to use virt-viewer, or virt-manager, with any guest. If I quickly close the client and reopen it, IT WORKS FINE. But the second audio playback stops, the channel seems to close and then it just ... **doesn't work any more until you restart the client again.**
Combining this with the infuriating behavior WRT to hidpi clients makes using virt-{viewer,manager} an extremely frustrating exercise.
There's no other journal messages for the system or my user that look relevant.https://gitlab.freedesktop.org/spice/spice-gtk/-/issues/165Potential leak for gst_bus_add_watch2023-01-23T10:12:14ZduanwujiePotential leak for gst_bus_add_watchIn the channel-display-gst.c
```C
bus = gst_pipeline_get_bus(GST_PIPELINE(decoder->pipeline));
gst_bus_add_watch(bus, handle_pipeline_message, decoder);
gst_object_unref(bus);
```
the gst_bus_add_watch's bus id not be free,which will ...In the channel-display-gst.c
```C
bus = gst_pipeline_get_bus(GST_PIPELINE(decoder->pipeline));
gst_bus_add_watch(bus, handle_pipeline_message, decoder);
gst_object_unref(bus);
```
the gst_bus_add_watch's bus id not be free,which will be cause gst_poll_read_controll assert error.https://gitlab.freedesktop.org/spice/spice-gtk/-/issues/164Cannot detach the keyboard when I switch to other virtual desktop.2023-01-23T10:15:00Z赵怡然Cannot detach the keyboard when I switch to other virtual desktop.Bug Step:
1.the virt-manager(spice) uses the mouse/keyboard alone in FULLSCREEN (catch all of the mouse/keyboard event)
2.leave the virtual machine by shortcut key
3.use KDE's hot corners to switch others virtual desktop
4.keyboard d...Bug Step:
1.the virt-manager(spice) uses the mouse/keyboard alone in FULLSCREEN (catch all of the mouse/keyboard event)
2.leave the virtual machine by shortcut key
3.use KDE's hot corners to switch others virtual desktop
4.keyboard doesn't work,what I have typed will be redirected to the virtual machine but I have exited it, and virtual machine window is in the other virtual desktop.
I reproduced the same problem with `virt-viewer win10 --attach`, I guess it is the "Spice GL/Virtio 3D support graphical issues" because I passthough my NVIDIA and vGPU , Enable OpenGL with spice
but when I move mouse to show the top tool bar, and press Ctrl+F8 to switch virtual desktop, the bug is gone, the bug is only emerged when I switch virtual desktop by hot corners
Original issue: https://github.com/virt-manager/virt-manager/issues/428
UPDATE: When I use QXL (without OPENGL and passthough), problem is disappeared.https://gitlab.freedesktop.org/spice/spice-gtk/-/issues/113dmabuf (virtio gpu, mdev) based spice display is divided by the host display ...2020-02-25T15:46:31ZChristoph Schmidpeterdmabuf (virtio gpu, mdev) based spice display is divided by the host display scaling ratio on Gnome 3 with WaylandWhen running a VM with spice-gtk, iGVT-g, and Gnome 3 on **Wayland**, the scaling for the displayed area is too small in relation to the spice window. There has been an analogous issue on **X11** with identical behaviour (see #99), which...When running a VM with spice-gtk, iGVT-g, and Gnome 3 on **Wayland**, the scaling for the displayed area is too small in relation to the spice window. There has been an analogous issue on **X11** with identical behaviour (see #99), which has already been fixed.
![SpiceGtkWithIgvtOnWayland](/uploads/cb52a0f84683451a099ce46873aff827/SpiceGtkWithIgvtOnWayland.jpeg)https://gitlab.freedesktop.org/spice/spice-gtk/-/issues/53remote-viewer hotplug mouse and keyboard error2018-06-07T21:39:38ZBugzilla Migration Userremote-viewer hotplug mouse and keyboard error## Submitted by hudeng
Assigned to **Spice Bug List**
**[Link to original bug (#103986)](https://bugs.freedesktop.org/show_bug.cgi?id=103986)**
## Description
Remote-viewer connect a kvm guest with fullscreen mode,When I hotplug m...## Submitted by hudeng
Assigned to **Spice Bug List**
**[Link to original bug (#103986)](https://bugs.freedesktop.org/show_bug.cgi?id=103986)**
## Description
Remote-viewer connect a kvm guest with fullscreen mode,When I hotplug my mouse and keyborad,my mouse and keyboard can't work and the only operation I can do is reboot my computer.And if I removed usbdk, this problem disappeared, so I guess mybey it's a problem about usbredirect.
virt-viewer version:5.0https://gitlab.freedesktop.org/spice/spice-gtk/-/issues/14Keys are stuck and not released in virt-viewer under excellent network condit...2023-07-11T13:07:13ZBugzilla Migration UserKeys are stuck and not released in virt-viewer under excellent network conditions## Submitted by Victor Toso
Assigned to **Spice Bug List**
**[Link to original bug (#94205)](https://bugs.freedesktop.org/show_bug.cgi?id=94205)**
## Description
++ This bug was originally reported in https://bugzilla.redhat.com/s...## Submitted by Victor Toso
Assigned to **Spice Bug List**
**[Link to original bug (#94205)](https://bugs.freedesktop.org/show_bug.cgi?id=94205)**
## Description
++ This bug was originally reported in https://bugzilla.redhat.com/show_bug.cgi?id=1286808 ++
Description of problem:
Intermittently keys are getting "stuck", using remote-viewer v2.00 and spice-gtk 0.30. I think the issue is similar to the following bug reports:
https://bugzilla.redhat.com/show_bug.cgi?id=1086650
https://bugzilla.redhat.com/show_bug.cgi?id=812347
The main difference being that it happens on a low latency/low jitter network, and the keys getting stuck are primarily modifier keys (CTRL the most, sometimes ALT & SHIFT). The most common case is using CTRL+C/CTRL+V to copy/paste, and the CTRL gets stuck or the "C" gets stuck.
Latency/Jitter example (local gigabit network):
PING 10.7.5.11 (10.7.5.11) 56(84) bytes of data.
64 bytes from 10.7.5.11: icmp_seq=1 ttl=64 time=0.222 ms
64 bytes from 10.7.5.11: icmp_seq=2 ttl=64 time=0.191 ms
64 bytes from 10.7.5.11: icmp_seq=3 ttl=64 time=0.205 ms
64 bytes from 10.7.5.11: icmp_seq=4 ttl=64 time=0.198 ms
64 bytes from 10.7.5.11: icmp_seq=5 ttl=64 time=0.200 ms
64 bytes from 10.7.5.11: icmp_seq=6 ttl=64 time=0.161 ms
64 bytes from 10.7.5.11: icmp_seq=7 ttl=64 time=0.121 ms
64 bytes from 10.7.5.11: icmp_seq=8 ttl=64 time=0.183 ms
64 bytes from 10.7.5.11: icmp_seq=9 ttl=64 time=0.130 ms
64 bytes from 10.7.5.11: icmp_seq=10 ttl=64 time=0.192 ms
--- 10.7.5.11 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8997ms
rtt min/avg/max/mdev = 0.121/0.180/0.222/0.032 ms
Version-Release number of selected component (if applicable):
remote-viewer v2.00
spice-gtk 0.30
How reproducible:
Unfortunately we can't reproduce it at will, but it seems to happen about 1-3x per day, even with "xset r off" on the client.
Previously when using spicec or remote-viewer v1.00 and spice-gtk 0.28 it seemed to happen around 4-6x per day and with more than just the modifier keys. However since upgrading to remote-viewer v2.00 and spice-gtk 0.30 it has reduced the occurrences significantly. Usually tapping the key that got stuck a few more times seems to "unstick" it.https://gitlab.freedesktop.org/spice/spice-gtk/-/issues/182Has the MacOS remote viewer client been abandoned?2024-03-23T17:34:19Zpresi 300Has the MacOS remote viewer client been abandoned?I'm not sure if this is the correct place to add an issue about this, if it isn't, please do tell me.
The MacOS remote viewer spice client is in a horrible state. It looks and feels straight out of 2013, as that's when the copyright dat...I'm not sure if this is the correct place to add an issue about this, if it isn't, please do tell me.
The MacOS remote viewer spice client is in a horrible state. It looks and feels straight out of 2013, as that's when the copyright dates say it was last updated, however, this isn't the reason why I'm saying that it's in a horrible state. It's not the fact that no one has bothered to rebuild it for apple silicon, nor to update the build instructions in 10 years either.
The big issue with it is that it leaks memory all over the place, causing a system crash after a few hours of continuous use.
-So why not just restart it?
Because closing the application is also broken. It closes, the icon disappears from the dock, yet it's still running in the background with the only way to actually close it being to go to the system monitor and force quit it from there...
My question is, since obviously nobody hasn't given any attention to this application in 10 years, is it considered abandoned? And if yes, why isn't there any indication anywhere that it is abandoned?https://gitlab.freedesktop.org/spice/win32/spice-nsis/-/issues/19Adapt Spice-Guest-Tools installer and documentation for Windows 112024-03-18T14:42:11ZFrancewhoaAdapt Spice-Guest-Tools installer and documentation for Windows 11## Challenge
The challenge is that with the latest Windows 11, if installing only [spice-guest-tools-latest](https://www.spice-space.org/download/windows/spice-guest-tools/spice-guest-tools-latest.exe), the clipboard sharing fails
## S...## Challenge
The challenge is that with the latest Windows 11, if installing only [spice-guest-tools-latest](https://www.spice-space.org/download/windows/spice-guest-tools/spice-guest-tools-latest.exe), the clipboard sharing fails
## Suggested Resolution 1
Adapt the spice-guest-tools installer so that **both** [Spice-Guest-Tools](https://www.spice-space.org/download/windows/spice-guest-tools/spice-guest-tools-latest.exe) and [Virtio-Win-Guest-Tools](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win-guest-tools.exe) are automatically installed.
In any order. We tested both orders. Both were successful.
## Suggested Resolution 2
Update this documentation page at https://www.spice-space.org/download.html to advise users to:
1. Install [Spice-Guest-Tools](https://www.spice-space.org/download/windows/spice-guest-tools/spice-guest-tools-latest.exe)
2. Install [Virtio-Win-Guest-Tools](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win-guest-tools.exe)
3. Reboot Windows 11
## Using
1. Latest [Spice-Guest-Tools](https://www.spice-space.org/download/windows/spice-guest-tools/spice-guest-tools-latest.exe)
2. Latest [Virtio-Win-Guest-Tools](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win-guest-tools.exe)
3. Guess Windows 11 version 23H2. 64 bits.
4. Host Debian 12 Bookworm. GNOME 43.9. Wayland. 64 bits.
No need to install anything on the Host. Except Virtual Manager (Virt-Manager). Also on the Host, no need to change any configuration with Virt-Manager. The default ones worked. In our case, Debian 12 Bookworm with GNOME Wayland.
## Contribution
Any volunteer for this? Both me and the Ubertus.Org team would be happy, as volunteer, to contribute testing and documentation, if needed.
## Related ticket
Details about this challenge at https://gitlab.freedesktop.org/spice/win32/spice-nsis/-/issues/16 Attribution to @Be for the suggested resolution.
## Virtio documentation
* https://github.com/virtio-win/virtio-win-pkg-scripts/blob/master/README.md
* https://github.com/virtio-win/virtio-win-guest-tools-installer/tree/163b5bbbbe0274ca9a0b18a1c49326d1e48caec3
* https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/virtual_machine_management_guide/installing_guest_agents_and_drivers_windows#Installing_the_Guest_Agents_and_Drivers_on_Windowshttps://gitlab.freedesktop.org/spice/spice-gtk/-/issues/180How to use a Port Channel on Windows guest?2024-02-16T19:54:41ZXws ZqHow to use a Port Channel on Windows guest?I'm trying to communicate between linux(host) and windows(guest) by using a Port Channel.
Based on the example provided in spicy I know how to implement the host side but not sure what to do on windows.
Is there any example code on how...I'm trying to communicate between linux(host) and windows(guest) by using a Port Channel.
Based on the example provided in spicy I know how to implement the host side but not sure what to do on windows.
Is there any example code on how to connect to my Port Channel from windows?https://gitlab.freedesktop.org/spice/spice/-/issues/860.15.2: test suite fails in one unit2024-02-02T11:47:45ZTomasz Kłoczko0.15.2: test suite fails in one unitLooks like something is wrong and test suite fails
```
+ cd spice-0.15.2
+ /usr/bin/meson test -C x86_64-redhat-linux-gnu --num-processes 48 --print-errorlogs
ninja: Entering directory `/home/tkloczko/rpmbuild/BUILD/spice-0.15.2/x86_64-r...Looks like something is wrong and test suite fails
```
+ cd spice-0.15.2
+ /usr/bin/meson test -C x86_64-redhat-linux-gnu --num-processes 48 --print-errorlogs
ninja: Entering directory `/home/tkloczko/rpmbuild/BUILD/spice-0.15.2/x86_64-redhat-linux-gnu'
ninja: no work to do.
1/26 spice-common / test_logging OK 0.17s
2/26 spice-common / test_ssl_verify OK 0.16s
3/26 spice-common / test_utils OK 0.16s
4/26 spice-common / test_marshallers OK 0.15s
5/26 spice / test-codecs-parsing OK 0.14s
6/26 spice / test-dispatcher OK 0.14s
7/26 spice / test-options OK 0.13s
8/26 spice / test-stat OK 0.13s
9/26 spice / test-agent-msg-filter OK 0.12s
10/26 spice / test-loop OK 0.12s
11/26 spice / test-leaks OK 0.11s
12/26 spice / test-vdagent OK 0.11s
13/26 spice / test-fail-on-null-core-interface OK 0.10s
14/26 spice / test-empty-success OK 0.10s
15/26 spice / test-set-ticket OK 0.08s
16/26 spice / test-stream OK 0.06s
17/26 spice / test-stat-file OK 0.05s
18/26 spice / test-smartcard OK 0.06s
19/26 spice / test-stream-device OK 0.10s
20/26 spice / test-record OK 0.11s
21/26 spice / test-listen FAIL 0.12s killed by signal 6 SIGABRT
>>> ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=157 /home/tkloczko/rpmbuild/BUILD/spice-0.15.2/x86_64-redhat-linux-gnu/server/tests/test-listen
――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――
stdout:
TAP version 13
# random seed: R02Sbb00adce09ab9a07614fd96f169d9481
1..5
# Start of server tests
# Start of listen tests
# Spice-DEBUG: ../server/reds.cpp:3417:do_spice_init: starting 0.15.2
# Spice-DEBUG: ../server/char-device.cpp:594:reset_dev_instance: sin (nil), char device 0x55b7ca8e8a00
# Spice-DEBUG: ../server/reds.cpp:2576:reds_init_socket: bound to 0.0.0.0:5728
# Spice-DEBUG: main:0 (0x55b7ca8ed170): thread_id 0x7fe64f289e40
# Spice-DEBUG: inputs:0 (0x55b7ca8ed2c0): thread_id 0x7fe64f289e40
# GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation dummy (GDummyProxyResolver) for ?gio-proxy-resolver?
# Spice-DEBUG: ../server/reds.cpp:550:reds_disconnect: trace
# Spice-DEBUG: ../server/char-device.cpp:715:reset: char device 0x55b7ca8e8a00
ok 1 /server/listen/connect_plain
# Spice-DEBUG: ../server/reds.cpp:3417:do_spice_init: starting 0.15.2
# Spice-DEBUG: ../server/char-device.cpp:594:reset_dev_instance: sin (nil), char device 0x55b7ca8f09e0
# Spice-DEBUG: ../server/reds.cpp:2576:reds_init_socket: bound to 0.0.0.0:5728
# Spice-DEBUG: ../server/reds.cpp:2836:reds_init_ssl: Loaded certificates from /home/tkloczko/rpmbuild/BUILD/spice-0.15.2/server/tests/pki/server-cert.pem
# Spice-DEBUG: ../server/reds.cpp:2849:reds_init_ssl: Using private key from /home/tkloczko/rpmbuild/BUILD/spice-0.15.2/server/tests/pki/server-key.pem
# Spice-DEBUG: ../server/reds.cpp:2858:reds_init_ssl: Loaded CA certificates from /home/tkloczko/rpmbuild/BUILD/spice-0.15.2/server/tests/pki/ca-cert.pem
# Spice-DEBUG: main:0 (0x55b7ca94e1f0): thread_id 0x7fe64f289e40
# Spice-DEBUG: inputs:0 (0x55b7ca94e2a0): thread_id 0x7fe64f289e40
# GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation dummy (GDummyTlsBackend) for ?gio-tls-backend?
not ok /server/listen/connect_tls - Spice:ERROR:../server/tests/test-listen.c:121:fake_client_connect_tls: assertion failed (*error == NULL): TLS support is not available (g-tls-error-quark, 0)
Bail out!
stderr:
**
Spice:ERROR:../server/tests/test-listen.c:121:fake_client_connect_tls: assertion failed (*error == NULL): TLS support is not available (g-tls-error-quark, 0)
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
22/26 spice-common / test_quic OK 0.21s
23/26 spice / test-channel OK 0.21s
24/26 spice / test-qxl-parsing OK 0.36s
25/26 spice / test-sasl OK 0.42s
26/26 spice-common / test_region OK 1.08s
Summary of Failures:
21/26 spice / test-listen FAIL 0.12s killed by signal 6 SIGABRT
Ok: 25
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 0
Timeout: 0
```https://gitlab.freedesktop.org/spice/win32/qxl-wddm-dod/-/issues/23Help needed to build this project2024-01-05T08:33:26ZVictorien PlanckeHelp needed to build this projectHello,
can you help me to build this project?
I tried with Visual studio 2015
Win Sdk, and Wdk are installed (latest version)
In the project properties i set win 10 as target
In Platform Toolset I can't select WindowsKernelModeDriv...Hello,
can you help me to build this project?
I tried with Visual studio 2015
Win Sdk, and Wdk are installed (latest version)
In the project properties i set win 10 as target
In Platform Toolset I can't select WindowsKernelModeDriver10 :
![image](/uploads/2c4e053969294bf8bd6f8524b068eded/image.png)
And i got many errors like :
`The build tools for WindowsKernelModeDriver10.0 (Platform Toolset = 'WindowsKernelModeDriver10.0') cannot be found. To build using the WindowsKernelModeDriver10.0 build tools, please install WindowsKernelModeDriver10.0 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution". `
![image](/uploads/aab894c96aa022a6573060179cf37111/image.png)
Thanks for your helphttps://gitlab.freedesktop.org/spice/spice/-/issues/85Fix GL_DRAW_COOKIE_INVALID error with QEMU/virtio-gpu on Apple Silicon2023-12-23T13:18:16ZJorrit JongmaFix GL_DRAW_COOKIE_INVALID error with QEMU/virtio-gpu on Apple SiliconOn Asahi Linux (Linux for Apple Silicon, both the Arch and Fedora based versions) trying to use Spice+OpenGL with virtio-gpu with QEMU crashes with a GL_DRAW_COOKIE_INVALID error.
It seems the UTM (emulator for iOS) folks ran into this ...On Asahi Linux (Linux for Apple Silicon, both the Arch and Fedora based versions) trying to use Spice+OpenGL with virtio-gpu with QEMU crashes with a GL_DRAW_COOKIE_INVALID error.
It seems the UTM (emulator for iOS) folks ran into this same issue last year as well, and patched it by simply removing the check in `spice_qxl_gl_scanout` (see attached patch below). I have tried this patch on both Arch and Fedora and it solved the problem, my VMs are now properly GL accelerated.
In this RedHat bug - https://bugzilla.redhat.com/show_bug.cgi?id=1674324 - they discuss the same crash, though their solution is different and it seems they reason it happens because of 2D calls being translated to 3D.
```
From 02cae4922d55c488cce790835ee2fccd61e34dbd Mon Sep 17 00:00:00 2001
From: osy <osy@turing.llc>
Date: Sun, 18 Dec 2022 23:20:48 -0800
Subject: [PATCH 11/11] red-qxl: remove cookie assertion on scanout
The original check ensures we do not have an outstanding GL_DRAW. However,
in QEMU, there is no guarantee that a scanout cannot happen while the async
GL_DRAW has not returned a result yet. This introduces a race where if a
scanout is called while there is an outstanding GL_DRAW, QEMU will crash.
The removal of this check enforces a new contract with the SPICE client.
Every GL_DRAW must be matched with a GL_DONE (i.e. with a call to
`spice_display_channel_gl_draw_done()` in the client) even if the render
context is no longer valid. Otherwise, the assertion crash will happen in
the next call to `spice_qxl_gl_draw_async()`.
---
server/red-qxl.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/server/red-qxl.c b/server/red-qxl.c
index dbfcd440..8cdf86f5 100644
--- a/server/red-qxl.c
+++ b/server/red-qxl.c
@@ -703,7 +703,6 @@ void spice_qxl_gl_scanout(QXLInstance *qxl,
spice_return_if_fail(qxl != NULL);
QXLState *qxl_state = qxl->st;
- spice_return_if_fail(qxl_state->gl_draw_cookie == GL_DRAW_COOKIE_INVALID);
pthread_mutex_lock(&qxl_state->scanout_mutex);
```https://gitlab.freedesktop.org/spice/usbredir/-/issues/34SIGILL triggerred by usbredirparser_serialize with nullptr in usbredirparser....2023-12-18T06:00:08Z王 平SIGILL triggerred by usbredirparser_serialize with nullptr in usbredirparser.c:1766I have found SIGILL crashes with usbredir-0.13.0 when running some fuzzing tests.
[usbredir-0.13.0-SIGILL.tar.gz](/uploads/374e4980d1cb1657b38ed1c464493a5c/usbredir-0.13.0-SIGILL.tar.gz)
Repordocing Steps:
1. Trigger the SIGILL crash...I have found SIGILL crashes with usbredir-0.13.0 when running some fuzzing tests.
[usbredir-0.13.0-SIGILL.tar.gz](/uploads/374e4980d1cb1657b38ed1c464493a5c/usbredir-0.13.0-SIGILL.tar.gz)
Repordocing Steps:
1. Trigger the SIGILL crashes with PoC attached.
`./usbredirparserfuzz < out2/default/crashes/id\:000033\,sig\:04\,src\:000083\,time\:5394\,execs\:37324\,op\:havoc\,rep\:3`
[AFL++ 0cc14d0bc3c5] /data/openeuler/usbredir/fuzzing # date
Mon Dec 18 02:50:16 AM UTC 2023
[AFL++ 0cc14d0bc3c5] /data/openeuler/usbredir/fuzzing # ./usbredirparserfuzz < out2/default/crashes/id\:000033\,sig\:04\,src\:000083\,time\:5394\,execs\:37324\,op\:havoc\,rep\:3
Illegal instruction
2. Debug Information:
`gdb ./usbredirparserfuzz`
![usbredir-0.13.0](/uploads/a6a5905dab39106554abec487a3f29c9/usbredir-0.13.0.png)
```
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./usbredirparserfuzz...
(gdb) run < out2/default/crashes/id\:000033\,sig\:04\,src\:000083\,time\:5394\,execs\:37324\,op\:havoc\,rep\:3
Starting program: /data/openeuler/usbredir/fuzzing/usbredirparserfuzz < out2/default/crashes/id\:000033\,sig\:04\,src\:000083\,time\:5394\,execs\:37324\,op\:havoc\,rep\:3
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Program received signal SIGILL, Illegal instruction.
0x000055555568cd92 in serialize_data (parser=<optimized out>, state=<optimized out>, pos=0x7fffffffdc00, remain=0x7fffffffdc20, data=0x0, len=<optimized out>, desc=0x55555558cd00 <str.20> "packet-data") at ../usbredirparser/usbredirparser.c:1661
1661 memcpy(*pos, data, len);
(gdb) p data
$1 = (uint8_t *) 0x0
(gdb) p len
$2 = <optimized out>
(gdb) bt
#0 0x000055555568cd92 in serialize_data (parser=<optimized out>, state=<optimized out>, pos=0x7fffffffdc00, remain=0x7fffffffdc20,
data=0x0, len=<optimized out>, desc=0x55555558cd00 <str.20> "packet-data") at ../usbredirparser/usbredirparser.c:1661
#1 0x000055555568b237 in usbredirparser_serialize (parser_pub=<optimized out>, state_dest=<optimized out>, state_len=<optimized out>)
at ../usbredirparser/usbredirparser.c:1766
#2 0x000055555567735b in (anonymous namespace)::try_serialize (parser=0x631000014824) at usbredirparserfuzz.cc:330
#3 LLVMFuzzerTestOneInput (data=<optimized out>, size=<optimized out>) at usbredirparserfuzz.cc:424
#4 0x000055555567e8d3 in main (argc=<optimized out>, argv=<optimized out>) at usbredirparserfuzz.cc:458
(gdb)
```
A more details debug info:
```
(gdb)bu usbredirparser.c:1661
Breakpoint 1 at 0x55555568c9ac: file ../usbredirparser/usbredirparser.c, line 1661.
(gdb) b usbredirparser.c:1766
Breakpoint 2 at 0x55555568b21a: file ../usbredirparser/usbredirparser.c, line 1766.
(gdb) usbredirparserfuzz.cc:330
Undefined command: "usbredirparserfuzz.cc". Try "help".
(gdb) b usbredirparserfuzz.cc:330
Breakpoint 3 at 0x55555567705f: usbredirparserfuzz.cc:330. (2 locations)
(gdb) r
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /data/openeuler/usbredir/fuzzing/usbredirparserfuzz < out2/default/crashes/id\:000033\,sig\:04\,src\:000083\,time\:5394\,execs\:37324\,op\:havoc\,rep\:3
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Breakpoint 3, (anonymous namespace)::try_serialize (parser=0x617000000080) at usbredirparserfuzz.cc:330
330 ret = usbredirparser_serialize(parser, &state, &len);
(gdb) p state
$1 = (uint8_t *) 0x0
(gdb) p len
$2 = 0
(gdb) c
Continuing.
Breakpoint 2, usbredirparser_serialize (parser_pub=<optimized out>, state_dest=<optimized out>, state_len=<optimized out>) at ../usbredirparser/usbredirparser.c:1766
1766 if (serialize_data(parser, &state, &pos, &remain,
(gdb) p state
$3 = (uint8_t *) 0x631000014800 "1PRU"
(gdb) p len
$4 = <optimized out>
(gdb) c
Continuing.
Program received signal SIGILL, Illegal instruction.
0x000055555568cd92 in serialize_data (parser=<optimized out>, state=<optimized out>, pos=0x7fffffffdc00, remain=0x7fffffffdc20, data=0x0, len=<optimized out>, desc=0x55555558cd00 <str.20> "packet-data") at ../usbredirparser/usbredirparser.c:1661
1661 memcpy(*pos, data, len);
(gdb) p data
$5 = (uint8_t *) 0x0
(gdb) p len
$6 = <optimized out>
(gdb) p pos
$7 = (uint8_t **) 0x7fffffffdc00
```
The fuzzing code I use is also attached above!https://gitlab.freedesktop.org/spice/win32/vd_agent/-/issues/26Clipboard sharing not working at Windows login2023-12-09T22:00:39ZMark BrownClipboard sharing not working at Windows loginHello, I'm using the spice vdagent on some VMs managed by Proxmox. The problem is that I find that after I connect, the clipboard sharing doens't work at the windows login screen, it only starts working afterwards. This mostly defeats th...Hello, I'm using the spice vdagent on some VMs managed by Proxmox. The problem is that I find that after I connect, the clipboard sharing doens't work at the windows login screen, it only starts working afterwards. This mostly defeats the purpose of clipboard sharing for me, as I still have to manually type the windows VM's password out manually. I assume this occurs because the vdagent doesn't start properly until after login, although the vd agent entry under windows services lists it as starting automatically and with the local system account, so I'm not sure why this is the case. Is this a known issue or is there some workaround?https://gitlab.freedesktop.org/spice/win32/vd_agent/-/issues/25basic clipboard ok BUT handle_max_clipboard & drag & drop unavailable2023-12-10T12:45:10ZOlivierorDanielbasic clipboard ok BUT handle_max_clipboard & drag & drop unavailableHost : Fedora 39, gnome wayland, laptop, x64
Guest VM qemu :
Windows 10 Version 10.0.19045 Build 19045
VdAgent 0.10.0
(spice-guest-tools last version from 2018-01 is absent)
virtio-win-guest-tools.exe 0.1.240, 20231201
Hello,
Thanks ...Host : Fedora 39, gnome wayland, laptop, x64
Guest VM qemu :
Windows 10 Version 10.0.19045 Build 19045
VdAgent 0.10.0
(spice-guest-tools last version from 2018-01 is absent)
virtio-win-guest-tools.exe 0.1.240, 20231201
Hello,
Thanks a lot for your driver, it's so useful!
- I can copy/paste some short text, bidirectionnal betwen vm & host
- I cannot copy/past file, cannot drag & drop. Past is grey.
- Same behavior on virt-manager or remmina with spice plugins on 127.0.0.1:5900
- error : handle_max_clipboard::Set max clipboard size: 104857600
Reading the code, I understand that the copy method is distinct between the basic one and the one for larger data.
What reassures me is that the simple copy works, this tells me that it seems an internal problem between Weston/Wayland & the large copy & the dragn&drop?
<details><summary>some logs:</summary>
3616::INFO::2023-12-08 23:33:42,133::handle_max_clipboard::Set max clipboard size: 104857600
3616::INFO::2023-12-08 23:33:42,133::handle_mon_config::0. 1665*673*32 (0,0) 1
3616::INFO::2023-12-08 23:33:42,133::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:33:42,133::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1665 x673)
3616::INFO::2023-12-08 23:33:42,945::handle_mon_config::0. 1665*673*32 (0,0) 1
3616::INFO::2023-12-08 23:33:42,945::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:33:42,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1665 x673)
3616::INFO::2023-12-08 23:33:43,445::handle_control_event::Control command 3
3616::INFO::2023-12-08 23:33:43,445::handle_control_event::session logon
3616::INFO::2023-12-08 23:33:47,039::handle_control_event::Control command 2
3616::INFO::2023-12-08 23:33:47,133::input_desktop_message_loop::Desktop: Default
3616::INFO::2023-12-08 23:33:47,133::input_desktop_message_loop::First display setting
3616::INFO::2023-12-08 23:33:47,133::load::loading display setting
3616::INFO::2023-12-08 23:33:47,133::reload_from_registry::explorer pid 2416
3616::INFO::2023-12-08 23:33:47,133::reload_wallpaper::
3616::INFO::2023-12-08 23:33:47,133::reload_wallpaper::reload wallpaper: success
3616::INFO::2023-12-08 23:33:47,133::reload_font_smoothing::
3616::INFO::2023-12-08 23:33:47,133::reload_font_smoothing::font smoothing is disabled in registry. do nothing
3616::INFO::2023-12-08 23:33:47,133::reload_animation::
3616::INFO::2023-12-08 23:33:47,133::reload_win_animation::
3616::INFO::2023-12-08 23:33:47,133::reload_win_animation::window animation is disabled in registry. do nothing
3616::INFO::2023-12-08 23:33:47,133::reload_ui_effects::
3616::INFO::2023-12-08 23:33:47,133::reload_ui_effects::UserPreferencesMask = 80031290 10
3616::INFO::2023-12-08 23:33:50,945::handle_mon_config::0. 2256*1366*32 (0,0) 1
3616::INFO::2023-12-08 23:33:50,945::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:33:50,945::custom_display_escape::updating \\.\DISPLAY1 resolution
3616::INFO::2023-12-08 23:33:50,945::update_mode_size::\\.\DISPLAY1 updated path mode to (0, 0 - (2256 x 1366)
3616::INFO::2023-12-08 23:33:50,945::set_displays::Set display mode 2256x1366
3616::INFO::2023-12-08 23:33:50,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (2256 x1366)
3616::INFO::2023-12-08 23:33:50,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (2256 x1366)
3616::INFO::2023-12-08 23:33:50,945::debug_print_config::\\.\DISPLAY1 [Before SetDisplayConfig] (0,0) (2256x1366).
3616::INFO::2023-12-08 23:33:50,945::wnd_proc::Display change
3616::INFO::2023-12-08 23:33:50,945::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:33:50,961::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (2256 x1366)
3616::INFO::2023-12-08 23:33:51,945::handle_mon_config::0. 2256*1366*32 (0,0) 1
3616::INFO::2023-12-08 23:33:51,945::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:33:51,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (2256 x1366)
3616::INFO::2023-12-08 23:33:57,305::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:33:57,945::handle_mon_config::0. 1665*673*32 (0,0) 1
3616::INFO::2023-12-08 23:33:57,945::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:33:57,945::custom_display_escape::updating \\.\DISPLAY1 resolution
3616::INFO::2023-12-08 23:33:57,945::update_mode_size::\\.\DISPLAY1 updated path mode to (0, 0 - (1665 x 673)
3616::INFO::2023-12-08 23:33:57,945::set_displays::Set display mode 1665x673
3616::INFO::2023-12-08 23:33:57,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1665 x673)
3616::INFO::2023-12-08 23:33:57,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1665 x673)3616::INFO::2023-12-08 23:33:42,133::handle_max_clipboard::Set max clipboard size: 104857600
3616::INFO::2023-12-08 23:33:42,133::handle_mon_config::0. 1665*673*32 (0,0) 1
3616::INFO::2023-12-08 23:33:42,133::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:33:42,133::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1665 x673)
3616::INFO::2023-12-08 23:33:42,945::handle_mon_config::0. 1665*673*32 (0,0) 1
3616::INFO::2023-12-08 23:33:42,945::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:33:42,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1665 x673)
3616::INFO::2023-12-08 23:33:43,445::handle_control_event::Control command 3
3616::INFO::2023-12-08 23:33:43,445::handle_control_event::session logon
3616::INFO::2023-12-08 23:33:47,039::handle_control_event::Control command 2
3616::INFO::2023-12-08 23:33:47,133::input_desktop_message_loop::Desktop: Default
3616::INFO::2023-12-08 23:33:47,133::input_desktop_message_loop::First display setting
3616::INFO::2023-12-08 23:33:47,133::load::loading display setting
3616::INFO::2023-12-08 23:33:47,133::reload_from_registry::explorer pid 2416
3616::INFO::2023-12-08 23:33:47,133::reload_wallpaper::
3616::INFO::2023-12-08 23:33:47,133::reload_wallpaper::reload wallpaper: success
3616::INFO::2023-12-08 23:33:47,133::reload_font_smoothing::
3616::INFO::2023-12-08 23:33:47,133::reload_font_smoothing::font smoothing is disabled in registry. do nothing
3616::INFO::2023-12-08 23:33:47,133::reload_animation::
3616::INFO::2023-12-08 23:33:47,133::reload_win_animation::
3616::INFO::2023-12-08 23:33:47,133::reload_win_animation::window animation is disabled in registry. do nothing
3616::INFO::2023-12-08 23:33:47,133::reload_ui_effects::
3616::INFO::2023-12-08 23:33:47,133::reload_ui_effects::UserPreferencesMask = 80031290 10
3616::INFO::2023-12-08 23:33:50,945::handle_mon_config::0. 2256*1366*32 (0,0) 1
3616::INFO::2023-12-08 23:33:50,945::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:33:50,945::custom_display_escape::updating \\.\DISPLAY1 resolution
3616::INFO::2023-12-08 23:33:50,945::update_mode_size::\\.\DISPLAY1 updated path mode to (0, 0 - (2256 x 1366)
3616::INFO::2023-12-08 23:33:50,945::set_displays::Set display mode 2256x1366
3616::INFO::2023-12-08 23:33:50,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (2256 x1366)
3616::INFO::2023-12-08 23:33:50,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (2256 x1366)
3616::INFO::2023-12-08 23:33:50,945::debug_print_config::\\.\DISPLAY1 [Before SetDisplayConfig] (0,0) (2256x1366).
3616::INFO::2023-12-08 23:33:50,945::wnd_proc::Display change
3616::INFO::2023-12-08 23:33:50,945::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:33:50,961::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (2256 x1366)
3616::INFO::2023-12-08 23:33:51,945::handle_mon_config::0. 2256*1366*32 (0,0) 1
3616::INFO::2023-12-08 23:33:51,945::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:33:51,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (2256 x1366)
3616::INFO::2023-12-08 23:33:57,305::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:33:57,945::handle_mon_config::0. 1665*673*32 (0,0) 1
3616::INFO::2023-12-08 23:33:57,945::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:33:57,945::custom_display_escape::updating \\.\DISPLAY1 resolution
3616::INFO::2023-12-08 23:33:57,945::update_mode_size::\\.\DISPLAY1 updated path mode to (0, 0 - (1665 x 673)
3616::INFO::2023-12-08 23:33:57,945::set_displays::Set display mode 1665x673
3616::INFO::2023-12-08 23:33:57,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1665 x673)
3616::INFO::2023-12-08 23:33:57,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1665 x673)
3616::INFO::2023-12-08 23:33:57,945::debug_print_config::\\.\DISPLAY1 [Before SetDisplayConfig] (0,0) (1665x673).
3616::INFO::2023-12-08 23:33:57,961::wnd_proc::Display change
3616::INFO::2023-12-08 23:33:57,961::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:33:57,961::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1665 x673)
3616::INFO::2023-12-08 23:33:58,945::handle_mon_config::0. 1665*673*32 (0,0) 1
3616::INFO::2023-12-08 23:33:58,945::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:33:58,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1665 x673)
3616::INFO::2023-12-08 23:34:02,414::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:34:02,945::handle_mon_config::0. 1681*995*32 (0,0) 1
3616::INFO::2023-12-08 23:34:02,945::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:34:02,945::custom_display_escape::updating \\.\DISPLAY1 resolution
3616::INFO::2023-12-08 23:34:02,945::update_mode_size::\\.\DISPLAY1 updated path mode to (0, 0 - (1681 x 995)
3616::INFO::2023-12-08 23:34:02,945::set_displays::Set display mode 1681x995
3616::INFO::2023-12-08 23:34:02,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1681 x995)
3616::INFO::2023-12-08 23:34:02,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1681 x995)
3616::INFO::2023-12-08 23:34:02,945::debug_print_config::\\.\DISPLAY1 [Before SetDisplayConfig] (0,0) (1681x995).
3616::INFO::2023-12-08 23:34:02,945::wnd_proc::Display change
3616::INFO::2023-12-08 23:34:02,961::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:34:02,961::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1681 x995)
3616::INFO::2023-12-08 23:34:03,945::handle_mon_config::0. 1681*995*32 (0,0) 1
3616::INFO::2023-12-08 23:34:03,945::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:34:03,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1681 x995)
3616::INFO::2023-12-08 23:40:49,820::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:43:58,430::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:45:26,101::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:45:27,273::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:49:33,929::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:49:35,117::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:51:06,242::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:51:30,305::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:55:34,992::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:56:18,633::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:33:57,945::debug_print_config::\\.\DISPLAY1 [Before SetDisplayConfig] (0,0) (1665x673).
3616::INFO::2023-12-08 23:33:57,961::wnd_proc::Display change
3616::INFO::2023-12-08 23:33:57,961::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:33:57,961::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1665 x673)
3616::INFO::2023-12-08 23:33:58,945::handle_mon_config::0. 1665*673*32 (0,0) 1
3616::INFO::2023-12-08 23:33:58,945::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:33:58,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1665 x673)
3616::INFO::2023-12-08 23:34:02,414::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:34:02,945::handle_mon_config::0. 1681*995*32 (0,0) 1
3616::INFO::2023-12-08 23:34:02,945::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:34:02,945::custom_display_escape::updating \\.\DISPLAY1 resolution
3616::INFO::2023-12-08 23:34:02,945::update_mode_size::\\.\DISPLAY1 updated path mode to (0, 0 - (1681 x 995)
3616::INFO::2023-12-08 23:34:02,945::set_displays::Set display mode 1681x995
3616::INFO::2023-12-08 23:34:02,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1681 x995)
3616::INFO::2023-12-08 23:34:02,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1681 x995)
3616::INFO::2023-12-08 23:34:02,945::debug_print_config::\\.\DISPLAY1 [Before SetDisplayConfig] (0,0) (1681x995).
3616::INFO::2023-12-08 23:34:02,945::wnd_proc::Display change
3616::INFO::2023-12-08 23:34:02,961::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:34:02,961::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1681 x995)
3616::INFO::2023-12-08 23:34:03,945::handle_mon_config::0. 1681*995*32 (0,0) 1
3616::INFO::2023-12-08 23:34:03,945::consistent_displays::#qxls 1 #others 0
3616::INFO::2023-12-08 23:34:03,945::update_mode_position::\\.\DISPLAY1 updated path mode to (0, 0) - (1681 x995)
3616::INFO::2023-12-08 23:40:49,820::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:43:58,430::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:45:26,101::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:45:27,273::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:49:33,929::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:49:35,117::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:51:06,242::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:51:30,305::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:55:34,992::handle_clipboard_grab::grab type 1 format=13
3616::INFO::2023-12-08 23:56:18,633::handle_clipboard_grab::grab type 1 format=13
</details>
Thanks in avdance.https://gitlab.freedesktop.org/spice/spice/-/issues/84spice-server: error: visibility does not match previous declaration2024-01-31T05:54:23ZKupietoolsspice-server: error: visibility does not match previous declaration```
---> Building spice-server
Error: Failed to build spice-server: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_spice-server/s...```
---> Building spice-server
Error: Failed to build spice-server: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_spice-server/spice-server/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there
is a bug.
Error: Processing of port spice-server failed
```
The mentioned main.log is enormous and searching for errors is tough.
I did find a failed make command in the log and ran it manually, and got:
```
inputs-channel.cpp:467:1: error: visibility does not match previous declaration
SPICE_GNUC_VISIBLE int spice_server_kbd_leds(SpiceKbdInstance *sin, int leds)
^
./utils.h:28:44: note: expanded from macro 'SPICE_GNUC_VISIBLE'
#define SPICE_GNUC_VISIBLE __attribute__ ((visibility ("default")))
^
./push-visibility.h:19:13: note: previous attribute is here
#pragma GCC visibility push(hidden)
```
I'm unable to install Colima because of this. MacBook Pro running Mojave 10.14.6. Thanks.https://gitlab.freedesktop.org/spice/win32/vd_agent/-/issues/24Release a new Version (0.11.0)2023-12-08T23:12:59ZLu KeRelease a new Version (0.11.0)As the last release was over 3 years ago it is time for a new one. There have been several commits since the beginning of 2020 when the last release was.
The current version of spice guest tools still use the vd_agent version 0.8.0. I ...As the last release was over 3 years ago it is time for a new one. There have been several commits since the beginning of 2020 when the last release was.
The current version of spice guest tools still use the vd_agent version 0.8.0. I already asked the spice guest tools when they release an update, but first this sub-module of it should get updated.https://gitlab.freedesktop.org/spice/spice/-/issues/83handle_dev_destroy_surface_wait: condition `msg->surface_id == 0' failed (DoS...2023-11-22T07:38:49ZMarc-André Lureauhandle_dev_destroy_surface_wait: condition `msg->surface_id == 0' failed (DoS via assert failure)```
cat << EOF | ./qemu-system-x86_64 -display none -machine accel=qtest, -m 512M -M \
pc -nodefaults -vga qxl -qtest stdio
outl 0xcf8 0x8000101c
outl 0xcfc 0xc000
outl 0xcf8 0x80001004
outw 0xcfc 0x01
outl 0xc00b 0x01000000
EOF
```
qem...```
cat << EOF | ./qemu-system-x86_64 -display none -machine accel=qtest, -m 512M -M \
pc -nodefaults -vga qxl -qtest stdio
outl 0xcf8 0x8000101c
outl 0xcfc 0xc000
outl 0xcf8 0x80001004
outw 0xcfc 0x01
outl 0xc00b 0x01000000
EOF
```
qemu-system-x86_64: Spice: ../server/red-worker.cpp:367:handle_dev_destroy_surface_wait: condition `msg->surface_id == 0' failed
qxl_spice_destroy_surface_wait() should probably return an error on surface_id != 0.https://gitlab.freedesktop.org/spice/win32/qxl-wddm-dod/-/issues/22Google Chrome has a tearing effect when playing a video containing a bullet s...2023-08-22T03:23:56Zsoul-jhGoogle Chrome has a tearing effect when playing a video containing a bullet screen![Snipaste_2023-08-22_11-18-30](/uploads/1ee94e6b35ecbe6d8f2c9e5a3ccc4f30/Snipaste_2023-08-22_11-18-30.png)
I'm function QxlDod: : PresentDisplayOnly (_In_ CONST DXGKARG_PRESENT_DISPLAYONLY * pPresentDisplayOnly) will be pPresentDisplay...![Snipaste_2023-08-22_11-18-30](/uploads/1ee94e6b35ecbe6d8f2c9e5a3ccc4f30/Snipaste_2023-08-22_11-18-30.png)
I'm function QxlDod: : PresentDisplayOnly (_In_ CONST DXGKARG_PRESENT_DISPLAYONLY * pPresentDisplayOnly) will be pPresentDisplayOnly->pSource save the full-screen data contained into bmp, and find that some pictures have tearshttps://gitlab.freedesktop.org/spice/linux/vd_agent/-/issues/35spice-vdagentd does not work on KDE Plasma2023-11-01T23:05:51ZDUO Labsspice-vdagentd does not work on KDE PlasmaRelated to #27. See also https://bugs.kde.org/show_bug.cgi?id=472622.
On KDE Plasma on X11,`spice-vdagentd` is started automatically when you log in. However, if you try to copy you get `UID mismatch: UID=1001 PID=636 suid=4294967295`.
...Related to #27. See also https://bugs.kde.org/show_bug.cgi?id=472622.
On KDE Plasma on X11,`spice-vdagentd` is started automatically when you log in. However, if you try to copy you get `UID mismatch: UID=1001 PID=636 suid=4294967295`.
`spice-vdagent` (the user daemon) is dead. If you try to start it manually with `spice-vdagent -d -x`, you get
```plaintext
spice-vdagent[17777]: vdagent started
spice-vdagent[17777]: 0xaaab02cf2d30 connected to /run/spice-vdagentd/spice-vdagent-sock
spice-vdagent[17777]: vdagent_display_create: net_wm_name="KWin", has icons=0
spice-vdagent[17777]: display: failed to call GetCurrentState from mutter over DBUS
spice-vdagent[17777]: error message: Cannot invoke method; proxy is for the well-known name org.gnome.Mutter.DisplayConfig without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
spice-vdagent[17777]: No guest output map, using output index as display id
spice-vdagent[17777]: Sending guest screen resolutions to vdagentd:
spice-vdagent[17777]: display_id=0 - 1280x800+0+0
spice-vdagent[17777]: 0xaaab02cf2d30 sent guest xorg resolution, arg1: 1280, arg2: 800, size 20
spice-vdagent[17777]: 0xaaab02cf2d30 disconnected
```
Interestingly, if I install xdg-desktop-portal-gtk/vte3 and reboot, clipboard sync works as expected. However, if I reboot again after, it stops working again.
All other DEs I have tried work as expected