Bug 1017301
| Summary: | Cursor is invisible over input fields on windows 8 client | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Tomas Jamrisko <tjamrisk> |
| Component: | mingw-virt-viewer | Assignee: | Marc-Andre Lureau <marcandre.lureau> |
| Status: | CLOSED DUPLICATE | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | acathrow, cfergeau, tjamrisk, yeylon |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-10-10 12:12:54 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: | |||
|
Description
Tomas Jamrisko
2013-10-09 15:20:39 UTC
client doesn't provide any warning? Can you get the SPICE_DEBUG=1 log please. only the warning about automount-inhibiting implementation not available. There's nothing else on cmd nor in event log ah, then this is likely going to be a gtk+ bug on win8. It would be surprising that noone else hit that. Well, it changes over URL input field before any connection actually takes place... (In reply to Tomas Jamrisko from comment #4) > Well, it changes over URL input field before any connection actually takes > place... yeah, but that's a local gtk+ or local windows cursor. I guess the customer cursor path could be broken. So, it's not really invisible, it appears that way on white background. It's actually ocmposed of white and transparent pixels only. Each line one pixel wide. Anyway started it wit --spice-debug and: (remote-viewer.exe:1812): GSpice-DEBUG: ../../gtk/channel-cursor.c:354 cursor-4:0: set_cursor: flags 4, size 0 (remote-viewer.exe:1812): GSpice-DEBUG: ../../gtk/channel-cursor.c:360 cursor-4:0: set_cursor: type 1, 3, 32x32 (remote-viewer.exe:1812): GSpice-DEBUG: ../../gtk/channel-cursor.c:354 cursor-4:0: set_cursor: flags 4, size 0 (remote-viewer.exe:1812): GSpice-DEBUG: ../../gtk/channel-cursor.c:360 cursor-4:0: set_cursor: type 1, 2, 32x32 (remote-viewer.exe:1812): GSpice-DEBUG: ../../gtk/channel-cursor.c:354 cursor-4:0: set_cursor: flags 4, size 0 (remote-viewer.exe:1812): GSpice-DEBUG: ../../gtk/channel-cursor.c:360 cursor-4:0: set_cursor: type 1, 3, 32x32 (remote-viewer.exe:1812): GSpice-DEBUG: ../../gtk/channel-cursor.c:354 cursor-4:0: set_cursor: flags 4, size 0 (remote-viewer.exe:1812): GSpice-DEBUG: ../../gtk/channel-cursor.c:360 cursor-4:0: set_cursor: type 1, 2, 32x32 (remote-viewer.exe:1812): GSpice-DEBUG: ../../gtk/channel-cursor.c:354 cursor-4:0: set_cursor: flags 4, size 0 (remote-viewer.exe:1812): GSpice-DEBUG: ../../gtk/channel-cursor.c:360 cursor-4:0: set_cursor: type 1, 3, 32x32 (remote-viewer.exe:1812): GSpice-DEBUG: ../../gtk/channel-cursor.c:354 cursor-4:0: set_cursor: flags 4, size 0 (remote-viewer.exe:1812): GSpice-DEBUG: ../../gtk/channel-cursor.c:360 cursor-4:0: set_cursor: type 1, 2, 32x32 (remote-viewer.exe:1812): GSpice-DEBUG: ../../gtk/channel-cursor.c:354 cursor-4:0: set_cursor: flags 4, size 0 (remote-viewer.exe:1812): GSpice-DEBUG: ../../gtk/channel-cursor.c:360 cursor-4:0: set_cursor: type 1, 3, 32x32 (remote-viewer.exe:1812): GSpice-DEBUG: ../../gtk/channel-cursor.c:354 cursor-4:0: set_cursor: flags 4, size 0 (remote-viewer.exe:1812): GSpice-DEBUG: ../../gtk/channel-cursor.c:360 cursor-4:0: set_cursor: type 1, 2, 32x32 That is probably related to the putty change in 998529. What happen with previous release of mingw-virt-viewer? Works with 0.5.6-5, so looks like you're right. I propose closing as duplicate of 1002697, and reopening there. Perhaps we should revert the change? I guess the issue happens not only with win8 clients. *** This bug has been marked as a duplicate of bug 1002697 *** Tomas, is it really only with win8 client? I wasn't sure about Windows 7 as I had only a VM as client, but tried in on a physical client and the Cursor appeared white and dotted as well. So it's not windows 8 exclusive -> It happens on all of them. |