Powersave mode extrem

Moem

@Linus67 said:

leftover files from the ubconnect app,

Where did you find these files please? I may have a similar situation.

uxes

@Moem you might wanna know that more applications does this daemon copy thing and after uninstall the service is there https://codeberg.org/tautologia/ubconnect/src/branch/master/ubconnect/daemon/install.sh
for example that smartwatch app

Moem

@uxes Thank you for the hint... I took a leap of faith and ran systemctl --user stop ubconnect-daemon.service and got a command prompt... no errors. I took this as encouragement and ran systemctl --user disable ubconnect-daemon.service and it told me something with UBconnect in it was removed. I think that was probably useful!

As for smartwatch apps, I'm still using those, so they can stay.

Linus67

@Moem

I was monitoring the journal with “sudo journalctl -f” while I turned the Wi-Fi on and off. I noticed that when turning on the Wi-Fi, a connection attempt by the daemon fails.

sudo journalctl -f
Mai 20 19:14:25 ubuntu-phablet systemd[2850]: ubconnect-daemon.service: Main process exited, code=exited, status=1/FAILUREMai 20 19:14:25 ubuntu-phablet systemd[2850]: ubconnect-daemon.service: Failed with result 'exit-code'.Mai 20 19:14:30 ubuntu-phablet systemd[2850]: ubconnect-daemon.service: Scheduled restart job, restart counter is at 89.Mai 20 19:14:30 ubuntu-phablet systemd[2850]: Started ubconnect-daemon.service - UB Connect Daemon.Mai 20 19:14:30 ubuntu-phablet aa-exec[5041]: [5041] aa-exec: ERROR: Failed to execute "/opt/click.ubuntu.com/ubconnect/current/usr/bin/ubconnect-daemon": No such file or directoryMai 20 19:14:30 ubuntu-phablet systemd[2850]: ubconnect-daemon.service: Main process exited, code=exited, status=1/FAILUREMai 20

gpatel-fr

@uxes

dekko does it too.
IIRC every app that is installing a systemd service I have looked at don't remove it when uninstalled.

Moem

@Linus67 said:

I was monitoring the journal with “sudo journalctl -f” while I turned the Wi-Fi on and off.

Thank you! That's a bit above my paygrade.

Linus67

@Moem
As @uxes wrote

Run the following commands in the Terminal.

systemctl --user stop ubconnect-daemon.service
systemctl --user disable ubconnect-daemon.service
rm -f ~/.config/systemd/user/ubconnect-daemon.service
systemctl --user daemon-reload
systemctl --user status ubconnect-daemon.service

result:

Unit ubconnect-daemon.service could not be found.

Moem

@Linus67 As I said, the first two were what I did, after figuring out they might be helpful.
Can I be a little proud of myself for figuring that out? I'm not a terminal user at all.

Moem

@Linus67 said:

rm -f ~/.config/systemd/user/ubconnect-daemon.service

Thanks to this hint, I knew where to find it and removed it using the file manager.
All clear now!

The advantage of using the GUI in this case was that it showed me what else lived there. There was another daemon that was no longer needed. So that was helpful.

uxes

@gpatel-fr yes that is just missing thing of click packages since they don’t have some kind of postinstall and postuninstall hooks to insert and remove those systemd services

gpatel-fr

@uxes

It's a feature, taken from the click documentation:

4.3.2 Specification
• Only system packages (i.e. .debs) may declare hooks. Click packages must be declarativeinclude code executed outside AppArmor confinement, which precludes declaring hooks.