date:20171204

This bug was fixed in the package binutils - 2.29.1-10ubuntu1

---
binutils (2.29.1-10ubuntu1) bionic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

binutils (2.29.1-10) unstable; urgency=medium

  * Update, taken from the 2.29 branch 20171201.
- Fix PR gold/22233, segfault in relocate_erratum_stub on aarch64.
- Update local fix for PR gold/20765, internal error in fix_errata on
  aarch64 (Peter Smith). LP: #1638902.
  * binutils-source: Depend on python3 instead of python.
  * Override m68k, powerpcspe and m68k buildd admins to run the testsuite.

 -- Matthias Klose   Fri, 01 Dec 2017 02:49:13 +0100

** Changed in: binutils (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
   [2.27 Regression] gold internal error in fix_errata on aarch64-linux-
  gnu

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released

Bug description:
  seen with binutils from the 2.27 branch:

  $ sh link.sh 
  ld.gold: internal error in fix_errata, at ../../gold/aarch64.cc:1960

  This works with the BFD linker, or when dropping the --fix-
  cortex-a53-843419 option.

  The test cases comes from the build of the gitit package on Ubuntu 16.10,
  see https://launchpad.net/ubuntu/+source/gitit/0.12.1.1+dfsg-2build7

  The package built successfully with binutils 2.26.1

  test case at
  http://people.canonical.com/~doko/tmp/tst.tar.xz

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

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

[Touch-packages] [Bug 1721600] Re: usb canon pixma g2000 not detected

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

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

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

Title:
  usb canon pixma g2000 not detected

Status in cups package in Ubuntu:
  Expired

Bug description:
  i bought a new printer that doesn't get detected when i connect to the
  usb port on my computer. doesn't even show any changes happening when
  i track connections to the usb

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct  5 23:02:33 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-29 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat: device for G2000series-TurboPrint: parallel:/dev/lp0
  MachineType: LENOVO 2347CTO
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/G2000series-TurboPrint.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/G2000series-TurboPrint.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET45WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2347CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET45WW(1.20):bd08/07/2012:svnLENOVO:pn2347CTO:pvrThinkPadT430:rvnLENOVO:rn2347CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2347CTO
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1717490] Re: LightDM keeps plain text login password in memory

2017-12-04 Thread Robert Ancell

** Changed in: lightdm
   Importance: Undecided => Medium

** Changed in: lightdm
   Status: New => Triaged

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

Title:
  LightDM keeps plain text login password in memory

Status in Light Display Manager:
  Triaged
Status in lightdm package in Ubuntu:
  New

Bug description:
  The lightdm process keeps the user password in memory, if the lightdm-
  greeter is used. This seems to be the case on Ubuntu up to the recent
  17.04 version. The issue was validated with lightdm  1.22.0-0ubuntu2
  (17.04) and 1.10.6-0ubuntu1 (14.04)

  Example:

  root@victim:~# ps fauxw | grep lightdm
  root   889  0.0  0.2 379344  8436 ?SLsl 12:43   0:00 
/usr/sbin/lightdm
  root   968  1.3  1.8 379900 72804 tty7 Ssl+ 12:43   0:01  \_ 
/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  root  1103  0.0  0.1 243564  6724 ?Sl   12:43   0:00  \_ lightdm 
--session-child 12 19
  root  2074  0.0  0.0  21328   976 pts/0S+   12:45   0:00  
\_ grep --color=auto lightdm
  root@victim:~# gcore 1103
  [...]
  Saved corefile core.1103
  root@victim:~# strings core.1103 | grep -A5 -B5 secretpassword
  ttyCH0
  ttyCH1
  #...ttyCH63
  # Moxa Intellio serial
  _pammodutil_getspnam_svbl_2
  secretpassword
  gkr_system_authtok
  -UN*X-FAIL-svbl
  svbl
  1000:1000:svbl,,,
  /home/svbl
  root@victim:~# 

  As far as I can tell it seems that the password is not cleared form
  memory after passing it to PAM. This is not a direct vulnerability or
  breaking a security boundary (root access required to dump the memory)
  but it seems not to be necessary for lightdm to keep the pw in memory.

  A similar issue was reported to gnome-keyring-daemon, where the need
  of keeping the password is a bit more understandable
  (https://bugzilla.gnome.org/show_bug.cgi?id=764014).

  Do you see any reason why LightDM needs to keep the password in
  memory?

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

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

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2017-12-04 Thread Steve Langasek

** Changed in: debconf (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Invalid
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2017-12-04 Thread Facundo

** Changed in: debconf (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Invalid
Status in debconf package in Ubuntu:
  Fix Released

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Touch-packages] [Bug 1713457] Re: DNS search domain not removed from resolv.conf on disconnect

2017-12-04 Thread Paul Natsuo Kishimoto

So this has occurred again:

=

~$ nmcli -f IP4.ADDRESS,IP4.DOMAIN dev show
IP4.ADDRESS[1]: 10.0.0.156/24
IP4.DOMAIN[1]:  hsd1.ma.comcast.net


IP4.ADDRESS[1]: 127.0.0.1/8

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

nameserver 127.0.0.53
search hsd1.ma.comcast.net utopia.net mit.edu

=

Note the extra entries in the 'search' line of resolv.conf—these were
from networks I was recently connected to.

** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=712818
   Importance: Unknown
   Status: Unknown

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

Title:
  DNS search domain not removed from resolv.conf on disconnect

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  When I connect to a wireless network that sets a DNS search domain
  name via DHCP, the line 'search ' is added to /etc/resolv.conf
  as expected.  But if I then disconnect and connect to a different
  network, it is not removed from resolv.conf.  If the second network
  also sets a search domain name, that one gets appended to resolv.conf
  along with the first one, and so on.  Depending on the network, this
  can cause DNS leaks, name resolution failures, or other misbehavior.

  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 172.20.20.1 dev wlp3s0 proto static metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC

2017-12-04 Thread Christopher M. Penalver

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  Cannot pair BLE remote devices when using combo BT SoC

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in bluez source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in bluez source package in Zesty:
  New
Status in linux source package in Zesty:
  Fix Committed
Status in bluez source package in Artful:
  New
Status in linux source package in Artful:
  Fix Committed

Bug description:
  It has been observed that sometimes it is not possible to pair with
  BLE remote devices when the host system is using combo (WiFi + BT)
  chip.

  The root cause of the disconnection has been identified as coming from
  the internal to bluez timeout. If bluez does not hear any reply from for
  two seconds the link is automagically disconnected. The reason fro the
  silence is not however a failure of the remote device but quite often a
  delay in the WiFi/BT combo driver that causes the packages not to reach
  the bluez stack.

  [Impact]

  Not possible to pair BLE remote devices such as sensors and such with
  Ubuntu when the host system uses BT+WiFi combo SoC. The connection
  attempt is disturbed with a timeout.

  [Fix]

  It has been fixed by increasing the timeout value from 2 seconds to
  4 seconds. It is enough for the events to reach the stack (measured
  that it takes between 3 and 3.5 seconds).

  [Testcase]

  Tested with the device that failed to connect to Ubuntu Core gateway.
  It fails w/o the patch, it connects just fine with the patch applied.

  [Regression Potential]

  Very small. The increased timeout is taken into consideration only for
  new and scan report triggered connections. It will not make any already
  working device to fail to pair.

  [Other Info]

  The bug has been discussed and fixed here:

  https://marc.info/?l=linux-bluetooth&m=150824844606937&w=2

  [Patch]

  https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
  next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

  The patch has been accepted by the upstream and will be a part of the next
  kernel release. Currently in the bluetooth-next tree.

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

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

[Touch-packages] [Bug 1728617] Re: Scrolled window broken when containing an eventbox

This bug was fixed in the package gtk+3.0 - 3.22.26-2ubuntu1

---
gtk+3.0 (3.22.26-2ubuntu1) bionic; urgency=medium

  * Merge with Debian. Remaining changes:
+ Install a settings.ini file to set our themes
+ Enable Mir backend
+ debian/control.in:
  - Build-depend on adwaita-icon-theme-full for icon name check test
+ debian/rules: Mark additional known test failures:
  - box-shadow-changes-modify-clip.ui
  - label-text-shadow-changes-modify-clip.ui
+ Ubuntu-specific patches:
  - 073_treeview_almost_fixed.patch
  - bzg_gtkcellrenderer_grabbing_modifier.patch
  - ubuntu_gtk_custom_menu_items.patch
  - print-dialog-show-options-of-remote-dnssd-printers.patch
  - uimanager-guard-against-nested-node-updates.patch
  - x-canonical-accel.patch
  - message-dialog-restore-traditional-look-on-unity.patch
  - 0001-gtk-reftest-Force-icon-theme-to-Adwaita.patch
  - restore_filechooser_typeaheadfind.patch
  - 0001-calendar-always-emit-day-selected-once.patch
  - 0001-gtkwindow-set-transparent-background-color.patch
  - ubuntu_fileselector_behaviour.patch
  - unity-border-radius.patch
  - unity-headerbar-maximized-mode.patch
  - gtksocket-unscale-before-sending-configurenotify.patch
  - no_content_hub.patch
  * Drop Ubuntu-specific 074_eventbox_scroll_mask.patch
which introduced a bug seen in the Lollypop music app (LP: #1728617)

gtk+3.0 (3.22.26-2) unstable; urgency=medium

  [ Simon McVittie ]
  * Set Rules-Requires-Root to no
  * Add a Lintian override to silence warnings about the non-standard
name of libgail-3-0, which should really have been libgailutil-3-0
but isn't going to be changed now

  [ Jeremy Bicha ]
  * Add git_text-view-support-emoji-chooser.patch:
- Offer right-click "Insert Emoji" menu item for GtkTextView too

 -- Jeremy Bicha   Tue, 28 Nov 2017 17:56:41 -0500

** Changed in: gtk+3.0 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Scrolled window broken when containing an eventbox

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Triaged

Bug description:
  https://github.com/gnumdk/lollypop/issues/1279

  Ubuntu is shipping 074_eventbox_scroll_mask.patch, this patch is
  really strange, it adds a scroll mask on all eventbox breaking all
  applications using eventbox in scrolled windows.

  This patch is not in Debian and should be removed!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1728617/+subscriptions

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

[Touch-packages] [Bug 459730] Re: rsyslog doesn't create /dev/xconsole

2017-12-04 Thread Tom Maher

Wow, eight years and this is still a bug on Xenial. This is bordering on
incompetence

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

Title:
  rsyslog doesn't create /dev/xconsole

Status in One Hundred Papercuts:
  Fix Released
Status in rsyslog package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: rsyslog

  Looks like this was missed in the move to upstart.

  This function was called in init.d/rsyslog start:

  create_xconsole() {
  if [ ! -e /dev/xconsole ]
  then
  mknod -m 640 /dev/xconsole p
  chown root:adm /dev/xconsole
  [ -x /sbin/restorecon ] && /sbin/restorecon /dev/xconsole
  fi
  }

  I can't find any reference to it now. If this is old school then it should be 
re
  moved from the config.

  rsyslog:
Installed: 4.2.0-2ubuntu5

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

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

[Touch-packages] [Bug 1717490] Re: LightDM keeps plain text login password in memory

** Information type changed from Private Security to Public Security

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

Title:
  LightDM keeps plain text login password in memory

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  The lightdm process keeps the user password in memory, if the lightdm-
  greeter is used. This seems to be the case on Ubuntu up to the recent
  17.04 version. The issue was validated with lightdm  1.22.0-0ubuntu2
  (17.04) and 1.10.6-0ubuntu1 (14.04)

  Example:

  root@victim:~# ps fauxw | grep lightdm
  root   889  0.0  0.2 379344  8436 ?SLsl 12:43   0:00 
/usr/sbin/lightdm
  root   968  1.3  1.8 379900 72804 tty7 Ssl+ 12:43   0:01  \_ 
/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  root  1103  0.0  0.1 243564  6724 ?Sl   12:43   0:00  \_ lightdm 
--session-child 12 19
  root  2074  0.0  0.0  21328   976 pts/0S+   12:45   0:00  
\_ grep --color=auto lightdm
  root@victim:~# gcore 1103
  [...]
  Saved corefile core.1103
  root@victim:~# strings core.1103 | grep -A5 -B5 secretpassword
  ttyCH0
  ttyCH1
  #...ttyCH63
  # Moxa Intellio serial
  _pammodutil_getspnam_svbl_2
  secretpassword
  gkr_system_authtok
  -UN*X-FAIL-svbl
  svbl
  1000:1000:svbl,,,
  /home/svbl
  root@victim:~# 

  As far as I can tell it seems that the password is not cleared form
  memory after passing it to PAM. This is not a direct vulnerability or
  breaking a security boundary (root access required to dump the memory)
  but it seems not to be necessary for lightdm to keep the pw in memory.

  A similar issue was reported to gnome-keyring-daemon, where the need
  of keeping the password is a bit more understandable
  (https://bugzilla.gnome.org/show_bug.cgi?id=764014).

  Do you see any reason why LightDM needs to keep the password in
  memory?

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

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

[Touch-packages] [Bug 1735654] Re: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package

Do you have any idea why aptdaemon installed different versions of amd64
vs x86 libpulse0 packages?

Thanks

** Package changed: tiff (Ubuntu) => aptdaemon (Ubuntu)

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

Title:
  package libpulse0 (not installed) failed to install/upgrade: trying to
  overwrite shared '/etc/pulse/client.conf', which is different from
  other instances of package libpulse0:i386

Status in aptdaemon package in Ubuntu:
  New

Bug description:
  installing skype

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpulse0 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Fri Dec  1 11:41:11 2017
  DuplicateSignature: package:libpulse0:(not installed):trying to overwrite 
shared '/etc/pulse/client.conf', which is different from other instances of 
package libpulse0:i386
  ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is 
different from other instances of package libpulse0:i386
  InstallationDate: Installed on 2016-09-27 (429 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: tiff
  Title: package libpulse0 (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/pulse/client.conf', which is different from other 
instances of package libpulse0:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1735654] Re: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package libpulse0 (not installed) failed to install/upgrade: trying to
  overwrite shared '/etc/pulse/client.conf', which is different from
  other instances of package libpulse0:i386

Status in aptdaemon package in Ubuntu:
  New

Bug description:
  installing skype

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpulse0 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Fri Dec  1 11:41:11 2017
  DuplicateSignature: package:libpulse0:(not installed):trying to overwrite 
shared '/etc/pulse/client.conf', which is different from other instances of 
package libpulse0:i386
  ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is 
different from other instances of package libpulse0:i386
  InstallationDate: Installed on 2016-09-27 (429 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: tiff
  Title: package libpulse0 (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/pulse/client.conf', which is different from other 
instances of package libpulse0:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1735548] Re: Black Screen on Booting

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Black Screen on Booting

Status in xorg package in Ubuntu:
  New

Bug description:
  I have been trying to update my OS from 12.04 LTS to 16.04.3 LTS, now
  I have an AMD graphics card which indeed have created a problem that
  consist of not booting my GUI screen and now its not even letting to
  load grub. All I get to see my BIOS getting load and then purple
  screen then nothing. Followed by alert tone of ubuntu, which I can't
  see because of black screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CasperVersion: 1.376.2
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Dec  1 02:02:51 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] [1002:9648] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Sumo [Radeon HD 6480G] [103c:3564]
  LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
  MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent 
file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet 
splash --- BOOT_IMAGE=/casper/vmlinuz.efi
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.6A
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3564
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 21.46
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.6A:bd05/13/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.46:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g4 Notebook PC
  dmi.product.version: 06911320461610100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Dec  1 01:54:18 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1399027] Re: logparser doesn't understand /var/log/messages format

2017-12-04 Thread Christian Boltz

> c0n7r4 (c0n7r4) wrote:
> apparmor="AUDIT"

AUDIT events happen if your profile has a rule like
audit /tmp/tempfile/ r,
and the program is then really doing something that needs this rule (like 
getting a directory listing for /tmp/tempfile/).

"audit" means that the action is allowed (but gets logged every time),
so there's nothing aa-logprof should ask about.

So for AUDIT events, aa-logprof works as expected - those things are
already allowed, so there's nothing to ask ;-)

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

Title:
  logparser doesn't understand /var/log/messages format

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  [impact]

  This bug causes tools that use libapparmor to parse syslog and other
  logs for apparmor rejections to fail to recognize apparmor events.

  [steps to reproduce]

  [regression potential]

  The patch for this issue is confined to the log parsing portion of
  the libapparmor library. Breakages occurring here would most likely
  prevent tools that help assist the management of apparmor policy
  from working; apparmor mediation would not be impacted. libapparmor
  does provide other functionality, mostly around the aa_change_hat(3)
  and aa_change_profile(3) calls; an entirely broken library could cause
  issues for applications that make use of these from working correctly;
  however, there are tests available in the upstream package that get
  invoked by the lp:qa-regression-testing test-apparmor.py script that
  ensure these continue to function.

  [original description]

  log parsing (part of libapparmor, used by aa-logprof and aa-genprof) doesn't 
understand the format in /var/log/messages, which means it doesn't find any 
events in it.

  IIRC I've seen a similar report for the ubuntu syslog format on IRC.

  Example log line from openSUSE:

  2014-06-09T20:37:28.975070+02:00 geeko kernel: [21028.143765]
  type=1400 audit(1402339048.973:1421): apparmor="ALLOWED"
  operation="open" profile="/home/cb/linuxtag/apparmor/scripts/hello"
  name="/dev/tty" pid=14335 comm="hello" requested_mask="rw"
  denied_mask="rw" fsuid=1000 ouid=0

  (Workaround: use auditd / audit.log)

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

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

[Touch-packages] [Bug 1561278] Re: internal sound card not detected HP X2

2017-12-04 Thread Swâmi Petaramesh

I never got any sound out of it so far, but for the record, With Manjaro
Linux and kernel 4.14 and 4.15, the sound card is recognized along with
its HDMI outputs.

Although I haven't plugged anything on the HDMI port, from my readings I
expect that it should work.

However the internal speakers still don't, so I expect something from
kernel 4.16 or 4.17  ;-)

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

Title:
  internal sound card not detected HP X2

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  HP Pavilion X2 - No sound card detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Mar 23 18:18:32 2016
  InstallationDate: Installed on 2016-03-18 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 813E
  dmi.board.vendor: HP
  dmi.board.version: 34.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1736265] [NEW] dbus init script does not work

2017-12-04 Thread Christopher Yeleighton

Public bug reported:

The following command fails:

test -x $DAEMON

First of all, the command is wrong, it should be

test -x "$DAEMON"

Then we have

DAEMON=/usr/bin/dbus-daemon

which does not exist.

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04

2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center

  Installed: 1.6.18-0ubuntu4.5
  Candidate: 1.6.18-0ubuntu4.5
  Version table:
 *** 1.6.18-0ubuntu4.5 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1.6.18-0ubuntu4.4 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
 1.6.18-0ubuntu4 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

3) What you expected to happen

let dbus service be running

4) What happened instead

nothing

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: dbus 1.6.18-0ubuntu4.5
ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
Uname: Linux 4.4.0-43-Microsoft x86_64
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
Date: Mon Dec  4 22:52:42 2017
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  dbus init script does not work

Status in dbus package in Ubuntu:
  New

Bug description:
  The following command fails:

  test -x $DAEMON

  First of all, the command is wrong, it should be

  test -x "$DAEMON"

  Then we have

  DAEMON=/usr/bin/dbus-daemon

  which does not exist.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

Installed: 1.6.18-0ubuntu4.5
Candidate: 1.6.18-0ubuntu4.5
Version table:
   *** 1.6.18-0ubuntu4.5 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.6.18-0ubuntu4.4 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   1.6.18-0ubuntu4 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  3) What you expected to happen

  let dbus service be running

  4) What happened instead

  nothing

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: dbus 1.6.18-0ubuntu4.5
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Mon Dec  4 22:52:42 2017
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1710609] Re: New release 8.27

2017-12-04 Thread Hans Joachim Desserud

Thanks for reporting.

Looks like coreutils 8.28-1 has been packaged in Debian
(https://tracker.debian.org/pkg/coreutils). However, since the Ubuntu
package carry some Ubuntu-specific patches, this might require a manual
merge.

** Tags added: needs-debian-merge

** Summary changed:

- New release 8.27
+ New release 8.28

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

Title:
  New release 8.28

Status in coreutils package in Ubuntu:
  New

Bug description:
  Hello,

  http://git.savannah.gnu.org/cgit/coreutils.git/tag/?h=v8.27

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: coreutils 8.26-3ubuntu3
  Uname: Linux 4.13.0-041300rc4-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 14 09:08:51 2017
  InstallationDate: Installed on 2017-07-05 (39 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to artful on 2017-07-05 (39 days ago)

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

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

[Touch-packages] [Bug 1561278] Re: internal sound card not detected HP X2

2017-12-04 Thread genepool

I never got it to work.

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

Title:
  internal sound card not detected HP X2

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  HP Pavilion X2 - No sound card detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Mar 23 18:18:32 2016
  InstallationDate: Installed on 2016-03-18 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 813E
  dmi.board.vendor: HP
  dmi.board.version: 34.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1736259] [NEW] apport-gtk segfault

2017-12-04 Thread Dmitry Korzhevin

Public bug reported:

[  717.875242] apport-gtk[2587]: segfault at 0 ip 7f8ddd065659 sp
7ffd91d18bb0 error 4 in libgtk-3.so.0.2200.25[7f8ddcd7e000+6fd000]

Please, assist - which log files could be useful?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apport 2.20.7-0ubuntu3.5
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CrashReports:
 640:121:119:21471288:2017-12-01 00:21:07.463343417 +0200:2017-12-01 
00:20:46.635068070 +0200:/var/crash/_usr_bin_gnome-shell.121.crash
 640:0:119:6944675:2017-12-04 23:01:59.209724958 +0200:2017-12-04 
23:01:54.621558919 +0200:/var/crash/_usr_share_apport_apport-gtk.0.crash
 640:1000:119:7570257:2017-12-01 00:11:17.960471870 +0200:2017-12-01 
00:11:17.964471907 +0200:/var/crash/_usr_bin_Xwayland.1000.crash
 640:1000:119:41459720:2017-12-01 00:11:10.500402699 +0200:2017-12-01 
00:12:47.737350953 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec  4 23:12:31 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-11-19 (15 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  apport-gtk segfault

Status in apport package in Ubuntu:
  New

Bug description:
  [  717.875242] apport-gtk[2587]: segfault at 0 ip 7f8ddd065659 sp
  7ffd91d18bb0 error 4 in libgtk-3.so.0.2200.25[7f8ddcd7e000+6fd000]

  Please, assist - which log files could be useful?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3.5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CrashReports:
   640:121:119:21471288:2017-12-01 00:21:07.463343417 +0200:2017-12-01 
00:20:46.635068070 +0200:/var/crash/_usr_bin_gnome-shell.121.crash
   640:0:119:6944675:2017-12-04 23:01:59.209724958 +0200:2017-12-04 
23:01:54.621558919 +0200:/var/crash/_usr_share_apport_apport-gtk.0.crash
   640:1000:119:7570257:2017-12-01 00:11:17.960471870 +0200:2017-12-01 
00:11:17.964471907 +0200:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:119:41459720:2017-12-01 00:11:10.500402699 +0200:2017-12-01 
00:12:47.737350953 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  4 23:12:31 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-19 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2017-12-04 Thread Dmitry Korzhevin

Public bug reported:

System hangs frequently, especially while playing video (html5)

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core
processor Graphics Controller (rev 09)

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Dell 3rd Gen Core processor Graphics Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
BootLog: /dev/sda1: clean, 196704/14655488 files, 3147475/58607360 blocks
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec  4 23:02:15 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:055c]
InstallationDate: Installed on 2017-11-19 (14 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. Vostro 3360
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=46f00411-5aba-4366-b7f8-fd8f27a18c11 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/20/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 0F5DWF
dmi.board.vendor: Dell Inc.
dmi.board.version: FAB1
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd03/20/2012:svnDellInc.:pnVostro3360:pvr:rvnDellInc.:rn0F5DWF:rvrFAB1:cvnDellInc.:ct8:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: Vostro 3360
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  System hangs frequently, especially while playing video (html5)

  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core
  processor Graphics Controller (rev 09)

  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Dell 3rd Gen Core processor Graphics Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  BootLog: /dev/sda1: clean, 196704/14655488 files, 3147475/58607360 blocks
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  4 23:02:15 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:055c]
  InstallationDate: Installed on 2017-11-19 (14 days ago)
  InstallationMe

[Touch-packages] [Bug 1736240] Re: package udev 229-4ubuntu21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-12-04 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package udev 229-4ubuntu21 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  I can't install updates, use my touchpad or open drop down menu.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Mon Dec  4 19:56:22 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 m6 Convertible
  ProcKernelCmdLine: 
file=/cdrom/multiboot/hostname-16.04.3-desktop-amd64/preseed/hostname.seed 
boot=casper cdrom-detect/try-usb=true persistent 
persistent-path=/multiboot/hostname-16.04.3-desktop-amd64 noprompt 
floppy.allowed_drive_mask=0 ignore_uuid 
live-media-path=/multiboot/hostname-16.04.3-desktop-amd64/casper/ 
initrd=/multiboot/hostname-16.04.3-desktop-amd64/casper/initrd.lz quiet splash 
--- maybe-ubiquity
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: systemd
  Title: package udev 229-4ubuntu21 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81AC
  dmi.board.vendor: HP
  dmi.board.version: 53.27
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd08/21/2017:svnHP:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHP:rn81AC:rvr53.27:cvnHP:ct31:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 m6 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1736240] [NEW] package udev 229-4ubuntu21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-12-04 Thread Stan Wilson

Public bug reported:

I can't install updates, use my touchpad or open drop down menu.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udev 229-4ubuntu21
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
Date: Mon Dec  4 19:56:22 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
Lsusb:
 Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ENVY x360 m6 Convertible
ProcKernelCmdLine: 
file=/cdrom/multiboot/hostname-16.04.3-desktop-amd64/preseed/hostname.seed 
boot=casper cdrom-detect/try-usb=true persistent 
persistent-path=/multiboot/hostname-16.04.3-desktop-amd64 noprompt 
floppy.allowed_drive_mask=0 ignore_uuid 
live-media-path=/multiboot/hostname-16.04.3-desktop-amd64/casper/ 
initrd=/multiboot/hostname-16.04.3-desktop-amd64/casper/initrd.lz quiet splash 
--- maybe-ubiquity
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: systemd
Title: package udev 229-4ubuntu21 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/21/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.41
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81AC
dmi.board.vendor: HP
dmi.board.version: 53.27
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd08/21/2017:svnHP:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHP:rn81AC:rvr53.27:cvnHP:ct31:cvrChassisVersion:
dmi.product.name: HP ENVY x360 m6 Convertible
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-package xenial

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

Title:
  package udev 229-4ubuntu21 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  I can't install updates, use my touchpad or open drop down menu.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Mon Dec  4 19:56:22 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 m6 Convertible
  ProcKernelCmdLine: 
file=/cdrom/multiboot/hostname-16.04.3-desktop-amd64/preseed/hostname.seed 
boot=casper cdrom-detect/try-usb=true persistent 
persistent-path=/multiboot/hostname-16.04.3-desktop-amd64 noprompt 
floppy.allowed_drive_mask=0 ignore_uuid 
live-media-path=/multiboot/hostname-16.04.3-desktop-amd64/casper/ 
initrd=/multiboot/hostname-16.04.3-desktop-amd64/casper/initrd.lz quiet splash 
--- maybe-ubiquity
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: systemd
  Title: package udev 229-4ubuntu21 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81AC
  dmi.board.vendor: HP
  dmi.board.version: 53.27
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd08/21/2017:svnHP:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHP:rn81AC:rvr53.27:cvnHP:ct31:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 m6 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1735934] Re: cron starts twice

2017-12-04 Thread Ken Sharp

Ignore all that. There is an issue but I'm blaming the wrong thing.

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

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

Title:
  cron starts twice

Status in cron package in Ubuntu:
  Invalid

Bug description:
  A fresh Ubuntu 16.04 server install...

  cron starts twice every boot. It has been running for a while but I
  have made no changes to cron since the fresh install, other than
  installing some crontabs.

  The first cron show systemd as its parent.
  The second cron shows Upstart as its parent.

  To work around I have disable the Upstart process:
  $ sudo update-rc.d cron disable

  This results in some jobs running around 30 times, I assume due to
  some sort of race condition between the two crons.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cron 3.0pl1-128ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20~16.04.1-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Sat Dec  2 18:30:05 2017
  InstallationDate: Installed on 2016-08-13 (476 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.cron.override: manual

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

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

[Touch-packages] [Bug 1399027] Re: logparser doesn't understand /var/log/messages format

2017-12-04 Thread c0n7r4

Linux Mint is not parsing AppArmor complain log files correctly, I'm not
sure why.

a sample from the audit.log file is
type=AVC msg=audit(1212212212.121:13867): apparmor="AUDIT" operation="open" 
profile="/usr/bin/testfile" name="/tmp/tempfile/" pid=2686 comm="testfile" 
requested_mask="r" fsuid=0 ouid=0

in the logparser.py file, it looks like it's getting picked up by the
regex, and makes its way all the way to "def parse_event_for_tree(self,
e):" where its stopped just a few lines in at:

"if aamode in ['UNKNOWN', 'AUDIT', 'STATUS', 'ERROR']: return None"

The aa-logprof run's without any fatal exceptions, just doesn't
recognize any events.

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

Title:
  logparser doesn't understand /var/log/messages format

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  [impact]

  This bug causes tools that use libapparmor to parse syslog and other
  logs for apparmor rejections to fail to recognize apparmor events.

  [steps to reproduce]

  [regression potential]

  The patch for this issue is confined to the log parsing portion of
  the libapparmor library. Breakages occurring here would most likely
  prevent tools that help assist the management of apparmor policy
  from working; apparmor mediation would not be impacted. libapparmor
  does provide other functionality, mostly around the aa_change_hat(3)
  and aa_change_profile(3) calls; an entirely broken library could cause
  issues for applications that make use of these from working correctly;
  however, there are tests available in the upstream package that get
  invoked by the lp:qa-regression-testing test-apparmor.py script that
  ensure these continue to function.

  [original description]
   
  log parsing (part of libapparmor, used by aa-logprof and aa-genprof) doesn't 
understand the format in /var/log/messages, which means it doesn't find any 
events in it.

  IIRC I've seen a similar report for the ubuntu syslog format on IRC.

  Example log line from openSUSE:

  2014-06-09T20:37:28.975070+02:00 geeko kernel: [21028.143765]
  type=1400 audit(1402339048.973:1421): apparmor="ALLOWED"
  operation="open" profile="/home/cb/linuxtag/apparmor/scripts/hello"
  name="/dev/tty" pid=14335 comm="hello" requested_mask="rw"
  denied_mask="rw" fsuid=1000 ouid=0

  (Workaround: use auditd / audit.log)

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

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

[Touch-packages] [Bug 1736213] [NEW] ubuntu can't detect usb canon MF4700 printer

2017-12-04 Thread Talal Marghalani

Public bug reported:

I'm trying to connect Canon MF4700 Series. i follow most of the instructions 
from the web.
i almost done. I have found the driver from the manufactures web page. I 
install the driver using the command "bash install.sh". it's work fine. but at 
the end. its show Canon printer set up utility and ask me to select the 
connection protocol if via network or Internet or a USB. My printer connection 
via USB connection. but it doesn't show any USB URI device to select. please 
hepl. i check if the printers.

I'm attaching most of the command line configuration.

lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04


apt-cache policy pkgname
pt-cache policy pkgnam
N: Unable to locate package pkgnam


usb kernel:
$ lsmod | grep usb
rtsx_usb_ms20480  0
memstick   16384  1 rtsx_usb_ms
btusb  45056  0
btrtl  16384  1 btusb
btbcm  16384  1 btusb
btintel16384  1 btusb
bluetooth 557056  31 btrtl,btintel,bnep,btbcm,rfcomm,btusb
rtsx_usb_sdmmc 28672  0
rtsx_usb   20480  2 rtsx_usb_sdmmc,rtsx_usb_ms
usbhid 53248  0
hid   118784  4 i2c_hid,hid_generic,usbhid,hid_multitouch

lsusb:
$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 1c7a:0570 LighTuning Technology Inc. 
Bus 001 Device 006: ID 04f2:b5f7 Chicony Electronics Co., Ltd 
Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
Bus 001 Device 002: ID 04f3:00a4 Elan Microelectronics Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

tail -f /var/log/syslog:
$ tail -f /var/log/syslog
Dec  4 20:36:33 talal-Swift-SF113-31 kernel: [24568.532856] usb 1-2: new 
high-speed USB device number 114 using xhci_hcd
Dec  4 20:36:36 talal-Swift-SF113-31 kernel: [24571.772759] usb 1-2: new 
high-speed USB device number 125 using xhci_hcd
Dec  4 20:37:27 talal-Swift-SF113-31 kernel: [24622.873751] usb 1-2: new 
high-speed USB device number 52 using xhci_hcd
Dec  4 20:38:32 talal-Swift-SF113-31 kernel: [24687.318305] usb 1-2: new 
high-speed USB device number 19 using xhci_hcd
Dec  4 20:40:37 talal-Swift-SF113-31 kernel: [24812.071640] usb 1-2: new 
high-speed USB device number 63 using xhci_hcd
Dec  4 20:43:09 talal-Swift-SF113-31 kernel: [24964.567220] usb 1-2: new 
high-speed USB device number 79 using xhci_hcd
Dec  4 20:43:52 talal-Swift-SF113-31 kernel: [25007.733124] usb 1-2: new 
high-speed USB device number 99 using xhci_hcd
Dec  4 20:47:20 talal-Swift-SF113-31 kernel: [25215.163150] usb 1-2: new 
high-speed USB device number 57 using xhci_hcd
Dec  4 20:53:55 talal-Swift-SF113-31 gnome-session[1195]: ** 
(zeitgeist-datahub:1728): WARNING **: zeitgeist-datahub.vala:212: Error during 
inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: 
Incomplete event: interpretation, manifestation and actor are required
Dec  4 21:06:13 talal-Swift-SF113-31 kernel: [26348.910869] usb 1-2: new 
high-speed USB device number 30 using xhci_hcd


^C
end


$ ls -l /dev/usb/lp* /dev/bus/usb/*/*
ls: cannot access '/dev/usb/lp*': No such file or directory
crw-rw-r-- 1 root root 189,   0 Dec  4 13:47 /dev/bus/usb/001/001
crw-rw-r-- 1 root root 189,   1 Dec  4 13:47 /dev/bus/usb/001/002
crw-rw-r-- 1 root root 189,   3 Dec  4 13:47 /dev/bus/usb/001/004
crw-rw-r-- 1 root root 189,   4 Dec  4 13:47 /dev/bus/usb/001/005
crw-rw-r-- 1 root root 189,   5 Dec  4 13:47 /dev/bus/usb/001/006
crw-rw-r-- 1 root root 189,   6 Dec  4 13:47 /dev/bus/usb/001/007
crw-rw-r-- 1 root root 189, 128 Dec  4 13:47 /dev/bus/usb/002/001


sudo usb_printerid /dev/usb/lp0
[sudo] password for talal: 
Error: No such file or directory: can't open '/dev/usb/lp0'
$ sudo usb_printerid /dev/usb/lp1
Error: No such file or directory: can't open '/dev/usb/lp1'


$ lpinfo -v
network beh
network lpd
network ipps
network https
network http
network socket
direct hp
network ipp14
network ipp
direct hpfax

please help me.
my regards,
Talal

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4
ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Dec  4 20:53:19 2017
InstallationDate: Installed on 2017-11-30 (3 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Acer Swift SF113-31
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=/dev/mmcblk0p5 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2017
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.07
dmi.board.asset.tag:

[Touch-packages] [Bug 1736216] [NEW] Suspend does not work when lid is closed on lenovo W530

2017-12-04 Thread Gerd Grundke

Public bug reported:

After upgrading to Ubuntu 17.10 closing the lid of my Lenovo W530 does
no longer suspend my machine.

I checked the power settings using tweak
-> Suspend, when lid is closed   is  ON
 

I ran the following commands

sudo apt install gksu
xhost si:localuser:root
gksudo gedit /etc/systemd/logind.conf

I changed the setting of HandleSuspendKey = hybernate to suspend
(Why was this still set to hybernate, when tweak power settings says suspend?)
 
[Login]
#HandleSuspendKey=suspend

after saving I ran
sudo systemctl restart systemd-logind

But still no action is performed, when I close the lid.


Checking System Settings for power
-> suspend when on battery after 15 minutes

This works perfect after the 15 min idle time.


Somehow no action is performed when I close my lid.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pm-utils 1.4.1-17
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec  4 19:23:44 2017
InstallationDate: Installed on 2017-10-25 (40 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: pm-utils
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pm-utils (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Suspend does not work when lid is closed on lenovo W530

Status in pm-utils package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 17.10 closing the lid of my Lenovo W530 does
  no longer suspend my machine.

  I checked the power settings using tweak
  -> Suspend, when lid is closed   is  ON
   

  I ran the following commands

  sudo apt install gksu
  xhost si:localuser:root
  gksudo gedit /etc/systemd/logind.conf

  I changed the setting of HandleSuspendKey = hybernate to suspend
  (Why was this still set to hybernate, when tweak power settings says suspend?)
   
  [Login]
  #HandleSuspendKey=suspend

  after saving I ran
  sudo systemctl restart systemd-logind

  But still no action is performed, when I close the lid.



  Checking System Settings for power
  -> suspend when on battery after 15 minutes

  This works perfect after the 15 min idle time.

  
  Somehow no action is performed when I close my lid.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pm-utils 1.4.1-17
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  4 19:23:44 2017
  InstallationDate: Installed on 2017-10-25 (40 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1212451] Re: upgrade to latest 4.1+Debian12

2017-12-04 Thread Hans Joachim Desserud

Thanks for reporting.

Looks like it took some time but lsb 9.20160110 was synced to Ubuntu
16.04, so I believe this can be marked fixed.

** Changed in: lsb (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  upgrade to latest 4.1+Debian12

Status in lsb package in Ubuntu:
  Fix Released

Bug description:
  upgrade to latest lsb version 4.1+Debian12 from Debian sid/jessie

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

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

[Touch-packages] [Bug 1682934] Re: python3 in /usr/local/bin can cause python3 packages to fail to install

Hello Brian, or anyone else affected,

Accepted python2.7 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python2.7/2.7.12-1ubuntu0~16.04.3
in a few hours, and then in the -proposed repository.

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

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

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

** Changed in: python2.7 (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

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

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

Title:
  python3 in /usr/local/bin can cause python3 packages to fail to
  install

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3.5 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  Fix Committed
Status in python3.5 source package in Xenial:
  Fix Released
Status in python2.7 source package in Zesty:
  Fix Committed
Status in python3.5 source package in Zesty:
  Fix Released
Status in python3.5 package in Debian:
  Fix Released

Bug description:
  [Impact]
  An upgrade of python3.5 will fail if someone has installed a different 
version of python3.5 in their path e.g. in /usr/local/bin. This is because the 
postinst scripts do not specify the complete path to python3.5.

  [Test Case]
  1) Ensure the version of python3.5 from the release pocket is installed
  2) Install python3 using the instructions at 
https://passingcuriosity.com/2015/installing-python-from-source/
  3) Confirm that python3.5 from /usr/local/bin/ is being used / the default
  4) Upgrade to a newer version of python3.5 from -proposed

  Observe the following Traceback:

  Setting up python3.5-minimal (3.5.3-1) ...
  Traceback (most recent call last):
File "/usr/lib/python3.5/py_compile.py", line 6, in 
  import importlib._bootstrap_external
File "/usr/lib/python3.5/importlib/__init__.py", line 57, in 
  import types
File "/usr/lib/python3.5/types.py", line 166, in 
  import functools as _functools
File "/usr/lib/python3.5/functools.py", line 23, in 
  from weakref import WeakKeyDictionary
File "/usr/lib/python3.5/weakref.py", line 12, in 
  from _weakref import (
  ImportError: cannot import name '_remove_dead_weakref'
  dpkg: error processing package python3.5-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of python3-minimal:
   python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however:
Package python3.5-minimal is not configured yet.

  dpkg: error processing package python3-minimal (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

Errors were encountered while processing:
   python3.5-minimal
   python3-minimal

  With the version of python3.5 from -proposed this Traceback will not
  be encountered.

  [Regression Potential]
  It's possible I missed a postinst script so other python3.5 binary packages 
should be installed to ensure they are all fixed e.g. python3.5-dbg.

  [Original Description]
  Got this error while using "Transmageddon Video Transcoder" and again while 
updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-05-01 (714 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4SourcePackage: python3-defaults
  Title: package python3 3.5.1-4 failed to install/upgrade: p

[Touch-packages] [Bug 1638695] Re: Python 2.7.12 performance regression

Hello Major, or anyone else affected,

Accepted python2.7 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python2.7/2.7.12-1ubuntu0~16.04.3
in a few hours, and then in the -proposed repository.

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

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

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

** Changed in: python2.7 (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  Python 2.7.12 performance regression

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  Fix Committed
Status in python2.7 source package in Zesty:
  Fix Committed

Bug description:
  SRU: Looks like only the math.o build without -fPIC makes it into the
  SRU. There shouldn't be any regression potential when building without
  -fPIC for the static interpreter.  Acceptance criteria is running the
  benchmarks and not showing any performance regressions.

  I work on the OpenStack-Ansible project and we've noticed that testing
  jobs on 16.04 take quite a bit longer to complete than on 14.04.  They
  complete within an hour on 14.04 but they normally take 90 minutes or
  more on 16.04.  We use the same version of Ansible with both versions
  of Ubuntu.

  After more digging, I tested python performance (using the
  'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12).  There
  is a significant performance difference between each version of
  python.  That is detailed in a spreadsheet[0].

  I began using perf to dig into the differences when running the python
  performance module and when using Ansible playbooks.  CPU migrations
  (as measured by perf) are doubled in Ubuntu 16.04 when running the
  same python workloads.

  I tried changing some of the kerne.sched sysctl configurables but they
  had very little effect on the results.

  I compiled python 2.7.12 from source on 14.04 and found the
  performance to be unchanged there.  I'm not entirely sure where the
  problem might be now.

  We also have a bug open in OpenStack-Ansible[1] that provides
  additional detail. Thanks in advance for any help you can provide!

  [0] 
https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing
  [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions

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

[Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

2017-12-04 Thread Ryan Harper

Revised patch, should fix error with kfree on env

** Patch added: "bcache_always_emit_backing_dev_change_uevent_v2.diff"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+attachment/5018329/+files/bcache_always_emit_backing_dev_change_uevent_v2.diff

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenS

Re: [Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

2017-12-04 Thread Ryan Harper

Looks like those two kfree's in dev_run can be dropped since that was an
exit after kmalloc'ing env entries which are now only done in

bch_cached_dev_emit_change()

which is only called by dev_run after it knows that the device is not
yet running.


On Mon, Dec 4, 2017 at 11:35 AM, Ryan Harper 
wrote:

> Hi Joseph,
>
> Sorry, I didn't give that a compile either; I just wanted to show what the
> change could look like;
> Let me see if I can get that to at least compile.
>
>
> On Mon, Dec 4, 2017 at 11:18 AM, Joseph Salisbury <
> joseph.salisb...@canonical.com> wrote:
>
>> It looks like env[] was declared in bch_cached_dev_emit_change(), but
>> not in bch_cached_dev_run().
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1729145
>>
>> Title:
>>   /dev/bcache/by-uuid links not created after reboot
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145
>> /+subscriptions
>>
>
>

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  A

Re: [Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

2017-12-04 Thread Ryan Harper

Hi Joseph,

Sorry, I didn't give that a compile either; I just wanted to show what the
change could look like;
Let me see if I can get that to at least compile.


On Mon, Dec 4, 2017 at 11:18 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> It looks like env[] was declared in bch_cached_dev_emit_change(), but
> not in bch_cached_dev_run().
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729145
>
> Title:
>   /dev/bcache/by-uuid links not created after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1729145/+subscriptions
>

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A

[Touch-packages] [Bug 1736205] [NEW] Dell latitude E6540 powers off only after switching to console with ctrl+alt+F7

2017-12-04 Thread munbi

Public bug reported:

After updating from 16.10 to 17.04 the system hangs indefinitely when powering 
off from Gnome.
After manually switching to console '7' with ctrl+alt+F7 the shutdown procedure 
resumes and the system powers off correctly.
Reboot is not affected, i.e. the systems resets as expected when choosing 
'Restart' instead of 'Power Off' from the Gnome dialog

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec  4 18:21:00 2017
InstallationDate: Installed on 2017-04-19 (228 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Dell Inc. Latitude E6540
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=703a96bd-4006-46d6-89f2-01dd1aaeb8d3 ro quiet splash vt.handoff=7
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 2 overridden configuration files found.
UpgradeStatus: Upgraded to artful on 2017-10-31 (34 days ago)
dmi.bios.date: 05/19/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A21
dmi.board.name: 0725FP
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd05/19/2017:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6540
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug artful

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

Title:
  Dell latitude E6540 powers off only after switching to console with
  ctrl+alt+F7

Status in systemd package in Ubuntu:
  New

Bug description:
  After updating from 16.10 to 17.04 the system hangs indefinitely when 
powering off from Gnome.
  After manually switching to console '7' with ctrl+alt+F7 the shutdown 
procedure resumes and the system powers off correctly.
  Reboot is not affected, i.e. the systems resets as expected when choosing 
'Restart' instead of 'Power Off' from the Gnome dialog

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  4 18:21:00 2017
  InstallationDate: Installed on 2017-04-19 (228 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6540
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=703a96bd-4006-46d6-89f2-01dd1aaeb8d3 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: Upgraded to artful on 2017-10-31 (34 days ago)
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 0725FP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd05/19/2017:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

On the Bileto silo I noticed that the autopkgtests for modemmanager-qt
have failed, looks like some ABI-check tests are failing. I need to see
if we don't need to re-build modemmanager-qt against the new
modemmanager in the silo as an experiment.

** Description changed:

+ [Impact]
+ 
+  * the new modemmanager packages bring in DW5816 supporting.
+  * These modemmanager packages is needed to support new devices.
+ 
+ [Test Case]
+ 
+  * install modemmanager and it's dependencies from 
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054
+ libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
+ libmbim-proxy 1.14.0-1ubuntu0.16.04.1
+ libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
+ libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
+ libqmi-proxy 1.16.2-1ubuntu0.16.04.1
+ modemmanager 1.6.4-1ubuntu0.16.04.1
+  * reboot and try WWAN function to see if any regression there.
+  * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)
+ 
+ [Regression Potential]
+ 
+  * The package comes from Zesty and should not have regression there.
+  * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.
+ 
+ [Original Description]
+ 
  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:
  
  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap
  
  This is also related to bug #1693756 which includes a subset of patches
  of what would be updated.

** Also affects: modemmanager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  In Progress
Status in libmbim source package in Xenial:
  New
Status in libqmi source package in Xenial:
  New
Status in modemmanager source package in Xenial:
  New

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from 
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

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

[Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

2017-12-04 Thread Joseph Salisbury

It looks like env[] was declared in bch_cached_dev_emit_change(), but
not in bch_cached_dev_run().

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  Proc

[Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

2017-12-04 Thread Joseph Salisbury

@Ryan

I tried to build an Artful test kernel with your patch.  However, there
were compilation errors:

ubuntu-artful/drivers/md/bcache/super.c:868:9: error: 'env' undeclared (first 
use in this function); did you mean '_end'?
   kfree(env[1]);
 ^~~
 _end

Did you have any issues compiling?

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Fo

[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

2017-12-04 Thread Wendell Soares

I have this problem on 17.10.

Is there any way to resolve this problem without removing my Google
account?

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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

Re: [Touch-packages] [Bug 1734967] Re: tzdata info for WGT/WGST broken

2017-12-04 Thread Thomas M Steenholdt

I have started a dialogue on the TZ mailinglist to perhaps have the
change (WGT/WGST at least) reverted. That's my goal anyway, so we'll see
how it goes.

/Thomas

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

Title:
  tzdata info for WGT/WGST broken

Status in php5 package in Ubuntu:
  New
Status in php7.0 package in Ubuntu:
  New
Status in php7.1 package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Invalid
Status in php7.0 package in Debian:
  New

Bug description:
  Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed
  from date command but instead just "-03". Problem is evident in PHP
  applications too, which now think we're in Sao Paolo.

  This appears to have changed with latest tzdata update or perhaps in
  combination with change from DST.

  Same problem on 16.04, 17.10 and Debian 9.

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

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

[Touch-packages] [Bug 1512068] Re: Python ctypes.util , Shell Injection in find_library()

Hello Bernd, or anyone else affected,

Accepted python2.7 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python2.7/2.7.12-1ubuntu0~16.04.3
in a few hours, and then in the -proposed repository.

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

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

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

** Changed in: python2.7 (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  Python ctypes.util , Shell Injection in find_library()

Status in Python:
  Fix Released
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  Fix Committed

Bug description:
  https://github.com/Legrandin/ctypes/issues/1

  The find_library() function can execute code when special chars like ;|`<>$ 
are in the name.
  The "os.popen()" calls in the util.py script should be replaced with 
"subprocess.Popen()".

  Demo Exploits for Linux :
  

  >>> from ctypes.util import find_library
  >>> find_library(";xeyes")# runs  xeyes 
  >>> find_library("|xterm")# runs terminal
  >>> find_library("&gimp")# runs gimp
  >>> find_library("$(nautilus)")  # runs filemanager
  >>> find_library(">test")   # creates, and if exists, 
erases a file "test"

   Traceback 

  >>> find_library("`xmessage hello`")# shows a message, press ctrl+c for 
Traceback
  ^CTraceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3.4/ctypes/util.py", line 244, in find_library
  return _findSoname_ldconfig(name) or _get_soname(_findLib_gcc(name))
File "/usr/lib/python3.4/ctypes/util.py", line 99, in _findLib_gcc
  trace = f.read()
  KeyboardInterrupt

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libpython2.7-stdlib 2.7.10-4ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov  1 10:34:38 2015
  InstallationDate: Installed on 2015-10-09 (22 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151009)
  SourcePackage: python2.7
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1734109] Re: Avoid symbol conflicts with `md5_*' symbols in third party extensions

Hello Matthias, or anyone else affected,

Accepted python2.7 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python2.7/2.7.12-1ubuntu0~16.04.3
in a few hours, and then in the -proposed repository.

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

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

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

** Changed in: python2.7 (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  Avoid symbol conflicts with `md5_*' symbols in third party extensions

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  Fix Committed
Status in python2.7 source package in Zesty:
  Fix Committed
Status in python2.7 source package in Artful:
  Fix Released

Bug description:
  SRU

  We link most extensions as built-ins into the python binary. the md5_*
  symbols cause a conflict with external libs/extensions.  So just use
  the _Py-* namespace for these. See the Debian report for details.

  These are internal functions for the md5 module. Renaming them to the
  _Py_* namespace avoids the conflict.  There should not be any case
  where these are intentionally referenced. At least in the archive
  there are no known references, so the regression potential is limited
  to external binaries, and there it should be minimal to non-existing
  as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1734109/+subscriptions

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

[Touch-packages] [Bug 1728574] Re: Xwayland fails to initialize on miral-desktop

2017-12-04 Thread Alan Griffiths

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

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

Title:
  Xwayland fails to initialize on miral-desktop

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  $ miral-desktop
  $ WAYLAND_DEBUG=1 miral-xrun xeyes

  This outputs:

  [3478171.835]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3478171.859]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3478171.992] wl_display@1.delete_id(3)
  [3478172.018] wl_registry@2.global(1, "wl_compositor", 3)
  [3478172.032]  -> wl_regis...@2.bind(1, "wl_compositor", 1, new id 
[unknown]@4)
  [3478172.056] wl_registry@2.global(2, "wl_seat", 5)
  [3478172.061] wl_registry@2.global(3, "wl_output", 2)
  [3478172.065]  -> wl_regis...@2.bind(3, "wl_output", 2, new id [unknown]@5)
  [3478172.078] wl_registry@2.global(4, "wl_shell", 1)
  [3478172.083]  -> wl_regis...@2.bind(4, "wl_shell", 1, new id [unknown]@6)
  [3478172.087] wl_registry@2.global(5, "wl_shm", 1)
  [3478172.092]  -> wl_regis...@2.bind(5, "wl_shm", 1, new id [unknown]@7)
  [3478172.098] wl_registry@2.global(6, "wl_drm", 2)
  [3478172.104]  -> wl_regis...@2.bind(6, "wl_drm", 2, new id [unknown]@8)
  [3478172.113] wl_callb...@3.done(0)
  [3478172.119]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3478172.227] wl_display@1.delete_id(3)
  [3478172.248] wl_output@5.geometry(0, 0, 310, 170, 0, "Fake manufacturer", 
"Fake model", 0)
  [3478172.271] wl_out...@5.mode(3, 1600, 900, 59970)
  [3478172.277] wl_output@5.scale(1)
  [3478172.280] wl_out...@5.done()
  [3478172.287] wl_drm@8.device("/dev/dri/card0")
  wayland-egl: could not open /dev/dri/card0 (Permission denied)
  [3478172.300] wl_drm@8.format(875713089)
  [3478172.304] wl_drm@8.format(875713112)
  [3478172.308] wl_drm@8.format(909199186)
  [3478172.312] wl_drm@8.format(961959257)
  [3478172.317] wl_drm@8.format(825316697)
  [3478172.321] wl_drm@8.format(842093913)
  [3478172.325] wl_drm@8.format(909202777)
  [3478172.330] wl_drm@8.format(875713881)
  [3478172.335] wl_drm@8.format(842094158)
  [3478172.339] wl_drm@8.format(909203022)
  [3478172.344] wl_drm@8.format(1448695129)
  [3478172.349] wl_drm@8.capabilities(1)
  [3478172.353] wl_callb...@3.done(0)
  [3478172.359]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3478172.388] wl_display@1.delete_id(3)
  [3478172.399] wl_callb...@3.done(0)
  [3478172.406]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3478172.486] wl_display@1.delete_id(3)
  [3478172.498] wl_callb...@3.done(0)
  [3478172.502]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3478172.532] wl_display@1.delete_id(3)
  [3478172.541] wl_callb...@3.done(0)
  [3478172.560]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3478172.610] wl_display@1.delete_id(3)
  [3478172.623] wl_callb...@3.done(0)

  with a lot of repetition of the last three lines. X11 clients fail to
  connect.

  

  For comparison, the output when connecting to miral-app is:

  [3926349.817]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3926349.862]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3926349.970] wl_display@1.delete_id(3)
  [3926349.994] wl_registry@2.global(1, "wl_compositor", 3)
  [3926350.006]  -> wl_regis...@2.bind(1, "wl_compositor", 1, new id 
[unknown]@4)
  [3926350.025] wl_registry@2.global(2, "wl_seat", 5)
  [3926350.033] wl_registry@2.global(3, "wl_output", 2)
  [3926350.053]  -> wl_regis...@2.bind(3, "wl_output", 2, new id [unknown]@5)
  [3926350.073] wl_registry@2.global(4, "wl_shell", 1)
  [3926350.078]  -> wl_regis...@2.bind(4, "wl_shell", 1, new id [unknown]@6)
  [3926350.083] wl_registry@2.global(5, "wl_shm", 1)
  [3926350.089]  -> wl_regis...@2.bind(5, "wl_shm", 1, new id [unknown]@7)
  [3926350.097] wl_registry@2.global(6, "wl_drm", 2)
  [3926350.101]  -> wl_regis...@2.bind(6, "wl_drm", 2, new id [unknown]@8)
  [3926350.106] wl_callb...@3.done(1)
  [3926350.109]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3926350.184] wl_display@1.delete_id(3)
  [3926350.190] wl_output@5.geometry(0, 0, 338, 198, 0, "Fake manufacturer", 
"Fake model", 0)
  [3926350.201] wl_out...@5.mode(3, 1280, 750, 6)
  [3926350.208] wl_output@5.scale(1)
  [3926350.211] wl_out...@5.done()
  [3926350.219] wl_drm@8.device("/dev/dri/renderD128")
  glamor: EGL version 1.4 (DRI2):
  [3926360.938] wl_drm@8.format(875713089)
  [3926360.952] wl_drm@8.format(875713112)
  [3926360.954] wl_drm@8.format(909199186)
  [3926360.957] wl_drm@8.format(961959257)
  [3926360.959] wl_drm@8.format(825316697)
  [3926360.971] wl_drm@8.format(842093913)
  [3926360.973] wl_drm@8.format(909202777)
  [3926360.975] wl_drm@8.format(875713881)
  [3926360.979] wl_drm@8.format(842094158)
  [3926360.981] wl_drm@8.format(909203022)
  [3926360.983] wl_drm@8.format(1448695129)
  [3926360.985] wl_drm@8.capabilities(1)
  [3926360.988] wl_callb...@3.done(1)
  [39

[Touch-packages] [Bug 1734967] Re: tzdata info for WGT/WGST broken

2017-12-04 Thread Eric Desrochers

The more I look into this the more I start to think it may not be a php bug as 
I first guess.
php is relying on tzdata package so it should follow what tzdata bundle has in 
hand.

I wonder if the change I mentioned in Comment#1 is valid and/or if it
has the appropriate informations for "America/Godthab", because for the
moment it seems to share similar value as southamerica locations
"America/Sao_Paulo" which I wonder if this could be the reason why it
conflicts. If it's not conflicting or something not well taken into
account.

Note that if I set the localtime to "America/Sao_Paulo", I don't see any 
conflict.
So it is really when "America/Godthab" is set and/or possibly other invented 
'europe' abbreviation adjust in the same commit.

@Thomas,
At this stage, I would contact upstream ML (if any) or the author of the patch :
Paul Eggert 


--
# filename: europe
Zone America/Godthab-3:26:56 -  LMT 1916 Jul 28 # Nuuk
-3:00   -   -03 1980 Apr  6  2:00
-3:00   EU  -03/-02

# filename: southamerica
Zone America/Sao_Paulo  -3:06:28 -  LMT 1914
-3:00   Brazil  -03/-02 1963 Oct 23  0:00
-3:00   1:00-02 1964
-3:00   Brazil  -03/-02

--

# strings /usr/share/zoneinfo/America/Sao_Paulo 
<-03>3<-02>,M10.3.0/0,M2.3.0/0

# strings /usr/share/zoneinfo/America/Godthab 
<-03>3<-02>,M3.5.0/-2,M10.5.0/-1

--

# ln -sf /usr/share/zoneinfo/America/Sao_Paulo /etc/localtime

# date
Mon Dec  4 13:53:33 -02 2017

# php tz.php 
America/Sao_Paulo

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

Title:
  tzdata info for WGT/WGST broken

Status in php5 package in Ubuntu:
  New
Status in php7.0 package in Ubuntu:
  New
Status in php7.1 package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Invalid
Status in php7.0 package in Debian:
  New

Bug description:
  Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed
  from date command but instead just "-03". Problem is evident in PHP
  applications too, which now think we're in Sao Paolo.

  This appears to have changed with latest tzdata update or perhaps in
  combination with change from DST.

  Same problem on 16.04, 17.10 and Debian 9.

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

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

[Touch-packages] [Bug 1486445] Re: Lots of zeitgeist errors

2017-12-04 Thread Scott P

Same class of errors.  Been happening almost forever.  Computer has been
rebooted in past week.  Computer has had its Ubuntu version upgraded
since 2015.

non-standard Packages installed often in use:
Skype (current beta)
SciTE text editor
KeePass2 (from repo in previous Ubuntu version)


user@computer:~$ uname -a
Linux computer 4.4.0-101-generic #124-Ubuntu SMP Fri Nov 10 18:29:59 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux


Dec  4 09:54:45 computer org.gnome.zeitgeist.SimpleIndexer[2111]: ** 
(zeitgeist-fts:2968): WARNING **: Unable to get info on 
application://nautilus-autostart.desktop
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
CRITICAL **: string_strip: assertion 'self != NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: (zeitgeist-datahub:2948): 
Gtk-CRITICAL **: gtk_recent_info_get_application_info: assertion 'app_name != 
NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
WARNING **: recent-manager-provider.vala:106: (null) was not registered in 
RecentInfo item 0x1689620
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
CRITICAL **: string_strip: assertion 'self != NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: (zeitgeist-datahub:2948): 
Gtk-CRITICAL **: gtk_recent_info_get_application_info: assertion 'app_name != 
NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
WARNING **: recent-manager-provider.vala:106: (null) was not registered in 
RecentInfo item 0x167d030
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
CRITICAL **: string_strip: assertion 'self != NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: (zeitgeist-datahub:2948): 
Gtk-CRITICAL **: gtk_recent_info_get_application_info: assertion 'app_name != 
NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
WARNING **: recent-manager-provider.vala:106: (null) was not registered in 
RecentInfo item 0x16977f0
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
CRITICAL **: string_strip: assertion 'self != NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: (zeitgeist-datahub:2948): 
Gtk-CRITICAL **: gtk_recent_info_get_application_info: assertion 'app_name != 
NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
WARNING **: recent-manager-provider.vala:106: (null) was not registered in 
RecentInfo item 0x1697690
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
CRITICAL **: string_strip: assertion 'self != NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: (zeitgeist-datahub:2948): 
Gtk-CRITICAL **: gtk_recent_info_get_application_info: assertion 'app_name != 
NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
WARNING **: recent-manager-provider.vala:106: (null) was not registered in 
RecentInfo item 0x1697530
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
CRITICAL **: string_strip: assertion 'self != NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: (zeitgeist-datahub:2948): 
Gtk-CRITICAL **: gtk_recent_info_get_application_info: assertion 'app_name != 
NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
WARNING **: recent-manager-provider.vala:106: (null) was not registered in 
RecentInfo item 0x16973b0
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
CRITICAL **: string_strip: assertion 'self != NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: (zeitgeist-datahub:2948): 
Gtk-CRITICAL **: gtk_recent_info_get_application_info: assertion 'app_name != 
NULL' failed

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

Title:
  Lots of zeitgeist errors

Status in Zeitgeist Datahub:
  Confirmed
Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  $ cat /var/log/syslog shows me lots of zeitgeist-related errors. My
  system is behaving weird lately since the upgrade from Ubuntu 14.10 to
  15.04 so I am guessing this might be related. Alright, here the
  relevant log entries:

  Aug 19 19:31:49 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: zeitgeist-datahub.vala:212: Error during 
inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: 
Incomplete event: interpretation, manifestation and actor are required
  ...
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/.config/sublime-text-3/Projects/seeflow_live.sublime-project"
 was not found, exec: sublime_text, mime_type: application/octet-stream
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: *

[Touch-packages] [Bug 1682934] Re: python3 in /usr/local/bin can cause python3 packages to fail to install

Hello Brian, or anyone else affected,

Accepted python2.7 into zesty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python2.7/2.7.13-2ubuntu0.2 in a
few hours, and then in the -proposed repository.

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

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

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

** Changed in: python2.7 (Ubuntu Zesty)
   Status: Confirmed => Fix Committed

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

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

Title:
  python3 in /usr/local/bin can cause python3 packages to fail to
  install

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3.5 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  Confirmed
Status in python3.5 source package in Xenial:
  Fix Released
Status in python2.7 source package in Zesty:
  Fix Committed
Status in python3.5 source package in Zesty:
  Fix Released
Status in python3.5 package in Debian:
  Fix Released

Bug description:
  [Impact]
  An upgrade of python3.5 will fail if someone has installed a different 
version of python3.5 in their path e.g. in /usr/local/bin. This is because the 
postinst scripts do not specify the complete path to python3.5.

  [Test Case]
  1) Ensure the version of python3.5 from the release pocket is installed
  2) Install python3 using the instructions at 
https://passingcuriosity.com/2015/installing-python-from-source/
  3) Confirm that python3.5 from /usr/local/bin/ is being used / the default
  4) Upgrade to a newer version of python3.5 from -proposed

  Observe the following Traceback:

  Setting up python3.5-minimal (3.5.3-1) ...
  Traceback (most recent call last):
File "/usr/lib/python3.5/py_compile.py", line 6, in 
  import importlib._bootstrap_external
File "/usr/lib/python3.5/importlib/__init__.py", line 57, in 
  import types
File "/usr/lib/python3.5/types.py", line 166, in 
  import functools as _functools
File "/usr/lib/python3.5/functools.py", line 23, in 
  from weakref import WeakKeyDictionary
File "/usr/lib/python3.5/weakref.py", line 12, in 
  from _weakref import (
  ImportError: cannot import name '_remove_dead_weakref'
  dpkg: error processing package python3.5-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of python3-minimal:
   python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however:
Package python3.5-minimal is not configured yet.

  dpkg: error processing package python3-minimal (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

Errors were encountered while processing:
   python3.5-minimal
   python3-minimal

  With the version of python3.5 from -proposed this Traceback will not
  be encountered.

  [Regression Potential]
  It's possible I missed a postinst script so other python3.5 binary packages 
should be installed to ensure they are all fixed e.g. python3.5-dbg.

  [Original Description]
  Got this error while using "Transmageddon Video Transcoder" and again while 
updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-05-01 (714 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4SourcePackage: python3-defaults
  Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency 
pr

[Touch-packages] [Bug 1734109] Re: Avoid symbol conflicts with `md5_*' symbols in third party extensions

Hello Matthias, or anyone else affected,

Accepted python2.7 into zesty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python2.7/2.7.13-2ubuntu0.2 in a
few hours, and then in the -proposed repository.

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

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

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

** Changed in: python2.7 (Ubuntu Zesty)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-zesty

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

Title:
  Avoid symbol conflicts with `md5_*' symbols in third party extensions

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  New
Status in python2.7 source package in Zesty:
  Fix Committed
Status in python2.7 source package in Artful:
  Fix Released

Bug description:
  SRU

  We link most extensions as built-ins into the python binary. the md5_*
  symbols cause a conflict with external libs/extensions.  So just use
  the _Py-* namespace for these. See the Debian report for details.

  These are internal functions for the md5 module. Renaming them to the
  _Py_* namespace avoids the conflict.  There should not be any case
  where these are intentionally referenced. At least in the archive
  there are no known references, so the regression potential is limited
  to external binaries, and there it should be minimal to non-existing
  as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1734109/+subscriptions

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

[Touch-packages] [Bug 1638695] Re: Python 2.7.12 performance regression

Hello Major, or anyone else affected,

Accepted python2.7 into zesty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python2.7/2.7.13-2ubuntu0.2 in a
few hours, and then in the -proposed repository.

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

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

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

** Changed in: python2.7 (Ubuntu Zesty)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-zesty

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

Title:
  Python 2.7.12 performance regression

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  Confirmed
Status in python2.7 source package in Zesty:
  Fix Committed

Bug description:
  SRU: Looks like only the math.o build without -fPIC makes it into the
  SRU. There shouldn't be any regression potential when building without
  -fPIC for the static interpreter.  Acceptance criteria is running the
  benchmarks and not showing any performance regressions.

  I work on the OpenStack-Ansible project and we've noticed that testing
  jobs on 16.04 take quite a bit longer to complete than on 14.04.  They
  complete within an hour on 14.04 but they normally take 90 minutes or
  more on 16.04.  We use the same version of Ansible with both versions
  of Ubuntu.

  After more digging, I tested python performance (using the
  'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12).  There
  is a significant performance difference between each version of
  python.  That is detailed in a spreadsheet[0].

  I began using perf to dig into the differences when running the python
  performance module and when using Ansible playbooks.  CPU migrations
  (as measured by perf) are doubled in Ubuntu 16.04 when running the
  same python workloads.

  I tried changing some of the kerne.sched sysctl configurables but they
  had very little effect on the results.

  I compiled python 2.7.12 from source on 14.04 and found the
  performance to be unchanged there.  I'm not entirely sure where the
  problem might be now.

  We also have a bug open in OpenStack-Ansible[1] that provides
  additional detail. Thanks in advance for any help you can provide!

  [0] 
https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing
  [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions

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

[Touch-packages] [Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

2017-12-04 Thread Andreas Hasenack

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

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

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

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

** Changed in: iproute2 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: iproute2 (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: iproute2 (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: iproute2 (Ubuntu Artful)
   Importance: Undecided => Medium

** Changed in: iproute2 (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: iproute2 (Ubuntu Trusty)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: iproute2 (Ubuntu Xenial)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: iproute2 (Ubuntu Zesty)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: iproute2 (Ubuntu Artful)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  In Progress
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  In Progress
Status in iproute2 source package in Xenial:
  In Progress
Status in iproute2 source package in Zesty:
  In Progress
Status in iproute2 source package in Artful:
  In Progress

Bug description:
  [Impact]
  When a nic has a long enough name such that there is no space between the 
name and the ":" in /proc/net/igmp, ip maddr show dev  will miss the IPV4 
addresses which is otherwise shown with "ip maddr show".

  This is inconsistent behavior and can break scripts and tests, as
  shown in this bug's original description.

  Three patches from upstream were taken to fix this bug, and they were used 
individually instead of being merged into one single patch so it's easier to 
track and recognize authorship:
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=530903dd9003492edb0714e937ad4a5d1219e376
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=b48a1161f5f9b6a0cda399a224bbbf72eba4a5c6
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=21503ed2af233ffe795926f6641ac84ec1b15bf9

  [Test Case]
  * deploy the ubuntu release under test. Please use bare metal or a VM instead 
of containers, because the ip tool parses a file in /proc. Make sure iproute2 
is installed:
  sudo apt install iproute2

  * Run these commands to setup a dummy interface with a long name and
  an IPv4 address. Please change the address if it conflicts with a real
  network you might have available on that machine:

  sudo ip link add dummylongnic0 type dummy
  sudo ip addr add 192.168.199.10/24 dev dummylongnic0
  sudo ip link set dev dummylongnic0 up

  * Compare the output of these two commands with regards to the dummylongnic0 
interface:
  sudo ip maddr show
  sudo ip maddr show dev dummylongnic0

  * With the buggy iproute2 package installed, the more specific output "ip 
maddr show dev dummylongnic0" should lack the "inet 224.0.0.1" line:
  ip maddr show dev dummylongnic0
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet6 ff02::1
inet6 ff01::1

  
  Whereas the less specific command, which lists all interfaces, will have it 
listed for dummylongnic0:
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet  224.0.0.1
inet6 ff02::1
inet6 ff01::1

  
  * With the fixed iproute2 package, all dummylongnic0 addresses will be 
present in both outputs.

  
  [Regression Potential]
  In the end, the ip tool is parsing a text file produced by the kernel. As 
most parsing done in C, it's pretty low level and sensitive to changes in the 
file it's reading.

  [Other Info]
  I suggest to conduct the tests in VMs instead of containers (LXD) because the 
ip maddr command parses /proc/net/igmp, which is produced by the kernel. If you 
use a container, then it's the host's kernel that will be providing that file 
and it might not be the same as with the native kernel of that particular 
ubuntu release.

  --- Original description ---
  Attn. Canonical:  Please make sure that the existing iproute2 package gets 
updated with the two referenced patches as the missing information is impacting 
our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data

  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 1

[Touch-packages] [Bug 1638695] Re: Python 2.7.12 performance regression

2017-12-04 Thread Matthias Klose

** Description changed:

+ SRU: Looks like only the math.o build without -fPIC makes it into the
+ SRU. There shouldn't be any regression potential when building without
+ -fPIC for the static interpreter. Acceptance criteria is running the
+ benchmarks and not showing any performance regressions.
+
I work on the OpenStack-Ansible project and we've noticed that testing
jobs on 16.04 take quite a bit longer to complete than on 14.04. They
complete within an hour on 14.04 but they normally take 90 minutes or
more on 16.04. We use the same version of Ansible with both versions of
Ubuntu.

After more digging, I tested python performance (using the 'performance'
module) on 14.04 (2.7.6) and on 16.04 (2.7.12). There is a significant
performance difference between each version of python. That is detailed
in a spreadsheet[0].

I began using perf to dig into the differences when running the python
performance module and when using Ansible playbooks. CPU migrations (as
measured by perf) are doubled in Ubuntu 16.04 when running the same
python workloads.

I tried changing some of the kerne.sched sysctl configurables but they
had very little effect on the results.

I compiled python 2.7.12 from source on 14.04 and found the performance
to be unchanged there. I'm not entirely sure where the problem might be
now.

We also have a bug open in OpenStack-Ansible[1] that provides additional
detail. Thanks in advance for any help you can provide!

[0]
https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing
[1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494

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

Title:
Python 2.7.12 performance regression

Status in python2.7 package in Ubuntu:
Fix Released
Status in python2.7 source package in Xenial:
Confirmed

Bug description:
SRU: Looks like only the math.o build without -fPIC makes it into the
SRU. There shouldn't be any regression potential when building without
-fPIC for the static interpreter. Acceptance criteria is running the
benchmarks and not showing any performance regressions.

I work on the OpenStack-Ansible project and we've noticed that testing
jobs on 16.04 take quite a bit longer to complete than on 14.04. They
complete within an hour on 14.04 but they normally take 90 minutes or
more on 16.04. We use the same version of Ansible with both versions
of Ubuntu.

After more digging, I tested python performance (using the
'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12). There
is a significant performance difference between each version of
python. That is detailed in a spreadsheet[0].

I began using perf to dig into the differences when running the python
performance module and when using Ansible playbooks. CPU migrations
(as measured by perf) are doubled in Ubuntu 16.04 when running the
same python workloads.

I tried changing some of the kerne.sched sysctl configurables but they
had very little effect on the results.

I compiled python 2.7.12 from source on 14.04 and found the
performance to be unchanged there. I'm not entirely sure where the
problem might be now.

We also have a bug open in OpenStack-Ansible[1] that provides
additional detail. Thanks in advance for any help you can provide!

[0]
https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing
[1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions

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

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

2017-12-04 Thread GRC FAMILY NET

Posted this bug when it was a hot summer day, now we are in the cold of
winter now..still no answer or evaluation has happened. I am not sure
this is the way free software can actually grow much..

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  The screen freezes (with no corruption) when the PC enters standby or screen 
power saving.
  The event does not happen when the PC enters standby or screen power saving 
from the users selection screen.
  Once the problem happens the only way to recover normal operation is to 
switch to another VT (ctrl+alt+f*), login as any user and run "sudo service 
lightdm restart".

  Until some of the last updates, I was experiencing very serious
  episodes of screen corruptions that forced me to disable hardware
  acceleration. Now I can use acceleration with this residual problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.10.8-041008-lowlatency x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Aug 16 21:11:05 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GF116 [GeForce GTX 550 
Ti] [1462:809d]
  InstallationDate: Installed on 2016-04-23 (480 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.8-041008-lowlatency 
root=UUID=116cf640-f3d4-409e-bb36-c01299150422 ro noprompt persistent quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99FX PRO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Aug 16 20:55:06 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.3
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1456789] Re: restarting services hangs on systemd-tty-ask-password-agent

2017-12-04 Thread Dr. Jens Harbott

Same here, sample ps auxf output: http://paste.ubuntu.com/26112646/

In the upgrade there was a systemd update at the same time as the other
package update, which seems to be the trigger according to the debian
bug.

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

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

Title:
  restarting services hangs on systemd-tty-ask-password-agent

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  I have a script run as root from cron that tweaks smb.conf and
  restarts smbd and winbind. Problem is, starting today after working
  perfectly up till yesterday, this script now hangs on Ubuntu 15.04.
  When run from cron, the process tree looks like this:

  service smbd restart
   \_ systemctl restart smbd.service
\_ /bin/systemd-tty-ask-password-agent --watch
\_ /usr/bin/pkttyagent --notify-fd 5 --fallback

  Run from a shell via sudo, same thing except the process tree
  (obviously) includes the sudo command. It times out after 5 minutes,
  causing the script to fail. If I manually kill the processes, it fails
  faster.

  The simplest possible scripts that reproduce this, run as root or
  through cron or via sudo, are:

  #!/bin/sh
  service smbd restart

  #!/bin/sh
  systemctl restart smbd.service

  Using 'service', this works perfectly on Ubuntu 14.04 and 14.10, and
  until this morning worked perfectly on 15.04 as well.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 15.04
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  systemd 219-7ubuntu5
  samba 2:4.1.13+dfsg-4ubuntu3
  3) What you expected to happen
  Services to restart
  4) What happened instead
  Services didn't restart, 'systemctl' hung

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

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

[Touch-packages] [Bug 1712921] Re: enabling networkd appears to eat up entropy

Hello Dimitri, or anyone else affected,

Accepted nplan into artful-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.32~17.10.1 in
a few hours, and then in the -proposed repository.

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

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

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

** Changed in: nplan (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-artful

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

Title:
  enabling networkd appears to eat up entropy

Status in nplan package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in nplan source package in Xenial:
  Fix Committed
Status in openssh source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in nplan source package in Zesty:
  Fix Committed
Status in openssh source package in Zesty:
  New
Status in systemd source package in Zesty:
  New
Status in nplan source package in Artful:
  Fix Committed
Status in openssh source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Triaged
Status in nplan source package in Bionic:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Triaged

Bug description:
  [Impact]
  Booting systems have a limited amount of entropy, especially in some of the 
cloud cases. We should avoid using it up unnecessarily.

  [Test cases]

  == netplan ==
  1) Boot system with netplan config; using networkd renderer
  2) Validate that it starts and does not cause undue delay.
  2b) strace nplan at boottime (the netplan generator at 
/lib/systemd/system-generators/netplan) and validate it does not call 
get_random() / uuid_generate().
  3) Validate that config with NetworkManager renderer generates UUIDs.

  [Regression potential]
  Netplan depends on UUID generation to create correct networkManager 
configuration for VLANs. This is a specific use-case that is typically not hit, 
but any failure to generate valid NetworkManager configuration would be a 
regression from this SRU.

  ---

  enabling networkd appears to eat up entropy

  as seen in openssh autopkgtest failing, when networkd is enabled by
  default.

  See http://autopkgtest.ubuntu.com/packages/openssh/artful/amd64 with
  triggers systemd/234-2ubuntu9

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

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

[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2017-12-04 Thread Joseph Salisbury

** Tags removed: kernel-key

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in linux package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in network-manager source package in Artful:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

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

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

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

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

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

[Touch-packages] [Bug 1719720] Re: [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with exit code 127

2017-12-04 Thread Andrew Cloke

Since this issue cannot be reproduced with 4.13, marking "invalid".

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

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

Title:
  [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with
  exit code 127

Status in The Ubuntu-power-systems project:
  Invalid
Status in coreutils package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  Currently syslog is getting flooded with below log messages ..
  Sep 25 03:16:41 ubuntu1710 systemd-udevd[2654]: Process '/bin/touch 
/run/run.vpdd
  update' failed with exit code 127.

  This is on UBuntu 17.10 latest build.. 
   
  ---uname output---
  Linux ubuntu1710 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:23:06 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = ZZ-L 

  ---Steps to Reproduce---
   I have seen these messages logged more often when we do any hotplug 
operations.. ex. cpu hotplug..

  Ok. .this is the continuation of LTC #144627 / Launchpad #1682774.

  As suggested in that bug, we did change udev script to create
  temporary file under /run and that patch is available in ubuntu 17.10.

  Looks like this is udev script issue. If I modify systemd-udevd like
  below it works fine.

  I've limited udev knowledge. I don't know if you have any other better
  solution to this issue.

  root@ltc-boston123:/lib/systemd/system# diff -Naurp  
systemd-udevd.service.org systemd-udevd.service
  --- systemd-udevd.service.org 2017-09-26 04:37:47.090057318 -0500
  +++ systemd-udevd.service 2017-09-26 04:37:55.381739372 -0500
  @@ -25,7 +25,7 @@ KillMode=mixed
   WatchdogSec=3min
   TasksMax=infinity
   MountFlags=slave
  -MemoryDenyWriteExecute=yes
  +#MemoryDenyWriteExecute=yes
   RestrictRealtime=yes
   RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
   SystemCallArchitectures=native

  
  -Vasant

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

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

[Touch-packages] [Bug 1719720] Re: [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with exit code 127

2017-12-04 Thread Manoj Iyer

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

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

Title:
  [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with
  exit code 127

Status in The Ubuntu-power-systems project:
  Invalid
Status in coreutils package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  Currently syslog is getting flooded with below log messages ..
  Sep 25 03:16:41 ubuntu1710 systemd-udevd[2654]: Process '/bin/touch 
/run/run.vpdd
  update' failed with exit code 127.

  This is on UBuntu 17.10 latest build.. 
   
  ---uname output---
  Linux ubuntu1710 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:23:06 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = ZZ-L 

  ---Steps to Reproduce---
   I have seen these messages logged more often when we do any hotplug 
operations.. ex. cpu hotplug..

  Ok. .this is the continuation of LTC #144627 / Launchpad #1682774.

  As suggested in that bug, we did change udev script to create
  temporary file under /run and that patch is available in ubuntu 17.10.

  Looks like this is udev script issue. If I modify systemd-udevd like
  below it works fine.

  I've limited udev knowledge. I don't know if you have any other better
  solution to this issue.

  root@ltc-boston123:/lib/systemd/system# diff -Naurp  
systemd-udevd.service.org systemd-udevd.service
  --- systemd-udevd.service.org 2017-09-26 04:37:47.090057318 -0500
  +++ systemd-udevd.service 2017-09-26 04:37:55.381739372 -0500
  @@ -25,7 +25,7 @@ KillMode=mixed
   WatchdogSec=3min
   TasksMax=infinity
   MountFlags=slave
  -MemoryDenyWriteExecute=yes
  +#MemoryDenyWriteExecute=yes
   RestrictRealtime=yes
   RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
   SystemCallArchitectures=native

  
  -Vasant

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

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

[Touch-packages] [Bug 1736166] [NEW] Can't make dualmonitor to work

2017-12-04 Thread Marica Alexandru

Public bug reported:

I have a gtx 960m and can't use the dual monitor for my work, doesn't
work with any kind of screen or projector. Thanks

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  387.12  Thu Sep 28 20:18:48 
PDT 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Dec  4 16:46:24 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1c5d]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d]
InstallationDate: Installed on 2017-09-28 (67 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 002: ID 13d3:5654 IMC Networks 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. GL552VW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic 
root=UUID=f098ecd2-d0e6-4ce6-9f35-6546a683ad54 ro
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL552VW.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL552VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: GL552VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Dec  4 13:17:19 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.4

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


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

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

Title:
  Can't make dualmonitor to work

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a gtx 960m and can't use the dual monitor for my work, doesn't
  work with any kind of screen or projector. Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  387.12  Thu Sep 28 20:18:48 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirec

[Touch-packages] [Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

2017-12-04 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
   Status: Triaged => In Progress

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  In Progress
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  New
Status in iproute2 source package in Zesty:
  New
Status in iproute2 source package in Artful:
  New

Bug description:
  [Impact]
  When a nic has a long enough name such that there is no space between the 
name and the ":" in /proc/net/igmp, ip maddr show dev  will miss the IPV4 
addresses which is otherwise shown with "ip maddr show".

  This is inconsistent behavior and can break scripts and tests, as
  shown in this bug's original description.

  Three patches from upstream were taken to fix this bug, and they were used 
individually instead of being merged into one single patch so it's easier to 
track and recognize authorship:
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=530903dd9003492edb0714e937ad4a5d1219e376
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=b48a1161f5f9b6a0cda399a224bbbf72eba4a5c6
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=21503ed2af233ffe795926f6641ac84ec1b15bf9

  [Test Case]
  * deploy the ubuntu release under test. Please use bare metal or a VM instead 
of containers, because the ip tool parses a file in /proc. Make sure iproute2 
is installed:
  sudo apt install iproute2

  * Run these commands to setup a dummy interface with a long name and
  an IPv4 address. Please change the address if it conflicts with a real
  network you might have available on that machine:

  sudo ip link add dummylongnic0 type dummy
  sudo ip addr add 192.168.199.10/24 dev dummylongnic0
  sudo ip link set dev dummylongnic0 up

  * Compare the output of these two commands with regards to the dummylongnic0 
interface:
  sudo ip maddr show
  sudo ip maddr show dev dummylongnic0

  * With the buggy iproute2 package installed, the more specific output "ip 
maddr show dev dummylongnic0" should lack the "inet 224.0.0.1" line:
  ip maddr show dev dummylongnic0
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet6 ff02::1
inet6 ff01::1

  
  Whereas the less specific command, which lists all interfaces, will have it 
listed for dummylongnic0:
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet  224.0.0.1
inet6 ff02::1
inet6 ff01::1

  
  * With the fixed iproute2 package, all dummylongnic0 addresses will be 
present in both outputs.

  
  [Regression Potential]
  In the end, the ip tool is parsing a text file produced by the kernel. As 
most parsing done in C, it's pretty low level and sensitive to changes in the 
file it's reading.

  [Other Info]
  I suggest to conduct the tests in VMs instead of containers (LXD) because the 
ip maddr command parses /proc/net/igmp, which is produced by the kernel. If you 
use a container, then it's the host's kernel that will be providing that file 
and it might not be the same as with the native kernel of that particular 
ubuntu release.

  --- Original description ---
  Attn. Canonical:  Please make sure that the existing iproute2 package gets 
updated with the two referenced patches as the missing information is impacting 
our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data

  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8286-42A

  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.0.0.252
  inet  224.0.0.1
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
  ...

  root@roselp1:~# ip maddr show dev enP20p96s0
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1

  == Comment: #12 - David Z. Dai  - 2017-11-13 15:07:32 ==

  I found upstream already had patches that fix this problem:

  1) ht

[Touch-packages] [Bug 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

2017-12-04 Thread Andrew Cloke

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

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

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

Status in The Ubuntu-power-systems project:
  Triaged
Status in util-linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies
   
  Contact Information = ppaid...@in.ibm.com 
   
  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV 8284-22A 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: lscpu 

  Userspace rpm: util-linux 
   
  The userspace tool has the following bit modes: 64-bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

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

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

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

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297884305,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297914258,7]   OCC Common Area at 0x200080 size 1MB
  [   42.310897465,7] HBRT: OCC common base 00200080 : 0080
  [   42.317109440,7] HBRT: OCC common base 00200080 : 0080
  [   42.323969570,7] HBRT: OCC common base 00200080 : 0080
  [   42.330941943,7] HBRT: OCC common base 00200080 : 0080
  [5.349544066,6] OCC: Got OCC Load message, scope=0x2 dbob=0x0 seq=0x29
  [6.017413373,7] HBRT: OCC Load requested
  [6.017414365,7] HBRT: Calling loadOCC() homer 00200140, 
occ_common_area 00200080, chip 
  [6.017553013,7] HBRT: Calling loadOCC() homer 3a00, 
occ_common_area 00200080, chip 0001
  [6.017666150,7] HBRT: Calling loadOCC() homer 00280040, 
occ_common_area 00200080, chip 0010
  [6.017790110,7] HBRT: Calling loadOCC() homer 0010004000

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

2017-12-04 Thread Wojciech Gomoła

Public bug reported:

System doesn't boot if 2 MSI Radeons RX 570 Gaming X are attached.
(System working fine if only one is attached). I Have MSI Gaming Plus
B350 mobo and overclocked Ryzen 7 1700. PSU is strong enough to handle 2
GPU's. Windows boots properly on this machine.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
Uname: Linux 4.4.0-101-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
Date: Mon Dec  4 15:28:12 2017
InstallationDate: Installed on 2017-11-23 (11 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug freeze xenial

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  System doesn't boot if 2 MSI Radeons RX 570 Gaming X are attached.
  (System working fine if only one is attached). I Have MSI Gaming Plus
  B350 mobo and overclocked Ryzen 7 1700. PSU is strong enough to handle
  2 GPU's. Windows boots properly on this machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Mon Dec  4 15:28:12 2017
  InstallationDate: Installed on 2017-11-23 (11 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1712921] Re: enabling networkd appears to eat up entropy

2017-12-04 Thread Mathieu Trudel-Lapierre

Autopktests still failing for xenial; the test is still not being
skipped (we know it won't work on Xenial due to the version of NM
shipped there). Marking verification-failed-xenial.

** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial

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

Title:
  enabling networkd appears to eat up entropy

Status in nplan package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in nplan source package in Xenial:
  Fix Committed
Status in openssh source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in nplan source package in Zesty:
  Fix Committed
Status in openssh source package in Zesty:
  New
Status in systemd source package in Zesty:
  New
Status in nplan source package in Artful:
  In Progress
Status in openssh source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Triaged
Status in nplan source package in Bionic:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Triaged

Bug description:
  [Impact]
  Booting systems have a limited amount of entropy, especially in some of the 
cloud cases. We should avoid using it up unnecessarily.

  [Test cases]

  == netplan ==
  1) Boot system with netplan config; using networkd renderer
  2) Validate that it starts and does not cause undue delay.
  2b) strace nplan at boottime (the netplan generator at 
/lib/systemd/system-generators/netplan) and validate it does not call 
get_random() / uuid_generate().
  3) Validate that config with NetworkManager renderer generates UUIDs.

  [Regression potential]
  Netplan depends on UUID generation to create correct networkManager 
configuration for VLANs. This is a specific use-case that is typically not hit, 
but any failure to generate valid NetworkManager configuration would be a 
regression from this SRU.

  ---

  enabling networkd appears to eat up entropy

  as seen in openssh autopkgtest failing, when networkd is enabled by
  default.

  See http://autopkgtest.ubuntu.com/packages/openssh/artful/amd64 with
  triggers systemd/234-2ubuntu9

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

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

[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu

2017-12-04 Thread Mathieu Trudel-Lapierre

Autopktests still failing for xenial; the test is still not being
skipped (we know it won't work on Xenial due to the version of NM
shipped there). Marking verification-failed-xenial.

** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial

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

Title:
  networkd does not accept / set advertised mtu

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in nplan source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Hosts may require a specific MTU to be set as passed by DHCP options. We 
should honor these settings to ensure proper communication of the host with the 
rest of the network.

  [Test case]
  1) Run netplan on a system that should receive MTU settings from DHCP.
  2) Validate that the MTU configuration provided by DHCP is applied to the 
right interface.

  [Regression Potential]
  If DHCP settings specify an invalid MTU setting which is currently being 
ignored and letting the systems communicate correctly with the network, then 
these systems would regress.

  ---

   Right, so as far as I can tell the neutron-api on lcy01 is
  configured to advertise an instance interface MTU of 1400, though
  that's lower than it has to be, and the new DHCP setup with networkd
  just doesn't respect that DHCP option.

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

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

[Touch-packages] [Bug 1709135] Re: add bond primary parameter

2017-12-04 Thread Mathieu Trudel-Lapierre

Autopktests still failing for xenial; the test is still not being
skipped (we know it won't work on Xenial due to the version of NM
shipped there). Marking verification-failed-xenial.

** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial

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

Title:
  add bond primary parameter

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Released
Status in nplan source package in Zesty:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Released
Status in nplan source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Some complex bond configurations require setting a "primary" interface for 
the bond, or setting this greatly improves performance on the network bond.

  [Test case]
  See below for a configuration example.
  1) Apply configuration on a system with netplan.
  2) Run 'netplan apply'
  3) Validate that netplan apply does not return with an error
  4) Validate that netplan properly sets the "primary_slave" value on the bond. 
This can be verified by looking at /sys/class/net//bonding/primary_slave.
  5) Validate that there are no parsing errors from systemd-networkd in the 
journalctl

  [Regression potential]
  If existing configuration fails to be parsed, or lack of primary interface 
breaks configuration for existing bonds, this would be a regression caused by 
this update.

  ---

  ifenslave/eni support a bond parameter:  bond-primary which accepts an
  interface name that can be used to tell the kernel bonding driver
  which interface it should preferred in active-backup (and other
  modes).  This config option is missing in netplan.

   % cat bond-primary.yaml
  network:
    version: 2
    ethernets:
  eth0:
    match:
  driver: virtio
  ens4:
    match:
  driver: e1000
    bonds:
  bond0:
    parameters:
  mode: active-backup
  mii-monitor-interval: 100
  primary: e1000
    dhcp4: true

  % ./generate -r `pwd`/target
  Error in network definition 
/home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 
column 8: unknown key primary

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

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

[Touch-packages] [Bug 1729850] Re: artful openssl FTBFS on armhf

This bug was fixed in the package openssl - 1.0.2g-1ubuntu14

---
openssl (1.0.2g-1ubuntu14) bionic; urgency=medium

  * SECURITY UPDATE: Malformed X.509 IPAddressFamily could cause OOB read
- debian/patches/CVE-2017-3735.patch: avoid out-of-bounds read in
  crypto/x509v3/v3_addr.c.
- CVE-2017-3735
  * SECURITY UPDATE: bn_sqrx8x_internal carry bug on x86_64
- debian/patches/CVE-2017-3736.patch: fix carry bug in
  bn_sqrx8x_internal in crypto/bn/asm/x86_64-mont5.pl.
- CVE-2017-3736
  * debian/patches/fix_armhf_ftbfs.patch: fix build with gcc-7.2 on armhf.
(LP: #1729850)

 -- Marc Deslauriers   Mon, 06 Nov 2017
07:56:00 -0500

** Changed in: openssl (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

Title:
  artful openssl FTBFS on armhf

Status in binutils package in Ubuntu:
  Invalid
Status in gcc-7 package in Ubuntu:
  Invalid
Status in openssl package in Ubuntu:
  Fix Released
Status in binutils source package in Artful:
  Invalid
Status in gcc-7 source package in Artful:
  Invalid
Status in openssl source package in Artful:
  Fix Released
Status in binutils source package in Bionic:
  Invalid
Status in gcc-7 source package in Bionic:
  Invalid
Status in openssl source package in Bionic:
  Fix Released

Bug description:
  openssl FTBFS on artful armhf with the following:

  ../util/shlib_wrap.sh ./sha256t
  Testing SHA-256 
  TEST 1 of 3 failed.

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

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

[Touch-packages] [Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

This bug was fixed in the package iproute2 - 4.9.0-1ubuntu3

---
iproute2 (4.9.0-1ubuntu3) bionic; urgency=medium

  * Fix ip maddr show (LP: #1732032):
- d/p/1003-ip-maddr-fix-igmp-parsing.patch: fix igmp parsing when iface is
  long
- d/p/1004-ip-maddr-avoid-uninitialized-data.patch: avoid accessing
  uninitialized data
- d/p/1005-ip-maddr-fix-filtering-by-device.patch: fix filtering
  by device
  * d/p/1006-fix-undeclared-UINT16_MAX.patch: FTBFS: tc: include stdint.h
explicitly for UINT16_MAX (LP: #1735158)

 -- Andreas Hasenack   Wed, 29 Nov 2017 09:35:46
-0200

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

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  Triaged
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  New
Status in iproute2 source package in Zesty:
  New
Status in iproute2 source package in Artful:
  New

Bug description:
  [Impact]
  When a nic has a long enough name such that there is no space between the 
name and the ":" in /proc/net/igmp, ip maddr show dev  will miss the IPV4 
addresses which is otherwise shown with "ip maddr show".

  This is inconsistent behavior and can break scripts and tests, as
  shown in this bug's original description.

  Three patches from upstream were taken to fix this bug, and they were used 
individually instead of being merged into one single patch so it's easier to 
track and recognize authorship:
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=530903dd9003492edb0714e937ad4a5d1219e376
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=b48a1161f5f9b6a0cda399a224bbbf72eba4a5c6
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=21503ed2af233ffe795926f6641ac84ec1b15bf9

  [Test Case]
  * deploy the ubuntu release under test. Please use bare metal or a VM instead 
of containers, because the ip tool parses a file in /proc. Make sure iproute2 
is installed:
  sudo apt install iproute2

  * Run these commands to setup a dummy interface with a long name and
  an IPv4 address. Please change the address if it conflicts with a real
  network you might have available on that machine:

  sudo ip link add dummylongnic0 type dummy
  sudo ip addr add 192.168.199.10/24 dev dummylongnic0
  sudo ip link set dev dummylongnic0 up

  * Compare the output of these two commands with regards to the dummylongnic0 
interface:
  sudo ip maddr show
  sudo ip maddr show dev dummylongnic0

  * With the buggy iproute2 package installed, the more specific output "ip 
maddr show dev dummylongnic0" should lack the "inet 224.0.0.1" line:
  ip maddr show dev dummylongnic0
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet6 ff02::1
inet6 ff01::1

  
  Whereas the less specific command, which lists all interfaces, will have it 
listed for dummylongnic0:
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet  224.0.0.1
inet6 ff02::1
inet6 ff01::1

  
  * With the fixed iproute2 package, all dummylongnic0 addresses will be 
present in both outputs.

  
  [Regression Potential]
  In the end, the ip tool is parsing a text file produced by the kernel. As 
most parsing done in C, it's pretty low level and sensitive to changes in the 
file it's reading.

  [Other Info]
  I suggest to conduct the tests in VMs instead of containers (LXD) because the 
ip maddr command parses /proc/net/igmp, which is produced by the kernel. If you 
use a container, then it's the host's kernel that will be providing that file 
and it might not be the same as with the native kernel of that particular 
ubuntu release.

  --- Original description ---
  Attn. Canonical:  Please make sure that the existing iproute2 package gets 
updated with the two referenced patches as the missing information is impacting 
our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data

  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8286-42A

  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.0.0.252
  inet  224.0.0

[Touch-packages] [Bug 1735158] Re: FTBFS with gcc7

This bug was fixed in the package iproute2 - 4.9.0-1ubuntu3

---
iproute2 (4.9.0-1ubuntu3) bionic; urgency=medium

  * Fix ip maddr show (LP: #1732032):
- d/p/1003-ip-maddr-fix-igmp-parsing.patch: fix igmp parsing when iface is
  long
- d/p/1004-ip-maddr-avoid-uninitialized-data.patch: avoid accessing
  uninitialized data
- d/p/1005-ip-maddr-fix-filtering-by-device.patch: fix filtering
  by device
  * d/p/1006-fix-undeclared-UINT16_MAX.patch: FTBFS: tc: include stdint.h
explicitly for UINT16_MAX (LP: #1735158)

 -- Andreas Hasenack   Wed, 29 Nov 2017 09:35:46
-0200

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

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

Title:
  FTBFS with gcc7

Status in iproute2 package in Ubuntu:
  Fix Released

Bug description:
  tc
  CC   tc_core.o
  tc_core.c: In function ‘tc_calc_size_table’:
  tc_core.c:190:29: error: ‘UINT16_MAX’ undeclared (first use in this 
function); did you mean ‘__INT16_MAX__’?
 if ((sz >> s->size_log) > UINT16_MAX) {
   ^~
   __INT16_MAX__
  tc_core.c:190:29: note: each undeclared identifier is reported only once for 
each function it appears in
  ../Config:40: recipe for target 'tc_core.o' failed
  make[3]: *** [tc_core.o] Error 1

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

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

[Touch-packages] [Bug 1736142] [NEW] No app icon for qpaeq in cinnamon environment

2017-12-04 Thread George Shuklin

Public bug reported:

This bug affects qpaeq from pulseaudio-equalizer package.

Steps to reproduce:
1. Boot into cinnamon desktop
2. Run qpaeq

Expected result:
Application in task bar with icon

Actual result:
icon 'missing icon' for application in task bar.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio-equalizer 1:11.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.8-0ubuntu2
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Dec  4 14:35:42 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-07-19 (1598 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to bionic on 2017-06-22 (165 days ago)
dmi.bios.date: 12/01/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET56WW (1.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4298R86
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X220 Tablet
dmi.product.name: 4298R86
dmi.product.version: ThinkPad X220 Tablet
dmi.sys.vendor: LENOVO
modified.conffile..etc.init.pulseaudio.conf: [modified]
mtime.conffile..etc.init.pulseaudio.conf: 2013-11-19T01:27:09.605730

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


** Tags: amd64 apport-bug bionic

** Summary changed:

- No app icon in cinnamon environment
+ No app icon for qpaeq in cinnamon environment

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

Title:
  No app icon for qpaeq in cinnamon environment

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This bug affects qpaeq from pulseaudio-equalizer package.

  Steps to reproduce:
  1. Boot into cinnamon desktop
  2. Run qpaeq

  Expected result:
  Application in task bar with icon

  Actual result:
  icon 'missing icon' for application in task bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio-equalizer 1:11.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Dec  4 14:35:42 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1598 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to bionic on 2017-06-22 (165 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4298R86
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220 Tablet
  dmi.product.name: 4298R86
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.init.pulseaudio.conf: [modified]
  mtime.conffile..etc.init.pulseaudio.conf: 2013-11-19T01:27:09.605730

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

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

[Touch-packages] [Bug 1736141] [NEW] Unable to delete programs, and tempory files

2017-12-04 Thread John Bolander II

Public bug reported:

Ever since I installed Astromenus, and then tried to uninstall it, I
have had problems with updates not deleting temporary installation
files, installing new programs, or deleting programs.  For example, even
though I uninstalled Astromenus, my computer is still trying to update
it. I also uninstalled Cairo-dock,yet it still loads on start up.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-102.125~14.04.1-generic 4.4.98
Uname: Linux 4.4.0-102-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Dec  2 22:56:10 2017
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller 
[8086:8108] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:02c6]
InstallationDate: Installed on 2016-10-19 (409 days ago)
InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
MachineType: Dell Inc. Inspiron 1010
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-102-generic 
root=UUID=7a6c8a62-bfe2-4c9a-bf79-420357ccaa90 ro drm.debug=0xe plymouth:debug
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/20/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0G651M
dmi.board.vendor: Dell Inc.
dmi.board.version: A05
dmi.chassis.asset.tag: **
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A05
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/20/2009:svnDellInc.:pnInspiron1010:pvrA05:rvnDellInc.:rn0G651M:rvrA05:cvnDellInc.:ct8:cvrA05:
dmi.product.name: Inspiron 1010
dmi.product.version: A05
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: apport-bug i386 trusty ubuntu

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

Title:
  Unable to delete programs, and tempory files

Status in xorg package in Ubuntu:
  New

Bug description:
  Ever since I installed Astromenus, and then tried to uninstall it, I
  have had problems with updates not deleting temporary installation
  files, installing new programs, or deleting programs.  For example,
  even though I uninstalled Astromenus, my computer is still trying to
  update it. I also uninstalled Cairo-dock,yet it still loads on start
  up.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-102.125~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-102-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Dec  2 22:56:10 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller 
[8086:8108] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:02c6]
  InstallationDate: Installed on 2016-10-19 (409 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
  MachineType: Dell Inc. Inspiron 1010
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-102-generic 
root=UUID=7a6c8a62-bfe2-4c9a-bf79-420357ccaa90 ro drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0G651M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.asset.tag: **
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/20/2009:svnDellInc.:pnInspiron1010:pvrA05:rvnDellIn

[Touch-packages] [Bug 1730232] Re: package bash 4.4-2ubuntu1.1 failed to install/upgrade: Unterprozess neues pre-installation-Skript wurde durch Signal (Abgebrochen), Speicherabbild erzeugt getötet