pop-os / system-updater Goto Github PK
View Code? Open in Web Editor NEWSystemd services for checking for and applying system updates.
License: Mozilla Public License 2.0
Systemd services for checking for and applying system updates.
License: Mozilla Public License 2.0
Pop!_OS 22.04 LTS.
The problem from Issue #14 appears to have come back.
pop-system-updater:
Installed: 0.1.0~1678118957~22.04~2e50214
Candidate: 0.1.0~1678118957~22.04~2e50214
cat /etc/pop-system-updater/config.ron
(auto_update:false,schedule:Some((interval:128,hour:22,minute:0)))
The option in Settings\OS Upgrade & Recovery: Automatic updates is set to Off
.
When I connected to the web recently, within minutes Pop!_Shop in the dock was showing a notification badge and a notification bubble appeared showing new updates were available.
Checking syslog
, there is an entry dated the day of the web connection:
INFO pop_system_updater::service::session: next update in 592218 seconds
With the same date is a log entry of how many new debian packages need updating.
I'm not expecting you to rush out a patch but could you confirm sooner than later if disablingcom.system76.SystemUpdater.service unit in systemd
like @cschmidat suggests is good enough to stop this from happening again?
After installing the most recent 21.10 iso, system-updater is pulled in via pop-upgrade updates, and the config file for update notifications is defaulting to Daily. If I delete the config file and reboot, then it does get regenerated to Weekly. Not yet sure where the initial Daily value is coming from.
Since updating Pop-OS to 22.04, I can't deactivate system updater anymore, which regularly messes up my system. I set auto-updates in gnome-control-center to off; here's the content of ~/.config/pop-system-updater/config.ron:
(enabled:false,notification_frequency:Weekly)
.
Despite that, the service still runs (very aggressive) apt-get -y --allow-downgrades full-upgrade
and apt-get autoremove -y
commands.
I just disabled the com.system76.SystemUpdater.service unit in systemd -- I hope that is good enough.
Distribution (run cat /etc/os-release
):
NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os
Issue/Bug Description:
Every time I select Automatic Update, this button is deselected.
Steps to reproduce (if you know):
Settings --> OS Upgrade & Recovery --> Automatic Update
Expected behavior:
That the selection does not change and it is possible to rely on the button to stay in place.
Pointed out by @joeftiger in #34:
I noticed, that the use of AM/PM time is hardcoded. This clashes with the default time format of 24h in, e.g., the German or French language.
Updates are running when they're scheduled to, but the global system-updater process is also installing updates at boot when it should not be, even when Automatic Updates
is disabled. This is happening on 22.04 and 21.10.
On 6870527, I'm seeing updates run at their previously-scheduled time even after turning Automatic Updates
off.
/etc/pop-system-updater/config.ron
shows auto_update
set to false
as expected, but also still shows the schedule that was previously configured (not sure if it's supposed to be set to I guess not, since it should load what it was set to before when re-enabling; the None
when disablingNone
option is for Update when Available
.)
After booting, it seems the system updater is running too quickly (I guess before my ethernet connection is entirely up) and it somehow fails to connect and entirely blocks. It never restarts nor stops afterwards and stays like this until I kill it manually.
Sadly it's holding the apt lock /var/lib/apt/lists/lock
indefinitely after failing to start and so I have to kill the process in order to be able to use apt
. In this case with the logs below I was told by apt
that process 2499
was holding the lock.
Interestingly it seems it's not preventing the Pop Shop from doing updates manually, but it does prevent me from using apt
manually.
-- Boot 8be4b728aa4c4b079652a39b81658e9f --
Feb 24 11:32:09 odys pop-system-updater[2332]: INFO pop_system_updater::config: loading config: "/home/anomalroil/.config/pop-system-updater/config.ron"
Feb 24 11:32:09 odys pop-system-updater[2332]: INFO pop_system_updater::config: loading config: "/home/anomalroil/.cache/pop-system-updater/cache.ron"
Feb 24 11:32:09 odys pop-system-updater[2332]: INFO pop_system_updater::config: writing config: "/home/anomalroil/.cache/pop-system-updater/cache.ron"
Feb 24 11:32:09 odys pop-system-updater[2332]: INFO pop_system_updater::package_managers::apt: debian packages requiring updates: 13
Feb 24 11:32:09 odys pop-system-updater[2332]: INFO pop_system_updater::service::session: displaying notification of available updates
Feb 24 11:32:16 odys pop-system-updater[2395]: INFO pop_system_updater::service::system: initiating system service
Feb 24 11:32:16 odys pop-system-updater[2395]: INFO pop_system_updater::service::system: DBus connection established
Feb 24 11:32:16 odys pop-system-updater[2395]: INFO pop_system_updater::config: loading config: "/etc/pop-system-updater/config.ron"
Feb 24 11:32:16 odys pop-system-updater[2395]: INFO pop_system_updater::service::system: restarting any session services
Feb 24 11:32:16 odys pop-system-updater[2395]: INFO pop_system_updater::service::system: listening for events
Feb 24 11:32:16 odys pop-system-updater[2395]: INFO pop_system_updater::service::system: received event: CheckForUpdates
Feb 24 11:32:16 odys pop-system-updater[2395]: INFO pop_system_updater::service::system: checking for system updates
Feb 24 11:32:16 odys pop-system-updater[2460]: Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user)
Feb 24 11:32:16 odys pop-system-updater[2395]: INFO pop_system_updater::package_managers::apt: updating package lists
Feb 24 11:32:16 odys pop-system-updater[2499]: Hit:1 https://deb.nodesource.com/node_18.x jammy InRelease
Feb 24 11:32:16 odys pop-system-updater[2499]: Ign:2 http://apt.pop-os.org/proprietary jammy InRelease
Feb 24 11:32:16 odys pop-system-updater[2499]: Get:3 https://packages.gopass.pw/repos/gopass stable InRelease
Feb 24 11:32:16 odys pop-system-updater[2499]: Ign:4 http://apt.pop-os.org/release jammy InRelease
Feb 24 11:32:17 odys pop-system-updater[2499]: Ign:5 http://apt.pop-os.org/ubuntu jammy InRelease
Feb 24 11:32:17 odys pop-system-updater[2499]: Ign:6 http://apt.pop-os.org/ubuntu jammy-security InRelease
Feb 24 11:32:17 odys pop-system-updater[2499]: Ign:7 http://apt.pop-os.org/ubuntu jammy-updates InRelease
Feb 24 11:32:17 odys pop-system-updater[2499]: Ign:8 http://apt.pop-os.org/ubuntu jammy-backports InRelease
Feb 24 11:32:17 odys pop-system-updater[2499]: Err:9 http://apt.pop-os.org/ubuntu jammy Release
Feb 24 11:32:17 odys pop-system-updater[2499]: Cannot initiate the connection to apt.pop-os.org:80 (18.165.183.61). - connect (101: Network is unreachable) Cannot initiate the connection to apt.pop-os.org:80 (18.165.183.47). - connect (101: Network is unreachable) Cannot initiate the connection to apt.pop-os.org:80 (18.165.183.75). - connect (101: Network is unreachable) Cannot initiate the connection to apt.pop-os.org:80 (18.165.183.23). - connect (101: Network is unreachable)
Feb 24 11:32:17 odys pop-system-updater[2499]: Err:10 http://apt.pop-os.org/ubuntu jammy-security Release
Feb 24 11:32:17 odys pop-system-updater[2499]: Cannot initiate the connection to apt.pop-os.org:80 (18.165.183.61). - connect (101: Network is unreachable) Cannot initiate the connection to apt.pop-os.org:80 (18.165.183.47). - connect (101: Network is unreachable) Cannot initiate the connection to apt.pop-os.org:80 (18.165.183.75). - connect (101: Network is unreachable) Cannot initiate the connection to apt.pop-os.org:80 (18.165.183.23). - connect (101: Network is unreachable)
Feb 24 11:32:17 odys pop-system-updater[2499]: Err:11 http://apt.pop-os.org/ubuntu jammy-updates Release
Feb 24 11:32:17 odys pop-system-updater[2499]: Cannot initiate the connection to apt.pop-os.org:80 (18.165.183.61). - connect (101: Network is unreachable) Cannot initiate the connection to apt.pop-os.org:80 (18.165.183.47). - connect (101: Network is unreachable) Cannot initiate the connection to apt.pop-os.org:80 (18.165.183.75). - connect (101: Network is unreachable) Cannot initiate the connection to apt.pop-os.org:80 (18.165.183.23). - connect (101: Network is unreachable)
Feb 24 11:32:17 odys pop-system-updater[2499]: Err:12 http://apt.pop-os.org/ubuntu jammy-backports Release
Feb 24 11:32:17 odys pop-system-updater[2499]: Cannot initiate the connection to apt.pop-os.org:80 (18.165.183.61). - connect (101: Network is unreachable) Cannot initiate the connection to apt.pop-os.org:80 (18.165.183.47). - connect (101: Network is unreachable) Cannot initiate the connection to apt.pop-os.org:80 (18.165.183.75). - connect (101: Network is unreachable) Cannot initiate the connection to apt.pop-os.org:80 (18.165.183.23). - connect (101: Network is unreachable)
Feb 24 11:32:17 odys pop-system-updater[2499]: Ign:2 http://apt.pop-os.org/proprietary jammy InRelease
This seems to consistently reproduce on each reboot.
I'm running the latest version afaik.
More details:
$ uname -a
Linux odys 6.1.11-76060111-generic #202302091138~1675975749~22.04~f771a7f SMP PREEMPT_DYNAMIC Thu F x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/os-release
NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os
$ apt policy pop-system-updater
pop-system-updater:
Installed: 0.1.0~1667931484~22.04~8a27133
Candidate: 0.1.0~1667931484~22.04~8a27133
Version table:
*** 0.1.0~1667931484~22.04~8a27133 1001
1001 http://apt.pop-os.org/release jammy/main amd64 Packages
100 /var/lib/dpkg/status
As a power user, it would be convenient for me to be able to specify in typical cron formatting, when i would like my automatic updates to kick off. Whether this is in a config file or in the GUI doesn't matter, so long as it's possible.
When booted up from a USB stick built from pop-os_22.04_amd64_intel_7.iso, or from a Pop!OS recovery partition made by installing from that ISO, the install/recovery environment prompts the user to install updates at the same time it loads the installer.
I feel like this has the potential to confuse both new Pop!OS users (who may think they have to run the updates before installing the OS) and users who are booting to a USB stick or recovery partition to fix a problem (who may think that they have to run the updates as part of the repair process).
In any case, you can't actually update a USB stick or recovery partition this way, since they're casper images, so I think that the notifications should be turned off, if possible.
Distribution (run cat /etc/os-release
):
NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os
Issue/Bug Description:
Keeps repeating this and filling up my syslog file:
Jul 4 23:42:16 popstudio pop-system-updater[72955]: INFO pop_system_updater::service::system: initiating system service
Jul 4 23:42:16 popstudio pop-system-updater[72955]: Error: system service is already active
Jul 4 23:42:16 popstudio systemd[8330]: com.system76.SystemUpdater.Local.service: Main process exited, code=exited, status=1/FAILURE
Jul 4 23:42:16 popstudio systemd[8330]: com.system76.SystemUpdater.Local.service: Failed with result 'exit-code'.
Jul 4 23:42:16 popstudio systemd[8330]: Failed to start Local session service for the Pop System Updater.
Jul 4 23:42:16 popstudio systemd[8330]: com.system76.SystemUpdater.Local.service: Scheduled restart job, restart counter is at 707.
Jul 4 23:42:16 popstudio systemd[8330]: Stopped Local session service for the Pop System Updater.
Jul 4 23:42:16 popstudio systemd[8330]: Starting Local session service for the Pop System Updater...
Hello, is it possible to add a progressbar? How do i know if the updates are complete? I have selected "Automatic Updates" and "Automatically Install".
Thank you
These entries are spamming my systemd logs ever since I installed the latest pop-system-updater:
May 14 12:48:49 lagos pop-system-updater[40163]: Error: service must be launched from either root or a desktop user
May 14 12:48:49 lagos systemd[1255]: com.system76.SystemUpdater.Local.service: Main process exited, code=exited, status=1/FAILURE
May 14 12:48:49 lagos systemd[1255]: com.system76.SystemUpdater.Local.service: Failed with result 'exit-code'.
May 14 12:48:49 lagos systemd[1255]: Failed to start Local session service for the Pop System Updater.
May 14 12:48:49 lagos systemd[1255]: com.system76.SystemUpdater.Local.service: Scheduled restart job, restart counter is at 402.
May 14 12:48:49 lagos systemd[1255]: Stopped Local session service for the Pop System Updater.
May 14 12:48:49 lagos systemd[1255]: Starting Local session service for the Pop System Updater...
This started after I got an update to version 0.1.0~1651702806~21.10~b49b23a
.
This is a very high priority issue as it is slamming updates in my log every 2-20 seconds and there isn't a way to roll BACK to a version without this bug without building it oneself. This is going to kill systms that have SSDs for their main disk.
Using the latest pop-system-updater package (pop-system-updater 0.1.0~1651702806~22.04~b49b23a
).
Now my /var/log/syslog/
show lines like this:
May 6 11:00:54 amperama pop-system-updater[445660]: #033[32m INFO#033[0m #033[2mpop_system_updater::package_managers::apt#033[0m#033[2m:#033[0m debian packages requiring updates: 0
Is there a way to turn off color codes for system log?
TIA
Distribution (run cat /etc/os-release
):
NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os
Issue/Bug Description:
Update notification card will not go away until system is rebooted. Attempting to close the card fails.
Steps to reproduce (if you know):
Update notification appears. Updates run, but card does not go away. Even attempting to close it with mouse fails. Only reboots remove it.
Expected behavior:
Should disappear when updates are finished, or when user clicks "close".
Other Notes:
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.