I have the standard SD card image install of PiAware on my RasPi and so far have been using terminal commands through SSH and PuTTY.
Is it possible to install the PIXEL GUI desktop environment on the RasPi and then use that desktop environment though Xrdp?
The command line utility works fine for common commands like sudo apt-get update and sudo apt-get upgrade, but it would be nice to have a full desktop environment to use on the Pi as well. Please advise, thank you.
An alternative way to do this is to install standard Raspbian and install PiAware as a package install instead of using the SD card image. Raspbian comes with a free VNC license courtesy of RealVNC.
You simply enable VNC Server in Raspbian and log in to your RealVNC account with it. You can then use VNC Viewer to access your Pi desktop from anywhere. It doesnât even need ports opening so is great for remote access behind a NAT router. RealVNCâs Viewer also has an iOS and Android app and the way theyâve designed the UI is quite clever; theyâve done a great job of making remote desktop control from a mobile device pretty painless.
Thanks for the info. That setup sounds very enticing, especially the easy to use mobile app.
However, I really have no need to manage my Pi from anywhere but home, so connecting to the desktop from my home PC would be plenty sufficient.
Iâm still hoping for a solution that allows the use of a GUI desktop with the SD card image.
This short video shows the basic of what is possible as long as a GUI desktop can be installed first: Remote Desktop from Windows 10 to Raspberry Pi 3 - YouTube
https://www.raspberrypi.org/forums/viewtopic.php?t=166806
This came up first when I googled âRPI install pixel desktopâ
You can install rdp too or use VNC.
It works!
If anyone else is interested in using the standard Raspbian desktop you need to install:
sudo apt-get install --no-install-recommends xserver-xorg xinit
sudo apt-get install raspberrypi-ui-mods
sudo apt-get install lightdm
sudo apt-get install xrdp
Then itâs as simple as opening the Remote Desktop Connection app on your Windows machine, entering the local IP of you Pi, and logging into Xrdp with the standard Pi and password (âflightawareâ by default). Then youâre taken to your Raspbian desktop environment.
I was trying to accomplish what the OP was looking for (and perhaps using VNC as well), so I started with what is laid out in the final post (4 âsudoâ steps), and I do not have success. I tried RDC and I get to the XRDP login page. I entered my Pi user/pass, and it just closes the XRDP login window and takes me back to the RDC page (âwhere do I want to login to?â)
Whatâs suggested here jibes with what Iâve seen elsewhere (suggestions for âupgradingâ Raspian-Lite to Full to get a desktop), but for some reason itâs not working for me, and I donât see why not.
Iâve been trying a number of approaches, and am starting to think maybe I need to just start from scratch, install full Raspian and then PiAware on top of that, instead of starting with PiAware (raspian-lite) and trying to add a desktop.
Has anyone else had issues? Have others started with Full Raspian? At this point if I do that, will I be able to reconnect to my existing PiAware identifier, or will I end up with a ânewâ radar installation?
Thanks.
Many have started with Full Raspbian (Raspberry Pi OS with Desktop)
Yes, you will be able to reconnect to your existing Piaware identifier
Please brows following thread
Scroll down to::
STEP-2: Write image to microSD Card
NOTE: Following item of OPTION-2 [Package Install] is outdated:
6.2 - Configure dump1090-fa & dump978-fa to use dongles of assigned serial numbers
Instead, use following commands:
sudo sed -i 's/^RECEIVER_SERIAL=.*/RECEIVER_SERIAL=00001090/' /etc/default/dump1090-fa
sudo sed -i 's/driver=rtlsdr[^ ]* /driver=rtlsdr,serial=00000978 /' /etc/default/dump978-fa
sudo raspi-config
Alternative guide starting from Raspbian: https://github.com/wiedehopf/adsb-wiki/wiki/Raspbian-Lite:-ADS-B-receiver
Thanks again for the spot-on help.
I installed a clean (full) version of Raspbian (Bullseye), got it working with RealVNC, and then installed PiAware and FR24. I hit just a couple minor hiccups - the biggest being that following the instructions here in [Section 2.1.3.1 Option 1]:
https://repo-feed.flightradar24.com/fr24feed-manual.pdf
and duplicated here in [Step 3.2.4]:
https://discussions.flightaware.com/t/re-imaging-made-easy/72347
didnât work - I got a bunch of errors, and at the end
sudo systemctl restart fr24feed
wouldnât work - âfr24feedâ was unknown.
However taking Option 2 from the manual (and then your advice given here:
https://forum.flightradar24.com/forum/radar-forums/flightradar24-feeding-data-to-flightradar24/10903-how-to-feed-data-to-multiple-sites-a-brief-guide?p=214568#post214568 )
seemed to get it working.
The remaining âweirdnessâ is that now that itâs running and feeding FA and FR24, VNC has stopped working (?). I had connected with VNC prior to all the work on getting the various services running, but now when I try to connect, it accepts my login, thinks for a moment, flashes a black screen saying âCannot currently show the desktopâ, and then dumps me back to the âlogin screenâ. Odd.
This is exactly the behavior I had with the [originally headless] Pi installation I tried to add a desktop to.
I wondered if I stopped the relevant services (piaware, fr24feeder, dump1090-fa) maybe VNC would work again, but that didnât seem to matter.
I guess Iâll take another run at it - starting with Raspbian (with VNC working) and watching more carefully as a add the various parts to the ADS-B monitoring to it.
âMark
Really weird. Yesterday, to verify that my how-to is up to date, on my RPi Model 4, I wrote Raspberry Pi OS Bullseye (64bit) and did exactly as you did, and my VNC never stopped. However there are two differences
(1) My OS is 64-bit, I donât know if yours is 32-bit or 64-bit. However this difference should NOT create the problems you have faced.
(2) I could get FR24 feeder installed by following bash script in the first attempt:
sudo bash -c "$(wget -O - http://repo.feed.flightradar24.com/install_fr24_rpi.sh)"
@abcd567 I installed 32-bit Raspbian (not 64) as I wasnât sure if all the FA/FR24 stuff was compatible with a 64bit OS.
I recreated my install âone step at a timeâ and checked as it went.
I loaded the OS (32-bit Bullseye) and confirmed that VNC is working,
I loaded PiAware, confirmed that itâs working (sending data to FA) and that VNC is working.
My next step was to activate FR24 per (Re-imaging Made Easy) Section 3.2
I created the fr24feed.ini file and populated it with the previous data, and then executed:
sudo bash -c "$(wget -O - https://repo-feed.flightradar24.com/install_fr24_rpi.sh)"
and what I get back finishes likeâŚ
Hit:1 http://flightaware.com/adsb/piaware/files/packages bullseye InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
dirmngr is already the newest version (2.2.27-2+deb11u2).
The following package was automatically installed and is no longer required:
libfuse2
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.WqM7tDuxwc/gpg.1.sh --recv-key --keyserver keyserver.ubuntu.com C969F07840C430F5
gpg: keyserver receive failed: Server indicated a failure
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.XADxvxJvr5/gpg.1.sh --recv-key --keyserver pool.sks-keyservers.net C969F07840C430F5
gpg: keyserver receive failed: Server indicated a failure
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.17F6gLHavv/gpg.1.sh --recv-key --keyserver pgp.mit.edu C969F07840C430F5
gpg: keyserver receive failed: Server indicated a failure
pi@PiPlane:~ $
multiple âfailuresâ and then it stops.
The steps on the above-linked webpage, state that the command should keep running and start the configuration process. Then I should end that process via (Ctrl+C), and start up the fr24feed via:
sudo systemctl restart fr24feed
However, I never get a chance to Ctrl+C, it just dies. If I try to start the process, I get back:
pi@PiPlane:~ $ sudo systemctl restart fr24feed
Failed to restart fr24feed.service: Unit fr24feed.service not found.
At this point VNC is still working.
Then I did âoption 2â from the Fr24 manual:
wget https://repo-feed.flightradar24.com/rpi_binaries/fr24feed_1.0.23-8_armhf.deb
sudo dpkg -i fr24feed_1.0.23-8_armhf.deb
sudo systemctl restart fr24feed
and it seemed to work - including asking if I wanted to keep the existing config file.
I rebooted, and now it seems to be working - both FA, FR24, and VNC (?)
So - VNC is working now - when (I think) it wasnât working on the identical effort yesterday. 
I am not going to try a third time, though, Iâm taking âsuccessâ and running with it.
But as to getting FR24 functional, I again confirmed that the âOption 1â approach doesnât work for me. Iâm not sure if thatâs due to the 32/64 bit question, maybe a Buster/Bullseye issue, or something else. The fact others havenât complained makes me wonder whatâs wrong with my setup, but Iâve made copious notes to myself so that if/when I have to do this again, Iâll have a recipe for getting to the end.
Again, I greatly appreciate all the time and attention youâve provided here (and in other threads in the various forums FA and FR24 that Iâve been reading).
Regards,
âMark
This is problem with FR24 key server. This problem often occurs with FR24 and RB24 key servers. The workaround is to use command starting with wget to directly download the package and install the downloaded package by command starting with sudo dpkg -i
This is old version (1.0.23-8) of FR24 feeder. Latest version is (1.0.29-10). You can upgrade it by following commands
wget https://repo-feed.flightradar24.com/rpi_binaries/fr24feed_1.0.29-10_armhf.deb
sudo dpkg -i fr24feed_1.0.29-10_armhf.deb
The 64-bit version of Raspberry Pi OS is by default multi-arch, (i.e. arm64 & armhf). It therefore by default supports both 64-bit & 32-bit packages of feeders and decoders.
The 32-bit official packages of Piaware, dump1090-fa, dump978-fa are available for installation from Flightaware site https://flightaware.com/adsb/piaware/install
I have built and uploaded to my Github site, the 64-bit packages of Piaware, dump1090-fa, dump978-fa, and piaware-web. If anyone wants to install 64-bit packages on 64-bit Raspberry Pi OS Bullseye, he can follow procedure here:
https://github.com/abcd567a/rpi/blob/master/README.md
Â
Â
Â
Â
Here is this morningâs weirdness (because it wouldnât be right to start the day without something going wrongâŚ)
I checked my PiAware feed, and it was working. I checked VNC and it would connect. I moved some stuff on my desk (where the Pi is currently sitting - with a coax snaked out a window) and bumped the Pi hard enough I dislodged the RTL-SDR dongle from the USB port. No problem, I plugged it back in - evidently to the wrong/different USB port, because I suddenly got âProblem Fetching data from dump1090â error on my PiAware feed page. OK, I think - I must have plugged into the wrong port, Iâll just reboot and that will fix things.
The reboot did indeed fix the dump1090 issue (the Pi just started looking out the new port), but - VNC has now stopped working (!?) Iâm getting the same behavior I had on the previous attempt at doing this install - namely VNC-Viewer asks for a password (and tells me if itâs wrong - so it is authenticating), flashes a black screen with âCannot currently show the desktopâ message, and then drops back to the login page. I rebooted a couple more times to see if VNC would revert back to working, and it hasnât. I rebooted multiple times yesterday and VNC stuck around every time - it was just this morningâs reboot that somehow messed things up.
Iâm really at a loss here - I guess I donât really need VNC (at least not at the moment - every thing else is working), but âWTH?â how does reboot ân+1â suddenly break functionality? Given the login does seem to be authenticating (it lets me try to login and knows if the provided password is correct) I would suspect VNC server is running on the Pi - and the problem is the desktop isnât. However, I have no idea how to debug that.
I did flash an image of my SDCard yesterday after I got PiAware running (but before installing FR24), so I think I will go back to that, install FR24 (the newer version - thanks @abcd567) and see if I get back VNC. At that point I still wonât know what âbrokeâ it this morning I guess, but Iâll keep an eye on it, and try to sort what I am doing that causes the desktop to stop.
It is really weird.
Just to test yout senario, I have now rebooted my Pi a large number of times. My VNC & GUI on 64-bit Full OS works OK even after all the reboots.
I am planning to re-image my microSD card with 32-bit Raspberry Pi OS Bullsrye with desktop and install piaware dump1090 and fr24feed to recreate your sensrio to find if the issue is a bug in 32-bit Raspberry Pi OS.
EDIT:
@SDMark
Which is the model of your Pi?
(I am using RPi Model 4)
I started on a RPi4 - original attempt to get this all to work (started with PiAware and then tried to upgrade the Lite to Full - adding a desktop).
Iâm now debugging on a RPi3B+ where I started with fresh install of Raspbian and then added PiAware. This was the setup where I was running VNC for a while - until it stopped.
Morning work:
From the /var/log/messages file - just after a rejected VNC connection attempt:
Aug 4 10:22:00 PiPlane lightdm[2713]: 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
Aug 4 10:22:01 PiPlane lightdm[2961]: 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
Aug 4 10:22:05 PiPlane vncserver-x11[529,root]: ConsoleDisplay: Found running X server (pid=2943, binary=/usr/lib/xorg/Xorg)
so âorg.freedesktop.Accountsâ is the problem?
A google search found this link:
https://bbs.archlinux.org/viewtopic.php?id=186550
which seems to address a similar (same?) topic, but Iâm not sure how to interpret this - itâs above my knowledge level (but Iâm trying to learnâŚ)
I feel problem is OS image.
With Raspberry Pi Imager, easy way is to choose from images presented by the imager. However I found this often gives error during writing, or during first boot, or after first boot.
I therefore as a first step downloaded myself the image to my computer from this page:
https://www.raspberrypi.com/software/operating-systems/
Direct download link
https://downloads.raspberrypi.org/raspios_armhf/images/raspios_armhf-2022-04-07/2022-04-04-raspios-bullseye-armhf.img.xz
Â
Then on RPi Imager tool, under âCHOOSE OSâ scrolled down to âUse Customâ, clicked it
Â
Selected the image I have downloaded from Raspberry Piâs Software page.
Â
Thanks - I will try that now. In the meantime, I flashed a new copy of my âafter PiAware / VNC workingâ image, and once again installed FR24feed. Again, VNC worked - briefly - but then stopped after âone reboot too manyâ.
Per another suggestion I had gotten, I checked in the /var/log/messages file - and looked at what happened after each reboot.
The first block shows what startup looks like for a reboot where VNC is working. I copied from just before vncserver is first referenced (started?) to the point the VNC session was started and ended (successfully). I trimmed out a big chunk where the Bluetooth was activated.
The second block is the same snip, but from the next reboot where VNC wasnât working (again Bluetooth removed).
There are two sets of âdifferent log reportsâ (annotated with #### ) the first is a couple lines related to rsyslogd - I suspect this is unrelated, although itâs curious thereâs a difference.
The second block of âextraâ stuff, seems pertinent.
I had assumed the error associated with org.freedesktop.Accounts was the culprit, but I see that error in each run - including the reboot where VNC worked.
However in the failed run, the second block of extras includes a second instance of that error, and then a bunch of stuff related to âpulseaudioâ (??)
The end of the second block - where the VNC session attempt fails - also has a reference to pulseaudio. Might it be that my speaker-less Pi is choking on some audio setting that could simply turn off?
WORKED AFTER REBOOT
Aug 4 10:57:26 PiPlane kernel: [ 11.221656] uart-pl011 3f201000.serial: no DMA platform data
Aug 4 10:57:26 PiPlane kernel: [ 11.292000] 8021q: 802.1Q VLAN Support v1.8
Aug 4 10:57:26 PiPlane kernel: [ 11.394820] Adding 102396k swap on /var/swap. Priority:-2 extents:2 across:176124k SSFS
Aug 4 10:57:26 PiPlane udisksd[387]: udisks daemon version 2.9.2 starting
Aug 4 10:57:27 PiPlane udisksd[387]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Aug 4 10:57:27 PiPlane kernel: [ 11.992574] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
Aug 4 10:57:27 PiPlane lightdm[514]: 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
Aug 4 10:57:27 PiPlane udisksd[387]: Failed to load the 'mdraid' libblockdev plugin
Aug 4 10:57:27 PiPlane kernel: [ 12.576000] 8021q: adding VLAN 0 to HW filter on device eth0
Aug 4 10:57:28 PiPlane udisksd[387]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Aug 4 10:57:28 PiPlane vncserver-x11[531,root]: ServerManager: Server started
Aug 4 10:57:29 PiPlane vncserver-x11[531,root]: ConsoleDisplay: Found running X server (pid=555, binary=/usr/lib/xorg/Xorg)
Aug 4 10:57:31 PiPlane lightdm[658]: 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
Aug 4 10:57:33 PiPlane kernel: [ 18.367468] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Aug 4 10:57:35 PiPlane kernel: [ 20.144923] Bluetooth: Core ver 2.22
...
Bluetooth removed
...
Aug 4 10:57:36 PiPlane kernel: [ 21.070069] Bluetooth: RFCOMM ver 1.11
Aug 4 10:58:00 PiPlane kernel: [ 33.110838] cam-dummy-reg: disabling
Aug 4 10:58:09 PiPlane vncserver-x11[531,root]: Connections: connected: 192.168.1.140::54907 (TCP)
Aug 4 10:58:09 PiPlane vncserver-x11[531,root]: Connections: authenticated: 192.168.1.140::54907 (TCP), as pi (d permissions)
Aug 4 10:58:13 PiPlane vncserver-x11[531,root]: Connections: disconnected: 192.168.1.140::54907 (TCP) ([ViewerClosed] VNC Viewer closed)
FAILED AFTER REBOOT
Aug 4 11:58:51 PiPlane kernel: [ 11.127898] uart-pl011 3f201000.serial: no DMA platform data
Aug 4 11:58:51 PiPlane kernel: [ 11.201965] 8021q: 802.1Q VLAN Support v1.8
Aug 4 11:58:51 PiPlane kernel: [ 11.281163] Adding 102396k swap on /var/swap. Priority:-2 extents:2 across:176124k SSFS
#### Aug 4 11:58:51 PiPlane rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.2102.0]
#### Aug 4 11:58:51 PiPlane rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="382" x-info="https://www.rsyslog.com"] start
Aug 4 11:58:51 PiPlane udisksd[402]: udisks daemon version 2.9.2 starting
Aug 4 11:58:52 PiPlane kernel: [ 11.908172] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
Aug 4 11:58:52 PiPlane lightdm[516]: 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
Aug 4 11:58:52 PiPlane udisksd[402]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Aug 4 11:58:52 PiPlane kernel: [ 12.497580] 8021q: adding VLAN 0 to HW filter on device eth0
Aug 4 11:58:53 PiPlane udisksd[402]: Failed to load the 'mdraid' libblockdev plugin
Aug 4 11:58:53 PiPlane udisksd[402]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Aug 4 11:58:53 PiPlane vncserver-x11[526,root]: ServerManager: Server started
Aug 4 11:58:54 PiPlane vncserver-x11[526,root]: ConsoleDisplay: Found running X server (pid=551, binary=/usr/lib/xorg/Xorg)
Aug 4 11:58:56 PiPlane lightdm[654]: 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
Aug 4 11:58:58 PiPlane kernel: [ 18.256238] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
#### Aug 4 11:58:58 PiPlane lightdm[758]: 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
#### Aug 4 11:58:59 PiPlane vncserver-x11[526,root]: ConsoleDisplay: Found running X server (pid=730, binary=/usr/lib/xorg/Xorg)
#### Aug 4 11:58:59 PiPlane pulseaudio[782]: Failed to open cookie file '/var/lib/lightdm/.config/pulse/cookie': No such file or directory
#### Aug 4 11:58:59 PiPlane pulseaudio[782]: Failed to load authentication key '/var/lib/lightdm/.config/pulse/cookie': No such file or directory
#### Aug 4 11:58:59 PiPlane pulseaudio[782]: Failed to open cookie file '/var/lib/lightdm/.pulse-cookie': No such file or directory
#### Aug 4 11:58:59 PiPlane pulseaudio[782]: Failed to load authentication key '/var/lib/lightdm/.pulse-cookie': No such file or directory
Aug 4 11:59:00 PiPlane kernel: [ 19.908007] Bluetooth: Core ver 2.22
...
Bluetooth removed
...
Aug 4 11:59:00 PiPlane kernel: [ 20.514322] Bluetooth: RFCOMM ver 1.11
Aug 4 11:59:24 PiPlane kernel: [ 33.110720] cam-dummy-reg: disabling
Aug 4 12:00:37 PiPlane vncserver-x11[526,root]: Connections: connected: 192.168.1.140::57270 (TCP)
Aug 4 12:00:37 PiPlane vncserver-x11[526,root]: Connections: authenticated: 192.168.1.140::57270 (TCP), as pi (d permissions)
#### Aug 4 12:00:53 PiPlane lightdm[1130]: 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
#### Aug 4 12:00:53 PiPlane lightdm[516]: g_dbus_connection_call_sync_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
#### Aug 4 12:00:53 PiPlane pulseaudio[782]: After module unload, module 'module-null-sink' was still loaded!
#### Aug 4 12:00:54 PiPlane lightdm[1193]: 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
#### Aug 4 12:00:55 PiPlane vncserver-x11[526,root]: ConsoleDisplay: Found running X server (pid=1175, binary=/usr/lib/xorg/Xorg)
@abcd567 I have sorted what is causing the problem now, although I donât understand why itâs causing a problem - but I suspect thatâs simply due to ignorance on my part.
I created a handful of aliases that I wanted to run:
alias temp='sudo /usr/bin/vcgencmd measure_temp'
alias rm='rm -i'
alias fastat='sudo piaware-status'
alias 1090stat='systemctl status dump1090*'
alias frstat='sudo fr24feed-status'
and originally I put them in ~/.bashrc
However, I had been given some advice (by a Linux user) that I shouldnât be running as âpiâ and instead I should create a new user account to generally operate out of. When I did that, I thought âif Iâm creating new user profiles, how do I mirror the aliases (etc.) when they get made - so I donât have to manually update multiple ~/.bashrc files every time I want a new alias?â I looked on the web and found a suggestion to
a) put the aliases in /etc/bash.bashrc
b) add a snip in /etc/profile
#
# check and read global /etc/bash.bashrc
#
if [ -f /etc/bash.bashrc ]; then
. /etc/bash.bashrc
fi
#
That would run the /etc/bash.bashrc file every reboot.
The issue seems to be that if that code is in /etc/profile - regardless of whether the aliases are in /etc/bash.bashrc or not - I get the desktop error.
I discovered this from starting with the downloaded image (as you suggested) and adding the aliases as the âfirst stepâ and found it broke even before any of PiAware or FR24feed was added. I presume that previously I was adding stuff âa piece at a timeâ and eventually once it was running, I went and added my aliases. I would source /etc/bash.bashrc to activate the aliases - and this doesnât break things - they wouldnât break until the next reboot when /etc/profile ran /etc/bash.bashrc at startup.
I do not understand what/why - but it would appear that thereâs something in /etc/bash.bashrc that is hosing the process here (but only on startup); I donât know what that is. Evidently /etc/bash.bashrc is not executed normally - just ~/.bashrc - so the solution is to move the aliases to ~/.bashrc . When I do so, even installations that were formerly working - then broken - are back to working again.
Iâll either have to figure some other solution for âglobal/generic aliasesâ, or else just stick with âpiâ as the user and not worry about adding more.
I greatly apologize for the time of yours I wasted on this goose chase - and appreciate the effort you put in to help. Your instincts seemed to have been correct - it was an OS issue; just a problem I unwittingly created.
This seems to be the easiest and trouble-free policy.