[Touch-packages] [Bug 1538284] Re: [SRU] Unescaped left brace in regex is deprecated

[Seyeong Kim]

** Changed in: pam (Ubuntu Trusty)
   Status: New => Won't Fix

** Changed in: pam (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: pam (Ubuntu Artful)
   Status: New => In Progress

** Changed in: pam (Ubuntu Xenial)
 Assignee: (unassigned) => Seyeong Kim (xtrusia)

** Changed in: pam (Ubuntu Artful)
 Assignee: (unassigned) => Seyeong Kim (xtrusia)

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

Title:
  [SRU] Unescaped left brace in regex is deprecated

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Trusty:
  Won't Fix
Status in pam source package in Xenial:
  In Progress
Status in pam source package in Artful:
  In Progress
Status in pam package in Debian:
  Fix Released

Bug description:
  [Impact]

  When installing postgresql, many warning msgs are raised
  Please refer to Original Description

  ## Corrections
  In trusty, escaping is missing but not the same symptome. NOT AFFECTED TO 
TRUSTY

  [Test Case]

  1. create ubuntu instance
  2. apt install postgresql

  [Regression Potentials]
  This change is quite small(just escaping), and it is not code changes but 
getenv script which made by debian. so risk is minimal in my opinion.

  [Original Description]

  When installing postgresql on Ubuntu 16.04 (xenial), the following
  warning are raised:

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/(?https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1538284/+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 1761682] [NEW] package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: sub-process pre-removal script returned error-code 1

[Marco Bruchmann]

Public bug reported:

Occurred during 'sudo apt full-upgrade'.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: avahi-dnsconfd 0.6.32-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Apr  6 09:22:10 2018
ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2015-06-02 (1038 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: avahi
Title: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: 
Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: sub-
  process pre-removal script returned error-code 1

Status in avahi package in Ubuntu:
  New

Bug description:
  Occurred during 'sudo apt full-upgrade'.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: avahi-dnsconfd 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Apr  6 09:22:10 2018
  ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 
zurück
  InstallationDate: Installed on 2015-06-02 (1038 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: 
Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1761682/+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 1756652] Re: $ sudo apt-get update Seccomp prevented execution of syscall 0000000041 on architecture amd64

[Julian Andres Klode]

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

** This bug has been marked a duplicate of bug 1732030
   'apt update' dies with seccomp error

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

Title:
  $ sudo apt-get update Seccomp prevented execution of syscall
  41 on architecture amd64

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Hit:1 http://ubuntu.mirrors.linux.ro/archive bionic InRelease
  Hit:2 http://ubuntu.mirrors.linux.ro/archive bionic-updates InRelease
  Hit:3 http://ubuntu.mirrors.linux.ro/archive bionic-backports InRelease
  Hit:4 http://ubuntu.mirrors.linux.ro/archive bionic-security InRelease
  Hit:5 http://repository.spotify.com stable InRelease   
  Get:6 http://repository.spotify.com stable/non-free amd64 Packages [1.630 B]
  66% [Working]
    Seccomp prevented execution of syscall 41 on architecture amd64 

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1756652/+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 1761576] [NEW] gnome-software crashed with SIGSEGV in wl_proxy_marshal → gtk_text_input_destroy → registry_handle_global_remove

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I think this crashed while the computer was sleeping and/or on wakeup.
Unfortunately I don't have anything beyond that.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.0-0ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  5 14:54:14 2018
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2017-07-18 (261 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.28.0-0ubuntu7
ProcCmdline: /usr/bin/gnome-software --gapplication-service
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7f31da2a1b09 :   mov
(%rbx),%rdx
 PC (0x7f31da2a1b09) ok
 source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-software
StacktraceTop:
 wl_proxy_marshal () at /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
 () at /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-wayland.so
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 () at /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
Title: gnome-software crashed with SIGSEGV in wl_proxy_marshal()
UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo

** Affects: gtk+3.0 (Ubuntu)
 Importance: Medium
 Status: Fix Committed


** Tags: amd64 apport-crash bionic wayland-session
-- 
gnome-software crashed with SIGSEGV in wl_proxy_marshal → 
gtk_text_input_destroy → registry_handle_global_remove
https://bugs.launchpad.net/bugs/1761576
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Touch-packages] [Bug 1761576] Re: gnome-software crashed with SIGSEGV in wl_proxy_marshal → gtk_text_input_destroy → registry_handle_global_remove

[Sebastien Bacher]

The issue looks like a imwayland one, might be fixed by that upstream commit
https://gitlab.gnome.org/GNOME/gtk/commit/31453164

** Package changed: gnome-software (Ubuntu) => gtk+3.0 (Ubuntu)

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

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

Title:
  gnome-software crashed with SIGSEGV in wl_proxy_marshal →
  gtk_text_input_destroy → registry_handle_global_remove

Status in gtk+3.0 package in Ubuntu:
  Fix Committed

Bug description:
  I think this crashed while the computer was sleeping and/or on wakeup.
  Unfortunately I don't have anything beyond that.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  5 14:54:14 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2017-07-18 (261 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SegvAnalysis:
   Segfault happened at: 0x7f31da2a1b09 : mov
(%rbx),%rdx
   PC (0x7f31da2a1b09) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   wl_proxy_marshal () at /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
   () at /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-wayland.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
  Title: gnome-software crashed with SIGSEGV in wl_proxy_marshal()
  UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1761576/+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 1761684] [NEW] Regression in lists like gnome-boxes

[Didier Roche]

Public bug reported:

The theme regressed the actively selected item on gnome-boxes (hover is also 
hard to read).
See attached screenshot.

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

** Attachment added: "Capture d’écran de 2018-04-06 09-47-37.png"
   
https://bugs.launchpad.net/bugs/1761684/+attachment/5103619/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202018-04-06%2009-47-37.png

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

Title:
  Regression in lists like gnome-boxes

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  The theme regressed the actively selected item on gnome-boxes (hover is also 
hard to read).
  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1761684/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) due to outdated gcc-4.8

[Dmitry S]

Running Ubuntu 16.04 (xenial) in VirtualBox (Windows host). After Ubuntu update 
got affected too - vboxdrv dkms won't install. dmesg would give:
[  260.993242] vboxdrv: version magic '4.4.0-119-generic SMP mod_unload 
modversions ' should be '4.4.0-119-generic SMP mod_unload modversions retpoline 
'

$ uname -a
Linux ... 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

In my case I had two GCC versions installed side by side (4.9 and 5):
$ sudo update-alternatives --config gcc
There are 2 choices for the alternative gcc (providing /usr/bin/gcc).

  SelectionPath  Priority   Status

  0/usr/bin/gcc-5 20auto mode
* 1/usr/bin/gcc-4.9   10manual mode
  2/usr/bin/gcc-5 20manual mode

update-alternatives was pointing to 4.9, so g++ --version was giving me 4.9:
$ gcc --version
gcc (Ubuntu 4.9.3-13ubuntu2) 4.9.3

Switched to version 5 and re-installed virtualbox-dkms:

$ sudo update-alternatives --config gcc
There are 2 choices for the alternative gcc (providing /usr/bin/gcc).

  SelectionPath  Priority   Status

  0/usr/bin/gcc-5 20auto mode
  1/usr/bin/gcc-4.9   10manual mode
* 2/usr/bin/gcc-5 20manual mode

Press  to keep the current choice[*], or type selection number: 2

$ sudo apt-get install virtualbox-dkms --reinstall

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) due to outdated gcc-4.8

Status in gcc-4.8 package in Ubuntu:
  Fix Released

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  v

[Touch-packages] [Bug 1761585] Re: ibus_bus_init does an unconditional call to chmod on $HOME/.config/ibus/bus

[Sebastien Bacher]

The fix from Olivier has been commited upstream, that's probably worth
backporting to bionic (note that there is already an ibus update in the
unapproved queue so a new upload needs to be based on that version)

** Also affects: ibus via
   https://github.com/ibus/ibus/issues/1996
   Importance: Unknown
   Status: Unknown

** Changed in: ibus (Ubuntu)
   Importance: Undecided => Low

** Changed in: ibus (Ubuntu)
   Status: New => In Progress

** Changed in: ibus (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  ibus_bus_init does an unconditional call to chmod on
  $HOME/.config/ibus/bus

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  In Progress

Bug description:
  This was spotted by jdstrand when running the chromium snap, which
  recently enabled ibus support (https://forum.snapcraft.io/t/cant-use-
  input-method-in-snap-apps/4712/12):

  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000

  The code that calls chmod is in ibus_bus_init:

static void
ibus_bus_init (IBusBus *bus)
{
  gchar *path;
  […]
  path = g_path_get_dirname (ibus_get_socket_path ());
  g_mkdir_with_parents (path, 0700);
  g_chmod (path, 0700);
  […]
}

  This could be avoided by checking first the file mode bits on that
  directory, and do the g_chmod call only if ≠ 0700.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  5 21:55:30 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (642 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1761585/+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 1761701] [NEW] package python3-crypto 2.6.1-7build2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

[Shubham]

Public bug reported:

No idea

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: python3-crypto 2.6.1-7build2
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Apr  6 19:38:47 2018
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-01-20 (75 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: python-crypto
Title: package python3-crypto 2.6.1-7build2 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package python3-crypto 2.6.1-7build2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in python-crypto package in Ubuntu:
  New

Bug description:
  No idea

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: python3-crypto 2.6.1-7build2
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Apr  6 19:38:47 2018
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-01-20 (75 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: python-crypto
  Title: package python3-crypto 2.6.1-7build2 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/python-crypto/+bug/1761701/+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 1761702] Re: lightdm crashed with SIGSEGV in _dl_fini()

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1761702/+attachment/5103724/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1761702/+attachment/5103726/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1761702/+attachment/5103733/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1761702/+attachment/5103734/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1761702/+attachment/5103735/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1761702/+attachment/5103736/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1761702/+attachment/5103737/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1675141
   lightdm crashed with SIGSEGV in munmap()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  lightdm crashed with SIGSEGV in _dl_fini()

Status in lightdm package in Ubuntu:
  New

Bug description:
  running 18.04 with unity.
  Got this crash-report after login. I first did enter a wrong password due to 
lag on the BT Keyboard.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Thu Apr  5 10:06:54 2018
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2013-09-28 (1650 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  ProcCmdline: lightdm --session-child 16 19
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7faa58a77b3a <_dl_fini+410>: mov0x8(%rax),%r15
   PC (0x7faa58a77b3a) ok
   source "0x8(%rax)" (0x7faa5438ce78) not located in a known VMA region 
(needed readable region)!
   destination "%r15" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   _dl_fini () at dl-fini.c:134
   __run_exit_handlers (status=0, listp=0x7faa575e3718 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:108
   __GI_exit (status=) at exit.c:139
   ()
() at /lib/x86_64-linux-gnu/libc.so.6
  Title: lightdm crashed with SIGSEGV in _dl_fini()
  UpgradeStatus: Upgraded to bionic on 2018-01-12 (83 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1761702/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) due to outdated gcc-4.8

[Simon Reed]

Running Xubuntu 14.04 and just upgraded to 3.13.0-144 from 3.13.0-143
and needed to re-apply the fix again.

The fix I have used is to edit  /usr/src/linux-
headers-3.13.0-144/include/linux/vermagic.h

$ cd /usr/src/linux-headers-3.13.0-144/include/linux
$ diff vermagic.h vermagic.h.WAS 
27,28c27
< /* #ifdef RETPOLINE */
< #if 1
---
> #ifdef RETPOLINE

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) due to outdated gcc-4.8

Status in gcc-4.8 package in Ubuntu:
  Fix Released

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1750937/+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 1761585] Re: ibus_bus_init does an unconditional call to chmod on $HOME/.config/ibus/bus

[Olivier Tilloy]

Once in bionic, we will want to SRU to xenial so that all snaps that are
built with a xenial stack get an updated libibus.

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

Title:
  ibus_bus_init does an unconditional call to chmod on
  $HOME/.config/ibus/bus

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  In Progress

Bug description:
  This was spotted by jdstrand when running the chromium snap, which
  recently enabled ibus support (https://forum.snapcraft.io/t/cant-use-
  input-method-in-snap-apps/4712/12):

  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000

  The code that calls chmod is in ibus_bus_init:

static void
ibus_bus_init (IBusBus *bus)
{
  gchar *path;
  […]
  path = g_path_get_dirname (ibus_get_socket_path ());
  g_mkdir_with_parents (path, 0700);
  g_chmod (path, 0700);
  […]
}

  This could be avoided by checking first the file mode bits on that
  directory, and do the g_chmod call only if ≠ 0700.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  5 21:55:30 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (642 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1761585/+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 1760096] Re: /usr/bin/software-properties-gtk:GLib.GError:/usr/bin/software-properties-gtk@101:__init__:init_livepatch:__init__:_load

[Launchpad Bug Tracker]

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

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

  * debian/control:
- Mark gnome-keyring as recommended, which provides
  org.freedesktop.secrets.service.
  * GoaAuty.py:
- Show warning and avoid crashing if gnome-keyring is not installed.
  (LP: #1760096)
  * SoftwareProperties.py:
- install canonical-livepatch from stable channel (LP: #1760117)

 -- Andrea Azzarone   Tue, 03 Apr 2018
16:04:32 +0200

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

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

Title:
  /usr/bin/software-properties-gtk:GLib.GError:/usr/bin/software-
  properties-gtk@101:__init__:init_livepatch:__init__:_load

Status in software-properties package in Ubuntu:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1760096/+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 1761176] Re: remove one more old Touch profile that causes profile compilation errors

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor - 2.12-4ubuntu4

---
apparmor (2.12-4ubuntu4) bionic; urgency=medium

  * Remove another Ubuntu Touch profile (LP: #1761176)
- debian/control: Breaks on messaging-app
- debian/postinst: on upgrade, remove profile for usr.bin.messaging-app

 -- Jamie Strandboge   Wed, 04 Apr 2018 13:58:26 +

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

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

Title:
  remove one more old Touch profile that causes profile compilation
  errors

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  This is an extension of
  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1756800 where
  we missed messaging-app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1761176/+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 1751011] Re: bash crashes in qemu-user environments (bionic)

[Launchpad Bug Tracker]

This bug was fixed in the package bash - 4.4.18-2ubuntu1

---
bash (4.4.18-2ubuntu1) bionic; urgency=medium

  * Merge with Debian; remaining changes:
- skel.bashrc:
  - Run lesspipe.
  - Enable ls aliases.
  - Set options in ll alias to -alF.
  - Define an alert alias.
  - Enabled colored grep aliases.
- etc.bash.bashrc:
  - Add sudo hint.

bash (4.4.18-2) unstable; urgency=medium

  * Revert the changes from the last upload.
  * Configure the normal build --without-bash-malloc as well.
See http://lists.nongnu.org/archive/html/qemu-devel/2018-03/msg04700.html
for the qemu fix.  Closes: #865599. LP: #1751011.
  * Apply upstream patch 019.

bash (4.4.18-1.1) unstable; urgency=high

  * Non-maintainer upload.
  * Build again with -no-pie as dropping it broke bash when run under
qemu-user (with the same symptoms as #842037). Closes: #889869
Re-opens: #865599

 -- Matthias Klose   Wed, 04 Apr 2018 20:30:26 +0200

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

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

Title:
  bash crashes in qemu-user environments (bionic)

Status in bash package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Confirmed
Status in bash source package in Bionic:
  Fix Released
Status in qemu source package in Bionic:
  Confirmed
Status in bash package in Debian:
  Fix Released

Bug description:
  Attempts to launch bash in an arm64 qemu-user environment in bionic
  results in the following error message:

  bash: xmalloc: .././shell.c:1709: cannot allocate 10 bytes (0 bytes
  allocated)

  This causes any qemu/chroot based bootstrapping to fail as many
  packages invoke bash during postinst.

  Version: bash_4.4.18-1ubuntu1_arm64
  Release: 18.04 pre-release

  QEMU: 2.8.0

  This appears to have been reported and fixed in the corresponding
  Debian package (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=889869)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1751011/+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 1760117] Re: software-properties-gtk installs canonical-livepatch from edge

[Launchpad Bug Tracker]

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

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

  * debian/control:
- Mark gnome-keyring as recommended, which provides
  org.freedesktop.secrets.service.
  * GoaAuty.py:
- Show warning and avoid crashing if gnome-keyring is not installed.
  (LP: #1760096)
  * SoftwareProperties.py:
- install canonical-livepatch from stable channel (LP: #1760117)

 -- Andrea Azzarone   Tue, 03 Apr 2018
16:04:32 +0200

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

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

Title:
  software-properties-gtk installs canonical-livepatch from edge

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

Bug description:
  software-properties installs canonical-livepatch from edge. Switch to
  stable before release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1760117/+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 1709603] Re: apt {upgrade, install, source} require an update call first

[Murukesh Mohanan]

Alternate:

- a `-u`/`--update` option that unconditionally performs an apt update
as an option to apt itself, since every subcommand except `update` and
`edit-sources` can potentially benefit from an `update` beforehand. For
`edit-sources`, have it update after instead of before, and for
`update`, the option can be a NOP.

I'd love to be able to do something like:

apt full-upgrade --autoremove --update

I can do `apt full-upgrade --autoremove` now, removing obsolete packages
and upgrading in one shot. It'd be glorious to include the package lists
update in that operation too.

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

Title:
  apt {upgrade,install, source} require an update call first

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  I think that this should be tracked in its own separate bug tracking
  my specific UX objection to the current status quo.

  See
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/5,
  subsequent discussion and
  https://twitter.com/chr1sa/status/894048628284604416

  We think that the updating of indexes should be an implementation
  detail of "apt upgrade" and "apt install", rather than something
  exposed to the user. If updating is judged be required (for example
  the index is more than X old), then it should be done automatically
  before the requested operation commences.

  Here's one proposed implementation:

  1) Fix bug 1429285 ("apt-get update --if-necessary").

  2) Add an option to have "apt install" and "apt upgrade" (also "apt
  full-upgrade", etc?) automatically and internally call the
  implementation of "apt-get update --if-necessary" first.

  3) Enable the option by default on Ubuntu.

  This would change the behaviour of "apt", which AIUI is intended to be
  the user focused CLI. It wouldn't change the behaviour of "apt-get",
  which AIUI needs to retain behavioural backwards compatibility for
  existing scripts.

  Then we could promote "apt install" and "apt upgrade" as much simpler
  commands to operate.

  Note that Julian disagreed with this proposed behaviour change in
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/7.
  I think that the very user-focused Ubuntu perspective should be to
  focus on the common use case for "apt". Hence my (compromise)
  suggestion that we implement this as an option upstream, and then
  leave it to distros to choose the default behaviour for their users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1709603/+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 1752415] Re: [patch] Please add command-not-found hints

[Launchpad Bug Tracker]

This bug was fixed in the package python3-defaults - 3.6.5-2

---
python3-defaults (3.6.5-2) unstable; urgency=medium

  * Distinguish between python3.6 and python3-stdlib-extensions versions.
Closes: #894168.
  * python3-venv: Depend on python3-distutils.

 -- Matthias Klose   Mon, 02 Apr 2018 07:06:32 +0200

** Changed in: python3-defaults (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [patch] Please add command-not-found hints

Status in python3-defaults package in Ubuntu:
  Fix Released

Bug description:
  The new command-not-found in bionic supports hints from the package
  now. To make command-not-found suggest "python3" on top if a user
  types "python" (when that is not installed) the attached debdiff is
  needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1752415/+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 1761712] Re: gsettings-data-convert crashed with signal 5 in g_settings_schema_get_value()

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1761712/+attachment/5103794/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1761712/+attachment/5103796/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1761712/+attachment/5103800/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1761712/+attachment/5103801/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1761712/+attachment/5103802/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1761712/+attachment/5103803/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1761712/+attachment/5103804/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 945144
   gsettings-data-convert crashed with signal 5 in g_settings_set_value()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gsettings-data-convert crashed with signal 5 in
  g_settings_schema_get_value()

Status in gconf package in Ubuntu:
  New

Bug description:
  This is caused by a missing setting in
  org.gnome.desktop.wm.preferences.

  This can be seen thanks to this error message that appears in the
  backtrace:

  Settings schema 'org.gnome.desktop.wm.preferences' does not contain a
  key named 'application-based'"

  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gconf2 3.2.6-4ubuntu1
  Uname: Linux 4.15.15-041515-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Apr  6 10:48:45 2018
  ExecutablePath: /usr/bin/gsettings-data-convert
  ExecutableTimestamp: 1496904803
  ProcCmdline: gsettings-data-convert
  ProcCwd: /home/bonnaudl
  Signal: 5
  SourcePackage: gconf
  StacktraceTop:
   g_settings_schema_get_value (schema=0x562a8ac5da30, key=0x562a8ac6b810 
"application-based") at ../../../../gio/gsettingsschema.c:970
   g_settings_schema_key_init (key=key@entry=0x7ffcbae8c490, 
schema=0x562a8ac5da30, name=name@entry=0x562a8ac6b810 "application-based") at 
../../../../gio/gsettingsschema.c:1249
   g_settings_set_value (settings=settings@entry=0x562a8ac5dc30 [GSettings], 
key=key@entry=0x562a8ac6b810 "application-based", value=0x562a8ac6f320) at 
../../../../gio/gsettings.c:1563
   g_settings_set (settings=0x562a8ac5dc30 [GSettings], key=0x562a8ac6b810 
"application-based", format=) at ../../../../gio/gsettings.c:1670
   handle_file (filename=) at gsettings-data-convert.c:295
  Title: gsettings-data-convert crashed with signal 5 in 
g_settings_schema_get_value()
  UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago)
  UserGroups: adm cdrom dip fuse libvirt libvirtd lpadmin plugdev sambashare 
staff sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1761712/+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 1761712] Re: gsettings-data-convert crashed with signal 5 in g_settings_schema_get_value()

[Sebastien Bacher]

** This bug is no longer a duplicate of bug 945144
   gsettings-data-convert crashed with signal 5 in g_settings_set_value()

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

Title:
  gsettings-data-convert crashed with signal 5 in
  g_settings_schema_get_value()

Status in gconf package in Ubuntu:
  New

Bug description:
  This is caused by a missing setting in
  org.gnome.desktop.wm.preferences.

  This can be seen thanks to this error message that appears in the
  backtrace:

  Settings schema 'org.gnome.desktop.wm.preferences' does not contain a
  key named 'application-based'"

  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gconf2 3.2.6-4ubuntu1
  Uname: Linux 4.15.15-041515-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Apr  6 10:48:45 2018
  ExecutablePath: /usr/bin/gsettings-data-convert
  ExecutableTimestamp: 1496904803
  ProcCmdline: gsettings-data-convert
  ProcCwd: /home/bonnaudl
  Signal: 5
  SourcePackage: gconf
  StacktraceTop:
   g_settings_schema_get_value (schema=0x562a8ac5da30, key=0x562a8ac6b810 
"application-based") at ../../../../gio/gsettingsschema.c:970
   g_settings_schema_key_init (key=key@entry=0x7ffcbae8c490, 
schema=0x562a8ac5da30, name=name@entry=0x562a8ac6b810 "application-based") at 
../../../../gio/gsettingsschema.c:1249
   g_settings_set_value (settings=settings@entry=0x562a8ac5dc30 [GSettings], 
key=key@entry=0x562a8ac6b810 "application-based", value=0x562a8ac6f320) at 
../../../../gio/gsettings.c:1563
   g_settings_set (settings=0x562a8ac5dc30 [GSettings], key=0x562a8ac6b810 
"application-based", format=) at ../../../../gio/gsettings.c:1670
   handle_file (filename=) at gsettings-data-convert.c:295
  Title: gsettings-data-convert crashed with signal 5 in 
g_settings_schema_get_value()
  UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago)
  UserGroups: adm cdrom dip fuse libvirt libvirtd lpadmin plugdev sambashare 
staff sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1761712/+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 1761585] Re: ibus_bus_init does an unconditional call to chmod on $HOME/.config/ibus/bus

[Sebastien Bacher]

** Changed in: ibus (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  ibus_bus_init does an unconditional call to chmod on
  $HOME/.config/ibus/bus

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Fix Committed

Bug description:
  This was spotted by jdstrand when running the chromium snap, which
  recently enabled ibus support (https://forum.snapcraft.io/t/cant-use-
  input-method-in-snap-apps/4712/12):

  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000

  The code that calls chmod is in ibus_bus_init:

static void
ibus_bus_init (IBusBus *bus)
{
  gchar *path;
  […]
  path = g_path_get_dirname (ibus_get_socket_path ());
  g_mkdir_with_parents (path, 0700);
  g_chmod (path, 0700);
  […]
}

  This could be avoided by checking first the file mode bits on that
  directory, and do the g_chmod call only if ≠ 0700.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  5 21:55:30 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (642 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1761585/+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 1756006] Re: FFe: Support suspend-then-hibernate

[Iain Lane]

(cleaning up ~ubuntu-release bugs)

Incomplete for g-s-d - please could you reset once this is accepted
upstream?

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: New => Incomplete

** Tags removed: block-proposed

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

Title:
  FFe: Support suspend-then-hibernate

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Suspend to hibernate is a new feature that will put the system into
  hibernate after a period of time spent in the system's supported sleep
  state.  This mode will be used on some systems that take suspend to
  idle in the future with Ubuntu 18.04.

  This feature is available in upstream systemd from these two commits.
  
https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703
  
https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5
  This is accepted upstream.

  The policy needs to be made available to gnome from this commit:
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9
  As of 3/15/2018 this is not yet accepted or rejected.

  The new mode is not selected by default, but that can be changed from a 
separate policy package.
  The policy for the amount of time spent in S3/S2I can be configured by a 
separate package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+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 1729491] Re: [UIFe] ubuntu-bug says that snap packages are not installed

[Iain Lane]

(cleaning up ~ubuntu-release bugs)

This has an ubuntu-docs task that may or may not be fixed for 18.04 -
I'm unsubscribing the team as it's not something we need to track at the
RT level.

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

Title:
  [UIFe] ubuntu-bug says that snap packages are not installed

Status in apport package in Ubuntu:
  Triaged
Status in ubuntu-docs package in Ubuntu:
  New
Status in apport source package in Bionic:
  Triaged

Bug description:
  User Interface Freeze Exception Justification
  =
  The interface for ubuntu-bug/apport-bug  is super confusing if  
was installed as a snap.

  List Notifications
  ==
  https://lists.ubuntu.com/archives/ubuntu-translators/2018-April/007471.html
  

  Original Bug Description
  
  1.
  I installed the package gnome-recipes, tried to send an error report program 
in response to the received message:you cannot report a problem:
  The report belongs to a package that was not installed.

  2.
  Expected that the program will be identified as installed.

  3.
  sudo apt -f install
  [sudo] password for Alexander:
  Reading package lists... Done
  Building dependency tree
  Reading state information... Ready
  0 upgraded, 0 newly installed, for removal 0 packets are marked, and 0 
packages are not updated.
  sudo gnome-sudo recipes: gnome-recipes: command not found
  sudo apt install gnome-recipes Reading package lists... Done
  Building dependency tree
  Reading state information... Ready
  E: unable to locate package gnome-recipes

  I installed via software-center

  gnome-recipes
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  ubuntu-bug gnome-recipes
  dpkg-query: template gnome-recipes no corresponding package
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ^C^Z
  [1]+ Stopped ubuntu-bug gnome-recipes

  https://youtu.be/AXtR5m2uqUg
  ---

  1.
  произвёл установку пакета gnome-recipes, попытался отправить отчёт об ошибке 
программы, в ответ получил сообщение:Не удаётся сообщить о неполадке:
  Отчёт относится к пакету , который не был установлен.

  2.
  Ожидал что программа будет идентифицироваться как установленная.

  3.
  sudo apt -f install
  [sudo] пароль для alexandr:
  Чтение списков пакетов… Готово
  Построение дерева зависимостей
  Чтение информации о состоянии… Готово
  обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 
0 пакетов не обновлено.
  sudo gnome-recipes sudo: gnome-recipes: команда не найдена
  sudo apt install gnome-recipes Чтение списков пакетов… Готово
  Построение дерева зависимостей
  Чтение информации о состоянии… Готово
  E: Не удалось найти пакет gnome-recipes

  произвёл установку через software-center

  gnome-recipes
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  ubuntu-bug gnome-recipes
  dpkg-query: шаблону gnome-recipes не соответствует ни один пакет
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ^C^Z
  [1]+  Остановлено  ubuntu-bug gnome-recipes

  https://youtu.be/AXtR5m2uqUg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-center (not installed)
  Uname: Linux 4.14.0-041400rc7-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov  2 08:06:48 2017
  InstallationDate: Installed on 2017-10-29 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1729491/+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 1761719] [NEW] [Vostro 3559, Realtek ALC255, Speaker, Internal] No sound at all

[NIKHIL SANJAY JADHAV]

Public bug reported:

1) NO sound output ..!!!
2) NO sound output with headphone ..!!!

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
Uname: Linux 3.11.0-26-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.11.0-26-generic.
ApportVersion: 2.0.1-0ubuntu17.15
Architecture: i386
ArecordDevices:
  List of CAPTURE Hardware Devices 
 card 0: Intel [HDA Intel], device 0: ALC255 Analog [ALC255 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nikhil 2318 F pulseaudio
 /dev/snd/pcmC0D0p:   nikhil 2318 F...m pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd122 irq 140'
   Mixer name   : 'Intel ID 2809'
   Components   : 'HDA:10ec0255,102806c2,0012 
HDA:80862809,80860101,0010'
   Controls  : 24
   Simple ctrls  : 9
Date: Fri Apr  6 15:08:15 2018
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_AlsaPlaybackTestStderr:
 W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
  x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   e 
r r o r 
  T r a n s f e r   f a i l e d :   O p e r a t i o n   n o t   p e r m i t t e 
d
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 2318  2318  nikhilF pulseaudio
 /dev/snd/pcmC0D0p:   nikhilF...m pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Vostro 3559, Realtek ALC255, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/27/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.0
dmi.board.name: 047TR1
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd06/27/2016:svnDellInc.:pnVostro3559:pvr:rvnDellInc.:rn047TR1:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Vostro 3559
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2018-01-05T14:09:28.811626

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


** Tags: apport-bug i386 precise running-unity

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

Title:
  [Vostro 3559, Realtek ALC255, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  1) NO sound output ..!!!
  2) NO sound output with headphone ..!!!

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.11.0-26-generic.
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC255 Analog [ALC255 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikhil 2318 F pulseaudio
   /dev/snd/pcmC0D0p:   nikhil 2318 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd122 irq 140'
 Mixer name : 'Intel ID 2809'
 Components : 'HDA:10ec0255,102806c2,0012 
HDA:80862809,80860101,0010'
 Controls  : 24
 Simple ctrls  : 9
  Date: Fri Apr  6 15:08:15 2018
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_AlsaPlaybackTestStderr:
   W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   
e r r o r 
T r a n s f e r   f a i l e d :   O p e r a t i o n   n o t   p e r m i t t 
e d
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   2318  2318  nikhilF pulseaudio
   /dev/snd/pcmC0D0p:   nikhilF...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Vostro 3559, Realtek ALC255, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios

[Touch-packages] [Bug 1756006] Re: FFe: Support suspend-then-hibernate

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 237-3ubuntu7

---
systemd (237-3ubuntu7) bionic; urgency=medium

  * Introduce suspend then hibernate (LP: #1756006)

 -- Mario Limonciello   Mon, 02 Apr 2018
14:25:04 -0500

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

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

Title:
  FFe: Support suspend-then-hibernate

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Suspend to hibernate is a new feature that will put the system into
  hibernate after a period of time spent in the system's supported sleep
  state.  This mode will be used on some systems that take suspend to
  idle in the future with Ubuntu 18.04.

  This feature is available in upstream systemd from these two commits.
  
https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703
  
https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5
  This is accepted upstream.

  The policy needs to be made available to gnome from this commit:
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9
  As of 3/15/2018 this is not yet accepted or rejected.

  The new mode is not selected by default, but that can be changed from a 
separate policy package.
  The policy for the amount of time spent in S3/S2I can be configured by a 
separate package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+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 1761630] Re: journald takes over /dev/log in bionic, impacts usability of syslog querying

[Launchpad Bug Tracker]

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

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

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

Title:
  journald takes over /dev/log in bionic, impacts usability of syslog
  querying

Status in rsyslog package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in rsyslog source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  In bionic, /dev/log is now owned by systemd-journald.

  $ sudo fuser -v /dev/log 
   USERPID ACCESS COMMAND
  /run/systemd/journal/dev-log:
   root  1 F systemd
   root628 F systemd-journal
  $

  This is ok; there are good reasons to want to do this.  (Timestamp
  precision that's not dependent on the syslog protocol; logging
  available earlier in boot and later at shutdown; unified queriability
  of logs around services.)

  The logfiles previously populated by rsyslog under /var/log are now
  empty (no longer being updated, and the previous files logrotated
  away):

  $ ls -l /var/log/auth.log
  -rw-r- 1 syslog adm 0 Mar 25 00:06 /var/log/auth.log
  $

  This is also ok, we don't really want log data duplicated in two
  places on the system; so since we now have persistent journal under
  /var/log/journal, we don't want to also create these plaintext files
  by default.

  However, it's not clear that this is by design, rather than by
  accident.  rsyslog is still /configured/ to log to these files; it
  just isn't receiving any data because it no longer controls the
  socket.

  $ sudo lsof -p 852|grep DGRAM
  rsyslogd 852 syslog3u  unix 0x8e5680435000  0t0351 
/run/systemd/journal/syslog type=DGRAM
  $

  Dimitri and I have discussed that rsyslog should continue to function,
  so that users who have remote syslogging configured can still make use
  of this.  It looks like currently this is not the case, because
  journald is not forwarding to rsyslog.

  That is not ok.

  What is also not ok is that, now that logs are only being written to
  the journal by default instead of to syslog files, querying these logs
  by syslog priority only works if you know the syslog facility by
  number (and, afaics, you can only filter by one syslog facility at a
  time).  So whereas before, you could find mail logs by looking in
  /var/log/mail.log by default, you now have to know to run 'journalctl
  SYSLOG_FACILITY=2'; and if you want a view of what was previously in
  /var/log/syslog (i.e. filtering out non-syslog systemd logs, it seems
  the most compact way to express this is 'journalctl --system
  SYSLOG_FACILITY={0,1,2,3,5,6,7,8,9,11,12,13,14,15,16,17,18,19,20,21,22,23}'.

  This is really not good.  Admins have never needed to know the mapping
  of symbolic names to facility numbers to work with syslog; this throws
  away 30 years of convention with log handling.

  If we are going to store the logs in the journal by default, I think
  there needs to be a way to query the logs using symbolic names
  consistent with syslog(3) and /etc/rsyslog.d/50-default.conf.

  I don't think we can release with things in the current state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1761630/+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 1761630] Re: journald takes over /dev/log in bionic, impacts usability of syslog querying

[Launchpad Bug Tracker]

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

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

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

Title:
  journald takes over /dev/log in bionic, impacts usability of syslog
  querying

Status in rsyslog package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in rsyslog source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  In bionic, /dev/log is now owned by systemd-journald.

  $ sudo fuser -v /dev/log 
   USERPID ACCESS COMMAND
  /run/systemd/journal/dev-log:
   root  1 F systemd
   root628 F systemd-journal
  $

  This is ok; there are good reasons to want to do this.  (Timestamp
  precision that's not dependent on the syslog protocol; logging
  available earlier in boot and later at shutdown; unified queriability
  of logs around services.)

  The logfiles previously populated by rsyslog under /var/log are now
  empty (no longer being updated, and the previous files logrotated
  away):

  $ ls -l /var/log/auth.log
  -rw-r- 1 syslog adm 0 Mar 25 00:06 /var/log/auth.log
  $

  This is also ok, we don't really want log data duplicated in two
  places on the system; so since we now have persistent journal under
  /var/log/journal, we don't want to also create these plaintext files
  by default.

  However, it's not clear that this is by design, rather than by
  accident.  rsyslog is still /configured/ to log to these files; it
  just isn't receiving any data because it no longer controls the
  socket.

  $ sudo lsof -p 852|grep DGRAM
  rsyslogd 852 syslog3u  unix 0x8e5680435000  0t0351 
/run/systemd/journal/syslog type=DGRAM
  $

  Dimitri and I have discussed that rsyslog should continue to function,
  so that users who have remote syslogging configured can still make use
  of this.  It looks like currently this is not the case, because
  journald is not forwarding to rsyslog.

  That is not ok.

  What is also not ok is that, now that logs are only being written to
  the journal by default instead of to syslog files, querying these logs
  by syslog priority only works if you know the syslog facility by
  number (and, afaics, you can only filter by one syslog facility at a
  time).  So whereas before, you could find mail logs by looking in
  /var/log/mail.log by default, you now have to know to run 'journalctl
  SYSLOG_FACILITY=2'; and if you want a view of what was previously in
  /var/log/syslog (i.e. filtering out non-syslog systemd logs, it seems
  the most compact way to express this is 'journalctl --system
  SYSLOG_FACILITY={0,1,2,3,5,6,7,8,9,11,12,13,14,15,16,17,18,19,20,21,22,23}'.

  This is really not good.  Admins have never needed to know the mapping
  of symbolic names to facility numbers to work with syslog; this throws
  away 30 years of convention with log handling.

  If we are going to store the logs in the journal by default, I think
  there needs to be a way to query the logs using symbolic names
  consistent with syslog(3) and /etc/rsyslog.d/50-default.conf.

  I don't think we can release with things in the current state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1761630/+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 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged

[Dimitri John Ledkov]

@dino99

Please specify version of systemd installed, e.g. $ dpkg -l systemd

Please attach the output of $ networkctl

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

Title:
  systemd-networkd-wait-online waits when devices are unmanaged

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  I started a system with cloud-init disabled, etc. and a single real
  network interface (ens3) that could be configured.

  That VM has no configuration whatsoever for systemd-networkd, as that
  would have to have been written by netplan, and cloud-init did not
  generate netplan config (because it was disabled).

  So:

  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  d-networkd-wait-online --ignore=lo
  ignoring: lo
  Event loop failed: Connection timed out
  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl
  IDX LINK TYPE   OPERATIONAL SETUP 
1 lo   loopback   carrier unmanaged 
2 ens3 ether  off unmanaged 
3 sit0 sitoff unmanaged 

  3 links listed.
  root@ubuntu:/etc/systemd/system/network-online.target.wants# 

  
  The system took 120 seconds to complete boot, because wait-online had to 
finish; and running wait-online from the system afterwards also waits 120 
seconds (its default timeout). If there is no configuration for an interface, 
it's unmanaged (as shown by networkctl), so wait-online should not wait, and 
simply report that all interfaces are unmanaged, possibly returning an error so 
we don't reach network-online.

  FWIW, having wait-online look up configuration might later be useful
  also to figure out if an interface was configured, but marked as
  optional (such that it is explicitly not required to be up at boot),
  or if we want to configure network devices but specify that networkd
  should *not* bring them online (like "administratively disabled"
  interfaces in Cisco world using the "shutdown" command).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+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 1760106] Re: FFe: Enable configuring resume offset via sysfs

[Andy Whitcroft]

As this is 4.17 only I assume we will have to backport this for the
kernel.  Asking one of the  kernel-team folk to review that.  Also how
close is pottering to accepting the systemd changes.  As it seems we
need all three bits ready.

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

Title:
  FFe: Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  New
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1760106/+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 1735218] Re: Real connectivity error is hidden from a user when PPA is added: ERROR: '~anonymous' user or team does not exist.

[Dmitrii Shcherbakov]

** Description changed:

  This is common in an environment where a proxy server is not properly
  configured via HTTP_PROXY or HTTPS_PROXY and you need to add a PPA.
  
  The error is very cryptic unless you look at the code:
  
  sudo add-apt-repository ppa:anonymous/very-important-packages
  Cannot add PPA: 'ppa:~anonymous/ubuntu/very-important-packages'.
  ERROR: '~anonymous' user or team does not exist.
  
- 
  Code path:
  
  https://git.launchpad.net/~usd-import-team/ubuntu/+source/software-
- properties/tree/softwareproperties/ppa.py?h=applied/ubuntu/xenial-
- updates#n305
+ properties/tree/softwareproperties/ppa.py?h=ubuntu/xenial-updates#n305
  
  def _get_suggested_ppa_message(user, ppa_name):
- try:
- msg = []
- try:
- try:
- lp_user = get_info_from_lp(LAUNCHPAD_USER_API % user)
- except PPAException:
- return _("ERROR: '{user}' user or team does not 
exist.").format(user=user) # <--- this is triggered
+ try:
+ msg = []
+ try:
+ try:
+ lp_user = get_info_from_lp(LAUNCHPAD_USER_API % user)
+ except PPAException:
+ return _("ERROR: '{user}' user or team does not 
exist.").format(user=user) # <--- this is triggered
  
  def get_info_from_lp(lp_url):
- if NEED_PYCURL:
- # python2 has no cert verification so we need pycurl
- return _get_https_content_pycurl(lp_url)
- else:
- # python3 has cert verification so we can use the buildin urllib
- return _get_https_content_py3(lp_url)
+ if NEED_PYCURL:
+ # python2 has no cert verification so we need pycurl
+ return _get_https_content_pycurl(lp_url)
+ else:
+ # python3 has cert verification so we can use the buildin urllib
+ return _get_https_content_py3(lp_url)
  
  ...
  
  def _get_https_content_pycurl(lp_url):
- # this is the fallback code for python2
- try:
- callback = CurlCallback()
- curl = pycurl.Curl()
- curl.setopt(pycurl.SSL_VERIFYPEER, 1)
- curl.setopt(pycurl.SSL_VERIFYHOST, 2)
- curl.setopt(pycurl.WRITEFUNCTION, callback.body_callback)
- if LAUNCHPAD_PPA_CERT:
- curl.setopt(pycurl.CAINFO, LAUNCHPAD_PPA_CERT)
- curl.setopt(pycurl.URL, str(lp_url))
- curl.setopt(pycurl.HTTPHEADER, ["Accept: application/json"])
- curl.perform()
- curl.close()
- json_data = callback.contents
- except pycurl.error as e: # <--- if this errors out due to connectivity
- raise PPAException("Error reading %s: %s" % (lp_url, e), e)
- return json.loads(json_data)
+ # this is the fallback code for python2
+ try:
+ callback = CurlCallback()
+ curl = pycurl.Curl()
+ curl.setopt(pycurl.SSL_VERIFYPEER, 1)
+ curl.setopt(pycurl.SSL_VERIFYHOST, 2)
+ curl.setopt(pycurl.WRITEFUNCTION, callback.body_callback)
+ if LAUNCHPAD_PPA_CERT:
+ curl.setopt(pycurl.CAINFO, LAUNCHPAD_PPA_CERT)
+ curl.setopt(pycurl.URL, str(lp_url))
+ curl.setopt(pycurl.HTTPHEADER, ["Accept: application/json"])
+ curl.perform()
+ curl.close()
+ json_data = callback.contents
+ except pycurl.error as e: # <--- if this errors out due to connectivity
+ raise PPAException("Error reading %s: %s" % (lp_url, e), e)
+ return json.loads(json_data)

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

Title:
  Real connectivity error is hidden from a user when PPA is added:
  ERROR: '~anonymous' user or team does not exist.

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  This is common in an environment where a proxy server is not properly
  configured via HTTP_PROXY or HTTPS_PROXY and you need to add a PPA.

  The error is very cryptic unless you look at the code:

  sudo add-apt-repository ppa:anonymous/very-important-packages
  Cannot add PPA: 'ppa:~anonymous/ubuntu/very-important-packages'.
  ERROR: '~anonymous' user or team does not exist.

  Code path:

  https://git.launchpad.net/~usd-import-team/ubuntu/+source/software-
  properties/tree/softwareproperties/ppa.py?h=ubuntu/xenial-updates#n305

  def _get_suggested_ppa_message(user, ppa_name):
  try:
  msg = []
  try:
  try:
  lp_user = get_info_from_lp(LAUNCHPAD_USER_API % user)
  except PPAException:
  return _("ERROR: '{user}' user or team does not 
exist.").format(user=user) # <--- this is triggered
  
  def get_info_from_lp(lp_url):
  if NEED_PYCURL:
  # python2 has no cert verification so we need pycurl
  return _get_https_content_pycurl(lp_url)
  else:
  # python3 has cert verification so we can use the bu

[Touch-packages] [Bug 1735218] Re: Real connectivity error is hidden from a user when PPA is added: ERROR: '~anonymous' user or team does not exist.

[Launchpad Bug Tracker]

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

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

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

Title:
  Real connectivity error is hidden from a user when PPA is added:
  ERROR: '~anonymous' user or team does not exist.

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  This is common in an environment where a proxy server is not properly
  configured via HTTP_PROXY or HTTPS_PROXY and you need to add a PPA.

  The error is very cryptic unless you look at the code:

  sudo add-apt-repository ppa:anonymous/very-important-packages
  Cannot add PPA: 'ppa:~anonymous/ubuntu/very-important-packages'.
  ERROR: '~anonymous' user or team does not exist.

  Code path:

  https://git.launchpad.net/~usd-import-team/ubuntu/+source/software-
  properties/tree/softwareproperties/ppa.py?h=ubuntu/xenial-updates#n305

  def _get_suggested_ppa_message(user, ppa_name):
  try:
  msg = []
  try:
  try:
  lp_user = get_info_from_lp(LAUNCHPAD_USER_API % user)
  except PPAException:
  return _("ERROR: '{user}' user or team does not 
exist.").format(user=user) # <--- this is triggered
  
  def get_info_from_lp(lp_url):
  if NEED_PYCURL:
  # python2 has no cert verification so we need pycurl
  return _get_https_content_pycurl(lp_url)
  else:
  # python3 has cert verification so we can use the buildin urllib
  return _get_https_content_py3(lp_url)

  ...

  def _get_https_content_pycurl(lp_url):
  # this is the fallback code for python2
  try:
  callback = CurlCallback()
  curl = pycurl.Curl()
  curl.setopt(pycurl.SSL_VERIFYPEER, 1)
  curl.setopt(pycurl.SSL_VERIFYHOST, 2)
  curl.setopt(pycurl.WRITEFUNCTION, callback.body_callback)
  if LAUNCHPAD_PPA_CERT:
  curl.setopt(pycurl.CAINFO, LAUNCHPAD_PPA_CERT)
  curl.setopt(pycurl.URL, str(lp_url))
  curl.setopt(pycurl.HTTPHEADER, ["Accept: application/json"])
  curl.perform()
  curl.close()
  json_data = callback.contents
  except pycurl.error as e: # <--- if this errors out due to connectivity
  raise PPAException("Error reading %s: %s" % (lp_url, e), e)
  return json.loads(json_data)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1735218/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Bret Ancowitz]

Same issue with Nvidia 390 with Ubuntu Budgie 18.04 beta 2, with an
MX-150 Nvidia on a Xiaomi Air 13.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1760598] Re: I/O Error after clicking "reboot now" - Ubuntu font missing from casper shutdown

[Harald Sitter]

As explained in Bug #1761478 that would still leave timing issues. With
--ping not blocking anymore casper-stop can shoot right past the prompt
code on account of --ping coming back !0 (if plymouth isn't quick enough
to start anyway). Meaning the user doesn't get told to remove the
installation medium.

e.g. this is what I get in a VM now
http://people.ubuntu.com/~apachelogger/screencasts/vokoscreen-2018-04-06_13-40-13.mkv

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

Title:
  I/O Error after clicking "reboot now" - Ubuntu font missing from
  casper shutdown

Status in ubuntu-mate:
  Invalid
Status in casper package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-mate-welcome package in Ubuntu:
  Invalid

Bug description:
  ubuntu Plymouth theme now correctly uses Ubuntu font, meaning it needs
  to be cached for display of the shutdown message.

  We really should be using shutdown initramfs on the livecd

  --

  Tested in Virtualbox VM.
  Ubuntu MATE works after force-reboot, but after I click on "restart now" 
after completing the installation, the screen shows me this:

  req_error: I/O error, dev sr0, sector 1488792

  And the above message loops a couple times, and wont turn off the
  computer to restart.

  No error happens after force reboot, and the OS boots properly, but
  I'm curious as to what's causing this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1760598/+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 1438014] Re: gnome-terminal-server and mate-terminal crash when setting keyboard shortcuts

[André Cruz]

Altered keyboard shortcuts for opening new terminals and copy/paste.

[11742.029806] gnome-terminal-[4755]: segfault at 7001e ip 7f82140be77e 
sp 7ffce1ff6fe8 error 4 in libgobject-2.0.so.0.5400.1[7f8214089000+52000]
[11785.274354] gnome-terminal-[27857]: segfault at 7001e ip 
7fdbbe5da77e sp 7ffee0b8a418 error 4 in 
libgobject-2.0.so.0.5400.1[7fdbbe5a5000+52000]
[12226.667034] gnome-terminal-[27916]: segfault at 7001e ip 
7fe13759c77e sp 7ffd2f2b76b8 error 4 in 
libgobject-2.0.so.0.5400.1[7fe137567000+52000]

17.10 (Artful Aardvark)

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

Title:
  gnome-terminal-server and mate-terminal crash when setting keyboard
  shortcuts

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  I put my laptop to sleep for an hour or so; when I restored it, gnome-
  terminal had crashed. It did not do this the previous time I suspended
  my laptop today, so I doubt that's immediately related.

  This crash can be reproduced by setting a shortcut in preferences.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gnome-terminal 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 30 00:19:43 2015
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2014-02-03 (419 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f98e2afbf1f :
testb  $0x4,0x16(%rax)
   PC (0x7f98e2afbf1f) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0xbcae) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel (widget=0x2580c30) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwidget.c:11382
   window_group_cleanup_grabs (group=, 
window=window@entry=0x252a230) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:110
   gtk_window_group_add_window (window_group=0x27e5c40, window=0x252a230) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:169
   gtk_window_set_transient_for (window=0x252a230, parent=0x23ac7d0) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindow.c:3134
  Title: gnome-terminal-server crashed with SIGSEGV in 
g_type_check_instance_is_a()
  UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago)
  UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare 
sbuild sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1438014/+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 1538284] Re: [SRU] Unescaped left brace in regex is deprecated

[Eric Desrochers]

** Description changed:

  [Impact]
  
  When installing postgresql, many warning msgs are raised
  Please refer to Original Description
  
  ## Corrections
  In trusty, escaping is missing but not the same symptome. NOT AFFECTED TO 
TRUSTY
  
  [Test Case]
  
  1. create ubuntu instance
  2. apt install postgresql
  
  [Regression Potentials]
  This change is quite small(just escaping), and it is not code changes but 
getenv script which made by debian. so risk is minimal in my opinion.
  
  [Original Description]
  
  When installing postgresql on Ubuntu 16.04 (xenial), the following
  warning are raised:
  
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/(?https://bugs.launchpad.net/bugs/1538284

Title:
  [SRU] Unescaped left brace in regex is deprecated

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Trusty:
  Won't Fix
Status in pam source package in Xenial:
  In Progress
Status in pam source package in Artful:
  In Progress
Status in pam package in Debian:
  Fix Released

Bug description:
  [Impact]

  When installing postgresql, many warning msgs are raised
  Please refer to Original Description

  ## Corrections
  In trusty, escaping is missing but not the same symptom. NOT AFFECTED TO 
TRUSTY

  [Test Case]

  1. create ubuntu instance
  2. apt install postgresql

  [Regression Potentials]
  This change is quite small(just escaping), and it is not code changes but 
getenv script which made by debian. so risk is minimal in my opinion.

  [Other info]

  Debian Bugs:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810873
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815595

  [Original Description]

  When installing postgresql on Ubuntu 16.04 (xenial), the following
  warning are raised:

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/(?https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1538284/+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 1538284] Re: [SRU] Unescaped left brace in regex is deprecated

[Eric Desrochers]

** Description changed:

  [Impact]
  
  When installing postgresql, many warning msgs are raised
  Please refer to Original Description
  
  ## Corrections
  In trusty, escaping is missing but not the same symptome. NOT AFFECTED TO 
TRUSTY
  
  [Test Case]
  
  1. create ubuntu instance
  2. apt install postgresql
  
  [Regression Potentials]
  This change is quite small(just escaping), and it is not code changes but 
getenv script which made by debian. so risk is minimal in my opinion.
  
  [Original Description]
  
  When installing postgresql on Ubuntu 16.04 (xenial), the following
  warning are raised:
  
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/(? Medium

** Changed in: pam (Ubuntu Artful)
   Importance: Undecided => Medium

** Description changed:

  [Impact]
  
  When installing postgresql, many warning msgs are raised
  Please refer to Original Description
  
  ## Corrections
- In trusty, escaping is missing but not the same symptome. NOT AFFECTED TO 
TRUSTY
+ In trusty, escaping is missing but not the same symptom. NOT AFFECTED TO 
TRUSTY
  
  [Test Case]
  
  1. create ubuntu instance
  2. apt install postgresql
  
  [Regression Potentials]
  This change is quite small(just escaping), and it is not code changes but 
getenv script which made by debian. so risk is minimal in my opinion.
+ 
+ [Other info]
+ 
+ Debian Bugs:
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810873
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815595
  
  [Original Description]
  
  When installing postgresql on Ubuntu 16.04 (xenial), the following
  warning are raised:
  
  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/(?https://bugs.launchpad.net/bugs/1538284

Title:
  [SRU] Unescaped left brace in regex is deprecated

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Trusty:
  Won't Fix
Status in pam source package in Xenial:
  In Progress
Status in pam source package in Artful:
  In Progress
Status in pam package in Debian:
  Fix Released

Bug description:
  [Impact]

  When installing postgresql, many warning msgs are raised
  Please refer to Original Description

  ## Corrections
  In trusty, escaping is missing but not the same symptom. NOT AFFECTED TO 
TRUSTY

  [Test Case]

  1. create ubuntu instance
  2. apt install postgresql

  [Regression Potentials]
  This change is quite small(just escaping), and it is not code changes but 
getenv script which made by debian. so risk is minimal in my opinion.

  [Other info]

  Debian Bugs:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810873
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815595

  [Original Description]

  When installing postgresql on Ubuntu 16.04 (xenial), the following
  warning are raised:

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/(?https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1538284/+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 1761630] Re: journald takes over /dev/log in bionic, impacts usability of syslog querying

[Francis Ginther]

** Tags added: id-5ac6b878dbf324d2105d5891

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

Title:
  journald takes over /dev/log in bionic, impacts usability of syslog
  querying

Status in rsyslog package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in rsyslog source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  In bionic, /dev/log is now owned by systemd-journald.

  $ sudo fuser -v /dev/log 
   USERPID ACCESS COMMAND
  /run/systemd/journal/dev-log:
   root  1 F systemd
   root628 F systemd-journal
  $

  This is ok; there are good reasons to want to do this.  (Timestamp
  precision that's not dependent on the syslog protocol; logging
  available earlier in boot and later at shutdown; unified queriability
  of logs around services.)

  The logfiles previously populated by rsyslog under /var/log are now
  empty (no longer being updated, and the previous files logrotated
  away):

  $ ls -l /var/log/auth.log
  -rw-r- 1 syslog adm 0 Mar 25 00:06 /var/log/auth.log
  $

  This is also ok, we don't really want log data duplicated in two
  places on the system; so since we now have persistent journal under
  /var/log/journal, we don't want to also create these plaintext files
  by default.

  However, it's not clear that this is by design, rather than by
  accident.  rsyslog is still /configured/ to log to these files; it
  just isn't receiving any data because it no longer controls the
  socket.

  $ sudo lsof -p 852|grep DGRAM
  rsyslogd 852 syslog3u  unix 0x8e5680435000  0t0351 
/run/systemd/journal/syslog type=DGRAM
  $

  Dimitri and I have discussed that rsyslog should continue to function,
  so that users who have remote syslogging configured can still make use
  of this.  It looks like currently this is not the case, because
  journald is not forwarding to rsyslog.

  That is not ok.

  What is also not ok is that, now that logs are only being written to
  the journal by default instead of to syslog files, querying these logs
  by syslog priority only works if you know the syslog facility by
  number (and, afaics, you can only filter by one syslog facility at a
  time).  So whereas before, you could find mail logs by looking in
  /var/log/mail.log by default, you now have to know to run 'journalctl
  SYSLOG_FACILITY=2'; and if you want a view of what was previously in
  /var/log/syslog (i.e. filtering out non-syslog systemd logs, it seems
  the most compact way to express this is 'journalctl --system
  SYSLOG_FACILITY={0,1,2,3,5,6,7,8,9,11,12,13,14,15,16,17,18,19,20,21,22,23}'.

  This is really not good.  Admins have never needed to know the mapping
  of symbolic names to facility numbers to work with syslog; this throws
  away 30 years of convention with log handling.

  If we are going to store the logs in the journal by default, I think
  there needs to be a way to query the logs using symbolic names
  consistent with syslog(3) and /etc/rsyslog.d/50-default.conf.

  I don't think we can release with things in the current state.

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

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

Re: [Touch-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

[Doug McMahon]

On 04/04/2018 11:11 PM, Daniel van Vugt wrote:
> My comment in #27 was current for daily images up to a few days ago.
>
> Today I am using image 20180404 and can't reproduce the issue. So
> Incomplete.
>
> Like Doug I do find many systems still hang instead of shutting down
> with 20180404, but there are different reasons for those and the error
> message this bug is about does not appear. So they should be different
> bugs.
>
>
> ** Changed in: systemd (Ubuntu Bionic)
> Status: Confirmed => Incomplete
>
Haven't tried todays image but noticed with 20180404 that when it hangs 
at 'splash' screen that going to tty1 & using ctrl+c allows the 
shutdown/restart to proceed to completion.

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

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (21s / no limit)"

Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in gdm3 source package in Bionic:
  Incomplete
Status in systemd source package in Bionic:
  Incomplete

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:

  [ ***  ] (2 of 2) A start job is running for Hold until boot process
  finishes up (21s / no limit)

  or

  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1706939/+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 1538284] Re: [SRU] Unescaped left brace in regex is deprecated

[Eric Desrochers]

Sponsored for Xenial, it is now waiting for approval by SRU team.

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

Title:
  [SRU] Unescaped left brace in regex is deprecated

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Trusty:
  Won't Fix
Status in pam source package in Xenial:
  In Progress
Status in pam source package in Artful:
  In Progress
Status in pam package in Debian:
  Fix Released

Bug description:
  [Impact]

  When installing postgresql, many warning msgs are raised
  Please refer to Original Description

  ## Corrections
  In trusty, escaping is missing but not the same symptom. NOT AFFECTED TO 
TRUSTY

  [Test Case]

  1. create ubuntu instance
  2. apt install postgresql

  [Regression Potentials]
  This change is quite small(just escaping), and it is not code changes but 
getenv script which made by debian. so risk is minimal in my opinion.

  [Other info]

  Debian Bugs:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810873
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815595

  [Original Description]

  When installing postgresql on Ubuntu 16.04 (xenial), the following
  warning are raised:

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/(?https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1538284/+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 1760308] Re: Unicode input not working on Bionic with CTRL-SHIFT-U

[Launchpad Bug Tracker]

This bug was fixed in the package ibus - 1.5.17-3ubuntu3

---
ibus (1.5.17-3ubuntu3) bionic; urgency=medium

  * debian/patches/ubuntu-conditional-chmod.patch: backport an upstream commit
to make a call to chmod conditional, to avoid apparmor denials for confined
apps (e.g. snaps) that use libibus (LP: #1761585)

ibus (1.5.17-3ubuntu2) bionic; urgency=medium

  * debian/patches/ubuntu-unicode-keybinding.patch:
- use a change proposed/rejected upstream to restore ctrl-shift-u,
  upstream consider it superseeded by the emoji selector but that has
  no keybinding in our ibus version and is not an exact replacement
  (lp: #1760308)

 -- Olivier Tilloy   Fri, 06 Apr 2018
11:04:22 +0200

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

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

Title:
  Unicode input not working on Bionic with CTRL-SHIFT-U

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Bionic:
  Fix Released

Bug description:
  I need to enter Unicode with Unicode escape codes and the Ubuntu
  prescribed way is to use CTRL-SHIFT-U and then enter some numbers to
  input.  This doesn't do anything in the Ubuntu Bionic beta.

  Potentially related the ALT-TAB window switching is delayed in
  recognizing the occurrence of the keys being pressed such that I have
  to hold ALT-TAB instead of quickly hitting both simultaneously.

  This is from a system that was upgraded from a previous Ubuntu version
  without any issues.

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  The "Affects" package may not be accurate as I don't know what the
  cause application is for this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1760308/+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 1761585] Re: ibus_bus_init does an unconditional call to chmod on $HOME/.config/ibus/bus

[Launchpad Bug Tracker]

This bug was fixed in the package ibus - 1.5.17-3ubuntu3

---
ibus (1.5.17-3ubuntu3) bionic; urgency=medium

  * debian/patches/ubuntu-conditional-chmod.patch: backport an upstream commit
to make a call to chmod conditional, to avoid apparmor denials for confined
apps (e.g. snaps) that use libibus (LP: #1761585)

ibus (1.5.17-3ubuntu2) bionic; urgency=medium

  * debian/patches/ubuntu-unicode-keybinding.patch:
- use a change proposed/rejected upstream to restore ctrl-shift-u,
  upstream consider it superseeded by the emoji selector but that has
  no keybinding in our ibus version and is not an exact replacement
  (lp: #1760308)

 -- Olivier Tilloy   Fri, 06 Apr 2018
11:04:22 +0200

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

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

Title:
  ibus_bus_init does an unconditional call to chmod on
  $HOME/.config/ibus/bus

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  This was spotted by jdstrand when running the chromium snap, which
  recently enabled ibus support (https://forum.snapcraft.io/t/cant-use-
  input-method-in-snap-apps/4712/12):

  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000

  The code that calls chmod is in ibus_bus_init:

static void
ibus_bus_init (IBusBus *bus)
{
  gchar *path;
  […]
  path = g_path_get_dirname (ibus_get_socket_path ());
  g_mkdir_with_parents (path, 0700);
  g_chmod (path, 0700);
  […]
}

  This could be avoided by checking first the file mode bits on that
  directory, and do the g_chmod call only if ≠ 0700.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  5 21:55:30 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (642 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1761585/+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 1717769] Re: day of week in german despite i configured the system in english

[Anthony Harrington]

Think this is a bug in the language/locale selecting mechanism rather
than anything english language related.

** Package changed: language-pack-en (Ubuntu) => localechooser (Ubuntu)

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

Title:
  day of week in german despite i configured the system in english

Status in localechooser package in Ubuntu:
  Incomplete

Bug description:
  Description
  ---
  I chose the english language and live in Belgium. So I chose Brussels for the 
Time Zone, and the Belgian keymap.

  The Ubuntu date & time applet, in the top bar of the Ubuntu desktop
  interface shows me "Son HH:MM", Son standing for "Sonntag" which is
  german. I don't get why there is german in my interface since I
  configured this language nowhere but English.

  Expected Behavior
  --
  Having the day of week in English.

  My configuration to reproduce the problem
  -
  Here is the region & language configuration as seen in the settings pannel:
  Language: English (United States)
  Formats : Belgien
  Input Sources: Belgian

  In the "Date & Time" settings:
  Time Zone: CEST (Brussels, Belgium)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/localechooser/+bug/1717769/+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 1761743] [NEW] Xorg crash, session logout after screen turned off

[dreasty]

Public bug reported:

Session logout after screen turned off and also logout during work

May be related to Bug 1721428

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  6 15:52:02 2018
DistUpgraded: 2018-04-02 12:05:40,293 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 v4l2loopback, 0.10.0, 4.13.0-37-generic, x86_64: installed
 v4l2loopback, 0.10.0, 4.15.0-13-generic, x86_64: installed
 virtualbox, 5.2.8, 4.13.0-37-generic, x86_64: installed
 virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 510 
[1462:7996]
InstallationDate: Installed on 2017-03-02 (400 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1a2c:2124 China Resource Semico Co., Ltd 
 Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MSI MS-7996
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=fa8af88c-68e6-4582-872e-a2c53edcbf97 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to bionic on 2018-04-02 (4 days ago)
dmi.bios.date: 07/27/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.80
dmi.board.asset.tag: Default string
dmi.board.name: H110M PRO-VD (MS-7996)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd07/27/2016:svnMSI:pnMS-7996:pvr1.0:rvnMSI:rnH110MPRO-VD(MS-7996):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: Default string
dmi.product.name: MS-7996
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic crash third-party-packages ubuntu 
wayland-session

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

Title:
  Xorg crash, session logout after screen turned off

Status in xorg package in Ubuntu:
  New

Bug description:
  Session logout after screen turned off and also logout during work

  May be related to Bug 1721428

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 15:52:02 2018
  DistUpgraded: 2018-04-02 12:05:40,293 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback, 0.10.0, 4.13.0-37-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.15.0-13-generic, x86_64: installed
   virtualbox, 5.2.8, 4.13.0-37-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 510 
[1462:7996]
  InstallationDate: Installed on 2017-03-02 (400 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1a2c:2124 China Resource Semico Co., Ltd 
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001

[Touch-packages] [Bug 1538284] Re: [SRU] Unescaped left brace in regex is deprecated

[Eric Desrochers]

Sponsored for Artful, it is now waiting for approval by SRU team.

Note:
I had to modify the version[1] for Xenial & Artful found in both original 
.debdiff in favour of the .1 annotation, since both versions were already 
existing in the Primary Archive for Ubuntu[2]

[1] Modified version:
>From "1.1.8-3.2ubuntu3" to "1.1.8-3.2ubuntu2.1"
>From "1.1.8-3.2ubuntu4" to "1.1.8-3.2ubuntu3.1"

[2] Already existing version:
https://launchpad.net/ubuntu/+source/pam/1.1.8-3.2ubuntu3
https://launchpad.net/ubuntu/+source/pam/1.1.8-3.2ubuntu4

I also modified to d/changelog in favour of the debian changelog entry
which I think is more explanatory.

- Eric

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

Title:
  [SRU] Unescaped left brace in regex is deprecated

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Trusty:
  Won't Fix
Status in pam source package in Xenial:
  In Progress
Status in pam source package in Artful:
  In Progress
Status in pam package in Debian:
  Fix Released

Bug description:
  [Impact]

  When installing postgresql, many warning msgs are raised
  Please refer to Original Description

  ## Corrections
  In trusty, escaping is missing but not the same symptom. NOT AFFECTED TO 
TRUSTY

  [Test Case]

  1. create ubuntu instance
  2. apt install postgresql

  [Regression Potentials]
  This change is quite small(just escaping), and it is not code changes but 
getenv script which made by debian. so risk is minimal in my opinion.

  [Other info]

  Debian Bugs:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810873
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815595

  [Original Description]

  When installing postgresql on Ubuntu 16.04 (xenial), the following
  warning are raised:

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/(?https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1538284/+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 1730035] Re: Needs to depend on Python3

[Launchpad Bug Tracker]

This bug was fixed in the package xorg - 1:7.7+19ubuntu6

---
xorg (1:7.7+19ubuntu6) bionic; urgency=medium

  * control: Add python3-apport to xserver-xorg depends due to the apport hook.
(LP: #1730035)
  * control: Depend on x11proto-dev instead of the old packages.

 -- Timo Aaltonen   Thu, 05 Apr 2018 15:47:54 +0300

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

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

Title:
  Needs to depend on Python3

Status in xorg package in Ubuntu:
  Fix Released
Status in xorg source package in Artful:
  New

Bug description:
  [Impact]

  source_xorg.py apport hook does not work if python3 is not installed.

  [Test case]

  install on a clean system, check that apport-bug xorg does the right
  thing.

  [Regression potential]

  Minimal, just adds the correct dependencies that were missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1730035/+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 1727237] Re: systemd-resolved is not finding a domain

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Bionic)
   Status: Triaged => Fix Committed

** Changed in: systemd (Ubuntu Bionic)
 Assignee: Mathieu Trudel-Lapierre (cyphermox) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu Artful)
 Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Triaged
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  
  [Impact] 

   * Certain WiFi captive portals do not support EDNS0 queries, as per RFC.
   * Instead of responding with the captive portal IP address, they resond with 
domain not found
   * This prevents the user from hitting the captive portal login page, able to 
authenticate, and gain access to the internets.

  [The Fix]

   * As per tcp dumps, the problem arrises from receiving NXDOMAIN when queried 
with EDNS0
   * And receiving the right response without EDNS0
   * The solution was to downgrade transactions, and retry EDNS0 + NXDOMAIN 
result without EDNS0 with a hope of getting the right answer.

  [Test Case]

  * systemd-resolve securelogin.example.com
  * journalctl -b -u systemd-resolve | grep DVE-2018

  You should obverse that a warning message that transaction was retried
  with a reduced feature level e.g. UDP or TCP.

  After this test case is performed the result will be cached, therefore
  to revert to pristine state perform

  * systemd-resolve --flush-caches

  [Regression Potential]

   * The code retries, and then caches, NXDOMAIN results for certain
  queries (those that have 'secure' in them) with and without EDNS0.

   * Thus initial query for these domains may take longer, but hopefully
  will manage to receive the correct response.

   * Manufacturers are encouraged to correctly support EDNS0 queries,
  with flag D0 set to zero.

  [Other Info]
   
   * This issue is tracked as a dns-violation at
  
https://github.com/dns-violations/dns-violations/blob/master/2018/DVE-2018-0001.md

  [Original Bug report]

  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$

  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

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

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

[Touch-packages] [Bug 1761746] [NEW] package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: підпроцес новий pre-removal сценарій повернув статус помилку 1

[Thehansky Bogdan]

Public bug reported:

1) Description: Ubuntu 16.04.4 LTS Release: 16.04
2) Встановлено: 0.6.32~rc+dfsg-1ubuntu2
  Кандидат:0.6.32~rc+dfsg-1ubuntu2.1
  Таблиця версій:
 0.6.32~rc+dfsg-1ubuntu2.1 500
500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
 *** 0.6.32~rc+dfsg-1ubuntu2 500
500 http://ua.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status

Failed when upgrade package. The subprocess of the new pre-removal
script returned the status of the error 1.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Apr  6 15:59:47 2018
ErrorMessage: підпроцес новий pre-removal сценарій повернув статус помилку 1
InstallationDate: Installed on 2017-12-18 (109 days ago)
InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: avahi
Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: підпроцес новий pre-removal сценарій повернув статус помилку 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: підпроцес новий pre-removal сценарій повернув статус
  помилку 1

Status in avahi package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 16.04.4 LTS Release: 16.04
  2) Встановлено: 0.6.32~rc+dfsg-1ubuntu2
Кандидат:0.6.32~rc+dfsg-1ubuntu2.1
Таблиця версій:
   0.6.32~rc+dfsg-1ubuntu2.1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
   *** 0.6.32~rc+dfsg-1ubuntu2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  Failed when upgrade package. The subprocess of the new pre-removal
  script returned the status of the error 1.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Apr  6 15:59:47 2018
  ErrorMessage: підпроцес новий pre-removal сценарій повернув статус помилку 1
  InstallationDate: Installed on 2017-12-18 (109 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: підпроцес новий pre-removal сценарій повернув статус помилку 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1761746/+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 1727237] Re: systemd-resolved is not finding a domain

[Dimitri John Ledkov]

** Description changed:

+ 
+ [Impact] 
+ 
+  * Certain WiFi captive portals do not support EDNS0 queries, as per RFC.
+  * Instead of responding with the captive portal IP address, they resond with 
domain not found
+  * This prevents the user from hitting the captive portal login page, able to 
authenticate, and gain access to the internets.
+ 
+ [The Fix]
+ 
+  * As per tcp dumps, the problem arrises from receiving NXDOMAIN when queried 
with EDNS0
+  * And receiving the right response without EDNS0
+  * The solution was to downgrade transactions, and retry EDNS0 + NXDOMAIN 
result without EDNS0 with a hope of getting the right answer.
+ 
+ [Test Case]
+ 
+ * systemd-resolve securelogin.example.com
+ * journalctl -b -u systemd-resolve | grep DVE-2018
+ 
+ You should obverse that a warning message that transaction was retried
+ with a reduced feature level e.g. UDP or TCP.
+ 
+ After this test case is performed the result will be cached, therefore
+ to revert to pristine state perform
+ 
+ * systemd-resolve --flush-caches
+ 
+ [Regression Potential]
+ 
+  * The code retries, and then caches, NXDOMAIN results for certain
+ queries (those that have 'secure' in them) with and without EDNS0.
+ 
+  * Thus initial query for these domains may take longer, but hopefully
+ will manage to receive the correct response.
+ 
+  * Manufacturers are encouraged to correctly support EDNS0 queries, with
+ flag D0 set to zero.
+ 
+ [Other Info]
+  
+  * This issue is tracked as a dns-violation at
+ 
https://github.com/dns-violations/dns-violations/blob/master/2018/DVE-2018-0001.md
+ 
+ [Original Bug report]
+ 
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which is
  resolvable with nslookup. If I use nslookup against the two nameservers
  on this network I get answers for the domain, but ping says it is unable
  to resolve the same domain (as do browsers and crucially the captive
  portal mechanism).
  
  Here are details:
  
  NSLOOKUP:
  
  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53
  
  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242
  
  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53
  
  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242
  
- 
  PING:
  
  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
- mark@mark-X1Y2:~$ 
- 
+ mark@mark-X1Y2:~$
  
  DIG:
  
  ~$ dig @208.67.222.222 securelogin.arubanetworks.com
  
  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A
  
  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400
  
  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144
  
- 
  MORE DIG:
  
  ~$ dig securelogin.arubanetworks.com
  
  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
  
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A
  
  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Triaged
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  
  [Impact] 

   * Certain WiFi captive portals do not support EDNS0 queries, as per RFC.
   * Instead of responding with the captive portal IP address, they resond with 
domain not found
   * This prevents the user from hitting the captive portal login page, able to 
authenticate, and gain access to the internets.

  [The Fix]

   * As per tcp dumps, the problem arrises from receiving NXDOMAIN when queried 
with EDNS0
   * And rec

[Touch-packages] [Bug 1761754] [NEW] unmet dependencies: linux-headers-4.4.0-119-generic

[Galen Thurber]

Public bug reported:

Xubuntu 16.04 x64
system is unable to upgrade due to 
"The following packages have unmet dependencies:
 linux-headers-4.4.0-119-generic : Depends: linux-headers-4.4.0-119 but it is 
not installed
E: Unmet dependencies. Try using -f.
"

sudo dpkg --configure -a
dpkg: dependency problems prevent configuration of 
linux-headers-4.4.0-119-generic:
 linux-headers-4.4.0-119-generic depends on linux-headers-4.4.0-119; however:
  Package linux-headers-4.4.0-119 is not installed.

dpkg: error processing package linux-headers-4.4.0-119-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-headers-generic:
 linux-headers-generic depends on linux-headers-4.4.0-119-generic; however:
  Package linux-headers-4.4.0-119-generic is not configured yet.

dpkg: error processing package linux-headers-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
 linux-generic depends on linux-headers-generic (= 4.4.0.119.125); however:
  Package linux-headers-generic is not configured yet.

dpkg: error processing package linux-generic (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-headers-4.4.0-119-generic
 linux-headers-generic
 linux-generic

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

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

Title:
  unmet dependencies: linux-headers-4.4.0-119-generic

Status in apt package in Ubuntu:
  New

Bug description:
  Xubuntu 16.04 x64
  system is unable to upgrade due to 
  "The following packages have unmet dependencies:
   linux-headers-4.4.0-119-generic : Depends: linux-headers-4.4.0-119 but it is 
not installed
  E: Unmet dependencies. Try using -f.
  "

  sudo dpkg --configure -a
  dpkg: dependency problems prevent configuration of 
linux-headers-4.4.0-119-generic:
   linux-headers-4.4.0-119-generic depends on linux-headers-4.4.0-119; however:
Package linux-headers-4.4.0-119 is not installed.

  dpkg: error processing package linux-headers-4.4.0-119-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-4.4.0-119-generic; however:
Package linux-headers-4.4.0-119-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 4.4.0.119.125); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   linux-headers-4.4.0-119-generic
   linux-headers-generic
   linux-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1761754/+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 1761585] Re: ibus_bus_init does an unconditional call to chmod on $HOME/.config/ibus/bus

[Olivier Tilloy]

** Description changed:

  This was spotted by jdstrand when running the chromium snap, which
  recently enabled ibus support (https://forum.snapcraft.io/t/cant-use-
  input-method-in-snap-apps/4712/12):
  
  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000
  
  The code that calls chmod is in ibus_bus_init:
  
static void
ibus_bus_init (IBusBus *bus)
{
  gchar *path;
  […]
  path = g_path_get_dirname (ibus_get_socket_path ());
  g_mkdir_with_parents (path, 0700);
  g_chmod (path, 0700);
  […]
}
  
- This could be avoided by checking first the file mode bits on that
- directory, and do the g_chmod call only if ≠ 0700.
+ This is rather harmless, but it could be avoided by checking first the
+ file mode bits on that directory, and do the g_chmod call only if ≠
+ 0700.
+ 
+ 
+ [Impact]
+ 
+ Snaps that build on a xenial stack against libibus will trigger that apparmor 
denial, and even if actually harmless this will no doubt be reported as a 
problem by users who inspect the denials generated by their snaps.
+ The patch (that is already upstream: 
https://github.com/ibus/ibus/commit/28d0c1d4bc47beb38995d84cc4bb1d539c08a070) 
fixes that by calling chmod conditionally, only if the file mode bits on the 
ibus socket path are ≠ 0700.
+ 
+ 
+ [Test Case]
+ 
+ Install the chromium snap from the stable channel (version
+ 65.0.3325.181, revision 274 as of this writing), and monitor the system
+ journal for apparmor denials while launching it:
+ 
+ journalctl -f | grep chmod
+ 
+ Observe a denial similar to that one:
+ 
+ audit[16919]: AVC apparmor="DENIED" operation="chmod"
+ profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
+ pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
+ fsuid=1000 ouid=1000
+ 
+ Now rebuild the chromium snap with the patched libibus (this can be done
+ by downloading the .snap file, unpacking it with  unsquashfs, replacing
+ the libibus files by unpacking the updated deb, then repacking the snap
+ with `snapcraft pack`), install it and launch it while monitoring the
+ system journal.
+ 
+ Observe the denial on chmod is gone.
+ 
+ 
+ [Regression Potential]
+ 
+ This is a low-risk, self-contained change. It doesn't change the logic of 
ibus_bus_init.
+ ibus input still working in apps (both debs and snaps) should be enough to 
prove that there are no regressions.
+ 
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
- Date: Thu Apr  5 21:55:30 2018
+ Date: Thu Apr 5 21:55:30 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (642 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (66 days ago)

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

Title:
  ibus_bus_init does an unconditional call to chmod on
  $HOME/.config/ibus/bus

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  This was spotted by jdstrand when running the chromium snap, which
  recently enabled ibus support (https://forum.snapcraft.io/t/cant-use-
  input-method-in-snap-apps/4712/12):

  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000

  The code that calls chmod is in ibus_bus_init:

static void
ibus_bus_init (IBusBus *bus)
{
  gchar *path;
  […]
  path = g_path_get_dirname (ibus_get_socket_path ());
  g_mkdir_with_parents (path, 0700);
  g_chmod (path, 0700);
  […]
}

  This is rather harmless, but it could be avoided by checking first the
  file mode bits on that directory, and do the g_chmod call only if ≠
  0700.

  
  [Impact]

  Snaps that build on a xenial stack against libibus will trigger that apparmor 
denial, and even if actually harmless this will no doubt be reported as a 
problem by users who inspect the denials generated by their snaps.
  The patch (that is already upstream: 
https://github.com/ibus/ibus/commit/28d0c1d4bc47beb38995d84cc4bb1d539c08a070) 
fixes that by calling chmod conditionally, only if the file mode bits on the 
ibus socket path are ≠ 0700.

  
  [Test Case]

  Install the chromium snap from the stable channel (version
  65.0.3325.181, revision 274 as of t

[Touch-packages] [Bug 1761585] Re: ibus_bus_init does an unconditional call to chmod on $HOME/.config/ibus/bus

[Olivier Tilloy]

** Patch added: "xenial SRU debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1761585/+attachment/5104078/+files/lp1761585.debdiff

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

Title:
  ibus_bus_init does an unconditional call to chmod on
  $HOME/.config/ibus/bus

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  This was spotted by jdstrand when running the chromium snap, which
  recently enabled ibus support (https://forum.snapcraft.io/t/cant-use-
  input-method-in-snap-apps/4712/12):

  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000

  The code that calls chmod is in ibus_bus_init:

static void
ibus_bus_init (IBusBus *bus)
{
  gchar *path;
  […]
  path = g_path_get_dirname (ibus_get_socket_path ());
  g_mkdir_with_parents (path, 0700);
  g_chmod (path, 0700);
  […]
}

  This is rather harmless, but it could be avoided by checking first the
  file mode bits on that directory, and do the g_chmod call only if ≠
  0700.

  
  [Impact]

  Snaps that build on a xenial stack against libibus will trigger that apparmor 
denial, and even if actually harmless this will no doubt be reported as a 
problem by users who inspect the denials generated by their snaps.
  The patch (that is already upstream: 
https://github.com/ibus/ibus/commit/28d0c1d4bc47beb38995d84cc4bb1d539c08a070) 
fixes that by calling chmod conditionally, only if the file mode bits on the 
ibus socket path are ≠ 0700.

  
  [Test Case]

  Install the chromium snap from the stable channel (version
  65.0.3325.181, revision 274 as of this writing), and monitor the
  system journal for apparmor denials while launching it:

  journalctl -f | grep chmod

  Observe a denial similar to that one:

  audit[16919]: AVC apparmor="DENIED" operation="chmod"
  profile="snap.chromium.chromium" name="/home/osomon/.config/ibus/bus/"
  pid=16919 comm="chromium-browse" requested_mask="w" denied_mask="w"
  fsuid=1000 ouid=1000

  Now rebuild the chromium snap with the patched libibus (this can be
  done by downloading the .snap file, unpacking it with  unsquashfs,
  replacing the libibus files by unpacking the updated deb, then
  repacking the snap with `snapcraft pack`), install it and launch it
  while monitoring the system journal.

  Observe the denial on chmod is gone.

  
  [Regression Potential]

  This is a low-risk, self-contained change. It doesn't change the logic of 
ibus_bus_init.
  ibus input still working in apps (both debs and snaps) should be enough to 
prove that there are no regressions.


  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 5 21:55:30 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (642 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1761585/+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 13795] Re: base-files: Insecure PATH in /root/.profile

[Bug Watch Updater]

** Changed in: base-files (Debian)
   Status: Fix Committed => Fix Released

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

Title:
  base-files: Insecure PATH in /root/.profile

Status in base-files package in Ubuntu:
  Invalid
Status in base-files package in Debian:
  Fix Released

Bug description:
  Automatically imported from Debian bug report #299007
  http://bugs.debian.org/299007

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/13795/+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 1731522] Re: systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)

[Dimitri John Ledkov]

** Description changed:

+ [Impact]
+ 
+  * Ubuntu hosts unable to perform queries against certain domains that 
respond with too big reponses that do not fit over UDP protocol.
+  * Solution is to enable local cachine DNS server to listen on both UDP and 
TCP by default
+ 
+ [Test Case]
+ 
+  * nslookup -q= pod51041.outlook.com 127.0.0.53
+ 
+ Should work and return a bunch of ipv6 answers.
+ 
+ Note, this expects that the upstream DNS server used by resolved is "a
+ sensitble" one, e.g. my default ISP/router did not work, whilst forcing
+ 8.8.8.8 via network manager for this connection made it work.
+ 
+ [Regression Potential]
+ 
+  * Given that resolved will now bind to a TCP port 53, this may result
+ in a conflict with deployed DNS servers which do not correctly take over
+ port 53 or bind to everything.
+ 
+  * In those cases the software should be fixed to not bind to all
+ interfaces and/or to not bind on 127.0.0.53, or change resolved to have
+ DNSStubListener set to 'udp'.
+ 
+ [Other Info]
+  
+  * Original bug report
+ 
+ ===
+ 
  Trying to resolve pod51041.outlook.com's domain name seems to fail for
  applications:
  
  $ ping pod51041.outlook.com
  ping: pod51041.outlook.com: Temporary failure in name resolution
  
  (Also can't access via thunderbird).
  
  However, it seems to work directly via systemd-resolve:
  
  $ systemd-resolve pod51041.outlook.com
  pod51041.outlook.com: 40.97.160.2
    40.97.126.50
    132.245.38.194
    40.97.147.194
    132.245.41.34
    40.97.176.2
    40.97.150.242
    40.97.85.114
    40.97.120.50
    40.97.85.2
    40.97.176.34
    40.97.138.242
    40.97.166.18
    40.97.120.162
    40.97.119.82
    40.97.176.18
    40.97.85.98
    40.97.134.34
    40.97.84.18
  
  -- Information acquired via protocol DNS in 2.5ms.
  -- Data is authenticated: no
  
  It also works with dig and nslookup.
  
  Not quite sure why this is the case, I've spotted this issue upstream
  that looks similar: https://github.com/systemd/systemd/issues/6520.
  However, I'm not familiar enough with DNS to tell if it is the same
  issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Nov 10 13:10:02 2017
  InstallationDate: Installed on 2017-11-10 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  MachineType: LENOVO 2324BB9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324BB9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2324BB9
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

** Description changed:

  [Impact]
  
-  * Ubuntu hosts unable to perform queries against certain domains that 
respond with too big reponses that do not fit over UDP protocol.
-  * Solution is to enable local cachine DNS server to listen on both UDP and 
TCP by default
+  * Ubuntu hosts unable to perform queries against certain domains that 
respond with too big responses that do not fit over UDP protocol.
+  * Solution is to enable local cachine DNS server to listen on both UDP and 
TCP by default
  
  [Test Case]
  
-  * nslookup -q= pod51041.outlook.com 127.0.0.53
+  * nslookup -q= pod51041.outlook.com 127.0.0.53
  
  Should work and return a bunch of ipv6 answers.
  
  Note, this expects that the upstream DNS server used by resolved is "a
  sensitble" one, e.g. my default ISP/router did not work, whilst forcing
  8.8.8.8 via network manager for this connection made it work.
  
  [Regression Potential]
  
-  * Given that resolved will now bind to a TCP port 53, this may result
+  * Given that resolved will now bind to a TCP port 53, this may result
  in a conflict with deployed DNS servers whi

[Touch-packages] [Bug 1735929] Re: security problems with incorrect permissions for ubuntu 17.10

[Sebastien Bacher]

Change attached to the upstream bug

** Changed in: gnome-session (Ubuntu Bionic)
   Status: Triaged => In Progress

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

Title:
  security problems with incorrect permissions for ubuntu 17.10

Status in dconf:
  Confirmed
Status in gnome-session:
  Confirmed
Status in d-conf package in Ubuntu:
  Fix Released
Status in dconf package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  In Progress
Status in session-migration package in Ubuntu:
  Fix Released
Status in d-conf source package in Bionic:
  Fix Released
Status in dconf source package in Bionic:
  Triaged
Status in gnome-session source package in Bionic:
  In Progress
Status in session-migration source package in Bionic:
  Fix Released

Bug description:
  The release of Ubuntu you are using (lsb_release -rd):
  Description:  Ubuntu 17.10
  Release:  17.10

  This is a fresh installation of Ubuntu 17.10 from the mini.iso.
  I select only default options + [Ubuntu Desktop] installation.

  What you expected to happen:
  My home folder contains the following folders with correct and safe 
permissions after the first login:
  drwx-- 11 user user 4096 Dec  2 17:40 .config
  drwx--  3 user user 4096 Dec  2 17:39 .local

  What happened instead:
  I received these folders after the first login:
  drwxr-xr-x 11 user user 4096 Dec  2 17:40 .config
  drwxr-xr-x  3 user user 4096 Dec  2 17:39 .local
  It is not safe. Any user can access to my .config folders and read for 
example my mail databases

  I'm trying to create a new user...:
  sudo useradd -m user2
  sudo passwd user2
  ... and login then.
  It has the same problem:
  drwxr-xr-x 10 user2 user2 4096 Dec  2 19:44 .config
  drwxr-xr-x  3 user2 user2 4096 Dec  2 19:44 .local

To manage notifications about this bug go to:
https://bugs.launchpad.net/dconf/+bug/1735929/+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 1761763] [NEW] package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Gary Caine]

Public bug reported:

This is using 17.10 so I believe it is different than the 1633217 bug
report

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: avahi-daemon 0.6.32-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Apr  6 08:18:27 2018
DpkgHistoryLog:
 Start-Date: 2018-04-06  08:18:02
 Upgrade: libvncclient1:amd64 (0.9.11+dfsg-1, 0.9.11+dfsg-1ubuntu0.1), 
libraw16:amd64 (0.18.2-2ubuntu0.1, 0.18.2-2ubuntu0.2), libavahi-glib1:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common-data:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common3:amd64 (0.6.32-1ubuntu1, 
0.6.32-1ubuntu1.1), libavahi-ui-gtk3-0:amd64 (0.6.32-1ubuntu1, 
0.6.32-1ubuntu1.1), avahi-daemon:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), 
libavahi-core7:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), avahi-autoipd:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), python3-crypto:amd64 (2.6.1-7build2, 
2.6.1-7ubuntu0.1), avahi-utils:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), 
libavahi-client3:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), hdparm:amd64 
(9.51+ds-1, 9.51+ds-1ubuntu0.1)
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2018-01-07 (89 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: avahi
Title: package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

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

Title:
  package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  This is using 17.10 so I believe it is different than the 1633217 bug
  report

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: avahi-daemon 0.6.32-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Apr  6 08:18:27 2018
  DpkgHistoryLog:
   Start-Date: 2018-04-06  08:18:02
   Upgrade: libvncclient1:amd64 (0.9.11+dfsg-1, 0.9.11+dfsg-1ubuntu0.1), 
libraw16:amd64 (0.18.2-2ubuntu0.1, 0.18.2-2ubuntu0.2), libavahi-glib1:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common-data:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common3:amd64 (0.6.32-1ubuntu1, 
0.6.32-1ubuntu1.1), libavahi-ui-gtk3-0:amd64 (0.6.32-1ubuntu1, 
0.6.32-1ubuntu1.1), avahi-daemon:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), 
libavahi-core7:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), avahi-autoipd:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), python3-crypto:amd64 (2.6.1-7build2, 
2.6.1-7ubuntu0.1), avahi-utils:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), 
libavahi-client3:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), hdparm:amd64 
(9.51+ds-1, 9.51+ds-1ubuntu0.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-01-07 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1761763/+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 1752417] Re: Out of the box, Ubuntu Bionic offers only insecure VPN option

[Robie Basak]

Thank you for filing this bug. I agree that it's worth asking the
desktop team to consider the default set of VPN plugins available by
default from time to time.

> In fact, most major desktop OSes have removed PPTP altogether because
it's insecure...

I'm commenting because I'd like to point out that I don't think this is
a reasonable justification. Ubuntu is *user focused*. Users don't
usually have the option of choosing their VPN technology since the
server end is normally configured by someone else. Ideally I think
Ubuntu should make sure that the majority of users can connect most
easily to the VPN they already have. We should keep Ubuntu useful to the
majority of Ubuntu users by default. This should be our primary
motivator for any decision.

A secondary effect is that those in control of choosing VPN technologies
might be influenced by the availability of clients in Ubuntu as default.
It might be reasonable for us to change what we ship by default based on
this effect, but it should only be secondary to the primary cause of
shipping something useful to users.

Inconveniencing users by removing the availability of a component by
default because we think they should be using something different is not
something I think is appropriate for the Ubuntu project. I don't think
it's appropriate for us to be hostile to our users in this manner.
Ubuntu has traditionally done the exact opposite - for example by taking
the pragmatic stance in making available non-free codecs and drivers
instead of deliberately making it difficult for users who have already
made non-free hardware and codec choices such as some other
distributions.

If PPTP support is removed by default for policy (rather than technical
or maintenance) reasons, I think it be done on the basis that Ubuntu VPN
users don't need and won't miss PPTP support and not just because we
think that the users are doing it wrong.

I have no objection to bringing in other plugins for default (eg.
openvpn sounds like a great idea) but of course that is subject to a
team being prepared to commit the time to maintain that.

(I'm just an unconnected Ubuntu developer and have no say in any final
decision)

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

Title:
  Out of the box, Ubuntu Bionic offers only insecure VPN option

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager-openvpn package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  network-manager lists only PPTP as an available VPN client connection
  type (and also offers to import a file). I'd expect L2TP-over-IPSec
  and IKEv1/IKEv2 options as well.

  In fact, most major desktop OSes have removed PPTP altogether because
  it's insecure, and Ubuntu should probably do so in 18.04 as well, at
  least from the GUI!

  $ apt list network-manager
  Llistant… Fet
  network-manager/bionic,now 1.10.4-1ubuntu2 amd64 [instal·lat]

  $ uname -a
  Linux machinename 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  Codename: bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1752417/+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 1761763] Re: package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  This is using 17.10 so I believe it is different than the 1633217 bug
  report

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: avahi-daemon 0.6.32-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Apr  6 08:18:27 2018
  DpkgHistoryLog:
   Start-Date: 2018-04-06  08:18:02
   Upgrade: libvncclient1:amd64 (0.9.11+dfsg-1, 0.9.11+dfsg-1ubuntu0.1), 
libraw16:amd64 (0.18.2-2ubuntu0.1, 0.18.2-2ubuntu0.2), libavahi-glib1:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common-data:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common3:amd64 (0.6.32-1ubuntu1, 
0.6.32-1ubuntu1.1), libavahi-ui-gtk3-0:amd64 (0.6.32-1ubuntu1, 
0.6.32-1ubuntu1.1), avahi-daemon:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), 
libavahi-core7:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), avahi-autoipd:amd64 
(0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), python3-crypto:amd64 (2.6.1-7build2, 
2.6.1-7ubuntu0.1), avahi-utils:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), 
libavahi-client3:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), hdparm:amd64 
(9.51+ds-1, 9.51+ds-1ubuntu0.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-01-07 (89 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1761763/+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 1761771] [NEW] package unattended-upgrades (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

[shabeeb]

Public bug reported:

shabeebk@shabeeb:~$ sudo apt --purge remove unattended-upgrades
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED:
  unattended-upgrades*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
11 not fully installed or removed.
After this operation, 315 kB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 255908 files and directories currently installed.)
Removing unattended-upgrades (0.90ubuntu0.9) ...
Purging configuration files for unattended-upgrades (0.90ubuntu0.9) ...
insserv: warning: script 'redis_6379' missing LSB tags and overrides
insserv: There is a loop between service monit and redis_6379 if stopped
insserv:  loop involving service redis_6379 at depth 2
insserv:  loop involving service monit at depth 1
insserv: Stopping redis_6379 depends on monit and therefore on system facility 
`$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package unattended-upgrades (--purge):
 subprocess installed post-removal script returned error exit status 1
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 unattended-upgrades
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades (not installed)
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Apr  6 20:14:11 2018
ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
InstallationDate: Installed on 2017-08-22 (227 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: unattended-upgrades
Title: package unattended-upgrades (not installed) failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package unattended-upgrades (not installed) failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  shabeebk@shabeeb:~$ sudo apt --purge remove unattended-upgrades
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
unattended-upgrades*
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  11 not fully installed or removed.
  After this operation, 315 kB disk space will be freed.
  Do you want to continue? [Y/n] Y
  (Reading database ... 255908 files and directories currently installed.)
  Removing unattended-upgrades (0.90ubuntu0.9) ...
  Purging configuration files for unattended-upgrades (0.90ubuntu0.9) ...
  insserv: warning: script 'redis_6379' missing LSB tags and overrides
  insserv: There is a loop between service monit and redis_6379 if stopped
  insserv:  loop involving service redis_6379 at depth 2
  insserv:  loop involving service monit at depth 1
  insserv: Stopping redis_6379 depends on monit and therefore on system 
facility `$all' which can not be true!
  insserv: exiting now without changing boot order!
  update-rc.d: error: insserv rejected the script header
  dpkg: error processing package unattended-upgrades (--purge):
   subprocess installed post-removal script returned error exit status 1
  Processing triggers for man-db (2.7.5-1) ...
  Errors were encountered while processing:
   unattended-upgrades
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Apr  6 20:14:11 2018
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-08-22 (227 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades (not installed) failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To mana

[Touch-packages] [Bug 1761771] Re: package unattended-upgrades (not installed) failed to install/upgrade: subprocess installed post-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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1761771

Title:
  package unattended-upgrades (not installed) failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  shabeebk@shabeeb:~$ sudo apt --purge remove unattended-upgrades
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
unattended-upgrades*
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  11 not fully installed or removed.
  After this operation, 315 kB disk space will be freed.
  Do you want to continue? [Y/n] Y
  (Reading database ... 255908 files and directories currently installed.)
  Removing unattended-upgrades (0.90ubuntu0.9) ...
  Purging configuration files for unattended-upgrades (0.90ubuntu0.9) ...
  insserv: warning: script 'redis_6379' missing LSB tags and overrides
  insserv: There is a loop between service monit and redis_6379 if stopped
  insserv:  loop involving service redis_6379 at depth 2
  insserv:  loop involving service monit at depth 1
  insserv: Stopping redis_6379 depends on monit and therefore on system 
facility `$all' which can not be true!
  insserv: exiting now without changing boot order!
  update-rc.d: error: insserv rejected the script header
  dpkg: error processing package unattended-upgrades (--purge):
   subprocess installed post-removal script returned error exit status 1
  Processing triggers for man-db (2.7.5-1) ...
  Errors were encountered while processing:
   unattended-upgrades
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Apr  6 20:14:11 2018
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-08-22 (227 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades (not installed) failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1761771/+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 1761773] Re: Touch Screen stop working on 18.04 beta1

[Raul Dias]

** Attachment added: "X.org logs from 16.04 (Install Media Try Ubuntu option) 
where it works"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761773/+attachment/5104182/+files/Xorg.0.log

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

Title:
  Touch Screen stop working on 18.04 beta1

Status in xorg package in Ubuntu:
  New

Bug description:
  The touch screen on a HP TouchSmart works fine on other releases.
  On the beta of 18.04 it stopped to work.

  Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen

  On 16.04 it is recognized as TOUCHSCREEN by X.org.  
  On 18.04 beta 1, it is recognized as mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 11:39:07 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010]
  InstallationDate: Installed on 2018-04-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: HP-Pavilion FQ429AA-AC4 IQ510br
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.06
  dmi.board.name: EVE
  dmi.board.vendor: PEGATRON CORPORATION.
  dmi.board.version: 1.04
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.family: 103C_53316J
  dmi.product.name: FQ429AA-AC4 IQ510br
  dmi.sys.vendor: HP-Pavilion
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761773/+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 1761770] Re: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1761770/+attachment/5104141/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1761770/+attachment/5104144/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1761770/+attachment/5104151/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1761770/+attachment/5104153/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1761770/+attachment/5104154/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1761770/+attachment/5104155/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1761770/+attachment/5104157/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1754214

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()

Status in systemd package in Ubuntu:
  New

Bug description:
  Applying copy-paste action of documents (from host computer running
  Budgie-Ubuntu 17.10 to usb full installation running Budgie-Ubuntu
  18.04 kernal 4.15.0-15) no apparent problem noted apart from system
  problem message

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr  6 15:25:33 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-03-12 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  MachineType: TOSHIBA SATELLITE L830
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=2dc06f87-aa49-4d7c-b9d7-6b89f9320fc3 ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __GI___pthread_timedjoin_ex (threadid=140719257347840, thread_return=0x0, 
abstime=0x0, block=) at pthread_join_common.c:89
   ?? () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
  Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/08/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.40:bd01/08/2013:svnTOSHIBA:pnSATELLITEL830:pvrPSKF2E-00K00FEN:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE L830
  dmi.product.version: PSKF2E-00K00FEN
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1761770/+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 1761773] [NEW] Touch Screen stop working on 18.04 beta1

[Raul Dias]

Public bug reported:

The touch screen on a HP TouchSmart works fine on other releases.
On the beta of 18.04 it stopped to work.

Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen

On 16.04 it is recognized as TOUCHSCREEN by X.org.  
On 18.04 beta 1, it is recognized as mouse.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  6 11:39:07 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010]
InstallationDate: Installed on 2018-04-05 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
MachineType: HP-Pavilion FQ429AA-AC4 IQ510br
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/10/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.06
dmi.board.name: EVE
dmi.board.vendor: PEGATRON CORPORATION.
dmi.board.version: 1.04
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.family: 103C_53316J
dmi.product.name: FQ429AA-AC4 IQ510br
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Touch Screen stop working on 18.04 beta1

Status in xorg package in Ubuntu:
  New

Bug description:
  The touch screen on a HP TouchSmart works fine on other releases.
  On the beta of 18.04 it stopped to work.

  Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen

  On 16.04 it is recognized as TOUCHSCREEN by X.org.  
  On 18.04 beta 1, it is recognized as mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 11:39:07 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010]
  InstallationDate: Installed on 2018-04-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: HP-Pavilion FQ429AA-AC4 IQ510br
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.06
  dmi.board.name: EVE
  dmi.board.vendor: PEGATRON CORPORATION.
  dmi.board.version: 1.04
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.family: 103C_53316J
  dmi.product.name: FQ429AA-AC4 IQ510br
  dmi.sys.vendor: HP-Pavilion
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: lib

[Touch-packages] [Bug 1758314] Re: Open new windows in the middle of the screen

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-settings - 18.04.2

---
ubuntu-settings (18.04.2) bionic; urgency=medium

  [ Didier Roche ]
  * Open new windows in the middle of the screen as requested by the community
for the communitheme session. (LP: #1758314)

  [ Jeremy Bicha ]
  * Add override for gnome-initial-setup.desktop for the Ubuntu sessions with
'Welcome to Ubuntu' title and Ubuntu icon
  * Allow the new .desktop to be translated
  * Depend on gnome-control-center-data since that's where the icon is
currently installed
  * Drop the imagemagick .desktop overrides. Let's fix the issue in
imagemagick directly.

 -- Jeremy Bicha   Fri, 06 Apr 2018 08:24:28 -0400

** Changed in: ubuntu-settings (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Open new windows in the middle of the screen

Status in ubuntu-settings package in Ubuntu:
  Fix Released

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

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

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

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

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

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

[Touch-packages] [Bug 1761782] [NEW] do-release-upgrade from 12.04 to 14.04 - package linux-firmware 1.127.24 failed to install/upgrade: subprocess installed post-installation script returned error ex

[Theo]

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

Public bug reported:

Tried do-release-upgrade from 12.04 to 14.04

Not sure what is going on but doing the following on another login
screen indicates that the upgrade has occurred

cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"

Hmm /boot is 100%

apt-get autoremove

failed again after /boot filled up again
manuall removed stuff Eg.
root@host1:/boot# rm initrd.img-3.2.0-75-generic initrd.img-3.2.0-77-generic 
initrd.img-3.2.0-80-generic initrd.img-3.2.0-83-generic 
initrd.img-3.2.0-95-generic

repeated apt-get autoremove which just re-creates the above and results
in the following

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-3.13.0-145-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
No apport report written because MaxReports is reached already
  Errors were 
encountered while processing:
 linux-image-extra-3.13.0-145-generic
 linux-image-generic
 linux-generic
 linux-image-server
 linux-server
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

Tried the following

apt-get update (also did that before the do-release-upgrade)
apt-get autoremove

and that worked

rebooting - wish me luck

rebooted

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-firmware 1.127.24
ProcVersionSignature: Ubuntu 3.2.0-126.169-generic 3.2.79
Uname: Linux 3.2.0-126-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
Date: Fri Apr  6 16:50:21 2018
Dependencies:
 
DuplicateSignature: package:linux-firmware:1.127.24:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2014-03-12 (1486 days ago)
InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.3)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.8
 apt  1.0.1ubuntu2.17
SourcePackage: initramfs-tools
Title: package linux-firmware 1.127.24 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to trusty on 2018-04-06 (0 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package dist-upgrade trusty

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

Title:
  do-release-upgrade from 12.04 to 14.04 - package linux-firmware
  1.127.24 failed to install/upgrade: subprocess installed post-
  installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Tried do-release-upgrade from 12.04 to 14.04

  Not sure what is going on but doing the following on another login
  screen indicates that the upgrade has occurred

  cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"

  Hmm /boot is 100%

  apt-get autoremove

  failed again after /boot filled up again
  manuall removed stuff Eg.
  root@host1:/boot# rm initrd.img-3.2.0-75-generic initrd.img-3.2.0-77-generic 
initrd.img-3.2.0-80-generic initrd.img-3.2.0-83-generic 
initrd.img-3.2.0-95-generic

  repeated apt-get autoremove which just re-creates the above and
  results in the following

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-3.13.0-145-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-image-extra-3.13.0-145-generic
   linux-image-generic
   linux-generic
   linux-image-server
   linux-server
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Tried the following

  apt-get update (also did that before the do-release-upgrade)
  apt-get autoremove

  and that worked

  rebooting - wish me luck

  rebooted

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-firmware 1.127.24
  ProcVersionSignature: Ubuntu 3.2.0-126.169-generic 3.2.79
  Uname: Linux 3.2.0-126-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Fri Apr  6 16:50:21 2018
  Dependencies:
   
  DuplicateSignature: package:linux-firmware:1.127.24:subprocess insta

[Touch-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

[Mario Limonciello]

regarding klibc upstream is MIA for a long time.  There are patches that
have been posted before mine, but no activity since:

commit 4d19974d7020488f63651244e1f9f51727c3f66c
Author: H. Peter Anvin 
Date:   Mon Feb 1 13:26:01 2016 -0800

[klibc] fwrite: fix typo in comment

Fix typo in comment, no code change.

Reported-by: Gilles Espinasse 
Signed-off-by: H. Peter Anvin 

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

Title:
  FFe: Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  New
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1760106/+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 1760106] Re: FFe: Enable configuring resume offset via sysfs

[Mario Limonciello]

@Andy,

The systemd changes are approved, just waiting for CI to pass and
they'll be merged.

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

Title:
  FFe: Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  New
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  New

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1760106/+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 1746326] Re: package linux-firmware 1.127.24 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-firmware 1.127.24 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Failed during upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-firmware 1.127.24
  ProcVersionSignature: Ubuntu 3.13.0-141.190-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-141-generic i686
  NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Tue Jan 30 19:29:42 2018
  Dependencies:
   
  DuplicateSignature: package:linux-firmware:1.127.24:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.127.24 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2014-10-18 (1200 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1746326/+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 1761782] Re: do-release-upgrade from 12.04 to 14.04 - package linux-firmware 1.127.24 failed to install/upgrade: subprocess installed post-installation script returned error exit

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1746326
   package linux-firmware 1.127.24 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

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

Title:
  do-release-upgrade from 12.04 to 14.04 - package linux-firmware
  1.127.24 failed to install/upgrade: subprocess installed post-
  installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Tried do-release-upgrade from 12.04 to 14.04

  Not sure what is going on but doing the following on another login
  screen indicates that the upgrade has occurred

  cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"

  Hmm /boot is 100%

  apt-get autoremove

  failed again after /boot filled up again
  manuall removed stuff Eg.
  root@host1:/boot# rm initrd.img-3.2.0-75-generic initrd.img-3.2.0-77-generic 
initrd.img-3.2.0-80-generic initrd.img-3.2.0-83-generic 
initrd.img-3.2.0-95-generic

  repeated apt-get autoremove which just re-creates the above and
  results in the following

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-3.13.0-145-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-image-extra-3.13.0-145-generic
   linux-image-generic
   linux-generic
   linux-image-server
   linux-server
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Tried the following

  apt-get update (also did that before the do-release-upgrade)
  apt-get autoremove

  and that worked

  rebooting - wish me luck

  rebooted

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-firmware 1.127.24
  ProcVersionSignature: Ubuntu 3.2.0-126.169-generic 3.2.79
  Uname: Linux 3.2.0-126-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Fri Apr  6 16:50:21 2018
  Dependencies:
   
  DuplicateSignature: package:linux-firmware:1.127.24:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-03-12 (1486 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.17
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.127.24 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2018-04-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1761782/+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 1761782] Re: do-release-upgrade from 12.04 to 14.04 - package linux-firmware 1.127.24 failed to install/upgrade: subprocess installed post-installation script returned error exit

[Theo]

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

Probably just a case of /boot at 100%

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

Title:
  do-release-upgrade from 12.04 to 14.04 - package linux-firmware
  1.127.24 failed to install/upgrade: subprocess installed post-
  installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Tried do-release-upgrade from 12.04 to 14.04

  Not sure what is going on but doing the following on another login
  screen indicates that the upgrade has occurred

  cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"

  Hmm /boot is 100%

  apt-get autoremove

  failed again after /boot filled up again
  manuall removed stuff Eg.
  root@host1:/boot# rm initrd.img-3.2.0-75-generic initrd.img-3.2.0-77-generic 
initrd.img-3.2.0-80-generic initrd.img-3.2.0-83-generic 
initrd.img-3.2.0-95-generic

  repeated apt-get autoremove which just re-creates the above and
  results in the following

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-3.13.0-145-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-image-extra-3.13.0-145-generic
   linux-image-generic
   linux-generic
   linux-image-server
   linux-server
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Tried the following

  apt-get update (also did that before the do-release-upgrade)
  apt-get autoremove

  and that worked

  rebooting - wish me luck

  rebooted

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-firmware 1.127.24
  ProcVersionSignature: Ubuntu 3.2.0-126.169-generic 3.2.79
  Uname: Linux 3.2.0-126-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Fri Apr  6 16:50:21 2018
  Dependencies:
   
  DuplicateSignature: package:linux-firmware:1.127.24:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-03-12 (1486 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.17
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.127.24 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2018-04-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1761782/+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 1752417] Re: [ffe] Out of the box, Ubuntu Bionic offers only insecure VPN option

[Sebastien Bacher]

Ubuntu Desktop and Ubuntu Security teams are in agreement that it would
be worth adding to the default installation, that's a new feature though
so needs ubuntu-release to ack the addition, turning the bug to a ffe
and subscribing them for review

** Summary changed:

- Out of the box, Ubuntu Bionic offers only insecure VPN option
+ [ffe] Out of the box, Ubuntu Bionic offers only insecure VPN option

** Summary changed:

- [ffe] Out of the box, Ubuntu Bionic offers only insecure VPN option
+ [ffe] including network-manager-openvpn-gnome in the default installation

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

Title:
  [ffe] including network-manager-openvpn-gnome in the default
  installation

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager-openvpn package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  network-manager lists only PPTP as an available VPN client connection
  type (and also offers to import a file). I'd expect L2TP-over-IPSec
  and IKEv1/IKEv2 options as well.

  In fact, most major desktop OSes have removed PPTP altogether because
  it's insecure, and Ubuntu should probably do so in 18.04 as well, at
  least from the GUI!

  $ apt list network-manager
  Llistant… Fet
  network-manager/bionic,now 1.10.4-1ubuntu2 amd64 [instal·lat]

  $ uname -a
  Linux machinename 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  Codename: bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1752417/+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 1749546] Re: Booting a live session is slow - fontconfig regenerates its font cache

[Launchpad Bug Tracker]

This bug was fixed in the package fontconfig - 2.12.6-0ubuntu2

---
fontconfig (2.12.6-0ubuntu2) bionic; urgency=medium

  * Upload proposed patch from upstream bug #103652. If the fontconfig cache
was built on a system that has nanosecond timestamps and then later
transplanted to one that doesn't - for example by mksquashfs as part of a
live CD build - we consider the cache invalid and rebuild it during the
boot process. Depending on the fonts involved, this can take a significant
amount of time and potentially cause knock-on timeouts. The approach in
this patch is to ignore the nanosecond portion of the cache's value if we
get 0 when stat()ing the referenced directory, meaning it is considered
fresh if the rest of the timestamp matches. (LP: #1749546)

 -- Iain Lane   Thu, 05 Apr 2018 17:13:52
+0100

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

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

Title:
  Booting a live session is slow - fontconfig regenerates its font cache

Status in Fontconfig:
  Confirmed
Status in fontconfig package in Ubuntu:
  Fix Released
Status in fontconfig source package in Bionic:
  Fix Released

Bug description:
  On Bionic Ubuntu Desktop booting to a live session is slow. It takes
  roughly 2 min on my test machine to boot from the "Try or Install
  Ubuntu" boot menu to a usable session.

  It also takes 1 minute to logout and 17s to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: casper 1.388
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:43:19 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/1749546/+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 1740741] Re: * Hide imagemagick's Display app from the Ubuntu GNOME session as well

[Jeremy Bicha]

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

** Changed in: imagemagick (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
* Hide imagemagick's Display app from the Ubuntu GNOME session as
  well

Status in imagemagick package in Ubuntu:
  Fix Committed

Bug description:
  Imagemagick's Display app was hidden from the default Ubuntu session
  for Artful (LP: #1717951), but was still visible if you chose the
  GNOME session instead.

  I propose to apply the same fix (for the same reasons given in Bug
  1717951) to the GNOME session in Bionic.

  Link to bug 1717951: https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  settings/+bug/1717951

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1740741/+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 465689] Re: Ubuntu Clock Won't Show Year

[Lonnie Lee Best]

Will I ever be able to convenience people that "show year" is actually a
useful feature when taking screenshots over time?

Now, that I've upgraded to Ubuntu 18.04 and GNOME 3.28, it looks like
I'll have to start this 2009 battle all over again. It will not allow me
to format the clock the way I want it to display.

In Unity, I could at least achieved my desired clock format with a
command:

gsettings set com.canonical.indicator.datetime time-format "'custom'" ;
gsettings set com.canonical.indicator.datetime custom-time-format "'%A |
%m-%d-%Y | %l:%M%p'"

In GNOME 3.28 on Ubuntu 18.04, I've yet to figure out a way to achieved
my desired format. The GUI doesn't offer "show year" and I've yet to
discover a command (like the one above) that achieves the exact custom
format I desire.

** Tags added: bionic

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

Title:
  Ubuntu Clock Won't Show Year

Status in GNOME Panel:
  In Progress
Status in Indicator Date and Time:
  Fix Released
Status in gnome-panel package in Ubuntu:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  indicator-datetime, Ubuntu 12.10

  The Ubuntu menu bar clock offers no setting to "show year".

  Yes, I know what year it is, but I have very good reason for wanting
  it shown. For years, I've been collecting screen-shots, when I'm doing
  something I think is pretty cool. When I use to use windows, these
  screen shots (over the years) have always showed the current year.

  However, since April of 2007 (The date I started using Ubuntu
  exclusively), my screen shots have not included the year, because the
  Gnome clock doesn't provide this capability.

  : "'Year' should be both
  insensitive and unchecked whenever 'Date and month' is unchecked..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-panel/+bug/465689/+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 465689] Re: Ubuntu Clock Won't Show Year

[Jeremy Bicha]

Lonnie, please use a separate gnome-shell bug for that issue.

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

Title:
  Ubuntu Clock Won't Show Year

Status in GNOME Panel:
  In Progress
Status in Indicator Date and Time:
  Fix Released
Status in gnome-panel package in Ubuntu:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  indicator-datetime, Ubuntu 12.10

  The Ubuntu menu bar clock offers no setting to "show year".

  Yes, I know what year it is, but I have very good reason for wanting
  it shown. For years, I've been collecting screen-shots, when I'm doing
  something I think is pretty cool. When I use to use windows, these
  screen shots (over the years) have always showed the current year.

  However, since April of 2007 (The date I started using Ubuntu
  exclusively), my screen shots have not included the year, because the
  Gnome clock doesn't provide this capability.

  : "'Year' should be both
  insensitive and unchecked whenever 'Date and month' is unchecked..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-panel/+bug/465689/+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 1739531] Re: apport-collect SHOULD NOT collect gnome-shell command history and favorites

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.9-0ubuntu4

---
apport (2.20.9-0ubuntu4) bionic; urgency=medium

  * apport/hookutils.py: When gathering gsettings schema changes redact
information regarding command-history and favorite-apps from gnome-shell.
(LP: #1739531)

 -- Brian Murray   Thu, 05 Apr 2018 10:51:59 -0700

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

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

Title:
  apport-collect SHOULD NOT collect gnome-shell command history and
  favorites

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Released

Bug description:
  In https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1739525/comments/4, I ran apport-collect for that bug
  report.

  To my horror, it posted "org.gnome.shell command-history" and "favorites" in 
the "GsettingsChanges.txt"!
  https://launchpadlibrarian.net/349970997/GsettingsChanges.txt

  It's _completely_ reasonable to see:
   * enabled-extensions
   * org.gnome.shell.* diffs
   * org.gnome.desktop.* diffs

  But it is _NOT_ acceptable (privacy reasons) to automatically harvest
  a user's favorites in the gnome-shell, nor their command histories.

  _IF_ we must harvest for bug-data gathering, it MUST come in a secure
  mechanism that is private only to submitter + the assigned dev.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1739531/+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 1729491] Re: [UIFe] ubuntu-bug says that snap packages are not installed

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.9-0ubuntu4

---
apport (2.20.9-0ubuntu4) bionic; urgency=medium

  * apport/hookutils.py: When gathering gsettings schema changes redact
information regarding command-history and favorite-apps from gnome-shell.
(LP: #1739531)

 -- Brian Murray   Thu, 05 Apr 2018 10:51:59 -0700

** Changed in: apport (Ubuntu Bionic)
   Status: Triaged => Fix Released

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

Title:
  [UIFe] ubuntu-bug says that snap packages are not installed

Status in apport package in Ubuntu:
  Fix Released
Status in ubuntu-docs package in Ubuntu:
  New
Status in apport source package in Bionic:
  Fix Released

Bug description:
  User Interface Freeze Exception Justification
  =
  The interface for ubuntu-bug/apport-bug  is super confusing if  
was installed as a snap.

  List Notifications
  ==
  https://lists.ubuntu.com/archives/ubuntu-translators/2018-April/007471.html
  

  Original Bug Description
  
  1.
  I installed the package gnome-recipes, tried to send an error report program 
in response to the received message:you cannot report a problem:
  The report belongs to a package that was not installed.

  2.
  Expected that the program will be identified as installed.

  3.
  sudo apt -f install
  [sudo] password for Alexander:
  Reading package lists... Done
  Building dependency tree
  Reading state information... Ready
  0 upgraded, 0 newly installed, for removal 0 packets are marked, and 0 
packages are not updated.
  sudo gnome-sudo recipes: gnome-recipes: command not found
  sudo apt install gnome-recipes Reading package lists... Done
  Building dependency tree
  Reading state information... Ready
  E: unable to locate package gnome-recipes

  I installed via software-center

  gnome-recipes
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  ubuntu-bug gnome-recipes
  dpkg-query: template gnome-recipes no corresponding package
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ^C^Z
  [1]+ Stopped ubuntu-bug gnome-recipes

  https://youtu.be/AXtR5m2uqUg
  ---

  1.
  произвёл установку пакета gnome-recipes, попытался отправить отчёт об ошибке 
программы, в ответ получил сообщение:Не удаётся сообщить о неполадке:
  Отчёт относится к пакету , который не был установлен.

  2.
  Ожидал что программа будет идентифицироваться как установленная.

  3.
  sudo apt -f install
  [sudo] пароль для alexandr:
  Чтение списков пакетов… Готово
  Построение дерева зависимостей
  Чтение информации о состоянии… Готово
  обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 
0 пакетов не обновлено.
  sudo gnome-recipes sudo: gnome-recipes: команда не найдена
  sudo apt install gnome-recipes Чтение списков пакетов… Готово
  Построение дерева зависимостей
  Чтение информации о состоянии… Готово
  E: Не удалось найти пакет gnome-recipes

  произвёл установку через software-center

  gnome-recipes
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  ubuntu-bug gnome-recipes
  dpkg-query: шаблону gnome-recipes не соответствует ни один пакет
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ^C^Z
  [1]+  Остановлено  ubuntu-bug gnome-recipes

  https://youtu.be/AXtR5m2uqUg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-center (not installed)
  Uname: Linux 4.14.0-041400rc7-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov  2 08:06:48 2017
  InstallationDate: Installed on 2017-10-29 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1729491/+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 1761593] [NEW] Uninstall left nouveau blacklisted

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Following a successful install and subsequent use of nvidia-340 -
uninstallation of nvidia via Additional Drivers led to a reboot to a
desktop at 640x480 px.

Investigation found an nvidia created file left on the system
blacklisting nouveau, deleted file and rebooted to normal desktop.

Didn't think about ubuntu-reporting this - can try and replicate and
apport-collect if it's of any use.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: Confirmed

-- 
Uninstall left nouveau blacklisted
https://bugs.launchpad.net/bugs/1761593
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to software-properties in Ubuntu.

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

[Touch-packages] [Bug 1761754] Re: unmet dependencies: linux-headers-4.4.0-119-generic

[Hans Joachim Desserud]

** Tags added: unmetdeps

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

Title:
  unmet dependencies: linux-headers-4.4.0-119-generic

Status in apt package in Ubuntu:
  New

Bug description:
  Xubuntu 16.04 x64
  system is unable to upgrade due to 
  "The following packages have unmet dependencies:
   linux-headers-4.4.0-119-generic : Depends: linux-headers-4.4.0-119 but it is 
not installed
  E: Unmet dependencies. Try using -f.
  "

  sudo dpkg --configure -a
  dpkg: dependency problems prevent configuration of 
linux-headers-4.4.0-119-generic:
   linux-headers-4.4.0-119-generic depends on linux-headers-4.4.0-119; however:
Package linux-headers-4.4.0-119 is not installed.

  dpkg: error processing package linux-headers-4.4.0-119-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-4.4.0-119-generic; however:
Package linux-headers-4.4.0-119-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 4.4.0.119.125); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   linux-headers-4.4.0-119-generic
   linux-headers-generic
   linux-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1761754/+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 1761593] Re: Uninstall left nouveau blacklisted

[Kev Bowring]

Rechecked this (multiple times)

Using the GUI at Software & Updates>Additional Drivers appears to now
not remove conf files and hence user is left with 640x480px (assume
because of the blacklist file left in /etc/modprobe.d)

If one installs via apt and then purges - the nvidia conf file is
removed and a normal at reboot results.

The same behaviour is seen if installed via Software & Updates and then
removed with apt purge.

Pretty positive this was not previously the case when using the GUI to
install nvidia driver.

Only have 1 card to test against - so possibly only affects nvidia-340.

Notes from testing and some pastebin of terminal logs attached.

** Attachment added: "nvidia_testing"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1761593/+attachment/5104355/+files/nvidia_testing

** Package changed: nvidia-graphics-drivers-340 (Ubuntu) => software-
properties (Ubuntu)

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

Title:
  Uninstall left nouveau blacklisted

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Following a successful install and subsequent use of nvidia-340 -
  uninstallation of nvidia via Additional Drivers led to a reboot to a
  desktop at 640x480 px.

  Investigation found an nvidia created file left on the system
  blacklisting nouveau, deleted file and rebooted to normal desktop.

  Didn't think about ubuntu-reporting this - can try and replicate and
  apport-collect if it's of any use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1761593/+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 465689] Re: Ubuntu Clock Won't Show Year

[Lonnie Lee Best]

I was ultimately able to achieve my exactly desired format using a GNOME
extension made by Daniel Khodabakhsh. Thank you Daniel!

I found that here:
https://github.com/Daniel-Khodabakhsh/datetime-format

Screenshot:
http://neartalk.com/ss/2018-04-06_003_1919x1079.png

Format:
%A | %m-%d-%G | %I:%M %p

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

Title:
  Ubuntu Clock Won't Show Year

Status in GNOME Panel:
  In Progress
Status in Indicator Date and Time:
  Fix Released
Status in gnome-panel package in Ubuntu:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  indicator-datetime, Ubuntu 12.10

  The Ubuntu menu bar clock offers no setting to "show year".

  Yes, I know what year it is, but I have very good reason for wanting
  it shown. For years, I've been collecting screen-shots, when I'm doing
  something I think is pretty cool. When I use to use windows, these
  screen shots (over the years) have always showed the current year.

  However, since April of 2007 (The date I started using Ubuntu
  exclusively), my screen shots have not included the year, because the
  Gnome clock doesn't provide this capability.

  : "'Year' should be both
  insensitive and unchecked whenever 'Date and month' is unchecked..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-panel/+bug/465689/+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 1568576] Re: Thinkpad T460 & Ultra Dock - No audio output on dock plug

[Stephan]

Same here with L470
(uname -a: 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux )

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

Title:
  Thinkpad T460 & Ultra Dock - No audio output on dock plug

Status in ALSA driver:
  New
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Thinkpad T460, Ultra dock, 2 channel speakers connected to dock.
  4.4.0-18 Kernel / 16.04.

  When the laptop is docked & speakers are connected to the dock audio
  connector, I get no audio outpout from the dock audio connector.

  Looks like the same issue as reported in:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1385680

  However the pin quirks appear to be different for the T*60 series of
  laptops.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1568576/+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 1761834] [NEW] Right-click doesn't work

[Eric Stith]

Public bug reported:

I decided to try out the beta for 18.04 from 17.10.  Upon upgrading, I
discovered that right-clicking no longer works on my trackpad, and
right-clicks are handled as left-clicks would be.  Two-finger right
click does not work either.  If I plug in a mouse with a physical right
button, right clicking does work.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Apr  6 11:26:00 2018
DistUpgraded: 2018-04-06 11:14:08,949 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.14.15-041415-generic, x86_64: installed
 bbswitch, 0.8, 4.15.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 530 [1028:06e4]
   Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
InstallationDate: Installed on 2017-05-04 (337 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Dell Inc. XPS 15 9550
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=UUID=62d6bfc3-82e2-4ca2-9255-8dae5ad9b117 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago)
dmi.bios.date: 08/21/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
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.:bvr1.4.0:bd08/21/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Right-click doesn't work

Status in xorg package in Ubuntu:
  New

Bug description:
  I decided to try out the beta for 18.04 from 17.10.  Upon upgrading, I
  discovered that right-clicking no longer works on my trackpad, and
  right-clicks are handled as left-clicks would be.  Two-finger right
  click does not work either.  If I plug in a mouse with a physical
  right button, right clicking does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  6 11:26:00 2018
  DistUpgraded: 2018-04-06 11:14:08,949 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.14.15-041415-generic, x86_64: installed
   bbswitch, 0.8, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2017-05-04 (337 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=UUID=62d6bfc3-82e2-4ca2-9255-8dae5ad9b117 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago)
  dmi.bios.date: 08/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi

[Touch-packages] [Bug 1761842] [NEW] package linux-image-extra-4.13.0-38-generic 4.13.0-38.43 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Josef]

Public bug reported:

I just ran the Software Updater and I got this error.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: linux-image-extra-4.13.0-38-generic 4.13.0-38.43
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm1429 F pulseaudio
  josef  1877 F pulseaudio
 /dev/snd/controlC0:  gdm1429 F pulseaudio
  josef  1877 F pulseaudio
Date: Fri Apr  6 20:44:14 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=e203c511-a20b-4f19-9b17-96abb1de77dd
InstallationDate: Installed on 2015-12-18 (840 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Dell Inc. Latitude E6420
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7.3
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.13.0-38-generic 4.13.0-38.43 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to artful on 2018-01-21 (75 days ago)
dmi.bios.date: 02/22/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 038C0K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd02/22/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6420
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package linux-image-extra-4.13.0-38-generic 4.13.0-38.43 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I just ran the Software Updater and I got this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-extra-4.13.0-38-generic 4.13.0-38.43
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1429 F pulseaudio
josef  1877 F pulseaudio
   /dev/snd/controlC0:  gdm1429 F pulseaudio
josef  1877 F pulseaudio
  Date: Fri Apr  6 20:44:14 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=e203c511-a20b-4f19-9b17-96abb1de77dd
  InstallationDate: Installed on 2015-12-18 (840 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Latitude E6420
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7.3
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.13.0-38-generic 4.13.0-38.43 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to artful on 2018-01-21 (75 days ago)
  dmi.bios.date: 02/22/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd02/22/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version:

[Touch-packages] [Bug 1761842] Re: package linux-image-extra-4.13.0-38-generic 4.13.0-38.43 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1761842

Title:
  package linux-image-extra-4.13.0-38-generic 4.13.0-38.43 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I just ran the Software Updater and I got this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-extra-4.13.0-38-generic 4.13.0-38.43
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1429 F pulseaudio
josef  1877 F pulseaudio
   /dev/snd/controlC0:  gdm1429 F pulseaudio
josef  1877 F pulseaudio
  Date: Fri Apr  6 20:44:14 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=e203c511-a20b-4f19-9b17-96abb1de77dd
  InstallationDate: Installed on 2015-12-18 (840 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Latitude E6420
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7.3
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.13.0-38-generic 4.13.0-38.43 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to artful on 2018-01-21 (75 days ago)
  dmi.bios.date: 02/22/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd02/22/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1761842/+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 1761593] Re: Uninstall left nouveau blacklisted

[Kev Bowring]

Just booted xubuntu 17.10.1 iso - installed nvidia with software-
properties - additional drivers.

Blacklist file added.

Removed nvidia with software-properties - additional drivers.

Blacklist file removed.

** Tags added: regression

** Tags removed: regression
** Tags added: regression-update

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

Title:
  Uninstall left nouveau blacklisted

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Following a successful install and subsequent use of nvidia-340 -
  uninstallation of nvidia via Additional Drivers led to a reboot to a
  desktop at 640x480 px.

  Investigation found an nvidia created file left on the system
  blacklisting nouveau, deleted file and rebooted to normal desktop.

  Didn't think about ubuntu-reporting this - can try and replicate and
  apport-collect if it's of any use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1761593/+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 1761849] [NEW] Radiance title bar is a lot bigger in fullscreen than Ambiance

[Hito]

Public bug reported:

Ubuntu 18.04 Beta 1
Radiance title bar is relay huge, see screenshots below;

Ambiance:
https://i.imgur.com/Q31yqx9.png

Radiance:
https://i.imgur.com/SYL0U7y.png

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

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

Title:
  Radiance title bar is a lot bigger in fullscreen than Ambiance

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 Beta 1
  Radiance title bar is relay huge, see screenshots below;

  Ambiance:
  https://i.imgur.com/Q31yqx9.png

  Radiance:
  https://i.imgur.com/SYL0U7y.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1761849/+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 1638345] Re: avahi-daemon crashes multiple times an hour

[Jose Serralles]

Hi, Trent.

I upgraded the avahi packages with apt
and replaced the configuration file that
I had edited with the file supplied by the
package. Everything works as intended.

Thank you!

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

Title:
  avahi-daemon crashes multiple times an hour

Status in avahi package in Ubuntu:
  Fix Released

Bug description:
  Ever since upgrading to 16.10, avahi-daemon crashes multiple times an
  hour, leading to the prompt to report the issue to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:48:35 2016
  InstallationDate: Installed on 2016-07-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1638345/+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 1761754] Re: unmet dependencies: linux-headers-4.4.0-119-generic

[Galen Thurber]

resolved

gnome-software was hung silently in the background (an old unresolved bug).
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1656347
killing it and running synaptic's fix broken resolved issue

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

Title:
  unmet dependencies: linux-headers-4.4.0-119-generic

Status in apt package in Ubuntu:
  New

Bug description:
  Xubuntu 16.04 x64
  system is unable to upgrade due to 
  "The following packages have unmet dependencies:
   linux-headers-4.4.0-119-generic : Depends: linux-headers-4.4.0-119 but it is 
not installed
  E: Unmet dependencies. Try using -f.
  "

  sudo dpkg --configure -a
  dpkg: dependency problems prevent configuration of 
linux-headers-4.4.0-119-generic:
   linux-headers-4.4.0-119-generic depends on linux-headers-4.4.0-119; however:
Package linux-headers-4.4.0-119 is not installed.

  dpkg: error processing package linux-headers-4.4.0-119-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-4.4.0-119-generic; however:
Package linux-headers-4.4.0-119-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 4.4.0.119.125); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   linux-headers-4.4.0-119-generic
   linux-headers-generic
   linux-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1761754/+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 1761754] Re: unmet dependencies: linux-headers-4.4.0-119-generic

[Julian Andres Klode]

marking as invalid. gnome-software running in the background should not
be a problem, though; it's designed to run in the background. Anyhow,
something broke somewhere in an upgrade, and apt is just telling you
that.

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

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

Title:
  unmet dependencies: linux-headers-4.4.0-119-generic

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Xubuntu 16.04 x64
  system is unable to upgrade due to 
  "The following packages have unmet dependencies:
   linux-headers-4.4.0-119-generic : Depends: linux-headers-4.4.0-119 but it is 
not installed
  E: Unmet dependencies. Try using -f.
  "

  sudo dpkg --configure -a
  dpkg: dependency problems prevent configuration of 
linux-headers-4.4.0-119-generic:
   linux-headers-4.4.0-119-generic depends on linux-headers-4.4.0-119; however:
Package linux-headers-4.4.0-119 is not installed.

  dpkg: error processing package linux-headers-4.4.0-119-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-4.4.0-119-generic; however:
Package linux-headers-4.4.0-119-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 4.4.0.119.125); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   linux-headers-4.4.0-119-generic
   linux-headers-generic
   linux-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1761754/+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 1761593] Re: Uninstall left nouveau blacklisted

[Jeremy Bicha]

** Also affects: nvidia-settings (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Uninstall left nouveau blacklisted

Status in nvidia-settings package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Following a successful install and subsequent use of nvidia-340 -
  uninstallation of nvidia via Additional Drivers led to a reboot to a
  desktop at 640x480 px.

  Investigation found an nvidia created file left on the system
  blacklisting nouveau, deleted file and rebooted to normal desktop.

  Didn't think about ubuntu-reporting this - can try and replicate and
  apport-collect if it's of any use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1761593/+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 1761858] [NEW] libx11-6-dbgsym should be insection "debug" insead of section "libs"

[Laurent Bonnaud]

Public bug reported:

Hi,

the problem is that deborphan lists this package as removable, whereas I
want to keep it:

$ deborphan
[...]
libx11-6-dbgsym:amd64

It comes from the fact that libx11-6-dbgsym is in section "libs":

$ dpkg -s libx11-6-dbgsym
[...]
Section: libs

whereas it should be in section "devel".  All other *-dbgsym packages on
my system belong to this section.  For instance:

$ dpkg -s libqt5gui5-dbgsym
[...]
Section: debug

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libx11-6-dbgsym 2:1.6.4-3
Uname: Linux 4.15.15-041515-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Fri Apr  6 22:00:55 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0494]
MachineType: Dell Inc. Latitude E6520
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.15-041515-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro vsyscall=none 
security=apparmor intel_iommu=on enable_mtrr_cleanup mtrr_spare_reg_nr=1 
mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=1
SourcePackage: libx11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A19
dmi.board.name: 0NVF5K
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6520
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  libx11-6-dbgsym should be insection "debug" insead of section "libs"

Status in libx11 package in Ubuntu:
  New

Bug description:
  Hi,

  the problem is that deborphan lists this package as removable, whereas
  I want to keep it:

  $ deborphan
  [...]
  libx11-6-dbgsym:amd64

  It comes from the fact that libx11-6-dbgsym is in section "libs":

  $ dpkg -s libx11-6-dbgsym
  [...]
  Section: libs

  whereas it should be in section "devel".  All other *-dbgsym packages
  on my system belong to this section.  For instance:

  $ dpkg -s libqt5gui5-dbgsym
  [...]
  Section: debug

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libx11-6-dbgsym 2:1.6.4-3
  Uname: Linux 4.15.15-041515-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Apr  6 22:00:55 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0494]
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.15-041515-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro vsyscall=none 
security=apparmor intel_iommu=on enable_mtrr_cleanup mtrr_spare_reg_nr=1 
mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=1
  SourcePackage: libx11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  ve

[Touch-packages] [Bug 1761861] [NEW] dh-python dependency removal changing behaviour of installing virtualenv

[Milind b]

Public bug reported:

root@6de0badbae8b:/# apt-get install --no-install-recommends virtualenv
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  ca-certificates libexpat1 libmpdec2 libpython3-stdlib libpython3.6-minimal 
libpython3.6-stdlib libssl1.1 mime-support openssl python-pip-whl python3 
python3-minimal
  python3-pkg-resources python3-virtualenv python3.6 python3.6-minimal
Suggested packages:
  python3-doc python3-tk python3-venv python3-setuptools python3.6-venv 
python3.6-doc binutils binfmt-support
Recommended packages:
  bzip2 file xz-utils
The following NEW packages will be installed:
  ca-certificates libexpat1 libmpdec2 libpython3-stdlib libpython3.6-minimal 
libpython3.6-stdlib libssl1.1 mime-support openssl python-pip-whl python3 
python3-minimal
  python3-pkg-resources python3-virtualenv python3.6 python3.6-minimal 
virtualenv
0 upgraded, 17 newly installed, 0 to remove and 43 not upgraded.
Need to get 7375 kB of archives.
After this operation, 29.9 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu bionic/main amd64 libssl1.1 amd64 
1.1.0g-2ubuntu3 [1128 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython3.6-minimal 
amd64 3.6.5-3 [529 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic/main amd64 libexpat1 amd64 
2.2.5-3 [80.2 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic/main amd64 python3.6-minimal 
amd64 3.6.5-3 [1425 kB]
Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 python3-minimal amd64 
3.6.5-2 [23.9 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic/main amd64 mime-support all 
3.60ubuntu1 [30.1 kB]
Get:7 http://archive.ubuntu.com/ubuntu bionic/main amd64 libmpdec2 amd64 
2.4.2-1 [82.6 kB]
Get:8 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython3.6-stdlib 
amd64 3.6.5-3 [1648 kB]
Get:9 http://archive.ubuntu.com/ubuntu bionic/main amd64 python3.6 amd64 
3.6.5-3 [186 kB]
Get:10 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython3-stdlib 
amd64 3.6.5-2 [7372 B]
Get:11 http://archive.ubuntu.com/ubuntu bionic/main amd64 python3 amd64 3.6.5-2 
[8780 B]
Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 openssl amd64 
1.1.0g-2ubuntu3 [532 kB]
Get:13 http://archive.ubuntu.com/ubuntu bionic/main amd64 ca-certificates all 
20170717 [167 kB]
Get:14 http://archive.ubuntu.com/ubuntu bionic/universe amd64 python-pip-whl 
all 9.0.1-2 [1379 kB]
Get:15 http://archive.ubuntu.com/ubuntu bionic/main amd64 python3-pkg-resources 
all 39.0.1-2 [98.8 kB]
Get:16 http://archive.ubuntu.com/ubuntu bionic/universe amd64 
python3-virtualenv all 15.1.0+ds-1 [43.2 kB]
Get:17 http://archive.ubuntu.com/ubuntu bionic/universe amd64 virtualenv all 
15.1.0+ds-1 [4376 B]
Fetched 7375 kB in 14s (515 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package libssl1.1:amd64.
(Reading database ... 4416 files and directories currently installed.)
Preparing to unpack .../0-libssl1.1_1.1.0g-2ubuntu3_amd64.deb ...
Unpacking libssl1.1:amd64 (1.1.0g-2ubuntu3) ...
Selecting previously unselected package libpython3.6-minimal:amd64.
Preparing to unpack .../1-libpython3.6-minimal_3.6.5-3_amd64.deb ...
Unpacking libpython3.6-minimal:amd64 (3.6.5-3) ...
Selecting previously unselected package libexpat1:amd64.
Preparing to unpack .../2-libexpat1_2.2.5-3_amd64.deb ...
Unpacking libexpat1:amd64 (2.2.5-3) ...
Selecting previously unselected package python3.6-minimal.
Preparing to unpack .../3-python3.6-minimal_3.6.5-3_amd64.deb ...
Unpacking python3.6-minimal (3.6.5-3) ...
Selecting previously unselected package python3-minimal.
Preparing to unpack .../4-python3-minimal_3.6.5-2_amd64.deb ...
Unpacking python3-minimal (3.6.5-2) ...
Selecting previously unselected package mime-support.
Preparing to unpack .../5-mime-support_3.60ubuntu1_all.deb ...
Unpacking mime-support (3.60ubuntu1) ...
Selecting previously unselected package libmpdec2:amd64.
Preparing to unpack .../6-libmpdec2_2.4.2-1_amd64.deb ...
Unpacking libmpdec2:amd64 (2.4.2-1) ...
Selecting previously unselected package libpython3.6-stdlib:amd64.
Preparing to unpack .../7-libpython3.6-stdlib_3.6.5-3_amd64.deb ...
Unpacking libpython3.6-stdlib:amd64 (3.6.5-3) ...
Selecting previously unselected package python3.6.
Preparing to unpack .../8-python3.6_3.6.5-3_amd64.deb ...
Unpacking python3.6 (3.6.5-3) ...
Selecting previously unselected package libpython3-stdlib:amd64.
Preparing to unpack .../9-libpython3-stdlib_3.6.5-2_amd64.deb ...
Unpacking libpython3-stdlib:amd64 (3.6.5-2) ...
Setting up libssl1.1:amd64 (1.1.0g-2ubuntu3) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: R

[Touch-packages] [Bug 1756937] Re: report_crashes setting not written

[Brian Murray]

Additionally in 18.04 there is nothing like "Send occasional system
information to Canonical" in gnome-control-center - only the report
crashes option appears.

** Also affects: whoopsie (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: whoopsie-preferences (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: whoopsie-preferences (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: whoopsie (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: whoopsie (Ubuntu Bionic)
   Importance: Undecided => Medium

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

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

Title:
  report_crashes setting not written

Status in whoopsie package in Ubuntu:
  In Progress
Status in whoopsie-preferences package in Ubuntu:
  Invalid
Status in whoopsie source package in Bionic:
  In Progress
Status in whoopsie-preferences source package in Bionic:
  Invalid

Bug description:
  whoopsie was built with two settings, report_metrics (statistics like
  popcon - currently unused) and report_crashes (for reporting crash
  reports to the Error Tracker). However, only report_metrics gets
  written to '/etc/whoopsie' while the setting for report_crashes is
  defined by having whoopsie.disable. This complicates matters as there
  are two places to look for whoopsie settings '/etc/whoopsie' and
  checking for a .disable file. It'd be best if "report_crashes" was
  also written to '/etc/whoopsie'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1756937/+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 1756937] Re: report_crashes setting not written

[Brian Murray]

However, what is written is "report_metrics" which is not read by
whoopsie. So to avoid any confusion the best approach seems to be to
just remove /etc/whoopsie.

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

Title:
  report_crashes setting not written

Status in whoopsie package in Ubuntu:
  In Progress
Status in whoopsie-preferences package in Ubuntu:
  Invalid
Status in whoopsie source package in Bionic:
  In Progress
Status in whoopsie-preferences source package in Bionic:
  Invalid

Bug description:
  whoopsie was built with two settings, report_metrics (statistics like
  popcon - currently unused) and report_crashes (for reporting crash
  reports to the Error Tracker). However, only report_metrics gets
  written to '/etc/whoopsie' while the setting for report_crashes is
  defined by having whoopsie.disable. This complicates matters as there
  are two places to look for whoopsie settings '/etc/whoopsie' and
  checking for a .disable file. It'd be best if "report_crashes" was
  also written to '/etc/whoopsie'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1756937/+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 1761867] [NEW] Can not remove nvidia-390.x drivers

[Doug McMahon]

Public bug reported:

What additional drivers does do is to remove the nvidia-driver-390
metapackage. This has no practical effect in removing the driver & lib
packages other than having them marked for autoremove

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: software-properties-gtk 0.96.24.25
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri Apr  6 16:42:17 2018
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  Can not remove nvidia-390.x drivers

Status in software-properties package in Ubuntu:
  New

Bug description:
  What additional drivers does do is to remove the nvidia-driver-390
  metapackage. This has no practical effect in removing the driver & lib
  packages other than having them marked for autoremove

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.25
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr  6 16:42:17 2018
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1761867/+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 1761866] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1760128
   package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  See the bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Apr  6 22:38:43 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2018-03-14 (23 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1761866/+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 1761866] [NEW] package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Peter Mihalik dr.]

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

Public bug reported:

See the bug

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Apr  6 22:38:43 2018
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2018-03-14 (23 days ago)
InstallationMedia: Ubuntu-MATE 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: avahi
Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  See the bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Apr  6 22:38:43 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2018-03-14 (23 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1761866/+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 1756937] Re: report_crashes setting not written

[Launchpad Bug Tracker]

** Branch linked: lp:whoopsie

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

Title:
  report_crashes setting not written

Status in whoopsie package in Ubuntu:
  In Progress
Status in whoopsie-preferences package in Ubuntu:
  Invalid
Status in whoopsie source package in Bionic:
  In Progress
Status in whoopsie-preferences source package in Bionic:
  Invalid

Bug description:
  whoopsie was built with two settings, report_metrics (statistics like
  popcon - currently unused) and report_crashes (for reporting crash
  reports to the Error Tracker). However, only report_metrics gets
  written to '/etc/whoopsie' while the setting for report_crashes is
  defined by having whoopsie.disable. This complicates matters as there
  are two places to look for whoopsie settings '/etc/whoopsie' and
  checking for a .disable file. It'd be best if "report_crashes" was
  also written to '/etc/whoopsie'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1756937/+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 1761754] Re: unmet dependencies: linux-headers-4.4.0-119-generic

[Galen Thurber]

Ah the joy of reporting bugs and having them marked as invalid, classy

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

Title:
  unmet dependencies: linux-headers-4.4.0-119-generic

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Xubuntu 16.04 x64
  system is unable to upgrade due to 
  "The following packages have unmet dependencies:
   linux-headers-4.4.0-119-generic : Depends: linux-headers-4.4.0-119 but it is 
not installed
  E: Unmet dependencies. Try using -f.
  "

  sudo dpkg --configure -a
  dpkg: dependency problems prevent configuration of 
linux-headers-4.4.0-119-generic:
   linux-headers-4.4.0-119-generic depends on linux-headers-4.4.0-119; however:
Package linux-headers-4.4.0-119 is not installed.

  dpkg: error processing package linux-headers-4.4.0-119-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-4.4.0-119-generic; however:
Package linux-headers-4.4.0-119-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 4.4.0.119.125); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   linux-headers-4.4.0-119-generic
   linux-headers-generic
   linux-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1761754/+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 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Settin

[Norbert]

Still happens after installation of `xubuntu-desktop` from beta2
netboot.iso.

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

Title:
  gnome-control-center is unusable on xubuntu-desktop, but called from
  Gear (About this Computer, System Settings) icon, Text Entry Settings,
  clock (Time & Date Settings)

Status in gnome-control-center package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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