In response to Erich E. Hoover's last comment, I've looked into the issue and can confirm update-notifer is indeed responsible. I've created a one line fix in case anyone is interested. It simply ensures a path exists before deleting it.
The problematic code resides in package-data-downloader within the update-notifier-common package. You have the option of either patching the installed file or updating the package itself.
To patch the installed file, download the patch then run:
`sudo patch /usr/lib/update-notifier/package-data-downloader < ./update-notifier-common-fix.patch`
To patch the package itself, you can do so quite easily with a utility I wrote named debtool (https://github.com/brbsix/debtool). Install debtool, download the patch, then run:
```
# unpack the system's update-notifier-common package into the current directory
debtool -u update-notifier-common
In response to Erich E. Hoover's last comment, I've looked into the issue and can confirm update-notifer is indeed responsible. I've created a one line fix in case anyone is interested. It simply ensures a path exists before deleting it.
The problematic code resides in package- data-downloader within the update- notifier- common package. You have the option of either patching the installed file or updating the package itself.
To patch the installed file, download the patch then run: update- notifier/ package- data-downloader < ./update- notifier- common- fix.patch`
`sudo patch /usr/lib/
To patch the package itself, you can do so quite easily with a utility I wrote named debtool (https:/ /github. com/brbsix/ debtool). Install debtool, download the patch, then run:
``` notifier- common package into the current directory notifier- common
# unpack the system's update-
debtool -u update-
# install patch notifier- common_ *_all/usr/ lib/update- notifier/ package- data-downloader < ./update- notifier- common- fix.patch
patch ./update-
# build and reinstall debian package notifier- common_ *_all
debtool -z ./update-
```