Bug 509000
Summary: | Mouse cursors are always black-and-white, 1-bit glyphs. They should be high-color instead. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kriston Rehberg <me> |
Component: | tigervnc | Assignee: | Adam Tkac <atkac> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | atkac, funtoos, matt, ovasik, scottro11 |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-06-27 14:16:00 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
Kriston Rehberg
2009-06-30 19:36:06 UTC
This, or at least something quite similar, is still occuring with the 64 bit versoin 1.0.0-3.fc12 in F12. When using tigervnc and connecting to a Windows host, the mouse is a tiny dot. It sometimes works as cursor should and sometimes doesn't. This occurs with any connection to a Windows machine. Removing tigervnc and replacing it with tightvnc fixes the problem. This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping So, this problem is still in F13, making tigervnc a poor choice of default viewer. If tigervnc's viewer can't be fixed, perhaps it should replaced with another vnc viewer program. This is endemic of all the various VNC software packages out there that came from the original VNC before it became "RealVNC." According to an email I received from RealVNC the commercial version of RealVNC has the bug fixed. I have no further information. I don't have the issue with a homemade tightvnc rpm. (I didn't do anything to it, it came with a spec file, though at this point, I don't remember where I got the tarball. It's version 1.3.10-1 if that helps.) Yes, I neglected to recall that later versions of TightVNC do not have this problem. (In reply to comment #5) > I don't have the issue with a homemade tightvnc rpm. (I didn't do anything to > it, it came with a spec file, though at this point, I don't remember where I > got the tarball. It's version 1.3.10-1 if that helps.) Does anybody have any idea about which version of tightvnc fixed it? May be its just about taking a patch from tightvnc and applying it to tigervnc code base. See my comment (#5). 1.3.10-1.x86_64 (I've been looking around my various machines, adn still can't find the srpm. I must have gotten it somewhere--rpmforge?) Ok, just found it. The source code tarball at http://tightvnc.com, when extracted, contains the spec file. I guess I used that to build. Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. Re-opened for Fedora 13 where the problem persists. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. As this is still not fixed, I've filed this against F15 as bug 717032 |