Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: spacebar generates non-space Version-Release number of selected component (if applicable): Released LiveCD of Fedora 24 for x86_64 How reproducible: It has happened several times, on several machines. I don't know whether it is always. Seems to be consistent within one boot. Steps to Reproduce: 1. Boot Live CD (I actually boot from a USB, checking the medium first) 2. Try to type a space Actual results: No space. Some claim that spacebar is interpreted as "zoom text" but I haven't observed this Expected results: space Additional info: Workaround: shift-space does work. See this thread where others observe this problem: http://forums.fedoraforum.org/showthread.php?t=310369
Same issue here. Booting from Fedora 24 dd'ed onto a USB stick. Space key non-functional. XPS 13, QHD+ display (4kish) Installed to M.2 SSD... issue persisted across reboot into installed OS. Plugged in external USB keyboard... same problem. Performed dnf update (using the holding shift solution). Rebooted and the issue went away.
Can't fix with "dnf update" if either you're running from a DVD, or your Wi-Fi password has a space in it.
Do we know which package causes the problem? This would be good to know for those people building custom live-cds for various purposes.
@mrj: you can enter a space by holding SHIFT down when pressing the spacebar. This was mentioned in the fedora forum posting I linked to.
Hugh: Yes, thanks for the shift-space workaround. It allowed me to use the shell. However it's annoying if you're on a DVD and stuck with it; and shift-space didn't seem to work with the Wi-Fi password.
I was also having this issue. A dnf update and reboot resolved it for me. This happened on a recent install of F24. I didn't notice if it was present on the live USB during the install. I don't know if this will help anyone debug the issue but I noticed that it only happened on the first user that I logged in as. When I switched users, the space bar worked normally, but then when I switched back it stopped working again. I assumed it was something that I had installed on one user but I rebooted and logged in as the other user first and the same thing happened. Seems strange to me.
I'm able to reproduce this boot up the F24 Workstation LiveCD in VirtualBox 5.0.28 on OS X 10.12, as well as on a physical machine (Intel C226 w/ Haswell generation Xeon).
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.