[Touch-packages] [Bug 1651518] Re: systemd/logind parsing problem: HTX exercisers stopped on error: rc 11, errno 11 from main(): pthread_create

[Luciano Chavez]

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

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

Title:
  systemd/logind parsing problem: HTX exercisers stopped on error: rc
  11, errno 11 from main(): pthread_create

Status in systemd package in Ubuntu:
  New

Bug description:
  == Comment: #1 - Application Cdeadmin  -
  2016-12-19 04:15:10 ==

  Configuration: IBM 8001-22C (S822LC), LSI SAS adapters, SMC 4U90 disk
  drawers, HDD (180) 7.3TB

  Problem: HTX exercisers stopped on error, with HTX log showing "rc 11,
  errno 11 from main(): pthread_create"

  htxubuntu-425

  lpar: busybee.aus.stglabs.ibm.com (root/ lab passwd)

  root@busybee:~# uname -a
  Linux busybee 4.4.0-51-generic #72-Ubuntu SMP Thu Nov 24 18:27:59 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  root@busybee:~# cat /tmp/htxerr

  /dev/sdh  Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdh  Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sdao Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdao Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sddx Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sddx Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sdcz Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdcz Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  /dev/sddp Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sddp Dec 12 23:52:42 2016 err=000b sev=1 hxestorage
  Hardware Exerciser stopped on an error

  No errors logged in syslog after starting HTX:

   State: Open by: asperez on 16 December 2016 10:28:02 
  This error recreated on the smaller 1U Open Power system with the same 
smaller 1-adapter/1-4U90 drawer/90 HDD. There are 2 cables connected to the 
drawer (one to each ESM) that requires multipath enabled. 

  lpar: yellowbee

  root@yellowbee:~# cat /tmp/htxerr

  /dev/sdao Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdak Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdt  Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdaz Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdn  Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdv  Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdaj Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

  /dev/sdal Dec 16 01:14:44 2016 err=000b sev=1 hxestorage
  rc 11, errno 11 from main(): pthread_create

   State: Open by: cde00 on 19 December 2016 02:48:46 

  This defect will go to Linux as even after making the below 2 changes
  in systemd resource limit, errors are seen:

  root@yellowbee:/etc/systemd/logind.conf.d# cat htxlogindcustom.conf
  [Login]
  UserTasksMax=infinity
  root@yellowbee:/etc/systemd/logind.conf.d# cat 
../system.conf.d/htxsystemdcustom.conf
  [Manager]
  DefaultTasksAccounting=yes
  DefaultTasksMax=infinity

  root@yellowbee:/etc/systemd/logind.conf.d#

  logind limit for MaxUserTask as well as systemd limit was made infinite.
  Please look defect SW363655 for more details and the suggestion given earlier 
by Linux team.

  errors are still seen. So, would ask Linux team to take a look and see if 
anything else is causing these
  errors.

  == Comment: #3 - Kevin W. Rudd  - 2016-12-19 17:34:27 ==
  It appears that the version of logind on this system does not support the 
value of "infinity", and is reverting to the default of 12288: 

  # cat /sys/fs/cgroup/pids/user.slice/user-0.slice/pids.max
  12288

  As a workaround until this can be resolved, specify an exact value.
  You can try using the current system thread-max value:

  # cat /proc/sys/kernel/threads-max
  3974272

  /etc/systemd/logind.conf.d/htxlogindcustom.conf:
  [Login]
  UserTasksMax=3974272

  == Comment: #4 - Kevin W. Rudd - 2016-12-20 10:25:09 ==

  Canonical,

  This issue appears to map to the following systemd bug and patch:

  

[Touch-packages] [Bug 1621824] Re: MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start Set console keymap."

[Luciano Chavez]

** Changed in: console-setup (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start
  Set console keymap."

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  == Comment: #1 - Application Cdeadmin <> - 2016-08-23 15:05:14 ==
   State: Open by: knodelk on 23 August 2016 14:00:43 

  Seeing the following error message in the Ubuntu dmesg log following
  IPL to Ubuntu on system with Ubuntu 16.04.1 installed:

  # dmesg -T --level=alert,crit,err
  [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap.

  This appears to be something that can be ignored so manufacturing will
  be ignoring this message until directed otherwise.

  ==> all systemd related messages: 
  # dmesg -T | grep systemd
  [Tue Aug 23 09:20:12 2016] systemd[1]: systemd 229 running in system mode. 
(+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
  [Tue Aug 23 09:20:12 2016] systemd[1]: Detected architecture ppc64-le.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Set hostname to .
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Device-mapper event 
daemon FIFOs.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Forward Password Requests to 
Wall Directory Watch.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on /dev/initctl 
Compatibility Named Pipe.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Encrypted Volumes.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Syslog Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket (/dev/log).
  [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target User and Group Name 
Lookups.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on fsck to fsckd 
communication Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Control Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 metadata daemon 
socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 poll daemon socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice User and Session Slice.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Kernel Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice System Slice.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting POSIX Message Queue File 
System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Slices.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Create list of required 
static device nodes for the current kernel...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Nameserver information 
manager...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Monitoring of LVM2 mirrors, 
snapshots etc. using dmeventd or progress polling...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting RPC Pipe File System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice 
system-serial\x2dgetty.slice.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Read required files in advance.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Load Kernel Modules...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Debug File System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Audit Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Journal Service...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Huge Pages File System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Set up automount Arbitrary Executable 
File Formats File System Automount Point.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Uncomplicated firewall...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Set console keymap...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Debug File System.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted POSIX Message Queue File 
System.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Huge Pages File System.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Create list of required static 
device nodes for the current kernel.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Nameserver information manager.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Uncomplicated firewall.
  [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Main process 
exited, code=exited, status=1/FAILURE
  [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap.
  [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Unit entered 
failed state.
  [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Failed with 
result 'exit-code'.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted RPC Pipe File System.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Load Kernel Modules.
  [Tue Aug 23 09:20:12 2016] 

[Touch-packages] [Bug 1621824] Re: MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start Set console keymap."

[Luciano Chavez]

** Package changed: ubuntu => console-setup (Ubuntu)

** Changed in: console-setup (Ubuntu)
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

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

Title:
  MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start
  Set console keymap."

Status in console-setup package in Ubuntu:
  New

Bug description:
  == Comment: #1 - Application Cdeadmin <> - 2016-08-23 15:05:14 ==
   State: Open by: knodelk on 23 August 2016 14:00:43 

  Seeing the following error message in the Ubuntu dmesg log following
  IPL to Ubuntu on system with Ubuntu 16.04.1 installed:

  # dmesg -T --level=alert,crit,err
  [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap.

  This appears to be something that can be ignored so manufacturing will
  be ignoring this message until directed otherwise.

  ==> all systemd related messages: 
  # dmesg -T | grep systemd
  [Tue Aug 23 09:20:12 2016] systemd[1]: systemd 229 running in system mode. 
(+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
  [Tue Aug 23 09:20:12 2016] systemd[1]: Detected architecture ppc64-le.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Set hostname to .
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Device-mapper event 
daemon FIFOs.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Forward Password Requests to 
Wall Directory Watch.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on /dev/initctl 
Compatibility Named Pipe.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Encrypted Volumes.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Syslog Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket (/dev/log).
  [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target User and Group Name 
Lookups.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on fsck to fsckd 
communication Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Control Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 metadata daemon 
socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 poll daemon socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice User and Session Slice.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Kernel Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice System Slice.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting POSIX Message Queue File 
System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Slices.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Create list of required 
static device nodes for the current kernel...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Nameserver information 
manager...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Monitoring of LVM2 mirrors, 
snapshots etc. using dmeventd or progress polling...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting RPC Pipe File System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice 
system-serial\x2dgetty.slice.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Read required files in advance.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Load Kernel Modules...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Debug File System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Audit Socket.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Journal Service...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Huge Pages File System...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Set up automount Arbitrary Executable 
File Formats File System Automount Point.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Uncomplicated firewall...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Set console keymap...
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Debug File System.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted POSIX Message Queue File 
System.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Huge Pages File System.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Create list of required static 
device nodes for the current kernel.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Nameserver information manager.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Started Uncomplicated firewall.
  [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Main process 
exited, code=exited, status=1/FAILURE
  [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap.
  [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Unit entered 
failed state.
  [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Failed with 
result 'exit-code'.
  [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted RPC Pipe File System.
  [Tue Aug 23 09:20:12 2016] 

[Touch-packages] [Bug 1580922] Re: Upgrade libseccomp from 2.2.3 ->2.3.1

[Luciano Chavez]

** Changed in: libseccomp (Ubuntu)
   Status: New => Invalid

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

Title:
  Upgrade libseccomp from 2.2.3 ->2.3.1

Status in libseccomp package in Ubuntu:
  Invalid

Bug description:
  == Comment: #1 - Heinz-Werner Seeck  - 
2016-05-11 05:09:09 ==
  Please upgrade package libseccomp.
  The new version 2.3.1 is available on github

  https://github.com/seccomp/libseccomp/releases

  == Comment: #2 - Heinz-Werner Seeck  - 
2016-05-11 05:10:59 ==
  ?Version 2.3.0 - February 29, 2016
  ?Added support for the s390 and s390x architectures
  ?Added support for the ppc, ppc64, and ppc64le architectures
  ?Update the internal syscall tables to match the Linux 4.5-rcX releases
  ?Filter generation for both multiplexed and direct socket syscalls on x86
  ?Support for the musl libc implementation
  ?Additions to the API to enable runtime version checking of the library
  ?Enable the use of seccomp() instead of prctl() on supported systems
  ?Added additional tests to the regression test suite

  ?Version 2.3.1 - April 20, 2016 
  ?Fixed a problem with 32-bit x86 socket syscalls on some systems
  ?Fixed problems with ipc syscalls on 32-bit x86
  ?Fixed problems with socket and ipc syscalls on s390 and s390x

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

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

[Touch-packages] [Bug 1389164] Re: Ubuntu 14.10 ppc64le not automatically mounting NFS mounts in /etc/fstab

[Luciano Chavez]

I believe 14.10 is no longer in support. Does this problem persist in
either Trusty or Xenial?

** Changed in: mountall (Ubuntu)
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

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

Title:
  Ubuntu 14.10 ppc64le not automatically mounting NFS mounts in
  /etc/fstab

Status in mountall package in Ubuntu:
  Incomplete

Bug description:
  Problem Description
  
  It seems the remote mounts in my /etc/fstab file are not being automatically 
mounted at bootup with ppc64le Ubuntu 14.10. This leads to some of my upstart 
scripts not running because they require certain mounts being available. I can 
give access to the machine via SSH key or password. Using mount -a or any other 
mount command works just fine after bootup. I don't personally notice a problem 
in logs with mounts.

  The machine is a VM hosted on a Power8 PowerKVM system running:
  # uname -a
  Linux kvm10d724t.rtp.raleigh.ibm.com 3.10.23-1700.pkvm2_1.2.ppc64 #1 SMP Mon 
Jun 2 20:14:25 CDT 2014 ppc64 ppc64 ppc64 GNU/Linux
  # cat /etc/base-release
  IBM_PowerKVM release 2.1.0 build 18 Service (pkvm2_1)

  VM details:
  # uname -a
  Linux cit607 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:24:38 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.10
  DISTRIB_CODENAME=utopic
  DISTRIB_DESCRIPTION="Ubuntu Utopic Unicorn (development branch)"

  If I recall correctly, we installed the 141002 daily build of Utopic
  Unicorn (14.10).

  I have implemented a workaround for now. I updated /etc/fstab to use
  IP addresses instead of names, put "mount -a" as the first non-
  commented line in /etc/init.d/mountnfs.sh and updated the crontab to
  run the jobs I had in the upstart configs. This works until the
  problem is fixed.

  ---uname output---
  Linux cit607 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:24:38 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = ppc64le 
   
  Steps to Reproduce
  =
   Without the workaround implemented and NFS mounts in your /etc/fstab, boot 
up the machine. It should be evident the mount points aren't there with df -h.

  == Comment: #3 - Breno Henrique Leitao  -  ==
  I was able to reproduce this problem.
  NFS is not mounted automatically, but it is when you run 'mount -a'. 
  I also toggled ASYNCMOUNTNFS in /etc/defaults/rcS and no luck.

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

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

[Touch-packages] [Bug 1443653] Re: Ubuntu 15.04 - Failed installation of ubuntu-desktop package (whoopsie package)

[Luciano Chavez]

** Changed in: whoopsie (Ubuntu)
   Status: New => Invalid

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

Title:
  Ubuntu 15.04 - Failed installation of ubuntu-desktop package (whoopsie
  package)

Status in whoopsie package in Ubuntu:
  Invalid

Bug description:
  -- Problem Description --
  When installing the ubuntu-desktop package in Ubuntu 15.04 during the set up 
of a package the following message is displayed and the installation doesn't go 
any further:

  Setting up whoopsie (0.2.47) ...
  Error getting authority: Error initializing authority: Error calling 
StartServi24)yName for org.freedesktop.PolicyKit1: Timeout was reached 
(g-io-error-quark, 2
  Failed to execute operation: Connection timed out

  I am able to reproduce this issue when installing the ubuntu-desktop
  package on top of a fresh install, but in a different test, I tried to
  install only the whoopsie package where the package installation stops
  and I did not see this issue.

  I am attaching below the full log of the apt-get installation.

  The problem is on starting the systemd script. If I stop it, it makes
  progress. There are other systemd initi scripts that are failing
  also...

  > Can you try by switching the init system back to upstart, and re-installing?
  > 
  > See [1]; probably this will do: init=/sbin/upstart
  > 
  > [1]
  > https://lists.ubuntu.com/archives/ubuntu-devel-announce/2015-March/001130.
  > html

  Mauricio, the installation of the packages went properly by adding the
  init=/sbin/upstart to the boot line. I attached the full installation
  log above.

  But when restarting the system, the following message is issued and
  the system doesn't seem to be bootable anymore.

  * Restoring resolver state... 
[ OK ] 
   * Starting uuid generator uuidd [ OK 
] 
   * speech-dispatcher disabled; edit /etc/default/speech-dispatcher
  /lib/init/init-d-script: 12: /etc/rc2.d/S02whoopsie: -c: not found
  basename: missing operand
  Try 'basename --help' for more information.
   * saned disabled; edit /etc/default/saned

  Interesting. It installed, but failed to stop services.
  Hm, it seems that whoopsie thing is broken intermediarily between upstart and 
systemd.

  Trying to get rid of whoopsie may help.
  Do you need an 'Ubuntu error tracker submission' tool? :)

  I'd suggest you to try to remove it.
  If some things depend on it, and are not important, pull them off/ignore 
dependencies, and try again. That might help.

  Nonetheless, it's certainly worth a launchpad bug for Canonical to
  look at.

  Another work-around, much less disruptive, is just ignore the rc
  script failing in the reboot chain. :)

  You can find a symlink for it in /etc/rc{6,0}.d (reboot/shutdown)..
  just renaming it to w/out a leading K should effectively disable it
  from the reboot/shutdown runlevel change chain.. and hopefully that
  will get the issue out of the way for now.

  Ah, the other comment mention it's rc2.d (an startup/single user
  runlevel, IIRC).. you can try the renaming there to, but to w/out a
  leading S.

  IIRC this command should achieve that too:
  $ sudo update-rc.d whoopsie disable

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

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

[Touch-packages] [Bug 1407622] Re: RELRO is not read-only on PowerLE (binutils)

[Luciano Chavez]

** Changed in: binutils (Ubuntu)
   Status: New => Invalid

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

Title:
  RELRO is not read-only on PowerLE (binutils)

Status in binutils package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2015-01-05 
01:29:11 ==
  ---Problem Description---
  RELRO is not read-only on PowerLE (binutils)
   
  Contact Information = pavsu...@in.ibm.com 
   
  ---uname output---
  Linux ubuntu 3.16.0-28-generic #38-Ubuntu SMP Fri Dec 12 17:39:43 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install a Ubuntu 15.04 PPC64 LE ISO as a guest VM on Power KVM host.
  Then try building and executing the below mentioned RELRO test case.

  root@ubuntu:~# cat relro.c
  #include 

  void *const foo = 

  int main (void)
  {
*(void **)  = 
return 0;
  }

  root@ubuntu:~# gcc -Wl,-z,relro relro.c
  root@ubuntu:~# bash checkrelro.sh --file a.out
  a.out - partial RELRO

  root@ubuntu:~# ./a.out
  root@ubuntu:~# echo $?
  0
  (pasess, should segfault)

  The reproducer Looks like GOT is not read-only.

   
  Userspace tool common name: binutils 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: binutils2.25-2ubuntu1

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for pavsu...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - PAVAMAN SUBRAMANIYAM  - 2015-01-05 
01:33:21 ==
  Adding output of readelf -Wa of the relro binary

  root@ubuntu:~# readelf -Wa a.out
  ELF Header:
Magic:   7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
Class: ELF64
Data:  2's complement, little endian
Version:   1 (current)
OS/ABI:UNIX - System V
ABI Version:   0
Type:  EXEC (Executable file)
Machine:   PowerPC64
Version:   0x1
Entry point address:   0x1410
Start of program headers:  64 (bytes into file)
Start of section headers:  6776 (bytes into file)
Flags: 0x2, abiv2
Size of this header:   64 (bytes)
Size of program headers:   56 (bytes)
Number of program headers: 8
Size of section headers:   64 (bytes)
Number of section headers: 29
Section header string table index: 26

  Section Headers:
[Nr] Name  TypeAddress  OffSize   ES 
Flg Lk Inf Al
[ 0]   NULL 00 00 00
  0   0  0
[ 1] .interp   PROGBITS1200 000200 11 00   
A  0   0  1
[ 2] .note.ABI-tag NOTE1214 000214 20 00   
A  0   0  4
[ 3] .note.gnu.build-id NOTE1234 000234 24 00   
A  0   0  4
[ 4] .gnu.hash GNU_HASH1258 000258 1c 00   
A  5   0  8
[ 5] .dynsym   DYNSYM  1278 000278 78 18   
A  6   1  8
[ 6] .dynstr   STRTAB  12f0 0002f0 45 00   
A  0   0  1
[ 7] .gnu.version  VERSYM  1336 000336 0a 02   
A  5   0  2
[ 8] .gnu.version_rVERNEED 1340 000340 20 00   
A  6   1  8
[ 9] .rela.dyn RELA1360 000360 48 18   
A  5   0  8
[10] .rela.plt RELA13a8 0003a8 18 18  
AI  5  23  8
[11] .init PROGBITS13c0 0003c0 3c 00  
AX  0   0  4
[12] .text PROGBITS1400 000400 000384 00  
AX  0   0 32
[13] .fini PROGBITS1784 000784 24 00  
AX  0   0  4
[14] .rodata   PROGBITS17a8 0007a8 24 00   
A  0   0  8
[15] .eh_frame PROGBITS17cc 0007cc 4c 00   
A  0   0  4
[16] .init_array   INIT_ARRAY  10010df0 000df0 08 00  
WA  0   0  8
[17] .fini_array   FINI_ARRAY  10010df8 000df8 08 00  
WA  0   0  8
[18] .jcr  PROGBITS10010e00 000e00 08 00  
WA  0   0  8
[19] .data.rel.ro  PROGBITS10010e08 000e08 08 00  
WA  0   0  8
[20] .dynamic  DYNAMIC 10010e10 000e10 0001f0 10  
WA  6   0  8
[21] .data PROGBITS

[Touch-packages] [Bug 1408589] Re: chfn does not work in chroot environment

[Luciano Chavez]

** Changed in: shadow (Ubuntu)
   Status: New => Invalid

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

Title:
  chfn does not work in chroot environment

Status in shadow package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - Guang Cheng Li  - 2015-01-07 01:51:51 ==
  ---Problem Description---
  chfn does not work in a chroot environment.

  In a chroot environment, the chroot exits with error "chfn: PAM:
  System error" and does not do anything.

  This might be related to 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763391 and 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745082
   
  Contact Information = Guang Cheng Li ligua...@cn.ibm.com, Ralph Bellofatto 
ralph...@us.ibm.com 
   
  ---uname output---
  Linux tulgpu002 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:55:08 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = N/A 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Create a Ubuntu chroot environment, chroot into the directory, then run chfn.

  root@tulgpu002:~# ls
  chfn-error-rootimg
  root@tulgpu002:~# chroot chfn-error-rootimg
  root@tulgpu002:/# ls
  bin   dev  homelibmedia  opt   root  sbin  sys  usr  vmlinux
  boot  etc  initrd.img  lib64  mntproc  run   srv   tmp  var  xcatpost
  root@tulgpu002:/# 
  root@tulgpu002:/# chfn -f 'games user id' games
  chfn: PAM: System error
  root@tulgpu002:/# 

   
  *Additional Instructions for Guang Cheng Li ligua...@cn.ibm.com, Ralph 
Bellofatto ralph...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

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

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

[Touch-packages] [Bug 1337407] Re: Upstart can NOT handle service/job started by others

[Luciano Chavez]

** Changed in: upstart (Ubuntu)
   Status: New => Invalid

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

Title:
  Upstart can NOT handle service/job started by others

Status in upstart package in Ubuntu:
  Invalid

Bug description:
  -- Problem Description --
  Upstart can not see a service/job/process that has been started and running 
by someone else. Old style init.d/systemd fully/partially handle start/stop 
correctly (on other Linux systems without Upstart), no matter who started the 
process.

  Our PMLinux collecting agent "daemon_PMLnx" was designed to start/run
  by root with any means, such as crontab, inittab, service, or even
  command line at a terminal. The program itself will quit immediately
  at the beginning if finds the process already running.

  Generally, we prefer to organize PMLinux as a service, plus create a
  start hook in the crontab to run "daemon_PMLnx" at 3am every day, in
  order to guarantee a restart won't be forgot if someone ever stopped
  the job.

  Here are some command outputs from Ubuntu/Upstart:

  # uname -a
  Linux ubuntu 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:09:21 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux

  # dpkg -l upstart
  Name Version  Architecture  Description
  -===--=-
  ii  upstart  1.12.1-0ubuntu4  ppc64el   event-based init daemon

  # ps -ef | grep -e PMLnx$ -e CRON$
  root 10263   771  0 17:59 ?00:00:00 CRON
  root 10264 10263  0 17:59 ?00:00:00 /bin/sh -c 
/var/perf/pm/bin/daemon_PMLnx (bug!)  
  root 10265 10264  0 17:59 ?00:00:00 /var/perf/pm/bin/daemon_PMLnx

  # start PMLinux
  PMLinux stop/waiting   <--- bad!

  # status PMLinux
  PMLinux stop/waiting   <--- bad!

  # stop PMLinux
  stop: Unknown instance:   <--- bad!

  # kill -2 10265

  # start PMLinux
  PMLinux start/running, process 10562

  # ps -ef | grep -e PMLnx$
  root 10562 1  0 19:49 ?00:00:00 /var/perf/pm/bin/daemon_PMLnx

  # start PMLinux
  start: Job is already running: PMLinux

  # stop PMLinux
  PMLinux stop/waiting

  # stop PMLinux
  stop: Unknown instance:

  # cat /etc/init/PMLinux.conf
  # daemon_PMLnx - Collecting Agent of IBM Performance Management for Power 
Linux (PMLinux)
  #
  # daemon_PMLnx collects PMLinux data at periodic scheduled times
  # working HOME directory - /var/perf/pm

  description "IBM PMLinux collecting daemon"
  author "IBM PMLinux Team, Rochester, USA"

  start on runlevel [2345]
  stop on runlevel [!2345]

  # console output  
  # not works as expected: output to the working terminal (instead of 
system console)
  pre-start script
  unset myErrMSG
  if [ ! -x /var/perf/pm/bin/daemon_PMLnx ]; then
  export myErrMSG='Daemon programs disappeared; please 
re-install ibmPMLinux'
  #   elif ps -C daemon_PMLnx >/dev/null; then
  #   export myErrMSG='PMLinux collecting daemon is already 
running!'
  elif [ ! -L /var/adm/perfmgr ] || [ ! -d /var/adm/perfmgr ]; then
  export myErrMSG='PMLinux was NOT enabled; Please run 
"config.PMLnx" to activate'
  fi
  if [ -n "$myErrMSG" ]; then
  echo -n "`date +'%D %T'` ";  stop;
  echo"`date +'%D %T'` $myErrMSG"; exit 0
  fi
  end script

  post-start script
  if ps -C daemon_PMLnx >/dev/null; then
  echo "`date +'%D %T'` PMLinux collecting daemon running..."
  else
  echo "`date +'%D %T'` FAILED: Could NOT start PMLinux 
collecting daemon!!!"
  fi
  end script

  post-stop script
  echo "`date +'%D %T'` PMLinux collecting daemon stopped."
  end script

  exec /var/perf/pm/bin/daemon_PMLnx

  The attachment is a screenshot to demonstrate an old init under a
  different distro 1 that can find/stop PMLinux daemon started from user
  terminal.

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

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

[Touch-packages] [Bug 1337576] Re: dash inability - cron starts binary with /bin/sh

[Luciano Chavez]

** Changed in: dash (Ubuntu)
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

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

Title:
  dash inability - cron starts binary with /bin/sh

Status in dash package in Ubuntu:
  New

Bug description:
  -- Problem Description --
  CRON uses shell to start a binary executable defined in crontab, which is a 
waste of the resources for the extra shell process hanging in the system. It's 
supposed to run it directly with exec system call.

  *** Here are some command outputs to see the extra process(12327) and 
relevant information: ***
  # ps -ef | grep -e CRON -e PMLnx
  root 12326   771  0 13:59 ?00:00:00 CRON
  root 12327 12326  0 13:59 ?00:00:00 /bin/sh -c 
/var/perf/pm/bin/daemon_PMLnx  <--- extra layer, a waste
  root 12328 12327  0 13:59 ?00:00:00 /var/perf/pm/bin/daemon_PMLnx

  # crontab -l
  59 * * * * /var/perf/pm/bin/daemon_PMLnx

  # file /var/perf/pm/bin/daemon_PMLnx
  /var/perf/pm/bin/daemon_PMLnx: ELF 64-bit LSB  executable, 64-bit PowerPC or 
cisco 7500, version 1 (SYSV), dynamically linked (uses shared libs), for 
GNU/Linux 3.0.0, BuildID[sha1]=1761d6d97eabb4e52870cb517fe6bf457e5bf89e, 
stripped

  # uname -a
  Linux ubuntu 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:09:21 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux

  # dpkg -l cron
  Name  VersionArchitecture  Description
  +++-=-==-=-=
  ii  cron  3.0pl1-124ubuntu2  ppc64el   process scheduling daemon

  *** Expect cron to directly execute a binary like this ***
  # ps -ef | grep -e CRON -e PMLnx
  root  2293  2223  0 09:59 ?00:00:00 /usr/sbin/CRON -n
  root  2294  2293  0 09:59 ?00:00:00 /var/perf/pm/bin/daemon_PMLnx

  # uname -a
  Linux hulala 3.12.15-3-default #1 SMP Wed Apr 2 17:08:55 UTC 2014 (69c2ea8) 
ppc64le ppc64le ppc64le GNU/Linux

  # cat /etc/SuSE-release
  SUSE Linux Enterprise Server 12 (ppc64le)
  VERSION = 12
  PATCHLEVEL = 0

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

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

[Touch-packages] [Bug 1532007] Re: libvirt's apparmor policy prevents starting domain with hugepage-backed memory store

[Luciano Chavez]

** Package changed: ubuntu => apparmor (Ubuntu)

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

Title:
  libvirt's apparmor policy prevents starting domain with hugepage-
  backed memory store

Status in apparmor package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  After enabling hugepages, unable to start a domain with hugepage-packed 
memory store:

  ~# virsh start ubuntu-14_04
  error: Failed to start domain ubuntu-14_04
  error: internal error: process exited while connecting to monitor: 
2015-07-10T14:26:04.627101Z qemu-system-ppc64le: unable to create backing store 
for hugepages: Permission denied

  ---uname output---
  Linux cipipeln 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 19:33:37 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
   
   
  ---Steps to Reproduce---
  1. set the sysctl setting for hugepages to 5000
  2. enable huge pages in /etc/default/qemu-kvm
  3. restart qemu-kvm
  4. restart libvirt 
  5. add to guest xml (using virsh edit)
  
 
  
  6. virsh define ubuntu-14_04.xml
  7. virsh start ubuntu-14_04

  
  # grep Huge /proc/meminfo 
  AnonHugePages: 0 kB
  HugePages_Total:5000
  HugePages_Free: 5000
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB

  # cat /etc/default/qemu-kvm 
  # To disable qemu-kvm's page merging feature, set KSM_ENABLED=0 and
  # sudo restart qemu-kvm
  KSM_ENABLED=1
  SLEEP_MILLISECS=200
  # To load the vhost_net module, which in some cases can speed up
  # network performance, set VHOST_NET_ENABLED to 1.
  VHOST_NET_ENABLED=1

  # Set this to 1 if you want hugepages to be available to kvm under
  # /run/hugepages/kvm
  KVM_HUGEPAGES=1

  ==
  File permissions on the hugepages mount dir:

  root@cipipeln:~# ls -lah /dev | grep hugep
  drwxr-xr-x  3 root root   0 Jun 16 12:39 hugepages
  root@cipipeln:~# ls -lah /dev/hugepages/
  total 0
  drwxr-xr-x  3 root root0 Jun 16 12:39 .
  drwxr-xr-x 18 root root 4.9K Jul  8 11:03 ..
  drwxr-xr-x  3 root root0 Jun 16 12:39 libvirt
  root@cipipeln:~# ls -lah /dev/hugepages/libvirt/
  total 0
  drwxr-xr-x 3 root root 0 Jun 16 12:39 .
  drwxr-xr-x 3 root root 0 Jun 16 12:39 ..
  drwxr-xr-x 2 libvirt-qemu kvm  0 Jul  9 18:34 qemu

  ==

  # sysctl -a | grep huge
  vm.hugepages_treat_as_movable = 0
  vm.hugetlb_shm_group = 0
  vm.nr_hugepages = 5000
  vm.nr_hugepages_mempolicy = 5000
  vm.nr_overcommit_hugepages = 0

  ==

  I was able to confirm that running qemu-kvm stand-alone was allocated
  4 hugepages (The number of free huge pages decreased by 4).

  ==
  I also tried:
  - sysctl -w vm.hugetlb_shm_group=X where X was the user id for libvirt, and 
then tried the group id for the kvm group
  - disabling apparmor
  - chmod -R 777 /dev/hugepages
   
  Hi Christy, Are you using apparmor for any specific reason ? If you can 
switch to selinux, it would be convinient for me to debug as I am very 
comfortable with selinux. The issue I see is qemu is not able to create a 
temporary file in /dev/hugepages/libvirt/qemu/qemu_back_mem.ppc_spapr.ram.XXX.

  Can you disable that and try Or confirm if the /dev/hugepages
  directory has relaxed security? I tried relaxing a bit and failed as I
  dont know apparmor well.

  Thanks,
  Shiva

  == Comment: #8 - Christy L. Norman Perez  - 2016-01-07 
11:33:19 ==
  (In reply to comment #7)
  > Hi Christy, Are you using apparmor for any specific reason ? If you can
  > switch to selinux, it would be convinient for me to debug as I am very
  > comfortable with selinux. The issue I see is qemu is not able to create a
  > temporary file in
  > /dev/hugepages/libvirt/qemu/qemu_back_mem.ppc_spapr.ram.XXX.

  Nope, not using apparmor for any reason aside from the fact that it's
  default on Ubuntu.

  > 
  > Can you disable that and try Or confirm if the /dev/hugepages directory has
  > relaxed security? I tried relaxing a bit and failed as I dont know apparmor
  > well. 

  I can't believe I didn't look into this before, but it does look like an 
apparmor issue:
  Jan 07 11:17:17 humphrey kernel: audit: type=1400 audit(1452183437.308:281): 
apparmor="DENIED" operation="mknod" 
profile="libvirt-be593664-727a-4905-bdb8-2eb7ccf85700

  So, here's what I did to get this to work:
  root@humphrey:~# aa-complain 
/etc/apparmor.d/libvirt/libvirt-be593664-727a-4905-bdb8-2eb7ccf85700
  Setting /etc/apparmor.d/libvirt/libvirt-be593664-727a-4905-bdb8-2eb7ccf85700 
to complain mode.

  root@humphrey:~# virsh start bz127508
  Domain bz127508 started

  > 
  > Thanks,
  > Shiva

  I think we should reroute this to apparmor, mirror to Ubuntu, and
  request an updated apparmor policy. This change should be done for
  14.04 and applicable releases after.

  Thanks for the suggestion, Shiva!

To manage notifications about this bug go to:

[Touch-packages] [Bug 1478087] Re: ISST-LTE: aureport -l couldn't print out login info on ubuntu 14.04.3

[Luciano Chavez]

** Package changed: ubuntu = audit (Ubuntu)

** Changed in: audit (Ubuntu)
 Assignee: (unassigned) = Taco Screen team (taco-screen-team)

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

Title:
  ISST-LTE: aureport -l couldn't print out login info on ubuntu 14.04.3

Status in audit package in Ubuntu:
  New

Bug description:
  -- Problem Description --
  We installed ubuntu 14.04.3 on lakelp1 and installed package auditd. We tried 
to
  ssh to lakelp1 several times and found that aureport -l couldn't print out 
the login 
  info.

  root@lakelp1:~# /etc/init.d/auditd status
   * auditd is running.

  root@lakelp1:~# auditctl -e 1
  AUDIT_STATUS: enabled=1 flag=1 pid=38784 rate_limit=0 backlog_limit=320 
lost=12 backlog=1

  root@lakelp1:~# grep -i login /var/log/audit/audit.log
  type=LOGIN msg=audit(1437641256.987:67): pid=11752 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=4 res=1
  type=LOGIN msg=audit(1437642646.478:85): pid=44269 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=5 res=1
  type=LOGIN msg=audit(1437642700.295:90): pid=21504 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=6 res=1
  type=LOGIN msg=audit(1437642765.339:104): pid=16628 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=7 res=1
  type=LOGIN msg=audit(1437644638.593:130): pid=3 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=8 res=1

  
  root@lakelp1:~# aureport -l

  Login Report
  
  # date time auid host term exe success event
  
  no events of interest were found

  This looks like a bug in aureport or libaudit. In addition to giving
  admins falsely empty record selections, this would prevent successful
  completion of a Common Criteria certification.

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

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

[Touch-packages] [Bug 1427995] Re: lscpu -p is showing wrong values for Node component

[Luciano Chavez]

** Changed in: util-linux (Ubuntu)
 Assignee: (unassigned) = Taco Screen team (taco-screen-team)

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

Title:
  lscpu -p is showing wrong values for Node component

Status in util-linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  lscpu -p is showing wrong values for Node component
   
  ---uname output---
  Linux ubuntu 3.16.0-25-generic #14-Ubuntu ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install a P8 machine with Ubuntu 14.04.02 ISO image in Power NV mode.
  Then execute the below test scenario.

  root@ubuntu-daily:~# lscpu -p
  # The following is the parsable format, which can be fed to other
  # programs. Each different item in every column has an unique ID
  # starting from zero.
  # CPU,Core,Socket,Node,,L1d,L1i,L2,L3
  0,0,0,0,,0,0,0,0
  1,0,0,1,,0,0,0,0
  2,0,0,16,,0,0,0,0
  3,0,0,17,,0,0,0,0
  4,0,0,0,,0,0,0,0
  5,0,0,0,,0,0,0,0
  6,0,0,33,,0,0,0,0
  7,0,0,0,,0,0,0,0
  8,1,0,0,,1,1,1,1
  9,1,0,0,,1,1,1,1
  10,1,0,-1429431768,,1,1,1,1
  11,1,0,16383,,1,1,1,1
  12,1,0,1852125029,,1,1,1,1
  13,1,0,777213279,,1,1,1,1
  14,1,0,81,,1,1,1,1
  15,1,0,0,,1,1,1,1
  16,2,0,1920169263,,2,2,2,2
  17,2,0,1634235183,,2,2,2,2
  18,2,0,1815045490,,2,2,2,2
  19,2,0,1818321775,,2,2,2,2
  20,2,0,1852125029,,2,2,2,2
  21,2,0,777213279,,2,2,2,2
  22,2,0,759583829,,2,2,2,2
  23,2,0,1953836600,,2,2,2,2
  24,3,0,1278163046,,3,3,3,3
  25,3,0,1162698563,,3,3,3,3
  26,3,0,1195463507,,3,3,3,3
  27,3,0,1966035781,,3,3,3,3
  28,3,0,762079604,,3,3,3,3
  29,3,0,1970170220,,3,3,3,3
  30,3,0,1869426296,,3,3,3,3
  31,3,0,0,,3,3,3,3
  32,4,1,0,,4,4,4,4
  33,4,1,0,,4,4,4,4
  34,4,1,177,,4,4,4,4
  35,4,1,0,,4,4,4,4
  36,4,1,269092192,,4,4,4,4
  37,4,1,256,,4,4,4,4
  38,4,1,1,,4,4,4,4
  39,4,1,16383,,4,4,4,4
  40,5,1,0,,5,5,5,5
  41,5,1,0,,5,5,5,5
  42,5,1,269096544,,5,5,5,5
  43,5,1,256,,5,5,5,5
  44,5,1,269092512,,5,5,5,5
  45,5,1,256,,5,5,5,5
  46,5,1,269097536,,5,5,5,5
  47,5,1,256,,5,5,5,5
  48,6,1,269092688,,6,6,6,6
  49,6,1,256,,6,6,6,6
  50,6,1,269098208,,6,6,6,6
  51,6,1,256,,6,6,6,6
  52,6,1,269096960,,6,6,6,6
  53,6,1,256,,6,6,6,6
  54,6,1,269097456,,6,6,6,6
  55,6,1,256,,6,6,6,6
  56,7,1,269096544,,7,7,7,7
  57,7,1,256,,7,7,7,7
  58,7,1,269098592,,7,7,7,7
  59,7,1,256,,7,7,7,7
  60,7,1,269097344,,7,7,7,7
  61,7,1,256,,7,7,7,7
  62,7,1,269098016,,7,7,7,7
  63,7,1,256,,7,7,7,7
  64,8,2,269096880,,8,8,8,8
  65,8,2,256,,8,8,8,8
  66,8,2,269098400,,8,8,8,8
  67,8,2,256,,8,8,8,8
  68,8,2,269097184,,8,8,8,8
  69,8,2,256,,8,8,8,8
  70,8,2,269097856,,8,8,8,8
  71,8,2,256,,8,8,8,8
  72,9,2,269096672,,9,9,9,9
  73,9,2,256,,9,9,9,9
  74,9,2,0,,9,9,9,9
  75,9,2,0,,9,9,9,9
  76,9,2,0,,9,9,9,9
  77,9,2,0,,9,9,9,9
  78,9,2,65,,9,9,9,9
  79,9,2,0,,9,9,9,9
  80,10,2,1920169263,,10,10,10,10
  81,10,2,1634235183,,10,10,10,10
  82,10,2,1815045490,,10,10,10,10
  83,10,2,1818321775,,10,10,10,10
  84,10,2,1852125029,,10,10,10,10
  85,10,2,777213279,,10,10,10,10
  86,10,2,759583829,,10,10,10,10
  87,10,2,1129066296,,10,10,10,10
  88,11,2,1397050719,,11,11,11,11
  89,11,2,1162297683,,11,11,11,11
  90,11,2,1953836883,,11,11,11,11
  91,11,2,1814916201,,11,11,11,11
  92,11,2,2020961897,,11,11,11,11
  93,11,2,7302446,,11,11,11,11
  94,11,2,113,,11,11,11,11
  95,11,2,0,,11,11,11,11
  96,12,3,269092448,,12,12,12,12
  97,12,3,256,,12,12,12,12
  98,12,3,1,,12,12,12,12
  99,12,3,16383,,12,12,12,12
  100,12,3,0,,12,12,12,12
  101,12,3,0,,12,12,12,12
  102,12,3,269092272,,12,12,12,12
  103,12,3,256,,12,12,12,12
  104,13,3,269092688,,13,13,13,13
  105,13,3,256,,13,13,13,13
  106,13,3,269096960,,13,13,13,13
  107,13,3,256,,13,13,13,13
  108,13,3,269096544,,13,13,13,13
  109,13,3,256,,13,13,13,13
  110,13,3,269097344,,13,13,13,13
  111,13,3,256,,13,13,13,13
  112,14,3,269096880,,14,14,14,14
  113,14,3,256,,14,14,14,14
  114,14,3,269097184,,14,14,14,14
  115,14,3,256,,14,14,14,14
  116,14,3,269096672,,14,14,14,14
  117,14,3,256,,14,14,14,14
  118,14,3,0,,14,14,14,14
  119,14,3,0,,14,14,14,14
  120,15,3,0,,15,15,15,15
  121,15,3,0,,15,15,15,15
  122,15,3,65,,15,15,15,15
  123,15,3,0,,15,15,15,15
  124,15,3,1920169263,,15,15,15,15
  125,15,3,1634235183,,15,15,15,15
  126,15,3,1815045490,,15,15,15,15
  127,15,3,1818321775,,15,15,15,15

  root@ubuntu-daily:~# dpkg --list | grep util-linux
  ii  util-linux  2.20.1-5.1ubuntu20.4
ppc64el  Miscellaneous system utilities

  
   
  Contact Information = pavsu...@in.ibm.com 
   
  Userspace tool common name: /usr/bin/lscpu 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace package: util-linux

  Userspace tool obtained from project website:  na

To manage notifications about this bug go to:

[Touch-packages] [Bug 1443653] Re: Ubuntu 15.04 - Failed installation of ubuntu-desktop package (whoopsie package)

[Luciano Chavez]

** Package changed: ubuntu = whoopsie (Ubuntu)

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

Title:
  Ubuntu 15.04 - Failed installation of ubuntu-desktop package (whoopsie
  package)

Status in whoopsie package in Ubuntu:
  New

Bug description:
  -- Problem Description --
  When installing the ubuntu-desktop package in Ubuntu 15.04 during the set up 
of a package the following message is displayed and the installation doesn't go 
any further:

  Setting up whoopsie (0.2.47) ...
  Error getting authority: Error initializing authority: Error calling 
StartServi24)yName for org.freedesktop.PolicyKit1: Timeout was reached 
(g-io-error-quark, 2
  Failed to execute operation: Connection timed out

  I am able to reproduce this issue when installing the ubuntu-desktop
  package on top of a fresh install, but in a different test, I tried to
  install only the whoopsie package where the package installation stops
  and I did not see this issue.

  I am attaching below the full log of the apt-get installation.

  The problem is on starting the systemd script. If I stop it, it makes
  progress. There are other systemd initi scripts that are failing
  also...

   Can you try by switching the init system back to upstart, and re-installing?
   
   See [1]; probably this will do: init=/sbin/upstart
   
   [1]
   https://lists.ubuntu.com/archives/ubuntu-devel-announce/2015-March/001130.
   html

  Mauricio, the installation of the packages went properly by adding the
  init=/sbin/upstart to the boot line. I attached the full installation
  log above.

  But when restarting the system, the following message is issued and
  the system doesn't seem to be bootable anymore.

  * Restoring resolver state... 
[ OK ] 
   * Starting uuid generator uuidd [ OK 
] 
   * speech-dispatcher disabled; edit /etc/default/speech-dispatcher
  /lib/init/init-d-script: 12: /etc/rc2.d/S02whoopsie: -c: not found
  basename: missing operand
  Try 'basename --help' for more information.
   * saned disabled; edit /etc/default/saned

  Interesting. It installed, but failed to stop services.
  Hm, it seems that whoopsie thing is broken intermediarily between upstart and 
systemd.

  Trying to get rid of whoopsie may help.
  Do you need an 'Ubuntu error tracker submission' tool? :)

  I'd suggest you to try to remove it.
  If some things depend on it, and are not important, pull them off/ignore 
dependencies, and try again. That might help.

  Nonetheless, it's certainly worth a launchpad bug for Canonical to
  look at.

  Another work-around, much less disruptive, is just ignore the rc
  script failing in the reboot chain. :)

  You can find a symlink for it in /etc/rc{6,0}.d (reboot/shutdown)..
  just renaming it to w/out a leading K should effectively disable it
  from the reboot/shutdown runlevel change chain.. and hopefully that
  will get the issue out of the way for now.

  Ah, the other comment mention it's rc2.d (an startup/single user
  runlevel, IIRC).. you can try the renaming there to, but to w/out a
  leading S.

  IIRC this command should achieve that too:
  $ sudo update-rc.d whoopsie disable

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

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

[Touch-packages] [Bug 1415917] Re: Hardware watchpoints not working on ppc64le guests running on Ubuntu 14.10 host

[Luciano Chavez]

** Package changed: ubuntu = gdb (Ubuntu)

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

Title:
  Hardware watchpoints not working on ppc64le guests running on Ubuntu
  14.10 host

Status in gdb package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Edjunior Barbosa Machado emach...@br.ibm.com - 2015-01-26 
06:38:42 ==
  GDB hw watchpoints don't work on ppc64le VMs running on top of Ubuntu 14.10 
Power8 host (sid.ltc.br.ibm.com). It fails quietly, ptrace calls and dmesg 
output display no error message.

  Tested on guests running different distros, kernel and  gdb versions
  (distro's packages and upstream). Unfortunately, I couldn't find any
  other Ubuntu 14.10 host to double check the problem, but it worked OK
  in other hosts I've tried.

  Steps to reproduce:

  $ cat test.c 
  int a;
  main(void)
  {
  a++;
  }

  $ gcc -g test.c -o test

  $ gdb ./test 
  GNU gdb (Ubuntu 7.8.1-1ubuntu2) 7.8.1
  ...
  Reading symbols from ./test...done.
  (gdb) watch a
  Hardware watchpoint 1: a
  (gdb) run
  Starting program: /home/emachado/test 
  [Inferior 1 (process 8179) exited with code 0134]
  (gdb) 

  Curiously, in the host it works as expected:

  $ gdb ./test 
  GNU gdb (Ubuntu 7.8-1ubuntu4) 7.8.0.20141001-cvs
  ...
  Reading symbols from ./test...done.
  (gdb) watch a
  Hardware watchpoint 1: a
  (gdb) r
  Starting program: /home/emachado/test 
  Hardware watchpoint 1: a

  Old value = 0
  New value = 1
  main () at test.c:5
  5   }
  (gdb)

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

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

[Touch-packages] [Bug 1427995] Re: lscpu -p is showing wrong values for Node component

[Luciano Chavez]

** Package changed: ubuntu = util-linux (Ubuntu)

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

Title:
  lscpu -p is showing wrong values for Node component

Status in util-linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  lscpu -p is showing wrong values for Node component
   
  ---uname output---
  Linux ubuntu 3.16.0-25-generic #14-Ubuntu ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install a P8 machine with Ubuntu 14.04.02 ISO image in Power NV mode.
  Then execute the below test scenario.

  root@ubuntu-daily:~# lscpu -p
  # The following is the parsable format, which can be fed to other
  # programs. Each different item in every column has an unique ID
  # starting from zero.
  # CPU,Core,Socket,Node,,L1d,L1i,L2,L3
  0,0,0,0,,0,0,0,0
  1,0,0,1,,0,0,0,0
  2,0,0,16,,0,0,0,0
  3,0,0,17,,0,0,0,0
  4,0,0,0,,0,0,0,0
  5,0,0,0,,0,0,0,0
  6,0,0,33,,0,0,0,0
  7,0,0,0,,0,0,0,0
  8,1,0,0,,1,1,1,1
  9,1,0,0,,1,1,1,1
  10,1,0,-1429431768,,1,1,1,1
  11,1,0,16383,,1,1,1,1
  12,1,0,1852125029,,1,1,1,1
  13,1,0,777213279,,1,1,1,1
  14,1,0,81,,1,1,1,1
  15,1,0,0,,1,1,1,1
  16,2,0,1920169263,,2,2,2,2
  17,2,0,1634235183,,2,2,2,2
  18,2,0,1815045490,,2,2,2,2
  19,2,0,1818321775,,2,2,2,2
  20,2,0,1852125029,,2,2,2,2
  21,2,0,777213279,,2,2,2,2
  22,2,0,759583829,,2,2,2,2
  23,2,0,1953836600,,2,2,2,2
  24,3,0,1278163046,,3,3,3,3
  25,3,0,1162698563,,3,3,3,3
  26,3,0,1195463507,,3,3,3,3
  27,3,0,1966035781,,3,3,3,3
  28,3,0,762079604,,3,3,3,3
  29,3,0,1970170220,,3,3,3,3
  30,3,0,1869426296,,3,3,3,3
  31,3,0,0,,3,3,3,3
  32,4,1,0,,4,4,4,4
  33,4,1,0,,4,4,4,4
  34,4,1,177,,4,4,4,4
  35,4,1,0,,4,4,4,4
  36,4,1,269092192,,4,4,4,4
  37,4,1,256,,4,4,4,4
  38,4,1,1,,4,4,4,4
  39,4,1,16383,,4,4,4,4
  40,5,1,0,,5,5,5,5
  41,5,1,0,,5,5,5,5
  42,5,1,269096544,,5,5,5,5
  43,5,1,256,,5,5,5,5
  44,5,1,269092512,,5,5,5,5
  45,5,1,256,,5,5,5,5
  46,5,1,269097536,,5,5,5,5
  47,5,1,256,,5,5,5,5
  48,6,1,269092688,,6,6,6,6
  49,6,1,256,,6,6,6,6
  50,6,1,269098208,,6,6,6,6
  51,6,1,256,,6,6,6,6
  52,6,1,269096960,,6,6,6,6
  53,6,1,256,,6,6,6,6
  54,6,1,269097456,,6,6,6,6
  55,6,1,256,,6,6,6,6
  56,7,1,269096544,,7,7,7,7
  57,7,1,256,,7,7,7,7
  58,7,1,269098592,,7,7,7,7
  59,7,1,256,,7,7,7,7
  60,7,1,269097344,,7,7,7,7
  61,7,1,256,,7,7,7,7
  62,7,1,269098016,,7,7,7,7
  63,7,1,256,,7,7,7,7
  64,8,2,269096880,,8,8,8,8
  65,8,2,256,,8,8,8,8
  66,8,2,269098400,,8,8,8,8
  67,8,2,256,,8,8,8,8
  68,8,2,269097184,,8,8,8,8
  69,8,2,256,,8,8,8,8
  70,8,2,269097856,,8,8,8,8
  71,8,2,256,,8,8,8,8
  72,9,2,269096672,,9,9,9,9
  73,9,2,256,,9,9,9,9
  74,9,2,0,,9,9,9,9
  75,9,2,0,,9,9,9,9
  76,9,2,0,,9,9,9,9
  77,9,2,0,,9,9,9,9
  78,9,2,65,,9,9,9,9
  79,9,2,0,,9,9,9,9
  80,10,2,1920169263,,10,10,10,10
  81,10,2,1634235183,,10,10,10,10
  82,10,2,1815045490,,10,10,10,10
  83,10,2,1818321775,,10,10,10,10
  84,10,2,1852125029,,10,10,10,10
  85,10,2,777213279,,10,10,10,10
  86,10,2,759583829,,10,10,10,10
  87,10,2,1129066296,,10,10,10,10
  88,11,2,1397050719,,11,11,11,11
  89,11,2,1162297683,,11,11,11,11
  90,11,2,1953836883,,11,11,11,11
  91,11,2,1814916201,,11,11,11,11
  92,11,2,2020961897,,11,11,11,11
  93,11,2,7302446,,11,11,11,11
  94,11,2,113,,11,11,11,11
  95,11,2,0,,11,11,11,11
  96,12,3,269092448,,12,12,12,12
  97,12,3,256,,12,12,12,12
  98,12,3,1,,12,12,12,12
  99,12,3,16383,,12,12,12,12
  100,12,3,0,,12,12,12,12
  101,12,3,0,,12,12,12,12
  102,12,3,269092272,,12,12,12,12
  103,12,3,256,,12,12,12,12
  104,13,3,269092688,,13,13,13,13
  105,13,3,256,,13,13,13,13
  106,13,3,269096960,,13,13,13,13
  107,13,3,256,,13,13,13,13
  108,13,3,269096544,,13,13,13,13
  109,13,3,256,,13,13,13,13
  110,13,3,269097344,,13,13,13,13
  111,13,3,256,,13,13,13,13
  112,14,3,269096880,,14,14,14,14
  113,14,3,256,,14,14,14,14
  114,14,3,269097184,,14,14,14,14
  115,14,3,256,,14,14,14,14
  116,14,3,269096672,,14,14,14,14
  117,14,3,256,,14,14,14,14
  118,14,3,0,,14,14,14,14
  119,14,3,0,,14,14,14,14
  120,15,3,0,,15,15,15,15
  121,15,3,0,,15,15,15,15
  122,15,3,65,,15,15,15,15
  123,15,3,0,,15,15,15,15
  124,15,3,1920169263,,15,15,15,15
  125,15,3,1634235183,,15,15,15,15
  126,15,3,1815045490,,15,15,15,15
  127,15,3,1818321775,,15,15,15,15

  root@ubuntu-daily:~# dpkg --list | grep util-linux
  ii  util-linux  2.20.1-5.1ubuntu20.4
ppc64el  Miscellaneous system utilities

  
   
  Contact Information = pavsu...@in.ibm.com 
   
  Userspace tool common name: /usr/bin/lscpu 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace package: util-linux

  Userspace tool obtained from project website:  na

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

-- 
Mailing list: 

[Touch-packages] [Bug 1427077] Re: [Ubuntu 15.10] initramfs extended attribute support - kernel piece

[Luciano Chavez]

** Package changed: ubuntu = cpio (Ubuntu)

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

Title:
  [Ubuntu 15.10] initramfs extended attribute support - kernel piece

Status in cpio package in Ubuntu:
  New

Bug description:
  add xattr support to cpio

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

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

[Touch-packages] [Bug 1427076] Re: [Ubuntu 15.10] Add Power LE support to libseccomp

[Luciano Chavez]

** Package changed: ubuntu = libseccomp (Ubuntu)

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

Title:
  [Ubuntu 15.10] Add  Power LE support to libseccomp

Status in libseccomp package in Ubuntu:
  New

Bug description:
  == Comment: #0 - George C. Wilson gcwil...@us.ibm.com - 2015-01-28
  10:13:19 ==

  seccomp mode 2 involves the parsing of BPF (Berkeley Packet Filter)
  configuration files to define system call filtering.  Mode 2 is not
  currently supported on Power; this feature covers the addition of this
  support, which likely includes updates to the kernel and to
  libseccomp.

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

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

[Touch-packages] [Bug 1436448] Re: Error messages while installing apport package

[Luciano Chavez]

** Package changed: ubuntu = 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/1436448

Title:
  Error messages while installing apport package

Status in apport package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Error messages while installing apport package

  ---uname output---
  3.19.0-9-generic
   
  Machine Type = POWER8 

  ---Steps to Reproduce---
  1) Install Ubuntu 15.04 as a PowerKVM guest.
  2) Install apport package using following command

  apt-get install apport

  Error messages are displayed during the installation. The installation
  eventually succeeds.

  root@ub1504:~# apt-get install apport
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-3.18.0-13 linux-headers-3.18.0-13-generic
linux-image-3.18.0-13-generic linux-image-extra-3.18.0-13-generic
python-support
  Use 'apt-get autoremove' to remove them.
  The following extra packages will be installed:
apport-symptoms libpolkit-agent-1-0 libpolkit-backend-1-0 policykit-1
python3-apport python3-problem-report
  Suggested packages:
apport-gtk apport-kde python3-launchpadlib
  The following NEW packages will be installed:
apport apport-symptoms libpolkit-agent-1-0 libpolkit-backend-1-0 policykit-1
python3-apport python3-problem-report
  0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
  Need to get 312 kB of archives.
  After this operation, 2,296 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://ports.ubuntu.com/ubuntu-ports/ vivid/main libpolkit-agent-1-0 
ppc64el 0.105-8ubuntu2 [14.6 kB]
  Get:2 http://ports.ubuntu.com/ubuntu-ports/ vivid/main libpolkit-backend-1-0 
ppc64el 0.105-8ubuntu2 [33.5 kB]
  Get:3 http://ports.ubuntu.com/ubuntu-ports/ vivid/main python3-problem-report 
all 2.16.2-0ubuntu4 [10.1 kB]
  Get:4 http://ports.ubuntu.com/ubuntu-ports/ vivid/main python3-apport all 
2.16.2-0ubuntu4 [75.9 kB]
  Get:5 http://ports.ubuntu.com/ubuntu-ports/ vivid/main apport all 
2.16.2-0ubuntu4 [113 kB]
  Get:6 http://ports.ubuntu.com/ubuntu-ports/ vivid/main apport-symptoms all 
0.20 [14.2 kB]
  Get:7 http://ports.ubuntu.com/ubuntu-ports/ vivid/main policykit-1 ppc64el 
0.105-8ubuntu2 [50.7 kB]
  Fetched 312 kB in 1s (217 kB/s)
  Selecting previously unselected package libpolkit-agent-1-0:ppc64el.
  (Reading database ... 114319 files and directories currently installed.)
  Preparing to unpack .../libpolkit-agent-1-0_0.105-8ubuntu2_ppc64el.deb ...
  Unpacking libpolkit-agent-1-0:ppc64el (0.105-8ubuntu2) ...
  Selecting previously unselected package libpolkit-backend-1-0:ppc64el.
  Preparing to unpack .../libpolkit-backend-1-0_0.105-8ubuntu2_ppc64el.deb ...
  Unpacking libpolkit-backend-1-0:ppc64el (0.105-8ubuntu2) ...
  Selecting previously unselected package python3-problem-report.
  Preparing to unpack .../python3-problem-report_2.16.2-0ubuntu4_all.deb ...
  Unpacking python3-problem-report (2.16.2-0ubuntu4) ...
  Selecting previously unselected package python3-apport.
  Preparing to unpack .../python3-apport_2.16.2-0ubuntu4_all.deb ...
  Unpacking python3-apport (2.16.2-0ubuntu4) ...
  Selecting previously unselected package apport.
  Preparing to unpack .../apport_2.16.2-0ubuntu4_all.deb ...
  Unpacking apport (2.16.2-0ubuntu4) ...
  Selecting previously unselected package apport-symptoms.
  Preparing to unpack .../apport-symptoms_0.20_all.deb ...
  Unpacking apport-symptoms (0.20) ...
  Selecting previously unselected package policykit-1.
  Preparing to unpack .../policykit-1_0.105-8ubuntu2_ppc64el.deb ...
  Unpacking policykit-1 (0.105-8ubuntu2) ...
  Processing triggers for man-db (2.7.0.2-5) ...
  Processing triggers for shared-mime-info (1.3-1) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Processing triggers for dbus (1.8.12-1ubuntu3) ...
  Setting up libpolkit-agent-1-0:ppc64el (0.105-8ubuntu2) ...
  Setting up libpolkit-backend-1-0:ppc64el (0.105-8ubuntu2) ...
  Setting up python3-problem-report (2.16.2-0ubuntu4) ...
  Setting up python3-apport (2.16.2-0ubuntu4) ...
  Setting up apport (2.16.2-0ubuntu4) ...
  Error getting authority: Error initializing authority: Error calling 
StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached 
(g-io-error-quark, 24)
  Failed to execute operation: Connection timed out
  invoke-rc.d: apport.service doesn't exist but the upstart job does. Nothing 
to start or stop until a systemd or init job is present.
  Setting up apport-symptoms (0.20) ...
  Setting up policykit-1 (0.105-8ubuntu2) ...
  Processing triggers for libc-bin (2.21-0ubuntu2) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Processing triggers for dbus (1.8.12-1ubuntu3) ...
  

[Touch-packages] [Bug 1418642] Re: GDB hangs at thread join function on Ubuntu 14.10 LE Power

[Luciano Chavez]

** Package changed: ubuntu = gdb (Ubuntu)

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

Title:
  GDB hangs at thread join function on Ubuntu 14.10 LE Power

Status in gdb package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  GDB hangs at thread join function while trying to debug STM (software 
transacational memory) code.

  ---uname output---
  Linux lep8aVM1 3.16.0-7-generic #12-Ubuntu SMP Sat Aug 9 05:05:32 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Power 8 

  ---Steps to Reproduce---

  Compile:
  -
  g++ s1.cpp -g -std=c++11 -fgnu-tm -lpthread -D D_STM

  sample source: s1.cpp
  ---
  root@lep8aVM1:~/p# cat s1.cpp
  #include iostream
  #include thread

  static const auto THR_NUM = 4;
  static const auto ITER_NUM = 1000 * 1000;

  static auto a = 0, b = 0, c = 0;

  static void thr_func()
  {
  for (auto i = 0; i  ITER_NUM; ++i)
  #ifdef D_STM
   __transaction_atomic {
  ++a;
  b += 2;
  c = a + b;
  }
  #else
  ++a;
  b += 2;
  c = a + b;
  #endif
  }

  
  int main(int argc, char *argv[])
  {
std::thread thr[THR_NUM];

for (auto t : thr)
t = std::thread(thr_func);

for (auto t : thr)
t.join();

  std::cout  a=  a   b=  b   c=  c 
  std::endl;

return 0;
  }

  Debug a.out using gdb:
  
  root@lep8aVM1:~/p# gdb ./a.out 
  GNU gdb (Ubuntu 7.8-0ubuntu1) 7.8
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type show copying
  and show warranty for details.
  This GDB was configured as powerpc64le-linux-gnu.
  Type show configuration for configuration details.
  For bug reporting instructions, please see:
  http://www.gnu.org/software/gdb/bugs/.
  Find the GDB manual and other documentation resources online at:
  http://www.gnu.org/software/gdb/documentation/.
  For help, type help.
  Type apropos word to search for commands related to word...
  Reading symbols from ./a.out...done.
  (gdb) run
  Starting program: /root/p/a.out 
  Can't read symbols from system-supplied DSO at 0x3fffb7fa: File truncated
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library 
/lib/powerpc64le-linux-gnu/libthread_db.so.1.

  Breakpoint 1, main (argc=1, argv=0x36b8) at s1.cpp:27
  27{
  (gdb) list
  22#endif
  23}
  24
  25
  26int main(int argc, char *argv[])
  27{
  28std::thread thr[THR_NUM];
  29
  30for (auto t : thr)
  31t = std::thread(thr_func);
  (gdb) n
  28std::thread thr[THR_NUM];
  (gdb) n
  30for (auto t : thr)
  (gdb) n
  31t = std::thread(thr_func);
  (gdb) n
  [New Thread 0x3fffb72cf170 (LWP 1278)]
  30for (auto t : thr)
  (gdb) n
  31t = std::thread(thr_func);
  (gdb) n
  [New Thread 0x3fffb6acf170 (LWP 1279)]
  30for (auto t : thr)
  (gdb) n
  31t = std::thread(thr_func);
  (gdb) n
  [New Thread 0x3fffb62cf170 (LWP 1280)]
  30for (auto t : thr)
  (gdb) n
  31t = std::thread(thr_func);
  (gdb) n
  [New Thread 0x3fffb5acf170 (LWP 1281)]
  30for (auto t : thr)
  (gdb) n
  33for (auto t : thr)
  (gdb) n
  34t.join();
  (gdb) n
  n
  n
  n
  Here the gdb seems hangs and does not come out...

  
   The same program been tried on Ubuntu 14.10 x86 VM; gdb could able to come 
out and program ends normally.

  I've found that this issue happens also on upstream gdb and not only
  on ppc64 LE, but also on BE. It is also reproducible without STM.

  This is a regression added recently upstream by commit
  2adfaa28b5ba2fb78ba5113977082c4d04752bd6. I'll continue investigating.

  Found this reduced testcase that reproduces the problem without -fgnu-
  tm flag:

  $ cat test.c
  #include stdlib.h
  #include stdio.h
  #include unistd.h
  #include pthread.h

  void *func(void *arg)
  {
  int i,a;
  for (i = 0; i  100; ++i)
  a++;
  return NULL;
  }

  int main()
  {   
  pthread_t thread;

  pthread_create(thread, NULL, func, NULL);
  pthread_join(thread, NULL);
  return 0;
  }

  $ gcc -g -lpthread test.c -o test

  Found that this commit c1a747c10948e2298083179f4e8aeed8b962e2af fixes
  the problem on upstream gdb. I'm backporting the patch for Ubuntu
  package in order to double 

[Touch-packages] [Bug 1414817] Re: [Ubuntu 15.04] Ubuntu should audit account modification events

[Luciano Chavez]

** Package changed: ubuntu = audit (Ubuntu)

** Changed in: audit (Ubuntu)
 Assignee: (unassigned) = Taco Screen team (taco-screen-team)

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

Title:
  [Ubuntu 15.04] Ubuntu should audit account modification events

Status in audit package in Ubuntu:
  New

Bug description:
  Ubuntu should log user modification events to the system audit trail
  (/var/log/audit/audit.log) but does not.

  Steps to Verify:

  - Install Ubuntu 14.04 on an x86_64 VM
  - apt install auditd
  - useradd testuser
  - ausearch -i

  Expected Results:

  An audit record should be appended to the audit trail that indicates
  testuser was added.

  Actual Results:

  An appropriate audit event was not appended to the audit trail.  A
  record is logged in /var/log/auth.log.

  Discussion:

  Auditable system events should be logged in the standard audit trail
  via the Linux audit subsystem. Doing so provides a central location
  where sysadmins can monitor security events. The Linux audit subsystem
  can be used to meet Common Criteria and compliance hardening standards
  requirements. OSPP v2.0
  [https://www.commoncriteriaportal.org/files/ppfiles/pp0067b_pdf.pdf]
  should provide a good reference for commonly logged audit events and
  other audit requirements.

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

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

[Touch-packages] [Bug 1410522] Re: auditctl command is throwing Error detecting machine type on Ubuntu 15.04

[Luciano Chavez]

** Package changed: ubuntu = audit (Ubuntu)

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

Title:
  auditctl command is throwing Error detecting machine type on Ubuntu
  15.04

Status in audit package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  auditctl is throwing Error detecting machine type error
   
  ---uname output---
  Linux ubuntu 3.18.0-8-generic #9-Ubuntu SMP Mon Jan 5 22:52:15 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 

  ---Steps to Reproduce---
  Install a Power VM LPAR with Ubuntu 15.04 ISO.
  Then execute the below test scenarios on the same.

  root@ubuntu:~# auditctl -A exit,always -S mkdir
  Error detecting machine type
  root@ubuntu:~# which auditctl
  /sbin/auditctl

  root@ubuntu:~# dpkg -S /sbin/auditctl
  auditd: /sbin/auditctl

  root@ubuntu:~# dpkg --list | grep auditd
  ii  auditd1:2.3.7-1ubuntu1
  ppc64el  User space tools for security auditing

  root@ubuntu:~# dpkg --list | grep libaudit
  ii  libaudit-common   1:2.3.7-1ubuntu1
  all  Dynamic library for security auditing - common files
  ii  libaudit1:ppc64el 1:2.3.7-1ubuntu1
  ppc64el  Dynamic library for security auditing

  I found a discussion of the need for ppc64le support in audit in the
  archives for the linux-audit ml

  https://www.redhat.com/archives/linux-
  audit/2014-December/msg3.html

  The full changeset for the ppc64le support is in trunk upstream:

  https://fedorahosted.org/audit/changeset/1013

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

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

[Touch-packages] [Bug 1400420] Re: [Ubuntu 15.04] Mesa/gallium: Fix Altivec pack intrinsics for little endian

[Luciano Chavez]

** Package changed: ubuntu = mesa (Ubuntu)

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

Title:
  [Ubuntu 15.04] Mesa/gallium:  Fix Altivec pack intrinsics for little
  endian

Status in mesa package in Ubuntu:
  New

Bug description:
  Please ensure the following patch is incorporated into the mesa
  package for correct behavior on ppc64el:

  http://lists.freedesktop.org/archives/mesa-dev/2014-August/064711.html

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

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

[Touch-packages] [Bug 1389302] Re: cannot create ppc64 kvm guest in libvirt

[Luciano Chavez]

** Package changed: ubuntu = apparmor (Ubuntu)

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

Title:
  cannot create ppc64 kvm guest in libvirt

Status in “apparmor” package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Cannot start my RHEL guest on an OpenPOWER system using libvirt/kvm

  ---uname output---
  Linux partpalm28 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:06:19 UTC 
2014 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = p8 openpower  

  ---Steps to Reproduce---
   Try to create a kvm guest using virsh create and a RHEL  (6.5 or later) ISO. 
During create, you will get the error 
  tyan@partpalm28:~$ virsh create rhel*
  error: Failed to create domain from rhel65.xml
  error: internal error: early end of file from monitor: possible problem:
  qemu: hardware error: qemu: could not load LPAR rtas 
'/usr/share/qemu/spapr-rtas.bin' 

  The problem is that /usr/share/qemu/spar-rtas.bin is symlinked to 
../slof/spapr-rtas.bin  and /usr/share/slof is not included in the libvirt 
apparmor profile as acceptable.  The fix is to change 
/etc/apparmor.d/abstractions/libvirt-qemu  as follows:
  *** libvirt-qemuFri Oct 31 09:58:34 2014
  --- libvirt-qemu+   Fri Oct 31 09:58:25 2014
  ***
  *** 73,78 
  --- 73,79 
  /usr/share/openbios/** r,
  /usr/share/openhackware/** r,
  /usr/share/proll/** r,
  +   /usr/share/slof/** r,
  /usr/share/vgabios/** r,
  /usr/share/seabios/** r,
  /usr/share/ovmf/** r,

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

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

[Touch-packages] [Bug 1378114] Re: Ubuntu 14.10 bash is still vulnerable to CVE-2014-6277 and CVE-2014-7186.

[Luciano Chavez]

** Package changed: ubuntu = bash (Ubuntu)

** Changed in: bash (Ubuntu)
   Status: New = Confirmed

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-6277

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7186

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

Title:
  Ubuntu 14.10 bash is still vulnerable to CVE-2014-6277 and
  CVE-2014-7186.

Status in “bash” package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  Ubuntu 14.10 bash still vulnerable to CVE-2014-6277 and CVE-2014-7186.

  ---uname output---
  manu@ubuntu:~$ uname -a Linux ubuntu 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 
1 17:24:38 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8284-22A 

  ---Steps to Reproduce---
  Ubuntu 14.10 bash still vulnerable to CVE-2014-6277 and CVE-2014-7186.

  1. install Oct 5 ppc64le ubuntu 14.10 ISO image.

  2. upgrade to latest bash.
  manu@ubuntu:~$  sudo apt-get update; apt-get install --only-upgrade bash

  manu@ubuntu:~$ bash --version
  GNU bash, version 4.3.27(1)-release (powerpc64le-unknown-linux-gnu)
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html

  This is free software; you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.


  
  3. run the shellshocker.net tests to see if the bash is still vulnerable.

  manu@ubuntu:~$ curl https://shellshocker.net/shellshock_test.sh | bash
% Total% Received % Xferd  Average Speed   TimeTime Time  
Current
   Dload  Upload   Total   SpentLeft  Speed
  100  2533  100  25330 0   3675  0 --:--:-- --:--:-- --:--:--  3671
  CVE-2014-6271 (original shellshock): not vulnerable
  bash: line 16: 14233 Segmentation fault  bash -c f() { x() { _;}; x() { 
_;} a; } 2 /dev/null
  CVE-2014-6277 (segfault): VULNERABLE
  CVE-2014-6278 (Florian's patch): not vulnerable
  CVE-2014-7169 (taviso bug): not vulnerable
  bash: line 49: 14250 Segmentation fault  bash -c 'true EOF EOF EOF 
EOF EOF EOF EOF EOF EOF EOF EOF EOF EOF EOF' 2 /dev/null
  CVE-2014-7186 (redir_stack bug): VULNERABLE
  CVE-2014-7187 (nested loops off by one): not vulnerable
  CVE-2014- (exploit 3 on http://shellshocker.net/): not vulnerable

  based on the test suite results, CVE-2014-6277 and CVE-2014-7186 are
  still vulnerable on Ubuntu 14.10.

  Other similar tests in these areas which still fails:

  1. manu@ubuntu:~$ bash -c f(){ x(){ _;};x(){ _;}a;}
  Segmentation fault

  2. manu@ubuntu:/tmp$ bash -c ':abcdefghijklmn'
  Segmentation fault

  
  3. manu@ubuntu:/tmp$ bash -c 'true EOF EOF EOF EOF EOF EOF EOF 
EOF EOF EOF EOF EOF EOF EOF' || echo CVE-2014-7186 vulnerable, 
redir_stack
  Segmentation fault
  CVE-2014-7186 vulnerable, redir_stack

  4. manu@ubuntu:~$ bash -c f() { x() { _;}; x() { _;} a; } 2/dev/null || 
echo vulnerable
  Segmentation fault
  vulnerable

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

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

[Touch-packages] [Bug 1376281] Re: gdb: Can't read symbols from system-supplied DSO at 0x3fffb7fa0000: File truncated

[Luciano Chavez]

** Package changed: ubuntu = gdb (Ubuntu)

** Changed in: gdb (Ubuntu)
   Status: New = Confirmed

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

Title:
  gdb: Can't read symbols from system-supplied DSO at 0x3fffb7fa:
  File truncated

Status in “gdb” package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  GDB produces an odd message about a failure to read symbols from the system 
DSO when running executables on LE Ubuntu 14.10 with 3.16 kernel.  This is a 
regression from LE Ubuntu 14.04, where the message is not produced.

  Bad case:

  $ uname -r
  3.16.0-6-generic
  $ gdb /bin/ls
  GNU gdb (Ubuntu 7.7.91.20140723-0ubuntu1) 7.7.91.20140723-cvs
  ...
  (gdb) run
  Starting program: /bin/ls 
  Can't read symbols from system-supplied DSO at 0x3fffb7fa: File truncated
  ...
  [Inferior 1 (process 1573) exited normally]
  (gdb) 

  Note the Can't read symbols... message.

  Good case (LE Ubuntu 14.04):

  $ uname -r
  3.13.0-32-generic
  $ gdb /bin/ls
  GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
  ...
  (gdb) run
  Starting program: /bin/ls 
  ...
  [Inferior 1 (process 91140) exited normally]
  (gdb)

  I haven't tried on the 3.15 kernel, so I don't know if the problem is
  sensitve to the 3.16 kernel being ELFv2.

   
  ---uname output---
  Linux tul115p1 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8286-42A 
   
  ---Steps to Reproduce---
   See description; occurs when running any application under gdb.
   
  The failing output above is with the 3.16 kernel supplied by Ubuntu, so the 
problem happens both with locally-built and Canonical/Ubuntu-supplied kernels 
on 14.10.

  This issue was recently fixed on upstream binutils-gdb:

  https://sourceware.org/ml/gdb-patches/2014-09/msg00594.html

  The attached patch against gdb 7.8-0ubuntu1 for Ubuntu 14.10 fixes the
  issue.

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

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

[Touch-packages] [Bug 1370259] Re: apport fails to collect nvram specific information

[Luciano Chavez]

Please ignore the first diff. The second diff is the correct one.
Thanks.

** Package changed: ubuntu = 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/1370259

Title:
  apport fails to collect nvram specific information

Status in “apport” package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  apport fails to collect nvram specific information
   
  ---uname output---
  3.16.0-10-generic
   
  Machine Type = POWER8 

  ---Steps to Reproduce---
   
  1) Install Ubuntu 14.10 in Power non-virtualized environment.
  2) Install apport package
  3) Run following command to verify if apport collects power specific 
information.

 apport-cli -f -p linux-generic --save=/home/sachin/linux.apport

  The command fails with following error :

  root@lep8d:/home/sachin# apport-cli -f -p linux-generic
  --save=/home/sachin/linux.apport

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ...tar: Removing leading `/' from member names
  ERROR: hook /usr/share/apport/general-hooks/powerpc.py crashed:
  Traceback (most recent call last):
File /usr/lib/python3/dist-packages/apport/report.py, line 197, in 
_run_hook
  symb['add_info'](report, ui)
File /usr/share/apport/general-hooks/powerpc.py, line 72, in add_info
  'nvram': 'cat /dev/nvram',
File /usr/lib/python3/dist-packages/apport/hookutils.py, line 469, in 
attach_root_command_outputs
  buf = f.read().strip()
File /usr/lib/python3.4/codecs.py, line 313, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb5 in position 1: 
invalid start byte
  ...
  root@lep8d:/home/sachin# 
   
  Userspace tool common name: apport 
   
  Following version of apport is installed.

  root@lep8d:/home/sachin# dpkg --list | grep apport
  ii  apport 2.14.7-0ubuntu1
all  automatically generate crash reports for 
debugging
  ii  apport-symptoms0.20   
all  symptom scripts for apport
  ii  python-apport  2.14.7-0ubuntu1
all  Python library for Apport crash report 
handling
  ii  python3-apport 2.14.7-0ubuntu1
all  Python 3 library for Apport crash report 
handling
  root@lep8d:/home/sachin#

  Looking at the code we are doing a cat /dev/nvram to the apport output file 
which doesn't sounds right to me. I would think using the function add_tar() 
creating a tar file and copying the content as a ascii file at end of apport 
output file more appropriate.
  One dummy question remaining, how getting the tar file from the ascii output 
file if we need to ? ( that's also true to validate the content of the 
DeviceTree tar file).

  Would suggest following patch:
  --- powerpc.py2014-09-10 10:28:18.824002770 -0400
  +++ powerpc.py.old2014-09-04 06:33:16.0 -0400
  @@ -69,8 +69,8 @@
   'cpu_runmode': 'ppc64_cpu --run-mode',
   'cpu_freq': 'ppc64_cpu --frequency',
   'cpu_dscr': 'ppc64_cpu --dscr',
  +'nvram': 'cat /dev/nvram',
   })
  -add_tar(report, '/dev/nvram', 'nvram.tar')
   attach_file_if_exists(report, '/var/log/platform')
   
   if ispSeries and not isPowerKVM:

  thanks
   diff -urN powerpc.py.old powerpc.py 
  --- powerpc.py.old2014-09-04 06:33:16.0 -0400
  +++ powerpc.py2014-09-10 10:28:18.824002770 -0400
  @@ -69,8 +69,8 @@
   'cpu_runmode': 'ppc64_cpu --run-mode',
   'cpu_freq': 'ppc64_cpu --frequency',
   'cpu_dscr': 'ppc64_cpu --dscr',
  -'nvram': 'cat /dev/nvram',
   })
  +add_tar(report, '/dev/nvram', 'nvram.tar')
   attach_file_if_exists(report, '/var/log/platform')
   
   if ispSeries and not isPowerKVM:

  Initial Launchpad bug id #1336462 implemented feature support

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

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

[Touch-packages] [Bug 1368302] Re: eglibc source tests are failing in Ubuntu 14.10 guest

[Luciano Chavez]

** Package changed: ubuntu = eglibc (Ubuntu)

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

Title:
  eglibc source tests are failing in Ubuntu 14.10 guest

Status in “eglibc” package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  eglibc source tests are failing in Ubuntu 14.10 guest

  ---uname output---
  Linux ubuntu 3.16.0-12-generic #18-Ubuntu SMP Mon Sep 1 13:03:43 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 

  ---Steps to Reproduce---
  Install a P8 system with Power KVM and then install Ubuntu 14.10 guest.
  Then try to build and execute the eglibc source test suites as below.

  root@ubuntu:~# apt-get source eglibc
  root@ubuntu:~# cd eglibc-2.19/
  root@ubuntu:~/eglibc-2.19# dpkg-buildpackage -b 21 | tee eglibclog

  #
  # Testsuite failures, someone should be working towards
  # fixing these! They are listed here for the purpose of
  # regression testing during builds.
  # Format: Failed test, Error Make error code [(ignored)]
  #
  annexc.out, Error 1 (ignored)
  run-conformtest.out, Error 1 (ignored)
  tst-cancelx17.out, Error 1
  tst-cpuclock2.out, Error 1
  ***
  Encountered regressions that don't match expected failures 
(debian/testsuite-checking/expected-results-powerpc64le-linux-gnu-libc):
  tst-cancelx17.out, Error 1
  TEST tst-cancelx17.out:
  going to cancel tf in-time
  going to cancel tf2 in-time
  in-time cancellation succeeded
  aio_cancel failed
  going to cancel tf early
  going to cancel tf2 early
  early cancellation succeeded
  Encountered progressions that don't match expected failures:
  check-localplt.out, Error 1
  tst-cputimer1.out, Error 1
  tst-mqueue5.out, Error 1
  tst-waitid.out, Error 1
  debian/rules.d/build.mk:123: recipe for target 
'/root/eglibc-2.19/stamp-dir/check_libc' failed
  make: *** [/root/eglibc-2.19/stamp-dir/check_libc] Error 1
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

tried the same steps in the provided  VM (192.168.122.70) and dpkg-
  buildpackage -b completed fine.

  ouch /root/eglibc-2.19/stamp-dir/binaryinst_libnss-files-udeb
   dpkg-genchanges -b ../eglibc_2.19-0ubuntu6_ppc64el.changes
  dpkg-genchanges: warning: package locales in control file but not in files 
list
  dpkg-genchanges: warning: package locales-all in control file but not in 
files list
  dpkg-genchanges: binary-only upload (no source code included)
   dpkg-source --after-build eglibc-2.19
  dpkg-source: info: using options from eglibc-2.19/debian/source/options: 
--compression=xz
  dpkg-buildpackage: binary-only upload (no source included)
  root@ubuntu:~/eglibc-2.19#

  Hi Rajalakshmi,

  If you grep for Testsuite failures in the eglibclog file, you get
  the below failures listed.

  
  #
  # Testsuite failures, someone should be working towards
  # fixing these! They are listed here for the purpose of
  # regression testing during builds.
  # Format: Failed test, Error Make error code [(ignored)]
  #
  annexc.out, Error 1 (ignored)
  run-conformtest.out, Error 1 (ignored)
  tst-cpuclock2.out, Error 1
  ***
  Passed regression testing. No new failures, no changed error values.
  TEST annexc.out:
  The following identifiers will be ignored since the compiler defines them
  by default:
  pixel
  bool
  vector
  unix
  linux
  Tested files:
  === aio.h ===
  *  invalid macro `SIGEV_THREAD_ID'
  *  invalid macro `sigev_notify_function'
  *  invalid macro `sigev_notify_attributes'
  ** macro `FD_CLOEXEC' not defined
  ** macro `F_DUPFD' not defined
  ** macro `F_GETFD' not defined
  ** macro `F_GETFL' not defined
  ** macro `F_GETLK' not defined
  ** macro `F_RDLCK' not defined
  ** macro `F_SETFD' not defined
  ** macro `F_SETFL' not defined
  ** macro `F_SETLK' not defined
  ** macro `F_SETLKW' not defined
  ** macro `F_UNLCK' not defined
  ** macro `F_WRLCK' not defined
  ** macro `O_ACCMODE' not defined
  ** macro `O_APPEND' not defined
  ** macro `O_CREAT' not defined
  ** macro `O_DSYNC' not defined
  ** macro `O_EXCL' not defined
  ** macro `O_NOCTTY' not defined
  ** macro `O_NONBLOCK' not defined
  ** macro `O_RDONLY' not defined
  ** macro `O_RDWR' not defined
  ** macro `O_RSYNC' not defined
  ** macro `O_SYNC' not defined
  ** macro `O_TRUNC' not defined
  ** macro `O_WRONLY' not defined
  ** macro `SA_NOCLDSTOP' not defined
  ** macro `SA_SIGINFO' not defined
  ** macro `SIGABRT' not defined
  ** macro `SIGALRM' not defined
  ** macro `SIGBUS' not defined
  ** macro `SIGCHLD' not defined
  ** macro `SIGCONT' not defined
  ** macro `SIGEV_SIGNAL' not defined
  ** macro `SIGFPE' not defined
  ** macro `SIGHUP' not defined
  ** macro `SIGILL' not defined
  ** macro `SIGINT' not defined
  ** macro `SIGKILL' not defined
  ** macro `SIGPIPE' not defined
  ** macro `SIGQUIT' not defined
  ** macro `SIGRTMAX' not defined
  ** macro 

[Touch-packages] [Bug 1367832] Re: gdbserver gets conditionals wrong on ppc64le

[Luciano Chavez]

** Package changed: ubuntu = gdb (Ubuntu)

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

Title:
  gdbserver gets conditionals wrong on ppc64le

Status in “gdb” package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Single stepping has issues with conditionals when debugging with gdbserver, 
taking the wrong path through the code.
   
  Machine Type = Power8 LE 
   
  ---Steps to Reproduce---
   ubuntu@ubuntu:~$ cat  test.c
  #include stdio.h
  #include stdlib.h

  typedef enum {
Success = 0,
Failure,
  } dev_status_t;

  dev_status_t getDeviceCount(int *countp)
  { 
*countp = 1;
return Success;
  }

  int
  main(int argc, char **argv)
  { 
int count = 0;
dev_status_t status = getDeviceCount(count);

if (status != Success)
  { 
printf(getDeviceCount returned %d\n, (int)status);
printf(Result = FAIL\n);
exit(EXIT_FAILURE);
  }

if (count == 0)
  { 
printf(There are no devices\n);
  }
else
  { 
printf(Detected %d device(s)\n, count);
  }

exit(EXIT_SUCCESS);
  }

  ubuntu@ubuntu:~$ gcc -g test.c -o test
  ubuntu@ubuntu:~$ gdbserver : ./test
  Process ./test created; pid = 25600
  Listening on port 
  Remote debugging from host 127.0.0.1

  In another terminal, run gdb:

  ubuntu@ubuntu:~$ gdb ./test 
  GNU gdb (Ubuntu 7.8-0ubuntu1) 7.8
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type show copying
  and show warranty for details.
  This GDB was configured as powerpc64le-linux-gnu.
  Type show configuration for configuration details.
  For bug reporting instructions, please see:
  http://www.gnu.org/software/gdb/bugs/.
  Find the GDB manual and other documentation resources online at:
  http://www.gnu.org/software/gdb/documentation/.
  For help, type help.
  Type apropos word to search for commands related to word...
  Reading symbols from ./test...done.
  (gdb) target remote :
  Remote debugging using :
  Reading symbols from /lib64/ld64.so.2...(no debugging symbols found)...done.
  Loaded symbols for /lib64/ld64.so.2
  Can't read symbols from system-supplied DSO at 0x3fffb7fa: File truncated
  0x3fffb7fc1a60 in ?? () from /lib64/ld64.so.2
  (gdb) b main
  Breakpoint 1 at 0x16d4: file test.c, line 17.
  (gdb) cont
  Continuing.

  Breakpoint 1, main (argc=1, argv=0x3088) at test.c:17
  17  {
  (gdb) next
  18int count = 0;
  (gdb) next
  19dev_status_t status = getDeviceCount(count);
  (gdb) next
  21if (status != Success)
  (gdb) next
  23printf(getDeviceCount returned %d\n, (int)status);
  (gdb) print status
  $1 = Success

  Notice the program took the wrong direction on if() block.
   
  ---uname output---
  Linux ubuntu 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:45:12 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Userspace tool common name: gdbserver

  The root cause of this issue was a routine that collect/supply ptrace
  registers on gdbserver, originally developed for BE only.

  The attached patch against gdb 7.8-0ubuntu1 sources fixes this problem
  on gdbserver. It was already accepted and committed upstream:

  https://sourceware.org/ml/gdb-patches/2014-09/msg00181.html

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

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

[Touch-packages] [Bug 1365664] Re: gdb source test suites are failing in Ubuntu14.10

[Luciano Chavez]

** Package changed: ubuntu = gdb (Ubuntu)

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

Title:
  gdb source test suites are failing in Ubuntu14.10

Status in “gdb” package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  gdb source test suites are failing in Ubuntu14.10
   
  Machine Type = P8 
   
  ---Steps to Reproduce---
  Install a P8 system with Power KVM and then install Ubuntu 14.10 guest.
  Then try to build and execute the gdb source test suites as below.

  root@ubuntu:~# apt-get source gdb
  root@ubuntu:~# cd gdb-7.8/
  root@ubuntu:~/gdb-7.8# dpkg-buildpackage -b 21 | tee gdblog

  === gdb Summary ===

  # of expected passes25009
  # of unexpected failures287
  # of unexpected successes   2
  # of expected failures  66
  # of unknown successes  1
  # of known failures 59
  # of unresolved testcases   3
  # of untested testcases 19
  # of unsupported tests  100

   
  ---uname output---
  Linux ubuntu 3.16.0-11-generic #16-Ubuntu SMP Mon Aug 25 20:02:00 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  I've retested gdb from Ubuntu 14.04 (gdb-7.7-0ubuntu3.1) in the Ubuntu 14.10 
VM provided by Pavaman and the number of failures curiously increased to 250 
(in comparison to less than 140 on 14.04), which leads me to believe that there 
is something in the environment of Ubuntu 14.10 compromising gdb functionality 
in several testcases.

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

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

[Touch-packages] [Bug 1353989] Re: systemd failure messages pop up on console as well as seen in dmesg

[Luciano Chavez]

** Package changed: ubuntu = systemd (Ubuntu)

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

Title:
  systemd failure messages pop up on console as well as seen in dmesg

Status in “systemd” package in Ubuntu:
  Confirmed

Bug description:
  Problem Description
  --
  Lot of systemd failure messages pops up on console as well as seen in dmesg

  ---uname output---
  Linux u10vm14 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Power 8 
   
  ---Debugger---
  A debugger is not configured
   
  Steps to Reproduce
  --
  1)  Install Ubuntu 14.10 August 6th build
  2)  After the installation while logging in seen multiple systemd failed 
messages on console and on dmesg

  Failed messages:
  [   58.564179] systemd-logind[1420]: Failed to enable subscription: No such 
method 'Subscribe'
  [   58.576888] systemd-logind[1420]: New seat seat0.
  [   58.580312] systemd-logind[1420]: Failed to start unit user@1000.service: 
Unknown unit: user@1000.service
  [   58.581059] systemd-logind[1420]: Failed to start user service: Unknown 
unit: user@1000.service
  [   58.584561] systemd-logind[1420]: New session c1 of user ubuntu.
  [11293.015056] init: hvc0 main process ended, respawning
  [11293.045923] systemd-logind[1420]: Failed to abandon scope session-c1.scope
  [11293.046499] systemd-logind[1420]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc1_2escope
  [17818.110774] systemd-logind[1420]: Failed to start unit user@0.service: 
Unknown unit: user@0.service
  [17818.111944] systemd-logind[1420]: Failed to start user service: Unknown 
unit: user@0.service
  [17818.115571] systemd-logind[1420]: New session c2 of user root.
  [18812.879680] systemd-logind[1420]: New session 22 of user root.
  [18814.620794] systemd-logind[1420]: Failed to abandon scope session-22.scope
  [18814.622186] systemd-logind[1420]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2d22_2escope

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

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