[Touch-packages] [Bug 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.

[Jeff Lane ]

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

Title:
  After updating ubuntu, the network to which the subnet address is
  assigned does not become active in KVM.

Status in dnsmasq package in Ubuntu:
  Confirmed

Bug description:
  phenomenon:
After updating ubuntu, the network to which the subnet address is assigned 
does not become active in KVM.

  Cause:
This is because the following dnsmasq update operation performed by apt's 
automatic update causes an error. It worked properly with dnsmasq 2.80, but 
does not work properly with 2.90.

  $ cat /var/log/apt/history.log
  (snip)
  Start-Date: 2024-02-27  06:17:31
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: dnsmasq-base:amd64 (2.80-1.1ubuntu1.7, 2.90-0ubuntu0.20.04.1)
  End-Date: 2024-02-27  06:17:44
  (snip)
  $

  Cause details:
As a premise, bind-dynamic is set in the dnsmasq config file for KVM. Below 
is an example.

  $ cat default.conf 
  ##WARNING:  THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
  ##OVERWRITTEN AND LOST.  Changes to this configuration should be made using:
  ##virsh net-edit default
  ## or other application using the libvirt API.
  ##
  ## dnsmasq conf file created by libvirt
  strict-order
  user=libvirt-dnsmasq
  pid-file=/run/libvirt/network/default.pid
  except-interface=lo
  bind-dynamic
  interface=virbr0
  dhcp-range=192.168.122.2,192.168.122.254,255.255.255.0
  dhcp-no-override
  dhcp-authoritative
  dhcp-lease-max=253
  dhcp-hostsfile=/var/lib/libvirt/dnsmasq/default.hostsfile
  addn-hosts=/var/lib/libvirt/dnsmasq/default.addnhosts
  $ 

  
  When starting the network with KVM (virsh net-start), dnsmasq started from 
KVM executes the make_sock function twice as shown below.

 $ cat network.c
 (snip)
 1087 static struct listener *create_listeners(union mysockaddr *addr, int 
do_
 1087 tftp, int dienow)
 1088 {
 1089   struct listener *l = NULL;
 1090   int fd = -1, tcpfd = -1, tftpfd = -1;
 1091 
 1092   (void)do_tftp;
 1093 
 1094   if (daemon->port != 0)
 1095 {
 1096   fd = make_sock(addr, SOCK_DGRAM, dienow);
 1097   tcpfd = make_sock(addr, SOCK_STREAM, dienow);
 1098 }
 (snip)

  The following code causes an issue with the update made in dnsmasq
  2.90.

 $ cat network.c
 (snip)
  895 static int make_sock(union mysockaddr *addr, int type, int dienow)
  896 {
  (snip)
  934   if (!option_bool(OPT_CLEVERBIND) || errno != EADDRNOTAVAIL)
  935 {
  936   if (dienow)
  937 die(s, daemon->addrbuff, EC_BADNET);
  938   else
  939 my_syslog(LOG_WARNING, s, daemon->addrbuff, 
strerror(errno))939 ;
  940 }
  (snip)

  
  function "make_sock" in network.c:1096 binds the socket to 192.168.122.1/24, 
and then make_sock in network.c:1097 tries to bind to the same address. 
However, in network.c:934, when errno==98 occurs, network.c:937 is executed, so 
dnsmasq does not cause a startup error. As a result, virsh net-start fails.

  As a temporary workaround, it will work if you try not to die.

  $ diff -u  network_c_back  network.c 
  --- network_c_back  2024-02-29 15:36:05.156467935 +
  +++ network.c 2024-02-29 15:36:38.733324350 +
  @@ -934,7 +934,8 @@
 if (!option_bool(OPT_CLEVERBIND) || errno != EADDRNOTAVAIL)
{
  if (dienow)
  - die(s, daemon->addrbuff, EC_BADNET);
  + my_syslog(LOG_WARNING, s, daemon->addrbuff, strerror(errno));
  + //die(s, daemon->addrbuff, EC_BADNET);
  else
my_syslog(LOG_WARNING, s, daemon->addrbuff, strerror(errno));
}
  $ 

  If bind-dynamic is set, it should be modified so that it works even if
  errno==98.

  For reference, in the case of dnsmasq 2.80, the code is as follows, so
  no error occurs.

  network.c
  699 static int make_sock(union mysockaddr *addr, int type, int dienow)
  700 {
  701   int family = addr->sa.sa_family;
  702   int fd, rc, opt = 1;
  (snip)
  715 err:
  716   errsave = errno;
  717   port = prettyprint_addr(addr, daemon->addrbuff);
  718   if (!option_bool(OPT_NOWILD) && !option_bool(OPT_CLEVERBIND))
  719 sprintf(daemon->addrbuff, "port %d", port);
  720   s = _("failed to create listening socket for %s: %s");
  721   
  722   if (fd != -1)
  723 close (fd);
  724 
  725   errno = errsave;
  726 
  727   if (dienow)
  728 {
  729   /* failure to bind addresses given by --listen-address at 
this
  729  point
  730  is OK if we're doing bind-dynamic */
  731   if (!option_bool(OPT_CLEVERBIND))
  732 die(s, daemon->addrbuff, EC_BADNET);
  733 

[Touch-packages] [Bug 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.

[Jeff Lane ]

Something in a recent dnsmasq update broke KVM. I hit the same and found
a workaround that gets me rolling again wtih KVM guests at least
here's a quick shell summary:

bladernr@galactica:~$ sudo virsh net-start default
error: Failed to start network default
error: internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper) unexpected exit status 2: 
dnsmasq: failed to create listening socket for 192.168.123.1: Address already 
in use

bladernr@galactica:~$ sudo virsh net-list
 Name   State   Autostart   Persistent


bladernr@galactica:~$ sudo apt-cache policy dnsmasq-base
dnsmasq-base:
  Installed: 2.90-0ubuntu0.23.10.1
  Candidate: 2.90-0ubuntu0.23.10.1
  Version table:
 *** 2.90-0ubuntu0.23.10.1 500
500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 
Packages
100 /var/lib/dpkg/status
 2.89-1 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages

bladernr@galactica:~$ sudo apt install dnsmasq-base=2.89-1
bladernr@galactica:~$ sudo virsh net-start default
Network default started

bladernr@galactica:~$ sudo virsh net-list
 Name  StateAutostart   Persistent

 default   active   yes yes

as you can see, as a workaround, reverting to the original Mantic
version allows the NAT network to start and I can once again launch KVM
guests on my machine.

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

Title:
  After updating ubuntu, the network to which the subnet address is
  assigned does not become active in KVM.

Status in dnsmasq package in Ubuntu:
  Confirmed

Bug description:
  phenomenon:
After updating ubuntu, the network to which the subnet address is assigned 
does not become active in KVM.

  Cause:
This is because the following dnsmasq update operation performed by apt's 
automatic update causes an error. It worked properly with dnsmasq 2.80, but 
does not work properly with 2.90.

  $ cat /var/log/apt/history.log
  (snip)
  Start-Date: 2024-02-27  06:17:31
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: dnsmasq-base:amd64 (2.80-1.1ubuntu1.7, 2.90-0ubuntu0.20.04.1)
  End-Date: 2024-02-27  06:17:44
  (snip)
  $

  Cause details:
As a premise, bind-dynamic is set in the dnsmasq config file for KVM. Below 
is an example.

  $ cat default.conf 
  ##WARNING:  THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
  ##OVERWRITTEN AND LOST.  Changes to this configuration should be made using:
  ##virsh net-edit default
  ## or other application using the libvirt API.
  ##
  ## dnsmasq conf file created by libvirt
  strict-order
  user=libvirt-dnsmasq
  pid-file=/run/libvirt/network/default.pid
  except-interface=lo
  bind-dynamic
  interface=virbr0
  dhcp-range=192.168.122.2,192.168.122.254,255.255.255.0
  dhcp-no-override
  dhcp-authoritative
  dhcp-lease-max=253
  dhcp-hostsfile=/var/lib/libvirt/dnsmasq/default.hostsfile
  addn-hosts=/var/lib/libvirt/dnsmasq/default.addnhosts
  $ 

  
  When starting the network with KVM (virsh net-start), dnsmasq started from 
KVM executes the make_sock function twice as shown below.

 $ cat network.c
 (snip)
 1087 static struct listener *create_listeners(union mysockaddr *addr, int 
do_
 1087 tftp, int dienow)
 1088 {
 1089   struct listener *l = NULL;
 1090   int fd = -1, tcpfd = -1, tftpfd = -1;
 1091 
 1092   (void)do_tftp;
 1093 
 1094   if (daemon->port != 0)
 1095 {
 1096   fd = make_sock(addr, SOCK_DGRAM, dienow);
 1097   tcpfd = make_sock(addr, SOCK_STREAM, dienow);
 1098 }
 (snip)

  The following code causes an issue with the update made in dnsmasq
  2.90.

 $ cat network.c
 (snip)
  895 static int make_sock(union mysockaddr *addr, int type, int dienow)
  896 {
  (snip)
  934   if (!option_bool(OPT_CLEVERBIND) || errno != EADDRNOTAVAIL)
  935 {
  936   if (dienow)
  937 die(s, daemon->addrbuff, EC_BADNET);
  938   else
  939 my_syslog(LOG_WARNING, s, daemon->addrbuff, 
strerror(errno))939 ;
  940 }
  (snip)

  
  function "make_sock" in network.c:1096 binds the socket to 192.168.122.1/24, 
and then make_sock in network.c:1097 tries to bind to the same address. 
However, in network.c:934, when errno==98 occurs, network.c:937 is executed, so 
dnsmasq does not cause a startup error. As a result, virsh net-start fails.

  As a temporary workaround, it will work if you try not to die.

  $ diff -u  network_c_back  network.c 
  --- network_c_back  

[Touch-packages] [Bug 1988023] Re: Could not switch uppercase/lowercase by using keyboard of laptop

[Jeff Lane ]

Questions/Comments:
What does "remotely" mean here?  The bug report speaks of using the laptop
keyboard, not remote access; and a remote connection would mean just passing
a data stream - the local keymap setting has no effect on the keys sent by a
remote connection.

localectl is not how we manage keyboard settings in Ubuntu, and console-data
is a package in universe that we don't use at all.  If you need to change
the keymap, this should be done with `sudo dpkg-reconfigure
keyboard-configuration`.  localectl may or may not do the right thing, it's
basically untested.  Regardless, capslock or shift not working correctly
should not be a question of keymap, there are no keymaps we ship by default
that don't handle these keys in the normal way.  Perhaps this is a kernel or
issue or a bug with their ACPI tables?

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

Title:
  Could not switch uppercase/lowercase by using keyboard of laptop

Status in systemd package in Ubuntu:
  New

Bug description:
  1. Fresh install ubuntu server 22.04.1 on Lenovo server.
  2. Install console-data package 
  3. Get locale status: 
  # localectl status
 System Locale: LANG=en_US.UTF-8
 VC Keymap: n/a
X11 Layout: us
 X11 Model: pc105
  4. Fail to ist and set keymap with command "localectl", but the kmap file can 
be found in the /usr/share./keymaps/
  #localectl list-keymaps 
  Failed to read list of keymaps: No such file or directory 
  # localectl set-keymap us
  Failed to set keymap: Keymap us is not installed.
  # find /usr/ -name us.kmap.gz
  /usr/share/keymaps/i386/qwerty/us.kmap.gz 
  5. It need type "CapsLock" twice when want to switch uppercase/lowercase by 
using keyboard of laptop, not once, the other keyboard has no issue about it.
  # dumpkeys | grep -E "keymaps|58"
  keymaps 0-127
  keycode  58 = CtrlL_Lock 
  6. It can switch uppercase/lowercase normally after run command "loadkeys us".

  Please help check why need type twice "CapsLock" for switching 
uppercase/lowercase and how to fix it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-29 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  MachineType: Lenovo ThinkSystem SR630 V2
  Package: systemd 249.11-0ubuntu3.4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/21/2022
  dmi.bios.release: 1.30
  dmi.bios.vendor: Lenovo
  dmi.bios.version: AFE118I-1.30
  dmi.board.asset.tag: none
  dmi.board.name: 7Z70CTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.80
  dmi.modalias: 
dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkSystem SR630 V2
  dmi.product.sku: 7Z70CTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

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


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

[Touch-packages] [Bug 1969477] Re: apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection

[Jeff Lane]

>If direct access to Launchpad is blocked how was a bug report filed in
the first place?

Clicking the "Report a Bug" link on any project's page in LP.  This is
done from a machine outside of the airgapped or restricted access lab
where the hardware sits.

Also, I should point out (which I mentioned originally) that one can,
and I'll also start suggesting they do this, use --save with ubuntu-bug
to create a bug report that can be submitted later from a different
machine.

I'm just asking to have apport-collect also feature this...

Perhaps the solution since, as you pointed out, apport needs to read the
bug to know which package to collect files for, is to require the
package as part of the commmand... e.g.

apport-collect --save=/path/to/filename --package=$PACKAGE $BUG_NUMBER

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

Title:
  apport-collect needs to be able to save logs to a file instead of
  requiring a launchpad connection

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  We very often tell our hardware partners to "file a bug" when they
  encounter issues.  This requires them to run apport-collect to gather
  and submit logs for the bug.

  However, very often, the hardware that has the problem is in a lab
  that has tight security restrictions and direct access to launchpad is
  blocked.  This makes it nearly impossible for them to gather any
  requested logs, since apport-collect requires a direct line to
  Launchpad.

  apport-collect needs to adopt the --save feature of apport-bug/ubuntu-
  bug to save the prescribed logs and system data in a tarball that can
  then be attached to a bug after the fact.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.23
  ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
  Uname: Linux 5.4.0-100-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_100_113_generic_85 zfs zunicode zavl 
icp nvidia_modeset zcommon znvpair nvidia
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 19 10:25:54 2022
  InstallationDate: Installed on 2016-02-11 (2258 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1969477] [NEW] apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection

[Jeff Lane]

Public bug reported:

We very often tell our hardware partners to "file a bug" when they
encounter issues.  This requires them to run apport-collect to gather
and submit logs for the bug.

However, very often, the hardware that has the problem is in a lab that
has tight security restrictions and direct access to launchpad is
blocked.  This makes it nearly impossible for them to gather any
requested logs, since apport-collect requires a direct line to
Launchpad.

apport-collect needs to adopt the --save feature of apport-bug/ubuntu-
bug to save the prescribed logs and system data in a tarball that can
then be attached to a bug after the fact.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apport 2.20.11-0ubuntu27.23
ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
Uname: Linux 5.4.0-100-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_5_4_0_100_113_generic_85 zfs zunicode zavl icp 
nvidia_modeset zcommon znvpair nvidia
ApportLog:
 
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 19 10:25:54 2022
InstallationDate: Installed on 2016-02-11 (2258 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  apport-collect needs to be able to save logs to a file instead of
  requiring a launchpad connection

Status in apport package in Ubuntu:
  New

Bug description:
  We very often tell our hardware partners to "file a bug" when they
  encounter issues.  This requires them to run apport-collect to gather
  and submit logs for the bug.

  However, very often, the hardware that has the problem is in a lab
  that has tight security restrictions and direct access to launchpad is
  blocked.  This makes it nearly impossible for them to gather any
  requested logs, since apport-collect requires a direct line to
  Launchpad.

  apport-collect needs to adopt the --save feature of apport-bug/ubuntu-
  bug to save the prescribed logs and system data in a tarball that can
  then be attached to a bug after the fact.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.23
  ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
  Uname: Linux 5.4.0-100-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_100_113_generic_85 zfs zunicode zavl 
icp nvidia_modeset zcommon znvpair nvidia
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 19 10:25:54 2022
  InstallationDate: Installed on 2016-02-11 (2258 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04

[Jeff Lane]

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

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

Title:
  Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with
  exit code 1." in Ubuntu 22.04

Status in snapd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Configuration:
   OS:jammy-live-server20220320-amd64.iso
   CPU:AMD EPYC 7702 64-Core Processor
   UEFI Version:D8E119A
   BMC Version:D8BT19I
   SSD:Intel 1.60TB NVMe SSD
   Boot mode:legacy
  Reproduce Steps:
   1.Boot into BIOS and set boot mode to legacy
   2.install ubuntu 22.04 on NVMe SSD
   3.Check syslog log
  Current behaviors:
  syslog shows systemd-udevd errors in Ubuntu 22.04
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1.

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


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

[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04

[Jeff Lane]

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

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

Title:
  Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with
  exit code 1." in Ubuntu 22.04

Status in snapd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Configuration:
   OS:jammy-live-server20220320-amd64.iso
   CPU:AMD EPYC 7702 64-Core Processor
   UEFI Version:D8E119A
   BMC Version:D8BT19I
   SSD:Intel 1.60TB NVMe SSD
   Boot mode:legacy
  Reproduce Steps:
   1.Boot into BIOS and set boot mode to legacy
   2.install ubuntu 22.04 on NVMe SSD
   3.Check syslog log
  Current behaviors:
  syslog shows systemd-udevd errors in Ubuntu 22.04
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1.

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


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

[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04

[Jeff Lane]

Can this be reproduced in EFI mode, or is it only when in Legacy Mode?

ALso, what is the mount command you are using? Just basic like "mount
/dev/device /mountpoint"? Or is there a different mount command you are
using that is failing?

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

Title:
  Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with
  exit code 1." in Ubuntu 22.04

Status in systemd package in Ubuntu:
  New

Bug description:
  Configuration:
   OS:jammy-live-server20220320-amd64.iso
   CPU:AMD EPYC 7702 64-Core Processor
   UEFI Version:D8E119A
   BMC Version:D8BT19I
   SSD:Intel 1.60TB NVMe SSD
   Boot mode:legacy
  Reproduce Steps:
   1.Boot into BIOS and set boot mode to legacy
   2.install ubuntu 22.04 on NVMe SSD
   3.Check syslog log
  Current behaviors:
  syslog shows systemd-udevd errors in Ubuntu 22.04
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1.

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


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

[Touch-packages] [Bug 1887372] Re: Cannot create lvm upon IMSM raid array

[Jeff Lane]

Please verify this is no longer an issue in Focal or Hirsute based on
Graham's comment #3 above.

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

Title:
  Cannot create lvm upon IMSM raid array

Status in lvm2 package in Ubuntu:
  Incomplete
Status in lvm2 source package in Focal:
  Incomplete
Status in lvm2 source package in Groovy:
  Won't Fix
Status in lvm2 source package in Hirsute:
  Incomplete

Bug description:
  The issue has been observed on 2.3.7 (Ubuntu 20.04).
  Reported to lvm team:
  https://bugzilla.redhat.com/show_bug.cgi?id=1855251

  Steps to Reproduce:
  1. Create IMSM raid array:
  #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1
  #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G

  2. Create lvm volume on raid:
  # pvcreate -ff -y /dev/md/vol
  # vgcreate group0 /dev/md/vol
  # lvcreate -Z y -y -l +100%FREE group0 -n lvm0

  Actual results:
  Vg creation fails.

  Expected results:
  LVM should be able to determine the best drive and ignore duplicates.

  Additional info:
  IMSM metadata is written at the end of the drive. The first drive sector 
belongs to the raid volume and other metadata saved there (like lvm) can be 
recognized directly on raid members.

  The following patches should fix the issue (not verified yet):
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81

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


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

[Touch-packages] [Bug 1887372] Re: Cannot create lvm upon IMSM raid array

[Jeff Lane]

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

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

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

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

Title:
  Cannot create lvm upon IMSM raid array

Status in lvm2 package in Ubuntu:
  Incomplete
Status in lvm2 source package in Focal:
  Incomplete
Status in lvm2 source package in Groovy:
  Won't Fix
Status in lvm2 source package in Hirsute:
  Incomplete

Bug description:
  The issue has been observed on 2.3.7 (Ubuntu 20.04).
  Reported to lvm team:
  https://bugzilla.redhat.com/show_bug.cgi?id=1855251

  Steps to Reproduce:
  1. Create IMSM raid array:
  #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1
  #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G

  2. Create lvm volume on raid:
  # pvcreate -ff -y /dev/md/vol
  # vgcreate group0 /dev/md/vol
  # lvcreate -Z y -y -l +100%FREE group0 -n lvm0

  Actual results:
  Vg creation fails.

  Expected results:
  LVM should be able to determine the best drive and ignore duplicates.

  Additional info:
  IMSM metadata is written at the end of the drive. The first drive sector 
belongs to the raid volume and other metadata saved there (like lvm) can be 
recognized directly on raid members.

  The following patches should fix the issue (not verified yet):
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81

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


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

[Touch-packages] [Bug 1933359] Re: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request

[Jeff Lane]

** Package changed: lxc (Ubuntu) => linux (Ubuntu)

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

Title:
  [Ubuntu 21.10][Broadcom] mpi3mr driver submission request

Status in linux package in Ubuntu:
  New

Bug description:
  Broadcom is coming up with next generation high performance Storage IO and 
RAID controllers. For details, follow: 
https://www.spinics.net/lists/linux-scsi/msg147868.html
  This family of controllers is managed by "mpi3mr" Linux device driver(written 
from scratch). First patchset of the driver is accepted by Linux upstream.
  The driver is available in git branch - 5.14/scsi-staging of Linux SCSI tree: 
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git
  The driver will be part of 5.14 mainline Linux kernel release. Here is the 
list of commit ids:

  9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints
  74e1f30a2868 scsi: mpi3mr: Add EEDP DIF DIX support
  28cbe2f420d3 scsi: mpi3mr: Add support for DSN secure firmware check
  2f9c4d520aa6 scsi: mpi3mr: Add support for PM suspend and resume
  44dc724f5eec scsi: mpi3mr: Wait for pending I/O completions upon detection of 
VD I/O timeout
  71e80106d059 scsi: mpi3mr: Print pending host I/Os for debugging
  f061178e0762 scsi: mpi3mr: Complete support for soft reset
  463429f8dd5c scsi: mpi3mr: Add support for threaded ISR
  392bbeb85b2a scsi: mpi3mr: Hardware workaround for UNMAP commands to NVMe 
drives
  82141ddba90a scsi: mpi3mr: Allow certain commands during pci-remove hook
  0ea177343f1f scsi: mpi3mr: Add change queue depth support
  e844adb1fbdc scsi: mpi3mr: Implement SCSI error handler hooks
  8f9c6173ca46 scsi: mpi3mr: Add bios_param SCSI host template hook
  ff9561e910fc scsi: mpi3mr: Print IOC info for debugging
  54dfcffb4191 scsi: mpi3mr: Add support for timestamp sync with firmware
  fb9b04574f14 scsi: mpi3mr: Add support for recovering controller
  e36710dc06e3 scsi: mpi3mr: Additional event handling
  8e653455547a scsi: mpi3mr: Add support for PCIe device event handling
  13ef29ea4aa0 scsi: mpi3mr: Add support for device add/remove event handling
  672ae26c8216 scsi: mpi3mr: Add support for internal watchdog thread
  023ab2a9b4ed scsi: mpi3mr: Add support for queue command processing
  c9566231cfaf scsi: mpi3mr: Create operational request and reply queue pair
  824a156633df scsi: mpi3mr: Base driver code
  c4f7ac64616e scsi: mpi3mr: Add mpi30 Rev-R headers and Kconfig

  Please include this driver in Ubuntu 21.10 release.
  Let me know for any questions.

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

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

[Touch-packages] [Bug 1887372] Re: Cannot create lvm upon IMSM raid array

[Jeff Lane]

Mariusz,

> The following patches should fix the issue (not verified yet):
> https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca
> https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81

Were those patches verified to fix this in LVM2?

And is there an upstream release version that contains them?

** Changed in: lvm2 (Ubuntu Groovy)
   Status: Confirmed => Won't Fix

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

Title:
  Cannot create lvm upon IMSM raid array

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Focal:
  Confirmed
Status in lvm2 source package in Groovy:
  Won't Fix
Status in lvm2 source package in Hirsute:
  Confirmed

Bug description:
  The issue has been observed on 2.3.7 (Ubuntu 20.04).
  Reported to lvm team:
  https://bugzilla.redhat.com/show_bug.cgi?id=1855251

  Steps to Reproduce:
  1. Create IMSM raid array:
  #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1
  #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G

  2. Create lvm volume on raid:
  # pvcreate -ff -y /dev/md/vol
  # vgcreate group0 /dev/md/vol
  # lvcreate -Z y -y -l +100%FREE group0 -n lvm0

  Actual results:
  Vg creation fails.

  Expected results:
  LVM should be able to determine the best drive and ignore duplicates.

  Additional info:
  IMSM metadata is written at the end of the drive. The first drive sector 
belongs to the raid volume and other metadata saved there (like lvm) can be 
recognized directly on raid members.

  The following patches should fix the issue (not verified yet):
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81

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

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

[Touch-packages] [Bug 1887372] Re: Cannot create lvm upon IMSM raid array

[Jeff Lane]

Can this please be targeted for 21.10?

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

Title:
  Cannot create lvm upon IMSM raid array

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Focal:
  Confirmed
Status in lvm2 source package in Groovy:
  Confirmed
Status in lvm2 source package in Hirsute:
  Confirmed

Bug description:
  The issue has been observed on 2.3.7 (Ubuntu 20.04).
  Reported to lvm team:
  https://bugzilla.redhat.com/show_bug.cgi?id=1855251

  Steps to Reproduce:
  1. Create IMSM raid array:
  #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1
  #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G

  2. Create lvm volume on raid:
  # pvcreate -ff -y /dev/md/vol
  # vgcreate group0 /dev/md/vol
  # lvcreate -Z y -y -l +100%FREE group0 -n lvm0

  Actual results:
  Vg creation fails.

  Expected results:
  LVM should be able to determine the best drive and ignore duplicates.

  Additional info:
  IMSM metadata is written at the end of the drive. The first drive sector 
belongs to the raid volume and other metadata saved there (like lvm) can be 
recognized directly on raid members.

  The following patches should fix the issue (not verified yet):
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81

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

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

[Touch-packages] [Bug 1887372] Re: Cannot create lvm upon IMSM raid array

[Jeff Lane]

** Also affects: lvm2 (Ubuntu Hirsute)
   Importance: Undecided
   Status: Confirmed

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

Title:
  Cannot create lvm upon IMSM raid array

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Focal:
  Confirmed
Status in lvm2 source package in Groovy:
  Confirmed
Status in lvm2 source package in Hirsute:
  Confirmed

Bug description:
  The issue has been observed on 2.3.7 (Ubuntu 20.04).
  Reported to lvm team:
  https://bugzilla.redhat.com/show_bug.cgi?id=1855251

  Steps to Reproduce:
  1. Create IMSM raid array:
  #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1
  #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G

  2. Create lvm volume on raid:
  # pvcreate -ff -y /dev/md/vol
  # vgcreate group0 /dev/md/vol
  # lvcreate -Z y -y -l +100%FREE group0 -n lvm0

  Actual results:
  Vg creation fails.

  Expected results:
  LVM should be able to determine the best drive and ignore duplicates.

  Additional info:
  IMSM metadata is written at the end of the drive. The first drive sector 
belongs to the raid volume and other metadata saved there (like lvm) can be 
recognized directly on raid members.

  The following patches should fix the issue (not verified yet):
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81

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

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

[Touch-packages] [Bug 1887372] Re: Cannot create lvm upon IMSM raid array

[Jeff Lane]

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

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

Title:
  Cannot create lvm upon IMSM raid array

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Focal:
  Confirmed
Status in lvm2 source package in Groovy:
  Confirmed

Bug description:
  The issue has been observed on 2.3.7 (Ubuntu 20.04).
  Reported to lvm team:
  https://bugzilla.redhat.com/show_bug.cgi?id=1855251

  Steps to Reproduce:
  1. Create IMSM raid array:
  #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1
  #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G

  2. Create lvm volume on raid:
  # pvcreate -ff -y /dev/md/vol
  # vgcreate group0 /dev/md/vol
  # lvcreate -Z y -y -l +100%FREE group0 -n lvm0

  Actual results:
  Vg creation fails.

  Expected results:
  LVM should be able to determine the best drive and ignore duplicates.

  Additional info:
  IMSM metadata is written at the end of the drive. The first drive sector 
belongs to the raid volume and other metadata saved there (like lvm) can be 
recognized directly on raid members.

  The following patches should fix the issue (not verified yet):
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81

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

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

[Touch-packages] [Bug 1867799] Re: Focal: sudo: setrlimit(RLIMIT_CORE): Operation not permitted

[Jeff Lane]

Just spun up a Focal LXD container and this is still an issue in
containers:

bladernr@focal-builder:~/development/kernels-ubuntu/focal$ sudo vim 
/etc/apt/sources.list
sudo: setrlimit(RLIMIT_CORE): Operation not permitted


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

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

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

Title:
  Focal: sudo: setrlimit(RLIMIT_CORE): Operation not permitted

Status in juju:
  Invalid
Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  When bootstrapping to focal and using debug output, we get the
  following outputted to the stderr.

  sudo: setrlimit(RLIMIT_CORE): Operation not permitted

  I'm unsure what it's attempting to do at that point, but others have
  also run into this with a suggested workaround.

  https://gitlab.alpinelinux.org/alpine/aports/issues/11122
  https://bugzilla.redhat.com/show_bug.cgi?id=1773148

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

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

[Touch-packages] [Bug 1868456] [NEW] "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container

[Jeff Lane]

Public bug reported:

I fired up a LXD container using ubuntu-daily:f on my machine and every
time I issue a comment inside the container using sudo, I get this
error:

sudo: setrlimit(RLIMIT_CORE): Operation not permitted

I did some digging online and found this was reported against Fedora last fall 
which lead me to this bugzilla report:
https://bugzilla.redhat.com/show_bug.cgi?id=1773148

which seems to tie this to a change in sudo between 1.8.28 and 1.8.29.

Focal has 1.8.31:
bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy sudo
sudo:
  Installed: 1.8.31-1ubuntu1
  Candidate: 1.8.31-1ubuntu1
  Version table:
 *** 1.8.31-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

This is not an issue on Bionic:
bladernr@galactica:~/development/kernels-upstream/mainline$ apt-cache policy 
sudo
sudo:
  Installed: 1.8.21p2-3ubuntu1.2
  Candidate: 1.8.21p2-3ubuntu1.2
  Version table:
 *** 1.8.21p2-3ubuntu1.2 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
100 /var/lib/dpkg/status
 1.8.21p2-3ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

>From the redhat bug, the described workaround does clear these messages
up:

# set disable_coredump false

Once I've done that, the error messages go away.

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

** Description changed:

  I fired up a LXD container using ubuntu-daily:f on my machine and every
  time I issue a comment inside the container using sudo, I get this
  error:
  
  sudo: setrlimit(RLIMIT_CORE): Operation not permitted
  
- I did some digging online and found this was reported against Fedora last 
fall:
+ I did some digging online and found this was reported against Fedora last 
fall which lead me to this bugzilla report:
  https://bugzilla.redhat.com/show_bug.cgi?id=1773148
  
  which seems to tie this to a change in sudo between 1.8.28 and 1.8.29.
  
  Focal has 1.8.31:
  bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy 
sudo
  sudo:
-   Installed: 1.8.31-1ubuntu1
-   Candidate: 1.8.31-1ubuntu1
-   Version table:
-  *** 1.8.31-1ubuntu1 500
- 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1.8.31-1ubuntu1
+   Candidate: 1.8.31-1ubuntu1
+   Version table:
+  *** 1.8.31-1ubuntu1 500
+ 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  This is not an issue on Bionic:
  bladernr@galactica:~/development/kernels-upstream/mainline$ apt-cache policy 
sudo
  sudo:
-   Installed: 1.8.21p2-3ubuntu1.2
-   Candidate: 1.8.21p2-3ubuntu1.2
-   Version table:
-  *** 1.8.21p2-3ubuntu1.2 500
- 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
- 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  1.8.21p2-3ubuntu1 500
- 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+   Installed: 1.8.21p2-3ubuntu1.2
+   Candidate: 1.8.21p2-3ubuntu1.2
+   Version table:
+  *** 1.8.21p2-3ubuntu1.2 500
+ 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
+ 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  1.8.21p2-3ubuntu1 500
+ 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  
  From the redhat bug, the described workaround does clear these messages
  up:
  
  # set disable_coredump false
  
  Once I've done that, the error messages go away.

** Package changed: lxd (Ubuntu) => sudo (Ubuntu)

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

Title:
  "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when
  using sudo in 20.04 LXD container

Status in sudo package in Ubuntu:
  New

Bug description:
  I fired up a LXD container using ubuntu-daily:f on my machine and
  every time I issue a comment inside the container using sudo, I get
  this error:

  sudo: setrlimit(RLIMIT_CORE): Operation not permitted

  I did some digging online and found this was reported against Fedora last 
fall which lead me to this bugzilla report:
  https://bugzilla.redhat.com/show_bug.cgi?id=1773148

  which seems to tie this to a change in sudo between 1.8.28 and 1.8.29.

  Focal has 1.8.31:
  bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy 
sudo
  sudo:
    Installed: 1.8.31-1ubuntu1
    Candidate: 1.8.31-1ubuntu1
    Version table:
   *** 1.8.31-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 

[Touch-packages] [Bug 1089389] Re: juju bootstrap fail behind a proxy when a gpg key must be imported

[Jeff Lane]

** Tags removed: hwcert-server

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

Title:
  juju bootstrap fail behind a proxy when a gpg key must be imported

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  This is related to a Maas environment hosted behind a proxy.

  I'm trying to use
  juju 0.6.0.1+bzr603-0juju1~precise1

  ubuntu@maas:~$ cat .juju/environments.yaml
  environments:
    mymaas:
  type: maas
  maas-server: 'http://192.168.124.2:80/MAAS'
  maas-oauth: 
'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt'
  admin-secret: 'nothing'
  default-series: precise
  juju-origin: ppa

  When juju boostrap, things do not behave as expected on the zookeeper
  node.

  Excerpt from the cloud-init-output.log:

  W: GPG error: http://ppa.launchpad.net precise Release: The following
  signatures couldn't be verified because the public key is not
  available: NO_PUBKEY 376A290EC8068B11

  On the zookeeper node, if i try to apt-add-repository , the needed gpg
  key is not injected, but the scrpit does not return any error code:

  ubuntu@zookeeper:/var/log$ sudo mv 
/etc/apt/sources.list.d/juju-pkgs-precise.list /tmp/
  ubuntu@zookeeper:/var/log$ sudo ls /etc/apt/sources.list.d/
  ubuntu@zookeeper:/var/log$ sudo apt-add-repository ppa:juju/pkgs --yes
  gpg: keyring `/tmp/tmpmlP7VA/secring.gpg' created
  gpg: keyring `/tmp/tmpmlP7VA/pubring.gpg' created
  gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com
  gpgkeys: key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 not found on keyserver
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  recv failed
  ubuntu@zookeeper:/var/log$ echo $?
  0

  Trying to inject key while setting the http_proxy environment variable works 
better:
  ubuntu@zookeeper:/var/log$ sudo http_proxy=http://91.189.90.174:3128/ 
apt-add-repository ppa:juju/pkgs --yes
  gpg: keyring `/tmp/tmp1pAd6X/secring.gpg' created
  gpg: keyring `/tmp/tmp1pAd6X/pubring.gpg' created
  gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp1pAd6X/trustdb.gpg: trustdb created
  gpg: key C8068B11: public key "Launchpad Ensemble PPA" imported
  gpg: Total number processed: 1
  gpg: imported: 1 (RSA: 1)
  OK
  ubuntu@zookeeper:/var/log$ echo $?
  0

  On the zookeeper node, python-software-properties is version 0.82.7.3

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: python-software-properties 0.82.7.3
  ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33
  Uname: Linux 3.2.0-34-generic x86_64
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: amd64
  Date: Wed Dec 12 14:40:21 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to precise on 2012-05-14 (212 days ago)

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

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

[Touch-packages] [Bug 1846543] [NEW] --massive-debug option produces very little debug messaging

[Jeff Lane]

Public bug reported:

According to --help:

  -m, --massive-debug   Print a lot of debug information to the command
line

Now, perhaps my understanding of the words "massive" and "debug" are
flawed, but the output I get while trying to debug failure to add a PPA
is neither massive, nor really debug level information:

ubuntu@hogplum:~$ sudo add-apt-repository -m ppa:checkbox-dev/testing
Cannot add PPA: 'ppa:~checkbox-dev/ubuntu/testing'.
ERROR: '~checkbox-dev' user or team does not exist.

The PPA most certainly exists:
https://code.launchpad.net/~checkbox-dev/+archive/ubuntu/testing

This message is the utterly useless messaging one gets when add-apt-
repository cannot talk to something upstream, be it ppa.launchpad.net or
keyserver.ubuntu.com, perhaps.

Either way, "user or team does not exist" is factually wrong, and
utterly unhelpful, and the level of messaging is in no way debug level
messaging, nor is it massive.

add-apt-repository should actually provide MASSIVE debug level logging
when -m/--massive-debug is passed to it, explaining each and every
action it takes from beginning to end.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: software-properties-common 0.96.24.32.11
ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Oct  3 13:57:15 2019
InstallationDate: Installed on 2016-02-11 (1329 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  --massive-debug option produces very little debug messaging

Status in software-properties package in Ubuntu:
  New

Bug description:
  According to --help:

-m, --massive-debug   Print a lot of debug information to the
  command line

  Now, perhaps my understanding of the words "massive" and "debug" are
  flawed, but the output I get while trying to debug failure to add a
  PPA is neither massive, nor really debug level information:

  ubuntu@hogplum:~$ sudo add-apt-repository -m ppa:checkbox-dev/testing
  Cannot add PPA: 'ppa:~checkbox-dev/ubuntu/testing'.
  ERROR: '~checkbox-dev' user or team does not exist.

  The PPA most certainly exists:
  https://code.launchpad.net/~checkbox-dev/+archive/ubuntu/testing

  This message is the utterly useless messaging one gets when add-apt-
  repository cannot talk to something upstream, be it ppa.launchpad.net
  or keyserver.ubuntu.com, perhaps.

  Either way, "user or team does not exist" is factually wrong, and
  utterly unhelpful, and the level of messaging is in no way debug level
  messaging, nor is it massive.

  add-apt-repository should actually provide MASSIVE debug level logging
  when -m/--massive-debug is passed to it, explaining each and every
  action it takes from beginning to end.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-common 0.96.24.32.11
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct  3 13:57:15 2019
  InstallationDate: Installed on 2016-02-11 (1329 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1832292] Re: reboot reboots system when -h is passed

[Jeff Lane]

Also, yes, I get that this is a nit-pick and that there's a history
there, this is more a wishlist thing because it's a usability issue.

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

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

Title:
  reboot reboots system when -h is passed

Status in systemd package in Ubuntu:
  New

Bug description:
  -h is a fairly common shortcut for --help.

  reboot, however, reboots the machine when one issues the command:

  reboot -h

  Now looking at the man page, there is an entry for --halt and --help,
  but NOTHING for -h at all.

  reboot should return the same as --help when -h is passed, or at the
  very least it should error out and not reboot the system, instead
  perhaps dumping a message like "-h unknown argument".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.21
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Jun 11 00:50:22 2019
  InstallationDate: Installed on 2016-02-11 (1215 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1832292] [NEW] reboot reboots system when -h is passed

[Jeff Lane]

Public bug reported:

-h is a fairly common shortcut for --help.

reboot, however, reboots the machine when one issues the command:

reboot -h

Now looking at the man page, there is an entry for --halt and --help,
but NOTHING for -h at all.

reboot should return the same as --help when -h is passed, or at the
very least it should error out and not reboot the system, instead
perhaps dumping a message like "-h unknown argument".

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu10.21
ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Jun 11 00:50:22 2019
InstallationDate: Installed on 2016-02-11 (1215 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  reboot reboots system when -h is passed

Status in systemd package in Ubuntu:
  New

Bug description:
  -h is a fairly common shortcut for --help.

  reboot, however, reboots the machine when one issues the command:

  reboot -h

  Now looking at the man page, there is an entry for --halt and --help,
  but NOTHING for -h at all.

  reboot should return the same as --help when -h is passed, or at the
  very least it should error out and not reboot the system, instead
  perhaps dumping a message like "-h unknown argument".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.21
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Jun 11 00:50:22 2019
  InstallationDate: Installed on 2016-02-11 (1215 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749774] [NEW] include fwupd packages in Server Seed

[Jeff Lane]

Public bug reported:

fwupd is the closest we have to a standard mechanism currently for doing
in-band firmware updates in a vendor agnostic way.  As long as the
vendors provide firmware blobs in an appropriately formatted package,
fwupd (or fwupdate) can install those firmware blobs from within Ubuntu.

Because of this, we should include the related packages in the server
seed.  The main components all live in Main currently.  As far as I can
tell (verified on a Bionic install), nothing in the current server seed
pulls in fwupd, fwupdate, or fwupdate-signed as a dependency.

ubuntu@xwing:~$ apt-cache policy fwup*

fwupdate:
  Installed: (none)
  Candidate: 10-2
  Version table:
 10-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
fwupd:
  Installed: (none)
  Candidate: 1.0.4-3build1
  Version table:
 1.0.4-3build1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
fwupdate-signed:
  Installed: (none)
  Candidate: 1.17+10-2
  Version table:
 1.17+10-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: hwcert-server

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

Title:
  include fwupd packages in Server Seed

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  fwupd is the closest we have to a standard mechanism currently for
  doing in-band firmware updates in a vendor agnostic way.  As long as
  the vendors provide firmware blobs in an appropriately formatted
  package, fwupd (or fwupdate) can install those firmware blobs from
  within Ubuntu.

  Because of this, we should include the related packages in the server
  seed.  The main components all live in Main currently.  As far as I
  can tell (verified on a Bionic install), nothing in the current server
  seed pulls in fwupd, fwupdate, or fwupdate-signed as a dependency.

  ubuntu@xwing:~$ apt-cache policy fwup*

  fwupdate:
Installed: (none)
Candidate: 10-2
Version table:
   10-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  fwupd:
Installed: (none)
Candidate: 1.0.4-3build1
Version table:
   1.0.4-3build1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  fwupdate-signed:
Installed: (none)
Candidate: 1.17+10-2
Version table:
   1.17+10-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Touch-packages] [Bug 1711254] Re: 16.04.3 deployments include non-existent directories in $PATH

[Jeff Lane]

@Steve, I don't disagree, and I've already merged a patch to fix that
issue in the cert suite.

For context, what happens isn't a test case, but a resource that
enumerates the binaries in the system so that the suite can validate
requirements for executing the tests.

e.g., it enumerates a list that contains "/usr/bin/iperf3" for example,
and the network test then has a constraint to only execute if
"/usr/bin/iperf3" actually exists.

The failure was that the enumeration just executes a 'find', the example
noted in the summary is almost exactly the command the resource job
uses, and find exits with a fail code because the directories listed in
$PATH didn't exist.  I couldn't find a way to tell find to simply ignore
non-existent things, without turning a shell oneliner into a more
complex script, so in the end, the resource job now always returns
"true" regardless of the exit code from 'find'.

But since customers started voicing concern about it, and because it
just seemed odd to me for us to be automatically injecting false data
into $PATH (for whatever reason, I read the bug Adam pointed out, and I
can understand now why this happened) I thought it was worth raising a
bug, even if the ultimate answer is "there were reasons for doing it
that couldn't be avoided".

** Description changed:

  Noticed this while doing regression testing on 16.04.3, and a number of
  customers have asked with concerns as well during their testing.
  
  I don't know exactly when this started, but we just started noticing it
  with 16.04.3 (4.10) but $PATH by default now includes several
  directories that do not exist:
  
- 
- ubuntu@above-ox:~$ find $(echo "$PATH" | sed -e 's/:/ /g') -maxdepth 1 -type 
dfind: ‘/home/ubuntu/bin’: No such file or directory
+ ubuntu@above-ox:~$ find $(echo "$PATH" | sed -e 's/:/ /g') -maxdepth 1 -type d
+ find: ‘/home/ubuntu/bin’: No such file or directory
  find: ‘/home/ubuntu/.local/bin’: No such file or directory
  /usr/local/sbin
  /usr/local/bin
  /usr/sbin
  /usr/bin
  /sbin
  /bin
  /usr/games
  /usr/local/games
  find: ‘/snap/bin’: No such file or directory
  
  We noticed this because it was causing a resource job in the
  certification suite to suddenly start failing (the failure was not
  catastrophic, but it did appear to customers who were concerned.
  
  I've verified this on both s390x and amd64 16.04.3 deployments via MAAS
  2.2.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic s390x
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: s390x
  Date: Wed Aug 16 18:59:34 2017
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en.US_UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en.US_UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  16.04.3 deployments include non-existent directories in $PATH

Status in bash package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  New

Bug description:
  Noticed this while doing regression testing on 16.04.3, and a number
  of customers have asked with concerns as well during their testing.

  I don't know exactly when this started, but we just started noticing
  it with 16.04.3 (4.10) but $PATH by default now includes several
  directories that do not exist:

  ubuntu@above-ox:~$ find $(echo "$PATH" | sed -e 's/:/ /g') -maxdepth 1 -type d
  find: ‘/home/ubuntu/bin’: No such file or directory
  find: ‘/home/ubuntu/.local/bin’: No such file or directory
  /usr/local/sbin
  /usr/local/bin
  /usr/sbin
  /usr/bin
  /sbin
  /bin
  /usr/games
  /usr/local/games
  find: ‘/snap/bin’: No such file or directory

  We noticed this because it was causing a resource job in the
  certification suite to suddenly start failing (the failure was not
  catastrophic, but it did appear to customers who were concerned.

  I've verified this on both s390x and amd64 16.04.3 deployments via
  MAAS 2.2.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic s390x
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: s390x
  Date: Wed Aug 16 18:59:34 2017
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en.US_UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: 

[Touch-packages] [Bug 1704508] [NEW] add-apt-repository traceback when hitting ctrl-c

[Jeff Lane]

Public bug reported:

add-apt-repository says to hit ctrl-c to cancel adding a PPA.  Then it
tracebacks when you do:

ubuntu@bysen:~$ sudo add-apt-repository ppa:maas/next
 This PPA holds new upstream development releases, usually development 
releases. Currently, it is holding the 2.2 series.
 More info: https://launchpad.net/~maas/+archive/ubuntu/next
Press [ENTER] to continue or ctrl-c to cancel adding it
^CTraceback (most recent call last):
  File "/usr/bin/add-apt-repository", line 143, in 
sys.stdin.readline()
KeyboardInterrupt


I understand why the trace is generated, but this is ugly (users should never 
see tracebacks for known conditions, IMO).  

The KeyboardInterrupt exception should be handled properly like any
other exception.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: software-properties-common 0.96.20.7
ProcVersionSignature: User Name 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: amd64
Date: Fri Jul 14 23:17:57 2017
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug uec-images xenial

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

Title:
  add-apt-repository traceback when hitting ctrl-c

Status in software-properties package in Ubuntu:
  New

Bug description:
  add-apt-repository says to hit ctrl-c to cancel adding a PPA.  Then it
  tracebacks when you do:

  ubuntu@bysen:~$ sudo add-apt-repository ppa:maas/next
   This PPA holds new upstream development releases, usually development 
releases. Currently, it is holding the 2.2 series.
   More info: https://launchpad.net/~maas/+archive/ubuntu/next
  Press [ENTER] to continue or ctrl-c to cancel adding it
  ^CTraceback (most recent call last):
File "/usr/bin/add-apt-repository", line 143, in 
  sys.stdin.readline()
  KeyboardInterrupt

  
  I understand why the trace is generated, but this is ugly (users should never 
see tracebacks for known conditions, IMO).  

  The KeyboardInterrupt exception should be handled properly like any
  other exception.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-common 0.96.20.7
  ProcVersionSignature: User Name 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Fri Jul 14 23:17:57 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 425704] Re: [Ubuntu server] Capslock don't turn on LED

[Jeff Lane]

This also affects Xenial.  Plugging a keyboard directly into a system
running Ubuntu Server 16.04.2 with the 4.8 kernel (and 4.10) fails to
illuminate the Caps Lock light on any USB keyboards tried, but the
actual function of the key works.

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

Title:
  [Ubuntu server] Capslock don't turn on LED

Status in console-setup package in Ubuntu:
  Triaged
Status in console-setup package in Debian:
  Confirmed

Bug description:
  Karmic server i386 alpha 5 
  When I press Capslock then LED don't turn on.
  But Shift switch register normally.

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

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

[Touch-packages] [Bug 1687647] Re: udev version 232-21ubuntu3 from ports is broken on Zesty s390x

[Jeff Lane]

Note that the udev package seems to be looking for /sys/class/net/eth*

On my z/KVM instance, eth* do not exist, rather the dev is enc*:

ubuntu@s1lp9g003:~$ ls /sys/class/net/ 
enc4  lo

Likewise, on z/VM, the device is also enc*:

ubuntu@hwe0008:~$ ls /sys/class/net
enc600  lo

Interestingly however, on z/VM, this did not fail.

ubuntu@hwe0008:~$ sudo apt-cache policy udev
udev:
  Installed: 232-21ubuntu2
  Candidate: 232-21ubuntu3
  Version table:
 232-21ubuntu3 500
500 http://us.ports.ubuntu.com/ubuntu-ports zesty-updates/main s390x 
Packages
 *** 232-21ubuntu2 500
500 http://us.ports.ubuntu.com/ubuntu-ports zesty/main s390x Packages
100 /var/lib/dpkg/status
ubuntu@hwe0008:~$ sudo apt-get install udev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  libudev1
The following packages will be upgraded:
  libudev1 udev
2 upgraded, 0 newly installed, 0 to remove and 49 not upgraded.
Need to get 1058 kB of archives.
After this operation, 3072 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.ports.ubuntu.com/ubuntu-ports zesty-updates/main s390x udev 
s390x 232-21ubuntu3 [1005 kB]
Get:2 http://us.ports.ubuntu.com/ubuntu-ports zesty-updates/main s390x libudev1 
s390x 232-21ubuntu3 [52.9 kB]
Fetched 1058 kB in 0s (22.0 MB/s)   
(Reading database ... 82787 files and directories currently installed.)
Preparing to unpack .../udev_232-21ubuntu3_s390x.deb ...
Unpacking udev (232-21ubuntu3) over (232-21ubuntu2) ...
Preparing to unpack .../libudev1_232-21ubuntu3_s390x.deb ...
Unpacking libudev1:s390x (232-21ubuntu3) over (232-21ubuntu2) ...
Setting up libudev1:s390x (232-21ubuntu3) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for libc-bin (2.24-9ubuntu2) ...
Setting up udev (232-21ubuntu3) ...
addgroup: The group `input' already exists as a system group. Exiting.
update-initramfs: deferring update (trigger activated)
Processing triggers for systemd (232-21ubuntu2) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for initramfs-tools (0.125ubuntu9) ...
update-initramfs: Generating /boot/initrd.img-4.10.0-19-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
Using config file '/etc/zipl.conf'
Building bootmap in '/boot'
Building menu 'menu'
Adding #1: IPL section 'ubuntu' (default)
Adding #2: IPL section 'old'
Preparing boot device: dasdb (0200).
Done.


Unfortunately, I have no way to revert my z/KVM instance to re-try on that 
machine

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

Title:
  udev version 232-21ubuntu3 from ports is broken on Zesty s390x

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm attempting to install some cert tools on a z/KVM instance of
  Zesty.  This is failing because udev exits with an error during
  installation.  The apt logs show this:

  Setting up udev (232-21ubuntu3) ...
  addgroup: The group `input' already exists as a system group. Exiting.
  cat: '/sys/class/net/eth*/address': No such file or directory
  dpkg: error processing package udev (--configure):
   subprocess installed post-installation script returned error exit status 1

  and because of that, all other packages up the dependency chain fail
  to install.

  Interestingly, this is resolved by installing the older version of
  udev and libudev1

  ubuntu@s1lp9g003:~$ apt-cache policy udev
  udev:
Installed: 232-21ubuntu3
Candidate: 232-21ubuntu3
Version table:
   *** 232-21ubuntu3 500
  500 http://us.ports.ubuntu.com/ubuntu-ports zesty-updates/main s390x 
Packages
  100 /var/lib/dpkg/status
   232-21ubuntu2 500
  500 http://us.ports.ubuntu.com/ubuntu-ports zesty/main s390x Packages

  ubuntu@s1lp9g003:~$ sudo apt-get install udev=232-21ubuntu2 
libudev1=232-21ubuntu2
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-image-4.8.0-36-generic linux-image-4.8.0-46-generic 
linux-image-extra-4.8.0-36-generic
linux-image-extra-4.8.0-46-generic
  Use 'sudo apt autoremove' to remove them.
  The following packages will be DOWNGRADED:
libudev1 udev
  0 upgraded, 0 newly installed, 2 downgraded, 0 to remove and 0 not upgraded.
  6 not fully installed or removed.
  Need to get 0 B/1056 kB of archives.
  After this operation, 3072 B disk space will be freed.
  Do you want to continue? [Y/n] y
  dpkg: warning: downgrading udev from 232-21ubuntu3 to 232-21ubuntu2
  (Reading database ... 99656 files and directories currently installed.)
  Preparing to unpack .../udev_232-21ubuntu2_s390x.deb ...
  Unpacking udev (232-21ubuntu2) over (232-21ubuntu3) ...
  dpkg: warning: 

[Touch-packages] [Bug 1687647] [NEW] udev version 232-21ubuntu3 from ports is broken on Zesty s390x

[Jeff Lane]

Public bug reported:

I'm attempting to install some cert tools on a z/KVM instance of Zesty.
This is failing because udev exits with an error during installation.
The apt logs show this:

Setting up udev (232-21ubuntu3) ...
addgroup: The group `input' already exists as a system group. Exiting.
cat: '/sys/class/net/eth*/address': No such file or directory
dpkg: error processing package udev (--configure):
 subprocess installed post-installation script returned error exit status 1

and because of that, all other packages up the dependency chain fail to
install.

Interestingly, this is resolved by installing the older version of udev
and libudev1

ubuntu@s1lp9g003:~$ apt-cache policy udev
udev:
  Installed: 232-21ubuntu3
  Candidate: 232-21ubuntu3
  Version table:
 *** 232-21ubuntu3 500
500 http://us.ports.ubuntu.com/ubuntu-ports zesty-updates/main s390x 
Packages
100 /var/lib/dpkg/status
 232-21ubuntu2 500
500 http://us.ports.ubuntu.com/ubuntu-ports zesty/main s390x Packages

ubuntu@s1lp9g003:~$ sudo apt-get install udev=232-21ubuntu2 
libudev1=232-21ubuntu2
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-image-4.8.0-36-generic linux-image-4.8.0-46-generic 
linux-image-extra-4.8.0-36-generic
  linux-image-extra-4.8.0-46-generic
Use 'sudo apt autoremove' to remove them.
The following packages will be DOWNGRADED:
  libudev1 udev
0 upgraded, 0 newly installed, 2 downgraded, 0 to remove and 0 not upgraded.
6 not fully installed or removed.
Need to get 0 B/1056 kB of archives.
After this operation, 3072 B disk space will be freed.
Do you want to continue? [Y/n] y
dpkg: warning: downgrading udev from 232-21ubuntu3 to 232-21ubuntu2
(Reading database ... 99656 files and directories currently installed.)
Preparing to unpack .../udev_232-21ubuntu2_s390x.deb ...
Unpacking udev (232-21ubuntu2) over (232-21ubuntu3) ...
dpkg: warning: downgrading libudev1:s390x from 232-21ubuntu3 to 232-21ubuntu2
Preparing to unpack .../libudev1_232-21ubuntu2_s390x.deb ...
Unpacking libudev1:s390x (232-21ubuntu2) over (232-21ubuntu3) ...
Setting up libudev1:s390x (232-21ubuntu2) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for libc-bin (2.24-9ubuntu2) ...
Setting up udev (232-21ubuntu2) ...
addgroup: The group `input' already exists as a system group. Exiting.
update-initramfs: deferring update (trigger activated)
Processing triggers for systemd (232-21ubuntu3) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up python3-checkbox-support 
(0.34.0~rc1+git201704041517+pkg52~ubuntu17.04.1) ...
Setting up plainbox-provider-resource-generic 
(0.31.0+git201704241134+pkg28~ubuntu17.04.1) ...
Setting up plainbox-provider-checkbox 
(0.35.0+git201705012258+pkg34~ubuntu17.04.1) ...
Setting up plainbox-provider-certification-server 
(0.33.0+git201705021508+pkg60~ubuntu17.04.1) ...
Setting up canonical-certification-server 
(0.33.0+git201705021508+pkg60~ubuntu17.04.1) ...
Processing triggers for initramfs-tools (0.125ubuntu9) ...
update-initramfs: Generating /boot/initrd.img-4.10.0-20-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
Using config file '/etc/zipl.conf'
Building bootmap in '/boot'
Building menu 'menu'
Adding #1: IPL section 'ubuntu' (default)
Adding #2: IPL section 'old'
Preparing boot device: vda ().
Done.


As you can see, once I installed the original zesty version of udev and 
libudev1, my packages succeeded in completing installation.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: udev 232-21ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic s390x
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu4
Architecture: s390x
CustomUdevRuleFiles: 41-generic-ccw-0.0.0003.rules 
41-generic-ccw-0.0.0004.rules 41-generic-ccw-0.0..rules 
41-generic-ccw-0.0.0005.rules 41-cio-ignore.rules 41-generic-ccw-0.0.0001.rules 
41-generic-ccw-0.0.0002.rules
Date: Tue May  2 11:41:16 2017
Lspci:
 
Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C
 SHELL=/bin/bash
ProcKernelCmdLine: root=/dev/mapper/s1lp9g003_vg-s1lp9g003_lv crashkernel=196M
SourcePackage: systemd
UpgradeStatus: Upgraded to zesty on 2017-04-13 (18 days ago)

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


** Tags: apport-bug s390x zesty

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

Title:
  udev version 232-21ubuntu3 from ports is broken on Zesty s390x

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm attempting to install some cert tools on a z/KVM instance of
  Zesty.  This is failing because udev exits with an error 

[Touch-packages] [Bug 1549507] Re: vim in xenial not compiled with python support

[Jeff Lane]

Looks to me like I have the same version you do, and Python3 IS compiled
in.

bladernr@galactica:~$ vim --version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 08 2016 11:38:28)
Included patches: 1-1689
Modified by pkg-vim-maintain...@lists.alioth.debian.org
Compiled by pkg-vim-maintain...@lists.alioth.debian.org
Huge version without GUI.  Features included (+) or not (-):
+acl +farsi   +mouse_netterm   +tag_binary
+arabic  +file_in_path+mouse_sgr   +tag_old_static
+autocmd +find_in_path-mouse_sysmouse  -tag_any_white
-balloon_eval+float   +mouse_urxvt +tcl
-browse  +folding +mouse_xterm +terminfo
++builtin_terms  -footer  +multi_byte  +termresponse
+byte_offset +fork()  +multi_lang  +textobjects
+channel +gettext -mzscheme+timers
+cindent -hangul_input+netbeans_intg   +title
-clientserver+iconv   +packages-toolbar
-clipboard   +insert_expand   +path_extra  +user_commands
+cmdline_compl   +job +perl+vertsplit
+cmdline_hist+jumplist+persistent_undo +virtualedit
+cmdline_info+keymap  +postscript  +visual
+comments+langmap +printer +visualextra
+conceal +libcall +profile +viminfo
+cryptv  +linebreak   -python  +vreplace
+cscope  +lispindent  +python3 +wildignore
+cursorbind  +listcmds+quickfix+wildmenu
+cursorshape +localmap+reltime +windows
+dialog_con  +lua +rightleft   +writebackup
+diff+menu+ruby-X11
+digraphs+mksession   +scrollbind  -xfontset
-dnd +modify_fname+signs   -xim
-ebcdic  +mouse   +smartindent -xsmp
+emacs_tags  -mouseshape  +startuptime -xterm_clipboard
+eval+mouse_dec   +statusline  -xterm_save
+ex_extra+mouse_gpm   -sun_workshop-xpm
+extra_search-mouse_jsbterm   +syntax

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

Title:
  vim in xenial not compiled with python support

Status in vim package in Ubuntu:
  Fix Released

Bug description:
  vim in xenial as of Feb 24, 2016 is missing python support. This has
  been present in all previous builds of vim at least since 14.04. For
  me, this makes the vundle-installed plugin ultisnips complain as
  follows:

  UltiSnips requires py >= 2.7 or py3
  Press ENTER or type command to continue

  I'm requesting that vim be modified to include python support

  Ubuntu xenial snapshot:
  vim --version |grep python
  +cryptv  +linebreak   -python  +viminfo
  +cscope  +lispindent  -python3 +vreplace

  Ubuntu 14.04
  vim --version |grep pyth
  +cryptv  +linebreak   +python  +viminfo
  +cscope  +lispindent  -python3 +vreplace
  Linking: gcc   -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -o vim   
 -lm -ltinfo -lnsl  -lselinux  -lacl -lattr -lgpm -ldl
-L/usr/lib/python2.7/config-x86_64-linux-gnu -lpython2.7 -lpthread -ldl -lutil 
-lm -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions

  
  Ubuntu Xenial vim version complete details

  root@ubuntu1604:/tmp # vim --version
  VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Feb 18 2016 11:55:21)
  Included patches: 1-963
  Modified by pkg-vim-maintain...@lists.alioth.debian.org
  Compiled by pkg-vim-maintain...@lists.alioth.debian.org
  Huge version without GUI.  Features included (+) or not (-):
  +acl +farsi   +mouse_netterm   +syntax
  +arabic  +file_in_path+mouse_sgr   +tag_binary
  +autocmd +find_in_path-mouse_sysmouse  +tag_old_static
  -balloon_eval+float   +mouse_urxvt -tag_any_white
  -browse  +folding +mouse_xterm -tcl
  ++builtin_terms  -footer  +multi_byte  +terminfo
  +byte_offset +fork()  +multi_lang  +termresponse
  +cindent +gettext -mzscheme+textobjects
  -clientserver-hangul_input+netbeans_intg   +title
  -clipboard   +iconv   +path_extra  -toolbar
  +cmdline_compl   +insert_expand   -perl+user_commands
  +cmdline_hist+jumplist+persistent_undo +vertsplit
  +cmdline_info+keymap  +postscript  +virtualedit
  +comments+langmap +printer +visual
  +conceal +libcall +profile +visualextra
  +cryptv  +linebreak   -python  +viminfo
  +cscope  +lispindent  -python3 +vreplace
  +cursorbind  +listcmds+quickfix+wildignore
  +cursorshape +localmap

[Touch-packages] [Bug 1576364] Re: NetworkManager service stops starting on boot after upgrade to Xenial

[Jeff Lane]

Gonna set this to invalid.  After the third or fourth reboot, NM started
loading on it's own and I no longer needed to manually do so.  I don't
know why, but I'm unable to recreate the original fail state now :(

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] JournalErrors.txt

[Jeff Lane]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650573/+files/JournalErrors.txt

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] PciNetwork.txt

[Jeff Lane]

apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650580/+files/PciNetwork.txt

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] nmcli-con.txt

[Jeff Lane]

apport information

** Attachment added: "nmcli-con.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650584/+files/nmcli-con.txt

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] IpAddr.txt

[Jeff Lane]

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1576364/+attachment/4650570/+files/IpAddr.txt

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] NetDevice.wlp3s0.txt

[Jeff Lane]

apport information

** Attachment added: "NetDevice.wlp3s0.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650578/+files/NetDevice.wlp3s0.txt

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] NetDevice.tun0.txt

[Jeff Lane]

apport information

** Attachment added: "NetDevice.tun0.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650575/+files/NetDevice.tun0.txt

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] WifiSyslog.txt

[Jeff Lane]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650583/+files/WifiSyslog.txt

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] NetDevice.lo.txt

[Jeff Lane]

apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650574/+files/NetDevice.lo.txt

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

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

[Jeff Lane]

apport information

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

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] NetDevice.virbr0-nic.txt

[Jeff Lane]

apport information

** Attachment added: "NetDevice.virbr0-nic.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650577/+files/NetDevice.virbr0-nic.txt

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] RfKill.txt

[Jeff Lane]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1576364/+attachment/4650582/+files/RfKill.txt

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] IwConfig.txt

[Jeff Lane]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650572/+files/IwConfig.txt

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

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

[Jeff Lane]

apport information

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

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] NetworkManager.conf.txt

[Jeff Lane]

apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650579/+files/NetworkManager.conf.txt

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] nmcli-dev.txt

[Jeff Lane]

apport information

** Attachment added: "nmcli-dev.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650585/+files/nmcli-dev.txt

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] NetDevice.virbr0.txt

[Jeff Lane]

apport information

** Attachment added: "NetDevice.virbr0.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650576/+files/NetDevice.virbr0.txt

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] IpRoute.txt

[Jeff Lane]

apport information

** Attachment added: "IpRoute.txt"
   
https://bugs.launchpad.net/bugs/1576364/+attachment/4650571/+files/IpRoute.txt

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] Re: NetworkManager service stops starting on boot after upgrade to Xenial

[Jeff Lane]

apport information

** Tags added: apport-collected xenial

** Description changed:

  Running Xenial on a Macbook Air.  This was running Wily and was upgraded
  to Xenial using do-release-upgrade.  Network Manager works, and can
  manage NICs, WiFI and VPNs that I have configured, however, the service
  no longer starts on boot like it did under Wily and like it should by
  default in any case.
  
  I have to manually start NetworkManager after each reboot using "service
  NetworkManager start".
  
  After that step, network is restored and works as it should.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2
+ Architecture: amd64
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ IfupdownConfig:
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
+ InstallationDate: Installed on 2015-10-21 (189 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
+ NetworkManager.state:
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
+  WimaxEnabled=true
+ NonfreeKernelModules: wl
+ Package: network-manager 1.1.93-0ubuntu4
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
+ Tags:  xenial
+ Uname: Linux 4.4.0-21-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1576364/+attachment/4650568/+files/CRDA.txt

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: wl
  Package: network-manager 1.1.93-0ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1576364] [NEW] NetworkManager service stops starting on boot after upgrade to Xenial

[Jeff Lane]

Public bug reported:

Running Xenial on a Macbook Air.  This was running Wily and was upgraded
to Xenial using do-release-upgrade.  Network Manager works, and can
manage NICs, WiFI and VPNs that I have configured, however, the service
no longer starts on boot like it did under Wily and like it should by
default in any case.

I have to manually start NetworkManager after each reboot using "service
NetworkManager start".

After that step, network is restored and works as it should.

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

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

Title:
  NetworkManager service stops starting on boot after upgrade to Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Running Xenial on a Macbook Air.  This was running Wily and was
  upgraded to Xenial using do-release-upgrade.  Network Manager works,
  and can manage NICs, WiFI and VPNs that I have configured, however,
  the service no longer starts on boot like it did under Wily and like
  it should by default in any case.

  I have to manually start NetworkManager after each reboot using
  "service NetworkManager start".

  After that step, network is restored and works as it should.

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

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

[Touch-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still works at the low level (can be controlled with alsamixer)

[Jeff Lane]

et viola, it's working.

Still, no idea where that second, edited version came from :/

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

Title:
  Pulseaudio stopped working but sound still works at the low level (can
  be controlled with alsamixer)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still works at the low level (can be controlled with alsamixer)

[Jeff Lane]

H... ok.  I didn't realize there was a second pulseaudio config.

I have no idea how it got there, nor where it came from, and I do not
recall ever setting it, but sure enough:

### Make some devices default
#set-default-sink output
set-default-source 2
set-source-mute 2 0

So this is likely cruft left over from an older version... to build this
machine, I did a fresh Xenial install and then installed a backup of
/home/$USER via rsync.

However, I do not ever remember configuring this file at any point in
the past, AND this worked just fine in Trusty, and also worked fine in
Xenial until it stopped working, then it started working, then it
stopped working.

Is there some sort of race condition where ~/.pulse/default.pa may or
may not be the default.pa Pulse uses?

Anyway, I'm removing the file and restarting to see what happens.

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

Title:
  Pulseaudio stopped working but sound still works at the low level (can
  be controlled with alsamixer)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still works at the low level (can be controlled with alsamixer)

[Jeff Lane]

On Tue, Mar 1, 2016 at 8:10 AM, David Henningsson
<1547...@bugs.launchpad.net> wrote:
> You haven't changed any configuration files (e g such as
> /etc/pulse/default.pa ) so they now reference a hard-coded "source #2",
> have you?

I have only changed the autospawn line in /etc/pulse/client.conf:

; autospawn = no

That at least stopped it from continuously respawning and flooding
syslog, until I rebooted, apparently that doesn't apply when it starts
as a daemon at boot time.

> If not, could you reproduce this with a higher log level (e g by
> following https://wiki.ubuntu.com/PulseAudio/Log ) and see if you get
> more information out of this error? Thanks.

Log attached... it died pretty quickly.


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

** Attachment added: "pulseverbose.log"
   
https://bugs.launchpad.net/bugs/1547585/+attachment/4586622/+files/pulseverbose.log

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

Title:
  Pulseaudio stopped working but sound still works at the low level (can
  be controlled with alsamixer)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still works at the low level (can be controlled with alsamixer)

[Jeff Lane]

** Summary changed:

- Pulseaudio stopped working but sound still comes out LOUDLY
+ Pulseaudio stopped working but sound still works at the low level (can be 
controlled with alsamixer)

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

Title:
  Pulseaudio stopped working but sound still works at the low level (can
  be controlled with alsamixer)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still comes out LOUDLY

[Jeff Lane]

Syslog is flooded with this series of messages

Feb 19 11:42:07 galactica pulseaudio[22209]: [pulseaudio] main.c: Source 2 does 
not exist.
Feb 19 11:42:07 galactica pulseaudio[22209]: [pulseaudio] main.c: No sink found 
by this name or index.
Feb 19 11:42:07 galactica pulseaudio[22209]: [pulseaudio] main.c: Failed to 
initialize daemon.
Feb 19 11:42:07 galactica pulseaudio[22206]: [pulseaudio] main.c: Daemon 
startup failed.

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

Title:
  Pulseaudio stopped working but sound still comes out LOUDLY

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still comes out LOUDLY

[Jeff Lane]

This may be related to bug #1547589

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

Title:
  Pulseaudio stopped working but sound still comes out LOUDLY

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still comes out LOUDLY

[Jeff Lane]

I AM able to control sound levels with alsamixer directly, FWIW.

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

Title:
  Pulseaudio stopped working but sound still comes out LOUDLY

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still comes out LOUDLY

[Jeff Lane]

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Critical

** Changed in: pulseaudio (Ubuntu)
   Importance: Critical => High

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

Title:
  Pulseaudio stopped working but sound still comes out LOUDLY

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1547651] [NEW] Network Manager shows no VPNs after reboot

[Jeff Lane]

Public bug reported:

After updating packages, I rebooted the system to load the new libc.  ON
reboot I discovered after login that I was unable to connect any
configured VPNs because NetworkManager showed no VPNs.

I eventually figured out that clicking "Enable Networking" to disable
and re-enable networking caused NetMan to reload and THEN I could see my
VPNs.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.0.4-0ubuntu9
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 19 13:54:07 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-02-11 (8 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
IpRoute:
 default via 192.168.0.1 dev enp2s0  proto static  metric 100 
 10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
 169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown 
 192.168.0.0/24 dev enp2s0  proto kernel  scope link  src 192.168.0.104  metric 
100 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Network Manager shows no VPNs after reboot

Status in network-manager package in Ubuntu:
  New

Bug description:
  After updating packages, I rebooted the system to load the new libc.
  ON reboot I discovered after login that I was unable to connect any
  configured VPNs because NetworkManager showed no VPNs.

  I eventually figured out that clicking "Enable Networking" to disable
  and re-enable networking caused NetMan to reload and THEN I could see
  my VPNs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 13:54:07 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-11 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  IpRoute:
   default via 192.168.0.1 dev enp2s0  proto static  metric 100 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown 
   192.168.0.0/24 dev enp2s0  proto kernel  scope link  src 192.168.0.104  
metric 100 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1547585] [NEW] Pulseaudio stopped working but sound still comes out LOUDLY

[Jeff Lane]

Public bug reported:

Not sure if it was an update or what that broke, but I suddenly have no
ability to control sound.

Sound settings no longer show any output devices and syslog is flooded
with pulseaudio messages.

Haven't tried a reboot, that's next.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
 /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
 /dev/snd/controlC0:  bladernr   2773 F chrome
 /dev/snd/timer:  bladernr   2773 f chrome
CurrentDesktop: Unity
Date: Fri Feb 19 11:10:11 2016
InstallationDate: Installed on 2016-02-11 (7 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z170MX-Gaming 5
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
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.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Z170MX-Gaming 5
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Pulseaudio stopped working but sound still comes out LOUDLY

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1547589] [NEW] rtkit-daemon flooding syslog

[Jeff Lane]

Public bug reported:

rtkit is flooding syslog with the following:

Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for 
user '1000', denying request.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for 
user '1000', denying request.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for 
user '1000', denying request.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for 
user '1000', denying request.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for 
user '1000', denying request.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for 
user '1000', denying request.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for 
user '1000', denying request.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit for 
user '1000', denying request.

This may be related to but #1547585

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: rtkit 0.11-4
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 19 11:42:58 2016
InstallationDate: Installed on 2016-02-11 (7 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
SourcePackage: rtkit
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  rtkit-daemon flooding syslog

Status in rtkit package in Ubuntu:
  New

Bug description:
  rtkit is flooding syslog with the following:

  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.

  This may be related to but #1547585

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rtkit 0.11-4
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:42:58 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: rtkit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still comes out LOUDLY

[Jeff Lane]

Rebooted system and still no audio devices, but I am listening to a
video play RIGHT NOW, despite the fact that pulseaudio thinks I have no
audio devices now.

This was working until I did a dist-upgrade earlier (maybe yesterday or
today).

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

Title:
  Pulseaudio stopped working but sound still comes out LOUDLY

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1545905] [NEW] PyGIWrning messages when running ubuntu-bug

[Jeff Lane]

Public bug reported:

Whenever I run ubuntu-bug on this newly installed and updated Xenial
destktop system, I get the following PyGIWarning messages dumped to
console:

bladernr@critical-maas:~$ ubuntu-bug apport
sys:1: PyGIWarning: Wnck was imported without specifying a version first. Use 
gi.require_version('Wnck', '3.0') before import to ensure that the right 
version gets loaded.
sys:1: PyGIWarning: GdkX11 was imported without specifying a version first. Use 
gi.require_version('GdkX11', '3.0') before import to ensure that the right 
version gets loaded.

These should be cleaned up, it looks bad when your bug reporting tool
has bugs like this.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apport 2.20-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
ApportLog:
 
ApportVersion: 2.20-0ubuntu2
Architecture: amd64
CrashReports: 640:108:116:1558842:2016-02-13 15:22:29.722635241 
-0500:2016-02-13 15:22:27.726586970 
-0500:/var/crash/_usr_lib_unity-settings-daemon_unity-settings-daemon.108.crash
CurrentDesktop: Unity
Date: Mon Feb 15 21:05:35 2016
InstallationDate: Installed on 2016-02-12 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  PyGIWrning messages when running ubuntu-bug

Status in apport package in Ubuntu:
  New

Bug description:
  Whenever I run ubuntu-bug on this newly installed and updated Xenial
  destktop system, I get the following PyGIWarning messages dumped to
  console:

  bladernr@critical-maas:~$ ubuntu-bug apport
  sys:1: PyGIWarning: Wnck was imported without specifying a version first. Use 
gi.require_version('Wnck', '3.0') before import to ensure that the right 
version gets loaded.
  sys:1: PyGIWarning: GdkX11 was imported without specifying a version first. 
Use gi.require_version('GdkX11', '3.0') before import to ensure that the right 
version gets loaded.

  These should be cleaned up, it looks bad when your bug reporting tool
  has bugs like this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20-0ubuntu2
  Architecture: amd64
  CrashReports: 640:108:116:1558842:2016-02-13 15:22:29.722635241 
-0500:2016-02-13 15:22:27.726586970 
-0500:/var/crash/_usr_lib_unity-settings-daemon_unity-settings-daemon.108.crash
  CurrentDesktop: Unity
  Date: Mon Feb 15 21:05:35 2016
  InstallationDate: Installed on 2016-02-12 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1544747] Re: Strange device names for USB NICs

[Jeff Lane]

Thanks for that explanation Pitti!  THat makes sense now that I've read
the thread.

I wouldn't suggest making changes here for the sake of convenience, I
also admit that I am a special corner case in this matter.

Would it be a safe assumption that if I can decipher how to write a udev
rule for network devices, I should be able to rename them myself?  I
think, knowing what you described above, that would be fine since this
is intended behaviour.

It just caught me off guard as this is the first time running anything
but Trusty on this hardware and the only time I generally run an interim
release is in VMs or Cloud instances which almost always only have one
network device anyway.

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

Title:
  Strange device names for USB NICs

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Fresh install of Xenial on an intel NUC with 1 onboard GigE and one
  USB GigE NIC.

  I was setting up networking for MAAS and discovered that the device
  names were ridiculous:

  bladernr@critical-maas:/etc/udev$ ifconfig |grep HWaddr
  eno1  Link encap:Ethernet  HWaddr ec:a8:6b:fb:9f:66  
  enx8cae4cff4099 Link encap:Ethernet  HWaddr 8c:ae:4c:ff:40:99  

  In the previous Trusty install on this NUC with the same USB dongle,
  they were named eth0 and em1.  The predictable standard device names.

  Looking at udevadm:
  P: /devices/pci:00/:00:19.0/net/eno1
  E: DEVPATH=/devices/pci:00/:00:19.0/net/eno1
  E: ID_BUS=pci
  E: ID_MM_CANDIDATE=1
  E: ID_MODEL_FROM_DATABASE=82579LM Gigabit Network Connection
  E: ID_MODEL_ID=0x1502
  E: ID_NET_DRIVER=e1000e
  E: ID_NET_LABEL_ONBOARD=en L1U1
  E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
  E: ID_NET_NAME_MAC=enxeca86bfb9f66
  E: ID_NET_NAME_ONBOARD=eno1
  E: ID_NET_NAME_PATH=enp0s25
  E: ID_OUI_FROM_DATABASE=ELITEGROUP COMPUTER SYSTEMS CO., LTD.
  E: ID_PATH=pci-:00:19.0
  E: ID_PATH_TAG=pci-_00_19_0
  E: ID_PCI_CLASS_FROM_DATABASE=Network controller
  E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
  E: ID_VENDOR_FROM_DATABASE=Intel Corporation
  E: ID_VENDOR_ID=0x8086
  E: IFINDEX=2
  E: INTERFACE=eno1
  E: SUBSYSTEM=net
  E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eno1
  E: TAGS=:systemd:
  E: USEC_INITIALIZED=5400250

  P: 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099
  E: 
DEVPATH=/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099
  E: ID_BUS=usb
  E: ID_MM_CANDIDATE=1
  E: ID_MODEL=AX88178
  E: ID_MODEL_ENC=AX88178\x20
  E: ID_MODEL_FROM_DATABASE=AX88178
  E: ID_MODEL_ID=1780
  E: ID_NET_DRIVER=asix
  E: ID_NET_LINK_FILE=/lib/systemd/network/90-mac-for-usb.link
  E: ID_NET_NAME=enx8cae4cff4099
  E: ID_NET_NAME_MAC=enx8cae4cff4099
  E: ID_NET_NAME_PATH=enp0s29u1u5
  E: ID_OUI_FROM_DATABASE=Plugable Technologies
  E: ID_PATH=pci-:00:1d.0-usb-0:1.5:1.0
  E: ID_PATH_TAG=pci-_00_1d_0-usb-0_1_5_1_0
  E: ID_REVISION=0001
  E: ID_SERIAL=ASIX_Elec._Corp._AX88178_02
  E: ID_SERIAL_SHORT=02
  E: ID_TYPE=generic
  E: ID_USB_CLASS_FROM_DATABASE=Vendor Specific Class
  E: ID_USB_DRIVER=asix
  E: ID_USB_INTERFACES=:00:
  E: ID_USB_INTERFACE_NUM=00
  E: ID_USB_SUBCLASS_FROM_DATABASE=Vendor Specific Subclass
  E: ID_VENDOR=ASIX_Elec._Corp.
  E: ID_VENDOR_ENC=ASIX\x20Elec.\x20Corp.
  E: ID_VENDOR_FROM_DATABASE=ASIX Electronics Corp.
  E: ID_VENDOR_ID=0b95
  E: IFINDEX=3
  E: INTERFACE=enx8cae4cff4099
  E: SUBSYSTEM=net
  E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enx8cae4cff4099 
/sys/subsystem/net/devices/enx8cae4cff4099
  E: TAGS=:systemd:
  E: USEC_INITIALIZED=8700146

  And finally, looking in /etc/udev:
  bladernr@critical-maas:/etc/udev$ sudo ls -ra /etc/udev/*
  /etc/udev/udev.conf

  /etc/udev/rules.d:
  ..  .

  /etc/udev/hwdb.d:
  ..  .

  There are NO rules at all in udev for persistent names.  Not even some
  samples and defaults.

  Looking at a completely different Xenial system with a single GigE NIC:
  bladernr@galactica:~$ ifconfig
  enp2s0Link encap:Ethernet  HWaddr 40:8d:5c:51:5b:0d  

  P: /devices/pci:00/:00:1b.2/:02:00.0/net/enp2s0
  E: DEVPATH=/devices/pci:00/:00:1b.2/:02:00.0/net/enp2s0
  E: ID_BUS=pci
  E: ID_MM_CANDIDATE=1
  E: ID_MODEL_FROM_DATABASE=Killer E220x Gigabit Ethernet Controller
  E: ID_MODEL_ID=0xe091
  E: ID_NET_DRIVER=alx
  E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
  E: ID_NET_NAME_MAC=enx408d5c515b0d
  E: ID_NET_NAME_PATH=enp2s0
  E: ID_OUI_FROM_DATABASE=GIGA-BYTE TECHNOLOGY CO.,LTD.
  E: ID_PATH=pci-:02:00.0
  E: ID_PATH_TAG=pci-_02_00_0
  E: ID_PCI_CLASS_FROM_DATABASE=Network controller
  E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
  E: ID_VENDOR_FROM_DATABASE=Qualcomm Atheros
  E: ID_VENDOR_ID=0x1969
  E: IFINDEX=2
  E: INTERFACE=enp2s0
  E: SUBSYSTEM=net
  E: 

[Touch-packages] [Bug 1544747] Re: No udev persistent rules in Xenial = strange device names for NICs

[Jeff Lane]

More checking... on Trusty, the file is generated by
/lib/udev/write_net_rules:

bladernr@sulaco:~$ cat /etc/udev/rules.d/70-persistent-net.rules 
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.

And checking my Xenial system (one of them) write_net_rules does not exist:
bladernr@galactica:/etc/udev/rules.d$ ls /lib/udev
ata_id hplj1000   hpljP1008 iphone-set-info  scsi_id
cdrom_id   hplj1005   hpljP1505 ipod-set-info
udev-add-printer
collecthplj1018   hpljP1505nmtd_probe
udev-configure-printer
console-setup-tty  hplj1020   hwclock-set   mtp-probe
usb_modeswitch
hdparm hpljP1005  hwdb.bin  pcmcia-check-broken-cis  v4l_id
hid2hcihpljP1006  hwdb.dpcmcia-socket-startup
hotplug.functions  hpljP1007  ifupdown-hotplug  rules.d


Now, comparing the packages installed in the two that include udev in the name:

Trusty:
bladernr@sulaco:~$ dpkg -l |grep udev|awk '{print $2 "   " $3}'
gir1.2-gudev-1.0   1:204-5ubuntu20.15
libgudev-1.0-0:amd64   1:204-5ubuntu20.15
libgudev-1.0-0:i386   1:175-0ubuntu9
libudev0:amd64   175-0ubuntu13
libudev0:i386   175-0ubuntu13
libudev1:amd64   204-5ubuntu20.15
libudev1:i386   204-5ubuntu20.15
python3-pyudev   0.16.1-2build1
system-config-printer-udev   1.4.3+20140219-0ubuntu2.6
udev   204-5ubuntu20.15


Xenial:
bladernr@galactica:/etc/udev/rules.d$ dpkg -l |grep udev |awk '{print $2 "   " 
$3}'
gir1.2-gudev-1.0:amd64   1:230-2
libgudev-1.0-0:amd64   1:230-2
libudev1:amd64   228-6ubuntu1
system-config-printer-udev   1.5.7+20150819-0ubuntu5
udev   228-6ubuntu1

the manpage for udev in Xenial says:
RULES FILES
   The udev rules are read from the files located in the system rules 
directory
   /lib/udev/rules.d, the volatile runtime directory /run/udev/rules.d and 
the local
   administration directory /etc/udev/rules.d. All rules files are 
collectively sorted and

SO looking at /lib/udev/rules.d for Trusty:
bladernr@sulaco:~$ ls /lib/udev/rules.d/ |grep net
40-bridge-network-interface.rules
40-vlan-network-interface.rules
75-net-description.rules
75-persistent-net-generator.rules
77-mm-huawei-net-port-types.rules

and Xenial:
bladernr@galactica:/etc/udev/rules.d$ ls /lib/udev/rules.d/ |grep net
75-net-description.rules
77-mm-huawei-net-port-types.rules
80-net-setup-link.rules

Xenial is missing one. If this is intentional, how does one go about
setting persistent network names?

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

Title:
  No udev persistent rules in Xenial = strange device names for NICs

Status in systemd package in Ubuntu:
  New

Bug description:
  Fresh install of Xenial on an intel NUC with 1 onboard GigE and one
  USB GigE NIC.

  I was setting up networking for MAAS and discovered that the device
  names were ridiculous:

  bladernr@critical-maas:/etc/udev$ ifconfig |grep HWaddr
  eno1  Link encap:Ethernet  HWaddr ec:a8:6b:fb:9f:66  
  enx8cae4cff4099 Link encap:Ethernet  HWaddr 8c:ae:4c:ff:40:99  

  In the previous Trusty install on this NUC with the same USB dongle,
  they were named eth0 and em1.  The predictable standard device names.

  Looking at udevadm:
  P: /devices/pci:00/:00:19.0/net/eno1
  E: DEVPATH=/devices/pci:00/:00:19.0/net/eno1
  E: ID_BUS=pci
  E: ID_MM_CANDIDATE=1
  E: ID_MODEL_FROM_DATABASE=82579LM Gigabit Network Connection
  E: ID_MODEL_ID=0x1502
  E: ID_NET_DRIVER=e1000e
  E: ID_NET_LABEL_ONBOARD=en L1U1
  E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
  E: ID_NET_NAME_MAC=enxeca86bfb9f66
  E: ID_NET_NAME_ONBOARD=eno1
  E: ID_NET_NAME_PATH=enp0s25
  E: ID_OUI_FROM_DATABASE=ELITEGROUP COMPUTER SYSTEMS CO., LTD.
  E: ID_PATH=pci-:00:19.0
  E: ID_PATH_TAG=pci-_00_19_0
  E: ID_PCI_CLASS_FROM_DATABASE=Network controller
  E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
  E: ID_VENDOR_FROM_DATABASE=Intel Corporation
  E: ID_VENDOR_ID=0x8086
  E: IFINDEX=2
  E: INTERFACE=eno1
  E: SUBSYSTEM=net
  E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eno1
  E: TAGS=:systemd:
  E: USEC_INITIALIZED=5400250

  P: 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099
  E: 
DEVPATH=/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099
  E: ID_BUS=usb
  E: ID_MM_CANDIDATE=1
  E: ID_MODEL=AX88178
  E: ID_MODEL_ENC=AX88178\x20
  E: ID_MODEL_FROM_DATABASE=AX88178
  E: ID_MODEL_ID=1780
  E: ID_NET_DRIVER=asix
  E: ID_NET_LINK_FILE=/lib/systemd/network/90-mac-for-usb.link
  E: ID_NET_NAME=enx8cae4cff4099
  E: ID_NET_NAME_MAC=enx8cae4cff4099
  E: ID_NET_NAME_PATH=enp0s29u1u5
  E: ID_OUI_FROM_DATABASE=Plugable Technologies
  E: ID_PATH=pci-:00:1d.0-usb-0:1.5:1.0
  E: 

[Touch-packages] [Bug 1544747] [NEW] No udev persistent rules in Xenial = strange device names for NICs

[Jeff Lane]

Public bug reported:

Fresh install of Xenial on an intel NUC with 1 onboard GigE and one USB
GigE NIC.

I was setting up networking for MAAS and discovered that the device
names were ridiculous:

bladernr@critical-maas:/etc/udev$ ifconfig |grep HWaddr
eno1  Link encap:Ethernet  HWaddr ec:a8:6b:fb:9f:66  
enx8cae4cff4099 Link encap:Ethernet  HWaddr 8c:ae:4c:ff:40:99  

In the previous Trusty install on this NUC with the same USB dongle,
they were named eth0 and em1.  The predictable standard device names.

Looking at udevadm:
P: /devices/pci:00/:00:19.0/net/eno1
E: DEVPATH=/devices/pci:00/:00:19.0/net/eno1
E: ID_BUS=pci
E: ID_MM_CANDIDATE=1
E: ID_MODEL_FROM_DATABASE=82579LM Gigabit Network Connection
E: ID_MODEL_ID=0x1502
E: ID_NET_DRIVER=e1000e
E: ID_NET_LABEL_ONBOARD=en L1U1
E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
E: ID_NET_NAME_MAC=enxeca86bfb9f66
E: ID_NET_NAME_ONBOARD=eno1
E: ID_NET_NAME_PATH=enp0s25
E: ID_OUI_FROM_DATABASE=ELITEGROUP COMPUTER SYSTEMS CO., LTD.
E: ID_PATH=pci-:00:19.0
E: ID_PATH_TAG=pci-_00_19_0
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
E: ID_VENDOR_FROM_DATABASE=Intel Corporation
E: ID_VENDOR_ID=0x8086
E: IFINDEX=2
E: INTERFACE=eno1
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eno1
E: TAGS=:systemd:
E: USEC_INITIALIZED=5400250

P: /devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099
E: 
DEVPATH=/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099
E: ID_BUS=usb
E: ID_MM_CANDIDATE=1
E: ID_MODEL=AX88178
E: ID_MODEL_ENC=AX88178\x20
E: ID_MODEL_FROM_DATABASE=AX88178
E: ID_MODEL_ID=1780
E: ID_NET_DRIVER=asix
E: ID_NET_LINK_FILE=/lib/systemd/network/90-mac-for-usb.link
E: ID_NET_NAME=enx8cae4cff4099
E: ID_NET_NAME_MAC=enx8cae4cff4099
E: ID_NET_NAME_PATH=enp0s29u1u5
E: ID_OUI_FROM_DATABASE=Plugable Technologies
E: ID_PATH=pci-:00:1d.0-usb-0:1.5:1.0
E: ID_PATH_TAG=pci-_00_1d_0-usb-0_1_5_1_0
E: ID_REVISION=0001
E: ID_SERIAL=ASIX_Elec._Corp._AX88178_02
E: ID_SERIAL_SHORT=02
E: ID_TYPE=generic
E: ID_USB_CLASS_FROM_DATABASE=Vendor Specific Class
E: ID_USB_DRIVER=asix
E: ID_USB_INTERFACES=:00:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_SUBCLASS_FROM_DATABASE=Vendor Specific Subclass
E: ID_VENDOR=ASIX_Elec._Corp.
E: ID_VENDOR_ENC=ASIX\x20Elec.\x20Corp.
E: ID_VENDOR_FROM_DATABASE=ASIX Electronics Corp.
E: ID_VENDOR_ID=0b95
E: IFINDEX=3
E: INTERFACE=enx8cae4cff4099
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enx8cae4cff4099 
/sys/subsystem/net/devices/enx8cae4cff4099
E: TAGS=:systemd:
E: USEC_INITIALIZED=8700146

And finally, looking in /etc/udev:
bladernr@critical-maas:/etc/udev$ sudo ls -ra /etc/udev/*
/etc/udev/udev.conf

/etc/udev/rules.d:
..  .

/etc/udev/hwdb.d:
..  .

There are NO rules at all in udev for persistent names.  Not even some
samples and defaults.

Looking at a completely different Xenial system with a single GigE NIC:
bladernr@galactica:~$ ifconfig
enp2s0Link encap:Ethernet  HWaddr 40:8d:5c:51:5b:0d  

P: /devices/pci:00/:00:1b.2/:02:00.0/net/enp2s0
E: DEVPATH=/devices/pci:00/:00:1b.2/:02:00.0/net/enp2s0
E: ID_BUS=pci
E: ID_MM_CANDIDATE=1
E: ID_MODEL_FROM_DATABASE=Killer E220x Gigabit Ethernet Controller
E: ID_MODEL_ID=0xe091
E: ID_NET_DRIVER=alx
E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
E: ID_NET_NAME_MAC=enx408d5c515b0d
E: ID_NET_NAME_PATH=enp2s0
E: ID_OUI_FROM_DATABASE=GIGA-BYTE TECHNOLOGY CO.,LTD.
E: ID_PATH=pci-:02:00.0
E: ID_PATH_TAG=pci-_02_00_0
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
E: ID_VENDOR_FROM_DATABASE=Qualcomm Atheros
E: ID_VENDOR_ID=0x1969
E: IFINDEX=2
E: INTERFACE=enp2s0
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enp2s0
E: TAGS=:systemd:
E: USEC_INITIALIZED=752502

and again, nothing in the udev rules:
bladernr@galactica:~$ ls -a /etc/udev/*
/etc/udev/udev.conf

/etc/udev/hwdb.d:
.  ..

/etc/udev/rules.d:
.  ..

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: udev 228-6ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
Date: Thu Feb 11 16:36:35 2016
InstallationDate: Installed on 2016-02-10 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic.efi.signed 
root=UUID=b53bf9e5-5cab-4ebd-98cc-a07ddffe53af ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/03/2014
dmi.bios.vendor: Intel Corp.
dmi.bios.version: RKPPT10H.86A.0032.2014.0303.1322
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: D53427RKE
dmi.board.vendor: Intel Corporation

[Touch-packages] [Bug 1544747] Re: No udev persistent rules in Xenial = strange device names for NICs

[Jeff Lane]

Hrmm... frustratingly, it's been changed automatically at boot somehow:

[5.389985] e1000e :00:19.0 eno1: renamed from eth0
[8.689549] asix 2-1.5:1.0 enx8cae4cff4099: renamed from eth0

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

Title:
  No udev persistent rules in Xenial = strange device names for NICs

Status in systemd package in Ubuntu:
  New

Bug description:
  Fresh install of Xenial on an intel NUC with 1 onboard GigE and one
  USB GigE NIC.

  I was setting up networking for MAAS and discovered that the device
  names were ridiculous:

  bladernr@critical-maas:/etc/udev$ ifconfig |grep HWaddr
  eno1  Link encap:Ethernet  HWaddr ec:a8:6b:fb:9f:66  
  enx8cae4cff4099 Link encap:Ethernet  HWaddr 8c:ae:4c:ff:40:99  

  In the previous Trusty install on this NUC with the same USB dongle,
  they were named eth0 and em1.  The predictable standard device names.

  Looking at udevadm:
  P: /devices/pci:00/:00:19.0/net/eno1
  E: DEVPATH=/devices/pci:00/:00:19.0/net/eno1
  E: ID_BUS=pci
  E: ID_MM_CANDIDATE=1
  E: ID_MODEL_FROM_DATABASE=82579LM Gigabit Network Connection
  E: ID_MODEL_ID=0x1502
  E: ID_NET_DRIVER=e1000e
  E: ID_NET_LABEL_ONBOARD=en L1U1
  E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
  E: ID_NET_NAME_MAC=enxeca86bfb9f66
  E: ID_NET_NAME_ONBOARD=eno1
  E: ID_NET_NAME_PATH=enp0s25
  E: ID_OUI_FROM_DATABASE=ELITEGROUP COMPUTER SYSTEMS CO., LTD.
  E: ID_PATH=pci-:00:19.0
  E: ID_PATH_TAG=pci-_00_19_0
  E: ID_PCI_CLASS_FROM_DATABASE=Network controller
  E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
  E: ID_VENDOR_FROM_DATABASE=Intel Corporation
  E: ID_VENDOR_ID=0x8086
  E: IFINDEX=2
  E: INTERFACE=eno1
  E: SUBSYSTEM=net
  E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eno1
  E: TAGS=:systemd:
  E: USEC_INITIALIZED=5400250

  P: 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099
  E: 
DEVPATH=/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/net/enx8cae4cff4099
  E: ID_BUS=usb
  E: ID_MM_CANDIDATE=1
  E: ID_MODEL=AX88178
  E: ID_MODEL_ENC=AX88178\x20
  E: ID_MODEL_FROM_DATABASE=AX88178
  E: ID_MODEL_ID=1780
  E: ID_NET_DRIVER=asix
  E: ID_NET_LINK_FILE=/lib/systemd/network/90-mac-for-usb.link
  E: ID_NET_NAME=enx8cae4cff4099
  E: ID_NET_NAME_MAC=enx8cae4cff4099
  E: ID_NET_NAME_PATH=enp0s29u1u5
  E: ID_OUI_FROM_DATABASE=Plugable Technologies
  E: ID_PATH=pci-:00:1d.0-usb-0:1.5:1.0
  E: ID_PATH_TAG=pci-_00_1d_0-usb-0_1_5_1_0
  E: ID_REVISION=0001
  E: ID_SERIAL=ASIX_Elec._Corp._AX88178_02
  E: ID_SERIAL_SHORT=02
  E: ID_TYPE=generic
  E: ID_USB_CLASS_FROM_DATABASE=Vendor Specific Class
  E: ID_USB_DRIVER=asix
  E: ID_USB_INTERFACES=:00:
  E: ID_USB_INTERFACE_NUM=00
  E: ID_USB_SUBCLASS_FROM_DATABASE=Vendor Specific Subclass
  E: ID_VENDOR=ASIX_Elec._Corp.
  E: ID_VENDOR_ENC=ASIX\x20Elec.\x20Corp.
  E: ID_VENDOR_FROM_DATABASE=ASIX Electronics Corp.
  E: ID_VENDOR_ID=0b95
  E: IFINDEX=3
  E: INTERFACE=enx8cae4cff4099
  E: SUBSYSTEM=net
  E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enx8cae4cff4099 
/sys/subsystem/net/devices/enx8cae4cff4099
  E: TAGS=:systemd:
  E: USEC_INITIALIZED=8700146

  And finally, looking in /etc/udev:
  bladernr@critical-maas:/etc/udev$ sudo ls -ra /etc/udev/*
  /etc/udev/udev.conf

  /etc/udev/rules.d:
  ..  .

  /etc/udev/hwdb.d:
  ..  .

  There are NO rules at all in udev for persistent names.  Not even some
  samples and defaults.

  Looking at a completely different Xenial system with a single GigE NIC:
  bladernr@galactica:~$ ifconfig
  enp2s0Link encap:Ethernet  HWaddr 40:8d:5c:51:5b:0d  

  P: /devices/pci:00/:00:1b.2/:02:00.0/net/enp2s0
  E: DEVPATH=/devices/pci:00/:00:1b.2/:02:00.0/net/enp2s0
  E: ID_BUS=pci
  E: ID_MM_CANDIDATE=1
  E: ID_MODEL_FROM_DATABASE=Killer E220x Gigabit Ethernet Controller
  E: ID_MODEL_ID=0xe091
  E: ID_NET_DRIVER=alx
  E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
  E: ID_NET_NAME_MAC=enx408d5c515b0d
  E: ID_NET_NAME_PATH=enp2s0
  E: ID_OUI_FROM_DATABASE=GIGA-BYTE TECHNOLOGY CO.,LTD.
  E: ID_PATH=pci-:02:00.0
  E: ID_PATH_TAG=pci-_02_00_0
  E: ID_PCI_CLASS_FROM_DATABASE=Network controller
  E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
  E: ID_VENDOR_FROM_DATABASE=Qualcomm Atheros
  E: ID_VENDOR_ID=0x1969
  E: IFINDEX=2
  E: INTERFACE=enp2s0
  E: SUBSYSTEM=net
  E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enp2s0
  E: TAGS=:systemd:
  E: USEC_INITIALIZED=752502

  and again, nothing in the udev rules:
  bladernr@galactica:~$ ls -a /etc/udev/*
  /etc/udev/udev.conf

  /etc/udev/hwdb.d:
  .  ..

  /etc/udev/rules.d:
  .  ..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 228-6ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: 

[Touch-packages] [Bug 1540591] [NEW] fontconfig breaks Trusty - Xenial upgrade

[Jeff Lane]

Public bug reported:

Attempting to upgrade a fully updated 14.04.3 system to Xenial using the
do-release-upgrade tool.

The upgrade proceeds until it attempts to install fontconfig.  This
fails and causes a cascading set of failures for 160+ more packages
resulting in a system that boots, and has console access, but no Unity,
and other things that either fail to work or only work halfway.

Attempts after the failed upgrade to fix the issues via "apt-get -f
install" fail with the same errors as seen during the upgrade.

Here's the apt term log showing the errors, starting with fontconfig:

http://paste.ubuntu.com/14852379/

And here's the contents of fontconfig.log as suggested by trying to
manually install fontconfig vai "apt-get install fontconfig"

/usr/share/fonts: caching, new cache contents: 0 fonts, 4 dirs
/usr/share/fonts/X11: caching, new cache contents: 0 fonts, 4 dirs
/usr/share/fonts/X11/Type1: caching, new cache contents: 9 fonts, 0 dirs
/usr/share/fonts/X11/encodings: caching, new cache contents: 0 fonts, 1 dirs
/usr/share/fonts/X11/encodings/large: caching, new cache contents: 0 fonts, 0 
dirs
/usr/share/fonts/X11/misc: caching, new cache contents: 59 fonts, 0 dirs
/usr/share/fonts/X11/util: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap: caching, new cache contents: 0 fonts, 5 dirs
/usr/share/fonts/cmap/adobe-cns1: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap/adobe-gb1: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap/adobe-japan1: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap/adobe-japan2: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/cmap/adobe-korea1: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/truetype: caching, new cache contents: 1 fonts, 19 dirs
/usr/share/fonts/truetype/abyssinica: caching, new cache contents: 1 fonts, 0 
dirs
/usr/share/fonts/truetype/dejavu: caching, new cache contents: 6 fonts, 0 dirs
/usr/share/fonts/truetype/droid: caching, new cache contents: 18 fonts, 0 dirs
/usr/share/fonts/truetype/freefont: caching, new cache contents: 12 fonts, 0 
dirs
/usr/share/fonts/truetype/kacst: caching, new cache contents: 15 fonts, 0 dirs
/usr/share/fonts/truetype/kacst-one: caching, new cache contents: 2 fonts, 0 
dirs
/usr/share/fonts/truetype/lao: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/liberation: caching, new cache contents: 16 fonts, 0 
dirs
/usr/share/fonts/truetype/nanum: caching, new cache contents: 6 fonts, 0 dirs
/usr/share/fonts/truetype/openoffice: caching, new cache contents: 1 fonts, 0 
dirs
/usr/share/fonts/truetype/padauk: caching, new cache contents: 4 fonts, 0 dirs
/usr/share/fonts/truetype/sinhala: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/truetype/takao-gothic: caching, new cache contents: 1 fonts, 0 
dirs
/usr/share/fonts/truetype/tibetan-machine: caching, new cache contents: 1 
fonts, 0 dirs
/usr/share/fonts/truetype/tlwg: caching, new cache contents: 54 fonts, 0 dirs
/usr/share/fonts/truetype/ttf-indic-fonts-core: caching, new cache contents: 17 
fonts, 0 dirs
/usr/share/fonts/truetype/ttf-khmeros-core: caching, new cache contents: 2 
fonts, 0 dirs
/usr/share/fonts/truetype/ttf-punjabi-fonts: caching, new cache contents: 2 
fonts, 0 dirs
/usr/share/fonts/truetype/ubuntu-font-family: caching, new cache contents: 13 
fonts, 0 dirs
/usr/share/fonts/type1: caching, new cache contents: 0 fonts, 2 dirs
/usr/share/fonts/type1/gsfonts: caching, new cache contents: 35 fonts, 0 dirs
/usr/share/fonts/type1/mathml: caching, new cache contents: 1 fonts, 0 dirs
/usr/local/share/fonts: caching, new cache contents: 0 fonts, 0 dirs
/.local/share/fonts: skipping, no such directory
Re-scanning /usr/share/fonts: fc-cache: symbol lookup error: fc-cache: 
undefined symbol: FcDirCacheRescan

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

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

Title:
  fontconfig breaks Trusty - Xenial upgrade

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Attempting to upgrade a fully updated 14.04.3 system to Xenial using
  the do-release-upgrade tool.

  The upgrade proceeds until it attempts to install fontconfig.  This
  fails and causes a cascading set of failures for 160+ more packages
  resulting in a system that boots, and has console access, but no
  Unity, and other things that either fail to work or only work halfway.

  Attempts after the failed upgrade to fix the issues via "apt-get -f
  install" fail with the same errors as seen during the upgrade.

  Here's the apt term log showing the errors, starting with fontconfig:

  http://paste.ubuntu.com/14852379/

  And here's the contents of fontconfig.log as suggested by trying to
  manually install fontconfig vai "apt-get install fontconfig"

  

Re: [Touch-packages] [Bug 1514960] Re: lxc-test-checkpoint-restore fails with no explanation why

[Jeff Lane]

Hi,

Not sure this is still an issue, Stephane informed me that those tests
are not meant to be run stand alone and could fail in spectacular ways
when run outside of autopkgtest.

if this is not the case, let me know and when I'm home next week,
I'll dig into this further... otherwise, you can mark this as invalid.

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

Title:
  lxc-test-checkpoint-restore fails with no explanation why

Status in lxc package in Ubuntu:
  New

Bug description:
  Ran the ste lxc-test-checkpoint-restore and that failed, but there is
  no explanation in the output as to why it failed.  All the output I
  was able to create says it created the container fine, but then just
  failed for some reason:

  I: Configuring libsemanage1:amd64...
  I: Configuring libacl1:amd64...
  I: Configuring makedev...
  I: Configuring bsdutils...
  I: Configuring coreutils...
  I: Configuring tar...
  I: Configuring dpkg...
  I: Configuring sed...
  I: Configuring perl-base...
  I: Configuring grep...
  I: Configuring debconf...
  I: Configuring tzdata...
  I: Configuring gzip...
  I: Configuring dash...
  I: Configuring sysv-rc...
  I: Configuring libpam0g:amd64...
  I: Configuring libpam-modules-bin...
  I: Configuring bash...
  I: Configuring libpam-modules:amd64...
  I: Configuring libpam-runtime...
  I: Configuring passwd...
  I: Configuring login...
  I: Configuring adduser...
  I: Configuring libuuid1:amd64...
  I: Configuring libblkid1:amd64...
  I: Configuring libmount1:amd64...
  I: Configuring libcryptsetup4:amd64...
  I: Configuring mount...
  I: Configuring libfdisk1:amd64...
  I: Configuring initscripts...
  I: Configuring util-linux...
  I: Configuring e2fsprogs...
  I: Configuring procps...
  I: Configuring udev...
  I: Configuring systemd...
  I: Configuring dmsetup...
  I: Configuring systemd-sysv...
  I: Configuring init...
  I: Configuring libc-bin...
  I: Unpacking the base system...
  I: Unpacking apt...
  I: Unpacking apt-utils...
  I: Unpacking busybox-initramfs...
  I: Unpacking bzip2...
  I: Unpacking console-setup...
  I: Unpacking console-setup-linux...
  I: Unpacking cpio...
  I: Unpacking cron...
  I: Unpacking debconf-i18n...
  I: Unpacking dh-python...
  I: Unpacking eject...
  I: Unpacking file...
  I: Unpacking gnupg...
  I: Unpacking gpgv...
  I: Unpacking init-system-helpers...
  I: Unpacking initramfs-tools...
  I: Unpacking initramfs-tools-bin...
  I: Unpacking iputils-ping...
  I: Unpacking isc-dhcp-client...
  I: Unpacking isc-dhcp-common...
  I: Unpacking kbd...
  I: Unpacking keyboard-configuration...
  I: Unpacking klibc-utils...
  I: Unpacking kmod...
  I: Unpacking language-pack-en...
  I: Unpacking language-pack-en-base...
  I: Unpacking less...
  I: Unpacking libalgorithm-c3-perl...
  I: Unpacking libapt-inst1.7:amd64...
  I: Unpacking libapt-pkg4.16:amd64...
  I: Unpacking libarchive-extract-perl...
  I: Unpacking libatm1:amd64...
  I: Unpacking libb-hooks-endofscope-perl...
  I: Unpacking libb-hooks-op-check-perl...
  I: Unpacking libbareword-filehandles-perl...
  I: Unpacking libbsd0:amd64...
  I: Unpacking libcgi-fast-perl...
  I: Unpacking libcgi-pm-perl...
  I: Unpacking libck-connector0:amd64...
  I: Unpacking libclass-c3-perl...
  I: Unpacking libclass-c3-xs-perl...
  I: Unpacking libclass-method-modifiers-perl...
  I: Unpacking libclass-xsaccessor-perl...
  I: Unpacking libcpan-changes-perl...
  I: Unpacking libcpan-meta-perl...
  I: Unpacking libdata-optlist-perl...
  I: Unpacking libdata-perl-perl...
  I: Unpacking libdata-section-perl...
  I: Unpacking libdbus-1-3:amd64...
  I: Unpacking libdevel-caller-perl...
  I: Unpacking libdevel-globaldestruction-perl...
  I: Unpacking libdevel-lexalias-perl...
  I: Unpacking libdns-export100...
  I: Unpacking libdpkg-perl...
  I: Unpacking libedit2:amd64...
  I: Unpacking libencode-locale-perl...
  I: Unpacking libestr0...
  I: Unpacking libexporter-tiny-perl...
  I: Unpacking libfcgi-perl...
  I: Unpacking libffi6:amd64...
  I: Unpacking libfile-fcntllock-perl...
  I: Unpacking libfile-slurp-perl...
  I: Unpacking libfribidi0:amd64...
  I: Unpacking libgdbm3:amd64...
  I: Unpacking libgetopt-long-descriptive-perl...
  I: Unpacking libgmp10:amd64...
  I: Unpacking libgnutls-deb0-28:amd64...
  I: Unpacking libgnutls-openssl27:amd64...
  I: Unpacking libgpm2:amd64...
  I: Unpacking libgssapi-krb5-2:amd64...
  I: Unpacking libhogweed4:amd64...
  I: Unpacking libhtml-parser-perl...
  I: Unpacking libhtml-tagset-perl...
  I: Unpacking libhttp-date-perl...
  I: Unpacking libhttp-message-perl...
  I: Unpacking libimport-into-perl...
  I: Unpacking libindirect-perl...
  I: Unpacking libio-html-perl...
  I: Unpacking libio-stringy-perl...
  I: Unpacking libirs-export91...
  I: Unpacking libisc-export95...
  I: Unpacking libisccfg-export90...
  I: Unpacking libjson-c2:amd64...
  I: 

[Touch-packages] [Bug 1515354] [NEW] netman icon does not show VPN status when VPN connected automatically at boot time

[Jeff Lane]

Public bug reported:

I have VPNs configured in Network Manager, one of which is a default
work VPN.  That VPN is configured to connect whenever the network
connection is active on my desktop, thus every time I reboot, the
connection for eth0 is active and the VPN connects automatically.

I've noticed, however, that the NM icon in the tray does not show this
connected status when the automatic connection is made.

Ordinarily, if I manually connect to a VPN, the status icon changes from
two arrows (this is a wired connection) to two arrows with a padlock
indicating a secured VPN connection.

When I boot this system and the VPN connection is established
automatically, however, the icon does not display the padlock, BUT if
you look at NM/VPN Connections/ you can clearly see the connection
marked as active by the check mark next to it.

If I boot the machine and the NM icon is in this state, I can manually
shut down and restart the VPN link and the icon changes to show the VPN
connection as it should.

The screen shot attached shows the icon after a boot, as well as the VPN
connections list with the currently active VPN highlighted by the
checkmark.

Additionally, If I manually disconnect the wired connection and
reconnect it, again, the icon shows the secure established VPN
connection.


Expected Behaviour:

The NM status icon should ALWAYS show the padlock when a VPN connection
is made, regardless of whether it is automatic or not.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7.1
ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
Uname: Linux 3.13.0-66-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.16
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Nov 11 13:16:05 2015
IfupdownConfig:
 auto lo
 iface lo inet loopback
 
 iface eth1:foo inet dhcp
InstallationDate: Installed on 2012-03-15 (1335 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120307)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: Upgraded to trusty on 2014-04-20 (569 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-07-30T16:31:50.821388
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 eth1   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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


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

** Attachment added: "vpn-status.jpg"
   
https://bugs.launchpad.net/bugs/1515354/+attachment/4517104/+files/vpn-status.jpg

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

Title:
  netman icon does not show VPN status when VPN connected automatically
  at boot time

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have VPNs configured in Network Manager, one of which is a default
  work VPN.  That VPN is configured to connect whenever the network
  connection is active on my desktop, thus every time I reboot, the
  connection for eth0 is active and the VPN connects automatically.

  I've noticed, however, that the NM icon in the tray does not show this
  connected status when the automatic connection is made.

  Ordinarily, if I manually connect to a VPN, the status icon changes
  from two arrows (this is a wired connection) to two arrows with a
  padlock indicating a secured VPN connection.

  When I boot this system and the VPN connection is established
  automatically, however, the icon does not display the padlock, BUT if
  you look at NM/VPN Connections/ you can clearly see the connection
  marked as active by the check mark next to it.

  If I boot the machine and the NM icon is in this state, I can manually
  shut down and restart the VPN link and the icon changes to show the
  VPN connection as it should.

  The screen shot attached shows the icon after a boot, as well as the
  VPN connections list with the currently active VPN highlighted by the
  checkmark.

  Additionally, If I manually disconnect the wired connection and
  reconnect it, again, the icon shows the secure established VPN
  connection.

  
  Expected Behaviour:

  The NM status icon should ALWAYS show the padlock when a VPN
  connection is made, regardless of whether it is automatic or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.1
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: 

[Touch-packages] [Bug 1514950] [NEW] lxc-test-checkpoint-restore can't run because no criu installed

[Jeff Lane]

Public bug reported:

on a default 15.10 installation, I have installed lxc-tests and am
running through them individually.

lxc-test-checkpoint-restore fails to run because the package criu is not
installed

ubuntu@xwing:~$ sudo lxc-test-checkpoint-restore
/usr/bin/lxc-test-checkpoint-restore: 22: /usr/bin/lxc-test-checkpoint-restore: 
criu: not found
SKIP: skipping test because no (or wrong) criu installed.

installing lxc-tests should also install any test dependencies like
criu.

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

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

Title:
  lxc-test-checkpoint-restore can't run because no criu installed

Status in lxc package in Ubuntu:
  New

Bug description:
  on a default 15.10 installation, I have installed lxc-tests and am
  running through them individually.

  lxc-test-checkpoint-restore fails to run because the package criu is
  not installed

  ubuntu@xwing:~$ sudo lxc-test-checkpoint-restore
  /usr/bin/lxc-test-checkpoint-restore: 22: 
/usr/bin/lxc-test-checkpoint-restore: criu: not found
  SKIP: skipping test because no (or wrong) criu installed.

  installing lxc-tests should also install any test dependencies like
  criu.

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

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

[Touch-packages] [Bug 1514960] [NEW] lxc-test-checkpoint-restore fails with no explanation why

[Jeff Lane]

Public bug reported:

Ran the ste lxc-test-checkpoint-restore and that failed, but there is no
explanation in the output as to why it failed.  All the output I was
able to create says it created the container fine, but then just failed
for some reason:

I: Configuring libsemanage1:amd64...
I: Configuring libacl1:amd64...
I: Configuring makedev...
I: Configuring bsdutils...
I: Configuring coreutils...
I: Configuring tar...
I: Configuring dpkg...
I: Configuring sed...
I: Configuring perl-base...
I: Configuring grep...
I: Configuring debconf...
I: Configuring tzdata...
I: Configuring gzip...
I: Configuring dash...
I: Configuring sysv-rc...
I: Configuring libpam0g:amd64...
I: Configuring libpam-modules-bin...
I: Configuring bash...
I: Configuring libpam-modules:amd64...
I: Configuring libpam-runtime...
I: Configuring passwd...
I: Configuring login...
I: Configuring adduser...
I: Configuring libuuid1:amd64...
I: Configuring libblkid1:amd64...
I: Configuring libmount1:amd64...
I: Configuring libcryptsetup4:amd64...
I: Configuring mount...
I: Configuring libfdisk1:amd64...
I: Configuring initscripts...
I: Configuring util-linux...
I: Configuring e2fsprogs...
I: Configuring procps...
I: Configuring udev...
I: Configuring systemd...
I: Configuring dmsetup...
I: Configuring systemd-sysv...
I: Configuring init...
I: Configuring libc-bin...
I: Unpacking the base system...
I: Unpacking apt...
I: Unpacking apt-utils...
I: Unpacking busybox-initramfs...
I: Unpacking bzip2...
I: Unpacking console-setup...
I: Unpacking console-setup-linux...
I: Unpacking cpio...
I: Unpacking cron...
I: Unpacking debconf-i18n...
I: Unpacking dh-python...
I: Unpacking eject...
I: Unpacking file...
I: Unpacking gnupg...
I: Unpacking gpgv...
I: Unpacking init-system-helpers...
I: Unpacking initramfs-tools...
I: Unpacking initramfs-tools-bin...
I: Unpacking iputils-ping...
I: Unpacking isc-dhcp-client...
I: Unpacking isc-dhcp-common...
I: Unpacking kbd...
I: Unpacking keyboard-configuration...
I: Unpacking klibc-utils...
I: Unpacking kmod...
I: Unpacking language-pack-en...
I: Unpacking language-pack-en-base...
I: Unpacking less...
I: Unpacking libalgorithm-c3-perl...
I: Unpacking libapt-inst1.7:amd64...
I: Unpacking libapt-pkg4.16:amd64...
I: Unpacking libarchive-extract-perl...
I: Unpacking libatm1:amd64...
I: Unpacking libb-hooks-endofscope-perl...
I: Unpacking libb-hooks-op-check-perl...
I: Unpacking libbareword-filehandles-perl...
I: Unpacking libbsd0:amd64...
I: Unpacking libcgi-fast-perl...
I: Unpacking libcgi-pm-perl...
I: Unpacking libck-connector0:amd64...
I: Unpacking libclass-c3-perl...
I: Unpacking libclass-c3-xs-perl...
I: Unpacking libclass-method-modifiers-perl...
I: Unpacking libclass-xsaccessor-perl...
I: Unpacking libcpan-changes-perl...
I: Unpacking libcpan-meta-perl...
I: Unpacking libdata-optlist-perl...
I: Unpacking libdata-perl-perl...
I: Unpacking libdata-section-perl...
I: Unpacking libdbus-1-3:amd64...
I: Unpacking libdevel-caller-perl...
I: Unpacking libdevel-globaldestruction-perl...
I: Unpacking libdevel-lexalias-perl...
I: Unpacking libdns-export100...
I: Unpacking libdpkg-perl...
I: Unpacking libedit2:amd64...
I: Unpacking libencode-locale-perl...
I: Unpacking libestr0...
I: Unpacking libexporter-tiny-perl...
I: Unpacking libfcgi-perl...
I: Unpacking libffi6:amd64...
I: Unpacking libfile-fcntllock-perl...
I: Unpacking libfile-slurp-perl...
I: Unpacking libfribidi0:amd64...
I: Unpacking libgdbm3:amd64...
I: Unpacking libgetopt-long-descriptive-perl...
I: Unpacking libgmp10:amd64...
I: Unpacking libgnutls-deb0-28:amd64...
I: Unpacking libgnutls-openssl27:amd64...
I: Unpacking libgpm2:amd64...
I: Unpacking libgssapi-krb5-2:amd64...
I: Unpacking libhogweed4:amd64...
I: Unpacking libhtml-parser-perl...
I: Unpacking libhtml-tagset-perl...
I: Unpacking libhttp-date-perl...
I: Unpacking libhttp-message-perl...
I: Unpacking libimport-into-perl...
I: Unpacking libindirect-perl...
I: Unpacking libio-html-perl...
I: Unpacking libio-stringy-perl...
I: Unpacking libirs-export91...
I: Unpacking libisc-export95...
I: Unpacking libisccfg-export90...
I: Unpacking libjson-c2:amd64...
I: Unpacking libk5crypto3:amd64...
I: Unpacking libkeyutils1:amd64...
I: Unpacking libklibc...
I: Unpacking libkrb5-3:amd64...
I: Unpacking libkrb5support0:amd64...
I: Unpacking liblexical-sealrequirehints-perl...
I: Unpacking liblist-moreutils-perl...
I: Unpacking liblocale-gettext-perl...
I: Unpacking liblog-message-perl...
I: Unpacking liblog-message-simple-perl...
I: Unpacking liblwp-mediatypes-perl...
I: Unpacking libmagic1:amd64...
I: Unpacking libmodule-build-perl...
I: Unpacking libmodule-implementation-perl...
I: Unpacking libmodule-pluggable-perl...
I: Unpacking libmodule-runtime-perl...
I: Unpacking libmodule-signature-perl...
I: Unpacking libmoo-perl...
I: Unpacking libmoox-handlesvia-perl...
I: Unpacking libmpdec2:amd64...
I: Unpacking libmro-compat-perl...
I: Unpacking libmultidimensional-perl...
I: Unpacking 

[Touch-packages] [Bug 1514961] [NEW] lxc-test-checkpoint-restore doesn't clean up after itself and I am unable to re-run it

[Jeff Lane]

Public bug reported:

I ran lxc-test-checkpoint-restore and it failed.  So I decided to try
one additional attempt to verify the failure.  However now I am unable
to re-run the test because apparently the container already exists
(previous test did not clean up after itself), however, lxc list does
not show any running containers...

ubuntu@xwing:~$ lxc list
+--+---+--+--+---+---+
| NAME | STATE | IPV4 | IPV6 | EPHEMERAL | SNAPSHOTS |
+--+---+--+--+---+---+
+--+---+--+--+---+---+
ubuntu@xwing:~$ sudo lxc-test-checkpoint-restore
Container already exists
Failed creating container
ubuntu@xwing:~$ sudo lxc list
+--+---+--+--+---+---+
| NAME | STATE | IPV4 | IPV6 | EPHEMERAL | SNAPSHOTS |
+--+---+--+--+---+---+
+--+---+--+--+---+---+

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

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

Title:
  lxc-test-checkpoint-restore doesn't clean up after itself and I am
  unable to re-run it

Status in lxc package in Ubuntu:
  New

Bug description:
  I ran lxc-test-checkpoint-restore and it failed.  So I decided to try
  one additional attempt to verify the failure.  However now I am unable
  to re-run the test because apparently the container already exists
  (previous test did not clean up after itself), however, lxc list does
  not show any running containers...

  ubuntu@xwing:~$ lxc list
  +--+---+--+--+---+---+
  | NAME | STATE | IPV4 | IPV6 | EPHEMERAL | SNAPSHOTS |
  +--+---+--+--+---+---+
  +--+---+--+--+---+---+
  ubuntu@xwing:~$ sudo lxc-test-checkpoint-restore
  Container already exists
  Failed creating container
  ubuntu@xwing:~$ sudo lxc list
  +--+---+--+--+---+---+
  | NAME | STATE | IPV4 | IPV6 | EPHEMERAL | SNAPSHOTS |
  +--+---+--+--+---+---+
  +--+---+--+--+---+---+

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

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

[Touch-packages] [Bug 1514942] [NEW] lxc-tests no runtime help (no man page, no --help, etc) for any of the lxc-tests tools

[Jeff Lane]

Public bug reported:

I'm investigating lxc-tests and have very little idea what they actually
do.  I had hoped to read a man page, or even just pass --help to them to
get some idea of what each is actually doing.

For example, lxc-test-apparmor, I know it does something with apparmor,
but no idea what.  And as they all seem to ignore --help, I have no idea
at all what it is actually doing.

Please document these tests so users actually understand what they are
testing.  Many tests pass, but some fail, and I really don't know why
they're failing, or what they're even doing in the first place to cause
a fail.

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

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

Title:
  lxc-tests no runtime help (no man page, no --help, etc) for any of the
  lxc-tests tools

Status in lxc package in Ubuntu:
  New

Bug description:
  I'm investigating lxc-tests and have very little idea what they
  actually do.  I had hoped to read a man page, or even just pass --help
  to them to get some idea of what each is actually doing.

  For example, lxc-test-apparmor, I know it does something with
  apparmor, but no idea what.  And as they all seem to ignore --help, I
  have no idea at all what it is actually doing.

  Please document these tests so users actually understand what they are
  testing.  Many tests pass, but some fail, and I really don't know why
  they're failing, or what they're even doing in the first place to
  cause a fail.

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

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

[Touch-packages] [Bug 1510091] Re: ubuntu-bug in wily fails to open a bug page when reporting bugs

[Jeff Lane]

Thanks for the pointers... I think this is not an apport bug after all,
but one in xdg?

I have Google Chrome set as the default browser.  When I launch via xdg-
open:

xdg-open http://bugs.launchpad.net

It returns the line "Created new window in existing browser session."

ANd it opens a new chrome window with an empty tab (no URL).

HOWEVER, when I switch the default back to FireFox, xdg-open DOES open a
FF window and loads launchpad.net successfully.

Modifying ui.py as you suggested prints this:
 opening URL: 
https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/e639d1fe-7bf7-11e5-a6ad-002481e7f48a?

and again, this fails to open in google chrome (even using xdg-open
which is what apport does, I just learned) but succeeds in opening in
Firefox.

Maybe this is, instead, a bug in xdg-utils?  in Trusty, apport had no
problems opening bugs in new Google Chrome windows.

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

Title:
  ubuntu-bug in wily fails to open a bug page when reporting bugs

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Fresh install of Wily.  Attempting to file a bug against Unity using
  ubuntu-bug.

  ubuntu-bug prompts me with the expected prompts for a Unity/Gfx bug
  and then says it will open a new window to complete the bug process.

  Normally, this would open a window to a launchpad bug in progress so I
  can update the bug with final details before completing the bug filing
  process.

  Instead, it opens a new browser window with NOTHING in the address
  bar.  Since Ubuntu-Bug does NOT give me the URL in the console where
  it was launched, I have NO way of completing any bugs using ubuntu-
  bug.

  I attempted to file a bug twice with ubuntu-bug and failed both times
  as it does NOT actually open a window that opens the bug's page on
  launchpad:

  bladernr@Rogue1:~/Downloads$ ubuntu-bug unity
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  bladernr@Rogue1:~/Downloads$ Created new window in existing browser session.

  bladernr@Rogue1:~/Downloads$ ubuntu-bug unity
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  bladernr@Rogue1:~/Downloads$ Created new window in existing browser session.

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

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

[Touch-packages] [Bug 1510091] Re: ubuntu-bug in wily fails to open a bug page when reporting bugs

[Jeff Lane]

Accidentally added the Ubuntu apport package... apparently xdg-utils
doesn't track bugs here... now what?

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

** No longer affects: apport (Ubuntu)

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

Title:
  ubuntu-bug in wily fails to open a bug page when reporting bugs

Status in Apport:
  New

Bug description:
  Fresh install of Wily.  Attempting to file a bug against Unity using
  ubuntu-bug.

  ubuntu-bug prompts me with the expected prompts for a Unity/Gfx bug
  and then says it will open a new window to complete the bug process.

  Normally, this would open a window to a launchpad bug in progress so I
  can update the bug with final details before completing the bug filing
  process.

  Instead, it opens a new browser window with NOTHING in the address
  bar.  Since Ubuntu-Bug does NOT give me the URL in the console where
  it was launched, I have NO way of completing any bugs using ubuntu-
  bug.

  I attempted to file a bug twice with ubuntu-bug and failed both times
  as it does NOT actually open a window that opens the bug's page on
  launchpad:

  bladernr@Rogue1:~/Downloads$ ubuntu-bug unity
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  bladernr@Rogue1:~/Downloads$ Created new window in existing browser session.

  bladernr@Rogue1:~/Downloads$ ubuntu-bug unity
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  bladernr@Rogue1:~/Downloads$ Created new window in existing browser session.

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

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

[Touch-packages] [Bug 1437035] [NEW] FEATURE: apt-get could use a dist-upgrade feature for packages

[Jeff Lane]

Public bug reported:

When you want to update just a specific package, you can do the
following:

apt-get install $PACKAGE

and if $PACKAGE is installed, apt will update it to the latest available
version in the repos.

If you want to update an entire system, you can do:

upgrade to upgrade all installed packages
dist-upgrade to upgrade all installed packages AND install any new dependencies 
that may have been added

It would be really cool if apt could do the same on the individual
package level, e.g.

apt-get package-upgrade $PACKAGE

which would update $PACKAGE and all it's dependencies to the latest
version.

This resolves a couple things:

1: apt install $PACKAGE is not obvious when dealing with packages that
are already installed... why am I installing again, instead of
upgrading?

2:  Some packages don't specify required VERSIONS of their dependencies,
so you can encounter a situation where you do this:

apt-get install $PACKAGE

and find that $PACKAGE no longer works because a dependency was not also
updated due the $PACKAGE's maintainer not specifying a certain version
for the dependencies.

Having a dist-upgrade like feature at the package level would ensure
that when you update an individual package, you also update all it's
dependencies as well, helping to ensure no more broken packages or tools
and making user experience better.

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

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

Title:
  FEATURE: apt-get could use a dist-upgrade feature for packages

Status in apt package in Ubuntu:
  New

Bug description:
  When you want to update just a specific package, you can do the
  following:

  apt-get install $PACKAGE

  and if $PACKAGE is installed, apt will update it to the latest
  available version in the repos.

  If you want to update an entire system, you can do:

  upgrade to upgrade all installed packages
  dist-upgrade to upgrade all installed packages AND install any new 
dependencies that may have been added

  It would be really cool if apt could do the same on the individual
  package level, e.g.

  apt-get package-upgrade $PACKAGE

  which would update $PACKAGE and all it's dependencies to the latest
  version.

  This resolves a couple things:

  1: apt install $PACKAGE is not obvious when dealing with packages that
  are already installed... why am I installing again, instead of
  upgrading?

  2:  Some packages don't specify required VERSIONS of their
  dependencies, so you can encounter a situation where you do this:

  apt-get install $PACKAGE

  and find that $PACKAGE no longer works because a dependency was not
  also updated due the $PACKAGE's maintainer not specifying a certain
  version for the dependencies.

  Having a dist-upgrade like feature at the package level would ensure
  that when you update an individual package, you also update all it's
  dependencies as well, helping to ensure no more broken packages or
  tools and making user experience better.

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

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

[Touch-packages] [Bug 401823] Re: Gdk-WARNING **: XID collision, trouble ahead

[Jeff Lane]

Can someone please close this bug?

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

Title:
  Gdk-WARNING **: XID collision, trouble ahead

Status in Chromium Browser:
  New
Status in The Mozilla Firefox Browser:
  Invalid
Status in GTK+ GUI Toolkit:
  Expired
Status in Modular X11 Libraries:
  Confirmed
Status in “firefox” package in Ubuntu:
  Fix Released
Status in “firefox-3.5” package in Ubuntu:
  Invalid
Status in “gtk+2.0” package in Ubuntu:
  Fix Released
Status in “firefox” source package in Lucid:
  Invalid
Status in “firefox-3.5” source package in Lucid:
  Invalid
Status in “gtk+2.0” source package in Lucid:
  Invalid
Status in “firefox” source package in Karmic:
  Invalid
Status in “firefox-3.5” source package in Karmic:
  Won't Fix
Status in “gtk+2.0” source package in Karmic:
  Fix Released

Bug description:
  karmic testing

  in .xsession-errors: (firefox:24993): Gdk-WARNING **: XID collision, trouble 
ahead
  previously, have had this one: (nautilus:3572):
   GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' 
failed (bug report 401822)

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/401823/+subscriptions

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

[Touch-packages] [Bug 1134069] Re: [HP Envy 4 Sleekbook] external audio jacks are reversed

[Jeff Lane]

Daniel, can you please hand this off?

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

Title:
  [HP Envy 4 Sleekbook] external audio jacks are reversed

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  Looking at the outside of the system, the external audio jacks  are in
  this order:

  Mic ___Headphone ___

  However, on testing, it appears that they are either mislabled, or the
  outputs are reversed internally.  I had to plug the headphones into
  the Mic jack to hear sound, and plug the mic into the headphone jack
  to record sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-25-generic 3.5.0-25.39~precise1
  ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1545 F pulseaudio
   /dev/snd/pcmC0D0c:   ubuntu 1545 F...m pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x5071 irq 48'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:111d76e0,103c1894,00100102 
HDA:80862806,80860101,0010'
 Controls  : 24
 Simple ctrls  : 11
  Date: Wed Feb 27 03:05:29 2013
  HibernationDevice: RESUME=UUID=286b25cc-7928-4406-854e-6c1cae69a6e6
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
  MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic 
root=UUID=0c6af5a9-e287-43f5-8ce6-647a4ae228f2 ro quiet splash initcall_debug 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-25-generic N/A
   linux-backports-modules-3.5.0-25-generic  N/A
   linux-firmware1.79.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: B.38
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1894
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 72.66
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrB.38:bd10/31/2012:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr088810250E102:rvnHewlett-Packard:rn1894:rvr72.66:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dm4 Notebook PC
  dmi.product.version: 088810250E102
  dmi.sys.vendor: Hewlett-Packard

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

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