Bug 918310

Summary: flurry of syslog messages from spice-vdagent
Product: [Fedora] Fedora Reporter: Gene Czarcinski <gczarcinski>
Component: spice-vdagentAssignee: Hans de Goede <hdegoede>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 18CC: hdegoede, marcandre.lureau, sandmann
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-13 11:01:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
some messages from /var/log/messages none

Description Gene Czarcinski 2013-03-05 21:38:41 UTC
Created attachment 705671 [details]
some messages from /var/log/messages

Description of problem:
Running f18 virtual guest on f18 host using qemu-kvm/libvirt/virt-manager, etc.

Suddenly there is a "flurry: or "error" messages in the virtual's syslog from spice-vdagent.  The messages seem to relate to the clipboard and copy/paste.

Attached are some "typical" messages.

Version-Release number of selected component (if applicable):
Fedora 18, spice-vdagent 0.12.1-1

How reproducible:
Pretty easy ... run one or more virtual guests with qxl display and spice (not vnc).  Run tail -f /var/log/messages in the virtual. Do a ctrl-shift-c in a host terminal window ... then do ctrl-shift-v  a few of those should give you some message to look at.

Comment 1 Hans de Goede 2013-03-09 22:05:32 UTC
Hi,

Thanks for the bug-report. I've tried to reproduce this but failed. Can you please answer the following questions to help me try to reproduce this? :

1) What desktop environment and terminal application are you using on the host ?

2) What desktop environment are you running inside the guest ?

3) Are you running any special software such as a clipboard manager on the host ?

4) Are you running any special software such as a clipboard manager inside the guest ?

Regards,

Hans

Comment 2 Gene Czarcinski 2013-03-10 14:56:34 UTC
1) What desktop environment and terminal application are you using on the host ?

Host runs Fedora 18 with Gnome desktop.

2) What desktop environment are you running inside the guest ?

The guest desktops are usually xfce4 and though there are some guest with gnome, kde, etc.  Since xfce is used mostly, it is the one I noticed having the problem ... I run tail -f /var/log/messages in one terminal window.  And, the system is Fedora 18 also.

3) Are you running any special software such as a clipboard manager on the host ?
Nothing that I specifically did.

4) Are you running any special software such as a clipboard manager inside the guest ?
Not that I know of ... whatever xfce does.

Comment 3 Hans de Goede 2013-04-12 13:08:58 UTC
I've again tried to reproduce this, and again I failed. This time I used xfce in the guest and gnome3 on the client side.

You're original problem report contains the following reproduction instructions:
"Do a ctrl-shift-c in a host terminal window ... then do ctrl-shift-v"

2 questions:
1) Are the ctrl-shift-c and ctrl-shift-v in the same terminal window, or is the copy in a terminal in the client, and the paste in a terminal on the guest ?
2) What terminal emulator are you using on the client side, and which one on the guest side ?

Also what is your locale / LANG / AC_ALL set to? Are you perhaps not using an UTF-8 locale ?

Comment 4 Gene Czarcinski 2013-05-11 15:08:47 UTC
I am sorry for not responding with the info you need.  I will try but do not promise I can get any.  It has been some time since this happened and I have worked around the problem.  I also have an additional constraint that I have to complete all my existing/outstanding efforts in the next 5 weeks because at that time my current Internet capabilities will be shutting down for at least three months.

I will try but no guarantees.

Comment 5 Hans de Goede 2013-08-13 11:01:51 UTC
Closing due to lack of response from the reporter.

Note this sounds a bit like a report received upstream in the mailing list, which was caused by running autoculsel (an old, buggy clipboard autosync tool) inside the guest. As a result of this some of the messages in question have been turned into debug messages since we cannot go and fix all broken X11 clients in existence.