[Touch-packages] [Bug 1695758] Re: package python-prompt-toolkit 1.0.9-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Scott Kitterman]

Traceback (most recent call last):
  File "/usr/bin/pycompile", line 35, in 
from debpython.version import SUPPORTED, debsorted, vrepr, \
  File "/usr/share/python/debpython/version.py", line 24, in 
from ConfigParser import SafeConfigParser
ImportError: No module named 'ConfigParser'

** Package changed: prompt-toolkit (Ubuntu) => python3-defaults (Ubuntu)

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

Title:
  package python-prompt-toolkit 1.0.9-1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  when I run sudo apt-get upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python-prompt-toolkit 1.0.9-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sun Jun  4 12:45:25 2017
  Dependencies:
   python-pkg-resources 33.1.1-1
   python-pygments 2.2.0+dfsg-1
   python-six 1.10.0-3
   python-wcwidth 0.1.7+dfsg1-1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-06-01 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: prompt-toolkit
  Title: package python-prompt-toolkit 1.0.9-1 failed to install/upgrade: 
subprocess installed post-installation 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/python3-defaults/+bug/1695758/+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 1695758] [NEW] package python-prompt-toolkit 1.0.9-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

when I run sudo apt-get upgrade

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: python-prompt-toolkit 1.0.9-1
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Sun Jun  4 12:45:25 2017
Dependencies:
 python-pkg-resources 33.1.1-1
 python-pygments 2.2.0+dfsg-1
 python-six 1.10.0-3
 python-wcwidth 0.1.7+dfsg1-1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-06-01 (2 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: prompt-toolkit
Title: package python-prompt-toolkit 1.0.9-1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty
-- 
package python-prompt-toolkit 1.0.9-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/1695758
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to python3-defaults in Ubuntu.

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

[Touch-packages] [Bug 1698612] [NEW] package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: telepítve post-installation parancsfájl alfolyamat 128 hibakóddal kilépett

[Lvadkerti]

Public bug reported:

this problem comes up after aech booting

ProblemType: Package
DistroRelease: elementary 0.4.1
Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Tue May 23 18:21:04 2017
ErrorMessage: telepítve post-installation parancsfájl alfolyamat 128 hibakóddal 
kilépett
InstallationDate: Installed on 2017-05-22 (26 days ago)
InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to 
install/upgrade: telepítve post-installation parancsfájl alfolyamat 128 
hibakóddal kilépett
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package loki third-party-packages

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

Title:
  package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to
  install/upgrade: telepítve post-installation parancsfájl alfolyamat
  128 hibakóddal kilépett

Status in gconf package in Ubuntu:
  New

Bug description:
  this problem comes up after aech booting

  ProblemType: Package
  DistroRelease: elementary 0.4.1
  Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue May 23 18:21:04 2017
  ErrorMessage: telepítve post-installation parancsfájl alfolyamat 128 
hibakóddal kilépett
  InstallationDate: Installed on 2017-05-22 (26 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to 
install/upgrade: telepítve post-installation parancsfájl alfolyamat 128 
hibakóddal kilépett
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1698612/+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 1698610] Re: package apport 2.20.4-0ubuntu4 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuració

[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/1698610

Title:
  package apport 2.20.4-0ubuntu4 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

Status in apport package in Ubuntu:
  New

Bug description:
  When I start the computer, an error message appears (I do not speak
  English, I do not know what it says), it asks me for my password to
  install a pluggin, but then tells me that the fault can not be solved.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic i686
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CrashReports:
   600:114:122:0:2017-06-12 01:15:08.678625626 -0400:2017-06-12 
01:15:08.678625626 -0400:/var/crash/_usr_bin_webbrowser-app.1000.uploaded
   600:0:122:85429:2017-06-18 00:30:38.761001825 -0400:2017-06-18 
00:30:39.761001825 -0400:/var/crash/apport.0.crash
   640:1000:122:14174623:2017-06-12 01:15:02.452246904 -0400:2017-06-12 
01:15:03.552214190 -0400:/var/crash/_usr_bin_webbrowser-app.1000.crash
   644:1000:122:0:2017-06-12 01:15:03.452246962 -0400:2017-06-12 
01:15:03.452246962 -0400:/var/crash/_usr_bin_webbrowser-app.1000.upload
  Date: Sun Jun 18 00:30:39 2017
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2016-11-08 (222 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package apport 2.20.4-0ubuntu4 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/apport/+bug/1698610/+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 1698610] [NEW] package apport 2.20.4-0ubuntu4 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configurac

[Rafael Ojeda C]

Public bug reported:

When I start the computer, an error message appears (I do not speak
English, I do not know what it says), it asks me for my password to
install a pluggin, but then tells me that the fault can not be solved.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: apport 2.20.4-0ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic i686
ApportLog:
 
ApportVersion: 2.20.4-0ubuntu4
Architecture: i386
CrashReports:
 600:114:122:0:2017-06-12 01:15:08.678625626 -0400:2017-06-12 
01:15:08.678625626 -0400:/var/crash/_usr_bin_webbrowser-app.1000.uploaded
 600:0:122:85429:2017-06-18 00:30:38.761001825 -0400:2017-06-18 
00:30:39.761001825 -0400:/var/crash/apport.0.crash
 640:1000:122:14174623:2017-06-12 01:15:02.452246904 -0400:2017-06-12 
01:15:03.552214190 -0400:/var/crash/_usr_bin_webbrowser-app.1000.crash
 644:1000:122:0:2017-06-12 01:15:03.452246962 -0400:2017-06-12 
01:15:03.452246962 -0400:/var/crash/_usr_bin_webbrowser-app.1000.upload
Date: Sun Jun 18 00:30:39 2017
ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
InstallationDate: Installed on 2016-11-08 (222 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: apport
Title: package apport 2.20.4-0ubuntu4 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: apport (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 zesty

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

Title:
  package apport 2.20.4-0ubuntu4 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

Status in apport package in Ubuntu:
  New

Bug description:
  When I start the computer, an error message appears (I do not speak
  English, I do not know what it says), it asks me for my password to
  install a pluggin, but then tells me that the fault can not be solved.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic i686
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CrashReports:
   600:114:122:0:2017-06-12 01:15:08.678625626 -0400:2017-06-12 
01:15:08.678625626 -0400:/var/crash/_usr_bin_webbrowser-app.1000.uploaded
   600:0:122:85429:2017-06-18 00:30:38.761001825 -0400:2017-06-18 
00:30:39.761001825 -0400:/var/crash/apport.0.crash
   640:1000:122:14174623:2017-06-12 01:15:02.452246904 -0400:2017-06-12 
01:15:03.552214190 -0400:/var/crash/_usr_bin_webbrowser-app.1000.crash
   644:1000:122:0:2017-06-12 01:15:03.452246962 -0400:2017-06-12 
01:15:03.452246962 -0400:/var/crash/_usr_bin_webbrowser-app.1000.upload
  Date: Sun Jun 18 00:30:39 2017
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2016-11-08 (222 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package apport 2.20.4-0ubuntu4 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/apport/+bug/1698610/+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 1698609] [NEW] Ubuntu running slow

[Jalo Moster]

Public bug reported:

1.) When I use the shortcut CTRL+ALT+T to open a terminal, it takes a while to 
load.
2.) When I try to open Google Chrome or Chromium, I get a very big delay 
followed by a black screen before the browser loads.
3.) When I hold my laptop close to my ear, I can hear some small buzzing sounds 
that I am a little concerned about.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
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
CurrentDesktop: Unity
Date: Sun Jun 18 00:31:09 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:075b]
InstallationDate: Installed on 2017-06-07 (11 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:670c Microdia 
 Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9360
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic.efi.signed 
root=UUID=30d3e102-c256-4697-b0f1-f0ae1abdb6a2 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.2
dmi.board.name: 05HM5Y
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9360
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.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
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

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu 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/1698609

Title:
  Ubuntu running slow

Status in xorg package in Ubuntu:
  New

Bug description:
  1.) When I use the shortcut CTRL+ALT+T to open a terminal, it takes a while 
to load.
  2.) When I try to open Google Chrome or Chromium, I get a very big delay 
followed by a black screen before the browser loads.
  3.) When I hold my laptop close to my ear, I can hear some small buzzing 
sounds that I am a little concerned about.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  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
  CurrentDesktop: Unity
  Date: Sun Jun 18 00:31:09 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:075b]
  InstallationDate: Installed on 2017-06-07 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic.efi.signed 
root=UUID=30d3e102-c256-4697-b0f1-f0ae1abdb6a2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 

[Touch-packages] [Bug 1683592] Re: tzdata doesn't set a reasonable default via debconf

[Launchpad Bug Tracker]

[Expired for tzdata (Ubuntu) because there has been no activity for 60
days.]

** Changed in: tzdata (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  tzdata doesn't set a reasonable default via debconf

Status in tzdata package in Ubuntu:
  Expired

Bug description:
  In cases where we don't prompt the user for a timezone value, the
  tzdata package should have a default value - Etc/UTC, which
  debootstrap currently populates for us but should really be handled in
  the package.

  This matters more now that we are demoting tzdata from the minimal set
  and users might have occasion to non-interactively install it on an
  existing system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1683592/+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 1698604] [NEW] login will show unmasked password if user types too fast on a slow system

[Alexandre-Xavier Labonté-Lamoureux]

Public bug reported:

At the login, from the terminal, the user must login using his username
and password.

The program first displays " login:", then the user enters his
username. Once the user has pressed "enter", he must enter his password.
The user may type too quickly before "Password:" appears and thus what
he types before "Password:" was displayed will appear on the screen.

This occurs when the computer is slow when verifying the login username.
Users that are used to fast computer will start typing right their
password right after pressing "enter" and the characters will appear on
the screen.

The result would be something like this:

Ubuntu 16.04.2 LTS computername tty2

computername login: myusername

mypPassword:



People who may look at my screen will see that my password starts with
"myp". The other characters typed after that "Password:" was displayed
are invisible.

The solution would be to make every characters that are typed after the
user has entered his password invisible. It could also be a good idea to
give the user a sound cue (a PC speaker beep) when he enters a character
in the case where he starts typing his password too fast.

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

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

Title:
  login will show unmasked password if user types too fast on a slow
  system

Status in shadow package in Ubuntu:
  New

Bug description:
  At the login, from the terminal, the user must login using his
  username and password.

  The program first displays " login:", then the user enters his
  username. Once the user has pressed "enter", he must enter his
  password. The user may type too quickly before "Password:" appears and
  thus what he types before "Password:" was displayed will appear on the
  screen.

  This occurs when the computer is slow when verifying the login
  username. Users that are used to fast computer will start typing right
  their password right after pressing "enter" and the characters will
  appear on the screen.

  The result would be something like this:
  
  Ubuntu 16.04.2 LTS computername tty2

  computername login: myusername

  mypPassword:

  

  People who may look at my screen will see that my password starts with
  "myp". The other characters typed after that "Password:" was displayed
  are invisible.

  The solution would be to make every characters that are typed after
  the user has entered his password invisible. It could also be a good
  idea to give the user a sound cue (a PC speaker beep) when he enters a
  character in the case where he starts typing his password too fast.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1698604/+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 1691486] Re: Mouse cursor jumps to top left corner on click+drag

[David R. Hedges]

I admit I don't fully understand how the "Coordinate Transformation
Matrix" works (well, especially in the context of a mouse instead of a
trackpad or something), but it appears that's the trigger for this
issue.

After I eliminated that modified Coordinate Transformation Matrix, the
dragging/jump issue disappeared.

(For anyone else who happens to have the same problem, I was able to solve the 
mouse hyper-sensitivity issue like this instead:
  xinput set-prop "Razer Razer DeathAdder" "libinput Accel Speed" "-0.3"
  xinput set-prop "Razer Razer DeathAdder" "libinput Accel Profile Enabled" 0, 1

Thanks to https://patrickmn.com/aside/lowering-gaming-mouse-sensitivity-
in-ubuntu-9-10/ (updated) and http://mouseaccuracy.com/ for helping me
decide on a comfortable value.)

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

Title:
  Mouse cursor jumps to top left corner on click+drag

Status in xorg package in Ubuntu:
  New

Bug description:
  Since the upgrade to 17.10, when I click and drag something (e.g.
  moving a file within a folder, or moving an email message within
  Thunderbird), the mouse pointer (and the dragged item) jumps to the
  top left corner of the screen. From there, movement is normal and no
  more jumping is observed (until the next click-drag).

  The issue does *not* manifest when using the paintbrush tool in GIMP
  or just selecting text (e.g. in Chromium), but if I then click and
  drag the selected text, the mouse cursor does jump.

  Here's an xinput --test log from an instance of clicking a file inside
  a folder and dragging it (moved the mouse slowly / just a few
  millimeters):

  motion a[0]=1326 a[1]=451 
  motion a[0]=1326 a[1]=451 
  motion a[0]=1327 a[1]=450 
  motion a[0]=1327 a[1]=449 
  motion a[1]=449 
  motion a[1]=449 
  motion a[1]=448 
  motion a[0]=1327 a[1]=448 
  motion a[1]=448 
  motion a[1]=447 
  motion a[0]=1327 a[1]=447 
  motion a[1]=447 
  motion a[0]=1328 a[1]=447 
  motion a[1]=446 
  motion a[0]=1328 
  motion a[1]=446 
  button press   1 
  motion a[0]=1328 
  motion a[0]=1328 
  motion a[0]=1328 
  motion a[0]=1328 a[1]=446 
  motion a[0]=1327 
  motion a[0]=1327 
  motion a[0]=1327 
  motion a[1]=446 
  motion a[0]=1327 
  motion a[0]=1327 
  motion a[0]=1326 
  motion a[0]=1326 
  motion a[1]=446 
  motion a[0]=1326 
  motion a[0]=1326 a[1]=445 
  motion a[0]=1326 
  motion a[0]=1325 
  motion a[0]=1325 
  motion a[1]=445 
  motion a[0]=1325 
  motion a[0]=1325 
  motion a[0]=1325 
  motion a[0]=1324 
  motion a[0]=1324 
  motion a[1]=445 
  motion a[0]=1324 
  motion a[0]=1324 
  motion a[0]=1324 
  motion a[1]=445 
  motion a[0]=1323 
  motion a[0]=1323 
  motion a[0]=1323 
  motion a[0]=1323 
  motion a[1]=445 
  motion a[0]=1322 
  motion a[0]=1322 
  motion a[0]=1322 
  motion a[0]=1322 
  motion a[0]=1322 
  motion a[0]=1321 
  motion a[1]=444 
  motion a[0]=1321 
  motion a[0]=1321 
  motion a[0]=1321 
  motion a[0]=1321 
  motion a[0]=1320 
  motion a[0]=1320 
  motion a[0]=1320 
  motion a[1]=444 
  motion a[0]=1320 
  motion a[0]=1320 
  motion a[0]=1319 
  motion a[1]=444 
  motion a[0]=1319 
  motion a[0]=1319 
  motion a[1]=444 
  motion a[0]=1319 
  motion a[0]=1319 
  motion a[1]=444 
  motion a[0]=1318 
  motion a[0]=1318 
  motion a[0]=1318 
  motion a[0]=1318 
  motion a[0]=1318 
  motion a[1]=443 
  motion a[0]=1317 
  motion a[0]=1317 
  motion a[0]=1317 a[1]=443 
  motion a[0]=1317 
  motion a[0]=1317 
  motion a[0]=1316 
  motion a[1]=443 
  motion a[0]=1316 
  motion a[0]=1316 
  motion a[0]=1316 
  motion a[1]=443 
  motion a[0]=1316 
  motion a[0]=1315 
  motion a[1]=443 
  motion a[0]=1315 
  motion a[0]=1315 
  motion a[0]=1315 a[1]=442 
  motion a[0]=1315 
  motion a[0]=1314 
  motion a[1]=442 
  motion a[0]=1314 
  motion a[0]=1314 
  motion a[0]=1314 a[1]=442 
  motion a[0]=261 
  motion a[0]=261 
  motion a[1]=87 
  motion a[0]=261 
  motion a[0]=261 
  motion a[0]=261 
  motion a[0]=260 
  motion a[0]=260 a[1]=87 
  motion a[1]=16 
  motion a[0]=51 
  motion a[0]=50 
  motion a[0]=50 
  motion a[0]=50 a[1]=16 
  motion a[0]=50 
  motion a[1]=16 
  motion a[0]=50 
  motion a[0]=49 
  motion a[0]=49 
  motion a[0]=49 
  motion a[1]=15 
  motion a[0]=49 
  motion a[0]=48 
  motion a[0]=48 
  motion a[0]=48 a[1]=15 
  motion a[1]=15 
  motion a[0]=48 
  motion a[0]=48 
  motion a[0]=47 
  motion a[1]=15 
  motion a[0]=47 
  motion a[0]=47 
  motion a[0]=47 
  motion a[1]=14 
  motion a[0]=47 
  motion a[0]=46 
  motion a[0]=46 
  motion a[1]=14 
  motion a[0]=46 
  button release 1

  
  Here are my xinput settings for the device (which I *do* customize with a 
script run at login to avert hypersensitivity):
  $ xinput --list-props "Razer Razer DeathAdder"
  Device 'Razer Razer DeathAdder':
Device Enabled (136):   1
Coordinate Transformation Matrix (138): 0.20, 0.00, 

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

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1632415, so 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.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1632415
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  upgrading from 16.04 to 17.04  failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  Date: Sat Jun 17 18:19:27 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-09-13 (277 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2017-06-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1698600/+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 1698600] [NEW] package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[cl...@cox.net]

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

Public bug reported:

upgrading from 16.04 to 17.04  failed to install

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: gconf2 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.3
Architecture: amd64
Date: Sat Jun 17 18:19:27 2017
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2016-09-13 (277 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1.1
 apt  1.3.5
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to yakkety on 2017-06-18 (0 days ago)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  upgrading from 16.04 to 17.04  failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  Date: Sat Jun 17 18:19:27 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-09-13 (277 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2017-06-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1698600/+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 1691556] Re: Can't send audio to Amazon Echo via Bluetooth

[Launchpad Bug Tracker]

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

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

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

Title:
  Can't send audio to Amazon Echo via Bluetooth

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Pairing and coupling to Amazon Echo works, but no sound is heard.

  I believe the issue is related to the fact that Amazon Echo is paired
  as a handset (i.e., speaker + microphone) rather than just as a
  speaker.  I believe the critical error is found in a dmesg line such
  as:

  Feb 28 10:59:05 n1 bluetoothd[1025]: a2dp-source profile connect
  failed for 50:F5:DA:A6:3F:EA: Device or resource busy

  as I describe in the askubuntu.com discussion at:

  https://askubuntu.com/questions/871630/cant-send-audio-to-amazon-echo-
  via-bluetooth

  I have clarified there my thinking and the steps I've taken thus far
  on this issue, which includes trying debug bluetooth per the Ubuntu
  wiki page which describes how to do so.

  This is probably an upstream issue, as Mike H-R has commented there
  that the problem also occurs on ArchLinux.

  I and a few others would like to get this resolved, and I am happy to
  help (I'm a software developer).  However, at this point, I'm not sure
  how to proceed without some assistance.  I suppose I could report it
  to Debain, but I've only ever used Debain vis a vis Ubuntu, so I
  thought it best to start here.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 17 22:27:59 2017
  InstallationDate: Installed on 2015-12-26 (507 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2017-02-28 (78 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: DC:53:60:97:55:17  ACL MTU: 1021:5  SCO MTU: 96:6
    UP RUNNING PSCAN
    RX bytes:13547334 acl:58 sco:0 events:1935087 errors:0
    TX bytes:1652407651 acl:1934967 sco:0 commands:76 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1691556/+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 1691556] Re: Can't send audio to Amazon Echo via Bluetooth

[goog64]

I have the same problem. Dell XPS13 laptop Linux Mint 18. Finally
managed to pair with Amazon Echo, but cannot get sound to it.

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

Title:
  Can't send audio to Amazon Echo via Bluetooth

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Pairing and coupling to Amazon Echo works, but no sound is heard.

  I believe the issue is related to the fact that Amazon Echo is paired
  as a handset (i.e., speaker + microphone) rather than just as a
  speaker.  I believe the critical error is found in a dmesg line such
  as:

  Feb 28 10:59:05 n1 bluetoothd[1025]: a2dp-source profile connect
  failed for 50:F5:DA:A6:3F:EA: Device or resource busy

  as I describe in the askubuntu.com discussion at:

  https://askubuntu.com/questions/871630/cant-send-audio-to-amazon-echo-
  via-bluetooth

  I have clarified there my thinking and the steps I've taken thus far
  on this issue, which includes trying debug bluetooth per the Ubuntu
  wiki page which describes how to do so.

  This is probably an upstream issue, as Mike H-R has commented there
  that the problem also occurs on ArchLinux.

  I and a few others would like to get this resolved, and I am happy to
  help (I'm a software developer).  However, at this point, I'm not sure
  how to proceed without some assistance.  I suppose I could report it
  to Debain, but I've only ever used Debain vis a vis Ubuntu, so I
  thought it best to start here.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 17 22:27:59 2017
  InstallationDate: Installed on 2015-12-26 (507 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2017-02-28 (78 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: DC:53:60:97:55:17  ACL MTU: 1021:5  SCO MTU: 96:6
    UP RUNNING PSCAN
    RX bytes:13547334 acl:58 sco:0 events:1935087 errors:0
    TX bytes:1652407651 acl:1934967 sco:0 commands:76 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1691556/+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 1695928] Re: Please remove obsolete UOA packages

[Jeremy Bicha]

** Description changed:

  Ubuntu Online Accounts is no longer maintained. There is an alternative,
  GNOME Online Accounts for the GNOME desktop.
  
  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.
  
  Please remove these source packages and their binaries:
  =
  
  Phase 1
  ---
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qtpurchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-china-photo-scope
  unity-scope-gdrive
+ 
+ By the way, gnome-control-center-signon fails to build with vala 0.36:
+ 
https://launchpadlibrarian.net/324396241/buildlog_ubuntu-artful-amd64.gnome-control-center-signon_0.1.9+16.10.20160825-0ubuntu1~ubuntu17.10.1_BUILDING.txt.gz
  
  Phase 2
  ---
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud
  address-book-app
  address-book-service
  dialer-app
  messaging-app
  telephony-service
  tone-generator
  ubuntu-system-settings
  buteo-sync-plugins-contacts-google
  camera-app
  indicator-transfer
  indicator-transfer-buteo
  libertine
  ubuntu-experience-tests
  unity-scopes-shell
  unity8
  
  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802
  
  Kubuntu still uses signon-ui.
  
  See also https://code.launchpad.net/~xnox/ubuntu-
  seeds/unity8-removals/+merge/323615

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

Title:
  Please remove obsolete UOA packages

Status in gnome-control-center-signon package in Ubuntu:
  New

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  =

  Phase 1
  ---
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qtpurchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-china-photo-scope
  unity-scope-gdrive

  By the way, gnome-control-center-signon fails to build with vala 0.36:
  
https://launchpadlibrarian.net/324396241/buildlog_ubuntu-artful-amd64.gnome-control-center-signon_0.1.9+16.10.20160825-0ubuntu1~ubuntu17.10.1_BUILDING.txt.gz

  Phase 2
  ---
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud
  address-book-app
  address-book-service
  dialer-app
  messaging-app
  telephony-service
  tone-generator
  ubuntu-system-settings
  buteo-sync-plugins-contacts-google
  camera-app
  indicator-transfer
  indicator-transfer-buteo
  libertine
  ubuntu-experience-tests
  unity-scopes-shell
  unity8

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses signon-ui.

  See also https://code.launchpad.net/~xnox/ubuntu-
  seeds/unity8-removals/+merge/323615

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+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 1698594] [NEW] Kubuntu Installer for 17.04 crashes reproducable with a too small /boot partition due to "No space left on device"

[andy]

Public bug reported:

Hello,

i have experienced reproducable crashes of the installer. The problem
seems to be that my boot partition is to small. I have a /boot partition
of about 100 MB

The problem seems to be that the initrd file in the boot partition is
very big and cannot be properly updated.

Is there a restriction to the size of a /boot partition? 100 MB seems to
be way to little, even though the initial installation is possible. But
at the end of the installation process the installer crashes.

= start  -> see full log at the end of the report
update-initramfs: Generating /boot/initrd.img-4.10.0-22-generic

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
= end 


I used my existing paritions and i would at least expect a warning (hint) that 
the /boot partition needs to be of a certain size (or just prevents 
installation with a too small boot partition).

I am also having problems updating the kernel, which seems to be the
same cause of the crash of the installer:


here is some information:

wuesand@wuesand-ESPRIMO-P1510:~/projects/kde/ansible$ sudo fdisk -l
Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x241c6624

Device Boot Start   End   Sectors   Size Id Type
/dev/sda1  * 2048 390625279 390623232 186,3G  7 HPFS/NTFS/exFAT
/dev/sda2   390625280 39081983919456095M 83 Linux
/dev/sda3   390819840 586131455 195311616  93,1G 83 Linux
/dev/sda4   586133502 976771071 390637570 186,3G  5 Extended
/dev/sda5   586133504 586717183583680   285M 82 Linux swap / Solaris
/dev/sda6   586719232 976771071 390051840   186G 83 Linux


wuesand@wuesand-ESPRIMO-P1510:~/projects/kde/ansible$ sudo mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=4042808k,nr_inodes=1010702,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=813128k,mode=755)
/dev/sda3 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=34,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=3715)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sda2 on /boot type ext2 (rw,relatime,block_validity,barrier,user_xattr,acl)
/dev/sda6 on /home type ext4 (rw,relatime,data=ordered)
tmpfs on /run/user/119 type tmpfs 
(rw,nosuid,nodev,relatime,size=813124k,mode=700,uid=119,gid=127)
tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=813124k,mode=700,uid=1000,gid=1000)
/dev/sda1 on /mnt/ntfs type fuseblk 
(rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)


wuesand@wuesand-ESPRIMO-P1510:~/projects/kde/ansible$ sudo apt-get upgrade -u
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
5 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up initramfs-tools (0.125ubuntu9) ...

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[513G3]

I agree with comments #25 and #26.  It's likely a red herring, but this
issue arose for me right after I installed the flatpak PPA and a pile of
mono/M$ stuff.  I still figure that those actions are orthogonal, but
just in case everyone else recently installed similar stuff or a new PPA
or...

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1698593] [NEW] [Blade, Realtek ALC298, Black Mic, Left] No sound at all

[Kenzie Togami]

Public bug reported:

I'm trying to get the mic from the combo jack on my Razer Blade working.
Headphones are functioning perfectly, but the mic seems to be picking up
on random data, unrelated to sound output or my surroundings. I know the
jack is working as I dual-boot Windows, and it works great there.

I've added the `options snd-hda-intel model=laptop-dmic` line as
recommended in some other threads, and tried setting pin 0x18 to mic
using hdajackretask, but it hasn't fixed it or made any difference.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   octy   1971 F...m pulseaudio
 /dev/snd/pcmC0D0p:   octy   1971 F...m pulseaudio
 /dev/snd/controlC0:  octy   1971 F pulseaudio
CurrentDesktop: X-Cinnamon
Date: Sat Jun 17 15:21:41 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-04-06 (72 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   octy   1971 F...m pulseaudio
 /dev/snd/pcmC0D0p:   octy   1971 F...m pulseaudio
 /dev/snd/controlC0:  octy   1971 F pulseaudio
Symptom_Jack: Black Mic, Left
Symptom_Type: No sound at all
Title: [Blade, Realtek ALC298, Black Mic, Left] No sound at all
UpgradeStatus: Upgraded to zesty on 2017-04-15 (63 days ago)
dmi.bios.date: 01/10/2017
dmi.bios.vendor: Razer
dmi.bios.version: 1.00
dmi.board.name: Razer
dmi.board.vendor: Razer
dmi.chassis.type: 9
dmi.chassis.vendor: Razer
dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
dmi.product.name: Blade
dmi.product.version: 6.06
dmi.sys.vendor: Razer
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-06-17T15:06:35.753276

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

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

Title:
  [Blade, Realtek ALC298, Black Mic, Left] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I'm trying to get the mic from the combo jack on my Razer Blade
  working. Headphones are functioning perfectly, but the mic seems to be
  picking up on random data, unrelated to sound output or my
  surroundings. I know the jack is working as I dual-boot Windows, and
  it works great there.

  I've added the `options snd-hda-intel model=laptop-dmic` line as
  recommended in some other threads, and tried setting pin 0x18 to mic
  using hdajackretask, but it hasn't fixed it or made any difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   octy   1971 F...m pulseaudio
   /dev/snd/pcmC0D0p:   octy   1971 F...m pulseaudio
   /dev/snd/controlC0:  octy   1971 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Sat Jun 17 15:21:41 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-06 (72 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   octy   1971 F...m pulseaudio
   /dev/snd/pcmC0D0p:   octy   1971 F...m pulseaudio
   /dev/snd/controlC0:  octy   1971 F pulseaudio
  Symptom_Jack: Black Mic, Left
  Symptom_Type: No sound at all
  Title: [Blade, Realtek ALC298, Black Mic, Left] No sound at all
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (63 days ago)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-06-17T15:06:35.753276

To manage notifications about this bug go to:

[Touch-packages] [Bug 1694989] Re: apt-mark overwrites existing held package info

[Julian Andres Klode]

** Bug watch added: Debian Bug tracker #864950
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864950

** Also affects: apt (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864950
   Importance: Unknown
   Status: Unknown

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

Title:
  apt-mark overwrites existing held package info

Status in apt package in Ubuntu:
  Triaged
Status in apt package in Debian:
  Unknown

Bug description:
  Running apt-mark hold commands overwrites / nullifies any existing
  held package data. Not sure if this is by design, but I assume it's
  meant to be cumulative.

  Ubuntu version: 16.04.2 LTS
  Package version: apt 1.2.19 amd64

  Expected behaviour:

  apt-mark hold 3dchess
  apt-mark hold 0ad
  apt-mark showhold

  3dchess
  0ad

  Actual behaviour:

  apt-mark hold 3dchess
  apt-mark hold 0ad
  apt-mark showhold

  0ad

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1694989/+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 1639372] Re: CVE-2016-9082: DOS attack in converting SVG to PNG

[Bug Watch Updater]

** Changed in: cairo
   Status: Unknown => Confirmed

** Changed in: cairo
   Importance: Unknown => Critical

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

Title:
  CVE-2016-9082: DOS attack in converting SVG to PNG

Status in cairo:
  Confirmed
Status in cairo package in Ubuntu:
  Fix Released
Status in cairo source package in Precise:
  Confirmed
Status in cairo source package in Trusty:
  Confirmed
Status in cairo source package in Xenial:
  Confirmed
Status in cairo source package in Yakkety:
  Confirmed
Status in cairo package in Debian:
  Fix Released

Bug description:
  I'm attaching debdiffs for trusty, xenial and yakkety. Zesty is
  already fixed by syncing cairo 1.14.6-1.1 from Debian. Maybe someone
  else can work on the precise update.

  Proof of Concept at
  http://seclists.org/oss-sec/2016/q4/44

  I didn't get gdb to work, but when I tried to convert the file, I got
  a crash report named /var/crash/_usr_bin_rsvg-convert.1000.crash .
  After the update, no crash happened.

  I reproduced the crash and verified that the new package doesn't crash
  on yakkety. In xenial I wasn't able to reproduce the crash. I did not
  test on trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1639372/+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 1698577] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1688721, so 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.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  Installing updates failed with message. New to Linux and Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jun 17 15:20:57 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-14 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1698577/+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 1698577] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Sal Sack]

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

Public bug reported:

Installing updates failed with message. New to Linux and Ubuntu

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
AptOrdering:
 gconf2-common:amd64: Install
 libgconf-2-4:amd64: Install
 gconf-service-backend:amd64: Install
 gconf-service:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Jun 17 15:20:57 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-14 (3 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  Installing updates failed with message. New to Linux and Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jun 17 15:20:57 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-14 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1698577/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Jose Luis]

had somebody tryed sound with kernel 4.12?

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1698570] Re: package keyboard-configuration 1.70ubuntu8 failed to install/upgrade: subprocess new pre-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 console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1698570

Title:
  package keyboard-configuration 1.70ubuntu8 failed to install/upgrade:
  subprocess new pre-installation script returned error exit status 1

Status in console-setup package in Ubuntu:
  New

Bug description:
  no idea what this is about.  I got it while upgrading to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: keyboard-configuration 1.70ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic i686
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  Date: Sat Jun 17 14:58:07 2017
  DuplicateSignature: package:keyboard-configuration:1.70ubuntu8:subprocess new 
pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2016-08-17 (304 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.0.1ubuntu2.17
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.70ubuntu8 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2017-06-17 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1698570/+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 1698570] [NEW] package keyboard-configuration 1.70ubuntu8 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[Stan Nickel]

Public bug reported:

no idea what this is about.  I got it while upgrading to 16.10

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: keyboard-configuration 1.70ubuntu8
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic i686
ApportVersion: 2.14.1-0ubuntu3.24
Architecture: i386
Date: Sat Jun 17 14:58:07 2017
DuplicateSignature: package:keyboard-configuration:1.70ubuntu8:subprocess new 
pre-installation script returned error exit status 1
ErrorMessage: subprocess new pre-installation script returned error exit status 
1
InstallationDate: Installed on 2016-08-17 (304 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1.1
 apt  1.0.1ubuntu2.17
SourcePackage: console-setup
Title: package keyboard-configuration 1.70ubuntu8 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
UpgradeStatus: Upgraded to yakkety on 2017-06-17 (0 days ago)

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


** Tags: apport-package i386 third-party-packages yakkety

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

Title:
  package keyboard-configuration 1.70ubuntu8 failed to install/upgrade:
  subprocess new pre-installation script returned error exit status 1

Status in console-setup package in Ubuntu:
  New

Bug description:
  no idea what this is about.  I got it while upgrading to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: keyboard-configuration 1.70ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic i686
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  Date: Sat Jun 17 14:58:07 2017
  DuplicateSignature: package:keyboard-configuration:1.70ubuntu8:subprocess new 
pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2016-08-17 (304 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.0.1ubuntu2.17
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.70ubuntu8 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2017-06-17 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1698570/+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 1623666] Re: iOS device contents not displayed in Ubuntu

[Fawad Raza]

#27 on Unbuntu 16.04 doesn't work anymore, gives same "package not met"
error:

configure: error: Package requirements (libusbmuxd >= 1.0.9) were not met:
No package 'libusbmuxd' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you installed 
software in a non-standard prefix.
Alternatively, you may set the environment variables libusbmuxd_CFLAGS and 
libusbmuxd_LIBS to avoid the need to call pkg-config.

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

Title:
  iOS device contents not displayed in Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice*:

  Vauge discussion that mentions using the latest git HEAD*:
  https://github.com/libimobiledevice/libimobiledevice/issues/327

  *This discussion is quite vague. One comment points out "iOS 10
  devices don't allow SSLv3 anymore but require at least TLSv1", but not
  how or if that has been fixed in libimobiledevice git HEAD.

  This ppa packages the git version and may resolve the issue:
  
https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages

  There are several other upstream reports related to this problem.

  Partial success patch (idevicepair only) trying to keep GnuTLS:
  https://github.com/libimobiledevice/libimobiledevice/issues/413

  Failure with GnuTLS, Success with OpenSSL:
  https://gitlab.com/gnutls/gnutls/issues/145

  Ubuntu packages libimobiledevice with "--disable-openssl":
  https://github.com/libimobiledevice/ifuse/issues/32

  Duplicate bug 1638177 suggests to repackage libimobiledevice using
  OpenSSL to avoid this problem, as per comment 27 below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+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 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting

[FFab]

https://bugs.freedesktop.org/show_bug.cgi?id=101483

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  [HP Pavilion Notebook - 17-g164ng] black screen when booting

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When booting the screen is black – backlight on – off - on.
  When HDD is inactive
  - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or 
Strg + Alt + Del
  - remote access e.g. using ssh is possible

  Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10.

  My notebook is a HP Pavilion  17-g164ng with an AMD A10-8780P APU and
  2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz.

  It seems very similar to that described in #1597079.

  The bug report was generated from a remote PC. My HP notebook was started 
without any workaround parameters.
  This apport doesn't display the second graphic subsystem Topaz R7 as an 
apport generated with nomodeset xforcevesa.

  WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver.

  WORKAROUND: When booting in UEFI mode, use kernel parameters:
  nomodeset

  or:
  nomodeset xforcevesa

  Resolution without xforcevesa: 800x600
  Resolution with xforcevesa: 1600x900 – the optimal resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  5 23:40:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Carrizo [103c:80b6]
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B6
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Nov  5 23:32:11 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.1
  xserver.video_driver: amdgpu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639517/+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 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting

[FFab]

to comment #18
filed upstream 

** Bug watch added: freedesktop.org Bugzilla #101483
   https://bugs.freedesktop.org/show_bug.cgi?id=101483

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

Title:
  [HP Pavilion Notebook - 17-g164ng] black screen when booting

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When booting the screen is black – backlight on – off - on.
  When HDD is inactive
  - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or 
Strg + Alt + Del
  - remote access e.g. using ssh is possible

  Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10.

  My notebook is a HP Pavilion  17-g164ng with an AMD A10-8780P APU and
  2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz.

  It seems very similar to that described in #1597079.

  The bug report was generated from a remote PC. My HP notebook was started 
without any workaround parameters.
  This apport doesn't display the second graphic subsystem Topaz R7 as an 
apport generated with nomodeset xforcevesa.

  WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver.

  WORKAROUND: When booting in UEFI mode, use kernel parameters:
  nomodeset

  or:
  nomodeset xforcevesa

  Resolution without xforcevesa: 800x600
  Resolution with xforcevesa: 1600x900 – the optimal resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  5 23:40:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Carrizo [103c:80b6]
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B6
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Nov  5 23:32:11 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.1
  xserver.video_driver: amdgpu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639517/+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 1698520] Re: I can not open raf archives of fujifilm X-T2 in UfRaw/Gimp

[Colin Watson]

** Package changed: debconf (Ubuntu) => ufraw (Ubuntu)

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

Title:
  I can not open raf archives of fujifilm X-T2 in UfRaw/Gimp

Status in ufraw package in Ubuntu:
  New

Bug description:
  Hi:I can not open raf archives of fujifilm X-T2 in UfRaw/Gimp. Any
  solution with this cain of files? Many thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufraw/+bug/1698520/+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 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[xtonic]

Have the same issue on 17.04
In order to make dns resolution work again one should type after resume:
sudo systemctl restart systemd-resolved.service

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1698541] [NEW] [MacBookAir4, 2, Cirrus Logic CS4206, Green Headphone Out, UNKNOWN] Underruns, dropouts or crackling sound

[Andrii]

Public bug reported:

I use next version of ubuntu x86_64
Description:Ubuntu 16.04.2 LTS
Release:16.04

kernel 4.2.8-040208-lowlatency

alsa-base  1.0.25+dfsg-0ubuntu5 
alsa-utils  1.1.0-0ubuntu5  
gstreamer1.0-alsa:amd64  1.8.3-1ubuntu0.2

Sound from speakers works fine (tested on wav and mp3 files). Problem
appears when I plug headphones, I hear audio crackling and noises during
sound play. But when I tried listen to music from flash player (like
youtube , online radio ...) sound works good without any problems in
headphones.

I tried to add different options in /etc/modprobe.d/alsa-base.conf and
changing configuration /etc/pulse/default.pa, but it didn't help.

Also I loaded ubuntu with kernels 4.8.0-54-generic, 4.8.0-53-generic but
it isn't solve the problem.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.2.8-040208-lowlatency x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ash1911 F pulseaudio
CurrentDesktop: Unity
Date: Sat Jun 17 15:21:52 2017
InstallationDate: Installed on 2017-06-05 (12 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Встроенное аудио - HDA Intel PCH
Symptom_Jack: Green Headphone Out, UNKNOWN
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [MacBookAir4,2, Cirrus Logic CS4206, Green Headphone Out, UNKNOWN] 
Underruns, dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA41.88Z.0077.B14.1510261805
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-742912EFDBEE19B3
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir4,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-742912EFDBEE19B3
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B14.1510261805:bd10/26/2015:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3:
dmi.product.name: MacBookAir4,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-06-17T15:11:50.985356

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  [MacBookAir4,2, Cirrus Logic CS4206, Green Headphone Out, UNKNOWN]
  Underruns, dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I use next version of ubuntu x86_64
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  kernel 4.2.8-040208-lowlatency

  alsa-base  1.0.25+dfsg-0ubuntu5 
  alsa-utils  1.1.0-0ubuntu5  
  gstreamer1.0-alsa:amd64  1.8.3-1ubuntu0.2

  Sound from speakers works fine (tested on wav and mp3 files). Problem
  appears when I plug headphones, I hear audio crackling and noises
  during sound play. But when I tried listen to music from flash player
  (like youtube , online radio ...) sound works good without any
  problems in headphones.

  I tried to add different options in /etc/modprobe.d/alsa-base.conf and
  changing configuration /etc/pulse/default.pa, but it didn't help.

  Also I loaded ubuntu with kernels 4.8.0-54-generic, 4.8.0-53-generic
  but it isn't solve the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.2.8-040208-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ash1911 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Jun 17 15:21:52 2017
  InstallationDate: Installed on 2017-06-05 (12 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Встроенное аудио - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, UNKNOWN
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [MacBookAir4,2, Cirrus Logic CS4206, Green Headphone Out, UNKNOWN] 
Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA41.88Z.0077.B14.1510261805
  

[Touch-packages] [Bug 1692870] Re: gzip compression broken in UniFi (built-in tomcat)

[Jean-Louis Dupond]

I tried to simulate the issue with Tomcat 7.0.77 (which is the version
UniFi uses), but I was unable to simulate this on Ubuntu 17.04.

The 'use-dso' patch that I removed in the debdiff, just point to an
empty file. So no use that file is in the deb.

Thanks

** Description changed:

- [Impact] 
+ [Impact]
  Since I upgraded from Ubuntu 16.10 to 17.04, my Guest portal for my UniFi 
system was broken (https://www.ubnt.com/download/unifi/).
  
  Curl gave me the following response:
  # curl - --compress localhost:8880/guest/s/default/
  *   Trying ::1...
  * TCP_NODELAY set
  * Connected to localhost (::1) port 8880 (#0)
  > GET /guest/s/default/ HTTP/1.1
  > Host: localhost:8880
  > User-Agent: curl/7.52.1
  > Accept: */*
  > Accept-Encoding: deflate, gzip
  >
  < HTTP/1.1 200 OK
  < Server: Apache-Coyote/1.1
  < Content-Type: text/html;charset=utf-8
  < Transfer-Encoding: chunked
  < Content-Encoding: gzip
  < Vary: Accept-Encoding
  < Date: Tue, 23 May 2017 11:19:22 GMT
  <
  * Error while processing content unencoding: invalid code lengths set
  * Failed writing data
  * Curl_http_done: called premature == 1
  * Closing connection 0
  curl: (23) Error while processing content unencoding: invalid code lengths set
  
  [Test Case]
- Just install a fresh Ubuntu 17.04 with UniFi controller. And the Guest Portal 
is broken. See above.
+ - Install UniFi controller on Ubuntu 17.04 
(http://dl.ubnt.com/unifi/5.4.16/unifi_sysvinit_all.deb)
+ - Go to https://:8443/manage/site/default/settings/guestcontrol
+ - Or do: curl - --compress :8880/guest/s/default/
+ 
+ When compression is enabled, its broken.
  When disabling compression in curl, it works fine.
  
  After some debugging, I found out that downgrading to zlib 1:1.2.8.dfsg-
  2ubuntu5.1 was a workaround.
  
  Now after digging into the issue some more, I found the following upstream 
patch (unreleased version), fixes the issue:
  https://github.com/madler/zlib/commit/f9694097dd69354b03cb8af959094c7f260db0a1
  
  [Regression Potential]
  Everybody upgrading from 16.10 (or previous) to 17.04 will be affected by 
this.
  
  The patch is taken from upstream, so this isn't a change we will need to
  keep different from upstream.
  
  I've already created a new package (see debdiff) that fixes the issue.
  
  [Other Info]
  Now as the UniFi controller is just some Tomcat, which relies on Java 
(OpenJDK), which uses zlib for its built-in Compression/Decompression. I guess 
even more java related tools can be broken. But I didn't have time to test this.
  
  At least some other people using UniFi have the same issue, see:
  
https://community.ubnt.com/t5/UniFi-Wireless/ERR-CONTENT-DECODING-FAILED-on-guest-portal-customisation/td-p/1903419

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

Title:
  gzip compression broken in UniFi (built-in tomcat)

Status in zlib package in Ubuntu:
  Confirmed
Status in zlib source package in Zesty:
  New

Bug description:
  [Impact]
  Since I upgraded from Ubuntu 16.10 to 17.04, my Guest portal for my UniFi 
system was broken (https://www.ubnt.com/download/unifi/).

  Curl gave me the following response:
  # curl - --compress localhost:8880/guest/s/default/
  *   Trying ::1...
  * TCP_NODELAY set
  * Connected to localhost (::1) port 8880 (#0)
  > GET /guest/s/default/ HTTP/1.1
  > Host: localhost:8880
  > User-Agent: curl/7.52.1
  > Accept: */*
  > Accept-Encoding: deflate, gzip
  >
  < HTTP/1.1 200 OK
  < Server: Apache-Coyote/1.1
  < Content-Type: text/html;charset=utf-8
  < Transfer-Encoding: chunked
  < Content-Encoding: gzip
  < Vary: Accept-Encoding
  < Date: Tue, 23 May 2017 11:19:22 GMT
  <
  * Error while processing content unencoding: invalid code lengths set
  * Failed writing data
  * Curl_http_done: called premature == 1
  * Closing connection 0
  curl: (23) Error while processing content unencoding: invalid code lengths set

  [Test Case]
  - Install UniFi controller on Ubuntu 17.04 
(http://dl.ubnt.com/unifi/5.4.16/unifi_sysvinit_all.deb)
  - Go to https://:8443/manage/site/default/settings/guestcontrol
  - Or do: curl - --compress :8880/guest/s/default/

  When compression is enabled, its broken.
  When disabling compression in curl, it works fine.

  After some debugging, I found out that downgrading to zlib 1:1.2.8
  .dfsg-2ubuntu5.1 was a workaround.

  Now after digging into the issue some more, I found the following upstream 
patch (unreleased version), fixes the issue:
  https://github.com/madler/zlib/commit/f9694097dd69354b03cb8af959094c7f260db0a1

  [Regression Potential]
  Everybody upgrading from 16.10 (or previous) to 17.04 will be affected by 
this.

  The patch is taken from upstream, so this isn't a change we will need
  to keep different from upstream.

  I've already created a new package (see debdiff) that fixes the issue.

  [Other Info]
  Now as the UniFi 

[Touch-packages] [Bug 1698534] [NEW] Network-manager crashing

[João Gabriel]

Public bug reported:

My Network Manager was working well, but in 15/jun/17, I lost
controlability over my hardware.

Now I can activate wifi through network-manager icon, but it doesn't
display any network.

I can see it is activated through command line:

nmcli -f in-use,ssid,bssid,signal,bars dev wifi

* SSID BSSID SINAL BARRAS
Virus_H@cker 18:D6:C7:76:D5:F8 90 ▂▄▆█
MARTIN 14:D6:4D:39:8D:85 80 ▂▄▆_
ROGERIO 2 24 GHZ E4:6F:13:3D:88:24 50 ▂▄__
MARTIN A0:8E:78:5D:76:30 47 ▂▄__
TP-LINK_2.4GHz_A60B15 A0:F3:C1:A6:0B:15 40 ▂▄__
maucoppi 18:D6:C7:76:C3:44 40 ▂▄__
HPEE75A0 02:21:11:5D:39:57 40 ▂▄__
NET-CLARO-WIFI 2A:32:C5:5F:94:C9 37 ▂▄__

I can even connect to a network through command line:

nmcli d wifi connect 14:D6:4D:39:8D:85

Dispositivo "wlp2s0" ativado com sucesso com "85fcc7fb-60bd-47af-
a9da-9381656ee2a3".

ping 192.168.1.1

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=4.48 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=4.11 ms

But through graphical interface I cannot operate it.

When I'm connected through WiFi, the network-manager icon has changed.

Before the bug, it presented the common wifi icon, showing signal
intensity of the connection.

Now it is presenting the icon of ethernet connection, when connect
through WiFi.


When I open Network Connections and exclude some network, it doesn't remove it 
from the list until I close the window and open it again.


I have made an update on 14/jun, in the night. During all day of 15/jun I used 
my network without any problem. In the end of the say the problem began.

The packages updated were:

Start-Date: 2017-06-14 20:36:07 Commandline: /usr/bin/unattended-upgrade
Upgrade: libgnutls-openssl27:amd64 (3.4.10-4ubuntu1.2,
3.4.10-4ubuntu1.3), flashplugin-installer:amd64
(25.0.0.171ubuntu0.16.04.1, 26.0.0.126ubuntu0.16.04.1), firefox-locale-
en:amd64 (53.0.3+build1-0ubuntu0.16.04.2, 54.0+build3-0ubuntu0.16.04.1),
firefox-locale-pt:amd64 (53.0.3+build1-0ubuntu0.16.04.2,
54.0+build3-0ubuntu0.16.04.1), libgnutls30:amd64 (3.4.10-4ubuntu1.2,
3.4.10-4ubuntu1.3), firefox:amd64 (53.0.3+build1-0ubuntu0.16.04.2,
54.0+build3-0ubuntu0.16.04.1) End-Date: 2017-06-14 20:41:18


I have tried loading my previous kernel version (linux-image-4.8.0-53-generic), 
but it doesn't change the wrong behavior.


Restarting network-manager, reestablish normal behavior. But after 
suspend-awake, sometimes the bug returns.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Network-manager crashing

Status in network-manager package in Ubuntu:
  New

Bug description:
  My Network Manager was working well, but in 15/jun/17, I lost
  controlability over my hardware.

  Now I can activate wifi through network-manager icon, but it doesn't
  display any network.

  I can see it is activated through command line:

  nmcli -f in-use,ssid,bssid,signal,bars dev wifi

  * SSID BSSID SINAL BARRAS
  Virus_H@cker 18:D6:C7:76:D5:F8 90 ▂▄▆█
  MARTIN 14:D6:4D:39:8D:85 80 ▂▄▆_
  ROGERIO 2 24 GHZ E4:6F:13:3D:88:24 50 ▂▄__
  MARTIN A0:8E:78:5D:76:30 47 ▂▄__
  TP-LINK_2.4GHz_A60B15 A0:F3:C1:A6:0B:15 40 ▂▄__
  maucoppi 18:D6:C7:76:C3:44 40 ▂▄__
  HPEE75A0 02:21:11:5D:39:57 40 ▂▄__
  NET-CLARO-WIFI 2A:32:C5:5F:94:C9 37 ▂▄__
  
  I can even connect to a network through command line:

  nmcli d wifi connect 14:D6:4D:39:8D:85

  Dispositivo "wlp2s0" ativado com sucesso com "85fcc7fb-60bd-47af-
  a9da-9381656ee2a3".

  ping 192.168.1.1

  PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
  64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=4.48 ms
  64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=4.11 ms

  But through graphical interface I cannot operate it.

  When I'm connected through WiFi, the network-manager icon has changed.

  Before the bug, it presented the common wifi icon, showing signal
  intensity of the connection.

  Now it is presenting the icon of ethernet connection, when connect
  through WiFi.

  
  When I open Network Connections and exclude some network, it doesn't remove 
it from the list until I close the window and open it again.

  
  I have made an update on 14/jun, in the night. During all day of 15/jun I 
used my network without any problem. In the end of the say the problem began.

  The packages updated were:

  Start-Date: 2017-06-14 20:36:07 Commandline: /usr/bin/unattended-
  upgrade Upgrade: libgnutls-openssl27:amd64 (3.4.10-4ubuntu1.2,
  3.4.10-4ubuntu1.3), flashplugin-installer:amd64
  (25.0.0.171ubuntu0.16.04.1, 26.0.0.126ubuntu0.16.04.1), firefox-
  locale-en:amd64 (53.0.3+build1-0ubuntu0.16.04.2,
  54.0+build3-0ubuntu0.16.04.1), 

[Touch-packages] [Bug 1698529] Re: package libpam-systemd:amd64 229-4ubuntu17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[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/1698529

Title:
  package libpam-systemd:amd64 229-4ubuntu17 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in systemd package in Ubuntu:
  New

Bug description:
  failed upgrade of the system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpam-systemd:amd64 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sat Jun 17 11:18:13 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2016-08-30 (290 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 229-4ubuntu17 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Ludmila Dck]

Public bug reported:

failed upgrade of the system

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpam-systemd:amd64 229-4ubuntu17
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Sat Jun 17 11:18:13 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2016-08-30 (290 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: systemd
Title: package libpam-systemd:amd64 229-4ubuntu17 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

** 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/1698529

Title:
  package libpam-systemd:amd64 229-4ubuntu17 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in systemd package in Ubuntu:
  New

Bug description:
  failed upgrade of the system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpam-systemd:amd64 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sat Jun 17 11:18:13 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2016-08-30 (290 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 229-4ubuntu17 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1698529/+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 1689825] Re: gnome-keyring not unlocked on boot

[Launchpad Bug Tracker]

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

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions

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

Re: [Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

[Zhanglei Mao]

hi Danneil,

Those are translate from Huawei's reply mail:

The sever board have only this VGA PCI devices:
   19e5 Huawei Technologies Co., Ltd.
   1711 Hi1710 [iBMC Intelligent Management system chip w/VGA support]

Please check if this math to our D05 testing environment.

thanks,
Mao

On Fri, Jun 16, 2017 at 4:21 PM, Zhanglei Mao 
wrote:

> hi Daniel,
>
> It is very nice for your to provide a patch for it. For other PCI IDs, I
> will check with Huawei team and back to you at next week.
>
> By the way, what is status of first bug ( The busid reported by libdrm on
> the arm64 system is "0007:a1:00.0"), has it been accept by upstram? Do you
> have bug id for it? Actually, I think we can take both those 2 bugs back to
> Huawei or Pearl team in case it is bugs from Kernel.
>
> thanks,
> Mao
>
> On Fri, Jun 16, 2017 at 11:46 AM, Daniel Axtens <
> daniel.axt...@canonical.com> wrote:
>
>> Hi Mao,
>>
>> I have done more work on the HiSilicon board. I have talked with the SEG
>> team and our conclusion is that the hardware is not compliant with the
>> specification, but that it is appropriate to include a workaround in
>> software.
>>
>> I have developed a patch that adds a workaround or 'quirk' to the kernel
>> specifically for the hisilicon graphics card and the hisilicon PCI
>> bridge. It tests for the card and the bridge on the development board. I
>> think it might be acceptable for upstream. With this, X
>> autoconfiguration works.
>>
>> Please could you ask the HiSilicon people if there are other boards or
>> parts with different PCI IDs that should be included in this fixup?
>>
>> Regards,
>> Daniel
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1691991
>>
>> Title:
>>   Xorg Segmentation fault on Hisilicon D05 board (arm64)
>>
>> Status in xorg package in Ubuntu:
>>   New
>>
>> Bug description:
>>   ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg
>>   [sudo] password for ubuntu:
>>
>>   X.Org X Server 1.18.4
>>   Release Date: 2016-07-19
>>   X Protocol Version 11, Revision 0
>>   Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
>>   Current Operating System: Linux ubuntu 4.10.0-20.22-generic
>> #22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
>>   Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic
>> root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug
>> earlycon=pl011,mmio,0x602B console=tty0
>>   Build Date: 02 November 2016  10:05:28PM
>>   xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see
>> http://www.ubuntu.com/support)
>>   Current version of pixman: 0.33.6
>> Before reporting problems, check http://wiki.x.org
>> to make sure that you have the latest version.
>>   Markers: (--) probed, (**) from config file, (==) default setting,
>> (++) from command line, (!!) notice, (II) informational,
>> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>>   (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
>>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>>   pci id for fd 10: 19e5:1711, driver (null)
>>   EGL_MESA_drm_image required.
>>   (EE)
>>   (EE) Backtrace:
>>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
>>   (EE)
>>   (EE) Segmentation fault at address 0xa0
>>   (EE)
>>   Fatal server error:
>>   (EE) Caught signal 11 (Segmentation fault). Server aborting
>>   (EE)
>>   (EE)
>>   Please consult the The X.Org Foundation support
>>  at http://wiki.x.org
>>for help.
>>   (EE) Please also check the log file at "/var/log/Xorg.0.log" for
>> additional information.
>>   (EE)
>>   (EE) Server terminated with error (1). Closing log file.
>>   Aborted (core dumped)
>>   ubuntu@ubuntu:~$
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/
>> +subscriptions
>>
>
>
>
> --
> Zhanglei Mao
> Solutions Architect, Sales and Business Development
> Canonical Group Ltd.
> zhanglei@canonical.com
> +86-13625010929 <+86%20136%202501%200929> (m)
> +852-6700 6026 <+852%206700%206026> (m)
> www.ubuntu.com
> www.canonical.com
>


-- 
Zhanglei Mao
Solutions Architect, Sales and Business Development
Canonical Group Ltd.
zhanglei@canonical.com
+86-13625010929 (m)
+852-6700 6026 (m)
www.ubuntu.com
www.canonical.com

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 

[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

[Zhanglei Mao]

Translate from Huawei's reply mail: The sever board have only this VGA PCI 
devices: 
   19e5  Huawei Technologies Co., Ltd.
   1711  Hi1710 [iBMC Intelligent Management system chip w/VGA support]

Please check if this math to our D05 testing environment.

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+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 1698520] [NEW] I can not open raf archives of fujifilm X-T2 in UfRaw/Gimp

[chichomolina]

Public bug reported:

Hi:I can not open raf archives of fujifilm X-T2 in UfRaw/Gimp. Any
solution with this cain of files? Many thanks in advance.

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

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

Title:
  I can not open raf archives of fujifilm X-T2 in UfRaw/Gimp

Status in debconf package in Ubuntu:
  New

Bug description:
  Hi:I can not open raf archives of fujifilm X-T2 in UfRaw/Gimp. Any
  solution with this cain of files? Many thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1698520/+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 1698384] Re: package network-manager 1.4.4-1ubuntu3.1 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: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  package network-manager 1.4.4-1ubuntu3.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  My networkmanager is masked as I'm using systemd-networkd and I don't
  want networkmanager running

  # apt upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up network-manager (1.4.4-1ubuntu3.1) ...
  Failed to try-restart NetworkManager-wait-online.service: Unit 
NetworkManager-wait-online.service is masked.
  Failed to enable unit: Unit file 
/etc/systemd/system/NetworkManager-wait-online.service is masked.
  dpkg: error processing package network-manager (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   network-manager
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3.1
  Uname: Linux 4.11.0-3.1-liquorix-amd64 x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Fri Jun 16 15:48:11 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  IpRoute:
   default via 10.154.160.10 dev eno1 src 10.154.161.10 metric 202 
   default via 10.154.160.10 dev eno1 proto dhcp src 10.154.161.10 metric 1024 
   10.154.160.0/20 dev eno1 proto kernel scope link src 10.154.161.10 metric 
202 
   10.154.160.10 dev eno1 proto dhcp scope link src 10.154.161.10 metric 1024
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  RfKill:
   
  SourcePackage: network-manager
  Title: package network-manager 1.4.4-1ubuntu3.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to zesty on 2017-04-22 (54 days ago)
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1698384/+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 1689825] Re: gnome-keyring not unlocked on boot

[Keith Newman]

Hans' observation that this is not impacting all of his machines is
consistent with my experience of this issue. I have three Ubuntu
machines and this is only impacting one of them. It is driving me nuts
because the machine that is impacted is my main laptop. My server and my
test machine which would be less of an issue to me as they don't get
booted so often are working fine. A classic example of Murphy's Law.

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  New
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1698516] Re: package libgl1-mesa-dri 11.2.0-1ubuntu2.2 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libg

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

Title:
  package libgl1-mesa-dri 11.2.0-1ubuntu2.2 failed to install/upgrade:
  trying to overwrite shared '/etc/drirc', which is different from other
  instances of package libgl1-mesa-dri:amd64

Status in mesa package in Ubuntu:
  New

Bug description:
  Was doing a regular sudo apt-get upgrade and got an error all of a
  sudden.  Was expected a clean upgrade with no intervention like now
  the upgrade normally works.

  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy libgl1-mesa-dri
  libgl1-mesa-dri:
Installed: 11.2.0-1ubuntu2.2
Candidate: 12.0.6-0ubuntu0.16.04.1
Version table:
   12.0.6-0ubuntu0.16.04.1 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt xenial-updates/main amd64 
Packages
  500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 11.2.0-1ubuntu2.2 100
  100 /var/lib/dpkg/status
   11.2.0-1ubuntu2 500
  500 mirror://mirrors.ubuntu.com/mirrors.txt xenial/main amd64 Packages
  500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Fri Jun 16 23:12:47 2017
  DistUpgraded: 2016-08-14 23:56:55,953 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-36-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-34-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-36-generic, x86_64: installed
  DuplicateSignature:
   package:libgl1-mesa-dri:11.2.0-1ubuntu2.2
   Unpacking libgl1-mesa-dri:amd64 (12.0.6-0ubuntu0.16.04.1) over 
(11.2.0-1ubuntu2.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libgl1-mesa-dri_12.0.6-0ubuntu0.16.04.1_amd64.deb 
(--unpack):
trying to overwrite shared '/etc/drirc', which is different from other 
instances of package libgl1-mesa-dri:amd64
  ErrorMessage: trying to overwrite shared '/etc/drirc', which is different 
from other instances of package libgl1-mesa-dri:amd64
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 760] [3842:2768]
  InstallationDate: Installed on 2015-02-08 (860 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=5f6d3d07-0215-46db-9fea-737305a33e02 ro rootflags=subvol=@ nomodeset 
nomdmonddf nomdmonisw
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 11.2.0-1ubuntu2.2 failed to install/upgrade: 
trying to overwrite shared '/etc/drirc', which is different from other 
instances of package libgl1-mesa-dri:amd64
  UpgradeStatus: Upgraded to xenial on 2016-08-15 (305 days ago)
  dmi.bios.date: 01/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0904
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87M-E
  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: 

[Touch-packages] [Bug 1698516] [NEW] package libgl1-mesa-dri 11.2.0-1ubuntu2.2 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package li

[Henry]

Public bug reported:

Was doing a regular sudo apt-get upgrade and got an error all of a
sudden.  Was expected a clean upgrade with no intervention like now the
upgrade normally works.

Description:Ubuntu 16.04.2 LTS
Release:16.04

apt-cache policy libgl1-mesa-dri
libgl1-mesa-dri:
  Installed: 11.2.0-1ubuntu2.2
  Candidate: 12.0.6-0ubuntu0.16.04.1
  Version table:
 12.0.6-0ubuntu0.16.04.1 500
500 mirror://mirrors.ubuntu.com/mirrors.txt xenial-updates/main amd64 
Packages
500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 *** 11.2.0-1ubuntu2.2 100
100 /var/lib/dpkg/status
 11.2.0-1ubuntu2 500
500 mirror://mirrors.ubuntu.com/mirrors.txt xenial/main amd64 Packages
500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgl1-mesa-dri 11.2.0-1ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
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: Fri Jun 16 23:12:47 2017
DistUpgraded: 2016-08-14 23:56:55,953 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-36-generic, x86_64: installed
 nvidia-361, 361.42, 4.4.0-34-generic, x86_64: installed
 nvidia-361, 361.42, 4.4.0-36-generic, x86_64: installed
DuplicateSignature:
 package:libgl1-mesa-dri:11.2.0-1ubuntu2.2
 Unpacking libgl1-mesa-dri:amd64 (12.0.6-0ubuntu0.16.04.1) over 
(11.2.0-1ubuntu2.2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libgl1-mesa-dri_12.0.6-0ubuntu0.16.04.1_amd64.deb 
(--unpack):
  trying to overwrite shared '/etc/drirc', which is different from other 
instances of package libgl1-mesa-dri:amd64
ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from 
other instances of package libgl1-mesa-dri:amd64
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GK104 [GeForce GTX 760] [3842:2768]
InstallationDate: Installed on 2015-02-08 (860 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=5f6d3d07-0215-46db-9fea-737305a33e02 ro rootflags=subvol=@ nomodeset 
nomdmonddf nomdmonisw
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: mesa
Title: package libgl1-mesa-dri 11.2.0-1ubuntu2.2 failed to install/upgrade: 
trying to overwrite shared '/etc/drirc', which is different from other 
instances of package libgl1-mesa-dri:amd64
UpgradeStatus: Upgraded to xenial on 2016-08-15 (305 days ago)
dmi.bios.date: 01/06/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0904
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87M-E
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.:bvr0904:bd01/06/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.68+git1604280630.fc09c5~gd~t
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: