[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

2020-10-14 Thread Matthieu Clemenceau
** Tags added: fr-303

-- 
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:
  Confirmed
Status in software-properties source package in Eoan:
  Won't Fix

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


[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

2020-08-18 Thread Brian Murray
eoan has reached end of life, so this bug will not be fixed for that
release

** Changed in: software-properties (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

-- 
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:
  Confirmed
Status in software-properties source package in Eoan:
  Won't Fix

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


[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

2019-11-05 Thread Erik Sax
This is a silly and very user hostile bug that is still present in
19.10. Seems crazy that it's basically being ignored.

-- 
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:
  Confirmed
Status in software-properties source package in Eoan:
  Confirmed

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


[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

2019-07-18 Thread Brian Murray
** Tags removed: rls-ee-incoming

-- 
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:
  Confirmed
Status in software-properties source package in Eoan:
  Confirmed

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


[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

2019-07-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

-- 
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:
  Confirmed
Status in software-properties source package in Eoan:
  Confirmed

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


[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

2019-07-12 Thread Francis Ginther
** Tags added: id-5d2752b415f430133d5cd4a1

-- 
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:
  New
Status in software-properties source package in Eoan:
  New

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


[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

2019-07-11 Thread Steve Langasek
** Also affects: software-properties (Ubuntu Eoan)
   Importance: High
   Status: New

-- 
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:
  New
Status in software-properties source package in Eoan:
  New

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


[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

2019-07-03 Thread Erik Sax
This continues to happen, more aggressively on 19.04 than on previous
versions. This system popped up with updates today has been running
19.04 the longest of all my systems with "never" as the selected option
and it just keeps checking for updates. I've got two processes seemingly
related, one was started by init

14921 1  0 08:37 tty2 00:00:15 /usr/bin/python3 /usr/bin/update-
manager --no-update --no-focus-on-map

The other must be the gui who has the gnome-session-binary as the parent
process

2351  1704  0 08:28 tty2 00:00:00 update-notifier

-- 
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:
  New

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


[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

2019-06-28 Thread Erik Sax
Did a PS on one of these systems this morning. Found some shenanigans.
root  3380 1  0 08:25 ?00:00:00 /bin/sh 
/usr/lib/apt/apt.systemd.daily install
root  3384  3380  0 08:25 ?00:00:00 /bin/sh 
/usr/lib/apt/apt.systemd.daily lock_is_held install
root  3415  3384 99 08:25 ?00:00:09 /usr/bin/python3 
/usr/bin/unattended-upgrade

Grep for "updates" yielded this:
$ ps -ef | grep upgrade
root  1182 1  0 08:22 ?00:00:00 /usr/bin/python3 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal
root  3415  3384 14 08:25 ?00:00:22 /usr/bin/python3 
/usr/bin/unattended-upgrade
root  5356  3415  1 08:27 ?00:00:00 /usr/bin/python3 
/usr/bin/unattended-upgrade

After I killed 3415 I was able to get the apt lock and proceed with a
manual `sudo apt-get upgrade`

-- 
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:
  New

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


[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

2019-06-27 Thread Sebastien Bacher
** Changed in: software-properties (Ubuntu)
   Status: Incomplete => New

-- 
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:
  New

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


[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

2019-06-27 Thread Erik Sax
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


[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

2019-06-27 Thread Brian Murray
** Changed in: software-properties (Ubuntu)
   Status: New => Incomplete

-- 
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


[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

2019-06-27 Thread Julian Andres Klode
Also, final question, did you turn off "Download and install
automatically" for security updates?

If you only turn of "Automatically check for updates", then we won't
automatically check for updates, but if you ran apt update, the next
day-ish all updates will be downloaded automatically (it should be only
security updates, but it also downloads non-security ones).

-- 
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:
  New

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


[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

2019-06-27 Thread Julian Andres Klode
Also, is this a desktop machine / does it have PackageKit installed, and
if so, which frontends for packagekit?

** Package changed: update-notifier (Ubuntu) => software-properties
(Ubuntu)

-- 
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:
  New

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