Keyboard stopped working -- big problem - Printable Version +- PINE64 (https://forum.pine64.org) +-- Forum: PinePhone Pro (https://forum.pine64.org/forumdisplay.php?fid=177) +--- Forum: PinePhone Pro Software (https://forum.pine64.org/forumdisplay.php?fid=179) +--- Thread: Keyboard stopped working -- big problem (/showthread.php?tid=15943) Pages:
1
2
|
Keyboard stopped working -- big problem - tckosvic - 02-02-2022 My keyboard has stopped working. When there is a text entry in an app the keyboard does not open. That leaves you dead in the water. You can't work with terminal to make any corrections. I am running off system memory; not an sd card. Working reasonably well with keyboard til now. Have restarted several times and also just shutdown and then restarted. No changes. What does the RE button do? Could that help. tom kosvic RE: Keyboard stopped working -- big problem - bcnaz - 02-02-2022 Check your POGO pins ? RE: Keyboard stopped working -- big problem - tckosvic - 02-02-2022 (02-02-2022, 07:42 AM)bcnaz Wrote: Check your POGO pins ? I have nothing attached to the pogo pins. The dip switches are all in the upper position as when they came RE: Keyboard stopped working -- big problem - bcnaz - 02-02-2022 Are you talking about the onboard screen keyboard or the new physical keyboard ? RE: Keyboard stopped working -- big problem - drh - 02-02-2022 The onscreen keyboard is also not usable on my PPP running stock kde/plasma. The only part of the keyboard that appears at the very bottom of the screen is the first row that has ctrl, arrows and a few others. No other keys are visible, which is why the onscreen has become unusable. I have not found a way to restore the appearance of the full keyboard. The happened this morning after applying an update using Discovery. The update was partially successful because a message appeared after the update process finished asking me whether to open discovery or repair. I chose repair but nothing seemed to happen. i then decided to recheck for the error message using the terminal and discovered that I cannot type anything. For now, the PPP is unusable without an onscreen keyboard. :-( RE: Keyboard stopped working -- big problem - tckosvic - 02-02-2022 (02-02-2022, 11:30 AM)drh Wrote: The onscreen keyboard is also not usable on my PPP running stock kde/plasma. The only part of the keyboard that appears at the very bottom of the screen is the first row that has ctrl, arrows and a few others. No other keys are visible, which is why the onscreen has become unusable. I am talking about the onscreen keyboard. The no-keyboard occurrence due to which I started this thread has the idential symptoms described by "drh" above. This also started this morning after a discovery update as per "drh". tom kosvic RE: Keyboard stopped working -- big problem - Ralt - 02-02-2022 I also have this same problem now. Things I have tried: A. https://forum.pine64.org/showthread.php?tid=12742 It seems like original pinephones have a "dock/undock" button in their top bar icons, but I don't have that at all. Don't see anything like "dock" anywhere in any settings. B. Theme? I have switched my "color" and "plasma theme" back to the defaults, but still no effect. C. Temp issue? I have rebooted several times now D. Keyboard Settings? I can still open the keyboard settings from the top menu bar, and I have also made sure that the "theme" for the keyboard is just "Breeze" to match my "plasma theme" and "color settings", in case the issue lies there for some crazy reason, but no dice. RE: Keyboard stopped working -- big problem - kaida - 02-02-2022 Did you try updating ? , cause for Arch , the current release has a broken onscreen keyboard and it's already fixed upstream but he hasn't made a new image yet , but a simple "sudo pacman -Syu" would fixed it RE: Keyboard stopped working -- big problem - bcnaz - 02-02-2022 Fresh install ? RE: Keyboard stopped working -- big problem - Ralt - 02-02-2022 (02-02-2022, 08:54 PM)kaida Wrote: Did you try updating ? , cause for Arch , the current release has a broken onscreen keyboard and it's already fixed upstream but he hasn't made a new image yet , but a simple "sudo pacman -Syu" would fixed it Yes, just as the others have stated, this was *caused* post-update. |