date:20170515

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

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

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

Title:
  signonpluginprocess crashed with SIGSEGV in
  QGlobalStaticDeleter::~QGlobalStaticDeleter()

Status in signon package in Ubuntu:
  Expired

Bug description:
  Opened Rhythmbox

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: signond 8.41-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu3
  Architecture: amd64
  Date: Tue Aug 28 23:24:29 2012
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/signonpluginprocess
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120819)
  ProcCmdline: /usr/bin/signonpluginprocess oauth2
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: signon
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   exit () from /lib/x86_64-linux-gnu/libc.so.6
   __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
  Title: signonpluginprocess crashed with SIGSEGV in exit()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 1427764] Re: When OpenStack sends the command “ip link set p4p1 vf 1 state enable”, it fails.

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

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

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

Title:
  When OpenStack sends the command “ip link set p4p1 vf 1 state enable”,
  it fails.

Status in iproute2 package in Ubuntu:
  Expired

Bug description:
  When OpenStack sends the command “ip link set p4p1 vf 1 state enable”,
  it fails.

  The Error returned is : RTNETLINK answers: Operation not supported

  The ip set is part of iproute2 package.

  I have  iproute2-3.12.0, igb 5.2.9.4, Ubuntu 14.04, kernel
  3.13.0-43-generic.

  The Ubuntu 14.04 LTS comes with iproute2-3.12.0, I can’t upgrade it to
  a newer version.

  Thanks,
  Dmitry

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

-- 
Mailing list: https://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 1670290] Re: Ubuntu can't suspend anymore after very recent update

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

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

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

Title:
  Ubuntu can't suspend anymore after very recent update

Status in systemd package in Ubuntu:
  Expired

Bug description:
  Earlier today after update Ubuntu can't suspend.

  When I suspend the power button blink like it's suspended, but when I
  try waking it up it boots from start. (It shows me bios password, then
  grub...). It used to work fine.

  It used to happen randomly but now it doesn't suspend at all. I always
  know if it shows me the bios password it will boot from scratch.

  Laptop is Hp Envy x360
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   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 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-09-29 (158 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   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 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=d2ff1e63-47ed-4e61-8be6-f9d308233284 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  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.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.system.conf: 2016-12-25T14:42:04.610046

To manage notifications

[Touch-packages] [Bug 1494692] Re: Total hang of krillin - mali_timeline_sync_fence_create() fail

** Also affects: mir-android-platform
   Importance: Undecided
   Status: New

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

Title:
  Total hang of krillin - mali_timeline_sync_fence_create() fail

Status in Mir:
  Won't Fix
Status in mir-android-platform:
  New
Status in mir package in Ubuntu:
  Won't Fix

Bug description:
  I've had total hangs with both OTA-5 and now OTA-6 on my krillin. This
  was the first time I had developer mode enabled when it happened. With
  total hang, I mean no interaction is possible besides turning screen
  on/off, and the hang does not go "by" ie it's not apport running.
  Auto-dimming is also still functional during the hang, as is
  brightening the screen when touched.

  However, I was not able to adb in in this state (I kept the screen on 
throughout until I was able to try adb):
  $ adb shell
  error: protocol fault (no status)

  $ adb devices
  List of devices attached
  JU012772  device

  $ adb shell
  error: closed

  The fault/closed statuses did take a minute or so to arrive, unlike
  when the device is locked when the "closed" is immediate.

  Hang happened at 12:48 (clock stalled at that point). Forced reboot at
  13:01. No .crash files generated. The log files below were touched at
  12:47 or later. I browsed through all of those and mostly nothing
  extraordinary was seen. Only two with timestamped logs showed any
  activity during the hang, but indeed they did show it was not total
  hang even though also adb was not working. Those without timestamps
  are hard to know when the messages were logged - before the hang,
  during the hang or after the reboot.

  ---
  2194 Sep 11 12:48 application-legacy-webbrowser-app-.log.1.gz
   130 Sep 11 13:01 indicator-network.log.1.gz
    91 Sep 11 13:01 untrusted-helper-type-end-push-helper.log.1.gz
   117 Sep 11 13:01 application-failed.log.1.gz
   457 Sep 11 13:02 usensord.log.1.gz
    41 Sep 11 13:02 ofono-setup.log.1.gz
  1673 Sep 11 13:02 mediascanner-2.0.log.1.gz
   118 Sep 11 13:02 telephony-service-indicator.log.1.gz
    57 Sep 11 13:02 click-user-hooks.log.1.gz
    94 Sep 11 13:02 tone-generator.log.1.gz
   178 Sep 11 13:02 indicator-messages.log.1.gz
   228 Sep 11 13:02 pulseaudio-trust-stored.log.1.gz
    52 Sep 11 13:02 cameraservice-trust-stored.log.1.gz
   113 Sep 11 13:02 mtp-server.log.1.gz
  7691 Sep 11 13:02 account-polld.log.1.gz
   272 Sep 11 13:02 ubuntu-location-service-trust-stored.log.1.gz
  3916 Sep 11 13:02 ciborium.log.1.gz
   465 Sep 11 13:02 maliit-server.log.1.gz
   323 Sep 11 13:02 nuntium.log.1.gz
   935 Sep 11 13:02 media-hub.log.1.gz
   370 Sep 11 13:02 address-book-service.log.1.gz
   195 Sep 11 13:02 ubuntu-push-client.log.1.gz
   257 Sep 11 13:02 sync-monitor.log.1.gz
   624 Sep 11 13:03 unity8-dash.log.1.gz
  2001 Sep 11 13:03 scope-registry.log.1.gz
  3018 Sep 11 13:03 dbus.log.1.gz
  8870 Sep 11 13:03 unity8.log.1.gz
   885 Sep 11 13:03 
application-click-com.ubuntu.telegram_telegram_1.3.20.114.log.1.gz
  ---

  The attached image shows how the phone hanged during starting
  Telegram. The poor picture quality is from the laptop's webcam, since
  I was on lunch when the hang happened. Note that the ghosting of two
  different sized "Telegram" titles is not an optical illusion - there
  were two overlapping texts with different sizes. That is, it was
  transitioning from the splash screen to the smaller title with a logo.
  The previous hangs have happened eg similarly when launching an app,
  or swiping the multi-tasking view, ie when device is under active use,
  never during idling.

  account-pold was clearly during the total hang. Also ubuntu-push-
  client had one line: 2015/09/11 12:51:06.632108 INFO connectivity
  check passed.

  pulseaudio-trust-stored.log had a non-timestamped lines with (this it the 
whole content of the file):
  Attempted to unregister path (path[0] = core path[1] = trust) which isn't 
registered
  reattempt connection to mir...
  reattempt connection to mir...
  reattempt connection to mir...
  reattempt connection to mir...
  Error during initialization and startup: Dynamic exception type: 
N4core5trust3mir20InvalidMirConnectionE
  std::exception::what: Cannot create instance for invalid connection to Mir.

  cameraservice-trust-stored.log.1.gz also had the single line:
  reattempt connection to mir...

  I've saved the potentially interesting logs for account-polld, dbus,
  unity8 and telegram for later watching. No other log files seemed to
  have anything of interest.

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

-- 
Mailing list: https://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 1373696] Re: Android overlay mode ping-pongs constantly when touchspots or software cursor is visible, causing stuttering and lag

** Also affects: mir-android-platform
   Importance: Undecided
   Status: New

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

Title:
  Android overlay mode ping-pongs constantly when touchspots or software
  cursor is visible, causing stuttering and lag

Status in Mir:
  Won't Fix
Status in mir-android-platform:
  New
Status in mir package in Ubuntu:
  Won't Fix

Bug description:
  Bypass/overlay mode ping-pongs constantly during touches with
  touchspots enabled, or when using a mouse (software cursor on
  Android). This visibly means the screen is stuttering and jerky.

  This is a lesser form of bug 1373689, which has a workaround about to
  land...

  $ bin/mir_demo_server_minimal --enable-touchspots --compositor-report=log
  # (and also start a fullscreen client from elsewhere)

  [1411611407.207459] (II) compositor: Started
  [1411611407.230898] (II) compositor: Added display 0x1123d48: 768x1280 +0+0
  [1411611407.236148] (II) compositor: Display 0x1123d48 bypass OFF
  [1411611410.060412] (II) compositor: Display 0x1123d48 bypass ON
  [1411611410.996746] (II) compositor: Display 0x1123d48 averaged 56.652 FPS, 
11.493 ms/frame, latency 0.741 ms, 57 frames over 1.006 sec, 98% bypassed
  [1411611411.998852] (II) compositor: Display 0x1123d48 averaged 59.875 FPS, 
10.765 ms/frame, latency 0.305 ms, 60 frames over 1.002 sec, 100% bypassed
  [1411611412.584721] (II) compositor: Display 0x1123d48 bypass OFF
  [1411611412.599981] (II) compositor: Display 0x1123d48 bypass ON
  [1411611412.677534] (II) compositor: Display 0x1123d48 bypass OFF
  [1411611412.683699] (II) compositor: Display 0x1123d48 bypass ON
  [1411611412.771628] (II) compositor: Display 0x1123d48 bypass OFF
  [1411611412.783500] (II) compositor: Display 0x1123d48 bypass ON
  [1411611412.874756] (II) compositor: Display 0x1123d48 bypass OFF
  [1411611412.883577] (II) compositor: Display 0x1123d48 bypass ON
  [1411611412.972513] (II) compositor: Display 0x1123d48 bypass OFF
  [1411611412.983714] (II) compositor: Display 0x1123d48 bypass ON

  Workaround: Start your Mir server with --disable-overylays=1

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

-- 
Mailing list: https://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 1339749] Re: [enhancement] android hwc overlay could optimize movement of surfaces without buffer update

** Also affects: mir-android-platform
   Importance: Undecided
   Status: New

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

Title:
  [enhancement] android hwc overlay could optimize movement of surfaces
  without buffer update

Status in Mir:
  Won't Fix
Status in mir-android-platform:
  New
Status in mir package in Ubuntu:
  Won't Fix

Bug description:
  Currently, we check in the hwc code that a buffer has changed from the
  previous commit to avoid submitting the same thing to the screen
  twice. This does not factor in changes to the the screen positioning.
  If it did, we could optimize a few more scenarios using 2d
  acceleration.

  This won't  cause rendering glitches, just a bit worse performance in
  some non-critical-path scenarios.

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

-- 
Mailing list: https://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 1547523] Re: Unity System Compositor crash on Pocket Desktop disconnect

** Also affects: mir-android-platform
   Importance: Undecided
   Status: New

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

Title:
  Unity System Compositor crash on Pocket Desktop disconnect

Status in Canonical System Image:
  Won't Fix
Status in Canonical Pocket Desktop:
  Won't Fix
Status in Mir:
  Won't Fix
Status in mir-android-platform:
  New
Status in Unity System Compositor:
  Won't Fix
Status in mir package in Ubuntu:
  Won't Fix
Status in unity-system-compositor package in Ubuntu:
  Won't Fix

Bug description:
  I've seen 2 u-s-c crash instances
  1) hitting the power button to blank the screen just as i was disconnecting 
the slimport cable
  crash file: https://drive.google.com/open?id=0B4GvOYxwuvpFRHJsTzNrUEY5YkU 
  2) allowing the device to blank & sit for a long time (retention mode) and 
then disconnect slimport cable
  crash file: https://drive.google.com/open?id=0B4GvOYxwuvpFYXJGbnNqSzFITnc

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1547523/+subscriptions

-- 
Mailing list: https://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 1478231] Re: nexus10: unity-system-compositor crashes while turning display on with power key [std::exception::what: error turning display on. rc = fffffff0]

** Also affects: mir-android-platform
   Importance: Undecided
   Status: New

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

Title:
  nexus10: unity-system-compositor crashes while turning display on with
  power key [std::exception::what: error turning display on. rc =
  fff0]

Status in Mir:
  Won't Fix
Status in mir-android-platform:
  New
Status in mir package in Ubuntu:
  Won't Fix

Bug description:
  unity-system-compositor-log (still on top of 0.13.3 - without 0.14.0)
  with exception that causes the crash:

  [1437824578.379250] mirplatform: Found graphics driver: android
  [1437824578.379366] mirplatform: Found graphics driver: dummy
  [1437824578.390219] Server: Starting
  [1437824578.393296] Loader: Loading modules from: 
/usr/lib/arm-linux-gnueabihf/mir/server-platform
  [1437824578.393433] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/server-platform/input-stub.so
  [1437824578.394298] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-android.so.2
  [1437824578.394348] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-dummy.so
  [1437824578.399155] mirplatform: Found graphics driver: android
  [1437824578.399198] mirplatform: Found graphics driver: dummy
  [1437824578.399436] Platform Loader: Selected driver: android (version 0.13.3)
  [1437824579.150982] mirserver: Using software cursor
  GL_VENDOR = ARM
  GL_RENDERER = Mali-T604
  GL_VERSION = OpenGL ES 3.0
  dm_connection_start
  [1437824579.197658] GL: vendor: ARM
  [1437824579.197683] GL: renderer: Mali-T604
  [1437824579.197691] GL: version: OpenGL ES 3.0
  [1437824579.197699] GL: SL version: OpenGL ES GLSL ES 3.00
  [1437824579.197712] GL: max texture size = 8192
  [1437824579.197735] GL: framebuffer bits: RGBA=, depth=0, stencil=0
  [1437824579.203708] DisplayServer: Mir version 0.13.3
  set_active_session 'session-0'
  Opening session eglspinner
  Opening session session-0
  Closing session session-0
  Opening session session-0
  Closing session eglspinner
  Current active output is 2560x1600 +0+0
  Server supports 3 of 6 surface pixel formats. Using format: 1
  Signal 15 received. Good night.
  Closing session session-0
  ERROR: 
/build/buildd/mir-0.13.3+15.04.20150617/src/platforms/android/server/real_hwc_wrapper.cpp(156):
 Throw in function virtual void 
mir::graphics::android::RealHwcWrapper::display_on(mir::graphics::android::DisplayName)
 const
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error
  std::exception::what: error turning display on. rc = fff0

  Can't get connection

  A manual restart of lightdm resolves the issue. usc starts up fine and
  is able to turn the display on. Sometimes afer waiting long enough
  lightdm seems to become aware of the situation and respawns unity-
  system-compositor. So we might derive another bug for lightdm - as it
  takes far too long to detect the crash.

  I havent tried yet 0.14.0 - but it should happen there too.

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

-- 
Mailing list: https://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 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues

** Also affects: mir-android-platform
   Importance: Undecided
   Status: New

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

Title:
  [android] renogotiation of pixel formats is not supported, leading to
  potential stride/pixelformat issues

Status in Mir:
  Won't Fix
Status in mir-android-platform:
  New
Status in mir package in Ubuntu:
  Won't Fix

Bug description:
  Some drivers will call android's perform hook with:
  NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats
  are the same depth, we accommodate this by just setting the format to
  the newly-requested format. (ie, mir_pixel_format_rgbx_ to
  mir_pixel_format_rgba_ is accommodated, as no reallocation is
  needed).

  However, we've encountered a device that will try to set the format to
  HAL_PIXEL_FORMAT_RGB_888  when mir has selected
  HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to
  a 24 bit format, the stride information becomes incorrect.

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

-- 
Mailing list: https://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 1369763] Re: [performance] Android overlays don't honour eglSwapInterval 0

** Also affects: mir-android-platform
   Importance: Undecided
   Status: New

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

Title:
  [performance] Android overlays don't honour eglSwapInterval 0

Status in Mir:
  Won't Fix
Status in mir-android-platform:
  New
Status in mir package in Ubuntu:
  Won't Fix

Bug description:
  eglSwapInterval 0 does not work when overlays are enabled.

  Both of these report the same fps:

  MIR_CLIENT_PERF_REPORT=log ./mir_demo_server_basic 
--launch-client="./mir_demo_client_egltriangle" --disable-overlays false
  MIR_CLIENT_PERF_REPORT=log ./mir_demo_server_basic 
--launch-client="./mir_demo_client_egltriangle -n" --disable-overlays false

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

-- 
Mailing list: https://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 1583469] Re: Screen jitters/flickers wildly - Unity8 screen does not fit the physical screen

** Also affects: mir-android-platform
   Importance: Undecided
   Status: New

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

Title:
  Screen jitters/flickers wildly - Unity8 screen does not fit the
  physical screen

Status in Canonical System Image:
  Won't Fix
Status in Mir:
  Incomplete
Status in mir-android-platform:
  New
Status in mir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Won't Fix

Bug description:
  I set the BQ M10 device in Desktop mode yesterday evening.

  After that i used the tablet mode. Then i went to sleep. As i turned
  on my device i got the flickering in the video.

  I restarted the device. The flickering was gone.

  The device is on the image version: r108

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583469/+subscriptions

-- 
Mailing list: https://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 1639255] Re: No HDMI output when frieza is connected to a Dell monitor

** Also affects: mir-android-platform
   Importance: Undecided
   Status: New

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

Title:
  No HDMI output when frieza is connected to a Dell monitor

Status in Canonical System Image:
  Won't Fix
Status in Mir:
  Won't Fix
Status in mir-android-platform:
  New
Status in mir package in Ubuntu:
  Won't Fix

Bug description:
  Environment:

  current build number: 75
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-11-04 10:44:56
  version version: 75
  version ubuntu: 20161104
  version device: 20161014.0
  version custom: 20161104

  Steps to reproduce:

  1º Connect hdmi cable to my dell monitor
  2º Select hdmi port

  Current result: I get a black screen with my dell monitor but it works 
correctly on a Lg tv
  Expected result: dell monitor should display tablet screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639255/+subscriptions

-- 
Mailing list: https://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 1690982] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-15 Thread Apport retracing service

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  I am not sure

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Tue May 16 09:05:54 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-14 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1654536] Re: unity-system-compositor crashed with src/platforms/android/server/gl_context.cpp(233): ... android::FramebufferGLContext::swap_buffers() ... std::exception::what: eg

** Also affects: mir-android-platform
   Importance: Undecided
   Status: New

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

Title:
  unity-system-compositor crashed with
  src/platforms/android/server/gl_context.cpp(233): ...
  android::FramebufferGLContext::swap_buffers() ...
  std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d)

Status in Canonical System Image:
  Won't Fix
Status in Mir:
  Won't Fix
Status in mir-android-platform:
  New
Status in mir package in Ubuntu:
  Won't Fix
Status in unity-system-compositor package in Ubuntu:
  Invalid

Bug description:
  unity-system-compositor sometimes aborts on latest xenial/arm64 on
  frieza:

  $ system-image-cli -i
  current build number: 116
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2017-01-06 09:43:26
  version version: 116
  version ubuntu: 20170106
  version device: 20161014.0
  version custom: 20170106

  /var/log/lightdm/unity-system-compositor.log has:
  ERROR: 
/build/mir-2omL3o/mir-0.25.0+16.04.20161203/src/platforms/android/server/gl_context.cpp(233):
 Throw in function virtual void 
mir::graphics::android::FramebufferGLContext::swap_buffers() const
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d)

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-system-compositor 0.8.0+16.04.20161206-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: arm64
  Date: Fri Jan  6 10:20:54 2017
  Disassembly: => 0x7fa41dd5e8: Cannot access memory at address 0x7fa41dd5e8
  ExecutablePath: /usr/sbin/unity-system-compositor
  ExecutableTimestamp: 1480992789
  GraphicsCard:
   
  ProcCmdline: unity-system-compositor --disable-overlays=false 
--spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket 
--from-dm-fd 11 --to-dm-fd 14 --vt 1
  ProcCwd: /
  ProcEnviron:
   
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   ()
   std::__exception_ptr::exception_ptr::_M_release() (this=0x7fa5647b20 
<_ZN12_GLOBAL__N_121termination_exceptionE.lto_priv.2774>) at 
../../../../src/libstdc++-v3/libsupc++/eh_ptr.cc:121
   __cxa_finalize (d=0x7fa5646498) at cxa_finalize.c:56
   __do_global_dtors_aux () at /usr/lib/aarch64-linux-gnu/libmirserver.so.42
   _dl_fini () at dl-fini.c:235
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.lightdm: lightdm 1.18.3-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1654536/+subscriptions

-- 
Mailing list: https://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 1690982] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-15 Thread Suresh Nicholas

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

Public bug reported:

I am not sure

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Tue May 16 09:05:54 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-14 (1 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  I am not sure

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Tue May 16 09:05:54 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-14 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1690980] [NEW] No pop-up window to warn users that system should not reboot or shutdown while installing security updates

2017-05-15 Thread ethan.hsieh

Public bug reported:

Title: No pop-up window to warn users that system should not reboot or
shutdown while installing security updates

Summary:
No pop-up window to warn users that system should not reboot or shutdown while 
installing security updates

Steps:
1. trigger unattended-upgrades
2. reboot or shutdown system while installing packages

Expected results: There is a pop-up window to warn users that system
should not reboot or shutdown

Actual results: There is no pop-up window to warn users

Additional information:
$ apt-cache policy unattended-upgrades
unattended-upgrades:
  Installed: 0.90
  Candidate: 0.90ubuntu0.5
$ lsb_release -rd
Description:Ubuntu 16.04 LTS

** Affects: unattended-upgrades
 Importance: Undecided
 Status: New

** Also affects: unattended-upgrades
   Importance: Undecided
   Status: New

** No longer affects: bluez (Ubuntu)

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

Title:
  No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

Status in unattended-upgrades:
  New

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

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

-- 
Mailing list: https://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 1690966] Re: Gnome Shell elements (power menu, launcher etc) are the wrong colour when using Ambiance (wrong grey, and blue highlights)

2017-05-15 Thread Jeremy Bicha

Some other themes ship a theme in /usr/share/themes/THEMENAME/gnome-
shell/ GNOME does not really recommend that distros enable the user-
theme extension by default so we should talk with GNOME to figure out
the recommended way to set a distro's default gnome-shell theme.

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

Title:
  Gnome Shell elements (power menu, launcher etc) are the wrong colour
  when using Ambiance (wrong grey, and blue highlights)

Status in gnome-shell package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  In artful, Gnome Shell elements (power menu, launcher etc) are the
  wrong colour when using Ambiance (wrong grey, and blue highlights)

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

-- 
Mailing list: https://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 1690966] [NEW] Gnome Shell elements (power menu, launcher etc) are the wrong colour when using Ambiance (wrong grey, and blue highlights)

Public bug reported:

In artful, Gnome Shell elements (power menu, launcher etc) are the wrong
colour when using Ambiance (wrong grey, and blue highlights)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: artful visual-quality

** Tags added: visual-quality

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: artful

** Summary changed:

- Gnome Shell popups (power menu, launcher etc) are the wrong colour (a blueish 
grey, not Ambiance grey)
+ Gnome Shell elements (power menu, launcher etc) are the wrong colour when 
using Ambiance (wrong grey, and blue highlights)

** Description changed:

- In artful using Ambiance, Gnome Shell popups (power menu, launcher etc)
- are the wrong colour (a blueish grey, not Ambiance grey).
+ In artful, Gnome Shell elements (power menu, launcher etc) are the wrong
+ colour when using Ambiance (wrong grey, and blue highlights)

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

Title:
  Gnome Shell elements (power menu, launcher etc) are the wrong colour
  when using Ambiance (wrong grey, and blue highlights)

Status in gnome-shell package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  In artful, Gnome Shell elements (power menu, launcher etc) are the
  wrong colour when using Ambiance (wrong grey, and blue highlights)

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

-- 
Mailing list: https://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 1685273] Re: gnome-shell: notebook tabs hard to distinguish

** Tags added: artful

** Summary changed:

- gnome-shell: notebook tabs hard to distinguish
+ Gedit/Text Editor tabs hard to distinguish under Ambiance

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

Title:
  Gedit/Text Editor tabs hard to distinguish under Ambiance

Status in ubuntu-themes package in Ubuntu:
  Triaged
Status in ubuntu-themes source package in Artful:
  Triaged

Bug description:
  Under gnome-shell, it's difficult to distinguish which tab is focused.
  See the attached screenshot.

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

-- 
Mailing list: https://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 1454841] Re: pulseaudio doesn't start if /home is a mounted CIFS

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

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

Title:
  pulseaudio doesn't start if /home is a mounted CIFS

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  I use Ubuntu 14.04.2 LTS
  >apt-cache policy pulseaudio
  pulseaudio:
Installé : 1:4.0-0ubuntu11.1
Candidat : 1:4.0-0ubuntu11.1
   Table de version :
   *** 1:4.0-0ubuntu11.1 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:4.0-0ubuntu11 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  When a user's home directory is mounted on a linux machine from
  another host using CIFS, pulseaudio will not start because pulseaudio
  cannot set the necessary permissions on the .config/pulse directory
  (CIFS doesn't allow permissions).

  I found someone that report the same bug under
  https://bugs.freedesktop.org/show_bug.cgi?id=71649

  It seams that redhat had implemented a workaround :
  https://rhn.redhat.com/errata/RHBA-2015-0419.html

  This is enoying because i do not have sound anymore since i have
  migrated all the /home/xxx directories to a nas.

  I expect to have sound even if my home directory is setup on a NAS
  through CIFS.

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

-- 
Mailing list: https://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 1690786] Re: Sound only from laptop subwoofer, not left or right speaker

** Tags added: xenial

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

Title:
  Sound only from laptop subwoofer, not left or right speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu release: 16.04

  Package version: 1:8.0-0ubuntu3.2

  Expected: Audio to play from all speakers as normal.

  What happened instead: Audio is only delivered via subwoofer. Left and
  right speakers are not detected.

  On Asus G750, Sound is delivered only from the subwoofer on the under-side of 
the laptop.
  The top speakers are ignored and subwoofer sound is distorted as it is not 
meant to be the primary sound delivery.

  Changing any settings results in total loss of audio, including
  changes to etc/pulse/daemon.conf

  In Sound settings, left and right speakers show up under test, but
  sound from both plays from the subwoofer. Subwoofer therefore seems to
  be being detected as the left and right speakers.

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

-- 
Mailing list: https://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 1690962] [NEW] [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] Audio Quiet in Left Channel

2017-05-15 Thread Sam Banks

Public bug reported:

When listening to music through the headphone jack it is normal in the
right channel but very quiet in the left.

Have tried different headphones with the same result.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   sbanks 1581 F...m pulseaudio
 /dev/snd/pcmC0D0p:   sbanks 1581 F...m pulseaudio
 /dev/snd/controlC0:  sbanks 1581 F pulseaudio
CurrentDesktop: GNOME
Date: Tue May 16 10:51:17 2017
InstallationDate: Installed on 2017-05-15 (0 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: None of the above
Title: [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] Playback 
problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.2
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.2:bd03/21/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

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

Title:
  [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] Audio Quiet
  in Left Channel

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When listening to music through the headphone jack it is normal in the
  right channel but very quiet in the left.

  Have tried different headphones with the same result.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   sbanks 1581 F...m pulseaudio
   /dev/snd/pcmC0D0p:   sbanks 1581 F...m pulseaudio
   /dev/snd/controlC0:  sbanks 1581 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May 16 10:51:17 2017
  InstallationDate: Installed on 2017-05-15 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: None of the above
  Title: [XPS 15 9560, Realtek ALC3266, Black Headphone Out, Left] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.2
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.2:bd03/21/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1673557] Re: /proc/cpuinfo should be collected

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

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

Title:
  /proc/cpuinfo should be collected

Status in apport package in Ubuntu:
  Fix Released
Status in whoopsie package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Committed
Status in whoopsie source package in Trusty:
  Fix Committed
Status in apport source package in Xenial:
  Fix Committed
Status in whoopsie source package in Xenial:
  Fix Committed
Status in apport source package in Yakkety:
  Fix Committed
Status in whoopsie source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  While some apport reports contain ProcCpuinfo not all of them do and it would 
be useful to determine how many users can only run the i386 version of Ubuntu. 
Additionally, the existing implementation gathers information about every 
processor which is quite lengthy - something smaller would be better.

  [Test Case]
  1. Run ubuntu-bug 2vcard
  2. Observe there is no report key ProcCpuinfoMinimal

  With the version of apport from -proposed you will have
  ProcCpuinfoMinimal which will contain information about your
  processor.

  To verify the whoopsie change you'll want to do the following:
  1) sudo service whoopsie stop
  2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
  3) kill -11 a process (but not the whoopsie one!)
  4) confirm sending the report
  5) Find the OOPS ID in the whoopsie output
  6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID
  7) Verify ProcCpuinfoMinimal appears in the OOPS


  [Regression Potential]
  This exists in Zesty, and Artful and there have been no issues collecting the 
information. Even if there are errors in the general ubuntu hook, which was 
modified for this SRU, apport will continue collecting information for the 
report and just add a traceback to the report about the hook error.

  The general Ubuntu hook, possibly add_kernel_info() could be used,
  should be modified such that the contents of /proc/cpuinfo are
  gathered.

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

-- 
Mailing list: https://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 1690485] Re: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

Here's the output of 'ssh -v localhost' when authorization is failing

** Attachment added: "Output of 'ssh -v localhost'"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1690485/+attachment/4877135/+files/sshclient.txt

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

Title:
  openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

Status in openssh package in Ubuntu:
  New

Bug description:
  The 'sshd' process gets 'authentication failure' and refuses to allow
  any login.

  dmesg indicates that the problem is SIGSYS on a call to 'socket'
  (syscall #41, signal #31).

  On a hunch, I decided to test whether the problem is related to
  'seccomp' and changed /etc/ssh/sshd_config from the default

  # UsePrivilegeSeparation sandbox

  to the former standard value

  UsePrivilegeSeparation yes

  and logins started to work again.

  Obviously, I'd like to have the additional protection that sandboxing
  would give me.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: openssh-server 1:7.4p1-10
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri May 12 21:06:20 2017
  InstallationDate: Installed on 2017-04-08 (35 days ago)
  InstallationMedia:
   
  SourcePackage: openssh
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago)

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

-- 
Mailing list: https://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 1690485] Re: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

And here's /etc/ssh/sshd_config on which authorization is failing.


** Attachment added: "/etc/ssh/sshd_config"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1690485/+attachment/4877150/+files/sshd_config

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

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

Title:
  openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

Status in openssh package in Ubuntu:
  New

Bug description:
  The 'sshd' process gets 'authentication failure' and refuses to allow
  any login.

  dmesg indicates that the problem is SIGSYS on a call to 'socket'
  (syscall #41, signal #31).

  On a hunch, I decided to test whether the problem is related to
  'seccomp' and changed /etc/ssh/sshd_config from the default

  # UsePrivilegeSeparation sandbox

  to the former standard value

  UsePrivilegeSeparation yes

  and logins started to work again.

  Obviously, I'd like to have the additional protection that sandboxing
  would give me.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: openssh-server 1:7.4p1-10
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri May 12 21:06:20 2017
  InstallationDate: Installed on 2017-04-08 (35 days ago)
  InstallationMedia:
   
  SourcePackage: openssh
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago)

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

-- 
Mailing list: https://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 1690485] Re: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

Here's /var/log/syslog from the ssh daemon restart through the
authorization failure

** Attachment added: "/var/log/syslog"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1690485/+attachment/4877134/+files/syslog.txt

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

Title:
  openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

Status in openssh package in Ubuntu:
  New

Bug description:
  The 'sshd' process gets 'authentication failure' and refuses to allow
  any login.

  dmesg indicates that the problem is SIGSYS on a call to 'socket'
  (syscall #41, signal #31).

  On a hunch, I decided to test whether the problem is related to
  'seccomp' and changed /etc/ssh/sshd_config from the default

  # UsePrivilegeSeparation sandbox

  to the former standard value

  UsePrivilegeSeparation yes

  and logins started to work again.

  Obviously, I'd like to have the additional protection that sandboxing
  would give me.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: openssh-server 1:7.4p1-10
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri May 12 21:06:20 2017
  InstallationDate: Installed on 2017-04-08 (35 days ago)
  InstallationMedia:
   
  SourcePackage: openssh
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago)

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

-- 
Mailing list: https://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 1690485] Re: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

I reset /etc/ssh/sshd_config to the attached version, and attempted

ssh -v localhost

while logged in as username=kennykb uid=117

The output of 'ssh -v' is attached as 'sshclient.txt'.

The only lines that appeared in syslog after I restarted the daemon were
in the attached 'syslog.txt'.

The corresponding time period in auth.log is attached as 'authlog.txt'.

The contents of /etc/ssh/ssh_config at the time of the failure are
attached.

(I'll attach the files in the next few messages.)

The first is auth.log. 192.168.1.1 is my gateway machine. I see that I'm
being hammered 3-4 times a minute with unauthorized requests to log in
as root from some external machine. Isn't the internet a spectacularly
hostile place?

If this is not enough, what else do you need?  Another developer
mentioned rebuilding from source with a particular debugging option
turned on - if you need this, can you give me a precise description of
the location and version of the package you want rebuilt and the exact
change you want?



** Attachment added: "auth.log from the ssh daemon restart through the login 
failure"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1690485/+attachment/4877132/+files/authlog.txt

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

Title:
  openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

Status in openssh package in Ubuntu:
  New

Bug description:
  The 'sshd' process gets 'authentication failure' and refuses to allow
  any login.

  dmesg indicates that the problem is SIGSYS on a call to 'socket'
  (syscall #41, signal #31).

  On a hunch, I decided to test whether the problem is related to
  'seccomp' and changed /etc/ssh/sshd_config from the default

  # UsePrivilegeSeparation sandbox

  to the former standard value

  UsePrivilegeSeparation yes

  and logins started to work again.

  Obviously, I'd like to have the additional protection that sandboxing
  would give me.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: openssh-server 1:7.4p1-10
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri May 12 21:06:20 2017
  InstallationDate: Installed on 2017-04-08 (35 days ago)
  InstallationMedia:
   
  SourcePackage: openssh
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago)

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

-- 
Mailing list: https://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 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

2017-05-15 Thread Kevin Rudloff

Hello everyone! I had the same issue. Google Chrome and Firefox just loaded 
Google's websites.
I went to resolv.conf to see what was happening and I saw a new configuration. 
So I decided to add Google's DNS and it worked again but just till I restarted 
my laptop.
I don't know much of programming but the solution purposed by Vincent Fortier 
(th0ma7) worked for me. Thanks!

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

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

-- 
Mailing list: https://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 1690437] Re: xenial autopkgtest fails because its using an End of Life release

The autopkgtests pass now:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/a/apport/20170515_093145_3c2f8@/log.gz

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

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

Title:
  xenial autopkgtest fails because its using an End of Life release

Status in apport package in Ubuntu:
  Invalid
Status in apport source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  A xenial autopackagetest, test_backend_apt_dpkg.py, for apport is failing 
because they try and get data from ddebs.ubuntu.com for an End of Life release.

  [Test Case]
  1) Observe the autopkgtest failure
  "SystemError: W:The repository 'http://ddebs.ubuntu.com wily Release' does 
not have a Release file., W:Data from such a repository can't be authenticated 
and is therefore potentially dangerous to use., W:See apt-secure(8) manpage for 
repository creation and user configuration details., E:Failed to fetch 
http://ddebs.ubuntu.com/dists/wily/main/binary-armhf/Packages  404  Not Found, 
E:Some index files failed to download. They have been ignored, or old ones used 
instead."

  With the version of apport in -proposed their will not be an
  autopkgtest failure.

  [Regression Potential]
  We are switching to the version of the autopkgtest which is currently working 
in apport and has been working since yakkety's development.  Additionally, its 
just a test change so there should be no regressions.

  Here's a link to a failure:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  xenial/xenial/amd64/a/apport/20170426_142511_fd07d@/log.gz

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

-- 
Mailing list: https://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 1516166] Re: [HDA-Intel - HDA Intel, playback] Pulseaudio fails to detect card

2017-05-15 Thread larsruneholger nilsson

Strange  i was using windows 7 with firefox  best regards Holger

Den 15 maj 2017 10:46 skrev "Daniel van Vugt" :
>
> Thank you for reporting this bug to Ubuntu.
> Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
>
> See this document for currently supported Ubuntu releases:
> https://wiki.ubuntu.com/Releases
>
> We appreciate that this bug may be old and you might not be interested
> in discussing it any more. But if you are then please upgrade to the
> latest Ubuntu version and re-test.
>
> ** Changed in: pulseaudio (Ubuntu)
>Status: New => Incomplete
>
> ** Changed in: pulseaudio (Ubuntu)
>  Assignee: larsruneholger nilsson (nilsson-holger) => (unassigned)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1516166
>
> Title:
>   [HDA-Intel - HDA Intel, playback] Pulseaudio fails to detect card
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>   00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High
Definition Audio Controller (rev 02)
> Subsystem: Fujitsu Limited. Device 1397
> Flags: bus master, fast devsel, latency 0, IRQ 29
> Memory at f054 (64-bit, non-prefetchable) [size=16K]
> Capabilities: [50] Power Management version 2
> Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
> Capabilities: [70] Express Root Complex Integrated Endpoint, MSI
00
> Capabilities: [100] Virtual Channel
> Capabilities: [130] Root Complex Link
> Kernel driver in use: snd_hda_intel
>
>
>   that was it says ! no drivers ?   best regards holger
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.10
>   Package: pulseaudio 1:6.0-0ubuntu13
>   ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
>   Uname: Linux 4.2.0-19-generic i686
>   ApportVersion: 2.19.1-0ubuntu5
>   Architecture: i386
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp',
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/controlC0',
'/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
>   CurrentDesktop: Unity
>   Date: Fri Nov 13 23:15:59 2015
>   InstallationDate: Installed on 2015-08-11 (94 days ago)
>   InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
>   SourcePackage: pulseaudio
>   Symptom: audio
>   Symptom_Card: HDA-Intel - HDA Intel
>   Title: [HDA-Intel - HDA Intel, playback] Pulseaudio fails to detect card
>   UpgradeStatus: Upgraded to wily on 2015-11-11 (2 days ago)
>   dmi.bios.date: 09/10/2008
>   dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
>   dmi.bios.version: Version 1.35
>   dmi.board.name: FJNB1B5
>   dmi.board.vendor: FUJITSU
>   dmi.board.version: CP279595-02
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: FUJITSU SIEMENS
>   dmi.chassis.version: S7110
>   dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:
bvrVersion1.35:bd09/10/2008:svnFUJITSUSIEMENS:pnLIFEBOOKS7110:pvr:
rvnFUJITSU:rnFJNB1B5:rvrCP279595-02:cvnFUJITSUSIEMENS:ct10:cvrS7110:
>   dmi.product.name: LIFEBOOK S7110
>   dmi.sys.vendor: FUJITSU SIEMENS
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+
bug/1516166/+subscriptions

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

Title:
  [HDA-Intel - HDA Intel, playback] Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition 
Audio Controller (rev 02)
Subsystem: Fujitsu Limited. Device 1397
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at f054 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: snd_hda_intel

  
  that was it says ! no drivers ?   best regards holger

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: pulseaudio 1:6.0-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Nov 13 23:15:59 2015
  InstallationDate: Installed on 2015-08-11 (94 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel
  Title: [HDA-Intel - HDA

[Touch-packages] [Bug 1493851] Re: Port to upstreamed versions of Audio Role patch

2017-05-15 Thread Albert Astals Cid

** Changed in: unity8 (Ubuntu)
 Assignee: Albert Astals Cid (aacid) => (unassigned)

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

Title:
  Port to upstreamed versions of Audio Role patch

Status in Ubuntu Clock App:
  Fix Released
Status in dropping-letters package in Ubuntu:
  Fix Released
Status in media-hub package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in qtubuntu-camera package in Ubuntu:
  Fix Released
Status in qtubuntu-media package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu:
  Fix Released
Status in ubuntu-clock-app package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  The Qt 5.5 packages at https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-012 now include the upstream versions
  of QML Playlist and Audio Role patches that went in to Qt 5.6.

  There are some differences in the Audio Role patch compared to the
  version on vivid-overlay PPA that requires changes.

  Qt 5.5 targets landing soon after xenial opens.

  For reference,
  Old API: 
http://anonscm.debian.org/cgit/pkg-kde/qt/qtmultimedia.git/diff/debian/patches/adding_media_role_property.patch?h=ubuntu=d5149eefcd093d96be3191d5f8a7f622f788e1f4
  New, upstreamed API: 
http://anonscm.debian.org/cgit/pkg-kde/qt/qtmultimedia.git/tree/debian/patches/Add-audio-role-API-to-QMediaPlayer.patch?h=ubuntu

  More information about Qt 5.5 at
  https://wiki.ubuntu.com/Touch/QtTesting

  The plan (2015-11-02):

  Patch some components to work with both old API & Qt 5.4 + new API &
  Qt 5.5 - qtubuntu-camera, qtubuntu-media to detect at compile time and
  Unity 8 at runtime.

  Pulseaudio and media-hub would land only to xenial, switching to the
  new API as part of the Qt 5.5 silo.

  Clock and dropping-letters drop the audio role usage as it's not
  supposed to be used in those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1493851/+subscriptions

-- 
Mailing list: https://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 1673557] Re: /proc/cpuinfo should be collected

Verifying the apport part for trusty:

bdmurray@upgrade-trusty-amd64:~$ grep -A4 ProcCpuinfoMinimal /tmp/test.crash
ProcCpuinfoMinimal:
 processor  : 1
 vendor_id  : GenuineIntel
 cpu family : 6
 model  : 58
bdmurray@upgrade-trusty-amd64:~$ apt-cache policy apport
apport:
  Installed: 2.14.1-0ubuntu3.24
  Candidate: 2.14.1-0ubuntu3.24

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

Title:
  /proc/cpuinfo should be collected

Status in apport package in Ubuntu:
  Fix Released
Status in whoopsie package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Committed
Status in whoopsie source package in Trusty:
  Fix Committed
Status in apport source package in Xenial:
  Fix Committed
Status in whoopsie source package in Xenial:
  Fix Committed
Status in apport source package in Yakkety:
  Fix Committed
Status in whoopsie source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  While some apport reports contain ProcCpuinfo not all of them do and it would 
be useful to determine how many users can only run the i386 version of Ubuntu. 
Additionally, the existing implementation gathers information about every 
processor which is quite lengthy - something smaller would be better.

  [Test Case]
  1. Run ubuntu-bug 2vcard
  2. Observe there is no report key ProcCpuinfoMinimal

  With the version of apport from -proposed you will have
  ProcCpuinfoMinimal which will contain information about your
  processor.

  To verify the whoopsie change you'll want to do the following:
  1) sudo service whoopsie stop
  2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
  3) kill -11 a process (but not the whoopsie one!)
  4) confirm sending the report
  5) Find the OOPS ID in the whoopsie output
  6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID
  7) Verify ProcCpuinfoMinimal appears in the OOPS


  [Regression Potential]
  This exists in Zesty, and Artful and there have been no issues collecting the 
information. Even if there are errors in the general ubuntu hook, which was 
modified for this SRU, apport will continue collecting information for the 
report and just add a traceback to the report about the hook error.

  The general Ubuntu hook, possibly add_kernel_info() could be used,
  should be modified such that the contents of /proc/cpuinfo are
  gathered.

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

-- 
Mailing list: https://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 1673557] Re: /proc/cpuinfo should be collected

The whoopsie part of the trusty SRU can be confirmed with OOPS:

https://errors.staging.ubuntu.com/oops/16658f2c-39bf-
11e7-aa36-fa163eaf9b83

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

Title:
  /proc/cpuinfo should be collected

Status in apport package in Ubuntu:
  Fix Released
Status in whoopsie package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Committed
Status in whoopsie source package in Trusty:
  Fix Committed
Status in apport source package in Xenial:
  Fix Committed
Status in whoopsie source package in Xenial:
  Fix Committed
Status in apport source package in Yakkety:
  Fix Committed
Status in whoopsie source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  While some apport reports contain ProcCpuinfo not all of them do and it would 
be useful to determine how many users can only run the i386 version of Ubuntu. 
Additionally, the existing implementation gathers information about every 
processor which is quite lengthy - something smaller would be better.

  [Test Case]
  1. Run ubuntu-bug 2vcard
  2. Observe there is no report key ProcCpuinfoMinimal

  With the version of apport from -proposed you will have
  ProcCpuinfoMinimal which will contain information about your
  processor.

  To verify the whoopsie change you'll want to do the following:
  1) sudo service whoopsie stop
  2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
  3) kill -11 a process (but not the whoopsie one!)
  4) confirm sending the report
  5) Find the OOPS ID in the whoopsie output
  6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID
  7) Verify ProcCpuinfoMinimal appears in the OOPS


  [Regression Potential]
  This exists in Zesty, and Artful and there have been no issues collecting the 
information. Even if there are errors in the general ubuntu hook, which was 
modified for this SRU, apport will continue collecting information for the 
report and just add a traceback to the report about the hook error.

  The general Ubuntu hook, possibly add_kernel_info() could be used,
  should be modified such that the contents of /proc/cpuinfo are
  gathered.

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

-- 
Mailing list: https://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 1690942] Re: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()

2017-05-15 Thread Apport retracing service

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1690942/+attachment/4877095/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1690942/+attachment/4877098/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1690942/+attachment/4877105/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1690942/+attachment/4877107/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1690942/+attachment/4877108/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1690942/+attachment/4877110/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1690942/+attachment/4877112/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1621396

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-resolved crashed with SIGSEGV in sd_event_dispatch()

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello,

  Upgrade to Ubuntu Artful Aardvark (development branch)

  Restart, and open apport

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: systemd 233-6ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu7
  Architecture: amd64
  Date: Mon May 15 18:30:13 2017
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2015-07-26 (659 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=es_CL.UTF-8
   LANGUAGE=es_CL
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-233.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-233.so
   sd_event_run () from /lib/systemd/libsystemd-shared-233.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
  UpgradeStatus: Upgraded to artful on 2017-05-15 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

-- 
Mailing list: https://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 1673557] Re: /proc/cpuinfo should be collected

Verifying the apport part for xenial:

bdmurray@clean-xenial-amd64:~$ grep -A4 ProcCpuinfoMinimal /tmp/crash.txt
ProcCpuinfoMinimal:
 processor  : 1
 vendor_id  : GenuineIntel
 cpu family : 6
 model  : 58
bdmurray@clean-xenial-amd64:~$ apt-cache policy apport
apport:
  Installed: 2.20.1-0ubuntu2.6
  Candidate: 2.20.1-0ubuntu2.6

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

Title:
  /proc/cpuinfo should be collected

Status in apport package in Ubuntu:
  Fix Released
Status in whoopsie package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Committed
Status in whoopsie source package in Trusty:
  Fix Committed
Status in apport source package in Xenial:
  Fix Committed
Status in whoopsie source package in Xenial:
  Fix Committed
Status in apport source package in Yakkety:
  Fix Committed
Status in whoopsie source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  While some apport reports contain ProcCpuinfo not all of them do and it would 
be useful to determine how many users can only run the i386 version of Ubuntu. 
Additionally, the existing implementation gathers information about every 
processor which is quite lengthy - something smaller would be better.

  [Test Case]
  1. Run ubuntu-bug 2vcard
  2. Observe there is no report key ProcCpuinfoMinimal

  With the version of apport from -proposed you will have
  ProcCpuinfoMinimal which will contain information about your
  processor.

  To verify the whoopsie change you'll want to do the following:
  1) sudo service whoopsie stop
  2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
  3) kill -11 a process (but not the whoopsie one!)
  4) confirm sending the report
  5) Find the OOPS ID in the whoopsie output
  6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID
  7) Verify ProcCpuinfoMinimal appears in the OOPS


  [Regression Potential]
  This exists in Zesty, and Artful and there have been no issues collecting the 
information. Even if there are errors in the general ubuntu hook, which was 
modified for this SRU, apport will continue collecting information for the 
report and just add a traceback to the report about the hook error.

  The general Ubuntu hook, possibly add_kernel_info() could be used,
  should be modified such that the contents of /proc/cpuinfo are
  gathered.

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

-- 
Mailing list: https://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 1673557] Re: /proc/cpuinfo should be collected

The whoopsie part of the xenial SRU can be confirmed with this OOPS:

https://errors.staging.ubuntu.com/oops/0ad9fe42-39bd-
11e7-8b26-fa163eaf9b83

** Tags added: verification-done-xenial

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

Title:
  /proc/cpuinfo should be collected

Status in apport package in Ubuntu:
  Fix Released
Status in whoopsie package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Committed
Status in whoopsie source package in Trusty:
  Fix Committed
Status in apport source package in Xenial:
  Fix Committed
Status in whoopsie source package in Xenial:
  Fix Committed
Status in apport source package in Yakkety:
  Fix Committed
Status in whoopsie source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  While some apport reports contain ProcCpuinfo not all of them do and it would 
be useful to determine how many users can only run the i386 version of Ubuntu. 
Additionally, the existing implementation gathers information about every 
processor which is quite lengthy - something smaller would be better.

  [Test Case]
  1. Run ubuntu-bug 2vcard
  2. Observe there is no report key ProcCpuinfoMinimal

  With the version of apport from -proposed you will have
  ProcCpuinfoMinimal which will contain information about your
  processor.

  To verify the whoopsie change you'll want to do the following:
  1) sudo service whoopsie stop
  2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
  3) kill -11 a process (but not the whoopsie one!)
  4) confirm sending the report
  5) Find the OOPS ID in the whoopsie output
  6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID
  7) Verify ProcCpuinfoMinimal appears in the OOPS


  [Regression Potential]
  This exists in Zesty, and Artful and there have been no issues collecting the 
information. Even if there are errors in the general ubuntu hook, which was 
modified for this SRU, apport will continue collecting information for the 
report and just add a traceback to the report about the hook error.

  The general Ubuntu hook, possibly add_kernel_info() could be used,
  should be modified such that the contents of /proc/cpuinfo are
  gathered.

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

-- 
Mailing list: https://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 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present

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

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

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

Title:
  during recovery mode, enable network failed due to /etc/resolv.conf
  not being present

Status in network-manager package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  Confirmed

Bug description:
  Something went wrong that required me to boot to recovery mode via
  grub.  The important part here, is that while I got as far as the
  recovery screen asking to "Enable Networking" and other options fsck
  filesystems, drop to root shell, etc.

  and selected "Enable Networking":

  the result was:

  grep: /etc/resolv.conf: No such File or directory.

  Unknown group "power" in message bus configuration file.


  (Networking did not enable, leaving me stranded at root shell without
  network which would have made adding/removing packages to troubleshoot
  easier)

  Ubuntu: zesty 17.04
  Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
  network-manager: 1.4.4-1ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  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
  CurrentDesktop: XFCE
  Date: Thu Apr 13 16:40:19 2017
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-09 (1009 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  IpRoute:
   default via 192.168.250.1 dev wlan1 proto static metric 600 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 
   192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   lxcbr0  bridgeconnected/org/freedesktop/NetworkManager/Devices/3  
lxcbr0  46595dd8-757b-4d93-ade3-c066f72d9e2e  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan1   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
Brisbane House  2b25e748-f9c5-4c84-9fe6-0f64071fcf0b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eth1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  disabled

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

-- 
Mailing list: https://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 1673557] Re: /proc/cpuinfo should be collected

The whoopsie part of yakkety can be confirmed with this OOPS:

https://errors.staging.ubuntu.com/oops/8ff45a12-39ba-
11e7-aa36-fa163eaf9b83

** Tags added: verification-done-yakkety

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

Title:
  /proc/cpuinfo should be collected

Status in apport package in Ubuntu:
  Fix Released
Status in whoopsie package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Committed
Status in whoopsie source package in Trusty:
  Fix Committed
Status in apport source package in Xenial:
  Fix Committed
Status in whoopsie source package in Xenial:
  Fix Committed
Status in apport source package in Yakkety:
  Fix Committed
Status in whoopsie source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  While some apport reports contain ProcCpuinfo not all of them do and it would 
be useful to determine how many users can only run the i386 version of Ubuntu. 
Additionally, the existing implementation gathers information about every 
processor which is quite lengthy - something smaller would be better.

  [Test Case]
  1. Run ubuntu-bug 2vcard
  2. Observe there is no report key ProcCpuinfoMinimal

  With the version of apport from -proposed you will have
  ProcCpuinfoMinimal which will contain information about your
  processor.

  To verify the whoopsie change you'll want to do the following:
  1) sudo service whoopsie stop
  2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
  3) kill -11 a process (but not the whoopsie one!)
  4) confirm sending the report
  5) Find the OOPS ID in the whoopsie output
  6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID
  7) Verify ProcCpuinfoMinimal appears in the OOPS


  [Regression Potential]
  This exists in Zesty, and Artful and there have been no issues collecting the 
information. Even if there are errors in the general ubuntu hook, which was 
modified for this SRU, apport will continue collecting information for the 
report and just add a traceback to the report about the hook error.

  The general Ubuntu hook, possibly add_kernel_info() could be used,
  should be modified such that the contents of /proc/cpuinfo are
  gathered.

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

-- 
Mailing list: https://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 1673557] Re: /proc/cpuinfo should be collected

Verifying the apport part for yakkety:

 $ apt-cache policy apport
apport:
  Installed: 2.20.3-0ubuntu8.3
  Candidate: 2.20.3-0ubuntu8.3

 $ grep -A4 ProcCpuinfoMinimal /tmp/test.crash
ProcCpuinfoMinimal:
 processor  : 3
 vendor_id  : GenuineIntel
 cpu family : 6
 model  : 58
 ...

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

Title:
  /proc/cpuinfo should be collected

Status in apport package in Ubuntu:
  Fix Released
Status in whoopsie package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Committed
Status in whoopsie source package in Trusty:
  Fix Committed
Status in apport source package in Xenial:
  Fix Committed
Status in whoopsie source package in Xenial:
  Fix Committed
Status in apport source package in Yakkety:
  Fix Committed
Status in whoopsie source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  While some apport reports contain ProcCpuinfo not all of them do and it would 
be useful to determine how many users can only run the i386 version of Ubuntu. 
Additionally, the existing implementation gathers information about every 
processor which is quite lengthy - something smaller would be better.

  [Test Case]
  1. Run ubuntu-bug 2vcard
  2. Observe there is no report key ProcCpuinfoMinimal

  With the version of apport from -proposed you will have
  ProcCpuinfoMinimal which will contain information about your
  processor.

  To verify the whoopsie change you'll want to do the following:
  1) sudo service whoopsie stop
  2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
  3) kill -11 a process (but not the whoopsie one!)
  4) confirm sending the report
  5) Find the OOPS ID in the whoopsie output
  6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID
  7) Verify ProcCpuinfoMinimal appears in the OOPS


  [Regression Potential]
  This exists in Zesty, and Artful and there have been no issues collecting the 
information. Even if there are errors in the general ubuntu hook, which was 
modified for this SRU, apport will continue collecting information for the 
report and just add a traceback to the report about the hook error.

  The general Ubuntu hook, possibly add_kernel_info() could be used,
  should be modified such that the contents of /proc/cpuinfo are
  gathered.

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

-- 
Mailing list: https://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 1689344] Re: print of __glib_assert_msg not returning a message

Verification for yakkety:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-
yakkety/yakkety/amd64/a/apport/20170512_193229_92825@/log.gz

Verification for zesty:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-zesty/zesty/amd64/a/apport/20170512_193953_7d1ed@/log.gz

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

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

Title:
  print of __glib_assert_msg not returning a message

Status in apport package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  New
Status in apport source package in Yakkety:
  Fix Committed
Status in glib2.0 source package in Yakkety:
  New
Status in apport source package in Zesty:
  Fix Committed
Status in glib2.0 source package in Zesty:
  New

Bug description:
  [Impact]
  apport's test, test_add_gdb_info_abort_glib is failing due to a change 
somewhere in glib2.0, how its built, or gdb. The test shall be disabled while 
the matter is investigated.

  [Test Case]
  Run the autopkgtest and observe the failure.
  With the version of the package in proposed the test will not be run.

  [Regression Potential]
  We are just disabling a broken test so there is none.

  apport's test test_add_gdb_info_abort_glib has been failing for a bit,
  since zesty(?), now. Digging into this matter I discovered that using
  gdb to "print __glib_assert_msg" is resulting in different behavior.

  With the generated binary, it used to return the following:

  $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 <
  0)"

  However, now I am seeing:

  (gdb) print __glib_assert_msg
  $1 = 1332592064
  (gdb) print (char*) __glib_assert_msg
  $2 = 0x4f6dbdc0 

  This seems to be a regression in gdb itself, I've added an apport task
  though to track the disabling of the autopkgtest which utilizes this
  command.

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

-- 
Mailing list: https://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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-05-15 Thread Vincent

Here is a solution that seems to work for me.

Note that I use a simple openvpn client configuration file that I run
directly from the console. I don't use a GUI for my vpn connection, but
I assume you can do the same via a gui interface.

Within my openvpn client config file, I call a script called update-
systemd-resolved as a replacement to the standard update-resolv-conf
used previously.

That script is available here: https://github.com/jonathanio/update-
systemd-resolved

After that, after connecting, when I run systemd-resolve --status I can
see that a new link is added for tun0 with the proper dns entries.

But that's only a first step, because it seems that with
systemd.resolved.service (I quote) "Multi-label names are routed to all
local interfaces that have a DNS sever configured (...) If lookups are
routed to multiple interfaces, the first successful response is
returned".  So basically it's still sending requests on all interfaces,
including the main eth0 or whatever it is on your system, and the
fastest one wins (in my case because eth0 points to my router that acts
as a dns server, it always wins). To avoid leaks, we want only requests
to go to the tun0 link.

Then I read that "Routing of lookups may be influenced by configuring
per-interface domain names".  If you read the instructions in the
update-systemd-resolved, you'll see that it allows to specify dhcp-
options DOMAIN-ROUTE to force a specific domain to go through that
interface. You can use a single dot to mean all domains.

So basically I added dhcp-option DOMAIN-ROUTE . to my clienf config to
send everything exclusively to tun0 and that seems to do the trick.

So combined with the instructions from the github page, this is what I
have on my config:

# avoid dns leak when using systemd-resolved
dhcp-option DOMAIN-ROUTE .
script-security 2
setenv PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
up /etc/openvpn/update-systemd-resolved
down /etc/openvpn/update-systemd-resolved
down-pre

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

-- 
Mailing list: https://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 1454841] Re: pulseaudio doesn't start if /home is a mounted CIFS

2017-05-15 Thread Emmanuel

The Ugly patch is not needed anymore on 16.04. Everythings works fine
without it.

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

Title:
  pulseaudio doesn't start if /home is a mounted CIFS

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I use Ubuntu 14.04.2 LTS
  >apt-cache policy pulseaudio
  pulseaudio:
Installé : 1:4.0-0ubuntu11.1
Candidat : 1:4.0-0ubuntu11.1
   Table de version :
   *** 1:4.0-0ubuntu11.1 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:4.0-0ubuntu11 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  When a user's home directory is mounted on a linux machine from
  another host using CIFS, pulseaudio will not start because pulseaudio
  cannot set the necessary permissions on the .config/pulse directory
  (CIFS doesn't allow permissions).

  I found someone that report the same bug under
  https://bugs.freedesktop.org/show_bug.cgi?id=71649

  It seams that redhat had implemented a workaround :
  https://rhn.redhat.com/errata/RHBA-2015-0419.html

  This is enoying because i do not have sound anymore since i have
  migrated all the /home/xxx directories to a nas.

  I expect to have sound even if my home directory is setup on a NAS
  through CIFS.

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

-- 
Mailing list: https://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 1690933] [NEW] isc-dhcp-server/dhcpd listens on 0.0.0.0:67/UDP no matter which interfaces is specified

2017-05-15 Thread Karl-Philipp Richter

Public bug reported:

The behaviour of the `systemd` unit `isc-dhcp-server.service` is the
same as on the command line: both `sudo dhcpd` and `sudo dhcpd p18p1`
(where `p18p1` is the name of a network interfaces) cause the daemon to
listen on all interfaces according to `sudo netstat -tupln | grep :67`:

udp0  0 0.0.0.0:67  0.0.0.0:*
5382/dnsmasq

The `isc-dhcp-server6.service` unit is deactivated.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: isc-dhcp-server 4.3.5-3ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Mon May 15 23:41:54 2017
DhServerLeases:
 
InstallationDate: Installed on 2015-04-20 (756 days ago)
InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
ProcEnviron:
 TERM=screen.xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: isc-dhcp
UpgradeStatus: Upgraded to zesty on 2017-05-05 (9 days ago)
mtime.conffile..etc.dhcp.dhcpd.conf: 2017-05-15T23:37:21.502892

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

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

Title:
  isc-dhcp-server/dhcpd listens on 0.0.0.0:67/UDP no matter which
  interfaces is specified

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  The behaviour of the `systemd` unit `isc-dhcp-server.service` is the
  same as on the command line: both `sudo dhcpd` and `sudo dhcpd p18p1`
  (where `p18p1` is the name of a network interfaces) cause the daemon
  to listen on all interfaces according to `sudo netstat -tupln | grep
  :67`:

  udp0  0 0.0.0.0:67  0.0.0.0:*
  5382/dnsmasq

  The `isc-dhcp-server6.service` unit is deactivated.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: isc-dhcp-server 4.3.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon May 15 23:41:54 2017
  DhServerLeases:
   
  InstallationDate: Installed on 2015-04-20 (756 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: Upgraded to zesty on 2017-05-05 (9 days ago)
  mtime.conffile..etc.dhcp.dhcpd.conf: 2017-05-15T23:37:21.502892

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

-- 
Mailing list: https://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 1649310] Re: RM Upstart, obsolete, superseded by systemd / Products discontinued

2017-05-15 Thread Steve Langasek

Removing packages from artful:
mountall 2.54ubuntu1 in artful
mountall 2.54ubuntu1 in artful amd64
mountall 2.54ubuntu1 in artful arm64
mountall 2.54ubuntu1 in artful armhf
mountall 2.54ubuntu1 in artful i386
mountall 2.54ubuntu1 in artful ppc64el
mountall 2.54ubuntu1 in artful s390x
Comment: Unused, replaced by systemd; LP: #1649310
Remove [y|N]? y
1 package successfully removed.


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

** Changed in: mountall (Ubuntu)
   Status: New => Fix Released

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

Title:
  RM Upstart, obsolete, superseded by systemd / Products discontinued

Status in cgmanager package in Ubuntu:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Released
Status in mountall package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart-watchdog package in Ubuntu:
  Fix Released

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

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

-- 
Mailing list: https://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 1605189] Re: Authentication is required for suspending the system

2017-05-15 Thread Markus Kwaśnicki

I also went into this issue "system is asking for authentication to
suspend" running Xubuntu 17.04 Zesty Zapus.

But luckily I figured out, this behaviour came when I set "lock session
automatically when screensaver is activated" in the security tab of XFCE
power management. Setting it back to "never", suspending the system is
working without authentication again.

Hope that hint helps finding some better solution.

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

Title:
  Authentication is required for suspending the system

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspend from the xfce power manager does not work, as a
  window opens and asks for my password. Well, if it wants to suspend
  the system after a given timeout, I cannot enter my password as I'm
  not in front of my system then. Once I'm able to enter my password it
  is too late to run the suspend action.

  The window asking for my password prints:

  Password: 

  Details

  Action: org.freedesktop.login1.suspend
  Vendor: The systemd project

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jul 21 13:13:12 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-17 (703 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 4236ML1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro intel_pstate=enable
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   2 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-05-28 (53 days ago)
  dmi.bios.date: 07/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4236ML1
  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:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236ML1:pvrThinkPadT420:rvnLENOVO:rn4236ML1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4236ML1
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 775803] ☯means a lot to me

2017-05-15 Thread John Butterworth

Dear,

Please read this info, it means so  much to me, here is the link
http://wolmedia.net/mysterious.php?2829

My best to you, john.butterworth

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

Title:
  /usr/bin/python: error while loading shared libraries: /lib/i386
  -linux-gnu/libz.so.1: invalid ELF header

Status in zlib package in Ubuntu:
  New

Bug description:
  Binary package hint: nvidia-common

  Upgrade failed to install correctly

  ProblemType: Package
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-9-generic 2.6.38-9.43
  ProcVersionSignature: Ubuntu 2.6.35-29.51-generic 2.6.35.12
  Uname: Linux 2.6.35-29-generic i686
  Architecture: i386
  Date: Mon May  2 19:42:26 2011
  ErrorMessage: run-parts: /etc/kernel/postinst.d/nvidia-common exited with 
return code 127
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  SourcePackage: nvidia-common
  Title: package linux-image-2.6.38-9-generic 2.6.38-9.43 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/nvidia-common exited with 
return code 127
  UpgradeStatus: Upgraded to natty on 2011-05-02 (0 days ago)

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

-- 
Mailing list: https://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 1690881] Re: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu13 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-05-15 Thread Steve Langasek

The error in your logs is:

dpkg: dependency problems prevent processing triggers for 
plymouth-theme-ubuntu-text:
 plymouth-theme-ubuntu-text depends on lsb-release; however:
  Package lsb-release is not configured yet.

And before this:

Unpacking lsb-release (9.20160110ubuntu0.2) over (9.20160110) ...

AptOrdering.txt claims that lsb-release is supposed to be configured
before plymouth-theme-ubuntu-text is configured.

So this is a problem with apt's upgrade ordering in the face of dpkg
triggers.

** Package changed: plymouth (Ubuntu) => apt (Ubuntu)

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

Title:
  package plymouth-theme-ubuntu-text 0.9.2-3ubuntu13 failed to
  install/upgrade: dependency problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  New

Bug description:
  was unable to install new updates

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu13
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May 14 21:31:28 2017
  DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
   Bus 001 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. H110M-S2
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.10ubuntu1
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu13 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-S2-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20:bd11/16/2016:svnGigabyteTechnologyCo.,Ltd.:pnH110M-S2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: H110M-S2
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://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 1690881] [NEW] package plymouth-theme-ubuntu-text 0.9.2-3ubuntu13 failed to install/upgrade: dependency problems - leaving triggers unprocessed

You have been subscribed to a public bug:

was unable to install new updates

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu13
ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
Uname: Linux 4.4.0-77-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sun May 14 21:31:28 2017
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ErrorMessage: dependency problems - leaving triggers unprocessed
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
 Bus 001 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for 
Bluetooth
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. H110M-S2
ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.10ubuntu1
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu13 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F20
dmi.board.asset.tag: Default string
dmi.board.name: H110M-S2-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20:bd11/16/2016:svnGigabyteTechnologyCo.,Ltd.:pnH110M-S2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: H110M-S2
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-package xenial
-- 
package plymouth-theme-ubuntu-text 0.9.2-3ubuntu13 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
https://bugs.launchpad.net/bugs/1690881
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apt in Ubuntu.

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

[Touch-packages] [Bug 1689854] Re: Multiple DHCPv6 client interfaces fail to receive some server responses

2017-05-15 Thread Dan Streetman

I reproduced the problem with:

ii isc-dhcp-client 4.2.4-7ubuntu12.8
amd64ISC DHCP client
ii isc-dhcp-common 4.2.4-7ubuntu12.8
amd64common files used by all the isc-dhcp* packages

After adding the proposed repo and updating isc-dhcp-client and isc-dhcp-common
to:

ii isc-dhcp-client 4.2.4-7ubuntu12.9
amd64ISC DHCP client
ii isc-dhcp-common 4.2.4-7ubuntu12.9
amd64common files used by all the isc-dhcp* packages

the problem was fixed and all IPv6 DHCPv6 interfaces successfully were
configured with their IPv6 addresses.

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

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

Title:
Multiple DHCPv6 client interfaces fail to receive some server
responses

Status in isc-dhcp package in Ubuntu:
Fix Released
Status in isc-dhcp source package in Trusty:
Fix Committed

Bug description:
[Impact]

When using isc-dhcp-client on a Trusty system, with multiple
interfaces configured to use DHCPv6, not all the DHCPv6 clients will
receive the server responses on some of the interfaces. This results
in not all DHCPv6 interfaces being configured.

[Test Case]

Set up a DHCPv6 server with multiple interfaces (3-4 is enough) and
configure it to serve DHCPv6 on all the interfaces (as separate
subnets). The server release does not matter. Set up a client system
with the same number of interfaces, connected/bridged to the server
interfaces. The client must be a Trusty system. Configure (with
ifupdown via /etc/network/interfaces) all the interfaces to use
DHCPv6, and reboot. Keep rebooting until one or more of the DHCPv6
interfaces fails to get an address; it should not take more than a few
reboots. After a failure, even manual ifdown/ifup on the failed
interface will not get a DHCPv6 address.

[Regression Potential]

* As this changes how the isc-dhcp-client binds to IPv6 sockets, this
could cause problems when the client tries to bind, send, or receive,
with this or other operations.

* This is fixed upstream already, and the patch is included in Xenial
and later releases. This patch is needed only in the Trusty release.

* Upstream patch :

https://source.isc.org/cgi-bin/gitweb.cgi?p=dhcp.git;a=commit;h=4b8251a0c06b7d8706a28904fdef2414f045cc2c

[Other Info]

* [ISC-Bugs #34784]
Please note that no ISC bug URL can be provided since the ISC bug database is
closed :

Reference: https://www.isc.org/community/report-bug/
...
Confidentiality

It is typical for open-source projects to have an open bug database. At the
moment, the ISC bug database is closed. However, we reserve the right to
publish your bug report at some point in the future. Please do not include
information you consider to be confidential.
...

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

--
Mailing list: https://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 1685273] Re: gnome-shell: notebook tabs hard to distinguish

2017-05-15 Thread Adolfo Jayme

** No longer affects: light-themes (Ubuntu)

** No longer affects: light-themes (Ubuntu Artful)

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

** Changed in: ubuntu-themes (Ubuntu Artful)
   Importance: Undecided => Medium

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

Title:
  gnome-shell: notebook tabs hard to distinguish

Status in ubuntu-themes package in Ubuntu:
  Triaged
Status in ubuntu-themes source package in Artful:
  Triaged

Bug description:
  Under gnome-shell, it's difficult to distinguish which tab is focused.
  See the attached screenshot.

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

-- 
Mailing list: https://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 1690894] [NEW] package libtiff5:amd64 4.0.6-1ubuntu0.1 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de

2017-05-15 Thread Antoine Jacquin

Public bug reported:

Maybe it's because I use 4K Downloader Who isn't in the Ubuntu official
online Market

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libtiff5:amd64 4.0.6-1ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
Uname: Linux 4.4.0-67-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon May  8 00:08:37 2017
ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  le 
réinstaller avant de tenter de le configurer.
InstallationDate: Installed on 2016-05-25 (355 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: tiff
Title: package libtiff5:amd64 4.0.6-1ubuntu0.1 failed to install/upgrade: le 
paquet est dans un état vraiment incohérent; vous devriez  le réinstaller avant 
de tenter de le configurer.
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libtiff5:amd64 4.0.6-1ubuntu0.1 failed to install/upgrade: le
  paquet est dans un état vraiment incohérent; vous devriez  le
  réinstaller avant de tenter de le configurer.

Status in tiff package in Ubuntu:
  New

Bug description:
  Maybe it's because I use 4K Downloader Who isn't in the Ubuntu
  official online Market

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libtiff5:amd64 4.0.6-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon May  8 00:08:37 2017
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2016-05-25 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: tiff
  Title: package libtiff5:amd64 4.0.6-1ubuntu0.1 failed to install/upgrade: le 
paquet est dans un état vraiment incohérent; vous devriez  le réinstaller avant 
de tenter de le configurer.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1690891] [NEW] RFE: remove ureadahead from package minimal

2017-05-15 Thread Jens Elkner

Public bug reported:

Since on common platforms ureadahead solves nothing but causes a huge
amount of garbage/totally useless error messages, which makes it really
hard to extract the important messages from e.g. journalctl output,  it
should be removed from ubuntu-minimal. If there are people, who need it,
can still explicitly install it.

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

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

Title:
  RFE: remove ureadahead from package minimal

Status in ureadahead package in Ubuntu:
  New

Bug description:
  Since on common platforms ureadahead solves nothing but causes a huge
  amount of garbage/totally useless error messages, which makes it
  really hard to extract the important messages from e.g. journalctl
  output,  it should be removed from ubuntu-minimal. If there are
  people, who need it, can still explicitly install it.

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

-- 
Mailing list: https://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 1590543] Re: A2DP configuration does not work on Kubuntu 16.04 with stereo speaker

2017-05-15 Thread Hervé Le Roy

Until this is fixed in a future release of Kubuntu, this gist does the
job: https://gist.github.com/pylover/d68be364adac5f946887b85e6ed6e7ae

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

Title:
  A2DP configuration does not work on Kubuntu 16.04 with stereo speaker

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The mode A2DP Sink does not work with my speaker Sony SRS-BTM8. PulseAudio 
shows three options,
  - HSP / HFP
  - A2DP Sink
  - Off
  Only works HSP and off options.
  Previously with version 14.04 everything worked perfectly, but since a few 
weeks upgraded to version 16.04 does not work correctly and I can not hear HiFi 
music, only low-quality mode.

  See the video settings

  https://mega.nz/#!L8p33BSZ!pyb6hZDKRW_JBLbDJ0mxYTPtv-vzi7QMGSZv8YU5N-k

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

-- 
Mailing list: https://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 1668914] Re: package humanity-icon-theme 0.6.10.1 failed to install/upgrade: package humanity-icon-theme is not ready for configuration cannot configure (current status 'half-ins

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

** Changed in: humanity-icon-theme (Ubuntu)
   Status: New => Confirmed

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

Title:
  package humanity-icon-theme 0.6.10.1 failed to install/upgrade:
  package humanity-icon-theme is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in humanity-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  really dont knw

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: humanity-icon-theme 0.6.10.1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Mar  1 14:44:40 2017
  ErrorMessage: package humanity-icon-theme is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-02-23 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: humanity-icon-theme
  Title: package humanity-icon-theme 0.6.10.1 failed to install/upgrade: 
package humanity-icon-theme is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1668914/+subscriptions

-- 
Mailing list: https://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 1689408] Re: System hang when utilising OpenGL 4.5 features

2017-05-15 Thread Joseph Salisbury

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

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

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

Title:
  System hang when utilising OpenGL 4.5 features

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  New

Bug description:
  I've found this to be easily reproducible via unigine's heaven
  benchmark, which uses tessellation and other features extensively.
  Simply creating a OpenGL 4.5 context will not trigger the hang, and
  you must explicitly request an OGL 4+ context as the default will only
  be 3.0.

  On a successful trigger, the screen may flicker on and off a few times
  and eventually hang completely on a black screen, there's no way to
  recover the system from this state bar a power cycle (ie hold the
  power button).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paulh  1405 F pulseaudio
   /dev/snd/controlC0:  paulh  1405 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue May  9 09:14:09 2017
  InstallationDate: Installed on 2017-01-05 (123 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=a5482167-6676-4a1a-b150-a86255560de6 ro rhgb quiet 
resume=/dev/sda6/swapfile resume_offset=7673856 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (24 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8133
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 98.0E
  dmi.chassis.asset.tag: 5CG6124XBK
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://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 1689537] Re: busybox: segmentation fault while ping to domain name (out of bound)

2017-05-15 Thread Joseph Salisbury

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

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

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

Title:
  busybox: segmentation fault while ping to domain name (out of bound)

Status in Linux:
  Fix Released
Status in busybox package in Ubuntu:
  New

Bug description:
  when running ping on an ARM (ubuntu version 17.4):
  root@raminfp:/home/raminfp/# /bin/busybox ping google.com
  Segmentation fault (core dumped)

  strace info :

  root@raminfp:/home/raminfp/Desktop/filegir# strace /bin/busybox ping 
google.com
  execve("/bin/busybox", ["/bin/busybox", "ping", "google.com"], [/* 67 vars 
*/]) = 0
  uname({sysname="Linux", nodename="raminfp", ...}) = 0
  brk(NULL)   = 0x260a000
  brk(0x260b1c0)  = 0x260b1c0
  arch_prctl(ARCH_SET_FS, 0x260a880)  = 0
  readlink("/proc/self/exe", "/bin/busybox", 4096) = 12
  brk(0x262c1c0)  = 0x262c1c0
  brk(0x262d000)  = 0x262d000
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  getuid()= 0
  getpid()= 7639
  socket(AF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
  connect(3, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 
ENOENT (No such file or directory)
  close(3)= 0
  socket(AF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
  connect(3, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 
ENOENT (No such file or directory)
  close(3)= 0
  open("/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=555, ...}) = 0
  read(3, "# /etc/nsswitch.conf\n#\n# Example"..., 4096) = 555
  read(3, "", 4096)   = 0
  close(3)= 0
  open("/etc/host.conf", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=92, ...}) = 0
  read(3, "# The \"order\" line is only used "..., 4096) = 92
  read(3, "", 4096)   = 0
  close(3)= 0
  open("/etc/resolv.conf", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=172, ...}) = 0
  read(3, "# Dynamic resolv.conf(5) file fo"..., 4096) = 172
  read(3, "", 4096)   = 0
  close(3)= 0
  uname({sysname="Linux", nodename="raminfp", ...}) = 0
  open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=137281, ...}) = 0
  mmap(NULL, 137281, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fc32082d000
  close(3)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  open("/lib/x86_64-linux-gnu/libnss_files.so.2", O_RDONLY|O_CLOEXEC) = 3
  read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320!\0\0\0\0\0\0"..., 
832) = 832
  fstat(3, {st_mode=S_IFREG|0644, st_size=47608, ...}) = 0
  mmap(NULL, 2168600, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fc32061b000
  mprotect(0x7fc320626000, 2093056, PROT_NONE) = 0
  mmap(0x7fc320825000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xa000) = 0x7fc320825000
  mmap(0x7fc320827000, 22296, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fc320827000
  close(3)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\20\5\2\0\0\0\0\0"..., 
832) = 832
  fstat(3, {st_mode=S_IFREG|0755, st_size=1856752, ...}) = 0
  mmap(NULL, 3959200, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fc320254000
  mprotect(0x7fc320411000, 2097152, PROT_NONE) = 0
  mmap(0x7fc320611000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1bd000) = 0x7fc320611000
  mmap(0x7fc320617000, 14752, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fc320617000
  close(3)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  open("/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2", O_RDONLY|O_CLOEXEC) = 3
  read(3, 
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\240\f\0\0\0\0\0\0"..., 832) = 
832
  fstat(3, {st_mode=S_IFREG|0755, st_size=158512, ...}) = 0
  mmap(NULL, 2253160, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fc32002d000
  mprotect(0x7fc320052000, 2093056, PROT_NONE) = 0
  mmap(0x7fc320251000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x24000) = 0x7fc320251000
  mmap(0x7fc320253000, 360, PROT_READ|PROT_WRITE,

[Touch-packages] [Bug 1689854] Re: Multiple DHCPv6 client interfaces fail to receive some server responses

2017-05-15 Thread Łukasz Zemczak

Hello Dan, or anyone else affected,

Accepted isc-dhcp into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.2.4-7ubuntu12.9 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  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: isc-dhcp (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  Multiple DHCPv6 client interfaces fail to receive some server
  responses

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  When using isc-dhcp-client on a Trusty system, with multiple
  interfaces configured to use DHCPv6, not all the DHCPv6 clients will
  receive the server responses on some of the interfaces.  This results
  in not all DHCPv6 interfaces being configured.

  [Test Case]

  Set up a DHCPv6 server with multiple interfaces (3-4 is enough) and
  configure it to serve DHCPv6 on all the interfaces (as separate
  subnets).  The server release does not matter.  Set up a client system
  with the same number of interfaces, connected/bridged to the server
  interfaces.  The client must be a Trusty system.  Configure (with
  ifupdown via /etc/network/interfaces) all the interfaces to use
  DHCPv6, and reboot.  Keep rebooting until one or more of the DHCPv6
  interfaces fails to get an address; it should not take more than a few
  reboots.  After a failure, even manual ifdown/ifup on the failed
  interface will not get a DHCPv6 address.

  [Regression Potential]

  * As this changes how the isc-dhcp-client binds to IPv6 sockets, this
  could cause problems when the client tries to bind, send, or receive,
  with this or other operations.

  * This is fixed upstream already, and the patch is included in Xenial
  and later releases.  This patch is needed only in the Trusty release.

  * Upstream patch :
  
https://source.isc.org/cgi-bin/gitweb.cgi?p=dhcp.git;a=commit;h=4b8251a0c06b7d8706a28904fdef2414f045cc2c

  [Other Info]

  * [ISC-Bugs #34784]
  Please note that no ISC bug URL can be provided since the ISC bug database is 
closed :

  Reference:  https://www.isc.org/community/report-bug/
  ...
  Confidentiality

  It is typical for open-source projects to have an open bug database. At the 
moment, the ISC bug database is closed.  However, we reserve the right to 
publish your bug report at some point in the future. Please do not include 
information you consider to be confidential.
  ...

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

-- 
Mailing list: https://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 1689537] [NEW] busybox: segmentation fault while ping to domain name (out of bound)

You have been subscribed to a public bug:

when running ping on an ARM (ubuntu version 17.4):
root@raminfp:/home/raminfp/# /bin/busybox ping google.com
Segmentation fault (core dumped)

strace info :

root@raminfp:/home/raminfp/Desktop/filegir# strace /bin/busybox ping google.com
execve("/bin/busybox", ["/bin/busybox", "ping", "google.com"], [/* 67 vars */]) 
= 0
uname({sysname="Linux", nodename="raminfp", ...}) = 0
brk(NULL)   = 0x260a000
brk(0x260b1c0)  = 0x260b1c0
arch_prctl(ARCH_SET_FS, 0x260a880)  = 0
readlink("/proc/self/exe", "/bin/busybox", 4096) = 12
brk(0x262c1c0)  = 0x262c1c0
brk(0x262d000)  = 0x262d000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
getuid()= 0
getpid()= 7639
socket(AF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
connect(3, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 
ENOENT (No such file or directory)
close(3)= 0
socket(AF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
connect(3, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 
ENOENT (No such file or directory)
close(3)= 0
open("/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=555, ...}) = 0
read(3, "# /etc/nsswitch.conf\n#\n# Example"..., 4096) = 555
read(3, "", 4096)   = 0
close(3)= 0
open("/etc/host.conf", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=92, ...}) = 0
read(3, "# The \"order\" line is only used "..., 4096) = 92
read(3, "", 4096)   = 0
close(3)= 0
open("/etc/resolv.conf", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=172, ...}) = 0
read(3, "# Dynamic resolv.conf(5) file fo"..., 4096) = 172
read(3, "", 4096)   = 0
close(3)= 0
uname({sysname="Linux", nodename="raminfp", ...}) = 0
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=137281, ...}) = 0
mmap(NULL, 137281, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fc32082d000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libnss_files.so.2", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320!\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=47608, ...}) = 0
mmap(NULL, 2168600, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fc32061b000
mprotect(0x7fc320626000, 2093056, PROT_NONE) = 0
mmap(0x7fc320825000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xa000) = 0x7fc320825000
mmap(0x7fc320827000, 22296, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fc320827000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\20\5\2\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1856752, ...}) = 0
mmap(NULL, 3959200, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fc320254000
mprotect(0x7fc320411000, 2097152, PROT_NONE) = 0
mmap(0x7fc320611000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1bd000) = 0x7fc320611000
mmap(0x7fc320617000, 14752, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fc320617000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\240\f\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=158512, ...}) = 0
mmap(NULL, 2253160, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fc32002d000
mprotect(0x7fc320052000, 2093056, PROT_NONE) = 0
mmap(0x7fc320251000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x24000) = 0x7fc320251000
mmap(0x7fc320253000, 360, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fc320253000
close(3)= 0
mprotect(0x7fc320251000, 4096, PROT_READ) = 0
mprotect(0x7fc320611000, 16384, PROT_READ) = 0
mprotect(0x7fc320825000, 4096, PROT_READ) = 0
munmap(0x7fc32082d000, 137281)  = 0
mmap(NULL, 1048576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fc31ff2d000
open("/etc/hosts", O_RDONLY|O_CLOEXEC)  = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=222, ...}) = 0
read(3, "127.0.0.1\tlocalhost\n127.0.1.1\tra"..., 4096) = 222
read(3, "", 4096)   = 0
close(3)

[Touch-packages] [Bug 1651623] Re: adt tests fail on zesty for apport

Setting to v-done for zesty:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-zesty/zesty/amd64/a/apport/20170512_193953_7d1ed@/log.gz

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

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

Title:
  adt tests fail on zesty for apport

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Invalid
Status in apport source package in Yakkety:
  Fix Committed
Status in apport source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Apport autopkgtests are failing with GPG errors e.g.:
  SystemError: W:GPG error: http://archive.ubuntu.com/ubuntu trusty Release: 
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32, E:The 
repository 'http://archive.ubuntu.com/ubuntu trusty Release' is not signed.

  [Test Case]
  Run the autopkgtests and observe failures regarding GPG.
  With the test fixed there should be no failures.

  [Regression Potential]
  While not a regression its possible fixing these tests will reveal other 
failures.

  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz

  fails.

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

-- 
Mailing list: https://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 1651623] Re: adt tests fail on zesty for apport

Setting to v-done for yakkety:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-
yakkety/yakkety/amd64/a/apport/20170512_193229_92825@/log.gz

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

Title:
  adt tests fail on zesty for apport

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Invalid
Status in apport source package in Yakkety:
  Fix Committed
Status in apport source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Apport autopkgtests are failing with GPG errors e.g.:
  SystemError: W:GPG error: http://archive.ubuntu.com/ubuntu trusty Release: 
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32, E:The 
repository 'http://archive.ubuntu.com/ubuntu trusty Release' is not signed.

  [Test Case]
  Run the autopkgtests and observe failures regarding GPG.
  With the test fixed there should be no failures.

  [Regression Potential]
  While not a regression its possible fixing these tests will reveal other 
failures.

  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz

  fails.

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

-- 
Mailing list: https://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 1649709] Re: unatttended-upgrades 0.92ubuntu3 installs all updates but update-manager is set to only install security automatically

** Changed in: unattended-upgrades (Ubuntu)
Milestone: ubuntu-17.01 => ubuntu-17.05

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

Title:
  unatttended-upgrades 0.92ubuntu3 installs all updates but update-
  manager is set to only install security automatically

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I opened my Zesty virtual machine in VirtualBox to manually install
  updates.

  I was surprised to see that unattended-upgrades was running and
  installed all the updates for me.

  update-manager is set to the default settings:
  - Download and install security updates automatically
  - Display other updates weekly

  I assume this is a regression caused by the fix for bug 1624641.

  Allowed origins are: ['o=Ubuntu,a=zesty', 'o=Ubuntu,a=zesty-security']

  And obviously zesty-security isn't open yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unattended-upgrades 0.93.1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec 13 17:26:22 2016
  InstallationDate: Installed on 2016-10-27 (47 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161027)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1690353] Re: package openssh-server 1:7.3p1-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it
helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

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

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

Title:
  package openssh-server 1:7.3p1-1ubuntu0.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Setting up openssh-server (1:7.3p1-1ubuntu0.1) ...
  Job for ssh.service failed because the control process exited with error code.
  See "systemctl status ssh.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript ssh, action "restart" failed.
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Fri 2017-05-12 12:05:21 BST; 7ms 
ago
Process: 21819 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 21819 (code=exited, status=255)

  May 12 12:05:21 chris-XPS-13-9343 systemd[1]: Starting OpenBSD Secure Shell 

  May 12 12:05:21 chris-XPS-13-9343 sshd[21819]: /etc/ssh/sshd_config line 
92:...n
  May 12 12:05:21 chris-XPS-13-9343 systemd[1]: ssh.service: Main process 
exit...a
  May 12 12:05:21 chris-XPS-13-9343 systemd[1]: Failed to start OpenBSD 
Secure
  May 12 12:05:21 chris-XPS-13-9343 systemd[1]: ssh.service: Unit entered 
fail
  May 12 12:05:21 chris-XPS-13-9343 systemd[1]: ssh.service: Failed with 
resul
  Hint: Some lines were ellipsized, use -l to show in full.
  dpkg: error processing package openssh-server (--configure):
   subprocess installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: openssh-server 1:7.3p1-1ubuntu0.1
  Uname: Linux 4.7.6-040706-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Fri May 12 11:25:50 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-07-16 (665 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: /etc/ssh/sshd_config line 92: bad port number in PermitOpen
  SourcePackage: openssh
  Title: package openssh-server 1:7.3p1-1ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2017-01-24 (107 days ago)

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

-- 
Mailing list: https://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 1628956] Re: From v49.0, Firefox needs read access to @{PROC}/net/arp

2017-05-15 Thread Vincas Dargis

I've tried patched version from 1659988, it works fine.

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

Title:
  From v49.0, Firefox needs read access to @{PROC}/net/arp

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Since the latest upgrade of Firefox to 49.0, it will need read access
  to @{PROC}/net/arp

  I don't know what the security implications are, so I don't know if we
  want to give read access to explicitely deny it. Both seem to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor-profiles 2.10.95-0ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 29 16:55:21 2016
  InstallationDate: Installed on 2015-10-04 (361 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  PackageArchitecture: all
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet 
splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   Sep 29 10:37:52 franck-ThinkPad-T430s dbus[2546]: [system] AppArmor D-Bus 
mediation is enabled
   Sep 29 16:50:57 franck-ThinkPad-T430s dbus[2410]: [system] AppArmor D-Bus 
mediation is enabled
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apparmor.d.sbin.klogd: [modified]
  modified.conffile..etc.apparmor.d.sbin.syslogd: [modified]
  modified.conffile..etc.apparmor.d.usr.bin.chromium-browser: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.dovecot: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.identd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.mdnsd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.nmbd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.nscd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.smbd: [modified]
  mtime.conffile..etc.apparmor.d.sbin.klogd: 2015-10-05T12:04:03.854535
  mtime.conffile..etc.apparmor.d.sbin.syslogd: 2015-10-05T12:03:15.705968
  mtime.conffile..etc.apparmor.d.usr.bin.chromium-browser: 
2015-10-05T12:02:05.273141
  mtime.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: 
2016-04-13T19:13:25.829679
  mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2016-04-13T19:13:05.941424
  mtime.conffile..etc.apparmor.d.usr.sbin.dovecot: 2015-10-05T12:00:55.356323
  mtime.conffile..etc.apparmor.d.usr.sbin.identd: 2015-10-05T12:01:02.204403
  mtime.conffile..etc.apparmor.d.usr.sbin.mdnsd: 2015-10-05T12:02:37.861523
  mtime.conffile..etc.apparmor.d.usr.sbin.nmbd: 2015-10-05T12:00:10.119794
  mtime.conffile..etc.apparmor.d.usr.sbin.nscd: 2016-04-13T19:14:17.520643
  mtime.conffile..etc.apparmor.d.usr.sbin.smbd: 2015-10-05T12:00:26.103981

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

-- 
Mailing list: https://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 1690353] Re: package openssh-server 1:7.3p1-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

>From the log:
SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config line 92: bad port number in PermitOpen

On upgrades services need to be restarted and the config for sshd seems
to have a problem in its config. Please see [1] for that config.

[1]: http://manpages.ubuntu.com/manpages/zesty/man5/sshd_config.5.html

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

Title:
  package openssh-server 1:7.3p1-1ubuntu0.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Setting up openssh-server (1:7.3p1-1ubuntu0.1) ...
  Job for ssh.service failed because the control process exited with error code.
  See "systemctl status ssh.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript ssh, action "restart" failed.
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Fri 2017-05-12 12:05:21 BST; 7ms 
ago
Process: 21819 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 21819 (code=exited, status=255)

  May 12 12:05:21 chris-XPS-13-9343 systemd[1]: Starting OpenBSD Secure Shell 

  May 12 12:05:21 chris-XPS-13-9343 sshd[21819]: /etc/ssh/sshd_config line 
92:...n
  May 12 12:05:21 chris-XPS-13-9343 systemd[1]: ssh.service: Main process 
exit...a
  May 12 12:05:21 chris-XPS-13-9343 systemd[1]: Failed to start OpenBSD 
Secure
  May 12 12:05:21 chris-XPS-13-9343 systemd[1]: ssh.service: Unit entered 
fail
  May 12 12:05:21 chris-XPS-13-9343 systemd[1]: ssh.service: Failed with 
resul
  Hint: Some lines were ellipsized, use -l to show in full.
  dpkg: error processing package openssh-server (--configure):
   subprocess installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: openssh-server 1:7.3p1-1ubuntu0.1
  Uname: Linux 4.7.6-040706-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Fri May 12 11:25:50 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-07-16 (665 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: /etc/ssh/sshd_config line 92: bad port number in PermitOpen
  SourcePackage: openssh
  Title: package openssh-server 1:7.3p1-1ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2017-01-24 (107 days ago)

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

-- 
Mailing list: https://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 1690860] [NEW] systemd-resolved does not use DNS servers from DHCP

2017-05-15 Thread KiberGus

Public bug reported:

Hi. I use Ubuntu 17.04 and I have systemd=232-21ubuntu3 installed. The
problem is that it always uses 8.8.8.8 as DNS server. This is very
disappointing because my mobile operator seems to block the server. And
google knows nothing about my home dns zone, so I can't access my NAS by
dns name. Here is a fragment from my /var/log/syslog upon connecting to
network. I've switched systemd log level to debug. I see that dhcp4
receives correct DNS server (it works), but then systemd just ignores it
and uses 8.8.8.8.

May 15 19:09:29 kibergus wpa_supplicant[1151]: wlp1s0: Reject scan trigger 
since one is already pending
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.5375] device 
(wlp1s0): supplicant interface state: ready -> inactive
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.5432] 
policy: auto-activating connection 'AndroidGus'
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.5443] device 
(wlp1s0): Activation: starting connection 'AndroidGus' 
(ec68d7b6-b77e-4604-8981-40b56f017413)
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.5473] device 
(wlp1s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
May 15 19:09:29 kibergus dhclient[24139]: receive_packet failed on wlp1s0: 
Network is down
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.6530] device 
(wlp1s0): set-hw-addr: set-cloned MAC address to E4:A4:71:3C:4A:97 (permanent)
May 15 19:09:29 kibergus kernel: [362356.079223] IPv6: ADDRCONF(NETDEV_UP): 
wlp1s0: link is not ready
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.6703] device 
(wlp1s0): state change: prepare -> config (reason 'none') [40 50 0]
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.6718] device 
(wlp1s0): Activation: (wifi) access point 'AndroidGus' has security, but 
secrets are required.
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.6718] device 
(wlp1s0): state change: config -> need-auth (reason 'none') [50 60 0]
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.6909] device 
(wlp1s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.6912] device 
(wlp1s0): state change: prepare -> config (reason 'none') [40 50 0]
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.6914] device 
(wlp1s0): Activation: (wifi) connection 'AndroidGus' has security, and secrets 
exist.  No new secrets needed.
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.6915] 
Config: added 'ssid' value 'AndroidGus'
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.6915] 
Config: added 'scan_ssid' value '1'
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.6915] 
Config: added 'key_mgmt' value 'WPA-PSK'
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.6915] 
Config: added 'psk' value ''
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.7060] device 
(wlp1s0): supplicant interface state: inactive -> disconnected
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.7068] 
sup-iface[0x55afd03050c0,wlp1s0]: config: set interface ap_scan to 1
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.7073] device 
(wlp1s0): supplicant interface state: disconnected -> inactive
May 15 19:09:29 kibergus wpa_supplicant[1151]: wlp1s0: SME: Trying to 
authenticate with d0:22:be:d3:7a:14 (SSID='AndroidGus' freq=2437 MHz)
May 15 19:09:29 kibergus kernel: [362356.140572] wlp1s0: authenticate with 
d0:22:be:d3:7a:14
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.7260] device 
(wlp1s0): supplicant interface state: inactive -> authenticating
May 15 19:09:29 kibergus kernel: [362356.147771] wlp1s0: send auth to 
d0:22:be:d3:7a:14 (try 1/3)
May 15 19:09:29 kibergus wpa_supplicant[1151]: wlp1s0: Trying to associate with 
d0:22:be:d3:7a:14 (SSID='AndroidGus' freq=2437 MHz)
May 15 19:09:29 kibergus kernel: [362356.155765] wlp1s0: authenticated
May 15 19:09:29 kibergus kernel: [362356.156847] wlp1s0: associate with 
d0:22:be:d3:7a:14 (try 1/3)
May 15 19:09:29 kibergus kernel: [362356.160692] wlp1s0: RX AssocResp from 
d0:22:be:d3:7a:14 (capab=0x411 status=0 aid=1)
May 15 19:09:29 kibergus NetworkManager[6932]:   [1494864569.7394] device 
(wlp1s0): supplicant interface state: authenticating -> associating
May 15 19:09:29 kibergus wpa_supplicant[1151]: wlp1s0: Associated with 
d0:22:be:d3:7a:14
May 15 19:09:29 kibergus kernel: [362356.162094] wlp1s0: associated
May 15 19:09:29 kibergus kernel: [362356.162143] IPv6: ADDRCONF(NETDEV_CHANGE): 
wlp1s0: link becomes ready
May 15 19:09:29 kibergus systemd-resolved[25104]: Got message type=method_call 
sender=:1.83262 destination=org.freedesktop.resolve1 
object=/org/freedesktop/resolve1 interface=org.freedesktop.resolve1.Manager 
member=ResolveHostname cookie=2 reply_cookie=0 error=n/a
May 15 19:09:29 kibergus systemd-resolved[25104]: Looking up RR for 
daisy.ubuntu.com IN A.
May

[Touch-packages] [Bug 1690861] [NEW] descripiton in README

2017-05-15 Thread Christopher Yeleighton

Public bug reported:

Line 19 of /usr/share/doc/patch/README contains "descripiton".

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: patch 2.7.1-4ubuntu2.3
Uname: Linux 3.4.0+ x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Mon May 15 18:40:47 2017
Dependencies:
 gcc-4.9-base 4.9.3-0ubuntu4
 libc6 2.19-0ubuntu6.11
 libgcc1 1:4.9.3-0ubuntu4
 multiarch-support 2.19-0ubuntu6.11
ProcEnviron: Error: [Errno 2] No such file or directory: '/proc/62/environ'
SourcePackage: patch
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  descripiton in README

Status in patch package in Ubuntu:
  New

Bug description:
  Line 19 of /usr/share/doc/patch/README contains "descripiton".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: patch 2.7.1-4ubuntu2.3
  Uname: Linux 3.4.0+ x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Mon May 15 18:40:47 2017
  Dependencies:
   gcc-4.9-base 4.9.3-0ubuntu4
   libc6 2.19-0ubuntu6.11
   libgcc1 1:4.9.3-0ubuntu4
   multiarch-support 2.19-0ubuntu6.11
  ProcEnviron: Error: [Errno 2] No such file or directory: '/proc/62/environ'
  SourcePackage: patch
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1645308] Re: [SRU] Backport zeromq3 4.2.0 to yakkety

2017-05-15 Thread Łukasz Zemczak

Roughly tested zeromq3 4.2.0-2ubuntu0.16.10 on a yakkety VM and played
around with python-zmq/python3-zmq bindings - seemed to work fine.
Couldn't really find any other easy way to get this tested, but that's
basically the same testing that has been done earlier. Also, seeing that
4.2.0 was in zesty for quite a while now I consider this tested.

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

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

Title:
  [SRU] Backport zeromq3 4.2.0 to yakkety

Status in zeromq3 package in Ubuntu:
  Fix Released
Status in zeromq3 source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  As per product requirement, we have released a git-snapshot based pre-
  release version of zeromq3 4.2.0 to yakkety
  (4.1.5+git20160811+2fc86bc) as the upstream version was not yet
  available. The agreement was that we will release the snapshot-based
  version only if, once the official update is available we will update
  and switch.

  The rationale for this would be that the snapshot-based version is
  anyway more-or-less feature compatible with the official version. It's
  also not wise to keep shipping a snapshot for long as some bugfixes
  might be missing from the cherry-pick. The generated binaries are
  binary-compatible, with only a few new symbols exported in the main
  4.2.0 version.

  [Test Case]

  No particular test-case - installing the new version and making sure
  that existing reverse-dependencies still work as intended.

  [Regression Potential]

  There is, of course, some regression potential, but as already
  mentioned: there weren't too many commits since the git snapshot that
  our previous version was based off.

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

-- 
Mailing list: https://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 1689356] Re: UI scale being reset to 1 everytime when display sleeps for a while

2017-05-15 Thread Timo Aaltonen

** Package changed: xorg (Ubuntu) => unity-settings-daemon (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/1689356

Title:
  UI scale being reset to 1 everytime when display sleeps for a while

Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.04,
  the HiDPI setting(Scale for menu and title bars)
  is being reset to 1 everytime when display sleeps for a while,
  making everything looks small.

  If the display sleeps and I resume it instantly, it's fine,
  but if the display slept for long, the HiDPI setting gets reset to 1.

  My guess is that if a display is plugged in(detected), the old DPI
  setting is not restored.

  This issue is not present on previous Ubuntu versions
  and the same issue persists even after a fresh install.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  Uname: Linux 4.10.14-zen+ x86_64
  NonfreeKernelModules: 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  375.66  Mon May  1 15:29:16 
PDT 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  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:Unity7
  Date: Tue May  9 02:08:25 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 375.66, 4.10.14-zen+, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1080] [1043:85aa]
   Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] 
[1002:6658] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Bonaire XTX [Radeon R7 260X/360] 
[1458:227b]
  InstallationDate: Installed on 2017-05-06 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.14-zen+ 
root=UUID=e1130f0b-d82f-4976-989f-c8b18f0965eb ro intel_iommu=on 
vfio_iommu_type1.allow_unsafe_interrupts=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd08/18/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  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.14-0ubuntu1
  xserver.bootTime: Tue May  9 00:26:57 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1689356/+subscriptions

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

[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-05-15 Thread Eric Desrochers

The same precision verification testing has been tested for zesty-
proposed with the same result as X and Y :

[Verificaton zesty]

# i386
- Significant performance increase using the zesty-proposed/i386 package inside 
a 32-bit LXD container build using a Ryzen CPU with Intel SHA Extension 
capability.
- Same performance (as expected) using the zesty-proposed/i386 package on a non 
SHA Extension Intel CPU (i7-6770HQ) with zesty-proposed package.

# amd64
- Significant performance increase using the zesty-proposed/amd64 package on 
Ryzen CPU with Intel SHA Extension capability.
- Same performance (as expected) using the zesty-proposed/amd64 package on a 
non SHA Extension Intel CPU (i7-6770HQ) with zesty-proposed package.

Note : I unfortunately don't (nor colleagues) have access to a Intel CPU with 
SHA Extension capability at our disposal. Ideally, if someone has access to one 
to test it would be good.
Otherwise, I think it is safe to rely on upstream author of the patch who 
confirmed it was working as expected using a Intel CPU with SHA extension 
capability.

Reference : https://github.com/openssl/openssl/issues/2848
"...Myself I tested on Intel processors, yes, with/without"


Additionally, we also had some feedbacks from 
Justin Erenkrantz, a affected users using a Ryzen/Naple CPU.

Please look comment #18 to see Justin feedback:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/comments/18

** Tags removed: sts-sru
** Tags added: sts-sru-done

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

Title:
  OpenSSL CPU detection for AMD Ryzen CPUs

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Fix Committed
Status in openssl source package in Yakkety:
  Fix Committed
Status in openssl source package in Zesty:
  Fix Committed
Status in openssl source package in Artful:
  Fix Released

Bug description:
  [Impact]

  * Context:

  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in
  64bit only (Confirmed with AMD representative). Current OpenSSL
  version in Ryzens still calls SHA for SSSE3 routine as result a number
  of extensions were effectively masked on Ryzen and shows no
  improvement.

  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family : 23
  model : 1
  model name : AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni 
pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold

  [2] - sha_ni: SHA1/SHA256 Instruction Extensions

  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...

  * Program to performs the CPUID check:

  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions

  ... Availability of the Intel® SHA Extensions on a particular
  processor can be determined by checking the SHA CPUID bit in
  CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function,
  using inline assembly, performs the CPUID check:

  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;

     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;

     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );

     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --

  On CPU with sha_ni the program return "1". Otherwise it return "0".

  [Test Case]

   * Reproducible with Xenial/Zesty/Artful release.

   * Generated a checksum of a big file (e.g. 5GB file) with openssl
   $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
  SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8

  real  0m12.835s
  user  0m12.344s
  sys   0m0.484s

  * Openssl speed
  $ openssl speed sha1
  Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
  Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
  Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
  Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s
  Doing sha1 for 3s on 8192 size blocks: 347842 sha1's

[Touch-packages] [Bug 1690822] Re: GPU device in lxc profile ignored?

2017-05-15 Thread Christian Brauner

I couldn't reproduce this behavior locally.
- We'd need the logs for the daemon and the corresponding containers in 
question from /var/log/lxd/*, please.
- Please also show

cat /proc/1/mountinfo

from inside one of those containers that doesn't mount the gpu device.

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

Title:
  GPU device in lxc profile ignored?

Status in lxc package in Ubuntu:
  New

Bug description:
  I am trying to add the gpu device in an profile so that new containers
  come up with gpu available.

  Even though the gpu device is in the profile it seems it is ignored.
  In this pastebin http://pastebin.ubuntu.com/24579662/ you can see the
  profile with the gpu device. We add a new container (juju add-unit)
  and we check if the device is there. It is not, so we add it (lxc
  config device add) after the container comes up.

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

-- 
Mailing list: https://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 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-05-15 Thread Eric Desrochers

[Verificaton XENIAL]

# i386
- Significant performance increase using the xenial-proposed/i386 package 
inside a 32-bit LXD container build using a Ryzen CPU with Intel SHA Extension 
capability.
- Same performance (as expected) using the xenial-proposed/i386 package on a 
non SHA Extension Intel CPU (i7-6770HQ) with xenial-proposed package.

# amd64
- Significant performance increase using the xenial-proposed/amd64 package on 
Ryzen CPU with Intel SHA Extension capability.
- Same performance (as expected) using the xenial-proposed/amd64 package on a 
non SHA Extension Intel CPU (i7-6770HQ) with xenial-proposed package.

Note : I unfortunately don't (nor colleagues) have access to a Intel CPU with 
SHA Extension capability at our disposal. Ideally, if someone has access to one 
to test it would be good. 
Otherwise, I think it is safe to rely on upstream author of the patch who 
confirmed it was working as expected using a Intel CPU with SHA extension 
capability. 

Reference : https://github.com/openssl/openssl/issues/2848
"...Myself I tested on Intel processors, yes, with/without"

==
* Test xenial/i386 on a 32-bit LXD container using a non SHA Extension Intel 
CPU:
--
ii  libssl1.0.0:i386  1.0.2g-1ubuntu4.6  i386   
  Secure Sockets Layer toolkit - shared libraries
ii  openssl   1.0.2g-1ubuntu4.6  i386   
  Secure Sockets Layer toolkit - cryptographic utility

# openssl speed sha1
Doing sha1 for 3s on 16 size blocks: 12391058 sha1's in 3.00s
Doing sha1 for 3s on 64 size blocks: 8934411 sha1's in 3.00s
Doing sha1 for 3s on 256 size blocks: 5048901 sha1's in 3.00s
Doing sha1 for 3s on 1024 size blocks: 1893157 sha1's in 3.00s
Doing sha1 for 3s on 8192 size blocks: 301374 sha1's in 3.00s
OpenSSL 1.0.2g  1 Mar 2016
built on: reproducible build, date unspecified
options:bn(64,32) rc4(8x,mmx) des(ptr,risc1,16,long) aes(partial) blowfish(idx) 
compiler: cc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS 
-D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wa,--noexecstack 
-Wall -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM 
-DRMD160_ASM -DAES_ASM -DVPAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes256 bytes   1024 bytes   8192 bytes
sha1 66085.64k   190600.77k   430839.55k   646197.59k   822951.94k

# time openssl dgst -sha256 /var/tmp/5Gfile 
SHA256(/var/tmp/5Gfile)= 
7f06c62352aebd8125b2a1841e2b9e1ffcbed602f381c3dcb3200200e383d1d5

real0m15.518s
user0m14.428s
sys 0m1.084s
==
* Test xenial-proposed/i386 on a 32-bit LXD container using a non SHA Extension 
Intel CPU:
--
ii  libssl1.0.0:i386  1.0.2g-1ubuntu4.7  i386   
  Secure Sockets Layer toolkit - shared libraries
ii  openssl   1.0.2g-1ubuntu4.7  i386   
  Secure Sockets Layer toolkit - cryptographic utility

# openssl speed sha1
Doing sha1 for 3s on 16 size blocks: 12451389 sha1's in 3.00s
Doing sha1 for 3s on 64 size blocks: 8913173 sha1's in 3.00s
Doing sha1 for 3s on 256 size blocks: 5037978 sha1's in 3.00s
Doing sha1 for 3s on 1024 size blocks: 1904530 sha1's in 3.00s
Doing sha1 for 3s on 8192 size blocks: 303177 sha1's in 3.00s
OpenSSL 1.0.2g  1 Mar 2016
built on: reproducible build, date unspecified
options:bn(64,32) rc4(8x,mmx) des(ptr,risc1,16,long) aes(partial) blowfish(idx) 
compiler: cc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS 
-D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wa,--noexecstack 
-Wall -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM 
-DRMD160_ASM -DAES_ASM -DVPAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes256 bytes   1024 bytes   8192 bytes
sha1 66407.41k   190147.69k   429907.46k   650079.57k   827875.33k

# time openssl dgst -sha256 /var/tmp/5Gfile 
SHA256(/var/tmp/5Gfile)= 
7f06c62352aebd8125b2a1841e2b9e1ffcbed602f381c3dcb3200200e383d1d5

real0m15.259s
user0m14.372s
sys 0m0.884s
==
* Test xenial/i386 on a 32-bit LXD container using a Ryzen CPU:
--
ii  libssl1.0.0:i386 1.0.2g-1ubuntu4.6  
i386 Secure Sockets Layer toolkit - shared libraries
ii  openssl  1.0.2g-1ubuntu4.6  
i386 Secure Sockets Layer toolkit - cryptographic utility

# openssl speed sha1
Doing

[Touch-packages] [Bug 1690820] Re: killing su does not kill subprocess (SIGTERM not propagated)

2017-05-15 Thread Serge Hallyn

Thanks for filing, Radu.

The commit which fixed it is in this PR:

https://github.com/shadow-maint/shadow/pull/72

(wget https://github.com/shadow-maint/shadow/pull/72.patch)

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

Title:
  killing su does not kill subprocess (SIGTERM not propagated)

Status in shadow package in Ubuntu:
  New

Bug description:
  Problem first appeared in login_4.1.5.1-1ubuntu9.4 and version
  login_4.1.5.1-1ubuntu9.2 was not affected.


  
  Example where the subprocess 115576 has not been terminated:
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 
'sleep '&
  [1] 115575
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# kill $!
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src#  ...waiting for child to 
terminate.
  pgrep sleep
  115576
  [1]+  Exit 255./su test -c 'sleep '
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pgrep sleep
  115576

  Expected behavior:
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 
'sleep ' &
  [1] 115503
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# kill $!
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src#
  Session terminated, terminating shell... ...terminated.
   ...terminated.

  [1]+  Exit 143./su test -c 'sleep '
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pgrep sleep

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

-- 
Mailing list: https://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 1690836] Re: libnl-genl-3.0 memory leak

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

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

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

Title:
  libnl-genl-3.0 memory leak

Status in libnl3 package in Ubuntu:
  Confirmed

Bug description:
  It seems that there is a memory leak in the libnl-genl-3.0 library.
  The memory-leak can be seen when the function genl_ctrl_resolve() fails.

  It seems that this function copy a buffer and forget to deallocate it 
properly:
    258 cb = nl_cb_clone(orig); // buffer copied not freed

  -
  The following attached source-code can help you to reproduce this behavior on 
Ubuntu 14.04.
  It forces an issue on the genl_ctrl_resolve by asking an unknown 
netlink-family.

  To compile program:
  g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 
libnl-genl-3.0) -o main

  To detect memory-leak using Valgrind:
  valgrind --leak-check=full ./main

  -
  Executing it on Debian 8.0 shows "no memory leak":
  sylvain@debian:~/test$ lsb_release -rd
  Description:  Debian GNU/Linux 8.8 (jessie)
  Release:  8.8

  sylvain@debian:~/test$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs 
libnl-3.0 libnl-genl-3.0) -o main
  sylvain@debian:~/test$ valgrind --leak-check=full ./main
  ==26390== Memcheck, a memory error detector
  ==26390== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
  ==26390== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
  ==26390== Command: ./main
  ==26390==
  start test
  error: can't retrieve the netlink-family id
  end test
  ==26390==
  ==26390== HEAP SUMMARY:
  ==26390== in use at exit: 0 bytes in 0 blocks
  ==26390==   total heap usage: 13 allocs, 13 frees, 22,142 bytes allocated
  ==26390==
  ==26390== All heap blocks were freed -- no leaks are possible
  ==26390==
  ==26390== For counts of detected and suppressed errors, rerun with: -v
  ==26390== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

  -
  Executing it on Ubuntu 14.04 shows a memory leak:
  ubuntu@ubuntu:~$ lsb_release -rd
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04

  ubuntu@ubuntu:~$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs 
libnl-3.0 libnl-genl-3.0) -o main
  ubuntu@ubuntu:~$ valgrind --leak-check=full ./main
  ==37377== Memcheck, a memory error detector
  ==37377== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
  ==37377== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
  ==37377== Command: ./main
  ==37377==
  start test
  error: can't retrieve the netlink-family id
  end test
  ==37377==
  ==37377== HEAP SUMMARY:
  ==37377== in use at exit: 224 bytes in 1 blocks
  ==37377==   total heap usage: 13 allocs, 12 frees, 22,142 bytes allocated
  ==37377==
  ==37377== 224 bytes in 1 blocks are definitely lost in loss record 1 of 1
  ==37377==at 0x4C2CC70: calloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==37377==by 0x5048FAA: nl_cb_alloc (in 
/lib/x86_64-linux-gnu/libnl-3.so.200.16.1)
  ==37377==by 0x504CB1E: nl_socket_alloc (in 
/lib/x86_64-linux-gnu/libnl-3.so.200.16.1)
  ==37377==by 0x4012E3: A::Init() (in /home/ubuntu/main)
  ==37377==by 0x401189: main (in /home/ubuntu/main)
  ==37377==
  ==37377== LEAK SUMMARY:
  ==37377==definitely lost: 224 bytes in 1 blocks
  ==37377==indirectly lost: 0 bytes in 0 blocks
  ==37377==  possibly lost: 0 bytes in 0 blocks
  ==37377==still reachable: 0 bytes in 0 blocks
  ==37377== suppressed: 0 bytes in 0 blocks
  ==37377==
  ==37377== For counts of detected and suppressed errors, rerun with: -v
  ==37377== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

  Thanks,
  Sylvain Trinquet

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

-- 
Mailing list: https://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 1690820] Re: killing su does not kill subprocess (SIGTERM not propagated)

2017-05-15 Thread Marc Deslauriers

** Information type changed from Public to Public Security

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

Title:
  killing su does not kill subprocess (SIGTERM not propagated)

Status in shadow package in Ubuntu:
  New

Bug description:
  Problem first appeared in login_4.1.5.1-1ubuntu9.4 and version
  login_4.1.5.1-1ubuntu9.2 was not affected.


  
  Example where the subprocess 115576 has not been terminated:
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 
'sleep '&
  [1] 115575
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# kill $!
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src#  ...waiting for child to 
terminate.
  pgrep sleep
  115576
  [1]+  Exit 255./su test -c 'sleep '
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pgrep sleep
  115576

  Expected behavior:
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 
'sleep ' &
  [1] 115503
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# kill $!
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src#
  Session terminated, terminating shell... ...terminated.
   ...terminated.

  [1]+  Exit 143./su test -c 'sleep '
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pgrep sleep

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

-- 
Mailing list: https://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 1690836] [NEW] libnl-genl-3.0 memory leak

2017-05-15 Thread Sylvain Trinquet

Public bug reported:

It seems that there is a memory leak in the libnl-genl-3.0 library.
The memory-leak can be seen when the function genl_ctrl_resolve() fails.

It seems that this function copy a buffer and forget to deallocate it properly:
  258 cb = nl_cb_clone(orig); // buffer copied not freed

-
The following attached source-code can help you to reproduce this behavior on 
Ubuntu 14.04.
It forces an issue on the genl_ctrl_resolve by asking an unknown netlink-family.

To compile program:
g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) 
-o main

To detect memory-leak using Valgrind:
valgrind --leak-check=full ./main

-
Executing it on Debian 8.0 shows "no memory leak":
sylvain@debian:~/test$ lsb_release -rd
Description:Debian GNU/Linux 8.8 (jessie)
Release:8.8

sylvain@debian:~/test$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs 
libnl-3.0 libnl-genl-3.0) -o main
sylvain@debian:~/test$ valgrind --leak-check=full ./main
==26390== Memcheck, a memory error detector
==26390== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==26390== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==26390== Command: ./main
==26390==
start test
error: can't retrieve the netlink-family id
end test
==26390==
==26390== HEAP SUMMARY:
==26390== in use at exit: 0 bytes in 0 blocks
==26390==   total heap usage: 13 allocs, 13 frees, 22,142 bytes allocated
==26390==
==26390== All heap blocks were freed -- no leaks are possible
==26390==
==26390== For counts of detected and suppressed errors, rerun with: -v
==26390== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

-
Executing it on Ubuntu 14.04 shows a memory leak:
ubuntu@ubuntu:~$ lsb_release -rd
Description:Ubuntu 14.04.5 LTS
Release:14.04

ubuntu@ubuntu:~$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 
libnl-genl-3.0) -o main
ubuntu@ubuntu:~$ valgrind --leak-check=full ./main
==37377== Memcheck, a memory error detector
==37377== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==37377== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==37377== Command: ./main
==37377==
start test
error: can't retrieve the netlink-family id
end test
==37377==
==37377== HEAP SUMMARY:
==37377== in use at exit: 224 bytes in 1 blocks
==37377==   total heap usage: 13 allocs, 12 frees, 22,142 bytes allocated
==37377==
==37377== 224 bytes in 1 blocks are definitely lost in loss record 1 of 1
==37377==at 0x4C2CC70: calloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==37377==by 0x5048FAA: nl_cb_alloc (in 
/lib/x86_64-linux-gnu/libnl-3.so.200.16.1)
==37377==by 0x504CB1E: nl_socket_alloc (in 
/lib/x86_64-linux-gnu/libnl-3.so.200.16.1)
==37377==by 0x4012E3: A::Init() (in /home/ubuntu/main)
==37377==by 0x401189: main (in /home/ubuntu/main)
==37377==
==37377== LEAK SUMMARY:
==37377==definitely lost: 224 bytes in 1 blocks
==37377==indirectly lost: 0 bytes in 0 blocks
==37377==  possibly lost: 0 bytes in 0 blocks
==37377==still reachable: 0 bytes in 0 blocks
==37377== suppressed: 0 bytes in 0 blocks
==37377==
==37377== For counts of detected and suppressed errors, rerun with: -v
==37377== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

Thanks,
Sylvain Trinquet

** Affects: libnl3 (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: leak libnl memory

** Attachment added: "trigger the memory leak"
   https://bugs.launchpad.net/bugs/1690836/+attachment/4876902/+files/main.cpp

** Description changed:

  It seems that there is a memory leak in the libnl-genl-3.0 library.
  The memory-leak can be seen when the function genl_ctrl_resolve() fails.
  
  It seems that this function copy a buffer and forget to deallocate it 
properly:
-   258 cb = nl_cb_clone(orig); // buffer copied not freed
+   258 cb = nl_cb_clone(orig); // buffer copied not freed
  
- 

+ -
  The following attached source-code can help you to reproduce this behavior on 
Ubuntu 14.04.
  It forces an issue on the genl_ctrl_resolve by asking an unknown 
netlink-family.
  
  To compile program:
  g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 
libnl-genl-3.0) -o main
  
  To detect memory-leak using Valgrind:
  valgrind --leak-check=full ./main
  
- 

+ -
  Executing it on Debian 8.0 shows "no memory

[Touch-packages] [Bug 1091647] Re: Smart completion does not work for localc and CSV and TSV files

2017-05-15 Thread Pander

** Tags removed: yakkety
** Tags added: artful zesty

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

Title:
  Smart completion does not work for localc and CSV and TSV files

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  (Not really sure if this is related to bash)

  Smart completion does not work for localc and CSV (.csv comma
  separated values) and TSV (.tsv tab separated values) files on the
  command line in bash. Please support this.

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

-- 
Mailing list: https://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 1690820] Re: killing su does not kill subprocess (SIGTERM not propagated)

2017-05-15 Thread Radu Duta

** Description changed:

+ Problem first appeared in login_4.1.5.1-1ubuntu9.4 and version
+ login_4.1.5.1-1ubuntu9.2 was not affected.
+ 
+ 
  
  Example where the subprocess 115576 has not been terminated:
- root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 
'sleep '&   

 
+ root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 
'sleep '&
  [1] 115575
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# kill $!
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src#  ...waiting for child to 
terminate.
  pgrep sleep
  115576
  [1]+  Exit 255./su test -c 'sleep '
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pgrep sleep
  115576
  
- 
  Expected behavior:
- root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 
'sleep ' &  

  
+ root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 
'sleep ' &
  [1] 115503
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# kill $!
- root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# 
+ root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src#
  Session terminated, terminating shell... ...terminated.
-  ...terminated.
+  ...terminated.
  
  [1]+  Exit 143./su test -c 'sleep '
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pgrep sleep

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

Title:
  killing su does not kill subprocess (SIGTERM not propagated)

Status in shadow package in Ubuntu:
  New

Bug description:
  Problem first appeared in login_4.1.5.1-1ubuntu9.4 and version
  login_4.1.5.1-1ubuntu9.2 was not affected.


  
  Example where the subprocess 115576 has not been terminated:
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 
'sleep '&
  [1] 115575
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# kill $!
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src#  ...waiting for child to 
terminate.
  pgrep sleep
  115576
  [1]+  Exit 255./su test -c 'sleep '
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pgrep sleep
  115576

  Expected behavior:
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 
'sleep ' &
  [1] 115503
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# kill $!
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src#
  Session terminated, terminating shell... ...terminated.
   ...terminated.

  [1]+  Exit 143./su test -c 'sleep '
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pgrep sleep

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

-- 
Mailing list: https://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 1383470] Re: scp does not work (fails at 'Sending command scp -v -t')

2017-05-15 Thread Serhiy Zahoriya

And it works now. Looks like some network problem that is not handled
properly to warn the user.

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

Title:
  scp does not work (fails at 'Sending command scp -v -t')

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  Following the last update of Ubuntu 14.02, scp (in the default system) has 
ceased working. It hangs after authentication at the point where it wold start 
an interactive session.  I've verified that the problem is in my system: scp 
still works at the target machine and scp won't work on my machine to various 
hosts.  Output below.
  rasmith@rasmith-Lemur-Ultra:~$ scp -v testfil apacentral.org:
  Executing: program /usr/bin/ssh host apacentral.org, user (unspecified), 
command scp -v -t .
  OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
  debug1: Reading configuration data /home/rasmith/.ssh/config
  debug1: /home/rasmith/.ssh/config line 17: Applying options for *
  debug1: /home/rasmith/.ssh/config line 20: Deprecated option 
"rhostsauthentication"
  debug1: /home/rasmith/.ssh/config line 25: Deprecated option "fallbacktorsh"
  debug1: /home/rasmith/.ssh/config line 26: Deprecated option "usersh"
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to apacentral.org [65.19.130.61] port 22.
  debug1: Connection established.
  debug1: could not open key file '/etc/ssh/ssh_host_key': No such file or 
directory
  debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission denied
  debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission 
denied
  debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission denied
  debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such file 
or directory
  debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission denied
  debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission 
denied
  debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission denied
  debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such file 
or directory
  debug1: identity file /home/rasmith/.ssh/identity type 0
  debug1: identity file /home/rasmith/.ssh/identity-cert type -1
  debug1: Remote protocol version 2.0, remote software version 
OpenSSH_6.4_hpn13v11 FreeBSD-2013
  debug1: match: OpenSSH_6.4_hpn13v11 FreeBSD-2013 pat OpenSSH* compat 
0x0400
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: server->client aes128-ctr hmac-md5-...@openssh.com none
  debug1: kex: client->server aes128-ctr hmac-md5-...@openssh.com none
  debug1: sending SSH2_MSG_KEX_ECDH_INIT
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: Server host key: RSA 61:40:9f:26:85:d2:57:34:f9:52:7b:c3:47:9d:7a:ae
  debug1: Host 'apacentral.org' is known and matches the RSA host key.
  debug1: Found key in /home/rasmith/.ssh/known_hosts:26
  debug1: ssh_rsa_verify: signature correct
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: Roaming not allowed by server
  debug1: SSH2_MSG_SERVICE_REQUEST sent
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: publickey,keyboard-interactive
  debug1: Next authentication method: publickey
  debug1: Offering DSA public key: rasm...@aristotle.tamu.edu
  debug1: Server accepts key: pkalg ssh-dss blen 433
  debug1: Authentication succeeded (publickey).
  Authenticated to apacentral.org ([65.19.130.61]:22).
  debug1: channel 0: new [client-session]
  debug1: Requesting no-more-sessi...@openssh.com
  debug1: Entering interactive session.
  debug1: Sending environment.
  debug1: Sending env LANG = en_US.UTF-8
  debug1: Sending command: scp -v -t .

  (at this point, the command hangs more or less indefinitely until
  killed with Ctrl-C)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ssh 1:6.6p1-2ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 15:25:14 2014
  InstallationDate: Installed on 2012-10-18 (732 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  PackageArchitecture: all
  SourcePackage: openssh
  UpgradeStatus: Upgraded to trusty on 2014-05-02 (170 days ago)

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

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

[Touch-packages] [Bug 1689093] Re: modify ubuntu-gnome hook to set UnreportableReason for 14.04 and 16.04

2017-05-15 Thread Jeremy Bicha

I installed apport 2.14.1-0ubuntu3.24 on Ubuntu GNOME 14.04. After
adding the GNOME3 PPA, I got the PPA notice when I ran ubuntu-bug gnome-
system-monitor. I did not get the notice when I ran ubuntu-bug witht an
unrelated package (I tested with ubuntu-bug firefox).

I installed apport 2.20.1-0ubuntu2.6 on Ubuntu GNOME 16.04. With the
GNOME3 Staging PPA, I got the expected PPA notice when I ran ubuntu-bug
nautilus. I also got the notice (slightly different wording) when I ran
ubuntu-bug firefox. This surprised me at first, but it's actually
expected because Firefox depends on gtk3 and gtk3 is one of the updated
packages in the 16.04 GNOME3 Staging PPA. When I tried with an unrelated
package (ubuntu-bug ppa-purge), apport worked fine without showing me
the notice.

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

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

Title:
  modify ubuntu-gnome hook to set UnreportableReason for 14.04 and 16.04

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Committed
Status in apport source package in Xenial:
  Fix Committed

Bug description:
  Impact
  --
  As announced, the GNOME3 PPAs for Ubuntu 16.04 LTS are no longer being 
maintained as of April 2017. Therefore, the Ubuntu GNOME project would like to 
stop receiving bugs from packages installed from those PPAs for that version, 
or for 14.04 LTS which is no longer supported by Ubuntu GNOME.

  See https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3

  Test Case
  -
  sudo add-apt-repository ppa:gnome3-team/gnome3
  sudo apt update
  sudo apt upgrade

  Ubuntu 14.04:
  ubuntu-bug gnome-system-monitor

  Ubuntu 16.04:
  ubuntu-bug nautilus

  What should happen:
  After several moments, you should see a popup with
  The GNOME3 PPA you are using is no longer supported for this Ubuntu release. 
Please run "ppa-purge ppa:gnome3-team/gnome3".

  Clean up:
  sudo apt install ppa-purge
  sudo ppa-purge ppa:gnome3-team/gnome3

  Other Info
  --
  Ubuntu GNOME has always installed ppa-purge by default.

  Regression Potential
  
  People will be unable to report bugs with PPA packages like they used to but 
they'll be told why. The message unfortunately likely won't be translated right 
away, but since it will land in the development release, it should eventually 
be translated for future Ubuntu releases.

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

-- 
Mailing list: https://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 1380702] Re: No keyboards shortcuts in QT apps

2017-05-15 Thread Anatoli

I can also confirm that the latest version fixes the bug on Ubuntu
16.04. Thanks, Dmitry!

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Fix Committed
Status in qtbase-opensource-src source package in Yakkety:
  Confirmed

Bug description:
  Impact
  ==

  This affects all Qt applications on Unity and other desktops which use
  global menu, either via appmenu-qt5 or via native implementation on
  Yakkety.

  Any shortcut is not working if the corresponding action is attached
  only to the menubar (i.e. and not also to the toolbar). It can be
  reproduced with almost any application by removing the toolbar (right-
  clicking on it and deselecting it).

  Test Case
  =

  * Open Qt Assistant;
  * Press Ctrl+T (this action is not on the toolbar).

  Expected: a new tab should be opened. Current result: nothing happens.

  In Yakkety the fix should work both with and without appmenu-qt5.

  Proposed Fix
  

  The proposed fix is a backport of the upstream fix at
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=287f548d4c7cc594.

  Actually just the qshortcut.cpp part would be sufficient, but the
  other parts make sure it plays fine together with https://cgit.kde.org
  /plasma-integration.git/commit/?id=aef74e97e2ed462a.

  Regression Potential
  

  The fix is in Zesty for 1½ months now (in upstream even longer), and
  so far nobody complained. People have verified that the fix works (see
  comment #63).

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions

-- 
Mailing list: https://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 1689585] Re: ntp doesn't unload its apparmor profile on purge

2017-05-15 Thread Jamie Strandboge

"Asking someone to know about that:

  echo -n "" > /sys/kernel/security/apparmor/.remove

Is asking too much IMHO and increases the friction between sysadmins and
Apparmor in general."

Of course. I listed this as something that could be considered for the
openntpd/ntpd case, not for a sysadmin. This is a corner case that
should be coordinated between these packages. In all cases except this
rare corner case, it is totally fine (and correct) to leave the profile
loaded until next reboot and sysadmins don't have to care about this at
all.

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

Title:
  ntp doesn't unload its apparmor profile on purge

Status in apparmor package in Ubuntu:
  Won't Fix
Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1) install ntp
apt install ntp
  2) confirm it has loaded its AA profile
aa-status | grep ntpd
  3) purge ntp
apt purge ntp
  4) the profile is left behind but shouldn't
aa-status | grep ntpd


  Additional info:

  This was found by first install ntp then changing my mind and deciding to go 
with OpenNTPD.
  FYI, just installing openntpd while ntp is still there works because openntpd 
has a kludge
  to unload ntpd's profile but that only works if the ntp package wasn't purged 
before.

   /var/lib/dpkg/info/openntpd.preinst:
   if [ -f /etc/apparmor.d/usr.sbin.ntpd ] && pathfind apparmor_parser ; then
   apparmor_parser -R /etc/apparmor.d/usr.sbin.ntpd
   fi
   
  Since a purge deletes /etc/apparmor.d/usr.sbin.ntpd, openntpd.preinst's 
kludge is ineffective.
  In any case, having implementation B include workaround for implementation A 
not cleaning up
  after itself seems wrong and the issue should be fixed at the source IMHO.

  # lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  # apt-cache policy ntp
  ntp:
Installed: 1:4.2.8p4+dfsg-3ubuntu5.4
Candidate: 1:4.2.8p4+dfsg-3ubuntu5.4
Version table:
   *** 1:4.2.8p4+dfsg-3ubuntu5.4 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:4.2.8p4+dfsg-3ubuntu5.3 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1:4.2.8p4+dfsg-3ubuntu5 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ntp (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue May  9 15:48:42 2017
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1690822] [NEW] GPU device in lxc profile ignored?

2017-05-15 Thread Konstantinos Tsakalozos

Public bug reported:

I am trying to add the gpu device in an profile so that new containers
come up with gpu available.

Even though the gpu device is in the profile it seems it is ignored. In
this pastebin http://pastebin.ubuntu.com/24579662/ you can see the
profile with the gpu device. We add a new container (juju add-unit) and
we check if the device is there. It is not, so we add it (lxc config
device add) after the container comes up.

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

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

Title:
  GPU device in lxc profile ignored?

Status in lxc package in Ubuntu:
  New

Bug description:
  I am trying to add the gpu device in an profile so that new containers
  come up with gpu available.

  Even though the gpu device is in the profile it seems it is ignored.
  In this pastebin http://pastebin.ubuntu.com/24579662/ you can see the
  profile with the gpu device. We add a new container (juju add-unit)
  and we check if the device is there. It is not, so we add it (lxc
  config device add) after the container comes up.

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

-- 
Mailing list: https://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 1690820] [NEW] killing su does not kill subprocess (SIGTERM not propagated)

2017-05-15 Thread Radu Duta

Public bug reported:


Example where the subprocess 115576 has not been terminated:
root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 'sleep 
'&  
  
[1] 115575
root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# kill $!
root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src#  ...waiting for child to 
terminate.
pgrep sleep
115576
[1]+  Exit 255./su test -c 'sleep '
root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pgrep sleep
115576


Expected behavior:
root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 'sleep 
' & 
   
[1] 115503
root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# kill $!
root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# 
Session terminated, terminating shell... ...terminated.
 ...terminated.

[1]+  Exit 143./su test -c 'sleep '
root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pgrep sleep

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

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

Title:
  killing su does not kill subprocess (SIGTERM not propagated)

Status in shadow package in Ubuntu:
  New

Bug description:

  Example where the subprocess 115576 has not been terminated:
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 
'sleep '&   

 
  [1] 115575
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# kill $!
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src#  ...waiting for child to 
terminate.
  pgrep sleep
  115576
  [1]+  Exit 255./su test -c 'sleep '
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pgrep sleep
  115576

  
  Expected behavior:
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pkill sleep; ./su test -c 
'sleep ' &  

  
  [1] 115503
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# kill $!
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# 
  Session terminated, terminating shell... ...terminated.
   ...terminated.

  [1]+  Exit 143./su test -c 'sleep '
  root@ubuntu:~/sudebug/src/shadow-4.1.5.1/src# pgrep sleep

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

-- 
Mailing list: https://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 1688310] Re: KDC/kadmind may fail to start on IPv4-only systems

2017-05-15 Thread LocutusOfBorg

** Tags added: verification-done

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

Title:
  KDC/kadmind may fail to start on IPv4-only systems

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  Fix Committed
Status in krb5 package in Debian:
  Fix Released

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8531
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch: 0011-Fix-KDC-kadmind-startup-on-some-IPv4-only-systems.patch

  [Impact]
  getaddrinfo() called on a wildcard address might return the IPv6 "::1" 
address. On machines without IPv6 support, binding to it will most likely fail 
and the kdc/kadmin services won't start.

  The provided patch is applied upstream and in Debian testing.

  [Test Case]

  Steps to reproduce the problem on zesty:

  a) install krb5-kdc krb5-admin-server
  $ sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, use the IP of this machine for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  $ sudo krb5_newrealm
  use any password of your liking when prompted

  c) confirm the kdc and admin services are running.
  $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
   4275 ?Ss 0:00 /usr/sbin/krb5kdc -P /var/run/krb5-kdc.pid
   4306 ?Ss 0:00 /usr/sbin/kadmind -nofork

  d) create a principal and obtain a ticket to confirm kerberos is working 
properly:
  $ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu
  $ kinit
  Password for ubu...@example.org:
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org

  Valid starting   Expires  Service principal
  05/04/2017 14:20:17  05/05/2017 00:20:17  krbtgt/example@example.org
   renew until 05/05/2017 14:20:13

  e) Confirm the kerberos services are bound to IPv6 local sockets:
  $ sudo netstat -anp|grep -E "^(tcp|udp)6.*(krb5kdc|kadmind)"
  tcp6   0  0 :::88   :::*LISTEN
  1078/krb5kdc
  tcp6   0  0 :::749  :::*LISTEN
  1065/kadmind
  tcp6   0  0 :::464  :::*LISTEN
  1065/kadmind
  udp6   0  0 :::88   :::*  
  1078/krb5kdc
  udp6   0  0 :::464  :::*  
  1065/kadmind
  udp6   0  0 :::750  :::*  
  1078/krb5kdc

  f) configure the system to not support IPv6. There are probably many ways to 
do this, but the one sure way is to reboot it with ipv6.disable=1 in the kernel 
command line:
  e.1) edit /etc/default/grub
  e.2) add "ipv6.disable=1" to GRUB_CMDLINE_LINUX and save
  e.3) run sudo update-grub
  e.4) reboot

  f) Confirm the kdc and admin services are NOT running:
  $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
  $

  g) /var/log/auth.log will contain the reason:
  $ sudo grep -E "(kadmind|krb5kdc).*Failed" /var/log/auth.log
  May  4 14:11:54 22-96 krb5kdc[1087]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:11:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for 
::.464)
  May  4 14:15:36 22-96 krb5kdc[1510]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:16:36 22-96 krb5kdc[1652]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:25:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for 
::.464)
  May  4 14:25:54 22-96 krb5kdc[1079]: Failed setting up a UDP socket (for 
::.750)

  With the updated packages, krb5-kdc and krb5-admin-server will startup
  just fine in the same conditions.

  [Regression Potential]
  We now tolerate a EAFNOSUPPORT error as long as at least one socket was bound 
to correctly. Maybe there could be a scenario when this one bound socket is 
useless, or unexpected: in that case, bailing out because of the EAFNOSUPPORT 
error could be seen as a more robust approach because it's immediately visible, 
instead of silently listening on the useless socket.

  That being said, I believe single stack systems (only IPv4, or only
  IPv6) take an extra configuration effort and most systems are dual
  stack. Zesty certainly is, out of the box.

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

-- 
Mailing list: https://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 1690485] Re: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

There isn't really enough information here for a developer to confirm
this issue is a bug, or to begin working on it, so I am marking this bug
Incomplete for now.

If you can provide exact steps so that a developer can reproduce the
original problem, then please add them to this bug and change the status
back to New.


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

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

Title:
  openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  The 'sshd' process gets 'authentication failure' and refuses to allow
  any login.

  dmesg indicates that the problem is SIGSYS on a call to 'socket'
  (syscall #41, signal #31).

  On a hunch, I decided to test whether the problem is related to
  'seccomp' and changed /etc/ssh/sshd_config from the default

  # UsePrivilegeSeparation sandbox

  to the former standard value

  UsePrivilegeSeparation yes

  and logins started to work again.

  Obviously, I'd like to have the additional protection that sandboxing
  would give me.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: openssh-server 1:7.4p1-10
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri May 12 21:06:20 2017
  InstallationDate: Installed on 2017-04-08 (35 days ago)
  InstallationMedia:
   
  SourcePackage: openssh
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago)

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

-- 
Mailing list: https://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 1688121] Re: KDC/kadmind explicit wildcard listener addresses do not use pktinfo

2017-05-15 Thread LocutusOfBorg

** Tags added: verification-done

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

Title:
  KDC/kadmind explicit wildcard listener addresses do not use pktinfo

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  Fix Committed

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch in artful's krb5: 
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch

  [Impact]

  When the KDC is configured to listen on the wildcard address (0.0.0.0) and 
receives a kinit request via UDP on an aliased interface, the response is sent 
with the wrong source IP and never received by kinit.
  After a short timeout, kinit tries again with TCP, in which case it works. 
But if using PREAUTH (the default), that means this first request will 
correctly fail, with the server demanding PREAUTH, and the client will try 
again with a changed request. The whole dance starts again: first UDP, ignored, 
then TCP, and finally we have a ticket.

  Most clients will just see an increased lag when obtaining tickets. If
  for some reason 88/TCP is blocked on the KDC and clients are expected
  to use UDP at all times, then kinit requests will just fail.

  A workaround is to list the aliased interface's address in kdc_listen
  besides the wildcard (0.0.0.0) address.

  The provided patch is applied upstream and in Debian testing.

  [Test Case]

  On zesty:
  a) install krb5-kdc and krb5-admin-server
  $ sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, select your own IP for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  $ sudo krb5_newrealm
  use any password of your liking when prompted

  b.1) Add "kdc_listen = 0.0.0.0" to the EXAMPLE.ORG [realm] section in 
/etc/krb5kdc/kdc.conf and restart the kerberos services:
  [realms]
  EXAMPLE.ORG = {
  kdc_listen = 0.0.0.0
  (...)
  $ sudo service krb5-kdc restart
  $ sudo service krb5-admin-server restart

  c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and 
with mandatory PREAUTH:
  $ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu

  d) extract the ubuntu principal keytab and time how long it takes to obtain a 
ticket:
  $ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu
  $ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m0.022s
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org

  Valid starting   Expires  Service principal
  05/03/2017 21:22:08  05/04/2017 07:22:08  krbtgt/example@example.org
   renew until 05/04/2017 21:22:08

  e) add another IP to your network interface. For example, this adds 
10.0.5.155 to ens3 (it has 10.0.5.55/24 already in my case):
  $ sudo ip addr add 10.0.5.155/24 dev ens3

  f) Edit the EXAMPLE.ORG realm section in /etc/krb5.conf and configure the kdc 
and admin server's IP to this new IP you just added in step (e):
  [realms]
  EXAMPLE.ORG = {
  kdc = 10.0.5.155
  admin_server = 10.0.5.155

  g) Time again how long it takes to obtain a ticket:
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m2.017s

  Step (g) shows the bug.

  On a more technical level, we can see that the server responds to kinit's UDP 
request using an incorrect source IP, therefore kinit never "sees" it. It 
quickly times out and switches to TCP, where the server responds using the 
correct source IP:
  1 0.010.0.5.55 → 10.0.5.155   KRB5 216 AS-REQ
  2 0.00056668210.0.5.55 → 10.0.5.55KRB5 298 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (2) has the incorrect source ip!

  After roughly 1s, kinit switches to tcp and tries again:
  3 1.00323150710.0.5.55 → 10.0.5.155   TCP 76 55588 → 88 [SYN] Seq=0 
Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=3523453804 TSecr=0 WS=128
  4 1.003269692   10.0.5.155 → 10.0.5.55TCP 76 88 → 55588 [SYN, ACK] 
Seq=0 Ack=1 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=2572724273 
TSecr=3523453804 WS=128
  5 1.00330261410.0.5.55 → 10.0.5.155   TCP 68 55588 → 88 [ACK] Seq=1 
Ack=1 Win=43776 Len=0 TSval=3523453804 TSecr=2572724273
  6 1.00354520410.0.5.55 → 10.0.5.155   KRB5 244 AS-REQ
  7 1.003567693   10.0.5.155 → 10.0.5.55TCP 68 88 → 55588 [ACK] Seq=1 
Ack=177 Win=44800 Len=0 TSval=2572724273 TSecr=3523453804
  8 1.003799664   10.0.5.155 → 10.0.5.55KRB5 326 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (continues)
  (8) and the whole tcp handshake happens with the correct IP addresses and the 
exchange

[Touch-packages] [Bug 1690485] Re: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'