RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1676919 - Vdagent stucks after remote-viewer reconnection while file xfer to guest
Summary: Vdagent stucks after remote-viewer reconnection while file xfer to guest
Keywords:
Status: CLOSED DUPLICATE of bug 1548419
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-vdagent-win
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Frediano Ziglio
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-13 15:39 UTC by Radek Duda
Modified: 2020-05-21 14:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-21 14:57:29 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
spice-debug.log (2.80 KB, text/plain)
2019-02-13 15:39 UTC, Radek Duda 		no flags Details
View All

Description Radek Duda 2019-02-13 15:39:08 UTC 
Created attachment 1534441 [details]
spice-debug.log

Description of problem:
File transfer is stuck when try to xfer file to VM after previous xfer is interrupted by restart of remote-viewer

Version-Release number of selected component (if applicable):
performed using rhv4.3.0.4
host:

host:
qemu-kvm-rhev-2.12.0-21.el7.x86_64
spice-server-0.14.0-6.el7_6.1.x86_64

client:
spice-gtk3-0.35-7.el8.x86_64
virt-viewer-7.0-3.el8.x86_64

guest:
win10 Pro 1809
vdagent-win-4.1-5

How reproducible:
always

Steps to Reproduce:
1.start VM and connect to it with remote-viewer
2. drag'n'drop some large file from client to guest
3.restart remote-viewer
4. drag'n'drop some large file from client to guest

Actual results:
file transfer is suck with copy. Copy dialog window is open and cannot be closed. Progress bar stays at zero position.

Expected results:
File is copied to guest

Additional info:
Comment 1 Victor Toso 2019-02-27 09:12:47 UTC 
> 3.restart remote-viewer

You mean that you Quit and launch it again or you did something else?

> file transfer is suck with copy.

Could you attach the logs from the agent? Would be great if you could do a small copy that works and than the big one, from steps 2, 3 and 4 just to
show that it was working and that it breaks when you quit. Probably some bad state in the agent.

> Copy dialog window is open and cannot be closed. Progress bar stays at zero position.

Errg. That's a bug in the client. Could you please also open a bug there?
Comment 2 Radek Duda 2019-02-27 10:42:33 UTC 
Hi Victor,
yes in step 3 I quit remote-viewer and launch it again.

a) successfully copied to guest:

5260::INFO::2019-02-27 10:36:05,293::handle_start::7 Hound dog.mp4 (12155024)
5260::INFO::2019-02-27 10:36:05,996::handle_data::7 completed

b) unsuccessfully copied to guest -> interrupted (by remote-viewer restart)

1524::INFO::2019-02-27 10:25:59,562::handle_clipboard_release::Received clipboard release from client while clipboard is not owned by client
1524::INFO::2019-02-27 10:25:59,562::handle_clipboard_grab::grab type 1 format=13
1524::INFO::2019-02-27 10:26:00,312::handle_clipboard_grab::grab type 1 format=13
1524::INFO::2019-02-27 10:26:00,312::handle_control_event::Control command 4
1524::INFO::2019-02-27 10:26:03,062::handle_clipboard_grab::grab type 1 format=13
1524::INFO::2019-02-27 10:26:03,062::handle_control_event::Control command 4
1524::INFO::2019-02-27 10:26:05,515::handle_start::1 BGStyl_TvNoe_SDverze.mpg (774221828)
1524::INFO::2019-02-27 10:26:05,796::handle_clipboard_grab::grab type 1 format=13
1524::INFO::2019-02-27 10:26:05,796::handle_control_event::Control command 4
1524::INFO::2019-02-27 10:26:08,203::dispatch_message::Client disconnected, resetting agent state
1524::INFO::2019-02-27 10:26:08,203::handle_control_event::Control command 1
1524::INFO::2019-02-27 10:26:08,218::handle_control_event::Control command 4

Yes you are right spice-vdagent is somewhat stuck - display resize does not work after remote-viewer reconnection. It works again after spice-vdagent service is restarted.
Comment 3 Radek Duda 2019-02-27 10:49:45 UTC 
I forgot to mention that after spice-vdagent service is restarted (after step 4), an error message-box appears : 'An error caused the following file transfers to fail: $filename'. Maybe it can help to identify in what situation has vdagent stuck.
Comment 4 Victor Toso 2019-02-27 11:03:14 UTC 
> Yes you are right spice-vdagent is somewhat stuck - display resize does not work after remote-viewer reconnection. It works again after spice-vdagent service is restarted.

Yep, bug in the agent, should be fixed asap.
Workaround is restarting the agent, either by restarting the vdservice, logout/login or rebooting VM.

Thanks!
Comment 5 Frediano Ziglio 2020-05-21 14:57:29 UTC 

*** This bug has been marked as a duplicate of bug 1548419 ***
Note You need to log in before you can comment on or make changes to this bug.