I installed "onboard" as a virtual keyboard on the system. It looked much nicer and more useful than matchbox. I went into the settings and chose the auto open option when I edit the post. after that i restarted my raspberry pi. As it didn't come on automatically, I couldn't run it from the terminal or the menu normally. The error I get when I try to run it from terminal
Hej blackmamba,
I had the same issue with the on screen keyboard florence. After I installed at-spi2-core, it didn't crash anymore, though i could not get it to open automatically.
So I tried installing onboard and everything worked quiet well. Might be a hint..
regards, jarvis
Raspberry Pi B+
5.10.63 Kernel
Debian Buster 10
Waveshare 10.1" HDMI LCD Touch Display
Related
My Node.js project utilizes CEC control and VLC where the app turns on the TV and chooses the HDMI port that the VLC video stream will be viewed on at a scheduled time.
Everything worked on Buster except that too many indeterminate crashes with segmentation faults occur with cec-client.
Since I am nearing a 'production' release, I thought it best to upgrade the OS to Bullseye and find a cec-client replacement. I found cec-ctl and made it asynchronous - ctl-cec works perfectly, everytime, no crashes. BUT, now VLC does not render anything, not even a black screen. Doing a 'ps' command during a time that a video should be playing, I can see that VLC is running.
What I tried: It turns out that changing the /boot/config.txt dtoverlay=vc4-fkms-v3d (Buster) to dtoverlay=vc4-kms-v3d (Bullseye) causes the problem. The Buster version of dtoverlay seems to be required for VLC to run, and The Bullseye version of dtoverlay is required for a /dev/cec0 to be created and used by ctl-cec.
All I can see from my inexperienced view is mutual exclusivity, but this doesn't feel like this is the final answer. Using both dtoverlay version (Buster/Bullseye) will brick the pi (speaking from the very recent experience of one not well-versed in dtoverlays).
I also tried: I Googled this problem to the extent of my search skills and have not been able to resolve this problem.
Any help is greatly appreciated!
Raspbian OS: Bullseye (Desktop)
Raspberry Pi 3 B+
App: Node.js based with ability to make config changes and set schedules via an external browser within the LAN.
The solution for my project, after days of Googling, turned out to be TOO simple (found here: https://www.reddit.com/r/archlinuxarm/comments/lg4z5u/no_hdmi_audio_via_alsa_on_raspberry_pi_400/):
sudo apt install pulseaudio
along with:
dtoverlay=vc4-kms-v3d
VLC and cec-ctl now work together perfectly on Raspberry Pi 3B+/Bullseye
My raspberry pi is installed with the latest raspbian image, and now I am trying to program my SenseHAT. The status is :
The firmware boots up successfully, the rainbow is displayed on the
screen and Sense HAT, and it proceeds.
The OS(up-to-date raspbian) start loading with the splash screen, but
it is stuck at somewhere when it says udisks2.service,
All the OS modules are installed,
I2C is enabled at /boot/config.txt
dt_overlay is configured at /boot/config.txt.
Anybody has faced this freezing problem before? My raspberry pi 3 and Sense HAT simply not getting along with each other.
I have a Raspberry Pi 4B running under NOOBS. I have installed XRDP to be able to access the Raspberry from Windows.
The remote connection is working fine but whenever I launch an application (ex: Chromium) from Windows, I don't see anything happening. If I check directly on the screen connected on the Raspberry, I see that the application is running there.
It looks like whatever I launch on the remote desktop screen, the output goes to the native screen and I can't see it in the remote desktop window. I'm connected with exactly the same user on both sides.
Do you have any idea how to solve this?
Raspberry is known for not beeing compatible with any VNC Software.
You should try RealVNC first which comes with NOOBS. Make sure you have the latest version.
sudo apt-get update
sudo apt-get install realvnc-vnc-server realvnc-vnc-viewer
At your desktop select Menu > Preferences > Raspberry Pi Configuration > Interfaces.
Ensure that VNC is Enabled.
Now get your RealVNC Application for Windows and youre ready to go.
Another alternative is TightVNC, which works in most cases fine, too.
I am looking for a way to install noobs raspbian from network. I mean i do not want to connect an hdmi TV, mouse or keyboard.
What i read in documentation is to download noobs (full version) and copy files into sd card. I have read i need to change something in recovery.cmdline file (Adding vncinstall word).
This works for the first raspberry boot: I can see installation screen through VNC. I have choose "Raspbian + pixel" installation. Then, I can see the progress bar.
But at the end of the installation, when the raspberry reboots, i have no VNC, neither ssh or telnet server and at this time i need to plug an HDMI TV, mouse and keyboard.
Do you know how i can automaticly launch a VNC or SSH server without having to plug a TV and keyboard ?
Thanks
i have installed wheezy on my raspberry pi and everything works fine except for the IDLE software where both versions IDLE and IDLE 3 won't open when double clicking them from the desktop or from the start like menu.
i try to open them but nothing happens?!
i don't know what does this have to do with this issue, but i used to connect to raspberry pi by putty and xming11 and at that case the IDLE software didn't open when trying to access it.
however by using tightvnc, this issue was solved!!!