And yet more adventures… and scorched earth…
OK - everything was running nicely… was able to build Sayonara from source code, and it sorta worked (tried it on a FLAC album and it sounded awful)… few niggles (didn’t seem to support using filesystem folders as music library, insisted on building a media library - which I hate - the only MEDIA database I want is the directory tree on my computer!).
So mostly all good… tried mpg123 and it worked just fine on mp3… tried ogg123 on a FLAC file and same result as Sayonara, so it’s not Sayonara… it’s something else…
Decided to take a look at omxplayer after reading about it on some Pi forums… seems there’s a bunch of stuff it needs (armhf stuff)…
So - by a process of elimination - its dependancies were :
libavcodec58:armhf libavformat58:armhf libraspberrypi0:armhf libssh-gcrypt-4:armhf libraspberrypi0:armhf libgssapi-krb5-2:armhf libkrb5-3:armhf libssl1.1:armhf
So I installed them - meanwhile, I’m trying to hook up a 2nd monitor with either HDMI > DVI or HDMI > VGA, and it’s not working…
I’m doing the omx + dependancies install on a remote session in a terminal window, and I’m looking across at it after I’d submitted :
`
sudo apt install libavcodec58:armhf libavformat58:armhf libraspberrypi0:armhf libssh-gcrypt-4:armhf libraspberrypi0:armhf libgssapi-krb5-2:armhf libkrb5-3:armhf libssl1.1:armhf
And what do I see? I can see it’s REMOVING a bunch of arm64 packages including ALL of xfce4!!!
WTF?
I look at the HDMI screen of the Pi4? It’s blank… I pull the plug on everything… Pi4 boots into TTY… hardly anything there…
PEZZO DI MERDA!
How can :
> sudo apt install libavcodec58:armhf libavformat58:armhf libraspberrypi0:armhf libssh-gcrypt-4:armhf libraspberrypi0:armhf libgssapi-krb5-2:armhf libkrb5-3:armhf libssl1.1:armhf
Become :
> sudo apt remove xfce*[:arm64]
???
Did it somehow interpret my installation of a bunch of [package]:armhf stuff mean I wanted to replace ALL of arm64 with armhf?
Who knows?
Currently restoring my somewhat “vanilla” RaspbiOS (i.e. no GUI or anything) backup onto the SD card… Not worth the trouble of trying to repair the damage - easier to start again. This could take hours :
xzcat mimas-bkup.img.xz| sudo dd bs=4M of=/dev/mmcblk0
the img.xz file is 800 MB, but the compressed image inside is 59 GB…
I suspect: