![]() It's running TightVNC with the following command-line options: $ ps aux | grep vnc PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)" Linux raspberrypi 4.4.21-v7+ #911 SMP Thu Sep 15 14:22: armv7l $ cat /etc/os-release My Raspberry Pi is running what I believe is the latest version of Raspbian (I updated/upgraded again last night to be sure): $ uname -a At least, I couldn't find anything ibus in ps and I couldn't find any options in the GUI preferences. There were some lubuntu posts about possibly not using ibus, but, from what I can tell, that is not relevant to my situation. I've searched for this issue on Google, but my search has turned up very little. I say "almost" above because, even though pressing keys on the keyboard don't appear to do anything, the cursor (especially visible in the terminal window) does flicker with each key press as it would if I were typing actual text. Restarting the vnc server does fix it until I start Chromium again. Closing the vnc connection from the client and logging back in doesn't fix the problem. Closing Chromium doesn't fix the problem. Mouse input still works fine and I can open and close programs to my heart's content. It is almost as if there is no keyboard connected at all at this point. However, if I start Chromium, all of the sudden nothing will accept keyboard input. I can use, for instance, the word processor or terminal available through the GUI. When I log on the first time after a reboot (or after restarting the vnc server), everything works fine. ![]() To start Chromium, I log with a vnc connection. ssh is fine, but I can't run Chromium on the Raspberry Pi via ssh (at one time, I found a tutorial on how to do this, but it has since been taken down and I think Google nixed the support for that somewhere along the line). Since I'm running headless, my primary means of connecting are via ssh and vnc connections from my Chromebook. Unfortunately, since doing so, I've been having problems. This kind of worked for a few months, but the cloud connection would go down after a few days and I'd have to reboot the Raspberry Pi to get it back (there was probably a better way, but, since it was headless, it just seemed easier to reboot).Įventually, I got tired of rebooting the Raspberry Pi and I read something on the Internet about upgrading my software to get new versions of the OS and of Chromium. To do this, I downloaded Chromium onto the Raspberry Pi and signed in using my gmail account. Both of the printers are accessible wirelessly from my home network, but because my primary computer is a Chromebook and I use Android phones and tablets, the only good way I've found to print to them is using Google Cloud Print. To do so, I bought a Raspberry Pi 2 and set it up as a headless print server following some online tutorials. I have a couple of older printers (a Brother and an HP all-in-one) that I want to run as wireless and cloud-based printers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |