apt-upgrade rpi-connect failure

[rkawala]

I'm seeing an error during the customize phase that I've never seen before. I'm not even sure it's a problem in SDM; perhaps it's a problem with rpi-connect. Have a look at line 773 in the attached log. I'm running Wayland, as you would expect, so I'm not sure why it's blathering about $DISPLAY and X11. Any idea what I ought to do about this?

sdm-citadel-customize-script.txt

[rkawala]

I think this won't matter, because I'll likely be removing rpi-connect anyway. It might mean there's a deeper problem, so I'll leave it open for now, but it's probably a red herring. Because there's so much that's changed, I'm on high alert.

[gitbls]

Looks like rpi-connect install needs to happen on a booted system. I haven't looked at it yet, was waiting for them to get a bit farther down the development path with it.

Best way to install it is to do a runatboot that does the apt install.

[rkawala]

Should I close this? It's a problem in rpi-connect, not SDM.

[gitbls]

Depends on where you want it fixed. There's a hack-around I mentioned above that could be done in the sdm docs somewhere. Or, if enough other people ask and you stop bugging me with stuff that's more fun to work on 🤣 it wouldn't be too difficult to whip up an rpi-connect plugin that at least did the basic installation.

[rkawala]

Please don't worry about rpi-connect on my account. Once I figured out that it wasn't a problem which V15.0 had somehow introduced, I immediately lost interest. Unless you think other users will be upset by it, you should just ignore it.

I was thinking maybe there ought to be a document called "Error Messages You Can Ignore." Like the cryptsetup errors I always see in the customize phase. Something about resolving /dev/loop1p2 and /dev/zram0; whatever is being complained about doesn't seem to matter.