i know that kup is pre-installed in kdelinux, & integrated into systemsettingsin a helpful way. this is good.
unfortunately kup lacks some features present in kbackup; in my non-kdelinux plasma installations i like to use kbackup for that reason. yesterday i realised there is no flatpak for kbackup, so i’ve been wondering if i have any alternative options to install kb another way
in older versions of kdelinux i was able to create multiple distroboxes as a nice way to obtain non-preinstalled non-flatpak apps, but my attempts to create a db recently failed with errors i don’t understand [atm i am posting in my archlinux plasma system, but if seeing such errors might be pertinent here i can reboot into kdelinux later; fwiw i had assumed such outcome related to discussion i’d read elsewhere about the Devs looking to something other than DB for this purpose].
The problem is that it’s not on Flathub. But that’s okay; Flatpak supports multiple repos. So you can add the nightly build repo and then install it from there! Just download https://cdn.kde.org/flatpak/kbackup-nightly/kbackup-nightly.flatpakrepo, open it in Discover, and then you can install KBackup from Discover (possibly after restarting the app).
…Or you could, if the nightly build repo was published at Index of /flatpak . The fact that it isn’t seems like an oversight to me.
before addressing specifics of your reply, as an important overall remark for context fyi… i am not a coder, not a Dev, have no IT background, regard myself merely as an enthusiastic but largely clueless & hamfisted Linux user rather than someone with actual knowledge & skills to do stuff.
so, with that in mind…
i looked at your linked example, & don’t really understand what i’m seeing, other than in the broadest of terms i realise it’s the way people organise for project changes to occur. i have no idea of any of the underlying processes, other than they exist. i’m sorry to be such a numpty.
as for the specifics of your initially exciting info about a putative nightly flatpak version of kbackup… as i read it i’m afraid i lost the plot. initially it seemed that yes i could do it, but then it seemed you were saying no i couldn’t because so far nobody has done the actions you mentioned. confused, i saved that link to my Downloads directory, right-clicked it, chose the top option in Dolphin to open it in Discover, but that only produced this error in Dolphin: Could not open file:///home/me/Downloads/kbackup-nightly.flatpakrepo … so i assume i entirely misunderstood the process & did the wrong thing. then i wondered if i might add this as a new repo, manually, by clicking the Add source button in Discover’s Settings, & pasting in the name of that downloaded file. alas that did not go well either:
thank you very much all the same, i appreciate you helping me.
PS: about 90’ ago i downloaded the latest kde-linux build, but have not yet rebooted, which i’ll do now. afterwards, i’ll retry those two actions, in case the new build helps.
oh good, today’s attempt to create an archlinuxdistroboxsucceeded [now a later kdelinux build than my earlier attempt], & so i was able to install kbackup in it then export it to my plasma apps menu… so now by hook or by crook, i have it – ha!
well that was disappointing. the latest build202605280254is broken; after entering my LUKS password, it then dumps me to the rescue screen. i had to boot back into my build of a few days ago [the 24th, iirc]. consequently, now retrying the Discover process per preceding post, only produced the same failure.
For me the 202605280254 build is fine. From your earlier post, it sounds like there might have been some weirdness where the image failed fo fully install for you?
oh wow, now i’m confused, coz i did the reboot twice, & both times it happened as i described… all good until after i’d entered my LUKS password. do you also use encryption? if not, maybe that’s the difference in our UX for that build. otoh, if you also have your partition/s encrypted, then… i don’t know how to explain the difference.should i simply wait another halfday or whatever for a new build, & try again then?
you might possibly recall my first post here, kde-linux_202605210254.raw does not update. , with which you kindly helped me. sadly the original problem has never gone away… there has not been a single time i have run updatectl check or updatectl update that has succeeded; they always error per my OP in that thread. each time since then, i have had to use the command you showed me, run0 /usr/lib/systemd/systemd-sysupdate update. that’s what i ran this afternoon.
oh, i see – haha, i forgot that deleted posts are still able to be seen, whoops. the reason i deleted it was that after that initial error, i waited ten or so minutes then tried again, & that time it completed without any error messages. at that point i chose to delete my post, as i did not want to bother anyone.
so yes, your statement ofc is accurate, but it was followed by an ostensibly successful update. if i understand your implication accurately, it might be that despite my successful second attempt some damage occurred from the fist attempt? no, that sounds silly for me to say that.
Maaaaaybe, but I agree with you it’s unlikely, if you did a second run and everything looked normal.
My residual worry would be that maybe the second run didn’t retry the thing that failed first time round, so it “succeeded” without fixing the problem. Sometimes when I’ve had issues, I’ve found that updatectl vacuum is needed to get the system into a state where it will properly re-attempt the upgrade.
