Bug 679361

Summary: spicec killed by signal 11 during shutdown in a full screen mode
Product: Red Hat Enterprise Linux 6 Reporter: Marian Krcmarik <mkrcmari>
Component: spice-clientAssignee: Uri Lublin <uril>
Status: CLOSED WORKSFORME QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1CC: dblechte, hdegoede, mkenneth
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-01 14:18:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Abrt log none

Description Marian Krcmarik 2011-02-22 11:45:45 UTC 
Description of problem:
While Guest machine is shutting down a segmentation fault occurs.

Version-Release number of selected component (if applicable):
architecture: x86_64
cmdline: spicec -h localhost -p 3001
component: spice-client
crash_function: RedScreen::find_pointer_layer
executable: /usr/bin/spicec
kernel: 2.6.32-114.0.1.el6.x86_64
package: spice-client-0.7.3-1.el6
rating: 4
reason: Process /usr/bin/spicec was killed by signal 11 (SIGSEGV)
release: Red Hat Enterprise Linux Workstation release 6.1 Beta (Santiago)

How reproducible:
3/3

Steps to Reproduce:
1. Run VM using qemu-kvm (/usr/libexec/qemu-kvm -vga qxl -m 1024 -smp 2 -spice port=3001,disable-ticketing /dev/rootvm/RHEL61_x64_test, where RHEL61_x64_test is lv with installed RHEL6.1 guest)
2. Connect to the Guest with spicec (spicec -h localhost -p 3001)
3. Switch to the fullscreen mode with pressing Shift+F11.
4. Shutdown the Guest with using shutdown button.

  
Actual results:
Segmentation fault

Expected result:
spice disconnects gracefully (no error to the user) when the VM is shutdown.
Comment 1 Marian Krcmarik 2011-02-22 11:46:57 UTC 
Created attachment 480110 [details]
Abrt log
Comment 3 Hans de Goede 2011-03-01 14:18:45 UTC 
I cannot reproduce this I'm afraid, please re-open if you see this again.
Comment 4 Marian Krcmarik 2011-03-01 14:38:22 UTC 
(In reply to comment #3)
> I cannot reproduce this I'm afraid, please re-open if you see this again.

I reproduced it 4-5 times in row but I am not able to reproduce it now as well. If nothing interesting in abrt report came out I would reopen in case It happends again.