Bug 665329

Summary:	changing workspace during SDL_WM_GrabInput leaves SDL client stuck
Product:	[Fedora] Fedora	Reporter:	Paolo Bonzini <pbonzini>
Component:	SDL	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	ppisar, twoerner
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	664771	Environment:
Last Closed:	2011-08-29 07:57:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Paolo Bonzini 2010-12-23 09:41:59 UTC

+++ This bug was initially created as a clone of Bug #664771 +++

Created attachment 470009 [details]
test program

Description of problem:
Easily reproducible using KVM's SDL interface.  Run this loop in a shell:

    i=0; while sleep 1; do echo $i; i=$((i+1)); done

Change workspace, stay there, go back.  The counter won't advance from the moment you press Ctrl-Alt-Right to the moment you go back to the original workspace and release Ctrl-Alt.

The bug provides a standalone program that demonstrates this bug.

Version-Release number of selected component (if applicable):
SDL-1.2.14-8.fc15

How reproducible:
100%

Steps to Reproduce:
1. Compile attached program:
gcc sdl.c `/usr/bin/sdl-config --cflags --libs` -o sdl
2. Run it with >1 workspaces set up.
3. Do Ctrl-Alt-Right and back (making sure Ctrl-Alt are pressed for more than one second)

Actual results:
Counter in the console remains stuck.

Expected results:
Counter in the console proceeds normally.

Additional info:
Patch at attachment 329082 [details] applies.

The bug is not present in upstream SDL 1.3.  As far as I know, upstream development of SDL 1.2 is halted (anyway the patch had been submitted there but it was not considered).

Comment 1 Petr Pisar 2011-08-26 07:35:19 UTC

This is duplicate of bug #480065, isn't?

Comment 2 Paolo Bonzini 2011-08-29 07:57:21 UTC

Yes, bug 480065 has been reopened since I reported this.

*** This bug has been marked as a duplicate of bug 480065 ***