[Touch-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2020-05-17 Thread kkivi
19.10->20.04 the same thing.
It is happened not to be a loop but a series of identical messages from 
different packages. I package name should be included int the messages,
to help user better understand the issue

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

Title:
  [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  During system upgrades, triggers for gconf2 might activate too early,
  while some of its dependencies aren't configured yet. This happens
  several times in a loop and stops the upgrade in the end.

  The attached debdiffs fix this issue by changing interest to interest-
  noawait in debian/gconf2.triggers file. The triggers will now activate
  near the end of upgrade.

  In addition, the debdiff for Bionic also contains a fix for FTBFS (bug
  1834211).

  [Test Case]

  Triggers for gconf2 are usually activated on changes in
  /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with
  GNOME) is most suitable for reproducing the issue. To reproduce it,
  install that edition, apply all updates, then try upgrading to the
  next release.

  [Regression Potential]

  None, interest-noawait trigger is known to work well in other packages
  (comment 31).

  [Other Info]

  Even if Cosmic goes EOL next month, the fix for it might be worth it
  for release upgrades.

  [Original Description]

  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome.
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+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 1838838] Re: username is not saved in openconnect connection dialog

2020-04-08 Thread kkivi
Not only it doesn't connect username, but it saves 
one time password instead

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

Title:
  username is not saved in openconnect connection dialog

Status in GNOME Shell:
  New
Status in NetworkManager:
  New
Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Same issue as https://bugs.launchpad.net/ubuntu/+source/network-
  manager-openconnect/+bug/1609700

  This was marked resolved. The report of its reappearance in Ubuntu
  19.04 and 19.10 has not been acknowledged.

  This was working for me in 18.10, but a fresh install of 19.04 and
  19.10 show that it is back. The password is saved when the option to
  save passwords is selected, but the username must be entered manually
  upon connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1838838/+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