[Touch-packages] [Bug 1753532] [NEW] apt-get update doesn't get new packages

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

apt-get update and upgrade do not upgrade the system
 
--Steps to Reproduce---
 apt-get update and apt-get upgrade.  It shows nothing to upgrade. But the 
kernel level is in an old version. 
 
New kernel packages are not shown in apt-cache. Somehow, the new packages are 
not being got from repo server when do apt-get update.

Executed on 16.04.3

Btw, not all the Ubuntu servers have that issues. I crossed check the
sources.list among the servers, there is no difference. So don't know
what caused some of them cannot get any update from ubuntu repo.
However, I can install individual packages via apt-get install command.

There is not any error during the apt-get update && apt-get upgrade. It
showed nothing to upgrade.

Hit:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease
Hit:2 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease
Hit:3 http://ports.ubuntu.com/ubuntu-ports xenial-backports InRelease
Hit:4 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

The servers were able to manually upgrade for a long time. But all the
sudden, they are not upgradable. It looks it can not retrieve new kernel
level packages during the apt-get update. The highest kernel level can
be installed is 4.4.0-97.. not more higher..


HWS: I mirrored this problem description, to be able to get support for
getting this fixed. Even it seems to be an environment problem. But
direct Q will probably help

** Affects: apt (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-164567 severity-high 
targetmilestone-inin---
-- 
apt-get update doesn't get new packages
https://bugs.launchpad.net/bugs/1753532
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apt 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 1747744] Re: [regression] Video playback in totem is corrupted in X11

[Daniel van Vugt]

** No longer affects: totem (Ubuntu)

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

Title:
  [regression] Video playback in totem is corrupted in X11

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  WORKAROUND (1):

  Install these two together:
  
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu2/+build/13697262/+files/libgl1-mesa-glx_17.2.4-0ubuntu2_amd64.deb
  
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu2/+build/13697262/+files/libglapi-mesa_17.2.4-0ubuntu2_amd64.deb

  WORKAROUND (2):

  sudo apt remove gstreamer1.0-vaapi

  WORKAROUND (3):

  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---

  Test case
  Log inti xorg session
  Install gstreamer1.0-vaapi plugin
  Play a supported video (- h.264/avc in .mp4, .mkv or .mov  would suffice

  Expected: hardware decoded playback
  What happens: totally corrupted screen, see screenshots

  Does work ok in a wayland session

  $ vainfo
  libva info: VA-API version 1.0.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.0 (libva 2.0.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Simple:   VAEntrypointEncSlice
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointEncSlice
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileH264MultiviewHigh  :   VAEntrypointVLD
    VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
    VAProfileH264StereoHigh :   VAEntrypointVLD
    VAProfileH264StereoHigh :   VAEntrypointEncSlice
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc
    VAProfileJPEGBaseline   :   VAEntrypointVLD

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 14:43:57 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer-vaapi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1753663] Re: No 3D acceleration, using llvmpipe

[Daniel van Vugt]

Can you tell us what nvidia package you have installed?

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

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

** Summary changed:

- No 3D acceleration, using llvmpipe
+ [Mesa 18.0] No 3D acceleration, using llvmpipe

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

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

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

Title:
  [Mesa 18.0] No 3D acceleration, using llvmpipe

Status in libglvnd package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  As requested in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I
  fill a new bug.

  Even after getting the fixed packages in
  https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get
  no 3D acceleration. Seems to be some mixup with nvidia drivers.

  $glxinfo
  ...
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: VMware, Inc. (0x)
  Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
  Version: 18.0.0
  Accelerated: no
  Video memory: 15963MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 3.3
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.0
  ...

  $ vdpauinfo
  display: :1 screen: 0
  Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object 
file: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: MATE
  Date: Tue Mar  6 08:00:28 2018
  DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed
   ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed
   r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed
   tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA 
controller])
     Subsystem: Intel Corporation HD Graphics 5500 [8086:1616]
  MachineType: www.51nb.com X62
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago)
  dmi.bios.date: 12/10/2016
  dmi.bios.vendor: 51NB
  dmi.bios.version: 5.011
  dmi.board.asset.tag: X62
  dmi.board.name: CRESCENTBAY
  dmi.board.vendor: INTEL Corporation
  dmi.board.version: X62.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: X62
  dmi.product.name: X62
  dmi.product.version: V10
  dmi.sys.vendor: www.51nb.com
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1751225] Re: apt update hangs when repository url is redirect url

[Seyeong Kim]

Hello Julian, no news for this?

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

Title:
  apt update hangs when repository url is redirect url

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Artful:
  Invalid

Bug description:
  [Impact]

  When using redirect url on /etc/apt/sources.list

  apt update command hangs

  this is affected with commit
  
https://anonscm.debian.org/git/apt/apt.git/commit/?id=dd547ebaffd2aceb42e2908f1d5f0ab386af6cb1

  In my test, moving below[1] code after[2]

  [1]
  ###
  if (ContentLength == 0)
  return true;
  ###
  [2]
  if (Encoding == Closes)
  Encoding = Stream;

  ###

  it worked fine.

  [Test Case]

  echo "deb http://packages.cloudfoundry.org/debian stable main" >
  /etc/apt/sources.list.d/cloudfoundry-cli.list

  apt update

  [Regression]
  TBD

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

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

[Touch-packages] [Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1

[Michael]

Thanks, done as in
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1753663.

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

Title:
  [regression] Missing Wayland login option and missing GL acceleration,
  after installing libegl1

Status in libglvnd package in Ubuntu:
  Fix Released
Status in mesa-demos package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  I just updated bionic and suddenly:
    * No 'Ubuntu on Wayland' login option.
    * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe 
(software rendering)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Feb 24 13:59:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-12 (73 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1753663] [NEW] No 3D acceleration, using llvmpipe

[Michael]

Public bug reported:

As requested in
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I fill
a new bug.

Even after getting the fixed packages in
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get
no 3D acceleration. Seems to be some mixup with nvidia drivers.

$glxinfo
...
Extended renderer info (GLX_MESA_query_renderer):
Vendor: VMware, Inc. (0x)
Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
Version: 18.0.0
Accelerated: no
Video memory: 15963MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 3.3
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0
...

$ vdpauinfo
display: :1 screen: 0
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object 
file: No such file or directory

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
.tmp.unity_support_test.1:

ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,imgpng,snap,mousepoll,commands,imgjpeg,workarounds,wall,imgsvg,resize,place,neg,grid,scale,regex,text,shelf,expo,move,gnomecompat,annotate,session,notification,resizeinfo,ezoom,staticswitcher,bench]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: MATE
Date: Tue Mar  6 08:00:28 2018
DistUpgraded: 2018-03-03 08:30:16,182 DEBUG /openCache(), new cache size 86475
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 fwts-efi-runtime-dkms, 18.02.00, 4.15.0-10-generic, x86_64: installed
 ndiswrapper, 1.60, 4.15.0-10-generic, x86_64: installed
 r8168, 8.045.08, 4.15.0-10-generic, x86_64: installed
 tp_smapi, 0.42, 4.15.0-10-generic, x86_64: installed
 virtualbox, 5.2.8, 4.15.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 08) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation HD Graphics 5500 [8086:1616]
MachineType: www.51nb.com X62
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=df422beb-6d13-4575-9b30-ad00e25a7d35 ro noquiet nosplash
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-03-03 (2 days ago)
dmi.bios.date: 12/10/2016
dmi.bios.vendor: 51NB
dmi.bios.version: 5.011
dmi.board.asset.tag: X62
dmi.board.name: CRESCENTBAY
dmi.board.vendor: INTEL Corporation
dmi.board.version: X62.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvn51NB:bvr5.011:bd12/10/2016:svnwww.51nb.com:pnX62:pvrV10:rvnINTELCorporation:rnCRESCENTBAY:rvrX62.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
dmi.product.family: X62
dmi.product.name: X62
dmi.product.version: V10
dmi.sys.vendor: www.51nb.com
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic compiz-0.9 performance ubuntu

** Description changed:

- As requested in #1751414, I fill a new bug.
+ As requested in
+ https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I fill
+ a new bug.
  
- Even after getting the fixed packages in #1751414, I get no 3D
- acceleration. Seems to be some mixup with nvidia drivers.
- 
+ Even after getting the fixed packages in
+ https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414, I get
+ no 3D acceleration. Seems to be some mixup with nvidia drivers.
  
  $glxinfo
  ...
  Extended renderer info (GLX_MESA_query_renderer):
- Vendor: VMware, Inc. (0x)
- Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
- Version: 18.0.0
- Accelerated: no
- Video memory: 15963MB
- Unified memory: no
- Preferred profile: core (0x1)
- Max core profile version: 3.3
- Max compat profile version: 3.0
- Max GLES1 profile version: 1.1
- Max GLES[23] profile version: 3.0
+ Vendor: VMware, Inc. (0x)
+ Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
+ Version: 18.0.0
+ Accelerated: no
+ Video memory: 15963MB
+ Unified memory: no
+ Preferred profile: core (0x1)
+ Max core profile version: 3.3
+ Max compat profile version: 3.0
+ Max 

[Touch-packages] [Bug 1746579] Re: A boxes instead of a Cyrillic chars in VTs

[Evgeniy Yanyuk]

I'll try to experiment on several hosts, when I have free time. Maybe,
at the weekend.

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

Title:
  A boxes instead of a Cyrillic chars in VTs

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  $ apt-cache policy keyboard-configuration
  keyboard-configuration:
Встановлено: 1.166ubuntu7
Кандидат:1.166ubuntu7
Таблиця версій:
   *** 1.166ubuntu7 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  I expected to have cyrillic fonts in any of six VTs, /dev/tty[1-6],
  but it shows boxes instead of them. Please, see screen shot in
  attachment.

  It's very likely that this is an old bug that was fixed earlier but it
  appeared it 18.04 dev again. Here it is:
  https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1565542

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: console-setup 1.166ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Jan 31 20:46:57 2018
  InstallationDate: Installed on 2018-01-12 (19 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180103)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: console-setup
  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/1746579/+subscriptions

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

[Touch-packages] [Bug 1752123] Re: Force 8bit RGB config

[Daniel van Vugt]

Any chance we could fix the aforementioned tests?

I've got 10-bit monitors I've been waiting to use with deep colour for
years. It would be nice if we could make it work now Mesa 18 is ready.

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

Title:
  Force 8bit RGB config

Status in cogl package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  New mesa supports 10bit RGB configs, and this causes issues with
  cogl/mutter which get a random EGLConfig that breaks some
  autopkgtests. To fix this this merge request is needed for mutter

  https://gitlab.gnome.org/GNOME/mutter/merge_requests/36

  and a similar one for cogl.

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

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

[Touch-packages] [Bug 1753658] Re: Xorg crash

[Daniel van Vugt]

To diagnose this problem we still need a crash file. Please:

1. Apply the workaround from bug 994921.
2. Reboot and reproduce the crash.
3. Look in /var/crash for new crash files.
4. Run:  ubuntu-bug /var/crash/YOURFILE.crash
5. Add a comment in this bug telling is the ID of the newly-created bug.

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

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

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

Title:
  Xorg crash

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Each time I turn my screen off I get logged out of my session. I have
  to log in again and all my apps have been forcefully closed (Chrome
  mentions it didn't close cleanly and offers me to restore my tabs, for
  example).

  This happens after 5 minutes of inactivity (I have the setting for
  screen off at 5 minutes) and also when I turn off my screen by myself.

  Some more info:

  $ lsb_release -rd 
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy xorg 
  xorg:
Installed: 1:7.7+19ubuntu3
Candidate: 1:7.7+19ubuntu3
Version table:
   *** 1:7.7+19ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  5 21:57:53 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 480 [1002:0b37]
  MachineType: MSI MS-7850
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/system-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85-G41 PC Mate(MS-7850)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd07/17/2014:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7850
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1752681] Re: wireless disconnect

[mahmood]

@Marco,
I also have disabled IPV6 but still the same thing happens. Many users reported 
that problem and I see many post for older ubuntu versions. That is a very 
annoying bug.

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

Title:
  wireless disconnect

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  There are many problems reported about random and quick
  disconnect/reconnect of the wireless connection in ubuntu. Some say,
  disabling the ipv6 is the solution but it isn't!

  I really do want to find a way to debug what happens that the wireless
  connection drops randomly. But I couldn't find a tool for that.

  The output of the following commands are attached:
  uname -a
  ifconfig
  cat /proc/sys/net/ipv6/conf/all/disable_ipv6
  iwconfig
  lsmod
  dmesg

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

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

[Touch-packages] [Bug 1753576] Re: GDM freeze

[Daniel van Vugt]

Nish,

To figure the problem out you will need to be logged in already while
it's happening(!), so..

1. Log into a VT (Ctrl+Alt+F4) or install openssh-server and log in from a 
separate machine.
2. Run 'top' to find the ID of the spinning process.
3. Run:
   kill -ABRT 
4. Wait a while for crash files to be written.
5. Look in /var/crash for crash files and run:
   ubuntu-bug /var/crash/YOURFILE.crash
6. Add a comment here telling us the ID of the new bug.

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

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

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

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

[Touch-packages] [Bug 1753576] Re: GDM freeze

[Daniel van Vugt]

dino99,

Given the large number of bugs we're dealing with it would be safer for
you to log your own bug. Often two people with similar symptoms turn out
to have different bugs.

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

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

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

[Touch-packages] [Bug 1753658] [NEW] Xorg crash

[dwilches]

Public bug reported:

Each time I turn my screen off I get logged out of my session. I have to
log in again and all my apps have been forcefully closed (Chrome
mentions it didn't close cleanly and offers me to restore my tabs, for
example).

This happens after 5 minutes of inactivity (I have the setting for
screen off at 5 minutes) and also when I turn off my screen by myself.

Some more info:

$ lsb_release -rd 
Description:Ubuntu 17.10
Release:17.10

$ apt-cache policy xorg 
xorg:
  Installed: 1:7.7+19ubuntu3
  Candidate: 1:7.7+19ubuntu3
  Version table:
 *** 1:7.7+19ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar  5 21:57:53 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 480 [1002:0b37]
MachineType: MSI MS-7850
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/system-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/17/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.8
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B85-G41 PC Mate(MS-7850)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd07/17/2014:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7850
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful crash ubuntu wayland-session

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  Each time I turn my screen off I get logged out of my session. I have
  to log in again and all my apps have been forcefully closed (Chrome
  mentions it didn't close cleanly and offers me to restore my tabs, for
  example).

  This happens after 5 minutes of inactivity (I have the setting for
  screen off at 5 minutes) and also when I turn off my screen by myself.

  Some more info:

  $ lsb_release -rd 
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy xorg 
  xorg:
Installed: 1:7.7+19ubuntu3
Candidate: 1:7.7+19ubuntu3
Version table:
   *** 1:7.7+19ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  5 21:57:53 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 480 [1002:0b37]
  MachineType: MSI MS-7850
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 

[Touch-packages] [Bug 1753576] Re: GDM freeze

[Nish Aravamudan]

But if I plug in my usb-c dongle, it immediately freezes and the fans
start to spin. Unplugging the dongle has no effect. Suggestions for
debugging?

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

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

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

[Touch-packages] [Bug 1753576] Re: GDM freeze

[Nish Aravamudan]

I just rebooted again and without hitting any keys, it did come up to
the greeter without issue.

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

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

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

[Touch-packages] [Bug 1753576] Re: GDM freeze

[dino99]

Also now get a 'smooth' freeze (kind of race, as the hdd is heavily used
before getting the login screen. But booting with 'plymooth:debug'
kernel option, journalctl has logged:

***
Mar 06 04:19:47 ubuntu plymouth[660]: [./ply-boot-client.c:183] 
  ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: 
Connection refused
Mar 06 04:19:47 ubuntu plymouth[660]: [./ply-boot-client.c:184] 
  ply_boot_client_connect:trying old fallback path /ply-boot-protocol
Mar 06 04:19:47 ubuntu plymouth[660]: [./ply-boot-client.c:190] 
  ply_boot_client_connect:could not connect to /ply-boot-protocol: 
Connection refused
Mar 06 04:19:47 ubuntu plymouth[660]: [./plymouth.c:1121]   
   main:daemon not running
Mar 06 04:19:47 ubuntu plymouth[660]: [./ply-boot-client.c:810]
ply_boot_client_detach_from_event_loop:detaching from event loop
Mar 06 04:19:56 ubuntu plymouth[1011]: [./ply-boot-client.c:183]
   ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: 
Connection refused
Mar 06 04:19:56 ubuntu plymouth[1011]: [./ply-boot-client.c:184]
   ply_boot_client_connect:trying old fallback path /ply-boot-protocol
Mar 06 04:19:56 ubuntu plymouth[1011]: [./ply-boot-client.c:190]
   ply_boot_client_connect:could not connect to /ply-boot-protocol: 
Connection refused
Mar 06 04:19:56 ubuntu plymouth[1011]: [./plymouth.c:1121]  
main:daemon not running
Mar 06 04:19:56 ubuntu plymouth[1011]: [./plymouth.c:1132]  
main:no need to wait
Mar 06 04:19:56 ubuntu gdm3[1016]: [./ply-boot-client.c:183]
   ply_boot_client_connect:could not connect to /org/freedesktop/plymouthd: 
Connection refused
Mar 06 04:19:56 ubuntu gdm3[1016]: [./ply-boot-client.c:184]
   ply_boot_client_connect:trying old fallback path /ply-boot-protocol
Mar 06 04:19:56 ubuntu gdm3[1016]: [./ply-boot-client.c:190]
   ply_boot_client_connect:could not connect to /ply-boot-protocol: Connection 
refused
Mar 06 04:19:56 ubuntu gdm3[1016]: [./plymouth.c:1121]  
main:daemon not running
Mar 06 04:19:56 ubuntu gdm3[1016]: [./plymouth.c:1124]  
main:ping failed
***

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

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo 

[Touch-packages] [Bug 1753576] Re: GDM freeze

[Nish Aravamudan]

Hrm, I'm not entirely sure what just changed. I rebooted and unlike
before, I hit Escape at the splash screen, and the GDM greeter showed up
just fine (after hitting Escape again to go back to graphics mode). I'll
see if that's reproducible shortly.

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

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

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

[Touch-packages] [Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1

[Daniel van Vugt]

Michael,

If you have any continuing problems then please log a new bug.

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

Title:
  [regression] Missing Wayland login option and missing GL acceleration,
  after installing libegl1

Status in libglvnd package in Ubuntu:
  Fix Released
Status in mesa-demos package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  I just updated bionic and suddenly:
    * No 'Ubuntu on Wayland' login option.
    * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe 
(software rendering)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Feb 24 13:59:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-12 (73 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1

[Daniel van Vugt]

Yes, the workaround "sudo apt remove libegl1" was only safe in February.
Not safe after the mutter and mir updates in March :(

Thanks for fixing this.

** Description changed:

  I just updated bionic and suddenly:
    * No 'Ubuntu on Wayland' login option.
    * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe 
(software rendering)
- 
- WORKAROUND: sudo apt remove libegl1
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Feb 24 13:59:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-12 (73 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  [regression] Missing Wayland login option and missing GL acceleration,
  after installing libegl1

Status in libglvnd package in Ubuntu:
  Fix Released
Status in mesa-demos package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  I just updated bionic and suddenly:
    * No 'Ubuntu on Wayland' login option.
    * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe 
(software rendering)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Feb 24 13:59:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-12 (73 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1717995] Re: extra domains not removed from resolv.conf when VPN disconnects

[pureblood]

I have had the same exact problem since I have upgraded to 17.10. In my
case it does not even involve the VPN. When I come back from work, if I
had suspended the laptop without restarting it, then I cannot connect to
the computers from work.

If I restart resolvconf with:
$ sudo /etc/init.d/resolvconf restart
The problem persists.

If I edit the file /run/resolvconf/interface/systemd-resolved with
$ sudo emacs -nw /run/resolvconf/interface/systemd-resolved
... remove the work computer name in the line starting with search ...
$ sudo /etc/init.d/resolvconf restart
Then it works fine.

I hope this bug is well understood and the fix is on its way. It seems
like a bit of a corner case, but it is indeed a serious bug.

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

Title:
  extra domains not removed from resolv.conf when VPN disconnects

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I use a VPN (network manager "vpnc" config) to connect to my work
  network.  The gateway is "webvpn.purestorage.com".  When I connect, I
  get "purestorage.com" added to the "search" line in my
  /etc/resolv.conf (and /run/resolvconf/interface/systemd-resolved) -
  which makes perfect sense, the VPN passes this info to me and then I
  can connect to systems within the work network without having to use a
  FQDN.

  The bug (which is a regression from older versions of Ubuntu) is that
  when I lose my connection to the VPN (either because I disconnect
  explicitly, or because the network goes down or I suspend my laptop),
  the "purestorage.com" domain is not removed from those "search" lines.
  And for some reason this prevents me from resolving
  webvpn.purestorage.com (which prevents me from reconnecting to the
  VPN).

  In particular, if I connect and disconnect my VPN, I get:

   $ systemd-resolve webvpn.purestorage.com
  webvpn.purestorage.com: resolve call failed: No appropriate name servers or 
networks for name found

  If I then edit /etc/resolv.conf by hand to remove all the
  purestorage.com entries from the search line - in other words, change

   $ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  search home.digitalvampire.org purestorage.com dev.purestorage.com

  to

   $ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  search home.digitalvampire.org

  and change nothing else, then:

   $ systemd-resolve webvpn.purestorage.com
  webvpn.purestorage.com: 192.30.189.1
  (vpn.purestorage.com)

  -- Information acquired via protocol DNS in 25.9ms.
  -- Data is authenticated: no

  
  I'm not sure if the bug is in systemd, network manager, or some other 
package, but I'm happy to try any debugging that is helpful to resolve this (no 
pun intended).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu10
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 11:20:17 2017
  InstallationDate: Installed on 2016-09-01 (381 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901)
  MachineType: LENOVO 20FRS2FK00
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic 
root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-07-26 (53 days ago)
  dmi.bios.date: 07/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET53W (1.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS2FK00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FRS2FK00:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2FK00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FRS2FK00
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

[Touch-packages] [Bug 1741150] Re: 'ubuntu-bug cups'

[Launchpad Bug Tracker]

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

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

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

Title:
  'ubuntu-bug cups'

Status in cups package in Ubuntu:
  Expired

Bug description:
  i can't print a single file.

  i think my printer is not detected.

  printer is always idle.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CupsErrorLog:
   E [04/Jan/2018:08:39:32 +0800] [cups-deviced] PID 6431 (gutenprint52+usb) 
stopped with status 1!
   E [04/Jan/2018:08:40:41 +0800] [cups-deviced] PID 6583 (gutenprint52+usb) 
stopped with status 1!
   W [04/Jan/2018:08:41:34 +0800] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'EPSON-ME-10-Series-Gray..\' already exists
   E [04/Jan/2018:08:45:32 +0800] [cups-deviced] PID 7126 (gutenprint52+usb) 
stopped with status 1!
   E [04/Jan/2018:08:51:42 +0800] [cups-deviced] PID 7239 (gutenprint52+usb) 
stopped with status 1!
  CurrentDesktop: Unity
  Date: Thu Jan  4 08:59:36 2018
  InstallationDate: Installed on 2018-01-03 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lpstat: device for EPSON-ME-10-Series: 
usb://EPSON/ME-10%20Series?serial=51344C4B3031333571
  MachineType: Hewlett-Packard 500-232d
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON-ME-10-Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON-ME-10-Series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic.efi.signed 
root=UUID=0ba09fb1-b9fa-45aa-a08e-c801161d6dcd ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2014
  dmi.bios.vendor: AMI
  dmi.bios.version: 80.12
  dmi.board.name: 2AF7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.03
  dmi.chassis.asset.tag: 4CE4110B0Q
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr80.12:bd01/15/2014:svnHewlett-Packard:pn500-232d:pvr1.00:rvnHewlett-Packard:rn2AF7:rvr1.03:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: 500-232d
  dmi.product.version: 1.00
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

[Launchpad Bug Tracker]

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

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

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in aptitude package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Fix Released
Status in aptitude source package in Xenial:
  Confirmed
Status in synaptic source package in Xenial:
  Confirmed
Status in update-notifier source package in Xenial:
  Fix Committed
Status in apt package in Debian:
  Fix Released
Status in aptitude package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  READ ME FIRST
  =
  This is a cosmetic issue. The warning message is just that— a warning. Though 
the message comes up, there is no problem with the install/upgrade happening 
like normal. That said, feel free to ignore it. It will get fixed, but it's 
nowhere near as urgent as bugs that actually result in the wrong behavior 
rather than just a simple extra message.

  update-notifier SRU
  ---
  [Impact]
  Cosmetic. Warnings when installing packages using update-notifier downloading 
stuff

  [Test case]

  Install flashplugin-installer with apt and check that the output does
  not contain a message like this:

  W: Can't drop privileges for downloading as file '...' couldn't be
  accessed by user '_apt'

  [Regression Potential]

  It just chowns /var/lib/update-notifier/package-data-
  downloads/partial/ to _apt:root, there should not be any regression.

  Original report
  ---

  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

[Launchpad Bug Tracker]

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

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

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in aptitude package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Fix Released
Status in aptitude source package in Xenial:
  Confirmed
Status in synaptic source package in Xenial:
  Confirmed
Status in update-notifier source package in Xenial:
  Fix Committed
Status in apt package in Debian:
  Fix Released
Status in aptitude package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  READ ME FIRST
  =
  This is a cosmetic issue. The warning message is just that— a warning. Though 
the message comes up, there is no problem with the install/upgrade happening 
like normal. That said, feel free to ignore it. It will get fixed, but it's 
nowhere near as urgent as bugs that actually result in the wrong behavior 
rather than just a simple extra message.

  update-notifier SRU
  ---
  [Impact]
  Cosmetic. Warnings when installing packages using update-notifier downloading 
stuff

  [Test case]

  Install flashplugin-installer with apt and check that the output does
  not contain a message like this:

  W: Can't drop privileges for downloading as file '...' couldn't be
  accessed by user '_apt'

  [Regression Potential]

  It just chowns /var/lib/update-notifier/package-data-
  downloads/partial/ to _apt:root, there should not be any regression.

  Original report
  ---

  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Doug McMahon]

On 03/05/2018 09:02 PM, Daniel van Vugt wrote:
> Doug,
>
> Ideally it will be automatically installed, or at least gets installed
> with ubuntu-restricted-addons. See:
> https://wiki.ubuntu.com/IntelQuickSyncVideo
>
Good to know about the add-ons package, been quite awhile here that I've 
used it. Generally on new install I'm just trying to play media & 
looking to see if the gst-packagekit > ubuntu-software reacts properly, 
ect. (- which it's doing a decent job atm, always some room for 
improvement..
I'd think many users also follow that path, i.e add or access media then 
follow the pop up if support isn't already available.

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Fix Released
Status in Totem:
  Expired
Status in VLC media player:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Committed
Status in gstreamer-vaapi package in Ubuntu:
  Won't Fix
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1753576] Re: GDM freeze

[Nish Aravamudan]

Oh also the splash screen correctly displays on both monitors, so i
think it must be in X that the multiple displays fail.

I'll see if I can figure out how to get to a temrinal.

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

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

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

[Touch-packages] [Bug 1753576] Re: GDM freeze

[Nish Aravamudan]

@vanvugt: no, as it's not crashed (afaict), it's just 100% cpu (based
upon fans). Numlock is still responsive as is sysrq, but i can't get to
any ttys (that is, ctrl+alt+f2, etc don't seem to work).

I even tried booting with 'text' and annoyingly gdm still started (I
might be misremembering how to do that, though).

Any suggestions on how to force a crash?

I might reboot now and just leave it to see if it eventually progresses.

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

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

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

[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

[Jamie Strandboge]

This is fixed in xenial 2.3.1-2.1ubuntu2~16.04.1

** Changed in: libseccomp (Ubuntu Xenial)
   Status: In Progress => Fix Released

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

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in Snappy:
  In Progress
Status in libseccomp package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in libseccomp source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

  [Impact]

  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).

  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds
  a number of new symbols and probably isn't appropriate to backport
  until upstream has acked the pull request. However, only a small part
  of that larger pull request is needed by snapd and that change can be
  safely backported since the only added symbol, the SCMP_ACT_LOG macro,
  must match the SECCOMP_RET_LOG macro that has already been approved
  and merged in the upstream Linux kernel.

  [libseccomp Test Case]

  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised
  to help catch any regressions. Note that on Artful, there's an
  existing test failure (20-live-basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)

  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  

  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:

  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test

  With a kernel that contains the logging patches and an updated
  libseccomp, the exit code should be 0 and you should have an entry in
  the system log that looks like this:

  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test"
  exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2
  compat=0 ip=0x7f547352c5c0 code=0x7ffc

  If you have an updated libseccomp with an old kernel, you'll see that
  seccomp_init() fails due to the added compatibility check inside of
  libseccomp determines that the kernel doesn't have proper support for
  the new log action:

  $ ./lp1567597-test
  ERROR: seccomp_init: Invalid argument

  [Linux Kernel Test Case]

  All of the libseccomp test cases apply here.

  

  Running the seccomp kernel selftests is also a great to exercise
  seccomp and the kernel patch set proposed for the SRU includes
  additional seccomp selftests. To build, enter into the root of the
  kernel source tree and build the seccomp test binary:

  $ make -C tools/testing/selftests TARGETS=seccomp

  Now you can execute 

[Touch-packages] [Bug 1753576] Re: GDM freeze

[Daniel van Vugt]

Can you find any crash files in /var/crash ?

If so then please run:

  ubuntu-bug /var/crash/YOURFILE.crash

and tell us the new bug ID.

** Summary changed:

- Xorg freeze
+ GDM freeze

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

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

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

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

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

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

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

[Touch-packages] [Bug 295876] Re: top and ps truncate command after 15 chars

[PabloAB]

The reason is in kernel TASK_COMM_LEN (check man proc) constant fixed to
16 (name + \0). A guy called [Luben Tuikov][0] proposed to increase this
back on 2006 ([last lines][1] of sys.c). Even if this is too difficult
because of mysterous complicated reasons pgrep should search on the
complete name, not the truncated version (/proc/PID/comm,
/proc/PID/status | grep ^Name).

Maybe something like  grep -hoa "\/[^/]*$" /proc/*/cmdline  | grep -a
pattern  [or][2]  ps aux | grep "[p]attern".

With -f "the full command line is used" (/proc/PID/cmdline, readlink
/proc/PID/exe). This is too broad.

Something similar happen with the 4096 B limit of PAGE_SIZE. In that
case the solution is easy, [just recompile the kernel][3] with a new
value... :s

[0](http://lkml.iu.edu/hypermail/linux/kernel/0606.2/3139.html)
[1](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/kernel/sys.c#n2544)
[2](https://unix.stackexchange.com/a/74186/209677)
[3](https://stackoverflow.com/a/199199/4970442)

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

Title:
  top and ps truncate command after 15 chars

Status in Procps:
  Confirmed
Status in procps package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: procps

  I guess this is an issue with 'top', and not really Ubuntu related,
  but...

  I noticed something hogging my CPU, and top revealed:

  15219 root  30  10  109m 104m 4092 R   92  5.2   1:44.15 update-
  apt-xapi

  Of course, there is no such process called 'update-apt-xapi'.

  top truncates the process name to 15 chars (this was in fact 'update-
  apt-xapian-index' running).

  Nick

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

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

[Touch-packages] [Bug 1753298] Re: audio not working, apollo lake 4.16 kernel

[Daniel van Vugt]

It appears you don't have audio because pulseaudio has crashed(?):

PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.

Can you please test a newer version by booting this?;

  http://cdimages.ubuntu.com/daily-live/current/

Please also apply the workaround for bug 994921, and if you find any
crash files in /var/crash then report them by running this command:

  ubuntu-bug /var/crash/YOURFILE.crash

And tell us the new bug ID that gets created.

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

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

Title:
  audio not working, apollo lake 4.16 kernel

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I tried a lot of 4.16 ubuntu kenerls and audio is not working.

  Jumper EZ book v4, Ubuntu 16.04.4.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  Uname: Linux 4.16.0-994-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mich   2171 F pulseaudio
  Date: Sun Mar  4 19:48:50 2018
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: JUMPER2x.P8.WP313R.NHNAUHN05
  dmi.board.asset.tag: Default string
  dmi.board.name: P313R
  dmi.board.vendor: INET
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrJUMPER2x.P8.WP313R.NHNAUHN05:bd09/30/2017:svnJumper:pnEZbook:pvrDefaultstring:rvnINET:rnP313R:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: EZbook
  dmi.product.version: Default string
  dmi.sys.vendor: Jumper
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2017-11-05T18:46:40.564172
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 4.16.0-994-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

[Hui Wang]

OK, got it. thanks.

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+subscriptions

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

[Touch-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

[Daniel van Vugt]

Yes I think that's what we need.

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+subscriptions

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

[Touch-packages] [Bug 1390709] Re: Wifi doesn't reconnect after waking from sleep

[Guillaume]

For me it happens on Ubuntu 18.04.
I'm on a surfacebook.

Directly if my pc go sleep, i lost the wifi connection.
I've to restart to have wifi connection.

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

Title:
  Wifi doesn't reconnect after waking from sleep

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Upgraded from 14.04 to 14.10. Before Wifi would reconnect after waking
  up from sleep mode. After Update reconnect fails with wlan0: aborting
  authentication with 1c:c6:3c:95:e7:74 by local choice (Reason:
  3=DEAUTH_LEAVING).

  I worked around this by killing wpa_supplicant with a script in
  /etc/pm/sleep.d

  
  #!/bin/sh

  case "$1" in
  thaw|resume) 
  { killall wpa_supplicant ; } 2>/dev/null
  ;;
  *)
  ;;
  esac

  exit $?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu28
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Nov  8 11:43:15 2014
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-04-19 (567 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  IpRoute:
   default via 192.168.138.251 dev wlan0  proto static 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
   192.168.138.0/24 dev wlan0  proto kernel  scope link  src 192.168.138.143  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-11-07 (0 days ago)
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

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

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

[Touch-packages] [Bug 1699033] Re: Two-finger right click does not work in gnome-shell

[Daniel van Vugt]

I completely agree. It is annoying that basic settings are missing in
the Settings app.

If it bothers you enough then please log a bug directly with the
upstream developers in their new bug tracker:

  https://gitlab.gnome.org/GNOME/gnome-control-center/issues

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

Title:
  Two-finger right click does not work in gnome-shell

Status in GSettings Desktop Schemas:
  Fix Released
Status in gsettings-desktop-schemas package in Ubuntu:
  Fix Released

Bug description:
  Using two fingers on the clickpad to right click does not work in
  gnome-shell.

  It seems to be defaulting to the old-style single finger click in the
  bottom right corner to do a right click.

  Workaround:
  gnome-tweak-tool > Keyboard & Mouse > Touchpad > Click Method = Fingers

  Gsettings diff:
  < org.gnome.desktop.peripherals.touchpad click-method 'default'
  ---
  > org.gnome.desktop.peripherals.touchpad click-method 'fingers'

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.11.0-7.12-generic 4.11.6
  Uname: Linux 4.11.0-7-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Tue Jun 20 14:50:10 2017
  DisplayManager: lightdm
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-06-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170613)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1699033/+subscriptions

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

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Daniel van Vugt]

Doug,

Ideally it will be automatically installed, or at least gets installed
with ubuntu-restricted-addons. See:
https://wiki.ubuntu.com/IntelQuickSyncVideo

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Fix Released
Status in Totem:
  Expired
Status in VLC media player:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Committed
Status in gstreamer-vaapi package in Ubuntu:
  Won't Fix
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Daniel van Vugt]

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

Bug 1710637 seems to be fixed in 17.10 and later only.

If you continue to experience this bug with Alt+left/right in 17.10 or
18.04 then yes we should reopen this bug.

Timothy: What release are you using?

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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

[Touch-packages] [Bug 1174911] Re: pgrep does at default not always match the input of the user against the process name

[Launchpad Bug Tracker]

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

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

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

Title:
  pgrep does at default not always match the input of the user against
  the process name

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  When looking for a process with a long process name, pgrep cuts the
  process name, and so doesn't match an exact search. For example:

  # launch gnome-calculator:
  $ gnome-calculator

  # use 'ps a' to show process table - note the whole process name is present:
  $ ps a
PID TTY  STAT   TIME COMMAND
   1411 tty4 Ss+0:00 /sbin/getty -8 38400 tty4
   1417 tty5 Ss+0:00 /sbin/getty -8 38400 tty5
   1427 tty2 Ss+0:00 /sbin/getty -8 38400 tty2
   1428 tty3 Ss+0:00 /sbin/getty -8 38400 tty3
   1436 tty6 Ss+0:00 /sbin/getty -8 38400 tty6
   9417 pts/1Sl 0:00 gnome-calculator
   9426 pts/1R+ 0:00 ps a

  (some results cut for clarity)

  # now try and find it with pgrep:
  $ pgrep gnome-calculator

  # no results! however, this works:
  $ pgrep gnome-calculato

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: procps 1:3.3.3-2ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Tue Apr 30 13:35:02 2013
  InstallationDate: Installed on 2012-01-17 (469 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: procps
  UpgradeStatus: Upgraded to raring on 2012-12-05 (145 days ago)

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

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

[Touch-packages] [Bug 1752123] Re: Force 8bit RGB config

[Jeremy Bicha]

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

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

Title:
  Force 8bit RGB config

Status in cogl package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  New mesa supports 10bit RGB configs, and this causes issues with
  cogl/mutter which get a random EGLConfig that breaks some
  autopkgtests. To fix this this merge request is needed for mutter

  https://gitlab.gnome.org/GNOME/mutter/merge_requests/36

  and a similar one for cogl.

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

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

[Touch-packages] [Bug 1752472] Re: [ffe] Implement an Ubuntu Single Sign-on Provider

[Bug Watch Updater]

** Changed in: gnome-online-accounts
   Importance: Medium => Wishlist

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

Title:
  [ffe] Implement an Ubuntu Single Sign-on Provider

Status in gnome-online-accounts:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Add an Ubuntu Single Sing-On provider in gnome-online-accounts. We plan to 
use this inside:
  1) gnome-software
  2) software-properties

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1752472/+subscriptions

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

[Touch-packages] [Bug 1753352] Re: package linux-image-extra-4.4.0-116-generic 4.4.0-116.140 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Christopher M BRADLEY]

Further to the above:

1. I found persisting references to earlier, now long-gone kernels in 
/var/lib/initramfs-tools, but not a complete list (there were 17, but there 
might have been many more if all the old kernel listings had been retained).
2. I manually deleted all but the newest and immediately prior references.
3. After confirming the system data via dpkg enquiries, I ran 'sudo dpkg 
--configure -a' which did not work.
4. I then ran 'sudo apt-get -f install' which allowed the new kernel extras 
installation to complete properly.

The cause of the installation failure was the attempt by the installer
to generate multiple initrd.img- files (as instructed from /var/lib
/initramfs-tools) which rapidly filled /boot leading to the software
break; these redundant initrd.img- files must be deleted from /boot for
the above steps to work (ie. to make space for the installer to proceed
within /boot).

These steps have solved this episode; it seems likely that with further
time, a new set of outdated kernel data will accumulate in /var/lib
/initramfs-tools, requiring manual deletion.

Automating this clean-up at the time of kernel updates may be entirely
inappropriate on many systems.

The above may assist others.

I look forward to more expert assessment.

CMB 06/03/2018

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

Title:
  package linux-image-extra-4.4.0-116-generic 4.4.0-116.140 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  dpkg -l | grep linux-image
  ii  linux-image-4.4.0-112-generic   4.4.0-112.135 
   amd64Linux kernel image for version 4.4.0 on 64 bit x86 
SMP
  ii  linux-image-4.4.0-116-generic   4.4.0-116.140 
   amd64Linux kernel image for version 4.4.0 on 64 bit x86 
SMP
  ii  linux-image-extra-4.4.0-112-generic 4.4.0-112.135 
   amd64Linux kernel extra modules for version 4.4.0 on 64 
bit x86 SMP
  iF  linux-image-extra-4.4.0-116-generic 4.4.0-116.140 
   amd64Linux kernel extra modules for version 4.4.0 on 64 
bit x86 SMP
  iU  linux-image-generic   

  uname -r
  4.4.0-116-generic

  The above after rebooting to *-116.
  System seems to be working; I will try to repair the failed installation soon.

  There has been a constant issue where the installer tries to recover
  long-uninstalled initram elements such as initrd.img-4.2.0-16-generic
  (and later) filling /boot, etc. I have manually removed these files
  from /boot to an "obsolete" folder to allow df -h to report enough
  space.

  The system seems to be reading outdated info from an 'initram.conf' or
  similar file and I believe this may be the fault, or part of it. I can
  manually edit out references to earlier kernels when I find the file.

  Do you have any suggestions?

  Advanced user

  CM BRADLEY
  05/03/2018
  AU CDST 13:25:00

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  administrator   2025 F pulseaudio
   /dev/snd/controlC0:  administrator   2025 F pulseaudio
   /dev/snd/seq:timidity   1329 F timidity
  Date: Mon Mar  5 13:03:41 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=abf7583a-8eda-4113-a8cd-1f301a7d7f06
  InstallationDate: Installed on 2016-04-26 (677 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-116-generic 4.4.0-116.140 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: 

[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

[gumbeto]

Bryce Schober (bryce-schober): I had a very similar issue, but on 16.04
and wanting gcc-7. Adding the the toolchain ppa made gcc-5 subject to
upgrading, triggering this issue. I managed to deal with it with package
pinning and aptitude (see comment 58).

Here are a few more details if in case you want to try this yourself (I
recommend using Timeshift or similar in case you want to go back).

$ cat /etc/apt/preferences.d/toolchain.pref
Package: *
Pin: release o=LP-PPA-ubuntu-toolchain-r-test
Pin-Priority: 60

Here are some quick instructions on how to use aptitude:
https://makandracards.com/makandra/47558-how-to-install-packages-from-
newer-ubuntu-releases#planning-the-upgrade

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) by an insufficient compiler!

Status in gcc:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

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

  Rebooted into 4.4.0-112 kernel and all was well.

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

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

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

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

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

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

-- 
Mailing list: 

[Touch-packages] [Bug 1693038] Re: needs to support restart on Lubuntu and Xubuntu

[Brian Murray]

** Description changed:

- The fix for bug 1241210 only works in gnome-session based sessions.
- Let's make sure that the driver restart button works on Xubuntu and
- Lubuntu.
+ [Test Case]
+ 1) sudo touch /var/run/reboot-required
+ 2) sudo apt install umockdev gir1.2-umockdev-1.0
+ 3) /usr/share/ubuntu-drivers-common/fake-devices-wrapper 
software-properties-gtk --open-tab 4
+ 4) click the Restart button
+ 
+ You should observe a dialog either confirming that you want to restart
+ or with a restart button. It depends what desktop environment you are
+ running.
+ 
+ Original Description
+ 
+ The fix for bug 1241210 only works in gnome-session based sessions. Let's 
make sure that the driver restart button works on Xubuntu and Lubuntu.

** Changed in: software-properties (Ubuntu)
Milestone: ubuntu-17.07 => None

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

Title:
  needs to support restart on Lubuntu and Xubuntu

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  [Test Case]
  1) sudo touch /var/run/reboot-required
  2) sudo apt install umockdev gir1.2-umockdev-1.0
  3) /usr/share/ubuntu-drivers-common/fake-devices-wrapper 
software-properties-gtk --open-tab 4
  4) click the Restart button

  You should observe a dialog either confirming that you want to restart
  or with a restart button. It depends what desktop environment you are
  running.

  Original Description
  
  The fix for bug 1241210 only works in gnome-session based sessions. Let's 
make sure that the driver restart button works on Xubuntu and Lubuntu.

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

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

[Touch-packages] [Bug 1753136] Re: Gettext package inconsistency

[Bug Watch Updater]

** Changed in: libgweather
   Status: Confirmed => Fix Released

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

Title:
  Gettext package inconsistency

Status in libgweather:
  Fix Released
Status in Ubuntu Translations:
  New
Status in libgweather package in Ubuntu:
  Triaged

Bug description:
  New translation issue after the switch to meson. It's probably an
  upstream thing, and I have filed an upstream bug report with a patch
  and explained it there.

  Possibly this motivates a new upstream release rather than distro
  patches in Debian/Ubuntu.

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

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

[Touch-packages] [Bug 1746579] Re: A boxes instead of a Cyrillic chars in VTs

[Gannet]

Recently I've been installed 18.04 on my host system. A boxes in VM
still is. So it is not because of Virtio/QXL/KVM.

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

Title:
  A boxes instead of a Cyrillic chars in VTs

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  $ apt-cache policy keyboard-configuration
  keyboard-configuration:
Встановлено: 1.166ubuntu7
Кандидат:1.166ubuntu7
Таблиця версій:
   *** 1.166ubuntu7 500
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://ua.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  I expected to have cyrillic fonts in any of six VTs, /dev/tty[1-6],
  but it shows boxes instead of them. Please, see screen shot in
  attachment.

  It's very likely that this is an old bug that was fixed earlier but it
  appeared it 18.04 dev again. Here it is:
  https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1565542

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: console-setup 1.166ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Jan 31 20:46:57 2018
  InstallationDate: Installed on 2018-01-12 (19 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180103)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: console-setup
  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/1746579/+subscriptions

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

[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

[Bryce Schober]

On Ubuntu 14.04, I've installed the ubuntu-toolchain-r/test ppa in order
to get a gcc-5 compiler, and the assumedly-conflicting
4.8.5-2ubuntu1~14.04.1 came from that PPA along for the ride.

Is there a better PPA option for installing gcc-5 on Ubuntu 14.04?

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) by an insufficient compiler!

Status in gcc:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

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

  Rebooted into 4.4.0-112 kernel and all was well.

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

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

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

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

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

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

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

[Touch-packages] [Bug 1753576] Re: Xorg freeze

[Jeremy Bicha]

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Xorg freeze

Status in gnome-shell package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

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

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

[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"

[Launchpad Bug Tracker]

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

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

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

Title:
  cpio in Busybox 1.27 ingnores "unsafe links"

Status in busybox package in Ubuntu:
  Confirmed
Status in debirf package in Ubuntu:
  Confirmed

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

  busybox:
Installed: 1:1.27.2-2ubuntu3
Candidate: 1:1.27.2-2ubuntu3

  3) Expected my CPIO archive to be fully extracted with proper symlinks
  Command: unxz < /rootfs.cxz | cpio -i

  4) 'Unsafe' symlinks were ignored such as:

  sbin/init -> /lib/systemd/systemd

  With the broken 1.27 sbin/init does not get created at all and my
  debirf initrd fails to load/boot properly.

  1.22 from Xenial works.
  GNU Cpio also works.

  It looks like 1.28 adds an env var to override this behavior:

  libarchive: do not extract unsafe symlinks unless
  $EXTRACT_UNSAFE_SYMLINKS=1

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

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

[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"

[Launchpad Bug Tracker]

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

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

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

Title:
  cpio in Busybox 1.27 ingnores "unsafe links"

Status in busybox package in Ubuntu:
  Confirmed
Status in debirf package in Ubuntu:
  Confirmed

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

  busybox:
Installed: 1:1.27.2-2ubuntu3
Candidate: 1:1.27.2-2ubuntu3

  3) Expected my CPIO archive to be fully extracted with proper symlinks
  Command: unxz < /rootfs.cxz | cpio -i

  4) 'Unsafe' symlinks were ignored such as:

  sbin/init -> /lib/systemd/systemd

  With the broken 1.27 sbin/init does not get created at all and my
  debirf initrd fails to load/boot properly.

  1.22 from Xenial works.
  GNU Cpio also works.

  It looks like 1.28 adds an env var to override this behavior:

  libarchive: do not extract unsafe symlinks unless
  $EXTRACT_UNSAFE_SYMLINKS=1

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

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

[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"

[Bryan Seitz]

** Project changed: busybox => debirf (Ubuntu)

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

Title:
  cpio in Busybox 1.27 ingnores "unsafe links"

Status in busybox package in Ubuntu:
  Confirmed
Status in debirf package in Ubuntu:
  Confirmed

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

  busybox:
Installed: 1:1.27.2-2ubuntu3
Candidate: 1:1.27.2-2ubuntu3

  3) Expected my CPIO archive to be fully extracted with proper symlinks
  Command: unxz < /rootfs.cxz | cpio -i

  4) 'Unsafe' symlinks were ignored such as:

  sbin/init -> /lib/systemd/systemd

  With the broken 1.27 sbin/init does not get created at all and my
  debirf initrd fails to load/boot properly.

  1.22 from Xenial works.
  GNU Cpio also works.

  It looks like 1.28 adds an env var to override this behavior:

  libarchive: do not extract unsafe symlinks unless
  $EXTRACT_UNSAFE_SYMLINKS=1

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

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

[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"

[Bryan Seitz]

** Also affects: busybox
   Importance: Undecided
   Status: New

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

Title:
  cpio in Busybox 1.27 ingnores "unsafe links"

Status in busybox package in Ubuntu:
  Confirmed
Status in debirf package in Ubuntu:
  Confirmed

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

  busybox:
Installed: 1:1.27.2-2ubuntu3
Candidate: 1:1.27.2-2ubuntu3

  3) Expected my CPIO archive to be fully extracted with proper symlinks
  Command: unxz < /rootfs.cxz | cpio -i

  4) 'Unsafe' symlinks were ignored such as:

  sbin/init -> /lib/systemd/systemd

  With the broken 1.27 sbin/init does not get created at all and my
  debirf initrd fails to load/boot properly.

  1.22 from Xenial works.
  GNU Cpio also works.

  It looks like 1.28 adds an env var to override this behavior:

  libarchive: do not extract unsafe symlinks unless
  $EXTRACT_UNSAFE_SYMLINKS=1

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

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

[Touch-packages] [Bug 1740666] Re: systemd-timesyncd doesn't sync time after resume from hibernate

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

Title:
  systemd-timesyncd doesn't sync time after resume from hibernate

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

Bug description:
  When resuming, the clock remains at the time when the hibernate
  happened, even if timedatectl claims that it is being synced:

  $ timedatectl status
Local time: Вс 2017-12-31 13:46:16 +05
Universal time: Вс 2017-12-31 08:46:16 UTC
  RTC time: Вс 2017-12-31 08:46:16
 Time zone: Asia/Yekaterinburg (+05, +0500)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  I've tried waiting a bit, but this persisted for some minutes, so I
  forced an update with

  systemctl restart systemd-timesyncd.service

  And afterwards the time was (apparently) correctly synced.

  Please, let me know what further informations are needed to debug the
  issue, and I would be happy to do some other test.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Dec 31 13:41:51 2017
  InstallationDate: Installed on 2017-06-05 (208 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=1bda199b-5177-4ed2-babe-46c9ab503918 ro quiet splash zswap.enabled=1 
zswap.compressor=lz4 zswap.max_pool_percent=33 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago)
  dmi.bios.date: 06/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1753576] [NEW] Xorg freeze

[Nish Aravamudan]

Public bug reported:

Here is what I know so far:

After rebooting this morning on Bionic (after receiving the gnome theme
updates, I think), upon reboot the CPU pegs and the greeter is never
displayed (there is a graphics system running, but I'm not sure what
it's doing). My num lock / caps lock keys work, but the touchpad on the
laptop does nothing to the mouse.

If I boot with nomodeset, greeter does not freeze.

Finally, in either case, I am now unable to use my external monitor,
which worked fine before (connected over a USB-C to HDMI dongle).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Mon Mar  5 11:47:53 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
InstallationDate: Installed on 2015-12-17 (809 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 80MK
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/29/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: C6CN34WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: VIUU4
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K45914 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA 900-13ISK
dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80MK
dmi.product.version: Lenovo YOGA 900-13ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Mar  5 11:17:58 2018
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu2

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


** Tags: amd64 apport-bug bionic freeze has-workaround regression reproducible 
single-occurrence 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/1753576

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: 

[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"

[Bryan Seitz]

Proposed solution: back port the env var patch or upgrade to 1.28.

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

Title:
  cpio in Busybox 1.27 ingnores "unsafe links"

Status in busybox package in Ubuntu:
  Confirmed

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

  busybox:
Installed: 1:1.27.2-2ubuntu3
Candidate: 1:1.27.2-2ubuntu3

  3) Expected my CPIO archive to be fully extracted with proper symlinks
  Command: unxz < /rootfs.cxz | cpio -i

  4) 'Unsafe' symlinks were ignored such as:

  sbin/init -> /lib/systemd/systemd

  With the broken 1.27 sbin/init does not get created at all and my
  debirf initrd fails to load/boot properly.

  1.22 from Xenial works.
  GNU Cpio also works.

  It looks like 1.28 adds an env var to override this behavior:

  libarchive: do not extract unsafe symlinks unless
  $EXTRACT_UNSAFE_SYMLINKS=1

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

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

[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"

[Launchpad Bug Tracker]

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

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

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

Title:
  cpio in Busybox 1.27 ingnores "unsafe links"

Status in busybox package in Ubuntu:
  Confirmed

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

  busybox:
Installed: 1:1.27.2-2ubuntu3
Candidate: 1:1.27.2-2ubuntu3

  3) Expected my CPIO archive to be fully extracted with proper symlinks
  Command: unxz < /rootfs.cxz | cpio -i

  4) 'Unsafe' symlinks were ignored such as:

  sbin/init -> /lib/systemd/systemd

  With the broken 1.27 sbin/init does not get created at all and my
  debirf initrd fails to load/boot properly.

  1.22 from Xenial works.
  GNU Cpio also works.

  It looks like 1.28 adds an env var to override this behavior:

  libarchive: do not extract unsafe symlinks unless
  $EXTRACT_UNSAFE_SYMLINKS=1

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

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

[Touch-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

[Krister]

I'm sorry for dumping the dmesg output into the thread.  Here it is in a
file.  But it's from after reboot.  Does this have the error messages in
it from the previous session?  Do I have to get a file from /var/log/ ?

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1752145/+attachment/5070185/+files/dmesg.txt

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

Title:
  system freeze after full screen video viewing with Xorg on ultrawide
  monitor

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. open a video (either youtube or totem)
  2. put it in full screen.
  3. wait

  Eventually (within minutes) the system will freeze in one of 2 ways.

  1. There will be only blackness with no response ( even
  unresponsive).

  2. There will be snow that shifts with keyboard and mouse interaction
  (see photo).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 19:08:13 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2018-01-05 (53 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago)

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

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

[Touch-packages] [Bug 1753572] [NEW] cpio in Busybox 1.27 ingnores "unsafe links"

[Bryan Seitz]

Public bug reported:

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

busybox:
  Installed: 1:1.27.2-2ubuntu3
  Candidate: 1:1.27.2-2ubuntu3

3) Expected my CPIO archive to be fully extracted with proper symlinks
Command: unxz < /rootfs.cxz | cpio -i

4) 'Unsafe' symlinks were ignored such as:

sbin/init -> /lib/systemd/systemd

With the broken 1.27 sbin/init does not get created at all and my debirf
initrd fails to load/boot properly.

1.22 from Xenial works.
GNU Cpio also works.

It looks like 1.28 adds an env var to override this behavior:

libarchive: do not extract unsafe symlinks unless
$EXTRACT_UNSAFE_SYMLINKS=1

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


** Tags: busybox cpio

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

Title:
  cpio in Busybox 1.27 ingnores "unsafe links"

Status in busybox package in Ubuntu:
  Confirmed

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

  busybox:
Installed: 1:1.27.2-2ubuntu3
Candidate: 1:1.27.2-2ubuntu3

  3) Expected my CPIO archive to be fully extracted with proper symlinks
  Command: unxz < /rootfs.cxz | cpio -i

  4) 'Unsafe' symlinks were ignored such as:

  sbin/init -> /lib/systemd/systemd

  With the broken 1.27 sbin/init does not get created at all and my
  debirf initrd fails to load/boot properly.

  1.22 from Xenial works.
  GNU Cpio also works.

  It looks like 1.28 adds an env var to override this behavior:

  libarchive: do not extract unsafe symlinks unless
  $EXTRACT_UNSAFE_SYMLINKS=1

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

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

[Touch-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

[Krister]

Here's dmesg after a freeze of the system when watching a video with
VLC.  The strange snow did not show up this time:

=> dmesg
[0.00] Linux version 4.15.0-10-generic (buildd@lgw01-amd64-036) (gcc 
version 7.3.0 (Ubuntu 7.3.0-3ubuntu1)) #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 
2018 (Ubuntu 4.15.0-10.11-generic 4.15.3)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=7
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0003efff] usable
[0.00] BIOS-e820: [mem 0x0003f000-0x0003] reserved
[0.00] BIOS-e820: [mem 0x0004-0x0009] usable
[0.00] BIOS-e820: [mem 0x0010-0xc93bcfff] usable
[0.00] BIOS-e820: [mem 0xc93bd000-0xc9f5cfff] reserved
[0.00] BIOS-e820: [mem 0xc9f5d000-0xc9fc3fff] ACPI data
[0.00] BIOS-e820: [mem 0xc9fc4000-0xcac90fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xcac91000-0xcb10efff] reserved
[0.00] BIOS-e820: [mem 0xcb10f000-0xcb172fff] type 20
[0.00] BIOS-e820: [mem 0xcb173000-0xcb173fff] usable
[0.00] BIOS-e820: [mem 0xcb174000-0xcb181fff] reserved
[0.00] BIOS-e820: [mem 0xcb182000-0xccff] usable
[0.00] BIOS-e820: [mem 0xcd00-0xcdff] reserved
[0.00] BIOS-e820: [mem 0xd000-0xdfff] reserved
[0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved
[0.00] BIOS-e820: [mem 0xff00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00082fff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.40 by American Megatrends
[0.00] efi:  ACPI=0xc9f72000  ACPI 2.0=0xc9f72000  SMBIOS=0xf 
[0.00] secureboot: Secure boot could not be determined (mode 0)
[0.00] random: fast init done
[0.00] SMBIOS 2.8 present.
[0.00] DMI: Dell Inc. Precision Tower 7810/0KJCC5, BIOS A20 07/26/2017
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] e820: last_pfn = 0x83 max_arch_pfn = 0x4
[0.00] MTRR default type: write-back
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-D write-protect
[0.00]   E-F uncachable
[0.00] MTRR variable ranges enabled:
[0.00]   0 base E000 mask 3FFFE000 uncachable
[0.00]   1 base D000 mask 3000 uncachable
[0.00]   2 base 0300 mask 3F80 uncachable
[0.00]   3 base CE00 mask 3E00 uncachable
[0.00]   4 base E000 mask 3000 write-through
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00]   8 disabled
[0.00]   9 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.00] e820: last_pfn = 0xcd000 max_arch_pfn = 0x4
[0.00] Scanning 1 areas for low memory corruption
[0.00] Base memory trampoline at [(ptrval)] 99000 size 24576
[0.00] Using GB pages for direct mapping
[0.00] BRK [0x60c93e000, 0x60c93efff] PGTABLE
[0.00] BRK [0x60c93f000, 0x60c93] PGTABLE
[0.00] BRK [0x60c94, 0x60c940fff] PGTABLE
[0.00] BRK [0x60c941000, 0x60c941fff] PGTABLE
[0.00] BRK [0x60c942000, 0x60c942fff] PGTABLE
[0.00] BRK [0x60c943000, 0x60c943fff] PGTABLE
[0.00] BRK [0x60c944000, 0x60c944fff] PGTABLE
[0.00] BRK [0x60c945000, 0x60c945fff] PGTABLE
[0.00] RAMDISK: [mem 0x31b2d000-0x34d8dfff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0xC9F72000 24 (v02 DELL  )
[0.00] ACPI: XSDT 0xC9F72098 B4 (v01 DELL   CBX3 
01072009 AMI  00010013)
[0.00] ACPI: FACP 0xC9F9DEC8 00010C (v05 DELL   CBX3 
01072009 AMI  00010013)
[0.00] ACPI: DSDT 0xC9F721E0 02BCE1 (v02 DELL   

[Touch-packages] [Bug 1752681] Re: wireless disconnect

[Marco Giannini]

I encounter the same problem with the daily Xubuntu 18.04 and Ubuntu MATE 18.04 
of March 5, 2018. The connection via ethernet cable does not work unless I 
disable the ipv6.
In practice I have to set the Method to Ignore in IPV6 Settings to navigate.

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

Title:
  wireless disconnect

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  There are many problems reported about random and quick
  disconnect/reconnect of the wireless connection in ubuntu. Some say,
  disabling the ipv6 is the solution but it isn't!

  I really do want to find a way to debug what happens that the wireless
  connection drops randomly. But I couldn't find a tool for that.

  The output of the following commands are attached:
  uname -a
  ifconfig
  cat /proc/sys/net/ipv6/conf/all/disable_ipv6
  iwconfig
  lsmod
  dmesg

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

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

[Touch-packages] [Bug 1752681] Re: wireless disconnect

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  wireless disconnect

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  There are many problems reported about random and quick
  disconnect/reconnect of the wireless connection in ubuntu. Some say,
  disabling the ipv6 is the solution but it isn't!

  I really do want to find a way to debug what happens that the wireless
  connection drops randomly. But I couldn't find a tool for that.

  The output of the following commands are attached:
  uname -a
  ifconfig
  cat /proc/sys/net/ipv6/conf/all/disable_ipv6
  iwconfig
  lsmod
  dmesg

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

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

[Touch-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[Launchpad Bug Tracker]

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

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

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
     Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
     Status: "Running"
     CGroup: /system.slice/bluetooth.service
     └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
  1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
   hci0 24:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  Thanking you in anticipation
  

[Touch-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[Launchpad Bug Tracker]

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

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

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
     Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
     Status: "Running"
     CGroup: /system.slice/bluetooth.service
     └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
  1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
   hci0 24:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  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 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  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

  Thanking you in 

[Touch-packages] [Bug 1752928] Re: [FFe] GNOME 3.28

[Jeremy Bicha]

** Description changed:

  Feature Freeze Justification
  
  Evolution was delayed to not intertangle transitions.
  gnome-shell was released late upstream.
  gnome-control-center & gnome-shell were waiting for a subject matter expert 
to return from holiday.
  Shotwell got overlooked but plans to release at the same time as GNOME.
  
  GNOME prefers us to not mix and match components from different versions
  as much as possible.
  
  GNOME 3.28.0 release is just over a week away
  
  Affected Packages
  -
  DONE: evolution transition LP: #1752578
  DONE: gnome-shell and mutter LP: #1751070
  DONE: shotwell
- gnome-settings-daemon LP: #1750174
+ DONE: gnome-settings-daemon LP: #1750174
+ DONE: gnome-session
  gnome-control-center  LP: #1750174
- gnome-session
  
  gnome-games, retro-gtk & libmanette (libmanette released yesterday with
  updated library name, waiting on new retro-gtk release expected any day)

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

Title:
  [FFe] GNOME 3.28

Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  Feature Freeze Justification
  
  Evolution was delayed to not intertangle transitions.
  gnome-shell was released late upstream.
  gnome-control-center & gnome-shell were waiting for a subject matter expert 
to return from holiday.
  Shotwell got overlooked but plans to release at the same time as GNOME.

  GNOME prefers us to not mix and match components from different
  versions as much as possible.

  GNOME 3.28.0 release is just over a week away

  Affected Packages
  -
  DONE: evolution transition LP: #1752578
  DONE: gnome-shell and mutter LP: #1751070
  DONE: shotwell
  DONE: gnome-settings-daemon LP: #1750174
  DONE: gnome-session
  gnome-control-center  LP: #1750174

  gnome-games, retro-gtk & libmanette (libmanette released yesterday
  with updated library name, waiting on new retro-gtk release expected
  any day)

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

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

[Touch-packages] [Bug 1753509] Re: avahi-daemon adds/installs every printer on network

[Sebastien Bacher]

** Package changed: avahi (Ubuntu) => cups (Ubuntu)

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

Title:
  avahi-daemon adds/installs every printer on network

Status in cups package in Ubuntu:
  New

Bug description:
  When connected to a network, avahi-daemon adds & installs all printer
  on a network without being prompted.  This is not desired behaviour.
  Discovery of the printers is good, but not automatic installation &
  addition.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  5 09:29:05 2018
  InstallationDate: Installed on 2017-09-29 (157 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1753059] Re: package ntp 1:4.2.8p10+dfsg-5ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

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

Title:
  package ntp 1:4.2.8p10+dfsg-5ubuntu3.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in ntp package in Ubuntu:
  New

Bug description:
  Issue with package install was reported by system after using Software
  Updater to install new updates on Lubuntu 17.10.  Equipment is a Dell
  Optiplex GX620.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sat Mar  3 02:32:57 2018
  DuplicateSignature:
   package:ntp:1:4.2.8p10+dfsg-5ubuntu3.2
   Installing new version of config file /etc/apparmor.d/usr.sbin.ntpd ...
   Segmentation fault (core dumped)
   dpkg: error processing package ntp (--configure):
subprocess installed post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2017-12-30 (62 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=f42c87eb-f326-4389-a256-d2a9d596508e ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p10+dfsg-5ubuntu3.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1753097] Re: package linux-image-extra-4.4.0-112-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-4.4.0-112-generic (not installed) failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  While I was running the update, there was no space on the /boot
  partition, and that finally resulted in Kernel breakage of an already
  existing version (this one).

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-112-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eswaramoorthi   1948 F pulseaudio
   /dev/snd/controlC0:  eswaramoorthi   1948 F pulseaudio
  Date: Sat Mar  3 08:45:43 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=d321ef13-6b36-425d-b776-761d63417431
  MachineType: LENOVO 80RK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-112-generic (not installed) failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/16/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E0CN23WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Nano 4B6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K13455 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 100-14IBD
  dmi.modalias: 
dmi:bvnLENOVO:bvrE0CN23WW:bd09/16/2015:svnLENOVO:pn80RK:pvrLenovoideapad100-14IBD:rvnLENOVO:rnNano4B6:rvrSDK0K13455WIN:cvnLENOVO:ct10:cvrLenovoideapad100-14IBD:
  dmi.product.name: 80RK
  dmi.product.version: Lenovo ideapad 100-14IBD
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1747460] Re: [MIR] py-macaroon-bakery, protobuf, pyrfc3339

[Mathieu Trudel-Lapierre]

python-nacl should be reviewed by the Security Team since it deals with
crypto, otherwise it looks fine to me. I have not done an in-depth code
review of the upstream source.

** Changed in: python-nacl (Ubuntu)
   Status: New => Incomplete

** Changed in: python-nacl (Ubuntu)
 Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team 
(ubuntu-security)

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

Title:
  [MIR] py-macaroon-bakery, protobuf, pyrfc3339

Status in protobuf package in Ubuntu:
  Invalid
Status in py-macaroon-bakery package in Ubuntu:
  Fix Committed
Status in pyrfc3339 package in Ubuntu:
  Fix Released
Status in python-nacl package in Ubuntu:
  Incomplete

Bug description:
  py-macaroon-bakery
  ==

  1. Availability: all

  2. Rationale:
  Macaroons is a new form of authorization mechanism. The macaroon bakery 
builds on pymacaroons, which allows it working at a higher level.

  In order for MAAS (and other projects) to support macaroon based
  authentication, this needs to be in main. This will allow projects to
  support remote/centralized authentication based on macaroons.

  3. Security:
  No CVE's

  4. QA:
  0 bugs in debian/ubuntu

  5. UI standards:
  None

  6. Dependencies:

  Dependencies in universe:
   - python3-pymacaroons (MIR LP: #1746772)
   - python3-nacl
   - python3-protobuf
   - python3-rfc3339

  7. Standards:
  No lintian errors.

  Packaged with debhelper. Source format is 3.0 (quilt)

  Standards version: 4.4.1

  8. Maintenance:
  Easy.

  9. Background information:
  This is a required dependency to implement third party/centralized 
authentication alongside with pymacaroons. This is a new dependency that's 
required by MAAS.

  python3-protobuf
  ==

  1. Availability: any

  2. Rationale:
  Dependency of python3-macaroonbakery. The library from this same source 
package, libprotobuf10, is already in main.

  3. Security:
  No CVE's

  4. QA:
  protobuf source, 10 bugs in debian, 11 ubuntu

  5. UI standards:
  None

  6. Dependencies:
  All in main

  7. Standards:
  No lintian errors.

  Packaged with debhelper. Source format is 3.0 (quilt)

  Standards version: 3.9.8

  8. Maintenance:
  Easy.

  9. Background information:
  protobuf source already has binaries in main. This is just the python 
bindings that are required by macaroonbakery.

  rfc3339
  ==

  1. Availability: all

  2. Rationale:
  Dependency of python3-macaroonbakery.

  3. Security:
  No CVE's

  4. QA:
  0 bugs in debian/ubuntu

  5. UI standards:
  None

  6. Dependencies:
  All in main

  7. Standards:
  No lintian errors. 1 warning:
  W: pyrfc3339 source: ancient-standards-version 3.9.6 (released 2014-09-17) 
(current is 4.1.3)

  Packaged with debhelper. Source format is 3.0 (quilt)

  8. Maintenance:
  Easy.

  9. Background information:
  Parser and generator of RFC 3339-compliant timestamps. This is a dependency 
for python3-macaroonbakery.

  
  python-nacl
  ==

  1. Availability: any

  2. Rationale:
  Dependency of python3-macaroonbakery.

  3. Security:
  No CVE's

  4. QA:
  0 bugs in debian/ubuntu

  5. UI standards:
  None

  6. Dependencies:
  All in main

  7. Standards:
  No lintian errors.

  Uses standards version 3.9.8

  Packaged with debhelper. Source format is 3.0 (quilt)

  8. Maintenance:
  Easy.

  9. Background information:
  PyNaCl is a Python binding to the Networking and Cryptography library. This 
is a dependency for python3-macaroonbakery.

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

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

[Touch-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: Incomplete => Fix Committed

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Fix Committed
Status in makedumpfile source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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

[Touch-packages] [Bug 1753509] Re: avahi-daemon adds/installs every printer on network

[cement_head]

** Summary changed:

- avahi-daemon adds/installs every printer on netwrok
+ avahi-daemon adds/installs every printer on network

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

Title:
  avahi-daemon adds/installs every printer on network

Status in avahi package in Ubuntu:
  New

Bug description:
  When connected to a network, avahi-daemon adds & installs all printer
  on a network without being prompted.  This is not desired behaviour.
  Discovery of the printers is good, but not automatic installation &
  addition.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  5 09:29:05 2018
  InstallationDate: Installed on 2017-09-29 (157 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1662137] Re: 16.04 recovery shell works only for two minutes

[Etienne Papegnies]

** Tags added: rls-bb-incoming

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

Title:
  16.04 recovery shell works only for two minutes

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Selecting "Rescue" shell from the "Advanced options" menu in grub
  enters the "friendly-recovery" service and allows to drop into a root
  shell.  After ~120 seconds, systemd sees a timeout and starts another
  "friendly-recovery" whiptail process.  This and the running shell now
  compete for tty access (input and output) thus making the shell nearly
  unusable.

  Diagnosing this, it becomes clear that in the first root shell entered
  from friendly-recovery, "systemctl list-jobs" lists the generated
  "wait for disk" tasks for the /boot partition and the swap partition
  still to be running.  Only when they run into a timeout, the next
  friendly-recovery is spawned.  I'll attach a log session for such a
  boot that has two manual "logger" entries in it:

  Feb 06 10:54:57 harry root[605]: now in root shell from friendly-recovery
  ...
  Feb 06 10:56:41 harry root[1254]: now running in parallel

  This clearly shows the timing of the startup.

  I have no idea why the "wait for disk" units run into a timeout as the
  system boots correctly in the "non-rescue" mode.  I'll further attach
  a "systemd-analyze blame" from a regular bootup to show that there is
  no trace of such a timeout to be found.

  Furthermore i do have this behaviour on a real machine and on an
  (independent) VM, so affects more than the machine the bug was
  reported from.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu16
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb  6 11:02:37 2017
  InstallationDate: Installed on 2015-03-27 (681 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic 
root=UUID=310be2be-96ea-4fe9-b929-75605e718fdc ro resume=/dev/sda6 
loop.max_part=63 quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-12-01 (66 days ago)
  dmi.bios.date: 12/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.22
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4A
  dmi.chassis.asset.tag: 617H
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1753042] Re: package python3-apt 1.1.0~beta1ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python3-apt 1.1.0~beta1ubuntu0.16.04.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in python-apt package in Ubuntu:
  New

Bug description:
  don't install properly

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-apt 1.1.0~beta1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Feb 28 23:52:31 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-08-16 (199 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: python-apt
  Title: package python3-apt 1.1.0~beta1ubuntu0.16.04.1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

[Andrew Cloke]

** Tags removed: triage-a
** Tags added: triage-g

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Fix Committed
Status in makedumpfile source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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

[Touch-packages] [Bug 1753100] Re: package python-protobuf 2.6.1-1.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 protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1753100

Title:
  package python-protobuf 2.6.1-1.3 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in protobuf package in Ubuntu:
  New

Bug description:
  No idea what to write here...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-protobuf 2.6.1-1.3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sat Mar  3 14:02:41 2018
  DpkgHistoryLog:
   Start-Date: 2018-03-03  14:01:38
   Commandline: aptdaemon role='role-upgrade-system' sender=':1.84'
   Install: libfarstream-0.2-5:i386 (0.2.7-0ubuntu1, automatic), 
libpurple0:i386 (1:2.10.12-0ubuntu5.2, automatic)
   Upgrade: update-notifier-common:i386 (3.168.7, 3.168.8), 
unity-scope-gdrive:i386 (0.9+13.10.20130723-0ubuntu1, 
0.9+16.04.20151125-0ubuntu1), python-wsgi-intercept:i386 (0.5.1-1, 1.1.2-2), 
usb-modeswitch-data:i386 (20140327-1, 20151101-1), libpurple-bin:i386 
(1:2.10.9-0ubuntu3.4, 1:2.10.12-0ubuntu5.2), ttf-liberation:i386 (1.07.3-3, 
1.07.4-1), usb-modeswitch:i386 (2.1.1+repack0-1ubuntu1, 
2.2.5+repack0-1ubuntu1), sessioninstaller:i386 (0.20+bzr141-0ubuntu4, 
0.20+bzr150-0ubuntu4.1), update-notifier:i386 (3.168.7, 3.168.8)
  DuplicateSignature:
   package:python-protobuf:2.6.1-1.3
   Processing triggers for ureadahead (0.100.0-19) ...
   ureadahead will be reprofiled on next reboot
   dpkg: error processing package python-protobuf (--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 2011-07-06 (2431 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: protobuf
  Title: package python-protobuf 2.6.1-1.3 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to xenial on 2018-03-02 (0 days ago)

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

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

[Touch-packages] [Bug 1753129] Re: package ncurses-term 6.0+20160213-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

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

Title:
  package ncurses-term 6.0+20160213-1ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in ncurses package in Ubuntu:
  New

Bug description:
  package ncurses-term 6.0+20160213-1ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ncurses-term 6.0+20160213-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  AptOrdering:
   gnome-disk-utility: Install
   ncurses-term: Configure
   gnome-disk-utility: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Mar  3 11:37:55 2018
  Dependencies:
   
  DpkgHistoryLog:
   Start-Date: 2018-03-03  11:37:53
   Commandline: aptdaemon role='role-commit-packages' sender=':1.84'
   Upgrade: gnome-disk-utility:amd64 (3.18.3.1-1ubuntu1, 3.18.3.1-1ubuntu1.1)
  DuplicateSignature:
   package:ncurses-term:6.0+20160213-1ubuntu1
   Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
   dpkg: error processing package ncurses-term (--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-02-03 (27 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: ncurses
  Title: package ncurses-term 6.0+20160213-1ubuntu1 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/ncurses/+bug/1753129/+subscriptions

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

[Touch-packages] [Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  Fix Released
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Released
Status in iproute2 source package in Xenial:
  Fix Released
Status in iproute2 source package in Zesty:
  Won't Fix
Status in iproute2 source package in Artful:
  Fix Released

Bug description:
  [Impact]
  When a nic has a long enough name such that there is no space between the 
name and the ":" in /proc/net/igmp, ip maddr show dev  will miss the IPV4 
addresses which is otherwise shown with "ip maddr show".

  This is inconsistent behavior and can break scripts and tests, as
  shown in this bug's original description.

  Three patches from upstream were taken to fix this bug, and they were used 
individually instead of being merged into one single patch so it's easier to 
track and recognize authorship:
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=530903dd9003492edb0714e937ad4a5d1219e376
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=b48a1161f5f9b6a0cda399a224bbbf72eba4a5c6
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=21503ed2af233ffe795926f6641ac84ec1b15bf9

  [Test Case]
  * deploy the ubuntu release under test. Please use bare metal or a VM instead 
of containers, because the ip tool parses a file in /proc. Make sure iproute2 
is installed:
  sudo apt install iproute2

  * Run these commands to setup a dummy interface with a long name and
  an IPv4 address. Please change the address if it conflicts with a real
  network you might have available on that machine:

  sudo ip link add dummylongnic0 type dummy
  sudo ip addr add 192.168.199.10/24 dev dummylongnic0
  sudo ip link set dev dummylongnic0 up

  * Compare the output of these two commands with regards to the dummylongnic0 
interface:
  sudo ip maddr show
  sudo ip maddr show dev dummylongnic0

  * With the buggy iproute2 package installed, the more specific output "ip 
maddr show dev dummylongnic0" should lack the "inet 224.0.0.1" line:
  ip maddr show dev dummylongnic0
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet6 ff02::1
inet6 ff01::1

  
  Whereas the less specific command, which lists all interfaces, will have it 
listed for dummylongnic0:
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet  224.0.0.1
inet6 ff02::1
inet6 ff01::1

  
  * With the fixed iproute2 package, all dummylongnic0 addresses will be 
present in both outputs.

  
  [Regression Potential]
  In the end, the ip tool is parsing a text file produced by the kernel. As 
most parsing done in C, it's pretty low level and sensitive to changes in the 
file it's reading.

  [Other Info]
  I suggest to conduct the tests in VMs instead of containers (LXD) because the 
ip maddr command parses /proc/net/igmp, which is produced by the kernel. If you 
use a container, then it's the host's kernel that will be providing that file 
and it might not be the same as with the native kernel of that particular 
ubuntu release.

  --- Original description ---
  Attn. Canonical:  Please make sure that the existing iproute2 package gets 
updated with the two referenced patches as the missing information is impacting 
our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data

  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8286-42A

  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.0.0.252
  inet  224.0.0.1
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
  ...

  root@roselp1:~# ip maddr show dev enP20p96s0
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1

  == Comment: #12 - David Z. Dai  - 2017-11-13 15:07:32 ==

  I found upstream already 

[Touch-packages] [Bug 1753352] Re: package linux-image-extra-4.4.0-116-generic 4.4.0-116.140 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-4.4.0-116-generic 4.4.0-116.140 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  dpkg -l | grep linux-image
  ii  linux-image-4.4.0-112-generic   4.4.0-112.135 
   amd64Linux kernel image for version 4.4.0 on 64 bit x86 
SMP
  ii  linux-image-4.4.0-116-generic   4.4.0-116.140 
   amd64Linux kernel image for version 4.4.0 on 64 bit x86 
SMP
  ii  linux-image-extra-4.4.0-112-generic 4.4.0-112.135 
   amd64Linux kernel extra modules for version 4.4.0 on 64 
bit x86 SMP
  iF  linux-image-extra-4.4.0-116-generic 4.4.0-116.140 
   amd64Linux kernel extra modules for version 4.4.0 on 64 
bit x86 SMP
  iU  linux-image-generic   

  uname -r
  4.4.0-116-generic

  The above after rebooting to *-116.
  System seems to be working; I will try to repair the failed installation soon.

  There has been a constant issue where the installer tries to recover
  long-uninstalled initram elements such as initrd.img-4.2.0-16-generic
  (and later) filling /boot, etc. I have manually removed these files
  from /boot to an "obsolete" folder to allow df -h to report enough
  space.

  The system seems to be reading outdated info from an 'initram.conf' or
  similar file and I believe this may be the fault, or part of it. I can
  manually edit out references to earlier kernels when I find the file.

  Do you have any suggestions?

  Advanced user

  CM BRADLEY
  05/03/2018
  AU CDST 13:25:00

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  administrator   2025 F pulseaudio
   /dev/snd/controlC0:  administrator   2025 F pulseaudio
   /dev/snd/seq:timidity   1329 F timidity
  Date: Mon Mar  5 13:03:41 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=abf7583a-8eda-4113-a8cd-1f301a7d7f06
  InstallationDate: Installed on 2016-04-26 (677 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-116-generic 4.4.0-116.140 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: EP45-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd01/27/2010:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP45-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: Triaged => Fix Committed

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released

Bug description:
  [Impact]
  lscpu fails to list CPU max and min frequencies if some CPUs are guarded.

  [Regression potential]
  Isolated change to lscpu min/max CPU frequency output, so the worst that 
could happen is that it fails to work elsewhere.

  [Test case]
  1. Clone https://github.com/open-power/op-test-framework
  2. Run this command to GUARD the cpu.
  ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert
  3. Repeat again, so that multiple CPUs are guarded.
  4. Run lscpu
  5. Observe that no CPU frequencies are displayed:
  CPU max MHz: (null)
  CPU min MHz: (null)
  6. Install util-linux from -proposed.
  7. Run lscpu again
  8. Observe that max and min CPU frequencies are correctly displayed.

  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies

  Contact Information = ppaid...@in.ibm.com

  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = PowerNV 8284-22A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL

  Stack trace output:
   no

  Oops output:
   no

  Userspace tool common name: lscpu

  Userspace rpm: util-linux

  The userspace tool has the following bit modes: 64-bit

  System Dump Info:
    The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na

  *Additional Instructions for ppaid...@in.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 

[Touch-packages] [Bug 1742941] Re: zlib: improve crc32 performance on P8

[Manoj Iyer]

IBM, Can you please update this bug when this patch lands upstream?

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

Title:
  zlib: improve  crc32 performance on P8

Status in The Ubuntu-power-systems project:
  Incomplete
Status in zlib package in Ubuntu:
  New

Bug description:
  Calculate the checksum of data that is 16 byte aligned and a multiple
  of  16 bytes.

  The first step is to reduce it to 1024 bits. We do this in 8 parallel
   chunks in order to mask the latency of the vpmsum instructions. If we
   have more than 32 kB of data to checksum we repeat this step multiple
   times, passing in the previous 1024 bits.

   The next step is to reduce the 1024 bits to 64 bits. This step adds
   32 bits of 0s to the end - this matches what a CRC does. We just
   calculate constants that land the data in this 32 bits.

   We then use fixed point Barrett reduction to compute a mod n over GF(2)
   for n = CRC using POWER8 instructions. We use x = 32.

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

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

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

[Touch-packages] [Bug 1747460] Re: [MIR] py-macaroon-bakery, protobuf, pyrfc3339

[Mathieu Trudel-Lapierre]

py-macaroons-bakery looks good to me; MIR approved.

** Changed in: py-macaroon-bakery (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  [MIR] py-macaroon-bakery, protobuf, pyrfc3339

Status in protobuf package in Ubuntu:
  Invalid
Status in py-macaroon-bakery package in Ubuntu:
  Fix Committed
Status in pyrfc3339 package in Ubuntu:
  Fix Released
Status in python-nacl package in Ubuntu:
  New

Bug description:
  py-macaroon-bakery
  ==

  1. Availability: all

  2. Rationale:
  Macaroons is a new form of authorization mechanism. The macaroon bakery 
builds on pymacaroons, which allows it working at a higher level.

  In order for MAAS (and other projects) to support macaroon based
  authentication, this needs to be in main. This will allow projects to
  support remote/centralized authentication based on macaroons.

  3. Security:
  No CVE's

  4. QA:
  0 bugs in debian/ubuntu

  5. UI standards:
  None

  6. Dependencies:

  Dependencies in universe:
   - python3-pymacaroons (MIR LP: #1746772)
   - python3-nacl
   - python3-protobuf
   - python3-rfc3339

  7. Standards:
  No lintian errors.

  Packaged with debhelper. Source format is 3.0 (quilt)

  Standards version: 4.4.1

  8. Maintenance:
  Easy.

  9. Background information:
  This is a required dependency to implement third party/centralized 
authentication alongside with pymacaroons. This is a new dependency that's 
required by MAAS.

  python3-protobuf
  ==

  1. Availability: any

  2. Rationale:
  Dependency of python3-macaroonbakery. The library from this same source 
package, libprotobuf10, is already in main.

  3. Security:
  No CVE's

  4. QA:
  protobuf source, 10 bugs in debian, 11 ubuntu

  5. UI standards:
  None

  6. Dependencies:
  All in main

  7. Standards:
  No lintian errors.

  Packaged with debhelper. Source format is 3.0 (quilt)

  Standards version: 3.9.8

  8. Maintenance:
  Easy.

  9. Background information:
  protobuf source already has binaries in main. This is just the python 
bindings that are required by macaroonbakery.

  rfc3339
  ==

  1. Availability: all

  2. Rationale:
  Dependency of python3-macaroonbakery.

  3. Security:
  No CVE's

  4. QA:
  0 bugs in debian/ubuntu

  5. UI standards:
  None

  6. Dependencies:
  All in main

  7. Standards:
  No lintian errors. 1 warning:
  W: pyrfc3339 source: ancient-standards-version 3.9.6 (released 2014-09-17) 
(current is 4.1.3)

  Packaged with debhelper. Source format is 3.0 (quilt)

  8. Maintenance:
  Easy.

  9. Background information:
  Parser and generator of RFC 3339-compliant timestamps. This is a dependency 
for python3-macaroonbakery.

  
  python-nacl
  ==

  1. Availability: any

  2. Rationale:
  Dependency of python3-macaroonbakery.

  3. Security:
  No CVE's

  4. QA:
  0 bugs in debian/ubuntu

  5. UI standards:
  None

  6. Dependencies:
  All in main

  7. Standards:
  No lintian errors.

  Uses standards version 3.9.8

  Packaged with debhelper. Source format is 3.0 (quilt)

  8. Maintenance:
  Easy.

  9. Background information:
  PyNaCl is a Python binding to the Networking and Cryptography library. This 
is a dependency for python3-macaroonbakery.

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

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

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space

[Raul Benalcazar]

** Changed in: initramfs-tools
 Assignee: (unassigned) => Raul  Benalcazar (raulbenalcazar24)

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space

Status in initramfs-tools:
  Confirmed
Status in Ubuntu Software Center:
  Invalid
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

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

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

[Touch-packages] [Bug 1753509] [NEW] avahi-daemon adds/installs every printer on netwrok

[cement_head]

Public bug reported:

When connected to a network, avahi-daemon adds & installs all printer on
a network without being prompted.  This is not desired behaviour.
Discovery of the printers is good, but not automatic installation &
addition.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar  5 09:29:05 2018
InstallationDate: Installed on 2017-09-29 (157 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: avahi
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  avahi-daemon adds/installs every printer on netwrok

Status in avahi package in Ubuntu:
  New

Bug description:
  When connected to a network, avahi-daemon adds & installs all printer
  on a network without being prompted.  This is not desired behaviour.
  Discovery of the printers is good, but not automatic installation &
  addition.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  5 09:29:05 2018
  InstallationDate: Installed on 2017-09-29 (157 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

[Thadeu Lima de Souza Cascardo]

The systemd update fixes the problem for me on artful.

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

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

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Fix Committed
Status in makedumpfile source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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

[Touch-packages] [Bug 1719038] Re: X Server crashes during log in VM since 16.04.2

[Gannet]

Here is a patch which fixes the issue:
https://cgit.freedesktop.org/xorg/driver/xf86-video-
qxl/commit/?id=ee8f904ab0d590c741e640e9548c472e6a58b3cc

** Tags added: patch

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

Title:
  X Server crashes during log in VM since 16.04.2

Status in X.Org X server:
  In Progress
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  If I change screen resolution in my VM with Kubuntu 16.04.3 and then
  make log off and then log on X server is crashes doesn't able me to
  log in.

  Please, look in Xorg.0.log.old for backtrace.

  Also the appropriate report on freedesktop.org:
  https://bugs.freedesktop.org/show_bug.cgi?id=102554

  Host:
  Kubuntu 17.04
  Linux 4.13.2
  libvirt-bin 3.6.0
  qemu 2.10

  
  Guest:
  Kubuntu 16.04.3
  Linux 4.10.0-35-generic
  xserver-xorg-video-qxl 0.1.4-3ubuntu3
  xserver-common 1.18.4-0ubuntu0.3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 23 01:27:49 2017
  InstallationDate: Installed on 2016-09-16 (371 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1719038/+subscriptions

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

[Touch-packages] [Bug 1662137] Re: 16.04 recovery shell works only for two minutes

[Etienne Papegnies]

Can confirm @kmputerguy's report.
Seen this bug on multiple hardware configurations, it basically renders the 
rescue mode useless for involved maintenance operations.

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

Title:
  16.04 recovery shell works only for two minutes

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Selecting "Rescue" shell from the "Advanced options" menu in grub
  enters the "friendly-recovery" service and allows to drop into a root
  shell.  After ~120 seconds, systemd sees a timeout and starts another
  "friendly-recovery" whiptail process.  This and the running shell now
  compete for tty access (input and output) thus making the shell nearly
  unusable.

  Diagnosing this, it becomes clear that in the first root shell entered
  from friendly-recovery, "systemctl list-jobs" lists the generated
  "wait for disk" tasks for the /boot partition and the swap partition
  still to be running.  Only when they run into a timeout, the next
  friendly-recovery is spawned.  I'll attach a log session for such a
  boot that has two manual "logger" entries in it:

  Feb 06 10:54:57 harry root[605]: now in root shell from friendly-recovery
  ...
  Feb 06 10:56:41 harry root[1254]: now running in parallel

  This clearly shows the timing of the startup.

  I have no idea why the "wait for disk" units run into a timeout as the
  system boots correctly in the "non-rescue" mode.  I'll further attach
  a "systemd-analyze blame" from a regular bootup to show that there is
  no trace of such a timeout to be found.

  Furthermore i do have this behaviour on a real machine and on an
  (independent) VM, so affects more than the machine the bug was
  reported from.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu16
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb  6 11:02:37 2017
  InstallationDate: Installed on 2015-03-27 (681 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic 
root=UUID=310be2be-96ea-4fe9-b929-75605e718fdc ro resume=/dev/sda6 
loop.max_part=63 quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-12-01 (66 days ago)
  dmi.bios.date: 12/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.22
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4A
  dmi.chassis.asset.tag: 617H
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1752448] Re: error message for unmet dependencies is misleading

[Christophe Malek]

Feel free to word the new message in whatever way you feel is more
correct. The current message is definitely incorrect.

Your suggestion is fine with me:
libcupsimage2 : Depends: libcups2 (= 1.7.2-0ubuntu1.8) but 1.7.2-0ubuntu1.9 
will remain installed.

Whether it is installed or not matters a lot to someone trying to
understand why they are getting an error message. As a package
management utility I'm sure apt should be able to detect what is
installed and give an appropriate message for either case.

If you think adding additional detection would overcomplicate the code then a 
more inclusive message could work too but is a little harder to read:
libcupsimage2 : Depends: libcups2 (= 1.7.2-0ubuntu1.8) but 1.7.2-0ubuntu1.9 is 
to be or will remain installed.

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

Title:
  error message for unmet dependencies is misleading

Status in apt package in Ubuntu:
  New

Bug description:
  When trying to install some older packages on a machine with newer
  packages I get the following message:

  The following packages have unmet dependencies:
   libcupsimage2 : Depends: libcups2 (= 1.7.2-0ubuntu1.8) but 1.7.2-0ubuntu1.9 
is to be installed
   libgfortran3 : Depends: gcc-4.8-base (= 4.8.4-2ubuntu1~14.04.3) but 
4.8.4-2ubuntu1~14.04.4 is to be installed
  E: Unable to correct problems, you have held broken packages. 

  The way the message is worded makes it seem like I was trying to
  install version 1.7.2-0ubuntu1.9 and 4.8.4-2ubuntu1~14.04.4 of the
  above packages.

  In reality, these were the versions of the packages that were already
  installed on the machine.

  This caused a fair bit of confusion when trying to debug the
  situation.

  If you could please reword the error message to be correct. Perhaps
  something along the lines of:

  The following packages have unmet dependencies:
   libcupsimage2 : Depends: libcups2 (= 1.7.2-0ubuntu1.8) but 1.7.2-0ubuntu1.9 
is already installed
   libgfortran3 : Depends: gcc-4.8-base (= 4.8.4-2ubuntu1~14.04.3) but 
4.8.4-2ubuntu1~14.04.4 is already installed
  E: Unable to correct problems, you have held broken packages. 

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.25
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb 28 18:14:25 2018
  InstallationDate: Installed on 2017-11-03 (117 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1752472] Re: [ffe] Implement an Ubuntu Single Sign-on Provider

[Łukasz Zemczak]

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Triaged

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

Title:
  [ffe] Implement an Ubuntu Single Sign-on Provider

Status in gnome-online-accounts:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Add an Ubuntu Single Sing-On provider in gnome-online-accounts. We plan to 
use this inside:
  1) gnome-software
  2) software-properties

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1752472/+subscriptions

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

[Touch-packages] [Bug 1752928] Re: [FFe] GNOME 3.28

[Łukasz Zemczak]

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

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

Title:
  [FFe] GNOME 3.28

Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  Feature Freeze Justification
  
  Evolution was delayed to not intertangle transitions.
  gnome-shell was released late upstream.
  gnome-control-center & gnome-shell were waiting for a subject matter expert 
to return from holiday.
  Shotwell got overlooked but plans to release at the same time as GNOME.

  GNOME prefers us to not mix and match components from different
  versions as much as possible.

  GNOME 3.28.0 release is just over a week away

  Affected Packages
  -
  DONE: evolution transition LP: #1752578
  DONE: gnome-shell and mutter LP: #1751070
  DONE: shotwell
  gnome-settings-daemon LP: #1750174
  gnome-control-center  LP: #1750174
  gnome-session

  gnome-games, retro-gtk & libmanette (libmanette released yesterday
  with updated library name, waiting on new retro-gtk release expected
  any day)

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

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

[Touch-packages] [Bug 1661851] Re: cannot enter rescue or emergency state from running system

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

Title:
  cannot enter rescue or emergency state from running system

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Typing "systemctl rescue" in a running system brings down the system
  and prompts

  Welcome to rescue mode! After logging in, type "journalctl -xb" to view
  system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
  boot into default mode.
  Press Enter for maintenance
  (or press Control-D to continue):

  Unfortunately the system is then completely dead.  No keyboard entry works, 
not even 7 times
  Ctrl-Alt-Del reboot the system.

  I have this behaviour on a real 16.04 system and on a VirtualBox VM.

  On the VM I currently have problems entering rescue mode by GRUB
  selection (different problem to be files separately), so these two
  bugs combined make it impossible for me to enter rescue mode there.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu16
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Feb  4 16:01:01 2017
  InstallationDate: Installed on 2015-03-27 (680 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic 
root=UUID=310be2be-96ea-4fe9-b929-75605e718fdc ro resume=/dev/sda6 
loop.max_part=63 quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-12-01 (64 days ago)
  dmi.bios.date: 12/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.22
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4A
  dmi.chassis.asset.tag: 617H
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

[Krister]

=> lspci -k
00:00.0 Host bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
DMI2 (rev 01)
Subsystem: Dell Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2
00:01.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 1 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:01.1 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 1 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:02.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 2 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:03.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 3 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:03.1 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 3 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:03.2 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 3 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:03.3 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D 
PCI Express Root Port 3 (rev 01)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:05.0 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D Map/VTd_Misc/System Management (rev 01)
00:05.1 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D IIO Hot Plug (rev 01)
00:05.2 System peripheral: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 
v4/Xeon D IIO RAS/Control Status/Global Errors (rev 01)
00:05.4 PIC: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC 
(rev 01)
Subsystem: Dell Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC
00:11.0 Unassigned class [ff00]: Intel Corporation C610/X99 series chipset SPSR 
(rev 05)
Subsystem: Dell C610/X99 series chipset SPSR
00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host 
Controller (rev 05)
Subsystem: Dell C610/X99 series chipset USB xHCI Host Controller
Kernel driver in use: xhci_hcd
00:16.0 Communication controller: Intel Corporation C610/X99 series chipset MEI 
Controller #1 (rev 05)
Subsystem: Dell C610/X99 series chipset MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
00:16.2 IDE interface: Intel Corporation C610/X99 series chipset IDE-r 
Controller (rev 05)
Subsystem: Dell C610/X99 series chipset IDE-r Controller
Kernel driver in use: ata_generic
Kernel modules: pata_acpi
00:16.3 Serial controller: Intel Corporation C610/X99 series chipset KT 
Controller (rev 05)
Subsystem: Dell C610/X99 series chipset KT Controller
Kernel driver in use: serial
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 
05)
Subsystem: Dell Ethernet Connection I217-LM
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced 
Host Controller #2 (rev 05)
Subsystem: Dell C610/X99 series chipset USB Enhanced Host Controller
Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio 
Controller (rev 05)
Subsystem: Dell C610/X99 series chipset HD Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root 
Port #1 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root 
Port #2 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.2 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root 
Port #3 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation C610/X99 series chipset USB Enhanced 
Host Controller #1 (rev 05)
Subsystem: Dell C610/X99 series chipset USB Enhanced Host Controller
Kernel driver in use: ehci-pci
00:1f.0 ISA bridge: Intel Corporation C610/X99 series chipset LPC Controller 
(rev 05)
Subsystem: Dell C610/X99 series chipset LPC Controller
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation C610/X99 series chipset 6-Port SATA 
Controller [AHCI mode] (rev 05)
Subsystem: Dell C610/X99 series chipset 6-Port SATA Controller [AHCI 
mode]
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.3 SMBus: Intel Corporation C610/X99 series chipset SMBus Controller (rev 
05)
Subsystem: Dell C610/X99 series 

[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

[Francis Ginther]

** Tags added: id-5a9cf9e8c002ae1b9f6de652

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

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  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
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (0 days ago)
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.

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

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

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

[Łukasz Zemczak]

Hello Jeff, or anyone else affected,

Accepted isc-dhcp into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.3.3-5ubuntu12.10 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!

** Changed in: isc-dhcp (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-trusty

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

Title:
  dhclient-script fails to wait for link-local address

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Zesty:
  Won't Fix
Status in isc-dhcp source package in Artful:
  Fix Committed
Status in isc-dhcp source package in Bionic:
  Fix Released
Status in isc-dhcp package in Debian:
  New

Bug description:
  [impact]

  bug 1633479 made a change to isc-dhcp to wait for an interface's link-local 
ipv6 address to switch from 'tentative' to normal, because all link-local 
addresses briefly go through a 'tentative' state while the kernel is performing 
ipv6 link-local 'duplicate address detection' (DAD).  While in the 'tentative' 
state, dhclient can't take over the interface and send out
  dhcpv6 requests; it must wait until DAD completes.

  However, the change made in that bug does not account for the case
  where the 'tentative' check is done before the interface has even set
  up a link-local address; its case statement assumes if there is no
  'tentative' or 'dadfailed' string in the output, the link-local
  address is ready to use.  When the address check finds no address at
  all, this will return as successful, even though it shouldn't, and
  dhclient will fail to get the dhcpv6 address.

  [test case]

  on a system that is configured for dhcpv6 on one or more of its
  interfaces, repeatedly try to get the dhcpv6 address.  For interfaces
  that are slower to actually set up their initial tentative link-local
  address, they will occasionally fail, since the current code is a race
  between the kernel adding the tentative link-local address, and the
  dhclient-script.linux code checking the interface for a tentative
  address.

  with the patch to correct this, even interfaces slow to add their
  tentative link-local address should correctly wait for the address to
  get added, and then transition from tentative to normal, and then
  begin the dhcpv6 process.

  [regression potential]

  errors in this function can cause dhclient to fail to get a ipv6
  address for an interface; regression would happen if this patch makes
  it fail more than it already is failing, but would not cause other
  failures or problems after getting an ipv6 address; this patch will
  affect only startup-time.

  additionally, the current behavior of dhclient when using an interface
  that has no link-local address after being brought up is to exit
  immediately; while after this patch dhclient will wait ~6 seconds
  before exiting (while waiting for the interface to get a non-tentative
  link-local addr).  This is the point of this bug, that some NIC hw
  doesn't show a tentative link-local addr immediately after coming up.
  However, if dhclient -6 is configured to run on an interface without
  any link state at all (e.g. its physical cable is unplugged), then
  while before dhclient would exit immediately with error, it now waits
  6 seconds.  If the system is misconfigured like that, or if someone
  pulls a cable and reboots, then system boot will be delayed an extra 6
  seconds.  However, that short delay for misconfigured/broken systems
  seems acceptable to me, in exchange for allowing dhclient to work with
  slightly slow NIC hw.  Additionally, consider that if the problem is
  instead no dhcpv6 server, dhclient -6 will wait a much, much longer
  amount of time for a dhcpv6 response before giving up.

  
  [other info]

  related bug 1633479

  [original description]

  Summary:
  

  If a interface does not yet have a link-local 

[Touch-packages] [Bug 1718568] Re: dhclient-script fails to wait for link-local address

[Łukasz Zemczak]

Hello Jeff, or anyone else affected,

Accepted isc-dhcp into artful-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.3.5-3ubuntu2.3 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-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. 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: isc-dhcp (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-artful

** Changed in: isc-dhcp (Ubuntu Xenial)
   Status: In Progress => 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 isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1718568

Title:
  dhclient-script fails to wait for link-local address

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Zesty:
  Won't Fix
Status in isc-dhcp source package in Artful:
  Fix Committed
Status in isc-dhcp source package in Bionic:
  Fix Released
Status in isc-dhcp package in Debian:
  New

Bug description:
  [impact]

  bug 1633479 made a change to isc-dhcp to wait for an interface's link-local 
ipv6 address to switch from 'tentative' to normal, because all link-local 
addresses briefly go through a 'tentative' state while the kernel is performing 
ipv6 link-local 'duplicate address detection' (DAD).  While in the 'tentative' 
state, dhclient can't take over the interface and send out
  dhcpv6 requests; it must wait until DAD completes.

  However, the change made in that bug does not account for the case
  where the 'tentative' check is done before the interface has even set
  up a link-local address; its case statement assumes if there is no
  'tentative' or 'dadfailed' string in the output, the link-local
  address is ready to use.  When the address check finds no address at
  all, this will return as successful, even though it shouldn't, and
  dhclient will fail to get the dhcpv6 address.

  [test case]

  on a system that is configured for dhcpv6 on one or more of its
  interfaces, repeatedly try to get the dhcpv6 address.  For interfaces
  that are slower to actually set up their initial tentative link-local
  address, they will occasionally fail, since the current code is a race
  between the kernel adding the tentative link-local address, and the
  dhclient-script.linux code checking the interface for a tentative
  address.

  with the patch to correct this, even interfaces slow to add their
  tentative link-local address should correctly wait for the address to
  get added, and then transition from tentative to normal, and then
  begin the dhcpv6 process.

  [regression potential]

  errors in this function can cause dhclient to fail to get a ipv6
  address for an interface; regression would happen if this patch makes
  it fail more than it already is failing, but would not cause other
  failures or problems after getting an ipv6 address; this patch will
  affect only startup-time.

  additionally, the current behavior of dhclient when using an interface
  that has no link-local address after being brought up is to exit
  immediately; while after this patch dhclient will wait ~6 seconds
  before exiting (while waiting for the interface to get a non-tentative
  link-local addr).  This is the point of this bug, that some NIC hw
  doesn't show a tentative link-local addr immediately after coming up.
  However, if dhclient -6 is configured to run on an interface without
  any link state at all (e.g. its physical cable is unplugged), then
  while before dhclient would exit immediately with error, it now waits
  6 seconds.  If the system is misconfigured like that, or if someone
  pulls a cable and reboots, then system boot will be delayed an extra 6
  seconds.  However, that short delay for misconfigured/broken systems
  seems acceptable to me, in exchange for allowing dhclient to work with
  slightly slow NIC hw.  Additionally, consider that if the problem is
  instead no dhcpv6 server, dhclient -6 will wait a much, much longer
  amount of time for a dhcpv6 response before giving 

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

[Łukasz Zemczak]

Hello Jeff, or anyone else affected,

Accepted isc-dhcp into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.2.4-7ubuntu12.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-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. 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 isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1718568

Title:
  dhclient-script fails to wait for link-local address

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Zesty:
  Won't Fix
Status in isc-dhcp source package in Artful:
  Fix Committed
Status in isc-dhcp source package in Bionic:
  Fix Released
Status in isc-dhcp package in Debian:
  New

Bug description:
  [impact]

  bug 1633479 made a change to isc-dhcp to wait for an interface's link-local 
ipv6 address to switch from 'tentative' to normal, because all link-local 
addresses briefly go through a 'tentative' state while the kernel is performing 
ipv6 link-local 'duplicate address detection' (DAD).  While in the 'tentative' 
state, dhclient can't take over the interface and send out
  dhcpv6 requests; it must wait until DAD completes.

  However, the change made in that bug does not account for the case
  where the 'tentative' check is done before the interface has even set
  up a link-local address; its case statement assumes if there is no
  'tentative' or 'dadfailed' string in the output, the link-local
  address is ready to use.  When the address check finds no address at
  all, this will return as successful, even though it shouldn't, and
  dhclient will fail to get the dhcpv6 address.

  [test case]

  on a system that is configured for dhcpv6 on one or more of its
  interfaces, repeatedly try to get the dhcpv6 address.  For interfaces
  that are slower to actually set up their initial tentative link-local
  address, they will occasionally fail, since the current code is a race
  between the kernel adding the tentative link-local address, and the
  dhclient-script.linux code checking the interface for a tentative
  address.

  with the patch to correct this, even interfaces slow to add their
  tentative link-local address should correctly wait for the address to
  get added, and then transition from tentative to normal, and then
  begin the dhcpv6 process.

  [regression potential]

  errors in this function can cause dhclient to fail to get a ipv6
  address for an interface; regression would happen if this patch makes
  it fail more than it already is failing, but would not cause other
  failures or problems after getting an ipv6 address; this patch will
  affect only startup-time.

  additionally, the current behavior of dhclient when using an interface
  that has no link-local address after being brought up is to exit
  immediately; while after this patch dhclient will wait ~6 seconds
  before exiting (while waiting for the interface to get a non-tentative
  link-local addr).  This is the point of this bug, that some NIC hw
  doesn't show a tentative link-local addr immediately after coming up.
  However, if dhclient -6 is configured to run on an interface without
  any link state at all (e.g. its physical cable is unplugged), then
  while before dhclient would exit immediately with error, it now waits
  6 seconds.  If the system is misconfigured like that, or if someone
  pulls a cable and reboots, then system boot will be delayed an extra 6
  seconds.  However, that short delay for misconfigured/broken systems
  seems acceptable to me, in exchange for allowing dhclient to work with
  slightly slow NIC hw.  Additionally, consider that if the problem is
  instead no dhcpv6 server, dhclient -6 will wait a much, much longer
  amount of time for a dhcpv6 response before giving up.

  
  [other info]

  related bug 1633479

  [original description]

  Summary:
  

  If a interface does not yet have a link-local address (as it may have
  just been brought up), dhclient -6  will fail. The built-in
  "wait for link-local address" loop does not 

[Touch-packages] [Bug 1753450] [NEW] [MIR] mpg123

[Iain Lane]

Public bug reported:

Availability

Built for all supported architectures. In sync with Debian.

Rationale
=
For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into 
gst-plugins-good. These are installed by default, and so now we can have MP3 
support in the default install. The desktop team would like this feature.

For that, it uses some libraries and we'll need to put them in main.

Security

There are some CVEs in the history of the project.

https://security-tracker.debian.org/tracker/source-package/mpg123
https://people.canonical.com/~ubuntu-security/cve/pkg/mpg123.html

The Ubuntu CVE page lists a 'needed' one which AFAICS is fixed in
1.25.8-1.

Quality assurance
=
Desktop team is subscribed.

Bugs


https://bugs.launchpad.net/ubuntu/+source/mpg123
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes=mpg123

Dependencies

We need libmpg123-0 in main, and this depends on libc6 only.

Standards compliance

4.1.2. debian/rules is slightly complicated because it generates some wrapper 
scripts for some old binary names. Those binaries don't go in a package that we 
need in main.

Maintenance
===
Desktop team will maintain. In Debian this is maintained by the multimedia 
team, which is active. We don't envisage the package diverging from Debian.

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

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

Title:
  [MIR] mpg123

Status in mpg123 package in Ubuntu:
  New

Bug description:
  Availability
  
  Built for all supported architectures. In sync with Debian.

  Rationale
  =
  For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into 
gst-plugins-good. These are installed by default, and so now we can have MP3 
support in the default install. The desktop team would like this feature.

  For that, it uses some libraries and we'll need to put them in main.

  Security
  
  There are some CVEs in the history of the project.

  https://security-tracker.debian.org/tracker/source-package/mpg123
  https://people.canonical.com/~ubuntu-security/cve/pkg/mpg123.html

  The Ubuntu CVE page lists a 'needed' one which AFAICS is fixed in
  1.25.8-1.

  Quality assurance
  =
  Desktop team is subscribed.

  Bugs
  

  https://bugs.launchpad.net/ubuntu/+source/mpg123
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes=mpg123

  Dependencies
  
  We need libmpg123-0 in main, and this depends on libc6 only.

  Standards compliance
  
  4.1.2. debian/rules is slightly complicated because it generates some wrapper 
scripts for some old binary names. Those binaries don't go in a package that we 
need in main.

  Maintenance
  ===
  Desktop team will maintain. In Debian this is maintained by the multimedia 
team, which is active. We don't envisage the package diverging from Debian.

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

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

[Touch-packages] [Bug 1753441] [NEW] [MIR] lame

[Iain Lane]

Public bug reported:

Availability

Built for all supported architectures. In sync with Debian.

Rationale
=
For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into 
gst-plugins-good. These are installed by default, and so now we can have MP3 
support in the default install. The desktop team would like this feature.

For that, it uses some libraries and we'll need to put them in main.

Security

There are some CVEs in the history of the project.

https://security-tracker.debian.org/tracker/source-package/lame
https://people.canonical.com/~ubuntu-security/cve/pkg/lame.html

The Ubuntu CVE page lists some 'needed' ones but from looking at those
ones in Debian they are duplicates and should be fixed already.

Quality assurance
=
Desktop team is subscribed.

Bugs


https://bugs.launchpad.net/ubuntu/+source/lame
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes=lame

I think they are reasonably calm given that this is a well known
project.

Dependencies


We need libmp3lame0 in main, and this depends on libc6 only.

Standards compliance


4.1.1 and dh minimal style rules.

Maintenance
===
Desktop team will maintain. In Debian this is maintained by the multimedia 
team, which is active. We don't envisage the package diverging from Debian.

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

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

Title:
  [MIR] lame

Status in lame package in Ubuntu:
  New

Bug description:
  Availability
  
  Built for all supported architectures. In sync with Debian.

  Rationale
  =
  For the 1.14 series, GStreamer upstream moved MP3 encoding and decoding into 
gst-plugins-good. These are installed by default, and so now we can have MP3 
support in the default install. The desktop team would like this feature.

  For that, it uses some libraries and we'll need to put them in main.

  Security
  
  There are some CVEs in the history of the project.

  https://security-tracker.debian.org/tracker/source-package/lame
  https://people.canonical.com/~ubuntu-security/cve/pkg/lame.html

  The Ubuntu CVE page lists some 'needed' ones but from looking at those
  ones in Debian they are duplicates and should be fixed already.

  Quality assurance
  =
  Desktop team is subscribed.

  Bugs
  

  https://bugs.launchpad.net/ubuntu/+source/lame
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes=lame

  I think they are reasonably calm given that this is a well known
  project.

  Dependencies
  

  We need libmp3lame0 in main, and this depends on libc6 only.

  Standards compliance
  

  4.1.1 and dh minimal style rules.

  Maintenance
  ===
  Desktop team will maintain. In Debian this is maintained by the multimedia 
team, which is active. We don't envisage the package diverging from Debian.

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

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

[Touch-packages] [Bug 1753433] [NEW] jackd crashed with SIGABRT

[David Kastrup]

Public bug reported:

Probably happened in connection with shotcut crashing while being
connected to Jackd.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: jackd2 1.9.12~dfsg-2
ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
Uname: Linux 4.15.0-10-lowlatency x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Mon Mar  5 11:12:22 2018
ExecutablePath: /usr/bin/jackd
InstallationDate: Installed on 2011-10-14 (2333 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/bin/jackd -T -ndefault -t 200 -p 2048 -R -T -d alsa -n 2 -r 
96000 -p 512 -d hw:Intel,0
Signal: 6
SourcePackage: jackd2
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 __cxa_rethrow () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 () at /usr/lib/x86_64-linux-gnu/libjackserver.so.0
Title: jackd crashed with SIGABRT
UpgradeStatus: Upgraded to bionic on 2018-01-23 (41 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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


** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages

** Information type changed from Private to Public

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

Title:
  jackd crashed with SIGABRT

Status in jackd2 package in Ubuntu:
  New

Bug description:
  Probably happened in connection with shotcut crashing while being
  connected to Jackd.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: jackd2 1.9.12~dfsg-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Mon Mar  5 11:12:22 2018
  ExecutablePath: /usr/bin/jackd
  InstallationDate: Installed on 2011-10-14 (2333 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  ProcCmdline: /usr/bin/jackd -T -ndefault -t 200 -p 2048 -R -T -d alsa -n 2 -r 
96000 -p 512 -d hw:Intel,0
  Signal: 6
  SourcePackage: jackd2
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libjackserver.so.0
  Title: jackd crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-01-23 (41 days ago)
  UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

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

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

[Touch-packages] [Bug 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)

[Guilherme G. Piccoli]

Thanks Dan.

About cgmanager: if we don't have it installed, it does not affect
memory of systemd-logind tool per se. What happens, IMHO, is even more
severe: we don't free/de-allocate sysfs cgroup paths for sessions. So,
in my tests _without_ cgmanager, after 8000 SSH sessions to my target
machine, I found 8000 folders with some files each at
/sys/fs/cgroup/systemd/user// .

Although it doesn't directly affects systemd-logind memory footprint, it
certainly affects system memory overall. So, in my consideration (given
cgmanager has even code glue added to systemd on Trusty), I'd suggest to
make it a dependency, not sure why it isn't anyway - for me, this cgroup
folders' leak is clearly a bug.

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

Title:
  systemd-logind: memory leaks on session's connections (trusty-only)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  In Progress
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  Below the SRU request form. Please refer to the Original Description
  to a more comprehensive explanation of the problem observed.

  
  [Impact] 

   * systemd-logind tool is leaking memory at each session connected. The 
   issues happens in systemd from Trusty (14.04) only.

   * Three issues observed:
- systemd-logind is leaking entire sessions, i.e, the sessions are not 
  feeed after they're closed. In order to fix that, we proactively add 
  the sessions to systemd garbage collector (gc) when they are closed. 
  Also, part of the fix is to make cgmanager package a dependency. Refer 
  to comment #1 to a more thorough explanation of the issue and the fix.

- a small memory leak was observed in the session creation logic of 
  systemd-logind. The fix for that is the addition of an appropriate 
  free() call. Refer to comment #2 to more details on the issue and fix.

- another small memory leak was observed in the cgmanager glue code of 
  systemd-logind - this code is only present in this specific Ubuntu 
  release of the package, due to necessary compatibility layer with 
  upstart init system. The fix is to properly call free() in 2 
  functions. Refer to comment #3 to a deep exposition of the issue and 
  the fix.

  
  [Test Case]

   * The basic test-case is to run the following loop from a remote machine:
 while true; do ssh  "whoami"; done

   * It's possible to watch the increase in memory consumption from 
 "systemd-logind" process in the target machine. One can use the
 "ps uax" command to verify the RSS of the process, or count its 
 anonymous pages from /proc//smaps.

  
  [Regression Potential] 

   * Since the fixes are small and not intrusive, the potential for 
 regressions are low. More regression considerations on comments #1, #2 
 and #3 for each fix.

   * A potential small regressson is performance-wise, since now we add 
 sessions to garbage collector proactively.

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

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

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2018-03-05 04:59 EDT---
IBM bugzilla status -> closed, Backports accepted for 1.0.2 and 1.1.0 -> Fix 
Released in bionic

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

Title:
  [18.04 FEAT] Add support for CPACF enhancements to openssl

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl1.0 package in Ubuntu:
  Fix Released

Bug description:
  Add support for CPACF enhancements to openssl

  Support new CPACF instructions to accelerate the GCM mode of operation as 
available with IBM z14 and later hardware
  This feature implements the instruction support in openssl !

  A prereq within IBMCA is already available with ibmca 1.4.0. Already
  requested for 17.10.

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

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

[Touch-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Launchpad Bug Tracker]

This bug was fixed in the package libjogl2-java - 2.3.2+dfsg-
4ubuntu0.16.04.1

---
libjogl2-java (2.3.2+dfsg-4ubuntu0.16.04.1) xenial; urgency=medium

  * fix-mesa-detection.diff: Fix detecting Mesa 17.2 ->. (LP: #1742894)

 -- Timo Aaltonen   Fri, 12 Jan 2018 21:23:23 +0200

** Changed in: libjogl2-java (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in scilab package in Ubuntu:
  Invalid
Status in libjogl2-java source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Invalid
Status in scilab source package in Xenial:
  Invalid
Status in libjogl2-java source package in Artful:
  Fix Released
Status in mesa source package in Artful:
  Invalid
Status in scilab source package in Artful:
  Invalid
Status in scilab package in Debian:
  Fix Released

Bug description:
  [Impact]

  Software that use libjogl2-java (Scilab, Matlab,...) fail to run,
  because Mesa dropped 'Gallium' from the renderer string.

  [Test case]
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped
   at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
   at com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
   at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
   at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
   at java.security.AccessController.doPrivileged(Native Method)
   at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
   at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
   at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
   at org.scilab.modules.gui.SwingView.(Unknown Source)
   at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
   at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  [Regression potential]
  The fix is a simple oneliner that allows libjogl2-java to detect Mesa with 
both new and original version of Mesa.

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

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

[Touch-packages] [Bug 1752448] Re: error message for unmet dependencies is misleading

[Julian Andres Klode]

I'm not sure if we can improve that. The current message is somewhat
correct, changing it to "already installed" would be sort of wrong -
whether it's installed or not does not matter. What's mattering is that
these versions are supposed to remain installed, sort of.

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

Title:
  error message for unmet dependencies is misleading

Status in apt package in Ubuntu:
  New

Bug description:
  When trying to install some older packages on a machine with newer
  packages I get the following message:

  The following packages have unmet dependencies:
   libcupsimage2 : Depends: libcups2 (= 1.7.2-0ubuntu1.8) but 1.7.2-0ubuntu1.9 
is to be installed
   libgfortran3 : Depends: gcc-4.8-base (= 4.8.4-2ubuntu1~14.04.3) but 
4.8.4-2ubuntu1~14.04.4 is to be installed
  E: Unable to correct problems, you have held broken packages. 

  The way the message is worded makes it seem like I was trying to
  install version 1.7.2-0ubuntu1.9 and 4.8.4-2ubuntu1~14.04.4 of the
  above packages.

  In reality, these were the versions of the packages that were already
  installed on the machine.

  This caused a fair bit of confusion when trying to debug the
  situation.

  If you could please reword the error message to be correct. Perhaps
  something along the lines of:

  The following packages have unmet dependencies:
   libcupsimage2 : Depends: libcups2 (= 1.7.2-0ubuntu1.8) but 1.7.2-0ubuntu1.9 
is already installed
   libgfortran3 : Depends: gcc-4.8-base (= 4.8.4-2ubuntu1~14.04.3) but 
4.8.4-2ubuntu1~14.04.4 is already installed
  E: Unable to correct problems, you have held broken packages. 

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.25
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb 28 18:14:25 2018
  InstallationDate: Installed on 2017-11-03 (117 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1752472] Re: [ffe] Implement an Ubuntu Single Sign-on Provider

[Andrea Azzarone]

I forgot to add python3-macaroonbakery as a dependency.
python3-macaroonbakery is used in the livepatch python helper and is not
automatically picked as a dependency.

** Patch added: "goa.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1752472/+attachment/5069669/+files/goa.debdiff

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

Title:
  [ffe] Implement an Ubuntu Single Sign-on Provider

Status in gnome-online-accounts:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Add an Ubuntu Single Sing-On provider in gnome-online-accounts. We plan to 
use this inside:
  1) gnome-software
  2) software-properties

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1752472/+subscriptions

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