Hide Forgot
Previously, after performing tasks such as resizing the window, copying and pasting data and changing to full-screen mode, the user session spice-vdagent process terminated when the system-level spice-vdagentd was restarted. With this update, the user session spice-vdagent process no longer crashes after restarts.
Description of problem: After running a small set of spice-vdagent tests, resizing the window, copy and pasting data, and full screen. Trying to stop and start the spice-vdagent service crashed the service. Restarting the service, shows that it is on, but it is unresponsive. (resizing, copy and pasting does not work) *Tested on RHEL 6.4 Snap3 64bit client/host Guest: RHEL 6.4 Snap3 32 bit guest Version-Release number of selected component (if applicable): spice-vdagent-0.12.0-4.el6.i686 How reproducible: Steps to Reproduce: 1. Stop & Start vdagent service 2. 3. Actual results: spice-vdagent crashes and is unresponsive after restarting the service Expected results: spice-vdagent is running and operational. Additional info:
Hi, Is this reproducable? Also have you checked that after the restart both the global daemon, (spice-vdagentd in ps aux) as well as the per user session daemon (spice-vdagent in ps aux) are running? Are there any clues in /var/log/spice-vdagent.log ? Regards, Hans
Created attachment 676924 [details] Crash info from abrt
Hi, >>Is this reproducable? I'm trying to reproduce it now, so far I have not been able to reproduce it. I will update the bug if I can. >>Also have you checked that after the restart both the global daemon, (spice-vdagentd in ps aux) as well as the per user session daemon (spice-vdagent in ps aux) are running? I only tried restarting the service, which did not work, I restarted the guest, and the service did work after that. >>Are there any clues in /var/log/spice-vdagent.log ? I see some error for clipboard and not being able to find session for cookie, I will attach this log to the bug.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
(In reply to comment #2) > Created attachment 676924 [details] > Crash info from abrt Ugh, this does not contain a backtrace, just a coredump file which is more or less unusable as is without first creating a vm re-creating your setup + debuginfo. I must say I like Fedora's abrt reports better ... Is there any tool that you know of to automatically generate a gdb backtrace from this?
Created attachment 680452 [details] Spice-vdagent log, crashed Jan 10th
I couldn't reproduce the crash, with the existing coredump, after installing all the debuginfo files I only see the following: Core was generated by `/usr/bin/spice-vdagent'. Program terminated with signal 11, Segmentation fault. #0 0x0804e5ea in udscs_write (conn=0x8fc4008, type=5, arg1=0, arg2=0, data=0x0, size=0) at src/udscs.c:399 399 while (wbuf->next)
(gdb) where #0 0x0804e5ea in udscs_write (conn=0x8fc4008, type=5, arg1=0, arg2=0, data=0x0, size=0) at src/udscs.c:399 #1 0x0804b273 in vdagent_x11_set_clipboard_owner (x11=<value optimized out>, selection=0 '\000', new_owner=0) at src/vdagent-x11.c:276 #2 0x0804c3aa in vdagent_x11_destroy (x11=0xb7704008) at src/vdagent-x11.c:180 #3 0x08049d6d in main (argc=1, argv=0xbfda31f4) at src/vdagent.c:242 (gdb)
Thanks! That was really useful. With the backtrace in hand it was actually pretty easy to figure out what what was going on, and writing a fix: http://cgit.freedesktop.org/spice/linux/vd_agent/commit/?id=f269ec359e0a9f7c11659af9e8121f7e8e714060 Adding devel-ack. Note to qa, this will be hard or impossible to reproduce, suggest sanity only qa.
I'm doing a new build for 6.5: spice-vdagent-0.12.0-4.el6. This new build brings in a whole set of interdependent patches from upstream to fix bug 881020, this includes the fix for this -> moving to MODIFIED.
Correction the new build is spice-vdagent-0.12.0-5.el6
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1560.html