[Touch-packages] [Bug 1803491] Re: in codeblocks ide

[Daniel van Vugt]

Those are two separate issues you have mentioned. Please change the bug
description to cover only one of the issues and log a new bug for the
other.

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  in codeblocks ide

Status in Ubuntu:
  Incomplete

Bug description:
  the system is taking much time to boot and hangs when codeblocks ide
  is opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Nov 15 11:26:35 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-127-generic, 
x86_64: installed
   oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-94-generic, x86_64: 
installed
   oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 1.2, 4.4.0-127-generic, x86_64: 
installed
   oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 1.2, 4.4.0-94-generic, x86_64: 
installed
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0841]
  InstallationDate: Installed on 2018-08-26 (80 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Vostro 3478
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed 
root=UUID=01b2b9ec-7c39-4d22-8f6c-e43fcdc44c2b ro acpi_rev_override quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 08R7RH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd05/22/2018:svnDellInc.:pnVostro3478:pvr:rvnDellInc.:rn08R7RH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Vostro 3478
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Nov 15 11:15:34 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1805 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1803487] Re: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix64

[Treviño]

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: libgweather (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

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

** Description changed:

+ [ Description ]
+ 
+ The second stable release in the 3.28 series.
+ 
+ [ QA ]
+ 
+ Run Ubuntu session, expect the shell to show weather information and not
+ to crash on timezone changes
+ 
+ https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
+ 
+ [ Regresison potential ]
+ 
+ Weather location might be leaked. However this is very safe as upstream
+ fix comes with proper testing.
+ 
+ ---
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.3-0ubuntu0.18.04.3, the problem page at 
https://errors.ubuntu.com/problem/4ff1b7671a7dc53f26da1c0f78af65d0cc5168fa 
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/.

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

Title:
  gnome-shell crashes with SIGSEGV in
  gweather_location_common_deserialize →
  gweather_location_format_two_deserialize →
  gweather_location_deserialize → ffi_call_unix64 → ffi_call

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in libgweather package in Ubuntu:
  New

Bug description:
  [ Description ]

  The second stable release in the 3.28 series.

  [ QA ]

  Run Ubuntu session, expect the shell to show weather information and
  not to crash on timezone changes

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Weather location might be leaked. However this is very safe as
  upstream fix comes with proper testing.

  ---

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.3-0ubuntu0.18.04.3, the problem page at 
https://errors.ubuntu.com/problem/4ff1b7671a7dc53f26da1c0f78af65d0cc5168fa 
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/gnome-shell/+bug/1803487/+subscriptions

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

[Touch-packages] [Bug 1803487] Re: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix64

[Daniel van Vugt]

** Summary changed:

- gnome-shell crashes in libgweather gweather_location_common_deserialize
+ gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → 
gweather_location_format_two_deserialize → gweather_location_deserialize → 
ffi_call_unix64 → ffi_call

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

Title:
  gnome-shell crashes with SIGSEGV in
  gweather_location_common_deserialize →
  gweather_location_format_two_deserialize →
  gweather_location_deserialize → ffi_call_unix64 → ffi_call

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in libgweather package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.3-0ubuntu0.18.04.3, the problem page at 
https://errors.ubuntu.com/problem/4ff1b7671a7dc53f26da1c0f78af65d0cc5168fa 
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/gnome-shell/+bug/1803487/+subscriptions

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

[Touch-packages] [Bug 1803487] Re: gnome-shell crashes in libgweather gweather_location_common_deserialize

[Treviño]

** Summary changed:

- 
/usr/bin/gnome-shell:11:gweather_location_common_deserialize:gweather_location_format_two_deserialize:gweather_location_deserialize:ffi_call_unix64:ffi_call
+ gnome-shell crashes in libgweather gweather_location_common_deserialize

** Changed in: gnome-shell (Ubuntu)
   Status: New => In Progress

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Released

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

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

Title:
  gnome-shell crashes in libgweather
  gweather_location_common_deserialize

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in libgweather package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.3-0ubuntu0.18.04.3, the problem page at 
https://errors.ubuntu.com/problem/4ff1b7671a7dc53f26da1c0f78af65d0cc5168fa 
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/gnome-shell/+bug/1803487/+subscriptions

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

[Touch-packages] [Bug 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 - LTS version

[punyabrat kumar]

Only file sharing not working now,Bluetooth Speaker is working

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

Title:
  [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04
  - LTS version

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to
  send or receive files via bluetooth,please do give a emulsion of this
  hardware problem

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  6 15:26:50 2018
  DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1366x768+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 
'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 
'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']"
  InstallationDate: Installed on 2016-11-07 (544 days ago)
  InstallationMedia:
   
  MachineType: HP HP 245 G5 Notebook PC
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash
  SourcePackage: compiz
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  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-1ubuntu4
  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/bluez/+bug/1769443/+subscriptions

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

[Touch-packages] [Bug 1790323] Re: system shutdown without warning or notification

[Launchpad Bug Tracker]

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

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

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

Title:
  system shutdown without warning or notification

Status in systemd package in Ubuntu:
  Expired

Bug description:
   lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu10.3
Candidate: 237-3ubuntu10.3
Version table:
   *** 237-3ubuntu10.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  during normal usage
  watching video on chrome
  http://lelang.ru/english/rik-i-morti-na-anglijskom-1-sezon-3-seriya/

  system shut down without warning or notice
  :(

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Sep  1 20:04:33 2018
  InstallationDate: Installed on 2018-08-24 (8 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Studio 1737
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=2b8227a7-271c-4d4c-8a2b-faa238133be0 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0P792H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/14/2011:svnDellInc.:pnStudio1737:pvrA09:rvnDellInc.:rn0P792H:rvrA09:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Studio 1737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Systemd update installation hangs in unattended-upgrades
  InstallOnShutdown mode

Status in systemd package in Ubuntu:
  New

Bug description:
  Installation of latest systemd update in -security hangs with current
  versions of unattended-upgrades in supported releases. The u-u-side
  fix is tracked in LP: #1778219.

  Reproduction:

  rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown
  Creating uu-systemd-onshutdown
  Starting uu-systemd-onshutdown
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown 
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# apt update -qq
  23 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown 
"true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
  root@uu-systemd-onshutdown:~# apt list --upgradable
  Listing... Done
  apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 
[upgradable from: 0.19.8.1-6]
  kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable 
from: 0.6-3ubuntu0.1]
  libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 
237-3ubuntu10.3]
  root@uu-systemd-onshutdown:~# reboot

  Session terminated, terminating shell...Terminated
  root@uu-systemd-
  rbalint@yogi:~$ 
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown 
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# tail 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ...
  Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ...
  Setting up libsystemd0:amd64 (237-3ubuntu10.6) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Setting up systemd (237-3ubuntu10.6) ...
  Failed to try-restart systemd-networkd.service: Transaction is destructive.
  See system logs and 'systemctl status systemd-networkd.service' for details.
  Failed to try-restart systemd-resolved.service: Transaction is destructive.
  See system logs and 'systemctl status systemd-resolved.service' for details.
  root@uu-systemd-onshutdown:~#  ps -ef  | cat
  UIDPID  PPID  C STIME TTY  TIME CMD
  root 1 0  0 15:34 ?00:00:00 /lib/systemd/systemd --system 
--deserialize 22
  root53 1  0 15:34 ?00:00:00 /lib/systemd/systemd-journald
  systemd+   153 1  0 15:34 ?00:00:00 /lib/systemd/systemd-networkd
  systemd+   154 1  0 15:34 ?00:00:00 /lib/systemd/systemd-resolved
  message+   194 1  0 15:34 ?00:00:00 /usr/bin/dbus-daemon --system 
--address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
  root   572 1  0 15:35 ?00:00:00 /usr/bin/python3 

[Touch-packages] [Bug 1690051] Re: pulseaudio crashed with SIGSEGV in publish_service() from once_callback() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate()

[Daniel van Vugt]

There is no known fix to backport. I am just trying to confirm if it
really has stopped happening in version 12.


** Tags removed: artful vivid wily yakkety zesty

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

Title:
  pulseaudio crashed with SIGSEGV in publish_service() from
  once_callback() from dispatch_defer() from pa_mainloop_dispatch() from
  pa_mainloop_iterate()

Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

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

[Touch-packages] [Bug 1690051] Re: pulseaudio crashed with SIGSEGV in publish_service() from once_callback() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate()

[Owen Williams]

I was really hoping to keep this machine on LTS, is the fix not going to
be backported?

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

Title:
  pulseaudio crashed with SIGSEGV in publish_service() from
  once_callback() from dispatch_defer() from pa_mainloop_dispatch() from
  pa_mainloop_iterate()

Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

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

[Touch-packages] [Bug 1803353] Re: Display freezes (possible i915 freeze/hang)

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => xorg-server (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/1803353

Title:
  Display freezes (possible i915 freeze/hang)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Xorg suddenly stops updating the display and CTRL+ALT+F1 does not
  work. The issue happens randomly and does not seem to be related to
  content being rendered. This time the display hang occurred while I
  was typing in gnome-terminal.

  I can successfully ssh into the system from another computer and run
  ubuntu-bug xorg while the display is frozen.

  Disconnecting the display port cable and reconnecting does not
  successfully restore the image. However, after disconnecting the cable
  and reconnecting, the monitor never resumed from DPMS suspend so the
  signal emitted did in fact change when I disconnected the cable.

  The problem occurs both with official lowlatency Ubuntu kernel and
  custom kernel built from vanilla kernel sources. I haven't found a way
  to deduce if this is in reality caused by kernel, xorg or the
  hardware. However, considering that this happens with many different
  kernel versions, I'd assume this is caused by xorg, instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  Uname: Linux 4.18.0-memalloc-watchdog+ x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,mousepoll,move,resize,imgpng,wall,animation,grid,fade,place,vpswitch,gnomecompat,session,workarounds,expo,scale,ezoom]
  Date: Wed Nov 14 15:23:50 2018
  DistUpgraded: 2016-06-10 11:06:21,514 WARNING no activity on terminal for 300 
seconds (Applying changes)
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: Installed on 2015-02-23 (1360 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-memalloc-watchdog+ 
root=UUID=254cacdb-f61b-45a6-9885-37afd2b598ce ro libata.noacpi=1 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-06-10 (887 days ago)
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  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.:bvr1101:bd02/04/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Sep  6 15:40:48 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   41047 
   vendor DEL
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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

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

[Touch-packages] [Bug 1803192] Re: Internal MIC stopped to work on 18.10

[Daniel van Vugt]

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

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

Title:
  Internal MIC stopped to work on 18.10

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After upgrading my mon's laptop from Kubuntu 18.04 to 18.10, the
  internal Mic stop to work.

  Everything works well (speakers, etc) however no more sound comes as entry 
from Internal Mic.
  I checked and she has chipset ALC269VB

  i update to alsa-driver 1.1.7 without success.
  i checked alsamixer and everything seems ok as with pavucontrol.

  I upgraded my laptop too to 18.10 and i have no issue with internal mic but i 
do not have the same chipset.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paulette   4997 F pulseaudio
   /dev/snd/pcmC0D0c:   paulette   4997 F...m pulseaudio
   /dev/snd/pcmC0D0p:   paulette   4997 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-28 (259 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20180105.2)
  Package: pulseaudio 1:12.2-0ubuntu4 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-mic.conf]
  PackageArchitecture: amd64
  Tags:  cosmic
  Uname: Linux 4.19.0-041900-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-11-04 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE50_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnAcer:bvrV1.11:bd05/24/2011:svnAcer:pnAspire5750G:pvrV1.11:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11:
  dmi.product.name: Aspire 5750G
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1690051] Re: pulseaudio crashed with SIGSEGV in publish_service() from once_callback() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate()

[Daniel van Vugt]

Looks like the crash stopped happening in PulseAudio 12. Can you please
try Ubuntu 18.10?

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

Title:
  pulseaudio crashed with SIGSEGV in publish_service() from
  once_callback() from dispatch_defer() from pa_mainloop_dispatch() from
  pa_mainloop_iterate()

Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

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

[Touch-packages] [Bug 1803470] Re: package linux-image-4.15.0-39-generic 4.15.0-39.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

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

Title:
  package linux-image-4.15.0-39-generic 4.15.0-39.42 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  
  There seems to be a programming error in aptdaemon, the software that allows 
you to install/remove software and to perform other package management related 
tasks.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-39-generic 4.15.0-39.42
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_38_41_generic_45
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1187 F pulseaudio
juan   1898 F pulseaudio
   /dev/snd/controlC0:  gdm1187 F pulseaudio
juan   1898 F pulseaudio
  Date: Wed Nov 14 19:17:20 2018
  Df:
   
  Dmesg:
   
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=45ec2b0c-3e08-4c6c-abb9-645caf9f287b
  InstallationDate: Installed on 2018-02-15 (272 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: TOSHIBA Satellite P55t-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=efe479bd-ea94-4b87-91c8-74190bf43a1b ro quiet splash vt.handoff=1
  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.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.7
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-39-generic 4.15.0-39.42 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to bionic on 2018-10-14 (31 days ago)
  dmi.bios.date: 12/09/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.50
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG20SQ
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.50:bd12/09/2014:svnTOSHIBA:pnSatelliteP55t-B:pvrPSPNVU-03XNC1:rvnTOSHIBA:rnVG20SQ:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite P55t-B
  dmi.product.version: PSPNVU-03XNC1
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode

[Balint Reczey]

** Patch added: 
"0001-debian-systemd.postinst-Skip-daemon-reexec-and-try-r.patch"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1803391/+attachment/5212859/+files/0001-debian-systemd.postinst-Skip-daemon-reexec-and-try-r.patch

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

Title:
  Systemd update installation hangs in unattended-upgrades
  InstallOnShutdown mode

Status in systemd package in Ubuntu:
  New

Bug description:
  Installation of latest systemd update in -security hangs with current
  versions of unattended-upgrades in supported releases. The u-u-side
  fix is tracked in LP: #1778219.

  Reproduction:

  rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown
  Creating uu-systemd-onshutdown
  Starting uu-systemd-onshutdown
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown 
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# apt update -qq
  23 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown 
"true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
  root@uu-systemd-onshutdown:~# apt list --upgradable
  Listing... Done
  apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 
[upgradable from: 0.19.8.1-6]
  kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable 
from: 0.6-3ubuntu0.1]
  libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 
237-3ubuntu10.3]
  root@uu-systemd-onshutdown:~# reboot

  Session terminated, terminating shell...Terminated
  root@uu-systemd-
  rbalint@yogi:~$ 
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown 
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# tail 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ...
  Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ...
  Setting up libsystemd0:amd64 (237-3ubuntu10.6) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Setting up systemd (237-3ubuntu10.6) ...
  Failed to try-restart systemd-networkd.service: Transaction is destructive.
  See system logs and 'systemctl status systemd-networkd.service' for details.
  Failed to try-restart systemd-resolved.service: Transaction is destructive.
  See system logs and 'systemctl status systemd-resolved.service' for details.
  root@uu-systemd-onshutdown:~#  ps -ef  | cat
  UIDPID  PPID  C STIME TTY  TIME CMD
  root 1 0  0 15:34 ?00:00:00 /lib/systemd/systemd --system 
--deserialize 22
  root53 1  0 15:34 ?00:00:00 /lib/systemd/systemd-journald
  systemd+   153 1  0 15:34 ?00:00:00 /lib/systemd/systemd-networkd
  systemd+   154 1  0 15:34 ?00:00:00 /lib/systemd/systemd-resolved
  message+   194 1  

[Touch-packages] [Bug 1803470] [NEW] package linux-image-4.15.0-39-generic 4.15.0-39.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Juan Pablo Florez]

Public bug reported:


There seems to be a programming error in aptdaemon, the software that allows 
you to install/remove software and to perform other package management related 
tasks.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-39-generic 4.15.0-39.42
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_4_15_0_38_41_generic_45
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm1187 F pulseaudio
  juan   1898 F pulseaudio
 /dev/snd/controlC0:  gdm1187 F pulseaudio
  juan   1898 F pulseaudio
Date: Wed Nov 14 19:17:20 2018
Df:
 
Dmesg:
 
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
HibernationDevice: RESUME=UUID=45ec2b0c-3e08-4c6c-abb9-645caf9f287b
InstallationDate: Installed on 2018-02-15 (272 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: TOSHIBA Satellite P55t-B
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=efe479bd-ea94-4b87-91c8-74190bf43a1b ro quiet splash vt.handoff=1
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.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions: grub-pc 2.02-2ubuntu8.7
SourcePackage: initramfs-tools
Title: package linux-image-4.15.0-39-generic 4.15.0-39.42 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
UpgradeStatus: Upgraded to bionic on 2018-10-14 (31 days ago)
dmi.bios.date: 12/09/2014
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 1.50
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: VG20SQ
dmi.board.vendor: TOSHIBA
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.50:bd12/09/2014:svnTOSHIBA:pnSatelliteP55t-B:pvrPSPNVU-03XNC1:rvnTOSHIBA:rnVG20SQ:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
dmi.product.family: PEGA Family
dmi.product.name: Satellite P55t-B
dmi.product.version: PSPNVU-03XNC1
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-package bionic

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

Title:
  package linux-image-4.15.0-39-generic 4.15.0-39.42 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  
  There seems to be a programming error in aptdaemon, the software that allows 
you to install/remove software and to perform other package management related 
tasks.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-39-generic 4.15.0-39.42
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_38_41_generic_45
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1187 F pulseaudio
juan   1898 F pulseaudio
   /dev/snd/controlC0:  gdm1187 F pulseaudio
juan   1898 F pulseaudio
  Date: Wed Nov 14 19:17:20 2018
  Df:
   
  Dmesg:
   
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=45ec2b0c-3e08-4c6c-abb9-645caf9f287b
  InstallationDate: Installed on 2018-02-15 (272 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: TOSHIBA Satellite P55t-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=efe479bd-ea94-4b87-91c8-74190bf43a1b ro quiet splash vt.handoff=1
  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.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.7
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-39-generic 4.15.0-39.42 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
 

[Touch-packages] [Bug 1690051] Re: pulseaudio crashed with SIGSEGV in publish_service() from once_callback() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate()

[Owen Williams]

>From my own debugging, the crash appears to be in this line:

if (!s->userdata->client || avahi_client_get_state(s->userdata->client) != 
AVAHI_CLIENT_S_RUNNING)
return;

adding a check for !s->userdata seems to fix the issue (for some reason,
probably due to a race condition, userdata is null at the time of the
call).

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

Title:
  pulseaudio crashed with SIGSEGV in publish_service() from
  once_callback() from dispatch_defer() from pa_mainloop_dispatch() from
  pa_mainloop_iterate()

Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

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

[Touch-packages] [Bug 1803236] Re: network-manager: switch from dnsmasq (16.04) to systemd-resolve (18.04) breaks DNS

[Yoan]

Here it is:
https://bugzilla.gnome.org/show_bug.cgi?id=797383

** Bug watch added: GNOME Bug Tracker #797383
   https://bugzilla.gnome.org/show_bug.cgi?id=797383

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

Title:
  network-manager: switch from dnsmasq (16.04) to systemd-resolve
  (18.04) breaks DNS

Status in network-manager package in Ubuntu:
  New

Bug description:
  During the do-release-upgrade from 16.04 to 18.04, if the user chooses
  to preserve the old NetworkManager.conf having "dns=dnsmasq", it does
  not preserve dnsmasq as the local resolver.

  It results in a broken DNS configuration, with /etc/resolv.conf set to
  127.0.0.53 but NetworkManager set to dnsmasq.

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

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

[Touch-packages] [Bug 1795678] Re: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[df1234]

I think the following may be associated with this problem.
My system will not resume from suspend
Hard rebooting causes a Kernel panic and inability to mount the file system
>From Grub using advanced options I can eventually "resume" through 
>4.15.0-34-generic
 (but not 4.15.0-36 or 4.15.0-38!) - but it does not resume the previous session

sudo update-initramfs -u
gives:
update-initramfs: Generating /boot/initrd.img-4.15.0-34-generic
W: initramfs-tools configuration sets 
RESUME=UUID=8690dd17-8c64-490e-9c50-d6099db9e1e4
W: but no matching swap device is available.
cp: -r not specified; omitting directory '/etc/udev/rules.d/79-udev-epson.rules'
E: /usr/share/initramfs-tools/hooks/udev failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.15.0-34-generic with 1.

The RESUME=UUID does not exist on my system - presumably it should be
the swap partition?

https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/50437
seems very similar - but that is from 5 years ago so I am nervous given
my proficiency at just following it through.

Is it relevant that
1) My system drive is a SSD (and I am told that you should manually optimise it 
- I have not)
2) My swap partition at 8.5GB is only a little more than my RAM?
3) Disks show a Swap partition on my SSD (sbd6) and an 8.5GB Block device 
(dev/mapper/cryptswap1)

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

Title:
  package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Since upgrading from Lubuntu 16.04 LTS to Lubuntu 18.04 LTS
  When Using Software Updater (either automatic notification or triggering 
through the GUI menus)
  I am getting "The installation or removal of a software package failed." 
error almost every day (more often than not)
  This is the first time I have been prompted to submit a bug report

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-34-generic.
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC295 Analog [ALC295 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1742 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xb1328000 irq 134'
 Mixer name : 'Realtek ALC295'
 Components : 'HDA:10ec0295,103c83f8,0012 
HDA:8086280b,80860101,0010'
 Controls  : 55
 Simple ctrls  : 15
  Date: Tue Oct  2 15:37:20 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=8690dd17-8c64-490e-9c50-d6099db9e1e4
  InstallationDate: Installed on 2017-11-08 (327 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 003: ID 0408:51e9 Quanta Computer, Inc. 
   Bus 001 Device 002: ID 045e:0023 Microsoft Corp. Trackball Optical
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Laptop 15-cc1xx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=c1b34c8f-6ab6-460d-9da0-56b763da6438 ro quiet splash vt.handoff=1
  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.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to bionic on 2018-08-12 (50 days ago)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83F8
  dmi.board.vendor: HP
  dmi.board.version: 46.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.20:bd06/30/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F8:rvr46.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  

[Touch-packages] [Bug 1800813] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: ca-certificates (Ubuntu)
   Status: New => Confirmed

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  Problem occurred while upgrading 16.04 -> 18.04. I can
  t tell if it's a unique problem or not.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Wed Oct 31 02:51:00 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-01-21 (1014 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-10-31 (0 days ago)

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

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

[Touch-packages] [Bug 1803407] Re: Totem freeze while reading a video under wayland

[Sebastien Bacher]

Do you have any error on stdout/stderr? Could you add your journal log
when getting the issue?

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

Title:
  Totem freeze while reading a video under wayland

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  I try to play a video .mp4 or other. Totem don't show the video (only sound) 
and stops after some seconds
  Ubuntu 18.10 64 bits (updated from 18.04). No additional driver. AMD CPU, AMD 
graphic card

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.4-1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 14 17:59:55 2018
  InstallationDate: Installed on 2018-04-27 (201 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to cosmic on 2018-10-16 (29 days ago)
  XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1803407/+subscriptions

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

[Touch-packages] [Bug 1803407] Re: Totem freeze while reading a video under wayland

[Sebastien Bacher]

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

** Summary changed:

- Totem freeze while reading a video
+ Totem freeze while reading a video under wayland

** Changed in: gstreamer1.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Totem freeze while reading a video under wayland

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  I try to play a video .mp4 or other. Totem don't show the video (only sound) 
and stops after some seconds
  Ubuntu 18.10 64 bits (updated from 18.04). No additional driver. AMD CPU, AMD 
graphic card

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.4-1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 14 17:59:55 2018
  InstallationDate: Installed on 2018-04-27 (201 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to cosmic on 2018-10-16 (29 days ago)
  XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1803407/+subscriptions

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

[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358799

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Fix Released
Status in landscape-client source package in Bionic:
  New
Status in systemd source package in Bionic:
  In Progress
Status in landscape-client source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

  
  Used Landscape (Paid Canonical Subscription) to upgrade one of my machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

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

-- 
Mailing list: https://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 1802498] Re: AppArmor - Error Messages log files - Mensagens de Erro arquivos de log

[Seth Arnold]

On Wed, Nov 14, 2018 at 09:03:13AM -, Rami Hakim wrote:
> When ESET v4 was released , AppArmor wasn't available back in the time
> it wasn't developed yet.

While ESET the company predates AppArmor, AppArmor predates this specific
version of ESET NOD32 :)

https://web.archive.org/web/2818164529/http://www.immunix.org:80/documentation.html#codomain

(Back in the 90s AppArmor was known as "CoDomain" and "SubDomain"
and started life as the "mighty morphin[g?] file system".)

> I'm not that experienced with AppArmor , but I think if one can properly
> configure AppArmor to work with ESET , it will work as far as I can
> imagine.

Probably yes, at least if ESET's code injections are relatively
straightforward and don't do anything too surprising. Policies will need
to be adapted to adjust for the injected code, but that's just the way it
is. Used resources must be enumerated.

> But the problem is from ESET's side , so they have made a program that
> doesn't work with SELinux , and not compatible with AppArmor.

I suspect the story on SELinux is similar -- they "just" need to modify
policy to recognize that all domains can communicate all types to the ESET
scanner. It would probably also require modifying policy to allow the code
injection to work in all domains.

> I've been on this problem for a while now , and it seems that ESET is so
> quiet about any replies, So I wonder if Ubuntu team will take a look at
> this problem, I would be very glad if someone fixes it , even if it was
> a workaround but atleast a fix.

We're happy to address specific DENIED messages (though the apparmor mail
list would probably be the better venue) but are unlikely to prioritise
actually installing and configuring ESET ourselves.

https://lists.ubuntu.com/mailman/listinfo/apparmor

We're also unlikely to modify our default policies. The tradeoff between
MAC policy and AV is best made by individual sysadmins.

Thanks

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

Title:
  AppArmor - Error Messages log files - Mensagens de Erro arquivos de
  log

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hello Canonical team - Ubuntu

  Eset Antivirus has some problems with apparmor.

  In Eset I have observed in the last weeks that the updates are being
  carried out, but the logs that have been installed successfully, where
  it was in bold, no longer appear.

  I also realize that these error messages below are constants and I
  would like to know what it is possible to do to resolve them, as they
  are due to mismatch with apparmor. Can Canonial and Eset work together
  to solve this problem?

  Here is the log of Eset Antivirus for Linux Version 4.90 installed on
  Ubuntu 18.10 Cosmic and log dmesg of Ubuntu.

  Thank you in advance for the attention and collaboration of all

  Edson Santos

  

  Obs: Most of these problems are caused by AppArmor , ESET v4 is not
  compatible with AppArmor/SELinux

  I've tried to test things here and there , ESET still does do it's job
  while AppArmor is enabled (I didn't try with AppArmor disabled) , but
  it encounters lot of errors , and while scanning AppArmor will prevent
  ESET from accessing most files as far as I have noticed.

  I don't know if there is a workaround for AppArmor to allow ESET , but
  I don't want to disable it and I don't want to remove ESET.

  
  Thank you in advance for the attention and collaboration of all

  
  Edson Santos

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

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

[Touch-packages] [Bug 1803192] Dependencies.txt

[alain.roger]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1803192/+attachment/5212782/+files/Dependencies.txt

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

Title:
  Internal MIC stopped to work on 18.10

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading my mon's laptop from Kubuntu 18.04 to 18.10, the
  internal Mic stop to work.

  Everything works well (speakers, etc) however no more sound comes as entry 
from Internal Mic.
  I checked and she has chipset ALC269VB

  i update to alsa-driver 1.1.7 without success.
  i checked alsamixer and everything seems ok as with pavucontrol.

  I upgraded my laptop too to 18.10 and i have no issue with internal mic but i 
do not have the same chipset.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paulette   4997 F pulseaudio
   /dev/snd/pcmC0D0c:   paulette   4997 F...m pulseaudio
   /dev/snd/pcmC0D0p:   paulette   4997 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-28 (259 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20180105.2)
  Package: pulseaudio 1:12.2-0ubuntu4 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-mic.conf]
  PackageArchitecture: amd64
  Tags:  cosmic
  Uname: Linux 4.19.0-041900-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-11-04 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE50_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnAcer:bvrV1.11:bd05/24/2011:svnAcer:pnAspire5750G:pvrV1.11:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11:
  dmi.product.name: Aspire 5750G
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1803192] ProcEnviron.txt

[alain.roger]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1803192/+attachment/5212784/+files/ProcEnviron.txt

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

Title:
  Internal MIC stopped to work on 18.10

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading my mon's laptop from Kubuntu 18.04 to 18.10, the
  internal Mic stop to work.

  Everything works well (speakers, etc) however no more sound comes as entry 
from Internal Mic.
  I checked and she has chipset ALC269VB

  i update to alsa-driver 1.1.7 without success.
  i checked alsamixer and everything seems ok as with pavucontrol.

  I upgraded my laptop too to 18.10 and i have no issue with internal mic but i 
do not have the same chipset.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paulette   4997 F pulseaudio
   /dev/snd/pcmC0D0c:   paulette   4997 F...m pulseaudio
   /dev/snd/pcmC0D0p:   paulette   4997 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-28 (259 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20180105.2)
  Package: pulseaudio 1:12.2-0ubuntu4 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-mic.conf]
  PackageArchitecture: amd64
  Tags:  cosmic
  Uname: Linux 4.19.0-041900-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-11-04 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE50_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnAcer:bvrV1.11:bd05/24/2011:svnAcer:pnAspire5750G:pvrV1.11:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11:
  dmi.product.name: Aspire 5750G
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1803192] ProcCpuinfoMinimal.txt

[alain.roger]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1803192/+attachment/5212783/+files/ProcCpuinfoMinimal.txt

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

Title:
  Internal MIC stopped to work on 18.10

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading my mon's laptop from Kubuntu 18.04 to 18.10, the
  internal Mic stop to work.

  Everything works well (speakers, etc) however no more sound comes as entry 
from Internal Mic.
  I checked and she has chipset ALC269VB

  i update to alsa-driver 1.1.7 without success.
  i checked alsamixer and everything seems ok as with pavucontrol.

  I upgraded my laptop too to 18.10 and i have no issue with internal mic but i 
do not have the same chipset.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paulette   4997 F pulseaudio
   /dev/snd/pcmC0D0c:   paulette   4997 F...m pulseaudio
   /dev/snd/pcmC0D0p:   paulette   4997 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-28 (259 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20180105.2)
  Package: pulseaudio 1:12.2-0ubuntu4 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-mic.conf]
  PackageArchitecture: amd64
  Tags:  cosmic
  Uname: Linux 4.19.0-041900-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-11-04 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE50_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnAcer:bvrV1.11:bd05/24/2011:svnAcer:pnAspire5750G:pvrV1.11:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11:
  dmi.product.name: Aspire 5750G
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1803192] Re: Internal MIC stopped to work on 18.10

[alain.roger]

apport information

** Tags added: apport-collected

** Description changed:

  After upgrading my mon's laptop from Kubuntu 18.04 to 18.10, the
  internal Mic stop to work.
  
  Everything works well (speakers, etc) however no more sound comes as entry 
from Internal Mic.
  I checked and she has chipset ALC269VB
  
  i update to alsa-driver 1.1.7 without success.
  i checked alsamixer and everything seems ok as with pavucontrol.
  
- I upgraded my laptop too to 18.10 and i have no issue with internal mic
- but i do not have the same chipset.
+ I upgraded my laptop too to 18.10 and i have no issue with internal mic but i 
do not have the same chipset.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  paulette   4997 F pulseaudio
+  /dev/snd/pcmC0D0c:   paulette   4997 F...m pulseaudio
+  /dev/snd/pcmC0D0p:   paulette   4997 F...m pulseaudio
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 18.10
+ InstallationDate: Installed on 2018-02-28 (259 days ago)
+ InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20180105.2)
+ Package: pulseaudio 1:12.2-0ubuntu4 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-mic.conf]
+ PackageArchitecture: amd64
+ Tags:  cosmic
+ Uname: Linux 4.19.0-041900-generic x86_64
+ UpgradeStatus: Upgraded to cosmic on 2018-11-04 (10 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/24/2011
+ dmi.bios.vendor: Acer
+ dmi.bios.version: V1.11
+ dmi.board.asset.tag: Base Board Asset Tag
+ dmi.board.name: JE50_HR
+ dmi.board.vendor: Acer
+ dmi.board.version: Base Board Version
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Acer
+ dmi.chassis.version: V1.11
+ dmi.modalias: 
dmi:bvnAcer:bvrV1.11:bd05/24/2011:svnAcer:pnAspire5750G:pvrV1.11:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11:
+ dmi.product.name: Aspire 5750G
+ dmi.product.version: V1.11
+ dmi.sys.vendor: Acer

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1803192/+attachment/5212780/+files/AlsaInfo.txt

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

Title:
  Internal MIC stopped to work on 18.10

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading my mon's laptop from Kubuntu 18.04 to 18.10, the
  internal Mic stop to work.

  Everything works well (speakers, etc) however no more sound comes as entry 
from Internal Mic.
  I checked and she has chipset ALC269VB

  i update to alsa-driver 1.1.7 without success.
  i checked alsamixer and everything seems ok as with pavucontrol.

  I upgraded my laptop too to 18.10 and i have no issue with internal mic but i 
do not have the same chipset.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paulette   4997 F pulseaudio
   /dev/snd/pcmC0D0c:   paulette   4997 F...m pulseaudio
   /dev/snd/pcmC0D0p:   paulette   4997 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-28 (259 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20180105.2)
  Package: pulseaudio 1:12.2-0ubuntu4 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-mic.conf]
  PackageArchitecture: amd64
  Tags:  cosmic
  Uname: Linux 4.19.0-041900-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-11-04 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE50_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnAcer:bvrV1.11:bd05/24/2011:svnAcer:pnAspire5750G:pvrV1.11:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11:
  dmi.product.name: Aspire 5750G
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1803192] Re: Internal MIC stopped to work on 18.10

[alain.roger]

Here they are

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

Title:
  Internal MIC stopped to work on 18.10

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading my mon's laptop from Kubuntu 18.04 to 18.10, the
  internal Mic stop to work.

  Everything works well (speakers, etc) however no more sound comes as entry 
from Internal Mic.
  I checked and she has chipset ALC269VB

  i update to alsa-driver 1.1.7 without success.
  i checked alsamixer and everything seems ok as with pavucontrol.

  I upgraded my laptop too to 18.10 and i have no issue with internal mic but i 
do not have the same chipset.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paulette   4997 F pulseaudio
   /dev/snd/pcmC0D0c:   paulette   4997 F...m pulseaudio
   /dev/snd/pcmC0D0p:   paulette   4997 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-28 (259 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20180105.2)
  Package: pulseaudio 1:12.2-0ubuntu4 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-mic.conf]
  PackageArchitecture: amd64
  Tags:  cosmic
  Uname: Linux 4.19.0-041900-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-11-04 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE50_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnAcer:bvrV1.11:bd05/24/2011:svnAcer:pnAspire5750G:pvrV1.11:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11:
  dmi.product.name: Aspire 5750G
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1803192] PulseList.txt

[alain.roger]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1803192/+attachment/5212785/+files/PulseList.txt

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

Title:
  Internal MIC stopped to work on 18.10

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading my mon's laptop from Kubuntu 18.04 to 18.10, the
  internal Mic stop to work.

  Everything works well (speakers, etc) however no more sound comes as entry 
from Internal Mic.
  I checked and she has chipset ALC269VB

  i update to alsa-driver 1.1.7 without success.
  i checked alsamixer and everything seems ok as with pavucontrol.

  I upgraded my laptop too to 18.10 and i have no issue with internal mic but i 
do not have the same chipset.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paulette   4997 F pulseaudio
   /dev/snd/pcmC0D0c:   paulette   4997 F...m pulseaudio
   /dev/snd/pcmC0D0p:   paulette   4997 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-28 (259 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20180105.2)
  Package: pulseaudio 1:12.2-0ubuntu4 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-mic.conf]
  PackageArchitecture: amd64
  Tags:  cosmic
  Uname: Linux 4.19.0-041900-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-11-04 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE50_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnAcer:bvrV1.11:bd05/24/2011:svnAcer:pnAspire5750G:pvrV1.11:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11:
  dmi.product.name: Aspire 5750G
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1803192] CurrentDmesg.txt

[alain.roger]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1803192/+attachment/5212781/+files/CurrentDmesg.txt

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

Title:
  Internal MIC stopped to work on 18.10

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading my mon's laptop from Kubuntu 18.04 to 18.10, the
  internal Mic stop to work.

  Everything works well (speakers, etc) however no more sound comes as entry 
from Internal Mic.
  I checked and she has chipset ALC269VB

  i update to alsa-driver 1.1.7 without success.
  i checked alsamixer and everything seems ok as with pavucontrol.

  I upgraded my laptop too to 18.10 and i have no issue with internal mic but i 
do not have the same chipset.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paulette   4997 F pulseaudio
   /dev/snd/pcmC0D0c:   paulette   4997 F...m pulseaudio
   /dev/snd/pcmC0D0p:   paulette   4997 F...m pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-28 (259 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20180105.2)
  Package: pulseaudio 1:12.2-0ubuntu4 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-mic.conf]
  PackageArchitecture: amd64
  Tags:  cosmic
  Uname: Linux 4.19.0-041900-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-11-04 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE50_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnAcer:bvrV1.11:bd05/24/2011:svnAcer:pnAspire5750G:pvrV1.11:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11:
  dmi.product.name: Aspire 5750G
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1803407] Re: Totem freeze while reading a video

[J-Paul BERARD]

At the end, this problem is due to Wayland !
In an X session, Totem is able to read the video !

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

Title:
  Totem freeze while reading a video

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  I try to play a video .mp4 or other. Totem don't show the video (only sound) 
and stops after some seconds
  Ubuntu 18.10 64 bits (updated from 18.04). No additional driver. AMD CPU, AMD 
graphic card

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.4-1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 14 17:59:55 2018
  InstallationDate: Installed on 2018-04-27 (201 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to cosmic on 2018-10-16 (29 days ago)
  XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1803407/+subscriptions

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

[Touch-packages] [Bug 1803407] [NEW] Totem freeze while reading a video

[J-Paul BERARD]

Public bug reported:

I try to play a video .mp4 or other. Totem don't show the video (only sound) 
and stops after some seconds
Ubuntu 18.10 64 bits (updated from 18.04). No additional driver. AMD CPU, AMD 
graphic card

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: libgstreamer1.0-0 1.14.4-1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 14 17:59:55 2018
InstallationDate: Installed on 2018-04-27 (201 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gstreamer1.0
UpgradeStatus: Upgraded to cosmic on 2018-10-16 (29 days ago)
XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'/var/log/Xorg.0.log'

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic wayland-session

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

Title:
  Totem freeze while reading a video

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  I try to play a video .mp4 or other. Totem don't show the video (only sound) 
and stops after some seconds
  Ubuntu 18.10 64 bits (updated from 18.04). No additional driver. AMD CPU, AMD 
graphic card

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.4-1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 14 17:59:55 2018
  InstallationDate: Installed on 2018-04-27 (201 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to cosmic on 2018-10-16 (29 days ago)
  XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1803407/+subscriptions

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

[Touch-packages] [Bug 1803176] Re: Search in Nautilus does not work correctly when called from other apps

[Rainer Rohde]

Ah, thanks for the clarification. I actually went to the #Ubuntu IRC
chat and asked - if called by an app, is the panel still nautilus, and I
was told "yes", hence I filed the bug report against it. Never knew that
this "GTK filechooser" is a different animal.

Anything else I need to do/provide to this ticket?

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

Title:
  Search in Nautilus does not work correctly when called from other apps

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  When Nautilus is called from another app, e.g., Thunderbird > Attach
  File to email (or Gedit > Save file) the search (via the magnifying
  glass icon in the top right) only allows for 1 character to be
  entered, and then jumps to the bottom right and subsequent characters
  appear there.

  This behavior, of course, messes up the expected search results as the
  search is split into two fields/areas of the panel.

  In contrast, when opening up a Nautilus browser panel directly, any
  search query entered from the magnifying glass icon stays in the text
  entry area as expected, and the search results work well.

  The expectation is that when another app calls Nautilus, the search
  function works as if it does when working directly out of Nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nautilus 1:3.26.4-0ubuntu7
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 13 13:05:42 2018
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'1165x787+417+87'"
   b'org.gnome.nautilus.compression' b'default-compression-format' b"'7z'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency']"
  InstallationDate: Installed on 2018-10-27 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: dropbox 2015.10.28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1803176/+subscriptions

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

[Touch-packages] [Bug 997217] Re: salsauthd maxes cpu

[Andreas Hasenack]

xenial verification

Confirming bug:

ubuntu@xenial-saslauthd:~$ apt-cache policy sasl2-bin
sasl2-bin:
  Installed: 2.1.26.dfsg1-14build1
  Candidate: 2.1.26.dfsg1-14build1
  Version table:
 *** 2.1.26.dfsg1-14build1 500
500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages


Confirmed saslauthd at 100% CPU after the test command:
  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 

   
  root  20   0   90860972  0 R 100.0  0.0   0:05.72 saslauthd   
   


subsequent testsaslauthd commands just block, as expected due to the bug.


Repeating the test with the package from proposed:
ubuntu@xenial-saslauthd:~$ apt-cache policy sasl2-bin
sasl2-bin:
  Installed: 2.1.26.dfsg1-14ubuntu0.1
  Candidate: 2.1.26.dfsg1-14ubuntu0.1
  Version table:
 *** 2.1.26.dfsg1-14ubuntu0.1 500
500 http://br.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages

Not only does saslauthd not start eating cpu, it keeps working:
with dovecot stopped:
ubuntu@xenial-saslauthd:~$ sudo testsaslauthd -u ubuntu -p ubuntu
0: NO "authentication failed"

Starting up dovecot and trying again:
ubuntu@xenial-saslauthd:~$ sudo service dovecot start
ubuntu@xenial-saslauthd:~$ sudo testsaslauthd -u ubuntu -p ubuntu
0: OK "Success."
ubuntu@xenial-saslauthd:~$ 

Xenial verification completed successfully.

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

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

Title:
  salsauthd maxes cpu

Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 source package in Precise:
  Won't Fix
Status in cyrus-sasl2 source package in Trusty:
  Invalid
Status in cyrus-sasl2 source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  The rimap authentication mechanism in saslauthd can hit a condition
  where it will start spinning and using all available CPU. This
  condition can be easily encountered when an authentication is
  happening and the imap service is being restarted.

  Furthermore, the saslauthd child process that picked up that
  authentication request and that is spinning now won't be reaped nor
  can it service further requests. If all children are left in this
  state, the authentication service as a whole won't be working anymore.

  [Test Case]

  This test can be performed in a LXD or VM.

  * install the needed packages. mail-stack-delivery is used to have an
  imap server available on localhost that needs no further
  configuration. Accept the defaults for all debconf prompts:

  sudo apt update
  sudo apt install sasl2-bin mail-stack-delivery

  * set the password "ubuntu" for the ubuntu user
  echo ubuntu:ubuntu | sudo chpasswd

  * start saslauthd like this, with just one child:
  sudo /usr/sbin/saslauthd -a rimap -O localhost -r -n 1

  * restart dovecot
  sudo service dovecot restart

  * test saslauthd authentication:
  $ sudo testsaslauthd -u ubuntu -p ubuntu
  0: OK "Success."

  * Now let's break it. In one terminal watch the output of top:
  top

  * in another terminal, run the following:
  sudo testsaslauthd -u ubuntu -p ubuntu & sleep 1; sudo service dovecot stop

  * observe in the "top" terminal that saslauthd is consuming a lot of
  cpu. If that's not happening, try starting dovecot again and adjusting
  the sleep value in the previous test command, but 1s was enough in all
  my runs.

  * start dovecot and repeat the authentication request. Since the only 
saslauthd child is now spinning, this will block:
  sudo service dovecot start
  $ sudo testsaslauthd -u ubuntu -p ubuntu
  

  [Regression Potential]
  This fix relies on read(2) returning zero bytes when the connection is 
dropped, and that is clearly documented in its manpage:

  "On  success,  the  number  of  bytes read is returned (zero indicates
  end of file),"

  The select manpage also documents such a case being a valid case to
  indicate that a socket is ready to be read from, and that it won't
  block:

  "The file descriptors listed in readfds will be watched to see if
  characters become available for reading (more precisely, to see  if  a
  read will  not  block;  in  particular, a file descriptor is also
  ready on end-of-file)"

  This patch is what was used upstream, and is also present in bionic.

  I can't think of regressions specific to this change, other than the
  usual risk of rebuilding a widely used library (sasl2) in an
  environment different from the one from when xenial was released,
  i.e., different libraries available, maybe different system-wide build
  options, etc.

  [Other Info]
  Trusty is still not accounting for read() returning zero being an end-of-file 
case, but the loop 

[Touch-packages] [Bug 1800877] Re: iproute2/xenial: Add support for the VF Trust setting (fix IPv6 multicast under SR-IOV on Mellanox adapters)

[Mauricio Faria de Oliveira]

autopkgtests for open-vm-tools,
failures in amd64 and i386.

These are consistently failing since May 14th, 2018
for a lot of other packages, thus not a change from
this upload.

Thanks,
Mauricio

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

Title:
  iproute2/xenial: Add support for the VF Trust setting (fix IPv6
  multicast under SR-IOV on Mellanox adapters)

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * An VM's VF cannot receive IPv6 multicast traffic
     from other VMs' VFs in the same Mellanox adapter
     _if_ its VF trust setting is not enabled, and on
     Xenial currently iproute2 _cannot_ enable it.

   * This breaks IPv6 NDP (Neighbor Discovery Protocol)
     in that scenario.

   * This upload adds three iproute2 upstream commits
     to enable/disable the VF setting, which resolves
     that problem/limitation.

  [Test Case]

   * Check 'ip link help' for the 'trust' option:

     Before:

   # ip link help 2>&1 | grep trust
   

     After:

   # ip link help 2>&1 | grep trust
   [ trust { on | off} ] ]

   * Check 'ip link show dev PF' for 'trust on|off' field in VFs.

     Before: (trust field _is not_ present)

   # ip link show dev ens1f0
   ...
   vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
   vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

     After: (trust field _is_ present)

   # ip link show dev ens1f0
   ...
   vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
   vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off

   * Set the VF trust on/off and check it:

   Set VF 0 trust on:

   # ip link set ens1f0 vf 0 trust on
   # ip link show dev ens1f0 | grep trust
   vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust on
   vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off

   Set VF 0 trust off:

   # ip link set ens1f0 vf 0 trust off
   # ip link show dev ens1f0 | grep trust
   vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
   vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off

  [Regression Potential]

   * Regression potential is low because the commits just add the
     netlink attribute for the userspace-kernel interface and the
     ways to set/clear it, and show the current value to the user.

   * Regressions could happen _if_ the user turns the setting on
     (it's disabled by default) and there's a problem/bug likely
     in _other_ component that depends on that setting (which is
     something to fix on such component).

  [Other Info]

   * The users that reported this problem have verified
     the test package with these changes, and confirmed
     that it now works correctly for IPv6 NDP/multicast.

   * Upstream commits:
   
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=dddf1b44126e
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=fe9322781e63
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=b6d77d9ee312

   * Only affect Xenial release :

   # rmadison iproute2
   iproute2 | 4.3.0-1ubuntu3.16.04.3 | xenial-updates
   iproute2 | 4.15.0-2ubuntu1| bionic 
   iproute2 | 4.18.0-1ubuntu2| cosmic
   iproute2 | 4.18.0-1ubuntu2| disco  

   # iproute2 upstream vcs

   $ git describe --contains dddf1b44126e
   v4.4.0~67

   $ git describe --contains b6d77d9ee312
   v4.5.0~47

   $ git describe --contains fe9322781e63
   v4.6.0~32

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

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

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

[Balint Reczey]

** This bug is no longer a duplicate of bug 1778219
   unattended-upgrades hangs on shutdown, leaves system in a broken state

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

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

Status in systemd package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  not sure. It just notifies a failure of installation

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21.8
  ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Tue Nov 13 06:26:36 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-06-27 (138 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Dell Inc. OptiPlex 9020
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=d6f84918-e5e2-4e2e-abb9-cc9127cf0382 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29
  SourcePackage: systemd
  Title: package udev 229-4ubuntu21.8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0N4YC8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd09/14/2015:svnDellInc.:pnOptiPlex9020:pvr00:rvnDellInc.:rn0N4YC8:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1800877] Re: iproute2/xenial: Add support for the VF Trust setting (fix IPv6 multicast under SR-IOV on Mellanox adapters)

[Mauricio Faria de Oliveira]

autopkgtests for ubuntu-fan
(triggered by this iproute2 upload)

The test failure in ubuntu-fan's lxd test (the thing
that is failing in these autopkgtests) does look flaky.

Looking at autopkgtest logs for ubuntu-fan on xenial, there's a series of 
retriggers
for the _same_ version of docker.io that led to different results (fail/pass), 
in
several architectures (and on arm64 it didn't help at all yet).

Based on that, I asked Dan (ddstreet) to retrigger autopkgtests
for ubuntu-fan on xenial for iproute2 and half of architectures
now pass (summary below).

I'll ask Dan to retrigger the pending/failing architectures a
few times more.

Thus, hopefully the autopkgtest failures in the pending/failing
architectures should not be a blocker for this SRU.

Summary:
- xenial/amd64: 
  - iproute2:  1x fail, then pass.
  - docker.io: 2x fail, then pass.
- xenial/arm64:
  - iproute2:  3x fail, no pass.
  - docker.io: 5x fail, no pass.
- xenial/armhf:
  - iproute2:  1x pass.
  - docker.io: 1x pass.
- xenial/i386:
  - iproute2:  2x fail, no pass.
  - docker.io: 1x fail, then pass.
- xenial/ppc64el:
  - iproute2:  1x fail, then pass.
  - docker.io: 1x pass.
- xenial/s390x:
  - iproute2:  3x fail, no pass.
  - docker.io: 1x pass.

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

Title:
  iproute2/xenial: Add support for the VF Trust setting (fix IPv6
  multicast under SR-IOV on Mellanox adapters)

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * An VM's VF cannot receive IPv6 multicast traffic
     from other VMs' VFs in the same Mellanox adapter
     _if_ its VF trust setting is not enabled, and on
     Xenial currently iproute2 _cannot_ enable it.

   * This breaks IPv6 NDP (Neighbor Discovery Protocol)
     in that scenario.

   * This upload adds three iproute2 upstream commits
     to enable/disable the VF setting, which resolves
     that problem/limitation.

  [Test Case]

   * Check 'ip link help' for the 'trust' option:

     Before:

   # ip link help 2>&1 | grep trust
   

     After:

   # ip link help 2>&1 | grep trust
   [ trust { on | off} ] ]

   * Check 'ip link show dev PF' for 'trust on|off' field in VFs.

     Before: (trust field _is not_ present)

   # ip link show dev ens1f0
   ...
   vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
   vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

     After: (trust field _is_ present)

   # ip link show dev ens1f0
   ...
   vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
   vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off

   * Set the VF trust on/off and check it:

   Set VF 0 trust on:

   # ip link set ens1f0 vf 0 trust on
   # ip link show dev ens1f0 | grep trust
   vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust on
   vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off

   Set VF 0 trust off:

   # ip link set ens1f0 vf 0 trust off
   # ip link show dev ens1f0 | grep trust
   vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
   vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off

  [Regression Potential]

   * Regression potential is low because the commits just add the
     netlink attribute for the userspace-kernel interface and the
     ways to set/clear it, and show the current value to the user.

   * Regressions could happen _if_ the user turns the setting on
     (it's disabled by default) and there's a problem/bug likely
     in _other_ component that depends on that setting (which is
     something to fix on such component).

  [Other Info]

   * The users that reported this problem have verified
     the test package with these changes, and confirmed
     that it now works correctly for IPv6 NDP/multicast.

   * Upstream commits:
   
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=dddf1b44126e
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=fe9322781e63
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=b6d77d9ee312

   * Only affect Xenial release :

   # rmadison iproute2
   iproute2 | 4.3.0-1ubuntu3.16.04.3 | xenial-updates
   iproute2 | 4.15.0-2ubuntu1| bionic 
   iproute2 | 4.18.0-1ubuntu2| cosmic
   iproute2 | 4.18.0-1ubuntu2| disco  

   # iproute2 upstream vcs

   $ git describe --contains dddf1b44126e
   v4.4.0~67

   $ git describe --contains b6d77d9ee312
   v4.5.0~47

   $ git describe --contains fe9322781e63
   v4.6.0~32

To manage notifications about this bug go to:

[Touch-packages] [Bug 796588] Re: Fine-grained network mediation

[John Johansen]

In 4.20 we landed some of the infrastructure to support this.
Specifically secmark support was landed which provides the
infrastructure needed for apparmor labels to interact with iptables and
iptables to interact with apparmor.

This isn't something generally available for use yet as it
infrastructure work necessary for full fine grained network mediation

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

Title:
  Fine-grained network mediation

Status in AppArmor:
  In Progress
Status in apparmor package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apparmor

  This is a wishlist item / feature request.

  Increase the granularity of network restrictions to allow
  specification of which ports or ranges of ports can or can't be used
  by an application.  This functionality is available in systrace if
  either the example or code would be of help:

  http://en.wikipedia.org/wiki/Systrace

  http://www.systrace.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/796588/+subscriptions

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

[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode

[Dimitri John Ledkov]

that's really really really bad!

_systemctl try-restart systemd-journald.service || true

_must_ not hang, it should either succeed or fail. that is the whole
point of try-restart

I wonder if `--no-block` would help here, but that's also a bandaid.
Imho systemctl/systemd itself shouldn't be able to hang systems like
that and like should reject this job submission if it will be impossible
to complete.

** Changed in: systemd (Ubuntu)
   Importance: Undecided => High

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

Title:
  Systemd update installation hangs in unattended-upgrades
  InstallOnShutdown mode

Status in systemd package in Ubuntu:
  New

Bug description:
  Installation of latest systemd update in -security hangs with current
  versions of unattended-upgrades in supported releases. The u-u-side
  fix is tracked in LP: #1778219.

  Reproduction:

  rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown
  Creating uu-systemd-onshutdown
  Starting uu-systemd-onshutdown
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown 
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# apt update -qq
  23 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown 
"true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
  root@uu-systemd-onshutdown:~# apt list --upgradable
  Listing... Done
  apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 
[upgradable from: 0.19.8.1-6]
  kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable 
from: 0.6-3ubuntu0.1]
  libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 
237-3ubuntu10.3]
  root@uu-systemd-onshutdown:~# reboot

  Session terminated, terminating shell...Terminated
  root@uu-systemd-
  rbalint@yogi:~$ 
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown 
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# tail 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ...
  Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ...
  Setting up libsystemd0:amd64 (237-3ubuntu10.6) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Setting up systemd (237-3ubuntu10.6) ...
  Failed to try-restart systemd-networkd.service: Transaction is destructive.
  See system logs and 'systemctl status systemd-networkd.service' for details.
  Failed to try-restart systemd-resolved.service: Transaction is destructive.
  See system logs and 'systemctl status systemd-resolved.service' for details.
  root@uu-systemd-onshutdown:~#  ps -ef  | cat
  UIDPID  PPID  C STIME TTY  TIME CMD
  root 1 0  0 15:34 ?00:00:00 /lib/systemd/systemd --system 
--deserialize 22
  root53 1  0 

[Touch-packages] [Bug 1803391] [NEW] Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode

[Balint Reczey]

Public bug reported:

Installation of latest systemd update in -security hangs with current
versions of unattended-upgrades in supported releases. The u-u-side fix
is tracked in LP: #1778219.

Reproduction:

rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown
Creating uu-systemd-onshutdown
Starting uu-systemd-onshutdown
rbalint@yogi:~$ lxc shell uu-systemd-onshutdown 
mesg: ttyname failed: No such device
root@uu-systemd-onshutdown:~# apt update -qq
23 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown 
"true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
root@uu-systemd-onshutdown:~# apt list --upgradable
Listing... Done
apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4]
gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 
[upgradable from: 0.19.8.1-6]
kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable 
from: 0.6-3ubuntu0.1]
libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 
237-3ubuntu10.3]
lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27]
python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 
237-3ubuntu10.3]
systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 
237-3ubuntu10.3]
root@uu-systemd-onshutdown:~# reboot

Session terminated, terminating shell...Terminated
root@uu-systemd-
rbalint@yogi:~$ 
rbalint@yogi:~$ lxc shell uu-systemd-onshutdown 
mesg: ttyname failed: No such device
root@uu-systemd-onshutdown:~# tail 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ...
Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ...
Setting up libsystemd0:amd64 (237-3ubuntu10.6) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Setting up systemd (237-3ubuntu10.6) ...
Failed to try-restart systemd-networkd.service: Transaction is destructive.
See system logs and 'systemctl status systemd-networkd.service' for details.
Failed to try-restart systemd-resolved.service: Transaction is destructive.
See system logs and 'systemctl status systemd-resolved.service' for details.
root@uu-systemd-onshutdown:~#  ps -ef  | cat
UIDPID  PPID  C STIME TTY  TIME CMD
root 1 0  0 15:34 ?00:00:00 /lib/systemd/systemd --system 
--deserialize 22
root53 1  0 15:34 ?00:00:00 /lib/systemd/systemd-journald
systemd+   153 1  0 15:34 ?00:00:00 /lib/systemd/systemd-networkd
systemd+   154 1  0 15:34 ?00:00:00 /lib/systemd/systemd-resolved
message+   194 1  0 15:34 ?00:00:00 /usr/bin/dbus-daemon --system 
--address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
root   572 1  0 15:35 ?00:00:00 /usr/bin/python3 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
root   586   572  0 15:35 ?00:00:08 /usr/bin/python3 
/usr/bin/unattended-upgrade
root   829 0  0 15:35 ?00:00:00 su -l
root   830   829  0 15:35 ?00:00:00 -su
root  1244 1  0 15:35 ?00:00:00 /lib/systemd/systemd-udevd
root  1918 1  0 15:35 ?00:00:00 /usr/sbin/sshd -D
root  1952   586  0 15:35 ?00:00:00 /usr/bin/python3 

[Touch-packages] [Bug 216847] Re: sshd will not start at boot if ListenAddress is set, because network interface is not yet up

[Simon Déziel]

Sorry, it should have read "After=network-online.target".

https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/#cutthecraphowdoimakesurethatmyservicestartsafterthenetworkisreallyonline

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

Title:
  sshd will not start at boot if ListenAddress is set, because network
  interface is not yet up

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: openssh-server

  The sshd will not start at boot if the ListenAddress option in
  /etc/ssh/sshd_config is set to an IPv4 address other then 0.0.0.0 .

  I am using Ubuntu 7.10 and the version 1:4.6p1-5ubuntu0.2 of the 
openssh-server package.
  I would expect that sshd is started after boot but it will not and I found 
this in /var/log/auth.log:

  sshd[4527]: error: Bind to port 22 on 10.1.1.22 failed: Cannot assign 
requested address.
  sshd[4527]: fatal: Cannot bind any address.

  Once the System is started you can start/stop the sshd with the
  /etc/init.d/ssh script without any problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/216847/+subscriptions

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

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

[Robert Giles]

Brian,

Thanks for sleuthing out a fix for this;  I wanted to add that this also
seems to work for netbooting 18.10.

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  netbooting the bionic live CD[1] over NFS goes straight to maintenance
  mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

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

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

[Touch-packages] [Bug 216847] Re: sshd will not start at boot if ListenAddress is set, because network interface is not yet up

[Simon Déziel]

@Rodman, as a workaround, maybe you could try to add an "After=systemd-
networkd-wait-online.service" clause in a drop-in snippet?

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

Title:
  sshd will not start at boot if ListenAddress is set, because network
  interface is not yet up

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: openssh-server

  The sshd will not start at boot if the ListenAddress option in
  /etc/ssh/sshd_config is set to an IPv4 address other then 0.0.0.0 .

  I am using Ubuntu 7.10 and the version 1:4.6p1-5ubuntu0.2 of the 
openssh-server package.
  I would expect that sshd is started after boot but it will not and I found 
this in /var/log/auth.log:

  sshd[4527]: error: Bind to port 22 on 10.1.1.22 failed: Cannot assign 
requested address.
  sshd[4527]: fatal: Cannot bind any address.

  Once the System is started you can start/stop the sshd with the
  /etc/init.d/ssh script without any problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/216847/+subscriptions

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

[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode

[Balint Reczey]

systemctl(1) does not say that try-restart must not hang and --no-block
in maintainer scripts would make maintainer scripts continue and execute
actions in highly unpredictable states.

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

Title:
  Systemd update installation hangs in unattended-upgrades
  InstallOnShutdown mode

Status in systemd package in Ubuntu:
  New

Bug description:
  Installation of latest systemd update in -security hangs with current
  versions of unattended-upgrades in supported releases. The u-u-side
  fix is tracked in LP: #1778219.

  Reproduction:

  rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown
  Creating uu-systemd-onshutdown
  Starting uu-systemd-onshutdown
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown 
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# apt update -qq
  23 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown 
"true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
  root@uu-systemd-onshutdown:~# apt list --upgradable
  Listing... Done
  apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 
[upgradable from: 0.19.8.1-6]
  kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 
2.56.2-0ubuntu0.18.04.2]
  libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3]
  libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable 
from: 0.6-3ubuntu0.1]
  libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 
[upgradable from: 237-3ubuntu10.3]
  libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 
3.0.1-0ubuntu1~18.04.1]
  openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 
[upgradable from: 1:7.6p1-4]
  python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 
2.20.9-0ubuntu7.4]
  systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable 
from: 237-3ubuntu10.3]
  ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 
1:18.04.27]
  udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 
237-3ubuntu10.3]
  root@uu-systemd-onshutdown:~# reboot

  Session terminated, terminating shell...Terminated
  root@uu-systemd-
  rbalint@yogi:~$ 
  rbalint@yogi:~$ lxc shell uu-systemd-onshutdown 
  mesg: ttyname failed: No such device
  root@uu-systemd-onshutdown:~# tail 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ...
  Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ...
  Setting up libsystemd0:amd64 (237-3ubuntu10.6) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Setting up systemd (237-3ubuntu10.6) ...
  Failed to try-restart systemd-networkd.service: Transaction is destructive.
  See system logs and 'systemctl status systemd-networkd.service' for details.
  Failed to try-restart systemd-resolved.service: Transaction is destructive.
  See system logs and 'systemctl status systemd-resolved.service' for details.
  root@uu-systemd-onshutdown:~#  ps -ef  | cat
  UIDPID  PPID  C STIME TTY  TIME CMD
  root 1 0  0 15:34 ?00:00:00 /lib/systemd/systemd --system 
--deserialize 22
  root53 1  0 15:34 ?00:00:00 /lib/systemd/systemd-journald
  systemd+   153 1  0 15:34 ?00:00:00 /lib/systemd/systemd-networkd
  systemd+   154 1  0 15:34 ?00:00:00 /lib/systemd/systemd-resolved
  message+   194 1  0 15:34 ?00:00:00 /usr/bin/dbus-daemon --system 

[Touch-packages] [Bug 216847] Re: sshd will not start at boot if ListenAddress is set, because network interface is not yet up

[Rodman]

This is still broken in 18.04 Server.  Setting the listen address fails
to load the SSHD daemon at boot time.  You have to have console access
and do a "service sshd restart" to fix.

How is this bug still here???

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

Title:
  sshd will not start at boot if ListenAddress is set, because network
  interface is not yet up

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: openssh-server

  The sshd will not start at boot if the ListenAddress option in
  /etc/ssh/sshd_config is set to an IPv4 address other then 0.0.0.0 .

  I am using Ubuntu 7.10 and the version 1:4.6p1-5ubuntu0.2 of the 
openssh-server package.
  I would expect that sshd is started after boot but it will not and I found 
this in /var/log/auth.log:

  sshd[4527]: error: Bind to port 22 on 10.1.1.22 failed: Cannot assign 
requested address.
  sshd[4527]: fatal: Cannot bind any address.

  Once the System is started you can start/stop the sshd with the
  /etc/init.d/ssh script without any problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/216847/+subscriptions

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

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

[Dimitri John Ledkov]

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

Hi, your system appears to have an invalid init.d script which is
causing boot ordering failures

insserv: warning: script 'S65nifi' missing LSB tags and overrides
insserv: warning: script 'nifi' missing LSB tags and overrides
insserv: There is a loop between service plymouth and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1


Do you know what nifi is ? Can you fix it's init.d script or remove it?

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

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

Status in systemd package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  not sure. It just notifies a failure of installation

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21.8
  ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Tue Nov 13 06:26:36 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-06-27 (138 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Dell Inc. OptiPlex 9020
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=d6f84918-e5e2-4e2e-abb9-cc9127cf0382 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29
  SourcePackage: systemd
  Title: package udev 229-4ubuntu21.8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0N4YC8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd09/14/2015:svnDellInc.:pnOptiPlex9020:pvr00:rvnDellInc.:rn0N4YC8:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state

[Launchpad Bug Tracker]

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

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

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

Title:
  unattended-upgrades hangs on shutdown, leaves system in a broken state

Status in apt package in Ubuntu:
  Invalid
Status in init-system-helpers package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in init-system-helpers source package in Xenial:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  Confirmed
Status in init-system-helpers source package in Bionic:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in unattended-upgrades source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * Unattended-upgrades hangs and gets killed when installing upgrades
  that stat/stop services on shutdown, leaving the system in a broken
  state

  [Test Case]

   * Install an updated bionic system:
 $ lxc launch ubuntu:18.04 uu-shutdown-test
 # apt update
 ...

   * When testing the fixed version, install upgrade u-u at this point checking 
that u-u.service is set up before and is wanted by shutdown.target:
  # systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket" 
[color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
 Color legend: black = Requires
   dark blue = Requisite
   dark grey = Wants
   red   = Conflicts
   green = After

   * Configure u-u to run on shutdown and install -updates:
 # echo 'Unattended-Upgrade::InstallOnShutdown "true";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
 # echo 'Unattended-Upgrade::Allowed-Origins:: 
"${distro_id}:${distro_codename}-updates";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too

   * Downgrade snapd:
 # apt install snapd=2.32.5+18.04
   
   * # reboot

   * With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
  
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
  `-{unattended-upgr}

   * With fixed u-u observe snapd update taking place and system
  rebooting after a few seconds with all updates installed

   * Since this fix is partially reverting the fix for LP: #1654600
  please test LP: #1654600 as well to avoid regressions.

  [Regression Potential]

   * As part of the fix manual changes were made to postinst to properly 
transition from coupling u-u.service with multi-user.target to coupling it with 
shutdown.target again which can make u-u started during normal boot when there 
is a bug in the implementation.
  on-testing the SRU.
   * Due to relationship changes between u-u.service, other services and 
targets u-u may fail to run on shutdown in case of an unexpected regression.

  [Original Bug Text]

  When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
  package installation on various packages hangs until the systemd
  ShutdownTimeout (30min) is expired and systemd kills all processes and
  powers off/reboots the system.

  This leaves packages in an unconfigured, broken state. At least
  sometimes this cannot be fixed with a "dpkg --configure -a", but
  instead requires the user to manually reinstall the package that
  caused the hang.

  This appears to be a deadlock, because the hanging commands are always
  "systemctl stop ..." or "systemctl restart ...", etc.. If I understand
  this correctly, those systemctl commands block because systemd tries
  to shutdown the system and tries to satisfy all dependencies for the
  shutdown targets before those systemctl commands could get executed,
  which creates a deadlock.

  Steps to reproduce:

  - Install 18.04
  - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades
  - disable bionic-updates in /etc/apt/sources.list (more on that later)
  - execute "unattended-upgrade --download-only"
  - reboot the system

  -> The upgrade on shutdown 

[Touch-packages] [Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state

[Launchpad Bug Tracker]

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

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

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

Title:
  unattended-upgrades hangs on shutdown, leaves system in a broken state

Status in apt package in Ubuntu:
  Invalid
Status in init-system-helpers package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in init-system-helpers source package in Xenial:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  Confirmed
Status in init-system-helpers source package in Bionic:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in unattended-upgrades source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * Unattended-upgrades hangs and gets killed when installing upgrades
  that stat/stop services on shutdown, leaving the system in a broken
  state

  [Test Case]

   * Install an updated bionic system:
 $ lxc launch ubuntu:18.04 uu-shutdown-test
 # apt update
 ...

   * When testing the fixed version, install upgrade u-u at this point checking 
that u-u.service is set up before and is wanted by shutdown.target:
  # systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket" 
[color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
 Color legend: black = Requires
   dark blue = Requisite
   dark grey = Wants
   red   = Conflicts
   green = After

   * Configure u-u to run on shutdown and install -updates:
 # echo 'Unattended-Upgrade::InstallOnShutdown "true";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
 # echo 'Unattended-Upgrade::Allowed-Origins:: 
"${distro_id}:${distro_codename}-updates";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too

   * Downgrade snapd:
 # apt install snapd=2.32.5+18.04
   
   * # reboot

   * With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
  
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
  `-{unattended-upgr}

   * With fixed u-u observe snapd update taking place and system
  rebooting after a few seconds with all updates installed

   * Since this fix is partially reverting the fix for LP: #1654600
  please test LP: #1654600 as well to avoid regressions.

  [Regression Potential]

   * As part of the fix manual changes were made to postinst to properly 
transition from coupling u-u.service with multi-user.target to coupling it with 
shutdown.target again which can make u-u started during normal boot when there 
is a bug in the implementation.
  on-testing the SRU.
   * Due to relationship changes between u-u.service, other services and 
targets u-u may fail to run on shutdown in case of an unexpected regression.

  [Original Bug Text]

  When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
  package installation on various packages hangs until the systemd
  ShutdownTimeout (30min) is expired and systemd kills all processes and
  powers off/reboots the system.

  This leaves packages in an unconfigured, broken state. At least
  sometimes this cannot be fixed with a "dpkg --configure -a", but
  instead requires the user to manually reinstall the package that
  caused the hang.

  This appears to be a deadlock, because the hanging commands are always
  "systemctl stop ..." or "systemctl restart ...", etc.. If I understand
  this correctly, those systemctl commands block because systemd tries
  to shutdown the system and tries to satisfy all dependencies for the
  shutdown targets before those systemctl commands could get executed,
  which creates a deadlock.

  Steps to reproduce:

  - Install 18.04
  - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades
  - disable bionic-updates in /etc/apt/sources.list (more on that later)
  - execute "unattended-upgrade --download-only"
  - reboot the system

  -> The upgrade on 

[Touch-packages] [Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state

[Launchpad Bug Tracker]

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

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

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

Title:
  unattended-upgrades hangs on shutdown, leaves system in a broken state

Status in apt package in Ubuntu:
  Invalid
Status in init-system-helpers package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in init-system-helpers source package in Xenial:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  Confirmed
Status in init-system-helpers source package in Bionic:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in unattended-upgrades source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * Unattended-upgrades hangs and gets killed when installing upgrades
  that stat/stop services on shutdown, leaving the system in a broken
  state

  [Test Case]

   * Install an updated bionic system:
 $ lxc launch ubuntu:18.04 uu-shutdown-test
 # apt update
 ...

   * When testing the fixed version, install upgrade u-u at this point checking 
that u-u.service is set up before and is wanted by shutdown.target:
  # systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket" 
[color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
 Color legend: black = Requires
   dark blue = Requisite
   dark grey = Wants
   red   = Conflicts
   green = After

   * Configure u-u to run on shutdown and install -updates:
 # echo 'Unattended-Upgrade::InstallOnShutdown "true";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
 # echo 'Unattended-Upgrade::Allowed-Origins:: 
"${distro_id}:${distro_codename}-updates";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too

   * Downgrade snapd:
 # apt install snapd=2.32.5+18.04
   
   * # reboot

   * With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
  
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
  `-{unattended-upgr}

   * With fixed u-u observe snapd update taking place and system
  rebooting after a few seconds with all updates installed

   * Since this fix is partially reverting the fix for LP: #1654600
  please test LP: #1654600 as well to avoid regressions.

  [Regression Potential]

   * As part of the fix manual changes were made to postinst to properly 
transition from coupling u-u.service with multi-user.target to coupling it with 
shutdown.target again which can make u-u started during normal boot when there 
is a bug in the implementation.
  on-testing the SRU.
   * Due to relationship changes between u-u.service, other services and 
targets u-u may fail to run on shutdown in case of an unexpected regression.

  [Original Bug Text]

  When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
  package installation on various packages hangs until the systemd
  ShutdownTimeout (30min) is expired and systemd kills all processes and
  powers off/reboots the system.

  This leaves packages in an unconfigured, broken state. At least
  sometimes this cannot be fixed with a "dpkg --configure -a", but
  instead requires the user to manually reinstall the package that
  caused the hang.

  This appears to be a deadlock, because the hanging commands are always
  "systemctl stop ..." or "systemctl restart ...", etc.. If I understand
  this correctly, those systemctl commands block because systemd tries
  to shutdown the system and tries to satisfy all dependencies for the
  shutdown targets before those systemctl commands could get executed,
  which creates a deadlock.

  Steps to reproduce:

  - Install 18.04
  - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades
  - disable bionic-updates in /etc/apt/sources.list (more on that later)
  - execute "unattended-upgrade --download-only"
  - reboot the system

  -> The upgrade on shutdown hangs 

[Touch-packages] [Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state

[Launchpad Bug Tracker]

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

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

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

Title:
  unattended-upgrades hangs on shutdown, leaves system in a broken state

Status in apt package in Ubuntu:
  Invalid
Status in init-system-helpers package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in init-system-helpers source package in Xenial:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  Confirmed
Status in init-system-helpers source package in Bionic:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in unattended-upgrades source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * Unattended-upgrades hangs and gets killed when installing upgrades
  that stat/stop services on shutdown, leaving the system in a broken
  state

  [Test Case]

   * Install an updated bionic system:
 $ lxc launch ubuntu:18.04 uu-shutdown-test
 # apt update
 ...

   * When testing the fixed version, install upgrade u-u at this point checking 
that u-u.service is set up before and is wanted by shutdown.target:
  # systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket" 
[color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
 Color legend: black = Requires
   dark blue = Requisite
   dark grey = Wants
   red   = Conflicts
   green = After

   * Configure u-u to run on shutdown and install -updates:
 # echo 'Unattended-Upgrade::InstallOnShutdown "true";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
 # echo 'Unattended-Upgrade::Allowed-Origins:: 
"${distro_id}:${distro_codename}-updates";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too

   * Downgrade snapd:
 # apt install snapd=2.32.5+18.04
   
   * # reboot

   * With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
  
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
  `-{unattended-upgr}

   * With fixed u-u observe snapd update taking place and system
  rebooting after a few seconds with all updates installed

   * Since this fix is partially reverting the fix for LP: #1654600
  please test LP: #1654600 as well to avoid regressions.

  [Regression Potential]

   * As part of the fix manual changes were made to postinst to properly 
transition from coupling u-u.service with multi-user.target to coupling it with 
shutdown.target again which can make u-u started during normal boot when there 
is a bug in the implementation.
  on-testing the SRU.
   * Due to relationship changes between u-u.service, other services and 
targets u-u may fail to run on shutdown in case of an unexpected regression.

  [Original Bug Text]

  When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
  package installation on various packages hangs until the systemd
  ShutdownTimeout (30min) is expired and systemd kills all processes and
  powers off/reboots the system.

  This leaves packages in an unconfigured, broken state. At least
  sometimes this cannot be fixed with a "dpkg --configure -a", but
  instead requires the user to manually reinstall the package that
  caused the hang.

  This appears to be a deadlock, because the hanging commands are always
  "systemctl stop ..." or "systemctl restart ...", etc.. If I understand
  this correctly, those systemctl commands block because systemd tries
  to shutdown the system and tries to satisfy all dependencies for the
  shutdown targets before those systemctl commands could get executed,
  which creates a deadlock.

  Steps to reproduce:

  - Install 18.04
  - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades
  - disable bionic-updates in /etc/apt/sources.list (more on that later)
  - execute "unattended-upgrade --download-only"
  - reboot the system

  -> The upgrade on shutdown 

[Touch-packages] [Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state

[Launchpad Bug Tracker]

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

** Changed in: init-system-helpers (Ubuntu Bionic)
   Status: New => Confirmed

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

Title:
  unattended-upgrades hangs on shutdown, leaves system in a broken state

Status in apt package in Ubuntu:
  Invalid
Status in init-system-helpers package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in init-system-helpers source package in Xenial:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  Confirmed
Status in init-system-helpers source package in Bionic:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in unattended-upgrades source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * Unattended-upgrades hangs and gets killed when installing upgrades
  that stat/stop services on shutdown, leaving the system in a broken
  state

  [Test Case]

   * Install an updated bionic system:
 $ lxc launch ubuntu:18.04 uu-shutdown-test
 # apt update
 ...

   * When testing the fixed version, install upgrade u-u at this point checking 
that u-u.service is set up before and is wanted by shutdown.target:
  # systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket" 
[color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
 Color legend: black = Requires
   dark blue = Requisite
   dark grey = Wants
   red   = Conflicts
   green = After

   * Configure u-u to run on shutdown and install -updates:
 # echo 'Unattended-Upgrade::InstallOnShutdown "true";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
 # echo 'Unattended-Upgrade::Allowed-Origins:: 
"${distro_id}:${distro_codename}-updates";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too

   * Downgrade snapd:
 # apt install snapd=2.32.5+18.04
   
   * # reboot

   * With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
  
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
  `-{unattended-upgr}

   * With fixed u-u observe snapd update taking place and system
  rebooting after a few seconds with all updates installed

   * Since this fix is partially reverting the fix for LP: #1654600
  please test LP: #1654600 as well to avoid regressions.

  [Regression Potential]

   * As part of the fix manual changes were made to postinst to properly 
transition from coupling u-u.service with multi-user.target to coupling it with 
shutdown.target again which can make u-u started during normal boot when there 
is a bug in the implementation.
  on-testing the SRU.
   * Due to relationship changes between u-u.service, other services and 
targets u-u may fail to run on shutdown in case of an unexpected regression.

  [Original Bug Text]

  When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
  package installation on various packages hangs until the systemd
  ShutdownTimeout (30min) is expired and systemd kills all processes and
  powers off/reboots the system.

  This leaves packages in an unconfigured, broken state. At least
  sometimes this cannot be fixed with a "dpkg --configure -a", but
  instead requires the user to manually reinstall the package that
  caused the hang.

  This appears to be a deadlock, because the hanging commands are always
  "systemctl stop ..." or "systemctl restart ...", etc.. If I understand
  this correctly, those systemctl commands block because systemd tries
  to shutdown the system and tries to satisfy all dependencies for the
  shutdown targets before those systemctl commands could get executed,
  which creates a deadlock.

  Steps to reproduce:

  - Install 18.04
  - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades
  - disable bionic-updates in /etc/apt/sources.list (more on that later)
  - execute "unattended-upgrade --download-only"
  - reboot the system

  -> The 

[Touch-packages] [Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state

[Launchpad Bug Tracker]

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

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

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

Title:
  unattended-upgrades hangs on shutdown, leaves system in a broken state

Status in apt package in Ubuntu:
  Invalid
Status in init-system-helpers package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in init-system-helpers source package in Xenial:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  Confirmed
Status in init-system-helpers source package in Bionic:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in unattended-upgrades source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * Unattended-upgrades hangs and gets killed when installing upgrades
  that stat/stop services on shutdown, leaving the system in a broken
  state

  [Test Case]

   * Install an updated bionic system:
 $ lxc launch ubuntu:18.04 uu-shutdown-test
 # apt update
 ...

   * When testing the fixed version, install upgrade u-u at this point checking 
that u-u.service is set up before and is wanted by shutdown.target:
  # systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket" 
[color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
 Color legend: black = Requires
   dark blue = Requisite
   dark grey = Wants
   red   = Conflicts
   green = After

   * Configure u-u to run on shutdown and install -updates:
 # echo 'Unattended-Upgrade::InstallOnShutdown "true";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
 # echo 'Unattended-Upgrade::Allowed-Origins:: 
"${distro_id}:${distro_codename}-updates";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too

   * Downgrade snapd:
 # apt install snapd=2.32.5+18.04
   
   * # reboot

   * With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
  
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
  `-{unattended-upgr}

   * With fixed u-u observe snapd update taking place and system
  rebooting after a few seconds with all updates installed

   * Since this fix is partially reverting the fix for LP: #1654600
  please test LP: #1654600 as well to avoid regressions.

  [Regression Potential]

   * As part of the fix manual changes were made to postinst to properly 
transition from coupling u-u.service with multi-user.target to coupling it with 
shutdown.target again which can make u-u started during normal boot when there 
is a bug in the implementation.
  on-testing the SRU.
   * Due to relationship changes between u-u.service, other services and 
targets u-u may fail to run on shutdown in case of an unexpected regression.

  [Original Bug Text]

  When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
  package installation on various packages hangs until the systemd
  ShutdownTimeout (30min) is expired and systemd kills all processes and
  powers off/reboots the system.

  This leaves packages in an unconfigured, broken state. At least
  sometimes this cannot be fixed with a "dpkg --configure -a", but
  instead requires the user to manually reinstall the package that
  caused the hang.

  This appears to be a deadlock, because the hanging commands are always
  "systemctl stop ..." or "systemctl restart ...", etc.. If I understand
  this correctly, those systemctl commands block because systemd tries
  to shutdown the system and tries to satisfy all dependencies for the
  shutdown targets before those systemctl commands could get executed,
  which creates a deadlock.

  Steps to reproduce:

  - Install 18.04
  - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades
  - disable bionic-updates in /etc/apt/sources.list (more on that later)
  - execute "unattended-upgrade --download-only"
  - reboot the system

  -> The upgrade on 

[Touch-packages] [Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state

[Launchpad Bug Tracker]

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

** Changed in: init-system-helpers (Ubuntu Xenial)
   Status: New => Confirmed

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

Title:
  unattended-upgrades hangs on shutdown, leaves system in a broken state

Status in apt package in Ubuntu:
  Invalid
Status in init-system-helpers package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in init-system-helpers source package in Xenial:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in apt source package in Bionic:
  Confirmed
Status in init-system-helpers source package in Bionic:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in unattended-upgrades source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * Unattended-upgrades hangs and gets killed when installing upgrades
  that stat/stop services on shutdown, leaving the system in a broken
  state

  [Test Case]

   * Install an updated bionic system:
 $ lxc launch ubuntu:18.04 uu-shutdown-test
 # apt update
 ...

   * When testing the fixed version, install upgrade u-u at this point checking 
that u-u.service is set up before and is wanted by shutdown.target:
  # systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket" 
[color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
 Color legend: black = Requires
   dark blue = Requisite
   dark grey = Wants
   red   = Conflicts
   green = After

   * Configure u-u to run on shutdown and install -updates:
 # echo 'Unattended-Upgrade::InstallOnShutdown "true";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
 # echo 'Unattended-Upgrade::Allowed-Origins:: 
"${distro_id}:${distro_codename}-updates";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too

   * Downgrade snapd:
 # apt install snapd=2.32.5+18.04
   
   * # reboot

   * With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
  
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
  `-{unattended-upgr}

   * With fixed u-u observe snapd update taking place and system
  rebooting after a few seconds with all updates installed

   * Since this fix is partially reverting the fix for LP: #1654600
  please test LP: #1654600 as well to avoid regressions.

  [Regression Potential]

   * As part of the fix manual changes were made to postinst to properly 
transition from coupling u-u.service with multi-user.target to coupling it with 
shutdown.target again which can make u-u started during normal boot when there 
is a bug in the implementation.
  on-testing the SRU.
   * Due to relationship changes between u-u.service, other services and 
targets u-u may fail to run on shutdown in case of an unexpected regression.

  [Original Bug Text]

  When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
  package installation on various packages hangs until the systemd
  ShutdownTimeout (30min) is expired and systemd kills all processes and
  powers off/reboots the system.

  This leaves packages in an unconfigured, broken state. At least
  sometimes this cannot be fixed with a "dpkg --configure -a", but
  instead requires the user to manually reinstall the package that
  caused the hang.

  This appears to be a deadlock, because the hanging commands are always
  "systemctl stop ..." or "systemctl restart ...", etc.. If I understand
  this correctly, those systemctl commands block because systemd tries
  to shutdown the system and tries to satisfy all dependencies for the
  shutdown targets before those systemctl commands could get executed,
  which creates a deadlock.

  Steps to reproduce:

  - Install 18.04
  - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades
  - disable bionic-updates in /etc/apt/sources.list (more on that later)
  - execute "unattended-upgrade --download-only"
  - reboot the system

  -> The 

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

[Balint Reczey]

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

** This bug has been marked a duplicate of bug 1778219
   unattended-upgrades hangs on shutdown, leaves system in a broken state

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

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

Status in systemd package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  not sure. It just notifies a failure of installation

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21.8
  ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Tue Nov 13 06:26:36 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-06-27 (138 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Dell Inc. OptiPlex 9020
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=d6f84918-e5e2-4e2e-abb9-cc9127cf0382 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29
  SourcePackage: systemd
  Title: package udev 229-4ubuntu21.8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0N4YC8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd09/14/2015:svnDellInc.:pnOptiPlex9020:pvr00:rvnDellInc.:rn0N4YC8:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

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

[Balint Reczey]

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

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

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

Status in systemd package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  not sure. It just notifies a failure of installation

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21.8
  ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Tue Nov 13 06:26:36 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-06-27 (138 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Dell Inc. OptiPlex 9020
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=d6f84918-e5e2-4e2e-abb9-cc9127cf0382 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29
  SourcePackage: systemd
  Title: package udev 229-4ubuntu21.8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0N4YC8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd09/14/2015:svnDellInc.:pnOptiPlex9020:pvr00:rvnDellInc.:rn0N4YC8:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1799206] Re: SRU: update python3.6 to the new minor release 3.6.7

[Matthias Klose]

** Description changed:

  SRU: update python3.6 to the new minor release 3.6.7
  
  See LP: #1792143 for the rationale, going one minor release ahead (and
  planning to do 3.6.8 in January, the last source release from the 3.6
  branch).
  
  [Impact]
  Provide the branch updates for the stable 3.6 branch in the LTS release.
  
  [Regression Potential]
  There is regression potential, but this version is in use in 18.10, which 
didn't show regressions.
  
  [Test Case]
  No regressions in the Python 3.6 test suite, no regressions in the autopkg 
tests
  
  Failing autopkg tests:
-  - http://autopkgtest.ubuntu.com/packages/p/python-asdf/bionic/armhf
-failed before, flaky autopkg tests history, now passes in disco.
-  - snapcraft: amd64 and i386 try to download some rust installation,
-which then fails to build some downloaded code. This doesn't look
-like a reliable test.
-  - python-mechanicalsoup: unrelated, fails in both 2.7 and 3.6.
-Fixed in cosmic, filed LP: #1802835 for a fix anyway.
-  - http://autopkgtest.ubuntu.com/packages/l/lxd/bionic/arm64
-doesn't look like a regression in the autopkg test history.
-pinged the lxd maintainers, but no response yet.
-  - ocrmypdf has a hint: adconrad:unblock ocrmypdf/6.1.2-1ubuntu1
-This does not seem to be a regression, although fixed in disco via
-a new upstream version 6.2.5.
+  - http://autopkgtest.ubuntu.com/packages/p/python-asdf/bionic/armhf
+    failed before, flaky autopkg tests history, now passes in disco.
+  - snapcraft: amd64 and i386 try to download some rust installation,
+    which then fails to build some downloaded code. This doesn't look
+    like a reliable test.
+  - python-mechanicalsoup: unrelated, fails in both 2.7 and 3.6.
+    Fixed in cosmic, filed LP: #1802835 for a fix anyway.
+  - http://autopkgtest.ubuntu.com/packages/l/lxd/bionic/arm64
+    doesn't look like a regression in the autopkg test history.
+    pinged the lxd maintainers, but no response yet. LP: #1803344
+  - ocrmypdf has a hint: adconrad:unblock ocrmypdf/6.1.2-1ubuntu1
+    This does not seem to be a regression, although fixed in disco via
+    a new upstream version 6.2.5.
+And now fixed by another SRU ...

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

Title:
  SRU: update python3.6 to the new minor release 3.6.7

Status in python3-defaults package in Ubuntu:
  Fix Committed
Status in python3.6 package in Ubuntu:
  Fix Committed
Status in python3-defaults source package in Bionic:
  Fix Committed
Status in python3.6 source package in Bionic:
  Fix Committed
Status in python3-defaults source package in Cosmic:
  Fix Released
Status in python3.6 source package in Cosmic:
  Fix Released

Bug description:
  SRU: update python3.6 to the new minor release 3.6.7

  See LP: #1792143 for the rationale, going one minor release ahead (and
  planning to do 3.6.8 in January, the last source release from the 3.6
  branch).

  [Impact]
  Provide the branch updates for the stable 3.6 branch in the LTS release.

  [Regression Potential]
  There is regression potential, but this version is in use in 18.10, which 
didn't show regressions.

  [Test Case]
  No regressions in the Python 3.6 test suite, no regressions in the autopkg 
tests

  Failing autopkg tests:
   - http://autopkgtest.ubuntu.com/packages/p/python-asdf/bionic/armhf
     failed before, flaky autopkg tests history, now passes in disco.
   - snapcraft: amd64 and i386 try to download some rust installation,
     which then fails to build some downloaded code. This doesn't look
     like a reliable test.
   - python-mechanicalsoup: unrelated, fails in both 2.7 and 3.6.
     Fixed in cosmic, filed LP: #1802835 for a fix anyway.
   - http://autopkgtest.ubuntu.com/packages/l/lxd/bionic/arm64
     doesn't look like a regression in the autopkg test history.
     pinged the lxd maintainers, but no response yet. LP: #1803344
   - ocrmypdf has a hint: adconrad:unblock ocrmypdf/6.1.2-1ubuntu1
     This does not seem to be a regression, although fixed in disco via
     a new upstream version 6.2.5.
 And now fixed by another SRU ...

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

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

[Touch-packages] [Bug 1803353] Re: Display freezes (possible i915 freeze/hang)

[Mikko Rantalainen]

Extra information: sudo kill -9  via ssh connection
did restore the display in working order without restarting the system
so I'm pretty sure this is caused by some kind of hang caused by xorg
process. Plain kill without -9 did not do anything, though.

Perhaps this is caused by some race conditition while xorg is keeping
some locks which cause keyboard not to work (e.g. Alt+Ctrl+F1) and the
display does not update.

After saying that, the system seems to be in some weird state where
pretty much all my old X client processess are still running (e.g.
Chrome, Opera, Thunderbird) even though the original xorg process does
not exists anymore. Thunderbird seems to be eating 100% of a single
core.

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

Title:
  Display freezes (possible i915 freeze/hang)

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg suddenly stops updating the display and CTRL+ALT+F1 does not
  work. The issue happens randomly and does not seem to be related to
  content being rendered. This time the display hang occurred while I
  was typing in gnome-terminal.

  I can successfully ssh into the system from another computer and run
  ubuntu-bug xorg while the display is frozen.

  Disconnecting the display port cable and reconnecting does not
  successfully restore the image. However, after disconnecting the cable
  and reconnecting, the monitor never resumed from DPMS suspend so the
  signal emitted did in fact change when I disconnected the cable.

  The problem occurs both with official lowlatency Ubuntu kernel and
  custom kernel built from vanilla kernel sources. I haven't found a way
  to deduce if this is in reality caused by kernel, xorg or the
  hardware. However, considering that this happens with many different
  kernel versions, I'd assume this is caused by xorg, instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  Uname: Linux 4.18.0-memalloc-watchdog+ x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,mousepoll,move,resize,imgpng,wall,animation,grid,fade,place,vpswitch,gnomecompat,session,workarounds,expo,scale,ezoom]
  Date: Wed Nov 14 15:23:50 2018
  DistUpgraded: 2016-06-10 11:06:21,514 WARNING no activity on terminal for 300 
seconds (Applying changes)
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
  InstallationDate: Installed on 2015-02-23 (1360 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-memalloc-watchdog+ 
root=UUID=254cacdb-f61b-45a6-9885-37afd2b598ce ro libata.noacpi=1 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-06-10 (887 days ago)
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1101
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  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.:bvr1101:bd02/04/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Sep  6 15:40:48 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   41047 
   vendor DEL
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

To manage 

[Touch-packages] [Bug 1803353] [NEW] Display freezes (possible i915 freeze/hang)

[Mikko Rantalainen]

Public bug reported:

Xorg suddenly stops updating the display and CTRL+ALT+F1 does not work.
The issue happens randomly and does not seem to be related to content
being rendered. This time the display hang occurred while I was typing
in gnome-terminal.

I can successfully ssh into the system from another computer and run
ubuntu-bug xorg while the display is frozen.

Disconnecting the display port cable and reconnecting does not
successfully restore the image. However, after disconnecting the cable
and reconnecting, the monitor never resumed from DPMS suspend so the
signal emitted did in fact change when I disconnected the cable.

The problem occurs both with official lowlatency Ubuntu kernel and
custom kernel built from vanilla kernel sources. I haven't found a way
to deduce if this is in reality caused by kernel, xorg or the hardware.
However, considering that this happens with many different kernel
versions, I'd assume this is caused by xorg, instead.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
Uname: Linux 4.18.0-memalloc-watchdog+ x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,mousepoll,move,resize,imgpng,wall,animation,grid,fade,place,vpswitch,gnomecompat,session,workarounds,expo,scale,ezoom]
Date: Wed Nov 14 15:23:50 2018
DistUpgraded: 2016-06-10 11:06:21,514 WARNING no activity on terminal for 300 
seconds (Applying changes)
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca]
InstallationDate: Installed on 2015-02-23 (1360 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-memalloc-watchdog+ 
root=UUID=254cacdb-f61b-45a6-9885-37afd2b598ce ro libata.noacpi=1 quiet splash 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-06-10 (887 days ago)
dmi.bios.date: 02/04/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1101
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H77-M PRO
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.:bvr1101:bd02/04/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Sep  6 15:40:48 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   41047 
 vendor DEL
xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  Display freezes (possible i915 freeze/hang)

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg suddenly stops updating the display and CTRL+ALT+F1 does not
  work. The issue happens randomly and does not seem to be related to
  content being rendered. This time the display hang occurred while I
  was typing in gnome-terminal.

  I can successfully ssh into the system from another computer and run
  ubuntu-bug xorg while the display is frozen.

  Disconnecting the display port cable and reconnecting does not
  successfully restore the image. However, after disconnecting the cable
  and reconnecting, the monitor never resumed from DPMS suspend so the
  signal emitted did in fact change when I disconnected the cable.

  The problem occurs both with official lowlatency Ubuntu kernel and
  custom 

[Touch-packages] [Bug 1010000] Re: gedit hangs when opening files with very long lines

[Sebastien Bacher]

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: Confirmed => Triaged

** This bug has been marked a duplicate of bug 505765
   gedit problem with long lines

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

Title:
  gedit hangs when opening files with very long lines

Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Opening the attached file using gedit 3.4.1 causes gedit to hang. The
  file opens correclty using medit and LibreOffice Calc.

  This file comes from a data logger that uses fixed length files,
  padding the unused area at the end of the file with null characters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/101/+subscriptions

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

[Touch-packages] [Bug 1441240] Re: vim locks up when freeing lots of objects

[Paul White]

>From Ubuntu changelog showing bug fixed:

vim (2:7.4.712-1) unstable; urgency=medium

  * Merge upstream tag v7-4-712
+ 7.4.586: Remove a cyclic dependency when generating documentation, which
  results in unreproducible builds.  (Closes: #775562)
+ 7.4.609: Use a stack of dicts and lists to be marked for garbage
  collection, thus making it iterative instead of recursive.  Fixes crash
  with some plugins written in other languages (e.g., lua).  (Closes:
  #778821)
+ runtime/syntax/registry.vim: Correct highlighting of comments.  (Closes:
  #687199)
+ runtime/syntax/strace.vim: Highlight 2-digit escape sequences the same
  as 1 or 3-digit escape sequences.  (Closes: #775113)
  * Remove backported patches upstream/v7-4-576.patch and
upstream/netrwSavePosn.patch.
  * Add a Build-Conflict for autoconf2.13 to avoid a FTBFS if it's installed.
(Closes: #781031)

 -- James McCoy   Sat, 25 Apr 2015 09:00:09 -0400


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

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

Title:
  vim locks up when freeing lots of objects

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

Bug description:
  When using a heavy plugin (e.g. unite, ctrlP, many others), vim's GC
  is stressed. vim's GC has a performance bug which causes it to be
  O(n^2), which results in vim freezing up when it runs. This is fixed
  in a newer version of vim. This patch should be considered for
  backporting.

  The patch is here:
  https://groups.google.com/forum/#!topic/vim_dev/pXjj7rww5RY

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: vim-gtk 2:7.4.273-2ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  Date: Tue Apr  7 12:00:38 2015
  InstallationDate: Installed on 2014-03-12 (390 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  SourcePackage: vim
  UpgradeStatus: Upgraded to utopic on 2015-01-09 (87 days ago)

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

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

[Touch-packages] [Bug 1050787] Re: vim: unable to create updated files list

[Paul White]

ricxzone,

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Do you still see a problem related to the one that you reported?

Please let us know if you do otherwise this bug report will expire in
approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


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

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

Title:
  vim: unable to create updated files list

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Unpacking replacement vim ...
  dpkg: error processing 
/var/cache/apt/archives/vim_2%3a7.2.330-1ubuntu3_i386.deb (--unpack):
   unable to create updated files list file for package vim: No such file or 
directory
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   /var/cache/apt/archives/libavutil49_4%3a0.5.9-0ubuntu0.10.04.1_i386.deb
   /var/cache/apt/archives/libgsm1_1.0.13-3_i386.deb
   
/var/cache/apt/archives/libschroedinger-1.0-0_1.0.9.is.1.0.8-0ubuntu1_i386.deb
   /var/cache/apt/archives/libavcodec52_4%3a0.5.9-0ubuntu0.10.04.1_i386.deb
   /var/cache/apt/archives/libavformat52_4%3a0.5.9-0ubuntu0.10.04.1_i386.deb
   /var/cache/apt/archives/libpostproc51_4%3a0.5.9-0ubuntu0.10.04.1_i386.deb
   /var/cache/apt/archives/libswscale0_4%3a0.5.9-0ubuntu0.10.04.1_i386.deb
   /var/cache/apt/archives/gstreamer0.10-ffmpeg_0.10.10-1_i386.deb
   /var/cache/apt/archives/gstreamer0.10-fluendo-mp3_0.10.12.debian-2_i386.deb
   /var/cache/apt/archives/liba52-0.7.4_0.7.4-13ubuntu1_i386.deb
   /var/cache/apt/archives/libdvdread4_4.1.3-8ubuntu1_i386.deb
   /var/cache/apt/archives/libid3tag0_0.15.1b-10build2_i386.deb
   /var/cache/apt/archives/libmad0_0.15.1b-4ubuntu1_i386.deb
   /var/cache/apt/archives/libmpeg2-4_0.4.1-3_i386.deb
   /var/cache/apt/archives/lE: Sub-process /usr/bin/dpkg returned an error code 
(1)

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

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

[Touch-packages] [Bug 1803207] Re: Missing alias for locale eo.UTF-8

[Daniel Pfeiffer]

The other solution would be to add eo.UTF-8 (& eo.ISO8859-3) to
locale.dir & compose.dir.  This is probably the most correct way,
because Esperanto is one of those languages which doesn't belong to any
country, nor has national variants.

I found that of the 3 files only locale.dir has eo_EO.UTF-8 (&
eo_EO.ISO8859-3) commented out with this correct explanation:  The EO
territory doesn't exist in ISO 3166.

The other variant X11 introduces, eo_XX is also not correct.  According
to Wikipedia that would be: unknown states, other entities or
organizations.  We're not from an unknown country, but rather world wide
(WW?) and anybody can easily learn to speak Esperanto without being
affiliated with an entity or organization.

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

Title:
  Missing alias for locale eo.UTF-8

Status in libx11 package in Ubuntu:
  New

Bug description:
  When downloading and running the latest kitty terminal with
  LANG=eo.UTF-8, I get an error that it can't find a composition for
  this locale.  This is fixed by adding this line

  eo.UTF-8:   eo_EO.UTF-8

  to /usr/share/X11/locale/locale.alias

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libx11-data 2:1.6.7-1 [modified: usr/share/X11/locale/locale.alias]
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 13 15:07:11 2018
  Dependencies:
   
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-11-07 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 007: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=dffdd333-04ee-4748-ab06-f138a6bf751a ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  SourcePackage: libx11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Touch-packages] [Bug 1803176] Re: Search in Nautilus does not work correctly when called from other apps

[Sebastien Bacher]

That's rather an issue with the GTK filechooser than with nautilus

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

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

Title:
  Search in Nautilus does not work correctly when called from other apps

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  When Nautilus is called from another app, e.g., Thunderbird > Attach
  File to email (or Gedit > Save file) the search (via the magnifying
  glass icon in the top right) only allows for 1 character to be
  entered, and then jumps to the bottom right and subsequent characters
  appear there.

  This behavior, of course, messes up the expected search results as the
  search is split into two fields/areas of the panel.

  In contrast, when opening up a Nautilus browser panel directly, any
  search query entered from the magnifying glass icon stays in the text
  entry area as expected, and the search results work well.

  The expectation is that when another app calls Nautilus, the search
  function works as if it does when working directly out of Nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nautilus 1:3.26.4-0ubuntu7
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 13 13:05:42 2018
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'1165x787+417+87'"
   b'org.gnome.nautilus.compression' b'default-compression-format' b"'7z'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency']"
  InstallationDate: Installed on 2018-10-27 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: dropbox 2015.10.28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1803176/+subscriptions

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

[Touch-packages] [Bug 366040] Re: gvim broken: undefined symbol: initstrop

[Paul White]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug a long time ago
and there have been many changes in Ubuntu and vim since that time.

We'd like to close this bug report due to its age and long period of
inactivity so please let us know if you still see a problem which is
related in any way to the one that you reported.

If we do not hear from you this bug report will expire in approximately
60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

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

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

Title:
  gvim broken: undefined symbol: initstrop

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: vim-gtk

  1) Ubuntu 9.04
  2) vim-gtk 2:7.2.079-1ubuntu5 (I _suppose_ it is this package)
  3) Launched gvim, expected it to work.
  4) Instead, it gave this error and died:
  gvim: symbol lookup error: gvim: undefined symbol: initstrop

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

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

[Touch-packages] [Bug 946734] Re: vim-gnome: difference between guifont 10 and guifont 11 is huge

[Paul White]

Thank you for reporting this bug to Ubuntu.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

Paul White
[Ubuntu Bug Squad]


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

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

Title:
  vim-gnome: difference between guifont 10 and guifont 11 is huge

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  I'm using vim-gnome with Monospace\ 11. Compared to vim-gnome on
  Ubuntu 11.10 the font is huge. If I set guifont=Monospace\ 10 it's too
  small. Looks like the step between 10 and 11 has increased. I tried it
  with different fixed widtht fonts and they all suffer from this
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: vim-gnome 2:7.3.429-2ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  ApportVersion: 1.94-0ubuntu1
  Architecture: amd64
  Date: Mon Mar  5 00:54:16 2012
  EcryptfsInUse: Yes
  InstallationMedia:
   
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1802644] Re: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[ Christian Ehrhardt ]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it
helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

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

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

Title:
  package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 127

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Automatically created.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sat Nov 10 14:22:59 2018
  DuplicateSignature:
   package:openssh-server:1:7.6p1-4ubuntu0.1
   Setting up openssh-server (1:7.6p1-4ubuntu0.1) ...
   awk: symbol lookup error: /usr/local/lib/libreadline.so.7: undefined symbol: 
UP
   dpkg: error processing package openssh-server (--configure):
installed openssh-server package post-installation script subprocess 
returned error exit status 127
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 127
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: openssh
  Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1010000] [NEW] gedit hangs when opening files padded with null characters

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Opening the attached file using gedit 3.4.1 causes gedit to hang. The
file opens correclty using medit and LibreOffice Calc.

This file comes from a data logger that uses fixed length files, padding
the unused area at the end of the file with null characters.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Low
 Status: Confirmed


** Tags: disco
-- 
gedit hangs when opening files padded with null characters
https://bugs.launchpad.net/bugs/101
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 1010000] Re: gedit hangs when opening files padded with null characters

[Paul White]

Upstream advise duplicate of https://gitlab.gnome.org/GNOME/gtk/issues/229
Not an issue with null characters but long lines
See second entry in https://wiki.gnome.org/Apps/Gedit/FAQ
Reassigning to gtk3

** Package changed: gedit (Ubuntu) => gtk+3.0 (Ubuntu)

** Summary changed:

- gedit hangs when opening files padded with null characters
+ gedit hangs when opening files with very long lines

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

Title:
  gedit hangs when opening files with very long lines

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Opening the attached file using gedit 3.4.1 causes gedit to hang. The
  file opens correclty using medit and LibreOffice Calc.

  This file comes from a data logger that uses fixed length files,
  padding the unused area at the end of the file with null characters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/101/+subscriptions

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

[Touch-packages] [Bug 1801832] Re: Input method toggled when using the numeric pad

[Sebastien Bacher]

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

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

Title:
  Input method toggled when using the numeric pad

Status in ibus package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 LTS

  During the Chinese character input mode, when I enter numbers using
  the numeric pad, the input method will be switched to English
  automatically, which is very annoying. Any suggestions?

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

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

[Touch-packages] [Bug 1795913] Re: Systemd Resolver works unreliable to local DNS Names

[Sebastien Bacher]

Closing that bug since the submitter debugged it and found out it was
not a systemd issue. Those who have other DNS problems please register a
new bug

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

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

Title:
  Systemd Resolver works unreliable to local DNS Names

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  systemd-resolved fails to resolve reliably local DNS names under
  home.example.com. The first call succeeds but all following calls
  fails to resolve the address correctly:

  steve@steve-ThinkPad-T560:~$ systemd-resolve --flush-caches
  steve@steve-ThinkPad-T560:~$ systemd-resolve akolus.home.example.com
  akolus.home.example.com: 192.168.1.5

  -- Information acquired via protocol DNS in 2.7ms.
  -- Data is authenticated: no
  steve@steve-ThinkPad-T560:~$ systemd-resolve akolus.home.example.com
  akolus.home.example.com: resolve call failed: 'akolus.home.example.com' not 
found

  A call to systemd-resolve --flush-caches get the next resolvement
  working again.

  The syslog show following entries

  Oct  3 16:44:41 steve-ThinkPad-T560 systemd-resolved[1092]: Flushed all 
caches.
  Oct  3 16:44:41 steve-ThinkPad-T560 systemd-resolved[1092]: Server returned 
error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.

  A dig for the adresses  to all DHCP provided DNS Server works:

  steve@steve-ThinkPad-T560:~$ dig akolus.home.example.com @192.168.1.1

  ; <<>> DiG 9.11.3-1ubuntu1.2-Ubuntu <<>> akolus.home.example.com @192.168.1.1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61886
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;akolus.home.example.com. IN  A

  ;; ANSWER SECTION:
  akolus.home.example.com. 0IN  A   192.168.1.5

  ;; Query time: 0 msec
  ;; SERVER: 192.168.1.1#53(192.168.1.1)
  ;; WHEN: Wed Oct 03 16:46:30 CEST 2018
  ;; MSG SIZE  rcvd: 70

  steve@steve-ThinkPad-T560:~$ dig akolus.home.example.com
  @2a04:4540:4707:a800::1

  ; <<>> DiG 9.11.3-1ubuntu1.2-Ubuntu <<>> akolus.home.example.com 
@2a04:4540:4707:a800::1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24202
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;akolus.home.example.com. IN  A

  ;; ANSWER SECTION:
  akolus.home.example.com. 0IN  A   192.168.1.5

  ;; Query time: 0 msec
  ;; SERVER: 2a04:4540:4707:a800::1#53(2a04:4540:4707:a800::1)
  ;; WHEN: Wed Oct 03 16:46:33 CEST 2018
  ;; MSG SIZE  rcvd: 70

  steve@steve-ThinkPad-T560:~$ dig akolus.home.example.com
  @fd9c:9819:4c58::1

  ; <<>> DiG 9.11.3-1ubuntu1.2-Ubuntu <<>> akolus.home.example.com 
@fd9c:9819:4c58::1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9783
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;akolus.home.example.com. IN  A

  ;; ANSWER SECTION:
  akolus.home.example.com. 0IN  A   192.168.1.5

  ;; Query time: 0 msec
  ;; SERVER: fd9c:9819:4c58::1#53(fd9c:9819:4c58::1)
  ;; WHEN: Wed Oct 03 16:46:38 CEST 2018
  ;; MSG SIZE  rcvd: 70

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed Oct  3 15:56:44 2018
  InstallationDate: Installed on 2018-03-05 (212 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  MachineType: LENOVO 20FH002RGE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET26W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FH002RGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:svnLENOVO:pn20FH002RGE:pvrThinkPadT560:rvnLENOVO:rn20FH002RGE:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:

[Touch-packages] [Bug 1803316] [NEW] VPN connection is stopped

[Marek Tenus]

Public bug reported:

>From a few days I cannot connect via VPN, It worked from a few months

*sudo apt policy network-manager*

network-manager:
  Installed: 1.2.6-0ubuntu0.16.04.3
  Candidate: 1.2.6-0ubuntu0.16.04.3
  Versions:
 *** 1.2.6-0ubuntu0.16.04.3 500
500 http://ftp.agh.edu.pl/ubuntu xenial-updates/main amd64 Packages
500 http://ftp.agh.edu.pl/ubuntu xenial-security/main amd64 Packages
100 /var/lib/dpkg/status
 1.1.93-0ubuntu4 500
500 http://ftp.agh.edu.pl/ubuntu xenial/main amd64 Packages


*/var/sys/log*


Nov 14 10:46:07 hs NetworkManager[1081]:   [1542188767.8520] audit: 
op="connection-activate" uuid="3872fc1d-94ce-465e-8d52-7bbeb3eb72fe" name="HS 
VPN" pid=13561 uid=1000 result="success"
Nov 14 10:46:07 hs NetworkManager[1081]:   [1542188767.8706] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: 
Started the VPN service, PID 2396
Nov 14 10:46:07 hs NetworkManager[1081]:   [1542188767.8815] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: Saw 
the service appear; activating connection
Nov 14 10:46:07 hs NetworkManager[1081]:   [1542188767.9989] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
connection: (ConnectInteractive) reply received
Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: pppd started with pid 2405
Nov 14 10:46:08 hs NetworkManager[1081]:   [1542188768.0148] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: state changed: starting (3)
Nov 14 10:46:08 hs pppd[2405]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Nov 14 10:46:08 hs NetworkManager[1081]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(plugin_init): initializing
Nov 14 10:46:08 hs pppd[2405]: pppd 2.4.7 started by root, uid 0
Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(nm_phasechange): status 3 / phase 'serial connection'
Nov 14 10:46:08 hs NetworkManager[1081]: nm_device_get_device_type: assertion 
'NM_IS_DEVICE (self)' failed
Nov 14 10:46:08 hs NetworkManager[1081]:   [1542188768.0226] manager: 
(ppp0): new Generic device (/org/freedesktop/NetworkManager/Devices/47)
Nov 14 10:46:08 hs pptp[2411]: nm-pptp-service-2396 log[main:pptp.c:350]: The 
synchronous pptp option is NOT activated
Nov 14 10:46:08 hs pppd[2405]: Using interface ppp0
Nov 14 10:46:08 hs NetworkManager[1081]: Using interface ppp0
Nov 14 10:46:08 hs pppd[2405]: Connect: ppp0 <--> /dev/pts/22
Nov 14 10:46:08 hs NetworkManager[1081]: Connect: ppp0 <--> /dev/pts/22
Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(nm_phasechange): status 5 / phase 'establish'
Nov 14 10:46:08 hs NetworkManager[1081]:   [1542188768.0391] devices 
added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Nov 14 10:46:08 hs NetworkManager[1081]:   [1542188768.0392] device added 
(path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration 
found.
Nov 14 10:46:39 hs pppd[2405]: LCP: timeout sending Config-Requests
Nov 14 10:46:39 hs NetworkManager[1081]: LCP: timeout sending Config-Requests
Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(nm_phasechange): status 11 / phase 'disconnect'
Nov 14 10:46:39 hs NetworkManager[1081]: Connection terminated.
Nov 14 10:46:39 hs pppd[2405]: Connection terminated.
Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: Terminated ppp daemon with 
PID 2405.
Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0566] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: failed: connect-failed (1)
Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0577] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: state changed: stopping (5)
Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0579] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: state changed: stopped (6)
Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0680] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: state change reason: unknown (0)
Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0802] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
service disappeared
Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(nm_phasechange): status 1 / phase 'dead'
Nov 14 10:46:39 hs NetworkManager[1081]: Terminating on signal 15
Nov 14 10:46:39 hs NetworkManager[1081]: Modem hangup
Nov 14 10:46:39 hs pppd[2405]: Terminating on signal 15
Nov 14 10:46:39 hs pppd[2405]: Modem hangup
Nov 14 10:46:39 hs pptp[2291]: nm-pptp-service-2215 
log[pptp_read_some:pptp_ctrl.c:593]: read error: Bad file descriptor
Nov 14 10:46:39 hs kernel: [ 5539.540135] pptpcm[2291]: segfault at 
7f069f3a87b8 ip 00406a87 sp 

[Touch-packages] [Bug 1802644] Re: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[ Christian Ehrhardt ]

Hi,
your log is rather short so I can't be sure, but I see this issue:
  Setting up openssh-server (1:7.6p1-4ubuntu0.1) ...
  awk: symbol lookup error: /usr/local/lib/libreadline.so.7: undefined symbol: 
UP

That in turn does not reproduce for me so it has to be some config/setup
on your machine and I wonder what it is.

I checked for similar cases and found a few where people had alternative 
(self-built/tarball install) libreadline*.so files in /lib or /usr/local/
Obviously if those are preferred by the linker and not matching what awk is 
built against it might fail.

Please take a look if you have any alien libreadline shared objects and remove 
them.
Then this should work as it is supposed to work.

I'd expect that awk fails all the time for you.
If it does you might check with:
  ldd /usr/bin/awk
where it resolves it's libreadline from

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

Title:
  package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 127

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Automatically created.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sat Nov 10 14:22:59 2018
  DuplicateSignature:
   package:openssh-server:1:7.6p1-4ubuntu0.1
   Setting up openssh-server (1:7.6p1-4ubuntu0.1) ...
   awk: symbol lookup error: /usr/local/lib/libreadline.so.7: undefined symbol: 
UP
   dpkg: error processing package openssh-server (--configure):
installed openssh-server package post-installation script subprocess 
returned error exit status 127
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 127
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: openssh
  Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1803236] Re: network-manager: switch from dnsmasq (16.04) to systemd-resolve (18.04) breaks DNS

[Sebastien Bacher]

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

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

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

Title:
  network-manager: switch from dnsmasq (16.04) to systemd-resolve
  (18.04) breaks DNS

Status in network-manager package in Ubuntu:
  New

Bug description:
  During the do-release-upgrade from 16.04 to 18.04, if the user chooses
  to preserve the old NetworkManager.conf having "dns=dnsmasq", it does
  not preserve dnsmasq as the local resolver.

  It results in a broken DNS configuration, with /etc/resolv.conf set to
  127.0.0.53 but NetworkManager set to dnsmasq.

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

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

[Touch-packages] [Bug 1567593] Re: package vim-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/pl/man1/xxd.1.gz', which is also in package vim 20160401-1

[Paul White]

Thank you for reporting this bug to Ubuntu.

Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

Paul White
[Ubuntu Bug Squad]

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

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

Title:
  package vim-common (not installed) failed to install/upgrade: trying
  to overwrite '/usr/share/man/pl/man1/xxd.1.gz', which is also in
  package vim 20160401-1

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  I have recently compiled and installed my own version of vim

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: vim-common (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Thu Apr  7 11:12:41 2016
  DpkgHistoryLog:
   Start-Date: 2016-04-07  11:12:38
   Install: vim-common:amd64 (7.4.712-2ubuntu4, automatic), 
linux-headers-4.2.0-35:amd64 (4.2.0-35.40, automatic), 
linux-headers-4.2.0-35-generic:amd64 (4.2.0-35.40, automatic), 
linux-image-extra-4.2.0-35-generic:amd64 (4.2.0-35.40, automatic), 
linux-image-4.2.0-35-generic:amd64 (4.2.0-35.40, automatic), vim-runtime:amd64 
(7.4.712-2ubuntu4, automatic)
   Upgrade: linux-headers-generic:amd64 (4.2.0.34.37, 4.2.0.35.38), vim:amd64 
(20160401-1, 7.4.712-2ubuntu4), linux-libc-dev:amd64 (4.2.0-34.39, 
4.2.0-35.40), linux-image-generic:amd64 (4.2.0.34.37, 4.2.0.35.38), 
linux-generic:amd64 (4.2.0.34.37, 4.2.0.35.38)
  DuplicateSignature: package:vim-common:(not installed):trying to overwrite 
'/usr/share/man/pl/man1/xxd.1.gz', which is also in package vim 20160401-1
  ErrorMessage: trying to overwrite '/usr/share/man/pl/man1/xxd.1.gz', which is 
also in package vim 20160401-1
  InstallationDate: Installed on 2015-02-22 (410 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: vim
  Title: package vim-common (not installed) failed to install/upgrade: trying 
to overwrite '/usr/share/man/pl/man1/xxd.1.gz', which is also in package vim 
20160401-1
  UpgradeStatus: Upgraded to wily on 2016-03-18 (19 days ago)

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

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

[Touch-packages] [Bug 1803176] [NEW] Search in Nautilus does not work correctly when called from other apps

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When Nautilus is called from another app, e.g., Thunderbird > Attach
File to email (or Gedit > Save file) the search (via the magnifying
glass icon in the top right) only allows for 1 character to be entered,
and then jumps to the bottom right and subsequent characters appear
there.

This behavior, of course, messes up the expected search results as the
search is split into two fields/areas of the panel.

In contrast, when opening up a Nautilus browser panel directly, any
search query entered from the magnifying glass icon stays in the text
entry area as expected, and the search results work well.

The expectation is that when another app calls Nautilus, the search
function works as if it does when working directly out of Nautilus.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: nautilus 1:3.26.4-0ubuntu7
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 13 13:05:42 2018
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.window-state' b'geometry' b"'1165x787+417+87'"
 b'org.gnome.nautilus.compression' b'default-compression-format' b"'7z'"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency']"
InstallationDate: Installed on 2018-10-27 (17 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: dropbox 2015.10.28

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic third-party-packages
-- 
Search in Nautilus does not work correctly when called from other apps
https://bugs.launchpad.net/bugs/1803176
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 1536193] Re: package vim-runtime 2:7.4.712-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/share/vim/vim74/optwin.vim', which is also in package vim 20160113-1

[Paul White]

Thank you for reporting this bug to Ubuntu.

Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

Paul White
[Ubuntu Bug Squad]

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

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

Title:
  package vim-runtime 2:7.4.712-2ubuntu4 failed to install/upgrade:
  trying to overwrite '/usr/share/vim/vim74/optwin.vim', which is also
  in package vim 20160113-1

Status in vim package in Ubuntu:
  Incomplete

Bug description:
  Upgrade failed

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: vim-runtime 2:7.4.712-2ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Mon Jan 18 11:39:49 2016
  DuplicateSignature: package:vim-runtime:2:7.4.712-2ubuntu4:trying to 
overwrite '/usr/share/vim/vim74/optwin.vim', which is also in package vim 
20160113-1
  ErrorMessage: trying to overwrite '/usr/share/vim/vim74/optwin.vim', which is 
also in package vim 20160113-1
  InstallationDate: Installed on 2015-11-12 (68 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: vim
  Title: package vim-runtime 2:7.4.712-2ubuntu4 failed to install/upgrade: 
trying to overwrite '/usr/share/vim/vim74/optwin.vim', which is also in package 
vim 20160113-1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1803313] [NEW] package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

[Goffdely]

Public bug reported:

I don't know anything about initralfs and *-tools. But Ubuntu rise a
bug...

Ubuntu 18.04.1 LTS
Release:18.04

apt-cache policy initramfs-tools
initramfs-tools:
  Installé : 0.130ubuntu3.5
  Candidat : 0.130ubuntu3.5
 Table de version :
 *** 0.130ubuntu3.5 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
100 /var/lib/dpkg/status
 0.130ubuntu3 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://fr.archive.ubuntu.com/ubuntu bionic/main i386 Packages

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3.5
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
AptOrdering:
 udev:amd64: Install
 libudev1:amd64: Install
 libudev1:amd64: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Nov 14 09:11:28 2018
Df:
 
Dmesg:
 
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 2
InstallationDate: Installed on 2018-11-11 (2 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I don't know anything about initralfs and *-tools. But Ubuntu rise a
  bug...

  Ubuntu 18.04.1 LTS
  Release:  18.04

  apt-cache policy initramfs-tools
  initramfs-tools:
Installé : 0.130ubuntu3.5
Candidat : 0.130ubuntu3.5
   Table de version :
   *** 0.130ubuntu3.5 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.130ubuntu3 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main i386 Packages

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.5
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   udev:amd64: Install
   libudev1:amd64: Install
   libudev1:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Nov 14 09:11:28 2018
  Df:
   
  Dmesg:
   
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2018-11-11 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1802498] Re: AppArmor - Error Messages log files - Mensagens de Erro arquivos de log

[Rami Hakim]

Hey Edson,

ESET doesn't seem to have Linux on their priority because their Linux
userbase seems to be small and not that big comparing to Windows / Mac,

When ESET v4 was released , AppArmor wasn't available back in the time it 
wasn't developed yet.
I'm not that experienced with AppArmor , but I think if one can properly 
configure AppArmor to work with ESET , it will work as far as I can imagine.

But the problem is from ESET's side , so they have made a program that
doesn't work with SELinux , and not compatible with AppArmor.

I've been on this problem for a while now , and it seems that ESET is so
quiet about any replies, So I wonder if Ubuntu team will take a look at
this problem, I would be very glad if someone fixes it , even if it was
a workaround but atleast a fix.

Thanks.

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

Title:
  AppArmor - Error Messages log files - Mensagens de Erro arquivos de
  log

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hello Canonical team - Ubuntu

  Eset Antivirus has some problems with apparmor.

  In Eset I have observed in the last weeks that the updates are being
  carried out, but the logs that have been installed successfully, where
  it was in bold, no longer appear.

  I also realize that these error messages below are constants and I
  would like to know what it is possible to do to resolve them, as they
  are due to mismatch with apparmor. Can Canonial and Eset work together
  to solve this problem?

  Here is the log of Eset Antivirus for Linux Version 4.90 installed on
  Ubuntu 18.10 Cosmic and log dmesg of Ubuntu.

  Thank you in advance for the attention and collaboration of all

  Edson Santos

  

  Obs: Most of these problems are caused by AppArmor , ESET v4 is not
  compatible with AppArmor/SELinux

  I've tried to test things here and there , ESET still does do it's job
  while AppArmor is enabled (I didn't try with AppArmor disabled) , but
  it encounters lot of errors , and while scanning AppArmor will prevent
  ESET from accessing most files as far as I have noticed.

  I don't know if there is a workaround for AppArmor to allow ESET , but
  I don't want to disable it and I don't want to remove ESET.

  
  Thank you in advance for the attention and collaboration of all

  
  Edson Santos

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

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

[Touch-packages] [Bug 1772094] Re: Surface Pro 4: Keyboard not functional during LUKS password prompt

[Ubuntu Foundations Team Bug Bot]

The attachment "multitouch.patch" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Surface Pro 4: Keyboard not functional during LUKS password prompt

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 18.04 desktop edition on a Microsoft Surface Pro 4,
  using LVM and full disk encryption.  When LUKS prompts for the
  password, however, the type cover keyboard does not work.  I had to
  plug in a USB keyboard to type in the password and boot.

  However, the solution is simple.  Edit the /etc/initramfs-
  tools/modules file, add "hid_multitouch" to a line on its own, then
  run "update-initramfs -u".  Now the typecover keyboard can be used to
  enter the LUKS password on boot.

  The Ubuntu 18.04 desktop installer should be modified to detect if it
  is running on Surface Pro hardware, and add the module, above, as
  needed.

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

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