Defender was (and is) a very nice and handy tool. And it eases ad blocking and adds some privacy measures. All kudos to nodevel!
Unfortunately it is not maintained anymore and even worse it caused encrypted devices to stop booting (it could be resolved by using recovery image and deinstalling ‘rpm -e harbour-defender’ (or editing path unit manually).
I could not (and still cannot) understand that systemd can be so bold to ‘support’ such situation causing full boot freezes.
It took me some efforts to grab what caused this but in the end found and solved it.
Furthermore I modified some code to handle as well nemo as defaultuser as valid GUI users.
This was the last obstacle keeping me from updating to 3.4. You kinda made my day.
Would you like to share some details what you did exactly to the systemd unit to fix it? And could you share the modified sources once you got the opportunity?
I would have sworn I tested this but maybe I was so happy that my test device booted up I forgot.
And (almost) nobody noticed.
In v0.4.1 I fixed the boot loop but the path unit (responsible to register/start the triggered update) was not started after boot.
I recognized only now after a frozen device reboot.
So back to systemd and finding that my chosen start (WantedBy / After) criteria were plain wrong. One was just mistyped and the other can only be used within user unit.
But now I am pretty sure it is okay
sorry, ok, storeman tells me he is installing but nothing happens, just the ring does infinitly loop.
with the download he asks for the Installation but then simply says “Installation fehlgeschlagen” which simply means could not install, no error msg. i have no idea if i can try it by console, i’m not that good in coding etc. i just like sailfish and its unlike ux (even if it gets worse so often with updates)’
Well first for the spinner (ring) not stopping to spin: This might be a small bug in Storeman. Happens for me, too. But it’s not necessarily an indicator for issues, I see it on successful installs as well.
Now, to the error message : Normally, when you tap the notification Storeman emmits, you should see some details about why the install failed.
Probably the most straight forward solution - without knowing the specific reason why installing failed (check you error message for that):
Try to refresh you package cache. You can do this using the terminal with developer mode enabled by issuing the command devel-su pkcon refresh.
Alternatively the more ‘average user way’ is to install Sailfish Utilities from the Jolla store and refresh the cache from there (see section “Paket-Zwischenspeicher”).
ok, i may be a more average user compred to most of you but i’m not afraid to use console ( on my work i’m the one using shell scripts)
i did pkcon refresh on decel-su first. now i did it without being root. then i tried to pkcon install habour-defender and got a fatal exception: a conflict with sailfishos-hosts-adblock. i hsd no idea that this is still on my device. after removing it i went to storeman and installed the defender. thanks for your help. i do not get why nowadays i have to be not under devel-su but this is my fault so as said before compred to nost of you i’m just an average user with some experience.
thanks all, defender is already installed now.
This great update has been working for months but recently I have run into the issue where updating the blocking lists loops forever. I’m using 0.4.2 and am still on SFOS 3.4.0.
I have disabled any sources except the Unified Hosts, Disconnect.me and hpHosts. Individually enabling any of these and restarting the update doesn’t help. Even after reinstalling Defender the update progress bar displays just the same
What can I do? Could it be that all the subscription sources have become unavailable ?
Right now blocking isn’t working at all.
short/fast answer…did you reboot or make sure with e.gg killall that ni python defender moduke was still running
afair this really hangs
so just reconfiguring and trying ti get it running okay will not work…
