Bug 685156 - client mouse doesn't work for the first time in gdm with spice-vdagent
Summary: client mouse doesn't work for the first time in gdm with spice-vdagent
Keywords:
Status: CLOSED DUPLICATE of bug 682416
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-vdagent
Version: 6.1
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Hans de Goede
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-15 13:02 UTC by Michal Haško
Modified: 2015-03-02 03:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-16 11:53:57 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Michal Haško 2011-03-15 13:02:20 UTC
Version-Release number of selected component (if applicable):
spice-vdagent-0.6.3-6.el6.i686
spice-server-0.8.0-1.el6.x86_64
spice-client-0.8.0-2.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. boot a rhel6.1 guest with spice-vdagentd service on in runlevel 5
2. in GDM, observe that client mouse is not used (mouse cursor is catured within the spicec window
  
Actual results:
local mouse is not used, it is captured in the spicec window

Expected results:
local mouse should be used and not captured

Additional info:
when you log in and log out of gnome, the local mouse is used just fine.

Comment 1 Michal Haško 2011-03-15 13:08:26 UTC
update: after logging out of GNOME, the mouse is not functioning at all

Comment 3 Hans de Goede 2011-03-15 13:16:21 UTC
Pretty sure this is a dup of the selinux issue, can you edit
/etc/sysconfig/selinux, set selinux to permissive and try again ?

Comment 4 Hans de Goede 2011-03-15 13:17:04 UTC
Note the selinux issue is being QA-ed by mkrcmari, ask him for details.

Comment 5 Michal Haško 2011-03-16 11:53:57 UTC
Hans, you are right, it is a duplicate of the SELinux issue

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


Note You need to log in before you can comment on or make changes to this bug.