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…
@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 So it does, not sure why, I copied it from the terminal window.
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
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.