[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/345498

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1771340] Re: sshd failed on config reload

[Tronde]

This bug seems to be fixed upstream in a newer version: [Debian Bug report logs 
- #865770
openssh-server fails to validate configuration before reloading, under 
systemd](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865770)

Maybe it is possible to get a version update in Xenial?!

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

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

Title:
  sshd failed on config reload

Status in openssh package in Ubuntu:
  New

Bug description:
  After adding some lines to /etc/ssh/sshd_config I tried to reload the
  configuration with the command:

  ```
  sudo systemctl reload sshd
  ```

  No error message was returned. So I assumed that the sshd was running
  with the current config. But `sudo systemctl status sshd` told me that
  the service failed due to a wrong option in /etc/ssh/sshd_config.
  Please see the following output:

  ~~~
  :~$ sudo vim /etc/ssh/sshd_config
  :~$ sudo systemctl reload sshd
  :~$ sudo systemctl status sshd
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Di 2018-05-15 10:00:04 CEST; 8s 
ago
Process: 12089 ExecReload=/bin/kill -HUP $MAINPID (code=exited, 
status=0/SUCCESS)
Process: 7536 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 7536 (code=exited, status=255)
  ~~~

  I would expect that a warning or error message is returned when the
  service fails while reloading it's configuration.

  A fix for this behaviour would be appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.4
  ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  Date: Tue May 15 10:18:25 2018
  InstallationDate: Installed on 2013-01-10 (1950 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to xenial on 2017-03-12 (428 days ago)
  mtime.conffile..etc.pam.d.sshd: 2017-03-13T19:59:01.965420

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

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

[Touch-packages] [Bug 1771329] Re: Can't open apps due to Too many open files

[Joe Littlejohn]

I think there's a strong argument that the default max open files for
Ubuntu Desktop should be higher than it is now. Modern apps use a lot of
file handles.

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

Title:
  Can't open apps due to Too many open files

Status in dbus package in Ubuntu:
  New

Bug description:
  Occasionally I find that I can't launch a new terminal, or can't
  achieve some other desktop task. Checking journalctl I see error
  messages like this:

  May 15 12:12:15 jl-XPS-13-9360 terminator.desktop[11840]:
  dbus.exceptions.DBusException:
  org.freedesktop.DBus.Error.LimitsExceeded: Failed to determine seats
  of user "1000": Too many open files

  
  or this:

  May 15 12:12:47 jl-XPS-13-9360 google-chrome.desktop[28308]:
  [28308:28343:0515/121247.966786:ERROR:bus.cc(394)] Failed to connect
  to the bus: Failed to determine seats of user "1000": Too many open
  files

  
  At the time this happen's I'm usually running Slack, Chrome, Emacs, and a few 
Java apps.

  I'm using Ubuntu Bionic (18.04), 4.15.0-20-generic x86_64, vanilla
  gnome-shell.

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

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

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

[Mario Costa]

Public bug reported:

When I try to use ubuntu with dual desktop display it crashes
continuously, and entering into login mode.

I cannot use dual display.
To use an external monitor, I have to start the laptop with the computer closed.

It seems to be related to the graphic card, maybe dual graphic card of
the laptop.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
Uname: Linux 4.4.0-124-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME-Classic:GNOME
Date: Wed May 16 10:36:05 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
 Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990]
InstallationDate: Installed on 2017-12-13 (153 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Hewlett-Packard HP EliteBook 840 G1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=e1833df7-4a4b-41b2-8393-d88536dd0165 ro quiet splash radeon.runpm=0 
vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2016
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L71 Ver. 01.39
dmi.board.name: 198F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 15.59
dmi.chassis.asset.tag: 5CG44010XD
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.39:bd09/26/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 840 G1
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.3+16.04.20180221-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 Mar  8 12:39:32 2018
xserver.configfile: default
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 crash 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/1771539

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  When I try to use ubuntu with dual desktop display it crashes
  continuously, and entering into login mode.

  I cannot use dual display.
  To use an external monitor, I have to start the laptop with the computer 
closed.

  It seems to be related to the graphic card, maybe dual graphic card of
  the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed May 16 10:36:05 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990]
  InstallationDate: Installed on 2017-12-13 (153 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  ProcKernelCmdLine: 

[Touch-packages] [Bug 1771329] Re: Can't open apps due to Too many open files

[Joe Littlejohn]

I tried the following:

echo '* hard nofile 65535' | sudo tee -a /etc/security/limits.conf
echo '* soft nofile 65535' | sudo tee -a /etc/security/limits.conf
echo 'session required pam_limits.so' | sudo tee -a /etc/pam.d/common-session

then restarted.

This did not fix the issue. So that's one 'increase limits' strategy we
can rule out - it doesn't work for this particular problem.

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

Title:
  Can't open apps due to Too many open files

Status in dbus package in Ubuntu:
  New

Bug description:
  Occasionally I find that I can't launch a new terminal, or can't
  achieve some other desktop task. Checking journalctl I see error
  messages like this:

  May 15 12:12:15 jl-XPS-13-9360 terminator.desktop[11840]:
  dbus.exceptions.DBusException:
  org.freedesktop.DBus.Error.LimitsExceeded: Failed to determine seats
  of user "1000": Too many open files

  
  or this:

  May 15 12:12:47 jl-XPS-13-9360 google-chrome.desktop[28308]:
  [28308:28343:0515/121247.966786:ERROR:bus.cc(394)] Failed to connect
  to the bus: Failed to determine seats of user "1000": Too many open
  files

  
  At the time this happen's I'm usually running Slack, Chrome, Emacs, and a few 
Java apps.

  I'm using Ubuntu Bionic (18.04), 4.15.0-20-generic x86_64, vanilla
  gnome-shell.

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

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

[Touch-packages] [Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Juan Manuel SA]

I had the same problem with Debian. 
The workaround I used is creating a link from the key to the keyring

keyctl link @u @s

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

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

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

[Touch-packages] [Bug 1771540] [NEW] i am not able to install the updates

[pawan naresh chandiramani]

Public bug reported:

 i am not able to install the updates

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed May 16 15:19:58 2018
DistUpgraded: 2017-09-01 00:53:53,943 WARNING no activity on terminal for 300 
seconds (Installed python3-renderpm (amd64))
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
InstallationDate: Installed on 2017-08-01 (287 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
MachineType: Dell Inc. Inspiron 5559
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=1cde99c2-2259-44dd-a873-b302c0633c92 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-08-31 (257 days ago)
dmi.bios.date: 09/16/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.6
dmi.board.name: 04D1V1
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.6:bd09/16/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn04D1V1:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5559
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed May 16 13:57:14 2018
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1557 
 vendor BOE
xserver.version: 2:1.18.4-0ubuntu0.7

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


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

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

Title:
  i am not able to install the updates

Status in xorg package in Ubuntu:
  New

Bug description:
   i am not able to install the updates

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed May 16 15:19:58 2018
  DistUpgraded: 2017-09-01 00:53:53,943 WARNING no activity on terminal for 300 
seconds (Installed python3-renderpm (amd64))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2017-08-01 (287 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 5559
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=1cde99c2-2259-44dd-a873-b302c0633c92 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-08-31 (257 days ago)
  dmi.bios.date: 09/16/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.6
  dmi.board.name: 04D1V1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[ Christian Ehrhardt ]

** Merge proposal unlinked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/345498

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1771329] Re: Can't open apps due to Too many open files

[Joe Littlejohn]

Thanks @dino99. I've seen a lot of different suggestions for tackling
this error, so it would be good to understand exactly which config
change is the critical one.

I think this is a major bug on a newly installed system. As an Ubuntu
Desktop user I shouldn't be experiencing an issue where the OS stops me
from launching any new app once I have a few apps open. I shouldn't need
to go hunting through logs to and start googling for a solution, then
modify open file limits, just to run a handful of desktop applications.

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

Title:
  Can't open apps due to Too many open files

Status in dbus package in Ubuntu:
  New

Bug description:
  Occasionally I find that I can't launch a new terminal, or can't
  achieve some other desktop task. Checking journalctl I see error
  messages like this:

  May 15 12:12:15 jl-XPS-13-9360 terminator.desktop[11840]:
  dbus.exceptions.DBusException:
  org.freedesktop.DBus.Error.LimitsExceeded: Failed to determine seats
  of user "1000": Too many open files

  
  or this:

  May 15 12:12:47 jl-XPS-13-9360 google-chrome.desktop[28308]:
  [28308:28343:0515/121247.966786:ERROR:bus.cc(394)] Failed to connect
  to the bus: Failed to determine seats of user "1000": Too many open
  files

  
  At the time this happen's I'm usually running Slack, Chrome, Emacs, and a few 
Java apps.

  I'm using Ubuntu Bionic (18.04), 4.15.0-20-generic x86_64, vanilla
  gnome-shell.

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

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

[Touch-packages] [Bug 1769891] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: ordinal not in range(128)

[Herbert Eisenbeis]

Same error message here.
Reason: Target filesystem had been mounted r/o.

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

Title:
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position
  37: ordinal not in range(128)

Status in Déjà Dup:
  New
Status in python2.7 package in Ubuntu:
  New

Bug description:
  Hello

  duplicity crash after backup because there is a python error

  Step to reproduce.

  1. Active developper option in software center
  2. install the backup python pyckage
  3. Lanch a backup with duplicity command

  Result :

  
   Type of backup set:Time:   Number of volumes:
  Full Tue Feb 20 22:00:34 2018  2284
   Incremental Thu Feb 22 03:26:48 2018 1
   Incremental Fri Feb 23 23:23:09 201842
   Incremental Wed Apr  4 15:54:05 2018   151
   Incremental Thu Apr  5 04:27:55 2018 1
   Incremental Sat Apr 14 21:51:41 2018 1
  -
  Also found 0 backup sets not part of any chain,
  and 1 incomplete backup set.
  These may be deleted by running duplicity with the "cleanup" command.
  Registering (mktemp) temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
  Deleting /tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
  Forgetting temporary file /tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
  Processing remote manifest 
duplicity-inc.20180405T022755Z.to.20180414T195141Z.manifest (154)
  Found manifest volume 1
  Found 1 volumes in manifest
  Registering (mktemp) temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 556, in 
get
  "from backend") % util.ufn(local_path.name))
   BackendException: File /tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3 not 
found locally after get from backend

  Attempt 1 failed. BackendException: File 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3 not found locally after get from 
backend
  Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
  return fn(self, *args)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 552, in 
get
  self.backend._get(remote_filename, local_path)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", 
line 151, in _get
  self.__copy_file(source_file, target_file)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", 
line 124, in __copy_file
  None, self.__copy_progress, None)
   Error: g-io-error-quark: Error opening file 
“/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3”: No such file or directory 
(1)

  Releasing lockfile 
/home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
  Removing still remembered temporary file 
/tmp/duplicity-hFkoYG-tempdir/mkstemp-useaK1-1
  Removing still remembered temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3
  Cleanup of temporary directory /tmp/duplicity-hFkoYG-tempdir failed - this is 
probably a bug.
  Releasing lockfile 
/home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 658, in incremental_backup
  sig_chain.get_fileobjs())
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 539, 
in get_fileobjs
  return [filename_to_fileobj(f) for f in self.get_filenames(time)]
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 676, in 
get_fileobj_read
  self.get(filename, tdp)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 392, in 
inner_retry
  util.uexc(e)), code=code, extra=extra)
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  Releasing lockfile /home/username/.cache/deja-
  dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile

  Note : this bug affect eclim and other python pyckages

  http://eclim.org

  
  Could you help me please to fix this issus

  Best regards

  Battant

  ProblemType: Bug
  

[Touch-packages] [Bug 1771329] Re: Can't open apps due to Too many open files

[dino99]

Maybe some days Dbus will grab some builtin IA to increase/decrease ulimit on 
the fly !!!
But yes special user's case also need custom user settings. Not a real bug per 
se, but more of a wish 

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

Title:
  Can't open apps due to Too many open files

Status in dbus package in Ubuntu:
  New

Bug description:
  Occasionally I find that I can't launch a new terminal, or can't
  achieve some other desktop task. Checking journalctl I see error
  messages like this:

  May 15 12:12:15 jl-XPS-13-9360 terminator.desktop[11840]:
  dbus.exceptions.DBusException:
  org.freedesktop.DBus.Error.LimitsExceeded: Failed to determine seats
  of user "1000": Too many open files

  
  or this:

  May 15 12:12:47 jl-XPS-13-9360 google-chrome.desktop[28308]:
  [28308:28343:0515/121247.966786:ERROR:bus.cc(394)] Failed to connect
  to the bus: Failed to determine seats of user "1000": Too many open
  files

  
  At the time this happen's I'm usually running Slack, Chrome, Emacs, and a few 
Java apps.

  I'm using Ubuntu Bionic (18.04), 4.15.0-20-generic x86_64, vanilla
  gnome-shell.

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

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

[Touch-packages] [Bug 1658273] Re: Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.

[Sunoro]

** Changed in: samba (Ubuntu)
 Assignee: (unassigned) => Sunoro (bibie)

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Sunoro (bibie)

** Changed in: samba (Ubuntu)
 Assignee: Sunoro (bibie) => (unassigned)

** Changed in: samba (Ubuntu)
 Assignee: (unassigned) => Sunoro (bibie)

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

Title:
  Failed to preset unit: Unit file /etc/systemd/system/samba-ad-
  dc.service is masked.

Status in samba package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  On a standalone desktop running zesty with a gnome-shell session, when
  upgrading the samba packages, i get:

  Setting up samba (2:4.4.5+dfsg-2ubuntu7) ...
  Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is 
masked.
  /usr/bin/deb-systemd-helper: error: systemctl preset failed on 
samba-ad-dc.service: No such file or directory

  note: ubuntu-bug ask questions about a possible windows relationship,
  but there is no option for a standalone system like that one; so as
  samba is installed to satisfy qemu, these questions completly ignore
  such case and send inappropriate report.

   and smbd still crashing on cold boot ( lp:1658293 ) (standalone
  desktop)

  note2: a more recent Debian version seems workaround that output:
  samba (2:4.4.5+dfsg-3)
  [ Mathieu Parent ]
* Remove /etc/systemd/system/samba-ad-dc.service (from postinst) on purge.
  Closes: #832352
  and samba (2:4.4.6+dfsg-1)
  Only fix PIDFile in {nmbd,samba-ad-dc,smbd,winbind}.service (i.e. not
  ctdb.service) Closes: #838000.
  and samba (2:4.4.6+dfsg-2) 
* Remove uses of tevent internals. This fixes segfault.
  Closes: #840382, #840298.
  
http://metadata.ftp-master.debian.org/changelogs/main/s/samba/samba_4.5.2+dfsg-2_changelog

  ... time to get package synced

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

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

[Touch-packages] [Bug 1771513] [NEW] package ibus-gtk:amd64 1.5.11-1ubuntu2 failed to install/upgrade: package ibus-gtk:amd64 is not ready for configuration cannot configure (current status 'half-inst

[David Melessa Asfaou]

Public bug reported:

Hello

Notification relating ibus appears when I open my notebook.
I don't know what is about this but everything is working nice

Version :ubuntu 16.04 LTS

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ibus-gtk:amd64 1.5.11-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Mon May 14 18:03:21 2018
DuplicateSignature:
 package:ibus-gtk:amd64:1.5.11-1ubuntu2
 Processing triggers for doc-base (0.10.7) ...
 Processing 2 added doc-base files...
 dpkg: error processing package ibus-gtk:amd64 (--configure):
  package ibus-gtk:amd64 is not ready for configuration
ErrorMessage: package ibus-gtk:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2018-04-03 (42 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: ibus
Title: package ibus-gtk:amd64 1.5.11-1ubuntu2 failed to install/upgrade: 
package ibus-gtk:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package ibus-gtk:amd64 1.5.11-1ubuntu2 failed to install/upgrade:
  package ibus-gtk:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in ibus package in Ubuntu:
  New

Bug description:
  Hello

  Notification relating ibus appears when I open my notebook.
  I don't know what is about this but everything is working nice

  Version :ubuntu 16.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ibus-gtk:amd64 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Mon May 14 18:03:21 2018
  DuplicateSignature:
   package:ibus-gtk:amd64:1.5.11-1ubuntu2
   Processing triggers for doc-base (0.10.7) ...
   Processing 2 added doc-base files...
   dpkg: error processing package ibus-gtk:amd64 (--configure):
package ibus-gtk:amd64 is not ready for configuration
  ErrorMessage: package ibus-gtk:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-04-03 (42 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: ibus
  Title: package ibus-gtk:amd64 1.5.11-1ubuntu2 failed to install/upgrade: 
package ibus-gtk:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1771513] Re: package ibus-gtk:amd64 1.5.11-1ubuntu2 failed to install/upgrade: package ibus-gtk:amd64 is not ready for configuration cannot configure (current status 'half-instal

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

Title:
  package ibus-gtk:amd64 1.5.11-1ubuntu2 failed to install/upgrade:
  package ibus-gtk:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in ibus package in Ubuntu:
  New

Bug description:
  Hello

  Notification relating ibus appears when I open my notebook.
  I don't know what is about this but everything is working nice

  Version :ubuntu 16.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ibus-gtk:amd64 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Mon May 14 18:03:21 2018
  DuplicateSignature:
   package:ibus-gtk:amd64:1.5.11-1ubuntu2
   Processing triggers for doc-base (0.10.7) ...
   Processing 2 added doc-base files...
   dpkg: error processing package ibus-gtk:amd64 (--configure):
package ibus-gtk:amd64 is not ready for configuration
  ErrorMessage: package ibus-gtk:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-04-03 (42 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: ibus
  Title: package ibus-gtk:amd64 1.5.11-1ubuntu2 failed to install/upgrade: 
package ibus-gtk:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1771345] Re: lscpu possible crash in min/max frequency

[Julian Andres Klode]

** Description changed:

- The following fixes are in 2.32 and also need to be backported to
- bionic, artful, and xenial:
+ [Impact]
+ lscpu prior to 2.32 does not correctly check for NULL members in min/max CPU 
frequency arrays and can call atof() on them, leading to crashes. It seems 
that's what caused the verification to fail for bug 1732865. The following 
fixes have been committed upstream:
  
- 
https://github.com/karelzak/util-linux/commit/0145d84a381fc2fcd7d37e0dbf3d9dff69609ecd
- 
https://github.com/karelzak/util-linux/commit/95f09bc63c564c50ec2c393352801cc056faaea2
+ from 2.30: https://github.com/karelzak/util-
+ linux/commit/0145d84a381fc2fcd7d37e0dbf3d9dff69609ecd
  
- This should also fix the crash in bug 1732865
+ from 2.32: https://github.com/karelzak/util-
+ linux/commit/95f09bc63c564c50ec2c393352801cc056faaea2
+ 
+ I plan to backport them to xenial (both patches); and artful, bionic
+ (second patch, they are > 2.30).
+ 
+ [Regression potential]
+ The worst possible regression is that lscpu would fail to correctly report 
min/max frequencies, but it seems unlikely, as we're only adding checks against 
null pointers / move an atof into a loop.
+ 
+ [Test case]
+ I'm afraid I don't have a test case, the bugs only manifest on some CPUs, and 
I don't know which.

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

Title:
  lscpu possible crash in min/max frequency

Status in util-linux package in Ubuntu:
  Fix Committed
Status in util-linux source package in Xenial:
  Triaged
Status in util-linux source package in Artful:
  Triaged
Status in util-linux source package in Bionic:
  Triaged

Bug description:
  [Impact]
  lscpu prior to 2.32 does not correctly check for NULL members in min/max CPU 
frequency arrays and can call atof() on them, leading to crashes. It seems 
that's what caused the verification to fail for bug 1732865. The following 
fixes have been committed upstream:

  from 2.30: https://github.com/karelzak/util-
  linux/commit/0145d84a381fc2fcd7d37e0dbf3d9dff69609ecd

  from 2.32: https://github.com/karelzak/util-
  linux/commit/95f09bc63c564c50ec2c393352801cc056faaea2

  I plan to backport them to xenial (both patches); and artful, bionic
  (second patch, they are > 2.30).

  [Regression potential]
  The worst possible regression is that lscpu would fail to correctly report 
min/max frequencies, but it seems unlikely, as we're only adding checks against 
null pointers / move an atof into a loop.

  [Test case]
  I'm afraid I don't have a test case, the bugs only manifest on some CPUs, and 
I don't know which.

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

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

[Touch-packages] [Bug 1771359] Re: No matching cipher found even if client and server have matching cipher

[Joshua Powers]

Hi, thanks for taking the time to file a bug.

The three ciphers you listed, aes128-cbc, 3des-cbc, and des-cbc, I
believe are not considered secure anymore. While your SSH client can use
them, it may not offer them without explicitly saying you wish to use
them as you have discovered.

It may be possible to use `ssh -vv ...` to produce some additional debug
output and may show what ciphers were offered.

As such I do not think this is actually a bug in Ubuntu and will mark it
incomplete. If you disagree or have additional information please feel
free to add it to this bug. Thanks again!

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

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

Title:
  No matching cipher found even if client and server have matching
  cipher

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Since Bionic upgrade (from Artful) I encounter problem to call HP
  switch with SSH.

  After the upgrade, trying to ssh some switch give me this message :

  $ ssh 192.168.0.1
  Unable to negotiate with 192.168.0.1 port 22: no matching cipher found. Their 
offer: aes128-cbc,3des-cbc,des-cbc

  So, I look for supported cipher :

  $ ssh -Q cipher
  3des-cbc
  aes128-cbc
  aes192-cbc
  aes256-cbc
  rijndael-...@lysator.liu.se
  aes128-ctr
  aes192-ctr
  aes256-ctr
  aes128-...@openssh.com
  aes256-...@openssh.com
  chacha20-poly1...@openssh.com

  I see that aes128-cbc seem both supported. So I try... :

  $ ssh -c aes128-cbc 192.168.0.1

  ...and It's work !

  Workaround :

  I've added “ciphers aes128-cbc” to ~/.ssh/config file for each switch
  I manage.

  The ssh-client should detect automatically the good cipher ? No ?

  Thank you for your attention.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssh-client 1:7.6p1-4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May 15 15:39:00 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:7.6p1-4
  SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017
  SourcePackage: openssh
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (21 days ago)

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

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

[Touch-packages] [Bug 1771359] Re: No matching cipher found even if client and server have matching cipher

[Joshua Powers]

Here are some change log entries confirming my suspicion:

openssh (1:7.4p1-1) unstable; urgency=medium

  * New upstream release (http://www.openssh.com/txt/release-7.4):
- ssh(1): Remove 3des-cbc from the client's default proposal.  64-bit
  block ciphers are not safe in 2016 and we don't want to wait until
  attacks like SWEET32 are extended to SSH.  As 3des-cbc was the only
  mandatory cipher in the SSH RFCs, this may cause problems connecting
  to older devices using the default configuration, but it's highly
  likely that such devices already need explicit configuration for key
  exchange and hostkey algorithms already anyway.

openssh (1:7.3p1-1) unstable; urgency=medium

  * New upstream release (http://www.openssh.com/txt/release-7.3):
- SECURITY: ssh(1), sshd(8): Fix observable timing weakness in the CBC
  padding oracle countermeasures.  Note that CBC ciphers are disabled by
  default and only included for legacy compatibility.

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

Title:
  No matching cipher found even if client and server have matching
  cipher

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Since Bionic upgrade (from Artful) I encounter problem to call HP
  switch with SSH.

  After the upgrade, trying to ssh some switch give me this message :

  $ ssh 192.168.0.1
  Unable to negotiate with 192.168.0.1 port 22: no matching cipher found. Their 
offer: aes128-cbc,3des-cbc,des-cbc

  So, I look for supported cipher :

  $ ssh -Q cipher
  3des-cbc
  aes128-cbc
  aes192-cbc
  aes256-cbc
  rijndael-...@lysator.liu.se
  aes128-ctr
  aes192-ctr
  aes256-ctr
  aes128-...@openssh.com
  aes256-...@openssh.com
  chacha20-poly1...@openssh.com

  I see that aes128-cbc seem both supported. So I try... :

  $ ssh -c aes128-cbc 192.168.0.1

  ...and It's work !

  Workaround :

  I've added “ciphers aes128-cbc” to ~/.ssh/config file for each switch
  I manage.

  The ssh-client should detect automatically the good cipher ? No ?

  Thank you for your attention.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssh-client 1:7.6p1-4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May 15 15:39:00 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:7.6p1-4
  SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017
  SourcePackage: openssh
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (21 days ago)

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

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

[Touch-packages] [Bug 1771598] Re: package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed sudo package pre-removal script subprocess returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed
  sudo package pre-removal script subprocess returned error exit status
  1

Status in sudo package in Ubuntu:
  New

Bug description:
  Hi, I tried editing the sudoers that is located on my Ubuntu setup on
  Virtual Box, it didn't allow me to update sudoers due to permission
  issues. I changed the permission of sudoers to 777 and was able to add
  my user name into it, however after that I was not able to run few
  commands hence I got instruction from google to purge and re-install
  it however it started throwing error afterwards however I noticed that
  I was able to remove my username entries from it before re-installing.
  Please suggest if I would need to re-install ubuntu on my virtual box
  or the current setup would work as before ?

  Thanks,
  Mahesh Bhatia

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: sudo 1.8.21p2-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   ubuntu-minimal:amd64: Purge
   sudo:amd64: Purge
   NULL: ConfigurePending
   NULL: PurgePending
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed May 16 16:17:51 2018
  ErrorMessage: installed sudo package pre-removal script subprocess returned 
error exit status 1
  InstallationDate: Installed on 2018-05-15 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: sudo
  Title: package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed 
sudo package pre-removal script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK
  mtime.conffile..etc.sudoers: 2018-05-16T16:12:29.233258

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

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

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

[Robie Basak]

Hello bugproxy, or anyone else affected,

Accepted util-linux into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.27.1-6ubuntu3.6 in a few hours, and then in the -proposed
repository.

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

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

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

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released

Bug description:
  [Impact]
  lscpu fails to list CPU max and min frequencies if some CPUs are guarded.

  [Regression potential]
  Isolated change to lscpu min/max CPU frequency output, so the worst that 
could happen is that it fails to work elsewhere.

  [Test case]
  1. Clone https://github.com/open-power/op-test-framework
  2. Run this command to GUARD the cpu.
  ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert
  3. Repeat again, so that multiple CPUs are guarded.
  4. Run lscpu
  5. Observe that no CPU frequencies are displayed:
  CPU max MHz: (null)
  CPU min MHz: (null)
  6. Install util-linux from -proposed.
  7. Run lscpu again
  8. Observe that max and min CPU frequencies are correctly displayed.

  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies

  Contact Information = ppaid...@in.ibm.com

  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = PowerNV 8284-22A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL

  Stack trace output:
   no

  Oops output:
   no

  Userspace tool common name: lscpu

  Userspace rpm: util-linux

  The userspace tool has the following bit modes: 64-bit

  System Dump Info:
    The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na

  *Additional Instructions for ppaid...@in.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 

[Touch-packages] [Bug 1771599] [NEW] OpenCV-3.2: Use of uninitialized variable in polygon drawing

[Vaclav Blazek]

Public bug reported:

Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
Package:libopencv-imgproc3.2:amd64 3.2.0+dfsg-4build2

The OpenCV version frozen in Ubuntu 18.04 has nasty bug where
uninitialized variables in the guts of drawing of a convex polygon runs
the output (random horizontal lines), see attached image.

This thing can ruin sofware perfecly working on OpenCV-2.4 for people
coming from Xenial to Bionic. See attached image to compare properly
rendered output and corrupted one.

This issue has already been fixed in the upstream
(https://github.com/opencv/opencv/commit/fa36b9d3455d62e98554a996dea3ebf7201109c2).
It would be worth to integrate the above mentioned patch it the 3.2.0
package in Bionic.

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


** Tags: opencv

** Attachment added: "Drawing result comparision. Left correct, right 
corrupted."
   
https://bugs.launchpad.net/bugs/1771599/+attachment/5140371/+files/drawing-comparision.png

** Description changed:

  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04
  Package:libopencv-imgproc3.2:amd64 3.2.0+dfsg-4build2
  
  The OpenCV version frozen in Ubuntu 18.04 has nasty bug where
- uninitialized variables in the guts of drawing of a convex polygon runs
+ uninitialized variables in the guts of drawing of a convex polygon ruins
  the output (random horizontal lines), see attached image.
  
  This thing can ruin sofware perfecly working on OpenCV-2.4 for people
  coming from Xenial to Bionic. See attached image to compare properly
  rendered output and corrupted one.
  
  This issue has already been fixed in the upstream
  
(https://github.com/opencv/opencv/commit/fa36b9d3455d62e98554a996dea3ebf7201109c2).
  It would be worth to integrate above mentioned patch it the 3.2.0
  package in Bionic.

** Description changed:

  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04
  Package:libopencv-imgproc3.2:amd64 3.2.0+dfsg-4build2
  
  The OpenCV version frozen in Ubuntu 18.04 has nasty bug where
- uninitialized variables in the guts of drawing of a convex polygon ruins
+ uninitialized variables in the guts of drawing of a convex polygon runs
  the output (random horizontal lines), see attached image.
  
  This thing can ruin sofware perfecly working on OpenCV-2.4 for people
  coming from Xenial to Bionic. See attached image to compare properly
  rendered output and corrupted one.
  
  This issue has already been fixed in the upstream
  
(https://github.com/opencv/opencv/commit/fa36b9d3455d62e98554a996dea3ebf7201109c2).
- It would be worth to integrate above mentioned patch it the 3.2.0
+ It would be worth to integrate the above mentioned patch it the 3.2.0
  package in Bionic.

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

Title:
  OpenCV-3.2: Use of uninitialized variable in polygon drawing

Status in apt package in Ubuntu:
  New

Bug description:
  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04
  Package:libopencv-imgproc3.2:amd64 3.2.0+dfsg-4build2

  The OpenCV version frozen in Ubuntu 18.04 has nasty bug where
  uninitialized variables in the guts of drawing of a convex polygon
  runs the output (random horizontal lines), see attached image.

  This thing can ruin sofware perfecly working on OpenCV-2.4 for people
  coming from Xenial to Bionic. See attached image to compare properly
  rendered output and corrupted one.

  This issue has already been fixed in the upstream
  
(https://github.com/opencv/opencv/commit/fa36b9d3455d62e98554a996dea3ebf7201109c2).
  It would be worth to integrate the above mentioned patch it the 3.2.0
  package in Bionic.

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

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

[Touch-packages] [Bug 1771345] Re: lscpu possible crash in min/max frequency

[Robie Basak]

Hello Julian, or anyone else affected,

Accepted util-linux into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.27.1-6ubuntu3.6 in a few hours, and then in the -proposed
repository.

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

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

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

** Changed in: util-linux (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Changed in: util-linux (Ubuntu Artful)
   Status: Triaged => Fix Committed

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

Title:
  lscpu possible crash in min/max frequency

Status in util-linux package in Ubuntu:
  Fix Committed
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Committed
Status in util-linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  lscpu prior to 2.32 does not correctly check for NULL members in min/max CPU 
frequency arrays and can call atof() on them, leading to crashes. It seems 
that's what caused the verification to fail for bug 1732865. The following 
fixes have been committed upstream:

  from 2.30: https://github.com/karelzak/util-
  linux/commit/0145d84a381fc2fcd7d37e0dbf3d9dff69609ecd

  from 2.32: https://github.com/karelzak/util-
  linux/commit/95f09bc63c564c50ec2c393352801cc056faaea2

  I plan to backport them to xenial (both patches); and artful, bionic
  (second patch, they are > 2.30).

  [Regression potential]
  The worst possible regression is that lscpu would fail to correctly report 
min/max frequencies, but it seems unlikely, as we're only adding checks against 
null pointers / move an atof into a loop.

  [Test case]
  Extract attached segvtest.tar.gz and run lscpu -s segvtest and check that it 
does not crash (this removes min mhz file for cpu #0 for testing).

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

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

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

[Robie Basak]

Hello Julian, or anyone else affected,

Accepted util-linux into artful-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.30.1-0ubuntu4.2 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, details of your
testing will help us make a better decision.

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

** Changed in: util-linux (Ubuntu Bionic)
   Status: Triaged => Fix Committed

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

Title:
  lscpu possible crash in min/max frequency

Status in util-linux package in Ubuntu:
  Fix Committed
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Committed
Status in util-linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  lscpu prior to 2.32 does not correctly check for NULL members in min/max CPU 
frequency arrays and can call atof() on them, leading to crashes. It seems 
that's what caused the verification to fail for bug 1732865. The following 
fixes have been committed upstream:

  from 2.30: https://github.com/karelzak/util-
  linux/commit/0145d84a381fc2fcd7d37e0dbf3d9dff69609ecd

  from 2.32: https://github.com/karelzak/util-
  linux/commit/95f09bc63c564c50ec2c393352801cc056faaea2

  I plan to backport them to xenial (both patches); and artful, bionic
  (second patch, they are > 2.30).

  [Regression potential]
  The worst possible regression is that lscpu would fail to correctly report 
min/max frequencies, but it seems unlikely, as we're only adding checks against 
null pointers / move an atof into a loop.

  [Test case]
  Extract attached segvtest.tar.gz and run lscpu -s segvtest and check that it 
does not crash (this removes min mhz file for cpu #0 for testing).

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

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

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

[Robie Basak]

Hello Julian, or anyone else affected,

Accepted util-linux into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.31.1-0.4ubuntu3.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

Title:
  lscpu possible crash in min/max frequency

Status in util-linux package in Ubuntu:
  Fix Committed
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Committed
Status in util-linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  lscpu prior to 2.32 does not correctly check for NULL members in min/max CPU 
frequency arrays and can call atof() on them, leading to crashes. It seems 
that's what caused the verification to fail for bug 1732865. The following 
fixes have been committed upstream:

  from 2.30: https://github.com/karelzak/util-
  linux/commit/0145d84a381fc2fcd7d37e0dbf3d9dff69609ecd

  from 2.32: https://github.com/karelzak/util-
  linux/commit/95f09bc63c564c50ec2c393352801cc056faaea2

  I plan to backport them to xenial (both patches); and artful, bionic
  (second patch, they are > 2.30).

  [Regression potential]
  The worst possible regression is that lscpu would fail to correctly report 
min/max frequencies, but it seems unlikely, as we're only adding checks against 
null pointers / move an atof into a loop.

  [Test case]
  Extract attached segvtest.tar.gz and run lscpu -s segvtest and check that it 
does not crash (this removes min mhz file for cpu #0 for testing).

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

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

[Touch-packages] [Bug 1771603] [NEW] Does not honour UID_MAX

[Marc Deslauriers]

Public bug reported:

accountsservice doesn't honour the UID_MAX settings in /etc/login.defs,
resulting in system users being displayed at the login screen and in the
users control panel.

See attached screenshot to see that the "libvirt-qemu" user is being
displayed when it shouldn't.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: accountsservice 0.6.45-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed May 16 11:03:09 2018
InstallationDate: Installed on 2017-12-12 (155 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: accountsservice
UpgradeStatus: Upgraded to bionic on 2018-05-09 (7 days ago)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "screenshot of issue"
   
https://bugs.launchpad.net/bugs/1771603/+attachment/5140372/+files/Screenshot%20from%202018-05-16%2011-05-30.png

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

Title:
  Does not honour UID_MAX

Status in accountsservice package in Ubuntu:
  New

Bug description:
  accountsservice doesn't honour the UID_MAX settings in
  /etc/login.defs, resulting in system users being displayed at the
  login screen and in the users control panel.

  See attached screenshot to see that the "libvirt-qemu" user is being
  displayed when it shouldn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: accountsservice 0.6.45-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 16 11:03:09 2018
  InstallationDate: Installed on 2017-12-12 (155 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: accountsservice
  UpgradeStatus: Upgraded to bionic on 2018-05-09 (7 days ago)

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

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

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

[Joshua Powers]

Confirmed this in a Cosmic container this morning. It appears the
version in cosmic has an issue with the underscore.

Steps to reproduce:
1. lxc launch ubuntu-daily:c c
2. lxc exec c bash
3. echo "PermitUserEnvironment yes" > /etc/ssh/sshd_config
4. ssh-import-id 
5. add environment="FOO_BAR=1" to start of ssh key line ~/.ssh/authorized_keys
6. attempt to ssh to container and get Permission denined
7. remove the underscore, attempt to ssh again, and ssh will be sucessful

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

** Changed in: openssh (Ubuntu)
   Importance: Low => High

** Tags added: cosmic

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

Title:
  Doesn't accept environment variable with underscore in its name in
  AuthorizedKeysFile

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  If environment variable name defined in AuthorizedKeysFile contains 
underscore character (environment="FOO_BAR=1" ...), sshd refuses connection and 
throws following error:
  authorized_keys:1: bad key options: invalid environment string

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

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

[Touch-packages] [Bug 1771011] Re: Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

[Joshua Powers]

This did not reproduce in xenial or bionic, so that narrows it down to a
change between 7.7p1-2 (cosmic) and 7.6p1-4 (bionic)

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

Title:
  Doesn't accept environment variable with underscore in its name in
  AuthorizedKeysFile

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  If environment variable name defined in AuthorizedKeysFile contains 
underscore character (environment="FOO_BAR=1" ...), sshd refuses connection and 
throws following error:
  authorized_keys:1: bad key options: invalid environment string

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

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

[Touch-packages] [Bug 1771345] Re: lscpu possible crash in min/max frequency

[Julian Andres Klode]

Test case

** Attachment added: "segvtest.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1771345/+attachment/5140350/+files/segvtest.tar.gz

** Description changed:

  [Impact]
  lscpu prior to 2.32 does not correctly check for NULL members in min/max CPU 
frequency arrays and can call atof() on them, leading to crashes. It seems 
that's what caused the verification to fail for bug 1732865. The following 
fixes have been committed upstream:
  
  from 2.30: https://github.com/karelzak/util-
  linux/commit/0145d84a381fc2fcd7d37e0dbf3d9dff69609ecd
  
  from 2.32: https://github.com/karelzak/util-
  linux/commit/95f09bc63c564c50ec2c393352801cc056faaea2
  
  I plan to backport them to xenial (both patches); and artful, bionic
  (second patch, they are > 2.30).
  
  [Regression potential]
  The worst possible regression is that lscpu would fail to correctly report 
min/max frequencies, but it seems unlikely, as we're only adding checks against 
null pointers / move an atof into a loop.
  
  [Test case]
- I'm afraid I don't have a test case, the bugs only manifest on some CPUs, and 
I don't know which.
+ Extract attached segvtest.tar.gz and run lscpu -s segvtest and check that it 
does not crash.

** Description changed:

  [Impact]
  lscpu prior to 2.32 does not correctly check for NULL members in min/max CPU 
frequency arrays and can call atof() on them, leading to crashes. It seems 
that's what caused the verification to fail for bug 1732865. The following 
fixes have been committed upstream:
  
  from 2.30: https://github.com/karelzak/util-
  linux/commit/0145d84a381fc2fcd7d37e0dbf3d9dff69609ecd
  
  from 2.32: https://github.com/karelzak/util-
  linux/commit/95f09bc63c564c50ec2c393352801cc056faaea2
  
  I plan to backport them to xenial (both patches); and artful, bionic
  (second patch, they are > 2.30).
  
  [Regression potential]
  The worst possible regression is that lscpu would fail to correctly report 
min/max frequencies, but it seems unlikely, as we're only adding checks against 
null pointers / move an atof into a loop.
  
  [Test case]
- Extract attached segvtest.tar.gz and run lscpu -s segvtest and check that it 
does not crash.
+ Extract attached segvtest.tar.gz and run lscpu -s segvtest and check that it 
does not crash (this removes min mhz file for cpu #0 for testing).

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

Title:
  lscpu possible crash in min/max frequency

Status in util-linux package in Ubuntu:
  Fix Committed
Status in util-linux source package in Xenial:
  Triaged
Status in util-linux source package in Artful:
  Triaged
Status in util-linux source package in Bionic:
  Triaged

Bug description:
  [Impact]
  lscpu prior to 2.32 does not correctly check for NULL members in min/max CPU 
frequency arrays and can call atof() on them, leading to crashes. It seems 
that's what caused the verification to fail for bug 1732865. The following 
fixes have been committed upstream:

  from 2.30: https://github.com/karelzak/util-
  linux/commit/0145d84a381fc2fcd7d37e0dbf3d9dff69609ecd

  from 2.32: https://github.com/karelzak/util-
  linux/commit/95f09bc63c564c50ec2c393352801cc056faaea2

  I plan to backport them to xenial (both patches); and artful, bionic
  (second patch, they are > 2.30).

  [Regression potential]
  The worst possible regression is that lscpu would fail to correctly report 
min/max frequencies, but it seems unlikely, as we're only adding checks against 
null pointers / move an atof into a loop.

  [Test case]
  Extract attached segvtest.tar.gz and run lscpu -s segvtest and check that it 
does not crash (this removes min mhz file for cpu #0 for testing).

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

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

[Touch-packages] [Bug 1771598] [NEW] package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed sudo package pre-removal script subprocess returned error exit status 1

[Mahesh]

Public bug reported:

Hi, I tried editing the sudoers that is located on my Ubuntu setup on
Virtual Box, it didn't allow me to update sudoers due to permission
issues. I changed the permission of sudoers to 777 and was able to add
my user name into it, however after that I was not able to run few
commands hence I got instruction from google to purge and re-install it
however it started throwing error afterwards however I noticed that I
was able to remove my username entries from it before re-installing.
Please suggest if I would need to re-install ubuntu on my virtual box or
the current setup would work as before ?

Thanks,
Mahesh Bhatia

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: sudo 1.8.21p2-3ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
AptOrdering:
 ubuntu-minimal:amd64: Purge
 sudo:amd64: Purge
 NULL: ConfigurePending
 NULL: PurgePending
 NULL: ConfigurePending
Architecture: amd64
Date: Wed May 16 16:17:51 2018
ErrorMessage: installed sudo package pre-removal script subprocess returned 
error exit status 1
InstallationDate: Installed on 2018-05-15 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: sudo
Title: package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed sudo 
package pre-removal script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
VisudoCheck:
 /etc/sudoers: parsed OK
 /etc/sudoers.d/README: parsed OK
mtime.conffile..etc.sudoers: 2018-05-16T16:12:29.233258

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

Title:
  package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed
  sudo package pre-removal script subprocess returned error exit status
  1

Status in sudo package in Ubuntu:
  New

Bug description:
  Hi, I tried editing the sudoers that is located on my Ubuntu setup on
  Virtual Box, it didn't allow me to update sudoers due to permission
  issues. I changed the permission of sudoers to 777 and was able to add
  my user name into it, however after that I was not able to run few
  commands hence I got instruction from google to purge and re-install
  it however it started throwing error afterwards however I noticed that
  I was able to remove my username entries from it before re-installing.
  Please suggest if I would need to re-install ubuntu on my virtual box
  or the current setup would work as before ?

  Thanks,
  Mahesh Bhatia

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: sudo 1.8.21p2-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   ubuntu-minimal:amd64: Purge
   sudo:amd64: Purge
   NULL: ConfigurePending
   NULL: PurgePending
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed May 16 16:17:51 2018
  ErrorMessage: installed sudo package pre-removal script subprocess returned 
error exit status 1
  InstallationDate: Installed on 2018-05-15 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: sudo
  Title: package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed 
sudo package pre-removal script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK
  mtime.conffile..etc.sudoers: 2018-05-16T16:12:29.233258

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

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

[Touch-packages] [Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'

[Mathieu Trudel-Lapierre]

This is fixed in cosmic; there a new version of initramfs-tools
(0.130ubuntu6).

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

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

Title:
  NFS-based remote root hangs when running 'netplan apply'

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  New
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Artful:
  New
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  New
Status in netplan.io source package in Bionic:
  Fix Committed
Status in nplan source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).

  [Test cases]
  1) Boot a system with its root filesystem over NFS.
  2) Run 'sudo netplan apply'
  3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.

  [Regression potential]
  This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.

  ---

  With a system booted on the network, with its remote root fs on NFS:

  Running 'netplan apply' restarts systemd-networkd, which releases the
  IP received from DHCP. With no IP (and and IP potentially changing),
  the NFS server can't be reached so the system hangs.

  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the effective IP remains the same.

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

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

[Touch-packages] [Bug 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - gnome-screensaver & gnome-shell fail to start?

[Jean-Baptiste Lallement]

I cannot reproduce this issue anymore with a fresh installation of
xenial upgraded to bionic. I'm wondering if the fontconfig fix that
delayed the boot was causing this issue (bug 1749546)

Setting to incomplete.

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

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

Title:
  Xenial -> Bionic - System fails to boot after upgrade - gnome-
  screensaver & gnome-shell fail to start?

Status in cryptsetup package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Test Case:
  1. Install Xenial Desktop with encrypted home
  2. Upgrade to bionic
  3. Reboot

  Actual Result
  The system appears to fail to start gnome-shell / gnome-screensaver:

  Apr 23 14:17:12 ubuntu dbus-daemon[1645]: [session uid=121 pid=1645] 
Activating service name='org.gnome.ScreenSaver' requested by ':1.3' (uid=121 
pid=1647 comm="/usr/lib/gnome-session/gnome-session-binary --auto
  Apr 23 14:17:12 ubuntu org.gnome.ScreenSaver[1645]: Unable to init server: 
Could not connect: Connection refused
  Apr 23 14:17:12 ubuntu gnome-screensav[1654]: Cannot open display:
  Apr 23 14:17:12 ubuntu dbus-daemon[1645]: [session uid=121 pid=1645] 
Activated service 'org.gnome.ScreenSaver' failed: Process org.gnome.ScreenSaver 
exited with status 1
  Apr 23 14:17:12 ubuntu gnome-session[1647]: gnome-session-binary[1647]: 
CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling 
StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.f
  Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: CRITICAL: Unable to create 
a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for 
org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error
  Apr 23 14:17:12 ubuntu gnome-shell[1656]: Failed to create backend: Could not 
find a primary drm kms device
  Apr 23 14:17:12 ubuntu gnome-session[1647]: gnome-session-binary[1647]: 
WARNING: App 'org.gnome.Shell.desktop' exited with code 1
  Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
  Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Apr 23 14:17:12 ubuntu gdm-launch-environment][1627]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm
  Apr 23 14:17:12 ubuntu gdm3[1187]: GdmDisplay: display lasted 0.292659 seconds
  Apr 23 14:17:12 ubuntu systemd-logind[1028]: Removed session c2.
  Apr 23 14:17:12 ubuntu spice-vdagentd[1186]: Error getting active session: No 
data available
  Apr 23 14:17:12 ubuntu spice-vdagentd[1186]: Error getting active session: No 
data available
  Apr 23 14:17:12 ubuntu gdm3[1187]: Child process -1643 was already dead.

  
  Also the system hangs on boot when it activates the encrypted swap. There are 
the following entries in the journal:
  $ journalctl -b-1 -o short-monotonic |grep crypt
  [1.535326] ubuntu kernel: Key type encrypted registered
  [  125.637205] ubuntu systemd[1]: Dependency failed for Cryptography Setup 
for cryptswap1.
  [  125.637789] ubuntu systemd[1]: Dependency failed for 
dev-mapper-cryptswap1.device.
  [  125.638311] ubuntu systemd[1]: Dependency failed for 
/dev/mapper/cryptswap1.
  [  125.639351] ubuntu systemd[1]: dev-mapper-cryptswap1.swap: Job 
dev-mapper-cryptswap1.swap/start failed with result 'dependency'.
  [  125.639478] ubuntu systemd[1]: dev-mapper-cryptswap1.device: Job 
dev-mapper-cryptswap1.device/start failed with result 'dependency'.
  [  125.639594] ubuntu systemd[1]: Dependency failed for Local Encrypted 
Volumes.
  [  125.640128] ubuntu systemd[1]: cryptsetup.target: Job 
cryptsetup.target/start failed with result 'dependency'.
  [  125.640266] ubuntu systemd[1]: systemd-cryptsetup@cryptswap1.service: Job 
systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'.
  [  383.902153] ubuntu systemd[1]: Starting Cryptography Setup for 
cryptswap1...
  [  383.913899] ubuntu systemd-cryptsetup[672]: Set cipher aes, mode 
xts-plain64, key size 256 bits for device 
/dev/disk/by-uuid/34ea85fd-854b-4892-95b9-7073dd2dbf7b.
  [  384.138596] ubuntu systemd[1]: Started Cryptography Setup for cryptswap1.
  [  384.143845] ubuntu systemd[1]: Reached target Local Encrypted Volumes.
  [  384.167475] ubuntu systemd[1]: Found device /dev/mapper/cryptswap1.
  [  384.171327] ubuntu systemd[1]: Activating swap /dev/mapper/cryptswap1...
  [  384.184639] ubuntu kernel: Adding 2093564k swap on /dev/mapper/cryptswap1. 
 Priority:-2 extents:1 across:2093564k FS
  [  384.191435] ubuntu systemd[1]: Activated swap /dev/mapper/cryptswap1.

  But eventually activates, once the device is there. Note this is not a
  hang, as timeouts are reached "instantly".

  ProblemType: Bug
  

[Touch-packages] [Bug 1771540] Re: i am not able to install the updates

[dino99]

Reporting againg 'xorg' is unrelated to 'upgrade'; should have been reported 
against 'apt' instead.
So all the logs joined here are useless for fixing that problem.

What are the outputs of:

sudo apt-get install -f
sudo apt-get update && sudo apt-get upgrade

Usually in such a case, either some package(s) are broken due to
dependencies conflict. If you have some ppa's package(s) installed, then
downgrade via 'ppa-purge'

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

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

Title:
  i am not able to install the updates

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
   i am not able to install the updates

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed May 16 15:19:58 2018
  DistUpgraded: 2017-09-01 00:53:53,943 WARNING no activity on terminal for 300 
seconds (Installed python3-renderpm (amd64))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2017-08-01 (287 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 5559
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=1cde99c2-2259-44dd-a873-b302c0633c92 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-08-31 (257 days ago)
  dmi.bios.date: 09/16/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.6
  dmi.board.name: 04D1V1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.6:bd09/16/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn04D1V1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May 16 13:57:14 2018
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1557 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1771513] Re: package ibus-gtk:amd64 1.5.11-1ubuntu2 failed to install/upgrade: package ibus-gtk:amd64 is not ready for configuration cannot configure (current status 'half-instal

[Olivier Tilloy]

Can you run the following command in a terminal and share the output?

sudo apt -f install

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

Title:
  package ibus-gtk:amd64 1.5.11-1ubuntu2 failed to install/upgrade:
  package ibus-gtk:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in ibus package in Ubuntu:
  New

Bug description:
  Hello

  Notification relating ibus appears when I open my notebook.
  I don't know what is about this but everything is working nice

  Version :ubuntu 16.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ibus-gtk:amd64 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Mon May 14 18:03:21 2018
  DuplicateSignature:
   package:ibus-gtk:amd64:1.5.11-1ubuntu2
   Processing triggers for doc-base (0.10.7) ...
   Processing 2 added doc-base files...
   dpkg: error processing package ibus-gtk:amd64 (--configure):
package ibus-gtk:amd64 is not ready for configuration
  ErrorMessage: package ibus-gtk:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-04-03 (42 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: ibus
  Title: package ibus-gtk:amd64 1.5.11-1ubuntu2 failed to install/upgrade: 
package ibus-gtk:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1771540] Re: i am not able to install the updates

[pawan naresh chandiramani]

I am getting failed to connect to a server and then it's saying check your
internet connection, but I am able to browse the net via my internet
connection

On Wed 16 May, 2018, 4:20 PM dino99, <1771...@bugs.launchpad.net> wrote:

> Reporting againg 'xorg' is unrelated to 'upgrade'; should have been
> reported against 'apt' instead.
> So all the logs joined here are useless for fixing that problem.
>
> What are the outputs of:
>
> sudo apt-get install -f
> sudo apt-get update && sudo apt-get upgrade
>
> Usually in such a case, either some package(s) are broken due to
> dependencies conflict. If you have some ppa's package(s) installed, then
> downgrade via 'ppa-purge'
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1771540
>
> Title:
>   i am not able to install the updates
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>i am not able to install the updates
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
>   Uname: Linux 4.4.0-98-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2.10
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   Date: Wed May 16 15:19:58 2018
>   DistUpgraded: 2017-09-01 00:53:53,943 WARNING no activity on terminal
> for 300 seconds (Installed python3-renderpm (amd64))
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   DpkgLog:
>
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07)
> (prog-if 00 [VGA controller])
>  Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
>   InstallationDate: Installed on 2017-08-01 (287 days ago)
>   InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64
> (20160803)
>   MachineType: Dell Inc. Inspiron 5559
>   ProcEnviron:
>LANGUAGE=en_IN:en
>PATH=(custom, no user)
>LANG=en_IN
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed
> root=UUID=1cde99c2-2259-44dd-a873-b302c0633c92 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: Upgraded to xenial on 2017-08-31 (257 days ago)
>   dmi.bios.date: 09/16/2015
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.0.6
>   dmi.board.name: 04D1V1
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.0.6:bd09/16/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn04D1V1:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: Inspiron 5559
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.1-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20160325-1ubuntu1.2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.12-1build2
>   xserver.bootTime: Wed May 16 13:57:14 2018
>   xserver.configfile: default
>   xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.outputs:
>product id1557
>vendor BOE
>   xserver.version: 2:1.18.4-0ubuntu0.7
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771540/+subscriptions
>

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

Title:
  i am not able to install the updates

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
   i am not able to install the updates

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: 

[Touch-packages] [Bug 1771557] Re: NVMe boot drives not supported - failing in generating initramfs

[Guilherme G. Piccoli]

** Changed in: initramfs-tools (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: initramfs-tools (Ubuntu)
   Importance: High => Medium

** Changed in: initramfs-tools (Ubuntu)
Milestone: trusty-updates => None

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

Title:
  NVMe boot drives not supported - failing in generating initramfs

Status in initramfs-tools:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Released

Bug description:
  [Impact] 
  The initramfs-tools hook-functions script cannot translate nvmeXnYpZ to 
nvmeXnY block device, so it's failing and not building the initram disk.

  Upstream solution is composed for at least 2 patches (it's a series,
  but the 2 below are really the needed ones):

  commit 3cb744c9
  Author: Ben Hutchings 
  hook-functions: Rewrite block device sysfs lookup to be generic

  commit 8ac52dc0
  Author: Ben Hutchings 
  hook-functions: Include modules for all components of a multi-disk device

  Instead of doing the backport, which is huge, we added another sed 
substitution: currently the script has substitutions for sdX and hdX, in order 
to convert sda1 to sda, for example. The new substitution converts nvmeXnYpZ to 
nvmeXnY.
  It's less intrusive than the full backport, since this is a SRU to Trusty 
only.

  
  [Test Case]
  To be added.

  
  [Regression Potential] 
  If the sed expression was somewhat broken, we could have an issue generating 
initiramfs for generic block devices, like regular HDDs.

  
  [Other Info]
  This issue is based on Debian bug #785147: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147

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

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

[Touch-packages] [Bug 1771557] Re: NVMe boot drives not supported - failing in generating initramfs

[Guilherme G. Piccoli]

** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu)

** Changed in: initramfs-tools (Ubuntu Xenial)
   Importance: Undecided => Medium

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

** Changed in: initramfs-tools (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: initramfs-tools (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: initramfs-tools (Ubuntu Trusty)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: initramfs-tools (Ubuntu Trusty)
Milestone: None => trusty-updates

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

Title:
  NVMe boot drives not supported - failing in generating initramfs

Status in initramfs-tools:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Trusty:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Released

Bug description:
  [Impact] 
  The initramfs-tools hook-functions script cannot translate nvmeXnYpZ to 
nvmeXnY block device, so it's failing and not building the initram disk.

  Upstream solution is composed for at least 2 patches (it's a series,
  but the 2 below are really the needed ones):

  commit 3cb744c9
  Author: Ben Hutchings 
  hook-functions: Rewrite block device sysfs lookup to be generic

  commit 8ac52dc0
  Author: Ben Hutchings 
  hook-functions: Include modules for all components of a multi-disk device

  Instead of doing the backport, which is huge, we added another sed 
substitution: currently the script has substitutions for sdX and hdX, in order 
to convert sda1 to sda, for example. The new substitution converts nvmeXnYpZ to 
nvmeXnY.
  It's less intrusive than the full backport, since this is a SRU to Trusty 
only.

  
  [Test Case]
  To be added.

  
  [Regression Potential] 
  If the sed expression was somewhat broken, we could have an issue generating 
initiramfs for generic block devices, like regular HDDs.

  
  [Other Info]
  This issue is based on Debian bug #785147: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147

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

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

[Touch-packages] [Bug 1769346] Re: Unable to install 18.04 server AMD64 with targeted kernel: initramfs-tools

[Manny Flores]

I fixed this error by updating my BIOS. Weird - I didn't have this issue
with prior versions including 16.04.4 but when I also tried 16.04.4, I
got the same problem. I might have been using an earlier 16.04.x where
this wasn't an issue. But again, in the end, the BIOS did the trick.

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

Title:
  Unable to install 18.04 server AMD64 with targeted kernel: initramfs-
  tools

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Trying to install from: ubuntu-18.04-server-amd64.iso

  at boot: F6->expert mode and F4->minimal VM

  I go through the usual steps but when it comes to the "install the
  system" phase, if I select normal (not live) and then "targeted", the
  installation stops with an error on initramfs.

  The error doesn't occur if I use a generic kernel instead of the
  targeted one.

  at that phase I'm not yet able to install reportbug so below you'll
  find what I found in syslog. VM running under ESXi 6.7.

  Thanks!

  May  5 12:52:58 in-target: (Reading database ... 100%^M(Reading database ... 
11077 files and directories currently installed.)^M
  May  5 12:52:58 in-target: Preparing to unpack 
.../0-linux-headers-4.15.0-20_4.15.0-20.21_all.deb ...^M
  May  5 12:52:58 in-target: Unpacking linux-headers-4.15.0-20 (4.15.0-20.21) 
...^M
  May  5 12:53:03 in-target: Selecting previously unselected package 
linux-headers-4.15.0-20-generic.^M
  May  5 12:53:03 in-target: Preparing to unpack 
.../1-linux-headers-4.15.0-20-generic_4.15.0-20.21_amd64.deb ...^M
  May  5 12:53:03 in-target: Unpacking linux-headers-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:05 in-target: Selecting previously unselected package 
linux-headers-generic.^M
  May  5 12:53:05 in-target: Preparing to unpack 
.../2-linux-headers-generic_4.15.0.20.23_amd64.deb ...^M
  May  5 12:53:05 in-target: Unpacking linux-headers-generic (4.15.0.20.23) 
...^M
  May  5 12:53:05 in-target: Selecting previously unselected package 
linux-headers-virtual.^M
  May  5 12:53:05 in-target: Preparing to unpack 
.../3-linux-headers-virtual_4.15.0.20.23_amd64.deb ...^M
  May  5 12:53:05 in-target: Unpacking linux-headers-virtual (4.15.0.20.23) 
...^M
  May  5 12:53:05 in-target: Selecting previously unselected package 
linux-modules-4.15.0-20-generic.^M
  May  5 12:53:05 in-target: Preparing to unpack 
.../4-linux-modules-4.15.0-20-generic_4.15.0-20.21_amd64.deb ...^M
  May  5 12:53:05 in-target: Unpacking linux-modules-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:08 in-target: Selecting previously unselected package 
linux-image-4.15.0-20-generic.^M
  May  5 12:53:08 in-target: Preparing to unpack 
.../5-linux-image-4.15.0-20-generic_4.15.0-20.21_amd64.deb ...^M
  May  5 12:53:08 in-target: Unpacking linux-image-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:08 in-target: Selecting previously unselected package 
linux-image-virtual.^M
  May  5 12:53:08 in-target: Preparing to unpack 
.../6-linux-image-virtual_4.15.0.20.23_amd64.deb ...^M
  May  5 12:53:08 in-target: Unpacking linux-image-virtual (4.15.0.20.23) ...^M
  May  5 12:53:08 in-target: Selecting previously unselected package 
linux-virtual.^M
  May  5 12:53:08 in-target: Preparing to unpack 
.../7-linux-virtual_4.15.0.20.23_amd64.deb ...^M
  May  5 12:53:08 in-target: Unpacking linux-virtual (4.15.0.20.23) ...^M
  May  5 12:53:09 in-target: Setting up linux-modules-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:09 in-target: Setting up linux-image-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:09 in-target: I: /vmlinuz.old is now a symlink to 
boot/vmlinuz-4.15.0-20-generic^M
  May  5 12:53:09 in-target: I: /initrd.img.old is now a symlink to 
boot/initrd.img-4.15.0-20-generic^M
  May  5 12:53:09 in-target: I: /vmlinuz is now a symlink to 
boot/vmlinuz-4.15.0-20-generic^M
  May  5 12:53:09 in-target: I: /initrd.img is now a symlink to 
boot/initrd.img-4.15.0-20-generic^M
  May  5 12:53:09 in-target: Setting up linux-image-virtual (4.15.0.20.23) ...^M
  May  5 12:53:10 in-target: Setting up linux-headers-4.15.0-20 (4.15.0-20.21) 
...^M
  May  5 12:53:10 in-target: Setting up linux-headers-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:10 in-target: Setting up linux-headers-generic (4.15.0.20.23) 
...^M
  May  5 12:53:10 in-target: Setting up linux-headers-virtual (4.15.0.20.23) 
...^M
  May  5 12:53:10 in-target: Setting up linux-virtual (4.15.0.20.23) ...^M
  May  5 12:53:10 in-target: Processing triggers for 
linux-image-4.15.0-20-generic (4.15.0-20.21) ...^M
  May  5 12:53:10 in-target: /etc/kernel/postinst.d/initramfs-tools:^M
  May  5 12:53:10 in-target: update-initramfs: Generating 
/boot/initrd.img-4.15.0-20-generic^M
  May  5 12:53:10 in-target: mkinitramfs: failed to determine device for /^M
  May  5 12:53:10 in-target: 

[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[Bug Watch Updater]

** Changed in: network-manager
   Status: Confirmed => Fix Released

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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

[Touch-packages] [Bug 1771557] [NEW] NVMe boot drives not supported - failing in generating initramfs

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Impact] 
The initramfs-tools hook-functions script cannot translate nvmeXnYpZ to nvmeXnY 
block device, so it's failing and not building the initram disk.

Upstream solution is composed for at least 2 patches (it's a series, but
the 2 below are really the needed ones):

commit 3cb744c9
Author: Ben Hutchings 
hook-functions: Rewrite block device sysfs lookup to be generic

commit 8ac52dc0
Author: Ben Hutchings 
hook-functions: Include modules for all components of a multi-disk device

Instead of doing the backport, which is huge, we added another sed 
substitution: currently the script has substitutions for sdX and hdX, in order 
to convert sda1 to sda, for example. The new substitution converts nvmeXnYpZ to 
nvmeXnY.
It's less intrusive than the full backport, since this is a SRU to Trusty only.


[Test Case]
To be added.


[Regression Potential] 
If the sed expression was somewhat broken, we could have an issue generating 
initiramfs for generic block devices, like regular HDDs.


[Other Info]
This issue is based on Debian bug #785147: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147

** Affects: initramfs-tools
 Importance: Unknown
 Status: Fix Released

** Affects: initramfs-tools (Ubuntu)
 Importance: High
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: In Progress

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

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


** Tags: sts trusty
-- 
NVMe boot drives not supported - failing in generating initramfs
https://bugs.launchpad.net/bugs/1771557
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to initramfs-tools in Ubuntu.

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

[Touch-packages] [Bug 1763096] Re: Multiple memory corruption in as-new (binuitils-2.30-15ubuntu1)

[Matthias Klose]

** Also affects: binutils (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  Multiple memory corruption in as-new (binuitils-2.30-15ubuntu1)

Status in binutils package in Ubuntu:
  New
Status in binutils source package in Bionic:
  New

Bug description:
  Dear all,
  The following binutils as-new memory corruptions were found by a modified 
version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have 
attached the crashing inputs and each ASAN report.

  Steps to reproduce:

  Build current verison of binutils:
  ```
  pull-lp-source binutils
  cd binutils-2.30
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" 
LDFLAGS="-fsanitize=address" ./configure
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address
  -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make
  ```

  run inputs under ASAN:

  ```
  ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./as-new $file
  ```

  We can verify those issues for as-new binuitils-2.30-15ubuntu1 (Ubuntu
  16.04.4 LTS / sources from "pull-lp-source bintuils").

  Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr-
  Universität Bochum)

  Best regards,
  Sergej Schumilo

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

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

[Touch-packages] [Bug 1771557] Re: NVMe boot drives not supported - failing in generating initramfs

[Guilherme G. Piccoli]

** Description changed:

- [Impact] 
- The initramfs-tools hook-functions script cannot translate nvmeXnYpZ to 
nvmeXnY block device, so it's failing and not building the initram disk.
+ [Impact]
  
- Upstream solution is composed for at least 2 patches (it's a series, but
+ When creating the initramfs image, mkinitramfs has multiple options on
+ how to include modules. The default (and most common) one is the
+ "MODULES=most", which includes the majority of filesystem modules and
+ all the block device drivers. One other option is "MODULES=dep", which
+ tries to descend in the sysfs hierarchy and guess modules to add, with
+ the goal of reduce the size of initramfs.
+ 
+ For the MODULES=dep case, the initramfs-tools hook-functions script
+ cannot translate nvmeXnYpZ to nvmeXnY block device, so it's failing in
+ the sysfs lookup, so it does not build the initram disk.
+ 
+ Upstream solution is composed of at least 2 patches (it's a series, but
  the 2 below are really the needed ones):
  
  commit 3cb744c9
  Author: Ben Hutchings 
  hook-functions: Rewrite block device sysfs lookup to be generic
  
  commit 8ac52dc0
  Author: Ben Hutchings 
  hook-functions: Include modules for all components of a multi-disk device
  
- Instead of doing the backport, which is huge, we added another sed 
substitution: currently the script has substitutions for sdX and hdX, in order 
to convert sda1 to sda, for example. The new substitution converts nvmeXnYpZ to 
nvmeXnY.
- It's less intrusive than the full backport, since this is a SRU to Trusty 
only.
+ Instead of doing the huge backport, we added another sed substitution: 
currently the script has substitutions for sdX and hdX, in order to convert 
sda1 to sda, for example. The new substitution converts nvmeXnYpZ to nvmeXnY.
+ It's less intrusive than the full backport, since this is a minimal SRU to 
Trusty only.
  
  
  [Test Case]
- To be added.
+ 1. Install Trusty with rootfs in a multi-disk(md) array composed of two nvme 
partitions - in my tests, I've used a RAID1.
+ 
+ (lsblk output of my test env:
+ 
+ nvme0n1 259:0010G  0 disk  
+ └─nvme0n1p1 259:1010G  0 part  
+   └─md0   9:0010G  0 raid1 /
+ nvme1n1 259:2010G  0 disk  
+ └─nvme1n1p1 259:3010G  0 part  
+   └─md0   9:0010G  0 raid1 /
+ )
  
  
- [Regression Potential] 
- If the sed expression was somewhat broken, we could have an issue generating 
initiramfs for generic block devices, like regular HDDs.
+ 2. Once system is booted, modify the "/etc/initramfs-tools/initramfs.conf", 
replacing "MODULES=most" to "MODULES=dep".
+ 
+ 3. Update your initramfs by running something like:
+ "update-initramfs -u -k "
+ 
+ The initramfs creating procedure will fail, unless the patch from this
+ LP is present.
+ 
+ 
+ [Regression Potential]
+ If the sed expression was somewhat broken, we could have an issue generating 
initiramfs when MODULES is set to "dep", even for generic block devices (like 
regular HDDs).
  
  
  [Other Info]
  This issue is based on Debian bug #785147: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147

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

Title:
  NVMe boot drives not supported - failing in generating initramfs

Status in initramfs-tools:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  When creating the initramfs image, mkinitramfs has multiple options on
  how to include modules. The default (and most common) one is the
  "MODULES=most", which includes the majority of filesystem modules and
  all the block device drivers. One other option is "MODULES=dep", which
  tries to descend in the sysfs hierarchy and guess modules to add, with
  the goal of reduce the size of initramfs.

  For the MODULES=dep case, the initramfs-tools hook-functions script
  cannot translate nvmeXnYpZ to nvmeXnY block device, so it's failing in
  the sysfs lookup, so it does not build the initram disk.

  Upstream solution is composed of at least 2 patches (it's a series,
  but the 2 below are really the needed ones):

  commit 3cb744c9
  Author: Ben Hutchings 
  hook-functions: Rewrite block device sysfs lookup to be generic

  commit 8ac52dc0
  Author: Ben Hutchings 
  hook-functions: Include modules for all components of a multi-disk device

  Instead of doing the huge backport, we added another sed substitution: 
currently the script has substitutions for sdX and hdX, in order to convert 
sda1 to sda, for example. The new substitution converts nvmeXnYpZ to nvmeXnY.
  It's less intrusive than the full backport, since this is a 

[Touch-packages] [Bug 1771628] [NEW] Grpahic Drivers

[Gurjeet]

Public bug reported:

Hi,

I'm getting a purple blank screen after putting my creadentials when the
computer is starting.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 16 19:05:08 2018
DistUpgraded: 2018-05-16 16:54:13,314 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704]
InstallationDate: Installed on 2016-11-01 (560 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:670c Microdia 
 Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
 Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9350
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=247af43d-40d7-48c1-8502-e54796f36b07 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-16 (0 days ago)
dmi.bios.date: 06/14/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.4
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic 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/1771628

Title:
  Grpahic Drivers

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  I'm getting a purple blank screen after putting my creadentials when
  the computer is starting.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 16 19:05:08 2018
  DistUpgraded: 2018-05-16 16:54:13,314 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704]
  InstallationDate: Installed on 2016-11-01 (560 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=247af43d-40d7-48c1-8502-e54796f36b07 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (0 days ago)
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  

[Touch-packages] [Bug 1771557] Re: NVMe boot drives not supported - failing in generating initramfs

[Guilherme G. Piccoli]

This solution was suggested by Szilard Cserey and further improved by
Dan Streetman - thanks both!

** Patch added: "lp1771557_v1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1771557/+attachment/5140444/+files/lp1771557_v1.debdiff

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

Title:
  NVMe boot drives not supported - failing in generating initramfs

Status in initramfs-tools:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  When creating the initramfs image, mkinitramfs has multiple options on
  how to include modules. The default (and most common) one is the
  "MODULES=most", which includes the majority of filesystem modules and
  all the block device drivers. One other option is "MODULES=dep", which
  tries to descend in the sysfs hierarchy and guess modules to add, with
  the goal of reduce the size of initramfs.

  For the MODULES=dep case, the initramfs-tools hook-functions script
  cannot translate nvmeXnYpZ to nvmeXnY block device, so it's failing in
  the sysfs lookup, so it does not build the initram disk.

  Upstream solution is composed of at least 2 patches (it's a series,
  but the 2 below are really the needed ones):

  commit 3cb744c9
  Author: Ben Hutchings 
  hook-functions: Rewrite block device sysfs lookup to be generic

  commit 8ac52dc0
  Author: Ben Hutchings 
  hook-functions: Include modules for all components of a multi-disk device

  Instead of doing the huge backport, we added another sed substitution: 
currently the script has substitutions for sdX and hdX, in order to convert 
sda1 to sda, for example. The new substitution converts nvmeXnYpZ to nvmeXnY.
  It's less intrusive than the full backport, since this is a minimal SRU to 
Trusty only.


  [Test Case]
  1. Install Trusty with rootfs in a multi-disk(md) array composed of two nvme 
partitions - in my tests, I've used a RAID1.

  (lsblk output of my test env:

  nvme0n1 259:0010G  0 disk  
  └─nvme0n1p1 259:1010G  0 part  
└─md0   9:0010G  0 raid1 /
  nvme1n1 259:2010G  0 disk  
  └─nvme1n1p1 259:3010G  0 part  
└─md0   9:0010G  0 raid1 /
  )

  
  2. Once system is booted, modify the "/etc/initramfs-tools/initramfs.conf", 
replacing "MODULES=most" to "MODULES=dep".

  3. Update your initramfs by running something like:
  "update-initramfs -u -k "

  The initramfs creating procedure will fail, unless the patch from this
  LP is present.


  [Regression Potential]
  If the sed expression was somewhat broken, we could have an issue generating 
initiramfs when MODULES is set to "dep", even for generic block devices (like 
regular HDDs).


  [Other Info]
  This issue is based on Debian bug #785147: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147

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

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

[Touch-packages] [Bug 1769657] Re: update toolchain packages for bionic

[Matthias Klose]

** Description changed:

  I'd like to update the toolchain packages in bionic, to state which we
  have in cosmic on May 07:
  
-  - binutils updates from the branch
-  - gcc-8, update to the final 8.1.0 release
-  - gcc-7, updates to the gcc-7-branch up to the time of the
-8.1.0 release.
-  - gcc-defaults to bump the 8.1 version, and add some provides
-  - build-essential to add cross packages for amd64 and i386
-  - corresponding gcc-cross packages
+  - LP: #1771635: binutils updates from the branch
+  - gcc-8, update to the final 8.1.0 release
+  - gcc-7, updates to the gcc-7-branch up to the time of the
+    8.1.0 release.
+  - gcc-defaults to bump the 8.1 version, and add some provides
+  - build-essential to add cross packages for amd64 and i386
+  - corresponding gcc-cross packages
  
  The package builds are prepared in
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages

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

Title:
  update toolchain packages for bionic

Status in binutils package in Ubuntu:
  New
Status in build-essential package in Ubuntu:
  New
Status in cross-toolchain-base package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in gcc-7-cross package in Ubuntu:
  New
Status in gcc-7-cross-ports package in Ubuntu:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gcc-8-cross package in Ubuntu:
  New
Status in gcc-8-cross-ports package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  New
Status in gcc-defaults-ports package in Ubuntu:
  New

Bug description:
  I'd like to update the toolchain packages in bionic, to state which we
  have in cosmic on May 07:

   - LP: #1771635: binutils updates from the branch
   - gcc-8, update to the final 8.1.0 release
   - gcc-7, updates to the gcc-7-branch up to the time of the
     8.1.0 release.
   - gcc-defaults to bump the 8.1 version, and add some provides
   - build-essential to add cross packages for amd64 and i386
   - corresponding gcc-cross packages

  The package builds are prepared in
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages

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

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

[Touch-packages] [Bug 1771635] [NEW] SRU: update binutils for bionic

[Matthias Klose]

Public bug reported:

This is the binutils part of LP: #1769657.

The update contains backports from the 2.30 branch.  GCC packages, and
GCC cross packages have been tebuilt using this version in cosmic. The
kernel has been rebuilt with -17 in cosmic.

Changes are:

  * Fix PR gprof/23056, memory corruption in gprof. LP: #1763098.
  * Fix PR binutils/23054, memory corruption in as. LP: #1763096.
  * Fix PR ld/23055, memory corruption in ld. LP: #1763094.
- Fix PR binutils/23109, disassembly mask for vector sdot on AArch64.
- Fix uninitialised memory acccess in COFF bfd backend.
- Update Portuguese translations.
- Fix PR ld/23123, PR ld/22374, PowerPC32 ifunc regression.
- AArch64: Fix the mask for the sqrdml(a|s)h instructions.
  * Fix unintialized memory in aarch64 opcodes, taken from the trunk.
- Fix PR ld 22782, x86: Remove the unused _GLOBAL_OFFSET_TABLE_.
- Update spanish and russian translations.

Packaging changes:

  * Add amd64, i386, x32 and riscv64 cross compilers as build (test)
dependencies.

Acceptance criteria:

 * The package builds and doesn't show any regression in the testsuite
and autopkg tests.

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

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

Title:
  SRU: update binutils for bionic

Status in binutils package in Ubuntu:
  New

Bug description:
  This is the binutils part of LP: #1769657.

  The update contains backports from the 2.30 branch.  GCC packages, and
  GCC cross packages have been tebuilt using this version in cosmic. The
  kernel has been rebuilt with -17 in cosmic.

  Changes are:

* Fix PR gprof/23056, memory corruption in gprof. LP: #1763098.
* Fix PR binutils/23054, memory corruption in as. LP: #1763096.
* Fix PR ld/23055, memory corruption in ld. LP: #1763094.
  - Fix PR binutils/23109, disassembly mask for vector sdot on AArch64.
  - Fix uninitialised memory acccess in COFF bfd backend.
  - Update Portuguese translations.
  - Fix PR ld/23123, PR ld/22374, PowerPC32 ifunc regression.
  - AArch64: Fix the mask for the sqrdml(a|s)h instructions.
* Fix unintialized memory in aarch64 opcodes, taken from the trunk.
  - Fix PR ld 22782, x86: Remove the unused _GLOBAL_OFFSET_TABLE_.
  - Update spanish and russian translations.

  Packaging changes:

* Add amd64, i386, x32 and riscv64 cross compilers as build (test)
  dependencies.

  Acceptance criteria:

   * The package builds and doesn't show any regression in the testsuite
  and autopkg tests.

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

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

[Touch-packages] [Bug 1763094] Re: Multiple memory corruption in ld-new (binuitils-2.30-15ubuntu1)

[Matthias Klose]

** Also affects: binutils (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  Multiple memory corruption in ld-new (binuitils-2.30-15ubuntu1)

Status in binutils package in Ubuntu:
  New
Status in binutils source package in Bionic:
  New

Bug description:
  Dear all,
  The following binutils ld-new memory corruptions were found by a modified 
version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have 
attached the crashing inputs and each ASAN report.

  Steps to reproduce:

  Build current verison of binutils:
  ```
  pull-lp-source binutils
  cd binutils-2.30
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" 
LDFLAGS="-fsanitize=address" ./configure
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address
  -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make
  ```

  Run inputs under ASAN:

  ```
  ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./ld-new $file
  ```

  We can verify those issues for ld-new binuitils-2.30-15ubuntu1 (Ubuntu
  16.04.4 LTS / sources from "pull-lp-source bintuils").

  Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr-
  Universität Bochum)

  Best regards,
  Sergej Schumilo

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

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

[Touch-packages] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

[Brian Murray]

Setting to v-done for artful since I did the verification for bug
1624644.

** 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1675079

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  New
Status in update-manager source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Artful:
  New
Status in update-manager source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

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

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

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Brian Murray]

Verified update-manager for artful.

** Attachment added: "bug-1624644-verification.png"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1624644/+attachment/5140527/+files/bug-1624644-verification.png

** 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1624644

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Released
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades, the fix comes in an update of u-u) Run
  unattended-upgrades manually and observe the removal of the
  autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

[Launchpad Bug Tracker]

This bug was fixed in the package update-manager - 1:17.10.14

---
update-manager (1:17.10.14) artful; urgency=medium

  * Offer removal of unused autoremovable kernel packages
(LP: #1624644, #1675079)
  * Support package removals in install backends and really remove packages
(LP: #1624644, #1675079)
  * Keep PEP 8 checks happy
  * Place .keep files in empty directories to keep them when converting the
repo to git (LP: #1758963)

 -- Balint Reczey   Sun, 25 Mar 2018 19:57:57 +0100

** Changed in: update-manager (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  New
Status in update-manager source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  New
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

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

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

[Touch-packages] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

[Launchpad Bug Tracker]

This bug was fixed in the package update-manager - 1:16.04.13

---
update-manager (1:16.04.13) xenial; urgency=medium

  * Offer removal of unused autoremovable kernel packages
(LP: #1624644, #1675079)
  * Support package removals in install backends and really remove packages
(LP: #1624644, #1675079)
  * Keep PEP 8 checks happy
  * Place .keep files in empty directories to keep them when converting the
repo to git (LP: #1758963)

 -- Balint Reczey   Sun, 25 Mar 2018 20:10:49 +0100

** Changed in: update-manager (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  New
Status in update-manager source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  New
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

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

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

[Touch-packages] [Bug 1675079] Update Released

[Brian Murray]

The verification of the Stable Release Update for update-manager has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  New
Status in update-manager source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  New
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

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

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

[Touch-packages] [Bug 1771689] Re: initramfs resets usb 3 bus while booting from usb 3 drive

[Damion Milne]

Here is some more-detailed description of my USB 3.0 adapter:
$ sudo lspci -nn | fgrep -i 'usb 3'
02:00.0 USB controller [0c03]: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 
xHCI Host Controller [104c:8241] (rev 02)

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

Title:
  initramfs resets usb 3 bus while booting from usb 3 drive

Status in busybox package in Ubuntu:
  New

Bug description:
  I boot ubuntu from a usb 3.0 thumb drive.
  But during boot, booting stops at a busybox prompt.
  Output of dmesg | tail says:
22.888260 usb 4-2: reset SuperSpeed USB device number 2 using xhci-hcd

  My work-around is to: unplug the usb 3.0 drive, plug it back in, then type 
exit.
  After that, ubuntu boot normally.

  Busybox version, stated at busybox prompt, is:
v1.27.2

  1) $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2) $ dpkg-query -l busybox-initramfs
  ii  busybox-initra 1:1.27.2-2ub amd64Standalone shell setup for initra

  3) I expect ubuntu to boot from the usb 3.0 drive, without having to
  use my work-around described above. It used to work fine on older
  versions of ubuntu.

  4) Instead booting stops at a busybox prompt as described above.

  Here is my PC's model of USB 3.0 adapter:
  $ sudo lspci | fgrep -i 'usb 3'
  02:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI 
Host Controller (rev 02)

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: busybox-initramfs 1:1.27.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 16 23:48:22 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  InstallationDate: Installed on 2017-06-28 (322 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: busybox
  UpgradeStatus: Upgraded to bionic on 2018-05-09 (6 days ago)

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

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

[Touch-packages] [Bug 1726802] Re: battery charging not showing if plugged in during boot

[Aniruddha Sarkar]

That problem has been resolved and was occuring due to battery
optimisation techniques and is not a bug (i guess).

** Changed in: indicator-power (Ubuntu)
   Status: Expired => Invalid

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

Title:
  battery charging not showing if plugged in during boot

Status in indicator-power package in Ubuntu:
  Invalid

Bug description:
  When I power up my device without plugging in, the indicator shows
  charging, but whenever I am powering up my laptop after plugging in
  the battery indicator is not showing charging.

  I am using ASUS R558U.

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

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

[Touch-packages] [Bug 1771699] [NEW] /usr/bin/python2.7:11:PyEval_EvalFrameEx:fast_function:call_function:PyEval_EvalFrameEx:fast_function

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
python2.7.  This problem was most recently seen with package version 
2.7.15~rc1-1, the problem page at 
https://errors.ubuntu.com/problem/78a0284e5690357b20d12b3ccbf616e100f5a01f 
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/.

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful bionic kylin-14.10 kylin-15.04 kylin-17.10 kylin-18.04 quantal 
saucy trusty utopic vivid wily xenial yakkety zesty

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

Title:
  
/usr/bin/python2.7:11:PyEval_EvalFrameEx:fast_function:call_function:PyEval_EvalFrameEx:fast_function

Status in python2.7 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
python2.7.  This problem was most recently seen with package version 
2.7.15~rc1-1, the problem page at 
https://errors.ubuntu.com/problem/78a0284e5690357b20d12b3ccbf616e100f5a01f 
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/python2.7/+bug/1771699/+subscriptions

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

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Launchpad Bug Tracker]

This bug was fixed in the package update-manager - 1:16.04.13

---
update-manager (1:16.04.13) xenial; urgency=medium

  * Offer removal of unused autoremovable kernel packages
(LP: #1624644, #1675079)
  * Support package removals in install backends and really remove packages
(LP: #1624644, #1675079)
  * Keep PEP 8 checks happy
  * Place .keep files in empty directories to keep them when converting the
repo to git (LP: #1758963)

 -- Balint Reczey   Sun, 25 Mar 2018 20:10:49 +0100

** Changed in: update-manager (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Released
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades, the fix comes in an update of u-u) Run
  unattended-upgrades manually and observe the removal of the
  autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Launchpad Bug Tracker]

This bug was fixed in the package update-manager - 1:17.10.14

---
update-manager (1:17.10.14) artful; urgency=medium

  * Offer removal of unused autoremovable kernel packages
(LP: #1624644, #1675079)
  * Support package removals in install backends and really remove packages
(LP: #1624644, #1675079)
  * Keep PEP 8 checks happy
  * Place .keep files in empty directories to keep them when converting the
repo to git (LP: #1758963)

 -- Balint Reczey   Sun, 25 Mar 2018 19:57:57 +0100

** Changed in: update-manager (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Released
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades, the fix comes in an update of u-u) Run
  unattended-upgrades manually and observe the removal of the
  autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)

[Touch-packages] [Bug 1624644] Update Released

[Brian Murray]

The verification of the Stable Release Update for update-manager has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Released
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades, the fix comes in an update of u-u) Run
  unattended-upgrades manually and observe the removal of the
  autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage 

[Touch-packages] [Bug 1771502] [NEW] package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: package libapparmor1:amd64 is already installed and configured

[Rachel Turkal]

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

Public bug reported:

?

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libapparmor1:amd64 2.12-4ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
AptdaemonVersion: 1.1.1+bzr982-0ubuntu19
Architecture: amd64
Date: Tue May 15 22:12:41 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DuplicateSignature:
 package:libapparmor1:amd64:2.12-4ubuntu5
 Unpacking mawk (1.3.3-17ubuntu3) over (1.3.3-17ubuntu2) ...
 dpkg: error processing package libapparmor1:amd64 (--configure):
  package libapparmor1:amd64 is already installed and configured
ErrorMessage: package libapparmor1:amd64 is already installed and configured
InstallationDate: Installed on 2016-10-29 (563 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7a0d2ab0-335f-4dce-89ba-6dbcb74afe85 ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: apparmor
Syslog:
 May 15 21:56:35 awesome-sauce dbus[934]: [system] AppArmor D-Bus mediation is 
enabled
 May 15 22:43:10 awesome-sauce dbus-daemon[935]: [system] AppArmor D-Bus 
mediation is enabled
 May 15 22:43:10 awesome-sauce dbus-daemon[1306]: [session uid=126 pid=1306] 
AppArmor D-Bus mediation is enabled
 May 15 22:43:26 awesome-sauce dbus-daemon[2163]: [session uid=1001 pid=2163] 
AppArmor D-Bus mediation is enabled
Title: package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: 
package libapparmor1:amd64 is already installed and configured
UpgradeStatus: Upgraded to bionic on 2018-05-16 (0 days ago)

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


** Tags: already-installed amd64 apport-package bionic

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

Title:
  package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade:
  package libapparmor1:amd64 is already installed and configured

Status in apparmor package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libapparmor1:amd64 2.12-4ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu19
  Architecture: amd64
  Date: Tue May 15 22:12:41 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DuplicateSignature:
   package:libapparmor1:amd64:2.12-4ubuntu5
   Unpacking mawk (1.3.3-17ubuntu3) over (1.3.3-17ubuntu2) ...
   dpkg: error processing package libapparmor1:amd64 (--configure):
package libapparmor1:amd64 is already installed and configured
  ErrorMessage: package libapparmor1:amd64 is already installed and configured
  InstallationDate: Installed on 2016-10-29 (563 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7a0d2ab0-335f-4dce-89ba-6dbcb74afe85 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: apparmor
  Syslog:
   May 15 21:56:35 awesome-sauce dbus[934]: [system] AppArmor D-Bus mediation 
is enabled
   May 15 22:43:10 awesome-sauce dbus-daemon[935]: [system] AppArmor D-Bus 
mediation is enabled
   May 15 22:43:10 awesome-sauce dbus-daemon[1306]: [session uid=126 pid=1306] 
AppArmor D-Bus mediation is enabled
   May 15 22:43:26 awesome-sauce dbus-daemon[2163]: [session uid=1001 pid=2163] 
AppArmor D-Bus mediation is enabled
  Title: package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: 
package libapparmor1:amd64 is already installed and configured
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (0 days ago)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1771502] Re: package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: package libapparmor1:amd64 is already installed and configured

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1771501
   package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: package 
libapparmor1:amd64 is already installed and configured

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

Title:
  package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade:
  package libapparmor1:amd64 is already installed and configured

Status in apparmor package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libapparmor1:amd64 2.12-4ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu19
  Architecture: amd64
  Date: Tue May 15 22:12:41 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DuplicateSignature:
   package:libapparmor1:amd64:2.12-4ubuntu5
   Unpacking mawk (1.3.3-17ubuntu3) over (1.3.3-17ubuntu2) ...
   dpkg: error processing package libapparmor1:amd64 (--configure):
package libapparmor1:amd64 is already installed and configured
  ErrorMessage: package libapparmor1:amd64 is already installed and configured
  InstallationDate: Installed on 2016-10-29 (563 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7a0d2ab0-335f-4dce-89ba-6dbcb74afe85 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: apparmor
  Syslog:
   May 15 21:56:35 awesome-sauce dbus[934]: [system] AppArmor D-Bus mediation 
is enabled
   May 15 22:43:10 awesome-sauce dbus-daemon[935]: [system] AppArmor D-Bus 
mediation is enabled
   May 15 22:43:10 awesome-sauce dbus-daemon[1306]: [session uid=126 pid=1306] 
AppArmor D-Bus mediation is enabled
   May 15 22:43:26 awesome-sauce dbus-daemon[2163]: [session uid=1001 pid=2163] 
AppArmor D-Bus mediation is enabled
  Title: package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: 
package libapparmor1:amd64 is already installed and configured
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (0 days ago)

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

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

[Touch-packages] [Bug 1769977] Re: jackd2 don't install in fresh installation of Ubuntu 18.04 LTS

[Esteban]

Ok.. My mistake... It's happened because isn't a fresh install.. jackd
install fail after add kxstudio repository. Where is the matter.

Thanks and sorry for the noise! :)

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

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

Title:
  jackd2 don't install in fresh installation of Ubuntu 18.04 LTS

Status in jackd2 package in Ubuntu:
  Invalid

Bug description:
  jackd2 package don't install in Ubuntu 18.04 LTS.

  Broken dependencies, libreadline6 can't be installed anymore.

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

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

[Touch-packages] [Bug 1771713] [NEW] Network Manager doesn't lits created connection in 18.04.

[Jo]

Public bug reported:

Tried Ubuntu, Xubuntu, Ubuntu Budgie? Ubuntu Mate, Lubuntu. 
But doesn't affect Kubuntu.
I tired to create DSL/pppoe connection.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu May 17 05:59:14 2018
InstallationDate: Installed on 2018-05-16 (0 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
 default dev ppp0 scope link 
 10.94.255.190 dev ppp0 proto kernel scope link src 46.0.29.255
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME  UUID  TYPE   TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH 
  ACTIVE  DEVICE  STATE  ACTIVE-PATH  SLAVE 
 DSL connection 1  fdbddcec-2e10-40c1-b6f7-ce93c7dc605a  pppoe  1526515179  Чт 
17 мая 2018 03:59:39  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
--
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
 wlp6s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/4  --   
   ----   
 enp7s0  ethernet  unmanaged/org/freedesktop/NetworkManager/Devices/2  --   
   ----   
 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  --   
   ----   
 ppp0ppp   unmanaged/org/freedesktop/NetworkManager/Devices/3  --   
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.10.6   connected  started  unknown   enabled enabled  
disabled  enabled  enabled

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

Title:
  Network Manager doesn't lits created connection in 18.04.

Status in network-manager package in Ubuntu:
  New

Bug description:
  Tried Ubuntu, Xubuntu, Ubuntu Budgie? Ubuntu Mate, Lubuntu. 
  But doesn't affect Kubuntu.
  I tired to create DSL/pppoe connection.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May 17 05:59:14 2018
  InstallationDate: Installed on 2018-05-16 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default dev ppp0 scope link 
   10.94.255.190 dev ppp0 proto kernel scope link src 46.0.29.255
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE   TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH 
  ACTIVE  DEVICE  STATE  ACTIVE-PATH  SLAVE 
   DSL connection 1  fdbddcec-2e10-40c1-b6f7-ce93c7dc605a  pppoe  1526515179  
Чт 17 мая 2018 03:59:39  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
--
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   wlp6s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/4  -- 
 ----   
   enp7s0  ethernet  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
   ppp0ppp   unmanaged/org/freedesktop/NetworkManager/Devices/3  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  unknown   enabled enabled  
disabled  enabled  enabled

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

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

[Touch-packages] [Bug 1755326] Re: Periodic glitch in sound with Firewire and snd-dice

[Takashi Sakamoto]

Please refer to my report in upstream:
http://mailman.alsa-project.org/pipermail/alsa-devel/2016-May/107715.html

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

Title:
  Periodic glitch in sound with Firewire and snd-dice

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

Bug description:
  I have a fresh installation of Ubuntu 17.10 with almost nothing extra
  installed yet besides Bitwig Studio, Cadence and a few other things
  from the KX Studio repositories.

  But I also tried the bug after a fresh install with nothing else than
  Bitwig Studio installed, it's the same.

  Not sure if this information can be added afterwards: but I installed
  the  3.19.8 low latency kernel, and the problem disappeared. On 17.1 I
  can't use the current low latency kernel because the system becomes
  very unresponsive to the point of being hard to even log in. So I'm
  not sure if this is just a matter of difference between the low
  latency and regular kernels.

  I have a TC Electronics Impact Twin Firewire audio interface.
  It is connected to a Iocrest SY-PEX30016 PCI-E card, which has a Texas 
Instruments XIO2213BZAY chipset.

  The ALSA snd-dice drivers work, but with glitches.

  There is a periodic, glitch in the sound that sounds like a part of the 
stream is missing, or something. It is steady in timing, nothing seems to have 
an effect on it.
  Recording seems to work. All outputs and inputs, also the ADAT outputs seem 
to work, altough I could not test if the ADAT outputs feature the glitch too.

  Seemingly randomly there might be a short maybe around 0.3 second
  total break in the sound.

  I'm not getting xruns at all.

  I tried also Ubuntu Studio live USB, it has the exact same glitch. I
  also tried a Native Instruments Audio2DJ USB interface, with that
  there is no problem with the sound on my computer.

  I tried also with Carla and ZynAddSubFx, and also with the live USB of
  Linux Mint (current version), and the same glitch is present.

  I tried also another Firewire controller card with a XIO2200A Texas
  Instruments chip, it features the same glitch, but running a different
  speed.

  I had a KX Studio 14.x installation a few years ago, where the
  interface was working without a hitch. But then I was running with
  FFADO.

  So to me it seems that the kernel integration of snd-dice has some
  problem with timing with a TC Electronics interface?

  I could not get FFADO to run with Jack now so I can't say if the FFADO
  implementation would work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC4D0c:   kim3563 F...m jackdbus
   /dev/snd/pcmC4D0p:   kim3563 F...m jackdbus
   /dev/snd/controlC4:  kim3563 F jackdbus
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 13 02:11:51 2018
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/hwC3D0', '/dev/snd/midiC3D0', '/dev/snd/pcmC3D0c', 
'/dev/snd/pcmC3D0p', '/dev/snd/controlC3', '/dev/snd/by-path', 
'/dev/snd/by-id', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/midiC2D0', 
'/dev/snd/controlC2', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: 

[Touch-packages] [Bug 1755326] Re: Periodic glitch in sound with Firewire and snd-dice

[Takashi Sakamoto]

Please refer to my report in upstream:
http://mailman.alsa-project.org/pipermail/alsa-devel/2016-May/107715.html

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

Title:
  Periodic glitch in sound with Firewire and snd-dice

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

Bug description:
  I have a fresh installation of Ubuntu 17.10 with almost nothing extra
  installed yet besides Bitwig Studio, Cadence and a few other things
  from the KX Studio repositories.

  But I also tried the bug after a fresh install with nothing else than
  Bitwig Studio installed, it's the same.

  Not sure if this information can be added afterwards: but I installed
  the  3.19.8 low latency kernel, and the problem disappeared. On 17.1 I
  can't use the current low latency kernel because the system becomes
  very unresponsive to the point of being hard to even log in. So I'm
  not sure if this is just a matter of difference between the low
  latency and regular kernels.

  I have a TC Electronics Impact Twin Firewire audio interface.
  It is connected to a Iocrest SY-PEX30016 PCI-E card, which has a Texas 
Instruments XIO2213BZAY chipset.

  The ALSA snd-dice drivers work, but with glitches.

  There is a periodic, glitch in the sound that sounds like a part of the 
stream is missing, or something. It is steady in timing, nothing seems to have 
an effect on it.
  Recording seems to work. All outputs and inputs, also the ADAT outputs seem 
to work, altough I could not test if the ADAT outputs feature the glitch too.

  Seemingly randomly there might be a short maybe around 0.3 second
  total break in the sound.

  I'm not getting xruns at all.

  I tried also Ubuntu Studio live USB, it has the exact same glitch. I
  also tried a Native Instruments Audio2DJ USB interface, with that
  there is no problem with the sound on my computer.

  I tried also with Carla and ZynAddSubFx, and also with the live USB of
  Linux Mint (current version), and the same glitch is present.

  I tried also another Firewire controller card with a XIO2200A Texas
  Instruments chip, it features the same glitch, but running a different
  speed.

  I had a KX Studio 14.x installation a few years ago, where the
  interface was working without a hitch. But then I was running with
  FFADO.

  So to me it seems that the kernel integration of snd-dice has some
  problem with timing with a TC Electronics interface?

  I could not get FFADO to run with Jack now so I can't say if the FFADO
  implementation would work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC4D0c:   kim3563 F...m jackdbus
   /dev/snd/pcmC4D0p:   kim3563 F...m jackdbus
   /dev/snd/controlC4:  kim3563 F jackdbus
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 13 02:11:51 2018
  InstallationDate: Installed on 2018-03-12 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/hwC3D0', '/dev/snd/midiC3D0', '/dev/snd/pcmC3D0c', 
'/dev/snd/pcmC3D0p', '/dev/snd/controlC3', '/dev/snd/by-path', 
'/dev/snd/by-id', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/midiC2D0', 
'/dev/snd/controlC2', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: 

[Touch-packages] [Bug 1765611] Re: package keyboard-configuration 1.178ubuntu2 failed to install/upgrade when user cancels selection of switch key combination

[Launchpad Bug Tracker]

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

** Changed in: console-setup (Ubuntu)
   Status: New => Confirmed

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

Title:
  package keyboard-configuration 1.178ubuntu2 failed to install/upgrade
  when user cancels selection of switch key combination

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I have layout switch combination set to both shift toggles (not via gnome 
configuration).
  During upgrade I could not find such combination. Therefore I choose cancel 
in combination selection window.
  This result in crash during upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: keyboard-configuration 1.178ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Fri Apr 20 08:18:54 2018
  ErrorMessage: installed keyboard-configuration package post-installation 
script subprocess returned error exit status 10
  InstallationDate: Installed on 2018-04-11 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Keyboard:
   XKBLAYOUT=us,lt
   XKBVARIANT=,
   BACKSPACE=guess
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.178ubuntu2 failed to install/upgrade: 
installed keyboard-configuration package post-installation script subprocess 
returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1771689] [NEW] initramfs resets usb 3 bus while booting from usb 3 drive

[Damion Milne]

Public bug reported:

I boot ubuntu from a usb 3.0 thumb drive.
But during boot, booting stops at a busybox prompt.
Output of dmesg | tail says:
  22.888260 usb 4-2: reset SuperSpeed USB device number 2 using xhci-hcd

My work-around is to: unplug the usb 3.0 drive, plug it back in, then type exit.
After that, ubuntu boot normally.

Busybox version, stated at busybox prompt, is:
  v1.27.2

1) $ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04

2) $ dpkg-query -l busybox-initramfs
ii  busybox-initra 1:1.27.2-2ub amd64Standalone shell setup for initra

3) I expect ubuntu to boot from the usb 3.0 drive, without having to use
my work-around described above. It used to work fine on older versions
of ubuntu.

4) Instead booting stops at a busybox prompt as described above.

Here is my PC's model of USB 3.0 adapter:
$ sudo lspci | fgrep -i 'usb 3'
02:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host 
Controller (rev 02)

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: busybox-initramfs 1:1.27.2-2ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed May 16 23:48:22 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
InstallationDate: Installed on 2017-06-28 (322 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: busybox
UpgradeStatus: Upgraded to bionic on 2018-05-09 (6 days ago)

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

Title:
  initramfs resets usb 3 bus while booting from usb 3 drive

Status in busybox package in Ubuntu:
  New

Bug description:
  I boot ubuntu from a usb 3.0 thumb drive.
  But during boot, booting stops at a busybox prompt.
  Output of dmesg | tail says:
22.888260 usb 4-2: reset SuperSpeed USB device number 2 using xhci-hcd

  My work-around is to: unplug the usb 3.0 drive, plug it back in, then type 
exit.
  After that, ubuntu boot normally.

  Busybox version, stated at busybox prompt, is:
v1.27.2

  1) $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  2) $ dpkg-query -l busybox-initramfs
  ii  busybox-initra 1:1.27.2-2ub amd64Standalone shell setup for initra

  3) I expect ubuntu to boot from the usb 3.0 drive, without having to
  use my work-around described above. It used to work fine on older
  versions of ubuntu.

  4) Instead booting stops at a busybox prompt as described above.

  Here is my PC's model of USB 3.0 adapter:
  $ sudo lspci | fgrep -i 'usb 3'
  02:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI 
Host Controller (rev 02)

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: busybox-initramfs 1:1.27.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 16 23:48:22 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  InstallationDate: Installed on 2017-06-28 (322 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: busybox
  UpgradeStatus: Upgraded to bionic on 2018-05-09 (6 days ago)

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

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

[Touch-packages] [Bug 1745664] Re: systemd-logind crashed with SIGABRT in __libc_connect()

[Launchpad Bug Tracker]

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

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

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

Title:
  systemd-logind crashed with SIGABRT in __libc_connect()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  configured system to use nis.  seems to be crashing when I attempt to
  use a NIS user account

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Fri Jan 26 13:45:06 2018
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2018-01-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. Z370 HD3
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at 
../sysdeps/unix/sysv/linux/connect.c:26
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, 
sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153
   __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, 
version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106
   __GI_pmap_getport (address=address@entry=0x7ffc27302060, 
program=program@entry=17, version=version@entry=2, 
protocol=protocol@entry=6) at pm_getport.c:154
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, 
sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: systemd-logind crashed with SIGABRT in __libc_connect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys 
sysdesign tty uucp
  dmi.bios.date: 09/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 HD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 HD3
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)

[Andreas Hasenack]

** Description changed:

  [Impact]
+ Concurrent SASL authentications could trigger a segfault. This was observed 
by the bug reporter during replication from a master to a slave, and can be 
reproduced with a test program.
  
-  * An explanation of the effects of the bug on users and
- 
-  * justification for backporting the fix to the stable release.
- 
-  * In addition, it is helpful, but not required, to include an
-explanation of how the upload fixes this bug.
+ The fix is applied upstream, see comment #13.
  
  [Test Case]
+ * Create a fresh xenial VM or container and login. Update the apt 
repositories:
+ sudo apt update
  
-  * detailed instructions how to reproduce the bug
+ * Create a local directory and cd into it:
+ mkdir test && cd test
  
-  * these should allow someone who is not familiar with the affected
-package to reproduce the bug and verify that the updated package fixes
-the problem.
+ * Download the test attachments from this bug: Makefile, sasltest.c and 
testscript:
+ wget 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139678/+files/Makefile
 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139679/+files/sasltest.c
 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139680/+files/testscript
+ 
+ * Execute the testscript with sudo once. It shall fail at the very end with a 
core dump:
+ sudo sh ./testscript
+ (...)
+ sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
+ Aborted (core dumped)
+ 
+ * Export this var:
+ export LDAPSASL_SECPROPS=none
+ 
+ 
+ * Run the actual test script a few more times to confirm the crasH:
+ $ ./sasltest 
+ rc = -6 (Unknown authentication method)
+ sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
+ rc = -6 (Unknown authentication method)
+ sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
+ rc = -6 (Unknown authentication method)
+ sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
+ Aborted (core dumped)
+ 
+ * Install the updated packages from proposed
+ 
+ * Run ./sasltest again. Make sure the LDAPSASL_SECPROPS var is still exported:
+ $ echo $LDAPSASL_SECPROPS 
+ none
+ 
+ $ ./sasltest
+ $
+ 
+ This time the test completes without crashing.
+ 
  
  [Regression Potential]
  
-  * discussion of how regressions are most likely to manifest as a result
+  * discussion of how regressions are most likely to manifest as a result
  of this change.
  
-  * It is assumed that any SRU candidate patch is well-tested before
-upload and has a low overall risk of regression, but it's important
-to make the effort to think about what ''could'' happen in the
-event of a regression.
+  * It is assumed that any SRU candidate patch is well-tested before
+    upload and has a low overall risk of regression, but it's important
+    to make the effort to think about what ''could'' happen in the
+    event of a regression.
  
-  * This both shows the SRU team that the risks have been considered,
-and provides guidance to testers in regression-testing the SRU.
+  * This both shows the SRU team that the risks have been considered,
+    and provides guidance to testers in regression-testing the SRU.
  
  [Other Info]
-  
-  * Anything else you think is useful to include
-  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
-  * and address these questions in advance
  
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
+  * and address these questions in advance
  
  [Original description]
  
  I have a slapd problem on a freshly installed 16.04 machine:
  
  slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080
  error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000]
  
  I'm using the server as Slave LDAP-Server and sync replication with kerberos 
authentication.
  The service either starts and runs successfully or it fails with segmentation 
fault or 100% CPU.
  Maybe an useful info, I'm replicating two databases. When I deactivate 
syncrepl for one of them (doesn't matter which one) the problem is not occuring.
  
  Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  slapd 2.4.42+dfsg-2ubuntu3.1
  libsasl2-2:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1
  
  GDB debug:
  
  Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u 
openldap -g openldap -f /etc/ldap/slapd.conf -d 256
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  590c82ab @(#) $OpenLDAP: slapd  (Ubuntu) (May 11 2016 16:12:05) $
   

[Touch-packages] [Bug 1771669] Re: package mime-support 3.60ubuntu1 failed to install/upgrade: installed mime-support package post-installation script subprocess returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package mime-support 3.60ubuntu1 failed to install/upgrade: installed
  mime-support package post-installation script subprocess returned
  error exit status 1

Status in mime-support package in Ubuntu:
  New

Bug description:
  No other information available.  This seems to be an automatic
  upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: mime-support 3.60ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 13 21:38:25 2018
  DuplicateSignature:
   package:mime-support:3.60ubuntu1
   Processing triggers for mime-support (3.60ubuntu1) ...
   Error: could not write '/etc/mailcap.new' -- Read-only file system
   dpkg: error processing package mime-support (--configure):
installed mime-support package post-installation script subprocess returned 
error exit status 1
  ErrorMessage: installed mime-support package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-05-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: mime-support
  Title: package mime-support 3.60ubuntu1 failed to install/upgrade: installed 
mime-support package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1771669] [NEW] package mime-support 3.60ubuntu1 failed to install/upgrade: installed mime-support package post-installation script subprocess returned error exit status 1

[Ian Penman]

Public bug reported:

No other information available.  This seems to be an automatic upgrade.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: mime-support 3.60ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Sun May 13 21:38:25 2018
DuplicateSignature:
 package:mime-support:3.60ubuntu1
 Processing triggers for mime-support (3.60ubuntu1) ...
 Error: could not write '/etc/mailcap.new' -- Read-only file system
 dpkg: error processing package mime-support (--configure):
  installed mime-support package post-installation script subprocess returned 
error exit status 1
ErrorMessage: installed mime-support package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-05-12 (3 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: mime-support
Title: package mime-support 3.60ubuntu1 failed to install/upgrade: installed 
mime-support package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package mime-support 3.60ubuntu1 failed to install/upgrade: installed
  mime-support package post-installation script subprocess returned
  error exit status 1

Status in mime-support package in Ubuntu:
  New

Bug description:
  No other information available.  This seems to be an automatic
  upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: mime-support 3.60ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 13 21:38:25 2018
  DuplicateSignature:
   package:mime-support:3.60ubuntu1
   Processing triggers for mime-support (3.60ubuntu1) ...
   Error: could not write '/etc/mailcap.new' -- Read-only file system
   dpkg: error processing package mime-support (--configure):
installed mime-support package post-installation script subprocess returned 
error exit status 1
  ErrorMessage: installed mime-support package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-05-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: mime-support
  Title: package mime-support 3.60ubuntu1 failed to install/upgrade: installed 
mime-support package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1771557] Re: NVMe boot drives not supported - failing in generating initramfs

[Eric Desrochers]

** Description changed:

  [Impact]
  
  When creating the initramfs image, mkinitramfs has multiple options on
  how to include modules. The default (and most common) one is the
  "MODULES=most", which includes the majority of filesystem modules and
  all the block device drivers. One other option is "MODULES=dep", which
  tries to descend in the sysfs hierarchy and guess modules to add, with
  the goal of reduce the size of initramfs.
  
  For the MODULES=dep case, the initramfs-tools hook-functions script
  cannot translate nvmeXnYpZ to nvmeXnY block device, so it's failing in
  the sysfs lookup, so it does not build the initram disk.
  
  Upstream solution is composed of at least 2 patches (it's a series, but
  the 2 below are really the needed ones):
  
  commit 3cb744c9
  Author: Ben Hutchings 
  hook-functions: Rewrite block device sysfs lookup to be generic
  
  commit 8ac52dc0
  Author: Ben Hutchings 
  hook-functions: Include modules for all components of a multi-disk device
  
  Instead of doing the huge backport, we added another sed substitution: 
currently the script has substitutions for sdX and hdX, in order to convert 
sda1 to sda, for example. The new substitution converts nvmeXnYpZ to nvmeXnY.
  It's less intrusive than the full backport, since this is a minimal SRU to 
Trusty only.
  
- 
  [Test Case]
  1. Install Trusty with rootfs in a multi-disk(md) array composed of two nvme 
partitions - in my tests, I've used a RAID1.
  
  (lsblk output of my test env:
  
- nvme0n1 259:0010G  0 disk  
- └─nvme0n1p1 259:1010G  0 part  
-   └─md0   9:0010G  0 raid1 /
- nvme1n1 259:2010G  0 disk  
- └─nvme1n1p1 259:3010G  0 part  
-   └─md0   9:0010G  0 raid1 /
+ nvme0n1 259:0010G  0 disk
+ └─nvme0n1p1 259:1010G  0 part
+   └─md0   9:0010G  0 raid1 /
+ nvme1n1 259:2010G  0 disk
+ └─nvme1n1p1 259:3010G  0 part
+   └─md0   9:0010G  0 raid1 /
  )
  
- 
- 2. Once system is booted, modify the "/etc/initramfs-tools/initramfs.conf", 
replacing "MODULES=most" to "MODULES=dep".
+ 2. Once system is booted, modify the "/etc/initramfs-
+ tools/initramfs.conf", replacing "MODULES=most" to "MODULES=dep".
  
  3. Update your initramfs by running something like:
  "update-initramfs -u -k "
  
  The initramfs creating procedure will fail, unless the patch from this
  LP is present.
  
- 
  [Regression Potential]
  If the sed expression was somewhat broken, we could have an issue generating 
initiramfs when MODULES is set to "dep", even for generic block devices (like 
regular HDDs).
  
+ [Other Info]
+ * This issue is based on Debian bug #785147: 
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147
  
- [Other Info]
- This issue is based on Debian bug #785147: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147
+ * Only Trusty is affected, Xenial and late contains the full fix as
+ mentioned above :
+ 
+ $ git describe --contains  8ac52dc0
+ v0.121_rc1~11
+ 
+ $ git describe --contains 3cb744c9
+ v0.121_rc1~11
+ 
+ $ rmadison initramfs-tools
+ 
+  initramfs-tools | 0.103ubuntu4| trusty   | source, all
+  ==> initramfs-tools | 0.103ubuntu4.10 | trusty-updates   | source, all
+  initramfs-tools | 0.122ubuntu8| xenial   | source, all
+  initramfs-tools | 0.122ubuntu8.11 | xenial-updates   | source, all
+  initramfs-tools | 0.125ubuntu12   | artful   | source, all
+  initramfs-tools | 0.125ubuntu12.1 | artful-updates   | source, all
+  initramfs-tools | 0.130ubuntu3| bionic   | source, all
+  initramfs-tools | 0.130ubuntu6| cosmic   | source, all

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

Title:
  NVMe boot drives not supported - failing in generating initramfs

Status in initramfs-tools:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  When creating the initramfs image, mkinitramfs has multiple options on
  how to include modules. The default (and most common) one is the
  "MODULES=most", which includes the majority of filesystem modules and
  all the block device drivers. One other option is "MODULES=dep", which
  tries to descend in the sysfs hierarchy and guess modules to add, with
  the goal of reduce the size of initramfs.

  For the MODULES=dep case, the initramfs-tools hook-functions script
  cannot translate nvmeXnYpZ to nvmeXnY block device, so it's failing in
  the sysfs lookup, so it does not build the initram disk.

  Upstream solution is composed of at least 2 patches (it's a series,
  but the 2 below are really the needed ones):

  commit 

[Touch-packages] [Bug 1771557] Re: NVMe boot drives not supported - failing in generating initramfs

[Eric Desrochers]

Uploaded in Trusty upload queue. It is now waiting on SRU verification
team approval to start building in trusty-proposed.

# Sponsoring note

[Nitpick]
- Add (LP: #1771557) in debian/changelog

[Note]
* The sed command seems pretty solid. The "*" is indeed a good idea, even if 
IMHO unlikely to exceed 2 digits if it happen the cmd will match any number 
that precedes "n", "p" and the end, even if exceeding 2 digits.
* I don't have an NVMe drive handy, but I know gpicolli did all the necessary 
validation pre-SRU.

[Manual verification]

Testing different nvme drive naming scenarios:

$ echo "nvme1n2p3" | sed 's/\(nvme[0-9][0-9]*n[0-9][0-9]*\)p[0-9]*/\1/g'
nvme1n2

$ echo "nvme11n22p33" | sed 's/\(nvme[0-9][0-9]*n[0-9][0-9]*\)p[0-9]*/\1/g'
nvme11n22

$ echo "nvme11n22p33" | sed 's/\(nvme[0-9][0-9]*n[0-9][0-9]*\)p[0-9]*/\1/g'
nvme11n22

$ echo "nvme111n222p333" | sed 's/\(nvme[0-9][0-9]*n[0-9][0-9]*\)p[0-9]*/\1/g'
nvme111n222

$ echo "nvmenp" | sed 
's/\(nvme[0-9][0-9]*n[0-9][0-9]*\)p[0-9]*/\1/g'
nvmen

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

Title:
  NVMe boot drives not supported - failing in generating initramfs

Status in initramfs-tools:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  When creating the initramfs image, mkinitramfs has multiple options on
  how to include modules. The default (and most common) one is the
  "MODULES=most", which includes the majority of filesystem modules and
  all the block device drivers. One other option is "MODULES=dep", which
  tries to descend in the sysfs hierarchy and guess modules to add, with
  the goal of reduce the size of initramfs.

  For the MODULES=dep case, the initramfs-tools hook-functions script
  cannot translate nvmeXnYpZ to nvmeXnY block device, so it's failing in
  the sysfs lookup, so it does not build the initram disk.

  Upstream solution is composed of at least 2 patches (it's a series,
  but the 2 below are really the needed ones):

  commit 3cb744c9
  Author: Ben Hutchings 
  hook-functions: Rewrite block device sysfs lookup to be generic

  commit 8ac52dc0
  Author: Ben Hutchings 
  hook-functions: Include modules for all components of a multi-disk device

  Instead of doing the huge backport, we added another sed substitution: 
currently the script has substitutions for sdX and hdX, in order to convert 
sda1 to sda, for example. The new substitution converts nvmeXnYpZ to nvmeXnY.
  It's less intrusive than the full backport, since this is a minimal SRU to 
Trusty only.

  [Test Case]
  1. Install Trusty with rootfs in a multi-disk(md) array composed of two nvme 
partitions - in my tests, I've used a RAID1.

  (lsblk output of my test env:

  nvme0n1 259:0010G  0 disk
  └─nvme0n1p1 259:1010G  0 part
    └─md0   9:0010G  0 raid1 /
  nvme1n1 259:2010G  0 disk
  └─nvme1n1p1 259:3010G  0 part
    └─md0   9:0010G  0 raid1 /
  )

  2. Once system is booted, modify the "/etc/initramfs-
  tools/initramfs.conf", replacing "MODULES=most" to "MODULES=dep".

  3. Update your initramfs by running something like:
  "update-initramfs -u -k "

  The initramfs creating procedure will fail, unless the patch from this
  LP is present.

  [Regression Potential]
  If the sed expression was somewhat broken, we could have an issue generating 
initiramfs when MODULES is set to "dep", even for generic block devices (like 
regular HDDs).

  [Other Info]
  * This issue is based on Debian bug #785147: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147

  * Only Trusty is affected, Xenial and late contains the full fix as
  mentioned above :

  $ git describe --contains  8ac52dc0
  v0.121_rc1~11

  $ git describe --contains 3cb744c9
  v0.121_rc1~11

  $ rmadison initramfs-tools

   initramfs-tools | 0.103ubuntu4| trusty   | source, all
   ==> initramfs-tools | 0.103ubuntu4.10 | trusty-updates   | source, all
   initramfs-tools | 0.122ubuntu8| xenial   | source, all
   initramfs-tools | 0.122ubuntu8.11 | xenial-updates   | source, all
   initramfs-tools | 0.125ubuntu12   | artful   | source, all
   initramfs-tools | 0.125ubuntu12.1 | artful-updates   | source, all
   initramfs-tools | 0.130ubuntu3| bionic   | source, all
   initramfs-tools | 0.130ubuntu6| cosmic   | source, all

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

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

[Touch-packages] [Bug 1771653] [NEW] package libperl5.26 5.26.1-6 failed to install/upgrade: zkouším přepsat sdílený „/usr/share/doc/libperl5.26/changelog.Debian.gz“, který se liší od ostatních instan

[petr tengler]

Public bug reported:

1

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libperl5.26 5.26.1-6
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 16 20:59:58 2018
ErrorMessage: zkouším přepsat sdílený 
„/usr/share/doc/libperl5.26/changelog.Debian.gz“, který se liší od ostatních 
instancí balíku libperl5.26:i386
InstallationDate: Installed on 2018-05-16 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: perl
Title: package libperl5.26 5.26.1-6 failed to install/upgrade: zkouším přepsat 
sdílený „/usr/share/doc/libperl5.26/changelog.Debian.gz“, který se liší od 
ostatních instancí balíku libperl5.26:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libperl5.26 5.26.1-6 failed to install/upgrade: zkouším
  přepsat sdílený „/usr/share/doc/libperl5.26/changelog.Debian.gz“,
  který se liší od ostatních instancí balíku libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libperl5.26 5.26.1-6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 16 20:59:58 2018
  ErrorMessage: zkouším přepsat sdílený 
„/usr/share/doc/libperl5.26/changelog.Debian.gz“, který se liší od ostatních 
instancí balíku libperl5.26:i386
  InstallationDate: Installed on 2018-05-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: perl
  Title: package libperl5.26 5.26.1-6 failed to install/upgrade: zkouším 
přepsat sdílený „/usr/share/doc/libperl5.26/changelog.Debian.gz“, který se liší 
od ostatních instancí balíku libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)

[Andreas Hasenack]

** Description changed:

+ [Impact]
+ 
+  * An explanation of the effects of the bug on users and
+ 
+  * justification for backporting the fix to the stable release.
+ 
+  * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+ 
+ [Test Case]
+ 
+  * detailed instructions how to reproduce the bug
+ 
+  * these should allow someone who is not familiar with the affected
+package to reproduce the bug and verify that the updated package fixes
+the problem.
+ 
+ [Regression Potential]
+ 
+  * discussion of how regressions are most likely to manifest as a result
+ of this change.
+ 
+  * It is assumed that any SRU candidate patch is well-tested before
+upload and has a low overall risk of regression, but it's important
+to make the effort to think about what ''could'' happen in the
+event of a regression.
+ 
+  * This both shows the SRU team that the risks have been considered,
+and provides guidance to testers in regression-testing the SRU.
+ 
+ [Other Info]
+  
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
+  * and address these questions in advance
+ 
+ 
+ [Original description]
+ 
  I have a slapd problem on a freshly installed 16.04 machine:
  
  slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080
  error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000]
  
  I'm using the server as Slave LDAP-Server and sync replication with kerberos 
authentication.
  The service either starts and runs successfully or it fails with segmentation 
fault or 100% CPU.
- Maybe an useful info, I'm replicating two databases. When I deactivate 
syncrepl for one of them (doesn't matter which one) the problem is not 
occuring. 
+ Maybe an useful info, I'm replicating two databases. When I deactivate 
syncrepl for one of them (doesn't matter which one) the problem is not occuring.
  
  Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  slapd 2.4.42+dfsg-2ubuntu3.1
  libsasl2-2:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1
  
  GDB debug:
  
  Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u 
openldap -g openldap -f /etc/ldap/slapd.conf -d 256
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  590c82ab @(#) $OpenLDAP: slapd  (Ubuntu) (May 11 2016 16:12:05) $
-   
buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd
+  
buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd
  590c82ab slapd starting
  [New Thread 0x7f2e96b7b700 (LWP 42139)]
  [New Thread 0x7f2e9637a700 (LWP 42140)]
  [New Thread 0x7f2e95b79700 (LWP 42141)]
  [New Thread 0x7f2e95378700 (LWP 42142)]
  [New Thread 0x7f2e94b77700 (LWP 42143)]
  590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s 
failed (-6)
  590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left)
  
  Thread 4 "slapd" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7f2e95b79700 (LWP 42141)]
  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
- 
  
  (gdb) thr apply all bt
  
  Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
  
  Thread 5 (Thread 0x7f2e95378700 (LWP 42142)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x7f2ea59463f3 in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #2  0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at 
pthread_create.c:333
  #3  0x7f2ea45b282d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
  
  Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)):
  #0  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #1  0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #2  0x7f2ea5303d69 in sasl_client_init () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2
  #3  0x7f2ea594da6c in ldap_int_sasl_init () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #4  0x7f2ea594db2c in ldap_int_sasl_open () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #5  0x7f2ea594e2d4 in ldap_int_sasl_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #6  0x7f2ea5951828 in ldap_sasl_interactive_bind () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #7  

[Touch-packages] [Bug 1769056] Re: driverless printing generates wrong language/encoding PPD

[Launchpad Bug Tracker]

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

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

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

Title:
  driverless printing generates wrong language/encoding PPD

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  The printing option dialog (see attached PNG file) is broken with Bionic 
Japanese environment.
  This issue seems to be coming from the generated PPD file with wrong 
language/encoding.

  I tried with Epson EP-879AW.

  Steps to reproduce:

  1) generate a print queue by driverless feature with ja-JP locale:

  $ LANG-ja_JP.UTF-8 lpadmin -p driverlesstest-ja -E -v `driverless` -m
  everywhere

  2) check the generated PPD (attached driverlesstest-ja.ppd)

  $ sudo less /etc/cups/ppd/driverlesstest-ja.ppd

  Expected: PPD have same language/encoding with content (if the content
  have Japanese, language/encoding should be Japanese/UTF-8)

  Actual: PPD has Japanese strings, but language/encoding is
  English/ISOLatin1

  
  
  Attached files:
   
  EPSON_EP_879A_Series_007.png: screenshot of printing option dialog of 
EP-879AW driverless print queue
  driverless-ja.ppd: PPD generated with ja_JP.UTF-8 locale
  driverless-en.ppd: PPD generated with C locale
  ipptool.txt: output of ipptool, by following command:

  $ ipptool -tv `driverless` get-printer-attributes.test > ipptool.txt

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

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

[Touch-packages] [Bug 1771236] Re: forced use of systemd-networkd interferes with ifupdown in 18.04

[Wes]

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

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

Title:
  forced use of systemd-networkd interferes with ifupdown in 18.04

Status in systemd package in Ubuntu:
  New

Bug description:
  For several reasons, we are not able to use netplan nor systemd-
  networkd due to legacy applications that expect ifupdown's pre-up and
  post-up script mechanism.  The documentation around 18.04's
  (premature, I feel) wholesale adoption of netplan claims that one can
  revert to old behaviour by merely installing ifupdown (amongst
  assertions that netplan will never offer a mechanism for configuring
  pre-up and post-up actions even for network managers that support
  them).

  However when ifupdown is installed, systemd-networkd still tries to
  manage interfaces.  If you 'systemctl disable systemd-networkd', upon
  next reboot it is automatically re-enabled.  We tried disabling any
  systemd units even remotely related to networking and yet systemd-
  networkd still runs.  If it hasn't been configured, it tries to DHCP.
  On networks that don't provide DHCP this results in a stupendously
  long stall during boot.  Currently it appears to be impossible to tell
  systemd-networkd not to run in a clean manner that won't get reverted
  on package upgrades.

  I sincerely hope this is is a bug/oversight and not intentional.  We
  need to be able to disable systemd-networkd properly.

  Thanks

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

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