Hi, The behaviour you are observing is related to the Debian-packaged version of the OneDrive client rather than the upstream project itself.
The Debian package currently referenced in this bug is v2.5.4, which is obsolete and no longer supported upstream. The actively maintained and supported builds are provided via the official OpenSuSE Build Service (OBS) repositories and upstream release artefacts. These builds are the only ones validated and supported by the project. The Debian/Ubuntu distribution packages also differ from upstream in how the user-level systemd service is installed and enabled. In particular, the distro packages automatically enable a default user service (/usr/lib/systemd/user/onedrive.service), which can remain enabled or active across package removal. This behaviour is not present in the upstream/OBS packages and is outside upstream control. I have raised this exact point many times with the Debian package maintainer to remove this behaviour from the Debian packages. As a result: * The issue described here does not occur with the official upstream packages * It originates from Debian packaging/service lifecycle behaviour and hot the Debian + Ubuntu packages are built * The Debian package version (v2.5.4) involved is already obsolete upstream and that application version should not be used. It contains many bugs which have been fixed. Please use v2.5.10 or greater to access your Microsoft OneDrive data. Users are therefore strongly advised to install the client using the supported upstream repositories and instructions: * https://github.com/abraunegg/onedrive/blob/master/docs/install.md * https://github.com/abraunegg/onedrive/blob/master/docs/ubuntu-package-instal l.md This ensures the current maintained version and correct service integration are used. This also means your client will remain up-to-date when new releases are done. Please refer to https://github.com/abraunegg/onedrive/releases as to changes between client versions. Kind regards, Alex Upstream maintainer - OneDrive Client for Linux https://github.com/abraunegg/onedrive On Tue, 10 Feb 2026 10:57:29 +0100 Lee Garrett <[email protected]> wrote: > Package: onedrive > Version: 2.5.4-1 > Severity: normal > X-Debbugs-Cc: [email protected] > > Hi, > > after purging the package, the onedrive service is still running in the user > instance, and as such will be restarted every 3 seconds and spam the logs: > > Feb 10 10:32:00 myws systemd[1692]: Started onedrive.service - OneDrive Client for Linux. > Feb 10 10:32:00 myws (onedrive)[24933]: onedrive.service: Unable to locate executable '/usr/bin/onedrive': No such file or directory > Feb 10 10:32:00 myws (onedrive)[24933]: onedrive.service: Failed at step EXEC spawning /usr/bin/onedrive: No such file or directory > Feb 10 10:32:00 myws systemd[1692]: onedrive.service: Main process exited, code=exited, status=203/EXEC > Feb 10 10:32:00 myws systemd[1692]: onedrive.service: Failed with result 'exit-code'. > Feb 10 10:32:02 myws systemd[12479]: Started onedrive.service - OneDrive Client for Linux. > Feb 10 10:32:02 myws (onedrive)[24940]: onedrive.service: Unable to locate executable '/usr/bin/onedrive': No such file or directory > Feb 10 10:32:02 myws (onedrive)[24940]: onedrive.service: Failed at step EXEC spawning /usr/bin/onedrive: No such file or directory > Feb 10 10:32:02 myws systemd[12479]: onedrive.service: Main process exited, code=exited, status=203/EXEC > Feb 10 10:32:02 myws systemd[12479]: onedrive.service: Failed with result 'exit-code'. > Feb 10 10:32:03 myws systemd[1692]: onedrive.service: Scheduled restart job, restart counter is at 201. > Feb 10 10:32:03 myws systemd[1692]: Starting onedrive.service - OneDrive Client for Linux... > Feb 10 10:32:05 myws systemd[12479]: onedrive.service: Scheduled restart job, restart counter is at 105. > Feb 10 10:32:05 myws systemd[12479]: Starting onedrive.service - OneDrive Client for Linux... > > This is due to the fact that the user instance of the service is still attempted > to run, but the binary is not there anymore. > > Steps to reproduce: > 1) install onedrive (duh) > 2) reboot > 3) log in to your desktop environment (e.g. gnome) > 4) apt purge onedrive > 5) notice the output above in `journalctl -f` > 6) systemctl status --user onedrive returns a failed service > > I was able to fix it by running `systemctl --user daemon-reload`. > > I'm unsure how to best fix this, since I'm not aware of a way to trigger this > for every user on the system via postrm script. But maybe the next best thing is > > ``` > ExecCondition=/usr/bin/test -x /usr/bin/onedrive > ``` > > since this will prevent the restart logic from catching on. > > Regards, > Lee > > > -- System Information: > Debian Release: 13.3 > APT prefers stable-updates > APT policy: (1001, 'stable-updates'), (1001, 'stable-security'), (1001, 'proposed-updates'), (1001, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.12.63+deb13-amd64 (SMP w/8 CPU threads; PREEMPT) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en > Shell: /bin/sh linked to /usr/bin/dash
