MMM-CalendarExt3 and MMM-MonthlyCalendar blank

[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

[Scott-M]

@sdetweil So it does, not sure why, I copied it from the terminal window.

[sdetweil]

@Scott-M said in MMM-CalendarExt3 and MMM-MonthlyCalendar blank:

So it does, not sure why, I copied it from the terminal window.

the MagicMirror forums assume word processing for quotes unless in a code block

once you save it, poof… it will never change back automatically
so it looks like you decided to add the code black later… (just experience )

[sdetweil]

@Scott-M note this latest fix also changes MagicMirror.sh to detect which window manager is running (wayland or labwc) and use the different start command if detected

[Scott-M]

@sdetweil
I probably did add the code block after. Lesson learned! And this is partly why I am having more issues with this. It has been very frustating, after it worked last night, it isn’t now.

I think I know what the issue is but it is time consuming writing the SD image and running the script so if you can bear with me. I want to test it at least twice before I update here.

I suspect the 2 dashes before

--force-confdef
--force-confnew

have been replaced by a single dash of a different character type. Again, because I put the code block around the text after I copied it.

This should be the correct code but let me test again to make sure. It has worked once, just want to do it again and will update.

sudo apt-get -y -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confnew" full-upgrade

In the mean time, the above code will auto select the default option if one is available and then answer Yes if there is no default. In the case of the prompt that was appearing, the old configuration file ‘/etc/xdg/labwc-greeter/autostart’ is kept. If you want the package maintainers file instead just remove the first option:

-o Dpkg::Options::="--force-confdef"

[sdetweil]

@Scott-M yes the double dash was replaced with single… new update pushed…

[Scott-M]

@sdetweil

It seemed to get through the upgrade stage very quickly and

apt-get upgrade  started
apt-get upgrade result =rc=0 Reading package lists...
Building dependency tree...

in the log seems to show the upgrade didn’t work. I will run the script locally on the pi and send the output to the termnial to see what is happening but it won’t be tonight, I have to go out now.

Update tomorrow…