Bug 1005576
Summary: | No mouse pointer in Alpha TC5, KVM guest | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Madison Kelly <mkelly> |
Component: | gnome-desktop3 | Assignee: | Richard Hughes <rhughes> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | 20 | CC: | cslee-redhat, mchalupa, negativo17, rhughes, tiagomatos |
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: | 2015-06-29 12:20:58 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
Madison Kelly
2013-09-08 16:33:04 UTC
I continued on and the mouse pointer did not become visible. I installed all available OS updates and rebooted. The pointer is visible at the user selection screen, but it disappears again after logging in. Same issue here with Fedora 20 Beta RC2. Mouse available at login, and then no cursor visible after logging in. The same is happening since Alpha. I have found that after install of Fedora 20 client as long as I leave the resolution at 1024 x 768 I have a mouse pointer everywhere. If I change the resolution to another value spice handles this fine and I can work well, but after reboot I have pointer in login screen (which is still 1024 x 768) but not in the user sssion which has saved and is using the new resolution. In the Gnome resolution configuration screen the ratio is still shown as 4:3 even though the new resoltion is not 4:3, could the be part of the cause? I see this behavior in F21 Beta 4... I experience this bug in fresh Fedora 21-5 installation too. To be precise, the bug is there only under wayland session in F21. This seems to be the reason: ioctl(11, 0xc01c64a3, 0x7fff77205ac0) = -1 EFAULT (Bad address) This is underlying syscall from drmModeMoveCursor. Gnome shell under wayland is using native backend and in update_hw_cursor() this call fails. This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |