Bug 448077
| Summary: | gnome-typing-monitor locks only one head | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jan "Yenya" Kasprzak <kas> |
| Component: | gnome-settings-daemon | Assignee: | Bastien Nocera <bnocera> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | CC: | mclasen, rstrode, smithj |
| Target Milestone: | --- | Keywords: | Reopened, Triaged |
| 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 13:58:33 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
Jan "Yenya" Kasprzak
2008-05-23 11:33:30 UTC
Another related problem: when the cursor is on the second head, the second head gets locked, but the image under the grey stripes is taken from the first head. Yeah, that code is probably uber busted. Upstream is at: http://bugzilla.gnome.org/show_bug.cgi?id=492974 Thanks, I have added a back-reference to the upstream bugzilla. You can probably close this one as UPSTREAM (?). Just a short note - this bug is still not fixed in GNOME 2.24 (Fedora 10). *** Bug 499002 has been marked as a duplicate of this bug. *** Reopening, the bug is still present in Fedora 12 (control-center-2.28.1-4.fc12.x86_64), and still not fixed upstream. This was improved a while ago: * Mon Dec 7 2009 Matthias Clasen <mclasen> 2.28.1-9 - Improve typing break locking for multiple monitors Works for me (gnome-settings-daemon-2.28.1-10.fc12.x86_64), thanks! I am reopening the bug, because in gnome-settings-daemon-2.30.1-6.fc13.x86_64 and control-center-2.30.1-2.fc13.x86_64 the problem is back. Only the right head is locked. The left one is still available for mouse input, but not for the keyboard input. In addition to that, the "Postpone break" button becomes active after about 5 seconds s after the screen is locked (I am not sure whether this a bug or feature, but it definitely does not help in the "I am in a hurry" situations :-). 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. |