i have a problem logging in to one of my rpis, its been running for some years fine but yesterday i went to login via vnc, and i am now presented with a gui login which never happened before. (it normally logged straight into the desktop)
the default login/pw is no longer working via this gui or the shell.
I plugged in a monitor and keyboard as ive seen suggestions to press ctrl+alt f1 etc and i can see some errors as shown.
any ideas? 🤞
I believe its the same os as one of my others but i cannot confirm this:
os detail:
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
thanks for reading/helping
screenshots of pi login error
Related
I am trying to get a GUI running on an AWS Centos 7 instance. Tiger vnc seems to run fine and I can get connected with the tigervnc viewer. However, all I get is a grey screen with 4 checkboxes in the upper right hand corner.
I installed Gnome and Server with GUI and I have tried changing my xstartup a hundred different ways, but I always get a grey screen. See the screenshot.
How can I get the gnome gui to work over my vnc session?
thanks
I found out that you will get this issue when using cPanel and WHM if you have the user in a jailed root. Open up the access and the full OS will load.
I would imagine that there is some way to work around this to keep a jailed root, but I am not a linux guru, so I don't know how to accomplish that.
I had built console core image for raspberry Pi3, and I am able to boot the Rpi3 successfully using SD card.
I have created an electron app which is able to launch on remote display over ssh.
However when I launch the application on Monitor connected through HDMI Cable, It gives following error
Can not open Display :0.0
I have seen many people asking this question for not able to launch on remote display, which works fine in my case.
Can anyone help in this?
With console core, you don't have an X server running to display on.
You can upgrade your system to include the X installation -- search for 'install pixel desktop' -- or you could just refresh the card with the lite or full image.
If you set the Pi to auto login to the pi account, you can start your application on login by adding it to the bottom of .xinitrc. You could also start it from a remote ssh, displaying on the local display, by setting DISPLAY=:0 in the environment before you start. You'll need to explore the world of X Windows authentication to make this work. See the man page for the xhost command, for instance.
(This is an expansion of LetoThe2nd's comment, which probably should have been an answer instead.)
Console core image means that there is no xserver running, and hence no display :0. Try getting started with core-image-x11 maybe, or whatever suits the RasPi.
I am currently programming a robot that is controlled by a raspberry-pi3 b with Xenial 16.04.
When i turn it on, the raspberry needs to automatically start up and launch some python programs. The problem is that it gets stuck on the login screen, waiting for me to press 'ok' (i removed the password).
Auto login isn't available in raspi-config, and going into System > Users and groups doesn't offer the option either.
I've tried using systemd service and other solutions but none have worked for now. Do you have any ideas how i could login automatically into my session?
Auto login IS available in raspi-config.
Run sudo raspi-config;
Scroll down to Boot Options and press Enter;
Select Desktop/CLI;
You should see the options for Desktop Autologin or Console Autologin.
This is based on Raspbian Stretch.
You should not mess with systemd service.
I'm trying to connect to my remote server using teamviewer 12.0.81460. It used to work absolutely fine. But from past few days I see a black screen when I connect using TeamViewer(see attached screenshot). But when I move the cursor it starts showing some points on the screen but that's also not clear. One thing I noticed is that when I connect with remote desktop from another PC and bypass this login screen it works fine. But this login screen has some issue.
The solution I have tried so far:
Changing screen resolution
Disabling black screen on my TeamViewer Settings
Installing a lower version (11) on my PC but
it asks me to upgrade since
remote PC is running latest version.
Any help would be greatly appreciated.
I know this is late, but i had the a similar issue where i was trying to connect from my windows computer to mac computer and got stuck at a black login screen. The workaround i have found to be useful is as follows:
Type the first letter of the account i wanted to login to
Press ENTER
type account
Press Enter
The screen was still black and shows anything until i reach step 4, it redirects me to the account! This was because although the screen was not working, the keyboard was working on remote computer.
I let me Parallels Desktop running Windows XP to start automatically during mac log-in. And to start Windows upon launch to let my dad use his WinXP by just pressing the power button, bypassing the Mac login window and desktop completely. When he shuts down Windows, Parallels closes.
I seem to remember I have a trigger to shut down mac as soon as Parallels closes. But I don't remember where... I have an AppleScript that tells Finder to shut down. I understand that. But now the problem is Mac shuts down AS SOON AS it boots up every time! I can't figure out what's triggering the shutdown... And I've run out of places to look.
It seems like a normal shut down rather than a fatal error. Seems like someone has chosen the 'Shut Down' command as soon as Mac starts up. So could mac gurus suggest places I should look -- what might have triggered this -- I'm pretty sure it's Parallels-related. Maybe there is something in the Package Contents linked to the shutdown script??
You added the Applescript (that shut down the mac) to login items