Fair enough. But I’m sure you’ll recognize the nagging realization that I turned away from a problem (GUI doesn’t work) without resolving it. If I do that, it will be a monkey on my back for a long, long time. 
I’d just as soon get the problem fixed once and for all, and then move on.
1 Like
I’m willing to do that (I guess), but I’m not sure of what 1) the sources of the software and 2) the steps involved would be.
This far removed from the original setup (a month or so), I can’t recall just which route I did take, partly because of information-rust, and partly because I’ve been doing all this stuff by rote with only a general understanding of what was going on.
I believe there was an error with the 3.6.2 piaware sd-card image where kernel updates wouldn’t properly work because of some problem i don’t remember.
So it may be you did an apt-get upgrade or just a piaware automatic update and that wouldn’t all install because there isn’t enough space on /boot. That could and might well me the source of your problems.
To check if you have that space on boot problem you can do:
sudo apt-get update
sudo apt-get upgrade
And see if it works properly or gives you any errors.
If you want to get putty running first it’s available here
(Download PuTTY: latest release (0.79))
I did start with 3.6.2, but in the meantime I ran an update/upgrade and now I’m running 3.6.3.
Just ran these, and they evidently ran without anything remarkable occurring. (i.e. every line of the script(s) ran to a proper end (… Done) without reporting errors. I guess that means that I have enough space on the boot partition of the SD card?
If I do start over again, I’d like to be certain that everything currently present on the SD card is wiped/purged/eliminated before installing new software. Secondly, I’d (of necessity) be at least doing the first download on a Windows machine. (I guess. Or not. Is there a way to do all of this on the Pi itself? I have it configured for kb/monitor/wifi access.)
BTW, this message is delayed because when I originally tried to send, I got a message response saying “New members can send a limited number of messages. Please try again in an hour”, or words to that effect. So I’m doing my time-out like a good little boy, facing the corner.
Let’s not start over just yet and see if we can access these logs
First enable ssh if you didn’t already with the following commands:
sudo systemctl enable ssh
sudo systemctl start ssh
Download Putty
(Download PuTTY: latest release (0.79))
and connect to the IP-address of the pi.
(Just start putty and it should be clear how to do it)
We’ll continue from there.
Ok!
ssh is enabled and started on the Pi.
PuTTY (64-bit version) is downloaded and started on the Windows 10 machine (this one).
First thing up is the PuTTY config window. I entered 192.168.1.25, which is the IP address of the Pi on my local network (via WiFi connection). As soon as I enter that, I get the PuTTY Security Alert (which I think is a good thing). I press ‘Yes’ to accept, and bingo! I get a new command screen having ‘192.168.1.25 - PuTTY’ in the title bar, and 'Login as: ’ as the command line prompt.
I think Mikey likes it!
But then it looks like the Pi timed out the network connection.
No matter, though. It’s easy enough to make the connection a second time.
What do I login as, and where do I go from here?
I just responded, but it may not have been addressed to you.
The default username is pi, unless you changed it use that.
Didn’t you use that to log in via GUI as well?
Once logged in you can paste a command by copying it with CTRL-C from here and then in putty using right click to paste. (ctrl-v won’t work)
Selecting text in putty should be enough to copy that to the clipboard you can then paste it here with crtrl-v.
Let’s try the following two commands again:
sudo cat /var/log/lightdm/lightdm.log
cat /home/pi/.xsessionerrors
Yes yes the first probably got a permission denied last time because i didn’t include sudo 
Maybe the file really does not exist we will see then we need to find out which display manager you are using.
The other file might just not exist because the problem is not with xsession.
I’ll just include this command to see which display manager is running:
/etc/X11/default-display-manager
also you can run
journalctl -e
after trying to log in via the gui and see if you see any relevant errors.
Thanks a lot. I can now see what putty/ssh does!
Here’s the resulting output. Note that the log appears when running sudo, but permissions are denied elsewise:
login as: pi
pi@192.168.1.25's password:
Linux piaware-dbm0 4.14.71-v7+ #1145 SMP Fri Sep 21 15:38:35 BST 2018 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Oct 27 17:50:54 2018 from 192.168.1.155
pi@piaware-dbm0:~ $ cat /home/pi/.xsessionerrors
cat: /home/pi/.xsessionerrors: No such file or directory
pi@piaware-dbm0:~ $ sudo cat /home/pi/.xsessionerrors
cat: /home/pi/.xsessionerrors: No such file or directory
pi@piaware-dbm0:~ $ cat /var/log/lightdm/lightdm.log
cat: /var/log/lightdm/lightdm.log: Permission denied
pi@piaware-dbm0:~ $ sudo cat /var/log/lightdm/lightdm.log
[+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.01s] DEBUG: Starting Light Display Manager 1.18.3, UID=0 PID=510
[+0.01s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.01s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.01s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.01s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registered seat module xlocal
[+0.01s] DEBUG: Registered seat module xremote
[+0.01s] DEBUG: Registered seat module unity
[+0.08s] DEBUG: Monitoring logind for seats
[+0.08s] DEBUG: New seat added from logind: seat0
[+0.09s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.09s] DEBUG: Seat seat0: Starting
[+0.09s] DEBUG: Seat seat0: Creating user session
[+0.11s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
[+0.11s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+0.13s] DEBUG: User pi added
[+0.16s] DEBUG: Seat seat0: Creating display server of type x
[+0.17s] DEBUG: Using VT 7
[+0.17s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.17s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.17s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+0.17s] DEBUG: DisplayServer x-0: Launching X Server
[+0.18s] DEBUG: Launching process 537: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.18s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.18s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.18s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+3.21s] DEBUG: Got signal 10 from process 537
[+3.21s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+3.21s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+3.39s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+3.39s] DEBUG: Session pid=732: Started with service 'lightdm-autologin', username 'pi'
[+3.49s] DEBUG: Session pid=732: Authentication complete with return value 0: Success
[+3.49s] DEBUG: Seat seat0: Session authenticated, running command
[+3.49s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+3.49s] DEBUG: Session pid=732: Running command /etc/X11/Xsession default
[+3.49s] DEBUG: Creating shared data directory /var/lib/lightdm/data/pi
[+3.49s] DEBUG: Session pid=732: Logging to .xsession-errors
[+3.80s] DEBUG: Activating VT 7
[+3.80s] DEBUG: Activating login1 session c1
[+3.80s] DEBUG: Seat seat0 changes active session to c1
[+3.80s] DEBUG: Session c1 is already active
[+3.92s] DEBUG: Session pid=732: Exited with return value 0
[+3.92s] DEBUG: Seat seat0: Session stopped
[+3.92s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+3.92s] DEBUG: Sending signal 15 to process 537
[+3.95s] DEBUG: Seat seat0 changes active session to
[+3.95s] CRITICAL: session_get_login1_session_id: assertion 'session != NULL' failed
[+4.20s] DEBUG: Process 537 exited with return value 0
[+4.20s] DEBUG: DisplayServer x-0: X server stopped
[+4.20s] DEBUG: Releasing VT 7
[+4.20s] DEBUG: DisplayServer x-0: Removing X server authority /var/run/lightdm/root/:0
[+4.20s] DEBUG: Seat seat0: Display server stopped
[+4.20s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+4.20s] DEBUG: Seat seat0: Creating greeter session
[+4.21s] DEBUG: Seat seat0: Creating display server of type x
[+4.21s] DEBUG: Using VT 7
[+4.21s] DEBUG: Seat seat0: Starting local X display on VT 7
[+4.21s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+4.21s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+4.21s] DEBUG: DisplayServer x-0: Launching X Server
[+4.22s] DEBUG: Launching process 791: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+4.22s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+5.05s] DEBUG: Got signal 10 from process 791
[+5.05s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+5.05s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+5.24s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+5.24s] DEBUG: Session pid=806: Started with service 'lightdm-greeter', username 'lightdm'
[+5.29s] DEBUG: Session pid=806: Authentication complete with return value 0: Success
[+5.29s] DEBUG: Seat seat0: Session authenticated, running command
[+5.29s] DEBUG: Session pid=806: Running command /usr/sbin/lightdm-gtk-greeter
[+5.29s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+5.29s] DEBUG: Session pid=806: Logging to /var/log/lightdm/seat0-greeter.log
[+5.48s] DEBUG: Activating VT 7
[+5.48s] DEBUG: Activating login1 session c2
[+5.48s] DEBUG: Seat seat0 changes active session to c2
[+5.48s] DEBUG: Session c2 is already active
[+6.95s] DEBUG: Greeter connected version=1.18.3 resettable=false
[+11.76s] DEBUG: Greeter start authentication
[+11.76s] DEBUG: Session pid=845: Started with service 'lightdm', username '(null)'
[+11.78s] DEBUG: Session pid=845: Got 1 message(s) from PAM
[+11.78s] DEBUG: Prompt greeter with 1 message(s)
[+16.58s] DEBUG: Greeter start authentication for pi
[+16.58s] DEBUG: Session pid=845: Sending SIGTERM
[+16.59s] DEBUG: Session pid=854: Started with service 'lightdm', username 'pi'
[+16.59s] DEBUG: Session pid=845: Terminated with signal 15
[+16.59s] DEBUG: Session: Failed during authentication
[+16.59s] DEBUG: Seat seat0: Session stopped
[+16.61s] DEBUG: Session pid=854: Got 1 message(s) from PAM
[+16.61s] DEBUG: Prompt greeter with 1 message(s)
[+24.34s] DEBUG: Continue authentication
[+24.46s] DEBUG: Session pid=854: Authentication complete with return value 0: Success
[+24.46s] DEBUG: Authenticate result for user pi: Success
[+24.46s] DEBUG: User pi authorized
[+24.48s] DEBUG: Greeter sets language en_US.utf8
[+24.53s] DEBUG: Greeter requests session lightdm-xsession
[+24.53s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+24.53s] DEBUG: Session pid=806: Sending SIGTERM
[+24.56s] DEBUG: Greeter closed communication channel
[+24.56s] DEBUG: Session pid=806: Exited with return value 0
[+24.56s] DEBUG: Seat seat0: Session stopped
[+24.56s] DEBUG: Seat seat0: Greeter stopped, running session
[+24.56s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session1
[+24.57s] DEBUG: Session pid=854: Running command /etc/X11/Xsession default
[+24.57s] DEBUG: Creating shared data directory /var/lib/lightdm/data/pi
[+24.57s] DEBUG: Session pid=854: Logging to .xsession-errors
[+24.86s] DEBUG: Activating VT 7
[+24.86s] DEBUG: Activating login1 session c3
[+24.86s] DEBUG: Seat seat0 changes active session to
[+24.86s] DEBUG: Seat seat0 changes active session to c3
[+24.86s] DEBUG: Session c3 is already active
[+24.96s] DEBUG: Session pid=854: Exited with return value 0
[+24.96s] DEBUG: Seat seat0: Session stopped
[+24.96s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+24.96s] DEBUG: Sending signal 15 to process 791
[+24.99s] DEBUG: Seat seat0 changes active session to
[+24.99s] CRITICAL: session_get_login1_session_id: assertion 'session != NULL' failed
[+25.13s] DEBUG: Process 791 exited with return value 0
[+25.13s] DEBUG: DisplayServer x-0: X server stopped
[+25.13s] DEBUG: Releasing VT 7
[+25.13s] DEBUG: DisplayServer x-0: Removing X server authority /var/run/lightdm/root/:0
[+25.13s] DEBUG: Seat seat0: Display server stopped
[+25.13s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+25.13s] DEBUG: Seat seat0: Creating greeter session
[+25.13s] DEBUG: Seat seat0: Creating display server of type x
[+25.13s] DEBUG: Using VT 7
[+25.13s] DEBUG: Seat seat0: Starting local X display on VT 7
[+25.13s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+25.13s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+25.13s] DEBUG: DisplayServer x-0: Launching X Server
[+25.13s] DEBUG: Launching process 915: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+25.13s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+26.02s] DEBUG: Got signal 10 from process 915
[+26.02s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+26.02s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+26.21s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+26.21s] DEBUG: Session pid=929: Started with service 'lightdm-greeter', username 'lightdm'
[+26.27s] DEBUG: Session pid=929: Authentication complete with return value 0: Success
[+26.27s] DEBUG: Seat seat0: Session authenticated, running command
[+26.27s] DEBUG: Session pid=929: Running command /usr/sbin/lightdm-gtk-greeter
[+26.27s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+26.27s] DEBUG: Session pid=929: Logging to /var/log/lightdm/seat0-greeter.log
[+26.46s] DEBUG: Activating VT 7
[+26.46s] DEBUG: Activating login1 session c4
[+26.47s] DEBUG: Seat seat0 changes active session to c4
[+26.47s] DEBUG: Session c4 is already active
[+27.64s] DEBUG: Greeter connected version=1.18.3 resettable=false
[+30.67s] DEBUG: Greeter start authentication
[+30.67s] DEBUG: Session pid=962: Started with service 'lightdm', username '(null)'
[+30.69s] DEBUG: Session pid=962: Got 1 message(s) from PAM
[+30.69s] DEBUG: Prompt greeter with 1 message(s)
[+56.45s] DEBUG: Seat seat0 changes active session to
[+79.90s] DEBUG: Seat seat0 changes active session to c5
pi@piaware-dbm0:~ $
[quote="wiedehopf, post:28, topic:41916"]
/etc/X11/default-display-manager
[/quote]
pi@piaware-dbm0:~ $ /etc/x11/default-display-manager
-bash: /etc/x11/default-display-manager: No such file or directory
pi@piaware-dbm0:~ $ sudo /etc/x11/default-display-manager
sudo: /etc/x11/default-display-manager: command not found
pi@piaware-dbm0:~ $
[quote="wiedehopf, post:28, topic:41916"]
journalctl -e
[/quote]
pi@piaware-dbm0:~ $ journalctl -e
Oct 27 18:10:06 piaware-dbm0 kernel: Voltage normalised (0x00000000)
Oct 27 18:11:24 piaware-dbm0 sshd[6953]: pam_unix(sshd:session): session closed
Oct 27 18:11:24 piaware-dbm0 systemd-logind[299]: Removed session c10.
Oct 27 18:11:53 piaware-dbm0 sshd[7079]: Accepted password for pi from 192.168.1
Oct 27 18:11:53 piaware-dbm0 sshd[7079]: pam_unix(sshd:session): session opened
Oct 27 18:11:53 piaware-dbm0 systemd-logind[299]: New session c11 of user pi.
Oct 27 18:11:53 piaware-dbm0 systemd[1]: Started Session c11 of user pi.
Oct 27 18:11:53 piaware-dbm0 sudo[7111]: pi : TTY=pts/0 ; PWD=/home/pi ; U
Oct 27 18:11:53 piaware-dbm0 sudo[7111]: pam_unix(sudo:session): session opened
Oct 27 18:11:54 piaware-dbm0 sudo[7111]: pam_unix(sudo:session): session closed
Oct 27 18:11:55 piaware-dbm0 kernel: Under-voltage detected! (0x00050005)
Oct 27 18:11:59 piaware-dbm0 kernel: Voltage normalised (0x00000000)
Oct 27 18:13:36 piaware-dbm0 sshd[7079]: pam_unix(sshd:session): session closed
Oct 27 18:13:36 piaware-dbm0 systemd-logind[299]: Removed session c11.
Oct 27 18:13:53 piaware-dbm0 sshd[7150]: Accepted password for pi from 192.168.1
Oct 27 18:13:53 piaware-dbm0 sshd[7150]: pam_unix(sshd:session): session opened
Oct 27 18:13:53 piaware-dbm0 systemd-logind[299]: New session c12 of user pi.
Oct 27 18:13:53 piaware-dbm0 systemd[1]: Started Session c12 of user pi.
Oct 27 18:13:54 piaware-dbm0 sudo[7178]: pi : TTY=pts/0 ; PWD=/home/pi ; U
Oct 27 18:13:54 piaware-dbm0 sudo[7178]: pam_unix(sudo:session): session opened
Oct 27 18:13:54 piaware-dbm0 sudo[7178]: pam_unix(sudo:session): session closed
Oct 27 18:14:01 piaware-dbm0 kernel: rpi_firmware_get_throttled: 1 callbacks sup
Oct 27 18:14:01 piaware-dbm0 kernel: Under-voltage detected! (0x00050005)
lines 979-1001/1001 (END)
I will not try to log in via the GUI and see of journalctl -e shows up any differently.
Again, thanks for all the help. It really is appreciated.(After trying a GUI login–again, unsuccessfully, I’m afraid 
)
pi@piaware-dbm0:~ $ journalctl -e
Oct 27 18:19:45 piaware-dbm0 sshd[982]: Accepted password for pi from 192.168.1.
Oct 27 18:19:45 piaware-dbm0 sshd[982]: pam_unix(sshd:session): session opened f
Oct 27 18:19:45 piaware-dbm0 systemd[1]: Created slice User Slice of pi.
Oct 27 18:19:45 piaware-dbm0 systemd[1]: Starting User Manager for UID 1000…
Oct 27 18:19:45 piaware-dbm0 systemd-logind[293]: New session c5 of user pi.
Oct 27 18:19:45 piaware-dbm0 systemd[1]: Started Session c5 of user pi.
Oct 27 18:19:45 piaware-dbm0 systemd[991]: pam_unix(systemd-user:session): sessi
Oct 27 18:19:45 piaware-dbm0 systemd[991]: Listening on GnuPG cryptographic agen
Oct 27 18:19:45 piaware-dbm0 systemd[991]: Listening on GnuPG cryptographic agen
Oct 27 18:19:45 piaware-dbm0 systemd[991]: Reached target Paths.
Oct 27 18:19:45 piaware-dbm0 systemd[991]: Reached target Timers.
Oct 27 18:19:45 piaware-dbm0 systemd[991]: Listening on GnuPG cryptographic agen
Oct 27 18:19:45 piaware-dbm0 systemd[991]: Listening on GnuPG cryptographic agen
Oct 27 18:19:45 piaware-dbm0 systemd[991]: Reached target Sockets.
Oct 27 18:19:45 piaware-dbm0 systemd[991]: Reached target Basic System.
Oct 27 18:19:45 piaware-dbm0 systemd[991]: Reached target Default.
Oct 27 18:19:45 piaware-dbm0 systemd[991]: Startup finished in 39ms.
Oct 27 18:19:45 piaware-dbm0 systemd[1]: Started User Manager for UID 1000.
Oct 27 18:19:45 piaware-dbm0 sudo[1019]: pi : TTY=pts/0 ; PWD=/home/pi ; U
Oct 27 18:19:46 piaware-dbm0 sudo[1019]: pam_unix(sudo:session): session opened
Oct 27 18:19:46 piaware-dbm0 sudo[1019]: pam_unix(sudo:session): session closed
Oct 27 18:19:46 piaware-dbm0 kernel: Under-voltage detected! (0x00050005)
Oct 27 18:19:50 piaware-dbm0 kernel: Voltage normalised (0x00000000)
lines 751-773/773 (END)
These power errors are not helping the situation. Not sure what you’re using for a power supply, But if you’re reusing an older wall wart, a PI 3B+ absolutely needs an updated (> 2.5A) wall wart.
Thanks for the catch; good eye!
I had been wondering what to do about that, but it seemed too minor compared with the brick wall I was facing.
Anyhow, I have taken your advice and the power supply is in its way. Thanks for the advice and pointer.
You’re welcome. I’m not convinced that’s all of the problem, but it never hurts to eliminate a possible problem or inconsistency. Raspberry Pi’s and other SBC do unpredictable things when there’s a power issue.
This
/etc/X11/default-display-manager
was of course supposed to be:
cat /etc/X11/default-display-manager
But no matter lightdm is in use anyway it seems so no need to check that.
Please check this commands output:
ls -ld /etc/alternatives/x-session-manager
And i just found another command i wrote something wrong:
cat /home/pi/.xsession-errors
I forgot the - in there so please do that again that’s where we fill find the actual error i think.
Also:
In the login screen is there a small button somewhere with a wrench (top right i think)
Click that and see what you can select there.
Select something different and try to log in.
Results coming right up!
pi@piaware-dbm0:~ $ cat /etc/X11/default-display-manager
/usr/sbin/lightdm
pi@piaware-dbm0:~ $ sudo cat /etc/X11/default-display-manager
/usr/sbin/lightdm
no joy on getting the x session manager
pi@piaware-dbm0:~ $ cat /etc/X11/default-display-manager
/usr/sbin/lightdm
pi@piaware-dbm0:~ $ sudo cat /etc/X11/default-display-manager
/usr/sbin/lightdm
pi@piaware-dbm0:~ $ cat /home/pi/.xsession-errors
Xsession: X session started for pi at Sat Oct 27 18:19:02 CDT 2018
Xsession: unable to start X session — no “/home/pi/.xsession” file, no
“/home/pi/.Xsession” file, no session managers, no window managers, and no
terminal emulators found; aborting.
pi@piaware-dbm0:~ $
The only thing that drops down is a radio button labellled “Default Xsession”. I can click on the dropdown (once dropped down) as much as I like and nothing changes. It makes no difference in GUI login behavior, either… No joy.
Yeah the window manager just got uninstalled somehow don’t ask me how.
sudo apt-get install lxde
should do the trick.
After that check the dropdown menu again.
Here is a complete guide on the different desktop choices on raspbian if you don’t like the appearance.
Also there might still be some still missing in that case feel free to say what you need and i will see if i know a packet.
(GUIDE: Raspbian Lite with RPD/LXDE/XFCE/MATE/i3/Openbox/X11 GUI - Raspberry Pi Forums)
As stated there the default dekstop environment is installed by
sudo apt-get install raspberrypi-ui-mods
i believe. But if you are ok with lxde then just use that.
I guess you could try the default with the above command and then uninstall if you don’t like it.
Yes, indeed! That for sure did the trick! Thank you, thank you, thank you:)
This is a significant plateau in my setting up of this system. (I’m constantly impressed at the power under the hood of this little board that’s thinner than a pack of king-size cigarettes!
Now that lxde is happily showing me the windows, with all the interesting things that implies, I find that the computer automatically logs itself on. I am 90% sure that in my desperation during weeks of no progress I must have set something for ‘auto-logon’. I am not sure that that is what I really want to do now.
BTW, now I can ‘Logout’ without rebooting. That brings up the login screen, which responds properly to the pi/password input (it logs me in!). Also, the little wrench in the title bar in the top of the login screen now produces three radio (‘option’?) buttons, instead of the original one, namely ‘Default Xsession’/LXDE/Openbox. Not sure what these do, but perhaps I’ll experiment.
Thanks for the link to the desktop choices on Raspbian. I have already printed it; it will make for some interesting bedtime reading
Any recommendations on further configuration of the GUI would be greatly appreciated.
Even better would be an evaluation of the overall system configuration I’ve proposed at various places in this thread. Being the newb, all of my choices were made naively. If there are limitations to what we’ve already decided to do, I don’t want to use such components as a foundation.
I’m perfectly willing to use putty/ssh to manage everything, if necessary. (If so, I’d need some kind of O’Reilly’s handbood to get me out of any rough spots.) We do both want to see graphical representations over the web, on any screen whether it’s desktop or a phone. And we both need to be able to get into the nuts and bolts of it and ‘program right down to the metal’, if that’s what’s necessary. If a GUI/VNC-based approach is going to be deficient, then we’d like your recommendations of how we need to set it up (especially now, since it’s in a warm room within arm’s reach, not on a cold, distant tower!)
I don’t think you are going to need more.
The local map of display is working isn’t it? What other graphical stuff do you want?
You can install the graphs from the adsb-receiver-project but be careful to only install the graphs.
Check this post: (Optimize Gain - which would you chose - #43 by abcd567)
And this post: (Optimize Gain - which would you chose - #75 by abcd567)
In the thread there is also much discussion of gain.
Which antenna / receiver setup will you be using?
You will want to be able to change gain that is easy enough via ssh and the command sudo piaware-config rtlsdr-gain 39
for example.
The port forward is mostly checking the configuration settings of the router and that depends how that thing is configured. Each device is different.
38123 forward to pi on port 22 (for ssh)
38180 forward to pi on port 80 (for http, the local SkyView)
You will want to check if the router supports dyndns otherwise you can setup a dyndns client on the Pi. (That gives the outward facing ip address of the router of your friend a name like a website has, let’s say it will be called douglas.my-ip.org)
Then you can ssh to douglas.my-ip.org on port 38123 and you will get a connection to the pi.
Visiting http://douglas.my-ip.org:38180/dump1090-fa/ will give you the local skyview.
Now most modern routers won’t normally change a dynamically assigned ip address so your pi will internally hopefully always get the same ip.
If that should not be the case you would need set a static IP, configure a gateway and dns servers but that can be done via piaware-config.
This is just an overview from the top of my head.
Upgrading to the next major revision of raspbian was a problem with the sd-card image last time.
I don’t think the same problem will appear again but still the piaware image is custom made for easy installation and configuration. In return there are some things you might not be able to configure like you want to.