In the updates tab, I keep all three boxes checked under "Install
updates from:", because I like to manually run `sudo apt-get update &&
sudo apt-get upgrade` whenever I have a good stable release of software
and feel like stomaching a raft of system changes.

In past versions of ubuntu going back 'Dapper Drake', I'd change the
setting for "automatically check for updates" and it was generally good
about respecting this setting from my recollection. I'm not sure which
release changed this but it's for sure worse, the updater tries to run
in the background, and I've noticed it's easy to repeat as I've
installed 19.04 on various machines. I've got laptops and desktops alike
with 19.04 installed, and they all have this problem. I tried letting it
actually do the updates, but that didn't work so I generally cancel it.

This non-deterministic behavior is nonsensical. When update-notifier
runs, check this flag and quit if it's set to 'Never'. There's really
nothing else to debug, is there?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1834226

Title:
  update-notifier doesn't respect "automatically check for updates:
  Never"

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  This has been a long-standing problem with various ubuntu
  installations, and I'm sensing some reticence in doing anything about
  it. This attitude also seems to be purposeful to try to cajole updates
  on people who make bad choices due to confusion/fud/paranoia.

  apt install fails due to:

  E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource 
temporarily unavailable)
  E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is 
another process using it?

  A great deal of networking is taking place despite setting automatic
  upgrades to "never". Cycling this doesn't seem to do anything. This
  action is hostile to programmers and the setting should be respected.

  Wisdom on threads is to let it update until it's out of updates, and
  then it supposedly respects the "never" flag, but the experience I'm
  having is much more non-deterministic. have been using 19.04 for weeks
  now and still get the background notifier using data and getting in
  the way of aptitude package installations. I prefer manual update &&
  upgrade once my code is ready to push.

  Is there another way around this or are people just living with it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1834226/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to