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

[Mythological]

Kaan Akşit:  You are going down the same rabbit hole that I did and it
won't work, and will just mess up your system.  The problem is not the
nVidia driver, it's the kernel upgrade.  Go to the thread at
https://ubuntuforums.org/showthread.php?t=2385621=13742281#post13742281
and you will see what you need to do.

-- 
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)

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.

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

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

[Kaan Akşit]

Having the exact same issue with nvidia-390 package at my Ubuntu 16.04,
rolled back to nvidia-387 and had the same issue. And later I rolled
back nvidia-384, and still the same issue.

Then I downloaded NVIDIA-Linux-x86_64-384.111.run from Nvidia's website
to see if I am able to get it up and running as Jason claimed in his
earlier post. Started installing the manual driver by killing the x
server. It prompt as unable to load the kernel module 'Nvidia.ko'.
Simply installation failed.

I am curious to find out how Jason switched to that version of Nvidia
drivers.

So for the one last time I tried removing all nvidia-* packages, and
tried installin nvidia-331 package from the repository... and the result
is the same on my end.

-- 
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)

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.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+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 1751198] [NEW] The problem is with ethernet. After sometime ethernet network doesn't work. LAN works well but internet connectivity has problem. I can connect to same network via

[Anupam Datta]

Public bug reported:

The problem is with ethernet. After sometime ethernet network doesn't
work. LAN works well but internet connectivity has problem. I can
connect to same network via wifi and there is no problem. Bu through
Ethernet for this particular machine I am seeing this problem. With
16.04 there was no issue at all.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.4-1ubuntu3 [modified: 
usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf]
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
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 23 11:52:12 2018
IpRoute:
 default via 10.100.10.1 dev eno1 proto static metric 20100 
 10.100.10.0/23 dev eno1 proto kernel scope link src 10.100.11.8 metric 100 
 169.254.0.0/16 dev eno1 scope link metric 1000 
 169.254.0.0/16 dev eno1 scope link metric 1001 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-08T14:11:20.564841
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
 virbr0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/3  
virbr0  f7ed1838-6b56-4032-99f9-602539799a67  
/org/freedesktop/NetworkManager/ActiveConnection/2  
 eno1ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  84d5092f-8385-491c-acab-38e47bc5ffc5  
/org/freedesktop/NetworkManager/ActiveConnection/16 
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
   
 virbr0-nic  tun   unmanaged  /org/freedesktop/NetworkManager/Devices/4  -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  limited   enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  The problem is with ethernet. After sometime ethernet network doesn't
  work. LAN works well but internet connectivity has problem. I can
  connect to same network via wifi and there is no problem. Bu through
  Ethernet for this particular machine I am seeing this problem.

Status in network-manager package in Ubuntu:
  New

Bug description:
  The problem is with ethernet. After sometime ethernet network doesn't
  work. LAN works well but internet connectivity has problem. I can
  connect to same network via wifi and there is no problem. Bu through
  Ethernet for this particular machine I am seeing this problem. With
  16.04 there was no issue at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3 [modified: 
usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf]
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 23 11:52:12 2018
  IpRoute:
   default via 10.100.10.1 dev eno1 proto static metric 20100 
   10.100.10.0/23 dev eno1 proto kernel scope link src 10.100.11.8 metric 100 
   169.254.0.0/16 dev eno1 scope link metric 1000 
   169.254.0.0/16 dev eno1 scope link metric 1001 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-08T14:11:20.564841
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   virbr0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/3  
virbr0  f7ed1838-6b56-4032-99f9-602539799a67  
/org/freedesktop/NetworkManager/ActiveConnection/2  
   eno1ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  84d5092f-8385-491c-acab-38e47bc5ffc5  

[Touch-packages] [Bug 1749075] Re: ubuntu light-theme doesn't correctly decorate menubar for widgets that are maximized

[Cui Wei]

** Attachment added: "This is maximized caja window, where menubar theme is not 
correct"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1749075/+attachment/5060892/+files/2018-02-23_13%3A44%3A44.png

** Changed in: ubuntu-themes (Ubuntu)
   Status: Incomplete => New

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

Title:
  ubuntu light-theme doesn't correctly decorate menubar for widgets that
  are maximized

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  OS: Ubuntu 18.04

  light-themes includes Ambiance & Radiance, when opening a widget that
  contains menu toolbar (with global-menu disabled), the background
  color of menu toolbar only keeps coordinate with titlebar when the
  widget is not maximized. Once the widget is maximized, the background
  color of its menu toolbar becomes different which is ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  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: MATE
  Date: Tue Feb 13 14:02:20 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749075] Re: ubuntu light-theme doesn't correctly decorate menubar for widgets that are maximized

[Cui Wei]

The following extra styles should be added into both Ambiance and
Radiance:

# Extra theme for lightdm-gtk-greeter
.lightdm-gtk-greeter separator {
border-style: none;
border-width: 0px;
}

# Extra theme for mate-terminal
window.background.mate-terminal vte-terminal {
-TerminalScreen-background-darkness: 0.95;
background-color: #300A24;
color: #F2F1F0;
}

# Extra theme for maximized window menubar
.maximized .menubar:not(:backdrop),
.maximized menubar:not(:backdrop) {
background-color: @dark_bg_color;
}

# Extra theme for default textview box
.view text {
background-color: @base_color;
color: @text_color;
}

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

Title:
  ubuntu light-theme doesn't correctly decorate menubar for widgets that
  are maximized

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  OS: Ubuntu 18.04

  light-themes includes Ambiance & Radiance, when opening a widget that
  contains menu toolbar (with global-menu disabled), the background
  color of menu toolbar only keeps coordinate with titlebar when the
  widget is not maximized. Once the widget is maximized, the background
  color of its menu toolbar becomes different which is ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  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: MATE
  Date: Tue Feb 13 14:02:20 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1751191] Re: Using Vbox with 3D enabled, creates strange stuttering

[BertN45]

** Description changed:

- It looks that the sequence of frames displayed at the screen is mixed up. The 
display goes back say ¼ a second and that gives a very strange effect. You type 
a letter, that letter is erased afterwards and reappears after ¼ of a second. 
See the ATTACHED video. You see the same type of going back a number of frames 
in e.g. YouTube videos, which gives a jittery effect.
- The problem only occurs if I have 3D acceleration enabled in Virtualbox and 
it occurred with both Ubuntu 16.04 and 17.10 hosts. It only occurs at Ubuntu 
16.04 guests, the problem does not occur in Ubuntu 17.10 nor in other Linux 
distros including Ubuntu Mate and Xubuntu. I use Virtualbox 5.2.6 with Guest 
Additions 5.2.7 as recommended by Oracle on their website.
+ It looks that the sequence of frames displayed at the screen is mixed
+ up. The display goes back say ¼ a second and that gives a very strange
+ effect. You type a letter, that letter is erased afterwards and
+ reappears after ¼ of a second. See the ATTACHED video. You see the same
+ type of going back a number of frames in e.g. YouTube videos, which
+ gives a jittery effect.
+ 
+ See also the Conky graphs going sometimes backward in both videos :)
+ 
+ The problem only occurs if I have 3D acceleration enabled in Virtualbox
+ and it occurred with both Ubuntu 16.04 and 17.10 hosts. It only occurs
+ at Ubuntu 16.04 guests, the problem does not occur in Ubuntu 17.10 nor
+ in other Linux distros including Ubuntu Mate and Xubuntu. I use
+ Virtualbox 5.2.6 with Guest Additions 5.2.7 as recommended by Oracle on
+ their website.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:
  
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Feb 22 23:35:36 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-03-29 (330 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=82019235-3f7b-4b99-b622-d6bb790566d5 ro quiet splash zswap.enabled=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb 22 23:13:23 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "vboxvideo" (module does not exist, 0)
   Failed to load module "vboxvideo" (module does not exist, 0)
   modeset(0): glamor initialization failed
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

Title:
  Using Vbox with 3D enabled, creates strange stuttering

Status in xorg package in Ubuntu:
  New

Bug description:
  It looks that the sequence of 

[Touch-packages] [Bug 1751191] Re: Using Vbox with 3D enabled, creates strange stuttering

[BertN45]

Another video with an audio player and a progress bar and counter
sometimes going backwards

** Attachment added: "stutter1.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1751191/+attachment/5060871/+files/stutter1.mp4

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

Title:
  Using Vbox with 3D enabled, creates strange stuttering

Status in xorg package in Ubuntu:
  New

Bug description:
  It looks that the sequence of frames displayed at the screen is mixed
  up. The display goes back say ¼ a second and that gives a very strange
  effect. You type a letter, that letter is erased afterwards and
  reappears after ¼ of a second. See the ATTACHED video. You see the
  same type of going back a number of frames in e.g. YouTube videos,
  which gives a jittery effect.

  See also the Conky graphs going sometimes backward in both videos :)

  The problem only occurs if I have 3D acceleration enabled in
  Virtualbox and it occurred with both Ubuntu 16.04 and 17.10 hosts. It
  only occurs at Ubuntu 16.04 guests, the problem does not occur in
  Ubuntu 17.10 nor in other Linux distros including Ubuntu Mate and
  Xubuntu. I use Virtualbox 5.2.6 with Guest Additions 5.2.7 as
  recommended by Oracle on their website.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Feb 22 23:35:36 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-03-29 (330 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=82019235-3f7b-4b99-b622-d6bb790566d5 ro quiet splash zswap.enabled=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb 22 23:13:23 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "vboxvideo" (module does not exist, 0)
   Failed to load module "vboxvideo" (module does not exist, 0)
   modeset(0): glamor initialization failed
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

-- 
Mailing list: https://launchpad.net/~touch-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)

[chipschap]

FWIW some NVIDIA-related changes were apparently made in 114:

2018-02-09 - Khalid Elmously 
linux (4.4.0-114.137) xenial; urgency=medium
* linux: 4.4.0-114.137 -proposed tracker (LP: #1748484)
* ALSA backport missing NVIDIA GPU codec IDs to patch table to
Ubuntu 16.04 LTS Kernel (LP: #1744117)
- ALSA: hda - Add missing NVIDIA GPU codec IDs to patch table
* Shutdown hang on 16.04 with iscsi targets (LP: #1569925)

I don't know if this caused the problem, but regressing from 116 to 112
also solved it for me (after about an hour of utter frustration).

-- 
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)

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.

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

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

[Launchpad Bug Tracker]

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

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

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

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

Status in audit package in Ubuntu:
  Expired

Bug description:
  see logs

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: auditd (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  AptOrdering:
   libauparse0: Install
   auditd: Install
   libauparse0: Configure
   auditd: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Dec 22 09:37:54 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-12-05 (17 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: audit
  Title: package auditd (not installed) 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/audit/+bug/1739789/+subscriptions

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

[Touch-packages] [Bug 1751191] [NEW] Using Vbox with 3D enabled, creates strange stuttering

[BertN45]

Public bug reported:

It looks that the sequence of frames displayed at the screen is mixed up. The 
display goes back say ¼ a second and that gives a very strange effect. You type 
a letter, that letter is erased afterwards and reappears after ¼ of a second. 
See the ATTACHED video. You see the same type of going back a number of frames 
in e.g. YouTube videos, which gives a jittery effect.
The problem only occurs if I have 3D acceleration enabled in Virtualbox and it 
occurred with both Ubuntu 16.04 and 17.10 hosts. It only occurs at Ubuntu 16.04 
guests, the problem does not occur in Ubuntu 17.10 nor in other Linux distros 
including Ubuntu Mate and Xubuntu. I use Virtualbox 5.2.6 with Guest Additions 
5.2.7 as recommended by Oracle on their website.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Feb 22 23:35:36 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2017-03-29 (330 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=82019235-3f7b-4b99-b622-d6bb790566d5 ro quiet splash zswap.enabled=1
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Feb 22 23:13:23 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "vboxvideo" (module does not exist, 0)
 Failed to load module "vboxvideo" (module does not exist, 0)
 modeset(0): glamor initialization failed
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


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

** Attachment added: "stutter.mp4"
   
https://bugs.launchpad.net/bugs/1751191/+attachment/5060849/+files/stutter.mp4

** Description changed:

  It looks that the sequence of frames displayed at the screen is mixed up. The 
display goes back say ¼ a second and that gives a very strange effect. You type 
a letter, that letter is erased afterwards and reappears after ¼ of a second. 
See the ATTACHED video. You see the same type of going back a number of frames 
in e.g. YouTube videos, which gives a jittery effect.
- The problem only occurs if I have 3D acceleration enabled in Virtualbox and 
it occurred with both Ubuntu 16.04 and 17.10 hosts. It only occurs at Ubuntu 
16.04 guests, the problem does not occur in Ubuntu 17.10 nor in other Linux 
distros. I use Virtualbox 5.2.6 with Guest Additions 5.2.7 as recommended by 
Oracle on their website.
+ The problem only occurs if I have 3D acceleration enabled in Virtualbox and 
it occurred with both Ubuntu 16.04 and 17.10 hosts. It only occurs at Ubuntu 
16.04 guests, the problem does not occur in Ubuntu 17.10 nor in other Linux 
distros including Ubuntu Mate and Xubuntu. I use Virtualbox 5.2.6 with Guest 
Additions 

Re: [Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Andres Rodriguez]

On Thu, Feb 22, 2018 at 10:30 PM Scott Moser 
wrote:

> Getting this fixed in cloud-init is tricky.
> In ifupdown (/etc/network/interfaces) world, we just took the "global dns"
> entries and put them on the loopback device (lo).  Since that device would
> always be brought up, and never really brought down, it served its purpose.
>
> That is what Ryan tried above, but it doesnt seem to work.  Even if it
> *did* work, the solution would be systemd-networkd specific, and cloud-
> init doesn't speak to systemd-networkd or systemd-resolved.  It speaks
> to netplan.  So we would still need a way for cloud-init to tell netplan
> to do this.
>
> That leaves us with 2 not-so-great solutions in cloud-init only:
> a.) blindly put global dns entries on *all* interfaces
> b.) cloud-init search through the config and find the "right" interface to
> put the global dns entry on.
>

This is the same issue we are facing in MAAS. Unless a user specifies a
specific set of dns servers on a subnet, which is not always the case, then
MAAS doesn’t know which interface the dns servers belong to.

I believe this is one of the reasons why the “global” config was used,
because effectively, the DNS server doesn’t really “belong” to a specific
interface.

So we either sent it to all, interfaces or pick a “best” interface, which
is not the best approach either.

As per mpontillo’s config, this has the likelihood to break dns
resolution.

That said, maybe option 3 would be to put th dns on the interface which the
default routes will be going through...


> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1750884
>
> Title:
>   [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
>   leads to no DNS resolution
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=cloud-init; status=New; importance=Undecided;
> assignee=None;
> Launchpad-Bug: product=maas; milestone=2.4.0alpha2; status=Triaged;
> importance=High; assignee=mike.ponti...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=nplan; component=main;
> status=New; importance=Critical; assignee=None;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=systemd; component=main;
> status=New; importance=Critical; assignee=None;
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: andreserl cyphermox dean raharper smoser xnox
> Launchpad-Bug-Reporter: Andres Rodriguez (andreserl)
> Launchpad-Bug-Modifier: Scott Moser (smoser)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: andreserl
>
-- 
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Triaged
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the 

[Touch-packages] [Bug 1751187] Re: package python-apt 1.1.0~beta1build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

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

Title:
  package python-apt 1.1.0~beta1build1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

Status in python-apt package in Ubuntu:
  New

Bug description:
  I don't know what happen

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-apt 1.1.0~beta1build1
  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:
   curl: Install
   python-apt: Install
   curl: Configure
   python-apt: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Feb 19 14:18:59 2018
  DuplicateSignature:
   package:python-apt:1.1.0~beta1build1
   Setting up python-apt (1.1.0~beta1build1) ...
   /var/lib/dpkg/info/python-apt.postinst: 6: 
/var/lib/dpkg/info/python-apt.postinst: pycompile: not found
   dpkg: error processing package python-apt (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2017-12-07 (77 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: python-apt
  Title: package python-apt 1.1.0~beta1build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Scott Moser]

Getting this fixed in cloud-init is tricky.
In ifupdown (/etc/network/interfaces) world, we just took the "global dns" 
entries and put them on the loopback device (lo).  Since that device would 
always be brought up, and never really brought down, it served its purpose.

That is what Ryan tried above, but it doesnt seem to work.  Even if it
*did* work, the solution would be systemd-networkd specific, and cloud-
init doesn't speak to systemd-networkd or systemd-resolved.  It speaks
to netplan.  So we would still need a way for cloud-init to tell netplan
to do this.

That leaves us with 2 not-so-great solutions in cloud-init only:
a.) blindly put global dns entries on *all* interfaces
b.) cloud-init search through the config and find the "right" interface to put 
the global dns entry on.

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Triaged
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 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 maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution

  [...]

  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms

  =
  Xenial
  ==

  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  dns-nameservers 10.90.90.1
  dns-search maaslab maas

  auto enp0s25
  iface enp0s25 inet static
  address 10.90.90.162/24
  gateway 10.90.90.1
  mtu 1500
  ubuntu@node05:~$ 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
  nameserver 10.90.90.1
  search maaslab maas

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions

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

[Touch-packages] [Bug 1751187] [NEW] package python-apt 1.1.0~beta1build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[zhouyuxiang]

Public bug reported:

I don't know what happen

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-apt 1.1.0~beta1build1
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:
 curl: Install
 python-apt: Install
 curl: Configure
 python-apt: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Feb 19 14:18:59 2018
DuplicateSignature:
 package:python-apt:1.1.0~beta1build1
 Setting up python-apt (1.1.0~beta1build1) ...
 /var/lib/dpkg/info/python-apt.postinst: 6: 
/var/lib/dpkg/info/python-apt.postinst: pycompile: not found
 dpkg: error processing package python-apt (--configure):
  subprocess installed post-installation script returned error exit status 127
ErrorMessage: subprocess installed post-installation script returned error exit 
status 127
InstallationDate: Installed on 2017-12-07 (77 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: python-apt
Title: package python-apt 1.1.0~beta1build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package python-apt 1.1.0~beta1build1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

Status in python-apt package in Ubuntu:
  New

Bug description:
  I don't know what happen

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-apt 1.1.0~beta1build1
  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:
   curl: Install
   python-apt: Install
   curl: Configure
   python-apt: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Feb 19 14:18:59 2018
  DuplicateSignature:
   package:python-apt:1.1.0~beta1build1
   Setting up python-apt (1.1.0~beta1build1) ...
   /var/lib/dpkg/info/python-apt.postinst: 6: 
/var/lib/dpkg/info/python-apt.postinst: pycompile: not found
   dpkg: error processing package python-apt (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2017-12-07 (77 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: python-apt
  Title: package python-apt 1.1.0~beta1build1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 40189] Re: [SRU] [xenial] autofs needs to be restarted to pick up some shares

[David Britton]

A good first step would be for someone to check that the bug is fixed in
bionic, as the package has been updated there.

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

Title:
  [SRU] [xenial] autofs needs to be restarted to pick up some shares

Status in autofs package in Ubuntu:
  Confirmed
Status in autofs5 package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Invalid

Bug description:
  I am using autofs to access shares on a Windows XP machine from a
  Kubuntu AMD64 machine.  The problems applies in both Breezy and
  Dapper.

  EDIT:  confirmed with similar configuration on Intrepid with a NetApp
  filer hosting NFS.  Server OS removed from summary.

  When I first try to access the mount point via cd or in Konqueror it
  does not exist.  However,  if I then restart autofs
  (/etc/init.d/autofs restart) everythin then works OK.  My config files
  are:

  auto.master

  #
  # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $
  #
  # Sample auto.master file
  # This is an automounter map and it has the following format
  # key [ -mount-options-separated-by-comma ] location
  # For details of the format look at autofs(5).
  #/misc/etc/auto.misc --timeout=60
  #/misc/etc/auto.misc
  #/net /etc/auto.net

  /petunia /etc/petunia.misc --timeout=60

  
  petunia.misc

  #
  # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $
  #
  # This is an automounter map and it has the following format
  # key [ -mount-options-separated-by-comma ] location
  # Details may be found in the autofs(5) manpage

  cd  -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom

  tony  -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/tony
  chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/chris
  shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/SharedDocs
  linuxbackups  -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 
://192.168.1.2/linuxbackups

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

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

[Touch-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.

[Daniel van Vugt]

** Tags added: artful trusty

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

Title:
  Bluetooth mouse fails to re-connect after sleep.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

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

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

[Touch-packages] [Bug 1750379] Re: Distortion Realtek ALC887

[Daniel van Vugt]

Please clarify exactly which kernel versions you have tested. It will
help us to narrow down the problem.

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

Title:
  Distortion Realtek ALC887

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

Bug description:
  Sounds can distort even when not amplified. Amplification worked well
  for years before recent PulseAudio update. The audio is Realtek ALC887
  under an IntelG41 Chipset with GA-G41M-Combo main board;

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

  I am seeking to engage upstream for April LTS release. Windows have
  abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user
  going!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fleamour   1049 F pulseaudio
   /dev/snd/controlC2:  fleamour   1049 F pulseaudio
   /dev/snd/controlC0:  fleamour   1049 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 19 13:54:33 2018
  InstallationDate: Installed on 2018-02-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  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.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1751140] Re: nss-pem needs additional headers, static libs to build

[Bug Watch Updater]

** Changed in: nss (Debian)
   Status: Unknown => New

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

Title:
  nss-pem needs additional headers, static libs to build

Status in nss package in Ubuntu:
  Triaged
Status in nss package in Debian:
  New

Bug description:
  nss-pem is needed for apps linked with libnss3 to read certificates in
  PEM format. This is required when setting up a freeipa server with
  ipa-server-setup, and also certmonger to be able to refresh
  certificates on a freeipa client.

  To be able to build, nss-pem needs some headers and static libs
  provided by nss. They are marked private though, and upstream refuses
  to make them public and Debian maintainer refuses to include them in
  the packaging because of this.

  The required files are blapi.h, alghmac.h, nssckfw.a, nssb.a, freebl.a
  and they could be shipped in a  separate libnss3-pkcs11-dev package,
  because they're not meant for generic consumption via libnss-dev.

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

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

[Touch-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.

[Pavel Francírek]

This happens my Mint too. Bluetooth keyboard is working after resume from 
suspend but mouse (Logitech M720 Triatlon) is not. bluetoothctl says Connected: 
yes  .. no .. yes .. no 
But bluetoothctl: agent off/on helps (no need to use power and pair commands).

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

Title:
  Bluetooth mouse fails to re-connect after sleep.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

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

-- 
Mailing list: https://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 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

[John Center]

Hi Dimitri,

> On Feb 22, 2018, at 8:32 AM, Dimitri John Ledkov  
> wrote:
> 
> john-center - I believe mdadm is used by default, instead of dmraid.
> However, I'm not sure if we do correctly activate Intel Raids with
> mdadm. I have not done an install with either 16.04 or 18.04. Or I guess
> at least start the install up to the partitioning screen. My expectation
> is, if one has raid arrays pre-setup in BIOS (ctrl+I on boot) already,
> they should show up as assembled and offered to be autopartitioned. With
> both 16.04 and 18.04.
> 
I know with 16.04 it wasn’t used by default. I had to do a lot of manipulation 
to set up the raid array before I could do the install. It used dmraid once it 
detected the imsm raid. I removed dmraid completely, then installed mdadm, 
assembled the array & ran the installation program again. I was hoping that 
mdadm would just do it all instead. 

-John

> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1587142
> 
> Title:
>  Shutdown hangs in md kworker after "Reached target Shutdown."
> 
> Status in systemd package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  I'm booting a fully patched 16.04 from an Intel Rapid Storage
>  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
>  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).
> 
>  If the RAID volume is recovering or resyncing for whatever reason, then 
> `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had to 
> `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in 
> order to consistently get that). However, once the recovery/resync is 
> complete and clean, the reboot and poweroff commands above hang forever after 
> "Reached target Shutdown.". Note that issuing `sudo swapoff -a` beforehand 
> (suggested in the bug #1464917) does not help.
>  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
> But I've never seen it succeed once the resync is complete.[/EDIT]
> 
>  Then, if the server has been forcibly restarted with the power button,
>  the Intel Matrix Storage Manager indicates a "Normal" status for the
>  RAID1 volume, but Ubuntu then resyncs the volume anyway:
> 
>  [1.223649] md: bind
>  [1.228426] md: bind
>  [1.230030] md: bind
>  [1.230738] md: bind
>  [1.232985] usbcore: registered new interface driver usbhid
>  [1.233494] usbhid: USB HID core driver
>  [1.234022] md: raid1 personality registered for level 1
>  [1.234876] md/raid1:md126: not clean -- starting background 
> reconstruction
>  [1.234956] input: CHESEN USB Keyboard as 
> /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
>  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
>  [1.236797] md126: detected capacity change from 0 to 1000202043392
>  [1.246271] md: md126 switched to read-write mode.
>  [1.246834] md: resync of RAID array md126
>  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
>  [1.247503]  md126: p1 p2 p3 p4
>  [1.248269] md: using maximum available idle IO bandwidth (but not more 
> than 20 KB/sec) for resync.
>  [1.248774] md: using 128k window, over a total of 976759940k.
> 
>  Note that the pain of "resync upon every (re)boot" cannot even be a
>  bit relieved thanks to bitmaps because mdadm does not support them for
>  IMSM containers:
> 
>  $ sudo mdadm --grow --bitmap=internal /dev/md126
>  mdadm: Cannot add bitmaps to sub-arrays yet
> 
>  I also get this in syslog during boot when the individual drives are
>  detected, but this seems to be harmless:
> 
>  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm 
> --incremental /dev/sdb --offroot' failed with exit code 1.
>  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
> with exit code 1.
> 
>  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm 
> --incremental /dev/sda --offroot' failed with exit code 1.
>  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
> with exit code 1.
> 
>  During a resync, `sudo sh -c 'echo idle >
>  /sys/block/md126/md/sync_action'` actually stops it as expected, but
>  it restarts immediately though nothing seems to have triggered it:
> 
>  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
>  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
> md126.
>  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
>  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
> speed: 1000 KB/sec/disk.
>  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
> idle IO bandwidth (but not more than 20 KB/sec) for resync.
>  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
> total of 976759940k.
>  May 30 18:17:02 

[Touch-packages] [Bug 1674330] Re: Please consider dropping /etc/network/if-up.d/openssh-server

[Ubuntu Foundations Team Bug Bot]

The attachment "openssh-7.6p1-4ubuntu1.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Please consider dropping /etc/network/if-up.d/openssh-server

Status in openssh package in Ubuntu:
  In Progress

Bug description:
  The /etc/network/if-up.d/openssh-server hack was introduced ten years ago [1] 
as a response to bug 
  103436. At least from today's perspective this isn't justified:

  I can't seem to be able to actually reproduce that issue: I can start
  a VM with no network interfaces, remove the above hack, then start
  sshd, then bring up an ethernet interface, and I can connect to ssh
  via ethernet just fine. Also, e. g. Fedora has no counterpart of this
  hack, and these days a lot of people would complain if that would
  cause problems, as hotpluggable/roaming network devices are
  everywhere.

  The hack introduces a race: you run into connection errors after
  bringing up a new interface as sshd stops listening briefly while
  being reloaded. That's the reason why I looked at it, as this
  regularly happens in upstream's cockpit integration tests.

  Also, /etc/network/if-up.d/ isn't being run when using
  networkd/netplan, i. e. in more recent Ubuntnu cloud instances. So far
  this doesn't seem to have caused any issues.

  I asked the original reporter of bug 103436 for some details, and to
  check whether that hack is still necessary. There is actually a
  proposed patch upstream [2] to use IP_FREEBIND, which is the modern
  solution to listening to all "future" interfaces as well. But at least
  for the majority of cases it seems to work fine without that even.

  So I wonder if it's time to bury that hack?

  [1] https://anonscm.debian.org/cgit/pkg-ssh/openssh.git/commit/?id=ba6b55ed6
  [2] https://bugzilla.mindrot.org/show_bug.cgi?id=2512

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

-- 
Mailing list: https://launchpad.net/~touch-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)

[Wadcutter]

Not only same video issue as others on Trusty with Nvidia 340.102 driver
for GEForce 8400GS, but am also unable to log in.Entering PW just keeps
flipping me back to "Enter PW box". Old 112 kernel works just fine so I
will stick with that until a fix is available.

-- 
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)

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.

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

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

[Jason]

Add me to the List of People with this problem, nvidia 384.111 worked
great until this kernel now same problem as original poster.  Had to go
back to 112 to get it to work.

-- 
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)

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.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+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 1751140] Re: nss-pem needs additional headers, static libs to build

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  nss-pem needs additional headers, static libs to build

Status in nss package in Ubuntu:
  Triaged
Status in nss package in Debian:
  Unknown

Bug description:
  nss-pem is needed for apps linked with libnss3 to read certificates in
  PEM format. This is required when setting up a freeipa server with
  ipa-server-setup, and also certmonger to be able to refresh
  certificates on a freeipa client.

  To be able to build, nss-pem needs some headers and static libs
  provided by nss. They are marked private though, and upstream refuses
  to make them public and Debian maintainer refuses to include them in
  the packaging because of this.

  The required files are blapi.h, alghmac.h, nssckfw.a, nssb.a, freebl.a
  and they could be shipped in a  separate libnss3-pkcs11-dev package,
  because they're not meant for generic consumption via libnss-dev.

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

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

[Touch-packages] [Bug 1674330] Re: Please consider dropping /etc/network/if-up.d/openssh-server

[David Britton]

This is a debdiff for Bionic applicable to 7.6p1-4. I built the binary packages 
in pbuilder
and they build, upgraded and installed successfully.

Tested that the ifup hook was removed on upgrade, and also on install it
was never installed.

I went through a series of tests on a laptop with a wireless interface
and desktop with some somewhat complicated network layout.

I did not run into any unexpected results in the testing.  After every
network event I could trigger, I did not see a daemon restart, and also
the ssh server was still reachable on all exposed interfaces I tried, as
it was on 127.0.0.1.

Thanks for your consideration of this patch.




** Patch added: "openssh-7.6p1-4ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1674330/+attachment/5060756/+files/openssh-7.6p1-4ubuntu1.debdiff

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

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

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

Title:
  Please consider dropping /etc/network/if-up.d/openssh-server

Status in openssh package in Ubuntu:
  In Progress

Bug description:
  The /etc/network/if-up.d/openssh-server hack was introduced ten years ago [1] 
as a response to bug 
  103436. At least from today's perspective this isn't justified:

  I can't seem to be able to actually reproduce that issue: I can start
  a VM with no network interfaces, remove the above hack, then start
  sshd, then bring up an ethernet interface, and I can connect to ssh
  via ethernet just fine. Also, e. g. Fedora has no counterpart of this
  hack, and these days a lot of people would complain if that would
  cause problems, as hotpluggable/roaming network devices are
  everywhere.

  The hack introduces a race: you run into connection errors after
  bringing up a new interface as sshd stops listening briefly while
  being reloaded. That's the reason why I looked at it, as this
  regularly happens in upstream's cockpit integration tests.

  Also, /etc/network/if-up.d/ isn't being run when using
  networkd/netplan, i. e. in more recent Ubuntnu cloud instances. So far
  this doesn't seem to have caused any issues.

  I asked the original reporter of bug 103436 for some details, and to
  check whether that hack is still necessary. There is actually a
  proposed patch upstream [2] to use IP_FREEBIND, which is the modern
  solution to listening to all "future" interfaces as well. But at least
  for the majority of cases it seems to work fine without that even.

  So I wonder if it's time to bury that hack?

  [1] https://anonscm.debian.org/cgit/pkg-ssh/openssh.git/commit/?id=ba6b55ed6
  [2] https://bugzilla.mindrot.org/show_bug.cgi?id=2512

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

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

[Touch-packages] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Jeremy Bicha]

Dimitri, could you split the duplication issue into a separate bug?

(On that topic, see also https://community.ubuntu.com/t/no-rsyslog-in-
default-desktop-install/4169 )

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

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

Bug description:
  [Impact]

   * System logs are lost across reboots because they are not stored
  persistently.

  [Test Case]

   * Fresh installations, or upgrades to this version of systemd, should create 
/var/log/journal and trigger automatic persistent logs.
   * Users may choose to remove said directory, or disable persistent logging 
in /etc/systemd/journald.conf

  [Regression Potential]

   * Persistent logging by default will cause logs to be flushed from
  /run to /var/log, meaning there will be less RAM used (/run is tmpfs
  backed), but increased disk usage (in /var/log). The journald daemon
  has limits set for logs, meaning they will be rotated and discarded
  and should not cause out of disk-space errors.

  [Other Info]
   
   * Original bug report

  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't.
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

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

[Touch-packages] [Bug 1749199] Re: purge conf files on removal of upstart (was session fails to start after an upgrade from xenial to bionic)

[Dimitri John Ledkov]

** Description changed:

- After an upgrade from Xenial to Bionic the session fails to start and
- returns immediately to the login screen.
+ [Testcase]
+ 
+ 1. Launch xenial lxd container
+ 2. install x11-common upstart
+ 3. do-release-upgrade to bionic
+ 4. Upgrade to bionic removes upstart
+ 5. upgrade to new x11-common, make sure the upstart snippets are gone from 
disk: /etc/X11/Xsession.d/00upstart
+ /etc/X11/Xsession.d/99upstart
+ 6. for the new release-upgrader, check that upstart is purged, if user 
selects to remove packages at the end of the do-release-upgrade.
+ 
+ 
+ After an upgrade from Xenial to Bionic the session fails to start and returns 
immediately to the login screen.
  
  There is this line in the journal
  [...] /usr/lib/gdm3/gdm-x-session[3584]: 
/etc/X11/Xsession.d/99x11-common_start: ligne 5: /sbin/upstart: Aucun fichier 
ou dossier de ce type
  
  (full journal from a failed attempt attached)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.26.1-0ubuntu9
  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
  Date: Tue Feb 13 15:11:12 2018
  InstallationDate: Installed on 2018-02-07 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
-  TERM=linux
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  TERM=linux
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-02-13 (0 days ago)

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

** Changed in: ubuntu-release-upgrader (Ubuntu Bionic)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  purge conf files on removal of upstart (was session fails to start
  after an upgrade from xenial to bionic)

Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Fix Committed
Status in ubuntu-release-upgrader source package in Bionic:
  Triaged
Status in xorg source package in Bionic:
  Fix Committed

Bug description:
  [Testcase]

  1. Launch xenial lxd container
  2. install x11-common upstart
  3. do-release-upgrade to bionic
  4. Upgrade to bionic removes upstart
  5. upgrade to new x11-common, make sure the upstart snippets are gone from 
disk: /etc/X11/Xsession.d/00upstart
  /etc/X11/Xsession.d/99upstart
  6. for the new release-upgrader, check that upstart is purged, if user 
selects to remove packages at the end of the do-release-upgrade.

  
  After an upgrade from Xenial to Bionic the session fails to start and returns 
immediately to the login screen.

  There is this line in the journal
  [...] /usr/lib/gdm3/gdm-x-session[3584]: 
/etc/X11/Xsession.d/99x11-common_start: ligne 5: /sbin/upstart: Aucun fichier 
ou dossier de ce type

  (full journal from a failed attempt attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.26.1-0ubuntu9
  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
  Date: Tue Feb 13 15:11:12 2018
  InstallationDate: Installed on 2018-02-07 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-02-13 (0 days ago)

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

-- 
Mailing list: https://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 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Dimitri John Ledkov]

On 22 February 2018 at 21:11, Bryan Quigley  wrote:
> @markstos
> Sorry, yea, I meant our defaults, not the journal config options itself. 
> SystemMaxUse= is unset in the config in bionic (although it's all commented 
> out, but I believe that's supposed to indicate our defaults?)
>
> Re:disk writing.  I don't disagree, but if we are SRUing it we need to
> consider that more.  For 18.04 we can still decide to remove rsyslog to
> reduce the impact, we can't do that for 17.10/16.04.
>

Current situation of non-persistent logs imho is critical bug. It has
a severe impact, data loss, on a large portion of Ubuntu users.

To reduce duplication, one of the suggestions was to still forward
messages to rsyslog (for forwarding) but do not store those that are
coming from journald on disk, as journald already has them one disk.

Alternative, is to switch to syslog-ng with journald module such that
it pulls in rich journal messages into syslog, and make journald stop
forwarding messages to syslog.

Another alternative is to drop rsyslog from default install, and make
journald be the default syslog provider on Ubuntu.

I am undecided on how to best implement de-duplication of a portion of
messages in Ubuntu going forward, but above are three technically
plausible paths to solve this.

-- 
Regards,

Dimitri.

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

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

Bug description:
  [Impact]

   * System logs are lost across reboots because they are not stored
  persistently.

  [Test Case]

   * Fresh installations, or upgrades to this version of systemd, should create 
/var/log/journal and trigger automatic persistent logs.
   * Users may choose to remove said directory, or disable persistent logging 
in /etc/systemd/journald.conf

  [Regression Potential]

   * Persistent logging by default will cause logs to be flushed from
  /run to /var/log, meaning there will be less RAM used (/run is tmpfs
  backed), but increased disk usage (in /var/log). The journald daemon
  has limits set for logs, meaning they will be rotated and discarded
  and should not cause out of disk-space errors.

  [Other Info]
   
   * Original bug report

  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't.
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

-- 
Mailing list: https://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 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Dimitri John Ledkov]

On 22 February 2018 at 20:20, Bryan Quigley  wrote:
> @xnox
> "The journald daemon has limits set for logs, meaning they will be rotated 
> and discarded and should not cause out of disk-space errors."
>
> What are they?  AFAICT it only has limits on the number of files, but
> not how big they can overall become.
>
>
> I'm also thinking that the duplicate writing of logs could cause other 
> regressions, one example being where high disk throughput is ongoing and many 
> things being written to the logs. Thoughts?
>

The performance impact on disk throughput should not be significant,
as journald still throttles and caches the log messages before
flushing them to disk and still forwards them to rsyslog as it did
before. The performance impact depends on the workload, and there is a
reduction of runtime memory used as well, which helps with throughput
by increasing available io cache buffers.

-- 
Regards,

Dimitri.

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

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

Bug description:
  [Impact]

   * System logs are lost across reboots because they are not stored
  persistently.

  [Test Case]

   * Fresh installations, or upgrades to this version of systemd, should create 
/var/log/journal and trigger automatic persistent logs.
   * Users may choose to remove said directory, or disable persistent logging 
in /etc/systemd/journald.conf

  [Regression Potential]

   * Persistent logging by default will cause logs to be flushed from
  /run to /var/log, meaning there will be less RAM used (/run is tmpfs
  backed), but increased disk usage (in /var/log). The journald daemon
  has limits set for logs, meaning they will be rotated and discarded
  and should not cause out of disk-space errors.

  [Other Info]
   
   * Original bug report

  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't.
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

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

[Touch-packages] [Bug 1750741] Re: Memory leak in g_dbus_proxy_new_for_bus_sync()

[Launchpad Bug Tracker]

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

** Changed in: glib2.0 (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  Memory leak in g_dbus_proxy_new_for_bus_sync()

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  Confirmed

Bug description:
  [Impact]

  This issue is found while debugging pacemaker lrmd memory leak

  glib2.0 gio function g_dbus_proxy_new_for_bus_sync has leak as [1]
  said

  this is affected to Trusty

  [Test Case]

  https://pastebin.ubuntu.com/p/fqK6Cx3SKK/
  you can check memory leak with this script

  [Regression]
  This patch is affected to library pkg. so related daemon should be restarted 
after patching. patch itself is very simple and old. it seems verified for few 
years.

  [Others]

  original commit

  
https://gitlab.gnome.org/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c

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

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

[Touch-packages] [Bug 1751150] [NEW] package libglib2.0-0:i386 2.48.2-0ubuntu1 failed to install/upgrade: dependency issues - Trigger not executed

[marius888]

Public bug reported:

happened durng automated updates

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libglib2.0-0:i386 2.48.2-0ubuntu1
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
Architecture: amd64
Date: Mon Feb 19 20:32:33 2018
ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
InstallationDate: Installed on 2017-08-07 (199 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: glib2.0
Title: package libglib2.0-0:i386 2.48.2-0ubuntu1 failed to install/upgrade: 
Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package libglib2.0-0:i386 2.48.2-0ubuntu1 failed to install/upgrade:
  dependency issues - Trigger not executed

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  happened durng automated updates

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-0:i386 2.48.2-0ubuntu1
  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
  Architecture: amd64
  Date: Mon Feb 19 20:32:33 2018
  ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
  InstallationDate: Installed on 2017-08-07 (199 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: glib2.0
  Title: package libglib2.0-0:i386 2.48.2-0ubuntu1 failed to install/upgrade: 
Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1751140] Re: nss-pem needs additional headers, static libs to build

[Timo Aaltonen]

** Patch added: "debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1751140/+attachment/5060717/+files/nss.debdiff

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

** Changed in: nss (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  nss-pem needs additional headers, static libs to build

Status in nss package in Ubuntu:
  Triaged
Status in nss package in Debian:
  Unknown

Bug description:
  nss-pem is needed for apps linked with libnss3 to read certificates in
  PEM format. This is required when setting up a freeipa server with
  ipa-server-setup, and also certmonger to be able to refresh
  certificates on a freeipa client.

  To be able to build, nss-pem needs some headers and static libs
  provided by nss. They are marked private though, and upstream refuses
  to make them public and Debian maintainer refuses to include them in
  the packaging because of this.

  The required files are blapi.h, alghmac.h, nssckfw.a, nssb.a, freebl.a
  and they could be shipped in a  separate libnss3-pkcs11-dev package,
  because they're not meant for generic consumption via libnss-dev.

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

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

[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Andres Rodriguez]

** Changed in: maas
   Importance: Low => High

** Changed in: maas
 Assignee: (unassigned) => Mike Pontillo (mpontillo)

** Changed in: maas
Milestone: None => 2.4.0alpha2

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Triaged
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 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 maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution

  [...]

  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms

  =
  Xenial
  ==

  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  dns-nameservers 10.90.90.1
  dns-search maaslab maas

  auto enp0s25
  iface enp0s25 inet static
  address 10.90.90.162/24
  gateway 10.90.90.1
  mtu 1500
  ubuntu@node05:~$ 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
  nameserver 10.90.90.1
  search maaslab maas

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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)

[Erik Kratzenberg]

This also seems to affect ZFS on Linux modules:

zavl: version magic '4.4.0-116-generic SMP mod_unload modversions '
should be '4.4.0-116-generic SMP mod_unload modversions retpoline '

-- 
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)

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.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+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 1751144] [NEW] xorg

[GLaDOS NeurotoxinsCore]

Public bug reported:

xorg

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-35-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Feb 22 15:33:01 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
   Subsystem: Dell Radeon HD 6450 [1028:2120]
 Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
   Subsystem: Dell Radeon HD 6450 [1028:2120]
MachineType: Dell Inc. OptiPlex 990
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-35-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro recovery nomodeset
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/28/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 06D7TR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 990
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.89+git20180214.e75e0ea2-0ubuntu0ricotz~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 
18.0.0~git20180214+18.0.1e173463-0ubuntu0ricotz~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 
18.0.0~git20180214+18.0.1e173463-0ubuntu0ricotz~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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

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

Title:
  xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  xorg

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-35-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Feb 22 15:33:01 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 6450 [1028:2120]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 6450 [1028:2120]
  MachineType: Dell Inc. OptiPlex 990
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-35-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.89+git20180214.e75e0ea2-0ubuntu0ricotz~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 
18.0.0~git20180214+18.0.1e173463-0ubuntu0ricotz~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
18.0.0~git20180214+18.0.1e173463-0ubuntu0ricotz~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  

[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Ryan Harper]

I gave the "loopback" trick a go like so:

root@b1:~# cat /etc/systemd/network/10-netplan-lo.network 
[Match]
Name=lo

[Network]
Address=127.0.0.1
DNS=10.90.90.1
Domains=maaslab maas
root@b1:~# networkctl status --all
● 1: lo
   Link File: n/a
Network File: /etc/systemd/network/10-netplan-lo.network
Type: loopback
   State: carrier (configured)
 Address: 127.0.0.1
  ::1
 DNS: 10.90.90.1
  Search Domains: maaslab
  maas

● 38: eth0
   Link File: n/a
Network File: /run/systemd/network/10-netplan-eth0.network
Type: ether
   State: routable (configured)
  HW Address: 00:16:3e:4c:5b:4b (Xensource, Inc.)
 Address: 10.8.107.71
  fe80::216:3eff:fe4c:5b4b
 Gateway: 10.8.107.1
 DNS: 10.8.107.1
  Search Domains: lxd
root@b1:~# systemd-resolve --status --no-pager 
Global
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 38 (eth0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.8.107.1
  DNS Domain: lxd


networkctl processed the .network file but systemd-resolved didn't seem to 
notice it.

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Triaged
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 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 maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution

  [...]

  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): 

[Touch-packages] [Bug 1751140] Re: nss-pem needs additional headers, static libs to build

[Timo Aaltonen]

further discussion in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732201
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726073
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726116
https://bugzilla.mozilla.org/show_bug.cgi?id=1429692

long story short; NSS upstream wouldn't merge nss-pem, so it was forked
as a separate project which uses APIs that will not be made public, nor
libs dynamically loadable

nss-pem Debian ITP is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=20

and I've verified that with nss-pem (and some other, unrelated fixes)
freeipa server setup and autopkgtest passes fine.

** Bug watch added: Debian Bug tracker #732201
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732201

** Bug watch added: Debian Bug tracker #726073
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726073

** Bug watch added: Debian Bug tracker #726116
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726116

** Bug watch added: Mozilla Bugzilla #1429692
   https://bugzilla.mozilla.org/show_bug.cgi?id=1429692

** Bug watch added: Debian Bug tracker #20
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=20

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

Title:
  nss-pem needs additional headers, static libs to build

Status in nss package in Ubuntu:
  New
Status in nss package in Debian:
  Unknown

Bug description:
  nss-pem is needed for apps linked with libnss3 to read certificates in
  PEM format. This is required when setting up a freeipa server with
  ipa-server-setup, and also certmonger to be able to refresh
  certificates on a freeipa client.

  To be able to build, nss-pem needs some headers and static libs
  provided by nss. They are marked private though, and upstream refuses
  to make them public and Debian maintainer refuses to include them in
  the packaging because of this.

  The required files are blapi.h, alghmac.h, nssckfw.a, nssb.a, freebl.a
  and they could be shipped in a  separate libnss3-pkcs11-dev package,
  because they're not meant for generic consumption via libnss-dev.

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

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

[Touch-packages] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Bryan Quigley]

@markstos
Sorry, yea, I meant our defaults, not the journal config options itself. 
SystemMaxUse= is unset in the config in bionic (although it's all commented 
out, but I believe that's supposed to indicate our defaults?)

Re:disk writing.  I don't disagree, but if we are SRUing it we need to
consider that more.  For 18.04 we can still decide to remove rsyslog to
reduce the impact, we can't do that for 17.10/16.04.

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

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

Bug description:
  [Impact]

   * System logs are lost across reboots because they are not stored
  persistently.

  [Test Case]

   * Fresh installations, or upgrades to this version of systemd, should create 
/var/log/journal and trigger automatic persistent logs.
   * Users may choose to remove said directory, or disable persistent logging 
in /etc/systemd/journald.conf

  [Regression Potential]

   * Persistent logging by default will cause logs to be flushed from
  /run to /var/log, meaning there will be less RAM used (/run is tmpfs
  backed), but increased disk usage (in /var/log). The journald daemon
  has limits set for logs, meaning they will be rotated and discarded
  and should not cause out of disk-space errors.

  [Other Info]
   
   * Original bug report

  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't.
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

-- 
Mailing list: https://launchpad.net/~touch-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)

[Mythological]

Bill Miller, I can ssh into the system and install packages - apt-get
still works, etc.  Right now the only thing I can't do is get into the
desktop; it shows a login screen but won't accept my password (even
though my password works fine in ssh).  I think it is because when I
tried to install the nVida Linux drivers it removed Noveau, and I can't
seem to get it back.

What I am not understanding is what you meant by "the -112" - I assume
you are talking about a version number or something, but of what?  I
went to that link but they are using Synaptic and I have no way to get
to that because I can't get into the desktop.  Also, unlike that guy, as
far as i know I did not "made the mistake of purging the functional
kernel" which means that the previous kernel is probably still around on
the hard drive, I just don't know how you would set it up to boot into
the previous kernel rather than the new kernel.

Rather than continue this discussion here I suggest we move it to
https://ubuntuforums.org/showthread.php?t=2385621=13742281#post13742281
as this is probably not appropriate for the bug tracker, and I suspect
many others are affected by this and would like to find a solution.

-- 
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)

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.

  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: 

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

[Andreas Hasenack]

** Changed in: landscape-client (Ubuntu)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: landscape-client (Ubuntu)
   Status: New => In Progress

** Changed in: landscape-client (Ubuntu Yakkety)
   Status: New => Won't Fix

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

Title:
  scheduled shutdown -r  does not work without dbus in xenial LXC
  container

Status in Landscape Client:
  Fix Committed
Status in landscape-client package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Xenial:
  New
Status in systemd source package in Xenial:
  Won't Fix
Status in landscape-client source package in Yakkety:
  Won't Fix
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  The command "shutdown -r +5" doesn't work in a xenial lxc container. I
  found this out by trying to use Landscape to restart a xenial lxc
  container and the operation failed. I was told by the Landscape team
  that the restart button simply does a "shutdown -r +5".

  The problem seems to be that the dbus package is missing in the xenial
  lxc image.

  This is what happens:

  root@xenialtest:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  And if I install dbus:

  root@xenialtest:/# shutdown -r +5
  Shutdown scheduled for Wed 2016-06-08 19:28:44 UTC, use 'shutdown -c' to 
cancel.

  The issue happens whether I use the download template or the ubuntu
  template when creating the LXC container:

  root@davecorelaptop:/var/cache/lxc# lxc-create -t ubuntu -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-start -d -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-attach -n test2

  root@test2:/# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  root@test2:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  
  or

  
  root@davecorelaptop:~# lxc-create -t download -n test
  Setting up the GPG keyring
  Downloading the image index

  ---
  DIST  RELEASE ARCHVARIANT BUILD
  ---
  alpine3.0 amd64   default 20160608_18:03
  alpine3.0 i386default 20160608_17:50
  alpine3.1 amd64   default 20160608_17:50
  alpine3.1 i386default 20160608_18:03
  alpine3.2 amd64   default 20160608_17:50
  alpine3.2 i386default 20160608_17:50
  alpine3.3 amd64   default 20160608_17:50
  alpine3.3 i386default 20160608_17:50
  alpineedgeamd64   default 20160608_17:50
  alpineedgei386default 20160608_17:50
  centos6   amd64   default 20160609_02:16
  centos6   i386default 20160609_02:16
  centos7   amd64   default 20160609_02:16
  debianjessie  amd64   default 20160608_22:42
  debianjessie  arm64   default 20160609_02:38
  debianjessie  armel   default 20160608_22:42
  debianjessie  armhf   default 20160608_22:42
  debianjessie  i386default 20160608_22:42
  debianjessie  powerpc default 20160608_22:42
  debianjessie  ppc64el default 20160608_22:42
  debianjessie  s390x   default 20160608_22:42
  debiansid amd64   default 20160608_22:42
  debiansid arm64   default 20160608_22:42
  debiansid armel   default 20160608_22:42
  debiansid armhf   default 20160608_22:42
  debiansid i386default 20160608_22:42
  debiansid powerpc default 20160608_22:42
  debiansid ppc64el default 20160608_22:42
  debiansid s390x   default 20160608_22:42
  debianstretch amd64   default 20160608_22:42
  debianstretch arm64   default 20160608_22:42
  debianstretch armel   default 20160608_22:42
  debianstretch armhf   default 20160608_22:42
  debianstretch i386default 20160608_22:42
  debianstretch powerpc default 20160608_22:42
  debianstretch ppc64el default 20160608_22:42
  debianstretch s390x   default 20160608_22:42
  debianwheezy  amd64   default 20160608_22:42
  debianwheezy  armel   default 20160608_22:42
  debianwheezy  armhf   default 20160608_22:42
  debianwheezy  i386default 20160608_22:42
  debianwheezy  powerpc default 20160609_02:38
  debianwheezy  s390x   default 20160608_22:42
  fedora22  amd64   default 20160609_01:27
  fedora22  armhf   default 20160112_01:27
  fedora22  i386default 20160609_01:27
  fedora23  amd64   default 20160609_01:27
  

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

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-384 (Ubuntu)
   Status: New => 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/1750937

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

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.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+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 1751139] [NEW] package linux-image-4.15.0-10-generic 4.15.0-10.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Don Forigua]

Public bug reported:

Just update my system

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-32-generic.
AplayDevices:
  List of PLAYBACK Hardware Devices 
 card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 
82801AA-ICH]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  diego   847 F pulseaudio
Card0.Amixer.info:
 Card hw:0 'I82801AAICH'/'Intel 82801AA-ICH with AD1980 at irq 21'
   Mixer name   : 'Analog Devices AD1980'
   Components   : 'AC97a:41445370'
   Controls  : 46
   Simple ctrls  : 32
Date: Thu Feb 22 15:52:49 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2018-02-22 (0 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221)
IwConfig:
 lono wireless extensions.
 
 enp0s3no wireless extensions.
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcFB: 0 vboxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=ce9e5e18-ee32-4c46-853e-74d50d70f85d ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No existe el archivo o el directorio: "/root/Error: 
command ['which', 'python'] failed with exit code 1:": "/root/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
RelatedPackageVersions: grub-pc 2.02-2ubuntu7
RfKill:
 
SourcePackage: initramfs-tools
Title: package linux-image-4.15.0-10-generic 4.15.0-10.11 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: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-package bionic

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

Title:
  package linux-image-4.15.0-10-generic 4.15.0-10.11 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:
  Just update my system

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-32-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 
82801AA-ICH]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego   847 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801AAICH'/'Intel 82801AA-ICH with AD1980 at irq 21'
 Mixer name : 'Analog Devices AD1980'
 Components : 'AC97a:41445370'
 Controls  : 46
 Simple ctrls  : 32
  Date: Thu Feb 22 15:52:49 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2018-02-22 (0 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=ce9e5e18-ee32-4c46-853e-74d50d70f85d ro quiet splash
  PulseList: 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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)

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.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+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 1751140] [NEW] nss-pem needs additional headers, static libs to build

[Timo Aaltonen]

Public bug reported:

nss-pem is needed for apps linked with libnss3 to read certificates in
PEM format. This is required when setting up a freeipa server with ipa-
server-setup, and also certmonger to be able to refresh certificates on
a freeipa client.

To be able to build, nss-pem needs some headers and static libs provided
by nss. They are marked private though, and upstream refuses to make
them public and Debian maintainer refuses to include them in the
packaging because of this.

The required files are blapi.h, alghmac.h, nssckfw.a, nssb.a, freebl.a
and they could be shipped in a  separate libnss3-pkcs11-dev package,
because they're not meant for generic consumption via libnss-dev.

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

** Affects: nss (Debian)
 Importance: Unknown
 Status: Unknown

** Summary changed:

- nss-pem needs blapi.h, alghmac.h, nssckfw.a, nssb.a, freebl.a
+ nss-pem needs additional headers, static libs to build

** Bug watch added: Debian Bug tracker #855879
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855879

** Also affects: nss (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855879
   Importance: Unknown
   Status: Unknown

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

Title:
  nss-pem needs additional headers, static libs to build

Status in nss package in Ubuntu:
  New
Status in nss package in Debian:
  Unknown

Bug description:
  nss-pem is needed for apps linked with libnss3 to read certificates in
  PEM format. This is required when setting up a freeipa server with
  ipa-server-setup, and also certmonger to be able to refresh
  certificates on a freeipa client.

  To be able to build, nss-pem needs some headers and static libs
  provided by nss. They are marked private though, and upstream refuses
  to make them public and Debian maintainer refuses to include them in
  the packaging because of this.

  The required files are blapi.h, alghmac.h, nssckfw.a, nssb.a, freebl.a
  and they could be shipped in a  separate libnss3-pkcs11-dev package,
  because they're not meant for generic consumption via libnss-dev.

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

-- 
Mailing list: https://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 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Mark Stosberg]

> @xnox
> "The journald daemon has limits set for logs, meaning they will be 
> rotated and discarded and should not cause out of disk-space errors."
> 
> What are they?  AFAICT it only has limits on the number of files, but
> not how big they can overall become.

The limits are documented in `man journald.conf`.

One of them is " SystemMaxUse=, ", which is based on disk usage, not
file size.

> I'm also thinking that the duplicate writing of logs could cause other 
> regressions, one example being where high disk throughput is ongoing and 
> many things being written to the logs. Thoughts?

Additional disk writing is somewhat mitigated by the general increase in
disk performance over time in new hardware

As one user found here, SSD is about 5x faster than HDD and the newer NVMe SSDs 
are about
5x faster than the older SSDs. A new NVMe SSD is about 25x faster than an HDD.

https://photographylife.com/nvme-vs-ssd-vs-hdd-performance

The idea here is to be "safe by default". People are welcome to
prioritize performance and reduce logging beyond the defaults.

Mark

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

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

Bug description:
  [Impact]

   * System logs are lost across reboots because they are not stored
  persistently.

  [Test Case]

   * Fresh installations, or upgrades to this version of systemd, should create 
/var/log/journal and trigger automatic persistent logs.
   * Users may choose to remove said directory, or disable persistent logging 
in /etc/systemd/journald.conf

  [Regression Potential]

   * Persistent logging by default will cause logs to be flushed from
  /run to /var/log, meaning there will be less RAM used (/run is tmpfs
  backed), but increased disk usage (in /var/log). The journald daemon
  has limits set for logs, meaning they will be rotated and discarded
  and should not cause out of disk-space errors.

  [Other Info]
   
   * Original bug report

  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't.
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

-- 
Mailing list: https://launchpad.net/~touch-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)

[Bill Miller]

Mythological, you have to fix the system to the point that you can
install packages. I am not sure you are that point yet from your
description.  Once you are there, you can install an old kernel by
following the procedure outlined here
https://askubuntu.com/questions/928146/install-an-older-kernel-14-04-lts
If you can only log into a terminal, you need to identify the 4 kernel
packages you want and install them with sudo apt install [packagenames]

-- 
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)

Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  New
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.

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

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

[Mythological]

Bo9b Miller, how do I install "-112"?  I am afraid I have already dug
myself into so deep a hole I don't want to make any more mistakes, and I
have no idea what you mean by "-112".  Please explain, or point me to a
page that does.

-- 
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)

Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  New
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.

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

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

[Mythological]

Bob Miller, how do I install "-112"? I am afraid I have already dug
myself into so deep a hole I don't want to make any more mistakes, and I
have no idea what you mean by "-112". Please explain, or point me to a
page that does.

-- 
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)

Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  New
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.

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

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

[gumbeto]

Same thing here on 16.04, with nvidia driver 384.111. 
Kernel 4.4.0-112: no problems
kernel 4.4.0-116: Low res and can't login on graphical mode. 

I have tried to uninstall and reinstall nvidia drivers to no effect.

I did a diff for dmesg output on both cases. The relevant bits are:

> Spectre V2 mitigation: Mitigation: Full generic retpoline
> Spectre V2 mitigation: Speculation control IBPB not-supported IBRS 
> not-supported

and

< nvidia: module license 'NVIDIA' taints kernel.
< Disabling lock debugging due to kernel taint
< nvidia: module verification failed: signature and/or required key missing - 
tainting kernel
---
> nvidia: version magic '4.4.0-116-generic SMP mod_unload modversions ' should 
> be '4.4.0-116-generic SMP mod_unload modversions retpoline '
> nvidia: version magic '4.4.0-116-generic SMP mod_unload modversions ' should 
> be '4.4.0-116-generic SMP mod_unload modversions retpoline '


** Also affects: nvidia-graphics-drivers-384 (Ubuntu)
   Importance: Undecided
   Status: New

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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)

Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  New
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.

  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:

[Touch-packages] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Bryan Quigley]

@xnox
"The journald daemon has limits set for logs, meaning they will be rotated and 
discarded and should not cause out of disk-space errors."

What are they?  AFAICT it only has limits on the number of files, but
not how big they can overall become.


I'm also thinking that the duplicate writing of logs could cause other 
regressions, one example being where high disk throughput is ongoing and many 
things being written to the logs. Thoughts?

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

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

Bug description:
  [Impact]

   * System logs are lost across reboots because they are not stored
  persistently.

  [Test Case]

   * Fresh installations, or upgrades to this version of systemd, should create 
/var/log/journal and trigger automatic persistent logs.
   * Users may choose to remove said directory, or disable persistent logging 
in /etc/systemd/journald.conf

  [Regression Potential]

   * Persistent logging by default will cause logs to be flushed from
  /run to /var/log, meaning there will be less RAM used (/run is tmpfs
  backed), but increased disk usage (in /var/log). The journald daemon
  has limits set for logs, meaning they will be rotated and discarded
  and should not cause out of disk-space errors.

  [Other Info]
   
   * Original bug report

  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't.
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

-- 
Mailing list: https://launchpad.net/~touch-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)

[gumbeto]

** Summary changed:

- 14.04 Kernel update on 2/21 breaks Nvidia drivers
+ 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.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)

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.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+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 1750593] Re: Misspelled word in description-en for unity-scopes-runner

[Jeremy Nation]

Thanks for confirming the problem.

I'm not interested in using apport/ubuntu-bug to submit reports, though
I understand why the wiki recommends it. In any case it does not appear
to have been necessary for this issue.

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

Title:
  Misspelled word in description-en for unity-scopes-runner

Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  For package "unity-scopes-runner", version
  "7.1.4+16.04.20180209.1-0ubuntu1", the "Description-en" value is:

  ```
  Description-en: desktop runner for misceallenous scopes
   The scope runner is a handy tool for wrapping on a desktop the various
   scoped installed on the system.
  ```

  "misceallenous" should be spelled "miscellaneous".

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

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

[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Dean Henrichsmeyer]

Let's make sure this is fixed for bionic. The scope of nameservers has
changed and maas should do the right thing.

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Triaged
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 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 maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution

  [...]

  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms

  =
  Xenial
  ==

  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  dns-nameservers 10.90.90.1
  dns-search maaslab maas

  auto enp0s25
  iface enp0s25 inet static
  address 10.90.90.162/24
  gateway 10.90.90.1
  mtu 1500
  ubuntu@node05:~$ 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
  nameserver 10.90.90.1
  search maaslab maas

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions

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

[Touch-packages] [Bug 1750593] Re: Misspelled word in description-en for unity-scopes-runner

[Hans Joachim Desserud]

Thanks for taking your time to report this issue and help making Ubuntu
better.

I can confirm this typo is still present in
7.1.4+18.04.20180209.1-0ubuntu1. I suspect it originates from the
debian/control file, since that's the only place I can see it in the
source package.

Btw, when reporting bugs in the future please use apport by using
'ubuntu-bug' and the name of the package affected. You can learn more
about this functionality at https://wiki.ubuntu.com/ReportingBugs.

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

** Tags added: bionic bitesize packaging string-fix

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

Title:
  Misspelled word in description-en for unity-scopes-runner

Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  For package "unity-scopes-runner", version
  "7.1.4+16.04.20180209.1-0ubuntu1", the "Description-en" value is:

  ```
  Description-en: desktop runner for misceallenous scopes
   The scope runner is a handy tool for wrapping on a desktop the various
   scoped installed on the system.
  ```

  "misceallenous" should be spelled "miscellaneous".

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

-- 
Mailing list: https://launchpad.net/~touch-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: 14.04 Kernel update on 2/21 breaks Nvidia drivers

[Bill Miller]

Mythological, instead of waiting for a new kernel, you could install the
-112 instead, it still works fine.

-- 
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:
  14.04 Kernel update on 2/21 breaks Nvidia drivers

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.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+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 1751120] Re: Xorg freeze when moving a window between external/internal monitors

[Dan Watkins]

** Attachment added: "20180222_133958.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1751120/+attachment/5060610/+files/20180222_133958.jpg

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

Title:
  Xorg freeze when moving a window between external/internal monitors

Status in xorg package in Ubuntu:
  New

Bug description:
  My mouse cursor would still move, but I couldn't do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 13:44:42 2018
  DistUpgraded: 2018-01-23 11:42:22,182 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.6, 4.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad T440p [17aa:220e]
  InstallationDate: Installed on 2017-10-23 (121 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20ANCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-01-23 (30 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET70WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ANCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET70WW(2.24):bd05/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20ANCTO1WW
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  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/xorg/+bug/1751120/+subscriptions

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

[Touch-packages] [Bug 1751120] [NEW] Xorg freeze when moving a window between external/internal monitors

[Dan Watkins]

Public bug reported:

My mouse cursor would still move, but I couldn't do anything.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 22 13:44:42 2018
DistUpgraded: 2018-01-23 11:42:22,182 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.2.6, 4.13.0-32-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Once a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo ThinkPad T440p [17aa:220e]
InstallationDate: Installed on 2017-10-23 (121 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 20ANCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to bionic on 2018-01-23 (30 days ago)
dmi.bios.date: 05/21/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GLET70WW (2.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20ANCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGLET70WW(2.24):bd05/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T440p
dmi.product.name: 20ANCTO1WW
dmi.product.version: ThinkPad T440p
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
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 freeze single-occurrence third-party-packages 
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/1751120

Title:
  Xorg freeze when moving a window between external/internal monitors

Status in xorg package in Ubuntu:
  New

Bug description:
  My mouse cursor would still move, but I couldn't do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 13:44:42 2018
  DistUpgraded: 2018-01-23 11:42:22,182 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.6, 4.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad T440p [17aa:220e]
  InstallationDate: Installed on 2017-10-23 (121 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20ANCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-01-23 (30 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET70WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ANCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  

[Touch-packages] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Brian Murray]

Hello Mark, or anyone else affected,

Accepted systemd into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu12.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: systemd (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

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

Bug description:
  [Impact]

   * System logs are lost across reboots because they are not stored
  persistently.

  [Test Case]

   * Fresh installations, or upgrades to this version of systemd, should create 
/var/log/journal and trigger automatic persistent logs.
   * Users may choose to remove said directory, or disable persistent logging 
in /etc/systemd/journald.conf

  [Regression Potential]

   * Persistent logging by default will cause logs to be flushed from
  /run to /var/log, meaning there will be less RAM used (/run is tmpfs
  backed), but increased disk usage (in /var/log). The journald daemon
  has limits set for logs, meaning they will be rotated and discarded
  and should not cause out of disk-space errors.

  [Other Info]
   
   * Original bug report

  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't.
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Brian Murray]

Hello bugproxy, or anyone else affected,

Accepted systemd into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu12.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: systemd (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-artful

-- 
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:
  Triaged
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 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu

[Brian Murray]

Hello Michael, or anyone else affected,

Accepted systemd into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu12.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: systemd (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  DNS doesn't work in no-cloud as launched by ubuntu

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * resolved does not start early enough in the boot-process preventing
  DNS resolution to be operational during early boot, for example as
  required by special early stages of cloud-init, resulting in failure
  to boot / provision the instance fully.

  [Test Case]

   * Boot container or a VM with a nocloud-net data source, and a URL pointing 
to the datasource as explained below
   * Observe that boot completes and provisioning is successful
   * Check that there are no dns-resolution errors in the cloud-init log / boot 
log

  [Regression Potential]

   * starting resolved earlier may prevent it from connecting to dbus,
  and may require a restart later on when re-triggered over dbus. This
  is on artful only, as in bionic resolved has gained ability to
  reconnected to dbus post-start. Backporting that, however, is too
  large for an SRU as it requires sd-bus changes.

  [Other Info]
   
   * Original bug report.

  I use no-cloud to test the kernel in CI (I am maintainer of the bcache
  subsystem), and have been running it successfully under 16.04 cloud
  images from qemu, using a qemu command that includes:

  -smbios "type=1,serial=ds=nocloud-
  net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-
  metadata/linuxtst/"

  As documented here:

  http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html

  Under the new 17.10 cloud images, this doesn't work: the network comes
  up, but name resolution doesn't work-- /etc/resolv.conf is a symlink
  to a nonexistent file at this point of the boot and systemd-resolved
  is not running.  When I manually hack /etc/resolv.conf in the cloud
  image to point to 4.2.2.1 it works fine.

  I don't know if nameservice not working is by design, but it seems
  like it should work.  The documentation states:

  "With ds=nocloud-net, the seedfrom value must start with http://,
  https:// or ftp://;

  And https is not going to work for a raw IP address.

  Related bugs:
   * bug 1734939: #include fails silently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1734167/+subscriptions

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

[Touch-packages] [Bug 1750608] Re: Fixup ADT tests

[Brian Murray]

Hello Dimitri, or anyone else affected,

Accepted systemd into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu12.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: systemd (Ubuntu Artful)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  Fixup ADT tests

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   In artful, there are autopkgtest failures that can be improved/fixed
  with the following commits:

   * stop using ext3, and instead use ext4 as fsck.ext3 may be missing
  in the initramfs.

   * correctly parse prefixes, when parsing units and deciding which
  binaries to copy into the test image.

  
  These are changes to the setup codes of the test-suite, and no change in test 
assertions being made. Hopefully this will make adt results more green.

  [Test Case]

   * Check that autopkgtests are not failing with missing fsck.ext3
   * Check that autopkgtesta are not failing with failing to copy referenced 
binaries

  [Regression Potential]

   * No changes to the code shipped / binaries shipped

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

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

[Touch-packages] [Bug 1725348] Re: Systemd - Bypassing MemoryDenyWriteExecution policy

[Brian Murray]

Hello Thomas, or anyone else affected,

Accepted systemd into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu12.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: systemd (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  Systemd - Bypassing MemoryDenyWriteExecution policy

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

Bug description:
  [Impact]

   * MemoryDenyWritePolicy can be bypassed by using a slightly different
  syscall.

  [Test Case]

   * Check that MemoryDenyWritePolicy, blocks pkey_mprotect as well as
  mprotect.

  [Regression Potential]

   * Upstream fix cherrypick, security vulnerability.

  [Other Info]
   
   * Original report

  Hello,

  We would like to report to you a vulnerability about systemd which
  allows to bypass the MemoryDenyWriteExecution policy on Linux 4.9+.

  The vulnerability is described in the attached PDF file.

  Sincerely,
  Thomas IMBERT

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

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

[Touch-packages] [Bug 1737570] Re: Add support for RequiredForOnline in networkd

[Brian Murray]

Hello Dimitri, or anyone else affected,

Accepted systemd into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu12.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: systemd (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  Add support for RequiredForOnline in networkd

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

Bug description:
  [Impact]

   * netplan & networkd based systems typically await networking to be
  up on boot, without any ability to specify that an interface should be
  configured, but might not be online at boot. This is a backport of the
  RequiredForOnline= feature to match optional=true in netplan.

  [Test Case]

   * Configure a netowkring interface using .link/.network file and specify 
RequiredForOnline=False
   * Bring the interface down / offline it
   * execute systemd-networkd-wait-online, which should exit immediately since 
no interfaces are required to be online

  [Regression Potential]

   * This adds a support for an additional stanza in the network files.
  This stanza is not used by default. if the stanza is used, but older
  networkd is in use, networkd will ignore this unknown stanza. Thus
  this change is backward and forward compatible. The difference is that
  boot is not blocked awaiting systemd-networkd-wait-online to timeout.

  [Other Info]
   
   * Original bug report

  Add support for RequiredForOnline in networkd

  
https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be

  RequiredForOnline= denotes a link/network that does/does not require being up
  for systemd-networkd-wait-online to consider the system online; this makes it
  possible to ignore devices without modifying parameters to wait-online.

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

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

[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore

[Brian Murray]

Hello Nicolino, or anyone else affected,

Accepted systemd into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu12.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: systemd (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  Networkd fail to set ip address between leases if ip address changes
  on UbuntuCore

Status in Snappy:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * networkd fails to renew a lease, specifically it fails to change IPv4 
address via DHCP renew/rebind.
   * networkd relies on a kernel feature to promote secondary IPv4 address to 
primary, upon primary address lease expiry.
   * this sysctl tunable was not enabled by default in systemd.

  [Test Case]

  Add a device, and assign two IPv4 addresses. First one, with a short
  lease time. Second one, with a different ip and a longer lease time.
  Second one should be treated as secondary ip address, and upon expiry
  of the first one, should be promoted and become primary ip address.
  The below scripted instructions simulate this:

  sudo ip link add name testleases type dummy

  sudo ip address add 192.0.2.10/27 dev testleases \
    valid_lft 5 preferred_lft 5

  sudo ip address add 192.0.2.11/27 dev testleases \
    valid_lft 11 preferred_lft 11

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \
  && echo ok || echo not ok

  sleep 6

  ip address list dev testleases | \
  grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \
  && echo ok || echo not ok

  sudo ip link del dev testleases

  [Regression Potential]

   * This changes the default kernel behaviour, previously upon expiry
  of the primary address, secondary addresses were removed as well.
  Which is imho silly.

  * comparing networkd renewal with isc-dhcp renewal the semantics are
  quite different. Upon acquiring new ip address, isc-dhcp would
  instantly flush existing ip address, and add a new one. Networkd add
  the new address as secondary, and waits for old one to expire first
  before promoting / switching to using the new ip address. IMHO kernel
  should have an API to promote secondary ip address to a primary one.

  * This update also applies other safe-looking options, which are
  currently also already applied via sysctls shipped in other packages

  # Source route verification
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.all.rp_filter = 1

  # Do not accept source routing
  net.ipv4.conf.default.accept_source_route = 0
  net.ipv4.conf.all.accept_source_route = 0

  # Enable hard and soft link protection
  fs.protected_hardlinks = 1
  fs.protected_symlinks = 1

  * This update also applies the following upstream/bufferbloat.net
  recommended setting

  # Fair Queue CoDel packet scheduler to fight bufferbloat
  net.core.default_qdisc = fq_codel

  * [~racb] There are complex network setups out there, such as HA with
  corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
  fix were SRU'd, will all of these things in the wild cope with this
  sysctl change?

  [Other Info]

   * Original bug report

  Hi there,
  we found a replicable issue that involves the Ubuntu Core networking and 
causes complete loss of connectivity.
  We run a custom board with ubuntu core: the architecure is amrhf.
  We replicated this issue with an official Ubuntu Core image on a Raspberry 
Pi: other platform was been tested.
  It shows that it is a snap core problem which interests networkd: we use the 
default network stack 

[Touch-packages] [Bug 1734410] Re: systemd: handle undelegated cgroup2 hierarchy

[Brian Murray]

Hello Christian, or anyone else affected,

Accepted systemd into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu12.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: systemd (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  systemd: handle undelegated cgroup2 hierarchy

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

Bug description:
  [Impact]

   * When a container is presented with a unified cgroup hierarchy,
  which is not properly delegated, systemd should not attempt (and fail)
  to use. This improves compatibility of xenial containers running on
  unified cgroup hierarchy hosts.

  [Test Case]

   * Xenial containers should boot, with non-writable unified cgroup
  hierarchy hosts.

  [Regression Potential]

   * unified cgroup hierarchy is not in use by default on xenial hosts,
  thus this is forward compatibility improvment with e.g. bionic hosts
  running xenial containers.

  [Other Info]
   
   * Original bug report

  Hey everyone,

  Current systemd versions all fail when the unified cgroup hierarchy is
  not-writable. This is especially problematic in containers where the
  systemd administrator might decide to not delegate the unified
  hierarchy or when running with a liblxc driver that doesn't yet know
  how to handle the unified cgroup hierarchy. I've pushed patches to
  systemd upstream that let systemd ingnore the non-delegated unified
  hierarchy. The relevant commits are:

  e07aefbd675b651f8d45b5fb458f2747b04d6e04
  2d56b80a1855836abf1d7458394c345ad9d55382
  1ff654e28b7b8e7d0a0be33522a84069ac6b07c0

  These patches will be in 236 but should be backported from xenial
  upwards.

  Christian

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

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

[Touch-packages] [Bug 1736955] Re: dep8 test systemd-fsckd fails on s390

[Brian Murray]

Hello Andreas, or anyone else affected,

Accepted systemd into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu12.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: systemd (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  dep8 test systemd-fsckd fails on s390

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Fix Committed

Bug description:
  The systemd-fsckd test has a constraint of isolation-machine, among
  others. Until recently, that actually prevented it from running on
  s390 because we were using containers for it.

  About 3 weeks ago, apparently we started using VMs for s390 dep8
  tests, so that constraint was finally satisfied and systemd-fsckd
  started to run. And to fail consistently, as can be see in
  http://autopkgtest.ubuntu.com/packages/s/systemd/artful/s390x:

  Traceback (most recent call last):
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 267, in 
  boot_with_systemd_distro()
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 243, in boot_with_systemd_distro
  enable_plymouth()
    File "/tmp/autopkgtest.PrPiv9/build.iis/src/debian/tests/systemd-fsckd", 
line 224, in enable_plymouth
  plymouth_enabled = 'splash' in open('/boot/grub/grub.cfg').read()
  FileNotFoundError: [Errno 2] No such file or directory: '/boot/grub/grub.cfg'

  There is no grub for s390, so this test must be adjusted or skipped in
  that architecture.

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

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

[Touch-packages] [Bug 1734908] Re: systemd-rfkill service times out when a new rfkill device is added

[Brian Murray]

Hello Kleber, or anyone else affected,

Accepted systemd into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu12.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!

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

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

Title:
  systemd-rfkill service times out when a new rfkill device is added

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The following issue was observed while running network-
  manager=1.8.4-1ubuntu3 autopkgtest on Artful with
  systemd=234-2ubuntu12.1:

  ---
  Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start 
operation timed out. Terminating.
  Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill 
Switch Status.
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered 
failed state.
  Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with 
result 'timeout'.
  ---

  This happens after the testcase inserts the fake-rfkill module (a
  module shipped with network-manager tests that registers a new fake
  device with the rfkill subsystem).

  On Artful, it causes the network-manager autopkgtest killswitches-no-
  urfkill to fail (see bug 1733321). The testcase reveals that when
  running network-manager cli to query the status of a WiFi interface
  ('nmcli radio wifi') it can report the wrong state of the device after
  'rfkill block/unblock' is run to change the device 'Soft blocked'
  state. This can affect the state of the device presented to the user.

  [Fix]

  The issue is fixed by the following systemd upstream patches:

  ---
  
https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac

  commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f
  Author: S. Fan 
  Date:   Mon Jul 31 05:10:10 2017 -0500

  rfkill: fix erroneous behavior when polling the udev monitor
  (#6489)

  Comparing udev_device_get_sysname(device) and sysname will always return
  true. We need to check the device received from udev monitor instead.

  Also, fd_wait_for_event() sometimes never exits. Better set a timeout
  here.
  ---

  ---
  
https://github.com/systemd/systemd/commit/c7f6ca9379279affa8f22d15fa13063491f86a49#diff-275947967677827e2b72930d97f1b8ac

  commit c7f6ca9379279affa8f22d15fa13063491f86a49
  Author: Xiang Fan 
  Date:   Wed Aug 9 05:51:53 2017 -0500

  rfkill: fix typo (#6574)
  ---

  With the fixes, the output from systemd-rfkill is:

  ---
  Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Nov 28 15:27:59 autopkgtest systemd-rfkill[14843]: Timed out waiting for udev 
monitor.
  Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch 
Status.
  ---

  The patches are needed to fix the ADT tests observed with Artful tests on 
ppc64el architecture:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz

  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  [Regression 

[Touch-packages] [Bug 1737570] Re: Add support for RequiredForOnline in networkd

[Dimitri John Ledkov]

** Description changed:

+ [Impact]
+ 
+  * netplan & networkd based systems typically await networking to be up
+ on boot, without any ability to specify that an interface should be
+ configured, but might not be online at boot. This is a backport of the
+ RequiredForOnline= feature to match optional=true in netplan.
+ 
+ [Test Case]
+ 
+  * Configure a netowkring interface using .link/.network file and specify 
RequiredForOnline=False
+  * Bring the interface down / offline it
+  * execute systemd-networkd-wait-online, which should exit immediately since 
no interfaces are required to be online
+ 
+ [Regression Potential]
+ 
+  * This adds a support for an additional stanza in the network files.
+ This stanza is not used by default. if the stanza is used, but older
+ networkd is in use, networkd will ignore this unknown stanza. Thus this
+ change is backward and forward compatible. The difference is that boot
+ is not blocked awaiting systemd-networkd-wait-online to timeout.
+ 
+ [Other Info]
+  
+  * Original bug report
+ 
  Add support for RequiredForOnline in networkd
  
  
https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be
  
  RequiredForOnline= denotes a link/network that does/does not require being up
  for systemd-networkd-wait-online to consider the system online; this makes it
  possible to ignore devices without modifying parameters to wait-online.

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

Title:
  Add support for RequiredForOnline in networkd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  In Progress
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * netplan & networkd based systems typically await networking to be
  up on boot, without any ability to specify that an interface should be
  configured, but might not be online at boot. This is a backport of the
  RequiredForOnline= feature to match optional=true in netplan.

  [Test Case]

   * Configure a netowkring interface using .link/.network file and specify 
RequiredForOnline=False
   * Bring the interface down / offline it
   * execute systemd-networkd-wait-online, which should exit immediately since 
no interfaces are required to be online

  [Regression Potential]

   * This adds a support for an additional stanza in the network files.
  This stanza is not used by default. if the stanza is used, but older
  networkd is in use, networkd will ignore this unknown stanza. Thus
  this change is backward and forward compatible. The difference is that
  boot is not blocked awaiting systemd-networkd-wait-online to timeout.

  [Other Info]
   
   * Original bug report

  Add support for RequiredForOnline in networkd

  
https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be

  RequiredForOnline= denotes a link/network that does/does not require being up
  for systemd-networkd-wait-online to consider the system online; this makes it
  possible to ignore devices without modifying parameters to wait-online.

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

-- 
Mailing list: https://launchpad.net/~touch-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: 14.04 Kernel update on 2/21 breaks Nvidia drivers

[Mythological]

One more to report, this one got my son's computer, an older Asrock
machine.  Uninstalling the nVidia drivers allowed booting into the
desktop but then when none of the available nVidia drivers worked we
made the mistake of trying to install the Linux driver from nVidia's
site.  Apparently somewhere in the process it uninstalled the Noveau
drivers and now we can't even log into the system except via ssh.

I then tried reinstalling the Noveau package xserver-xorg-video-nouveau
and it claims it cannot be installed because

The following packages have unmet dependencies:
xserver-xorg-video-nouveau : Depends: xorg-video-abi-15
 Depends: xserver-xorg-core (>= 2:1.14.99.902)
 Recommends: libgl1-mesa-dri (>= 9.0)

If I tried to reinstall the xorg/xserver stuff, no matter what I tried I
kept getting these:

The following packages have unmet dependencies:
unity-control-center : Depends: libcheese-gtk23 (>= 3.4.0) but it is not going 
to be installed
   Depends: libcheese7 (>= 3.0.1) but it is not going to be 
installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

But if I try to install those I get:

libcheese-gtk23 is already the newest version.
libcheese7 is already the newest version.

And if I tried to force install them, it showed that it is already
running libcheese-gtk23:amd64 (3.10.2-0ubuntu2) and libcheese7:amd64
(3.10.2-0ubuntu2) which are both higher versions than what xorg seems to
require, so I don't understand what is going on here.  Anyway, at this
point the system is pretty much totally broken as far as getting into
the desktop is concerned.

Is there any chance you can fix this and get a new kernel update out
very soon, like tonight or tomorrow?  Because if not, it looks like I
may have to reinstall from scratch, and even then I'm not entirely
certain I won't run into the exact same 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/1750937

Title:
  14.04 Kernel update on 2/21 breaks Nvidia drivers

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.

  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
 

[Touch-packages] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Dimitri John Ledkov]

** Description changed:

+ [Impact]
+ 
+  * System logs are lost across reboots because they are not stored
+ persistently.
+ 
+ [Test Case]
+ 
+  * Fresh installations, or upgrades to this version of systemd, should create 
/var/log/journal and trigger automatic persistent logs.
+  * Users may choose to remove said directory, or disable persistent logging 
in /etc/systemd/journald.conf
+ 
+ [Regression Potential]
+ 
+  * Persistent logging by default will cause logs to be flushed from /run
+ to /var/log, meaning there will be less RAM used (/run is tmpfs backed),
+ but increased disk usage (in /var/log). The journald daemon has limits
+ set for logs, meaning they will be rotated and discarded and should not
+ cause out of disk-space errors.
+ 
+ [Other Info]
+  
+  * Original bug report
+ 
  After upgrading 14.04 -> 16.04, key services are now running on systemd
  and using the systemd journal for logging. In 14.04, key system logs
  like /var/log/messages and /var/log/syslog were persistent, but after
  the upgrade to 16.04 there has a been a regression of sorts: Logs sent
  to systemd's journald are now being thrown away during reboots.
  
  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the 14.04
  -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.
  
  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.
  
  ## Related reference
  
-  * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't. 
-  * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)
+  * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't.
+  * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)
  
  ## Recommended fix
  
  Restoring persistent logging as the default is recommended.

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  In Progress
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * System logs are lost across reboots because they are not stored
  persistently.

  [Test Case]

   * Fresh installations, or upgrades to this version of systemd, should create 
/var/log/journal and trigger automatic persistent logs.
   * Users may choose to remove said directory, or disable persistent logging 
in /etc/systemd/journald.conf

  [Regression Potential]

   * Persistent logging by default will cause logs to be flushed from
  /run to /var/log, meaning there will be less RAM used (/run is tmpfs
  backed), but increased disk usage (in /var/log). The journald daemon
  has limits set for logs, meaning they will be rotated and discarded
  and should not cause out of disk-space errors.

  [Other Info]
   
   * Original bug report

  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   

[Touch-packages] [Bug 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu

[Dimitri John Ledkov]

** Description changed:

+ [Impact]
+ 
+  * resolved does not start early enough in the boot-process preventing
+ DNS resolution to be operational during early boot, for example as
+ required by special early stages of cloud-init, resulting in failure to
+ boot / provision the instance fully.
+ 
+ [Test Case]
+ 
+  * Boot container or a VM with a nocloud-net data source, and a URL pointing 
to the datasource as explained below
+  * Observe that boot completes and provisioning is successful
+  * Check that there are no dns-resolution errors in the cloud-init log / boot 
log
+ 
+ [Regression Potential]
+ 
+  * starting resolved earlier may prevent it from connecting to dbus, and
+ may require a restart later on when re-triggered over dbus. This is on
+ artful only, as in bionic resolved has gained ability to reconnected to
+ dbus post-start. Backporting that, however, is too large for an SRU as
+ it requires sd-bus changes.
+ 
+ [Other Info]
+  
+  * Original bug report.
+ 
  I use no-cloud to test the kernel in CI (I am maintainer of the bcache
  subsystem), and have been running it successfully under 16.04 cloud
  images from qemu, using a qemu command that includes:
  
  -smbios "type=1,serial=ds=nocloud-
  net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-
  metadata/linuxtst/"
  
  As documented here:
  
  http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
  
  Under the new 17.10 cloud images, this doesn't work: the network comes
  up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to
  a nonexistent file at this point of the boot and systemd-resolved is not
  running.  When I manually hack /etc/resolv.conf in the cloud image to
  point to 4.2.2.1 it works fine.
  
  I don't know if nameservice not working is by design, but it seems like
  it should work.  The documentation states:
  
  "With ds=nocloud-net, the seedfrom value must start with http://,
  https:// or ftp://;
  
  And https is not going to work for a raw IP address.
  
  Related bugs:
-  * bug 1734939: #include fails silently.
+  * bug 1734939: #include fails silently.

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

Title:
  DNS doesn't work in no-cloud as launched by ubuntu

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  In Progress
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * resolved does not start early enough in the boot-process preventing
  DNS resolution to be operational during early boot, for example as
  required by special early stages of cloud-init, resulting in failure
  to boot / provision the instance fully.

  [Test Case]

   * Boot container or a VM with a nocloud-net data source, and a URL pointing 
to the datasource as explained below
   * Observe that boot completes and provisioning is successful
   * Check that there are no dns-resolution errors in the cloud-init log / boot 
log

  [Regression Potential]

   * starting resolved earlier may prevent it from connecting to dbus,
  and may require a restart later on when re-triggered over dbus. This
  is on artful only, as in bionic resolved has gained ability to
  reconnected to dbus post-start. Backporting that, however, is too
  large for an SRU as it requires sd-bus changes.

  [Other Info]
   
   * Original bug report.

  I use no-cloud to test the kernel in CI (I am maintainer of the bcache
  subsystem), and have been running it successfully under 16.04 cloud
  images from qemu, using a qemu command that includes:

  -smbios "type=1,serial=ds=nocloud-
  net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-
  metadata/linuxtst/"

  As documented here:

  http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html

  Under the new 17.10 cloud images, this doesn't work: the network comes
  up, but name resolution doesn't work-- /etc/resolv.conf is a symlink
  to a nonexistent file at this point of the boot and systemd-resolved
  is not running.  When I manually hack /etc/resolv.conf in the cloud
  image to point to 4.2.2.1 it works fine.

  I don't know if nameservice not working is by design, but it seems
  like it should work.  The documentation states:

  "With ds=nocloud-net, the seedfrom value must start with http://,
  https:// or ftp://;

  And https is not going to work for a raw IP address.

  Related bugs:
   * bug 1734939: #include fails silently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1734167/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1750741] Re: Memory leak in g_dbus_proxy_new_for_bus_sync()

[Dan Streetman]

Seyeong,

+ - d/p/0001-GDBusProxy-Fix-a-memory-leak-during-
initialization.patch

this fixes a memory leak, but in later code than the Trusty glib2.0 code

+ - d/p/0001-tests-gdatetime-Use-a-real-rather-than-invented-
time.patch

this fixes an autopkgtest regression, that's unrelated to this memleak
bug - it's ok to include in the same upload, but it needs its own lp
bug.  This is also needed in xenial glib2.0.

+ - d/p/0001-gio-Add-names-to-idles-and-timeouts.patch
+ - d/p/0002-gio-belatedly-port-gdbus-from-GSimpleAsyncResult-to-.patch

these patches are huge backports, that update the glib2.0 code to use a
different function that appears to *introduce* the memleak that your
first patch "fixes".  Are you sure there is actually a memleak in the
Trusty glib2.0 code?  If so, it does not seem to be the one that your
first patch fixes.  In any case, this huge backport is not acceptable as
a SRU for only a memleak.

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

Title:
  Memory leak in g_dbus_proxy_new_for_bus_sync()

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  New

Bug description:
  [Impact]

  This issue is found while debugging pacemaker lrmd memory leak

  glib2.0 gio function g_dbus_proxy_new_for_bus_sync has leak as [1]
  said

  this is affected to Trusty

  [Test Case]

  https://pastebin.ubuntu.com/p/fqK6Cx3SKK/
  you can check memory leak with this script

  [Regression]
  This patch is affected to library pkg. so related daemon should be restarted 
after patching. patch itself is very simple and old. it seems verified for few 
years.

  [Others]

  original commit

  
https://gitlab.gnome.org/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c

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

-- 
Mailing list: https://launchpad.net/~touch-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: 14.04 Kernel update on 2/21 breaks Nvidia drivers

[Tim Habigt]

It seems to me that all modules that were re-built with DKMS are
affected by this. For example, I get the same error message when I try
to load the "vboxdrv" module from VirtualBox.

-- 
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:
  14.04 Kernel update on 2/21 breaks Nvidia drivers

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.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+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 1751099] [NEW] Different bugs from what I saw (new linux user)

[Enache Stefan]

Public bug reported:

I had some errors for 2-3 days, but it resolved after I made an update, but I 
wanted to check if I still had some bugs,so I runned the command "ubuntu-bug 
cups" and I found a long row...
I would love some help if you can give it to me, I'm a new user and I don't 
know so much about Linux

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4ubuntu0.4
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: Thu Feb 22 19:04:27 2018
InstallationDate: Installed on 2018-01-31 (22 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Dell Inc. Latitude D620
Papersize: letter
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=c5716610-bf00-4497-938c-dba51b08d432 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0FT292
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd12/18/2006:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0FT292:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D620
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  Different bugs from what I saw (new linux user)

Status in cups package in Ubuntu:
  New

Bug description:
  I had some errors for 2-3 days, but it resolved after I made an update, but I 
wanted to check if I still had some bugs,so I runned the command "ubuntu-bug 
cups" and I found a long row...
  I would love some help if you can give it to me, I'm a new user and I don't 
know so much about Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.4
  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: Thu Feb 22 19:04:27 2018
  InstallationDate: Installed on 2018-01-31 (22 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Latitude D620
  Papersize: letter
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=c5716610-bf00-4497-938c-dba51b08d432 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0FT292
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd12/18/2006:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0FT292:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D620
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Andres Rodriguez]

** Changed in: maas
   Importance: Undecided => Low

** Changed in: maas
   Status: Invalid => Triaged

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Triaged
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 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 maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution

  [...]

  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms

  =
  Xenial
  ==

  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  dns-nameservers 10.90.90.1
  dns-search maaslab maas

  auto enp0s25
  iface enp0s25 inet static
  address 10.90.90.162/24
  gateway 10.90.90.1
  mtu 1500
  ubuntu@node05:~$ 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
  nameserver 10.90.90.1
  search maaslab maas

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions

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

[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel

[Balint Reczey]

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  
  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 21 16:11:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (114 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
  mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 
2016-07-30T12:15:32.706300

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

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

[Touch-packages] [Bug 1737441] Re: /usr/bin/unattended-upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string

[Steve Langasek]

** Also affects: python-apt (Ubuntu Bionic)
   Importance: Undecided
   Status: Confirmed

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

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

Title:
  /usr/bin/unattended-
  
upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string

Status in python-apt package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in python-apt source package in Bionic:
  Confirmed
Status in unattended-upgrades source package in Bionic:
  Invalid

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

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

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

[Touch-packages] [Bug 1749597] Re: [aarch64] gas: Error: non-constant expression in ".if" statement

[Stephen Warren]

For my own understanding, I'm curious:

a) Whether Ubuntu toolchains are usually updated for bugs like this

b) Roughly how often toolchain updates are usually released. I suppose
you're busy with Spectre stuff right now though?

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

Title:
  [aarch64] gas: Error: non-constant expression in ".if" statement

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  New

Bug description:
  gas in binutils 2.26 contains a bug that prevents compilation of ARM
  Trusted Firmware in particular, or any code that references the "."
  symbol following a .align statement that specifies explicit padding
  data.

  ATF bug report: https://github.com/ARM-software/tf-issues/issues/401
  binutils bug report: https://sourceware.org/bugzilla/show_bug.cgi?id=20364

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

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

[Touch-packages] [Bug 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies

[Steve Langasek]

** Also affects: apt (Ubuntu Bionic)
   Importance: Undecided
   Status: Triaged

** Also affects: unattended-upgrades (Ubuntu Bionic)
   Importance: Undecided
   Status: In Progress

** Tags removed: rls-bb-incoming

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

Title:
  linux-cloud-tools version specific packages are being removed by
  unattended-upgrade's  Remove-Unused-Dependencies

Status in apt package in Ubuntu:
  Triaged
Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in apt source package in Bionic:
  Triaged
Status in unattended-upgrades source package in Bionic:
  In Progress

Bug description:
  When running kernel version 4.4.0-78 (for example) and the unattended-
  upgrade packages installs a new kernel 4.4.0-79 (for example) the
  linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic
  packages are removed by the Remove-Unused-Dependencies rule, because
  unlike "normal" kernel packages they are not excluded by
  /etc/apt/apt.conf.d/01autoremove-kernels.

  The linux-cloud-tools package has the hyper-v integration services
  daemons in it, so it's deletion leaves some of the integration not
  working.

  Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other
  hyper-v users aren't caught out by this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 15 15:27:35 2017
  InstallationDate: Installed on 2016-04-25 (415 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
  modified.conffile..etc.update-motd.d.90-updates-available: [deleted]
  modified.conffile..etc.update-motd.d.98-fsck-at-reboot: [deleted]
  modified.conffile..etc.update-motd.d.98-reboot-required: [deleted]
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-04-25T16:28:36.64

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

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

[Touch-packages] [Bug 1749199] Re: purge conf files on removal of upstart (was session fails to start after an upgrade from xenial to bionic)

[Steve Langasek]

** No longer affects: upstart (Ubuntu)

** No longer affects: upstart (Ubuntu Bionic)

** Changed in: xorg (Ubuntu Bionic)
   Importance: Undecided => Critical

** Changed in: xorg (Ubuntu Bionic)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Tags removed: rls-bb-incoming

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

Title:
  purge conf files on removal of upstart (was session fails to start
  after an upgrade from xenial to bionic)

Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader source package in Bionic:
  Triaged
Status in xorg source package in Bionic:
  Triaged

Bug description:
  After an upgrade from Xenial to Bionic the session fails to start and
  returns immediately to the login screen.

  There is this line in the journal
  [...] /usr/lib/gdm3/gdm-x-session[3584]: 
/etc/X11/Xsession.d/99x11-common_start: ligne 5: /sbin/upstart: Aucun fichier 
ou dossier de ce type

  (full journal from a failed attempt attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.26.1-0ubuntu9
  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
  Date: Tue Feb 13 15:11:12 2018
  InstallationDate: Installed on 2018-02-07 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-02-13 (0 days ago)

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

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

[Touch-packages] [Bug 1751076] Re: Xorg freeze when use mpv or cheese.

[Hans Joachim Desserud]

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

** This bug has been marked a duplicate of bug 1751075
   Xorg freeze when use mpv or cheese.

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

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  New

Bug description:
  I have my new laptop, Lenovo 720s-13ARR shipped with the latest Ryzen 5 
2500U, installed Ubuntu 17.10, it seems everything works except Wifi and GPU. 
After changing the wifi card with Intel 8265 and manually upgrading kernel with 
M-bab's build from 'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'. 
Wifi and Gpu are working. But if I use mpv playing a video, when I try to 
resume the window from fullscreen, the screen freezes. Same thing happens when 
I use cheese, the camera app. Nothing I can do except a hard poweroff. After 
suffering that couple of times, I started to look for solutions from Internet. 
There are many error messages I can see if I use 'dmesg -l err' in the 
terminal. I cannot solve most of them, only use pci=noaer in the grub to 
suppress the "PCIe bus error", which keep increasing my "/var/log/kern.log" 
file size hundreds MB per hour before.
  One more thing, if I start a reboot, the laptop might have a random hang on 
ubuntu logo screen. To avoid this, I have to poweroff first, then press power 
button to implement a 'reboot'. No idea for me in which part problem should be 
responsible for these failures.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature:
   
  Uname: Linux 4.15.4+ x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Thu Feb 22 21:53:01 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:380c]
  InstallationDate: Installed on 2018-01-30 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 81BR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6KCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0L77769 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
  dmi.product.family: ideapad 720S-13ARR
  dmi.product.name: 81BR
  dmi.product.version: Lenovo ideapad 720S-13ARR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  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/xorg/+bug/1751076/+subscriptions

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

[Touch-packages] [Bug 1749199] Re: purge conf files on removal of upstart (was session fails to start after an upgrade from xenial to bionic)

[Dimitri John Ledkov]

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

** Changed in: upstart (Ubuntu Bionic)
   Status: Triaged => Won't Fix

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

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

Title:
  purge conf files on removal of upstart (was session fails to start
  after an upgrade from xenial to bionic)

Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader source package in Bionic:
  Triaged
Status in xorg source package in Bionic:
  Triaged

Bug description:
  After an upgrade from Xenial to Bionic the session fails to start and
  returns immediately to the login screen.

  There is this line in the journal
  [...] /usr/lib/gdm3/gdm-x-session[3584]: 
/etc/X11/Xsession.d/99x11-common_start: ligne 5: /sbin/upstart: Aucun fichier 
ou dossier de ce type

  (full journal from a failed attempt attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.26.1-0ubuntu9
  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
  Date: Tue Feb 13 15:11:12 2018
  InstallationDate: Installed on 2018-02-07 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-02-13 (0 days ago)

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

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

[Touch-packages] [Bug 1749199] Re: purge conf files on removal of upstart (was session fails to start after an upgrade from xenial to bionic)

[Steve Langasek]

** Also affects: upstart (Ubuntu Bionic)
   Importance: Critical
   Status: Triaged

** Also affects: ubuntu-release-upgrader (Ubuntu Bionic)
   Importance: Critical
   Status: Triaged

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

Title:
  purge conf files on removal of upstart (was session fails to start
  after an upgrade from xenial to bionic)

Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader source package in Bionic:
  Triaged
Status in xorg source package in Bionic:
  Triaged

Bug description:
  After an upgrade from Xenial to Bionic the session fails to start and
  returns immediately to the login screen.

  There is this line in the journal
  [...] /usr/lib/gdm3/gdm-x-session[3584]: 
/etc/X11/Xsession.d/99x11-common_start: ligne 5: /sbin/upstart: Aucun fichier 
ou dossier de ce type

  (full journal from a failed attempt attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.26.1-0ubuntu9
  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
  Date: Tue Feb 13 15:11:12 2018
  InstallationDate: Installed on 2018-02-07 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-02-13 (0 days ago)

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

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

[Touch-packages] [Bug 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies

[Balint Reczey]

I'm testing the fix for u-u right now that will rely on apt's one. The
u-u fix will land soon in the git repository.

** Changed in: unattended-upgrades (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  linux-cloud-tools version specific packages are being removed by
  unattended-upgrade's  Remove-Unused-Dependencies

Status in apt package in Ubuntu:
  Triaged
Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  When running kernel version 4.4.0-78 (for example) and the unattended-
  upgrade packages installs a new kernel 4.4.0-79 (for example) the
  linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic
  packages are removed by the Remove-Unused-Dependencies rule, because
  unlike "normal" kernel packages they are not excluded by
  /etc/apt/apt.conf.d/01autoremove-kernels.

  The linux-cloud-tools package has the hyper-v integration services
  daemons in it, so it's deletion leaves some of the integration not
  working.

  Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other
  hyper-v users aren't caught out by this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 15 15:27:35 2017
  InstallationDate: Installed on 2016-04-25 (415 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
  modified.conffile..etc.update-motd.d.90-updates-available: [deleted]
  modified.conffile..etc.update-motd.d.98-fsck-at-reboot: [deleted]
  modified.conffile..etc.update-motd.d.98-reboot-required: [deleted]
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-04-25T16:28:36.64

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

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

[Touch-packages] [Bug 1747711] Re: file mis-identifies modern executables as application/x-sharedlib

[Steve Langasek]

** Tags removed: rls-bb-incoming
** Tags added: rls-bb-notfixing

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

Title:
  file mis-identifies modern executables as application/x-sharedlib

Status in file package in Ubuntu:
  New

Bug description:
  file doesn't recognize modern PIE (Position Independent Executable)
  x86 executables as such, reporting them as “application/x-sharedlib”.
  Consequently, only non-PIE executables can be opened in graphical file
  managers such as nautilus. This may cause a minor (?) security risk if
  a commonly-published workaround is attempted.

  Expected behaviour:

  $ echo "int main() { return 0; }" > foo.c
  $ gcc -o foo foo.c
  $ file foo
  foo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically 
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, 
BuildID[sha1]=6e7749f995a89a53f74ec29d3c16fcf3f56be90f, not stripped
  $ file --mime-type foo
  foo: application/x-executable

  Actual behaviour:

  $ echo "int main() { return 0; }" > foo.c
  $ gcc -o foo foo.c
  $ file foo
  foo: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically 
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, 
BuildID[sha1]=6e7749f995a89a53f74ec29d3c16fcf3f56be90f, not stripped
  $ file --mime-type foo
  foo: application/x-sharedlib

  Workaround (unsafe?):

  $ echo "int main() { return 0; }" > foo.c
  $ gcc -o foo-nopie foo.c -no-pie
  $ file foo-nopie
  foo-nopie: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 
3.2.0, BuildID[sha1]=3eb8c581f43c19997e3c828f5a9730dbdc794470, not stripped
  $ file --mime-type foo-nopie
  foo-nopie: application/x-executable

  gcc now defaults to building with PIE enabled for security reasons.

  Also affects: nautilus (and likely other graphical file managers like
  those on Lubuntu) - because nautilus uses mime-type to determine if a
  file is executable, double-click to run a program no longer works.

  Also noted on: Gnome Bugs -
  https://bugzilla.gnome.org/show_bug.cgi?id=737849 (2014) - before PIE
  became the default build option.

  This may be an upstream issue. This may not affect architectures
  outside x86.*

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: file 1:5.32-1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Feb  6 11:21:20 2018
  InstallationDate: Installed on 2017-05-11 (270 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: file
  UpgradeStatus: Upgraded to artful on 2017-10-21 (108 days ago)

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

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

[Touch-packages] [Bug 1749036] Re: package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has multiple installed in

[Adam Conrad]

e2fsprogs (1.43.9-1ubuntu1) bionic; urgency=medium

  * Make transitional library packages be Arch: any and Multi-Arch: same
so that upgrades actually function correctly when two or more exist.

 -- Adam Conrad   Mon, 19 Feb 2018 06:05:49 -0700


** Changed in: e2fsprogs (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all
  1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which
  has multiple installed instances

Status in e2fsprogs package in Ubuntu:
  Fix Released

Bug description:
  This happened during a partial upgrade of Bionic.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libcomerr2 1.43.8-2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Mon Feb 12 15:51:57 2018
  Dependencies:
   gcc-7-base 7.2.0-18ubuntu2
   libc6 2.26-0ubuntu2
   libgcc1 1:7.2.0-18ubuntu2
  DpkgTerminalLog:
   Preparing to unpack .../comerr-dev_2.1-1.43.9-1_amd64.deb ...
   Unpacking comerr-dev:amd64 (2.1-1.43.9-1) over (2.1-1.43.8-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libcomerr2_1.43.9-1_all.deb (--unpack):
libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with 
libcomerr2 which has multiple installed instances
  DuplicateSignature:
   package:libcomerr2:1.43.8-2
   Unpacking comerr-dev:amd64 (2.1-1.43.9-1) over (2.1-1.43.8-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libcomerr2_1.43.9-1_all.deb (--unpack):
libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with 
libcomerr2 which has multiple installed instances
  ErrorMessage: libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable 
with libcomerr2 which has multiple installed instances
  InstallationDate: Installed on 2013-01-16 (1853 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  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.6~alpha7ubuntu1
  SourcePackage: e2fsprogs
  Title: package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all 
1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has 
multiple installed instances
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1750851] Re: re-add cloud-initramfs-dyn-netconf to ubuntu-server

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-meta - 1.411

---
ubuntu-meta (1.411) bionic; urgency=medium

  * Refreshed dependencies
  * Added cloud-initramfs-dyn-netconf to server (LP: #1750851)
  * Added printer-driver-m2300w to desktop-recommends
  * Removed gnome-calculator from desktop-recommends
  * Removed ttf-ancient-fonts-symbola from desktop-recommends

 -- Scott Moser   Thu, 22 Feb 2018 09:53:43 -0500

** Changed in: ubuntu-meta (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  re-add cloud-initramfs-dyn-netconf to ubuntu-server

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  I (smoser) removed cloud-initramfs-dyn-netconf from ubuntu-server meta
  package.  That package provides functionality needed by MAAS and cause bug
  1748875.  Under that bug we re-added cloud-initramfs-dyn-netconf to the
  initramfs that MAAS publishes.

  We subsequently saw failure in open-iscsi tests, which utilize that same
  function.

  My commit message to the fix of maas-images is below for informational
  purposes [1]:
[1] 
https://code.launchpad.net/~smoser/maas-images/trunk.lp1749019-re-add-cloud-intramfs-dyn-netconf/+merge/337605

  'b' is *also* used by the open-iscsi use case.  It boots with a slightly
  different form than maas images:
BOOTIF_DEFAULT=eth0 and ip=:name:BOOTIF

  Here, 'BOOTIF' will be replaced with 'eth0'.

  | Re-add cloud-initramfs-dyn-netconf. Needed by maas for BOOTIF in ip=.
  |
  | The previous commit to trunk dropped cloud-initramfs-dyn-netconf from
  | the maas image in releases newer than xenial.
  | 
  | That caused errors in MAAS. cloud-initramfs-dyn-netconf does 2 things:
  | a.) writes /run/network/dynamic-interfaces
  | this is a ENI style file with data retrived from ipconfig
  | b.) convert 'BOOTIF' string in the value of IP
  |   Example:
  | ip=foobar:BOOTIF BOOTIF=01-00-22-68-10-c1-e6
  |   will be effectively rendered as:
  | ip=foobar:eth0
  |
  | 'b' is still required by maas.
  |
  | Note: in maas v3 images, the squashfs image is re-used pristine
  | from cloud-images. Because of this, the installation into the image
  | affects initramfs creation, but does not affect the image. That is
  | correct in that this package is not needed in the image but only
  | in the initramfs.

  Related bugs:
   * bug 1748875:  Unable to deploy Bionic on bare-metals with MaaS 2.3.0

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

-- 
Mailing list: https://launchpad.net/~touch-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: 14.04 Kernel update on 2/21 breaks Nvidia drivers

[Bernhard]

It affects me too:

Nvidia NVS 300 and GT 430 . Nvidia 340.x and 384.111

-- 
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:
  14.04 Kernel update on 2/21 breaks Nvidia drivers

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.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+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 1750379] Re: Distortion Realtek ALC887

[fleamour]

Can confirm kernel makes no difference.

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

Title:
  Distortion Realtek ALC887

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

Bug description:
  Sounds can distort even when not amplified. Amplification worked well
  for years before recent PulseAudio update. The audio is Realtek ALC887
  under an IntelG41 Chipset with GA-G41M-Combo main board;

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

  I am seeking to engage upstream for April LTS release. Windows have
  abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user
  going!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fleamour   1049 F pulseaudio
   /dev/snd/controlC2:  fleamour   1049 F pulseaudio
   /dev/snd/controlC0:  fleamour   1049 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 19 13:54:33 2018
  InstallationDate: Installed on 2018-02-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  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.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1750586] Re: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Stephen Pape]

The post installation file /var/lib/dpkg/info/python-minimal.postinst
runs the following command:

python2.7 -m compileall /usr/share/python/ >/dev/null

Running the command manually (without the /dev/null redirect) produces
the following error for me:

Compiling 
/usr/share/python/rekall-forensic/lib/python2.7/site-packages/pexpect/async.py 
...
  File 
"/usr/share/python/rekall-forensic/lib/python2.7/site-packages/pexpect/async.py",
 line 16
transport, pw = yield from asyncio.get_event_loop()\
 ^
SyntaxError: invalid syntax

I removed the /usr/share/python/rekall-forensic folder and was able to
"apt install -f". Likely a different package is causing you trouble, but
try running that command for more information.

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

Title:
  package python-minimal 2.7.12-1~16.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in python-defaults package in Ubuntu:
  Confirmed

Bug description:
  There seems to be a dependency snarl:

  python-minimal is already the newest version (2.7.12-1~16.04).
  python-minimal set to manually installed.
  You might want to run 'apt-get -f install' to correct these:
  The following packages have unmet dependencies:
   python : PreDepends: python-minimal (= 2.7.11-1) but 2.7.12-1~16.04 is to be 
installed
   python-all : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
   python-all-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
Depends: libpython-all-dev (= 2.7.12-1~16.04) but 2.7.11-1 
is to be installed
   python-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
Depends: libpython-dev (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
  E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify 
a solution).

  apt-get -f install tries to set up python-minimal (2.7.12-1~16.04) and
  returns 1.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-minimal 2.7.12-1~16.04
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Feb 20 08:48:01 2018
  DuplicateSignature:
   package:python-minimal:2.7.12-1~16.04
   Setting up python-minimal (2.7.12-1~16.04) ...
   dpkg: error processing package python-minimal (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-23 (484 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: python-defaults
  Title: package python-minimal 2.7.12-1~16.04 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-defaults/+bug/1750586/+subscriptions

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

[Touch-packages] [Bug 1734586] Re: Merge NetworkManager with Debian 1.10.0-1

[Sebastien Bacher]

** Also affects: python-dbusmock (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: python-dbusmock (Ubuntu)
   Importance: Undecided => High

** Changed in: python-dbusmock (Ubuntu)
   Status: New => In Progress

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

Title:
  Merge NetworkManager with Debian 1.10.0-1

Status in network-manager package in Ubuntu:
  Fix Committed
Status in python-dbusmock package in Ubuntu:
  In Progress

Bug description:
  Debian has packaged the latest major release of NetworkManager, 1.10.
  We should update to this version for Ubuntu 18.04 "bionic".

  I have prepared the merge at
  https://git.launchpad.net/network-manager?h=bionic

  The only thing missing is that this patch needs to be rebased or dropped:
  
https://git.launchpad.net/network-manager/tree/debian/patches/dns-manager-don-t-merge-split-DNS-search-domains.patch?h=bionic

  Otherwise, the build will fail:

  src/.libs/libNetworkManagerTest.a(src_libNetworkManager_la-nm-dns-manager.o):
  In function `merge_one_ip_config_data':
  ./src/dns/nm-dns-manager.c:417: undefined reference to
  `nm_ip4_config_get_never_default'
  ./src/dns/nm-dns-manager.c:419: undefined reference to
  `nm_ip4_config_get_never_default'

  There's been a lot of refactoring, but this commit looks important:
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=5c29945

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

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

[Touch-packages] [Bug 1751075] [NEW] Xorg freeze when use mpv or cheese.

[Ven]

Public bug reported:

I have my new laptop, Lenovo 720s-13ARR shipped with the latest Ryzen 5 2500U, 
installed Ubuntu 17.10, it seems everything works except Wifi and GPU. After 
changing the wifi card with Intel 8265 and manually upgrading kernel with 
M-bab's build from 'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'. 
Wifi and Gpu are working. But if I use mpv playing a video, when I try to 
resume the window from fullscreen, the screen freezes. Same thing happens when 
I use cheese, the camera app. Nothing I can do except a hard poweroff. After 
suffering that couple of times, I started to look for solutions from Internet. 
There are many error messages I can see if I use 'dmesg -l err' in the 
terminal. I cannot solve most of them, only use pci=noaer in the grub to 
suppress the "PCIe bus error", which keep increasing my "/var/log/kern.log" 
file size hundreds MB per hour before.
One more thing, if I start a reboot, the laptop might have a random hang on 
ubuntu logo screen. To avoid this, I have to poweroff first, then press power 
button to implement a 'reboot'. No idea for me in which part problem should be 
responsible for these failures.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature:
 
Uname: Linux 4.15.4+ x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Thu Feb 22 21:53:01 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: I don't know
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo Device [17aa:380c]
InstallationDate: Installed on 2018-01-30 (22 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: LENOVO 81BR
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/19/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 6KCN28WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0L77769 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 720S-13ARR
dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
dmi.product.family: ideapad 720S-13ARR
dmi.product.name: 81BR
dmi.product.version: Lenovo ideapad 720S-13ARR
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.85-4~a~padoka0
version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
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 freeze third-party-packages 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/1751075

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  New

Bug description:
  I have my new laptop, Lenovo 720s-13ARR shipped with the latest Ryzen 5 
2500U, installed Ubuntu 17.10, it seems everything works except Wifi and GPU. 
After changing the wifi card with Intel 8265 and manually upgrading kernel with 
M-bab's build from 'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'. 
Wifi and Gpu are working. But if I use mpv playing a video, when I try to 
resume the window from fullscreen, the screen freezes. Same thing happens when 
I use cheese, the camera app. Nothing I can do except a hard poweroff. After 
suffering that couple of times, I started to look for solutions from Internet. 
There are many error messages I can see if I use 'dmesg -l err' in the 
terminal. I cannot solve most of them, only use pci=noaer in the grub to 
suppress the "PCIe bus error", which keep increasing my "/var/log/kern.log" 
file size hundreds MB per hour before.
  One more thing, if I start a reboot, the laptop might have a random hang on 
ubuntu logo screen. To avoid this, I have to poweroff first, then press power 
button to implement a 'reboot'. No idea for me in which part problem should be 
responsible for 

[Touch-packages] [Bug 1751076] [NEW] Xorg freeze when use mpv or cheese.

[Ven]

Public bug reported:

I have my new laptop, Lenovo 720s-13ARR shipped with the latest Ryzen 5 2500U, 
installed Ubuntu 17.10, it seems everything works except Wifi and GPU. After 
changing the wifi card with Intel 8265 and manually upgrading kernel with 
M-bab's build from 'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'. 
Wifi and Gpu are working. But if I use mpv playing a video, when I try to 
resume the window from fullscreen, the screen freezes. Same thing happens when 
I use cheese, the camera app. Nothing I can do except a hard poweroff. After 
suffering that couple of times, I started to look for solutions from Internet. 
There are many error messages I can see if I use 'dmesg -l err' in the 
terminal. I cannot solve most of them, only use pci=noaer in the grub to 
suppress the "PCIe bus error", which keep increasing my "/var/log/kern.log" 
file size hundreds MB per hour before.
One more thing, if I start a reboot, the laptop might have a random hang on 
ubuntu logo screen. To avoid this, I have to poweroff first, then press power 
button to implement a 'reboot'. No idea for me in which part problem should be 
responsible for these failures.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature:
 
Uname: Linux 4.15.4+ x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Thu Feb 22 21:53:01 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: I don't know
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo Device [17aa:380c]
InstallationDate: Installed on 2018-01-30 (22 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: LENOVO 81BR
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.4+ 
root=UUID=399cfaf6-9c73-4786-8ef5-bd331d20aadc ro pci=noaer 
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.1 quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/19/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 6KCN28WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0L77769 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 720S-13ARR
dmi.modalias: 
dmi:bvnLENOVO:bvr6KCN28WW:bd12/19/2017:svnLENOVO:pn81BR:pvrLenovoideapad720S-13ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13ARR:
dmi.product.family: ideapad 720S-13ARR
dmi.product.name: 81BR
dmi.product.version: Lenovo ideapad 720S-13ARR
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.85-4~a~padoka0
version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
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 freeze third-party-packages 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/1751076

Title:
  Xorg freeze when use mpv or cheese.

Status in xorg package in Ubuntu:
  New

Bug description:
  I have my new laptop, Lenovo 720s-13ARR shipped with the latest Ryzen 5 
2500U, installed Ubuntu 17.10, it seems everything works except Wifi and GPU. 
After changing the wifi card with Intel 8265 and manually upgrading kernel with 
M-bab's build from 'https://github.com/M-Bab/linux-kernel-amdgpu-binaries'. 
Wifi and Gpu are working. But if I use mpv playing a video, when I try to 
resume the window from fullscreen, the screen freezes. Same thing happens when 
I use cheese, the camera app. Nothing I can do except a hard poweroff. After 
suffering that couple of times, I started to look for solutions from Internet. 
There are many error messages I can see if I use 'dmesg -l err' in the 
terminal. I cannot solve most of them, only use pci=noaer in the grub to 
suppress the "PCIe bus error", which keep increasing my "/var/log/kern.log" 
file size hundreds MB per hour before.
  One more thing, if I start a reboot, the laptop might have a random hang on 
ubuntu logo screen. To avoid this, I have to poweroff first, then press power 
button to implement a 'reboot'. No idea for me in which part problem should be 
responsible for 

[Touch-packages] [Bug 1751068] Re: My Intel HD driver became VMvare driver after today`s update

[Виктор Бутко]

I repeated this bug by installing the system from scratch and updating
all the proposed packages

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

Title:
  My Intel HD driver became VMvare driver after today`s update

Status in libglu package in Ubuntu:
  New

Bug description:
  tamer@tamer-desktop:~$ lspci | grep -E "VGA|3D"
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)

  tamer@tamer-desktop:~$ glxinfo -B 
  name of display: :0
  display: :0  screen: 0
  direct rendering: Yes
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: VMware, Inc. (0x)
  Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
  Version: 17.3.3
  Accelerated: no
  Video memory: 7390MB
  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
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile

  OpenGL version string: 3.0 Mesa 17.3.3
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)

  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 17.3.3
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libglu1-mesa 9.0.0-2.1build1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb 22 15:53:29 2018
  InstallationDate: Installed on 2018-02-22 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180206)
  SourcePackage: libglu
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Timo Aaltonen]

sounds like artful is verified, same for xenial would be great

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

-- 
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 Committed
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 Committed
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 1200296] Re: [MIR] spice-vdagent

[Andy Whitcroft]

Override component to main
spice-vdagent 0.17.0-1ubuntu2 in bionic: universe/x11 -> main
spice-vdagent 0.17.0-1ubuntu2 in bionic amd64: universe/x11/optional/100% -> 
main
spice-vdagent 0.17.0-1ubuntu2 in bionic arm64: universe/x11/optional/100% -> 
main
spice-vdagent 0.17.0-1ubuntu2 in bionic armhf: universe/x11/optional/100% -> 
main
spice-vdagent 0.17.0-1ubuntu2 in bionic i386: universe/x11/optional/100% -> main
spice-vdagent 0.17.0-1ubuntu2 in bionic ppc64el: universe/x11/optional/100% -> 
main
spice-vdagent 0.17.0-1ubuntu2 in bionic s390x: universe/x11/optional/100% -> 
main
7 publications overridden.


** Changed in: spice-vdagent (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] spice-vdagent

Status in spice-vdagent package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Committed

Bug description:
  Availability
  
  Built for all supported architectures.

  In sync with Debian except for one cherry-picked patch to hide spice-
  vdagent from Startup Applications.

  Rationale
  =
  "spice-vdagent adds some nice features to guest systems running over SPICE: 
copy and paste between guest and host, arbitrary resolution support, ... It's 
also very tiny (40kB compressed, less than 200kB installed) and won't startup 
when not running in a SPICE guest.
  Shipping it on the desktop ISOs will improve the user experience when using 
SPICE (eg in GNOME Boxes), and will have no impact on other use cases, so it 
would be really nice to add this package to the ISO."

  Ubuntu GNOME 16.10 and 17.04 included it in the default install.

  Security
  
  No known open security vulnerabilities.

  https://rhn.redhat.com/errata/RHSA-2013-0924.html (CVE-2013-2152)

  Quality assurance
  =
  Bug subscriber: Ubuntu Desktop Bugs

  https://bugs.launchpad.net/ubuntu/+source/spice-vdagent
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=spice-vdagent
  https://bugs.freedesktop.org/buglist.cgi?bug_status=__open__=unix 
agent=Spice

  No tests.

  Dependencies
  
  check-mir reports all other binary dependencies are in main

  Standards compliance
  
  3.9.8

  Maintenance
  ===
  - Actively developed upstream
  https://cgit.freedesktop.org/spice/linux/vd_agent/log/
  https://anonscm.debian.org/git/collab-maint/spice-vdagent.git

  - Maintained in Debian by the same Debian Developer who maintains the
  other Spice packages.

  short dh7 style rules, dh compat 10

  Background information
  ==
  N/A

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Johan Marius Wesselink]

Tested the scilab 5.5.2 for ubuntu which works great. 
However, I did not test it before applying the jogl2 patch :-o.  

Had a look at the source and it seems that the Ubuntu version is patched to use 
the
generic version of jogl2. 

I would like to try and get this patch integrated in the Scilab source tree. 
Probably a difficult and slow process.

-- 
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 Committed
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 Committed
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 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Andres Rodriguez]

@Scott,

Sure, we can all improve but I just want to note one thing. The "Silly"
config that MAAS sends to curtin is valid config. That yields valid
configuration in Xenial. Since Curtin is now passing the /same/
configuration to cloud-init, cloud-init is not generating valid
configuration in Bionic. Despite the fact that theres a "global" DNS,
there's also DNS defined for the bridge, but cloud-init is not writing
the bridge config correctly.

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Invalid
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 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 maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution

  [...]

  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms

  =
  Xenial
  ==

  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  dns-nameservers 10.90.90.1
  dns-search maaslab maas

  auto enp0s25
  iface enp0s25 inet static
  address 10.90.90.162/24
  gateway 10.90.90.1
  mtu 1500
  ubuntu@node05:~$ 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
  nameserver 10.90.90.1
  search maaslab maas

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions

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

[Touch-packages] [Bug 1751068] [NEW] My Intel HD driver became VMvare driver after today`s update

[Виктор Бутко]

Public bug reported:

tamer@tamer-desktop:~$ lspci | grep -E "VGA|3D"
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)

tamer@tamer-desktop:~$ glxinfo -B 
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: VMware, Inc. (0x)
Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
Version: 17.3.3
Accelerated: no
Video memory: 7390MB
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
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.0 Mesa 17.3.3
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.0 Mesa 17.3.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libglu1-mesa 9.0.0-2.1build1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Feb 22 15:53:29 2018
InstallationDate: Installed on 2018-02-22 (0 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180206)
SourcePackage: libglu
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  My Intel HD driver became VMvare driver after today`s update

Status in libglu package in Ubuntu:
  New

Bug description:
  tamer@tamer-desktop:~$ lspci | grep -E "VGA|3D"
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)

  tamer@tamer-desktop:~$ glxinfo -B 
  name of display: :0
  display: :0  screen: 0
  direct rendering: Yes
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: VMware, Inc. (0x)
  Device: llvmpipe (LLVM 5.0, 256 bits) (0x)
  Version: 17.3.3
  Accelerated: no
  Video memory: 7390MB
  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
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile

  OpenGL version string: 3.0 Mesa 17.3.3
  OpenGL shading language version string: 1.30
  OpenGL context flags: (none)

  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 17.3.3
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libglu1-mesa 9.0.0-2.1build1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb 22 15:53:29 2018
  InstallationDate: Installed on 2018-02-22 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180206)
  SourcePackage: libglu
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

[Dimitri John Ledkov]

john-center - I believe mdadm is used by default, instead of dmraid.
However, I'm not sure if we do correctly activate Intel Raids with
mdadm. I have not done an install with either 16.04 or 18.04. Or I guess
at least start the install up to the partitioning screen. My expectation
is, if one has raid arrays pre-setup in BIOS (ctrl+I on boot) already,
they should show up as assembled and offered to be autopartitioned. With
both 16.04 and 18.04.

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to