I have downloaded the 32 bit ARM VScode to my raspberry Pi 3. It is currently running Jessie and I have ran updates and upgrade.
The VSCode icon is available and I can find the exe file is installed. When I click to open it will not launch. Nothing happens, no messages or dialog box. I have uninstalled and reinstalled and still the same thing happens.
Am I missing something?
I had this exact same problem, and this command worked for me:
sudo apt --fix-broken install
When I launch VS Code after installation, I get black screen. I tried to reinstall it, but without a result and I also tried to start it with «--disable-gpu» argument, no result too. Is there any possible solution for this?
Screenshot.
Also «--status» argument.
I use Raspberry Pi 3 on Raspbian and code-oss 1.32.0 ARM (by headmelted)
you've probably figured it out so far, but I'll answer in case anyone else visits this thread.
All you need to do is downgrade code-oss.
sudo apt-get install code-oss=1.29.0-1539702286
I am working on a project similar to the one at http://www.instructables.com/id/Raspberry-Pi-Wall-Mounted-Google-Calendar/?ALLSTEPS
Similarly, I need my pi to stay on constantly. I have the regular Raspbian OS installed and I am using Iceweasel browser to run a web application all day.
I have tried every single one of these suggestions from this link http://www.bitpi.co/2015/02/14/prevent-raspberry-pi-from-sleeping/
Yet the pi fails to stay on longer than 10 minutes. Any help would be greatly appreciated.
I installed xscreensaver
sudo apt-get install xscreensaver
Once installed, go to Rpi's desktop "Menu" (left top corner)
Go to preference --> screensaver.
You will see a screen saver main menu. In the mode drop-down menu, select "disable screensaver" then close the window.
Reboot the Raspberry PI.
It should work now.
You don't need to install lib, just edit lightdm
1 - Open lightdm using your prefer text editor, eg using default editor(nano).:
sudo nano /etc/lightdm/lightdm.conf
2 - Add this line
xserver-command=X -s 0 -p 0 -dpms
I recently installed Raspian Buster with Desktop (circa 2019-September) - the smaller install with the Desktop, but without the "recommended software". I found there are two settings that have to be changed as either one of them will blank the screen in ten minutes under the default settings.
set screen saver timeout to zero:
xset s 0
and set dpms (EnergyStar) to disabled:
xset -dpms
This way I haven't needed to install anything (no screensaver). It was confusing because I'd tried both items, but it wasn't until I learned they both were blanking the screen at ten minutes that I saw what was going on. As this has tested out OK, the next step for me is to put them into an autostart routine.
ps Verify your settings with
xset q
Without installing anything, official Raspberry Pi doc:
On the Console
If you are using the Raspberry Pi solely on the console (no desktop GUI), you need to set the console blanking. The current setting, in seconds, can be displayed using
cat /sys/module/kernel/parameters/consoleblank
Here, consoleblank is a kernel parameter. In order to be permanently set, it needs to be defined on the kernel command line.
sudo nano /boot/cmdline.txt
Add consoleblank=0 to turn screen blanking off completely, or edit it to set the number of seconds of inactivity before the console will blank. Note the kernel command line must be a single line of text.
https://www.raspberrypi.org/documentation/configuration/screensaver.md
Simply enter the config with sudo raspi-config and disable screen blanking in the display settings.
I've created a picture frame with a pi 3 and want to stop the screen going blank. I installed xscreensaver as in answer 22 and it's working a treat:
sudo apt-get install xscreensaver
After install, went to Rpi's desktop "Menu" (left top corner)
Went to preference ---> screensaver.
Then In mode : section, selected "disable screensaver" and closed.
Rebooted Rpi.
I had the same issue with Raspbian OS that was installed on raspberry Pi device. I just installed xscreensaver by using the following command in default Command panel.
sudo apt-get install xscreensaver
After installation is completed, Go to the menu in the left corner and select preference. First time you will see a pop up to enable xscreensaver on your screen. Just accept it. After that you can disable the screensaver.
I wants to make my Pi a network security tool, so I downloaded the source code from Raspberry Pwn's github source [https://github.com/pwnieexpress/Raspberry-Pwn].
I found my network rather slow when installing, so I interrupted the progress. I used its uninstall script to make sure that all changes would be recovered.
The uninstall successfully ended, but since then I cannot proceed on to the GUI after I typed startx. Are there any way for me to proceed a clean install of all GUI components?
Thanks
You could try the following:
sudo apt-get remove --purge xserver-xorg
sudo apt-get install xserver-xorg
sudo dpkg-reconfigure xserver-xorg
Yesterday I installed Teamviewer 7 on my Centos 5.8 desktop. After a reboot, am not able to see the login screen. Only a blue color screen is visible.
I read https://superuser.com/questions/403548/os-x-stuck-at-blue-screen-after-installing-teamviewer-host-and-rebooting?rq=1
But how do I do that on Centos?
I know that to login to Single User Mode, we need to press a key while the os boots up. And then type single in the cmd. And then?
Once in Single User Mode, you can try to remove TeamViewer from your system.
For example, if you have installed TeamViewer by running the rpm -ivh teamviewer_linux.rpm command, you can run the rpm -e teamviewer_linux command to uninstall it.
I don't think that the Mac OS link you've referred to can be very useful in your case.
If you peek into the teamviewer_linux.rpm (for example by running the command rpm -qpl teamviewer_linux.rpm) you won't find any "Launch Agents and Daemons", since on CentOS TeamViewer is wrapped around a Windows Emulator (wine).
By default the TeamViewer files gets installed in the /opt/teamviewer folder; the only exception is the startup script /usr/bin/teamviewer7.
Finally, the rpm post-installation script does nothing more and nothing less than create a desktop icon and add a menu entry, so I can't really understand how the TeamViewer installation could have broken your system.