[Touch-packages] [Bug 1395321] Re: Adding ppa not working under proxy

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.96.24.25

---
software-properties (0.96.24.25) bionic; urgency=medium

  * ppa.py:
   - rework key retrieval, instead of using hkp & gnupg/dirmngr, use https
 & python's built in urllib.
   - thus, add-apt-key for PPAs observes https_proxy for key retrieval
   - simplify gnupg operations, depend on gpg package only, and use
 import/public key operations only.
   - fix unicode process output bugs, when operating in a non-UTF-8
 locale, thus enabling to import keys for my ppas in C locale.
   - avoid creating trustdb, or requiring any gpg-agent systemd socket to
 be activated
   - update tests to execute key addition fully with less things stubbed
 out with mock
   - stop using apt-key for installing keys
   - dirmngr is a heavy dependency and not used, and it is hard to pass
 proxy information to it when invoking gpg from a non-standard homedir
   - deprecate --keyserver option, making HTTPS access to
 keyserver.ubuntu.com required
   - LP: #1755192, LP: #1713962, LP: #1699086, LP: #1510220, LP: #1433761,
 LP: #1395321, LP: #1312267

 -- Dimitri John Ledkov   Mon, 02 Apr 2018 10:19:34
+0100

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

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

Title:
  Adding ppa not working under proxy

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu 13.10, PPA's could be added under proxy. But after that, i.e
  in 14.04, error comes like this

  Cannot add PPA: 'ppa:ppa name'.
  Please check that the PPA name or format is correct.

  apt works fine under proxy. But, repositories are not added. I have to
  use a non-proxified network to add repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1395321/+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 1433761] Re: apt-key and add-apt-repository don't honor Acquire::http::Proxy

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.96.24.25

---
software-properties (0.96.24.25) bionic; urgency=medium

  * ppa.py:
   - rework key retrieval, instead of using hkp & gnupg/dirmngr, use https
 & python's built in urllib.
   - thus, add-apt-key for PPAs observes https_proxy for key retrieval
   - simplify gnupg operations, depend on gpg package only, and use
 import/public key operations only.
   - fix unicode process output bugs, when operating in a non-UTF-8
 locale, thus enabling to import keys for my ppas in C locale.
   - avoid creating trustdb, or requiring any gpg-agent systemd socket to
 be activated
   - update tests to execute key addition fully with less things stubbed
 out with mock
   - stop using apt-key for installing keys
   - dirmngr is a heavy dependency and not used, and it is hard to pass
 proxy information to it when invoking gpg from a non-standard homedir
   - deprecate --keyserver option, making HTTPS access to
 keyserver.ubuntu.com required
   - LP: #1755192, LP: #1713962, LP: #1699086, LP: #1510220, LP: #1433761,
 LP: #1395321, LP: #1312267

 -- Dimitri John Ledkov   Mon, 02 Apr 2018 10:19:34
+0100

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

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

Title:
  apt-key and add-apt-repository don't honor Acquire::http::Proxy

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  When setting the proxy server globally on the system for the APT
  package manager, add-apt-repository ignores the setting. This issue is
  present on all versions of Debian that I have tested.

  # cat /etc/apt/apt.conf.d/80proxy 
  Acquire::http::proxy "http://w.x.y.z:/;;

  # apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5A9A06AEF9CB8DB0
  Executing: gpg --ignore-time-conflict --no-options --no-default-keyring 
--homedir /tmp/tmp.TIa517Kcw8 --no-auto-check-trustdb --trust-model always 
--keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg --keyring 
/etc/apt/trusted.gpg.d/saltstack-salt.gpg --keyserver keyserver.ubuntu.com 
--recv-keys 5A9A06AEF9CB8DB0
  gpg: requesting key F9CB8DB0 from hkp server keyserver.ubuntu.com
  gpg: keyserver timed out
  gpg: keyserver receive failed: keyserver error

  This has serious repercussions. Unattended installs such as juju,
  maas, etc are all affected for anyone who is working behind a proxy.
  This is the case for most enterprise environments where such maas and
  juju setups will be tested out, and as such has great repercussions
  for Canonical as a viable supplier of OpenStack environments: if your
  product fails to install, you're not going to get the business.

  Considering that:

  * The setting to use already exists in /etc/apt/apt.conf and that all other 
tools use this correctly
  * The serious impact of this issue for downstream projects and Debian usage 
in the enterprise
  * The long time this issue has been standing and has affected people

  I suggest that this either

  1) be fixed, or
  2) the apt-key and add-apt-repository programs are renamed so that it is made 
clear they are not part of the APT suite of programs and therefor cannot be 
trusted to behave as if they were part of APT.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1433761/+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 1510220] Re: add-apt-repository backtraces on PPA with utf8 characters

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.96.24.25

---
software-properties (0.96.24.25) bionic; urgency=medium

  * ppa.py:
   - rework key retrieval, instead of using hkp & gnupg/dirmngr, use https
 & python's built in urllib.
   - thus, add-apt-key for PPAs observes https_proxy for key retrieval
   - simplify gnupg operations, depend on gpg package only, and use
 import/public key operations only.
   - fix unicode process output bugs, when operating in a non-UTF-8
 locale, thus enabling to import keys for my ppas in C locale.
   - avoid creating trustdb, or requiring any gpg-agent systemd socket to
 be activated
   - update tests to execute key addition fully with less things stubbed
 out with mock
   - stop using apt-key for installing keys
   - dirmngr is a heavy dependency and not used, and it is hard to pass
 proxy information to it when invoking gpg from a non-standard homedir
   - deprecate --keyserver option, making HTTPS access to
 keyserver.ubuntu.com required
   - LP: #1755192, LP: #1713962, LP: #1699086, LP: #1510220, LP: #1433761,
 LP: #1395321, LP: #1312267

 -- Dimitri John Ledkov   Mon, 02 Apr 2018 10:19:34
+0100

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

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

Title:
  add-apt-repository backtraces on PPA with utf8 characters

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  On a brand new trusty container:

  root@apatest3:~# add-apt-repository ppa:ondrej/apache2
   This branch follows latest PHP packages as maintained by the Debian Apache2 
team.

  It also includes some widely used Apache 2 modules (if you need some
  other feel free to send me a request).

  If you need to stay with PHP 5 you can use the PHP repository:
  https://launchpad.net/~ondrej/+archive/php5

  BUGS: This PPA now has a issue tracker:
  https://deb.sury.org/pages/bugreporting.html

  PLEASE READ: If you like my work and want to give me a little motivation, 
please consider donating: https://deb.sury.org/pages/donate.html
   More info: https://launchpad.net/~ondrej/+archive/ubuntu/apache2
  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keyring `/tmp/tmprl8b6i1r/secring.gpg' created
  gpg: keyring `/tmp/tmprl8b6i1r/pubring.gpg' created
  gpg: requesting key E5267A6C from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmprl8b6i1r/trustdb.gpg: trustdb created
  gpg: key E5267A6C: public key "Launchpad PPA for Ond\xc5\x99ej Sur▒" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  Exception in thread Thread-1:
  Traceback (most recent call last):
File "/usr/lib/python3.4/threading.py", line 920, in _bootstrap_inner
  self.run()
File "/usr/lib/python3.4/threading.py", line 868, in run
  self._target(*self._args, **self._kwargs)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
687, in addkey_func
  func(**kwargs)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 370, 
in add_key
  return apsk.add_ppa_signing_key()
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 261, 
in add_ppa_signing_key
  tmp_export_keyring, signing_key_fingerprint, tmp_keyring_dir):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 210, 
in _verify_fingerprint
  got_fingerprints = self._get_fingerprints(keyring, keyring_dir)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 202, 
in _get_fingerprints
  output = subprocess.check_output(cmd, universal_newlines=True)
File "/usr/lib/python3.4/subprocess.py", line 605, in check_output
  output, unused_err = process.communicate(inputdata, timeout=timeout)
File "/usr/lib/python3.4/subprocess.py", line 936, in communicate
  stdout = _eintr_retry_call(self.stdout.read)
File "/usr/lib/python3.4/subprocess.py", line 487, in _eintr_retry_call
  return func(*args)
File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode
  return codecs.ascii_decode(input, self.errors)[0]
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 92: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-common 0.92.37.5
  ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  Date: Mon Oct 26 18:22:33 2015
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1755192] Re: Running add-apt-repository inside docker bionic container gives No such file or directory: 'S.gpg-agent.browser'

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.96.24.25

---
software-properties (0.96.24.25) bionic; urgency=medium

  * ppa.py:
   - rework key retrieval, instead of using hkp & gnupg/dirmngr, use https
 & python's built in urllib.
   - thus, add-apt-key for PPAs observes https_proxy for key retrieval
   - simplify gnupg operations, depend on gpg package only, and use
 import/public key operations only.
   - fix unicode process output bugs, when operating in a non-UTF-8
 locale, thus enabling to import keys for my ppas in C locale.
   - avoid creating trustdb, or requiring any gpg-agent systemd socket to
 be activated
   - update tests to execute key addition fully with less things stubbed
 out with mock
   - stop using apt-key for installing keys
   - dirmngr is a heavy dependency and not used, and it is hard to pass
 proxy information to it when invoking gpg from a non-standard homedir
   - deprecate --keyserver option, making HTTPS access to
 keyserver.ubuntu.com required
   - LP: #1755192, LP: #1713962, LP: #1699086, LP: #1510220, LP: #1433761,
 LP: #1395321, LP: #1312267

 -- Dimitri John Ledkov   Mon, 02 Apr 2018 10:19:34
+0100

** Changed in: software-properties (Ubuntu Bionic)
   Status: Confirmed => Fix Released

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

Title:
  Running add-apt-repository inside docker bionic container gives No
  such file or directory: 'S.gpg-agent.browser'

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Released

Bug description:
  This used to work for Ubuntu 14.04 and 16.04.

  ```
  Step 5/7 : RUN add-apt-repository -y ppa:kernsuite/kern-dev
   ---> Running in 4d6412c3d237
  gpg: keybox '/tmp/tmpol6z8f79/pubring.gpg' created
  gpg: /tmp/tmpol6z8f79/trustdb.gpg: trustdb created
  gpg: key 813B0DC8B7D042E7: public key "Launchpad PPA for KERN suite" imported
  gpg: Total number processed: 1
  gpg:   imported: 1
  Warning: apt-key output should not be parsed (stdout is not a terminal)
  OK
  [Errno 2] No such file or directory: 'S.gpg-agent.browser'
  ```

  Dockerfile:

  ```
  FROM ubuntu:18.04
  MAINTAINER gijsmolen...@gmail.com
  RUN apt-get update
  RUN apt-get install -y software-properties-common
  RUN add-apt-repository -y ppa:kernsuite/kern-dev
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1755192/+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 1758844] Re: gnome-software crashed with SIGSEGV in tcache_get() → _FcStrSetGrow → #3 → IA__FcStrSetAdd → IA__FcConfigParseAndLoad → FcConfigParseAndLoadDir → #7 → FcParseInclude

[Adam Collard]

** Attachment added: "10-scale-bitmap-fonts.conf"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1758844/+attachment/5099805/+files/10-scale-bitmap-fonts.conf

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

Title:
  gnome-software crashed with SIGSEGV in tcache_get() → _FcStrSetGrow →
  #3 → IA__FcStrSetAdd → IA__FcConfigParseAndLoad →
  FcConfigParseAndLoadDir → #7 → FcParseInclude → #9 → doContent →
  contentProcessor

Status in fontconfig package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New

Bug description:
  Background crash report

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 26 07:05:25 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2015-07-04 (995 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f55edd0f207 <__GI___libc_malloc+407>:   mov
(%rdx),%rdi
   PC (0x7f55edd0f207) ok
   source "(%rdx)" (0x6e6f662f6374652f) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   tcache_get (tc_idx=2) at malloc.c:2943
   __GI___libc_malloc (bytes=48) at malloc.c:3050
   () at /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
   FcStrSetAdd () at /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
   FcConfigParseAndLoad () at /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
  Title: gnome-software crashed with SIGSEGV in tcache_get()
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (10 days ago)
  UserGroups: adm cdrom dip docker landscape libvirt libvirtd lpadmin lxd 
plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1758844/+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 1699086] Re: add-apt-repository crashes on non-ascii names in PGP keys

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.96.24.25

---
software-properties (0.96.24.25) bionic; urgency=medium

  * ppa.py:
   - rework key retrieval, instead of using hkp & gnupg/dirmngr, use https
 & python's built in urllib.
   - thus, add-apt-key for PPAs observes https_proxy for key retrieval
   - simplify gnupg operations, depend on gpg package only, and use
 import/public key operations only.
   - fix unicode process output bugs, when operating in a non-UTF-8
 locale, thus enabling to import keys for my ppas in C locale.
   - avoid creating trustdb, or requiring any gpg-agent systemd socket to
 be activated
   - update tests to execute key addition fully with less things stubbed
 out with mock
   - stop using apt-key for installing keys
   - dirmngr is a heavy dependency and not used, and it is hard to pass
 proxy information to it when invoking gpg from a non-standard homedir
   - deprecate --keyserver option, making HTTPS access to
 keyserver.ubuntu.com required
   - LP: #1755192, LP: #1713962, LP: #1699086, LP: #1510220, LP: #1433761,
 LP: #1395321, LP: #1312267

 -- Dimitri John Ledkov   Mon, 02 Apr 2018 10:19:34
+0100

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

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

Title:
  add-apt-repository crashes on non-ascii names in PGP keys

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  When adding the PHP 7.1 repo into Ubuntu 16.04 LTS I get the following
  error.

  Command;
  add-apt-repository ppa:ondrej/php -y

  Output;
  gpg: keyring `/tmp/tmprs_t5_d6/secring.gpg' created
  gpg: keyring `/tmp/tmprs_t5_d6/pubring.gpg' created
  gpg: requesting key E5267A6C from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmprs_t5_d6/trustdb.gpg: trustdb created
  gpg: key E5267A6C: public key "Launchpad PPA for Ond\xc5\x99ej Sur�" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  'ascii' codec can't decode byte 0xc5 in position 92: ordinal not in range(128)

  The command exits with code 1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1699086/+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 1713962] Re: apt-add-repository times out behind proxy

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.96.24.25

---
software-properties (0.96.24.25) bionic; urgency=medium

  * ppa.py:
   - rework key retrieval, instead of using hkp & gnupg/dirmngr, use https
 & python's built in urllib.
   - thus, add-apt-key for PPAs observes https_proxy for key retrieval
   - simplify gnupg operations, depend on gpg package only, and use
 import/public key operations only.
   - fix unicode process output bugs, when operating in a non-UTF-8
 locale, thus enabling to import keys for my ppas in C locale.
   - avoid creating trustdb, or requiring any gpg-agent systemd socket to
 be activated
   - update tests to execute key addition fully with less things stubbed
 out with mock
   - stop using apt-key for installing keys
   - dirmngr is a heavy dependency and not used, and it is hard to pass
 proxy information to it when invoking gpg from a non-standard homedir
   - deprecate --keyserver option, making HTTPS access to
 keyserver.ubuntu.com required
   - LP: #1755192, LP: #1713962, LP: #1699086, LP: #1510220, LP: #1433761,
 LP: #1395321, LP: #1312267

 -- Dimitri John Ledkov   Mon, 02 Apr 2018 10:19:34
+0100

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

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

Title:
  apt-add-repository times out behind proxy

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  1) Release
  Ubuntu 17.04

  2) Package
  software-properties-common: 0.96.24.13

  3) What you expected to happen
  GPG key processed successfully
  e.g.

  $ sudo -E add-apt-repository ppa:whatever

  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keybox '/tmp/tmpby0unfol/pubring.gpg' created
  gpg: /tmp/tmpby0unfol/trustdb.gpg: trustdb created
  gpg: key XX: public key "Launchpad VLC" imported
  gpg: no ultimately trusted keys found
  gpg: Total number processed: 1
  gpg:   imported: 1
  OK

  4) What happened instead
  Timeout on gpg command
  e.g.

  $ sudo -E add-apt-repository ppa:whatever

  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keybox '/tmp/xxx/pubring.gpg' created
  Error: retrieving gpg key timed out.

  5) Additional info

  - OK on Ubuntu 16.04.3 LTS, software-properties-common: 0.96.20.7
  - Network Proxy is set via GUI, applied system wide

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1713962/+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 1758841] Re: virt-manager: Light grey menu items on light grey background are barely readable

[ChristianEhrhardt]

At least I can confirm the issue with a KVM install of
http://cdimage.ubuntu.com/daily-live/current/bionic-desktop-amd64.iso

Tried virt-manager in there, and see the reported readbility issue.

But I installed gnome-tweaks and ALL themes except ambience work juts fine.
So the default of Adwaita, good, any as I said all else good.

For I'd much more consider it an issue in the latest "Ambience" Theme than 
virt-manager.
It might use a more uncommon thing, but since all others work it should be the 
theme right?

** Changed in: virt-manager (Ubuntu)
   Status: New => Confirmed

** Changed in: virt-manager (Ubuntu)
   Importance: Medium => Low

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

Title:
  virt-manager: Light grey menu items on light grey background are
  barely readable

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  New
Status in virt-manager package in Ubuntu:
  Confirmed

Bug description:
  With latest update of ubuntu-theme (16.10+18.04.20180322.3-0ubuntu1) menu 
items in the toolbar are barely readable (cf screenshot)
  Background should be dark. virt-manager is the only application I found with 
this issue so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: virt-manager 1:1.5.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 26 09:50:17 2018
  InstallationDate: Installed on 2014-07-15 (1349 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1758841/+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 1759846] Re: Incorrect test used for anacron being active

[Gordon Lack]

Actually
systemctl -q is-enabled anacron 2>/dev/null
works to, and is shorter (and more intuitive).

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

Title:
  Incorrect test used for anacron being active

Status in cron package in Ubuntu:
  New

Bug description:
  /etc/crontab uses

 test -x /usr/sbin/anacron

  for whether anacron is handling the daily/weekly/monthly cron jobs on a 
system.
  This means that if anacron is installed it is assumed to be running.
  However, this is a service, and can be disabled and since the package is 
installed by default it's simpler to just disable it on systems where you don't 
want it running rather then remove it.

  Changing the test to be:

  systemctl --no-pager is-enabled anacron 2>/dev/null

  (and changing the || to be &&, since the login is now reversed) caters
  for either case by checking what you really wish to know - is it
  active, not just installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: cron 3.0pl1-128ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Mar 29 13:33:47 2018
  InstallationDate: Installed on 2017-11-01 (147 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1759846/+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 1747460] Re: [MIR] py-macaroon-bakery, protobuf, pyrfc3339

[Matthias Klose]

closing the python-nacl task. already promoted.

** Changed in: python-nacl (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  [MIR] py-macaroon-bakery, protobuf, pyrfc3339

Status in protobuf package in Ubuntu:
  Invalid
Status in py-macaroon-bakery package in Ubuntu:
  Fix Released
Status in pyrfc3339 package in Ubuntu:
  Fix Released
Status in python-nacl package in Ubuntu:
  Fix Released

Bug description:
  py-macaroon-bakery
  ==

  1. Availability: all

  2. Rationale:
  Macaroons is a new form of authorization mechanism. The macaroon bakery 
builds on pymacaroons, which allows it working at a higher level.

  In order for MAAS (and other projects) to support macaroon based
  authentication, this needs to be in main. This will allow projects to
  support remote/centralized authentication based on macaroons.

  3. Security:
  No CVE's

  4. QA:
  0 bugs in debian/ubuntu

  5. UI standards:
  None

  6. Dependencies:

  Dependencies in universe:
   - python3-pymacaroons (MIR LP: #1746772)
   - python3-nacl
   - python3-protobuf
   - python3-rfc3339

  7. Standards:
  No lintian errors.

  Packaged with debhelper. Source format is 3.0 (quilt)

  Standards version: 4.4.1

  8. Maintenance:
  Easy.

  9. Background information:
  This is a required dependency to implement third party/centralized 
authentication alongside with pymacaroons. This is a new dependency that's 
required by MAAS.

  python3-protobuf
  ==

  1. Availability: any

  2. Rationale:
  Dependency of python3-macaroonbakery. The library from this same source 
package, libprotobuf10, is already in main.

  3. Security:
  No CVE's

  4. QA:
  protobuf source, 10 bugs in debian, 11 ubuntu

  5. UI standards:
  None

  6. Dependencies:
  All in main

  7. Standards:
  No lintian errors.

  Packaged with debhelper. Source format is 3.0 (quilt)

  Standards version: 3.9.8

  8. Maintenance:
  Easy.

  9. Background information:
  protobuf source already has binaries in main. This is just the python 
bindings that are required by macaroonbakery.

  rfc3339
  ==

  1. Availability: all

  2. Rationale:
  Dependency of python3-macaroonbakery.

  3. Security:
  No CVE's

  4. QA:
  0 bugs in debian/ubuntu

  5. UI standards:
  None

  6. Dependencies:
  All in main

  7. Standards:
  No lintian errors. 1 warning:
  W: pyrfc3339 source: ancient-standards-version 3.9.6 (released 2014-09-17) 
(current is 4.1.3)

  Packaged with debhelper. Source format is 3.0 (quilt)

  8. Maintenance:
  Easy.

  9. Background information:
  Parser and generator of RFC 3339-compliant timestamps. This is a dependency 
for python3-macaroonbakery.

  
  python-nacl
  ==

  1. Availability: any

  2. Rationale:
  Dependency of python3-macaroonbakery.

  3. Security:
  No CVE's

  4. QA:
  0 bugs in debian/ubuntu

  5. UI standards:
  None

  6. Dependencies:
  All in main

  7. Standards:
  No lintian errors.

  Uses standards version 3.9.8

  Packaged with debhelper. Source format is 3.0 (quilt)

  8. Maintenance:
  Easy.

  9. Background information:
  PyNaCl is a Python binding to the Networking and Cryptography library. This 
is a dependency for python3-macaroonbakery.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/1747460/+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 1758844] Re: gnome-software crashed with SIGSEGV in tcache_get() → _FcStrSetGrow → #3 → IA__FcStrSetAdd → IA__FcConfigParseAndLoad → FcConfigParseAndLoadDir → #7 → FcParseInclude

[Jean-Baptiste Lallement]

** Summary changed:

- gnome-software crashed with SIGSEGV in tcache_get()
+ gnome-software crashed with SIGSEGV in tcache_get() → _FcStrSetGrow → #3 → 
IA__FcStrSetAdd → IA__FcConfigParseAndLoad → FcConfigParseAndLoadDir → #7 → 
FcParseInclude → #9 → doContent → contentProcessor

** Information type changed from Private to Public

** Also affects: fontconfig (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  gnome-software crashed with SIGSEGV in tcache_get() → _FcStrSetGrow →
  #3 → IA__FcStrSetAdd → IA__FcConfigParseAndLoad →
  FcConfigParseAndLoadDir → #7 → FcParseInclude → #9 → doContent →
  contentProcessor

Status in fontconfig package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New

Bug description:
  Background crash report

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 26 07:05:25 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2015-07-04 (995 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f55edd0f207 <__GI___libc_malloc+407>:   mov
(%rdx),%rdi
   PC (0x7f55edd0f207) ok
   source "(%rdx)" (0x6e6f662f6374652f) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   tcache_get (tc_idx=2) at malloc.c:2943
   __GI___libc_malloc (bytes=48) at malloc.c:3050
   () at /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
   FcStrSetAdd () at /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
   FcConfigParseAndLoad () at /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
  Title: gnome-software crashed with SIGSEGV in tcache_get()
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (10 days ago)
  UserGroups: adm cdrom dip docker landscape libvirt libvirtd lpadmin lxd 
plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1758844/+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 1760848] [NEW] lxc-create can't create bionic container on xenial

[h]

Public bug reported:


I did run:

 lxc-create -t ubuntu -n ubu18.04 -- template-options -r bionic

which fails in the end:

(...)
Download complete
Copy /var/cache/lxc/bionic/rootfs-amd64 to /var/lib/lxc/ubu18.04/rootfs ... 
Copying rootfs to /var/lib/lxc/ubu18.04/rootfs ...
Generating locales (this might take a while)...
  de_DE.UTF-8... done
Generation complete.
mv: Aufruf von stat für '/var/lib/lxc/ubu18.04/rootfs/etc/init/ssh.conf' nicht 
möglich: Datei oder Verzeichnis nicht gefunden
lxc-create: lxccontainer.c: create_run_template: 1295 container creation 
template for ubu18.04 failed
lxc-create: tools/lxc_create.c: main: 318 Error creating container ubu18.04

I've seen that when creating a xenial container this is the point where
new sshd keys get created.

  dpkg -l 'lxc*'
||/ Name   Version
+++-==-==-
ii  lxc2.0.8-0ubuntu1~16.04.2 
ii  lxc-common 2.0.8-0ubuntu1~16.04.2 
ii  lxc-templates  2.0.8-0ubuntu1~16.04.2 
ii  lxc1   2.0.8-0ubuntu1~16.04.2 
ii  lxcfs  2.0.8-0ubuntu1~16.04.2 
un  lxcguest   
un  lxctl


  lsb_release -rd
Description:Ubuntu 16.04.4 LTS
Release:16.04

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "log of failing lxc-create"
   
https://bugs.launchpad.net/bugs/1760848/+attachment/5099757/+files/lxc-create.log

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

Title:
  lxc-create can't create bionic container on xenial

Status in lxc package in Ubuntu:
  New

Bug description:
  
  I did run:

   lxc-create -t ubuntu -n ubu18.04 -- template-options -r bionic

  which fails in the end:

  (...)
  Download complete
  Copy /var/cache/lxc/bionic/rootfs-amd64 to /var/lib/lxc/ubu18.04/rootfs ... 
  Copying rootfs to /var/lib/lxc/ubu18.04/rootfs ...
  Generating locales (this might take a while)...
de_DE.UTF-8... done
  Generation complete.
  mv: Aufruf von stat für '/var/lib/lxc/ubu18.04/rootfs/etc/init/ssh.conf' 
nicht möglich: Datei oder Verzeichnis nicht gefunden
  lxc-create: lxccontainer.c: create_run_template: 1295 container creation 
template for ubu18.04 failed
  lxc-create: tools/lxc_create.c: main: 318 Error creating container ubu18.04

  I've seen that when creating a xenial container this is the point
  where new sshd keys get created.

dpkg -l 'lxc*'
  ||/ Name   Version
  +++-==-==-
  ii  lxc2.0.8-0ubuntu1~16.04.2 
  ii  lxc-common 2.0.8-0ubuntu1~16.04.2 
  ii  lxc-templates  2.0.8-0ubuntu1~16.04.2 
  ii  lxc1   2.0.8-0ubuntu1~16.04.2 
  ii  lxcfs  2.0.8-0ubuntu1~16.04.2 
  un  lxcguest   
  un  lxctl

  
lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1760848/+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 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

[Iain Lane]

I've done a do-release-upgrade -d update with the plymouth from xenial-
proposed and it completed successfully. Not marking v-done, since the
test case in the description requires some additional testing.

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

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Confirmed
Status in ubuntu-mate-artwork package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  Confirmed
Status in budgie-artwork source package in Xenial:
  Confirmed
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Committed
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in budgie-artwork source package in Artful:
  Confirmed
Status in kubuntu-settings source package in Artful:
  Confirmed
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Confirmed
Status in ubuntu-mate-artwork source package in Artful:
  Confirmed

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Jarno Suni]

** Description changed:

  [Impact]
  
   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.
  
  [Test Case]
  
   1. Install kernel packages to be removed, mark them auto-installed and
  run apt's kernel hook script to make apt consider them autoremovable:
  
    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal
  
   2. Also downgrade a package to be upgraded:
  
-    sudo apt-get install -y ca-certificates=20160104ubuntu1
+    sudo apt-get install -y --allow-downgrades ca-
+ certificates=20160104ubuntu1
  
   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.
  
    sudo update-manager
  
   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.
  
   3. (unattended-upgrades, the fix comes in an update of u-u) Run
  unattended-upgrades manually and observe the removal of the
  autoremovable kernel packages:
  
    sudo unattended-upgrade -v
  
  [Regression Potential]
  
   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.
  
  [Other Info]
  
  The unattended-upgrades fix is uploaded with many other fixes and those
  may cause regressions in other areas in unattended-upgrades.
  
  [Original bug text]
  
  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.
  
  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.
  
  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Committed
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years 

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Jarno Suni]

Yes, it is good that update-manager can do removing, as that is what
most people use anyway.  linux-purge might still have some use e.g. if
for some reason /boot becomes full, or there are non-autoremovable
kernel packages (which may happen in 14.04 even with kernels installed
using update-manager Bug #1439769).

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Committed
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y ca-certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades, the fix comes in an update of u-u) Run
  unattended-upgrades manually and observe the removal of the
  autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Balint Reczey]

** Description changed:

  [Impact]
  
-  * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
-  * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
-  * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.
+  * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
+  * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
+  * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.
  
  [Test Case]
  
-  1. Install kernel packages to be removed, mark them auto-installed and
+  1. Install kernel packages to be removed, mark them auto-installed and
  run apt's kernel hook script to make apt consider them autoremovable:
  
-   sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
-   sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
-   sudo /etc/kernel/postinst.d/apt-auto-removal
+   sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
+   sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
+   sudo /etc/kernel/postinst.d/apt-auto-removal
  
-  2. Also downgrade a package to be upgraded:
+  2. Also downgrade a package to be upgraded:
  
-sudo apt-get install -y ca-certificates=20160104ubuntu1
+    sudo apt-get install -y ca-certificates=20160104ubuntu1
  
-  3. (update-manager). Run update-manager and observe that kernel
+  3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.
  
-   sudo update-manager
+   sudo update-manager
  
-  4. (update-manager) Click on Install Now and observe that the kernel
+  4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.
  
-  3. (unattended-upgrades) Run unattended-upgrades manually and observe
- the removal of the autoremovable kernel packages:
+  3. (unattended-upgrades, the fix comes in an update of u-u) Run
+ unattended-upgrades manually and observe the removal of the
+ autoremovable kernel packages:
  
-   sudo unattended-upgrade -v
+   sudo unattended-upgrade -v
  
  [Regression Potential]
  
-  The change may cause update-manager or unattanded-upgrades to remove
+  The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.
  
  [Other Info]
-  
- The unattended-upgrades fix is uploaded with many other fixes and those may 
cause regressions in other areas in unattended-upgrades.
+ 
+ The unattended-upgrades fix is uploaded with many other fixes and those
+ may cause regressions in other areas in unattended-upgrades.
  
  [Original bug text]
  
  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.
  
  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.
  
  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  

[Touch-packages] [Bug 1760818] [NEW] gedit and gnome-calculator transparency/graphics corruption issue

[Michał Sawicz]

Public bug reported:

In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator suffer
from a graphics issue where parts of their windows hold parts of
wallpaper or other windows' contents as background.

See attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180328-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  3 09:12:31 2018
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago)

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic visual-quality

** Attachment added: "o0coBMd.jpg"
   
https://bugs.launchpad.net/bugs/1760818/+attachment/5099621/+files/o0coBMd.jpg

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

Title:
  gedit and gnome-calculator transparency/graphics corruption issue

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator
  suffer from a graphics issue where parts of their windows hold parts
  of wallpaper or other windows' contents as background.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 09:12:31 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1760818/+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

Re: [Touch-packages] [Bug 1760810] Re: Non-pinned available package in -proposed not chosen

[Iain Lane]

On Tue, Apr 03, 2018 at 09:26:55AM -, Julian Andres Klode wrote:
> APT, by design, only picks candidate versions when installing
> dependencies, and the non-pinned proposed version is not the candidate.
> apt install foo/target has some logic to switch dependencies to target
> too, which works sometimes, but it's nothing that happens when using
> pinning.

Then this bug is about finding a way for autopkgtest to do what we mean
here. If there's a solution available in -proposed, we want to find it -
in this case it'd have been upgrading python3-distutils.

(In a perfect world we'd want to then tell proposed-migration to enforce
this constraint, but we aren't really ready for that.)

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  Non-pinned available package in -proposed not chosen

Status in Auto Package Testing:
  New
Status in apt package in Ubuntu:
  Invalid

Bug description:
  In autopkgtest we just had this situation:

  root@humorous-bullfrog:~# cat /etc/apt/preferences
  Package: *
  Pin: release a=bionic
  Pin-Priority: 990

  Package: python3.6
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-venv
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-stdlib
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-minimal
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-minimal
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-examples
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-dev
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-dev
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-testsuite
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: idle-python3.6
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-doc
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-dbg
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-dbg
  Pin: release a=bionic-proposed
  Pin-Priority: 995
  root@humorous-bullfrog:~# apt -oDebug::pkgProblemResolver=true full-upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU 
Ib >
  Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
Added python3-distutils:amd64 to the remove list
Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
  Investigating (0) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 7 as a solution to dh-python:amd64 15
Added python3-distutils:amd64 to the remove list
Fixing dh-python:amd64 via keep of python3-distutils:amd64
  Investigating (1) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU 
Ib >
  Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
Added python3-distutils:amd64 to the remove list
Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
  Investigating (1) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 7 as a solution to dh-python:amd64 15
Added python3-distutils:amd64 to the remove list
Fixing dh-python:amd64 via keep of python3-distutils:amd64
  Investigating (2) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU 
Ib >
  Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
Added python3-distutils:amd64 to the remove list
Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
  Investigating (2) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 22 as a solution to dh-python:amd64 15

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

[ChristianEhrhardt]

The actual seccomp fail is important.
Eventually it is a sandbox and we want to add exceptions after we know it has a 
valid use case.
As the above libvirt nss case which we added.

Trying the ppa you mentioned I can run just fine - so something is
special in your setup.

Please the exact details are important to Julian - see comment #17 - if
it is the same you could also try the suggested workaround via config in
comment #19.

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1732030/+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 1760810] Re: Non-pinned available package in -proposed not chosen

[Julian Andres Klode]

sbuild passes:

--solver aspcud -o APT::Solver::Strict-Pinning=false -o
'APT::Solver::aspcud::Preferences=-removed,-changed,-new,+sum(solution
,apt-pin)'


That probably works here too. I guess I'd try without, and then fall back to it 
if pure APT can't handle it.

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

Title:
  Non-pinned available package in -proposed not chosen

Status in Auto Package Testing:
  New
Status in apt package in Ubuntu:
  Invalid

Bug description:
  In autopkgtest we just had this situation:

  root@humorous-bullfrog:~# cat /etc/apt/preferences
  Package: *
  Pin: release a=bionic
  Pin-Priority: 990

  Package: python3.6
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-venv
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-stdlib
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-minimal
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-minimal
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-examples
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-dev
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-dev
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-testsuite
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: idle-python3.6
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-doc
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-dbg
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-dbg
  Pin: release a=bionic-proposed
  Pin-Priority: 995
  root@humorous-bullfrog:~# apt -oDebug::pkgProblemResolver=true full-upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU 
Ib >
  Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
Added python3-distutils:amd64 to the remove list
Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
  Investigating (0) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 7 as a solution to dh-python:amd64 15
Added python3-distutils:amd64 to the remove list
Fixing dh-python:amd64 via keep of python3-distutils:amd64
  Investigating (1) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU 
Ib >
  Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
Added python3-distutils:amd64 to the remove list
Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
  Investigating (1) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 7 as a solution to dh-python:amd64 15
Added python3-distutils:amd64 to the remove list
Fixing dh-python:amd64 via keep of python3-distutils:amd64
  Investigating (2) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU 
Ib >
  Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
Added python3-distutils:amd64 to the remove list
Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
  Investigating (2) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 22 as a solution to dh-python:amd64 15
Removing dh-python:amd64 rather than change python3-distutils:amd64
  Investigating (3) python3:amd64 < 3.6.4-1 @ii mK Ib >
  Broken python3:amd64 Depends on dh-python:amd64 < 3.20180325ubuntu2 @ii mR >
Considering dh-python:amd64 22 as a solution to python3:amd64 40
Added dh-python:amd64 to the remove list
Fixing python3:amd64 via keep of dh-python:amd64
  Investigating (3) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 22 as a solution to dh-python:amd64 40
Added python3-distutils:amd64 to the remove list
Fixing 

[Touch-packages] [Bug 1758841] Re: virt-manager: Light grey menu items on light grey background are barely readable

[ChristianEhrhardt]

I (for virt-manager) are not GTKxperienced enough to even know what to try :-/
If I understand you correctly it is picking up the change to the font color but 
not the background color - is that right?

virt-manager mostly uses gir from "Source: gtk+3.0" for display.
But that should be working.

If there are experienced desktop tips what should be tried please let me
know.

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

Title:
  virt-manager: Light grey menu items on light grey background are
  barely readable

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  New
Status in virt-manager package in Ubuntu:
  New

Bug description:
  With latest update of ubuntu-theme (16.10+18.04.20180322.3-0ubuntu1) menu 
items in the toolbar are barely readable (cf screenshot)
  Background should be dark. virt-manager is the only application I found with 
this issue so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: virt-manager 1:1.5.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 26 09:50:17 2018
  InstallationDate: Installed on 2014-07-15 (1349 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1758841/+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 1760824] [NEW] mlx4 modprobe dep not needed by default

[Tobias Urdin]

Public bug reported:

My machine:
Ubuntu 16.04.4 Xenial
4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 
x86_64 GNU/Linux

Changes were made in bug [1] to fix an issue where mlx4_en was not loaded.
The following change was added:

cat /etc/modprobe.d/mlx4.conf
# mlx4_core should load mlx4_en (LP: #1115710).
softdep mlx4_core post: mlx4_en

This change is no longer needed since [2] also see testing in [3]

Without /etc/modprobe.d/mlx4.conf and having following in 
/etc/modprobe.d/mlx4_core.conf
options mlx4_core log_num_mgm_entry_size=-1

# lsmod | grep mlx
mlx4_en   110592  0
vxlan  49152  2 i40e,mlx4_en
ptp20480  3 igb,i40e,mlx4_en
mlx4_core 286720  1 mlx4_en

# ethtool -k enp59s0 | grep tx-udp
tx-udp_tnl-segmentation: on

[1] https://bugs.launchpad.net/maas/+bug/1115710
[2] https://bugs.launchpad.net/maas/+bug/1115710/comments/21
[3] https://bugs.launchpad.net/maas/+bug/1115710/comments/22

** Affects: kmod (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  mlx4 modprobe dep not needed by default

Status in kmod package in Ubuntu:
  New

Bug description:
  My machine:
  Ubuntu 16.04.4 Xenial
  4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 
x86_64 GNU/Linux

  Changes were made in bug [1] to fix an issue where mlx4_en was not loaded.
  The following change was added:

  cat /etc/modprobe.d/mlx4.conf
  # mlx4_core should load mlx4_en (LP: #1115710).
  softdep mlx4_core post: mlx4_en

  This change is no longer needed since [2] also see testing in [3]

  Without /etc/modprobe.d/mlx4.conf and having following in 
/etc/modprobe.d/mlx4_core.conf
  options mlx4_core log_num_mgm_entry_size=-1

  # lsmod | grep mlx
  mlx4_en   110592  0
  vxlan  49152  2 i40e,mlx4_en
  ptp20480  3 igb,i40e,mlx4_en
  mlx4_core 286720  1 mlx4_en

  # ethtool -k enp59s0 | grep tx-udp
  tx-udp_tnl-segmentation: on

  [1] https://bugs.launchpad.net/maas/+bug/1115710
  [2] https://bugs.launchpad.net/maas/+bug/1115710/comments/21
  [3] https://bugs.launchpad.net/maas/+bug/1115710/comments/22

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1760824/+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 1115710] Re: Mellanox mlx4_en network driver is not automatically loaded

[Tobias Urdin]

Must have had a brain freeze or something, I rebuild my initramfs with belo and 
it worked after boot.
update-initramfs -k `uname -r` -c

The point that the default /etc/modprobe.d/mlx4.conf should be removed
still stands, I'll report a new bug to kmod I guess.

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

Title:
  Mellanox mlx4_en network driver is not automatically loaded

Status in MAAS:
  Invalid
Status in kmod package in Ubuntu:
  Fix Released
Status in module-init-tools package in Ubuntu:
  Invalid
Status in module-init-tools source package in Precise:
  Triaged
Status in module-init-tools source package in Quantal:
  Won't Fix
Status in kmod source package in Raring:
  Fix Released

Bug description:
  The Mellanox Ethernet card module is not being loaded in the ephemeral
  images, which causes enlisting/commissioning to fail to boot the root
  image from ISCSI, given that the interface is not loaded.

  Related bugs:
   * bug 1015339: installer initrd missing kernel modules for Mellanox ConnectX 
HCA Ethernet

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1115710/+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 1115710] Re: Mellanox mlx4_en network driver is not automatically loaded

[Tobias Urdin]

Ping, this migt be causing issue when using the mlx4 driver today.

Ubuntu 16.04 Xenial
4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 
x86_64 GNU/Linux

The following file is no longer needed, mlx4_core and mlx4_en will be loaded 
properly automatic
cat /etc/modprobe.d/mlx4.conf 
# mlx4_core should load mlx4_en (LP: #1115710).
softdep mlx4_core post: mlx4_en

Another issue I have, I cannot enable VXLAN offloading on boot.
I have tried:

* Keeping /etc/modprobe.d/mlx4.conf and adding "options mlx4_core 
log_num_mgm_entry_size=-1" to start of file
* Keeping /etc/modprobe.d/mlx4.conf and adding "options mlx4_core 
log_num_mgm_entry_size=-1" to end of file
* Remove all lines in /etc/modprobe.d/mlx4.conf except for "options mlx4_core 
log_num_mgm_entry_size=-1"
* Keeping /etc/modprobe.d/mlx4.conf and adding "options mlx4_core 
log_num_mgm_entry_size=-1" to /etc/modprobe.d/mlx4_core.conf
* Removing /etc/modprobe.d/mlx4.conf and adding "options mlx4_core 
log_num_mgm_entry_size=-1" to /etc/modprobe.d/mlx4_core.conf

None of these makes the VXLAN offloading capability available.
ethtool -k enp59s0 | grep tx-udp
tx-udp_tnl-segmentation: off [fixed]

But if I remove and load the driver manually after boot and add it again to 
works.
modprobe -r mlx4_en
modprobe -r mlx4_core

(after I load modules manually below I also get the mlx4_ib module, so
the process to remove again involves unloading mlx4_en and mlx4_ib
before unloading mlx4_core)

* Keeping /etc/modprobe.d/mlx4.conf and adding "options mlx4_core 
log_num_mgm_entry_size=-1" to start of file
modprobe mlx4_en
ethtool -k enp59s0 | grep tx-udp
tx-udp_tnl-segmentation: on

* Keeping /etc/modprobe.d/mlx4.conf and adding "options mlx4_core 
log_num_mgm_entry_size=-1" to end of file
modprobe mlx4_en
ethtool -k enp59s0 | grep tx-udp
tx-udp_tnl-segmentation: on

* Remove all lines in /etc/modprobe.d/mlx4.conf except for "options mlx4_core 
log_num_mgm_entry_size=-1"
modprobe mlx4_en
ethtool -k enp59s0 | grep tx-udp
tx-udp_tnl-segmentation: on

* Removing /etc/modprobe.d/mlx4.conf and adding "options mlx4_core 
log_num_mgm_entry_size=-1" to /etc/modprobe.d/mlx4_core.conf
modprobe mlx4_en
ethtool -k enp59s0 | grep tx-udp
tx-udp_tnl-segmentation: on

On boot the following modules is loaded:
# lsmod | grep mlx
mlx4_en   110592  0
vxlan  49152  2 i40e,mlx4_en
mlx4_core 286720  1 mlx4_en
ptp20480  3 igb,i40e,mlx4_en

When I modprobe manually the following modules is loaded:
# lsmod | grep mlx
mlx4_ib   151552  0
mlx4_en   110592  0
mlx4_core 286720  2 mlx4_en,mlx4_ib
ib_sa  36864  3 rdma_cm,ib_cm,mlx4_ib
ib_mad 49152  3 ib_cm,ib_sa,mlx4_ib
ib_core   106496  7 rdma_cm,ib_cm,ib_sa,iw_cm,mlx4_ib,ib_mad,ib_iser
vxlan  49152  2 i40e,mlx4_en
ptp20480  3 igb,i40e,mlx4_en


What could cause this blockage that the driver is not loaded properly with the 
options on boot?
Best regards

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

Title:
  Mellanox mlx4_en network driver is not automatically loaded

Status in MAAS:
  Invalid
Status in kmod package in Ubuntu:
  Fix Released
Status in module-init-tools package in Ubuntu:
  Invalid
Status in module-init-tools source package in Precise:
  Triaged
Status in module-init-tools source package in Quantal:
  Won't Fix
Status in kmod source package in Raring:
  Fix Released

Bug description:
  The Mellanox Ethernet card module is not being loaded in the ephemeral
  images, which causes enlisting/commissioning to fail to boot the root
  image from ISCSI, given that the interface is not loaded.

  Related bugs:
   * bug 1015339: installer initrd missing kernel modules for Mellanox ConnectX 
HCA Ethernet

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1115710/+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 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

[Sean Davis]

If this bug does not affect Ubuntu directly, this is a list of shared
differences that Ubuntu MATE and Xubuntu have with Ubuntu. Hopefully
this can help identify where the issue exists.

** Attachment added: "Differences with Ubuntu"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+attachment/5099620/+files/ubuntu_vs_mate_and_xubuntu.txt

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1754836/+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 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue

[Daniel van Vugt]

I can't reproduce this on 18.04... can anyone else?

** Tags added: visual-quality

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

Title:
  gedit and gnome-calculator transparency/graphics corruption issue

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator
  suffer from a graphics issue where parts of their windows hold parts
  of wallpaper or other windows' contents as background.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 09:12:31 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1760818/+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 1732030] Re: 'apt update' dies with seccomp error

[Jimmy Olsen]

Idk if I did has something to do with the bug itself. I noticed this bug
happened just after when I added PPA as seen from
https://www.omgubuntu.co.uk/2018/03/gimp-2-10-release-candidate-released
and ran "sudo apt update && sudo apt upgrade" commands. Once it was
removed,no error was shown anymore.

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

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1732030/+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 1758314] Re: Open new windows in the middle of the screen

[Didier Roche]

** Package changed: mutter (Ubuntu) => ubuntu-settings (Ubuntu)

** Changed in: ubuntu-settings (Ubuntu)
 Assignee: (unassigned) => Didier Roche (didrocks)

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

Title:
  Open new windows in the middle of the screen

Status in ubuntu-settings package in Ubuntu:
  Triaged

Bug description:
  When opening a new new window in gnome-shell it comes up in the top
  left corner. This is not desireable since it creates a lot of "black"
  there in dark themes and it has some pixels of a bright background
  theme shining through due to window headerbar being rounded.

  Gnome solved the "pixels shining through thing" upstream by having
  that corner rounded in a gnome-session. But this is not feasible in
  the Ubuntu session because the Ubuntu dock is there and the corner
  cannot be rounded.

  Having new windows come up in the middle of the screen would be more
  pleasing visually: It doesn't look crammed (dark headerbar + dark top
  bar) by default and the background pixels shine only "through" if you
  choose to drag the window to that corner.

  On the Ubuntu Community HUB Carlos Lobrano suggested to toggle a
  switch in Mutter to change the default position for new windows. It's
  center-new-windows under /org/gnome/mutter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1758314/+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 1760810] Re: Non-pinned available package in -proposed not chosen

[Julian Andres Klode]

APT, by design, only picks candidate versions when installing
dependencies, and the non-pinned proposed version is not the candidate.
apt install foo/target has some logic to switch dependencies to target
too, which works sometimes, but it's nothing that happens when using
pinning.

** Changed in: apt (Ubuntu)
   Status: New => Invalid

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

Title:
  Non-pinned available package in -proposed not chosen

Status in Auto Package Testing:
  New
Status in apt package in Ubuntu:
  Invalid

Bug description:
  In autopkgtest we just had this situation:

  root@humorous-bullfrog:~# cat /etc/apt/preferences
  Package: *
  Pin: release a=bionic
  Pin-Priority: 990

  Package: python3.6
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-venv
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-stdlib
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-minimal
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-minimal
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-examples
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-dev
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-dev
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-testsuite
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: idle-python3.6
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-doc
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-dbg
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-dbg
  Pin: release a=bionic-proposed
  Pin-Priority: 995
  root@humorous-bullfrog:~# apt -oDebug::pkgProblemResolver=true full-upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU 
Ib >
  Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
Added python3-distutils:amd64 to the remove list
Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
  Investigating (0) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 7 as a solution to dh-python:amd64 15
Added python3-distutils:amd64 to the remove list
Fixing dh-python:amd64 via keep of python3-distutils:amd64
  Investigating (1) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU 
Ib >
  Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
Added python3-distutils:amd64 to the remove list
Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
  Investigating (1) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 7 as a solution to dh-python:amd64 15
Added python3-distutils:amd64 to the remove list
Fixing dh-python:amd64 via keep of python3-distutils:amd64
  Investigating (2) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU 
Ib >
  Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
Added python3-distutils:amd64 to the remove list
Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
  Investigating (2) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 22 as a solution to dh-python:amd64 15
Removing dh-python:amd64 rather than change python3-distutils:amd64
  Investigating (3) python3:amd64 < 3.6.4-1 @ii mK Ib >
  Broken python3:amd64 Depends on dh-python:amd64 < 3.20180325ubuntu2 @ii mR >
Considering dh-python:amd64 22 as a solution to python3:amd64 40
Added dh-python:amd64 to the remove list
Fixing python3:amd64 via keep of dh-python:amd64
  Investigating (3) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 22 as a solution to 

Re: [Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Balint Reczey]

On Fri, Mar 30, 2018 at 3:12 PM, Jarno Suni <1624...@bugs.launchpad.net> wrote:
> Brian, I tested the update-manager version you told. It is true that
> update-manager removes the unused packages, but step 3. (unattended-
> upgrades) does not remove the unused kernels.
>
> I add failed tag as this bug is originally about unattended-upgrades.

Thanks for testing the fix and also thank you for preparing the
linux-purge script. I read it but integrating it to to current tools
would have been problematic and I hope you agree that the solution
finally used is minimally intrusive and achieves removing unused
kernels in a safe way.

The fix for unattended-upgrades is not uploaded yet but is available
Bionic and in the ppa:rbalint/scratch PPA if you would like to give it
a try.

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Committed
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

 sudo apt-get install -y ca-certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]
   
  The unattended-upgrades fix is uploaded with many other fixes and those may 
cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 

[Touch-packages] [Bug 1760810] [NEW] Non-pinned available package in -proposed not chosen

[Iain Lane]

Public bug reported:

In autopkgtest we just had this situation:

root@humorous-bullfrog:~# cat /etc/apt/preferences
Package: *
Pin: release a=bionic
Pin-Priority: 990

Package: python3.6
Pin: release a=bionic-proposed
Pin-Priority: 995

Package: python3.6-venv
Pin: release a=bionic-proposed
Pin-Priority: 995

Package: libpython3.6-stdlib
Pin: release a=bionic-proposed
Pin-Priority: 995

Package: python3.6-minimal
Pin: release a=bionic-proposed
Pin-Priority: 995

Package: libpython3.6-minimal
Pin: release a=bionic-proposed
Pin-Priority: 995

Package: libpython3.6
Pin: release a=bionic-proposed
Pin-Priority: 995

Package: python3.6-examples
Pin: release a=bionic-proposed
Pin-Priority: 995

Package: python3.6-dev
Pin: release a=bionic-proposed
Pin-Priority: 995

Package: libpython3.6-dev
Pin: release a=bionic-proposed
Pin-Priority: 995

Package: libpython3.6-testsuite
Pin: release a=bionic-proposed
Pin-Priority: 995

Package: idle-python3.6
Pin: release a=bionic-proposed
Pin-Priority: 995

Package: python3.6-doc
Pin: release a=bionic-proposed
Pin-Priority: 995

Package: python3.6-dbg
Pin: release a=bionic-proposed
Pin-Priority: 995

Package: libpython3.6-dbg
Pin: release a=bionic-proposed
Pin-Priority: 995
root@humorous-bullfrog:~# apt -oDebug::pkgProblemResolver=true full-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU Ib 
>
Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
  Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
  Added python3-distutils:amd64 to the remove list
  Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
Investigating (0) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii mR >
  Considering python3-distutils:amd64 7 as a solution to dh-python:amd64 15
  Added python3-distutils:amd64 to the remove list
  Fixing dh-python:amd64 via keep of python3-distutils:amd64
Investigating (1) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU Ib 
>
Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
  Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
  Added python3-distutils:amd64 to the remove list
  Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
Investigating (1) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii mR >
  Considering python3-distutils:amd64 7 as a solution to dh-python:amd64 15
  Added python3-distutils:amd64 to the remove list
  Fixing dh-python:amd64 via keep of python3-distutils:amd64
Investigating (2) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU Ib 
>
Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
  Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
  Added python3-distutils:amd64 to the remove list
  Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
Investigating (2) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii mR >
  Considering python3-distutils:amd64 22 as a solution to dh-python:amd64 15
  Removing dh-python:amd64 rather than change python3-distutils:amd64
Investigating (3) python3:amd64 < 3.6.4-1 @ii mK Ib >
Broken python3:amd64 Depends on dh-python:amd64 < 3.20180325ubuntu2 @ii mR >
  Considering dh-python:amd64 22 as a solution to python3:amd64 40
  Added dh-python:amd64 to the remove list
  Fixing python3:amd64 via keep of dh-python:amd64
Investigating (3) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii mR >
  Considering python3-distutils:amd64 22 as a solution to dh-python:amd64 40
  Added python3-distutils:amd64 to the remove list
  Fixing dh-python:amd64 via keep of python3-distutils:amd64
Investigating (4) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU Ib 
>
Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
  Considering python3-distutils:amd64 40 as a solution to 
libpython3.6-stdlib:amd64 22
  Removing libpython3.6-stdlib:amd64 rather than change python3-distutils:amd64
Investigating (4) python3.6:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU Ib >
Broken python3.6:amd64 Depends on libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 | 
3.6.5-3 @ii umR > (= 3.6.5-3)
  Considering libpython3.6-stdlib:amd64 40 as a solution to python3.6:amd64 21
  Removing python3.6:amd64 rather than change libpython3.6-stdlib:amd64
Investigating (4) 

[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

[Sean Davis]

Since it seemed like this issue was coming from bluez or blueman, I did
some package removal tests and was surprised by the results. These were
done in order, which all packages removed in the previous step still
removed in the following step.

1. Remove pulseaudio-module-bluetooth, no change.
2. Remove blueman, no change.
3. Remove bluez, bluez-cups, bluez-obexd, no change.
4. Autoremoved libbluetooth3 (brltty brltty-x11 libbluetooth3 network-manager 
network-manager-gnome network-manager-pptp network-manager-pptp-gnome), and 
still no change.

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Also causing the long time to desktop from try/install livesession
  dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:

  rfkill:

  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: 
  [1520681416.8951] Loaded device plugin: NMBluezManager
  (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-
  bluetooth.so)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1754836/+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 1758314] [NEW] Open new windows in the middle of the screen

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When opening a new new window in gnome-shell it comes up in the top left
corner. This is not desireable since it creates a lot of "black" there
in dark themes and it has some pixels of a bright background theme
shining through due to window headerbar being rounded.

Gnome solved the "pixels shining through thing" upstream by having that
corner rounded in a gnome-session. But this is not feasible in the
Ubuntu session because the Ubuntu dock is there and the corner cannot be
rounded.

Having new windows come up in the middle of the screen would be more
pleasing visually: It doesn't look crammed (dark headerbar + dark top
bar) by default and the background pixels shine only "through" if you
choose to drag the window to that corner.

On the Ubuntu Community HUB Carlos Lobrano suggested to toggle a switch
in Mutter to change the default position for new windows. It's center-
new-windows under /org/gnome/mutter

** Affects: ubuntu-settings (Ubuntu)
 Importance: Wishlist
 Status: Triaged

-- 
Open new windows in the middle of the screen
https://bugs.launchpad.net/bugs/1758314
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-settings in Ubuntu.

-- 
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 1652486] Re: mesa gpu lockup

[Bug Watch Updater]

** Changed in: mesa
   Status: Unknown => Fix Released

** Changed in: mesa
   Importance: Unknown => Medium

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

Title:
  mesa gpu lockup

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Yakkety:
  Fix Released

Bug description:
  package: mesa
  version: 11.2.0-1ubuntu2.2
  release: 16.04.1 / "Xenial"

  references:
  * https://bugs.freedesktop.org/show_bug.cgi?id=93649
  * https://cgit.freedesktop.org/mesa/mesa/commit/?id=6dc96de3

  symptoms:
  1. kernel reports "GPU lockup"
  2. kernel reports "GPU softreset"
  3. immediately frozen display
  4. eventual "INFO: task (kworker|Xorg)[/:0-9]+ blocked for more than 120 
seconds."
  5. computer hanging on system reboot requiring a forced power off

  Symptoms occur when playing Team Fortress 2.

  Attachments:
  1. mesa source package patch
  2. lspci output for video card (ie Radeon HD 7750)
  3. kernel log

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1652486/+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 1717015] Re: libc resolver stops searching domain search list after getting back NSEC record

[Dimitri John Ledkov]

1) one should not manually adjust search domains in /etc/resolv.conf
2) systemd-resolved should learn about search domains

 - for example, set search domains in /etc/systemd/resolved.conf if
nothing sets them on per link basis vai resolved dbus api or
networkd.network files.

3) /etc/resolv.conf should be a symlink to 
../run/systemd/resolve/stub-resolv.conf
4) ../run/systemd/resolve/stub-resolv.conf should be dynamically updated by 
resolved to contain the correct search domains
5) resolved does not send DNSSEC info to clients that do not support DNSSEC nor 
requested a DNSSEC response
6) if you expect DNSSEC validation from responses resolved provides, please 
manually enable DNSSEC in /etc/systemd/resolved.conf and all the relevant links 
via systemd-resolve cmdline tool (if not managed vai networkd.network units)

** Changed in: systemd (Ubuntu)
   Status: New => Incomplete

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

Title:
  libc resolver stops searching domain search list after getting back
  NSEC record

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Suppose that:

  1. you have a "search" line in your /etc/resolv.conf file;
  2. it has two domains in it; and
  3. the first of the two domains does DNSSEC, including returning NSEC records 
for nonexisting hosts.

  In this situation, when you try to look up a host name in the second
  domain without specifying the domain part of the host name, the libc
  resolver will stop after it gets back the NSEC record and report that
  the host name doesn't exist, rather than moving on to the second
  domain in the search list and searching for the host in that domain.

  See also https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1717014
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libc6 2.24-9ubuntu2.2
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Sep 13 16:00:45 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
  InstallationDate: Installed on 2016-08-09 (400 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: glibc
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (147 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717015/+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 1433761] Re: apt-key and add-apt-repository don't honor Acquire::http::Proxy

[Launchpad Bug Tracker]

** Branch linked: lp:~xnox/software-properties/gnupg-fix-all-the-things

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

Title:
  apt-key and add-apt-repository don't honor Acquire::http::Proxy

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  When setting the proxy server globally on the system for the APT
  package manager, add-apt-repository ignores the setting. This issue is
  present on all versions of Debian that I have tested.

  # cat /etc/apt/apt.conf.d/80proxy 
  Acquire::http::proxy "http://w.x.y.z:/;;

  # apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5A9A06AEF9CB8DB0
  Executing: gpg --ignore-time-conflict --no-options --no-default-keyring 
--homedir /tmp/tmp.TIa517Kcw8 --no-auto-check-trustdb --trust-model always 
--keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg --keyring 
/etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg --keyring 
/etc/apt/trusted.gpg.d/saltstack-salt.gpg --keyserver keyserver.ubuntu.com 
--recv-keys 5A9A06AEF9CB8DB0
  gpg: requesting key F9CB8DB0 from hkp server keyserver.ubuntu.com
  gpg: keyserver timed out
  gpg: keyserver receive failed: keyserver error

  This has serious repercussions. Unattended installs such as juju,
  maas, etc are all affected for anyone who is working behind a proxy.
  This is the case for most enterprise environments where such maas and
  juju setups will be tested out, and as such has great repercussions
  for Canonical as a viable supplier of OpenStack environments: if your
  product fails to install, you're not going to get the business.

  Considering that:

  * The setting to use already exists in /etc/apt/apt.conf and that all other 
tools use this correctly
  * The serious impact of this issue for downstream projects and Debian usage 
in the enterprise
  * The long time this issue has been standing and has affected people

  I suggest that this either

  1) be fixed, or
  2) the apt-key and add-apt-repository programs are renamed so that it is made 
clear they are not part of the APT suite of programs and therefor cannot be 
trusted to behave as if they were part of APT.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1433761/+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 1312267] Re: apt-add-repository, gpg, wget does not honour proxy inside sudo

[Launchpad Bug Tracker]

** Branch linked: lp:~xnox/software-properties/gnupg-fix-all-the-things

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

Title:
  apt-add-repository, gpg, wget does not honour proxy inside sudo

Status in software-properties package in Ubuntu:
  New

Bug description:
  On precise wget honours the proxy inside sudo:

  0 jan@tunis:/tmp$lsb_release -d
  Description:  Ubuntu 12.04.4 LTS
  0 jan@tunis:/tmp$sudo echo $http_proxy
  http://proxy.aims.ac.za:3128/
  0 jan@tunis:/tmp$sudo wget www.ubuntu.com
  --2014-04-24 18:01:02--  http://www.ubuntu.com/
  Resolving proxy.aims.ac.za (proxy.aims.ac.za)... 192.168.42.2
  Connecting to proxy.aims.ac.za (proxy.aims.ac.za)|192.168.42.2|:3128... 
connected.
  Proxy request sent, awaiting response... 200 OK
  Length: 17268 (17K) [text/html]
  Saving to: `index.html.1'

  100%[==>] 17 268  --.-K/s   in
  0,001s

  2014-04-24 18:01:02 (12,9 MB/s) - `index.html.1' saved [17268/17268]

  0 jan@tunis:/tmp$

  On trusty, it does not:

  ift@gift-laptop:~$ lsb_release -d
  Description:Ubuntu 14.04 LTS
  gift@gift-laptop:~$ sudo echo $http_proxy
  [sudo] password for gift:
  http://proxy.aims.ac.za:3128/
  gift@gift-laptop:~$ sudo wget www.ubuntu.com
  --2014-04-24 19:04:22--  http://www.ubuntu.com/
  Resolving www.ubuntu.com (www.ubuntu.com)... 91.189.89.103
  Connecting to www.ubuntu.com (www.ubuntu.com)|91.189.89.103|:80... failed: 
Connection refused.
  gift@gift-laptop:~$ 

  This is going to break most of the advice on the internet to e.g. sudo
  wget somesite/some-apt-key.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1312267/+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 1395321] Re: Adding ppa not working under proxy

[Launchpad Bug Tracker]

** Branch linked: lp:~xnox/software-properties/gnupg-fix-all-the-things

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

Title:
  Adding ppa not working under proxy

Status in software-properties package in Ubuntu:
  New

Bug description:
  In Ubuntu 13.10, PPA's could be added under proxy. But after that, i.e
  in 14.04, error comes like this

  Cannot add PPA: 'ppa:ppa name'.
  Please check that the PPA name or format is correct.

  apt works fine under proxy. But, repositories are not added. I have to
  use a non-proxified network to add repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1395321/+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 1510220] Re: add-apt-repository backtraces on PPA with utf8 characters

[Launchpad Bug Tracker]

** Branch linked: lp:~xnox/software-properties/gnupg-fix-all-the-things

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

Title:
  add-apt-repository backtraces on PPA with utf8 characters

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  On a brand new trusty container:

  root@apatest3:~# add-apt-repository ppa:ondrej/apache2
   This branch follows latest PHP packages as maintained by the Debian Apache2 
team.

  It also includes some widely used Apache 2 modules (if you need some
  other feel free to send me a request).

  If you need to stay with PHP 5 you can use the PHP repository:
  https://launchpad.net/~ondrej/+archive/php5

  BUGS: This PPA now has a issue tracker:
  https://deb.sury.org/pages/bugreporting.html

  PLEASE READ: If you like my work and want to give me a little motivation, 
please consider donating: https://deb.sury.org/pages/donate.html
   More info: https://launchpad.net/~ondrej/+archive/ubuntu/apache2
  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keyring `/tmp/tmprl8b6i1r/secring.gpg' created
  gpg: keyring `/tmp/tmprl8b6i1r/pubring.gpg' created
  gpg: requesting key E5267A6C from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmprl8b6i1r/trustdb.gpg: trustdb created
  gpg: key E5267A6C: public key "Launchpad PPA for Ond\xc5\x99ej Sur▒" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  Exception in thread Thread-1:
  Traceback (most recent call last):
File "/usr/lib/python3.4/threading.py", line 920, in _bootstrap_inner
  self.run()
File "/usr/lib/python3.4/threading.py", line 868, in run
  self._target(*self._args, **self._kwargs)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
687, in addkey_func
  func(**kwargs)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 370, 
in add_key
  return apsk.add_ppa_signing_key()
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 261, 
in add_ppa_signing_key
  tmp_export_keyring, signing_key_fingerprint, tmp_keyring_dir):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 210, 
in _verify_fingerprint
  got_fingerprints = self._get_fingerprints(keyring, keyring_dir)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 202, 
in _get_fingerprints
  output = subprocess.check_output(cmd, universal_newlines=True)
File "/usr/lib/python3.4/subprocess.py", line 605, in check_output
  output, unused_err = process.communicate(inputdata, timeout=timeout)
File "/usr/lib/python3.4/subprocess.py", line 936, in communicate
  stdout = _eintr_retry_call(self.stdout.read)
File "/usr/lib/python3.4/subprocess.py", line 487, in _eintr_retry_call
  return func(*args)
File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode
  return codecs.ascii_decode(input, self.errors)[0]
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 92: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-common 0.92.37.5
  ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  Date: Mon Oct 26 18:22:33 2015
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1510220/+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 1713962] Re: apt-add-repository times out behind proxy

[Launchpad Bug Tracker]

** Branch linked: lp:~xnox/software-properties/gnupg-fix-all-the-things

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

Title:
  apt-add-repository times out behind proxy

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  1) Release
  Ubuntu 17.04

  2) Package
  software-properties-common: 0.96.24.13

  3) What you expected to happen
  GPG key processed successfully
  e.g.

  $ sudo -E add-apt-repository ppa:whatever

  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keybox '/tmp/tmpby0unfol/pubring.gpg' created
  gpg: /tmp/tmpby0unfol/trustdb.gpg: trustdb created
  gpg: key XX: public key "Launchpad VLC" imported
  gpg: no ultimately trusted keys found
  gpg: Total number processed: 1
  gpg:   imported: 1
  OK

  4) What happened instead
  Timeout on gpg command
  e.g.

  $ sudo -E add-apt-repository ppa:whatever

  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keybox '/tmp/xxx/pubring.gpg' created
  Error: retrieving gpg key timed out.

  5) Additional info

  - OK on Ubuntu 16.04.3 LTS, software-properties-common: 0.96.20.7
  - Network Proxy is set via GUI, applied system wide

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1713962/+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 1699086] Re: add-apt-repository crashes on non-ascii names in PGP keys

[Launchpad Bug Tracker]

** Branch linked: lp:~xnox/software-properties/gnupg-fix-all-the-things

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

Title:
  add-apt-repository crashes on non-ascii names in PGP keys

Status in software-properties package in Ubuntu:
  New

Bug description:
  When adding the PHP 7.1 repo into Ubuntu 16.04 LTS I get the following
  error.

  Command;
  add-apt-repository ppa:ondrej/php -y

  Output;
  gpg: keyring `/tmp/tmprs_t5_d6/secring.gpg' created
  gpg: keyring `/tmp/tmprs_t5_d6/pubring.gpg' created
  gpg: requesting key E5267A6C from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmprs_t5_d6/trustdb.gpg: trustdb created
  gpg: key E5267A6C: public key "Launchpad PPA for Ond\xc5\x99ej Sur�" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  'ascii' codec can't decode byte 0xc5 in position 92: ordinal not in range(128)

  The command exits with code 1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1699086/+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 1755192] Re: Running add-apt-repository inside docker bionic container gives No such file or directory: 'S.gpg-agent.browser'

[Launchpad Bug Tracker]

** Branch linked: lp:~xnox/software-properties/gnupg-fix-all-the-things

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

Title:
  Running add-apt-repository inside docker bionic container gives No
  such file or directory: 'S.gpg-agent.browser'

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Bionic:
  Confirmed

Bug description:
  This used to work for Ubuntu 14.04 and 16.04.

  ```
  Step 5/7 : RUN add-apt-repository -y ppa:kernsuite/kern-dev
   ---> Running in 4d6412c3d237
  gpg: keybox '/tmp/tmpol6z8f79/pubring.gpg' created
  gpg: /tmp/tmpol6z8f79/trustdb.gpg: trustdb created
  gpg: key 813B0DC8B7D042E7: public key "Launchpad PPA for KERN suite" imported
  gpg: Total number processed: 1
  gpg:   imported: 1
  Warning: apt-key output should not be parsed (stdout is not a terminal)
  OK
  [Errno 2] No such file or directory: 'S.gpg-agent.browser'
  ```

  Dockerfile:

  ```
  FROM ubuntu:18.04
  MAINTAINER gijsmolen...@gmail.com
  RUN apt-get update
  RUN apt-get install -y software-properties-common
  RUN add-apt-repository -y ppa:kernsuite/kern-dev
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1755192/+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 1760190] Re: Useless icon themes installed

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  Useless icon themes installed

Status in humanity-icon-theme package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Humanity-Dark
  LoginIcons
  Ubuntu-mono-dark
  Ubuntu-mono-light
  Hicolor

  if i switch icons from these icons nothing happening.
  I think these icons are no longer used in ubuntu.

  And DMZ-Black, DMZ-White listing in icons

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1760190/+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 1760190] Re: Useless icon themes installed

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: humanity-icon-theme (Ubuntu)
   Status: New => Confirmed

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

Title:
  Useless icon themes installed

Status in humanity-icon-theme package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Humanity-Dark
  LoginIcons
  Ubuntu-mono-dark
  Ubuntu-mono-light
  Hicolor

  if i switch icons from these icons nothing happening.
  I think these icons are no longer used in ubuntu.

  And DMZ-Black, DMZ-White listing in icons

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1760190/+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 1756031] Re: openssh-server doesn't accept aes256-cbc key

[Colin Watson]

Indeed.  PuTTY 0.62 and earlier had a habit of generating slightly short
keys sometimes.

This is unlikely to change in OpenSSH - the minimum key size is only
likely to increase over time.  I'd strongly suggest just generating a
2048-bit key, since SSH keys are usually pretty easy to roll over.

** Changed in: openssh (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  openssh-server doesn't accept aes256-cbc key

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  I am using putty connection with RSA key cached in pageant and want to
  login without password.

  Private key on windows:
  PuTTY-User-Key-File-2: ssh-rsa
  Encryption: aes256-cbc
  ...

  On ubuntu there is public key in .ssh/authorized_keys
  ssh-rsa B3Nz...JBjQ== palo@winpgnotas

  This key works well in ubuntu versions 14.04...17.10
  When I tried 18.04 beta, I am getting sshd error:
  mar 15 10:26:21 ubox sshd[5205]: error: userauth_pubkey: could not parse key: 
Invalid key length [preauth]
  and I have to provide password.

  I've found that aes256-cbc is not in the list of allowed ciphers by default, 
so I added
  Ciphers +aes256-cbc
  to /etc/ssh/sshd_config
  (and verified with nmap --script ssh2-enum-algos -sV -p 22 127.0.0.1)
  but the sshd error remains.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Thu Mar 15 10:03:14 2018
  InstallationDate: Installed on 2018-03-12 (2 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1756031/+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 1760190] Re: Useless icon themes

[Daniel van Vugt]

** This bug is no longer a duplicate of bug 1760201
   ubuntu 18.04 GDM - missing icons and letters

** Also affects: humanity-icon-theme (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Useless icon themes
+ Useless icon themes installed

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

Title:
  Useless icon themes installed

Status in humanity-icon-theme package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Humanity-Dark
  LoginIcons
  Ubuntu-mono-dark
  Ubuntu-mono-light
  Hicolor

  if i switch icons from these icons nothing happening.
  I think these icons are no longer used in ubuntu.

  And DMZ-Black, DMZ-White listing in icons

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1760190/+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 1759601] Re: [UIFe] 18.04 LTS Bionic Beaver Mascot

[Jean-Baptiste Lallement]

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Invalid

** Changed in: ubuntu-themes
   Status: New => Invalid

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

Title:
  [UIFe] 18.04 LTS Bionic Beaver Mascot

Status in Ubuntu theme:
  Invalid
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  The mascots for this release needed adding to the welcome page of the
  slideshow.  The final versions of the mascots arrived after UIF and I
  updated the slideshow yesterday.

  As part of that updated I changed the string describing what software
  was available to include mention of the snap store.  Since snaps are
  core component of the desktop and GNOME Software (promoted snaps
  appearing on the front page of Software for example) I think this is
  an important change.

  The string changes are:

  -Say goodbye to searching the web for new software. With access to
  the Ubuntu Software Store, you can find and install new apps with
  ease. Just type in what you’re looking for, or explore categories such
  as Science, Education and Games, alongside helpful reviews from other
  users.

  +Say goodbye to searching the web for new software. With access to
  the Snap Store and the Ubuntu software archive, you can find and
  install new apps with ease. Just type in what you’re looking for, or
  explore categories such as Games, Graphics & Photography and
  Productivity, alongside helpful reviews from other users.

  
  Post to doc-team: 
https://lists.ubuntu.com/archives/ubuntu-doc/2018-March/020580.html
  Post to translators: 
https://lists.ubuntu.com/archives/ubuntu-translators/2018-March/007454.html

  
  Beavers and branch attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1759601/+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 1760190] Re: Useless icon themes installed

[Daniel van Vugt]

** Changed in: humanity-icon-theme (Ubuntu)
   Importance: Undecided => Low

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Useless icon themes installed

Status in humanity-icon-theme package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Humanity-Dark
  LoginIcons
  Ubuntu-mono-dark
  Ubuntu-mono-light
  Hicolor

  if i switch icons from these icons nothing happening.
  I think these icons are no longer used in ubuntu.

  And DMZ-Black, DMZ-White listing in icons

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1760190/+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 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[Will Cooke]

** Tags added: rls-bb-incoming

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Confirmed
Status in laptop-mode-tools source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send 

[Touch-packages] [Bug 1760801] Re: package python3-dbus 1.2.0-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python3-dbus 1.2.0-3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 127

Status in dbus-python package in Ubuntu:
  New

Bug description:
  this error appeared during Ubuntu startup

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-dbus 1.2.0-3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Mar 26 14:45:49 2018
  DuplicateSignature:
   package:python3-dbus:1.2.0-3
   Setting up python3-apt (1.1.0~beta1ubuntu0.16.04.1) ...
   /var/lib/dpkg/info/python3-apt.postinst: 6: 
/var/lib/dpkg/info/python3-apt.postinst: py3compile: not found
   dpkg: error processing package python3-apt (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2018-03-07 (26 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: dbus-python
  Title: package python3-dbus 1.2.0-3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-python/+bug/1760801/+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 1760801] [NEW] package python3-dbus 1.2.0-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[Dmytro Grendach]

Public bug reported:

this error appeared during Ubuntu startup

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python3-dbus 1.2.0-3
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Mon Mar 26 14:45:49 2018
DuplicateSignature:
 package:python3-dbus:1.2.0-3
 Setting up python3-apt (1.1.0~beta1ubuntu0.16.04.1) ...
 /var/lib/dpkg/info/python3-apt.postinst: 6: 
/var/lib/dpkg/info/python3-apt.postinst: py3compile: not found
 dpkg: error processing package python3-apt (--configure):
  subprocess installed post-installation script returned error exit status 127
ErrorMessage: subprocess installed post-installation script returned error exit 
status 127
InstallationDate: Installed on 2018-03-07 (26 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: dbus-python
Title: package python3-dbus 1.2.0-3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dbus-python (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package python3-dbus 1.2.0-3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 127

Status in dbus-python package in Ubuntu:
  New

Bug description:
  this error appeared during Ubuntu startup

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-dbus 1.2.0-3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Mar 26 14:45:49 2018
  DuplicateSignature:
   package:python3-dbus:1.2.0-3
   Setting up python3-apt (1.1.0~beta1ubuntu0.16.04.1) ...
   /var/lib/dpkg/info/python3-apt.postinst: 6: 
/var/lib/dpkg/info/python3-apt.postinst: py3compile: not found
   dpkg: error processing package python3-apt (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2018-03-07 (26 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: dbus-python
  Title: package python3-dbus 1.2.0-3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-python/+bug/1760801/+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 1760371] Re: LightDM and GDM fail to start after update in virtualbox-guest-x11

[Shepherd King]

Apparently, I've had VirtualBox guest utilities installed on my host
system which you are generally just supposed to run on the guest. This
issue only occurred when the package was updated. After trial and error,
I've found that the offending package is virtualbox-guest-x11:amd64
(5.1.34-dfsg-0ubuntu1.16.04.2), none of the other virtualbox-guest
packages cause this problem.

** Summary changed:

- LightDM and GDM fail to start after systemd update in VirtualBox guest
+ LightDM and GDM fail to start after update in virtualbox-guest-x11

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

Title:
  LightDM and GDM fail to start after update in virtualbox-guest-x11

Status in lightdm package in Ubuntu:
  New

Bug description:
  1) Output of lsb_release -rd:
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04

  2) Output of apt-cache policy lightdm:
  lightdm:
Installed: 1.18.3-0ubuntu1.1
Candidate: 1.18.3-0ubuntu1.1
Version table:
   *** 1.18.3-0ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.18.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) What I expected to happen:
  - Expected the display manager to take me to the lightdm user login screen.

  4) What happened instead:
  - lightdm made 5 attempts to start before failing. Failure messages were 
"failed to start Detect the available GPUs and deal with any system changes" 
and "Failed to start Light Display Manager".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Mar 31 17:43:08 2018
  InstallationDate: Installed on 2015-11-23 (859 days ago)
  InstallationMedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2017-01-18 (437 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1760371/+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 1748844] Re: hud-service crash with qmessageLogger::fatal() reported at login

[Thomas A. F. Thorne]

Happened again today.  Raised #1760792 this morning to see if the trace
will work.  If it does not I shall try adding more -dev packages to see
if the backtrace can be brought about.

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

Title:
  hud-service crash with qmessageLogger::fatal() reported at login

Status in hud package in Ubuntu:
  New

Bug description:
  I start up my Ubuntu 16.04 machine and immediately after loginning in
  to the GUI I get a crash report about the hub-service.  Often this is
  followed by one or two other reports but not today.

  Today I followed the instructions on: 
https://help.ubuntu.com/community/ReportingBugs 
  `enabled=1` was already set in /etc/default/apport but I had not set `# 
'problem_types': ['Bug', 'Package'],` in /etc/apport/crashdb.conf until this 
morning.  This had the effect of a bug report appearing to be sent in the 
background but no launchpad page opening.  After setting both of the above I 
did `ubuntu-bug hud` on the command line to generate this report.  

  This PC was a fresh install a few months ago.  As far as I can recall
  it has been generating the crash report message for most of that time.

  It would be nice if I could at least silence the error.  Ideally I
  would like to fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hud 14.10+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 12 09:11:35 2018
  InstallationDate: Installed on 2017-11-16 (87 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: hud
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.hud.log:
   This application failed to start because it could not find or load the Qt 
platform plugin "minimal"
   in "".
   
   Reinstalling the application may fix this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1748844/+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 1732970] Re: Remove cordova-ubuntu-3.4, qtfeedback-opensource-src, qtsystems-opensource-src from archive

[Dmitry Shachnev]

Marius: these packages were dead and unmaintained both in Ubuntu and
upstream. For qtfeedback and qtsystems, the only release (5.0.0 beta 1)
was six years ago (in 2012). Also they were not present in Debian.

If you are willing to maintain them, feel free to reintroduce them, but
to get it right, you will need to synchronize your work with both
upstream and Debian.

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

Title:
  Remove cordova-ubuntu-3.4, qtfeedback-opensource-src, qtsystems-
  opensource-src from archive

Status in cordova-ubuntu-3.4 package in Ubuntu:
  Fix Released
Status in qtfeedback-opensource-src package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  cordova-ubuntu is dead upstream (https://github.com/apache/cordova-
  ubuntu had last commit in Oct 2016), Ubuntu packaging has no active
  maintainer and has not been updated since 2014.

  I have talked to Alberto Mardegan on IRC, he confirmed that it should be safe 
to remove it:
  https://irclogs.ubuntu.com/2017/11/17/%23ubuntu-devel.html#t18:43

  qtfeedback-opensource-src and qtsystems-opensource-src are libraries
  which have never become part of official Qt releases, and their only
  user in Ubuntu was cordova-ubuntu-3.4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cordova-ubuntu-3.4/+bug/1732970/+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 1721378] Re: /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-upgrade@1550:main:get_dpkg_log_content:decode

[Michael Arlt]

It would be nice if "importance" can be rated high because the automatic
patching process is currently not working -> security

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

Title:
  /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-
  upgrade@1550:main:get_dpkg_log_content:decode

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.93.1ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/9cc4adbd103ea3f15d6342d3cbb048179054885d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1721378/+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 1760366] Re: [regression] Terminal titlebars are too tall

[Daniel van Vugt]

Correction:

1. Please run:  apport-collect 1760366

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

Title:
  [regression] Terminal titlebars are too tall

Status in Ubuntu theme:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  It seems like change messed with the padding on the titlebar buttons
  (see attached screenshot):

  https://code.launchpad.net/~3v1n0/ubuntu-themes/windowbuttons-bg-and-
  padding

  Please go back to the way it was before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1760366/+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 1760366] Re: Titlebars are too tall

[Daniel van Vugt]

Sorry about that. I can't seem to reproduce the issue with Terminal...

Please:

1. Run 'ubuntu-bug 1760366' to help us get more information; and

2. Attach a larger screenshot of the whole Terminal window.

** Changed in: ubuntu-themes
   Status: Won't Fix => Incomplete

** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- Titlebars are too tall
+ Terminal titlebars are too tall

** Summary changed:

- Terminal titlebars are too tall
+ [regression] Terminal titlebars are too tall

** Tags added: regression

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

Title:
  [regression] Terminal titlebars are too tall

Status in Ubuntu theme:
  Incomplete
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  It seems like change messed with the padding on the titlebar buttons
  (see attached screenshot):

  https://code.launchpad.net/~3v1n0/ubuntu-themes/windowbuttons-bg-and-
  padding

  Please go back to the way it was before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1760366/+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 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

[Steve Langasek]

** Description changed:

  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.
  
  [Test case]
- 1. Install plymouth-themes-ubuntu-text from artful-proposed.
+ 1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.
  
  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.
  
  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not strong
  confirmation that the bug is fixed.
- 
  
  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04
  
  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (0 days ago)
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.

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

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Confirmed
Status in ubuntu-mate-artwork package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  Confirmed
Status in budgie-artwork source package in Xenial:
  Confirmed
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Committed
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  

[Touch-packages] [Bug 1758498] Re: perl crashed with SIGABRT in _dbus_abort()

[Niels Erik Jensen]

i have this 3g modem that works but this not show up in top bar

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

Title:
  perl crashed with SIGABRT in _dbus_abort()

Status in perl package in Ubuntu:
  Confirmed

Bug description:
  I was browsing the internet using firefox installed from ubuntu repo

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: perl-base 5.26.1-5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Fri Mar 23 22:56:12 2018
  ExecutablePath: /usr/bin/perl
  InstallationDate: Installed on 2018-03-15 (9 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: perl
  StacktraceTop:
   _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so
   Perl_pp_entersub ()
  Title: perl crashed with SIGABRT in _dbus_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1758498/+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