@sdetweil
Luckily I had a slow week at work!
This seems to have worked:
sudo apt-get -y -o Dpkg::Options::=“–force-confdef” -o Dpkg::Options::=“–force-confnew” full-upgrade
I have brought my Pi5 home, and a couple of micro SDs so happy to test when I can. I do have a lot of driving chilren around to do but some time in between.
@sdetweil said in MMM-CalendarExt3 and MMM-MonthlyCalendar blank:
oninteractive’ apt full-upgrade -y
That did not seem to make any difference, I tried apt-get update and then DEBIAN_FRONTEND=‘noninteractive’ apt-get --assume-yes full-upgrade
but was still asked about the config file /labwc-greeter/autostart
On the plus side… It worked after answering Yes and MagicMirror started.
It did take an unusually long time intalling dependencies and again fixing sandbox permissions. I almost gave up but it did finish, and works
@sdetweil Bear with me, I have run it 3 times now and it seems to freeze / stop during the upgrade, I can’t see where in the upgrade process it is happening so I have modified the script to output to the treminal during the upgrade instead of the log after it has finished and running it locally on the Pi
Will post back later…
I am assuming the ugrade ran into a problem somewhere, I had left it for nearly an hour and progress hadn’t moved.
Update::
I think the issue is that despite having --assume-yes in the apt-get upgrade command it is still stopping and asking :
Configuration file '/etc/xdg/labwc-greeter/autostart'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** autostart (Y/I/N/O/D/Z) [default=N] ?
But there is no output to terminal so you can’t answer.
I didn’t do either, I just ran your script from first run on the OS on the first 2 cards. On the other 2 cards, on first run of the OS I entered
sudo apt update
sudo apt full-upgrade
bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh)"
The only difference between them is your script not updating the system. It may all just be a coincidence and someone else with same hardware verifying would be helpful.
Results from todays adventures writing Pi images to SD cards…
I don’t really know what, if any difference there could be but I flashed 4 SD cards with the same
64 bit Bookworm image.
2 of them, I just ran the install script and let it update the system. The other 2, I updated / upgraded first. 1 with apt full-upgrade and the other with apt upgrade and then ran the install script.
The first 2 stopped at the same point on the starting server message and the other 2 just worked.
When the system stops at the starting server message, CTRL-C doesn’t do anything so SIGINT is not being picked up.
It may well just be something peculiar to my setup or enviroment.
@sdetweil
I am sorry if this has been a wild goose chase and a waste of your time. I flashed the SD card, ran the script several times and it didn’t work, I will try one more time tomorrow and leave it at that.
Random results from repeating the same process are very frustrating.
I had one more attempt at this, this time I ran an update and upgrade before running your script and this time it worked. Cannot see why that would be…
Happy to experiment more if you need more info but I am going to start on building the 2 way mirror now!
@sdetweil OK, I will keep the various SD cards with working and non working version for a while just in case it would be of help.
So, it works installing manually, bash history…:
sudo apt update
sudo apt full-upgrade
sudo reboot now
curl -sL https://deb.nodesource.com/setup_20.x | sudo -E bash -
sudo apt-get install nodejs -y
sudo apt install npm
git clone https://github.com/MagicMirrorOrg/MagicMirror
cd MagicMirror
npm run install-mm
cp config/config.js.sample config/config.js
npm start
The install log from the one that doesn’t run is here if that helps at all.
