[Touch-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 18.2.1-1ubuntu1

---
mesa (18.2.1-1ubuntu1) cosmic; urgency=medium

  * Merge from Debian experimental. (LP: #1714178, #1792873)
  * glvnd-fix-a-segfault-in-eglgetprocaddess.diff: Dropped, upstream.

mesa (18.2.1-1) experimental; urgency=medium

  * New upstream release.
  * control: Add libd3dadapter9-mesa to -dev depends.
  * control: Fix libd3dadapter9-mesa-dev section, and drop
shlibs:Depends.

mesa (18.2.0-3) experimental; urgency=medium

  * control, rules: Nine needs llvmpipe, and also makes sense to build it
only on archs that have wine.

mesa (18.2.0-2) experimental; urgency=medium

  * control: Bump build-dep on libxcb-dri3-dev and libxcb-present-dev to
1.13. (Closes: #908827)
  * control: Build-depend on x11proto-dev, modify libegl1-mesa-dev and
libgl1-mesa-dev depends.
  * Migrate to llvm/clang-7.
  * Enable gallium D3D state tracker, thanks Antonio Russo and Andrew
Cook! (Closes: #863972)
  * rules: Enable v3d on arm. Thanks, Fabio Pedretti!
  * rules: Drop enabling texture float, it's enabled by default now.

mesa (18.2.0-1) experimental; urgency=medium

  * New upstream release.

mesa (18.2.0~rc4-1) experimental; urgency=medium

  * New upstream release candidate.
  * control: Add libxrandr-dev and libwayland-egl-backend-dev to build-
depends.

mesa (18.1.8-1) unstable; urgency=medium

  * New upstream release.

mesa (18.1.7-1) unstable; urgency=medium

  * New upstream release.
  * libglx-mesa0: Add Breaks: glx-diversions (<< 0.8.4~) (Closes:
#903929).

mesa (18.1.6-1) unstable; urgency=medium

  * New upstream release.
- Fixes white screen when running Xfwm4 with compositing
  (Closes: #901789).
  * Drop glvnd-fix-gl-dot-pc.patch, fixed upstream (0c927e8da9e)
(Closes: #896447).

 -- Timo Aaltonen   Tue, 25 Sep 2018 23:26:15 +0300

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

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in X.Org X server:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in mesa source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Confirmed

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  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
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare

[Touch-packages] [Bug 1792873] Re: FFE: 18.2.x for cosmic

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 18.2.1-1ubuntu1

---
mesa (18.2.1-1ubuntu1) cosmic; urgency=medium

  * Merge from Debian experimental. (LP: #1714178, #1792873)
  * glvnd-fix-a-segfault-in-eglgetprocaddess.diff: Dropped, upstream.

mesa (18.2.1-1) experimental; urgency=medium

  * New upstream release.
  * control: Add libd3dadapter9-mesa to -dev depends.
  * control: Fix libd3dadapter9-mesa-dev section, and drop
shlibs:Depends.

mesa (18.2.0-3) experimental; urgency=medium

  * control, rules: Nine needs llvmpipe, and also makes sense to build it
only on archs that have wine.

mesa (18.2.0-2) experimental; urgency=medium

  * control: Bump build-dep on libxcb-dri3-dev and libxcb-present-dev to
1.13. (Closes: #908827)
  * control: Build-depend on x11proto-dev, modify libegl1-mesa-dev and
libgl1-mesa-dev depends.
  * Migrate to llvm/clang-7.
  * Enable gallium D3D state tracker, thanks Antonio Russo and Andrew
Cook! (Closes: #863972)
  * rules: Enable v3d on arm. Thanks, Fabio Pedretti!
  * rules: Drop enabling texture float, it's enabled by default now.

mesa (18.2.0-1) experimental; urgency=medium

  * New upstream release.

mesa (18.2.0~rc4-1) experimental; urgency=medium

  * New upstream release candidate.
  * control: Add libxrandr-dev and libwayland-egl-backend-dev to build-
depends.

mesa (18.1.8-1) unstable; urgency=medium

  * New upstream release.

mesa (18.1.7-1) unstable; urgency=medium

  * New upstream release.
  * libglx-mesa0: Add Breaks: glx-diversions (<< 0.8.4~) (Closes:
#903929).

mesa (18.1.6-1) unstable; urgency=medium

  * New upstream release.
- Fixes white screen when running Xfwm4 with compositing
  (Closes: #901789).
  * Drop glvnd-fix-gl-dot-pc.patch, fixed upstream (0c927e8da9e)
(Closes: #896447).

 -- Timo Aaltonen   Tue, 25 Sep 2018 23:26:15 +0300

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

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

Title:
  FFE: 18.2.x for cosmic

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Mesa 18.2.0 was recently released after several delays, but at least
  it doesn't have any known regressions on Intel hw. We tend to get the
  latest major version in the devel series ~2 weeks after FF, but since
  a month has passed now I thought it would be best to file an actual
  FFE request.

  We'd also build it against LLVM 7, which is about to be released.
  Together these provide support for AMD Vega20 (kernel support still
  needed) among other things.

  New features from mesa upstream reldocs:

  OpenGL 4.3 on virgl
  OpenGL 4.4 Compatibility profile on radeonsi
  OpenGL ES 3.2 on radeonsi and virgl
  GL_ARB_ES3_2_compatibility on radeonsi
  GL_ARB_fragment_shader_interlock on i965
  GL_ARB_sample_locations and GL_NV_sample_locations on nvc0 (GM200+)
  GL_ANDROID_extension_pack_es31a on radeonsi.
  GL_KHR_texture_compression_astc_ldr on radeonsi
  GL_NV_conservative_raster and GL_NV_conservative_raster_dilate on nvc0 
(GM200+)
  GL_NV_conservative_raster_pre_snap_triangles on nvc0 (GP102+)
  multisampled images on nvc0 (GM107+) (now supported on GF100+)

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

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

[Touch-packages] [Bug 1790320] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  system does not recover from hibernation

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

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

  3) What you expected to happen

  I walked away from the laptop. The laptop went into sleep mode or
  equivalent.

  4)what should happen is when i move the mouse or type a key or quickly
  press the power button, the machine should come out of sleep mode. It
  does not.

  I have to hard reboot the machine :(

  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 19:39:46 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/linux/+bug/1790320/+subscriptions

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

[Touch-packages] [Bug 1790320] Re: system does not recover from hibernation

[Kai-Heng Feng]

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

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

Title:
  system does not recover from hibernation

Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

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

  3) What you expected to happen

  I walked away from the laptop. The laptop went into sleep mode or
  equivalent.

  4)what should happen is when i move the mouse or type a key or quickly
  press the power button, the machine should come out of sleep mode. It
  does not.

  I have to hard reboot the machine :(

  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 19:39:46 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/linux/+bug/1790320/+subscriptions

-- 
Mailing list: https://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 1792752] Re: do-release-upgrade failed on ec2

[J K]

Thanks. It worked.

On Sun, 16 Sep 2018 at 23:31, Steve Langasek 
wrote:

> The error in your log shows:
>
> insserv: warning: script 'S99startEverything' missing LSB tags and
> overrides
> insserv: warning: script 'startEverything.sh' missing LSB tags and
> overrides
> [...]
> insserv: There is a loop between service startEverything and udev if
> started
> insserv:  loop involving service udev at depth 1
> insserv: There is a loop at service startEverything if started
> insserv: Starting startEverything.sh depends on grub-common and therefore
> on system facility `$all' which can not be true!
> [...]
>
> You appear to have a local init script, /etc/init.d/startEverything.sh,
> which is not a valid LSB init script and therefore causes problems on
> upgrade when trying to calculate init script dependencies.
>
> It's a problem that this is treated as a fatal error in the upgrader.
> Nevertheless, this script probably isn't going to do what you want it to
> post-upgrade due to the lack of correct init script dependency
> declarations.  You will want to either adjust this init script to
> contain a proper LSB init header, or remove it from your system, and try
> the upgrade again with 'sudo apt-get -f install && sudo apt-get dist-
> upgrade'.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1792752
>
> Title:
>   do-release-upgrade failed on ec2
>
> Status in sysvinit package in Ubuntu:
>   New
>
> Bug description:
>   I tried upgrading my ec2 instance from 14.04 using sudo do-release-
>   upgrade
>
>   I get this error
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: initscripts 2.88dsf-59.3ubuntu2
>   ProcVersionSignature: Ubuntu 3.13.0-158.208-generic 3.13.11-ckt39
>   Uname: Linux 3.13.0-158-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.18
>   Architecture: amd64
>   Date: Sat Sep 15 22:25:52 2018
>   Ec2AMI: ami-066736b10f23b32a3
>   Ec2AMIManifest: (unknown)
>   Ec2AvailabilityZone: ap-south-1a
>   Ec2InstanceType: t2.micro
>   Ec2Kernel: unavailable
>   Ec2Ramdisk: unavailable
>   ErrorMessage: subprocess installed post-installation script returned
> error exit status 1
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.4
>apt  1.2.27
>   SourcePackage: sysvinit
>   Title: package initscripts 2.88dsf-59.3ubuntu2 failed to
> install/upgrade: subprocess installed post-installation script returned
> error exit status 1
>   UpgradeStatus: Upgraded to xenial on 2018-09-15 (0 days ago)
>   mtime.conffile..etc.default.rcS: 2015-03-25T11:52:34.180359
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1792752/+subscriptions
>

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

Title:
  do-release-upgrade failed on ec2

Status in sysvinit package in Ubuntu:
  New

Bug description:
  I tried upgrading my ec2 instance from 14.04 using sudo do-release-
  upgrade

  I get this error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initscripts 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-158.208-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-158-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sat Sep 15 22:25:52 2018
  Ec2AMI: ami-066736b10f23b32a3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-south-1a
  Ec2InstanceType: t2.micro
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: sysvinit
  Title: package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-09-15 (0 days ago)
  mtime.conffile..etc.default.rcS: 2015-03-25T11:52:34.180359

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

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

[Touch-packages] [Bug 1794640] Re: package apport 2.20.9-0ubuntu7.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package apport 2.20.9-0ubuntu7.3 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  This bug shows up when install gparted

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_22_24_generic_42
  ApportLog:
   ERROR: apport (pid 2101) Thu Sep 27 08:53:22 2018: called for pid 2019, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 2101) Thu Sep 27 08:53:22 2018: executable: 
/usr/sbin/gpartedbin (command line "/usr/sbin/gpartedbin")
   ERROR: apport (pid 2101) Thu Sep 27 08:53:22 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
   ERROR: apport (pid 2101) Thu Sep 27 08:53:22 2018: apport: report 
/var/crash/_usr_sbin_gpartedbin.0.crash already exists and unseen, doing 
nothing to avoid disk usage DoS
  ApportVersion: 2.20.9-0ubuntu7.3
  AptOrdering:
   cups-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CrashReports:
   600:0:117:63803:2018-09-27 08:20:48.565904617 +0700:2018-09-27 
08:20:49.565904617 +0700:/var/crash/apport.0.crash
   640:0:117:1694840:2018-09-26 17:10:45.873321080 +0700:2018-09-26 
17:10:43.941266328 +0700:/var/crash/_usr_sbin_gpartedbin.0.crash
  Date: Thu Sep 27 08:20:49 2018
  DpkgHistoryLog:
   Start-Date: 2018-09-27  08:20:47
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: cups-common:amd64 (2.2.7-1ubuntu2, 2.2.7-1ubuntu2.1)
  DuplicateSignature:
   package:apport:2.20.9-0ubuntu7.3
   Setting up cups-common (2.2.7-1ubuntu2.1) ...
   dpkg: error processing package apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-05-09 (141 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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
   apt  1.6.3ubuntu0.1
  SourcePackage: apport
  Title: package apport 2.20.9-0ubuntu7.3 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1794640] [NEW] package apport 2.20.9-0ubuntu7.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Hefri Mardi]

Public bug reported:

This bug shows up when install gparted

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu7.3
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_22_24_generic_42
ApportLog:
 ERROR: apport (pid 2101) Thu Sep 27 08:53:22 2018: called for pid 2019, signal 
6, core limit 0, dump mode 1
 ERROR: apport (pid 2101) Thu Sep 27 08:53:22 2018: executable: 
/usr/sbin/gpartedbin (command line "/usr/sbin/gpartedbin")
 ERROR: apport (pid 2101) Thu Sep 27 08:53:22 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
 ERROR: apport (pid 2101) Thu Sep 27 08:53:22 2018: apport: report 
/var/crash/_usr_sbin_gpartedbin.0.crash already exists and unseen, doing 
nothing to avoid disk usage DoS
ApportVersion: 2.20.9-0ubuntu7.3
AptOrdering:
 cups-common:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CrashReports:
 600:0:117:63803:2018-09-27 08:20:48.565904617 +0700:2018-09-27 
08:20:49.565904617 +0700:/var/crash/apport.0.crash
 640:0:117:1694840:2018-09-26 17:10:45.873321080 +0700:2018-09-26 
17:10:43.941266328 +0700:/var/crash/_usr_sbin_gpartedbin.0.crash
Date: Thu Sep 27 08:20:49 2018
DpkgHistoryLog:
 Start-Date: 2018-09-27  08:20:47
 Commandline: /usr/bin/unattended-upgrade
 Upgrade: cups-common:amd64 (2.2.7-1ubuntu2, 2.2.7-1ubuntu2.1)
DuplicateSignature:
 package:apport:2.20.9-0ubuntu7.3
 Setting up cups-common (2.2.7-1ubuntu2.1) ...
 dpkg: error processing package apport (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-05-09 (141 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
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
 apt  1.6.3ubuntu0.1
SourcePackage: apport
Title: package apport 2.20.9-0ubuntu7.3 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package apport 2.20.9-0ubuntu7.3 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  This bug shows up when install gparted

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_22_24_generic_42
  ApportLog:
   ERROR: apport (pid 2101) Thu Sep 27 08:53:22 2018: called for pid 2019, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 2101) Thu Sep 27 08:53:22 2018: executable: 
/usr/sbin/gpartedbin (command line "/usr/sbin/gpartedbin")
   ERROR: apport (pid 2101) Thu Sep 27 08:53:22 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
   ERROR: apport (pid 2101) Thu Sep 27 08:53:22 2018: apport: report 
/var/crash/_usr_sbin_gpartedbin.0.crash already exists and unseen, doing 
nothing to avoid disk usage DoS
  ApportVersion: 2.20.9-0ubuntu7.3
  AptOrdering:
   cups-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CrashReports:
   600:0:117:63803:2018-09-27 08:20:48.565904617 +0700:2018-09-27 
08:20:49.565904617 +0700:/var/crash/apport.0.crash
   640:0:117:1694840:2018-09-26 17:10:45.873321080 +0700:2018-09-26 
17:10:43.941266328 +0700:/var/crash/_usr_sbin_gpartedbin.0.crash
  Date: Thu Sep 27 08:20:49 2018
  DpkgHistoryLog:
   Start-Date: 2018-09-27  08:20:47
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: cups-common:amd64 (2.2.7-1ubuntu2, 2.2.7-1ubuntu2.1)
  DuplicateSignature:
   package:apport:2.20.9-0ubuntu7.3
   Setting up cups-common (2.2.7-1ubuntu2.1) ...
   dpkg: error processing package apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-05-09 (141 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, 

[Touch-packages] [Bug 1794629] [NEW] CVE-2018-15473 - User enumeration vulnerability

[Alex Tomkins]

*** This bug is a security vulnerability ***

Public security bug reported:

https://nvd.nist.gov/vuln/detail/CVE-2018-15473

OpenSSH through 7.7 is prone to a user enumeration vulnerability due to
not delaying bailout for an invalid authenticating user until after the
packet containing the request has been fully parsed, related to
auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

Currently pending triage? https://people.canonical.com/~ubuntu-
security/cve/2018/CVE-2018-15473.html

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15473

** Information type changed from Private Security to Public

** Information type changed from Public to Public Security

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

Status in openssh package in Ubuntu:
  New

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

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

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

[Touch-packages] [Bug 1788643] Re: zombies pile up, system becomes unresponsive

[David Coronel]

Hi Ivan, the best way to engage Canonical Support to get assistance with
this issue will be to file a support case on support.canonical.com and
attach an sosreport of the affected system that is collected when the
issue happens. See my previous comment #5 for the details of sosreport.
Please check with Stephen Zarkos if you need access to the Canonical
Support Portal.

One other idea that may help in case your system is not responsive is to
have a serial console output logged in a gnu screen or tmux session.
Inside this console session, you can enable the maximum log level ("echo
9 > /proc/sysrq-trigger", you might have to run "sysctl -w
kernel.sysrq=1" before to enable sysrq) and run "dmesg -w", which will
dump dmesg and continuously append new entries to the kernel log. This
way, you won't depend on saving logs to the disk to see what's going on,
since the disk access could freeze in the moment of the failure.

You can also enable kdump and all the "panic_on_X" sysctl settings
(section Enabling various types of panics in CrashdumpRecipe
article[1]). If the system is locking up so hard that it freezes, it may
then capture a dump so that we can see what's going on. Refer to the
CrashdumpRecipe article[1] for more information.

[1] https://wiki.ubuntu.com/Kernel/CrashdumpRecipe

Thank you,
David

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

Title:
  zombies pile up, system becomes unresponsive

Status in systemd package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 16.04.5 LTS
  Release:16.04

  systemd:
Installed: 229-4ubuntu21.4
Candidate: 229-4ubuntu21.4
Version table:
   *** 229-4ubuntu21.4 500
  500 http://azure.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu21.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://azure.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  This problem is in Azure. We are seeing these problems on different
  systems. Worker nodes (Ubuntu 16.04) in a hadoop cluster start piling
  up zombies and become unresponsive. The syslog and the kernel logs
  don't provide much information.

  The only error we could correlate with what we are seeing was in the
  audit logs. See at the end of this message, the "Connection timed out"
  and the "Cannot create session: Already running in a session"
  messages.

  Our first suspect was memory pressure on the machines. We added
  logging and settings to reboot on out of memory, but all these turned
  to be red herrings.

  Aug 18 19:11:08 wn2-d3ncsp su[112600]: Successful su for root by root
  Aug 18 19:11:08 wn2-d3ncsp su[112600]: + ??? root:root
  Aug 18 19:11:08 wn2-d3ncsp su[112600]: pam_unix(su:session): session opened 
for user root by (uid=0)
  Aug 18 19:11:08 wn2-d3ncsp systemd-logind[1486]: New session c8 of user root.
  Aug 18 19:11:26 wn2-d3ncsp sshd[112690]: Did not receive identification 
string from 10.84.93.35
  Aug 18 19:11:34 wn2-d3ncsp su[112600]: pam_systemd(su:session): Failed to 
create session: Connection timed out
  Aug 18 19:11:34 wn2-d3ncsp su[112600]: pam_unix(su:session): session closed 
for user root
  Aug 18 19:11:34 wn2-d3ncsp systemd-logind[1486]: Removed session c8.

   
  Aug 18 19:12:03 wn2-d3ncsp sudo: ehiadmin : TTY=pts/1 ; PWD=/home/ehiadmin ; 
USER=root ; COMMAND=/bin/su -
  Aug 18 19:12:03 wn2-d3ncsp sudo: pam_unix(sudo:session): session opened for 
user root by ehiadmin(uid=0)
  Aug 18 19:12:03 wn2-d3ncsp su[113085]: Successful su for root by root
  Aug 18 19:12:03 wn2-d3ncsp su[113085]: + /dev/pts/1 root:root
  Aug 18 19:12:03 wn2-d3ncsp su[113085]: pam_unix(su:session): session opened 
for user root by ehiadmin(uid=0)
  Aug 18 19:12:03 wn2-d3ncsp su[113085]: pam_systemd(su:session): Cannot create 
session: Already running in a session
  Aug 18 19:12:42 wn2-d3ncsp sshd[113274]: Did not receive identification 
string from 10.84.93.42
  Aug 18 19:13:37 wn2-d3ncsp su[113085]: pam_unix(su:session): session closed 
for user root
  Aug 18 19:13:37 wn2-d3ncsp sudo: pam_unix(sudo:session): session closed for 
user root
  Aug 18 19:13:37 wn2-d3ncsp sshd[112285]: pam_unix(sshd:session): session 
closed for user ehiadmin
  Aug 18 19:13:37 wn2-d3ncsp systemd-logind[1486]: Removed session 1291.

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

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

[Touch-packages] [Bug 1794618] [NEW] package console-setup-linux 1.178ubuntu2.7 failed to install/upgrade: geïnstalleerd console-setup-linux pakket post-installation script subproces meldde een fout a

[David]

Public bug reported:

david@ubuntu-VBox:~$ lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

david@ubuntu-VBox:~$ apt-cache policy console-setup
console-setup:
  Geïnstalleerd: 1.178ubuntu2.7
  Kandidaat: 1.178ubuntu2.7
  Versietabel:
 *** 1.178ubuntu2.7 500
500 http://nl.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://nl.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
100 /var/lib/dpkg/status
 1.178ubuntu2 500
500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://nl.archive.ubuntu.com/ubuntu bionic/main i386 Packages

I was upgrading my packages using apt-get when the error occurred.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: console-setup-linux 1.178ubuntu2.7
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.3
Architecture: amd64
Date: Wed Sep 26 22:35:45 2018
ErrorMessage: geïnstalleerd console-setup-linux pakket post-installation script 
subproces meldde een fout afsluitstatus 2
InstallationDate: Installed on 2018-08-27 (30 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/local/bin/python3.7, Python 3.7.0, unpackaged
PythonDetails: /usr/local/bin/python2.7, Python 2.7.15, unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: console-setup
Title: package console-setup-linux 1.178ubuntu2.7 failed to install/upgrade: 
geïnstalleerd console-setup-linux pakket post-installation script subproces 
meldde een fout afsluitstatus 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

** Attachment added: "log apt-get upgrade.log"
   
https://bugs.launchpad.net/bugs/1794618/+attachment/5193442/+files/log%20apt-get%20upgrade.log

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

Title:
  package console-setup-linux 1.178ubuntu2.7 failed to install/upgrade:
  geïnstalleerd console-setup-linux pakket post-installation script
  subproces meldde een fout afsluitstatus 2

Status in console-setup package in Ubuntu:
  New

Bug description:
  david@ubuntu-VBox:~$ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  david@ubuntu-VBox:~$ apt-cache policy console-setup
  console-setup:
Geïnstalleerd: 1.178ubuntu2.7
Kandidaat: 1.178ubuntu2.7
Versietabel:
   *** 1.178ubuntu2.7 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://nl.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.178ubuntu2 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main i386 Packages

  I was upgrading my packages using apt-get when the error occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: console-setup-linux 1.178ubuntu2.7
  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.3
  Architecture: amd64
  Date: Wed Sep 26 22:35:45 2018
  ErrorMessage: geïnstalleerd console-setup-linux pakket post-installation 
script subproces meldde een fout afsluitstatus 2
  InstallationDate: Installed on 2018-08-27 (30 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/local/bin/python3.7, Python 3.7.0, unpackaged
  PythonDetails: /usr/local/bin/python2.7, Python 2.7.15, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: console-setup
  Title: package console-setup-linux 1.178ubuntu2.7 failed to install/upgrade: 
geïnstalleerd console-setup-linux pakket post-installation script subproces 
meldde een fout afsluitstatus 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1794606] [NEW] Optimization

[Siarhei]

Public bug reported:

Start optimization

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-135.161~14.04.1-generic 4.4.140
Uname: Linux 4.4.0-135-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.29
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: Wed Sep 26 22:53:02 2018
DistUpgraded: 2018-07-08 20:07:10,594 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 4.4.0-130-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-131-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-133-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-134-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-135-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:022f]
   Subsystem: Dell Device [1028:022f]
InstallationDate: Installed on 2018-07-08 (80 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
MachineType: Dell Inc. Inspiron 1525
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-135-generic 
root=UUID=b322bd19-1fdb-4af7-95d2-59d52d3a5ce1 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2018-07-08 (80 days ago)
dmi.bios.date: 10/27/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0U990C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1525
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Sep 26 20:48:43 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   12631 
 vendor SEC
xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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


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

Title:
  Optimization

Status in xorg package in Ubuntu:
  New

Bug description:
  Start optimization

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-135.161~14.04.1-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.29
  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: Wed Sep 26 22:53:02 2018
  DistUpgraded: 2018-07-08 20:07:10,594 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.4.0-130-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-131-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-133-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-134-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-135-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:022f]
 Subsystem: Dell Device [1028:022f]
  InstallationDate: Installed on 2018-07-08 (80 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 1525
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-135-generic 
root=UUID=b322bd19-1fdb-4af7-95d2-59d52d3a5ce1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2018-07-08 (80 days ago)
  dmi.bios.date: 10/27/2009
  dmi.bios.vendor: 

[Touch-packages] [Bug 1794603] [NEW] Optimization

[Siarhei]

Public bug reported:

Bug fix

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-135.161~14.04.1-generic 4.4.140
Uname: Linux 4.4.0-135-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Sep 26 23:05:51 2018
DistUpgraded: 2018-07-08 20:07:10,594 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 4.4.0-130-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-131-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-133-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-134-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-135-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:022f]
   Subsystem: Dell Device [1028:022f]
InstallationDate: Installed on 2018-07-08 (80 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
MachineType: Dell Inc. Inspiron 1525
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-135-generic 
root=UUID=b322bd19-1fdb-4af7-95d2-59d52d3a5ce1 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2018-07-08 (80 days ago)
dmi.bios.date: 10/27/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0U990C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1525
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Sep 26 20:48:43 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   12631 
 vendor SEC
xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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


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

Title:
  Optimization

Status in xorg package in Ubuntu:
  New

Bug description:
  Bug fix

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-135.161~14.04.1-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Sep 26 23:05:51 2018
  DistUpgraded: 2018-07-08 20:07:10,594 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.4.0-130-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-131-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-133-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-134-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-135-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:022f]
 Subsystem: Dell Device [1028:022f]
  InstallationDate: Installed on 2018-07-08 (80 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 1525
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-135-generic 
root=UUID=b322bd19-1fdb-4af7-95d2-59d52d3a5ce1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2018-07-08 (80 days ago)
  dmi.bios.date: 10/27/

[Touch-packages] [Bug 1794595] Re: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers
  looping, abandoned

Status in dbus package in Ubuntu:
  New

Bug description:
  failed to upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: dbus 1.12.2-1ubuntu1
  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
  Date: Tue Sep 25 21:11:33 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-10-20 (1072 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  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
   apt  1.6.3ubuntu0.1
  SourcePackage: dbus
  Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-09-25 (0 days ago)

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

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

[Touch-packages] [Bug 1794595] [NEW] package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned

[nigel]

Public bug reported:

failed to upgrade

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: dbus 1.12.2-1ubuntu1
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
Date: Tue Sep 25 21:11:33 2018
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2015-10-20 (1072 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
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
 apt  1.6.3ubuntu0.1
SourcePackage: dbus
Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-09-25 (0 days ago)

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


** Tags: amd64 apport-package bionic need-duplicate-check

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

Title:
  package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers
  looping, abandoned

Status in dbus package in Ubuntu:
  New

Bug description:
  failed to upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: dbus 1.12.2-1ubuntu1
  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
  Date: Tue Sep 25 21:11:33 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-10-20 (1072 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  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
   apt  1.6.3ubuntu0.1
  SourcePackage: dbus
  Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-09-25 (0 days ago)

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

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

[Touch-packages] [Bug 1789476] Re: glib apps using GSubprocess communicate might crash on g_subprocess_communicate_cancelled

[Iain Lane]

in the q

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

Title:
  glib apps using GSubprocess communicate might crash on
  g_subprocess_communicate_cancelled

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  Glib apps using subprocess communicate and cancellable is cancelled
  crashes

  [ Test case ]

  Run the attached example with
   gjs subprocess-cancelled.js

  Should not crash, or running:
   valgrind gjs subprocess-cancelled.js

  should not return any read error (as the one mentioned below)

  [ Regression potential ]

  Really low, the only thing that could happen is that the subprocess
  isn't really cancelled.

  ---

  Fixed upstream in
  https://gitlab.gnome.org/GNOME/glib/merge_requests/266

  #0  g_cancellable_cancel (cancellable=0x6) at 
../../glib/gio/gcancellable.c:486
  #1  0x77ab8d1d in g_subprocess_communicate_cancelled 
(user_data=) at ../../glib/gio/gsubprocess.c:1535

  --

  ==25871== Memcheck, a memory error detector
  ==25871== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
  ==25871== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
  ==25871== Command: gjs /tmp/subprocess-cancelled.js
  ==25871== 
  ==25871== Warning: set address range perms: large range [0x377ee1e21000, 
0x377f21e21000) (noaccess)
  ==25871== Invalid read of size 8
  ==25871==at 0x4EC5604: g_subprocess_communicate_cancelled 
(gsubprocess.c:1535)
  ==25871==by 0x547A0F4: g_main_dispatch (gmain.c:3177)
  ==25871==by 0x547A0F4: g_main_context_dispatch (gmain.c:3830)
  ==25871==by 0x547A4BF: g_main_context_iterate.isra.26 (gmain.c:3903)
  ==25871==by 0x547A54B: g_main_context_iteration (gmain.c:3964)
  ==25871==by 0x6C4EDAD: ffi_call_unix64 (in 
/usr/lib/x86_64-linux-gnu/libffi.so.6.0.4)
  ==25871==by 0x6C4E71E: ffi_call (in 
/usr/lib/x86_64-linux-gnu/libffi.so.6.0.4)
  ==25871==by 0x5775607: ??? (in /usr/lib/libgjs.so.0.0.0)
  ==25871==by 0x5776F53: ??? (in /usr/lib/libgjs.so.0.0.0)
  ==25871==by 0x8A3FF6B: CallJSNative (jscntxtinlines.h:239)
  ==25871==by 0x8A3FF6B: js::InternalCallOrConstruct(JSContext*, 
JS::CallArgs const&, js::MaybeConstruct) (Interpreter.cpp:447)

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

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

[Touch-packages] [Bug 1794169] Re: AWS ubuntu became unreachable after ssh login

[Andrii Petrenko]

information attached and status changed.

i'm using linux-image-4.15.0-1021-aws. based on
https://packages.ubuntu.com/bionic/linux-image-4.15.0-1021-aws it
maintained my Ubuntu Core.

Also i'm not 100% sure that issue in the kernel.

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

Title:
  AWS ubuntu became unreachable after ssh login

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

Bug description:
  I've reached strange situation with Ubuntu 18.04 LTS with latest
  kernel on AWS m5.xlarge instance.

  System became unreachable after series of successful ssh logins.
  systemd -user became zombie and block main systemd daemon (PID 1).

  I've created bug https://github.com/systemd/systemd/issues/10123 but
  it was closed with "there's a problem with your kernel".
  https://github.com/systemd/systemd/issues/10123#issuecomment-423984751

  Symptoms are very similar to
  https://github.com/systemd/systemd/issues/8598

  apetren+ 26679  0.0  0.0  0 0 ?Z02:56   0:00  \_ 
[(sd-pam)] 
  apetren+ 26855  0.0  0.0  76636  7816 ?Ds   02:57   0:00 
/lib/systemd/systemd --user
  apetren+ 26856  0.0  0.0  0 0 ?Z02:57   0:00  \_ 
[(sd-pam)] 
  apetren+ 26954  0.0  0.0  0 0 ?Zs   02:57   0:00  \_ [kill] 

  apetren+ 27053  0.0  0.0  76636  7496 ?Ss   02:58   0:00 
/lib/systemd/systemd --user
  apetren+ 27054  0.0  0.0 193972  2768 ?S02:58   0:00  \_ (sd-pam)

  This situation is repeatable on 7 instances 1-2 times per week.

  how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image
  2. update kernel and packages to latest version 3. from another
  instance run

  while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep
  defunc |grep -v grep" ; done

  By this command in couple of days I have 2->4->6->8... zombies and in
  a hour system is frozen...

  sudo reboot is not working, because systemd with PID 1 is unreachable.
  kill -9 1 -- not working as well.

  # uname -r:
  Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

  # systemd --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid

  
  AWS instance m5.xlarge

  Please let me know if you need any information.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-91caece9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: m5.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.xlarge
  Package: systemd 237-3ubuntu10.3
  PackageArchitecture: amd64
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws 
root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 
nvme.io_timeout=4294967295
  ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1021-aws N/A
   linux-backports-modules-4.15.0-1021-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1021-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: docker
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-02cfe7fcd8a997085
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.xlarge
  dmi.sys.vendor: Amazon EC2

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

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

[Touch-packages] [Bug 1794169] UdevDb.txt

[Andrii Petrenko]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1794169/+attachment/5193230/+files/UdevDb.txt

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

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

Title:
  AWS ubuntu became unreachable after ssh login

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

Bug description:
  I've reached strange situation with Ubuntu 18.04 LTS with latest
  kernel on AWS m5.xlarge instance.

  System became unreachable after series of successful ssh logins.
  systemd -user became zombie and block main systemd daemon (PID 1).

  I've created bug https://github.com/systemd/systemd/issues/10123 but
  it was closed with "there's a problem with your kernel".
  https://github.com/systemd/systemd/issues/10123#issuecomment-423984751

  Symptoms are very similar to
  https://github.com/systemd/systemd/issues/8598

  apetren+ 26679  0.0  0.0  0 0 ?Z02:56   0:00  \_ 
[(sd-pam)] 
  apetren+ 26855  0.0  0.0  76636  7816 ?Ds   02:57   0:00 
/lib/systemd/systemd --user
  apetren+ 26856  0.0  0.0  0 0 ?Z02:57   0:00  \_ 
[(sd-pam)] 
  apetren+ 26954  0.0  0.0  0 0 ?Zs   02:57   0:00  \_ [kill] 

  apetren+ 27053  0.0  0.0  76636  7496 ?Ss   02:58   0:00 
/lib/systemd/systemd --user
  apetren+ 27054  0.0  0.0 193972  2768 ?S02:58   0:00  \_ (sd-pam)

  This situation is repeatable on 7 instances 1-2 times per week.

  how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image
  2. update kernel and packages to latest version 3. from another
  instance run

  while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep
  defunc |grep -v grep" ; done

  By this command in couple of days I have 2->4->6->8... zombies and in
  a hour system is frozen...

  sudo reboot is not working, because systemd with PID 1 is unreachable.
  kill -9 1 -- not working as well.

  # uname -r:
  Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

  # systemd --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid

  
  AWS instance m5.xlarge

  Please let me know if you need any information.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-91caece9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: m5.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.xlarge
  Package: systemd 237-3ubuntu10.3
  PackageArchitecture: amd64
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws 
root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 
nvme.io_timeout=4294967295
  ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1021-aws N/A
   linux-backports-modules-4.15.0-1021-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1021-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: docker
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-02cfe7fcd8a997085
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.xlarge
  dmi.sys.vendor: Amazon EC2

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

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

[Touch-packages] [Bug 1794169] ProcModules.txt

[Andrii Petrenko]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1794169/+attachment/5193228/+files/ProcModules.txt

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

Title:
  AWS ubuntu became unreachable after ssh login

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

Bug description:
  I've reached strange situation with Ubuntu 18.04 LTS with latest
  kernel on AWS m5.xlarge instance.

  System became unreachable after series of successful ssh logins.
  systemd -user became zombie and block main systemd daemon (PID 1).

  I've created bug https://github.com/systemd/systemd/issues/10123 but
  it was closed with "there's a problem with your kernel".
  https://github.com/systemd/systemd/issues/10123#issuecomment-423984751

  Symptoms are very similar to
  https://github.com/systemd/systemd/issues/8598

  apetren+ 26679  0.0  0.0  0 0 ?Z02:56   0:00  \_ 
[(sd-pam)] 
  apetren+ 26855  0.0  0.0  76636  7816 ?Ds   02:57   0:00 
/lib/systemd/systemd --user
  apetren+ 26856  0.0  0.0  0 0 ?Z02:57   0:00  \_ 
[(sd-pam)] 
  apetren+ 26954  0.0  0.0  0 0 ?Zs   02:57   0:00  \_ [kill] 

  apetren+ 27053  0.0  0.0  76636  7496 ?Ss   02:58   0:00 
/lib/systemd/systemd --user
  apetren+ 27054  0.0  0.0 193972  2768 ?S02:58   0:00  \_ (sd-pam)

  This situation is repeatable on 7 instances 1-2 times per week.

  how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image
  2. update kernel and packages to latest version 3. from another
  instance run

  while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep
  defunc |grep -v grep" ; done

  By this command in couple of days I have 2->4->6->8... zombies and in
  a hour system is frozen...

  sudo reboot is not working, because systemd with PID 1 is unreachable.
  kill -9 1 -- not working as well.

  # uname -r:
  Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

  # systemd --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid

  
  AWS instance m5.xlarge

  Please let me know if you need any information.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-91caece9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: m5.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.xlarge
  Package: systemd 237-3ubuntu10.3
  PackageArchitecture: amd64
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws 
root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 
nvme.io_timeout=4294967295
  ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1021-aws N/A
   linux-backports-modules-4.15.0-1021-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1021-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: docker
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-02cfe7fcd8a997085
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.xlarge
  dmi.sys.vendor: Amazon EC2

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

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

[Touch-packages] [Bug 1794169] SystemdDelta.txt

[Andrii Petrenko]

apport information

** Attachment added: "SystemdDelta.txt"
   
https://bugs.launchpad.net/bugs/1794169/+attachment/5193229/+files/SystemdDelta.txt

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

Title:
  AWS ubuntu became unreachable after ssh login

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

Bug description:
  I've reached strange situation with Ubuntu 18.04 LTS with latest
  kernel on AWS m5.xlarge instance.

  System became unreachable after series of successful ssh logins.
  systemd -user became zombie and block main systemd daemon (PID 1).

  I've created bug https://github.com/systemd/systemd/issues/10123 but
  it was closed with "there's a problem with your kernel".
  https://github.com/systemd/systemd/issues/10123#issuecomment-423984751

  Symptoms are very similar to
  https://github.com/systemd/systemd/issues/8598

  apetren+ 26679  0.0  0.0  0 0 ?Z02:56   0:00  \_ 
[(sd-pam)] 
  apetren+ 26855  0.0  0.0  76636  7816 ?Ds   02:57   0:00 
/lib/systemd/systemd --user
  apetren+ 26856  0.0  0.0  0 0 ?Z02:57   0:00  \_ 
[(sd-pam)] 
  apetren+ 26954  0.0  0.0  0 0 ?Zs   02:57   0:00  \_ [kill] 

  apetren+ 27053  0.0  0.0  76636  7496 ?Ss   02:58   0:00 
/lib/systemd/systemd --user
  apetren+ 27054  0.0  0.0 193972  2768 ?S02:58   0:00  \_ (sd-pam)

  This situation is repeatable on 7 instances 1-2 times per week.

  how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image
  2. update kernel and packages to latest version 3. from another
  instance run

  while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep
  defunc |grep -v grep" ; done

  By this command in couple of days I have 2->4->6->8... zombies and in
  a hour system is frozen...

  sudo reboot is not working, because systemd with PID 1 is unreachable.
  kill -9 1 -- not working as well.

  # uname -r:
  Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

  # systemd --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid

  
  AWS instance m5.xlarge

  Please let me know if you need any information.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-91caece9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: m5.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.xlarge
  Package: systemd 237-3ubuntu10.3
  PackageArchitecture: amd64
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws 
root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 
nvme.io_timeout=4294967295
  ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1021-aws N/A
   linux-backports-modules-4.15.0-1021-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1021-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: docker
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-02cfe7fcd8a997085
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.xlarge
  dmi.sys.vendor: Amazon EC2

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

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

[Touch-packages] [Bug 1794169] ProcInterrupts.txt

[Andrii Petrenko]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1794169/+attachment/5193227/+files/ProcInterrupts.txt

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

Title:
  AWS ubuntu became unreachable after ssh login

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

Bug description:
  I've reached strange situation with Ubuntu 18.04 LTS with latest
  kernel on AWS m5.xlarge instance.

  System became unreachable after series of successful ssh logins.
  systemd -user became zombie and block main systemd daemon (PID 1).

  I've created bug https://github.com/systemd/systemd/issues/10123 but
  it was closed with "there's a problem with your kernel".
  https://github.com/systemd/systemd/issues/10123#issuecomment-423984751

  Symptoms are very similar to
  https://github.com/systemd/systemd/issues/8598

  apetren+ 26679  0.0  0.0  0 0 ?Z02:56   0:00  \_ 
[(sd-pam)] 
  apetren+ 26855  0.0  0.0  76636  7816 ?Ds   02:57   0:00 
/lib/systemd/systemd --user
  apetren+ 26856  0.0  0.0  0 0 ?Z02:57   0:00  \_ 
[(sd-pam)] 
  apetren+ 26954  0.0  0.0  0 0 ?Zs   02:57   0:00  \_ [kill] 

  apetren+ 27053  0.0  0.0  76636  7496 ?Ss   02:58   0:00 
/lib/systemd/systemd --user
  apetren+ 27054  0.0  0.0 193972  2768 ?S02:58   0:00  \_ (sd-pam)

  This situation is repeatable on 7 instances 1-2 times per week.

  how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image
  2. update kernel and packages to latest version 3. from another
  instance run

  while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep
  defunc |grep -v grep" ; done

  By this command in couple of days I have 2->4->6->8... zombies and in
  a hour system is frozen...

  sudo reboot is not working, because systemd with PID 1 is unreachable.
  kill -9 1 -- not working as well.

  # uname -r:
  Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

  # systemd --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid

  
  AWS instance m5.xlarge

  Please let me know if you need any information.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-91caece9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: m5.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.xlarge
  Package: systemd 237-3ubuntu10.3
  PackageArchitecture: amd64
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws 
root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 
nvme.io_timeout=4294967295
  ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1021-aws N/A
   linux-backports-modules-4.15.0-1021-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1021-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: docker
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-02cfe7fcd8a997085
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.xlarge
  dmi.sys.vendor: Amazon EC2

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

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

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

[Andrii Petrenko]

apport information

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

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

Title:
  AWS ubuntu became unreachable after ssh login

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

Bug description:
  I've reached strange situation with Ubuntu 18.04 LTS with latest
  kernel on AWS m5.xlarge instance.

  System became unreachable after series of successful ssh logins.
  systemd -user became zombie and block main systemd daemon (PID 1).

  I've created bug https://github.com/systemd/systemd/issues/10123 but
  it was closed with "there's a problem with your kernel".
  https://github.com/systemd/systemd/issues/10123#issuecomment-423984751

  Symptoms are very similar to
  https://github.com/systemd/systemd/issues/8598

  apetren+ 26679  0.0  0.0  0 0 ?Z02:56   0:00  \_ 
[(sd-pam)] 
  apetren+ 26855  0.0  0.0  76636  7816 ?Ds   02:57   0:00 
/lib/systemd/systemd --user
  apetren+ 26856  0.0  0.0  0 0 ?Z02:57   0:00  \_ 
[(sd-pam)] 
  apetren+ 26954  0.0  0.0  0 0 ?Zs   02:57   0:00  \_ [kill] 

  apetren+ 27053  0.0  0.0  76636  7496 ?Ss   02:58   0:00 
/lib/systemd/systemd --user
  apetren+ 27054  0.0  0.0 193972  2768 ?S02:58   0:00  \_ (sd-pam)

  This situation is repeatable on 7 instances 1-2 times per week.

  how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image
  2. update kernel and packages to latest version 3. from another
  instance run

  while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep
  defunc |grep -v grep" ; done

  By this command in couple of days I have 2->4->6->8... zombies and in
  a hour system is frozen...

  sudo reboot is not working, because systemd with PID 1 is unreachable.
  kill -9 1 -- not working as well.

  # uname -r:
  Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

  # systemd --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid

  
  AWS instance m5.xlarge

  Please let me know if you need any information.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-91caece9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: m5.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.xlarge
  Package: systemd 237-3ubuntu10.3
  PackageArchitecture: amd64
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws 
root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 
nvme.io_timeout=4294967295
  ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1021-aws N/A
   linux-backports-modules-4.15.0-1021-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1021-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: docker
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-02cfe7fcd8a997085
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.xlarge
  dmi.sys.vendor: Amazon EC2

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

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

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

[Andrii Petrenko]

apport information

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

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

Title:
  AWS ubuntu became unreachable after ssh login

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

Bug description:
  I've reached strange situation with Ubuntu 18.04 LTS with latest
  kernel on AWS m5.xlarge instance.

  System became unreachable after series of successful ssh logins.
  systemd -user became zombie and block main systemd daemon (PID 1).

  I've created bug https://github.com/systemd/systemd/issues/10123 but
  it was closed with "there's a problem with your kernel".
  https://github.com/systemd/systemd/issues/10123#issuecomment-423984751

  Symptoms are very similar to
  https://github.com/systemd/systemd/issues/8598

  apetren+ 26679  0.0  0.0  0 0 ?Z02:56   0:00  \_ 
[(sd-pam)] 
  apetren+ 26855  0.0  0.0  76636  7816 ?Ds   02:57   0:00 
/lib/systemd/systemd --user
  apetren+ 26856  0.0  0.0  0 0 ?Z02:57   0:00  \_ 
[(sd-pam)] 
  apetren+ 26954  0.0  0.0  0 0 ?Zs   02:57   0:00  \_ [kill] 

  apetren+ 27053  0.0  0.0  76636  7496 ?Ss   02:58   0:00 
/lib/systemd/systemd --user
  apetren+ 27054  0.0  0.0 193972  2768 ?S02:58   0:00  \_ (sd-pam)

  This situation is repeatable on 7 instances 1-2 times per week.

  how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image
  2. update kernel and packages to latest version 3. from another
  instance run

  while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep
  defunc |grep -v grep" ; done

  By this command in couple of days I have 2->4->6->8... zombies and in
  a hour system is frozen...

  sudo reboot is not working, because systemd with PID 1 is unreachable.
  kill -9 1 -- not working as well.

  # uname -r:
  Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

  # systemd --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid

  
  AWS instance m5.xlarge

  Please let me know if you need any information.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-91caece9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: m5.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.xlarge
  Package: systemd 237-3ubuntu10.3
  PackageArchitecture: amd64
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws 
root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 
nvme.io_timeout=4294967295
  ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1021-aws N/A
   linux-backports-modules-4.15.0-1021-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1021-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: docker
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-02cfe7fcd8a997085
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.xlarge
  dmi.sys.vendor: Amazon EC2

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

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

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

[Andrii Petrenko]

apport information

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

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

Title:
  AWS ubuntu became unreachable after ssh login

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

Bug description:
  I've reached strange situation with Ubuntu 18.04 LTS with latest
  kernel on AWS m5.xlarge instance.

  System became unreachable after series of successful ssh logins.
  systemd -user became zombie and block main systemd daemon (PID 1).

  I've created bug https://github.com/systemd/systemd/issues/10123 but
  it was closed with "there's a problem with your kernel".
  https://github.com/systemd/systemd/issues/10123#issuecomment-423984751

  Symptoms are very similar to
  https://github.com/systemd/systemd/issues/8598

  apetren+ 26679  0.0  0.0  0 0 ?Z02:56   0:00  \_ 
[(sd-pam)] 
  apetren+ 26855  0.0  0.0  76636  7816 ?Ds   02:57   0:00 
/lib/systemd/systemd --user
  apetren+ 26856  0.0  0.0  0 0 ?Z02:57   0:00  \_ 
[(sd-pam)] 
  apetren+ 26954  0.0  0.0  0 0 ?Zs   02:57   0:00  \_ [kill] 

  apetren+ 27053  0.0  0.0  76636  7496 ?Ss   02:58   0:00 
/lib/systemd/systemd --user
  apetren+ 27054  0.0  0.0 193972  2768 ?S02:58   0:00  \_ (sd-pam)

  This situation is repeatable on 7 instances 1-2 times per week.

  how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image
  2. update kernel and packages to latest version 3. from another
  instance run

  while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep
  defunc |grep -v grep" ; done

  By this command in couple of days I have 2->4->6->8... zombies and in
  a hour system is frozen...

  sudo reboot is not working, because systemd with PID 1 is unreachable.
  kill -9 1 -- not working as well.

  # uname -r:
  Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

  # systemd --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid

  
  AWS instance m5.xlarge

  Please let me know if you need any information.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-91caece9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: m5.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.xlarge
  Package: systemd 237-3ubuntu10.3
  PackageArchitecture: amd64
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws 
root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 
nvme.io_timeout=4294967295
  ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1021-aws N/A
   linux-backports-modules-4.15.0-1021-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1021-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: docker
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-02cfe7fcd8a997085
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.xlarge
  dmi.sys.vendor: Amazon EC2

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

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

[Touch-packages] [Bug 1794169] ProcCpuinfo.txt

[Andrii Petrenko]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1794169/+attachment/5193225/+files/ProcCpuinfo.txt

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

Title:
  AWS ubuntu became unreachable after ssh login

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

Bug description:
  I've reached strange situation with Ubuntu 18.04 LTS with latest
  kernel on AWS m5.xlarge instance.

  System became unreachable after series of successful ssh logins.
  systemd -user became zombie and block main systemd daemon (PID 1).

  I've created bug https://github.com/systemd/systemd/issues/10123 but
  it was closed with "there's a problem with your kernel".
  https://github.com/systemd/systemd/issues/10123#issuecomment-423984751

  Symptoms are very similar to
  https://github.com/systemd/systemd/issues/8598

  apetren+ 26679  0.0  0.0  0 0 ?Z02:56   0:00  \_ 
[(sd-pam)] 
  apetren+ 26855  0.0  0.0  76636  7816 ?Ds   02:57   0:00 
/lib/systemd/systemd --user
  apetren+ 26856  0.0  0.0  0 0 ?Z02:57   0:00  \_ 
[(sd-pam)] 
  apetren+ 26954  0.0  0.0  0 0 ?Zs   02:57   0:00  \_ [kill] 

  apetren+ 27053  0.0  0.0  76636  7496 ?Ss   02:58   0:00 
/lib/systemd/systemd --user
  apetren+ 27054  0.0  0.0 193972  2768 ?S02:58   0:00  \_ (sd-pam)

  This situation is repeatable on 7 instances 1-2 times per week.

  how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image
  2. update kernel and packages to latest version 3. from another
  instance run

  while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep
  defunc |grep -v grep" ; done

  By this command in couple of days I have 2->4->6->8... zombies and in
  a hour system is frozen...

  sudo reboot is not working, because systemd with PID 1 is unreachable.
  kill -9 1 -- not working as well.

  # uname -r:
  Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

  # systemd --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid

  
  AWS instance m5.xlarge

  Please let me know if you need any information.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-91caece9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: m5.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.xlarge
  Package: systemd 237-3ubuntu10.3
  PackageArchitecture: amd64
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws 
root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 
nvme.io_timeout=4294967295
  ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1021-aws N/A
   linux-backports-modules-4.15.0-1021-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1021-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: docker
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-02cfe7fcd8a997085
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.xlarge
  dmi.sys.vendor: Amazon EC2

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

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

[Touch-packages] [Bug 1794169] Lspci.txt

[Andrii Petrenko]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1794169/+attachment/5193224/+files/Lspci.txt

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

Title:
  AWS ubuntu became unreachable after ssh login

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

Bug description:
  I've reached strange situation with Ubuntu 18.04 LTS with latest
  kernel on AWS m5.xlarge instance.

  System became unreachable after series of successful ssh logins.
  systemd -user became zombie and block main systemd daemon (PID 1).

  I've created bug https://github.com/systemd/systemd/issues/10123 but
  it was closed with "there's a problem with your kernel".
  https://github.com/systemd/systemd/issues/10123#issuecomment-423984751

  Symptoms are very similar to
  https://github.com/systemd/systemd/issues/8598

  apetren+ 26679  0.0  0.0  0 0 ?Z02:56   0:00  \_ 
[(sd-pam)] 
  apetren+ 26855  0.0  0.0  76636  7816 ?Ds   02:57   0:00 
/lib/systemd/systemd --user
  apetren+ 26856  0.0  0.0  0 0 ?Z02:57   0:00  \_ 
[(sd-pam)] 
  apetren+ 26954  0.0  0.0  0 0 ?Zs   02:57   0:00  \_ [kill] 

  apetren+ 27053  0.0  0.0  76636  7496 ?Ss   02:58   0:00 
/lib/systemd/systemd --user
  apetren+ 27054  0.0  0.0 193972  2768 ?S02:58   0:00  \_ (sd-pam)

  This situation is repeatable on 7 instances 1-2 times per week.

  how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image
  2. update kernel and packages to latest version 3. from another
  instance run

  while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep
  defunc |grep -v grep" ; done

  By this command in couple of days I have 2->4->6->8... zombies and in
  a hour system is frozen...

  sudo reboot is not working, because systemd with PID 1 is unreachable.
  kill -9 1 -- not working as well.

  # uname -r:
  Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

  # systemd --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid

  
  AWS instance m5.xlarge

  Please let me know if you need any information.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-91caece9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: m5.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.xlarge
  Package: systemd 237-3ubuntu10.3
  PackageArchitecture: amd64
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws 
root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 
nvme.io_timeout=4294967295
  ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1021-aws N/A
   linux-backports-modules-4.15.0-1021-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1021-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: docker
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-02cfe7fcd8a997085
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.xlarge
  dmi.sys.vendor: Amazon EC2

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

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

[Touch-packages] [Bug 1794169] Re: AWS ubuntu became unreachable after ssh login

[Andrii Petrenko]

apport information

** Tags added: apport-collected ec2-images

** Description changed:

  I've reached strange situation with Ubuntu 18.04 LTS with latest kernel
  on AWS m5.xlarge instance.
  
  System became unreachable after series of successful ssh logins. systemd
  -user became zombie and block main systemd daemon (PID 1).
  
  I've created bug https://github.com/systemd/systemd/issues/10123 but it
  was closed with "there's a problem with your kernel".
  https://github.com/systemd/systemd/issues/10123#issuecomment-423984751
  
  Symptoms are very similar to
  https://github.com/systemd/systemd/issues/8598
  
  apetren+ 26679  0.0  0.0  0 0 ?Z02:56   0:00  \_ 
[(sd-pam)] 
  apetren+ 26855  0.0  0.0  76636  7816 ?Ds   02:57   0:00 
/lib/systemd/systemd --user
  apetren+ 26856  0.0  0.0  0 0 ?Z02:57   0:00  \_ 
[(sd-pam)] 
  apetren+ 26954  0.0  0.0  0 0 ?Zs   02:57   0:00  \_ [kill] 

  apetren+ 27053  0.0  0.0  76636  7496 ?Ss   02:58   0:00 
/lib/systemd/systemd --user
  apetren+ 27054  0.0  0.0 193972  2768 ?S02:58   0:00  \_ (sd-pam)
  
  This situation is repeatable on 7 instances 1-2 times per week.
  
  how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image 2.
  update kernel and packages to latest version 3. from another instance
  run
  
  while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep
  defunc |grep -v grep" ; done
  
  By this command in couple of days I have 2->4->6->8... zombies and in a
  hour system is frozen...
  
  sudo reboot is not working, because systemd with PID 1 is unreachable.
  kill -9 1 -- not working as well.
  
  # uname -r:
  Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  
  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
  
  # systemd --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid
  
  
  AWS instance m5.xlarge
  
  Please let me know if you need any information.
+ --- 
+ ProblemType: Bug
+ AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
+ ApportVersion: 2.20.9-0ubuntu7.3
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
+ CRDA: N/A
+ DistroRelease: Ubuntu 18.04
+ Ec2AMI: ami-91caece9
+ Ec2AMIManifest: (unknown)
+ Ec2AvailabilityZone: us-west-2b
+ Ec2InstanceType: m5.xlarge
+ Ec2Kernel: unavailable
+ Ec2Ramdisk: unavailable
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ MachineType: Amazon EC2 m5.xlarge
+ Package: systemd 237-3ubuntu10.3
+ PackageArchitecture: amd64
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws 
root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 
nvme.io_timeout=4294967295
+ ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-1021-aws N/A
+  linux-backports-modules-4.15.0-1021-aws  N/A
+  linux-firmware   N/A
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
+ Tags:  bionic ec2-images
+ Uname: Linux 4.15.0-1021-aws x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: docker
+ WifiSyslog:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 10/16/2017
+ dmi.bios.vendor: Amazon EC2
+ dmi.bios.version: 1.0
+ dmi.board.asset.tag: i-02cfe7fcd8a997085
+ dmi.board.vendor: Amazon EC2
+ dmi.chassis.asset.tag: Amazon EC2
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: Amazon EC2
+ dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
+ dmi.product.name: m5.xlarge
+ dmi.sys.vendor: Amazon EC2

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1794169/+attachment/5193221/+files/AudioDevicesInUse.txt

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

Title:
  AWS ubuntu became unreachable after ssh login

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

Bug description:
  I've reached strange situation with Ubuntu 18.04 LTS with latest
  kernel on AWS m5.xlarge instance.

  System became unreachable after series of successful ssh logins.
  syst

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[Gerben Wijnja]

And here's another one... I'm in Ubuntu 18.04, and Apache 2.4 and cURL
can not be installed at the same time.

apache2-bin depends on libcurl3
curl depends on libcurl4

:-(

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop
  mongodb

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

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

[Touch-packages] [Bug 1793092] Re: [FFe] openssl 1.1.1

[Łukasz Zemczak]

Basing on the comment from Steve this is approved so switching status to
Triaged.

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

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

Title:
  [FFe] openssl 1.1.1

Status in openssl package in Ubuntu:
  Triaged
Status in python2.7 package in Ubuntu:
  New
Status in python3.6 package in Ubuntu:
  New

Bug description:
  Merge openssl 1.1.1 from debian unstable.

  OpenSSL 1.1.1 is now out, with TLS1.3 support, and is the new upstream
  LTS release.

  Resulting in the following changes in Ubuntu:

  - openssl moves from 1.1.0 series to 1.1.1 LTS series

  - TLS1.3 is enabled, and used by default, when possible. Major
  feature.

  - All existing delta, and minimally accepted key sizes, and minimally
  accepted protocol versions remain the same.

  Proposed package is in
  https://launchpad.net/~xnox/+archive/ubuntu/openssl with a rebuild of
  all the reverse dependencies. It demonstrates that openssl compiled as
  above is more compatible and has less issues than debian config. There
  are a few FTBFS, which are also present in cosmic-release; there are
  some test-suite expectations mismatch (connectivity succeeds with
  tls1.3 even though lower/different algos are expected); there are very
  little connectivity tests thus connectivity interop are the biggest
  issues which will be unavoidable with introducing 1.3.

  ===

  Ubuntu delta summary versus debian unstable in this merge:
  - Replace duplicate files in the doc directory with symlinks.
  - debian/libssl1.1.postinst:
    + Display a system restart required notification on libssl1.1
  upgrade on servers.
    + Use a different priority for libssl1.1/restart-services depending
  on whether a desktop, or server dist-upgrade is being performed.
  - Revert "Enable system default config to enforce TLS1.2 as a
    minimum" & "Increase default security level from 1 to 2".
  - Further decrease security level from 1 to 0, for compatibility with
    openssl 1.0.2.

  These mitigate most of the runtime incompatibilities, and ensure
  client<->server compatibility between 1.1.1, 1.1.0, and 1.0.2 series
  and thus one can continue to mix & match xenial/bionic/cosmic
  releases.

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

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

[Touch-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot

[Chris J Arges]

Hello Tiago, or anyone else affected,

Accepted initramfs-tools into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.130ubuntu3.4 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

** Changed in: initramfs-tools (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-bionic

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  [SRU] remove orphaned initrd old-dkms files in /boot

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has been manually configured by a user then when a kernel is removed its 
possible for an ".old-dkms" file to be left in /boot with no associated kernel.

  bug 1515513 dealt with removing old-dkms initrd files using the
  kernel's prerm hook, but that is only executed for the kernel version
  being removed: any other old-dkms file generated prior to that would
  not be removed by the hook, taking space in the /boot directory and
  being carried forward with every upgrade.

  Note: Filling up the /boot partition causes updates and upgrades to
  fail.

  [Test Case]
  As the fix for bug 1515513 is available on Xenial and Bionic it is no longer 
possible to reproduce this by simply installing and updating kernels - dkms 
2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. 
In order to replicate it an old dkms file will be created by hand.

  This assumes a new Xenial/Bionic schroot.

  1) create files to work as a placeholders for old dkms files (there are 4 
possible namings for these files)
  touch /boot/initrd-4.0.0-0-generic.img.old-dkms 
/boot/initramfs-4.0.0-0-generic.img.old-dkms 
/boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms

  2) install 3 old kernels, r8168-dkms, and the current initramfs-tools
  * xenial:
  apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic 
linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12
  * bionic:
  apt-get install -y linux-image-4.15.0-32-generic 
linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms 
initramfs-tools=0.130ubuntu3.3

  3) install the headers for the old kernels (forces dkms to run)
  * xenial:
  apt-get install -y linux-headers-4.4.0-21-generic 
linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic
  * bionic:
  apt-get install -y linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic

  4) verify that there are 7 old-dkms, the 4 manually created ones and one for 
each installed kernel
  ls -1 /boot/*.old-dkms

  5) install the initramfs-tools from proposed that contains this fix
  apt-get install -y initramfs-tools

  6) verify that the manually created old-dkms files were removed and that 
there are only 3 files now, one for each installed kernel
  ls /boot/*.old-dkms

  7) mark kernel images and headers as automatically installed
  apt-mark auto linux-image-4*-generic linux-headers-4*-generic

  8) autoremove the older kernel
  apt-get autoremove -y

  9) verify that there are now only 2 old-dkms, one for each installed kernel
  ls -1 /boot/*.old-dkms

  
  These steps guarantees that:
  - orphaned old-dkms are correctly removed from /boot
  - non-orphaned old-dkms are kept
  - when kernel is removed the related old-dkms are also deleted

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo a

[Touch-packages] [Bug 1667512] Please test proposed package

[Chris J Arges]

Hello tbenst, or anyone else affected,

Accepted initramfs-tools into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.122ubuntu8.13 in a few hours, and then in the -proposed
repository.

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

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

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

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

Title:
  [SRU] update-initramfs should sync only the filesystem containing the
  initramfs image

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  [Impact]
  If there is lots of activity on a different filesystem, high io/cache 
pressure, or a stale mount updating initramfs might hang because the 
update-initramfs script calls sync. This leaves the system unresponsive and 
will require the user to forcefully kill dpkg.

  [Test Case]
  One easy way to simulate this is by copying a huge file over nfs. Note: do 
not use localhost, it is too fast for this purpose, a network bridge over qemu 
is good enough.

  1. Setup a nfs server and export a directory with write permissions
  for the client

  2. Copy a big file over NFS (assumes it is mounted at /mnt in the client)
  $ dd if=/dev/zero of=/mnt/big_zeros bs=512 count=1M status=progress
  Note: adjust the "count" accordingly to how fast/slow your system is.

  3. Call sync and verify that it only finished after "dd" is done.

  4. Repeat step #2 and now call "sync -f /boot/".
  Verify that it finished immediatly.

  [Regression Potential]
  Although syncfs(2) man page [2] states that it works just the same as sync - 
except being limited to a filesystem -, any actual differences in the 
implementation can affect how the initrd image file is synced to the disk, 
leading to unexpected behavior.

  [Other]
  If syncfs is unsupported then the 'sync' binary will ensure that a normal 
system-wide sync is called [1]. The proposed patch won't help in scenarios 
where the initrd file is located in a busy filesystem (eg. no separated /boot 
partition).

  The 'sync' and 'syncfs' specifications are pretty much similar and
  syncfs is expected to work the same as a normal sync regarding data
  integrity. Also altought the patch introduces the initrd file as an
  extra argument which would cause 'sync -f' to fail if the file does
  not exist, the update-initramfs script would fail earlier than that
  because that file is created by the 'mv' call a few lines above. Thus
  no regressions are expected.

  [References]
  [1] 
http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/sync.c?id=8b2bf5295f353016d4f5e6a2317d55b6a8e7fd00
  [2] http://manpages.ubuntu.com/manpages/xenial/man2/syncfs.2.html

  [Original bug report]
  At least four users, including myself, are having an issue with 
update-initramfs hanging while updating ubuntu 16.04. The bug has been 
documented while attempting an update to multiple kernel versions ( 4.4.0-24, 
4.4.0-62,  4.4.0-63). The bug causes any apt-get update or install to fail, and 
may also lead to an unbootable system.

  User #1 (me):
  $ uname -a
  Linux  4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo apt-get upgrade
  Fetched 1,571 MB in 2min 9s (12.2 MB/s)
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  (Reading database ... 344634 files and directories currently installed.)
  Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ...
  Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ...
  Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for cracklib-runtime (2.9.2-1build2) ...
  Processing triggers for install-info (6.1.0.dfsg.1-5) ...
  Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic

   

[Touch-packages] [Bug 1667512] Re: [SRU] update-initramfs should sync only the filesystem containing the initramfs image

[Chris J Arges]

Hello tbenst, or anyone else affected,

Accepted initramfs-tools into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.130ubuntu3.4 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

** Changed in: initramfs-tools (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-bionic

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  [SRU] update-initramfs should sync only the filesystem containing the
  initramfs image

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  [Impact]
  If there is lots of activity on a different filesystem, high io/cache 
pressure, or a stale mount updating initramfs might hang because the 
update-initramfs script calls sync. This leaves the system unresponsive and 
will require the user to forcefully kill dpkg.

  [Test Case]
  One easy way to simulate this is by copying a huge file over nfs. Note: do 
not use localhost, it is too fast for this purpose, a network bridge over qemu 
is good enough.

  1. Setup a nfs server and export a directory with write permissions
  for the client

  2. Copy a big file over NFS (assumes it is mounted at /mnt in the client)
  $ dd if=/dev/zero of=/mnt/big_zeros bs=512 count=1M status=progress
  Note: adjust the "count" accordingly to how fast/slow your system is.

  3. Call sync and verify that it only finished after "dd" is done.

  4. Repeat step #2 and now call "sync -f /boot/".
  Verify that it finished immediatly.

  [Regression Potential]
  Although syncfs(2) man page [2] states that it works just the same as sync - 
except being limited to a filesystem -, any actual differences in the 
implementation can affect how the initrd image file is synced to the disk, 
leading to unexpected behavior.

  [Other]
  If syncfs is unsupported then the 'sync' binary will ensure that a normal 
system-wide sync is called [1]. The proposed patch won't help in scenarios 
where the initrd file is located in a busy filesystem (eg. no separated /boot 
partition).

  The 'sync' and 'syncfs' specifications are pretty much similar and
  syncfs is expected to work the same as a normal sync regarding data
  integrity. Also altought the patch introduces the initrd file as an
  extra argument which would cause 'sync -f' to fail if the file does
  not exist, the update-initramfs script would fail earlier than that
  because that file is created by the 'mv' call a few lines above. Thus
  no regressions are expected.

  [References]
  [1] 
http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/sync.c?id=8b2bf5295f353016d4f5e6a2317d55b6a8e7fd00
  [2] http://manpages.ubuntu.com/manpages/xenial/man2/syncfs.2.html

  [Original bug report]
  At least four users, including myself, are having an issue with 
update-initramfs hanging while updating ubuntu 16.04. The bug has been 
documented while attempting an update to multiple kernel versions ( 4.4.0-24, 
4.4.0-62,  4.4.0-63). The bug causes any apt-get update or install to fail, and 
may also lead to an unbootable system.

  User #1 (me):
  $ uname -a
  Linux  4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo apt-get upgrade
  Fetched 1,571 MB in 2min 9s (12.2 MB/s)
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  (Reading database ... 344634 files and directories currently installed.)
  Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ...
  Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ...
  Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for man

[Touch-packages] [Bug 1791959] Please test proposed package

[Chris J Arges]

Hello Tiago, or anyone else affected,

Accepted initramfs-tools into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.122ubuntu8.13 in a few hours, and then in the -proposed
repository.

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

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

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

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

Title:
  [SRU] remove orphaned initrd old-dkms files in /boot

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has been manually configured by a user then when a kernel is removed its 
possible for an ".old-dkms" file to be left in /boot with no associated kernel.

  bug 1515513 dealt with removing old-dkms initrd files using the
  kernel's prerm hook, but that is only executed for the kernel version
  being removed: any other old-dkms file generated prior to that would
  not be removed by the hook, taking space in the /boot directory and
  being carried forward with every upgrade.

  Note: Filling up the /boot partition causes updates and upgrades to
  fail.

  [Test Case]
  As the fix for bug 1515513 is available on Xenial and Bionic it is no longer 
possible to reproduce this by simply installing and updating kernels - dkms 
2.2.0.3-2ubuntu11.3/xenial or 2.3-3ubuntu1/bionic would be required for that. 
In order to replicate it an old dkms file will be created by hand.

  This assumes a new Xenial/Bionic schroot.

  1) create files to work as a placeholders for old dkms files (there are 4 
possible namings for these files)
  touch /boot/initrd-4.0.0-0-generic.img.old-dkms 
/boot/initramfs-4.0.0-0-generic.img.old-dkms 
/boot/initrd.img-4.0.0-0-generic.old-dkms /boot/initrd-4.0.0-0-generic.old-dkms

  2) install 3 old kernels, r8168-dkms, and the current initramfs-tools
  * xenial:
  apt-get install -y linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic 
linux-image-4.4.0-24-generic r8168-dkms initramfs-tools=0.122ubuntu8.12
  * bionic:
  apt-get install -y linux-image-4.15.0-32-generic 
linux-image-4.15.0-33-generic linux-image-4.15.0-34-generic r8168-dkms 
initramfs-tools=0.130ubuntu3.3

  3) install the headers for the old kernels (forces dkms to run)
  * xenial:
  apt-get install -y linux-headers-4.4.0-21-generic 
linux-headers-4.4.0-22-generic linux-headers-4.4.0-24-generic
  * bionic:
  apt-get install -y linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-33-generic linux-headers-4.15.0-34-generic

  4) verify that there are 7 old-dkms, the 4 manually created ones and one for 
each installed kernel
  ls -1 /boot/*.old-dkms

  5) install the initramfs-tools from proposed that contains this fix
  apt-get install -y initramfs-tools

  6) verify that the manually created old-dkms files were removed and that 
there are only 3 files now, one for each installed kernel
  ls /boot/*.old-dkms

  7) mark kernel images and headers as automatically installed
  apt-mark auto linux-image-4*-generic linux-headers-4*-generic

  8) autoremove the older kernel
  apt-get autoremove -y

  9) verify that there are now only 2 old-dkms, one for each installed kernel
  ls -1 /boot/*.old-dkms

  
  These steps guarantees that:
  - orphaned old-dkms are correctly removed from /boot
  - non-orphaned old-dkms are kept
  - when kernel is removed the related old-dkms are also deleted

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

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

-- 
Mailing list: https://launc

[Touch-packages] [Bug 1789476] Re: glib apps using GSubprocess communicate might crash on g_subprocess_communicate_cancelled

[Iain Lane]

I'm uploading 2.56.3 now

** Also affects: glib2.0 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: glib2.0 (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: glib2.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  glib apps using GSubprocess communicate might crash on
  g_subprocess_communicate_cancelled

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  Glib apps using subprocess communicate and cancellable is cancelled
  crashes

  [ Test case ]

  Run the attached example with
   gjs subprocess-cancelled.js

  Should not crash, or running:
   valgrind gjs subprocess-cancelled.js

  should not return any read error (as the one mentioned below)

  [ Regression potential ]

  Really low, the only thing that could happen is that the subprocess
  isn't really cancelled.

  ---

  Fixed upstream in
  https://gitlab.gnome.org/GNOME/glib/merge_requests/266

  #0  g_cancellable_cancel (cancellable=0x6) at 
../../glib/gio/gcancellable.c:486
  #1  0x77ab8d1d in g_subprocess_communicate_cancelled 
(user_data=) at ../../glib/gio/gsubprocess.c:1535

  --

  ==25871== Memcheck, a memory error detector
  ==25871== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
  ==25871== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
  ==25871== Command: gjs /tmp/subprocess-cancelled.js
  ==25871== 
  ==25871== Warning: set address range perms: large range [0x377ee1e21000, 
0x377f21e21000) (noaccess)
  ==25871== Invalid read of size 8
  ==25871==at 0x4EC5604: g_subprocess_communicate_cancelled 
(gsubprocess.c:1535)
  ==25871==by 0x547A0F4: g_main_dispatch (gmain.c:3177)
  ==25871==by 0x547A0F4: g_main_context_dispatch (gmain.c:3830)
  ==25871==by 0x547A4BF: g_main_context_iterate.isra.26 (gmain.c:3903)
  ==25871==by 0x547A54B: g_main_context_iteration (gmain.c:3964)
  ==25871==by 0x6C4EDAD: ffi_call_unix64 (in 
/usr/lib/x86_64-linux-gnu/libffi.so.6.0.4)
  ==25871==by 0x6C4E71E: ffi_call (in 
/usr/lib/x86_64-linux-gnu/libffi.so.6.0.4)
  ==25871==by 0x5775607: ??? (in /usr/lib/libgjs.so.0.0.0)
  ==25871==by 0x5776F53: ??? (in /usr/lib/libgjs.so.0.0.0)
  ==25871==by 0x8A3FF6B: CallJSNative (jscntxtinlines.h:239)
  ==25871==by 0x8A3FF6B: js::InternalCallOrConstruct(JSContext*, 
JS::CallArgs const&, js::MaybeConstruct) (Interpreter.cpp:447)

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

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

[Touch-packages] [Bug 1794551] [NEW] Incorrect display resolution being set on startup

[Ritesh Doke]

Public bug reported:

On startup, incorrect display resolution is setup which is showing UI in
higher resolution.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
Uname: Linux 4.4.0-135-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Sep 26 20:35:26 2018
InstallationDate: Installed on 2017-08-22 (400 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Incorrect display resolution being set on startup

Status in lightdm package in Ubuntu:
  New

Bug description:
  On startup, incorrect display resolution is setup which is showing UI
  in higher resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 26 20:35:26 2018
  InstallationDate: Installed on 2017-08-22 (400 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1788220] Re: [snap] Ubuntu 18.04 LTS includes gnome-calculator as a snap

[Ivan]

** Changed in: ubuntu-meta (Ubuntu)
   Status: Invalid => New

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

Title:
  [snap] Ubuntu 18.04 LTS includes gnome-calculator as a snap

Status in gnome-calculator package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 includes the calculator as a snap.

  The standard installation of snap, with no custom snap apps installed
  other than what Ubuntu installs by default, takes a whooping 1.6GB of
  hard disk. Calc takes forever to start in a modern machine compared to
  the normal calc installed with APT, creates snap files in the user's
  home dir (with name $HOME/snap). This is ridiculous.

  Snap is immature, there's no sysadmin tool support, and it's not ready
  to make it the default for standard Ubuntu LTS.

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

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

[Touch-packages] [Bug 1794544] [NEW] [SRU] 2.56.3

[Iain Lane]

Public bug reported:

[ Description ]

The third stable release in the 2.56 series.

[ QA ]

Upstream release, so QA already performed by maintainers

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

[ Regresison potential ]

Various fixes in multiple places so multiple apps could be affected.

  * New upstream release (LP: #xxx)
+ The documentation for G_GNUC_MALLOC has changed to be more restrictive
  to avoid miscompilations; you should check whether any uses of it in
  your code are appropriate
+ Fix cancellation of g_subprocess_communicate_async() calls
+ Bug fixes:
  + /network-monitor/create-in-thread fails in (LXC) containers on glib-2-56
  + GBookmarkFile: nullptr access in current_element
  + GBookmarkFile: heap-buffer-overflow in g_utf8_get_char
  + Backport g_subprocess_communicate() cancellation fixes from !266 to 
glib-2-56 (LP: #1789476)
  + Many uses of G_GNUC_MALLOC are incorrect
  + Test for BROKEN_IP_MREQ_SOURCE_STRUCT is broken on Windows / Mingw
  + Fix persistent CI failure on glib-2-56

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: glib2.0 (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Also affects: glib2.0 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: glib2.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: glib2.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  [SRU] 2.56.3

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  In Progress

Bug description:
  [ Description ]

  The third stable release in the 2.56 series.

  [ QA ]

  Upstream release, so QA already performed by maintainers

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

  [ Regresison potential ]

  Various fixes in multiple places so multiple apps could be affected.

* New upstream release (LP: #xxx)
  + The documentation for G_GNUC_MALLOC has changed to be more restrictive
to avoid miscompilations; you should check whether any uses of it in
your code are appropriate
  + Fix cancellation of g_subprocess_communicate_async() calls
  + Bug fixes:
+ /network-monitor/create-in-thread fails in (LXC) containers on 
glib-2-56
+ GBookmarkFile: nullptr access in current_element
+ GBookmarkFile: heap-buffer-overflow in g_utf8_get_char
+ Backport g_subprocess_communicate() cancellation fixes from !266 to 
  glib-2-56 (LP: #1789476)
+ Many uses of G_GNUC_MALLOC are incorrect
+ Test for BROKEN_IP_MREQ_SOURCE_STRUCT is broken on Windows / Mingw
+ Fix persistent CI failure on glib-2-56

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

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

[Touch-packages] [Bug 1793555] Re: networkd tears down bridge ip address when the last device is pulled out from the bridge

[Launchpad Bug Tracker]

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

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

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

Title:
  networkd tears down bridge ip address when the last device is pulled
  out from the bridge

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 18.04.1 LTS (systemd 237) pulling out the last device out of
  the bridge removes the bridge ip address.

  given the following config:

  # cat /etc/systemd/network/vmbr0.netdev
  [NetDev]
  Name=vmbr0
  Kind=bridge

  [Bridge]
  HelloTimeSec=0
  ForwardDelaySec=0
  STP=no

  # cat /etc/systemd/network/vmbr0.network
  [Match]
  Name=vmbr0

  [Network]
  Address=10.10.0.1/16
  ConfigureWithoutCarrier=yes
  DHCP=no
  IPForward=yes
  IPv6AcceptRA=no
  LinkLocalAddressing=no

  networkd would bring up vmbr0 with 10.10.0.1/16 on system boot despite
  it not having any devices, allowing services to bind to 10.10.0.1.

  However, if you add a device and then remove it (e.g. by starting and
  then stopping a virtual machine connected to the bridge), networkd
  would tear down the interface:

  3: vmbr0:  mtu 1500 qdisc noqueue state 
DOWN group default qlen 1000
  link/ether 16:19:4c:7f:e8:c4 brd ff:ff:ff:ff:ff:ff

  thus making any service listening on 10.10.0.1 inaccessible.

  previously on Xenial the bridge would stay intact.

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

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

[Touch-packages] [Bug 1788220] Re: [snap] Ubuntu 18.04 LTS includes gnome-calculator as a snap

[Ivan]

@paulw2u I disagree with this being a gnome-calculator problem. This is
a much more general problem that has to do also with the installation
size.

I believe that bugs like this, and like [1], indicate that snap is not
yet ready to be included by default, and especially not for basic
desktop applications like calc.

I would like the status of this bug to be reset to affect Ubuntu (or
perhaps ubuntu-desktop if that's the one that should depend on gnome-
calculator), and the inclusion of snap or potential removal from the
default installation (meaning as a direct or indirect dependency of
ubuntu-desktop) to be discussed.

[1] https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1575053

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

Title:
  [snap] Ubuntu 18.04 LTS includes gnome-calculator as a snap

Status in gnome-calculator package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 18.04 includes the calculator as a snap.

  The standard installation of snap, with no custom snap apps installed
  other than what Ubuntu installs by default, takes a whooping 1.6GB of
  hard disk. Calc takes forever to start in a modern machine compared to
  the normal calc installed with APT, creates snap files in the user's
  home dir (with name $HOME/snap). This is ridiculous.

  Snap is immature, there's no sysadmin tool support, and it's not ready
  to make it the default for standard Ubuntu LTS.

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

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

[Touch-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic

[Julian Andres Klode]

As Adam mentioned, the top-level kernel meta packages should change
their section to metapackages, so we don't mark linux-image-generic for
autoremoval if linux-generic is removed.

I'm looking into adding additional NeverAutoRemove entries for the
metapackages to apt as

"^linux-image-[a-z0-9]*$";
"^linux-image-[a-z0-9]*-[a-z0-9]*$";

but I'm not sure if that catches all meta packages or more than it
should.

** Package changed: unattended-upgrades (Ubuntu) => apt (Ubuntu)

** Changed in: linux-meta (Ubuntu)
   Importance: Undecided => Critical

** Changed in: linux-meta-hwe (Ubuntu)
   Importance: Undecided => Critical

** Changed in: linux-meta-hwe (Ubuntu)
   Status: New => Triaged

** Changed in: linux-meta (Ubuntu)
   Status: New => Triaged

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

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

Title:
  Unattended upgrades removed linux-image-generic

Status in apt package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-hwe package in Ubuntu:
  Triaged

Bug description:
  On a fairly fresh install of 18.04 with no modifications whatsoever to
  the unattended-upgrades configuration, it decided to remove linux-
  image-generic which also removed linux-modules-extra which caused
  sound drivers to disappear, etc.

  The relative snippet from /var/log/unattended-upgrades/unattended-
  upgrades.log is:

  2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
  2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
  2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
  2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
  2018-08-15 06:18:09,477 INFO Packages that are kept back: 
linux-headers-generic
  2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
  2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2018-08-15 06:18:39,238 INFO All upgrades installed
  2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: 
linux-image-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:42,818 INFO Packages that are kept back:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 13:17:30 2018
  InstallationDate: Installed on 2018-07-24 (23 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic

[Julian Andres Klode]

** Also affects: linux-hwe (Ubuntu)
   Importance: Undecided
   Status: New

** Package changed: linux-hwe (Ubuntu) => linux-meta-hwe (Ubuntu)

** Also affects: linux-meta (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/1787460

Title:
  Unattended upgrades removed linux-image-generic

Status in apt package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-hwe package in Ubuntu:
  Triaged

Bug description:
  On a fairly fresh install of 18.04 with no modifications whatsoever to
  the unattended-upgrades configuration, it decided to remove linux-
  image-generic which also removed linux-modules-extra which caused
  sound drivers to disappear, etc.

  The relative snippet from /var/log/unattended-upgrades/unattended-
  upgrades.log is:

  2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
  2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
  2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
  2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
  2018-08-15 06:18:09,477 INFO Packages that are kept back: 
linux-headers-generic
  2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
  2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2018-08-15 06:18:39,238 INFO All upgrades installed
  2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: 
linux-image-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:42,818 INFO Packages that are kept back:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 13:17:30 2018
  InstallationDate: Installed on 2018-07-24 (23 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1794523] [NEW] lxc-net.service is not properly ordered with network-online.target

[EOLE team]

Public bug reported:

I made several tests and I figure out that the lxc-net.service is
missing a Wants= directive to be properly ordered against network-
online.target.

As I understand the systemd.unit manpage, to be properly ordered a unit
must define a Requires=/Wants= in addition to an After=/Before=.

Regards.

Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic

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


** Tags: bionic

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

Title:
  lxc-net.service is not properly ordered with network-online.target

Status in lxc package in Ubuntu:
  New

Bug description:
  I made several tests and I figure out that the lxc-net.service is
  missing a Wants= directive to be properly ordered against network-
  online.target.

  As I understand the systemd.unit manpage, to be properly ordered a
  unit must define a Requires=/Wants= in addition to an After=/Before=.

  Regards.

  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

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

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

[Touch-packages] [Bug 1786940] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From bren...@br.ibm.com 2018-09-26 09:14 EDT---
(In reply to comment #8)
> Given the targets specified, you are asking to SRU this into bionic as well,
> right? or is cosmic sufficient? (to e.g. use chroots?)

Yes, if it is possible, I would like to have this available in bionic
also.

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

Title:
  Enable arm-linux-gnueabi target on ppc64el toolchain

Status in The Ubuntu-power-systems project:
  Incomplete
Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-7-cross package in Ubuntu:
  New
Status in gcc-8-cross package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  Incomplete

Bug description:
  Dear Canonical.

  We would like to have arm-linux-gnueabi target on ppc64el cross
  toolchain. This would enable us to use a ppc64el host to do cross
  compilation for aarch64.

  I talked to Matthias Klose already, and he is aware of this request.

  Thank you,
  Breno

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1786940/+subscriptions

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

[Touch-packages] [Bug 1794517] Re: Empty Display property in org.freedesktop.login1.session

[Roman Shipovskij]

** Tags added: bionic

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

Title:
  Empty Display property in org.freedesktop.login1.session

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 18.04 when get property of Display variable using DBus
  org.freedesktop.login1.session get empty value.

  In Ubuntu 16.04 release these values isn`t empty and get for example
  Display = :0.

  I use:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Package info:

  Package: systemd
  Version: 237-3ubuntu10.3
  Priority: important
  Section: admin
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian systemd Maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 12,9 MB
  Pre-Depends: libacl1 (>= 2.2.51-8), libblkid1 (>= 2.19.1), libc6 (>= 2.27), 
libcap2 (>= 1:2.10), libcryptsetup12 (>= 2:1.4), libgcrypt20 (>= 1.8.0), 
libidn11 (>= 1.13), libip4tc0 (>= 1.6.0+snapshot20161117), liblz4-1 (>= 
0.0~r130), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2 (>= 2.3.1), 
libselinux1 (>= 2.1.9)
  Depends: libapparmor1 (>= 2.9.0-3+exp2), libaudit1 (>= 1:2.2.1), 
libcryptsetup12 (>= 2:1.4.3), libgpg-error0 (>= 1.14), libkmod2 (>= 5~), 
libmount1 (>= 2.26.2), libpam0g (>= 0.99.7.1), libsystemd0 (= 237-3ubuntu10.3), 
util-linux (>= 2.27.1), mount (>= 2.26), adduser, procps
  Recommends: libpam-systemd, dbus, networkd-dispatcher
  Suggests: systemd-container, policykit-1
  Breaks: apparmor (<< 2.9.2-1), ifupdown (<< 0.8.5~), laptop-mode-tools (<< 
1.68~), systemd-shim (<< 10-3~), udev (<< 228-5)
  Replaces: udev (<< 228-5)
  Homepage: https://www.freedesktop.org/wiki/Software/systemd
  Task: minimal, ubuntu-core
  Supported: 5y
  Download-Size: 2 947 kB
  APT-Manual-Installed: yes
  APT-Sources: http://my.repo/ubuntu-current bionic-updates/main i386 Packages
  Description: system and service manager

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

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

[Touch-packages] [Bug 1794517] Re: Empty Display property in org.freedesktop.login1.session

[Launchpad Bug Tracker]

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

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

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

Title:
  Empty Display property in org.freedesktop.login1.session

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 18.04 when get property of Display variable using DBus
  org.freedesktop.login1.session get empty value.

  In Ubuntu 16.04 release these values isn`t empty and get for example
  Display = :0.

  I use:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Package info:

  Package: systemd
  Version: 237-3ubuntu10.3
  Priority: important
  Section: admin
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian systemd Maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 12,9 MB
  Pre-Depends: libacl1 (>= 2.2.51-8), libblkid1 (>= 2.19.1), libc6 (>= 2.27), 
libcap2 (>= 1:2.10), libcryptsetup12 (>= 2:1.4), libgcrypt20 (>= 1.8.0), 
libidn11 (>= 1.13), libip4tc0 (>= 1.6.0+snapshot20161117), liblz4-1 (>= 
0.0~r130), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2 (>= 2.3.1), 
libselinux1 (>= 2.1.9)
  Depends: libapparmor1 (>= 2.9.0-3+exp2), libaudit1 (>= 1:2.2.1), 
libcryptsetup12 (>= 2:1.4.3), libgpg-error0 (>= 1.14), libkmod2 (>= 5~), 
libmount1 (>= 2.26.2), libpam0g (>= 0.99.7.1), libsystemd0 (= 237-3ubuntu10.3), 
util-linux (>= 2.27.1), mount (>= 2.26), adduser, procps
  Recommends: libpam-systemd, dbus, networkd-dispatcher
  Suggests: systemd-container, policykit-1
  Breaks: apparmor (<< 2.9.2-1), ifupdown (<< 0.8.5~), laptop-mode-tools (<< 
1.68~), systemd-shim (<< 10-3~), udev (<< 228-5)
  Replaces: udev (<< 228-5)
  Homepage: https://www.freedesktop.org/wiki/Software/systemd
  Task: minimal, ubuntu-core
  Supported: 5y
  Download-Size: 2 947 kB
  APT-Manual-Installed: yes
  APT-Sources: http://my.repo/ubuntu-current bionic-updates/main i386 Packages
  Description: system and service manager

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

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

[Touch-packages] [Bug 1794516] Re: systemd-logind does not track all user processes

[Valentyna]

** Description changed:

  In Ubuntu 16.04(xenial) release all user processes are in session scope
  for example:
  
  └─user.slice
-   └─user-200463.slice
- ├─user@200463.service
- │ └─init.scope
- │   ├─5886 /lib/systemd/systemd --user
- │   └─5888 (sd-pam) 
- └─session-c2.scope
-   ├─  419 bash
-   ├─  471 mc
-   ├─  473 bash -rcfile .bashrc
-   ├─ 1432 bash
-   ├─ 1455 mc
-   ├─ 1457 bash -rcfile .bashrc
-   ├─ 1915 /usr/sbin/sssd -D -f
+   └─user-200463.slice
+ ├─user@200463.service
+ │ └─init.scope
+ │   ├─5886 /lib/systemd/systemd --user
+ │   └─5888 (sd-pam)
+ └─session-c2.scope
+   ├─  419 bash
+   ├─  471 mc
+   ├─  473 bash -rcfile .bashrc
+   ├─ 1432 bash
+   ├─ 1455 mc
+   ├─ 1457 bash -rcfile .bashrc
+   ├─ 1915 /usr/sbin/sssd -D -f
  
  In Ubuntu 18.04 (bionic) some processes are in session scope and other
  are in user service for example:
  
  ├─user.slice
  │ ├─user-200463.slice
  │ │ ├─session-84.scope
  │ │ │ ├─14992 gdm-session-worker [pam/gdm-password]
  │ │ │ ├─15013 /usr/bin/gnome-keyring-daemon --daemonize --login
  │ │ │ ├─15057 /usr/lib/gdm3/gdm-x-session --run-script env 
GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
  │ │ │ ├─15059 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/200463/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  │ │ │ ├─15114 /usr/lib/gnome-session/gnome-session-binary --session=ubuntu
  │ │ │ ├─15205 /usr/bin/ssh-agent /usr/bin/im-launch env 
GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
  │ │ │ ├─15317 /usr/bin/gnome-shell
  │ │ │ ├─15326 /usr/bin/pulseaudio --start --log-target=syslog
  │ │ │ ├─15345 ibus-daemon --xim --panel disable
  │ │ │ ├─15349 /usr/lib/ibus/ibus-dconf
  │ │ │ ├─15353 /usr/lib/ibus/ibus-x11 --kill-daemon
  │ │ │ ├─15417 /usr/lib/gnome-settings-daemon/gsd-power
  │ │ │ ├─15419 /usr/lib/gnome-settings-daemon/gsd-print-notifications
  │ │ │ ├─15420 /usr/lib/gnome-settings-daemon/gsd-rfkill
  │ │ │ ├─15423 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  │ │ │ ├─15425 /usr/lib/gnome-settings-daemon/gsd-sharing
  │ │ │ ├─15431 /usr/lib/gnome-settings-daemon/gsd-smartcard
  │ │ │ ├─15434 /usr/lib/gnome-settings-daemon/gsd-xsettings
  │ │ │ ├─15439 /usr/lib/gnome-settings-daemon/gsd-wacom
  │ │ │ ├─15442 /usr/lib/gnome-settings-daemon/gsd-sound
  │ │ │ ├─15452 /usr/lib/gnome-settings-daemon/gsd-clipboard
  │ │ │ ├─15454 /usr/lib/gnome-settings-daemon/gsd-a11y-settings
  │ │ │ ├─15457 /usr/lib/gnome-settings-daemon/gsd-datetime
  │ │ │ ├─15461 /usr/lib/gnome-settings-daemon/gsd-color
  │ │ │ ├─15464 /usr/lib/gnome-settings-daemon/gsd-keyboard
  │ │ │ ├─15465 /usr/lib/gnome-settings-daemon/gsd-housekeeping
  │ │ │ ├─15469 /usr/lib/gnome-settings-daemon/gsd-mouse
  │ │ │ ├─15472 /usr/lib/gnome-settings-daemon/gsd-media-keys
  │ │ │ ├─15510 diodon
  │ │ │ ├─15515 /usr/lib/gnome-disk-utility/gsd-disk-utility-notify
  │ │ │ ├─15516 
/usr/lib/i386-linux-gnu/indicator-messages/indicator-messages-service
  │ │ │ ├─15519 
/usr/lib/i386-linux-gnu/indicator-application/indicator-application-service
  │ │ │ ├─15527 /usr/lib/gnome-settings-daemon/gsd-printer
  │ │ │ ├─15531 nautilus-desktop
  │ │ │ ├─15593 /usr/lib/ibus/ibus-engine-simple
  │ │ │ ├─15711 update-notifier
  │ │ │ └─16083 /usr/lib/deja-dup/deja-dup-monitor
  │ │ └─user@200463.service
  │ │   ├─zeitgeist.service
  │ │   │ └─15551 /usr/bin/zeitgeist-daemon
  │ │   ├─gnome-terminal-server.service
  │ │   │ ├─15661 /usr/lib/gnome-terminal/gnome-terminal-server
  │ │   │ ├─15671 bash
  │ │   │ ├─15682 systemd-cgls
  │ │   │ └─15683 pager
  │ │   ├─gvfs-gphoto2-volume-monitor.service
  │ │   │ └─15400 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
  │ │   ├─zeitgeist-fts.service
  │ │   │ └─15557 /usr/lib/zeitgeist/zeitgeist/zeitgeist-fts
  │ │   ├─at-spi-dbus-bus.service
  │ │   │ ├─15267 /usr/lib/at-spi2-core/at-spi-bus-launcher
  │ │   │ ├─15277 /usr/bin/dbus-daemon 
--config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork 
--print-address 3
  │ │   │ └─15282 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
  │ │   ├─dbus.service
  │ │   │ ├─15110 /usr/bin/dbus-daemon --session --address=systemd: --nofork 
--nopidfile --systemd-activation --syslog-only
  │ │   │ ├─15298 /usr/bin/gnome-keyring-daemon --start --foreground 
--components=secrets
  │ │   │ ├─15357 /usr/lib/ibus/ibus-portal
  │ │   │ ├─15364 /usr/lib/gnome-shell/gnome-shell-calendar-server
  │ │   │ ├─15376 /usr/lib/gnome-online-accounts/goa-daemon
  │ │   │ ├─15387 /usr/lib/gnome-online-accounts/goa-identity-service
  │ │   │ └─15602 /usr/lib/dconf/dconf-service
  │ │   ├─gvfs-udisks2-volume-monitor.service
  │ │   │ └─15396 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
  │ │   ├─evolution-calendar-factory.service
  │ │   │ ├─15567 /usr/lib/evolution/evolution-calendar-factory
  │ │   │ └─15603 /usr/lib/evolution/evolution-calendar-factory-subprocess 
--f

[Touch-packages] [Bug 1794517] [NEW] Empty Display property in org.freedesktop.login1.session

[Valentyna]

Public bug reported:

In Ubuntu 18.04 when get property of Display variable using DBus
org.freedesktop.login1.session get empty value.

In Ubuntu 16.04 release these values isn`t empty and get for example
Display = :0.

I use:
Description:Ubuntu 18.04.1 LTS
Release:18.04

Package info:

Package: systemd
Version: 237-3ubuntu10.3
Priority: important
Section: admin
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian systemd Maintainers 

Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 12,9 MB
Pre-Depends: libacl1 (>= 2.2.51-8), libblkid1 (>= 2.19.1), libc6 (>= 2.27), 
libcap2 (>= 1:2.10), libcryptsetup12 (>= 2:1.4), libgcrypt20 (>= 1.8.0), 
libidn11 (>= 1.13), libip4tc0 (>= 1.6.0+snapshot20161117), liblz4-1 (>= 
0.0~r130), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2 (>= 2.3.1), 
libselinux1 (>= 2.1.9)
Depends: libapparmor1 (>= 2.9.0-3+exp2), libaudit1 (>= 1:2.2.1), 
libcryptsetup12 (>= 2:1.4.3), libgpg-error0 (>= 1.14), libkmod2 (>= 5~), 
libmount1 (>= 2.26.2), libpam0g (>= 0.99.7.1), libsystemd0 (= 237-3ubuntu10.3), 
util-linux (>= 2.27.1), mount (>= 2.26), adduser, procps
Recommends: libpam-systemd, dbus, networkd-dispatcher
Suggests: systemd-container, policykit-1
Breaks: apparmor (<< 2.9.2-1), ifupdown (<< 0.8.5~), laptop-mode-tools (<< 
1.68~), systemd-shim (<< 10-3~), udev (<< 228-5)
Replaces: udev (<< 228-5)
Homepage: https://www.freedesktop.org/wiki/Software/systemd
Task: minimal, ubuntu-core
Supported: 5y
Download-Size: 2 947 kB
APT-Manual-Installed: yes
APT-Sources: http://my.repo/ubuntu-current bionic-updates/main i386 Packages
Description: system and service manager

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

** Description changed:

  In Ubuntu 18.04 when get property of Display variable using DBus
  org.freedesktop.login1.session get empty value.
  
  In Ubuntu 16.04 release these values isn`t empty and get for example
  Display = :0.
  
  I use:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  
  Package info:
  
  Package: systemd
  Version: 237-3ubuntu10.3
  Priority: important
  Section: admin
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian systemd Maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 12,9 MB
  Pre-Depends: libacl1 (>= 2.2.51-8), libblkid1 (>= 2.19.1), libc6 (>= 2.27), 
libcap2 (>= 1:2.10), libcryptsetup12 (>= 2:1.4), libgcrypt20 (>= 1.8.0), 
libidn11 (>= 1.13), libip4tc0 (>= 1.6.0+snapshot20161117), liblz4-1 (>= 
0.0~r130), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2 (>= 2.3.1), 
libselinux1 (>= 2.1.9)
  Depends: libapparmor1 (>= 2.9.0-3+exp2), libaudit1 (>= 1:2.2.1), 
libcryptsetup12 (>= 2:1.4.3), libgpg-error0 (>= 1.14), libkmod2 (>= 5~), 
libmount1 (>= 2.26.2), libpam0g (>= 0.99.7.1), libsystemd0 (= 237-3ubuntu10.3), 
util-linux (>= 2.27.1), mount (>= 2.26), adduser, procps
  Recommends: libpam-systemd, dbus, networkd-dispatcher
  Suggests: systemd-container, policykit-1
  Breaks: apparmor (<< 2.9.2-1), ifupdown (<< 0.8.5~), laptop-mode-tools (<< 
1.68~), systemd-shim (<< 10-3~), udev (<< 228-5)
  Replaces: udev (<< 228-5)
  Homepage: https://www.freedesktop.org/wiki/Software/systemd
  Task: minimal, ubuntu-core
  Supported: 5y
  Download-Size: 2 947 kB
  APT-Manual-Installed: yes
- APT-Sources: http://archive.pls.pbank.com.ua/ubuntu-current 
bionic-updates/main i386 Packages
+ APT-Sources: http://my.repo/ubuntu-current bionic-updates/main i386 Packages
  Description: system and service manager

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

Title:
  Empty Display property in org.freedesktop.login1.session

Status in systemd package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.04 when get property of Display variable using DBus
  org.freedesktop.login1.session get empty value.

  In Ubuntu 16.04 release these values isn`t empty and get for example
  Display = :0.

  I use:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Package info:

  Package: systemd
  Version: 237-3ubuntu10.3
  Priority: important
  Section: admin
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian systemd Maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 12,9 MB
  Pre-Depends: libacl1 (>= 2.2.51-8), libblkid1 (>= 2.19.1), libc6 (>= 2.27), 
libcap2 (>= 1:2.10), libcryptsetup12 (>= 2:1.4), libgcrypt20 (>= 1.8.0), 
libidn11 (>= 1.13), libip4tc0 (>= 1.6.0+snapshot20161117), liblz4-1 (>= 
0.0~r130), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2 (>= 2.3.1), 
libselinux1 (>= 2.1.9)
  Depends: libapparmor1 (>= 2.9.0-3+exp2), libaudit1 (>= 1:2.2.1), 
libcryptsetup12 (>= 2:1.4.3), libgpg-error0 (>= 1.14), libkmod2 (>= 5~), 
libmount1 (>= 2.26.2), libpam0g (>= 0.99.7.1), libsystemd0 (= 237-3ubuntu10.3), 
util-linux (>= 2.27.1), mount (>= 2.26

[Touch-packages] [Bug 1794516] Re: systemd-logind does not track all user processes

[Launchpad Bug Tracker]

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

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

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

Title:
  systemd-logind does not track all user processes

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04(xenial) release all user processes are in session
  scope for example:

  └─user.slice
└─user-200463.slice
  ├─user@200463.service
  │ └─init.scope
  │   ├─5886 /lib/systemd/systemd --user
  │   └─5888 (sd-pam) 
  └─session-c2.scope
├─  419 bash
├─  471 mc
├─  473 bash -rcfile .bashrc
├─ 1432 bash
├─ 1455 mc
├─ 1457 bash -rcfile .bashrc
├─ 1915 /usr/sbin/sssd -D -f

  In Ubuntu 18.04 (bionic) some processes are in session scope and other
  are in user service for example:

  ├─user.slice
  │ ├─user-200463.slice
  │ │ ├─session-84.scope
  │ │ │ ├─14992 gdm-session-worker [pam/gdm-password]
  │ │ │ ├─15013 /usr/bin/gnome-keyring-daemon --daemonize --login
  │ │ │ ├─15057 /usr/lib/gdm3/gdm-x-session --run-script env 
GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
  │ │ │ ├─15059 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/200463/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  │ │ │ ├─15114 /usr/lib/gnome-session/gnome-session-binary --session=ubuntu
  │ │ │ ├─15205 /usr/bin/ssh-agent /usr/bin/im-launch env 
GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
  │ │ │ ├─15317 /usr/bin/gnome-shell
  │ │ │ ├─15326 /usr/bin/pulseaudio --start --log-target=syslog
  │ │ │ ├─15345 ibus-daemon --xim --panel disable
  │ │ │ ├─15349 /usr/lib/ibus/ibus-dconf
  │ │ │ ├─15353 /usr/lib/ibus/ibus-x11 --kill-daemon
  │ │ │ ├─15417 /usr/lib/gnome-settings-daemon/gsd-power
  │ │ │ ├─15419 /usr/lib/gnome-settings-daemon/gsd-print-notifications
  │ │ │ ├─15420 /usr/lib/gnome-settings-daemon/gsd-rfkill
  │ │ │ ├─15423 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  │ │ │ ├─15425 /usr/lib/gnome-settings-daemon/gsd-sharing
  │ │ │ ├─15431 /usr/lib/gnome-settings-daemon/gsd-smartcard
  │ │ │ ├─15434 /usr/lib/gnome-settings-daemon/gsd-xsettings
  │ │ │ ├─15439 /usr/lib/gnome-settings-daemon/gsd-wacom
  │ │ │ ├─15442 /usr/lib/gnome-settings-daemon/gsd-sound
  │ │ │ ├─15452 /usr/lib/gnome-settings-daemon/gsd-clipboard
  │ │ │ ├─15454 /usr/lib/gnome-settings-daemon/gsd-a11y-settings
  │ │ │ ├─15457 /usr/lib/gnome-settings-daemon/gsd-datetime
  │ │ │ ├─15461 /usr/lib/gnome-settings-daemon/gsd-color
  │ │ │ ├─15464 /usr/lib/gnome-settings-daemon/gsd-keyboard
  │ │ │ ├─15465 /usr/lib/gnome-settings-daemon/gsd-housekeeping
  │ │ │ ├─15469 /usr/lib/gnome-settings-daemon/gsd-mouse
  │ │ │ ├─15472 /usr/lib/gnome-settings-daemon/gsd-media-keys
  │ │ │ ├─15510 diodon
  │ │ │ ├─15515 /usr/lib/gnome-disk-utility/gsd-disk-utility-notify
  │ │ │ ├─15516 
/usr/lib/i386-linux-gnu/indicator-messages/indicator-messages-service
  │ │ │ ├─15519 
/usr/lib/i386-linux-gnu/indicator-application/indicator-application-service
  │ │ │ ├─15527 /usr/lib/gnome-settings-daemon/gsd-printer
  │ │ │ ├─15531 nautilus-desktop
  │ │ │ ├─15593 /usr/lib/ibus/ibus-engine-simple
  │ │ │ ├─15711 update-notifier
  │ │ │ └─16083 /usr/lib/deja-dup/deja-dup-monitor
  │ │ └─user@200463.service
  │ │   ├─zeitgeist.service
  │ │   │ └─15551 /usr/bin/zeitgeist-daemon
  │ │   ├─gnome-terminal-server.service
  │ │   │ ├─15661 /usr/lib/gnome-terminal/gnome-terminal-server
  │ │   │ ├─15671 bash
  │ │   │ ├─15682 systemd-cgls
  │ │   │ └─15683 pager
  │ │   ├─gvfs-gphoto2-volume-monitor.service
  │ │   │ └─15400 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
  │ │   ├─zeitgeist-fts.service
  │ │   │ └─15557 /usr/lib/zeitgeist/zeitgeist/zeitgeist-fts
  │ │   ├─at-spi-dbus-bus.service
  │ │   │ ├─15267 /usr/lib/at-spi2-core/at-spi-bus-launcher
  │ │   │ ├─15277 /usr/bin/dbus-daemon 
--config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork 
--print-address 3
  │ │   │ └─15282 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
  │ │   ├─dbus.service
  │ │   │ ├─15110 /usr/bin/dbus-daemon --session --address=systemd: --nofork 
--nopidfile --systemd-activation --syslog-only
  │ │   │ ├─15298 /usr/bin/gnome-keyring-daemon --start --foreground 
--components=secrets
  │ │   │ ├─15357 /usr/lib/ibus/ibus-portal
  │ │   │ ├─15364 /usr/lib/gnome-shell/gnome-shell-calendar-server
  │ │   │ ├─15376 /usr/lib/gnome-online-accounts/goa-daemon
  │ │   │ ├─15387 /usr/lib/gnome-online-accounts/goa-identity-service
  │ │   │ └─15602 /usr/lib/dconf/dconf-service
  │ │   ├─gvfs-udisks2-volume-monitor.service
  │ │   │ └─15396 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
  │ │   ├─evolution-calendar-factory.service
  │ │   │ ├─15567 /usr/lib/evolution/evolution-calendar-factory
  │ │   │ └─15603 /usr/lib/e

[Touch-packages] [Bug 1794516] Re: systemd-logind does not track all user processes

[Roman Shipovskij]

** Tags added: bionic

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

Title:
  systemd-logind does not track all user processes

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04(xenial) release all user processes are in session
  scope for example:

  └─user.slice
└─user-200463.slice
  ├─user@200463.service
  │ └─init.scope
  │   ├─5886 /lib/systemd/systemd --user
  │   └─5888 (sd-pam) 
  └─session-c2.scope
├─  419 bash
├─  471 mc
├─  473 bash -rcfile .bashrc
├─ 1432 bash
├─ 1455 mc
├─ 1457 bash -rcfile .bashrc
├─ 1915 /usr/sbin/sssd -D -f

  In Ubuntu 18.04 (bionic) some processes are in session scope and other
  are in user service for example:

  ├─user.slice
  │ ├─user-200463.slice
  │ │ ├─session-84.scope
  │ │ │ ├─14992 gdm-session-worker [pam/gdm-password]
  │ │ │ ├─15013 /usr/bin/gnome-keyring-daemon --daemonize --login
  │ │ │ ├─15057 /usr/lib/gdm3/gdm-x-session --run-script env 
GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
  │ │ │ ├─15059 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/200463/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  │ │ │ ├─15114 /usr/lib/gnome-session/gnome-session-binary --session=ubuntu
  │ │ │ ├─15205 /usr/bin/ssh-agent /usr/bin/im-launch env 
GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
  │ │ │ ├─15317 /usr/bin/gnome-shell
  │ │ │ ├─15326 /usr/bin/pulseaudio --start --log-target=syslog
  │ │ │ ├─15345 ibus-daemon --xim --panel disable
  │ │ │ ├─15349 /usr/lib/ibus/ibus-dconf
  │ │ │ ├─15353 /usr/lib/ibus/ibus-x11 --kill-daemon
  │ │ │ ├─15417 /usr/lib/gnome-settings-daemon/gsd-power
  │ │ │ ├─15419 /usr/lib/gnome-settings-daemon/gsd-print-notifications
  │ │ │ ├─15420 /usr/lib/gnome-settings-daemon/gsd-rfkill
  │ │ │ ├─15423 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  │ │ │ ├─15425 /usr/lib/gnome-settings-daemon/gsd-sharing
  │ │ │ ├─15431 /usr/lib/gnome-settings-daemon/gsd-smartcard
  │ │ │ ├─15434 /usr/lib/gnome-settings-daemon/gsd-xsettings
  │ │ │ ├─15439 /usr/lib/gnome-settings-daemon/gsd-wacom
  │ │ │ ├─15442 /usr/lib/gnome-settings-daemon/gsd-sound
  │ │ │ ├─15452 /usr/lib/gnome-settings-daemon/gsd-clipboard
  │ │ │ ├─15454 /usr/lib/gnome-settings-daemon/gsd-a11y-settings
  │ │ │ ├─15457 /usr/lib/gnome-settings-daemon/gsd-datetime
  │ │ │ ├─15461 /usr/lib/gnome-settings-daemon/gsd-color
  │ │ │ ├─15464 /usr/lib/gnome-settings-daemon/gsd-keyboard
  │ │ │ ├─15465 /usr/lib/gnome-settings-daemon/gsd-housekeeping
  │ │ │ ├─15469 /usr/lib/gnome-settings-daemon/gsd-mouse
  │ │ │ ├─15472 /usr/lib/gnome-settings-daemon/gsd-media-keys
  │ │ │ ├─15510 diodon
  │ │ │ ├─15515 /usr/lib/gnome-disk-utility/gsd-disk-utility-notify
  │ │ │ ├─15516 
/usr/lib/i386-linux-gnu/indicator-messages/indicator-messages-service
  │ │ │ ├─15519 
/usr/lib/i386-linux-gnu/indicator-application/indicator-application-service
  │ │ │ ├─15527 /usr/lib/gnome-settings-daemon/gsd-printer
  │ │ │ ├─15531 nautilus-desktop
  │ │ │ ├─15593 /usr/lib/ibus/ibus-engine-simple
  │ │ │ ├─15711 update-notifier
  │ │ │ └─16083 /usr/lib/deja-dup/deja-dup-monitor
  │ │ └─user@200463.service
  │ │   ├─zeitgeist.service
  │ │   │ └─15551 /usr/bin/zeitgeist-daemon
  │ │   ├─gnome-terminal-server.service
  │ │   │ ├─15661 /usr/lib/gnome-terminal/gnome-terminal-server
  │ │   │ ├─15671 bash
  │ │   │ ├─15682 systemd-cgls
  │ │   │ └─15683 pager
  │ │   ├─gvfs-gphoto2-volume-monitor.service
  │ │   │ └─15400 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
  │ │   ├─zeitgeist-fts.service
  │ │   │ └─15557 /usr/lib/zeitgeist/zeitgeist/zeitgeist-fts
  │ │   ├─at-spi-dbus-bus.service
  │ │   │ ├─15267 /usr/lib/at-spi2-core/at-spi-bus-launcher
  │ │   │ ├─15277 /usr/bin/dbus-daemon 
--config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork 
--print-address 3
  │ │   │ └─15282 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
  │ │   ├─dbus.service
  │ │   │ ├─15110 /usr/bin/dbus-daemon --session --address=systemd: --nofork 
--nopidfile --systemd-activation --syslog-only
  │ │   │ ├─15298 /usr/bin/gnome-keyring-daemon --start --foreground 
--components=secrets
  │ │   │ ├─15357 /usr/lib/ibus/ibus-portal
  │ │   │ ├─15364 /usr/lib/gnome-shell/gnome-shell-calendar-server
  │ │   │ ├─15376 /usr/lib/gnome-online-accounts/goa-daemon
  │ │   │ ├─15387 /usr/lib/gnome-online-accounts/goa-identity-service
  │ │   │ └─15602 /usr/lib/dconf/dconf-service
  │ │   ├─gvfs-udisks2-volume-monitor.service
  │ │   │ └─15396 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
  │ │   ├─evolution-calendar-factory.service
  │ │   │ ├─15567 /usr/lib/evolution/evolution-calendar-factory
  │ │   │ └─15603 /usr/lib/evolution/evolution-calendar-factory-subprocess 
--factory all --bus-name 
org.gnome.evolution.dataserver.Subproce

[Touch-packages] [Bug 1794516] [NEW] systemd-logind does not track all user processes

[Valentyna]

Public bug reported:

In Ubuntu 16.04(xenial) release all user processes are in session scope
for example:

└─user.slice
  └─user-200463.slice
├─user@200463.service
│ └─init.scope
│   ├─5886 /lib/systemd/systemd --user
│   └─5888 (sd-pam) 
└─session-c2.scope
  ├─  419 bash
  ├─  471 mc
  ├─  473 bash -rcfile .bashrc
  ├─ 1432 bash
  ├─ 1455 mc
  ├─ 1457 bash -rcfile .bashrc
  ├─ 1915 /usr/sbin/sssd -D -f

In Ubuntu 18.04 (bionic) some processes are in session scope and other
are in user service for example:

├─user.slice
│ ├─user-200463.slice
│ │ ├─session-84.scope
│ │ │ ├─14992 gdm-session-worker [pam/gdm-password]
│ │ │ ├─15013 /usr/bin/gnome-keyring-daemon --daemonize --login
│ │ │ ├─15057 /usr/lib/gdm3/gdm-x-session --run-script env 
GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
│ │ │ ├─15059 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/200463/gdm/Xauthority -background none -noreset -keeptty -verbose 3
│ │ │ ├─15114 /usr/lib/gnome-session/gnome-session-binary --session=ubuntu
│ │ │ ├─15205 /usr/bin/ssh-agent /usr/bin/im-launch env 
GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
│ │ │ ├─15317 /usr/bin/gnome-shell
│ │ │ ├─15326 /usr/bin/pulseaudio --start --log-target=syslog
│ │ │ ├─15345 ibus-daemon --xim --panel disable
│ │ │ ├─15349 /usr/lib/ibus/ibus-dconf
│ │ │ ├─15353 /usr/lib/ibus/ibus-x11 --kill-daemon
│ │ │ ├─15417 /usr/lib/gnome-settings-daemon/gsd-power
│ │ │ ├─15419 /usr/lib/gnome-settings-daemon/gsd-print-notifications
│ │ │ ├─15420 /usr/lib/gnome-settings-daemon/gsd-rfkill
│ │ │ ├─15423 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
│ │ │ ├─15425 /usr/lib/gnome-settings-daemon/gsd-sharing
│ │ │ ├─15431 /usr/lib/gnome-settings-daemon/gsd-smartcard
│ │ │ ├─15434 /usr/lib/gnome-settings-daemon/gsd-xsettings
│ │ │ ├─15439 /usr/lib/gnome-settings-daemon/gsd-wacom
│ │ │ ├─15442 /usr/lib/gnome-settings-daemon/gsd-sound
│ │ │ ├─15452 /usr/lib/gnome-settings-daemon/gsd-clipboard
│ │ │ ├─15454 /usr/lib/gnome-settings-daemon/gsd-a11y-settings
│ │ │ ├─15457 /usr/lib/gnome-settings-daemon/gsd-datetime
│ │ │ ├─15461 /usr/lib/gnome-settings-daemon/gsd-color
│ │ │ ├─15464 /usr/lib/gnome-settings-daemon/gsd-keyboard
│ │ │ ├─15465 /usr/lib/gnome-settings-daemon/gsd-housekeeping
│ │ │ ├─15469 /usr/lib/gnome-settings-daemon/gsd-mouse
│ │ │ ├─15472 /usr/lib/gnome-settings-daemon/gsd-media-keys
│ │ │ ├─15510 diodon
│ │ │ ├─15515 /usr/lib/gnome-disk-utility/gsd-disk-utility-notify
│ │ │ ├─15516 
/usr/lib/i386-linux-gnu/indicator-messages/indicator-messages-service
│ │ │ ├─15519 
/usr/lib/i386-linux-gnu/indicator-application/indicator-application-service
│ │ │ ├─15527 /usr/lib/gnome-settings-daemon/gsd-printer
│ │ │ ├─15531 nautilus-desktop
│ │ │ ├─15593 /usr/lib/ibus/ibus-engine-simple
│ │ │ ├─15711 update-notifier
│ │ │ └─16083 /usr/lib/deja-dup/deja-dup-monitor
│ │ └─user@200463.service
│ │   ├─zeitgeist.service
│ │   │ └─15551 /usr/bin/zeitgeist-daemon
│ │   ├─gnome-terminal-server.service
│ │   │ ├─15661 /usr/lib/gnome-terminal/gnome-terminal-server
│ │   │ ├─15671 bash
│ │   │ ├─15682 systemd-cgls
│ │   │ └─15683 pager
│ │   ├─gvfs-gphoto2-volume-monitor.service
│ │   │ └─15400 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
│ │   ├─zeitgeist-fts.service
│ │   │ └─15557 /usr/lib/zeitgeist/zeitgeist/zeitgeist-fts
│ │   ├─at-spi-dbus-bus.service
│ │   │ ├─15267 /usr/lib/at-spi2-core/at-spi-bus-launcher
│ │   │ ├─15277 /usr/bin/dbus-daemon 
--config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork 
--print-address 3
│ │   │ └─15282 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
│ │   ├─dbus.service
│ │   │ ├─15110 /usr/bin/dbus-daemon --session --address=systemd: --nofork 
--nopidfile --systemd-activation --syslog-only
│ │   │ ├─15298 /usr/bin/gnome-keyring-daemon --start --foreground 
--components=secrets
│ │   │ ├─15357 /usr/lib/ibus/ibus-portal
│ │   │ ├─15364 /usr/lib/gnome-shell/gnome-shell-calendar-server
│ │   │ ├─15376 /usr/lib/gnome-online-accounts/goa-daemon
│ │   │ ├─15387 /usr/lib/gnome-online-accounts/goa-identity-service
│ │   │ └─15602 /usr/lib/dconf/dconf-service
│ │   ├─gvfs-udisks2-volume-monitor.service
│ │   │ └─15396 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
│ │   ├─evolution-calendar-factory.service
│ │   │ ├─15567 /usr/lib/evolution/evolution-calendar-factory
│ │   │ └─15603 /usr/lib/evolution/evolution-calendar-factory-subprocess 
--factory all --bus-name 
org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx15567x2 --own-path 
/org/gnome/evolution/dataserver/Subprocess/Backend/Cal
│ │   ├─evolution-source-registry.service
│ │   │ └─15368 /usr/lib/evolution/evolution-source-registry
│ │   ├─gvfs-metadata.service
│ │   │ └─15643 /usr/lib/gvfs/gvfsd-metadata
│ │   ├─gvfs-mtp-volume-monitor.service
│ │   │ └─15404 /usr/lib/gvfs/gvfs-mtp-volume-monitor
│ │   ├─gvfs-goa-volume-monitor.service
│ │   │ └─15413 /usr/lib/gvfs/gvfs-goa-volume-monitor
│ │   ├─gvfs-afc-vol

[Touch-packages] [Bug 1793092] Re: [FFe] openssl 1.1.1

[Dimitri John Ledkov]

ruby2.5 ruby-openssl python3.7 correctly gain stronger dep on libssl1.1
>= 1.1.1.

python2.7 and python3.6 still need more patches to pick up
https://bugs.python.org/issue34670

** No longer affects: ruby2.5 (Ubuntu)

** No longer affects: python3.7 (Ubuntu)

** Bug watch added: Python Roundup #34670
   http://bugs.python.org/issue34670

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

Title:
  [FFe] openssl 1.1.1

Status in openssl package in Ubuntu:
  Confirmed
Status in python2.7 package in Ubuntu:
  New
Status in python3.6 package in Ubuntu:
  New

Bug description:
  Merge openssl 1.1.1 from debian unstable.

  OpenSSL 1.1.1 is now out, with TLS1.3 support, and is the new upstream
  LTS release.

  Resulting in the following changes in Ubuntu:

  - openssl moves from 1.1.0 series to 1.1.1 LTS series

  - TLS1.3 is enabled, and used by default, when possible. Major
  feature.

  - All existing delta, and minimally accepted key sizes, and minimally
  accepted protocol versions remain the same.

  Proposed package is in
  https://launchpad.net/~xnox/+archive/ubuntu/openssl with a rebuild of
  all the reverse dependencies. It demonstrates that openssl compiled as
  above is more compatible and has less issues than debian config. There
  are a few FTBFS, which are also present in cosmic-release; there are
  some test-suite expectations mismatch (connectivity succeeds with
  tls1.3 even though lower/different algos are expected); there are very
  little connectivity tests thus connectivity interop are the biggest
  issues which will be unavoidable with introducing 1.3.

  ===

  Ubuntu delta summary versus debian unstable in this merge:
  - Replace duplicate files in the doc directory with symlinks.
  - debian/libssl1.1.postinst:
    + Display a system restart required notification on libssl1.1
  upgrade on servers.
    + Use a different priority for libssl1.1/restart-services depending
  on whether a desktop, or server dist-upgrade is being performed.
  - Revert "Enable system default config to enforce TLS1.2 as a
    minimum" & "Increase default security level from 1 to 2".
  - Further decrease security level from 1 to 0, for compatibility with
    openssl 1.0.2.

  These mitigate most of the runtime incompatibilities, and ensure
  client<->server compatibility between 1.1.1, 1.1.0, and 1.0.2 series
  and thus one can continue to mix & match xenial/bionic/cosmic
  releases.

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

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

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

[ Christian Ehrhardt ]

Summarizing the Server Team related task status for a better overview.

For postfix a discussion existed, and they seem not to have any better tracker 
set up.
For the others I reported new issues upstream, so that they are aware and we 
have something to track.
I listed those new ones after "---".


Ready Packages since Bug/Commit:
haproxy: 
https://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=f2592b29f13907ddf2bba42d00bc41cb8ee5b69b
php7.3: 
https://salsa.debian.org/php-team/php/commit/fbe3eb003c4bc3d81414880b923e276c9b7acb56

Open Upstream Bugs:
apache2: https://bz.apache.org/bugzilla/show_bug.cgi?id=57471
exim4: https://bugs.exim.org/show_bug.cgi?id=1878
nginx: https://trac.nginx.org/nginx/ticket/720
sssd: https://pagure.io/SSSD/sssd/issue/3833
---
postfix: 
http://postfix.1071664.n5.nabble.com/Plans-for-using-PCRE-v2-in-Postfix-td83200.html
nmap: https://github.com/nmap/nmap/issues/1335
freeradius: https://github.com/FreeRADIUS/freeradius-server/issues/2315
quagga: https://bugzilla.quagga.net/show_bug.cgi?id=997

** Bug watch added: bz.apache.org/bugzilla/ #57471
   https://bz.apache.org/bugzilla/show_bug.cgi?id=57471

** Bug watch added: github.com/nmap/nmap/issues #1335
   https://github.com/nmap/nmap/issues/1335

** Bug watch added: github.com/FreeRADIUS/freeradius-server/issues #2315
   https://github.com/FreeRADIUS/freeradius-server/issues/2315

** Bug watch added: Quagga Bugzilla #997
   http://bugzilla.quagga.net/show_bug.cgi?id=997

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Triaged
Status in libpam-mount package in Ubuntu:
  Incomplete
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in php7.3 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Incomplete
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in wget package in Ubuntu:
  Incomplete
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

[ Christian Ehrhardt ]

** Summary changed:

- demotion of pcre3 in favor of pcre2
+ demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

** Also affects: php7.3 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: php7.3 (Ubuntu)
   Status: New => Triaged

** Changed in: php7.2 (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Triaged
Status in libpam-mount package in Ubuntu:
  Incomplete
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in php7.3 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Incomplete
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in wget package in Ubuntu:
  Incomplete
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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

[Touch-packages] [Bug 1746856] Re: usb printer does not print (canon d530)

[gf]

That's wonderful, Alex!
Have a great day!
:)
G

Closed per reporter's feedback.

** Changed in: cups (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  usb printer does not print (canon d530)

Status in cups package in Ubuntu:
  Invalid

Bug description:
  Bus 002 Device 005: ID 04a9:2775 Canon, Inc. 
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 04f2:b217 Chicony Electronics Co., Ltd Lenovo 
Integrated Camera (0.3MP)
  Bus 001 Device 004: ID 1267:0201 Logic3 / SpectraVideo plc A4Tech SWOP-3 Mouse
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Description:  Ubuntu 17.10
  Release:  17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: cups 2.2.4-7ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 19:14:46 2018
  InstallationDate: Installed on 2018-01-22 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lpstat: device for Canon_D530_D560: cnusb:/dev/usb/lp0
  MachineType: LENOVO 4239CTO
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Canon_D530_D560.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Canon_D530_D560.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=1aa4feb1-4b49-43d5-bcce-25b90425a69e ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET58WW (1.38 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4239CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET58WW(1.38):bd07/05/2012:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T520
  dmi.product.name: 4239CTO
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1793222] Re: Mousepad doesn't take input after canceled save dialog

[Theo Linkspfeifer]

I have tried to reproduce it in the live session of Xubuntu 18.04.1 and
18.10 (dev release), but I did not encounter the issue.

Maybe there is another component interfering, or some setting needs to
be changed to trigger the bug.

** Package changed: mousepad (Ubuntu) => ibus (Ubuntu)

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

Title:
  Mousepad doesn't take input after canceled save dialog

Status in ibus package in Ubuntu:
  New

Bug description:
  1 Open Mousepad
  2 Write something
  3 Ctrl+S for save 
 -> dialog opens 
  4 Exit dialog with ESC 
 -> Mousepad will not take any keyboard input anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mousepad 0.4.0-4ubuntu1
  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: XFCE
  Date: Wed Sep 19 07:17:27 2018
  InstallationDate: Installed on 2018-02-12 (218 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: mousepad
  UpgradeStatus: Upgraded to bionic on 2018-08-25 (24 days ago)

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

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

[Touch-packages] [Bug 1786644] Re: package rsyslog-mysql 8.32.0-1ubuntu4 failed to install/upgrade: installed rsyslog-mysql 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: rsyslog (Ubuntu)
   Status: New => Confirmed

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

Title:
  package rsyslog-mysql 8.32.0-1ubuntu4 failed to install/upgrade:
  installed rsyslog-mysql package post-installation script subprocess
  returned error exit status 1

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  Update failed

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: rsyslog-mysql 8.32.0-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Aug 12 01:05:33 2018
  ErrorMessage: installed rsyslog-mysql package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-08-05 (736 days ago)
  InstallationMedia: Ubuntu 16.04 LTS (Finnish Remix) "Xenial Xerus" - Release 
amd64 (20160420.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, 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
   apt  1.6.3
  SourcePackage: rsyslog
  Title: package rsyslog-mysql 8.32.0-1ubuntu4 failed to install/upgrade: 
installed rsyslog-mysql package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1793222] [NEW] Mousepad doesn't take input after canceled save dialog

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

1 Open Mousepad
2 Write something
3 Ctrl+S for save 
   -> dialog opens 
4 Exit dialog with ESC 
   -> Mousepad will not take any keyboard input anymore.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: mousepad 0.4.0-4ubuntu1
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: XFCE
Date: Wed Sep 19 07:17:27 2018
InstallationDate: Installed on 2018-02-12 (218 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: mousepad
UpgradeStatus: Upgraded to bionic on 2018-08-25 (24 days ago)

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


** Tags: amd64 apport-bug bionic
-- 
Mousepad doesn't take input after canceled save dialog
https://bugs.launchpad.net/bugs/1793222
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ibus 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 1794485] [NEW] diagnostics performed on 26. sept2018

[Radmila]

Public bug reported:

Computer could not boot from Windows

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-34-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: Wed Sep 26 12:15:30 2018
DistUpgraded: 2018-09-25 15:02:59,416 ERROR Cache can not be locked (E:Could 
not get lock //var/lib/dpkg/lock - open (11: Resource temporarily unavailable), 
E:Unable to lock the administration directory (//var/lib/dpkg/), is another 
process using it?)
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Technology Solutions 2nd Generation Core Processor Family 
Integrated Graphics Controller [1734:11b9]
InstallationDate: Installed on 2018-09-25 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: FUJITSU ESPRIMO P400
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=b4e9e30a-9f16-4900-a101-c4095de6a434 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2018-09-25 (0 days ago)
dmi.bios.date: 04/02/2012
dmi.bios.vendor: FUJITSU // American Megatrends Inc.
dmi.bios.version: V4.6.4.0 R1.10.0 for D2990-A1x
dmi.board.name: D2990-A1
dmi.board.vendor: FUJITSU
dmi.board.version: S26361-D2990-A1
dmi.chassis.type: 6
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: C$PHW1
dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.4.0R1.10.0forD2990-A1x:bd04/02/2012:svnFUJITSU:pnESPRIMOP400:pvr:rvnFUJITSU:rnD2990-A1:rvrS26361-D2990-A1:cvnFUJITSU:ct6:cvrC$PHW1:
dmi.product.name: ESPRIMO P400
dmi.sys.vendor: FUJITSU
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: Tue Sep 25 15:13:12 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputPIXART USB OPTICAL MOUSE MOUSE, id 8
 input  USB Keyboard   KEYBOARD, id 9
 input  USB Keyboard   KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  diagnostics performed on 26. sept2018

Status in xorg package in Ubuntu:
  New

Bug description:
  Computer could not boot from Windows

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-34-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: Wed Sep 26 12:15:30 2018
  DistUpgraded: 2018-09-25 15:02:59,416 ERROR Cache can not be locked (E:Could 
not get lock //var/lib/dpkg/lock - open (11: Resource temporarily unavailable), 
E:Unable to lock the administration directory (//var/lib/dpkg/), is another 
process using it?)
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Technology Solutions 2nd Generation Core Processor 
Family Integrated Graphics Controller [1734:11b9]
  InstallationDate: Installed on 2018-09-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus

[Touch-packages] [Bug 1792644] Re: If snapd is not working it can take down systemd

[Dimitri John Ledkov]

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

yeah, there is/was a bug in both systemd and snapd w.r.t. injecting
:/snap/bin. I believe it is fixed in cosmic already, and bionic should
be fixed soon too. I will mark this report as a duplicate.

** This bug has been marked a duplicate of bug 1771858
   /snap/bin not in default PATH for units, snapd should ship 
system-environment-generators to inject /snap/bin into $PATH

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

Title:
  If snapd is not working it can take down systemd

Status in systemd package in Ubuntu:
  New

Bug description:
  I'll start out with saying, this bug is probably priority "invalid"
  due to my non-stock configuration (this 18.04.1 install is on an Acer
  Chromebook 13, so it has a held back kernel and Xorg for the lovely
  nvidia drivers it came with.) But I figure I'll file anyway since the
  problem is rather serious if it arises on your particular system, and
  the workaround/fix is easy once you figure out what the heck is
  happening.

  So, snapd has errored out since I updated to 18.04 due to my held back
  kernel (snap packages are using xz compression, and this kernel has no
  xz support...)  I found within the last day or so that my machine
  would not boot to graphical environment, just to text login with no
  networking up and several missing services (ntp and a few others.)
  journalctl -xe showed failures due to "file not found" on files like
  tr, cut, modprobe, cat, that should definitely be found.  PATH
  problems!  Ultimately, I found /usr/lib/systemd/system-environment-
  generators/snapd-env-generator (which appears -- not sure since it's a
  binary instead of a shell script -- to be intended to just add
  "/snap/bin" to the PATH.)I moved this out of the folder, on reboot
  everything worked fine. Then I went ahead and uninstalled snapd.

  I suspect systemd is "too smart for it's own good", and instead of
  providing it's own environment variables then letting items in
  /usr/lib/systemd/system-environment-generators/ modify the environment
  (as docs say), instead systemd either decided "snapd-env-generator" is
  setting a PATH so systemd doesn't have to (resulting in PATH of
  ":/snap/bin") or systemd "rolled back" that PATH when snapd service
  failed, resetting PATH to empty instead of the default PATH value.

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

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

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

[Dimitri John Ledkov]

Using this bug to fix systemd exported environment to the generators.

** Changed in: systemd (Ubuntu Cosmic)
   Status: Won't Fix => Fix Committed

** Changed in: systemd (Ubuntu Bionic)
   Status: Won't Fix => Confirmed

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed
Status in snapd source package in Cosmic:
  Confirmed
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).

  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.

  E.g.:

  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd

  Something similar can be done for user-environment-generators too.
  Note that user-environment-generators can generate unique variables
  per user.

  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.

  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.

  [Testcase]

  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

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

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

[Touch-packages] [Bug 1794476] [NEW] curl-config uses krb5-config, but libcurl4-openssl-dev only Suggests libkrb5-dev

[Mekk]

Public bug reported:

Attempt to run curl-config on the system, on which libkrb5-dev is not
installed, results in error

   /usr/bin/curl-config: krb5-config: not found

At the same time, libcurl4-openssl-dev only Suggests libkrb5-dev.

Either curl-config should gracefully handle lack of krb5-config, or the
dependency should be stronger.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libcurl4-openssl-dev 7.58.0-2ubuntu3.3
ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18
Uname: Linux 4.15.0-33-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Sep 26 11:25:10 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-02-18 (2046 days ago)
InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.3)
SourcePackage: curl
UpgradeStatus: Upgraded to bionic on 2018-04-11 (168 days ago)

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


** Tags: amd64 apport-bug bionic curl dependency

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

Title:
  curl-config uses krb5-config, but libcurl4-openssl-dev only Suggests
  libkrb5-dev

Status in curl package in Ubuntu:
  New

Bug description:
  Attempt to run curl-config on the system, on which libkrb5-dev is not
  installed, results in error

 /usr/bin/curl-config: krb5-config: not found

  At the same time, libcurl4-openssl-dev only Suggests libkrb5-dev.

  Either curl-config should gracefully handle lack of krb5-config, or
  the dependency should be stronger.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libcurl4-openssl-dev 7.58.0-2ubuntu3.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18
  Uname: Linux 4.15.0-33-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Sep 26 11:25:10 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-02-18 (2046 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  SourcePackage: curl
  UpgradeStatus: Upgraded to bionic on 2018-04-11 (168 days ago)

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

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

[Touch-packages] [Bug 1794473] [NEW] ubuntu18.04 no sound after disconnect from television

[widon1104]

Public bug reported:

I use hdmi connect to my television and set sound output device to: HDMI XXX.
After I disconnect from my television, the ubuntu system will have no sound.

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

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

Title:
  ubuntu18.04 no sound after disconnect from television

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I use hdmi connect to my television and set sound output device to: HDMI XXX.
  After I disconnect from my television, the ubuntu system will have no sound.

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

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

[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

[Tim Edwards]

Fixed for me, I didn't do anything different or change anything, I guess
one of the Ubuntu updates must've fixed it

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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

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

[Touch-packages] [Bug 1794178] Re: Install failure

[Juhani Numminen]

This does not seem to be a problem in the libxext package. The error
message indicates that apt-get failed to download the file from a mirror
server "xxx.xxx.xxx.xxx". Please report the problem to the administrator
of "xxx.xxx.xxx.xxx". You can try to use an official Ubuntu archive
mirror to see if that solves the problem.

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

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

Title:
  Install failure

Status in libxext package in Ubuntu:
  Invalid

Bug description:
  apt-get install libxext6
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following package was automatically installed and is no longer required:
libxmuu1
  Use 'apt autoremove' to remove it.
  The following NEW packages will be installed:
libxext6
  0 upgraded, 1 newly installed, 0 to remove and 27 not upgraded.
  Need to get 29.4 kB of archives.
  After this operation, 125 kB of additional disk space will be used.
  Err:1 
http://xxx.xxx.xxx.xxx:80/data/040d470b23b0f368/archive.ubuntu.com/ubuntu 
xenial/main amd64 libxext6 amd64 2:1.3.3-1
Unknown date format Bad header data
  E: Failed to fetch 
http://xxx.xxx.xxx.xxx:80/data/040d470b23b0f368/archive.ubuntu.com/ubuntu/pool/main/libx/libxext/libxext6_1.3.3-1_amd64.deb
  Unknown date format Bad header data

  E: Unable to fetch some archives, maybe run apt-get update or try with
  --fix-missing?

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

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