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

[Zhanglei Mao]

Yes, you can close this bug now. Thank you very much for your good works
and to fix this problems.

-- 
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 1685007] Re: package bluez:i386 5.37-0ubuntu5 failed to install/upgrade: aliprosessi komentotiedosto post-installation asennettu palautti virhetilakoodin 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package bluez:i386 5.37-0ubuntu5 failed to install/upgrade:
  aliprosessi komentotiedosto post-installation asennettu palautti
  virhetilakoodin 1

Status in bluez package in Ubuntu:
  Expired

Bug description:
  dont working

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez:i386 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Apr 20 22:45:53 2017
  ErrorMessage: aliprosessi komentotiedosto post-installation asennettu 
palautti virhetilakoodin 1
  InstallationDate: Installed on 2017-04-20 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  InterestingModules: bnep bluetooth
  MachineType: Hewlett-Packard HP 250 G3 Notebook PC
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=5ae53ed4-6ded-4c79-a24b-3d7de51913c2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: bluez
  Title: package bluez:i386 5.37-0ubuntu5 failed to install/upgrade: 
aliprosessi komentotiedosto post-installation asennettu palautti 
virhetilakoodin 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.39
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2213
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.54
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.39:bd05/26/2015:svnHewlett-Packard:pnHP250G3NotebookPC:pvr097510405F0620181:rvnHewlett-Packard:rn2213:rvr57.54:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 250 G3 Notebook PC
  dmi.product.version: 097510405F0620181
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1685007/+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 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Kai-Heng Feng]

Please try this: http://people.canonical.com/~khfeng/lp1654448-artful/

** Changed in: linux (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

Status in Dell Sputnik:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+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 1699001] [NEW] package liblzma5:i386 5.1.1alpha+20120614-2ubuntu2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar co

[CyberMSX]

Public bug reported:

error of instalation after try to install teamviewer 12

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: liblzma5:i386 5.1.1alpha+20120614-2ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Tue Jun 20 00:11:16 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
 multiarch-support 2.23-0ubuntu9
DpkgTerminalLog:
 dpkg: erro ao processar o pacote liblzma5:i386 (--configure):
  O pacote está num mau estado de inconsistência; deve
  reinstala-lo antes de tentar configura-lo.
ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
InstallationDate: Installed on 2017-05-01 (49 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: xz-utils
Title: package liblzma5:i386 5.1.1alpha+20120614-2ubuntu2 failed to 
install/upgrade: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xz-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package liblzma5:i386 5.1.1alpha+20120614-2ubuntu2 failed to
  install/upgrade: O pacote está num mau estado de inconsistência; deve
  reinstala-lo antes de tentar configura-lo.

Status in xz-utils package in Ubuntu:
  New

Bug description:
  error of instalation after try to install teamviewer 12

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liblzma5:i386 5.1.1alpha+20120614-2ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue Jun 20 00:11:16 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu9
  DpkgTerminalLog:
   dpkg: erro ao processar o pacote liblzma5:i386 (--configure):
O pacote está num mau estado de inconsistência; deve
reinstala-lo antes de tentar configura-lo.
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  InstallationDate: Installed on 2017-05-01 (49 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: xz-utils
  Title: package liblzma5:i386 5.1.1alpha+20120614-2ubuntu2 failed to 
install/upgrade: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1699001/+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 1698795] Re: App icons in top panel (next to menu) doesn't match theme

[Daniel van Vugt]

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

** Tags added: gnome-17.10

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

Title:
  App icons in top panel (next to menu) doesn't match theme

Status in gnome-shell package in Ubuntu:
  New
Status in humanity-icon-theme package in Ubuntu:
  New

Bug description:
  The app icon in top panel next to application menu entry is the
  default adwaita icons and don't match the current theming.

  It's either:
  - the fact that we don't provide the correct icon size in our themes, and so, 
the icons are defaulted
  - a bug in G-S

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1698795/+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 1698638] Re: indicator-datetime list evolution calendar full-day event a day before actual date of event (Unity-7)

[Jeremy Bicha]

** Changed in: indicator-datetime (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  indicator-datetime list evolution calendar full-day event a day before
  actual date of event (Unity-7)

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  Indicator-datetime lists events to take place one day ahead e.g. all
  day event on Monday is listed to be happen on Sunday

  Also this scenario also happens for today's date. Foe example;

  1. Create a full-day-event in any previous day (2nd june 2017)
  2. Click 2nd june on calendar
  3. Full-day event is listed there.

  But it doesn't work for today's date. (DTSTART == DTEND)

  1. Create a full-day-event on today.
  2. Click today on calendar
  3. Full-day event is NOT listed there.
  4. Click previous day.and you will find full-day event listed there
  5. It even shows today's date on side but just doesn't list the event on 
today's date.

  Note: This is reproducible for any event when DTSTART == DTEND (i.e
  Events from Google Calendar)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1698638/+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 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)

[Bug Watch Updater]

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

** Changed in: glib
   Importance: Unknown => Low

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

Title:
  fstab binds appear as mounts (x-gvfs-hide is being ignored)

Status in GLib:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  glib2 version 2.52.2+1+gb8bd46bc8-1 (possibly the version before it as
  well, I haven't tested) causes fstab binds to appear as mounts in
  Nautilus (and in Deepin Dock - Deepin is based on Gnome).

  Downgrading to glib2 and glib2-docs 2.52.0-1 resolves this behaviour.

  I first noted this bug behaviour here:
  https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/452049

  Details of my particular system and issue with what I tried to resolve
  it can be found here:
  https://bbs.archlinux.org/viewtopic.php?pid=1712030#p1712030

  1. Not using Ubuntu. Deepin Desktop 15.4 (Gnome based) on Arch Linux.

   OS: Arch Linux 
   Kernel: x86_64 Linux 4.10.13-1-ARCH
   Shell: bash 4.4.12
   Resolution: 1920x1200
   DE: Deepin 15.4
   WM: Deepin WM
   WM Theme: Arc-Darker
   GTK Theme: Arc-Darker [GTK2/3]
   Icon Theme: deepin
   Font: Noto Sans 11
   CPU: Intel Core i5-6500 @ 4x 3.6GHz [27.8°C]
   GPU: GeForce GTX 950
   RAM: 2598MiB / 15990MiB

  2. 2.52.2+1+gb8bd46bc8-1 (downgrading to 2.52.0-1 removed the
  problem).

  3. Nautilus to list internal physical drives (my SSD and 1TB HDD)
  only.

  4. Nautilus listed my system disk (as expected) but also listed all of
  my fstab binds as removable drives (Downloads, Music, Pictures, Videos
  and Documents although this was not listed as "Documents" but instead
  listed as the HDD label "Farsight"). Adding x-gvfs-hide did not hide
  those drives.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1691908/+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 1698979] [NEW] ftbfs with python 3.6

[Michael Hudson-Doyle]

Public bug reported:

Tests fail with Python 3.6:

==
FAIL: 
autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_launcher_wrapper_raises_runtimeerror
--
Traceback (most recent call last):
  File 
"/<>/autopilot-1.6.0+17.04.20170313/autopilot/tests/unit/test_application_launcher.py",
 line 1091, in test_get_application_launcher_wrapper_raises_runtimeerror
raises(RuntimeError(expected_error))
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 435, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: RuntimeError("Command '['ldd', 
'autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_launcher_wrapper_raises_runtimeerror-1']'
 returned non-zero exit status 1.",) has different arguments to 
RuntimeError("Command '['ldd', 
'autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_launcher_wrapper_raises_runtimeerror-1']'
 returned non-zero exit status 1",).
==
FAIL: 
autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_path_raises_when_cant_find_app
--
Traceback (most recent call last):
  File 
"/<>/autopilot-1.6.0+17.04.20170313/autopilot/tests/unit/test_application_launcher.py",
 line 1076, in test_get_application_path_raises_when_cant_find_app
raises(ValueError(expected_error))
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 435, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: ValueError("Unable to find path for 
application 
autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_path_raises_when_cant_find_app-1:
 Command '['which', 
'autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_path_raises_when_cant_find_app-1']'
 returned non-zero exit status 1.",) has different arguments to 
ValueError("Unable to find path for application 
autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_path_raises_when_cant_find_app-1:
 Command '['which', 
'autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_path_raises_when_cant_find_app-1']'
 returned non-zero exit status 1",).

It's a bit hard to see but I think the difference is just that there is
a period at the end of the error messages now.

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


** Tags: python3.6

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

Title:
  ftbfs with python 3.6

Status in autopilot package in Ubuntu:
  New

Bug description:
  Tests fail with Python 3.6:

  ==
  FAIL: 
autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_launcher_wrapper_raises_runtimeerror
  --
  Traceback (most recent call last):
File 
"/<>/autopilot-1.6.0+17.04.20170313/autopilot/tests/unit/test_application_launcher.py",
 line 1091, in test_get_application_launcher_wrapper_raises_runtimeerror
  raises(RuntimeError(expected_error))
File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 435, in 
assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: RuntimeError("Command '['ldd', 
'autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_launcher_wrapper_raises_runtimeerror-1']'
 returned non-zero exit status 1.",) has different arguments to 
RuntimeError("Command '['ldd', 
'autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_launcher_wrapper_raises_runtimeerror-1']'
 returned non-zero exit status 1",).
  ==
  FAIL: 
autopilot.tests.unit.test_application_launcher.ApplicationLauncherInternalTests.test_get_application_path_raises_when_cant_find_app
  --
  Traceback (most recent call last):
File 
"/<>/autopilot-1.6.0+17.04.20170313/autopilot/tests/unit/test_application_launcher.py",
 line 1076, in test_get_application_path_raises_when_cant_find_app
  raises(ValueError(expected_error))
File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 435, in 
assertThat
  raise mismatch_error
  

[Touch-packages] [Bug 1692127] Re: duplicate signature for Package problems can be too short

[Brian Murray]

** Description changed:

- Steve brought up bug 1691983 and how it's duplicate signature is missing
- information.  It contains:
+ [Impact]
+ apport is creating a shorter than necessary duplicate signature in 
apport-package bug reports which can lead to misconsolidation and confused 
developers.
+ 
+ [Test Case]
+ 1) Boot a system with an old kernel installed or a freshly installed system
+ 2) edit /etc/default/grub and replace a ` with a '
+ 3) Upgrade the kernel, watch it crash
+ 4) Discover a crash report with a DuplicateSignature whose 2nd line starts 
with "Examining"
+ 
+ With the version of the package from -proposed the DuplicateSignature in
+ this case should really have a 2nd line that starts with 'Setting up
+ linux-image* ...'. While in this particular case not much is lost in
+ other cases valuable information will be missing.
+ 
+ [Regression Potential]
+ The code change is correct and has been tested in artful, additionally I'm 
using the same regular expression to clean up apport-package reports as they 
come in to LP. The only risk here is a typo in the patch that would cause the 
hook (the change is in the ubuntu general hook) to error out which apport would 
handle gracefully and we just wouldn't have a DuplicateSignature.
+ 
+ [The Original Description]
+ Steve brought up bug 1691983 and how it's duplicate signature is missing 
information.  It contains:
  
  package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  Installing for x86_64-efi platform.
  Installation finished. No error reported.
  Running in non-interactive mode, doing nothing.
  dpkg: error processing package shim-signed (--configure):
-  subprocess installed post-installation script returned error exit status 1
+  subprocess installed post-installation script returned error exit status 1
  
  But is missing:
  
  Setting up shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
  locale: Cannot set LC_CTYPE to default locale: No such file or directory
  locale: Cannot set LC_MESSAGES to default locale: No such file or directory
  locale: Cannot set LC_ALL to default locale: No such file or directory
  debconf: unable to initialize frontend: Passthrough
  debconf: (Cannot connect to /tmp/aptdaemon-7jrqb_du/debconf.socket: 
Connection refused at (eval 18) line 3.)
  debconf: falling back to frontend: Noninteractive
  
  This is because of the following code in data/general-hooks/ubuntu.py:
  
  145 PKG_MSGS = ('Authenticating', 'De-configuring', 'Examining',
  146 'Installing ', 'Preparing', 'Processing 
triggers', 'Purging',
  147 'Removing', 'Replaced', 'Replacing', 'Setting up',
  148 'Unpacking', 'Would remove')
  149 for line in termlog.split('\n'):
  150 if line.startswith(PKG_MSGS):
  151 dupe_sig = '%s\n' % line
  152 continue
  
  The shim-signed package prints a line starts with "Installing " and that
  matches PKG_MSGS so we reset the dupe_sig because that's a message we'd
  expect from a package manager.

** Changed in: apport (Ubuntu Yakkety)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: apport (Ubuntu Xenial)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: apport (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: apport (Ubuntu Yakkety)
   Status: Triaged => In Progress

** Changed in: apport (Ubuntu Zesty)
   Status: Triaged => In Progress

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

Title:
  duplicate signature for Package problems can be too short

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  In Progress
Status in apport source package in Yakkety:
  In Progress
Status in apport source package in Zesty:
  In Progress
Status in apport source package in Artful:
  Fix Released

Bug description:
  [Impact]
  apport is creating a shorter than necessary duplicate signature in 
apport-package bug reports which can lead to misconsolidation and confused 
developers.

  [Test Case]
  1) Boot a system with an old kernel installed or a freshly installed system
  2) edit /etc/default/grub and replace a ` with a '
  3) Upgrade the kernel, watch it crash
  4) Discover a crash report with a DuplicateSignature whose 2nd line starts 
with "Examining"

  With the version of the package from -proposed the DuplicateSignature
  in this case should really have a 2nd line that starts with 'Setting
  up linux-image* ...'. While in this particular case not much is lost
  in other cases valuable information will be missing.

  [Regression Potential]
  The code change is correct and has been tested in artful, additionally I'm 
using the same regular expression to clean up apport-package reports as 

[Touch-packages] [Bug 1698972] [NEW] package bsdutils 1:2.29-1ubuntu2 [modified: usr/bin/logger usr/bin/renice usr/bin/script usr/bin/scriptreplay usr/bin/wall] failed to install/upgrade: package bsdu

[Michael Ulett]

Public bug reported:

I am not sure that the issue is a bug.
I was trying to install screen by the command prompt when i got the error 
message.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: bsdutils 1:2.29-1ubuntu2 [modified: usr/bin/logger usr/bin/renice 
usr/bin/script usr/bin/scriptreplay usr/bin/wall]
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:
 bsdutils:amd64: Configure
 screen:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Jun 19 18:32:36 2017
DpkgTerminalLog:
 dpkg: error processing package bsdutils (--configure):
  package bsdutils is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package bsdutils is not ready for configuration  cannot configure 
(current status 'half-installed')
InstallationDate: Installed on 2017-06-03 (16 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: util-linux
Title: package bsdutils 1:2.29-1ubuntu2 [modified: usr/bin/logger 
usr/bin/renice usr/bin/script usr/bin/scriptreplay usr/bin/wall] failed to 
install/upgrade: package bsdutils is not ready for configuration  cannot 
configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package bsdutils 1:2.29-1ubuntu2 [modified: usr/bin/logger
  usr/bin/renice usr/bin/script usr/bin/scriptreplay usr/bin/wall]
  failed to install/upgrade: package bsdutils is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in util-linux package in Ubuntu:
  New

Bug description:
  I am not sure that the issue is a bug.
  I was trying to install screen by the command prompt when i got the error 
message.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2 [modified: usr/bin/logger usr/bin/renice 
usr/bin/script usr/bin/scriptreplay usr/bin/wall]
  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:
   bsdutils:amd64: Configure
   screen:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Jun 19 18:32:36 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package bsdutils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package bsdutils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-03 (16 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 [modified: usr/bin/logger 
usr/bin/renice usr/bin/script usr/bin/scriptreplay usr/bin/wall] failed to 
install/upgrade: package bsdutils is not ready for configuration  cannot 
configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1698972/+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 1698171] Re: package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: le paquet openssl n'est pas prêt pour la configuration configuration impossible (état actuel « half-ins

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: le paquet
  openssl n'est pas prêt pour la configuration  configuration impossible
  (état actuel « half-installed »)

Status in openssl package in Ubuntu:
  New

Bug description:
  je voudrais installer Minecraft pour y jouer, j'ai été sur un site qui
  m'a demander de faire un commande sur "Terminal". je l'ai effectuer (
  voici le site :https://doc.ubuntu-fr.org/minecraft) j'espère que vous
  trouverez une solution très rapidement merci.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   minecraft-installer: Install
   openssl: Configure
   minecraft-installer: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Thu Jun 15 19:13:14 2017
  ErrorMessage: le paquet openssl n'est pas prêt pour la configuration  
configuration impossible (état actuel « half-installed »)
  InstallationDate: Installed on 2017-05-14 (31 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: le paquet 
openssl n'est pas prêt pour la configuration  configuration impossible (état 
actuel « half-installed »)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1698171/+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 1698244] Re: package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakiet openssl nie jest gotowy do skonfigurowania nie można go skonfigurować (bieżący stan "half-instal

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakiet
  openssl nie jest gotowy do skonfigurowania  nie można go skonfigurować
  (bieżący stan "half-installed")

Status in openssl package in Ubuntu:
  New

Bug description:
  package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakiet
  openssl nie jest gotowy do skonfigurowania  nie można go skonfigurować
  (bieżący stan "half-installed")

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4.8
  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: Wed Jun 14 14:33:16 2017
  ErrorMessage: pakiet openssl nie jest gotowy do skonfigurowania  nie można go 
skonfigurować (bieżący stan "half-installed")
  InstallationDate: Installed on 2016-09-30 (258 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakiet 
openssl nie jest gotowy do skonfigurowania  nie można go skonfigurować (bieżący 
stan "half-installed")
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1698244/+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 1698100] Re: package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: el paquete openssl no está listo para configurarse no se puede configurar (estado actual `half-installe

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: el
  paquete openssl no está listo para configurarse  no se puede
  configurar (estado actual `half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  Automatic report

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4.6
  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: Thu Jun 15 10:57:22 2017
  ErrorMessage: el paquete openssl no está listo para configurarse  no se puede 
configurar (estado actual `half-installed')
  InstallationDate: Installed on 2016-11-04 (222 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: el 
paquete openssl no está listo para configurarse  no se puede configurar (estado 
actual `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1698100/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[NJ]

Cruz, thanks for this.

However, (1) after all the trouble I had getting OpenVPN working, I
don't fancy switching to something else (and my system does work at
present, using the older version of Network Manager).

Also, (2) I don't really understand what you say about /etc/hosts,
though probably I could work it out.

Further, (3) if I understand the last paragraph of your comment #13: I
don't know; after all, at the top of this page we can read not only,
'Xenial - In Progress' (though it seems pretty slow progress! It's been
at least a month since this show-stopping bug was first reported) but
also, 'Yakkety - Triaged'.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1698113] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssl package in Ubuntu:
  New

Bug description:
  Update Failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Thu Jun 15 11:41:07 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-05-13 (397 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to xenial on 2017-04-12 (63 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1698113/+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 1698104] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 usr/lib/x86_64-linux-gnu/openssl-

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64
  -linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so
  usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to
  install/upgrade: пакет libssl1.0.0:amd64 не готов к настройке
  настройка невозможна (текущее состояние: «half-installed»)

Status in openssl package in Ubuntu:
  New

Bug description:
  Problem.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
  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: Thu Jun 15 13:37:43 2017
  ErrorMessage: пакет libssl1.0.0:amd64 не готов к настройке  настройка 
невозможна (текущее состояние: «half-installed»)
  InstallationDate: Installed on 2017-06-03 (11 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1698104/+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 1697290] Re: package libssl-doc 1.0.2g-1ubuntu4.8 failed to install/upgrade: pacote libssl-doc não está pronto para configuração não posso configurar (estado atual 'half-install

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl-doc 1.0.2g-1ubuntu4.8 failed to install/upgrade: pacote
  libssl-doc não está pronto para configuração  não posso configurar
  (estado atual 'half-installed')

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  Tentei diversas vezes executar esta atualização. Mesmo com o uso de
  ferramentas como "dpkg --configure -a" ou o "apt-get -f install" não
  obtive sucesso.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl-doc 1.0.2g-1ubuntu4.8
  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
  AptOrdering:
   libssl-doc: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jun 11 12:40:04 2017
  Dependencies:
   
  DpkgTerminalLog:
   dpkg: erro ao processar o pacote libssl-doc (--configure):
pacote libssl-doc não está pronto para configuração
não posso configurar (estado atual 'half-installed')
  ErrorMessage: pacote libssl-doc não está pronto para configuração  não posso 
configurar (estado atual 'half-installed')
  InstallationDate: Installed on 2016-06-18 (358 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl-doc 1.0.2g-1ubuntu4.8 failed to install/upgrade: pacote 
libssl-doc não está pronto para configuração  não posso configurar (estado 
atual 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1697290/+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 1698292] Re: package libssl-doc 1.0.2g-1ubuntu4.6 [modified: usr/share/doc/libssl-doc/changelog.Debian.gz usr/share/man/man3/evp.3ssl.gz] failed to install/upgrade: package libss

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl-doc 1.0.2g-1ubuntu4.6 [modified: usr/share/doc/libssl-
  doc/changelog.Debian.gz usr/share/man/man3/evp.3ssl.gz] failed to
  install/upgrade: package libssl-doc is not ready for configuration
  cannot configure (current status 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  Everyday the same thing.
  I cannot install last software updates.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl-doc 1.0.2g-1ubuntu4.6 [modified: 
usr/share/doc/libssl-doc/changelog.Debian.gz usr/share/man/man3/evp.3ssl.gz]
  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: Thu Jun 15 15:09:25 2017
  Dependencies:
   
  ErrorMessage: package libssl-doc is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-02-20 (115 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl-doc 1.0.2g-1ubuntu4.6 [modified: 
usr/share/doc/libssl-doc/changelog.Debian.gz usr/share/man/man3/evp.3ssl.gz] 
failed to install/upgrade: package libssl-doc is not ready for configuration  
cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1698292/+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 1698097] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6
  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: Thu Jun 15 10:05:06 2017
  DuplicateSignature:
   package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.6
   Processing triggers for libc-bin (2.23-0ubuntu7) ...
   dpkg: error processing package libssl1.0.0:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-06-02 (12 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1698097/+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 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[Seth Arnold]

Hello; would those of you affected by this bug please attach your
/var/log/apt/term.log file?

Thanks

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

Title:
  package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   libssl1.0.0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue May 23 21:47:55 2017
  DuplicateSignature:
   package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
   Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
   dpkg: error processing package libssl-dev:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-15 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: openssl
  Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1692981/+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 1698303] Re: package libssl-doc 1.0.2g-1ubuntu4.6 [modified: usr/share/doc/libssl-doc/changelog.Debian.gz] failed to install/upgrade: package libssl-doc is not ready for configur

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl-doc 1.0.2g-1ubuntu4.6 [modified: usr/share/doc/libssl-
  doc/changelog.Debian.gz] failed to install/upgrade: package libssl-doc
  is not ready for configuration  cannot configure (current status
  'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  Updating of the package is not possible. Other packages included in this 
update are:
  grub-common
  grub-pc
  grub-pc-bin
  grub2-common
  libssl-dev
  linux-firmware
  openssl
  yad
  zziplib-bin

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl-doc 1.0.2g-1ubuntu4.6 [modified: 
usr/share/doc/libssl-doc/changelog.Debian.gz]
  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: Fri Jun 16 09:33:07 2017
  Dependencies:
   
  DuplicateSignature:
   package:libssl-doc:1.0.2g-1ubuntu4.6 [modified: 
usr/share/doc/libssl-doc/changelog.Debian.gz]
   Unpacking firefox-locale-en (54.0+build3-0ubuntu0.16.04.1) over 
(53.0.3+build1-0ubuntu0.16.04.2) ...
   dpkg: error processing package libssl-doc (--configure):
package libssl-doc is not ready for configuration
  ErrorMessage: package libssl-doc is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-08-29 (290 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl-doc 1.0.2g-1ubuntu4.6 [modified: 
usr/share/doc/libssl-doc/changelog.Debian.gz] failed to install/upgrade: 
package libssl-doc is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1698303/+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 1698150] Re: package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: Paket openssl ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »hal

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: Paket
  openssl ist nicht bereit zur Konfiguration  kann nicht konfiguriert
  werden (momentaner Status »half-installed«)

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  Installation over Softwarecenter and that was it, afterwards I got after
  new start of the system and login the error message.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4.8
  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: Thu Jun 15 12:56:35 2017
  ErrorMessage: Paket openssl ist nicht bereit zur Konfiguration  kann nicht 
konfiguriert werden (momentaner Status »half-installed«)
  InstallationDate: Installed on 2017-03-03 (104 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: Paket 
openssl ist nicht bereit zur Konfiguration  kann nicht konfiguriert werden 
(momentaner Status »half-installed«)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1698150/+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 1698670] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: lib/i386-linux-gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0 usr/lib/i386-linux-gnu/openssl-1.0.0/e

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: lib/i386-linux-
  gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0 usr/lib/i386
  -linux-gnu/openssl-1.0.0/engines/lib4758cca.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libaep.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libatalla.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libcapi.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libchil.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libcswift.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libgmp.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libgost.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libnuron.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libpadlock.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libsureware.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libubsec.so
  usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to
  install/upgrade: el paquete libssl1.0.0:i386 no está listo para
  configurarse  no se puede configurar (estado actual `half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  please

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: 
lib/i386-linux-gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun Jun 18 11:19:46 2017
  ErrorMessage: el paquete libssl1.0.0:i386 no está listo para configurarse  no 
se puede configurar (estado actual `half-installed')
  InstallationDate: Installed on 2017-05-05 (44 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1698670/+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 1698098] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu9.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu9.3 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssl package in Ubuntu:
  New

Bug description:
  at the startup the system say me that an error occur.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu9.3
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8.3
  AptOrdering:
   libgnutls30:amd64: Install
   flashplugin-installer:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Jun 15 07:17:57 2017
  DuplicateSignature:
   package:libssl1.0.0:amd64:1.0.2g-1ubuntu9.3
   Unpacking flashplugin-installer (26.0.0.126ubuntu0.16.10.1) over 
(25.0.0.171ubuntu0.16.10.1) ...
   dpkg: error processing package libssl1.0.0:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-12-12 (184 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu9.3 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1698098/+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 1698324] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: package libssl1.0.0:amd64 is not ready for configuration cannot configure (current status 'hal

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade:
  package libssl1.0.0:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  I got notification of an OS update... 
  The install failed 
  The next time I rebooted I got another notification to report this issue

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 4.10.0-10.12~16.04.2+IntelAtom-linuxium 4.10.0
  Uname: Linux 4.10.0-10-linuxium x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun 14 04:26:56 2017
  DuplicateSignature:
   package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.8
   Installing from local file 
/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20170613.2.orig.tar.gz
   Flash Plugin installed.
   dpkg: error processing package libssl1.0.0:amd64 (--configure):
package libssl1.0.0:amd64 is not ready for configuration
  ErrorMessage: package libssl1.0.0:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-04-22 (54 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" Linuxium - Release Intel 
Atom (20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: 
package libssl1.0.0:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1698324/+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 1583463] Re: package openssl 1.0.2g-1ubuntu4 [modified: usr/bin/openssl] failed to install/upgrade: package openssl is not ready for configuration cannot configure (current statu

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package openssl 1.0.2g-1ubuntu4 [modified: usr/bin/openssl] failed to
  install/upgrade: package openssl is not ready for configuration
  cannot configure (current status 'half-installed')

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4 [modified: usr/bin/openssl]
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 14:32:45 2016
  ErrorMessage: package openssl is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-05-19 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: openssl
  Title: package openssl 1.0.2g-1ubuntu4 [modified: usr/bin/openssl] failed to 
install/upgrade: package openssl is not ready for configuration  cannot 
configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1583463/+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 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[Launchpad Bug Tracker]

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

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

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

Title:
  package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   libssl1.0.0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue May 23 21:47:55 2017
  DuplicateSignature:
   package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
   Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
   dpkg: error processing package libssl-dev:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-15 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: openssl
  Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1692981/+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 1696827] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 usr/lib/x86_64-linux-gnu/openssl-

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64
  -linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so
  usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to
  install/upgrade: package libssl1.0.0:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  I keep getting a error with dvd+rw-tools, install and remove.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libssl1.0.0: Configure
   dvd+rw-tools: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Jun  8 12:33:20 2017
  ErrorMessage: package libssl1.0.0:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-23 (16 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1696827/+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 1696799] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  share/bleachbit/bleachbit/Command.py", line 131, in execute
  func_ret = self.func()
File "/usr/share/bleachbit/bleachbit/Unix.py", line 383, in apt_autoremove
  raise RuntimeError(line)
  RuntimeError: E: Sub-process /usr/bin/dpkg returned an error code (1)
  Delete 1.1MB /var/cache/apt/archivesshare/bleachbit/bleachbit/Command.py", 
line 131, in execute
  func_ret = self.func()
File "/usr/share/bleachbit/bleachbit/Unix.py", line 383, in apt_autoremove
  raise RuntimeError(line)
  RuntimeError: E: Sub-process /usr/bin/dpkg returned an error code (1)
  Delete 1.1MB /var/cache/apt/archives

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8
  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
  AptOrdering:
   libssl1.0.0: Install
   libssl1.0.0: Configure
   libssl1.0.0: Configure
   libssl-dev: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Jun  8 12:29:11 2017
  DuplicateSignature:
   package:libssl1.0.0:i386:1.0.2g-1ubuntu4.8
   Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu4.8) ...
   dpkg: error processing package libssl1.0.0:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-11-30 (190 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1696799/+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 1657243] Re: package openssl 1.0.2g-1ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package openssl 1.0.2g-1ubuntu4 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  I have recently installed ubuntu on my computer. I wanted to install 2
  upgrades and it crashed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Tue Jan 17 21:10:53 2017
  DuplicateSignature:
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package openssl (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-12-05 (42 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: openssl
  Title: package openssl 1.0.2g-1ubuntu4 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1657243/+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 1697335] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: el paquete libssl1.0.0:amd64 no está listo para configurarse no se puede configurar (estado a

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  el paquete libssl1.0.0:amd64 no está listo para configurarse  no se
  puede configurar (estado actual `half-installed')

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  Desconozco lo que sucede.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6
  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
  AptOrdering:
   linux-libc-dev: Install
   libssl1.0.0: Configure
   linux-libc-dev: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jun 11 20:22:48 2017
  ErrorMessage: el paquete libssl1.0.0:amd64 no está listo para configurarse  
no se puede configurar (estado actual `half-installed')
  InstallationDate: Installed on 2016-11-20 (203 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
el paquete libssl1.0.0:amd64 no está listo para configurarse  no se puede 
configurar (estado actual `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1697335/+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 1697016] Re: package libssl-doc 1.0.2g-1ubuntu4.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl-doc 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssl package in Ubuntu:
  New

Bug description:
  no sound in player

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl-doc 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   gstreamer1.0-libav: Install
   libssl-doc: Configure
   gstreamer1.0-libav: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jun  9 20:58:12 2017
  Dependencies:
   
  DuplicateSignature:
   package:libssl-doc:1.0.2g-1ubuntu4.6
   Unpacking gstreamer1.0-libav:amd64 (1.8.3-1ubuntu0.2) ...
   dpkg: error processing package libssl-doc (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-11-24 (197 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl-doc 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to xenial on 2017-05-02 (37 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1697016/+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 1696930] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 usr/lib/x86_64-linux-gnu/openssl-

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64
  -linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so] failed
  to install/upgrade: package libssl1.0.0:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by 
another process: Resource temporarily unavailable
  dpkg: error processing package libssl1.0.0:amd64 (--configure):
   package libssl1.0.0:amd64 is not ready for configuration
   cannot configure (current status 'half-installed')
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so]
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libssl1.0.0: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jun  9 12:29:49 2017
  DpkgTerminalLog:
   dpkg: error processing package libssl1.0.0:amd64 (--configure):
package libssl1.0.0:amd64 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package libssl1.0.0:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-05 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so] failed to 
install/upgrade: package libssl1.0.0:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1696930/+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 1697011] Re: package libssl-doc 1.0.2g-1ubuntu4.6 failed to install/upgrade: package libssl-doc is not ready for configuration cannot configure (current status 'half-installed')

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl-doc 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  package libssl-doc is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  I tried to update by the ubuntu software and the OS system update did
  not finished. I restarted the pc and ran the command: sudo apt-get -f
  install and showed the error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl-doc 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libssl-doc: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jun  9 12:11:10 2017
  Dependencies:
   
  DpkgTerminalLog:
   dpkg: error processing package libssl-doc (--configure):
package libssl-doc is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package libssl-doc is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-04 (36 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl-doc 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
package libssl-doc is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1697011/+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 1697838] Re: package libssl-doc 1.0.2g-1ubuntu4.8 failed to install/upgrade: package libssl-doc is not ready for configuration cannot configure (current status 'half-installed')

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl-doc 1.0.2g-1ubuntu4.8 failed to install/upgrade:
  package libssl-doc is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  My os dose not update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl-doc 1.0.2g-1ubuntu4.8
  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: Wed Jun 14 09:16:00 2017
  Dependencies:
   
  DuplicateSignature:
   package:libssl-doc:1.0.2g-1ubuntu4.8
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package libssl-doc (--configure):
package libssl-doc is not ready for configuration
  ErrorMessage: package libssl-doc is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-07-14 (334 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl-doc 1.0.2g-1ubuntu4.8 failed to install/upgrade: 
package libssl-doc is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1697838/+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 1697068] Re: package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvore

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakket
  verkeert in een heel slechte en inconsistente staat; u zou het
  opnieuw moeten installeren alvorens het te configureren.

Status in openssl package in Ubuntu:
  New

Bug description:
  Don't know.

  Fouten gevonden tijdens verwerken van:
   openssl
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun  9 20:51:04 2017
  ErrorMessage: pakket verkeert in een heel slechte en inconsistente staat; u 
zou het  opnieuw moeten installeren alvorens het te configureren.
  InstallationDate: Installed on 2016-01-24 (502 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package openssl 1.0.2g-1ubuntu4.8 failed to install/upgrade: pakket 
verkeert in een heel slechte en inconsistente staat; u zou het  opnieuw moeten 
installeren alvorens het te configureren.
  UpgradeStatus: Upgraded to xenial on 2017-01-07 (153 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1697068/+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 1697072] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu9.3 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu9.3 failed to install/upgrade:
  el subproceso instalado el script post-installation devolvió el código
  de salida de error 1

Status in openssl package in Ubuntu:
  New

Bug description:
  imposible via synaptic either

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu9.3
  Uname: Linux 4.9.10-040910-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  AptOrdering:
   libssl1.0.0:i386: Install
   libssl1.0.0:amd64: Install
   openssl:amd64: Install
   libpam-cgfs:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jun  9 14:10:49 2017
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu9.3 failed to install/upgrade: 
el subproceso instalado el script post-installation devolvió el código de 
salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1697072/+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 1697356] Re: package libssl-doc 1.0.2g-1ubuntu4.6 [modified: usr/share/doc/libssl-doc/changelog.Debian.gz] failed to install/upgrade: el paquete libssl-doc no está listo para con

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl-doc 1.0.2g-1ubuntu4.6 [modified: usr/share/doc/libssl-
  doc/changelog.Debian.gz] failed to install/upgrade: el paquete libssl-
  doc no está listo para configurarse  no se puede configurar (estado
  actual `half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  Cannot install last software update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl-doc 1.0.2g-1ubuntu4.6 [modified: 
usr/share/doc/libssl-doc/changelog.Debian.gz]
  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: Mon Jun 12 08:00:17 2017
  Dependencies:
   
  ErrorMessage: el paquete libssl-doc no está listo para configurarse  no se 
puede configurar (estado actual `half-installed')
  InstallationDate: Installed on 2017-02-20 (111 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl-doc 1.0.2g-1ubuntu4.6 [modified: 
usr/share/doc/libssl-doc/changelog.Debian.gz] failed to install/upgrade: el 
paquete libssl-doc no está listo para configurarse  no se puede configurar 
(estado actual `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1697356/+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 1697597] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: le paquet libssl1.0.0:i386 n'est pas prêt pour la configuration configuration impossible (état

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  le paquet libssl1.0.0:i386 n'est pas prêt pour la configuration
  configuration impossible (état actuel « half-installed »)

Status in openssl package in Ubuntu:
  New

Bug description:
  Le system indique une erreur mais je n'ai pas de code.
  De plus, j'ai pu utiliser le programme et les information que je cherchais 
était présente.

  Merci.

  Jean-Marie (baroul)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Tue Jun 13 08:10:29 2017
  ErrorMessage: le paquet libssl1.0.0:i386 n'est pas prêt pour la configuration 
 configuration impossible (état actuel « half-installed »)
  InstallationDate: Installed on 2017-05-23 (20 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
le paquet libssl1.0.0:i386 n'est pas prêt pour la configuration  configuration 
impossible (état actuel « half-installed »)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1697597/+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 1697911] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: package libssl1.0.0:amd64 cannot be configured because libssl1.0.0:i386 is not ready (current

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  package libssl1.0.0:amd64 cannot be configured because
  libssl1.0.0:i386 is not ready (current status 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  package libssl1.0.0:amd64 cannot be configured because
  libssl1.0.0:i386 is not ready (current status 'half-installed')

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6
  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: Wed Jun 14 13:06:50 2017
  DuplicateSignature:
   package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.6
   Installing from local file 
/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20170613.2.orig.tar.gz
   Flash Plugin installed.
   dpkg: error processing package libssl1.0.0:amd64 (--configure):
package libssl1.0.0:amd64 cannot be configured because libssl1.0.0:i386 is 
not ready (current status 'half-installed')
  ErrorMessage: package libssl1.0.0:amd64 cannot be configured because 
libssl1.0.0:i386 is not ready (current status 'half-installed')
  InstallationDate: Installed on 2017-01-07 (157 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
package libssl1.0.0:amd64 cannot be configured because libssl1.0.0:i386 is not 
ready (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1697911/+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 1696940] Re: package libssl-doc 1.0.2g-1ubuntu4.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl-doc 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  nill

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl-doc 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun  9 14:07:13 2017
  Dependencies:
   
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-13 (26 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl-doc 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1696940/+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 1697313] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: package libssl1.0.0:i386 is not ready for configuration cannot configure (current status 'half-

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  package libssl1.0.0:i386 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  I can't connect to a vpn site. i can't add a connection. I can't
  remove and reinstall vpn.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libssl1.0.0: Configure
   libssl1.0.0: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jun 11 17:15:16 2017
  DpkgTerminalLog:
   dpkg: error processing package libssl1.0.0:amd64 (--configure):
package libssl1.0.0:amd64 cannot be configured because libssl1.0.0:i386 is 
not ready (current status 'half-installed')
   dpkg: error processing package libssl1.0.0:i386 (--configure):
package libssl1.0.0:i386 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package libssl1.0.0:i386 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-11-01 (222 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
package libssl1.0.0:i386 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: Upgraded to xenial on 2016-11-01 (222 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1697313/+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 1696863] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: o pacote libssl1.0.0:i386 não está pronto para configuração não pode configurar (status actual

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  o pacote libssl1.0.0:i386 não está pronto para configuração  não pode
  configurar (status actual `half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  In the Ubuntu Software App it said there was one update. I asked to
  update and it stopped installation in the middle of the process.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libssl1.0.0: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Thu Jun  8 22:32:49 2017
  DpkgTerminalLog:
   dpkg: erro ao processar o pacote libssl1.0.0:i386 (--configure):
o pacote libssl1.0.0:i386 não está pronto para configuração
não pode configurar (status actual `half-installed')
  ErrorMessage: o pacote libssl1.0.0:i386 não está pronto para configuração  
não pode configurar (status actual `half-installed')
  InstallationDate: Installed on 2013-07-28 (1410 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
o pacote libssl1.0.0:i386 não está pronto para configuração  não pode 
configurar (status actual `half-installed')
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (311 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1696863/+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 1697280] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  le paquet est dans un état vraiment incohérent; vous devriez  le
  réinstaller avant de tenter de le configurer.

Status in openssl package in Ubuntu:
  New

Bug description:
  we are 2017-06-11
  working on HP probook 650g1 
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  from ubuntu sw I should be able to automatically install 2 updates, one for 
system one for other sw.
  after clicking on install(for both) button, scroll bar go to middle then stop.
  From sudo apt-get install , i got pop-up warning for errors ...

  help please...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libssl1.0.0: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Sun Jun 11 16:25:48 2017
  DpkgTerminalLog:
   dpkg: erreur de traitement du paquet libssl1.0.0:i386 (--configure) :
le paquet est dans un état vraiment incohérent; vous devriez
le réinstaller avant de tenter de le configurer.
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2016-08-20 (295 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
le paquet est dans un état vraiment incohérent; vous devriez  le réinstaller 
avant de tenter de le configurer.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1697280/+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 1697801] Re: package libssl-dev:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: package libssl-dev:amd64 is not ready for configuration cannot configure (current status 'half-

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl-dev:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade:
  package libssl-dev:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  This is part of the fail to update issue and came after attempting to
  run sudo apt-get upgrade

  alister@alister-HP-2000-Notebook-PC:~$ sudo apt-get update
  [sudo] password for alister: 
  Hit:1 http://au.archive.ubuntu.com/ubuntu xenial InRelease
 
  Get:2 http://au.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]   
 
  Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
 
  Ign:4 http://archive.canonical.com/ubuntu trusty InRelease
 
  Ign:5 http://ppa.launchpad.net/pmcenery/ppa/ubuntu xenial InRelease   
 
  Get:6 http://au.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 
[7,532 kB]
  Get:7 http://archive.canonical.com/ubuntu trusty Release [9,359 B]
 
  Ign:8 http://ppa.launchpad.net/pmcenery/ppa/ubuntu xenial Release 
 
  Get:9 http://archive.canonical.com/ubuntu trusty Release.gpg [933 B]  
 
  Ign:10 http://ppa.launchpad.net/pmcenery/ppa/ubuntu xenial/main amd64 
Packages 
  Ign:11 http://ppa.launchpad.net/pmcenery/ppa/ubuntu xenial/main i386 Packages 
 
  Get:12 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 
[284 kB]
  Get:13 http://archive.canonical.com/ubuntu trusty/partner Sources [10.1 kB]   
 
  Ign:14 http://ppa.launchpad.net/pmcenery/ppa/ubuntu xenial/main all Packages  
 
  Get:15 http://archive.canonical.com/ubuntu trusty/partner amd64 Packages 
[5,532 B]
  Get:16 http://archive.canonical.com/ubuntu trusty/partner i386 Packages 
[6,246 B]
  Ign:17 http://ppa.launchpad.net/pmcenery/ppa/ubuntu xenial/main 
Translation-en_AU
  Get:18 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 
[270 kB]
  Get:19 http://security.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 
Metadata [54.6 kB]
  Get:20 http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 
Icons [50.7 kB]
  Get:21 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages [132 kB]
  Ign:22 http://ppa.launchpad.net/pmcenery/ppa/ubuntu xenial/main 
Translation-en 
  Get:23 http://security.ubuntu.com/ubuntu xenial-security/universe i386 
Packages [118 kB]
  Get:24 http://security.ubuntu.com/ubuntu xenial-security/universe 
Translation-en [68.0 kB]
  Get:25 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
DEP-11 Metadata [35.7 kB]
  Get:26 http://security.ubuntu.com/ubuntu xenial-security/universe DEP-11 
64x64 Icons [52.2 kB]
  Get:27 http://security.ubuntu.com/ubuntu xenial-security/restricted amd64 
Packages [7,420 B]
  Get:28 http://security.ubuntu.com/ubuntu xenial-security/restricted i386 
Packages [7,420 B]
  Get:29 http://security.ubuntu.com/ubuntu xenial-security/restricted 
Translation-en [2,428 B]
  Ign:30 http://ppa.launchpad.net/pmcenery/ppa/ubuntu xenial/main amd64 DEP-11 
Metadata
  Get:31 http://security.ubuntu.com/ubuntu xenial-security/restricted amd64 
DEP-11 Metadata [200 B]
  Get:32 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 
Packages [2,748 B]
  Get:33 http://security.ubuntu.com/ubuntu xenial-security/multiverse i386 
Packages [2,908 B]
  Get:34 http://security.ubuntu.com/ubuntu xenial-security/multiverse 
Translation-en [1,232 B]
  Get:35 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 
DEP-11 Metadata [212 B]
  Get:36 http://security.ubuntu.com/ubuntu xenial-security/multiverse DEP-11 
64x64 Icons [29 B]
  Get:37 http://au.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 
[7,512 kB]
  Ign:38 http://ppa.launchpad.net/pmcenery/ppa/ubuntu xenial/main DEP-11 64x64 
Icons
  Ign:10 http://ppa.launchpad.net/pmcenery/ppa/ubuntu xenial/main amd64 
Packages 
  Ign:11 http://ppa.launchpad.net/pmcenery/ppa/ubuntu xenial/main i386 Packages 
 
  Ign:14 http://ppa.launchpad.net/pmcenery/ppa/ubuntu xenial/main all Packages  
 
  Ign:17 http://ppa.launchpad.net/pmcenery/ppa/ubuntu xenial/main 
Translation-en_AU
  Ign:22 http://ppa.launchpad.net/pmcenery/ppa/ubuntu xenial/main 
Translation-en 
  Ign:30 http://ppa.launchpad.net/pmcenery/ppa/ubuntu xenial/main amd64 DEP-11 
Metadata
  Get:39 http://au.archive.ubuntu.com/ubuntu xenial/universe Translation-en_AU 
[3,039 kB]
  Ign:38 

[Touch-packages] [Bug 1697099] Re: package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: package openssl is not ready for configuration cannot configure (current status 'half-installed')

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: package
  openssl is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  Software update fails to update.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   deja-dup-backend-gvfs: Install
   openssl: Configure
   deja-dup-backend-gvfs: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jun  9 15:22:04 2017
  DuplicateSignature:
   package:openssl:1.0.2g-1ubuntu4.6
   Unpacking deja-dup-backend-gvfs (34.2-0ubuntu1.1) over (34.2-0ubuntu1) ...
   dpkg: error processing package openssl (--configure):
package openssl is not ready for configuration
  ErrorMessage: package openssl is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package openssl 1.0.2g-1ubuntu4.6 failed to install/upgrade: package 
openssl is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1697099/+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 1697121] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: lib/i386-linux-gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0] failed to install/upgrade: package li

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: lib/i386-linux-
  gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0] failed to
  install/upgrade: package libssl1.0.0:i386 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  I am going to investigate w/ synaptic package manager and software.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: 
lib/i386-linux-gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0]
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libssl1.0.0: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Fri Jun  9 17:40:32 2017
  DpkgTerminalLog:
   dpkg: error processing package libssl1.0.0:i386 (--configure):
package libssl1.0.0:i386 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package libssl1.0.0:i386 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-27 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: 
lib/i386-linux-gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0] 
failed to install/upgrade: package libssl1.0.0:i386 is not ready for 
configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1697121/+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 1582767] Re: apparmor permissions missing for winbind

[Bug Watch Updater]

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

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

Title:
  apparmor permissions missing for winbind

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Won't Fix
Status in ntp package in Debian:
  Fix Released

Bug description:
  When using Winbind, ntpd needs to access the Winbind pipe:

  May 17 16:23:15 bo kernel: [   27.598551] type=1400
  audit(1463494995.048:18): apparmor="DENIED" operation="connect"
  profile="/usr/sbin/ntpd" name="/run/samba/winbindd/pipe" pid=1517
  comm="ntpd" requested_mask="rw" denied_mask="rw" fsuid=0 ouid=0

  Would there be any reason not to allow this ? I added the following
  line to /etc/apparmor/init/network-interface-security/usr.sbin.ntpd:

  /run/samba/winbindd/pipe rw,

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1582767/+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 1666980] Re: cannot install click, missing python files

[Launchpad Bug Tracker]

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

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

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

Title:
  cannot install click, missing python files

Status in click package in Ubuntu:
  Confirmed

Bug description:
  When I try to install click package, I get the following error:

  dpkg: click: dependency problems, but removing anyway as you requested:
   ubuntu-system-settings depends on click | ubuntu-snappy-cli; however:
Package click is to be removed.
Package ubuntu-snappy-cli is not installed.

  (Reading database ... 255714 files and directories currently installed.)
  Removing click (0.4.45.1+16.10.20160916-0ubuntu1) ...
  Traceback (most recent call last):
File "/usr/bin/click", line 37, in 
  import click
  ImportError: No module named 'click'
  dpkg: error processing package click (--remove):
   subprocess installed pre-removal script returned error exit status 1
  Job for click-system-hooks.service failed because the control process exited 
with error code.
  See "systemctl status click-system-hooks.service" and "journalctl -xe" for 
details.
  click-system-hooks.service couldn't start.
  Errors were encountered while processing:
   click

  Script /usr/bin/click tries to import python module click, but it is
  missing. I suppose that this module should be included in *.deb
  package, but I cannot find it there. It seems that source code of
  required module is located here: http://bazaar.launchpad.net/~ubuntu-
  branches/ubuntu/vivid/click/vivid/files/head:/click/ as it contains
  submodule "commands"

  Ubuntu 16.10
  click 0.4.45.1+16.10.20160916-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1666980/+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 1698958] Re: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in click package in Ubuntu:
  Confirmed

Bug description:
  I am unable to update Ubuntu through Software Updater, so I tried to
  update it manually.  I am using the LXDE environment, in order to save
  RAM, as it is lighter than Gnome.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: click 0.4.45.1+16.10.20160916-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  Date: Mon Jun 19 18:21:37 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-05-10 (40 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: click
  Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to zesty on 2017-05-10 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1698958/+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 1698958] Re: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: subprocess new pre-removal 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 click in Ubuntu.
https://bugs.launchpad.net/bugs/1698958

Title:
  package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in click package in Ubuntu:
  Confirmed

Bug description:
  I am unable to update Ubuntu through Software Updater, so I tried to
  update it manually.  I am using the LXDE environment, in order to save
  RAM, as it is lighter than Gnome.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: click 0.4.45.1+16.10.20160916-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  Date: Mon Jun 19 18:21:37 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-05-10 (40 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: click
  Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to zesty on 2017-05-10 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1698958/+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 1698958] [NEW] package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Christopher Kendalls]

Public bug reported:

I am unable to update Ubuntu through Software Updater, so I tried to
update it manually.  I am using the LXDE environment, in order to save
RAM, as it is lighter than Gnome.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: click 0.4.45.1+16.10.20160916-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: i386
Date: Mon Jun 19 18:21:37 2017
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2017-05-10 (40 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: click
Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
UpgradeStatus: Upgraded to zesty on 2017-05-10 (39 days ago)

** Affects: click (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: apport-package i386 zesty

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

Title:
  package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in click package in Ubuntu:
  Confirmed

Bug description:
  I am unable to update Ubuntu through Software Updater, so I tried to
  update it manually.  I am using the LXDE environment, in order to save
  RAM, as it is lighter than Gnome.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: click 0.4.45.1+16.10.20160916-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  Date: Mon Jun 19 18:21:37 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-05-10 (40 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: click
  Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to zesty on 2017-05-10 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1698958/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Launchpad Bug Tracker]

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

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

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+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 1681410] Re: fstrim corrupts ocfs2 filesystems when clustered

[jdh239]

Seeing the same thing with OCFS2 on Oracle VM Server 3.3.3.  Clustered
OCFS2, but on one device and only one node (Clustered when setup,
but then the cluster portion wasn't utilized due to licensing)

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

Title:
  fstrim corrupts ocfs2 filesystems when clustered

Status in util-linux package in Ubuntu:
  Expired

Bug description:
  Recently upgraded from trusty to xenial and found that our ocfs2
  filesystems, which are mounted across a number of nodes
  simultaneously, would become corrupt on the weekend:

  [Sun Apr  9 06:46:35 2017] OCFS2: ERROR (device dm-2): 
ocfs2_validate_gd_self: Group descriptor #516096 has bad signature 
  [Sun Apr  9 06:46:35 2017] On-disk corruption discovered. Please run 
fsck.ocfs2 once the filesystem is unmounted.
  [Sun Apr  9 06:46:35 2017] OCFS2: File system is now read-only.
  [Sun Apr  9 06:46:35 2017] (fstrim,1080,8):ocfs2_trim_fs:7399 ERROR: status = 
-30
  [Sun Apr  9 06:46:35 2017] OCFS2: ERROR (device dm-3): 
ocfs2_validate_gd_self: Group descriptor #516096 has bad signature 
  [Sun Apr  9 06:46:36 2017] On-disk corruption discovered. Please run 
fsck.ocfs2 once the filesystem is unmounted.
  [Sun Apr  9 06:46:36 2017] OCFS2: File system is now read-only.
  [Sun Apr  9 06:46:36 2017] (fstrim,1080,10):ocfs2_trim_fs:7399 ERROR: status 
= -30

  We found the cron.weekly job which is pretty close to the timing:
  47 6* * 7   roottest -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.weekly )

  # cat /etc/cron.weekly/fstrim 
  #!/bin/sh
  # trim all mounted file systems which support it
  /sbin/fstrim --all || true

  
  We have disabled this job across our servers running clustered ocfs2 
filesystems.  I think either the utility or the cronjob should ignore ocfs2 
(gfs too?) filesystems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1681410/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

[spm2011]

Also affects ALC3234 on Dell Latitude 3340
See https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1670059

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801/+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 1692127] Re: duplicate signature for Package problems can be too short

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/ubuntu/artful/apport/ubuntu

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

Title:
  duplicate signature for Package problems can be too short

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Yakkety:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Fix Released

Bug description:
  Steve brought up bug 1691983 and how it's duplicate signature is
  missing information.  It contains:

  package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  Installing for x86_64-efi platform.
  Installation finished. No error reported.
  Running in non-interactive mode, doing nothing.
  dpkg: error processing package shim-signed (--configure):
   subprocess installed post-installation script returned error exit status 1

  But is missing:

  Setting up shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
  locale: Cannot set LC_CTYPE to default locale: No such file or directory
  locale: Cannot set LC_MESSAGES to default locale: No such file or directory
  locale: Cannot set LC_ALL to default locale: No such file or directory
  debconf: unable to initialize frontend: Passthrough
  debconf: (Cannot connect to /tmp/aptdaemon-7jrqb_du/debconf.socket: 
Connection refused at (eval 18) line 3.)
  debconf: falling back to frontend: Noninteractive

  This is because of the following code in data/general-hooks/ubuntu.py:

  145 PKG_MSGS = ('Authenticating', 'De-configuring', 'Examining',
  146 'Installing ', 'Preparing', 'Processing 
triggers', 'Purging',
  147 'Removing', 'Replaced', 'Replacing', 'Setting up',
  148 'Unpacking', 'Would remove')
  149 for line in termlog.split('\n'):
  150 if line.startswith(PKG_MSGS):
  151 dupe_sig = '%s\n' % line
  152 continue

  The shim-signed package prints a line starts with "Installing " and
  that matches PKG_MSGS so we reset the dupe_sig because that's a
  message we'd expect from a package manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1692127/+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 1698638] Re: indicator-datetime list evolution calendar full-day event a day before actual date of event (Unity-7)

[Khurshid Alam]

> What Ubuntu release are you using?

This is reproducible on 16.04, 17.04 & 17.10

For 16.04 there was a patch which fixes the issue for me
(https://launchpadlibrarian.net/206123315/upcoming-after-end.patch) but
since then indicator-datetime code changed significantly and the patch
is not valid anymore.

What is the output of 'locale' specifically LC_TIME ?

LANG=en_IN
LANGUAGE=en_IN:en
LC_CTYPE="en_IN"
LC_NUMERIC="en_IN"
LC_TIME="en_IN"
LC_COLLATE="en_IN"
LC_MONETARY="en_IN"
LC_MESSAGES="en_IN"
LC_PAPER="en_IN"
LC_NAME="en_IN"
LC_ADDRESS="en_IN"
LC_TELEPHONE="en_IN"
LC_MEASUREMENT="en_IN"
LC_IDENTIFICATION="en_IN"
LC_ALL=

> Does the event show correctly in gnome-calendar and in evolution?

Yes.

** Description changed:

  Indicator-datetime lists events to take place one day ahead e.g. all day
  event on Monday is listed to be happen on Sunday
  
  Also this scenario also happens for today's date. Foe example;
  
  1. Create a full-day-event in any previous day (2nd june 2017)
  2. Click 2nd june on calendar
  3. Full-day event is listed there.
  
  But it doesn't work for today's date. (DTSTART == DTEND)
  
  1. Create a full-day-event on today.
- 2. Click 2nd june on calendar
+ 2. Click today on calendar
  3. Full-day event is NOT listed there.
  4. Click previous day.and you will find full-day event listed there
  5. It even shows today's date on side but just doesn't list the event on 
today's date.
  
  Note: This is reproducible for any event when DTSTART == DTEND (i.e
  Events from Google Calendar)

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

Title:
  indicator-datetime list evolution calendar full-day event a day before
  actual date of event (Unity-7)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Indicator-datetime lists events to take place one day ahead e.g. all
  day event on Monday is listed to be happen on Sunday

  Also this scenario also happens for today's date. Foe example;

  1. Create a full-day-event in any previous day (2nd june 2017)
  2. Click 2nd june on calendar
  3. Full-day event is listed there.

  But it doesn't work for today's date. (DTSTART == DTEND)

  1. Create a full-day-event on today.
  2. Click today on calendar
  3. Full-day event is NOT listed there.
  4. Click previous day.and you will find full-day event listed there
  5. It even shows today's date on side but just doesn't list the event on 
today's date.

  Note: This is reproducible for any event when DTSTART == DTEND (i.e
  Events from Google Calendar)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1698638/+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 1698638] Re: indicator-datetime list evolution calendar full-day event a day before actual date of event (Unity-7)

[Jeremy Bicha]

What Ubuntu release are you using?

What is the output of 'locale' specifically LC_TIME ?

Does the event show correctly in gnome-calendar and in evolution?

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

Title:
  indicator-datetime list evolution calendar full-day event a day before
  actual date of event (Unity-7)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Indicator-datetime lists events to take place one day ahead e.g. all
  day event on Monday is listed to be happen on Sunday

  Also this scenario also happens for today's date. Foe example;

  1. Create a full-day-event in any previous day (2nd june 2017)
  2. Click 2nd june on calendar
  3. Full-day event is listed there.

  But it doesn't work for today's date. (DTSTART == DTEND)

  1. Create a full-day-event on today.
  2. Click 2nd june on calendar
  3. Full-day event is NOT listed there.
  4. Click previous day.and you will find full-day event listed there
  5. It even shows today's date on side but just doesn't list the event on 
today's date.

  Note: This is reproducible for any event when DTSTART == DTEND (i.e
  Events from Google Calendar)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1698638/+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 1698638] Re: indicator-datetime list evolution calendar full-day event a day before actual date of event (Unity-7)

[Khurshid Alam]

** Description changed:

  Indicator-datetime lists events to take place one day ahead e.g. all day
  event on Monday is listed to be happen on Sunday
  
  Also this scenario also happens for today's date. Foe example;
  
  1. Create a full-day-event in any previous day (2nd june 2017)
  2. Click 2nd june on calendar
  3. Full-day event is listed there.
  
  But it doesn't work for today's date. (DTSTART == DTEND)
  
  1. Create a full-day-event on today.
  2. Click 2nd june on calendar
  3. Full-day event is NOT listed there.
  4. Click previous day.and you will find full-day event listed there
  5. It even shows today's date on side but just doesn't list the event on 
today's date.
  
- 
- Note: This is reproducible for any event when DTSTART == DTEND
+ Note: This is reproducible for any event when DTSTART == DTEND (i.e
+ Events from Google Calendar)

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

Title:
  indicator-datetime list evolution calendar full-day event a day before
  actual date of event (Unity-7)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Indicator-datetime lists events to take place one day ahead e.g. all
  day event on Monday is listed to be happen on Sunday

  Also this scenario also happens for today's date. Foe example;

  1. Create a full-day-event in any previous day (2nd june 2017)
  2. Click 2nd june on calendar
  3. Full-day event is listed there.

  But it doesn't work for today's date. (DTSTART == DTEND)

  1. Create a full-day-event on today.
  2. Click 2nd june on calendar
  3. Full-day event is NOT listed there.
  4. Click previous day.and you will find full-day event listed there
  5. It even shows today's date on side but just doesn't list the event on 
today's date.

  Note: This is reproducible for any event when DTSTART == DTEND (i.e
  Events from Google Calendar)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1698638/+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 1302004] Re: Indicator-datetime doesn't list in-progress events

[Khurshid Alam]

The bug occurs for any event when DTSTART == DTEND

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

Title:
  Indicator-datetime doesn't list in-progress events

Status in Canonical System Image:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  This bug is related to this bug: Bug #1293646 (Which is marked as fix
  released)

  With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
  lists all events for all past selected dates properly (which was fixed
  in bug Bug #1293646) except today's date. When I click on any past
  date in calendar it shows:

  1. all all-day events for the day.
  2. all events with time for the day
  3. upcoming (future) all-day events
  4. upcoming (future) events with time

  But when I click on today's date it only shows:

  1. future all day events
  2. future events with time

  I still have to click on previous day's date to find out all all-day
  events for today.

  The behavior (showing all events for a day) should be same for any
  date, including today's date.

  : "If there are more
  than five, the events shown should be, in order of priority, * any
  events that start or end (a) for today, after the current minute, or
  (b) for any other date, at any time on that date, * any full-day
  events that span all of the selected date..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1302004/+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 1698638] Re: indicator-datetime list evolution calendar full-day event a day before actual date of event (Unity-7)

[Khurshid Alam]

** Description changed:

  Indicator-datetime lists events to take place one day ahead e.g. all day
  event on Monday is listed to be happen on Sunday
- 
  
  Also this scenario also happens for today's date. Foe example;
  
  1. Create a full-day-event in any previous day (2nd june 2017)
  2. Click 2nd june on calendar
  3. Full-day event is listed there.
  
- But it doesn't work for today's date.
+ But it doesn't work for today's date. (DTSTART == DTEND)
  
  1. Create a full-day-event on today.
  2. Click 2nd june on calendar
  3. Full-day event is NOT listed there.
  4. Click previous day.and you will find full-day event listed there
  5. It even shows today's date on side but just doesn't list the event on 
today's date.
+ 
+ 
+ Note: This is reproducible for any event when DTSTART == DTEND

** Tags added: artful

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

Title:
  indicator-datetime list evolution calendar full-day event a day before
  actual date of event (Unity-7)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Indicator-datetime lists events to take place one day ahead e.g. all
  day event on Monday is listed to be happen on Sunday

  Also this scenario also happens for today's date. Foe example;

  1. Create a full-day-event in any previous day (2nd june 2017)
  2. Click 2nd june on calendar
  3. Full-day event is listed there.

  But it doesn't work for today's date. (DTSTART == DTEND)

  1. Create a full-day-event on today.
  2. Click 2nd june on calendar
  3. Full-day event is NOT listed there.
  4. Click previous day.and you will find full-day event listed there
  5. It even shows today's date on side but just doesn't list the event on 
today's date.

  Note: This is reproducible for any event when DTSTART == DTEND (i.e
  Events from Google Calendar)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1698638/+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 1531184] Re: dnsmasq doesn't start on boot because its interface isn't up yet

[David Britton]

Submitted patch upstream, will revisit in a couple weeks before taking
on an extra deviation in Ubuntu (since currently we do not have any
delta).

** Changed in: hundredpapercuts
 Assignee: David Britton (davidpbritton) => (unassigned)

** Changed in: dnsmasq (Ubuntu)
 Assignee: David Britton (davidpbritton) => (unassigned)

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

Title:
  dnsmasq doesn't start on boot because its interface isn't up yet

Status in One Hundred Papercuts:
  In Progress
Status in dnsmasq package in Ubuntu:
  In Progress
Status in dnsmasq package in Debian:
  Unknown

Bug description:
  My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0
  is managed manually in /etc/network/interfaces.

  During boot, dnsmasq is started before br-vz0 is created and this
  causes dnsmasq to exit:

  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0
  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0
  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up
  Jan  5 08:56:17 simon-laptop NetworkManager[937]:   NetworkManager 
(version 1.0.4) is starting...
  ...
  Jan  5 08:56:18 simon-laptop NetworkManager[937]: 
interface-parser: parsing file /etc/network/interfaces
  ...
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   found bridge ports 
none for br-vz0
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   adding bridge port 
none to eni_ifaces
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   management mode: 
unmanaged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq 2.75-1
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan  5 09:53:30 2016
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+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 736349] Re: "Test speakers" is silent

[Lucio]

For me, installing libcanberra-pulse worked.

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

Title:
  "Test speakers" is silent

Status in OEM Priority Project:
  Fix Released
Status in gnome-media package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntu-sounds package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-media

  My speakers are working fine (I can year playback with Banshee and
  VLC), but "Test speakers" is silent. I hear nothing when I press on
  the "Test" button.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-media 2.32.0-0ubuntu5
  Uname: Linux 2.6.38-020638-generic x86_64
  Architecture: amd64
  Date: Wed Mar 16 20:30:19 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100921.1)
  ProcEnviron:
   LANGUAGE=de_DE:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-media
  UpgradeStatus: Upgraded to natty on 2011-03-11 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/736349/+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 1531184] Re: dnsmasq doesn't start on boot because its interface isn't up yet

[David Britton]

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

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

Title:
  dnsmasq doesn't start on boot because its interface isn't up yet

Status in One Hundred Papercuts:
  In Progress
Status in dnsmasq package in Ubuntu:
  In Progress
Status in dnsmasq package in Debian:
  Unknown

Bug description:
  My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0
  is managed manually in /etc/network/interfaces.

  During boot, dnsmasq is started before br-vz0 is created and this
  causes dnsmasq to exit:

  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0
  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0
  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up
  Jan  5 08:56:17 simon-laptop NetworkManager[937]:   NetworkManager 
(version 1.0.4) is starting...
  ...
  Jan  5 08:56:18 simon-laptop NetworkManager[937]: 
interface-parser: parsing file /etc/network/interfaces
  ...
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   found bridge ports 
none for br-vz0
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   adding bridge port 
none to eni_ifaces
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   management mode: 
unmanaged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq 2.75-1
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan  5 09:53:30 2016
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[J. Scott Farrow]

I gave up and spent $80 on new headphones that seem to work. GhostTek
SoDrop2s, if anyone wants to know. Working for me on 17.04 Zesty.

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+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 1376329] Re: readarray doesn't work with pipes

[xhienne]

This is not a bug but the expected behavior.

Due to the use of a pipe, "readarray blah" is executed in a sub-shell.
But "echo ${blah[@]}" is executed in the parent shell. This has nothing
to do with readarray, the command ": | blah=blah; echo $blah" would also
fail to output blah.

On the other hand, this will work because both readarray and echo execute in 
the same subshell:
$ cat /tmp/foo | ( readarray blah; echo "${blah[@]}" )

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

Title:
  readarray doesn't work with pipes

Status in bash package in Ubuntu:
  New

Bug description:
  (echo one 1 ; echo two 2 ; echo three 3) > /tmp/foo

  #works
  readarray blah < /tmp/foo
  echo "${blah[@]}"

  # doesn't work:
  unset blah
  cat /tmp/foo | readarray blah
  echo "${blah[@]}"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1376329/+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 1381567] Re: Bash returns unexpected character \001 on string operation

[xhienne]

Affects xenial too. There is definitely something wrong.

Several notes on this:

1. A direct call to "echo ${f[@]:0:1}" outputs "a". The problems thus
lies in the variable assignment.

2. If first_char=${f[@]:0:1}, then echo "$first_char" outputs \001 but
"declare -p first_char" outputs \001\001

3. Double-quoted first_char="${f[@]:0:1}" puts "a" in first_char like in
Precise

4. first_char=${f[*]:0:1} has the same behaviour

5. Anyway, proper syntax should be first_char=${f:0:1} since you
consider f as a string. If you want to force bash to consider f as an
array (with the ${f[@]} syntax), then first_char=${f[@]:0:1} should put
f[0] in first_char, that is "abcd", not "a". So IMHO both Precise and
Trusty results are wrong.

** Tags added: xenial

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

Title:
  Bash returns unexpected character \001 on string operation

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  There has been some change between Precise and Trusty that lets this code 
snippet behave differently:
  

  Precise:
  $ unset f ; f=abcd ; first_char=${f[@]:0:1} ; echo $first_char
  a

  Trusty
  $ unset f ; f=abcd ; first_char=${f[@]:0:1} ; echo $first_char
  \001

  
  The solution is to use ${f:0:1} but nevertheless the result on Trusty seems 
completely wrong. Where does the \001 even come from?!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1381567/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[Ricardo Rodrigues]

More than a year and this bug is not yet fixed?

Is it a huge problem to solve?

Can I help with some log files or something like that?

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+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 1606078] Re: No sound with Ubuntu 16.04

[César Biosca .]

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

Very same issue on an Asus E202SA.

After watching a movie pulseaudio stoped working at the next reboot. Now
I must use ALSA, but cannot use headphones o connect to HDI and listen
only with the netbook's sound. It is very annoying and disturbing.

At best I get this (took a screenshot). Before I got a notice saying
that could not connect to the pulseaoudio server...

** Attachment added: "Connecting to pulseaudio, and it takes forever..."
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1606078/+attachment/4898628/+files/pulseaudio-connecting.png

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

Title:
  No sound with Ubuntu 16.04

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Ubuntu 16.04.1 on an LG S1 Express Dual
  laptop there was no sound from the speakers unless external speakers
  where hooked to the headphones socket. This applies to the Ubuntu
  Mate, Xubuntu and Lubuntu variants. This laptop was working fine for
  all previous releases up to 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bashar 3263 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 25 01:51:19 2016
  InstallationDate: Installed on 2016-07-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bashar 3263 F pulseaudio
  Symptom_Jack: Line Out, Internal
  Symptom_Type: No sound at all
  Title: [S1-M401E1, Realtek ALC880, Line Out, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: RKYWSF0B
  dmi.board.name: ROCKY
  dmi.board.vendor: LG Electronics
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF0B:bd02/16/2006:svnLGElectronics:pnS1-M401E1:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A:
  dmi.product.name: S1-M401E1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: LG Electronics

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1606078/+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 1394136] Re: if statement with pipe to grep randomly fails if pipefail is set

[xhienne]

This is not a bug, although some might disagree with the current
behavior of bash.

With a command like 'yes | grep -q .', because the grep terminates early
and the yes is writing past the end of the pipe buffer, the yes process
is _always_ terminated with a SIGPIPE signal (which translates to a
return value of 141). Combined with the pipefail option, the whole
command is considered to have failed.

pipefail should be used scarcely, that's why it is not enabled by
default.

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

Title:
  if statement with pipe to grep randomly fails if pipefail is set

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  The following bash script will fail randomly on trusty but when tested
  on saucy it worked all the time. On the system we test we have kvm
  installed and the if statement should evaluate to false and we should
  see ten PASS lines and no Error. And this should happen all the time.

  ==
  #!/bin/bash 

  set -eu
  set -o pipefail

  if ! lsmod | grep -q -e ^kvm_intel -e ^kvm_amd ; then
  echo 'Error: check that virtualisation is enabled in your BIOS'
  else
  echo "PASS"
  fi
  ===

  As can be seen if I run it 10 times I get 2 PASS and 8 failures

  ===
  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ for i in $(seq 0 9) ; do bash 
test-simple.bash ; done
  PASS
  PASS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  Error: check that virtualisation is enabled in your BIOS
  ===

  Now if I turn off the pipefail then the script passes all the time and
  just prints out 10 PASS lines.

  The script uses bash, grep and lsmod and I have the following versions
  on trusty of them

  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ dpkg -l | grep bash
  ii  bash  4.3-7ubuntu1.5  
amd64GNU Bourne Again SHell
  ii  bash-completion   1:2.1-4 
all  programmable completion for the 
bash shell
  ii  command-not-found 0.3ubuntu12 
all  Suggest installation of packages 
in interactive bash sessions
  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ dpkg -l | grep grep
  ii  grep  2.16-1  
amd64GNU grep, egrep and fgrep
  kerrin@kerrin-HP-Z620-Workstation:~/ce_build$ dpkg -l | grep kmod
  ii  kmod  15-0ubuntu6 
amd64tools for managing Linux kernel 
modules
  ii  libkmod2:amd6415-0ubuntu6 
amd64libkmod shared library
  ii  module-init-tools 15-0ubuntu6 
all  transitional dummy package 
(module-init-tools to kmod)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1394136/+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 1698880] [NEW] Horizontal line flickering

[Malte Koch]

Public bug reported:

When i'm scrolling or watching a video there is a horizontal line
flickering in the middle of the screen. It doesnt matter if i use an
external monitor or the monitor of my laptop.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-77.98-lowlatency 4.4.59
Uname: Linux 4.4.0-77-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Mon Jun 19 18:08:04 2017
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages 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/1698880

Title:
  Horizontal line flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  When i'm scrolling or watching a video there is a horizontal line
  flickering in the middle of the screen. It doesnt matter if i use an
  external monitor or the monitor of my laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-77.98-lowlatency 4.4.59
  Uname: Linux 4.4.0-77-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Mon Jun 19 18:08:04 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1698880/+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 1693226] Re: Break the conflicts with click the optparser

[Launchpad Bug Tracker]

This bug was fixed in the package click -
0.4.46+17.04.20170607.3-0ubuntu1

---
click (0.4.46+17.04.20170607.3-0ubuntu1) zesty; urgency=medium

  * Rename the python package this installs from click to click_package.
(LP: #1693226)
  * Use the correct overlayfs module name for the chroot configuration.
(LP: #1696402)

 -- Sergio Schvezov   Wed, 07 Jun 2017
18:53:16 +

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

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

Title:
  Break the conflicts with click the optparser

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Xenial:
  Fix Released
Status in click source package in Yakkety:
  Fix Released
Status in click source package in Zesty:
  Fix Released
Status in click source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * python-click and python-click-package conflict as they use the same
 python package for its implementation.

   * Since python-click-package is an implementation detail for the click 
 package and python3-click is a package meant to be used in other
 implementations it makes sense to break the conflict by moving the
 package name for python-click-package to a different name

   * snapcraft has moved from docopt to python3-click, users that have click
 installed don't have an upgrade path.his bug.

  [Test Case]

   * Where snapcraft 2.30 is present:
 
 - apt install click
 - Install snapcraft << 2.30
 - update to snapcraft >= 2.30
 - the upgrade should not be held on any package.
 - click and snapcraft commands should work.

  * Install python3-click and click should be possible. The click command
should keep working and python3 -c 'from click import group' shall work.

  
  [Regression Potential] 

   * Users depending on click from python-click-package will be importing an
 unexpected click in any scripts they may have.

  [Other Info]
   
   * While unfortunate, click as a technology is deprecated and not used
 anymore. This resolution path was discussed with slangasek and apw prior
 to any work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+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 1693226] Re: Break the conflicts with click the optparser

[Launchpad Bug Tracker]

This bug was fixed in the package click -
0.4.46+16.10.20170607.3-0ubuntu1

---
click (0.4.46+16.10.20170607.3-0ubuntu1) yakkety; urgency=medium

  * Rename the python package this installs from click to click_package.
(LP: #1693226)
  * Use the correct overlayfs module name for the chroot configuration.
(LP: #1696402)

 -- Sergio Schvezov   Wed, 07 Jun 2017
18:53:16 +

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

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

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

Title:
  Break the conflicts with click the optparser

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Xenial:
  Fix Released
Status in click source package in Yakkety:
  Fix Released
Status in click source package in Zesty:
  Fix Released
Status in click source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * python-click and python-click-package conflict as they use the same
 python package for its implementation.

   * Since python-click-package is an implementation detail for the click 
 package and python3-click is a package meant to be used in other
 implementations it makes sense to break the conflict by moving the
 package name for python-click-package to a different name

   * snapcraft has moved from docopt to python3-click, users that have click
 installed don't have an upgrade path.his bug.

  [Test Case]

   * Where snapcraft 2.30 is present:
 
 - apt install click
 - Install snapcraft << 2.30
 - update to snapcraft >= 2.30
 - the upgrade should not be held on any package.
 - click and snapcraft commands should work.

  * Install python3-click and click should be possible. The click command
should keep working and python3 -c 'from click import group' shall work.

  
  [Regression Potential] 

   * Users depending on click from python-click-package will be importing an
 unexpected click in any scripts they may have.

  [Other Info]
   
   * While unfortunate, click as a technology is deprecated and not used
 anymore. This resolution path was discussed with slangasek and apw prior
 to any work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+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 1693226] Re: Break the conflicts with click the optparser

[Launchpad Bug Tracker]

This bug was fixed in the package click - 0.4.43+16.04.20170613-0ubuntu1

---
click (0.4.43+16.04.20170613-0ubuntu1) xenial; urgency=medium

  * Rename the python package this installs from click to click_package.
(LP: #1693226)

 -- Kyle Fazzari   Tue, 13 Jun 2017 17:14:46 +

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

Title:
  Break the conflicts with click the optparser

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Xenial:
  Fix Released
Status in click source package in Yakkety:
  Fix Released
Status in click source package in Zesty:
  Fix Released
Status in click source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * python-click and python-click-package conflict as they use the same
 python package for its implementation.

   * Since python-click-package is an implementation detail for the click 
 package and python3-click is a package meant to be used in other
 implementations it makes sense to break the conflict by moving the
 package name for python-click-package to a different name

   * snapcraft has moved from docopt to python3-click, users that have click
 installed don't have an upgrade path.his bug.

  [Test Case]

   * Where snapcraft 2.30 is present:
 
 - apt install click
 - Install snapcraft << 2.30
 - update to snapcraft >= 2.30
 - the upgrade should not be held on any package.
 - click and snapcraft commands should work.

  * Install python3-click and click should be possible. The click command
should keep working and python3 -c 'from click import group' shall work.

  
  [Regression Potential] 

   * Users depending on click from python-click-package will be importing an
 unexpected click in any scripts they may have.

  [Other Info]
   
   * While unfortunate, click as a technology is deprecated and not used
 anymore. This resolution path was discussed with slangasek and apw prior
 to any work.

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

[Łukasz Zemczak]

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

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

Title:
  Break the conflicts with click the optparser

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Xenial:
  Fix Released
Status in click source package in Yakkety:
  Fix Released
Status in click source package in Zesty:
  Fix Released
Status in click source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * python-click and python-click-package conflict as they use the same
 python package for its implementation.

   * Since python-click-package is an implementation detail for the click 
 package and python3-click is a package meant to be used in other
 implementations it makes sense to break the conflict by moving the
 package name for python-click-package to a different name

   * snapcraft has moved from docopt to python3-click, users that have click
 installed don't have an upgrade path.his bug.

  [Test Case]

   * Where snapcraft 2.30 is present:
 
 - apt install click
 - Install snapcraft << 2.30
 - update to snapcraft >= 2.30
 - the upgrade should not be held on any package.
 - click and snapcraft commands should work.

  * Install python3-click and click should be possible. The click command
should keep working and python3 -c 'from click import group' shall work.

  
  [Regression Potential] 

   * Users depending on click from python-click-package will be importing an
 unexpected click in any scripts they may have.

  [Other Info]
   
   * While unfortunate, click as a technology is deprecated and not used
 anymore. This resolution path was discussed with slangasek and apw prior
 to any work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+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 1696402] Re: chroot configuration strictly depends on overlayfs

[Launchpad Bug Tracker]

This bug was fixed in the package click -
0.4.46+16.10.20170607.3-0ubuntu1

---
click (0.4.46+16.10.20170607.3-0ubuntu1) yakkety; urgency=medium

  * Rename the python package this installs from click to click_package.
(LP: #1693226)
  * Use the correct overlayfs module name for the chroot configuration.
(LP: #1696402)

 -- Sergio Schvezov   Wed, 07 Jun 2017
18:53:16 +

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

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

Title:
  chroot configuration strictly depends on overlayfs

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Yakkety:
  Fix Released
Status in click source package in Zesty:
  Fix Released

Bug description:
  The kernel changed the module name from overlayfs to overlay, this
  needs to be taken into consideration when creating the chroot.

  [Impact]

  When trying to create the chroot, it fails like this:
  Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
  E: 10mount: mount: wrong fs type, bad option, bad superblock on 
click-ubuntu-sdk-14.04-armhf,
  E: 10mount:missing codepage or helper program, or other error
  E: 10mount:
  E: 10mount:In some cases useful info is found in syslog - try
  E: 10mount:dmesg | tail or so.
  E: click-ubuntu-sdk-14.04-armhf-06293574-400d-48f5-8eb2-b74b8af77b72: Chroot 
setup failed: stage=setup-start
  Command returned 1: schroot -c click-ubuntu-sdk-14.04-armhf -- env 
DEB_HOST_ARCH_BITS=32 DEB_BUILD_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little 
DEB_BUILD_ARCH_ABI
  =base DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_LIBC=gnu 
DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_OS=linux 
DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_TARG
  ET_ARCH_OS=linux DEB_HOST_ARCH_LIBC=gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu 
DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_SYSTEM=linux-gnueabihf 
DEB_BUILD_ARCH_BITS=
  64 DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_GNU_CPU=x86_64 
DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH=armhf DEB_BUILD_ARCH_LIBC=gnu 
DEB_TARGET_GNU_TYPE=arm-linux-gn
  ueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_CPU=arm 
DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_CPU=arm 
DEB_TARGET_ARCH_CPU=arm DEB_B
  UILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf 
DEB_TARGET_ARCH_ABI=eabihf DEB_TARGET_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little 
DEB_HOST_ARCH
  _CPU=arm DEB_BUILD_ARCH_CPU=amd64 cmake .. -DCLICK_MODE=on -DINSTALL_TESTS=off
  ERROR

  This makes the autopkgtests fail, so it's blocking bug #1693226.

  [Test Case]

  Run the click autopkgtests.
  Check that there are no errors related to the wrong fs type.

  [Regression Potential]

  Fixing this for artful could make it fail in previous versions.
  However, this was found by the autopkgtests, so as long as the chroot tests 
pass in the other revisions the fix is correct.

  [Other Info]

  Click is now longer in active development. These tests were failing
  for a long time. In here we are just trying to make a small change on
  the name of the python module so it doesn't conflict with
  python3-click which is in active development and needed by snapcraft
  in bug #1692102.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1696402/+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 1696402] Re: chroot configuration strictly depends on overlayfs

[Leo Arias]

Thanks Lukasz.

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

Title:
  chroot configuration strictly depends on overlayfs

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Yakkety:
  Fix Released
Status in click source package in Zesty:
  Fix Released

Bug description:
  The kernel changed the module name from overlayfs to overlay, this
  needs to be taken into consideration when creating the chroot.

  [Impact]

  When trying to create the chroot, it fails like this:
  Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
  E: 10mount: mount: wrong fs type, bad option, bad superblock on 
click-ubuntu-sdk-14.04-armhf,
  E: 10mount:missing codepage or helper program, or other error
  E: 10mount:
  E: 10mount:In some cases useful info is found in syslog - try
  E: 10mount:dmesg | tail or so.
  E: click-ubuntu-sdk-14.04-armhf-06293574-400d-48f5-8eb2-b74b8af77b72: Chroot 
setup failed: stage=setup-start
  Command returned 1: schroot -c click-ubuntu-sdk-14.04-armhf -- env 
DEB_HOST_ARCH_BITS=32 DEB_BUILD_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little 
DEB_BUILD_ARCH_ABI
  =base DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_LIBC=gnu 
DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_OS=linux 
DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_TARG
  ET_ARCH_OS=linux DEB_HOST_ARCH_LIBC=gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu 
DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_SYSTEM=linux-gnueabihf 
DEB_BUILD_ARCH_BITS=
  64 DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_GNU_CPU=x86_64 
DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH=armhf DEB_BUILD_ARCH_LIBC=gnu 
DEB_TARGET_GNU_TYPE=arm-linux-gn
  ueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_CPU=arm 
DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_CPU=arm 
DEB_TARGET_ARCH_CPU=arm DEB_B
  UILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf 
DEB_TARGET_ARCH_ABI=eabihf DEB_TARGET_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little 
DEB_HOST_ARCH
  _CPU=arm DEB_BUILD_ARCH_CPU=amd64 cmake .. -DCLICK_MODE=on -DINSTALL_TESTS=off
  ERROR

  This makes the autopkgtests fail, so it's blocking bug #1693226.

  [Test Case]

  Run the click autopkgtests.
  Check that there are no errors related to the wrong fs type.

  [Regression Potential]

  Fixing this for artful could make it fail in previous versions.
  However, this was found by the autopkgtests, so as long as the chroot tests 
pass in the other revisions the fix is correct.

  [Other Info]

  Click is now longer in active development. These tests were failing
  for a long time. In here we are just trying to make a small change on
  the name of the python module so it doesn't conflict with
  python3-click which is in active development and needed by snapcraft
  in bug #1692102.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1696402/+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 1698670] DuplicateSignature.txt

[Brian Murray]

Due to a bug in apport's method for creating a duplicate signature, the
DuplicateSignature in this report was incorrect. We are fixing that now,
sorry for the noise!

** Attachment added: "DuplicateSignature.txt"
   
https://bugs.launchpad.net/bugs/1698670/+attachment/4898611/+files/DuplicateSignature.txt

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: lib/i386-linux-
  gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0 usr/lib/i386
  -linux-gnu/openssl-1.0.0/engines/lib4758cca.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libaep.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libatalla.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libcapi.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libchil.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libcswift.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libgmp.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libgost.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libnuron.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libpadlock.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libsureware.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libubsec.so
  usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to
  install/upgrade: el paquete libssl1.0.0:i386 no está listo para
  configurarse  no se puede configurar (estado actual `half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  please

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: 
lib/i386-linux-gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun Jun 18 11:19:46 2017
  ErrorMessage: el paquete libssl1.0.0:i386 no está listo para configurarse  no 
se puede configurar (estado actual `half-installed')
  InstallationDate: Installed on 2017-05-05 (44 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1698670/+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 1696402] Re: chroot configuration strictly depends on overlayfs

[Launchpad Bug Tracker]

This bug was fixed in the package click -
0.4.46+17.04.20170607.3-0ubuntu1

---
click (0.4.46+17.04.20170607.3-0ubuntu1) zesty; urgency=medium

  * Rename the python package this installs from click to click_package.
(LP: #1693226)
  * Use the correct overlayfs module name for the chroot configuration.
(LP: #1696402)

 -- Sergio Schvezov   Wed, 07 Jun 2017
18:53:16 +

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

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

Title:
  chroot configuration strictly depends on overlayfs

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Yakkety:
  Fix Released
Status in click source package in Zesty:
  Fix Released

Bug description:
  The kernel changed the module name from overlayfs to overlay, this
  needs to be taken into consideration when creating the chroot.

  [Impact]

  When trying to create the chroot, it fails like this:
  Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
  E: 10mount: mount: wrong fs type, bad option, bad superblock on 
click-ubuntu-sdk-14.04-armhf,
  E: 10mount:missing codepage or helper program, or other error
  E: 10mount:
  E: 10mount:In some cases useful info is found in syslog - try
  E: 10mount:dmesg | tail or so.
  E: click-ubuntu-sdk-14.04-armhf-06293574-400d-48f5-8eb2-b74b8af77b72: Chroot 
setup failed: stage=setup-start
  Command returned 1: schroot -c click-ubuntu-sdk-14.04-armhf -- env 
DEB_HOST_ARCH_BITS=32 DEB_BUILD_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little 
DEB_BUILD_ARCH_ABI
  =base DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_LIBC=gnu 
DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_OS=linux 
DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_TARG
  ET_ARCH_OS=linux DEB_HOST_ARCH_LIBC=gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu 
DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_SYSTEM=linux-gnueabihf 
DEB_BUILD_ARCH_BITS=
  64 DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_GNU_CPU=x86_64 
DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH=armhf DEB_BUILD_ARCH_LIBC=gnu 
DEB_TARGET_GNU_TYPE=arm-linux-gn
  ueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_CPU=arm 
DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_CPU=arm 
DEB_TARGET_ARCH_CPU=arm DEB_B
  UILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf 
DEB_TARGET_ARCH_ABI=eabihf DEB_TARGET_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little 
DEB_HOST_ARCH
  _CPU=arm DEB_BUILD_ARCH_CPU=amd64 cmake .. -DCLICK_MODE=on -DINSTALL_TESTS=off
  ERROR

  This makes the autopkgtests fail, so it's blocking bug #1693226.

  [Test Case]

  Run the click autopkgtests.
  Check that there are no errors related to the wrong fs type.

  [Regression Potential]

  Fixing this for artful could make it fail in previous versions.
  However, this was found by the autopkgtests, so as long as the chroot tests 
pass in the other revisions the fix is correct.

  [Other Info]

  Click is now longer in active development. These tests were failing
  for a long time. In here we are just trying to make a small change on
  the name of the python module so it doesn't conflict with
  python3-click which is in active development and needed by snapcraft
  in bug #1692102.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1696402/+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 1696402] Re: chroot configuration strictly depends on overlayfs

[Łukasz Zemczak]

Autopkgtests in -proposed passed for both series, considering this as
verified.

** Tags removed: verification-needed
** Tags added: verification-done-yakkety verification-done-zesty

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

Title:
  chroot configuration strictly depends on overlayfs

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Yakkety:
  Fix Released
Status in click source package in Zesty:
  Fix Released

Bug description:
  The kernel changed the module name from overlayfs to overlay, this
  needs to be taken into consideration when creating the chroot.

  [Impact]

  When trying to create the chroot, it fails like this:
  Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
  E: 10mount: mount: wrong fs type, bad option, bad superblock on 
click-ubuntu-sdk-14.04-armhf,
  E: 10mount:missing codepage or helper program, or other error
  E: 10mount:
  E: 10mount:In some cases useful info is found in syslog - try
  E: 10mount:dmesg | tail or so.
  E: click-ubuntu-sdk-14.04-armhf-06293574-400d-48f5-8eb2-b74b8af77b72: Chroot 
setup failed: stage=setup-start
  Command returned 1: schroot -c click-ubuntu-sdk-14.04-armhf -- env 
DEB_HOST_ARCH_BITS=32 DEB_BUILD_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little 
DEB_BUILD_ARCH_ABI
  =base DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_LIBC=gnu 
DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_OS=linux 
DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_TARG
  ET_ARCH_OS=linux DEB_HOST_ARCH_LIBC=gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu 
DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_SYSTEM=linux-gnueabihf 
DEB_BUILD_ARCH_BITS=
  64 DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_GNU_CPU=x86_64 
DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH=armhf DEB_BUILD_ARCH_LIBC=gnu 
DEB_TARGET_GNU_TYPE=arm-linux-gn
  ueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_CPU=arm 
DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_CPU=arm 
DEB_TARGET_ARCH_CPU=arm DEB_B
  UILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf 
DEB_TARGET_ARCH_ABI=eabihf DEB_TARGET_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little 
DEB_HOST_ARCH
  _CPU=arm DEB_BUILD_ARCH_CPU=amd64 cmake .. -DCLICK_MODE=on -DINSTALL_TESTS=off
  ERROR

  This makes the autopkgtests fail, so it's blocking bug #1693226.

  [Test Case]

  Run the click autopkgtests.
  Check that there are no errors related to the wrong fs type.

  [Regression Potential]

  Fixing this for artful could make it fail in previous versions.
  However, this was found by the autopkgtests, so as long as the chroot tests 
pass in the other revisions the fix is correct.

  [Other Info]

  Click is now longer in active development. These tests were failing
  for a long time. In here we are just trying to make a small change on
  the name of the python module so it doesn't conflict with
  python3-click which is in active development and needed by snapcraft
  in bug #1692102.

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

[Łukasz Zemczak]

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

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

Title:
  chroot configuration strictly depends on overlayfs

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Yakkety:
  Fix Released
Status in click source package in Zesty:
  Fix Released

Bug description:
  The kernel changed the module name from overlayfs to overlay, this
  needs to be taken into consideration when creating the chroot.

  [Impact]

  When trying to create the chroot, it fails like this:
  Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
  E: 10mount: mount: wrong fs type, bad option, bad superblock on 
click-ubuntu-sdk-14.04-armhf,
  E: 10mount:missing codepage or helper program, or other error
  E: 10mount:
  E: 10mount:In some cases useful info is found in syslog - try
  E: 10mount:dmesg | tail or so.
  E: click-ubuntu-sdk-14.04-armhf-06293574-400d-48f5-8eb2-b74b8af77b72: Chroot 
setup failed: stage=setup-start
  Command returned 1: schroot -c click-ubuntu-sdk-14.04-armhf -- env 
DEB_HOST_ARCH_BITS=32 DEB_BUILD_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little 
DEB_BUILD_ARCH_ABI
  =base DEB_TARGET_ARCH_BITS=32 DEB_TARGET_ARCH_LIBC=gnu 
DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_OS=linux 
DEB_TARGET_MULTIARCH=arm-linux-gnueabihf DEB_TARG
  ET_ARCH_OS=linux DEB_HOST_ARCH_LIBC=gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu 
DEB_BUILD_ARCH_OS=linux DEB_TARGET_GNU_SYSTEM=linux-gnueabihf 
DEB_BUILD_ARCH_BITS=
  64 DEB_HOST_ARCH_ABI=eabihf DEB_BUILD_GNU_CPU=x86_64 
DEB_BUILD_ARCH_ENDIAN=little DEB_HOST_ARCH=armhf DEB_BUILD_ARCH_LIBC=gnu 
DEB_TARGET_GNU_TYPE=arm-linux-gn
  ueabihf DEB_HOST_MULTIARCH=arm-linux-gnueabihf DEB_TARGET_GNU_CPU=arm 
DEB_HOST_GNU_TYPE=arm-linux-gnueabihf DEB_HOST_GNU_CPU=arm 
DEB_TARGET_ARCH_CPU=arm DEB_B
  UILD_MULTIARCH=x86_64-linux-gnu DEB_HOST_GNU_SYSTEM=linux-gnueabihf 
DEB_TARGET_ARCH_ABI=eabihf DEB_TARGET_ARCH=armhf DEB_HOST_ARCH_ENDIAN=little 
DEB_HOST_ARCH
  _CPU=arm DEB_BUILD_ARCH_CPU=amd64 cmake .. -DCLICK_MODE=on -DINSTALL_TESTS=off
  ERROR

  This makes the autopkgtests fail, so it's blocking bug #1693226.

  [Test Case]

  Run the click autopkgtests.
  Check that there are no errors related to the wrong fs type.

  [Regression Potential]

  Fixing this for artful could make it fail in previous versions.
  However, this was found by the autopkgtests, so as long as the chroot tests 
pass in the other revisions the fix is correct.

  [Other Info]

  Click is now longer in active development. These tests were failing
  for a long time. In here we are just trying to make a small change on
  the name of the python module so it doesn't conflict with
  python3-click which is in active development and needed by snapcraft
  in bug #1692102.

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

[Ubuntu Foundations Team Bug Bot]

** Attachment removed: "DuplicateSignature.txt"
   
https://bugs.launchpad.net/bugs/1698610/+attachment/4898221/+files/DuplicateSignature.txt

-- 
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] DuplicateSignature.txt

[Brian Murray]

Due to a bug in apport's method for creating a duplicate signature, the
DuplicateSignature in this report was incorrect. We are fixing that now,
sorry for the noise!

** Attachment added: "DuplicateSignature.txt"
   
https://bugs.launchpad.net/bugs/1698610/+attachment/4898622/+files/DuplicateSignature.txt

-- 
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 1698670] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: lib/i386-linux-gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0 usr/lib/i386-linux-gnu/openssl-1.0.0/e

[Ubuntu Foundations Team Bug Bot]

** Attachment removed: "DuplicateSignature.txt"
   
https://bugs.launchpad.net/bugs/1698670/+attachment/4898219/+files/DuplicateSignature.txt

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: lib/i386-linux-
  gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0 usr/lib/i386
  -linux-gnu/openssl-1.0.0/engines/lib4758cca.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libaep.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libatalla.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libcapi.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libchil.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libcswift.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libgmp.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libgost.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libnuron.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libpadlock.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libsureware.so usr/lib/i386-linux-
  gnu/openssl-1.0.0/engines/libubsec.so
  usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to
  install/upgrade: el paquete libssl1.0.0:i386 no está listo para
  configurarse  no se puede configurar (estado actual `half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  please

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6 [modified: 
lib/i386-linux-gnu/libcrypto.so.1.0.0 lib/i386-linux-gnu/libssl.so.1.0.0 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/i386-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun Jun 18 11:19:46 2017
  ErrorMessage: el paquete libssl1.0.0:i386 no está listo para configurarse  no 
se puede configurar (estado actual `half-installed')
  InstallationDate: Installed on 2017-05-05 (44 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1698670/+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 1583269] Re: Bash dies with a SIGABRT sporadically when doing 'read -N INTEGER'.

[xhienne]

Affects trusty too. A quick way to reproduce this is (works 9 times out of 10 
here):
$ bash -c 'read -N 1000' < /dev/urandom 

Trusty output:
$ bash -c 'read -N 1000' < /dev/urandom 
malloc: ../.././builtins/../.././builtins/read.def:603: assertion botched
realloc: start and end chunk sizes differ
Aborting...Aborted

Xenial output:
$ bash -c 'read -N 1000' < /dev/urandom 
malloc: ../.././builtins/../.././builtins/read.def:617: assertion botched
realloc: start and end chunk sizes differ
Aborting...Aborted

** Tags added: trusty

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

Title:
  Bash dies with a SIGABRT sporadically when doing  'read -N INTEGER'.

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Bash sometimes dies with a SIGABRT on the command
  read -N $N < /dev/urandom
  where $N represent an integer >=1.

  It occurs frequently for high values of N (>2**20).
  It occurs rarely for low values of N (<2**20).
  It has occurred more than once with a value of N as low as 128!

  With N=2**21, this command aborts approximately 5 out of 10 tries.
  ( read -N 2097152 < /dev/urandom )

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 18 12:24:28 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-formosa-beigang-precise-amd64-20130801-1
  InstallationDate: Installed on 2016-01-23 (116 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130801-07:00
  SourcePackage: bash
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (26 days ago)

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

[Olivier Tilloy]

Although chromium-browser is affected by the issue, it doesn't appear to
be the cause of the issue itself (other apps like gnome-terminal appear
to be similarly affected), so I'm marking this bug invalid for chromium-
browser.

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

-- 
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:
  Invalid
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 1583269] Re: Bash dies with a SIGABRT sporadically when doing 'read -N INTEGER'.

[Launchpad Bug Tracker]

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

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

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

Title:
  Bash dies with a SIGABRT sporadically when doing  'read -N INTEGER'.

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Bash sometimes dies with a SIGABRT on the command
  read -N $N < /dev/urandom
  where $N represent an integer >=1.

  It occurs frequently for high values of N (>2**20).
  It occurs rarely for low values of N (<2**20).
  It has occurred more than once with a value of N as low as 128!

  With N=2**21, this command aborts approximately 5 out of 10 tries.
  ( read -N 2097152 < /dev/urandom )

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 18 12:24:28 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-formosa-beigang-precise-amd64-20130801-1
  InstallationDate: Installed on 2016-01-23 (116 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130801-07:00
  SourcePackage: bash
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1583269/+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 1650792] Re: Ubuntu 16.04.1 System policy prevents modification of network settings for all users

[Launchpad Bug Tracker]

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

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

Title:
  Ubuntu 16.04.1 System policy prevents modification of network settings
  for all users

Status in modemmanager package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Same bug as described for Ubuntu 15.04 (see
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/964705)
  is still in my Ubuntu 16.04.1! My workaround is simple but strange:

  After switching on my notebook, booting into Ubuntu 16.04.1, and being
  at the login screen, before having logged into any user, the SIM-PIN
  menu appears. I key in the SIM-PIN, hit the  button, then I am
  asked again for the SIM-PIN, this time with the error message
  "PolicyKit authorization failed: challenge needed for
  org.freedesktop.ModemManager1.Device.Control". My workaround:

  Hit the  button

  After that, I am able to log in and connect with my Aldi/Medion Huawei
  E173 USB stick to the network, if I am an AdminUser. For a user
  without Admin-rights it is a little bit more complicated after having
  logged in: he has to unlock the SIM pin again, then he is asked for
  the Admin passwort because necessary administrative rights. He has to
  hit  twice, but then he can connect to the network without any
  knowledge of the Admin-paswort. Strange!

  Will Ubuntu 16.04 sometime come to the point of enabling mobile
  networking as simple as it was with Ubuntu 14.04?

  Thank you,

  siggi2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1650792/+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 1650792] Re: Ubuntu 16.04.1 System policy prevents modification of network settings for all users

[Carlo Lobrano]

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

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. 
I marked this bug as duplicate of bug #964705.

Could you please take some time to open one more bug for the udev rule
you added?

** This bug has been marked a duplicate of bug 964705
   System policy prevents modification of network settings for all users

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

Title:
  Ubuntu 16.04.1 System policy prevents modification of network settings
  for all users

Status in modemmanager package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Same bug as described for Ubuntu 15.04 (see
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/964705)
  is still in my Ubuntu 16.04.1! My workaround is simple but strange:

  After switching on my notebook, booting into Ubuntu 16.04.1, and being
  at the login screen, before having logged into any user, the SIM-PIN
  menu appears. I key in the SIM-PIN, hit the  button, then I am
  asked again for the SIM-PIN, this time with the error message
  "PolicyKit authorization failed: challenge needed for
  org.freedesktop.ModemManager1.Device.Control". My workaround:

  Hit the  button

  After that, I am able to log in and connect with my Aldi/Medion Huawei
  E173 USB stick to the network, if I am an AdminUser. For a user
  without Admin-rights it is a little bit more complicated after having
  logged in: he has to unlock the SIM pin again, then he is asked for
  the Admin passwort because necessary administrative rights. He has to
  hit  twice, but then he can connect to the network without any
  knowledge of the Admin-paswort. Strange!

  Will Ubuntu 16.04 sometime come to the point of enabling mobile
  networking as simple as it was with Ubuntu 14.04?

  Thank you,

  siggi2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1650792/+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 1650792] Re: Ubuntu 16.04.1 System policy prevents modification of network settings for all users

[Launchpad Bug Tracker]

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

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

** Changed in: modemmanager (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/1650792

Title:
  Ubuntu 16.04.1 System policy prevents modification of network settings
  for all users

Status in modemmanager package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Same bug as described for Ubuntu 15.04 (see
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/964705)
  is still in my Ubuntu 16.04.1! My workaround is simple but strange:

  After switching on my notebook, booting into Ubuntu 16.04.1, and being
  at the login screen, before having logged into any user, the SIM-PIN
  menu appears. I key in the SIM-PIN, hit the  button, then I am
  asked again for the SIM-PIN, this time with the error message
  "PolicyKit authorization failed: challenge needed for
  org.freedesktop.ModemManager1.Device.Control". My workaround:

  Hit the  button

  After that, I am able to log in and connect with my Aldi/Medion Huawei
  E173 USB stick to the network, if I am an AdminUser. For a user
  without Admin-rights it is a little bit more complicated after having
  logged in: he has to unlock the SIM pin again, then he is asked for
  the Admin passwort because necessary administrative rights. He has to
  hit  twice, but then he can connect to the network without any
  knowledge of the Admin-paswort. Strange!

  Will Ubuntu 16.04 sometime come to the point of enabling mobile
  networking as simple as it was with Ubuntu 14.04?

  Thank you,

  siggi2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1650792/+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 1693226] Re: Break the conflicts with click the optparser

[Leo Arias]

We tested this in xenial, yakkety and zesty proposed, together with snapcraft 
for bug #1692102.
No issues found with the rename of the package, and now snapcraft can be 
updated without problems.

I've just marked this as verified.

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

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

Title:
  Break the conflicts with click the optparser

Status in click package in Ubuntu:
  Fix Released
Status in click source package in Xenial:
  Fix Committed
Status in click source package in Yakkety:
  Fix Committed
Status in click source package in Zesty:
  Fix Committed
Status in click source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * python-click and python-click-package conflict as they use the same
 python package for its implementation.

   * Since python-click-package is an implementation detail for the click 
 package and python3-click is a package meant to be used in other
 implementations it makes sense to break the conflict by moving the
 package name for python-click-package to a different name

   * snapcraft has moved from docopt to python3-click, users that have click
 installed don't have an upgrade path.his bug.

  [Test Case]

   * Where snapcraft 2.30 is present:
 
 - apt install click
 - Install snapcraft << 2.30
 - update to snapcraft >= 2.30
 - the upgrade should not be held on any package.
 - click and snapcraft commands should work.

  * Install python3-click and click should be possible. The click command
should keep working and python3 -c 'from click import group' shall work.

  
  [Regression Potential] 

   * Users depending on click from python-click-package will be importing an
 unexpected click in any scripts they may have.

  [Other Info]
   
   * While unfortunate, click as a technology is deprecated and not used
 anymore. This resolution path was discussed with slangasek and apw prior
 to any work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Cruz Fernandez]

Just expanding a little bit more my last comment, on Ubuntu 17.04, using
the 'sudo openconnect xxx' command is adding to the file
/run/resolvconf/resolv.conf file the DNS IP addresses as global ones.
Just also added them on the 'icon' version and it fixed it too. In
Ubuntu 17.04 it's using by default the systemd-resolved service (instead
of the reported one dnsmasq).

Maybe we should report a different bug for Ubuntu 17.04 as the packages
interaction look to be other ones?

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1694296] Re: package libnspr4:amd64 2:4.13.1-0ubuntu0.17.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c

[Robie Basak]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better.
 
Since there isn't enough information in your report to differentiate between a 
local configuration problem and a bug in Ubuntu, I'm marking this bug as 
Incomplete.
 
If indeed this is a local configuration problem, you can find pointers to get 
help for this sort of problem here: http://www.ubuntu.com/support/community 
 
Or if you believe that this is really a bug, then you may find it helpful to 
read "How to report bugs effectively" 
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you 
would then provide a more complete description of the problem, explain why you 
believe this is a bug in Ubuntu rather than a problem specific to your system, 
and then change the bug status back to New.


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

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

Title:
  package libnspr4:amd64 2:4.13.1-0ubuntu0.17.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in nspr package in Ubuntu:
  Incomplete

Bug description:
  Sempre estou tendo problemas para adicionar novos pacotes nao consigo
  reproduzir videos . Por favor gostaria de ajuda

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libnspr4:amd64 2:4.13.1-0ubuntu0.17.04.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon May 29 12:05:30 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2
   libgcc1 1:6.3.0-12ubuntu2
  DuplicateSignature:
   package:libnspr4:amd64:2:4.13.1-0ubuntu0.17.04.1
   Processing triggers for update-notifier-common (3.179) ...
   ttf-mscorefonts-installer: processing...
   dpkg: error processing package libnspr4:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-06 (23 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: nspr
  Title: package libnspr4:amd64 2:4.13.1-0ubuntu0.17.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nspr/+bug/1694296/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Cruz Fernandez]

On my Ubuntu 17.04 (also happened on 16.10, upgraded to 17.10 that same
machine) the bug it's happening to me. My current workaround is to use
an equivalent 'openconnect'.

Command issued in my case:

sudo openconnect --user my-vpn-user --csd-user my-local-unix-user
--csd-wrapper ~/csd-wrapper-download.sh --authgroup GROUP_OF_VPN
https://remote.corporate.network.com

Another workaround I'm using is to put the internal VPNs IPs on
/etc/hosts

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1683923] Re: Empty extglob patterns hang bash

[xhienne]

** Tags added: trusty

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

Title:
  Empty extglob patterns hang bash

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Bash hangs when extglobs with no patterns are specified.

  Example:

  $ echo !()

  should print the contents of the current directory, but actually makes
  bash hang with 100% CPU usage. Also affects other pattern types, e.g.
  @() and ?(). Non-empty patterns work correctly.

  After executing a command containing such a glob, a SIGKILL is
  required to terminate the process.

  Additional info:

  $ lsb_release  -rd
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04

  $ apt-cache policy bash
  bash:
Installed: 4.3-7ubuntu1.5
Candidate: 4.3-7ubuntu1.5
Version table:
   *** 4.3-7ubuntu1.5 0
  500 http://mirrors.linode.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://mirrors.linode.com/ubuntu/ trusty-security/main amd64 
Packages

  100 /var/lib/dpkg/status
   4.3-6ubuntu1 0
  500 http://mirrors.linode.com/ubuntu/ trusty/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1683923/+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 1683923] Re: Empty extglob patterns hang bash

[Launchpad Bug Tracker]

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

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

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

Title:
  Empty extglob patterns hang bash

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Bash hangs when extglobs with no patterns are specified.

  Example:

  $ echo !()

  should print the contents of the current directory, but actually makes
  bash hang with 100% CPU usage. Also affects other pattern types, e.g.
  @() and ?(). Non-empty patterns work correctly.

  After executing a command containing such a glob, a SIGKILL is
  required to terminate the process.

  Additional info:

  $ lsb_release  -rd
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04

  $ apt-cache policy bash
  bash:
Installed: 4.3-7ubuntu1.5
Candidate: 4.3-7ubuntu1.5
Version table:
   *** 4.3-7ubuntu1.5 0
  500 http://mirrors.linode.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://mirrors.linode.com/ubuntu/ trusty-security/main amd64 
Packages

  100 /var/lib/dpkg/status
   4.3-6ubuntu1 0
  500 http://mirrors.linode.com/ubuntu/ trusty/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1683923/+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 1686573] Re: USB Modem not displayed in network manager

[Carlo Lobrano]

It seems that both ModemManager and NetworkManager are doing the right
thing

Apr 27 10:57:05 Paul-HP-Laptop ModemManager[846]:  Modem 
/org/freedesktop/ModemManager1/Modem/1: state changed (enabling -> registered)
Apr 27 10:57:06 Paul-HP-Laptop NetworkManager[898]:  
[1493254626.0016] (ttyUSB2): modem state changed, 'enabling' --> 'registered' 
(reason: user-requested)


If you're able to reproduce the issue, could you please enable debug logs in 
both NetworkManager and ModemManager?

Please do the following (I know, it's a bit long, sorry for that)

$ sudo systemctl stop NetworkManager
$ sudo systemctl stop ModemManager

$ sudo NetworkManager --log-level=DEBUG --debug | tee $HOME/network-
manager.logs

then open a new shell and run:

$ sudo ModemManager -d | tee $HOME/modem-manager.logs

and then attach the two log file in your home directory

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

Title:
  USB Modem not displayed in network manager

Status in modemmanager package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in plasma-nm package in Ubuntu:
  New

Bug description:
  4G USB WAN modem will not display in network manager, but is fully
  detected by the kernel and is displayed in ip link

  journal;
  Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: new high-speed USB device 
number 5 using xhci_hcd
  Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: config 1 has an invalid 
interface number: 7 but max is 3
  Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: config 1 has no interface 
number 2
  Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: New USB device found, 
idVendor=1199, idProduct=68a3
  Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: New USB device strings: 
Mfr=3, Product=2, SerialNumber=4
  Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Product: AC760S
  Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Manufacturer: Sierra 
Wireless, Incorporated
  Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: SerialNumber: 359822042204515
  Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.0: Sierra USB modem 
converter detected
  Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter 
now attached to ttyUSB0
  Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.1: Sierra USB modem 
converter detected
  Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter 
now attached to ttyUSB1
  Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.3: Sierra USB modem 
converter detected
  Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter 
now attached to ttyUSB2
  Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra_net 5-2:1.7 wwan0: register 
'sierra_net' at usb-:00:10.0-2, Sierra Wireless USB-to-WWAN Modem, 
ce:6b:97:53:02:07
  Apr 27 10:56:44 Paul-HP-Laptop mtp-probe[19472]: checking bus 5, device 5: 
"/sys/devices/pci:00/:00:10.0/usb5/5-2"
  Apr 27 10:56:44 Paul-HP-Laptop mtp-probe[19472]: bus: 5, device: 5 was not an 
MTP device
  Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra_net 5-2:1.7 wwp0s16f0u2i7: 
renamed from wwan0
  Apr 27 10:56:44 Paul-HP-Laptop NetworkManager[898]:   [1493254604.4733] 
devices added (path: 
/sys/devices/pci:00/:00:10.0/usb5/5-2/5-2:1.7/net/wwp0s16f0u2i7, iface: 
wwp0s16f0u2i7
  Apr 27 10:56:44 Paul-HP-Laptop NetworkManager[898]:   [1493254604.4734] 
device added (path: 
/sys/devices/pci:00/:00:10.0/usb5/5-2/5-2:1.7/net/wwp0s16f0u2i7, iface: 
wwp0s16f0u2i7)
  Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]:   (ttyUSB1): port 
attributes not fully set
  Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]:   (ttyUSB0): port 
attributes not fully set
  Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]:   (ttyUSB2): port 
attributes not fully set
  Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]:   Creating modem with 
plugin 'Sierra (legacy)' and '4' ports
  Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]:   Could not grab port 
(tty/ttyUSB1): 'Cannot add port 'tty/ttyUSB1', unhandled serial type'
  Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]:   Could not grab port 
(tty/ttyUSB0): 'Cannot add port 'tty/ttyUSB0', unhandled serial type'
  Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]:   (ttyUSB2): port 
attributes not fully set
  Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]:   Modem for device at 
'/sys/devices/pci:00/:00:10.0/usb5/5-2' successfully created
  Apr 27 10:57:01 Paul-HP-Laptop ModemManager[846]:   Modem: state 
changed (unknown -> disabled)
  Apr 27 10:57:01 Paul-HP-Laptop NetworkManager[898]:   [1493254621.9962] 
(ttyUSB2): modem state changed, 'disabled' --> 'enabling' (reason: user 
preference)
  Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]:   [1493254622.0002] 
manager: (ttyUSB2): new Broadband device 
(/org/freedesktop/NetworkManager/Devices/5)
  Apr 27 10:57:02 Paul-HP-Laptop 

[Touch-packages] [Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

[Dimitri John Ledkov]

** Tags added: verification-done-zesty

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

Title:
  systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Yakkety:
  Confirmed
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

   * Null-pointer dereference in resolved, results in resolved crash and
  reports on launchpad and errors.

  [Test Case]

   * Unknown steps to reproduce
   * Monitor the drop off in crashes on errors.ubuntu.com:
  https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465

  [Regression Potential]

   * The behavior is similar, instead of crashing resolved it returns an
  error in the relevant function. Whilst this may not result in correct
  dns resolution for the affected dns packets, it should not result in
  resolved crashes.

  [Original Bug Report]

  This is one of background errors that happens without any active app being 
involved.
  For the records, I had open: Firefox, Slack, Franz and the Terminal

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd. This problem was most recently seen with package version 233-6ubuntu2, 
the problem page at 
https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep  8 09:33:55 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2013-06-06 (1189 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. Dell System XPS L322X
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-231.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago)
  UserGroups:

  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1698751] Re: interface related rules appear active after deletion

[Jamie Strandboge]

Thank you for using ufw and reporting a bug. I cannot reproduce this:

$ sudo ufw allow OpenSSH
$ sudo ufw enable
$ sudo ufw show added
Added user rules (see 'ufw status' for running firewall):
ufw allow OpenSSH

$ sudo ufw allow in on eth0 to any port 8080 proto tcp
Rule added
Rule added (v6)
$ sudo ufw show added
Added user rules (see 'ufw status' for running firewall):
ufw allow OpenSSH
ufw allow in on eth0 to any port 8080 proto tcp

$ sudo ufw delete allow in on eth0 to any port 8080 proto tcp 
Rule deleted
Rule deleted (v6)
$ sudo ufw show added
Added user rules (see 'ufw status' for running firewall):
ufw allow OpenSSH

The rule you added (as you can see from the above) is generic enough to
be applied to *both* IPv4 and IPv6. Did you delete the rule in the
manner I did above, or did you use 'ufw delete NUMBER'. When using
'delete NUMBER' ufw will only delete the rule specified and will not
assume you want other numbered rules to be deleted also. Eg:

$ sudo ufw allow in on eth0 to any port 8080 proto tcp
Rule added
Rule added (v6)
$ sudo ufw show added
Added user rules (see 'ufw status' for running firewall):
ufw allow OpenSSH
ufw allow in on eth0 to any port 8080 proto tcp
$ sudo ufw status numbered
Status: active

 To Action  From
 -- --  
[ 1] OpenSSHALLOW INAnywhere  
[ 2] 8080/tcp on eth0   ALLOW INAnywhere  
[ 3] OpenSSH (v6)   ALLOW INAnywhere (v6) 
[ 4] 8080/tcp (v6) on eth0  ALLOW INAnywhere (v6) 

$ sudo ufw delete 2
Deleting:
 allow in on eth0 to any port 8080 proto tcp
Proceed with operation (y|n)? y
Rule deleted
$ sudo ufw status numbered
Status: active

 To Action  From
 -- --  
[ 1] OpenSSHALLOW INAnywhere  
[ 2] OpenSSH (v6)   ALLOW INAnywhere (v6) 
[ 3] 8080/tcp (v6) on eth0  ALLOW INAnywhere (v6) 

$ sudo ufw show added
Added user rules (see 'ufw status' for running firewall):
ufw allow OpenSSH
ufw allow in on eth0 to any port 8080 proto tcp

The above is expected and intended behavior.

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

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

Title:
  interface related rules appear active after deletion

Status in ufw package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  In ufw 0.35 in Ubuntu 16.04.2 LTS , when deleting the following format rule:
  ufw allow in on eth0 to any port 8080 proto tcp

  the rule is actually deleted and the port is blocked, But when issuing 'ufw 
show added'
  the rule is still there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1698751/+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 1672499] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf

[Dimitri John Ledkov]

** Tags added: verification-done-zesty

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

Title:
  systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on
  armhf

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * ADT test superfluously fails, resulting in SRU / proposed-migration
  delays

  [Test Case]

   * Check that systemd ADT tests pass

  [Regression Potential]

   * No change to the binary packages, this is a change in ADT test-
  suite only.

  [Original Bug Report]

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/s/systemd/20170310_221057_b5cf9@/log.gz

  root-unittests fails:

   -> Unit a.service:
    Description: a.service
    Instance: n/a
    Unit Load State: not-found
    Unit Active State: inactive
    State Change Timestamp: n/a
    Inactive Exit Timestamp: n/a
    Active Enter Timestamp: n/a
    Activeerror: org.freedesktop.systemd1.NoSuchUnit: Unit c.service not found.
  Assertion 'r == 0' failed at ../src/test/test-engine.c:62, function main(). 
Aborting.
   Exit Timestamp: n/a

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