[Touch-packages] [Bug 1732847] [NEW] package libperl5.22:amd64 5.22.1-9ubuntu0.2 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar

[Cuauhtemoc Gonzalez]

Public bug reported:

when i tried to install python-mysqldb, the problem surge.
I tried to install the pandas libreries and sqlalchelmy with conda and pip

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libperl5.22:amd64 5.22.1-9ubuntu0.2
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Nov 15 00:08:45 2017
ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
InstallationDate: Installed on 2017-08-23 (85 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: perl
Title: package libperl5.22:amd64 5.22.1-9ubuntu0.2 failed to install/upgrade: 
El paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes 
de intentar su configuración.
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: perl (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 perl in Ubuntu.
https://bugs.launchpad.net/bugs/1732847

Title:
  package libperl5.22:amd64 5.22.1-9ubuntu0.2 failed to install/upgrade:
  El paquete está en un estado grave de inconsistencia - debe
  reinstalarlo  antes de intentar su configuración.

Status in perl package in Ubuntu:
  New

Bug description:
  when i tried to install python-mysqldb, the problem surge.
  I tried to install the pandas libreries and sqlalchelmy with conda and pip

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22:amd64 5.22.1-9ubuntu0.2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Nov 15 00:08:45 2017
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-08-23 (85 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: perl
  Title: package libperl5.22:amd64 5.22.1-9ubuntu0.2 failed to install/upgrade: 
El paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes 
de intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1732847/+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 1727390] Re: New bugfix release 17.2.4

[Timo Aaltonen]

but it's 17.2.4 that was uploaded and what this bug is about

** Summary changed:

- New bugfix release 17.2.5
+ New bugfix release 17.2.4

** Changed in: mesa (Ubuntu)
   Status: Fix Released => In Progress

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

Title:
  New bugfix release 17.2.4

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  [Impact]

  A new upstream bugfix release is available. Release note diff compared
  to 17.2.2:

  "Mesa 17.2.3 is now available.

  In this release we have:

  The Vulkan drivers ANV and RADV have multiple small fixes.

  The EGL code has improved handling of the new wl_dmabuf codepath.

  SWR no longer crashes when checking environment variables.

  Other gallium drivers have also seen updates - freedreno, nouveau and
  radeonsi. The gallivm module, used by llvmpipe et al. has gained little
  endian PPC64 fixes.

  The VA and VDPAU state-trackers have seems improvements handling
  interlaced videos.

  We're using python3 compatible constructs which gives us SCons 3.0
  support."

  "Mesa 17.2.4 is now available.

  In this release we have:

  In Mesa Core we have included a change to prevent KOTOR from breaking
  when in combination with the ATI fragment shader extension. 
  Additionally, NIR has also received a correction.

  Mesa's state tracker has gotten a patch to avoid leaks in certain
  situations like when resizing a window.

  Intel drivers have received several fixes.  The compiler has gotten a
  couple, while anv also received one.  i965 got a patch to avoid VA-
  API, Beignet and other contexts in the system to break when in
  combination with previous versions of Mesa 17.2.x.

  AMD's compiler has received a couple of fixes while radv has also
  received another couple, including one to avoid a hang due to an
  overflow on huge textures.

  Broadcom's vc4 has corrected a problem when compiling with Android's
  clang.

  clover has also seen fixed a problem compiling after a specific clang
  revision.

  Vulkan's WSI has gotten plugged a memory leak for X11."

  
  [Test case]

  Test typical use cases on the most common hw/driver combinations:
  intel/i965
  nvidia/nouveau
  radeon/radeonsi

  [Regression potential]

  These releases are tested against compliance, bugfix releases in
  particular have minimal risk of regressing anything major at least.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+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 1732836] Re: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1732836

Title:
  package apport 2.20.1-0ubuntu2.12 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in apport package in Ubuntu:
  New

Bug description:
  sudo apt-get dist-upgrade
  Чтение списков пакетов… Готово
  Построение дерева зависимостей   
  Чтение информации о состоянии… Готово
  Расчёт обновлений… Готово
  Пакеты, которые будут обновлены:
bind9-host dnsutils libbind9-140 libdns-export162 libdns162 libirs-export141
libisc-export160 libisc160 libisccc140 libisccfg-export140 libisccfg140
liblwres141
  обновлено 12, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 
0 пакетов не обновлено.
  не установлено до конца или удалено 2 пакетов.
  Необходимо скачать 2 209 kБ архивов.
  После данной операции, объём занятого дискового пространства возрастёт на 
12,3 kB.
  Хотите продолжить? [Д/н] y
  Пол:1 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libisc-export160 amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [153 kB]
  Пол:2 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libdns-export162 amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [666 kB]
  Пол:3 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 dnsutils 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [88,9 kB]
  Пол:4 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
bind9-host amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [38,3 kB]
  Пол:5 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libisc160 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [215 kB]
  Пол:6 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libdns162 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [879 kB]
  Пол:7 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libisccc140 amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [16,3 kB]
  Пол:8 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libisccfg140 amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [40,5 kB]
  Пол:9 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
liblwres141 amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [33,7 kB]
  Пол:10 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libbind9-140 amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [23,6 kB]
  Пол:11 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libisccfg-export140 amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [38,4 kB]
  Пол:12 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libirs-export141 amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [17,4 kB]
  Получено 2 209 kБ за 1с (1 671 kБ/c)  
  dpkg: предупреждение: список файлов пакета «openvpn» отсутствует; 
предполагаем, что на данный момент у пакета нет установленных файлов
  dpkg: предупреждение: список файлов пакета «resolvconf» отсутствует; 
предполагаем, что на данный момент у пакета нет установленных файлов
  (Чтение базы данных … на данный момент установлено 246692 файла и каталога.)
  Подготовка к распаковке 
…/libisc-export160_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
  Распаковывается libisc-export160 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
  Подготовка к распаковке 
…/libdns-export162_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
  Распаковывается libdns-export162 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
  Подготовка к распаковке …/dnsutils_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
  Распаковывается dnsutils (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
  Подготовка к распаковке …/bind9-host_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
  Распаковывается bind9-host (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
  Подготовка к распаковке …/libisc160_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
  Распаковывается libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
  Подготовка к распаковке …/libdns162_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
  Распаковывается libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
  Подготовка к распаковке …/libisccc140_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb 
…
  Распаковывается libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
  Подготовка к распаковке 
…/libisccfg140_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
  Распаковывается libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
  Подготовка к распаковке …/liblwres141_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb 
…
  Распаковывается liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
  Подготовка к распаковке 
…/libbind9-140_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
  Распаковывается libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
  Подготовка к распаковке 

[Touch-packages] [Bug 1732836] [NEW] package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Maxim Kosarev]

Public bug reported:

sudo apt-get dist-upgrade
Чтение списков пакетов… Готово
Построение дерева зависимостей   
Чтение информации о состоянии… Готово
Расчёт обновлений… Готово
Пакеты, которые будут обновлены:
  bind9-host dnsutils libbind9-140 libdns-export162 libdns162 libirs-export141
  libisc-export160 libisc160 libisccc140 libisccfg-export140 libisccfg140
  liblwres141
обновлено 12, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 0 
пакетов не обновлено.
не установлено до конца или удалено 2 пакетов.
Необходимо скачать 2 209 kБ архивов.
После данной операции, объём занятого дискового пространства возрастёт на 12,3 
kB.
Хотите продолжить? [Д/н] y
Пол:1 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libisc-export160 amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [153 kB]
Пол:2 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libdns-export162 amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [666 kB]
Пол:3 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 dnsutils 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [88,9 kB]
Пол:4 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 bind9-host 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [38,3 kB]
Пол:5 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libisc160 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [215 kB]
Пол:6 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libdns162 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [879 kB]
Пол:7 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libisccc140 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [16,3 kB]
Пол:8 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libisccfg140 amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [40,5 kB]
Пол:9 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 liblwres141 
amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [33,7 kB]
Пол:10 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libbind9-140 amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [23,6 kB]
Пол:11 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libisccfg-export140 amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [38,4 kB]
Пол:12 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libirs-export141 amd64 1:9.10.3.dfsg.P4-8ubuntu1.9 [17,4 kB]
Получено 2 209 kБ за 1с (1 671 kБ/c)  
dpkg: предупреждение: список файлов пакета «openvpn» отсутствует; предполагаем, 
что на данный момент у пакета нет установленных файлов
dpkg: предупреждение: список файлов пакета «resolvconf» отсутствует; 
предполагаем, что на данный момент у пакета нет установленных файлов
(Чтение базы данных … на данный момент установлено 246692 файла и каталога.)
Подготовка к распаковке 
…/libisc-export160_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
Распаковывается libisc-export160 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
Подготовка к распаковке 
…/libdns-export162_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
Распаковывается libdns-export162 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
Подготовка к распаковке …/dnsutils_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
Распаковывается dnsutils (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
Подготовка к распаковке …/bind9-host_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
Распаковывается bind9-host (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
Подготовка к распаковке …/libisc160_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
Распаковывается libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
Подготовка к распаковке …/libdns162_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
Распаковывается libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
Подготовка к распаковке …/libisccc140_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
Распаковывается libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
Подготовка к распаковке …/libisccfg140_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
Распаковывается libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
Подготовка к распаковке …/liblwres141_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
Распаковывается liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
Подготовка к распаковке …/libbind9-140_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
Распаковывается libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
Подготовка к распаковке 
…/libisccfg-export140_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
Распаковывается libisccfg-export140 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
Подготовка к распаковке 
…/libirs-export141_1%3a9.10.3.dfsg.P4-8ubuntu1.9_amd64.deb …
Распаковывается libirs-export141 (1:9.10.3.dfsg.P4-8ubuntu1.9) на замену 
(1:9.10.3.dfsg.P4-8ubuntu1.8) …
Обрабатываются триггеры для libc-bin (2.23-0ubuntu9) …
Обрабатываются триггеры для man-db (2.7.5-1) …
Настраивается пакет apport (2.20.1-0ubuntu2.12) …

[Touch-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Timo Aaltonen]

yes, but it's stuck in bionic-proposed until libva transition is done,
aiui

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1732827] [NEW] package perl-base 5.22.1-9ubuntu0.2 failed to install/upgrade: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它

[liangding]

Public bug reported:

I don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: perl-base 5.22.1-9ubuntu0.2
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Nov 17 12:13:55 2017
DpkgTerminalLog:
 dpkg: 处理软件包 perl-base (--configure)时出错：
  该软件包正处于非常不稳定的状态；
 您最好在配置它之前，先重新安装它
ErrorMessage: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它
InstallationDate: Installed on 2017-08-28 (80 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: perl
Title: package perl-base 5.22.1-9ubuntu0.2 failed to install/upgrade: 
该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: perl (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 perl in Ubuntu.
https://bugs.launchpad.net/bugs/1732827

Title:
  package perl-base 5.22.1-9ubuntu0.2 failed to install/upgrade:
  该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它

Status in perl package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: perl-base 5.22.1-9ubuntu0.2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Nov 17 12:13:55 2017
  DpkgTerminalLog:
   dpkg: 处理软件包 perl-base (--configure)时出错：
该软件包正处于非常不稳定的状态；
   您最好在配置它之前，先重新安装它
  ErrorMessage: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它
  InstallationDate: Installed on 2017-08-28 (80 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: perl
  Title: package perl-base 5.22.1-9ubuntu0.2 failed to install/upgrade: 
该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1732827/+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 1726075] Re: [HP Pavilion Power Laptop 15-cb0xx, Realtek ALC295, Speaker, Internal] No sound at all

[Richard]

I can confirm I'm having the same problem with a similar HP Pavilion
model under Fedora 27. There is no audio from the built in speakers but
pavucontrol shows audio is being played. Verified nothing is muted in
alsamixer.

Headphone jack works as expected.

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

Title:
  [HP Pavilion Power Laptop 15-cb0xx, Realtek ALC295, Speaker, Internal]
  No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I cannot hear anything without headphone, the speaker don't work at
  all, even though after i set the speaker volume bar in the alsamixer
  panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  remaincool   1862 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct 23 00:57:26 2017
  InstallationDate: Installed on 2017-07-06 (108 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: 内置音频 - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  remaincool   1862 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP Pavilion Power Laptop 15-cb0xx, Realtek ALC295, Speaker, Internal] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 836B
  dmi.board.vendor: HP
  dmi.board.version: 46.20
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.09:bd06/02/2017:svnHP:pnHPPavilionPowerLaptop15-cb0xx:pvrType1ProductConfigId:rvnHP:rn836B:rvr46.20:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Power Laptop 15-cb0xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1726075/+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 174858] Re: 'netstat' doesn't check for sockets using SCTP protocol

[Ken Sharp]

Bug trackers doesn't seem to like https://sourceforge.net/p/net-
tools/bugs/21/

Once that's fixed, Debian should be ready to update their package.

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

Title:
  'netstat' doesn't check for sockets using SCTP protocol

Status in net-tools package in Ubuntu:
  Triaged
Status in net-tools package in Debian:
  Fix Released
Status in net-tools package in Gentoo Linux:
  Fix Released

Bug description:
  Binary package hint: net-tools

  'netstat' doesn't display information about listening SCTP sockets. I
  checked it twice. First time with my own applications and second time
  server - client examples provided with SCTP implementation for Linux.
  When server is listening command 'neststat -l' doesn't display any
  information about it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/174858/+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 1732791] Re: package evolution-data-server 3.12.11-0ubuntu1.15.04.1 failed to install/upgrade: package evolution-data-server is already installed and configured

[dino99]

*** This bug is a duplicate of bug 545790 ***
https://bugs.launchpad.net/bugs/545790

** Package changed: evolution-data-server (Ubuntu) => dpkg (Ubuntu)

** This bug has been marked a duplicate of bug 545790
   package PACKAGE failed to install/upgrade: error writing to '': Success

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

Title:
  package evolution-data-server 3.12.11-0ubuntu1.15.04.1 failed to
  install/upgrade: package evolution-data-server is already installed
  and configured

Status in dpkg package in Ubuntu:
  New

Bug description:
  I do not know what happened . This message appears to me and brings me
  here

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: evolution-data-server 3.12.11-0ubuntu1.15.04.1
  ProcVersionSignature: Ubuntu 3.19.0-84.92-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-84-generic i686
  ApportVersion: 2.17.2-0ubuntu1.8
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu3.1
  Architecture: i386
  CrashReports:
   640:0:118:2130146:2017-11-16 23:29:55.060662269 +0200:2017-11-16 
23:29:56.060662269 +0200:/var/crash/libedata-cal-1.2-23.0.crash
   600:0:118:348319:2017-11-16 20:54:21.022795438 +0200:2017-11-16 
20:54:22.022795438 +0200:/var/crash/evolution-data-server.0.crash
  Date: Thu Nov 16 20:54:21 2017
  DuplicateSignature: 
package:evolution-data-server:3.12.11-0ubuntu1.15.04.1:package 
evolution-data-server is already installed and configured
  ErrorMessage: package evolution-data-server is already installed and 
configured
  InstallationDate: Installed on 2017-11-16 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1.1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: evolution-data-server
  Title: package evolution-data-server 3.12.11-0ubuntu1.15.04.1 failed to 
install/upgrade: package evolution-data-server is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1732791/+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 1058191] Re: file doesn't recognise all "Linux make config build file[s]"

[Ken Sharp]

$ file -i /boot/config*
/boot/config-4.10.0-38-generic: text/plain; charset=us-ascii
/boot/config-4.4.0-98-generic:  text/plain; charset=us-ascii

Format changed again in Xenial.

** Tags added: xenial

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

Title:
  file doesn't recognise all "Linux make config build file[s]"

Status in file package in Ubuntu:
  Fix Committed

Bug description:
  $ file /boot/config*
  /boot/config-2.6.38-16-generic: Linux make config build file
  /boot/config-2.6.38-8-generic:  Linux make config build file
  /boot/config-3.2.0-30-generic:  ASCII text
  /boot/config-3.2.0-31-generic:  ASCII text

  $ file -i /boot/config*
  /boot/config-2.6.38-16-generic: text/plain; charset=us-ascii
  /boot/config-2.6.38-8-generic:  text/plain; charset=us-ascii
  /boot/config-3.2.0-30-generic:  text/plain; charset=us-ascii
  /boot/config-3.2.0-31-generic:  text/plain; charset=us-ascii

  The files are practically identical.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: file 5.09-2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  Date: Fri Sep 28 17:04:17 2012
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: file
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file/+bug/1058191/+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 1065147] Re: file doesn't recognise lzma archives with higher compression

[Ken Sharp]

** Changed in: file (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  file doesn't recognise lzma archives with higher compression

Status in file package in Ubuntu:
  Fix Released
Status in file package in Debian:
  Fix Released

Bug description:
  $ lzma -fqqkz Hello\ world.txt ; file Hello\ world.txt.lzma ; lzma -fqqkz9 
Hello\ world.txt ; file Hello\ world.txt.lzma
  Hello world.txt.lzma: LZMA compressed data, streamed
  Hello world.txt.lzma: data

  File doesn't recognise lzma archives when -9 is used for compression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: file 5.09-2
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  Date: Wed Oct 10 17:59:49 2012
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: file
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file/+bug/1065147/+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 1203300] Re: Can no longer mount (cifs)

[Ken Sharp]

Precise is EOL

** Changed in: util-linux (Ubuntu)
   Status: New => Invalid

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

Title:
  Can no longer mount (cifs)

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  I have no idea what is going on now but following a recent dist-
  upgrade (yesterday) my computer refused to boot.

  I commented out all the non-essential stuff in my fstab to try and
  work out why:

  # sudo mount -av
  mount.cifs kernel mount options: 
ip=192.168.0.5,unc=\\192.168.0.5\winetricks,guest,sec=none,noperm,uid=0,gid=50,ver=1,user=,pass=
  Unable to find suitable address.
  mount.cifs kernel mount options: 
ip=192.168.0.5,unc=\\192.168.0.5\wine,guest,sec=none,noperm,uid=0,gid=50,ver=1,user=,pass=
  Unable to find suitable address.

  Jul 20 14:11:33 aspire kernel: [ 2619.660374] CIFS VFS: Error connecting to 
socket. Aborting operation
  Jul 20 14:11:33 aspire kernel: [ 2619.660585] CIFS VFS: cifs_mount failed 
w/return code = -113
  Jul 20 14:11:39 aspire kernel: [ 2625.660338] CIFS VFS: Error connecting to 
socket. Aborting operation
  Jul 20 14:11:39 aspire kernel: [ 2625.660551] CIFS VFS: cifs_mount failed 
w/return code = -113

  I went back to the previous kernel to see if that was the cause but it
  made no difference. Not even sure if this is the correct package to
  report it against!

  I can still use gvfs to access the mounts but that's not ideal.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: mount 2.20.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-49.75-generic 3.2.46
  Uname: Linux 3.2.0-49-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Sat Jul 20 14:13:40 2013
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1203300/+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 1229618] Re: Saucy: /forcefsck not being removed after execution / completion of boot system check

[Ken Sharp]

Saucy and Precise are EOL and this seems to work in later releases.

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

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

Title:
  Saucy: /forcefsck not being removed after execution / completion of
  boot system check

Status in mountall package in Ubuntu:
  Invalid

Bug description:
  '/forcefsck' not being removed after execution / completion of boot
  system check.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: e2fsprogs 1.42.8-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  Date: Tue Sep 24 10:12:13 2013
  InstallationDate: Installed on 2013-09-12 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  SourcePackage: e2fsprogs
  UpgradeStatus: Upgraded to saucy on 2013-09-12 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1229618/+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 1413332] Re: eject command has to be issued twice

[Ken Sharp]

Precise is EOL. Works on Trusty+.

** Changed in: eject (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  eject command has to be issued twice

Status in eject package in Ubuntu:
  Fix Released

Bug description:
  eject has to be issued twice, as it will fail the first time,
  succeeding the second time.

  $ sudo eject /dev/sr0
  eject: unable to eject, last error: Inappropriate ioctl for device
  $ sudo eject /dev/sr0

  It should simply eject. I don't know what the first eject does
  different to the second. Nothing in the syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: eject 2.1.5+deb1+cvs20081104-9
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Wed Jan 21 16:46:45 2015
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: eject
  UpgradeStatus: Upgraded to precise on 2014-12-07 (45 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eject/+bug/1413332/+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 1732803] Re: systemd-journald RateLimitBurst is sometimes divided by 4

[David Glasser]

Correction: I believe this occurs when the amount of remaining space
until journald hits its allocated limit is between 1 and 16MB, not when
the entire filesystem has that little space left.  (This makes it much
more likely to occur: any system that is using logs enough for them to
be rotated due to space will hit this issue whenever it's near rotation
time.)

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

Title:
  systemd-journald RateLimitBurst is sometimes divided by 4

Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

  systemd-journald allows you to configure a per-service journal rate limit in 
/etc/systemd/journald.conf via the RateLimitBurst parameter. systemd-journald 
has
  code that effectively increases the rate limit when there is a lot of disk 
space available.
  However, all versions of systemd before v232 had a bug which would shrink the 
rate limit
  when there is between 1 and 16 MB available on disk.

  If you designed a service to log at a rate R and configured
  RateLimitBurst to a little above R, this can lead to loss of logs when
  free disk is between 1 and 16 MB, as your service will be surprisingly
  rate limited at lower than your configured rate.

  This bug was fixed upstream in https://github.com/systemd/systemd/pull/4218
  It is a straightforward one-line change that makes the code match the 
comments under it.

  [Test Case]

  Run a systemd service that prints lots of logs (eg `yes`). Fill your
  disk to have only 1MB full. Use journalctl to see how many log lines
  are between "Suppressed" lines. Note that it is 1/4 of what you'd
  expect.  (Admittedly this test case is a little hard to achieve since
  journald itself is writing to disk. I did run into this in
  production.)

  [Regression Potential]

  This does mean that journald can write slightly more to disk than it
  did before when free disk is between 1 and 16MB, but given that the
  full burst rate is available below 1MB it seems unlikely that any
  systems are depending on this change in order to not break.

  The fix has been in systemd since v232 (shipped in Zesty). I would
  like to see it in Xenial.

  
  [Other Info]
   
  I am seeing this on:
  ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 1 ~/systemd-229$ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 0 ~/systemd-229$ apt-cache policy 
systemd
  systemd:
Installed: 229-4ubuntu19
Candidate: 229-4ubuntu21
Version table:
   229-4ubuntu21 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu 
xenial-updates/main amd64 Packages
   *** 229-4ubuntu19 100
  100 /var/lib/dpkg/status
   229-4ubuntu10 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial/main amd64 
Packages

  This bug seems to date back to the original implementation of rate
  limiting (https://github.com/systemd/systemd/commit/6e409ce10d).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732803/+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 1732803] Re: systemd-journald RateLimitBurst is sometimes divided by 4

[David Glasser]

** Patch added: "debdiff backporting fix from upstream"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732803/+attachment/5010237/+files/Fix-journald-rate-limit-with-low-disk-space.debdiff

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

Title:
  systemd-journald RateLimitBurst is sometimes divided by 4

Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

  systemd-journald allows you to configure a per-service journal rate limit in 
/etc/systemd/journald.conf via the RateLimitBurst parameter. systemd-journald 
has
  code that effectively increases the rate limit when there is a lot of disk 
space available.
  However, all versions of systemd before v232 had a bug which would shrink the 
rate limit
  when there is between 1 and 16 MB available on disk.

  If you designed a service to log at a rate R and configured
  RateLimitBurst to a little above R, this can lead to loss of logs when
  free disk is between 1 and 16 MB, as your service will be surprisingly
  rate limited at lower than your configured rate.

  This bug was fixed upstream in https://github.com/systemd/systemd/pull/4218
  It is a straightforward one-line change that makes the code match the 
comments under it.

  [Test Case]

  Run a systemd service that prints lots of logs (eg `yes`). Fill your
  disk to have only 1MB full. Use journalctl to see how many log lines
  are between "Suppressed" lines. Note that it is 1/4 of what you'd
  expect.  (Admittedly this test case is a little hard to achieve since
  journald itself is writing to disk. I did run into this in
  production.)

  [Regression Potential]

  This does mean that journald can write slightly more to disk than it
  did before when free disk is between 1 and 16MB, but given that the
  full burst rate is available below 1MB it seems unlikely that any
  systems are depending on this change in order to not break.

  The fix has been in systemd since v232 (shipped in Zesty). I would
  like to see it in Xenial.

  
  [Other Info]
   
  I am seeing this on:
  ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 1 ~/systemd-229$ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 0 ~/systemd-229$ apt-cache policy 
systemd
  systemd:
Installed: 229-4ubuntu19
Candidate: 229-4ubuntu21
Version table:
   229-4ubuntu21 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu 
xenial-updates/main amd64 Packages
   *** 229-4ubuntu19 100
  100 /var/lib/dpkg/status
   229-4ubuntu10 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial/main amd64 
Packages

  This bug seems to date back to the original implementation of rate
  limiting (https://github.com/systemd/systemd/commit/6e409ce10d).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732803/+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 1732803] [NEW] systemd-journald RateLimitBurst is sometimes divided by 4

[David Glasser]

Public bug reported:

[Impact]

systemd-journald allows you to configure a per-service journal rate limit in 
/etc/systemd/journald.conf via the RateLimitBurst parameter. systemd-journald 
has
code that effectively increases the rate limit when there is a lot of disk 
space available.
However, all versions of systemd before v232 had a bug which would shrink the 
rate limit
when there is between 1 and 16 MB available on disk.

If you designed a service to log at a rate R and configured
RateLimitBurst to a little above R, this can lead to loss of logs when
free disk is between 1 and 16 MB, as your service will be surprisingly
rate limited at lower than your configured rate.

This bug was fixed upstream in https://github.com/systemd/systemd/pull/4218
It is a straightforward one-line change that makes the code match the comments 
under it.

[Test Case]

Run a systemd service that prints lots of logs (eg `yes`). Fill your
disk to have only 1MB full. Use journalctl to see how many log lines are
between "Suppressed" lines. Note that it is 1/4 of what you'd expect.
(Admittedly this test case is a little hard to achieve since journald
itself is writing to disk. I did run into this in production.)

[Regression Potential]

This does mean that journald can write slightly more to disk than it did
before when free disk is between 1 and 16MB, but given that the full
burst rate is available below 1MB it seems unlikely that any systems are
depending on this change in order to not break.

The fix has been in systemd since v232 (shipped in Zesty). I would like
to see it in Xenial.


[Other Info]
 
I am seeing this on:
ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 1 ~/systemd-229$ lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04
ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 0 ~/systemd-229$ apt-cache policy 
systemd
systemd:
  Installed: 229-4ubuntu19
  Candidate: 229-4ubuntu21
  Version table:
 229-4ubuntu21 500
500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial-updates/main 
amd64 Packages
 *** 229-4ubuntu19 100
100 /var/lib/dpkg/status
 229-4ubuntu10 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 229-4ubuntu4 500
500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial/main amd64 
Packages

This bug seems to date back to the original implementation of rate
limiting (https://github.com/systemd/systemd/commit/6e409ce10d).

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

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

Title:
  systemd-journald RateLimitBurst is sometimes divided by 4

Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

  systemd-journald allows you to configure a per-service journal rate limit in 
/etc/systemd/journald.conf via the RateLimitBurst parameter. systemd-journald 
has
  code that effectively increases the rate limit when there is a lot of disk 
space available.
  However, all versions of systemd before v232 had a bug which would shrink the 
rate limit
  when there is between 1 and 16 MB available on disk.

  If you designed a service to log at a rate R and configured
  RateLimitBurst to a little above R, this can lead to loss of logs when
  free disk is between 1 and 16 MB, as your service will be surprisingly
  rate limited at lower than your configured rate.

  This bug was fixed upstream in https://github.com/systemd/systemd/pull/4218
  It is a straightforward one-line change that makes the code match the 
comments under it.

  [Test Case]

  Run a systemd service that prints lots of logs (eg `yes`). Fill your
  disk to have only 1MB full. Use journalctl to see how many log lines
  are between "Suppressed" lines. Note that it is 1/4 of what you'd
  expect.  (Admittedly this test case is a little hard to achieve since
  journald itself is writing to disk. I did run into this in
  production.)

  [Regression Potential]

  This does mean that journald can write slightly more to disk than it
  did before when free disk is between 1 and 16MB, but given that the
  full burst rate is available below 1MB it seems unlikely that any
  systems are depending on this change in order to not break.

  The fix has been in systemd since v232 (shipped in Zesty). I would
  like to see it in Xenial.

  
  [Other Info]
   
  I am seeing this on:
  ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 1 ~/systemd-229$ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 0 ~/systemd-229$ apt-cache policy 
systemd
  systemd:
Installed: 229-4ubuntu19
Candidate: 229-4ubuntu21
Version table:
   229-4ubuntu21 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu 
xenial-updates/main amd64 Packages
   *** 229-4ubuntu19 100
  100 /var/lib/dpkg/status
   

[Touch-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Brian Murray]

Hello Sjors, or anyone else affected,

Accepted network-manager into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.2.6-0ubuntu0.16.04.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: network-manager (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed

Bug description:
  SRU REQUEST:

  Debdiff (nm-dhcp-helper.debdiff) attached.

  Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This
  bug was fixed upstream in 1.4.

  [Impact]

   * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP
     lease renewal due to a DBus race condition.

   * Upstream NetworkManager 1.4 fixes the race condition by changing
     nm-dhcp-helper's DBus notification from signal "Event" to method
     "Notify".

   * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix 
to NM 1.2. This SRU request applies that backported patch to Xenial's
     NM 1.2.x.

  [Test Case]

   * Not reliably reproducible. Out of hundreds of machines, only a
     dozen or so fail to notify NetworkManager of a DHCP lease
     renewal about 30-50% of the time. (i.e. It's always the same
     handful of machines that fail.)

   * All such machines with the patched packages have been fine for weeks,
     over many dozens of lease renewals.

  [Regression Potential]

  * The patch changes both nm-dhcp-helper and NetworkManager itself. As
  soon as the new packages are unpacked, the new nm-dhcp-helper will be
  used on DHCP lease renewals, with the new Notify mechanism. Since the
  running, old NetworkManager is still expecting Event notifications,
  the patched nm-dhcp-helper has fallback capability to Event.

  * Once NetworkManager is restarted and is running the patched version,
  it will have the new Notify support.

  [Other Info]

   * Upstream bug w/ patch:
  https://bugzilla.gnome.org/show_bug.cgi?id=784636

   * RHEL bug with links to the 1.4 commits from which the patch was
     derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276

   * NOTE:  The final comment on the upstream GNOME bug claims that the
  fix is incomplete.  However, it is possible that the running
  NetworkManager was not restarted (see Regression Potential notes
  above), which is why nm-dhcp-helper is falling back to Event.  The
  remainder of the log messages in that final comment are from a custom
  wrapper the submitter was running around nm-dhcp-helper.  I have
  deployed the exact same patch (without said wrapper) to real-world
  systems and tested extensively, and see nothing but successful DHCP
  lease renewal notifications using D-Bus Notify, not D-Bus Event.


  
  I've found an issue on some of our Xenial office machines, causing 
NetworkManager to drop its IP address lease in some cases when it shouldn't. 
I'm not sure if the actual bug is in NetworkManager or perhaps dbus or 
dhclient, but I'll do my best to help to figure out where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').

  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: 

[Touch-packages] [Bug 1716203] Re: Backport packages for 16.04.4 HWE stack

[Brian Murray]

Hello Timo, or anyone else affected,

Accepted libclc into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libclc/0.2.0+git20170330-3~16.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libclc (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

** Changed in: libdrm (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Backport packages for 16.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-5.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland-protocols package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in llvm-toolchain-5.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland-protocols source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.4 ***

  A minor update, only some driver updates plus a newer Mesa.

  Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols
  updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.76 to 2.4.83
  - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests
  - intel: new pci-ids
  - drm: leak fixes, manpage updates
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  wayland-protocols:
  None, just adds a few protocol definitions (xml files)

  llvm-toolchain-5.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-5 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for 
the bugfix release (xenial & artful) is bug 1727390

  [Other information]

  build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc,
  xorg-server], mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1716203] Please test proposed package

[Brian Murray]

Hello Timo, or anyone else affected,

Accepted libdrm into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.83-1~16.04.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  Backport packages for 16.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-5.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland-protocols package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in llvm-toolchain-5.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland-protocols source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.4 ***

  A minor update, only some driver updates plus a newer Mesa.

  Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols
  updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.76 to 2.4.83
  - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests
  - intel: new pci-ids
  - drm: leak fixes, manpage updates
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  wayland-protocols:
  None, just adds a few protocol definitions (xml files)

  llvm-toolchain-5.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-5 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for 
the bugfix release (xenial & artful) is bug 1727390

  [Other information]

  build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc,
  xorg-server], mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Brian Murray]

Is this fixed in bionic yet?

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  New
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1732484] Re: package libperl5.22 5.22.1-9 [modified: usr/share/doc/libperl5.22/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5

[Launchpad Bug Tracker]

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

** Changed in: perl (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libperl5.22 5.22.1-9 [modified:
  usr/share/doc/libperl5.22/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different
  from other instances of package libperl5.22:amd64

Status in perl package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu bug reporting guidelines:

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9 [modified: 
usr/share/doc/libperl5.22/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.4.0-100.123-generic 4.4.95
  Uname: Linux 4.4.0-100-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Nov 15 16:09:42 2017
  DuplicateSignature:
   package:libperl5.22:5.22.1-9 [modified: 
usr/share/doc/libperl5.22/changelog.Debian.gz]
   Unpacking libperl5.22:amd64 (5.22.1-9ubuntu0.2) over (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9ubuntu0.2_amd64.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:amd64
  InstallationDate: Installed on 2014-07-21 (1213 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 [modified: 
usr/share/doc/libperl5.22/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', 
which is different from other instances of package libperl5.22:amd64
  UpgradeStatus: Upgraded to xenial on 2017-08-02 (105 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1732484/+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 1666432] Re: Internet drops every few minutes on wired and wireless connection

[Otávio Augusto Soares]

Same here on Ubuntu 17.10

*-network 
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:04:00.0
   logical name: enp4s0
   version: 10
   serial: 20:47:47:76:7b:a5
   size: 10Mbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8168g-3_0.0.1 04/23/13 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
   resources: irq:317 ioport:d000(size=256) memory:df304000-df304fff 
memory:df30-df303fff
  *-network
   description: Wireless interface
   product: Wireless 3165
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:05:00.0
   logical name: wlp5s0
   version: 79
   serial: 08:d4:0c:a8:60:a6
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
   configuration: broadcast=yes driver=iwlwifi 
driverversion=4.13.0-16-lowlatency firmware=29.541020.0 ip=192.168.0.11 
latency=0 link=yes multicast=yes wireless=IEEE 802.11
   resources: irq:319 memory:df20-df201fff

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21 16:36:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: 

[Touch-packages] [Bug 1732795] [NEW] Sync rfkill 0.5-2 (main) from Debian unstable (main)

[Bryan Quigley]

Public bug reported:

Please sync rfkill 0.5-2 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Resynchronise with Debian.  Remaining changes:
- Add upstart jobs rfkill-store and rfkill-restore to save soft RF kill
  state across reboots.

Per the changelog the only remaining changes is to create the upstart jobs in 
/etc/init. 
That's no longer needed and no longer has any effect with upstart no longer 
used - in fact
some of upstart has already been removed from this package, see:
  * Drop obsolete and no-op dh_installinit --upstart-only option.
(LP: #1519228)


Changelog entries since current bionic version 0.5-1ubuntu4:

rfkill (0.5-2) unstable; urgency=medium

  * QA upload.
  * Set Debian QA Group as maintainer. (see #881513)
  * Migrations:
  - debian/control to format 1.0.
  - debian/rules to simplified format.
  - DH level to 10.
  * debian/control:
  - Bumped Standards-Version to 4.1.1.
  - Removed no longer needed build dependency dpkg-dev.
  - Updated VCS fields.
  * debian/patches/:
  - debian-changes:
  ~ Renamed to 10_fix-manpage.patch.
  ~ Added a specific header.
  - 20_add-GCC-hardening.patch: created to use GCC hardening.
  * debian/rules:
  - Do not use Debian revision as version for final binary.
  - Use build architecture compiler to avoid a FTCBFS. Thanks to
Helmut Grohne . (Closes: #839798)
  * debian/source/:
  - options: removed. This file was pushing all patches to a single file.
  - patch-header: removed. It was creating a "default" header.
  * debian/watch:
  - Bumped to version 4.
  - Updated.

 -- Joao Eriberto Mota Filho   Mon, 13 Nov 2017
18:17:03 -0200

** Affects: rfkill (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: rfkill (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync rfkill 0.5-2 (main) from Debian unstable (main)

Status in rfkill package in Ubuntu:
  New

Bug description:
  Please sync rfkill 0.5-2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Resynchronise with Debian.  Remaining changes:
  - Add upstart jobs rfkill-store and rfkill-restore to save soft RF kill
state across reboots.

  Per the changelog the only remaining changes is to create the upstart jobs in 
/etc/init. 
  That's no longer needed and no longer has any effect with upstart no longer 
used - in fact
  some of upstart has already been removed from this package, see:
* Drop obsolete and no-op dh_installinit --upstart-only option.
  (LP: #1519228)

  
  Changelog entries since current bionic version 0.5-1ubuntu4:

  rfkill (0.5-2) unstable; urgency=medium

* QA upload.
* Set Debian QA Group as maintainer. (see #881513)
* Migrations:
- debian/control to format 1.0.
- debian/rules to simplified format.
- DH level to 10.
* debian/control:
- Bumped Standards-Version to 4.1.1.
- Removed no longer needed build dependency dpkg-dev.
- Updated VCS fields.
* debian/patches/:
- debian-changes:
~ Renamed to 10_fix-manpage.patch.
~ Added a specific header.
- 20_add-GCC-hardening.patch: created to use GCC hardening.
* debian/rules:
- Do not use Debian revision as version for final binary.
- Use build architecture compiler to avoid a FTCBFS. Thanks to
  Helmut Grohne . (Closes: #839798)
* debian/source/:
- options: removed. This file was pushing all patches to a single file.
- patch-header: removed. It was creating a "default" header.
* debian/watch:
- Bumped to version 4.
- Updated.

   -- Joao Eriberto Mota Filho   Mon, 13 Nov 2017
  18:17:03 -0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1732795/+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 1732792] Re: package libperl5.22:amd64 5.22.1-9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[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 perl in Ubuntu.
https://bugs.launchpad.net/bugs/1732792

Title:
  package libperl5.22:amd64 5.22.1-9 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in perl package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 16.04.3 LTS
  Release:  16.04

  2) perl:
Instalado: 5.22.1-9
Candidato: 5.22.1-9ubuntu0.2
Tabela de versão:
   5.22.1-9ubuntu0.2 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   *** 5.22.1-9 500
  500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) This error occur with frequency, I'm normally using Ubuntu and the
  error appear. I don't know what it is and nothing happen after that I
  ignore the message, the system continues to working.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22:amd64 5.22.1-9
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Nov 16 19:19:18 2017
  DuplicateSignature:
   package:libperl5.22:amd64:5.22.1-9
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libperl5.22:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: perl
  Title: package libperl5.22:amd64 5.22.1-9 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1732792/+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 1642634] Re: indicator-datetime uses excessive memory

[machadoug]

Still having this issue with Ubuntu 17.10.
Disabled the option to Show clock in the menu bar and it still causes the issue.
Iǜe also set the time manually instead of Automatically from the internet and 
it has no effect.
Does anyone have a workaround?

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

Title:
  indicator-datetime uses excessive memory

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  On my Aquaris 4.5, OTA-13, indicator-datetime
  15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS
  is 315892, almost three times as much as unity8.

  I believe this is an OTA regression. I'm not sure if it regressed from
  OTA-11 or OTA-12.

  Just now, I got caught in an oom killer loop with constant killing of
  unity8-dash because of this, making my phone unusable. I had to kill
  indicator-datetime manually. It then restarted automatically and now
  uses 80456 RSS only. I see bug 1633319 exists complaining about a
  memory leak. It's not exactly the same version since mine is
  15.10+15.04.20160820.1-0ubuntu1 and that one is
  15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are
  the same or something? Perhaps the two are dupes, but I'll let someone
  more familiar make that determination.

  I have only a handful of alarms (perhaps five on average; rarely more)
  but I do have my Google calendar syncing with perhaps hundreds of
  events. However, there's no reason that this should cause indicator-
  datetime to use more RSS; it shouldn't be keeping these in memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+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 1732792] [NEW] package libperl5.22:amd64 5.22.1-9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Eliana Bertol Rosa]

Public bug reported:

1) Description: Ubuntu 16.04.3 LTS
Release:16.04

2) perl:
  Instalado: 5.22.1-9
  Candidato: 5.22.1-9ubuntu0.2
  Tabela de versão:
 5.22.1-9ubuntu0.2 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 *** 5.22.1-9 500
500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

3) This error occur with frequency, I'm normally using Ubuntu and the
error appear. I don't know what it is and nothing happen after that I
ignore the message, the system continues to working.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libperl5.22:amd64 5.22.1-9
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Nov 16 19:19:18 2017
DuplicateSignature:
 package:libperl5.22:amd64:5.22.1-9
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package libperl5.22:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: perl
Title: package libperl5.22:amd64 5.22.1-9 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: perl (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 perl in Ubuntu.
https://bugs.launchpad.net/bugs/1732792

Title:
  package libperl5.22:amd64 5.22.1-9 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in perl package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 16.04.3 LTS
  Release:  16.04

  2) perl:
Instalado: 5.22.1-9
Candidato: 5.22.1-9ubuntu0.2
Tabela de versão:
   5.22.1-9ubuntu0.2 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   *** 5.22.1-9 500
  500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) This error occur with frequency, I'm normally using Ubuntu and the
  error appear. I don't know what it is and nothing happen after that I
  ignore the message, the system continues to working.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22:amd64 5.22.1-9
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Nov 16 19:19:18 2017
  DuplicateSignature:
   package:libperl5.22:amd64:5.22.1-9
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libperl5.22:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: perl
  Title: package libperl5.22:amd64 5.22.1-9 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1732792/+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 1732791] [NEW] package evolution-data-server 3.12.11-0ubuntu1.15.04.1 failed to install/upgrade: package evolution-data-server is already installed and configured

[mahmoud wahbeh]

Public bug reported:

I do not know what happened . This message appears to me and brings me
here

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: evolution-data-server 3.12.11-0ubuntu1.15.04.1
ProcVersionSignature: Ubuntu 3.19.0-84.92-generic 3.19.8-ckt22
Uname: Linux 3.19.0-84-generic i686
ApportVersion: 2.17.2-0ubuntu1.8
AptdaemonVersion: 1.1.1+bzr982-0ubuntu3.1
Architecture: i386
CrashReports:
 640:0:118:2130146:2017-11-16 23:29:55.060662269 +0200:2017-11-16 
23:29:56.060662269 +0200:/var/crash/libedata-cal-1.2-23.0.crash
 600:0:118:348319:2017-11-16 20:54:21.022795438 +0200:2017-11-16 
20:54:22.022795438 +0200:/var/crash/evolution-data-server.0.crash
Date: Thu Nov 16 20:54:21 2017
DuplicateSignature: 
package:evolution-data-server:3.12.11-0ubuntu1.15.04.1:package 
evolution-data-server is already installed and configured
ErrorMessage: package evolution-data-server is already installed and configured
InstallationDate: Installed on 2017-11-16 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1.1
 apt  1.0.9.7ubuntu4.2
SourcePackage: evolution-data-server
Title: package evolution-data-server 3.12.11-0ubuntu1.15.04.1 failed to 
install/upgrade: package evolution-data-server is already installed and 
configured
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: already-installed apport-package i386 vivid

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

Title:
  package evolution-data-server 3.12.11-0ubuntu1.15.04.1 failed to
  install/upgrade: package evolution-data-server is already installed
  and configured

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I do not know what happened . This message appears to me and brings me
  here

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: evolution-data-server 3.12.11-0ubuntu1.15.04.1
  ProcVersionSignature: Ubuntu 3.19.0-84.92-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-84-generic i686
  ApportVersion: 2.17.2-0ubuntu1.8
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu3.1
  Architecture: i386
  CrashReports:
   640:0:118:2130146:2017-11-16 23:29:55.060662269 +0200:2017-11-16 
23:29:56.060662269 +0200:/var/crash/libedata-cal-1.2-23.0.crash
   600:0:118:348319:2017-11-16 20:54:21.022795438 +0200:2017-11-16 
20:54:22.022795438 +0200:/var/crash/evolution-data-server.0.crash
  Date: Thu Nov 16 20:54:21 2017
  DuplicateSignature: 
package:evolution-data-server:3.12.11-0ubuntu1.15.04.1:package 
evolution-data-server is already installed and configured
  ErrorMessage: package evolution-data-server is already installed and 
configured
  InstallationDate: Installed on 2017-11-16 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1.1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: evolution-data-server
  Title: package evolution-data-server 3.12.11-0ubuntu1.15.04.1 failed to 
install/upgrade: package evolution-data-server is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1732791/+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 1732791] Re: package evolution-data-server 3.12.11-0ubuntu1.15.04.1 failed to install/upgrade: package evolution-data-server is already installed and configured

[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 evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1732791

Title:
  package evolution-data-server 3.12.11-0ubuntu1.15.04.1 failed to
  install/upgrade: package evolution-data-server is already installed
  and configured

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I do not know what happened . This message appears to me and brings me
  here

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: evolution-data-server 3.12.11-0ubuntu1.15.04.1
  ProcVersionSignature: Ubuntu 3.19.0-84.92-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-84-generic i686
  ApportVersion: 2.17.2-0ubuntu1.8
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu3.1
  Architecture: i386
  CrashReports:
   640:0:118:2130146:2017-11-16 23:29:55.060662269 +0200:2017-11-16 
23:29:56.060662269 +0200:/var/crash/libedata-cal-1.2-23.0.crash
   600:0:118:348319:2017-11-16 20:54:21.022795438 +0200:2017-11-16 
20:54:22.022795438 +0200:/var/crash/evolution-data-server.0.crash
  Date: Thu Nov 16 20:54:21 2017
  DuplicateSignature: 
package:evolution-data-server:3.12.11-0ubuntu1.15.04.1:package 
evolution-data-server is already installed and configured
  ErrorMessage: package evolution-data-server is already installed and 
configured
  InstallationDate: Installed on 2017-11-16 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1.1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: evolution-data-server
  Title: package evolution-data-server 3.12.11-0ubuntu1.15.04.1 failed to 
install/upgrade: package evolution-data-server is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1732791/+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 1681910] Re: gnome-terminal constantly logs "Unable to load blank_cursor from the cursor theme" under gnome/wayland

[Launchpad Bug Tracker]

This bug was fixed in the package gtk+3.0 - 3.22.25-0ubuntu0.1

---
gtk+3.0 (3.22.25-0ubuntu0.1) artful; urgency=medium

  [ Simon McVittie ]
  * New upstream release (LP: #1728421)
- Fix tiling behaviour with Mutter/Shell 3.26 (Closes: #879566)
- Fix crash when adding Google online account (LP: #1720400)
- Fixes log spam about cursor when running gnome-terminal on Wayland
  (LP: #1681910)
- Update symbols file
- d/p/0001-Adwaita-Fix-typo-.backgrounf-.background.patch,
  d/p/0002-theme-Fix-Adwaita-headerbars.patch,
  d/p/0003-display-x11-Unset-tiled-state-if-_GTK_EDGE_CONSTRAIN.patch:
  Drop patches, applied upstream
- d/p/gdk-wayland-protocol-server-decoration.patch:
  Add server-decoration.xml from upstream git. It is missing from the
  tarball release.

  [ Jeremy Bicha ]
  * Drop 0004_fix-gtkentry-wayland-regression.path:
Because this caused a totem regression, we're fixing the
bug in mutter instead.
  * Drop some unapplied patches from the package source

 -- Jeremy Bicha   Mon, 30 Oct 2017 16:07:23 -0400

** Changed in: gtk+3.0 (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-terminal constantly logs "Unable to load blank_cursor from the
  cursor theme" under gnome/wayland

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Fix Released

Bug description:
  Impact
  ==
  The systemd journal gets full of useless messages about "Unable to load 
blank_cursor from the cursor theme" when using GNOME Terminal in Wayland on 
Ubuntu 17.10. Ubuntu 17.10 uses Wayland by default when the hardware supports 
it.

  Test Case
  =
  1.Install the gtk3 updates to Ubuntu 17.10.
  2. Log out then log into "Ubuntu" or "GNOME" on a computer that supports 
Wayland.
  3. Open the default terminal app.
  4. Verify that you are running Wayland by running this command. If there is 
output, you are running Wayland.

   env | grep -i wayland

  5. Run this command to check for the useless messages from gnome-
  terminal:

  journalctl -f

  Regression Potential
  ===
  This fix is part of the gtk3 3.22.25 update (LP: #1728421) and seems unlikely 
to cause problems.

  https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=fc741adbb

  Original Bug Report
  ===
  Under GNOME/Wayland, regardless of cursor theme (I'm using 'DMZ-White', but 
confirmed with 'Adwaita'), whenever the terminal obtains focus and the user 
starts entering input, gnome-terminal will generate two log entries:

  Apr 11 13:39:22 localhost gnome-terminal-[28979]: Unable to load blank_cursor 
from the cursor theme
  Apr 11 13:39:22 localhost gnome-terminal-[28979]: Unable to load blank_cursor 
from the cursor theme

  This seems to be:
  https://bugzilla.redhat.com/show_bug.cgi?id=1417490

  and related to:
  https://bugzilla.gnome.org/show_bug.cgi?id=775217

  (though in Ubuntu 17.04 the log doesn't contain 'gdkcursor-
  wayland.c:170' like in the gnome bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1681910/+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 1720400] Update Released

[Brian Murray]

The verification of the Stable Release Update for gtk+3.0 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  /usr/bin/gnome-control-
  
center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

Status in GTK+:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Fix Released

Bug description:
  Impact
  ==
  On artful every time gnome-control-center (goa panel) is used to add a google 
account, gnome-control-center crashes. This is one of the most reported crashes 
after the release.

  Test Case
  =
  - Open gnome-control-center
  - Go to online-account panel
  - Add a Google online account.
  - gnome-control-center should not crash while adding a google online account.

  Regression Potential
  ===
  This is a minimal patch applied upstream:
  https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=1c3aff510

  Check if closing a gtk window/dialog creates no artifacts both on xorg
  and on wayland.

  Original Bug Report
  ===
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a 
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/gtk/+bug/1720400/+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 1681910] Update Released

[Brian Murray]

The verification of the Stable Release Update for gtk+3.0 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  gnome-terminal constantly logs "Unable to load blank_cursor from the
  cursor theme" under gnome/wayland

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Fix Released

Bug description:
  Impact
  ==
  The systemd journal gets full of useless messages about "Unable to load 
blank_cursor from the cursor theme" when using GNOME Terminal in Wayland on 
Ubuntu 17.10. Ubuntu 17.10 uses Wayland by default when the hardware supports 
it.

  Test Case
  =
  1.Install the gtk3 updates to Ubuntu 17.10.
  2. Log out then log into "Ubuntu" or "GNOME" on a computer that supports 
Wayland.
  3. Open the default terminal app.
  4. Verify that you are running Wayland by running this command. If there is 
output, you are running Wayland.

   env | grep -i wayland

  5. Run this command to check for the useless messages from gnome-
  terminal:

  journalctl -f

  Regression Potential
  ===
  This fix is part of the gtk3 3.22.25 update (LP: #1728421) and seems unlikely 
to cause problems.

  https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=fc741adbb

  Original Bug Report
  ===
  Under GNOME/Wayland, regardless of cursor theme (I'm using 'DMZ-White', but 
confirmed with 'Adwaita'), whenever the terminal obtains focus and the user 
starts entering input, gnome-terminal will generate two log entries:

  Apr 11 13:39:22 localhost gnome-terminal-[28979]: Unable to load blank_cursor 
from the cursor theme
  Apr 11 13:39:22 localhost gnome-terminal-[28979]: Unable to load blank_cursor 
from the cursor theme

  This seems to be:
  https://bugzilla.redhat.com/show_bug.cgi?id=1417490

  and related to:
  https://bugzilla.gnome.org/show_bug.cgi?id=775217

  (though in Ubuntu 17.04 the log doesn't contain 'gdkcursor-
  wayland.c:170' like in the gnome bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1681910/+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 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

[Launchpad Bug Tracker]

This bug was fixed in the package gtk+3.0 - 3.22.25-0ubuntu0.1

---
gtk+3.0 (3.22.25-0ubuntu0.1) artful; urgency=medium

  [ Simon McVittie ]
  * New upstream release (LP: #1728421)
- Fix tiling behaviour with Mutter/Shell 3.26 (Closes: #879566)
- Fix crash when adding Google online account (LP: #1720400)
- Fixes log spam about cursor when running gnome-terminal on Wayland
  (LP: #1681910)
- Update symbols file
- d/p/0001-Adwaita-Fix-typo-.backgrounf-.background.patch,
  d/p/0002-theme-Fix-Adwaita-headerbars.patch,
  d/p/0003-display-x11-Unset-tiled-state-if-_GTK_EDGE_CONSTRAIN.patch:
  Drop patches, applied upstream
- d/p/gdk-wayland-protocol-server-decoration.patch:
  Add server-decoration.xml from upstream git. It is missing from the
  tarball release.

  [ Jeremy Bicha ]
  * Drop 0004_fix-gtkentry-wayland-regression.path:
Because this caused a totem regression, we're fixing the
bug in mutter instead.
  * Drop some unapplied patches from the package source

 -- Jeremy Bicha   Mon, 30 Oct 2017 16:07:23 -0400

** Changed in: gtk+3.0 (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  /usr/bin/gnome-control-
  
center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

Status in GTK+:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Fix Released

Bug description:
  Impact
  ==
  On artful every time gnome-control-center (goa panel) is used to add a google 
account, gnome-control-center crashes. This is one of the most reported crashes 
after the release.

  Test Case
  =
  - Open gnome-control-center
  - Go to online-account panel
  - Add a Google online account.
  - gnome-control-center should not crash while adding a google online account.

  Regression Potential
  ===
  This is a minimal patch applied upstream:
  https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=1c3aff510

  Check if closing a gtk window/dialog creates no artifacts both on xorg
  and on wayland.

  Original Bug Report
  ===
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a 
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/gtk/+bug/1720400/+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 1728421] Re: Update gtk+3.0 to 3.22.25

[Launchpad Bug Tracker]

This bug was fixed in the package gtk+3.0 - 3.22.25-0ubuntu0.1

---
gtk+3.0 (3.22.25-0ubuntu0.1) artful; urgency=medium

  [ Simon McVittie ]
  * New upstream release (LP: #1728421)
- Fix tiling behaviour with Mutter/Shell 3.26 (Closes: #879566)
- Fix crash when adding Google online account (LP: #1720400)
- Fixes log spam about cursor when running gnome-terminal on Wayland
  (LP: #1681910)
- Update symbols file
- d/p/0001-Adwaita-Fix-typo-.backgrounf-.background.patch,
  d/p/0002-theme-Fix-Adwaita-headerbars.patch,
  d/p/0003-display-x11-Unset-tiled-state-if-_GTK_EDGE_CONSTRAIN.patch:
  Drop patches, applied upstream
- d/p/gdk-wayland-protocol-server-decoration.patch:
  Add server-decoration.xml from upstream git. It is missing from the
  tarball release.

  [ Jeremy Bicha ]
  * Drop 0004_fix-gtkentry-wayland-regression.path:
Because this caused a totem regression, we're fixing the
bug in mutter instead.
  * Drop some unapplied patches from the package source

 -- Jeremy Bicha   Mon, 30 Oct 2017 16:07:23 -0400

** Changed in: gtk+3.0 (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  Update gtk+3.0 to 3.22.25

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Fix Released

Bug description:
  Impact
  ==
  There is a new gtk3 release, 3.22.25.

  Highlights
  --
  * Allows dropping these cherry-picked patches:
    - 0001-Adwaita-Fix-typo-.backgrounf-.background.patch
    - 0002-theme-Fix-Adwaita-headerbars.patch
   - 0003-display-x11-Unset-tiled-state-if-_GTK_EDGE_CONSTRAIN.patch
  * Fixes crash with GNOME Online Accounts (LP: #1720400)
  * Fixes menu forwarding over SSH (LP: #1700319)
  * Fixes log spam about cursor when running gnome-terminal on Wayland (LP: 
#1681910)
  * Support KDE SSD (server-side decorations) handling on Wayland
  * Restores middle-click to do the opposite of primary (usually left-) click 
in scrollbars, GTKRange
  * Some theme fixes for the gtk3 High Contrast theme
  * Allow more key buttons in the GNOME Settings > Keyboard panel to be 
translatable
  * A fix to not show duplicate printers in some cases
  * Improves the GNOME 3.26 tiling feature for GNOME Terminal

  For more changes since 3.22.24, see
  https://git.gnome.org/browse/gtk+/log?h=gtk-3-22
  https://git.gnome.org/browse/gtk+/tree/NEWS?h=gtk-3-22

  Test Case
  =
  Install the update. Run a variety of apps in the default Ubuntu install with 
the Ambiance theme.

  Also check that the Adwaita and High Contrast themes still look ok. You can 
change the theme with the GNOME Tweaks app (gnome-tweak-tool). For the window 
buttons to look as designed, you should change the icon theme to Adwaita when 
you set the theme to Adwaita or High Contrast. Afterwards, you can reset your 
theme back to the defaults with
  gsettings reset org.gnome.desktop.interface gtk-theme
  gsettings reset org.gnome.desktop.interface icon-theme

  Regression Potential
  
  Quite a few changes, but mostly it's bug fixes.

  Earlier gtk3 releases had some regressions (that's why we had those
  cherry-picked patches), but that was mostly related to the late GNOME
  3.26 tiling feature that was rushed in. This release does not have any
  major new features like that.

  Unfortunately, very few people run gtk3 from git master so regressions
  often aren't seen until distros start shipping the gtk3 update.

  The GNOME stack has an SRU Micro-release exception
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  We haven't done micro-release SRUs for gtk3.22 yet. This might be a
  good trial run to see how well it works before 18.04 LTS. Fedora does
  keep their gtk3 up to date throughout the life of their releases.

  Other Info
  ==
  This update also drops a few old patches that weren't listed in 
debian/patches/series. Sorry about the noise but this makes it a bit cleaner in 
the future.

  0001-Update-the-GDK-Mir-backend-to-fix-a-few-problems.patch
  0001-Improve-external-drives-detection.patch
  0002-fix-other-locations-with-glib-249.patch
  0003-use-null-for-generic-marshallers.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1728421/+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 1728421] Update Released

[Brian Murray]

The verification of the Stable Release Update for gtk+3.0 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Update gtk+3.0 to 3.22.25

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Fix Released

Bug description:
  Impact
  ==
  There is a new gtk3 release, 3.22.25.

  Highlights
  --
  * Allows dropping these cherry-picked patches:
    - 0001-Adwaita-Fix-typo-.backgrounf-.background.patch
    - 0002-theme-Fix-Adwaita-headerbars.patch
   - 0003-display-x11-Unset-tiled-state-if-_GTK_EDGE_CONSTRAIN.patch
  * Fixes crash with GNOME Online Accounts (LP: #1720400)
  * Fixes menu forwarding over SSH (LP: #1700319)
  * Fixes log spam about cursor when running gnome-terminal on Wayland (LP: 
#1681910)
  * Support KDE SSD (server-side decorations) handling on Wayland
  * Restores middle-click to do the opposite of primary (usually left-) click 
in scrollbars, GTKRange
  * Some theme fixes for the gtk3 High Contrast theme
  * Allow more key buttons in the GNOME Settings > Keyboard panel to be 
translatable
  * A fix to not show duplicate printers in some cases
  * Improves the GNOME 3.26 tiling feature for GNOME Terminal

  For more changes since 3.22.24, see
  https://git.gnome.org/browse/gtk+/log?h=gtk-3-22
  https://git.gnome.org/browse/gtk+/tree/NEWS?h=gtk-3-22

  Test Case
  =
  Install the update. Run a variety of apps in the default Ubuntu install with 
the Ambiance theme.

  Also check that the Adwaita and High Contrast themes still look ok. You can 
change the theme with the GNOME Tweaks app (gnome-tweak-tool). For the window 
buttons to look as designed, you should change the icon theme to Adwaita when 
you set the theme to Adwaita or High Contrast. Afterwards, you can reset your 
theme back to the defaults with
  gsettings reset org.gnome.desktop.interface gtk-theme
  gsettings reset org.gnome.desktop.interface icon-theme

  Regression Potential
  
  Quite a few changes, but mostly it's bug fixes.

  Earlier gtk3 releases had some regressions (that's why we had those
  cherry-picked patches), but that was mostly related to the late GNOME
  3.26 tiling feature that was rushed in. This release does not have any
  major new features like that.

  Unfortunately, very few people run gtk3 from git master so regressions
  often aren't seen until distros start shipping the gtk3 update.

  The GNOME stack has an SRU Micro-release exception
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  We haven't done micro-release SRUs for gtk3.22 yet. This might be a
  good trial run to see how well it works before 18.04 LTS. Fedora does
  keep their gtk3 up to date throughout the life of their releases.

  Other Info
  ==
  This update also drops a few old patches that weren't listed in 
debian/patches/series. Sorry about the noise but this makes it a bit cleaner in 
the future.

  0001-Update-the-GDK-Mir-backend-to-fix-a-few-problems.patch
  0001-Improve-external-drives-detection.patch
  0002-fix-other-locations-with-glib-249.patch
  0003-use-null-for-generic-marshallers.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1728421/+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 1648183] Re: Crackling and popping sound when using headphones

[Théo Besnard]

Hi! 
First, thank's a lot to @robertjjoynt for the solution. It works also on my pc 
(Omen Pc by HP), however i can't find out how to run the script on start up. I 
think i've done a wrong thing on the crontab command. Could someone tell me the 
exactly things to write in the crontab script (my script name is son.sh and its 
directory is /usr/local/bin 

Thanks a lot to the person who will answer me !

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1732776] [NEW] debconf/priority not respected

[Joshua Powers]

Public bug reported:

Starting with the bionic ISOs setting the debconf priority level via
`debconf/priority=LEVEL` on the cmdline is not respected. Using
`priority=LEVEL` however is.

Steps to reproduce:
1. Download daily bionic ISO from 
http://cdimage.ubuntu.com/ubuntu-server/daily/pending/

2. Pull out the kernel and initrd
$ mkdir iso
$ bsdtar xfp bionic-server-amd64.iso -C iso
$ cp iso/install/vmlinuz .
$ cp iso/install/initrd.gz .

3. Create QEMU disk
$ qemu-img create -f qcow2 vdisk.img 4G

4. Launch ISO via QEMU with debconf/priority set on cmdline:
$ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \
-initrd initrd.gz -kernel kernel -display none -nographic \
-hda vdisk.img -cdrom bionic-server-amd64.iso \
-append 'console=ttyS0 locale=en_US.UTF-8 debconf/priority=critical'

The installer will ask you for keyboard layout, which is not expected as
the priority on those questions is high, not critical.

5. Change 'debconf/priority=critical' to 'priority=critical' and the
install will skip the initial keyboard and language questions, load
additional modules, bring up the network, and finally ask you about a
username and password, which is a critical question.

The expected behavior is that debconf/priority=critical and
priority=critical are treated in the same manner.

Here are two example installer syslogs show how artful does and bionic
does not respect the debconf/priority setting. In both you can clearly
see it set on the cmdline, however see debconf does not respect it:

artful: http://paste.ubuntu.com/25970598/
bionic: http://paste.ubuntu.com/25970599/

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

** Description changed:

  Starting with the bionic ISOs setting the debconf priority level via
  `debconf/priority=LEVEL` on the cmdline is not respected. Using
  `priority=LEVEL` however is.
  
  Steps to reproduce:
  1. Download daily bionic ISO from 
http://cdimage.ubuntu.com/ubuntu-server/daily/pending/
  
  2. Pull out the kernel and initrd
  $ mkdir iso
  $ bsdtar xfp bionic-server-amd64.iso -C iso
  $ cp iso/install/vmlinuz .
  $ cp iso/install/initrd.gz .
  
  3. Create QEMU disk
- $ qemu-img create -f qcow2 vdisk.img 4G 
+ $ qemu-img create -f qcow2 vdisk.img 4G
  
  4. Launch ISO via QEMU with debconf/priority set on cmdline:
  $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \
- -initrd initrd.gz -kernel kernel -display none -nographic \
- -hda vdisk.img -cdrom bionic-server-amd64.iso \
- -append 'console=ttyS0 locale=en_US.UTF-8 debconf/priority=critical'
+ -initrd initrd.gz -kernel kernel -display none -nographic \
+ -hda vdisk.img -cdrom bionic-server-amd64.iso \
+ -append 'console=ttyS0 locale=en_US.UTF-8 debconf/priority=critical'
  
  The installer will ask you for keyboard layout, which is not expected as
  the priority on those questions is high, not critical.
  
  5. Change 'debconf/priority=critical' to 'priority=critical' and the
  install will skip the initial keyboard and language questions, load
  additional modules, bring up the network, and finally ask you about a
  username and password, which is a critical question.
  
  The expected behavior is that debconf/priority=critical and
  priority=critical are treated in the same manner.
+ 
+ Here are two example installer syslogs show how artful does and bionic
+ does not respect the debconf/priority setting. In both you can clearly
+ see it set on the cmdline, however see debconf does not respect it:
+ 
+ artful: http://paste.ubuntu.com/25970598/
+ bionic: http://paste.ubuntu.com/25970599/

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

Title:
  debconf/priority not respected

Status in debconf package in Ubuntu:
  New

Bug description:
  Starting with the bionic ISOs setting the debconf priority level via
  `debconf/priority=LEVEL` on the cmdline is not respected. Using
  `priority=LEVEL` however is.

  Steps to reproduce:
  1. Download daily bionic ISO from 
http://cdimage.ubuntu.com/ubuntu-server/daily/pending/

  2. Pull out the kernel and initrd
  $ mkdir iso
  $ bsdtar xfp bionic-server-amd64.iso -C iso
  $ cp iso/install/vmlinuz .
  $ cp iso/install/initrd.gz .

  3. Create QEMU disk
  $ qemu-img create -f qcow2 vdisk.img 4G

  4. Launch ISO via QEMU with debconf/priority set on cmdline:
  $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \
  -initrd initrd.gz -kernel kernel -display none -nographic \
  -hda vdisk.img -cdrom bionic-server-amd64.iso \
  -append 'console=ttyS0 locale=en_US.UTF-8 debconf/priority=critical'

  The installer will ask you for keyboard layout, which is not expected
  as the priority on those questions is high, not critical.

  5. Change 'debconf/priority=critical' to 'priority=critical' and the
  install will skip the initial keyboard and language 

[Touch-packages] [Bug 1732769] Re: package udev 229-4ubuntu21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1732769

Title:
  package udev 229-4ubuntu21 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  I cannot say more than the summary/title

  The number 21 is not in the list on display

  Thanks to help

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  Date: Thu Nov 16 19:57:42 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-07-30 (474 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision M6500
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=80b71b49-579d-4c19-b1ed-b0f1cee9626e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: systemd
  Title: package udev 229-4ubuntu21 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0R1203
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/04/2013:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn0R1203:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Precision M6500
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732769/+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 1732769] [NEW] package udev 229-4ubuntu21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Claude Camy-Peyret]

Public bug reported:

I cannot say more than the summary/title

The number 21 is not in the list on display

Thanks to help

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udev 229-4ubuntu21
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.12
Architecture: amd64
Date: Thu Nov 16 19:57:42 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-07-30 (474 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. Precision M6500
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=80b71b49-579d-4c19-b1ed-b0f1cee9626e ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: systemd
Title: package udev 229-4ubuntu21 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/04/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0R1203
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/04/2013:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn0R1203:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Precision M6500
dmi.sys.vendor: Dell Inc.

** Affects: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1732769

Title:
  package udev 229-4ubuntu21 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  I cannot say more than the summary/title

  The number 21 is not in the list on display

  Thanks to help

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  Date: Thu Nov 16 19:57:42 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-07-30 (474 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision M6500
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=80b71b49-579d-4c19-b1ed-b0f1cee9626e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: systemd
  Title: package udev 229-4ubuntu21 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0R1203
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/04/2013:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn0R1203:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Precision M6500
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732769/+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 1653324] Re: No wireless networks visible on resume from suspend. Erroneous Wired connection icon in nm-applet

[Koen Roggemans]

Same on a Dell latitude 5580 with Intel Corporation Device 24fd (rev 78)

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

Title:
  No wireless networks visible on resume from suspend. Erroneous Wired
  connection icon in nm-applet

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  As others have reported this I just woke my Thinkpad 450 to find no
  network. I resolved this by manually reconnecting with "nmcli c up id
  " where  was taken from the output of
  "nmcli c" on the same machine.

  Steps to reproduce:-

  This is an intermittent issue which for me happens once in a while,
  but not super often to be annoying. For others it appears to happen
  often. I suspend my laptop multiple times daily and don't see this
  more than once per couple of weeks, or sometimes once a month.

  * Use laptop in one location on wifi
  * Suspend (shut lid) laptop
  * Resume (open lid) in same location (so same wifi networks nearby)

  Expected behaviour:-

  * Network come back up

  Actual behaviour:-

  * No network connectivity
  * nm-applet icon shows the two arrows as if a wired connection is made
  * No or few wireless erroneous wireless networks shown nearby

  * Workaround 1 (reconnect from command line)

  nmcli c

  (lists wireless networks, look for yours in the "NAME" column, use it
  in command below)

  nmcli c up id NAME

  * Workaround 2 (restart entire network stack)

  This AskUbuntu question has one solution
  http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-
  after-16-04-upgrade#761220

  Further information:-

  Output of nmcli m while suspending and resuming:-

  alan@gort:~$ nmcli m
  Connectivity is now 'none'
  Networkmanager is now in the 'asleep' state
  enp0s25: unmanaged
  wlp3s0: unmanaged
  Connectivity is now 'full'
  Networkmanager is now in the 'connected (local only)' state
  enp0s25: unavailable
  wlp3s0: unavailable
  wlp3s0: disconnected

  Output of nmcli after using workaround 1 above:-

  popey_2.4g_bed: connection profile changed
  Connectivity is now 'none'
  Networkmanager is now in the 'connecting' state
  wlp3s0: connecting (configuring)
  wlp3s0: using connection 'popey_2.4g_bed'
  wlp3s0: connecting (getting IP configuration)
  Connectivity is now 'full'
  'popey_2.4g_bed' is now the primary connection
  Networkmanager is now in the 'connected' state
  wlp3s0: connected
  popey_2.4g_bed: connection profile changed

  Hardware info:-

  Thinkpad T450
  alan@gort:~$ lspci | grep -i net
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) 
I218-LM (rev 03)
  03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  alan@gort:~$ uptime
   05:31:54 up 2 days, 18:03,  7 users,  load average: 0.34, 0.94, 1.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 31 05:38:47 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-27 (247 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 linkdown 
   10.235.160.0/24 dev lxdbr0  proto kernel  scope link  src 10.235.160.1 
linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.95  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1653324/+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 1719043] Re: Gnome web urlbar very slow to show typed input

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.26.2-0ubuntu0.1

---
mutter (3.26.2-0ubuntu0.1) artful; urgency=medium

  * New upstream release (LP: #1730097):
- Fix unredirecting full-screen windows and fix returning to
  full-screen after Alt-Tab (LP: #1725649)
- Allow HiDPI scaling even when non-HiDPI displays are connected
  (LP: #1724024)
- Fix Epiphany URL bar (LP: #1719043) (Closes: #875826)
  * Drop cherry-picked patches

 -- Jeremy Bicha   Sat, 04 Nov 2017 14:07:59 -0400

** Changed in: mutter (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  Gnome web urlbar very slow to show typed input

Status in GTK+:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Invalid
Status in mutter source package in Artful:
  Fix Released
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  It is very difficult to use the address bar in Epiphany on GNOME on Wayland 
because after a few characters, the address bar field stops redrawing. (This 
apparently was triggered by mutter 3.26?)

  Test Case
  =
  sudo apt install epiphany-browser
  Open the Web app
  Type a URL into the address bar. Type a lng URL.
  You should see all the characters you type into the address bar.

  Regression Potential
  ===
  To fix this issue, an optimization commit applied earlier in 3.26 development 
was reverted. This fix is part of mutter 3.26.2 (LP: #1730097).

  Other Info
  ==
  The first SRU gtk+3.0 3.22.24-0ubuntu2 caused a regression seen in totem and 
so was reverted in both gtk upstream and in the next SRU 3.22.25-0ubuntu0.1

  Instead, this is being fixed in mutter.

  Original Bug Report
  ===
  First two characters typed in urlbar show immediately, other characters take 
up to 30 seconds to appear, or url will appear in full once enter key is 
pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1719043/+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 1722151] Re: Incorrect syntax when writing to ~/.pam_environment

[Launchpad Bug Tracker]

This bug was fixed in the package accountsservice - 0.6.42-0ubuntu3.1

---
accountsservice (0.6.42-0ubuntu3.1) artful-proposed; urgency=medium

  * debian/patches/0009-language-tools.patch:
- Modification of the update-langlist script due to new
  ~/.pam_environment syntax (LP: #1722151).

 -- Gunnar Hjalmarsson   Fri, 27 Oct 2017 22:15:00
+0200

** Changed in: accountsservice (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  Incorrect syntax when writing to ~/.pam_environment

Status in accountsservice package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in accountsservice source package in Artful:
  Fix Released
Status in language-selector source package in Artful:
  Fix Released

Bug description:
  [Impact]

  When the syntax for the entries in ~/.pam_environment was changed, the
  GUI in language-selector-gnome for maintaining the language priority
  list was broken since language-selector-gnome reads from
  ~/.pam_environment. The language-selector upload to artful makes
  language-selector-gnome handle both the old and the new syntax
  correctly.

  An additional similar change to accountsservice (the update-langlist
  script) is needed; hence also an accountsservice upload to artful.

  [Test Case]

  * Log in to an "Ubuntu on Xorg" session.
  * Open Language Support and find that it appears as if you can only
    set one item before the "English" item in the language list.

  With the new version, it works as expected again.

  [Regression Potential]

  Low. This is necessary to fix the regression caused by the change in
  accountsservice.

  [Original description]

  While investigating bug #1662031, I found out that /usr/share
  /language-tools/save-to-pam-env writes to ~/.pam_environment using an
  incorrect syntax: "VARIABLE=value" on each line. The expected syntax
  is "VARIABLE [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: accountsservice 0.6.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 06:57:17 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (463 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: accountsservice
  UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1722151/+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 1719043] Update Released

[Brian Murray]

The verification of the Stable Release Update for mutter has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Gnome web urlbar very slow to show typed input

Status in GTK+:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Invalid
Status in mutter source package in Artful:
  Fix Released
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  It is very difficult to use the address bar in Epiphany on GNOME on Wayland 
because after a few characters, the address bar field stops redrawing. (This 
apparently was triggered by mutter 3.26?)

  Test Case
  =
  sudo apt install epiphany-browser
  Open the Web app
  Type a URL into the address bar. Type a lng URL.
  You should see all the characters you type into the address bar.

  Regression Potential
  ===
  To fix this issue, an optimization commit applied earlier in 3.26 development 
was reverted. This fix is part of mutter 3.26.2 (LP: #1730097).

  Other Info
  ==
  The first SRU gtk+3.0 3.22.24-0ubuntu2 caused a regression seen in totem and 
so was reverted in both gtk upstream and in the next SRU 3.22.25-0ubuntu0.1

  Instead, this is being fixed in mutter.

  Original Bug Report
  ===
  First two characters typed in urlbar show immediately, other characters take 
up to 30 seconds to appear, or url will appear in full once enter key is 
pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1719043/+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 1644530] Re: keepalived fails to restart cleanly due to the wrong systemd settings

[Bug Watch Updater]

** Changed in: keepalived (Debian)
   Status: New => Fix Released

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

Title:
  keepalived fails to restart cleanly due to the wrong systemd settings

Status in keepalived package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Opinion
Status in keepalived source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Opinion
Status in keepalived package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Restarts of keepalived can leave stale processes with the old
  configuration around.

   * The systemd detection of the MainPID is suboptimal, and combined
  with not waiting on signals being handled it can fail on second
  restart killing the (still) remaining process of the first start.

   * Upstream has a PIDFile statement, this has proven to avoid the
  issue in the MainPID guessing code of systemd.

  [Test Case]

   * Set up keepalived, the more complex the config is the "bigger" is the 
reace window, below in the description is a trivial sample config that works 
well.
   
   * As a test run the loop restarting the service head-to-head while staying 
under the max-restart limit
  $ for j in $(seq 1 20); do sleep 11s; time for i in $(seq 1 5); do sudo 
systemctl restart keepalived; sudo systemctl status keepalived | egrep 
'Main.*exited'; done; done

   Expectation: no output other than timing
   Without fix: sometimes MainPIDs do no more exist, in these cases the child 
processes are the "old" ones from last execution with the old config.

  [Regression Potential]

   * Low because
 * A PIDFile statement is recommended by systemd for type=forking services 
anyway.
 * Upstream keepalived has this statement in their service file
 * By the kind of change, it should have no functional impact to other 
parts of the service other than for the PID detection of the job by Systemd.

   * Yet regression potential is never zero. There might be the unlikely
  case, which were considered working before due to a new config not
  properly being picked up. After the fix they will behave correctly and
  might show up as false-positives then if e.g. config was bad.

  [Other Info]
   
   * Usually a fix has to be in at least the latest Development release before 
SRUing it. But as I outlined below in later Releases than Xenial systemd seems 
to have improved making this change not-required. We haven't identified the 
bits for this (there is a bug task here), and they might as well be very 
complex. I think it is correct to fix Xenial in this regard with the simple 
change to the service file for now.

   * To eventually match I created a Debian bug task to ask them for the
  inclusion of the PIDFile so it can slowly tickle back down to newer
  Ubuntu Releases - also there more often people run backports where the
  issue might occur on older systemd versions (just as it does for us on
  Xenial)

  ---

  Because "PIDFile=" directive is missing in the systemd unit file,
  keepalived sometimes fails to kill all old processes. The old
  processes remain with old settings and cause unexpected behaviors. The
  detail of this bug is described in this ticket in upstream:
  https://github.com/acassen/keepalived/issues/443.

  The official systemd unit file is available since version 1.2.24 by
  this commit:

  
https://github.com/acassen/keepalived/commit/635ab69afb44cd8573663e62f292c6bb84b44f15

  This includes "PIDFile" directive correctly:

  PIDFile=/var/run/keepalived.pid

  We should go the same way.

  I am using Ubuntu 16.04.1, kernel 4.4.0-45-generic.

  Package: keepalived
  Version: 1.2.19-1

  ===

  How to reproduce:

  I used the two instances of Ubuntu 16.04.2 on DigitalOcean:

  Configurations
  --

  MASTER server's /etc/keepalived/keepalived.conf:

    vrrp_script chk_nothing {
   script "/bin/true"
   interval 2
    }

    vrrp_instance G1 {
  interface eth1
  state BACKUP
  priority 100

  virtual_router_id 123
  unicast_src_ip 
  unicast_peer {
    
  }
  track_script {
    chk_nothing
  }
    }

  BACKUP server's /etc/keepalived/keepalived.conf:

    vrrp_script chk_nothing {
   script "/bin/true"
   interval 2
    }

    vrrp_instance G1 {
  interface eth1
  state MASTER
  priority 200

  virtual_router_id 123
  unicast_src_ip 
  unicast_peer {
    
  }
  track_script {
    chk_nothing
  }
    }

  Loop based probing for the Error to exist:
  --
  After the setup above start keepalived on both servers:
  $ sudo systemctl start keepalived.service
  Then run the following loop
  $ for j in $(seq 1 20); do sleep 11s; time for i in $(seq 

[Touch-packages] [Bug 342581] Re: symlink of /bin/open to /bin/openvt obsolete

[Launchpad Bug Tracker]

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

** Changed in: kbd (Ubuntu)
   Status: New => Confirmed

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

Title:
  symlink of /bin/open to /bin/openvt obsolete

Status in kbd package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: kbd

  As of  intrepid (8.10) and kbd 1.14.1-3ubuntu3, kbd installs a symlink
  from /bin/open to /bin/openvt. This legacy behaviour doesn't seem to
  be depended-upon by any scripts within the distro itself, which all
  refer to the appropriate /bin/openvt. I can understand keeping this
  functionality to avoid breaking scripts the distro uses (though any
  such scripts should be rewritten to use the more appropriate command
  name), but it really doesn't seem necessary to keep it. This would
  free a package such as xdg-utils to use the command 'open' as a link
  to something of more immediate utility, namely xdg-open.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/342581/+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 1732735] [NEW] hostname lookup broken in ldap.conf

[Reinhard]

Public bug reported:

A scripted installation of an ldap-client WORKING in ubuntu 16.04 is broken in 
ubuntu 17.10.
In ldap.conf:
host ldap01 ldap02 (was working in 16.04)
has to be replaced with:
host 10.0.0.9 10.0.0.10

otherwise the system stays in an endless loop at boot up!

Change from hostname to ip has to be done with a rescue system.

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


** Tags: boot-loop ldap-client

** Attachment added: "bash file, installing ldap-client"
   
https://bugs.launchpad.net/bugs/1732735/+attachment/5010079/+files/410-createLDAPClient.sh

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

Title:
  hostname lookup broken in ldap.conf

Status in xorg package in Ubuntu:
  New

Bug description:
  A scripted installation of an ldap-client WORKING in ubuntu 16.04 is broken 
in ubuntu 17.10.
  In ldap.conf:
  host ldap01 ldap02 (was working in 16.04)
  has to be replaced with:
  host 10.0.0.9 10.0.0.10

  otherwise the system stays in an endless loop at boot up!

  Change from hostname to ip has to be done with a rescue system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1732735/+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 1732676] Re: package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyb

[Hans Joachim Desserud]

*** This bug is a duplicate of bug 1588998 ***
https://bugs.launchpad.net/bugs/1588998

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1588998, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1588998
   [master] package console-setup-linux 1.108ubuntu15 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15

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

Title:
  package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade:
  trying to overwrite '/lib/systemd/system/console-setup.service', which
  is also in package keyboard-configuration 1.108ubuntu15.3

Status in console-setup package in Ubuntu:
  New

Bug description:
  Errors were encountered while processing:
   /var/cache/apt/archives/console-setup-linux_1.170_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Kali 2017.3
  Package: console-setup-linux 1.108ubuntu15.3
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Nov 16 03:47:46 2017
  ErrorMessage: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.3
  InstallationDate: Installed on 2017-10-08 (39 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.19.0.4kali1
   apt  1.2.24
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade: 
trying to overwrite '/lib/systemd/system/console-setup.service', which is also 
in package keyboard-configuration 1.108ubuntu15.3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1732676/+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 1688933] Re: systemd restart-loops logind

[Launchpad Bug Tracker]

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

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

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

Title:
  systemd restart-loops logind

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Syslog logs systemd trying to restart logind every few seconds:

  May  7 00:51:29 server systemd[1]: Starting Login Service...
  May  7 00:51:54 server systemd[1]: systemd-logind.service: Main process 
exited, code=exited, status=1/FAILURE
  May  7 00:51:54 server systemd[1]: Failed to start Login Service.
  May  7 00:51:54 server systemd[1]: systemd-logind.service: Unit entered 
failed state.
  May  7 00:51:54 server systemd[1]: systemd-logind.service: Failed with result 
'exit-code'.
  May  7 00:51:54 server systemd[1]: systemd-logind.service: Service has no 
hold-off time, scheduling restart.
  May  7 00:51:54 server systemd[1]: Stopped Login Service.
  May  7 00:51:54 server systemd[1]: Starting Login Service...
  May  7 00:52:19 server systemd[1]: systemd-logind.service: Main process 
exited, code=exited, status=1/FAILURE
  May  7 00:52:19 server systemd[1]: Failed to start Login Service.
  May  7 00:52:19 server systemd[1]: systemd-logind.service: Unit entered 
failed state.
  May  7 00:52:19 server systemd[1]: systemd-logind.service: Failed with result 
'exit-code'.
  May  7 00:52:19 server systemd[1]: systemd-logind.service: Service has no 
hold-off time, scheduling restart.
  May  7 00:52:19 server systemd[1]: Stopped Login Service.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun May  7 00:51:07 2017
  InstallationDate: Installed on 2013-08-21 (1353 days ago)
  InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-51-generic 
root=UUID=16120d81-8cde-4e81-87cd-f55f65a4923b ro rootflags=subvol=@
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   2 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-10-24 (193 days ago)
  dmi.bios.date: 03/13/2014
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SWQ6710H.86A.0067.2014.0313.1347
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DQ67OW
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG12528-309
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSWQ6710H.86A.0067.2014.0313.1347:bd03/13/2014:svn:pn:pvr:rvnIntelCorporation:rnDQ67OW:rvrAAG12528-309:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1688933/+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 997483] Re: VT_WAITACTIVE does not work well with a multiseat setup

[Jonathan Marler]

This bug is happening on my machine, Ubuntu 16.04 LTS

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

Title:
  VT_WAITACTIVE does not work well with a multiseat setup

Status in Light Display Manager:
  In Progress
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Related to the fix introduced in bug #851612 .

  Saw this in lightdm.log (system call interrupted because of ctrl-alt-del 
pressed):
  [+2.97s] DEBUG: New display ready, switching to it
  [+2.97s] DEBUG: Activating VT 8
  [+77.56s] WARNING: Error using VT_WAITACTIVE 8 on /dev/console: Interrupted 
system call
  [+77.56s] DEBUG: Got signal 15 from process 1
  [+77.56s] DEBUG: Caught Terminated signal, shutting down

  And in x-1-greeter.log:
  [+0.48s] DEBUG: Loading users from org.freedesktop.Accounts
  [+0.48s] DEBUG: Loading user /org/freedesktop/Accounts/User1001
  [+0.50s] DEBUG: Loading user /org/freedesktop/Accounts/User1000
  [+50.56s] WARNING: Error getting session list from 
org.freedesktop.DisplayManager: Timeout was reached

  On vt7, unity-greeter would get stuck after password input.
  On vt8, unity-greeter appears after that "getting session list timeout", 
which is about a minute later than vt7, and does not have a password input 
field.

  lightdm blocked by VT_WAITACTIVE may be the cause...

  Tested with lightdm 1.2.0-0ubuntu2 in precise.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/997483/+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 1623003] Re: udev-generated /dev/disk/by-path names broken for virtio disks

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2017-11-16 11:01 EDT---
IBM Bugzilla Status-> closed. fixed with systemd 233 which is included with 
Ubuntu 17.10.

** Tags removed: targetmilestone-inin16041
** Tags added: targetmilestone-inin1710

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

Title:
  udev-generated /dev/disk/by-path names broken for virtio disks

Status in systemd:
  Unknown
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  The udev-generated /dev/disk/by-path names for virtio disks are broken on z 
Systems as they have the format virtio-pci-h.h.[-partn], where h.h. is 
the CCW devno of the virtio device representing the whole disk. Historically, 
the standard CCW naming was applied, which was ccw-h.h.[-partn]
   
  ---uname output---
  Linux ubuntu 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:05:09 UTC 2016 
s390x s390x s390x GNU/Linux
   
  Machine Type = 2964-703 running KVM for IBM z Systems 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Install Ubuntu LTS 16.04.1 on KVM for IBM z Systems 1.1.1
  2. Issue ls -l /dev/disk/by-path
   
  Userspace tool common name: udev 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: udev

  Userspace tool obtained from project website:  na

  There are basically two problems with this:
  1. The naming is technically incorrect, since the virtio devices on z are no 
PCI devices but CCW devices
  2. Then naming based on virtio- is backwards incompatible. This may seem not 
to be an issue for Xenial but customers may be confused if they have been 
running Linux on KVM for IBM z before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1623003/+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 1732548] Re: package apport 2.20.1-0ubuntu2.10 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: apport (Ubuntu)
   Status: New => Confirmed

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

Title:
  package apport 2.20.1-0ubuntu2.10 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I am not familiar with Linux, so I don't know how to describe the
  issue.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Nov 16 09:06:19 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-11-08 (7 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.10 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1732548/+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 1729192] Re: Shutdown needs often longer than usual

[ChristianEhrhardt]

Hmm,
that seems odd - but it doesn't have enough to recreate and debug.
As irqbalance isn't strictly required you could consider uninstalling or 
masking it in systemd.
But that is only a workaround.

For the sake of going forward I merged the latest irqbalance which should show 
up soon in 18.04.
Could you try if you can reproduce so in e.g. a KVM guest.

If so you could redirect the console and maybe even pipe it through something 
adding timestamps.
Sorry I'm not the biggest expert on systemd debugging - maybe there are much 
better options out there I don't know for shutdown delay analysis.

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

Title:
  Shutdown needs often longer than usual

Status in irqbalance package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 18.04 dev with irqbalance 1.1.0-2.3ubuntu1 and for
  some weeks on shutting down the system often (around 50%-75%) I'm
  seeing that the irqbalance job needs some seconds to shutdown causing
  to delay the system shutdown noticeable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1729192/+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 1729192] Re: Shutdown needs often longer than usual

[Sworddragon]

I have extended the test a bit by instead of testing if a manual
irqbalance shutdown is fast or slow I have tested if the system shutdown
is also delayed if irqbalance is manually shutdown before a system
shutdown. I have made a few system shutdowns with and without irqbalance
running and in the cases where irqbalance was running the most times the
system shutdown was delayed with systemd blaming the irqbalance job on
the console while without irqbalance running the system shutdown was
always fast.

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

Title:
  Shutdown needs often longer than usual

Status in irqbalance package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 18.04 dev with irqbalance 1.1.0-2.3ubuntu1 and for
  some weeks on shutting down the system often (around 50%-75%) I'm
  seeing that the irqbalance job needs some seconds to shutdown causing
  to delay the system shutdown noticeable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1729192/+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 1729192] Re: Shutdown needs often longer than usual

[Sworddragon]

> 1. does on the system running also take quite some time if you do like
"systemctl stop irqbalance"?

I have tested this now multiple times by stopping and starting it again
and all looked fine.


> 2. I'd assume that systemd concurrently stops multiple things and irqbalance 
> is just the last to print but not the one you are actually waiting on.

Based on the above this might be true. So is it a known issue that
systemd prints wrong things? I think this is an issue that should be
actually fixed before tinkering around on every shutdow delay issue
(also [1] blames that [2] isn't reliable enough so it would eventually
also make sense to wait for [1]'s implementation).

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

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

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

Title:
  Shutdown needs often longer than usual

Status in irqbalance package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 18.04 dev with irqbalance 1.1.0-2.3ubuntu1 and for
  some weeks on shutting down the system often (around 50%-75%) I'm
  seeing that the irqbalance job needs some seconds to shutdown causing
  to delay the system shutdown noticeable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1729192/+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 1726124] Re: DNS domain search paths not updated when VPN started

[Andreas Fritiofson]

BTW, the long timeout you see on short name lookup failures is most
likely due to LLMNR being on by default. I think this is insane and I
always switch it off in /etc/systemd/resolved.conf .

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

Title:
  DNS domain search paths not updated when VPN started

Status in network-manager package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be 

[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

[Andreas Fritiofson]

to->two

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

Title:
  DNS domain search paths not updated when VPN started

Status in network-manager package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:

[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

[Andreas Fritiofson]

Paul Smith, what you describe is information leakage and shouldn't IMHO
work as you say by default.

Consider that I'm connected to a corporate network and have an
(untrusted) VPN active which I only want to use to access resources on
its network (never-default: yes). Then by having the resolver adding the
domain of the VPN network to short name lookups could leak those local
names to the remote VPN (depending on the order the lookups are
performed in) and potentially allow the untrusted network to take over
internal services that are accessed using short names. This could happen
by mistake also (such as setting "mail" as your smtp server if the
remote network uses the same name).

I don't think the order of the lookups can be controlled to prevent
this, for example what should determine the order when you have to VPN
active?

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

Title:
  DNS domain search paths not updated when VPN started

Status in network-manager package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh 

[Touch-packages] [Bug 1732678] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

[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 fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1732678

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  attempted upgrade and had crash during install.
  Resumed install, this is result.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  Date: Wed Nov 15 19:25:52 2017
  ErrorMessage: triggers looping, abandoned
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2017-11-16 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1732678/+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 1732678] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

[Lo]

Public bug reported:

attempted upgrade and had crash during install.
Resumed install, this is result.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.12
Architecture: amd64
Date: Wed Nov 15 19:25:52 2017
ErrorMessage: triggers looping, abandoned
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: fontconfig
Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to xenial on 2017-11-16 (0 days ago)

** Affects: fontconfig (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 fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1732678

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  attempted upgrade and had crash during install.
  Resumed install, this is result.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  Date: Wed Nov 15 19:25:52 2017
  ErrorMessage: triggers looping, abandoned
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2017-11-16 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1732678/+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 1700011] Re: package libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1 failed to install/upgrade: package libmirclient9:amd64 is not ready for configuration cannot configure (cu

[Alan Griffiths]

It looks as though there is a failing attempt to upgrade some of the Mir
libraries (probably Mir 0.24 to Mir 0.26) as IIRC the 16.04.2 shipped
before that update in the archive.

If that theory is correct, it will be fixed by:

$ sudo apt dist-upgrade

In addition, it shouldn't happen with the current ubuntu-16.04.3
-desktop-amd64.iso

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

Title:
  package libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1 failed to
  install/upgrade: package libmirclient9:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in mir package in Ubuntu:
  Confirmed

Bug description:
  i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 23 14:19:00 2017
  DuplicateSignature:
   package:libmirclient9:amd64:0.26.3+16.04.20170605-0ubuntu1
   Setting up libc6-i386 (2.23-0ubuntu9) ...
   dpkg: error processing package libmirclient9:amd64 (--configure):
package libmirclient9:amd64 is not ready for configuration
  ErrorMessage: package libmirclient9:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-11 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: mir
  Title: package libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1 failed to 
install/upgrade: package libmirclient9:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1700011/+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 1732676] [NEW] package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package ke

[Dan Lewis]

Public bug reported:

Errors were encountered while processing:
 /var/cache/apt/archives/console-setup-linux_1.170_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Kali 2017.3
Package: console-setup-linux 1.108ubuntu15.3
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Nov 16 03:47:46 2017
ErrorMessage: trying to overwrite '/lib/systemd/system/console-setup.service', 
which is also in package keyboard-configuration 1.108ubuntu15.3
InstallationDate: Installed on 2017-10-08 (39 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.19.0.4kali1
 apt  1.2.24
SourcePackage: console-setup
Title: package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade: 
trying to overwrite '/lib/systemd/system/console-setup.service', which is also 
in package keyboard-configuration 1.108ubuntu15.3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package kali-rolling third-party-packages

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

Title:
  package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade:
  trying to overwrite '/lib/systemd/system/console-setup.service', which
  is also in package keyboard-configuration 1.108ubuntu15.3

Status in console-setup package in Ubuntu:
  New

Bug description:
  Errors were encountered while processing:
   /var/cache/apt/archives/console-setup-linux_1.170_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Kali 2017.3
  Package: console-setup-linux 1.108ubuntu15.3
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Nov 16 03:47:46 2017
  ErrorMessage: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.3
  InstallationDate: Installed on 2017-10-08 (39 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.19.0.4kali1
   apt  1.2.24
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade: 
trying to overwrite '/lib/systemd/system/console-setup.service', which is also 
in package keyboard-configuration 1.108ubuntu15.3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1732676/+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 1700011] Re: package libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1 failed to install/upgrade: package libmirclient9:amd64 is not ready for configuration cannot configure (cu

[Launchpad Bug Tracker]

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

** Changed in: mir (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1 failed to
  install/upgrade: package libmirclient9:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in mir package in Ubuntu:
  Confirmed

Bug description:
  i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 23 14:19:00 2017
  DuplicateSignature:
   package:libmirclient9:amd64:0.26.3+16.04.20170605-0ubuntu1
   Setting up libc6-i386 (2.23-0ubuntu9) ...
   dpkg: error processing package libmirclient9:amd64 (--configure):
package libmirclient9:amd64 is not ready for configuration
  ErrorMessage: package libmirclient9:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-11 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: mir
  Title: package libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1 failed to 
install/upgrade: package libmirclient9:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1700011/+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 1716670] Re: package libmirclient9:amd64 0.21.0+16.04.20160330-0ubuntu1 failed to install/upgrade: пакет libmirclient9:amd64 не готов к настройке настройка невозможна (текущее с

[Alan Griffiths]

*** This bug is a duplicate of bug 1700011 ***
https://bugs.launchpad.net/bugs/1700011

** This bug has been marked a duplicate of bug 1700011
   package libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1 failed to 
install/upgrade: package libmirclient9:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')

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

Title:
  package libmirclient9:amd64 0.21.0+16.04.20160330-0ubuntu1 failed to
  install/upgrade: пакет libmirclient9:amd64 не готов к настройке
  настройка невозможна (текущее состояние: «half-installed»)

Status in mir package in Ubuntu:
  New

Bug description:
  install updates system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libmirclient9:amd64 0.21.0+16.04.20160330-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Sep 12 15:58:02 2017
  ErrorMessage: пакет libmirclient9:amd64 не готов к настройке  настройка 
невозможна (текущее состояние: «half-installed»)
  InstallationDate: Installed on 2017-09-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: mir
  Title: package libmirclient9:amd64 0.21.0+16.04.20160330-0ubuntu1 failed to 
install/upgrade: пакет libmirclient9:amd64 не готов к настройке  настройка 
невозможна (текущее состояние: «half-installed»)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1716670/+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 1732672] Re: package libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es no

[Alan Griffiths]

*** This bug is a duplicate of bug 1700011 ***
https://bugs.launchpad.net/bugs/1700011

** This bug has been marked a duplicate of bug 1700011
   package libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1 failed to 
install/upgrade: package libmirclient9:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')

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

Title:
  package libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1.1 failed to
  install/upgrade: Paket ist in einem sehr schlechten inkonsistenten
  Zustand - Sie sollten es  nochmal installieren, bevor Sie die
  Konfiguration versuchen.

Status in mir package in Ubuntu:
  New

Bug description:
  On Start Screen i got Information about an Error and if i want to
  report it. I really don't know anything about it. I'm a Linux-Noob,
  sorry :D

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  Date: Thu Nov 16 07:06:45 2017
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  InstallationDate: Installed on 2017-09-28 (48 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: mir
  Title: package libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1.1 failed to 
install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - 
Sie sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1732672/+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 1728188] Re: Don't build pulseaudio with trust-store support

[Łukasz Zemczak]

I'm looking into getting rid of the trust-store integration. If it's
trivial enough I might do it myself to get trust-store out of libboost's
way. Looking of course to see what changes need to be left for the
snappy parts to work.

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

Title:
  Don't build pulseaudio with trust-store support

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Please check whether we still need to build pulseaudio with trust-
  store support or if we can drop it and remove trust-store from Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1728188/+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 1732672] [NEW] package libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es

[Reiner Totzek]

Public bug reported:

On Start Screen i got Information about an Error and if i want to report
it. I really don't know anything about it. I'm a Linux-Noob, sorry :D

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.12
Architecture: amd64
Date: Thu Nov 16 07:06:45 2017
ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
InstallationDate: Installed on 2017-09-28 (48 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: mir
Title: package libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1.1 failed to 
install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - 
Sie sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mir (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 mir in Ubuntu.
https://bugs.launchpad.net/bugs/1732672

Title:
  package libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1.1 failed to
  install/upgrade: Paket ist in einem sehr schlechten inkonsistenten
  Zustand - Sie sollten es  nochmal installieren, bevor Sie die
  Konfiguration versuchen.

Status in mir package in Ubuntu:
  New

Bug description:
  On Start Screen i got Information about an Error and if i want to
  report it. I really don't know anything about it. I'm a Linux-Noob,
  sorry :D

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  Date: Thu Nov 16 07:06:45 2017
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  InstallationDate: Installed on 2017-09-28 (48 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: mir
  Title: package libmirclient9:amd64 0.26.3+16.04.20170605-0ubuntu1.1 failed to 
install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - 
Sie sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1732672/+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 1732595] Re: dont know

[Steve Beattie]

Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

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

** Tags added: xenial

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

Title:
  dont know

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  dont know

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Nov 15 22:27:02 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   vboxguest, 5.0.14, 4.4.0-101-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
   virtualbox, 5.0.40, 4.4.0-101-generic, x86_64: installed
   virtualbox-guest, 5.0.40, 4.4.0-101-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell OptiPlex 755 [1028:0211]
 Subsystem: Dell OptiPlex 755 [1028:0211]
  InstallationDate: Installed on 2017-11-13 (3 days ago)
  InstallationMedia: Linux Lite 2.8 64-bit - Release amd64
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-101-generic 
root=UUID=9e37a8d2-938f-47f8-aed7-14c07877368d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd06/11/2012:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Nov 15 18:50:59 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputB16_b_02 USB-PS/2 Optical Mouse MOUSE, id 8
   inputUSB USB Keykoard KEYBOARD, id 9
   inputUSB USB Keykoard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id2448 
   vendor LEN
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1732595/+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 1732559] Re: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: end of file on stdin at conffile prompt

[Steve Beattie]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: end of
  file on stdin at conffile prompt

Status in apport package in Ubuntu:
  New

Bug description:
  weather applet crashes on logou

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.12
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CrashReports: 600:0:116:2842973:2017-11-15 19:14:12.331785678 
-0400:2017-11-15 19:14:13.331785678 -0400:/var/crash/apport.0.crash
  Date: Wed Nov 15 19:14:13 2017
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2016-08-04 (468 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: end of 
file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.apport.conf: 2016-04-13T22:46:42
  mtime.conffile..etc.init.d.apport: 2016-03-31T09:43:38
  mtime.conffile..etc.logrotate.d.apport: 2016-04-13T22:46:42

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1732559/+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 1732120] Re: i can't login correctly..

[Steve Beattie]

** Information type changed from Private Security to Public

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

Title:
  i can't login correctly..

Status in xorg package in Ubuntu:
  New

Bug description:
  initframes command line executed at startup.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Nov 14 14:56:58 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c]
  InstallationDate: Installed on 2017-11-07 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20351
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=ce1a215d-419c-4fbe-b91e-7c44679d5575 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN32WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN32WW:bd07/20/2015:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Nov 14 11:14:44 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1732120/+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 1724808] Re: osd progress looks odd using Ambiance or Radiance

[Jean-Baptiste Lallement]

SRU verification for Artful:
I have reproduced the problem with ubuntu-themes 
16.10+17.10.20171012.1-0ubuntu1 in artful and have verified that the version of 
ubuntu-themes 16.10+17.10.20171115-0ubuntu1 in -proposed fixes the issue.

Marking as verification-done


** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful

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

** Changed in: ubuntu-themes (Ubuntu Artful)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

Title:
  osd progress looks odd using Ambiance or Radiance

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  == Impact ==
  osd progress bars look poor with Ambiance or Radiance in Ubuntu 17.10.
  osd progress bars are used e.g. in epiphany web browser.

  == Test Case ==
  1. Open gnome control center
  2. Go to online accounts panel
  3. Add a google account
  4. Make sure the progress bar close to the title bar of the login dialog does 
not present borders and paddings.

  == Potential Regressions ==
  Please check thare are no regressions with osd toolbars. An example of 
application using osd toolbars is totem. Make sure the overlay with play/pause 
controls is not affected by the fix.

  == Original Bug Report ==
  osd progress bar, used e.g. the one used by epiphany-browser when loading 
pages, looks odd with Ambiance or Radiance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1724808/+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 1721102] Re: Thin line at the left of Simple Scan's "Scan" headerbar button

[Jean-Baptiste Lallement]

SRU verification for Artful:
I have reproduced the problem with ubuntu-themes 
16.10+17.10.20171012.1-0ubuntu1 in artful and have verified that the version of 
ubuntu-themes 16.10+17.10.20171115-0ubuntu1 in -proposed fixes the issue.

Marking as verification-done


** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful

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

** Changed in: ubuntu-themes (Ubuntu Artful)
 Assignee: (unassigned) => Carlo Lobrano (c-lobrano)

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

Title:
  Thin line at the left of Simple Scan's "Scan" headerbar button

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  There is a thin colored line (green or red) at the left of rounded button, 
for example in simple-scan in the screenshot attached (I didn't find any other 
app affected ATM)

  [Test case]
  1. Run simple scan
  2. Expect "Scan" button background color to fill all the space.

  4. Start scanning and expect the same for "Stop" button too

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170930-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  3 20:16:32 2017
  InstallationDate: Installed on 2013-09-03 (1490 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1721102/+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 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

[Jean-Baptiste Lallement]

SRU verification for Artful:
I have reproduced the problem with ubuntu-themes 
16.10+17.10.20171012.1-0ubuntu1 in artful and have verified that the version of 
ubuntu-themes 16.10+17.10.20171115-0ubuntu1 in -proposed fixes the issue.

Marking as verification-done


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

** Changed in: ubuntu-themes (Ubuntu Artful)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  That installation is a default Ubuntu , no Mate installed, and
  Ambiance is set for 'applications' into tweaks

  [Test case]

  1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal
  2. App has to run without any error

  [Possible regression]

  Different scrollbars in gtk2 apps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1723422/+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 1719355] Re: Switcher widget background goes outside its border

[Jean-Baptiste Lallement]

SRU verification for Artful:
I have reproduced the problem with ubuntu-themes 
16.10+17.10.20171012.1-0ubuntu1 in artful and have verified that the version of 
ubuntu-themes 16.10+17.10.20171115-0ubuntu1 in -proposed fixes the issue.

Marking as verification-done


** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful

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

** Changed in: ubuntu-themes (Ubuntu Artful)
 Assignee: (unassigned) => Carlo Lobrano (c-lobrano)

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

Title:
  Switcher widget background goes outside its border

Status in Ubuntu theme:
  In Progress
Status in Ubuntu UX:
  New
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  In both Ambiance and Radiance themes, the switcher background is
  visible outside the widget border when inside a headerbar.

  See picture from Gnome Control Settings -> Search

  [Test case]

  1. Open Gnome Control Settings -> Search
  2. Ensure that no extra border is around the switcher (especially in the 
headerbar)

  [Regression potential]

  Switchers  borders are incorrect

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1719355/+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 1726318] Re: Destructive actions on headerbar aren't properly themed

[Jean-Baptiste Lallement]

SRU verification for Artful:
I have reproduced the problem with ubuntu-themes 
16.10+17.10.20171012.1-0ubuntu1 in artful and have verified that the version of 
ubuntu-themes 16.10+17.10.20171115-0ubuntu1 in -proposed fixes the issue.

Marking as verification-done


** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful

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

** Changed in: ubuntu-themes (Ubuntu Artful)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Destructive actions on headerbar aren't properly themed

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [ Impact ]

  On simple scan (for example) there's a .destructive-action button in
  the headerbar and it's not drawn as red unless the button is hovered,
  clicked or unfocused. It also uses inconsistent gradients

  [ Test case ]

  1. Run gnome-scan
  2. Start a scan session (or use the inspector to set the "Stop" button as 
visible)
  3. Expect it to be red in all the cases (focused, pressed, unfocused, hovered)

  [ Regression Potential]

  Destructive buttons in headerbar could be broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1726318/+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 1726322] Re: Suggested and Destructive action buttons in headerbar have wrong gradients in maximized windows

[Jean-Baptiste Lallement]

SRU verification for Artful:
I have reproduced the problem with ubuntu-themes 
16.10+17.10.20171012.1-0ubuntu1 in artful and have verified that the version of 
ubuntu-themes 16.10+17.10.20171115-0ubuntu1 in -proposed fixes the issue.

Marking as verification-done


** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful

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

** Changed in: ubuntu-themes (Ubuntu Artful)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Suggested and Destructive action buttons in headerbar have wrong
  gradients in maximized windows

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Suggested and Desctructive action (simple-scan is an example for both)
  buttons still have the "normal" gradient when the window is maximized,
  while this should be inverted.

  See https://usercontent.irccloud-cdn.com/file/hm2uCy3D/image.png
  (shown both for reference)

  [Test case]

  1. Run simple scan
  2. Maximize the window
  3. The gradient should have consistent direction with other buttons around

  [Regression potential]

  Background gradients for windows with such buttons might be wrong in
  normal windows.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1726322/+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 1732044] Re: /usr/sbin/NetworkManager:11:nm_device_remove_pending_action:queued_set_state:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate

[Sebastien Bacher]

There has been no reported in recent versions, assuming it's fixed there

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Released

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

Title:
  
/usr/sbin/NetworkManager:11:nm_device_remove_pending_action:queued_set_state:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
network-manager.  This problem was most recently seen with package version 
1.4.4-1ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/7815ce42fb3209d74c2ccf84a2df89e18b3283c1 
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/network-manager/+bug/1732044/+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 1732173] Re: Java GUI apps do not work properly under Wayland

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

** Tags added: wayland

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

Title:
  Java GUI apps do not work properly under Wayland

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 17.10 with Wayland enabled. I noticed Java GUI apps
  running with native look and feel (i.e. Swing based apps with GTK look
  and feel) do not properly work, i.e. fonts are not displayed properly,
  windows sometimes do not draw correctly and other problems.

  If I switch to X11 all works fine instead.

  The Java version is:

  java version "1.8.0_152"
  Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
  Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 14 12:20:33 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07bf]
 Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf]
  InstallationDate: Installed on 2017-10-24 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5520
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=4f5a6ba3-2eb6-42d3-aa57-c85c628e312d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.4
  dmi.board.name: 0X41RR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1732173/+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 1728188] Re: Don't build pulseaudio with trust-store support

[Sebastien Bacher]

Daniel is on holiday for some weeks you better don't block on him there

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

Title:
  Don't build pulseaudio with trust-store support

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Please check whether we still need to build pulseaudio with trust-
  store support or if we can drop it and remove trust-store from Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1728188/+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 1732422] Re: glue-sprite: Inconsistent dependencies

[Sebastien Bacher]

** Package changed: apport (Ubuntu) => glue (Ubuntu)

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

Title:
  glue-sprite: Inconsistent dependencies

Status in glue package in Ubuntu:
  New

Bug description:
  It's about the glue-sprite package (sudo apt install glue-sprite).
  The latest version of glue-sprite (0.11.1) does not work due to the 
dependency:
  Python package (/usr/lib/python3/dist-packages/glue-0.11.1.egg-info) depends 
on Jinja2>=2.7,<2.8 (requires.txt) but there is no appropriate version

  /etc/apt$ sudo dpkg -l | grep jinj
  ii  python3-jinja2   2.8-1  all   
   small but fast and easy to use stand-alone template engine

  So the dependancy is "Jinja2>=2.7,<2.8" but the latest version is
  2.8-1 !

  The original bug on Debian is here https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=860169

  System info:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glue/+bug/1732422/+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 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

[Treviño]

** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  That installation is a default Ubuntu , no Mate installed, and
  Ambiance is set for 'applications' into tweaks

  [Test case]

  1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal
  2. App has to run without any error

  [Possible regression]

  Different scrollbars in gtk2 apps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1723422/+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 1732629] [NEW] Selecting USB Amp/Dac audio output in gnome sound does nothing

[Sergio Bossa]

Public bug reported:

Running Ubuntu 17.10, when I plug an external USB Amp/Dac it is
correctly recognized and I can play audio through it via aplay, but when
I select it as my output sink from gnome sound, nothing happens: apps
still output sound via the speakers.

In order to fix it I have to restart pulseaudio.
I've also found online that modifying /etc/pulse/default.pa, moving 
module-switch-on-connect.so loading before module-udev-detect.so, permanently 
fixes the issue.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0p:   sergio 1374 F...m pulseaudio
 /dev/snd/controlC1:  sergio 1374 F pulseaudio
 /dev/snd/controlC0:  sergio 1374 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 16 09:03:19 2017
InstallationDate: Installed on 2017-10-24 (22 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.4
dmi.board.name: 0X41RR
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA02:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2017-11-15T18:42:36.359190

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


** Tags: amd64 apport-bug artful

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

Title:
  Selecting USB Amp/Dac audio output in gnome sound does nothing

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Running Ubuntu 17.10, when I plug an external USB Amp/Dac it is
  correctly recognized and I can play audio through it via aplay, but
  when I select it as my output sink from gnome sound, nothing happens:
  apps still output sound via the speakers.

  In order to fix it I have to restart pulseaudio.
  I've also found online that modifying /etc/pulse/default.pa, moving 
module-switch-on-connect.so loading before module-udev-detect.so, permanently 
fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   sergio 1374 F...m pulseaudio
   /dev/snd/controlC1:  sergio 1374 F pulseaudio
   /dev/snd/controlC0:  sergio 1374 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 16 09:03:19 2017
  InstallationDate: Installed on 2017-10-24 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.4
  dmi.board.name: 0X41RR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-11-15T18:42:36.359190

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1732629/+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 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space

[Deon Joubert]

** Changed in: initramfs-tools (Ubuntu)
 Assignee: lizehao (lllwonder) => Deon Joubert (02deon-j)

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space

Status in initramfs-tools:
  Confirmed
Status in Ubuntu Software Center:
  Invalid
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

[Thijs Kinkhorst]

Upgrading from proposed-updates fixes the problem for me.

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  That installation is a default Ubuntu , no Mate installed, and
  Ambiance is set for 'applications' into tweaks

  [Test case]

  1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal
  2. App has to run without any error

  [Possible regression]

  Different scrollbars in gtk2 apps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1723422/+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 1727365] Re: gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type() from intel_update_image_buffers() from intel_update_renderbuffers()

[TLE]

** Attachment added: "SA650-xrandr"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727365/+attachment/5009931/+files/SA650-xrandr

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

Title:
  gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type() from
  intel_update_image_buffers() from intel_update_renderbuffers()

Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  This bug is triggered for me by leaving the system inactive for a time
  and it happens whether the system settings is set to lock the screen
  or not, but I can be provoked by locking the screen. At the time when
  I want to reactivate the system (as I can see on the time stamp on the
  crash report), something happens and I loose the entire login session
  and am dropped at the login screen to login anew. This has lead me to
  believe that this has to do with re-enabling the display.

  The effect of this bug is that I loose *all* running programs in my
  session and has to start everything up again, which means that Ubuntu
  17.10 is basically unusable for me. For this reason, of course
  depending on how many people are affected, I think this should be
  considered a high priority bug.

  This is a fresh install with no shenanigans except installing a few
  programs that I needed.

  I happy to provide any extra information is required and to any kind
  of testing that might be required as long as I can return to a non-
  modified system after test.

  Mandatory info:
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  apt-cache policy gnome-shell
  gnome-shell:
Installeret: 3.26.1-0ubuntu4
Kandidat:3.26.1-0ubuntu4
Versionstabel:
   *** 3.26.1-0ubuntu4 500
  500 http://dk.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 16:11:36 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'commandout...@elken.tdos.gmail.com']"
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-23 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f37ebf9cf80:push   %rdx
   PC (0x7f37ebf9cf80) in non-executable VMA region: 
0x7f37ebf99000-0x7f37ec00 rw-p None
   source "%rdx" ok
   destination "(%rsp)" (0x7fff6f7a1cb8) ok
  SegvReason: executing writable VMA None
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __bss_start () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so
  Title: gnome-shell crashed with SIGSEGV in __bss_start()
  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/gnome-shell/+bug/1727365/+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 1727365] Re: gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type() from intel_update_image_buffers() from intel_update_renderbuffers()

[TLE]

** Attachment added: "Z27s-get-edid"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727365/+attachment/5009928/+files/Z27s-get-edid

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

Title:
  gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type() from
  intel_update_image_buffers() from intel_update_renderbuffers()

Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  This bug is triggered for me by leaving the system inactive for a time
  and it happens whether the system settings is set to lock the screen
  or not, but I can be provoked by locking the screen. At the time when
  I want to reactivate the system (as I can see on the time stamp on the
  crash report), something happens and I loose the entire login session
  and am dropped at the login screen to login anew. This has lead me to
  believe that this has to do with re-enabling the display.

  The effect of this bug is that I loose *all* running programs in my
  session and has to start everything up again, which means that Ubuntu
  17.10 is basically unusable for me. For this reason, of course
  depending on how many people are affected, I think this should be
  considered a high priority bug.

  This is a fresh install with no shenanigans except installing a few
  programs that I needed.

  I happy to provide any extra information is required and to any kind
  of testing that might be required as long as I can return to a non-
  modified system after test.

  Mandatory info:
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  apt-cache policy gnome-shell
  gnome-shell:
Installeret: 3.26.1-0ubuntu4
Kandidat:3.26.1-0ubuntu4
Versionstabel:
   *** 3.26.1-0ubuntu4 500
  500 http://dk.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 16:11:36 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'commandout...@elken.tdos.gmail.com']"
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-23 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f37ebf9cf80:push   %rdx
   PC (0x7f37ebf9cf80) in non-executable VMA region: 
0x7f37ebf99000-0x7f37ec00 rw-p None
   source "%rdx" ok
   destination "(%rsp)" (0x7fff6f7a1cb8) ok
  SegvReason: executing writable VMA None
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __bss_start () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so
  Title: gnome-shell crashed with SIGSEGV in __bss_start()
  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/gnome-shell/+bug/1727365/+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 1727365] Re: gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type() from intel_update_image_buffers() from intel_update_renderbuffers()

[TLE]

** Attachment added: "SA650-get-edid"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727365/+attachment/5009930/+files/SA650-get-edid

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

Title:
  gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type() from
  intel_update_image_buffers() from intel_update_renderbuffers()

Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  This bug is triggered for me by leaving the system inactive for a time
  and it happens whether the system settings is set to lock the screen
  or not, but I can be provoked by locking the screen. At the time when
  I want to reactivate the system (as I can see on the time stamp on the
  crash report), something happens and I loose the entire login session
  and am dropped at the login screen to login anew. This has lead me to
  believe that this has to do with re-enabling the display.

  The effect of this bug is that I loose *all* running programs in my
  session and has to start everything up again, which means that Ubuntu
  17.10 is basically unusable for me. For this reason, of course
  depending on how many people are affected, I think this should be
  considered a high priority bug.

  This is a fresh install with no shenanigans except installing a few
  programs that I needed.

  I happy to provide any extra information is required and to any kind
  of testing that might be required as long as I can return to a non-
  modified system after test.

  Mandatory info:
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  apt-cache policy gnome-shell
  gnome-shell:
Installeret: 3.26.1-0ubuntu4
Kandidat:3.26.1-0ubuntu4
Versionstabel:
   *** 3.26.1-0ubuntu4 500
  500 http://dk.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 16:11:36 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'commandout...@elken.tdos.gmail.com']"
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-23 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f37ebf9cf80:push   %rdx
   PC (0x7f37ebf9cf80) in non-executable VMA region: 
0x7f37ebf99000-0x7f37ec00 rw-p None
   source "%rdx" ok
   destination "(%rsp)" (0x7fff6f7a1cb8) ok
  SegvReason: executing writable VMA None
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __bss_start () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so
  Title: gnome-shell crashed with SIGSEGV in __bss_start()
  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/gnome-shell/+bug/1727365/+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 1727365] Re: gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type() from intel_update_image_buffers() from intel_update_renderbuffers()

[TLE]

** Attachment added: "Z27s-xrandr"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727365/+attachment/5009929/+files/Z27s-xrandr

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

Title:
  gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type() from
  intel_update_image_buffers() from intel_update_renderbuffers()

Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  This bug is triggered for me by leaving the system inactive for a time
  and it happens whether the system settings is set to lock the screen
  or not, but I can be provoked by locking the screen. At the time when
  I want to reactivate the system (as I can see on the time stamp on the
  crash report), something happens and I loose the entire login session
  and am dropped at the login screen to login anew. This has lead me to
  believe that this has to do with re-enabling the display.

  The effect of this bug is that I loose *all* running programs in my
  session and has to start everything up again, which means that Ubuntu
  17.10 is basically unusable for me. For this reason, of course
  depending on how many people are affected, I think this should be
  considered a high priority bug.

  This is a fresh install with no shenanigans except installing a few
  programs that I needed.

  I happy to provide any extra information is required and to any kind
  of testing that might be required as long as I can return to a non-
  modified system after test.

  Mandatory info:
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  apt-cache policy gnome-shell
  gnome-shell:
Installeret: 3.26.1-0ubuntu4
Kandidat:3.26.1-0ubuntu4
Versionstabel:
   *** 3.26.1-0ubuntu4 500
  500 http://dk.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 16:11:36 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'commandout...@elken.tdos.gmail.com']"
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-23 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f37ebf9cf80:push   %rdx
   PC (0x7f37ebf9cf80) in non-executable VMA region: 
0x7f37ebf99000-0x7f37ec00 rw-p None
   source "%rdx" ok
   destination "(%rsp)" (0x7fff6f7a1cb8) ok
  SegvReason: executing writable VMA None
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __bss_start () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so
  Title: gnome-shell crashed with SIGSEGV in __bss_start()
  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/gnome-shell/+bug/1727365/+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 1727365] Re: gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type() from intel_update_image_buffers() from intel_update_renderbuffers()

[TLE]

As additional information, I can add that this bug seems to correlate
with monitor type or screen resolution.

When I encountered the error (all the time), I was using a high res HP
Z27s monitor (I attached get-edid and xrand information with Z27s
prefixes). However, since I couldn't work with the bug in effect, I had
to do something and so I tried changing to a normal Samsung SyncMaster
SA650 monitor (information attached with SA650 prefixes) and since then
I haven't experienced the bug.

I hope this extra information is useful. I'm happy to do further
troubleshooting if necessary.

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

Title:
  gnome-shell crashed with SIGSEGV in glsl_type::_vec4_type() from
  intel_update_image_buffers() from intel_update_renderbuffers()

Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  This bug is triggered for me by leaving the system inactive for a time
  and it happens whether the system settings is set to lock the screen
  or not, but I can be provoked by locking the screen. At the time when
  I want to reactivate the system (as I can see on the time stamp on the
  crash report), something happens and I loose the entire login session
  and am dropped at the login screen to login anew. This has lead me to
  believe that this has to do with re-enabling the display.

  The effect of this bug is that I loose *all* running programs in my
  session and has to start everything up again, which means that Ubuntu
  17.10 is basically unusable for me. For this reason, of course
  depending on how many people are affected, I think this should be
  considered a high priority bug.

  This is a fresh install with no shenanigans except installing a few
  programs that I needed.

  I happy to provide any extra information is required and to any kind
  of testing that might be required as long as I can return to a non-
  modified system after test.

  Mandatory info:
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  apt-cache policy gnome-shell
  gnome-shell:
Installeret: 3.26.1-0ubuntu4
Kandidat:3.26.1-0ubuntu4
Versionstabel:
   *** 3.26.1-0ubuntu4 500
  500 http://dk.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 16:11:36 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'commandout...@elken.tdos.gmail.com']"
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-23 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f37ebf9cf80:push   %rdx
   PC (0x7f37ebf9cf80) in non-executable VMA region: 
0x7f37ebf99000-0x7f37ec00 rw-p None
   source "%rdx" ok
   destination "(%rsp)" (0x7fff6f7a1cb8) ok
  SegvReason: executing writable VMA None
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __bss_start () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so
  Title: gnome-shell crashed with SIGSEGV in __bss_start()
  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/gnome-shell/+bug/1727365/+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 1728791] Re: [SRU] pulseaudio-droid module crashes on start

[bhushan]

I can confirm that proposed package works as intended.

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

Title:
  [SRU] pulseaudio-droid module crashes on start

Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 16.04 Xenial, and pulseaudio version 8.0-0ubuntu3.4

  [Impact]

   * This bug prevents users (currently Project Halium, UBports, Plasma Mobile) 
from using the pulseaudio-modules-droid on android devices.
   * This behavior can be seen in Ubuntu Xenial 16.04 with xenial-updates 
enabled.
   * Last 3 releases of pulseaudio included multiple patches which modified 
behavior of pulsecore library but required changes were not made in 
pulseaudio-module-droid.
   * This results in crash in pulseaudio-modules-droid

  
  #0  init_profile (u=0x59528) at modules/droid/module-droid-card.c:370
  #1  module_droid_card_22_LTX_pa__init (m=0x3c3f8) at 
modules/droid/module-droid-card.c:923
  #2  0xf76feb88 in pa_module_load (c=c@entry=0x33a80, name=name@entry=0x58240 
"module-droid-card-22", argument=0x0) at pulsecore/module.c:180
  #3  0xf76f1d7e in pa_cli_command_load (c=0x33a80, t=0x49320, buf=0x44f28, 
fail=0x3c1f4) at pulsecore/cli-command.c:439
  #4  0xf76f6ad8 in pa_cli_command_execute_line_stateful (c=0x33a80, 
s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, 
fail=fail@entry=0x3c1f4, ifstate=ifstate@entry=0x0) at 
pulsecore/cli-command.c:2134
  #5  0xf76f6fc8 in pa_cli_command_execute_line (c=, 
s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, 
fail=fail@entry=0x3c1f4) at pulsecore/cli-command.c:2155
  #6  0xee32fc82 in line_callback (line=0x3c208, s=0x59120 "load-module 
module-droid-card-22", userdata=0x3c1e0) at pulsecore/cli.c:153
  #7  0xf76a1360 in scan_for_lines (skip=, l=0x3c208) at 
pulsecore/ioline.c:269
  #8  do_read (l=0x3c208) at pulsecore/ioline.c:337
  #9  do_work (l=0x3c208) at pulsecore/ioline.c:386
  #10 0xf7655fa6 in dispatch_pollfds (m=0x32bd0) at pulse/mainloop.c:655
  #11 pa_mainloop_dispatch (m=m@entry=0x32bd0) at pulse/mainloop.c:898
  #12 0xf765629a in pa_mainloop_iterate (m=0x32bd0, block=, 
retval=0xfffef1c4) at pulse/mainloop.c:929
  #13 0xf7656314 in pa_mainloop_run (m=m@entry=0x32bd0, 
retval=retval@entry=0xfffef1c4) at pulse/mainloop.c:944
  #14 0x000158ca in main (argc=, argv=) at 
daemon/main.c:1152

  
  [Test Case]

   * Start pulseaudio
   * From another session run pacmd
   * In prompt type load-module module-droid-discover
   * On ubuntu touch devices, it will crash at startup

  [Regression Potential]

   * There is no regression potential for other parts of pulseaudio
  components.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1728791/+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 1725644] Re: package linux-firmware 1.169 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-firmware 1.169 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Error appears during upgrade from 17.04 to 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-firmware 1.169
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 21 10:33:30 2017
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.169 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)

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