MMM-CalendarExt3 and MMM-MonthlyCalendar blank

[sdetweil]

@Scott-M thanks… appreciate that

[Scott-M]

@sdetweil

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]

@Scott-M and my script does that before too, its in the install.log file

[Scott-M]

@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.

[sdetweil]

@Scott-M frustrating indeed

but its normal

[Scott-M]

@sdetweil

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]

@Scott-M great feedback… I have family stuff most of the day today…

did you do npm install or npm run install-mm

npm run install-mm is more like what I do in the script… which limits what things npm does…

npm install does everything possible

[Scott-M]

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.

[sdetweil]

@Scott-M ah… ok, I don’t do full-upgrade… only upgrade

Use apt upgrade for routine updates when you don't want to risk removing packages. 
Use apt full-upgrade when you need to ensure that all packages are up-to-date, even if it means removing some packages. 
Be cautious when using apt full-upgrade as it can potentially remove packages that you might need. 

but it seems that full-upgrade handles some dependencies NOT handled by upgrade, which seems like a bug to me… whats the point of upgrade if dependencies aren’t handled…

[sdetweil]

@Scott-M if you have a hankering to run another test, run the script from the test branch for next release… it will still get 2.30 , this does full-upgrade

bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/v231/raspberry.sh)”

[Scott-M]

@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.

[sdetweil]

@Scott-M that lovely problem again… thanks

[Scott-M]

@sdetweil

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]

@Scott-M yes, how to avoid the prompt and handle it some other time

searching leads to adding this in front of the apt full-upgrade command
DEBIAN_FRONTEND=‘noninteractive’

like this

DEBIAN_FRONTEND=‘noninteractive’ apt full-upgrade -y

[Scott-M]

@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

[sdetweil]

@Scott-M thanks… SO much fun…

I am trying to test on my pi5 , I am remote from my home office, and do not have my hdmi/micro adapter… so am trying headless…

pi imager, set ssh on, use pw authentication,
pi boots, ssh is on, but password doesn’t work…

using mac and ubuntu vm , and windows vm…

also of interest is that the wifi connection also does not work , only ethernet

[Scott-M]

@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]

@Scott-M thank you very much

ok, I’ve updated raspberry.sh on the v231 branch
let me know what you find when u can

[Scott-M]

@sdetweil

These seems to be a subtle difference between our keyboard layouts perhaps,

raspberry.sh has this line

upgrade_result=$(sudo apt-get -y  -o Dpkg::Options::=“–force-confdef” -o Dpkg::Options::=“–force-confnew” full-upgrade | pv -l -p)

but the quotes around –force-confdef and –force-confnew are the wrong type . Should be:

upgrade_result=$(sudo apt-get -y  -o Dpkg::Options::="–force-confdef" -o Dpkg::Options::="–force-confnew" full-upgrade | pv -l -p)

It causes this error:

dpkg: error: need an action option

Type dpkg --help for help about installing and deinstalling packages [*];
Use 'apt' or 'aptitude' for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;

Options marked [*] produce a lot of output - pipe it through 'less' or 'more' !
E: Sub-process dpkg --set-selections returned an error code (2)
E: Couldn't record the approved state changes as dpkg selection states

Maybe just replace the quotes rather than copy and pase. I noticed the same thing when I copied the link you sent previously for the test branch.

[sdetweil]

@Scott-M I copied directly from your original post, it also shows the curved quotes

pushed fix