Description of problem: When tvtime is running and I am working in other window (for example in rxterm now, but I think it does not matter), when SHIFT key is pressed in wrong time, it's locked. Then all keys are giving char as if SHIFT is hold. Version-Release number of selected component (if applicable): I am seeing this problem from at least Fedora 11. How reproducible: sometimes, always if you try to reproduce as described below Steps to Reproduce: 1. run tvtime 2. open terminal window and select terminal 3. hold SHIFT+3 for at least 60 seconds Actual results: ####################################################################################################################################################################################################################################################################################3333333333333333333333333333333333333333333333 Expected results: Only "####" no 3333 chars. Additional info: If this happens, unable to unlock SHIFT lock by only pressing shift. I need to do reproduce steps again to unlock.
Hello, thanks for reporting. I would bet it's the (silly) way tvtime disables screensaver that causes this weirdnes. I'll see what I would be able to do with that. Regards.
Same problem if no xscreensaver or other screensaver running. I think it's less often without running screensaver, but still happens sometimes.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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
Same problem on Fedora 13. May be occurs less times.
Hello. I admit I have forgotten about this one a bit. However: The magnificent Debian guys already seem to have patch for the issue so I just bent it a little. I might get to the testing in the evening. Just in case -- I uploaded the testing packages to http://tsmetana.fedorapeople.org/tvtime-571339.test/ Regards.
Thank you. Looking that your packages are 64bit only and I have only a 32bit system. Please make a build in koji and I will test them. Thank you.
tvtime-1.0.2-14.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/tvtime-1.0.2-14.fc14
tvtime-1.0.2-14.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/tvtime-1.0.2-14.fc13
tvtime-1.0.2-14.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update tvtime'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/tvtime-1.0.2-14.fc14
Jan, thank you for your feedback in Bodhi.
tvtime-1.0.2-14.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
tvtime-1.0.2-14.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.