https://www.driveuconnect.com/support/software-update.html has the updates . . . except the downloads aren't there anymore and they expect you to use wifi, which it doesn't have I'm pretty sure.

Apparently the dealership attempt to fix it was by attempting to upgrade to version 21 of UConnect. They didn't even accomplish that.

Looking at the logs, I got the section name wrong. So I've changed it to:

... it's still OOM-killing the mariadb service

The conf got loaded on reboot, so in theory it's all good, but I should perhaps give it some more swap or RAM (and probably disk space?)

https://mariadb.com/kb/en/systemd/#configuring-the-systemd-service led me to doing this:

I suppose I should perhaps clean up the Nextcloud warnings first.

Currently:

Current version is 29.0.7.

Current status:

Current version is 28.0.10.

Yeah, Tekore 4.6.1 worked but earlier 5.x versions didn't, I mean cheers to that project for actually taking semantic versioning seriously?

Hmmmm the immediate problem was I didn't have the tekore module installed, but when I install it then I get another error:

The recurring OOM killing of the database server isn't the only issue, alas. As reported to me by Val in Discord, https://kloud.keithzg.ca/pymusicleague/spotify_track_availability.php isn't working right:

Got Nextcloud to 27.1.11, latest is 29.0.7 with 30 in release candidates.

ah, well

root@kloud:/var/www/owncloud# service mariadb status
× mariadb.service - MariaDB 10.6.18 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/mariadb.service.d
             └─migrated-from-my.cnf-settings.conf
     Active: failed (Result: oom-kill) since Mon 2024-09-16 00:30:11 UTC; 11min ago
       Docs: man:mariadbd(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 1044 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=killed, signal=KILL)
   Main PID: 1044 (code=killed, signal=KILL)
     Status: "Taking your SQL requests now..."
        CPU: 1min 9.381s

Current error:

https://www.nass.org/sites/default/files/reports/summary-ballot-access-laws-president-june-2024.pdf

Changing the clock to SYNC while having the CV sync out on the Beatstep going into the Liven . . . changes nothing. Nor does any other of the MIDI settings, as far as I can tell. Even setting the Liven to use internal sync results in silence once Play is pressed (unless it's held, and until rebooting the Liven).

Ohhhhh I was just skimming past the part with all the instructions for GUIs I wasn't using before and missed

amidi -p hw:1,0,0 -s Liven_8bit_Warps_v3.0.76_2023-09-15.syx -i 60just sits there, and the unit doesn't react at all. I tried both from booted normally, and booting while holding PTN to get to the menu that lists the firmware info.

Like https://gearspace.com/board/electronic-music-instruments-and-electronic-music-production/1378662-sonicware-liven-xfm-sync-issues.html but I can add the following odd details:

Maybe configure with --no-ytk? Well that failed on missing gtkmm, lets install that via too then.

Trying to install the deps with:

sudo port install aubio automake boost cairomm cmake curl fftw flex freetype gettext glibmm gnome-doc-utils harfbuzz itstool libarchive libiconv libogg libsamplerate libsndfile libusb libwebsockets libxslt liblrdf pango pkgconfig pcre raptor2 redland serd sratom tiff xz autoconf bison cairo cppunit expat flac fontconfig fribidi glib2 gnome-common gobject-introspection intltool jpeg libffi liblo libpng libsigcxx2 libtool libvorbis libxml2 lilv lv2 m4 nss libopus pangomm libpixman rasqal readline rubberband sord taglib zlib

Repairing has seemed to work since, though it didn't the first time I had tried it (there were also GadgetBridge updates though)