[Touch-packages] [Bug 1695141] Re: Recent update broke multiheaded sleep

[Timo Aaltonen]

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers (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/1695141

Title:
  Recent update broke multiheaded sleep

Status in nvidia-graphics-drivers package in Ubuntu:
  New

Bug description:
  I just dist-upgraded my Zesty machine and two things broke related to
  sleeping the displays.  I have a 34" wide panel on the left and a 20"
  high resolution Dell on the right.

  Everything works fine until the displays sleep, say after a lockscreen
  has started.  First, the right screen never wakes from sleep; even
  though the lights on the front are green (indicating an active
  display), once the right display has slept, it never wakes back up
  even after a login.

  Second, and probably related: all the windows that were on the right
  display are now shifted over to the left and full-screened.

  This has all worked for a long time, but something in the recent
  stable updates has broken this, so it's a pretty serious regression.
  Nothing short of a reboot returns the dual screens to full
  functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  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: Fri Jun  2 00:17:33 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-20-generic, x86_64: installed
   bbswitch, 0.8, 4.10.0-21-generic, x86_64: installed
   nvidia-375, 375.66, 4.10.0-21-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GK104 [GeForce GTX 760] [1458:360b]
  InstallationDate: Installed on 2016-01-22 (497 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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 1:2.10.5-1ubuntu1
  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: Thu Jun  1 23:54:29 2017
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu1

To manage notifications about this bug go to:

[Touch-packages] [Bug 1695141] Re: Recent update broke multiheaded sleep

[Barry Warsaw]

% uname -a
Linux subdivisions 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux


FWIW, booting 4.10.0-20 hangs on boot so that's not a viable option.

Also, setting Brightness>Turn screen off when inactive for: Never
does not prevent Ubuntu from sleeping the displays (after progressive dimming) 
and thus causing the problem.

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

Title:
  Recent update broke multiheaded sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  I just dist-upgraded my Zesty machine and two things broke related to
  sleeping the displays.  I have a 34" wide panel on the left and a 20"
  high resolution Dell on the right.

  Everything works fine until the displays sleep, say after a lockscreen
  has started.  First, the right screen never wakes from sleep; even
  though the lights on the front are green (indicating an active
  display), once the right display has slept, it never wakes back up
  even after a login.

  Second, and probably related: all the windows that were on the right
  display are now shifted over to the left and full-screened.

  This has all worked for a long time, but something in the recent
  stable updates has broken this, so it's a pretty serious regression.
  Nothing short of a reboot returns the dual screens to full
  functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  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: Fri Jun  2 00:17:33 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-20-generic, x86_64: installed
   bbswitch, 0.8, 4.10.0-21-generic, x86_64: installed
   nvidia-375, 375.66, 4.10.0-21-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GK104 [GeForce GTX 760] [1458:360b]
  InstallationDate: Installed on 2016-01-22 (497 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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 1:2.10.5-1ubuntu1
  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: Thu Jun  1 23:54:29 

[Touch-packages] [Bug 1695141] [NEW] Recent update broke multiheaded sleep

[Barry Warsaw]

Public bug reported:

I just dist-upgraded my Zesty machine and two things broke related to
sleeping the displays.  I have a 34" wide panel on the left and a 20"
high resolution Dell on the right.

Everything works fine until the displays sleep, say after a lockscreen
has started.  First, the right screen never wakes from sleep; even
though the lights on the front are green (indicating an active display),
once the right display has slept, it never wakes back up even after a
login.

Second, and probably related: all the windows that were on the right
display are now shifted over to the left and full-screened.

This has all worked for a long time, but something in the recent stable
updates has broken this, so it's a pretty serious regression.  Nothing
short of a reboot returns the dual screens to full functionality.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
 GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.1
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: Fri Jun  2 00:17:33 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.10.0-20-generic, x86_64: installed
 bbswitch, 0.8, 4.10.0-21-generic, x86_64: installed
 nvidia-375, 375.66, 4.10.0-21-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GK104 [GeForce GTX 760] [1458:360b]
InstallationDate: Installed on 2016-01-22 (497 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z170X-UD5-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Z170X-UD5
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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 1:2.10.5-1ubuntu1
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: Thu Jun  1 23:54:29 2017
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.3-1ubuntu1

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu uec-images zesty

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

Title:
  Recent update broke multiheaded sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  I just dist-upgraded my Zesty machine and two things broke related to
  sleeping the displays.  I have a 34" wide panel on the left and a 20"
  high resolution Dell on the right.

  Everything 

[Touch-packages] [Bug 1436203] Re: [Dash] unity8-dash crashed with ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"

[Launchpad Bug Tracker]

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

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

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

Title:
  [Dash] unity8-dash crashed with ASSERT:
  "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"

Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Testing unity8 on a Lenovo IdeaPad s10-3t. The welcome wizard completed 
successfully. Unity8 loads, the indicators are visible and working.
  However, nothing else works: the scope shell doesn't load, only the splash 
screen is shown with the progress indicator spinning, and you can see that 
periodically it's restarted. Upstart logs for unity8-shell show an infinite 
loop of these:

  ==
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0'
  [1427269742.137055] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/client-platform/
  [1427269742.137918] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/dummy.so
  [1427269742.139587] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/mesa.so.2
  [1427269742.140657] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/mesa.so
  QSocketNotifier: Can only be used with threads started with QThread
  QSocketNotifier: Can only be used with threads started with QThread
  QObject::startTimer: Timers can only be used with threads started with QThread
  QIBusPlatformInputContext: invalid bus.
  file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not 
defined
  UbuntuWindow - regular geometry
  file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not 
defined
  ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE" in file 
../../../src/ubuntumirclient/glcontext.cpp, line 70
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0'
  [1427269746.575630] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/client-platform/
  [1427269746.576432] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/dummy.so
  ...
  ==

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150318-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic i686
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: i386
  Date: Tue Mar 24 17:31:02 2015
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2012-10-07 (898 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
   qt_assert(char const*, char const*, int) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
   ?? () from 
/usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   ?? () from 
/usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   QOpenGLContext::destroy() () from /usr/lib/i386-linux-gnu/sse2/libQt5Gui.so.5
  Title: unity8-dash crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: Upgraded to vivid on 2015-01-31 (52 days ago)
  UserGroups: adm lpadmin nopasswdlogin sambashare sudo

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

-- 
Mailing list: https://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 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

[Alex Tu]

** Changed in: oem-priority
   Status: New => In Progress

** Changed in: oem-priority
 Assignee: (unassigned) => Alex Tu (alextu)

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

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

Status in ModemManager:
  New
Status in OEM Priority Project:
  In Progress
Status in modemmanager package in Ubuntu:
  New

Bug description:
  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
    - but works well on on Yakkety.

  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
    - libmbim-glib4_1.14.0-1_amd64.deb
    - libmbim-glib-dev_1.14.0-1_amd64.deb
    - libmbim-proxy_1.14.0-1_amd64.deb
    - libmbim-utils_1.14.0-1_amd64.deb
    - libqmi-glib5_1.16.0-1_amd64.deb
    - libqmi-proxy_1.16.0-1_amd64.deb

   * different from ModemManager --debug
     - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/

  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.

  # environment information:

   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
    - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.

   * uname -r: 4.4.0-73-generic

   * lsusb -v: http://paste.ubuntu.com/24662332/

  FCC authentication reference:
   * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html
   * 
https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704

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

-- 
Mailing list: https://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 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows

[Bug Watch Updater]

** Changed in: apt (Debian)
   Status: New => Fix Released

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

Title:
  Apt updates that are uniformly spread across all timezones, with
  predictable application windows

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  Triaged
Status in unattended-upgrades source package in Xenial:
  Triaged
Status in apt source package in Yakkety:
  Triaged
Status in unattended-upgrades source package in Yakkety:
  Triaged
Status in apt source package in Zesty:
  Triaged
Status in unattended-upgrades source package in Zesty:
  Triaged
Status in apt source package in Artful:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Triaged
Status in apt package in Debian:
  Fix Released
Status in unattended-upgrades package in Debian:
  New

Bug description:
  [ Impact ]

   * unattended-upgrades are enabled by default in Ubuntu 16.04 and
  later

   * Currently the following three things happen as a monolithic event:
     - metadata updates: apt update
     - download of updates: apt upgrade --download-only
     - application of updates: apt upgrade

   * For the long running instances, all of the above happens at random
     times throughout the day.

   * If systems were poweredoff / suspended, this happens on boot /
  resume

   * End-users would like to have predictable timing, and control over when
     the updates happen.

  Considering all of the above, the following new behavior is proposed
  which should address all concerns in question. It combines all the
  desired properties from both end-user and mirror perspectives.

  [ Proposed Default Behavior ]

   * Decouple unattended-upgrades application, from apt update

   * apt update:
     - shall be a systemd timer based unit, triggered every 12h with a
   random delay of 12h, therefore executed randomly twice a day.
     - if unattened-upgrades (default on), or download-upgreadaeble-packages
   are enabled, it should result in updates being downloaded aka
   `apt upgrade --download-only`

   * unattended-upgrades:
     - shall be a separate systemd timer based unit triggered at 6am local
   time with a random delay of 1h, therefore executed between 6am and
   7am local time.

   * On boot / resume:
     - if we have missed one, or more, apt update timers,
   apt update / download upgrades / unattended-upgrade will happen in
   sequence. This may result in mirror spikes, but we do want to secure
   cold/stale-booted systems as soon as possible.

  [Test Case]

   * Run system for more than 24h, and check that apt updates were
     automatically executed twice.

   * Check that unattended upgrades were triggered to be applied at
     6am..7am window, if any.

   * Poweroff the machine over the period when apt-get update was
     scheduled, poweron and observe that apt-get update / download / 
 unattended upgrade are all performed on boot.

  [Regression Potential]

   * The newly proposed behavior is a mix of Pre-xenial behavior of "do
     everything at 6am..6:30am window" and the xenial+ behavior of "do 
 everything at random times throughout the day". If there are specific 
 deployments that rely on the previous types of behaviour they will be 
 able to adjust manually the systemd timers with the overrides to be 
 executed exactly as they wish; or match the .0 release behaviour that 
 they preffer.

   * If timers behavior is coded wrongly the proposed behaviour might not be
     executed as intended, thus requiring further SRUs to bring us in-line
     with the great expectations.

  [Other Info]

    * Related bug reports and history:
  - bug #1615482
  - bug #1554848

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

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

[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
   Packages that trigger multiple debconf prompts fail to install

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

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:
  tried to install comix

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Thu Jun  1 21:26:08 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-29 (3 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/1695134/+subscriptions

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

[manny l]

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

Public bug reported:

tried to install comix

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Thu Jun  1 21:26:08 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-29 (3 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/1695134

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:
  tried to install comix

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Thu Jun  1 21:26:08 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-29 (3 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/1695134/+subscriptions

-- 
Mailing list: https://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 1695079] Re: bluetoothd crashed with SIGSEGV in malloc_consolidate()

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1690013, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1690013
   bluetoothd crashed with SIGSEGV in malloc_consolidate() from _int_malloc() 
from __libc_calloc() from __GI___open_memstream() from __GI___vsyslog_chk

** Information type changed from Private to Public

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

Title:
  bluetoothd crashed with SIGSEGV in malloc_consolidate()

Status in bluez package in Ubuntu:
  New

Bug description:
  found this pending crash report after login

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-22.24~16.04.1-lowlatency 4.10.15
  Uname: Linux 4.10.0-22-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun  1 21:16:46 2017
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  ExecutableTimestamp: 1456846426
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/bluetooth/bluetoothd
  ProcCwd: /
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-22-lowlatency 
root=/dev/mapper/vgcrypt0-root ro ip=192.168.33.4::192.168.33.253 quiet 
nvidia_drm.modeset=1 crashkernel=384M-:128M irqpoll
  RetraceOutdatedPackages: no debug symbol package found for liblzma5
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
   malloc_consolidate (av=av@entry=0x7f558b1c6b20 ) at malloc.c:4167
   _int_malloc (av=av@entry=0x7f558b1c6b20 , 
bytes=bytes@entry=8192) at malloc.c:3448
   __libc_calloc (n=, elem_size=) at malloc.c:3234
   __GI___open_memstream (bufloc=bufloc@entry=0x7ffc798b0bb0, 
sizeloc=sizeloc@entry=0x7ffc798b0bb8) at memstream.c:83
   __GI___vsyslog_chk (pri=30, pri@entry=6, flag=flag@entry=1, 
fmt=fmt@entry=0x5560910fd518 "Endpoint unregistered: sender=%s path=%s", 
ap=ap@entry=0x7ffc798b0c80) at ../misc/syslog.c:167
  Title: bluetoothd crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/13/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A78T-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/13/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78T-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:19:15:4E:47:D7  ACL MTU: 1017:8  SCO MTU: 64:0
UP RUNNING PSCAN 
RX bytes:3488668 acl:62 sco:68335 events:93 errors:0
TX bytes:1625 acl:56 sco:0 commands:59 errors:0
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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

-- 
Mailing list: https://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 1695089] Re: Network Interface names differ between BIOS / UEFI

[Jochen Blacha]

Well, since a bug has to be filed against a package... I'd guess
"systemd" though I would say it's somehow related to systemd-network
(which doesn't seem to have a package)

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

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

Title:
  Network Interface names differ between BIOS / UEFI

Status in systemd package in Ubuntu:
  New

Bug description:
  Out of a discussion (with Stuart Langridge) about SystemD's new
  interface naming convention I discovered the following inconsistency
  in device naming on a BIOS vs a UEFI system...

  Using QEmu, set to act as a "440FX BIOS" system, and booting up the
  Ubuntu MATE 16.04.2 LTS ISO I get the following output from "ifconfig"
  ...

  eth0  Link encap:Ethernet  HWaddr CA:FE:15:60:0D:70
    inet addr:192.168.0.105  Bcast:192.168.0.1  Mask:255.255.255.0
    inet6 addr: fe80::b19a:de94:6e2c:37b7/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST  MTU:9100  Metric:1
    RX packets:54071 errors:0 dropped:0 overruns:0 frame:0
    TX packets:48515 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:22009423 (20.9 MiB)  TX bytes:25690847 (24.5 MiB)
    Interrupt:16

  Doing the same thing again but with QEmu being set to act as a "Q35
  UEFI" system (using the OVMF firmware) "ifconfig" gives me ...

  enp0s3Link encap:Ethernet  HWaddr CA:FE:15:60:0D:70
    inet addr:192.168.0.105  Bcast:192.168.0.1  Mask:255.255.255.0
    inet6 addr: fe80::b19a:de94:6e2c:37b7/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST  MTU:9100  Metric:1
    RX packets:27003 errors:0 dropped:0 overruns:0 frame:0
    TX packets:16171 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:11000712 (10.2 MiB)  TX bytes:8563615 (8.1 MiB)
    Interrupt:16

  NOTE: The same is true on my desktop system (UEFI capable), the
  network interface is "enp0s5" not "eth0".

  The later one would be more like what I would expect as SystemD's
  documentation goes to great lengths to try and explain the new naming
  convention for network interfaces.

  This inconsistency could actually lead to further problems down the
  road with other packages ... for example Samba. The default example
  config reads "bind interfaces = 127.0.0.0/8 eth0" (commented out
  though) where "eth0" is not really a good example default because with
  SystemD it no longer exists (at least on a UEFI system - and I had
  that issue with several friends already where I told them "uncomment
  'bind interfaces'" to have samba only bind/listen to the desired
  interfaces ... and then it not working because there's no "eth0"). It
  might be better to determine and append the lan/subnet post-install
  (i.e. 192.168.0.0/24) or settle on a uniform device naming convention
  for the network interfaces.

  The problem should be reproducible by simply booting a installation
  ISO on a BIOS and UEFI system (or accordingly configured VM).

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

-- 
Mailing list: https://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 1695089] [NEW] Network Interface names differ between BIOS / UEFI

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Out of a discussion (with Stuart Langridge) about SystemD's new
interface naming convention I discovered the following inconsistency in
device naming on a BIOS vs a UEFI system...

Using QEmu, set to act as a "440FX BIOS" system, and booting up the
Ubuntu MATE 16.04.2 LTS ISO I get the following output from "ifconfig"
...

eth0  Link encap:Ethernet  HWaddr CA:FE:15:60:0D:70
  inet addr:192.168.0.105  Bcast:192.168.0.1  Mask:255.255.255.0
  inet6 addr: fe80::b19a:de94:6e2c:37b7/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:9100  Metric:1
  RX packets:54071 errors:0 dropped:0 overruns:0 frame:0
  TX packets:48515 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:22009423 (20.9 MiB)  TX bytes:25690847 (24.5 MiB)
  Interrupt:16

Doing the same thing again but with QEmu being set to act as a "Q35
UEFI" system (using the OVMF firmware) "ifconfig" gives me ...

enp0s3Link encap:Ethernet  HWaddr CA:FE:15:60:0D:70
  inet addr:192.168.0.105  Bcast:192.168.0.1  Mask:255.255.255.0
  inet6 addr: fe80::b19a:de94:6e2c:37b7/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:9100  Metric:1
  RX packets:27003 errors:0 dropped:0 overruns:0 frame:0
  TX packets:16171 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:11000712 (10.2 MiB)  TX bytes:8563615 (8.1 MiB)
  Interrupt:16

NOTE: The same is true on my desktop system (UEFI capable), the network
interface is "enp0s5" not "eth0".

The later one would be more like what I would expect as SystemD's
documentation goes to great lengths to try and explain the new naming
convention for network interfaces.

This inconsistency could actually lead to further problems down the road
with other packages ... for example Samba. The default example config
reads "bind interfaces = 127.0.0.0/8 eth0" (commented out though) where
"eth0" is not really a good example default because with SystemD it no
longer exists (at least on a UEFI system - and I had that issue with
several friends already where I told them "uncomment 'bind interfaces'"
to have samba only bind/listen to the desired interfaces ... and then it
not working because there's no "eth0"). It might be better to determine
and append the lan/subnet post-install (i.e. 192.168.0.0/24) or settle
on a uniform device naming convention for the network interfaces.

The problem should be reproducible by simply booting a installation ISO
on a BIOS and UEFI system (or accordingly configured VM).

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


** Tags: bot-comment
-- 
Network Interface names differ between BIOS / UEFI
https://bugs.launchpad.net/bugs/1695089
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd 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 1695117] Re: package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  To be honest, im not really sure what happened, I started up and
  received this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   skypeforlinux:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CrashReports:
   644:0:122:0:2017-06-01 19:22:21.986094497 -0400:2017-06-01 
19:22:21.986094497 -0400:/var/crash/python3-apport.0.upload
   600:0:122:65859:2017-06-01 20:15:31.175392389 -0400:2017-06-01 
20:15:32.175392389 -0400:/var/crash/python3-apport.0.crash
   600:113:122:0:2017-06-01 19:22:24.362038086 -0400:2017-06-01 
19:22:24.362038086 -0400:/var/crash/python3-apport.0.uploaded
  Date: Thu Jun  1 20:15:32 2017
  DpkgHistoryLog:
   Start-Date: 2017-06-01  20:15:30
   Commandline: aptdaemon role='role-remove-packages' sender=':1.167'
   Remove: skypeforlinux:amd64 (5.2.0.1)
  DuplicateSignature:
   package:python3-apport:2.20.4-0ubuntu4
   Processing triggers for desktop-file-utils (0.23-1ubuntu2) ...
   dpkg: error processing package python3-apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-12 (20 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1695117] [NEW] package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura

[Andrea Cole]

Public bug reported:

To be honest, im not really sure what happened, I started up and
received this error.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: python3-apport 2.20.4-0ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportLog:
 
ApportVersion: 2.20.4-0ubuntu4
AptOrdering:
 skypeforlinux:amd64: Remove
 NULL: ConfigurePending
Architecture: amd64
CrashReports:
 644:0:122:0:2017-06-01 19:22:21.986094497 -0400:2017-06-01 19:22:21.986094497 
-0400:/var/crash/python3-apport.0.upload
 600:0:122:65859:2017-06-01 20:15:31.175392389 -0400:2017-06-01 
20:15:32.175392389 -0400:/var/crash/python3-apport.0.crash
 600:113:122:0:2017-06-01 19:22:24.362038086 -0400:2017-06-01 
19:22:24.362038086 -0400:/var/crash/python3-apport.0.uploaded
Date: Thu Jun  1 20:15:32 2017
DpkgHistoryLog:
 Start-Date: 2017-06-01  20:15:30
 Commandline: aptdaemon role='role-remove-packages' sender=':1.167'
 Remove: skypeforlinux:amd64 (5.2.0.1)
DuplicateSignature:
 package:python3-apport:2.20.4-0ubuntu4
 Processing triggers for desktop-file-utils (0.23-1ubuntu2) ...
 dpkg: error processing package python3-apport (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-05-12 (20 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: apport
Title: package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  To be honest, im not really sure what happened, I started up and
  received this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   skypeforlinux:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CrashReports:
   644:0:122:0:2017-06-01 19:22:21.986094497 -0400:2017-06-01 
19:22:21.986094497 -0400:/var/crash/python3-apport.0.upload
   600:0:122:65859:2017-06-01 20:15:31.175392389 -0400:2017-06-01 
20:15:32.175392389 -0400:/var/crash/python3-apport.0.crash
   600:113:122:0:2017-06-01 19:22:24.362038086 -0400:2017-06-01 
19:22:24.362038086 -0400:/var/crash/python3-apport.0.uploaded
  Date: Thu Jun  1 20:15:32 2017
  DpkgHistoryLog:
   Start-Date: 2017-06-01  20:15:30
   Commandline: aptdaemon role='role-remove-packages' sender=':1.167'
   Remove: skypeforlinux:amd64 (5.2.0.1)
  DuplicateSignature:
   package:python3-apport:2.20.4-0ubuntu4
   Processing triggers for desktop-file-utils (0.23-1ubuntu2) ...
   dpkg: error processing package python3-apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-12 (20 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1692111] Re: Unable to configure raw.id_map with multiple entries

[Christian Brauner]

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

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

** Changed in: lxc (Ubuntu)
   Status: New => Fix Committed

** Changed in: lxc (Ubuntu)
 Assignee: (unassigned) => Christian Brauner (cbrauner)

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

Title:
  Unable to configure raw.id_map with multiple entries

Status in lxc package in Ubuntu:
  Fix Committed
Status in lxd package in Ubuntu:
  Fix Committed

Bug description:
  I am trying to map two users (999, 1001) to one of my containers. I
  added both IDs to /etc/subgid and /etc/subuid. I followed by setting
  raw.id_map property value (as instructed here
  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2017-March/013034.html):

  "echo -e "both 999 999\nboth 1001 1001" |  lxc config set mycontainer
  raw.idmap -"

  However upon starting the container, I get errors (log excerpt below).
  If, on the other hand, I set idmap to either "both 999 999" or "both
  1001 1001" only - i.e. if I map only one user at the time, the
  container starts just fine and the user is mapped as expected.

  My subgid and subuid look as follows:

  lxd:10:65536
  root:10:65536
  root:1001:1
  root:999:1

  Log excerpt:

  Name: mycontainer
  Remote: unix:/var/lib/lxd/unix.socket
  Architecture: x86_64
  Created: 2017/02/22 18:54 UTC
  Status: Stopped
  Type: persistent
  Profiles: default

  Log:

  lxc 20170519204102.895 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer" already existed.
  lxc 20170519204102.896 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer: No such file or directory
  lxc 20170519204102.897 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-1" already existed.
  lxc 20170519204102.897 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-1: No such file or directory
  lxc 20170519204102.897 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-2" already existed.
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-2: No such file or directory
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-3" already existed.
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-3: No such file or directory
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-4" already existed.
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-4: No such file or directory
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-5" already existed.
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-5: No such file or directory
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-6" already existed.
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-6: No such file or directory
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-7" already existed.
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-7: No such file or directory
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-8" already existed.
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such 

[Touch-packages] [Bug 1693570] Re: package software-properties-common 0.96.20.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[Launchpad Bug Tracker]

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

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  package software-properties-common 0.96.20.7 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 139

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Beetween of update the os sand this message.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: software-properties-common 0.96.20.7
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Thu May 25 19:17:33 2017
  DuplicateSignature:
   package:software-properties-common:0.96.20.7
   Setting up software-properties-common (0.96.20.7) ...
   Segmentation fault (core dumped)
   dpkg: error processing package software-properties-common (--configure):
subprocess installed post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2016-08-08 (290 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160720)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: software-properties
  Title: package software-properties-common 0.96.20.7 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows

[Bug Watch Updater]

** Changed in: unattended-upgrades (Debian)
   Status: Unknown => New

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

Title:
  Apt updates that are uniformly spread across all timezones, with
  predictable application windows

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  Triaged
Status in unattended-upgrades source package in Xenial:
  Triaged
Status in apt source package in Yakkety:
  Triaged
Status in unattended-upgrades source package in Yakkety:
  Triaged
Status in apt source package in Zesty:
  Triaged
Status in unattended-upgrades source package in Zesty:
  Triaged
Status in apt source package in Artful:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Triaged
Status in apt package in Debian:
  New
Status in unattended-upgrades package in Debian:
  New

Bug description:
  [ Impact ]

   * unattended-upgrades are enabled by default in Ubuntu 16.04 and
  later

   * Currently the following three things happen as a monolithic event:
     - metadata updates: apt update
     - download of updates: apt upgrade --download-only
     - application of updates: apt upgrade

   * For the long running instances, all of the above happens at random
     times throughout the day.

   * If systems were poweredoff / suspended, this happens on boot /
  resume

   * End-users would like to have predictable timing, and control over when
     the updates happen.

  Considering all of the above, the following new behavior is proposed
  which should address all concerns in question. It combines all the
  desired properties from both end-user and mirror perspectives.

  [ Proposed Default Behavior ]

   * Decouple unattended-upgrades application, from apt update

   * apt update:
     - shall be a systemd timer based unit, triggered every 12h with a
   random delay of 12h, therefore executed randomly twice a day.
     - if unattened-upgrades (default on), or download-upgreadaeble-packages
   are enabled, it should result in updates being downloaded aka
   `apt upgrade --download-only`

   * unattended-upgrades:
     - shall be a separate systemd timer based unit triggered at 6am local
   time with a random delay of 1h, therefore executed between 6am and
   7am local time.

   * On boot / resume:
     - if we have missed one, or more, apt update timers,
   apt update / download upgrades / unattended-upgrade will happen in
   sequence. This may result in mirror spikes, but we do want to secure
   cold/stale-booted systems as soon as possible.

  [Test Case]

   * Run system for more than 24h, and check that apt updates were
     automatically executed twice.

   * Check that unattended upgrades were triggered to be applied at
     6am..7am window, if any.

   * Poweroff the machine over the period when apt-get update was
     scheduled, poweron and observe that apt-get update / download / 
 unattended upgrade are all performed on boot.

  [Regression Potential]

   * The newly proposed behavior is a mix of Pre-xenial behavior of "do
     everything at 6am..6:30am window" and the xenial+ behavior of "do 
 everything at random times throughout the day". If there are specific 
 deployments that rely on the previous types of behaviour they will be 
 able to adjust manually the systemd timers with the overrides to be 
 executed exactly as they wish; or match the .0 release behaviour that 
 they preffer.

   * If timers behavior is coded wrongly the proposed behaviour might not be
     executed as intended, thus requiring further SRUs to bring us in-line
     with the great expectations.

  [Other Info]

    * Related bug reports and history:
  - bug #1615482
  - bug #1554848

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

-- 
Mailing list: https://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 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows

[Julian Andres Klode]

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

** Also affects: unattended-upgrades (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863911
   Importance: Unknown
   Status: Unknown

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

Title:
  Apt updates that are uniformly spread across all timezones, with
  predictable application windows

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  Triaged
Status in unattended-upgrades source package in Xenial:
  Triaged
Status in apt source package in Yakkety:
  Triaged
Status in unattended-upgrades source package in Yakkety:
  Triaged
Status in apt source package in Zesty:
  Triaged
Status in unattended-upgrades source package in Zesty:
  Triaged
Status in apt source package in Artful:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Triaged
Status in apt package in Debian:
  New
Status in unattended-upgrades package in Debian:
  Unknown

Bug description:
  [ Impact ]

   * unattended-upgrades are enabled by default in Ubuntu 16.04 and
  later

   * Currently the following three things happen as a monolithic event:
     - metadata updates: apt update
     - download of updates: apt upgrade --download-only
     - application of updates: apt upgrade

   * For the long running instances, all of the above happens at random
     times throughout the day.

   * If systems were poweredoff / suspended, this happens on boot /
  resume

   * End-users would like to have predictable timing, and control over when
     the updates happen.

  Considering all of the above, the following new behavior is proposed
  which should address all concerns in question. It combines all the
  desired properties from both end-user and mirror perspectives.

  [ Proposed Default Behavior ]

   * Decouple unattended-upgrades application, from apt update

   * apt update:
     - shall be a systemd timer based unit, triggered every 12h with a
   random delay of 12h, therefore executed randomly twice a day.
     - if unattened-upgrades (default on), or download-upgreadaeble-packages
   are enabled, it should result in updates being downloaded aka
   `apt upgrade --download-only`

   * unattended-upgrades:
     - shall be a separate systemd timer based unit triggered at 6am local
   time with a random delay of 1h, therefore executed between 6am and
   7am local time.

   * On boot / resume:
     - if we have missed one, or more, apt update timers,
   apt update / download upgrades / unattended-upgrade will happen in
   sequence. This may result in mirror spikes, but we do want to secure
   cold/stale-booted systems as soon as possible.

  [Test Case]

   * Run system for more than 24h, and check that apt updates were
     automatically executed twice.

   * Check that unattended upgrades were triggered to be applied at
     6am..7am window, if any.

   * Poweroff the machine over the period when apt-get update was
     scheduled, poweron and observe that apt-get update / download / 
 unattended upgrade are all performed on boot.

  [Regression Potential]

   * The newly proposed behavior is a mix of Pre-xenial behavior of "do
     everything at 6am..6:30am window" and the xenial+ behavior of "do 
 everything at random times throughout the day". If there are specific 
 deployments that rely on the previous types of behaviour they will be 
 able to adjust manually the systemd timers with the overrides to be 
 executed exactly as they wish; or match the .0 release behaviour that 
 they preffer.

   * If timers behavior is coded wrongly the proposed behaviour might not be
     executed as intended, thus requiring further SRUs to bring us in-line
     with the great expectations.

  [Other Info]

    * Related bug reports and history:
  - bug #1615482
  - bug #1554848

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

-- 
Mailing list: https://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 1694995] Re: package libsystemd0:i386 229-4ubuntu17 failed to install/upgrade: package libsystemd0:i386 is not ready for configuration cannot configure (current status 'half-inst

[Emily Ratliff]

** Information type changed from Private Security to Public

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

Title:
  package libsystemd0:i386 229-4ubuntu17 failed to install/upgrade:
  package libsystemd0:i386 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in systemd package in Ubuntu:
  New

Bug description:
  can not download any app

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsystemd0:i386 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun  1 19:12:43 2017
  DuplicateSignature:
   package:libsystemd0:i386:229-4ubuntu17
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package libsystemd0:i386 (--configure):
package libsystemd0:i386 is not ready for configuration
  ErrorMessage: package libsystemd0:i386 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-30 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: systemd
  Title: package libsystemd0:i386 229-4ubuntu17 failed to install/upgrade: 
package libsystemd0:i386 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/systemd/+bug/1694995/+subscriptions

-- 
Mailing list: https://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 1694995] Re: package libsystemd0:i386 229-4ubuntu17 failed to install/upgrade: package libsystemd0:i386 is not ready for configuration cannot configure (current status 'half-inst

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libsystemd0:i386 229-4ubuntu17 failed to install/upgrade:
  package libsystemd0:i386 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in systemd package in Ubuntu:
  New

Bug description:
  can not download any app

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsystemd0:i386 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun  1 19:12:43 2017
  DuplicateSignature:
   package:libsystemd0:i386:229-4ubuntu17
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package libsystemd0:i386 (--configure):
package libsystemd0:i386 is not ready for configuration
  ErrorMessage: package libsystemd0:i386 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-30 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: systemd
  Title: package libsystemd0:i386 229-4ubuntu17 failed to install/upgrade: 
package libsystemd0:i386 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/systemd/+bug/1694995/+subscriptions

-- 
Mailing list: https://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

[Brian Murray]

Eric - Have you tested the new version of openssl which William
uploaded?

-- 
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 in 3.00s
  OpenSSL 1.0.2g 1 Mar 2016
  built on: reproducible build, date unspecified
  options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) 
blowfish(idx)
  compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT 
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall 
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM 
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
  The 'numbers' are in 1000s of bytes per second processed.
  type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
  sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55

  The performance are clearly better when using the patch which take
  benefit of the sha extension. (See Regression Potential section for
  result with patch)

  [Regression Potential]

   * Note : IRC discussion with infinity :
  
https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/comments/8

   * Note from irc discussion with apw and rbasak :
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/comments/2

   * It basically allow openssl to take benefit of sha extension
  potential (mostly performance-wise) now that new AMD cpu starting  to
  have the capability.

  * The code check the CPUID bit to determine if the sha instructions
  are available are not.

  * 

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

[Brian Murray]

William - could you add some information about the verification you did
since you tagged this verification-done?

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

-- 
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 in 3.00s
  OpenSSL 1.0.2g 1 Mar 2016
  built on: reproducible build, date unspecified
  options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) 
blowfish(idx)
  compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT 
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall 
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM 
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
  The 'numbers' are in 1000s of bytes per second processed.
  type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
  sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55

  The performance are clearly better when using the patch which take
  benefit of the sha extension. (See Regression Potential section for
  result with patch)

  [Regression Potential]

   * Note : IRC discussion with infinity :
  
https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/comments/8

   * Note from irc discussion with apw and rbasak :
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/comments/2

   * It basically allow openssl to take benefit of sha extension
  potential (mostly performance-wise) now that new AMD cpu starting  to
  have the 

[Touch-packages] [Bug 1694592] Re: xdiagnose

[Emily Ratliff]

** Information type changed from Private Security to Public

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

Title:
  xdiagnose

Status in xorg package in Ubuntu:
  New

Bug description:
  xdiagnose bug report

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue May 30 23:33:21 2017
  DistUpgraded: 2016-08-19 20:34:43,656 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.40, 4.4.0-78-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF119 [GeForce GT 520] [10de:1040] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GF119 [GeForce GT 520] [10de:0915]
  InstallationDate: Installed on 2015-03-01 (821 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: Gateway FX4710-UB003A
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=d15f951b-4509-4584-a71a-2cfce009ad0a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-20 (284 days ago)
  dmi.bios.date: 07/02/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 841P051G
  dmi.board.name: G33M05G1
  dmi.board.vendor: Gateway
  dmi.board.version: MP
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr841P051G:bd07/02/2008:svnGateway:pnFX4710-UB003A:pvrOEM:rvnGateway:rnG33M05G1:rvrMP:cvnGateway:ct3:cvrOEM:
  dmi.product.name: FX4710-UB003A
  dmi.product.version: OEM
  dmi.sys.vendor: Gateway
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon May 29 13:54:58 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech K520KEYBOARD, id 8
   inputLogitech Wireless Mouse MOUSE, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: nouveau

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

-- 
Mailing list: https://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 1692315] Re: Package description is inaccurate

[Robie Basak]

(except in the development release, I suppose, but that wasn't the
reason I filed this bug)

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

Title:
  Package description is inaccurate

Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  unattended-upgrades 0.93.1ubuntu6

  "Description: automatic installation of security upgrades"

  This is now wrong for Ubuntu, since the default behaviour of the
  package is not restricted to security upgrades.

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

-- 
Mailing list: https://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 1692315] Re: Package description is inaccurate

[Robie Basak]

I'm wrong. It is.

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Package description is inaccurate

Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  unattended-upgrades 0.93.1ubuntu6

  "Description: automatic installation of security upgrades"

  This is now wrong for Ubuntu, since the default behaviour of the
  package is not restricted to security upgrades.

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

-- 
Mailing list: https://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

[Eric Desrochers]

** Description changed:

  [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 in 3.00s
  OpenSSL 1.0.2g 1 Mar 2016
  built on: reproducible build, date unspecified
  options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) 
blowfish(idx)
  compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT 
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall 
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM 
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
  The 'numbers' are in 1000s of bytes per second processed.
  type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
  sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55
  
  The performance are clearly better when using the patch which take
  benefit of the sha extension. (See Regression Potential section for
  result with patch)
  
  [Regression Potential]
  
   * Note : IRC discussion with infinity :
  
https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/comments/8
  
   * Note from irc discussion with apw and rbasak :
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/comments/2
  
   * It basically allow openssl to take benefit of sha extension potential
  (mostly performance-wise) now that new AMD cpu starting  to have the
  capability.
  
  * The code check the CPUID bit to determine if the sha instructions are
  available are not.
  
  * Maintainer comment proves that he did the successfully tested on Intel
  with/without SHA extension
  
  Reference: https://github.com/openssl/openssl/issues/2848
  "I don't have access to Ryzen system, so I didn't test it explicitly on 
Ryzen. Reporter did confirm it tough. Myself I tested on Intel processors, yes, 
with/without."
  
  * LP reporter comment :
  I, slashd, have tested on a Ryzen system (and AMD non-ryzen) and non-sha 
INTEL cpu. It does reveal a significant performance increase on Ryzen due to 
the sha extension :
  

[Touch-packages] [Bug 1695080] [NEW] crash during thread exit when using thread local storage

[Mike Gulick]

Public bug reported:

An application we develop crashes on exit with:
*** Error in `foo': free(): invalid pointer: 0x09309bc0 ***

This issue occurs when there are a large number of threads running which
use thread local storage.  We have identified the issue as an existing
upstream glibc bug, #13862.  This bug was fixed in glibc-2.21.  See
https://sourceware.org/bugzilla/show_bug.cgi?id=13862.  The upstream bug
report has a reproducer which reliably reproduces the problem.

I have reported this bug to Debian (#854007), and provided a backported
patch for the glibc-2.19 package included in Debian-8 (0001-Resize-DTV-
if-the-current-DTV-isn-t-big-enough.patch).  I have not tested whether
this patch resolves this issue in eglibc-2.19 in Ubuntu 14.04, however
the reproducer in the original glibc bug report does reliably reproduce
the problem on Ubuntu 14.04.5 with the latest glibc6 package installed.

The Debian bug report can be found at https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=854007

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libc6 2.19-0ubuntu6.11
ProcVersionSignature: Ubuntu 3.13.0-119.166-generic 3.13.11-ckt39
Uname: Linux 3.13.0-119-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.24
Architecture: amd64
Date: Thu Jun  1 15:43:48 2017
Dependencies:
 gcc-5-base 5.3.0-3ubuntu1~14.04 [origin: unknown]
 libc6 2.19-0ubuntu6.11
 libgcc1 1:5.3.0-3ubuntu1~14.04 [origin: unknown]
 multiarch-support 2.19-0ubuntu6.11
InstallationDate: Installed on 2015-04-09 (784 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: eglibc
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages trusty

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

Title:
  crash during thread exit when using thread local storage

Status in eglibc package in Ubuntu:
  New

Bug description:
  An application we develop crashes on exit with:
  *** Error in `foo': free(): invalid pointer: 0x09309bc0 ***

  This issue occurs when there are a large number of threads running
  which use thread local storage.  We have identified the issue as an
  existing upstream glibc bug, #13862.  This bug was fixed in
  glibc-2.21.  See
  https://sourceware.org/bugzilla/show_bug.cgi?id=13862.  The upstream
  bug report has a reproducer which reliably reproduces the problem.

  I have reported this bug to Debian (#854007), and provided a
  backported patch for the glibc-2.19 package included in Debian-8 (0001
  -Resize-DTV-if-the-current-DTV-isn-t-big-enough.patch).  I have not
  tested whether this patch resolves this issue in eglibc-2.19 in Ubuntu
  14.04, however the reproducer in the original glibc bug report does
  reliably reproduce the problem on Ubuntu 14.04.5 with the latest
  glibc6 package installed.

  The Debian bug report can be found at https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=854007

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libc6 2.19-0ubuntu6.11
  ProcVersionSignature: Ubuntu 3.13.0-119.166-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-119-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  Date: Thu Jun  1 15:43:48 2017
  Dependencies:
   gcc-5-base 5.3.0-3ubuntu1~14.04 [origin: unknown]
   libc6 2.19-0ubuntu6.11
   libgcc1 1:5.3.0-3ubuntu1~14.04 [origin: unknown]
   multiarch-support 2.19-0ubuntu6.11
  InstallationDate: Installed on 2015-04-09 (784 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: eglibc
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1695067] Re: package python3-problem-report 2.20.4-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python3-problem-report 2.20.4-0ubuntu4.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in apport package in Ubuntu:
  New

Bug description:
  I have fixed this install issue once already :(

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-problem-report 2.20.4-0ubuntu4.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic i686
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  CrashReports:
   644:0:119:0:2017-05-27 22:41:47.248780694 +0100:2017-05-27 
22:41:47.248780694 +0100:/var/crash/_usr_bin_py3compile.0.upload
   600:0:119:63972:2017-06-01 19:01:26.924177169 +0100:2017-06-01 
19:01:27.924177169 +0100:/var/crash/python3-problem-report.0.crash
   640:1000:119:1025742:2017-05-31 23:28:37.258940662 +0100:2017-06-01 
18:54:08.430309493 +0100:/var/crash/_usr_bin_xfce4-power-manager.1000.crash
   600:110:119:0:2017-05-27 22:41:54.488541095 +0100:2017-05-23 
20:31:36.192501415 +0100:/var/crash/_usr_bin_py3compile.0.uploaded
   640:0:119:11856:2017-06-01 19:01:27.780084923 +0100:2017-06-01 
19:01:27.780084923 +0100:/var/crash/_usr_bin_py3compile.0.crash
  Date: Thu Jun  1 19:01:27 2017
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-11-03 (209 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package python3-problem-report 2.20.4-0ubuntu4.1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (46 days ago)

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

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

[Emily Ratliff]

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

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

** Information type changed from Private Security to Public

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

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:
  It shows System problem detecetd frequently

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Tue May 30 02:45:24 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-30 (0 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/1694521/+subscriptions

-- 
Mailing list: https://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 1695067] [NEW] package python3-problem-report 2.20.4-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[ChewieB]

Public bug reported:

I have fixed this install issue once already :(

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: python3-problem-report 2.20.4-0ubuntu4.1
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic i686
ApportLog:
 
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: i386
CrashReports:
 644:0:119:0:2017-05-27 22:41:47.248780694 +0100:2017-05-27 22:41:47.248780694 
+0100:/var/crash/_usr_bin_py3compile.0.upload
 600:0:119:63972:2017-06-01 19:01:26.924177169 +0100:2017-06-01 
19:01:27.924177169 +0100:/var/crash/python3-problem-report.0.crash
 640:1000:119:1025742:2017-05-31 23:28:37.258940662 +0100:2017-06-01 
18:54:08.430309493 +0100:/var/crash/_usr_bin_xfce4-power-manager.1000.crash
 600:110:119:0:2017-05-27 22:41:54.488541095 +0100:2017-05-23 
20:31:36.192501415 +0100:/var/crash/_usr_bin_py3compile.0.uploaded
 640:0:119:11856:2017-06-01 19:01:27.780084923 +0100:2017-06-01 
19:01:27.780084923 +0100:/var/crash/_usr_bin_py3compile.0.crash
Date: Thu Jun  1 19:01:27 2017
Dependencies:
 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-11-03 (209 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: apport
Title: package python3-problem-report 2.20.4-0ubuntu4.1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: Upgraded to zesty on 2017-04-15 (46 days ago)

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


** Tags: apport-package i386 zesty

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

Title:
  package python3-problem-report 2.20.4-0ubuntu4.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in apport package in Ubuntu:
  New

Bug description:
  I have fixed this install issue once already :(

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-problem-report 2.20.4-0ubuntu4.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic i686
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  CrashReports:
   644:0:119:0:2017-05-27 22:41:47.248780694 +0100:2017-05-27 
22:41:47.248780694 +0100:/var/crash/_usr_bin_py3compile.0.upload
   600:0:119:63972:2017-06-01 19:01:26.924177169 +0100:2017-06-01 
19:01:27.924177169 +0100:/var/crash/python3-problem-report.0.crash
   640:1000:119:1025742:2017-05-31 23:28:37.258940662 +0100:2017-06-01 
18:54:08.430309493 +0100:/var/crash/_usr_bin_xfce4-power-manager.1000.crash
   600:110:119:0:2017-05-27 22:41:54.488541095 +0100:2017-05-23 
20:31:36.192501415 +0100:/var/crash/_usr_bin_py3compile.0.uploaded
   640:0:119:11856:2017-06-01 19:01:27.780084923 +0100:2017-06-01 
19:01:27.780084923 +0100:/var/crash/_usr_bin_py3compile.0.crash
  Date: Thu Jun  1 19:01:27 2017
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-11-03 (209 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package python3-problem-report 2.20.4-0ubuntu4.1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (46 days ago)

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

-- 
Mailing list: https://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 455024] Re: resize2fs: memory allocation failed while trying to resize

[elatllat]

e2fsck -y $D
fails with 
"ext2fs_get_mem: Cannot allocate memory"
on a computer with 100GB swap and 2GB RAM.
#e2fsck 1.42.13 (17-May-2015) 

e2fsprogs is clearly not designed to scale, guess it's time to switch to
btrfs

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

Title:
  resize2fs: memory allocation failed while trying to resize

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: e2fsprogs

  When I try to resize a big EXT3 filesystem on a RAID5 (/dev/md0) from
  5TB to 7TB i get this output:

  # resize2fs -p /dev/md0 
  resize2fs 1.41.9 (22-Aug-2009)
  Resizing the filesystem on /dev/md0 to 1709329888 (4k) blocks.
  Start von Durchgang 1 (max = 14904)
  Vergrößere die Inode-Tabelle
  resize2fs: Memory allocation failed beim Versuch, die Größe von /dev/md0 zu 
ändern
  Please run 'e2fsck -fy /dev/md0' to fix the filesystem
  after the aborted resize operation.

  Note: Im using Ubuntu Hardy due to its LTS. But I installed the
  packages from Karmic, because they had no special dependencies, I
  could install them without any problem. The message above is from this
  updated e2fsprogs version (note the version). I get the exactly same
  message from the original e2fsprogs, except the last two lines (Please
  run...).

  I use 4KB Blocks, so EXT3 should be able to address 8TB...

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

-- 
Mailing list: https://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 1688017] Re: Connection to bluetooth headsets fails

[Bouddhid]

Hi ! Have you tried to install pulseaudio-module-bluetooth ?

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

Title:
  Connection to bluetooth headsets fails

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi,

  since upgrading to 17.04 I can't connect to bluetooth headsets
  anymore. Headsets are found and listed as devices, but when trying to
  connect, there's an error

  blueman.bluez.errors.DBusFailedError: Protocol not available...

  
  syslog says:

  May  3 16:43:12 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed 
for 00:18:91:4F:E5:C6: Protocol not available
  May  3 16:47:18 pcdanisch bluetoothd[2075]: message repeated 8 times: [ 
a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available]
  May  3 16:48:14 pcdanisch bluetoothd[2075]: EF:AC:86:08:6F:21: error updating 
services: Operation already in progress (114)
  May  3 16:50:56 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed 
for 00:18:91:4F:E5:C6: Protocol not available
  May  3 16:53:01 pcdanisch bluetoothd[2075]: Pair device timed out for hci0
  May  3 16:59:30 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed 
for 00:18:91:4F:E5:C6: Protocol not available
  May  3 17:04:11 pcdanisch bluetoothd[2075]: message repeated 3 times: [ 
a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available]



  Here someone else reports the same observation:
  
http://www.1oo.club/bluetooth-unable-to-connect-to-headphones-after-ubuntu-17-04-upgrade/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: bluez 5.43-0ubuntu1
  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
  CurrentDesktop: XFCE
  Date: Wed May  3 17:12:51 2017
  InstallationDate: Installed on 2016-04-22 (376 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  InterestingModules: bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
  SourcePackage: bluez
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (15 days ago)
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:BB:58:C1:E9:FA  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN 
RX bytes:18751 acl:51 sco:0 events:1345 errors:0
TX bytes:27309 acl:48 sco:0 commands:1243 errors:0

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

-- 
Mailing list: https://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 1619327] Re: package ibus 1.5.11-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127

[Launchpad Bug Tracker]

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

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

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

Title:
  package ibus 1.5.11-1ubuntu2 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 127

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  I can not update some packages . there is always errors

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ibus 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep  1 21:32:20 2016
  DuplicateSignature:
   package:ibus:1.5.11-1ubuntu2
   Removing ibus (1.5.11-1ubuntu2) ...
   /var/lib/dpkg/info/ibus.prerm: 7: /var/lib/dpkg/info/ibus.prerm: dconf: not 
found
   dpkg: error processing package ibus (--remove):
subprocess installed pre-removal script returned error exit status 127
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 127
  InstallationDate: Installed on 2016-07-16 (47 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: ibus
  Title: package ibus 1.5.11-1ubuntu2 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1692437] Re: Monitors on second GPU not working after upgrade to zesty

[Richard Eames]

I'm beginning to think this is a driver issue. I have a builtin "Kaveri"
amd gpu, and pci Radeon HD 4850. I usually have the 4850 as my primary
card/monitor setup. However, since upgrading to Ubuntu 17.04, once
lightdm is started, only the monitor on the Kaveri works.

I dropped to VT1, and ran `X -configure` after shutting lightdm down,
and received an error:

amdgpu_device_initialize: DRM version is 2.49.0 but this driver is only
compatible with 3.x.x

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

Title:
  Monitors on second GPU not working after upgrade to zesty

Status in Light Display Manager:
  New
Status in xserver-xorg-driver-radeonhd:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm not 100% sure this is the right package to file the bug against,
  but since upgrading to zesty the two monitors on my second GPU are no
  longer detected once I reach the greeter screen at login time.
  However, both of them display information during boot.

  Let me know how I can narrow down the bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lightdm 1.22.0-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon May 22 01:42:58 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-29 (388 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago)

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

-- 
Mailing list: https://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 1694513] Re: (software-properties, missing debconf socket; frontend window closed too early?) package shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/u

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  (software-properties, missing debconf socket; frontend window closed
  too early?) package shim-signed
  1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in shim-signed package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New

Bug description:
  Just appeared out of no where.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  .proc.sys.kernel.moksbstate_disabled: 0
  .sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23: 
Error: [Errno 2] No such file or directory: 
'/sys/firmware/efi/efivars/MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23'
  .sys.firmware.efi.efivars.SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c: 

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

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

[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
   Packages that trigger multiple debconf prompts fail to install

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

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:
  just trying to change my boot order.
  Bug happened when running literally:

  1.fgrep menuentry /boot/grub/grub.cfg
  - this was ok and outputs the cfg file contents on screen
  2.  gksu edit /etc/default/grub
  - results in 
  The program 'gksu' is currently not installed. You can install it by typing:
  sudo apt install gksu
  3. sudo apt install gksu
  - asks password (ofc)
  output is the following 2 lines beginning with E:
  E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily 
unavailable)
  E: Unable to lock the administration directory (/var/lib/dpkg/), is another 
process using it?

  *might* have to do with the fact that firefox plugins wont install, and also 
chrome install hangs at 51% when installing from "Ubuntu Software"
  The error with FF is identical with complaining about the administration 
directory, but chrome just silently hangs there.

  My install is quite default ubuntu latest i guess 17.04 x64. tbh i did
  not change anything but kb and regional settings while installing.

  lsb:
  Description:  Ubuntu 17.04
  Release:  17.04

  apt-cache policy gconf:
  gconf:
Installed: (none)
Candidate: (none)
Version table:

  what i expected to happen:
  apt download and install of gksu (which i don't know what it is some editor i 
guess)
  what happened:
  the same 2 E: lines that I get in the other mentioned situations.

  note: I don't know if this is a bug as such. I mean maybe, I guess (never 
having gui installed linux before, I've been windows / apple since 90's) gconf 
is missing from the install package?
  So kind of not a bug but a packaging issue maybe, I don't know how ubuntu is 
structured in regards to ALM, if this were a software with multiple components 
I would guess all the builds are ok but the output copy failed for that part? I 
am just a .net dev / architect so this is a guess. But if this were microsoft 
server app X, then we're talking a missing dll / component from the 
distribution image.

  As it might be pertinent,install was done by rufus (2.11) just making a 
bootable usb stick from:
  ubuntu-17.04-desktop-amd64.iso
  which was downloaded a few days ago from the offical main page.

  I won't bother doing the DebuggingProcedures, as my personal guess is that 
debugging software that does not exist on this install is not technically 
feasible.
  I will also not try to update manually or anything, in case someone wants to 
take a remote gander at the situation, or require more info which would be lost 
in case I change something.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Tue May 30 14:01:58 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-29 (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/1694620/+subscriptions

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

[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
   Packages that trigger multiple debconf prompts fail to install

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

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:
  The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About 
Ubuntu
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  3) What you expected to happen
  4) What happened instead

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed May 31 10:43:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-31 (0 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/1694807/+subscriptions

-- 
Mailing list: https://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 1694627] Re: ksplice-uptrac failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  ksplice-uptrac failed to install/upgrade: subprocess installed post-
  installation script returned error exit status 128

Status in consolekit package in Ubuntu:
  New

Bug description:
  Instalation Failed on Xenial - Using file manager

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpam-ck-connector:amd64 0.4.6-5
  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.6
  Architecture: amd64
  Date: Wed May 31 09:06:54 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2016-07-12 (322 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: consolekit
  Title: package libpam-ck-connector:amd64 0.4.6-5 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/consolekit/+bug/1694627/+subscriptions

-- 
Mailing list: https://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 1694628] Re: package zlib1g:amd64 1:1.2.8.dfsg-2ubuntu4.1 failed to install/upgrade: package zlib1g:amd64 cannot be configured because zlib1g:i386 is not ready (current status 'h

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package zlib1g:amd64 1:1.2.8.dfsg-2ubuntu4.1 failed to
  install/upgrade: package zlib1g:amd64 cannot be configured because
  zlib1g:i386 is not ready (current status 'half-installed')

Status in zlib package in Ubuntu:
  New

Bug description:
  The error occured whlile installing the epson xp205 printer driver on
  ubuntu mate

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zlib1g:amd64 1:1.2.8.dfsg-2ubuntu4.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed May 31 10:10:22 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:zlib1g:amd64:1:1.2.8.dfsg-2ubuntu4.1
   Processing triggers for libc-bin (2.23-0ubuntu7) ...
   dpkg: error processing package zlib1g:amd64 (--configure):
package zlib1g:amd64 cannot be configured because zlib1g:i386 is not ready 
(current status 'half-installed')
  ErrorMessage: package zlib1g:amd64 cannot be configured because zlib1g:i386 
is not ready (current status 'half-installed')
  InstallationDate: Installed on 2017-05-28 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: zlib
  Title: package zlib1g:amd64 1:1.2.8.dfsg-2ubuntu4.1 failed to 
install/upgrade: package zlib1g:amd64 cannot be configured because zlib1g:i386 
is not ready (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/zlib/+bug/1694628/+subscriptions

-- 
Mailing list: https://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 1694916] Re: package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  New

Bug description:
  Issues updating apport:

  sudo dpkg --configure -a
  dpkg: error processing package apport (--configure):
   package is in a very bad inconsistent state; you should
   reinstall it before attempting configuration
  Errors were encountered while processing:
   apport
  ssr@PC3248 ~/gdrive-local/mgmt/admin/info $ sudo apt-get install apport
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be upgraded:
apport
  1 upgraded, 0 newly installed, 0 to remove and 23 not upgraded.
  1 not fully installed or removed.
  Need to get 0 B/121 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 430429 files and directories currently installed.)
  Preparing to unpack .../apport_2.20.4-0ubuntu4.1_all.deb ...
File "/usr/bin/pyclean", line 63
  except (IOError, OSError), e:
   ^
  SyntaxError: invalid syntax
  dpkg: warning: subprocess old pre-removal script returned error exit status 1
  dpkg: trying script from the new package instead ...
File "/usr/bin/pyclean", line 63
  except (IOError, OSError), e:
   ^
  SyntaxError: invalid syntax
  dpkg: error processing archive 
/var/cache/apt/archives/apport_2.20.4-0ubuntu4.1_all.deb (--unpack):
   subprocess new pre-removal script returned error exit status 1
  Traceback (most recent call last):
File "/usr/bin/pycompile", line 35, in 
  from debpython.version import SUPPORTED, debsorted, vrepr, \
File "/usr/share/python/debpython/version.py", line 24, in 
  from ConfigParser import SafeConfigParser
  ImportError: No module named 'ConfigParser'
  *** Error in `/usr/bin/dpkg': munmap_chunk(): invalid pointer: 
0x56449feb52e8 ***
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(+0x7908b)[0x7ff8ca09608b]
  /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1f8)[0x7ff8ca0a32d8]
  /usr/bin/dpkg(+0x20cd0)[0x56449dd54cd0]
  /usr/bin/dpkg(+0x21119)[0x56449dd55119]
  /usr/bin/dpkg(+0x283cd)[0x56449dd5c3cd]
  /usr/bin/dpkg(+0x17737)[0x56449dd4b737]
  /usr/bin/dpkg(+0x17915)[0x56449dd4b915]
  /usr/bin/dpkg(+0x17b5d)[0x56449dd4bb5d]
  /usr/bin/dpkg(+0xaed7)[0x56449dd3eed7]
  /usr/bin/dpkg(+0x20c0b)[0x56449dd54c0b]
  /usr/bin/dpkg(+0x20e01)[0x56449dd54e01]
  /usr/bin/dpkg(+0xa962)[0x56449dd3e962]
  /usr/bin/dpkg(+0x72fd)[0x56449dd3b2fd]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7ff8ca03d3f1]
  /usr/bin/dpkg(+0x743a)[0x56449dd3b43a]
  === Memory map: 
  56449dd34000-56449dd79000 r-xp  fd:00 4718628
/usr/bin/dpkg
  56449df79000-56449df7c000 r--p 00045000 fd:00 4718628
/usr/bin/dpkg
  56449df7c000-56449df7d000 rw-p 00048000 fd:00 4718628
/usr/bin/dpkg
  56449df7d000-56449e191000 rw-p  00:00 0 
  56449f79-5644a454c000 rw-p  00:00 0  
[heap]
  7ff8c8879000-7ff8c888f000 r-xp  fd:00 6816526
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7ff8c888f000-7ff8c8a8e000 ---p 00016000 fd:00 6816526
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7ff8c8a8e000-7ff8c8a8f000 r--p 00015000 fd:00 6816526
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7ff8c8a8f000-7ff8c8a9 rw-p 00016000 fd:00 6816526
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7ff8c8a9-7ff8c8e1c000 rw-p  00:00 0 
  7ff8c8e1c000-7ff8c8e27000 r-xp  fd:00 6817463
/lib/x86_64-linux-gnu/libnss_files-2.24.so
  7ff8c8e27000-7ff8c9026000 ---p b000 fd:00 6817463
/lib/x86_64-linux-gnu/libnss_files-2.24.so
  7ff8c9026000-7ff8c9027000 r--p a000 fd:00 6817463
/lib/x86_64-linux-gnu/libnss_files-2.24.so
  7ff8c9027000-7ff8c9028000 rw-p b000 fd:00 6817463
/lib/x86_64-linux-gnu/libnss_files-2.24.so
  7ff8c9028000-7ff8c902e000 rw-p  00:00 0 
  7ff8c902e000-7ff8c9039000 r-xp  fd:00 6817465
/lib/x86_64-linux-gnu/libnss_nis-2.24.so
  7ff8c9039000-7ff8c9238000 ---p b000 fd:00 6817465
/lib/x86_64-linux-gnu/libnss_nis-2.24.so
  7ff8c9238000-7ff8c9239000 r--p a000 fd:00 6817465
/lib/x86_64-linux-gnu/libnss_nis-2.24.so
  7ff8c9239000-7ff8c923a000 rw-p b000 fd:00 6817465
/lib/x86_64-linux-gnu/libnss_nis-2.24.so
  7ff8c923a000-7ff8c925 r-xp  fd:00 6817460
/lib/x86_64-linux-gnu/libnsl-2.24.so
  

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

[Eric Desrochers]

** Description changed:

  [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 in 3.00s
  OpenSSL 1.0.2g 1 Mar 2016
  built on: reproducible build, date unspecified
  options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) 
blowfish(idx)
  compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT 
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall 
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM 
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
  The 'numbers' are in 1000s of bytes per second processed.
  type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
  sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55
  
  The performance are clearly better when using the patch which take
  benefit of the sha extension. (See Regression Potential section for
  result with patch)
  
  [Regression Potential]
  
   * Note : IRC discussion with infinity :
  
https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/comments/8
  
   * Note from irc discussion with apw and rbasak :
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/comments/2
  
   * It basically allow openssl to take benefit of sha extension potential
  (mostly performance-wise) now that new AMD cpu starting  to have the
  capability.
  
  * The code check the CPUID bit to determine if the sha instructions are
  available are not.
  
  * Maintainer comment proves that he did the successfully tested on Intel
  with/without SHA extension
  
  Reference: https://github.com/openssl/openssl/issues/2848
  "I don't have access to Ryzen system, so I didn't test it explicitly on 
Ryzen. Reporter did confirm it tough. Myself I tested on Intel processors, yes, 
with/without."
  
  * LP reporter comment :
  I, slashd, have tested on a Ryzen system (and AMD non-ryzen) and non-sha 
INTEL cpu. It does reveal a significant performance increase on Ryzen due to 
the sha extension :
  

[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Łukasz Zemczak]

Anyone else can reproduce the issue on yakkety as-is and can test the
-proposed dbus packages? They're a bit stuck in -proposed for too long.

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Fix Released
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Fix Committed
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  [Impact]

  The bug affects multiple users and introduces an user visible delay
  (~25 seconds) on SSH connections after a large number of sessions have
  been processed. This has a serious impact on big systems and servers
  running our software.

  The currently proposed fix is actually a safe workaround for the bug
  as proposed by the dbus upstream. The workaround makes uid 0 immune to
  the pending_fd_timeout limit that kicks in and causes the original
  issue.

  [Test Case]

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  Then checking the log file if there are any ssh sessions that are
  taking 25+ seconds to complete.

  Multiple instances of the same script can be used at the same time.

  [Regression Potential]

  The fix has a rather low regression potential as the workaround is a
  very small change only affecting one particular case - handling of uid
  0. The fix has been tested by multiple users and has been around in
  zesty for a while, with multiple people involved in reviewing the
  change. It's also a change that has been proposed by upstream.

  [Original Description]

  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  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

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

-- 
Mailing list: 

[Touch-packages] [Bug 1621216] Re: [MIR] geoclue-2.0

[Didier Roche]

Override component to main
iio-sensor-proxy 2.2-0ubuntu1 in artful: universe/misc -> main
iio-sensor-proxy 2.2-0ubuntu1 in artful amd64: universe/utils/optional/100% -> 
main
iio-sensor-proxy 2.2-0ubuntu1 in artful arm64: universe/utils/optional/100% -> 
main
iio-sensor-proxy 2.2-0ubuntu1 in artful armhf: universe/utils/optional/100% -> 
main
iio-sensor-proxy 2.2-0ubuntu1 in artful i386: universe/utils/optional/100% -> 
main
iio-sensor-proxy 2.2-0ubuntu1 in artful ppc64el: universe/utils/optional/100% 
-> main
iio-sensor-proxy 2.2-0ubuntu1 in artful s390x: universe/utils/optional/100% -> 
main
Override [y|N]? y
*7 publications overridden.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is a bug assignee.
https://bugs.launchpad.net/bugs/1621216

Title:
  [MIR] geoclue-2.0

Status in geoclue package in Ubuntu:
  New
Status in geoclue-2.0 package in Ubuntu:
  Fix Released
Status in iio-sensor-proxy package in Ubuntu:
  Fix Released

Bug description:
  libqt5positioning5 now recommends geoclue-2.0

  +qtlocation-opensource-src (5.6.0-1) experimental; urgency=medium
  +
  +  [ Lisandro Damián Nicanor Pérez Meyer ]
  +  * New upstream release.
  +- Bump Qt build dependencies.
  +  * Make qtlocation5-examples depend on qml-module-qtpositioning.
  +  * Make libqt5positioning5 recommend geoclue-2.0. It will connect to it by
  +using dbus.

  geoclue-2.0 was previously in main see the MIR for it in bug #1388294.

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

-- 
Mailing list: https://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 1629226] Re: Bash exits after a few failed fork()-s

[Manoj Iyer]

** Tags added: ubuntu-17.04

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

Title:
  Bash exits after a few failed fork()-s

Status in The Ubuntu-power-systems project:
  New
Status in bash package in Ubuntu:
  Invalid

Bug description:
  Problem Description
  ===
  I write a simple systemd service which will fork child processes fiercely. 
But quickly the service failed:

  % sudo systemctl status reproducer.service
  ? reproducer.service - Reproducer of systemd services killed by ips
 Loaded: loaded (/etc/systemd/system/reproducer.service; disabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Fri 2016-03-18 06:58:37 CDT; 2min 
43s ago
Process: 5103 ExecStart=/home/hpt/reproducer/reproducer.sh (code=exited, 
status=0/SUCCESS)
   Main PID: 5105 (code=exited, status=254)

  Mar 18 06:58:36 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:36 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 systemd[1]: reproducer.service: Main process exited, 
code=exited, status=254/n/a
  Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: 
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
  Mar 18 06:58:37 pinelp3 systemd[1]: reproducer.service: Unit entered failed 
state.
  Mar 18 06:58:37 pinelp3 systemd[1]: reproducer.service: Failed with result 
'exit-code'.

  The default task limit of systemd services is 512. Looks like the
  service is terminated by the kernel's ips cgroup controller. I think
  this isn't correct. Child processes cannot be forked shouldn't cause
  parent to die.

  
  % cat /etc/systemd/system/reproducer.service 
  [Unit]
  Description=Reproducer of systemd services killed by ips
  After=multi-user.target

  [Service]
  ExecStart=/home/hpt/reproducer/reproducer.sh
  Type=forking

  [Install]
  WantedBy=multi-user.target

  % cat /home/hpt/reproducer/reproducer.sh
  #!/bin/bash

  foo()
  {
  #exec sh -c "echo $1: \$\$;sleep 60"
  echo $1: 
  sleep 60
  }

  bar()
  {
  c=1
  while true
  do
  for ((i=1;i<=2048;i++))
  do
  foo $c &
  ((c++))
  done

  wait
  c=1
  done
  }

  # main
  bar &

  disown -a

  exit 0

  
  ---uname output---
  Linux pinelp3 4.4.0-12-generic #28-Ubuntu SMP Wed Mar 9 00:40:38 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = IBM,8408-E8E,lpar 

  Steps to Reproduce
  
  1. install the simple service in "Problem description"
  2. sudo systemctl start reproducer.service
  3. wait 2~3 minutes
   
  == Comment: #3 - Vaishnavi Bhat  - 2016-03-22 11:21:55 ==
  From the machine,
  root@pinelp3:~# ulimit -a
  core file size  (blocks, -c) 0
  data seg size   (kbytes, -d) unlimited
  scheduling priority (-e) 0
  file size   (blocks, -f) unlimited
  pending signals (-i) 48192
  max locked memory   (kbytes, -l) 64
  max memory size (kbytes, -m) unlimited
  open files  (-n) 1024
  pipe size(512 bytes, -p) 8
  POSIX message queues (bytes, -q) 819200
  real-time priority  (-r) 0
  stack size  (kbytes, -s) 8192
  cpu time   (seconds, -t) unlimited
  max user processes  (-u) 48192
  virtual memory  (kbytes, -v) unlimited
  file locks  (-x) unlimited

  root@pinelp3:~# ps aux | wc -l  ->While the service is 
running 
  1084
  root@pinelp3:~# ps aux | wc -l   "
  1084
  root@pinelp3:~# ps aux | wc -l   "
  1084
  root@pinelp3:~# ps aux | wc -l   "
  1084
  root@pinelp3:~# ps aux | wc -l-->While the service is not 
running. 
  572

  root@pinelp3:~# free -m   --> While service is running
totalusedfree  shared  buff/cache   
available
  Mem:  12117 628 459  22   11029
9541
  Swap:  2052   82044

  

[Touch-packages] [Bug 1694991] Re: Replace Unity with Gnome Shell

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-meta - 1.383

---
ubuntu-meta (1.383) artful; urgency=medium

  * Remove Unity & associated component to remplace it with Gnome Shell
(LP: #1694991).
  * Refreshed dependencies
  * Removed notify-osd from desktop
  * Removed overlay-scrollbar-gtk2 from desktop-recommends
  * Removed unity from desktop [amd64 arm64 armhf i386 ppc64el]
  * Removed unity-control-center from desktop [amd64 arm64 armhf i386
ppc64el]
  * Removed unity-settings-daemon from desktop
  Bye bye Unity, it has been a long and fun ride: from the Unity0 in
  vala+mutter for Ubuntu Netbook Edition, to Unity1 becoming Unity7
  with the compiz C++ rewrite and Nux additions. We had our load of fun,
  joy, sadness, crazyness… without forgetting crashes as well!
  Remember those shaders, those overlay scrollbars, those window stack issues,
  those 5am releases? And synchronizing you with the Unity2D team!
  Thanks to everyone involved, all those still here, those who left.

 -- Didier Roche   Thu, 01 Jun 2017 15:43:44 +0200

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Replace Unity with Gnome Shell

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Replace Unity with Gnome Shell in artful, as per
  https://insights.ubuntu.com/2017/04/05/growing-ubuntu-for-cloud-and-
  iot-rather-than-phone-and-convergence/.

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

-- 
Mailing list: https://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 1176046] Re: isc-dhcp dhclient listens on extra random ports

[Launchpad Bug Tracker]

This bug was fixed in the package isc-dhcp - 4.3.3-5ubuntu12.7

---
isc-dhcp (4.3.3-5ubuntu12.7) xenial; urgency=medium

  * debian/control : Add "Replaces:" option for package isc-dhcp-client
to allow the packaging system to remove "isc-dhcp-client-noddns" on
systems on which it is installed and replace it by "isc-dhcp-client"
during a release upgrade from Trusty to Xenial. (LP: #1176046)

 -- Eric Desrochers   Wed, 01 Feb 2017
08:36:18 -0500

** Changed in: isc-dhcp (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  isc-dhcp dhclient listens on extra random ports

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

Bug description:
  [Impact]

  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.

  Impact reported by users :

  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."

  There is a randomization mechanism in libdns that prevent dhclient to
  take the sysctl values into account (net.ipv4.ip_local_port_range &
  net.ipv4.ip_local_reserved_ports) to workaround this, and after
  discussion isc-dhcp upstream doesn't want to rely on kernel for
  randomization.

  There is no realtime configuration to disable the feature or
  workaround this. The only possible way is at compile time.

  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.

  Xenial has separated dhclient in two packages :

  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)

  The goal here is to reproduce the same situation in Trusty, for this
  bug to be less painful for at least users that doesn't require DDNS
  functionnality.

  [Test Case]

  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common

  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```

  [Regression Potential]

  I did the split such that Trusty users will automatically get "isc-
  dhcp-client-ddns" installed but users bothered by this bug will have
  the option to switch to "isc-dhcp-client-noddns".

  Existing Trusty users can continue to use this DDNS functionality
  after the SRU without any necessary intervention.

  With isc-dhcp-client:
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port

  With isc-dhcp-client-noddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc

  Xenial also has both distinct dhclient binary package but in the
  opposite way. We have decided to use the opposite way approach for not
  impacting actual Trusty users by changing the nature of isc-dhcp-
  client itself.

  Caribou and I, slashd, have also tested a couple of release upgrades from 
Trusty to Xenial with both scenarios :
  1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns"
  2 - Trusty upgrade to Xenial with "isc-dhcp-client-noddns"

  and both scenarios worked as expected for caribou and I. (See comment
  #42)

  Results :
  ===
  ** Upgrade tested with isc-dhcp-client **

  # dpkg -l
  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

  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:20114   0.0.0.0:* 
  632/dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  632/dhclient
  udp6   0  0 :::52249:::*  
  632/dhclient

  After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2)
  ii  isc-dhcp-client  4.3.3-5ubuntu12.7
  amd64DHCP client for automatically obtaining an IP 

[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports

[Launchpad Bug Tracker]

This bug was fixed in the package isc-dhcp - 4.2.4-7ubuntu12.10

---
isc-dhcp (4.2.4-7ubuntu12.10) trusty; urgency=medium

  * Introduction of a new binary package "isc-dhcp-client-noddns" (LP: #1176046)
- isc-dhcp-client : no behavioural change from previous version.
- isc-dhcp-client-noddns : dhclient with DDNS functionality disabled.

The current functionality in Trusty is to provide DDNS to dhclient by
default. Note that, this is the opposite in Xenial where dhclient,
by default, offers no DDNS functionality.

  * Disable tracing and failover.

The tracing and failover are stricly disabled for the new package
"isc-dhcp-client-noddns" and doesn't apply to package "isc-dhcp-client".

In order to successfully build "isc-dhcp-client-noddns" without
-DNSUPDATE and stay align with upstream Debian git commit [0bbf7c7]
(closes: #712503) which implies the following:

- debian/rules : Disable support for failover
  (DHCP Failover is a mechanism whereby two DHCP servers are both configured
  to manage the same pool of addresses so that they can share the load of
  assigning leases for that pool, and provide back-up for each other in case
  of network outages.
  (Define to include Failover Protocol support)

- debian/rules : Disable support for server activity tracing
  (Server tracing support)

  * CFLAGS configuration change
- debian/rules : Add backslash '\' characters for CLAGS options :
  "-D_PATH_DHCLIENT_CONF" , "-D_PATH_DHCPD_CONF" , "-D_PATH_DHCLIENT_SCRIPT"
  to avoid compilation errors expression before '/' token is expected at
  compile time.
- debian/rules : Remove "export CLAGS" line, since it is now passing during
  ./configure in order to control when compiling with or without DDNS
  functionality.

 -- Eric Desrochers   Wed, 24 May 2017
08:41:07 -0400

** Changed in: isc-dhcp (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  isc-dhcp dhclient listens on extra random ports

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

Bug description:
  [Impact]

  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.

  Impact reported by users :

  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."

  There is a randomization mechanism in libdns that prevent dhclient to
  take the sysctl values into account (net.ipv4.ip_local_port_range &
  net.ipv4.ip_local_reserved_ports) to workaround this, and after
  discussion isc-dhcp upstream doesn't want to rely on kernel for
  randomization.

  There is no realtime configuration to disable the feature or
  workaround this. The only possible way is at compile time.

  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.

  Xenial has separated dhclient in two packages :

  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)

  The goal here is to reproduce the same situation in Trusty, for this
  bug to be less painful for at least users that doesn't require DDNS
  functionnality.

  [Test Case]

  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common

  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```

  [Regression Potential]

  I did the split such that Trusty users will automatically get "isc-
  dhcp-client-ddns" installed but users bothered by this bug will have
  the option to switch to "isc-dhcp-client-noddns".

  Existing Trusty users can continue to use this DDNS functionality
  after the SRU without any necessary intervention.

  With isc-dhcp-client:
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port

  With isc-dhcp-client-noddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP 

[Touch-packages] [Bug 1176046] Update Released

[Łukasz Zemczak]

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

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

Title:
  isc-dhcp dhclient listens on extra random ports

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

Bug description:
  [Impact]

  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.

  Impact reported by users :

  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."

  There is a randomization mechanism in libdns that prevent dhclient to
  take the sysctl values into account (net.ipv4.ip_local_port_range &
  net.ipv4.ip_local_reserved_ports) to workaround this, and after
  discussion isc-dhcp upstream doesn't want to rely on kernel for
  randomization.

  There is no realtime configuration to disable the feature or
  workaround this. The only possible way is at compile time.

  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.

  Xenial has separated dhclient in two packages :

  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)

  The goal here is to reproduce the same situation in Trusty, for this
  bug to be less painful for at least users that doesn't require DDNS
  functionnality.

  [Test Case]

  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common

  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```

  [Regression Potential]

  I did the split such that Trusty users will automatically get "isc-
  dhcp-client-ddns" installed but users bothered by this bug will have
  the option to switch to "isc-dhcp-client-noddns".

  Existing Trusty users can continue to use this DDNS functionality
  after the SRU without any necessary intervention.

  With isc-dhcp-client:
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port

  With isc-dhcp-client-noddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc

  Xenial also has both distinct dhclient binary package but in the
  opposite way. We have decided to use the opposite way approach for not
  impacting actual Trusty users by changing the nature of isc-dhcp-
  client itself.

  Caribou and I, slashd, have also tested a couple of release upgrades from 
Trusty to Xenial with both scenarios :
  1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns"
  2 - Trusty upgrade to Xenial with "isc-dhcp-client-noddns"

  and both scenarios worked as expected for caribou and I. (See comment
  #42)

  Results :
  ===
  ** Upgrade tested with isc-dhcp-client **

  # dpkg -l
  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

  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:20114   0.0.0.0:* 
  632/dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  632/dhclient
  udp6   0  0 :::52249:::*  
  632/dhclient

  After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2)
  ii  isc-dhcp-client  4.3.3-5ubuntu12.7
  amd64DHCP client for automatically obtaining an IP address
  ii  isc-dhcp-common  4.3.3-5ubuntu12.7
  amd64common files 

[Touch-packages] [Bug 1694991] Re: Replace Unity with Gnome Shell

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  Replace Unity with Gnome Shell

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Replace Unity with Gnome Shell in artful, as per
  https://insights.ubuntu.com/2017/04/05/growing-ubuntu-for-cloud-and-
  iot-rather-than-phone-and-convergence/.

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

-- 
Mailing list: https://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 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

[dann frazier]

On Thu, Jun 1, 2017 at 7:27 AM, Zhanglei Mao  wrote:
> Daniel,
>
> It is really good. For patch driver and new kernel buiding, I cc Dann on the
> mail too, he is our engineer for this enablement project with Hisilicon.
> This is pearl kernel was build by him too.
>
> Dann,
>
> Can you patch and build out a new kernel for us or help Daniel to build a
> new testing kernel.

The latest zesty kernel works fine on the HiSilicon board, I'd suggest
patching that for your testing.

  -dann

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

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

-- 
Mailing list: https://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 1694989] Re: apt-mark overwrites existing held package info

[Julian Andres Klode]

Yup, something odd is going on there.

** Changed in: apt (Ubuntu)
   Status: New => Triaged

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

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

Title:
  apt-mark overwrites existing held package info

Status in apt package in Ubuntu:
  Triaged

Bug description:
  Running apt-mark hold commands overwrites / nullifies any existing
  held package data. Not sure if this is by design, but I assume it's
  meant to be cumulative.

  Ubuntu version: 16.04.2 LTS
  Package version: apt 1.2.19 amd64

  Expected behaviour:

  apt-mark hold 3dchess
  apt-mark hold 0ad
  apt-mark showhold

  3dchess
  0ad

  Actual behaviour:

  apt-mark hold 3dchess
  apt-mark hold 0ad
  apt-mark showhold

  0ad

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

-- 
Mailing list: https://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 1694991] [NEW] Replace Unity with Gnome Shell

[Didier Roche]

Public bug reported:

Replace Unity with Gnome Shell in artful, as per
https://insights.ubuntu.com/2017/04/05/growing-ubuntu-for-cloud-and-iot-
rather-than-phone-and-convergence/.

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

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

Title:
  Replace Unity with Gnome Shell

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Replace Unity with Gnome Shell in artful, as per
  https://insights.ubuntu.com/2017/04/05/growing-ubuntu-for-cloud-and-
  iot-rather-than-phone-and-convergence/.

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

-- 
Mailing list: https://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 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

[Zhanglei Mao]

Daniel,

It is really good. For patch driver and new kernel buiding, I cc Dann on
the mail too, he is our engineer for this enablement project with
Hisilicon. This is pearl kernel was build by him too.

Dann,

Can you patch and build out a new kernel for us or help Daniel to build a
new testing kernel.

For the new kernel install, I should be able to set it up.

thanks,
Mao

On Thu, Jun 1, 2017 at 7:56 PM, Daniel Axtens 
wrote:

> Ok, so I think part of the problem is that the kernel hibmc driver needs
> to use a set_busid function from the drm core. I've simulated this
> change in the debugger, and it seems to at least prevent the crash. (It
> doesn't seem to be enough for the server to work, still working on
> that.)
>
> Here's a patch - we can discuss the best way to build and install it.
>
> ** Patch added: "0001-Use-standard-busid-function-from-drm-core.patch"
>https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/
> 1691991/+attachment/4887275/+files/0001-Use-standard-busid-
> function-from-drm-core.patch
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1691991
>
> Title:
>   Xorg Segmentation fault on Hisilicon D05 board (arm64)
>
> Status in xorg package in Ubuntu:
>   New
>
> Bug description:
>   ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg
>   [sudo] password for ubuntu:
>
>   X.Org X Server 1.18.4
>   Release Date: 2016-07-19
>   X Protocol Version 11, Revision 0
>   Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
>   Current Operating System: Linux ubuntu 4.10.0-20.22-generic
> #22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
>   Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic
> root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug
> earlycon=pl011,mmio,0x602B console=tty0
>   Build Date: 02 November 2016  10:05:28PM
>   xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see
> http://www.ubuntu.com/support)
>   Current version of pixman: 0.33.6
> Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
>   Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>   (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>   pci id for fd 10: 19e5:1711, driver (null)
>   EGL_MESA_drm_image required.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
>   (EE)
>   (EE) Segmentation fault at address 0xa0
>   (EE)
>   Fatal server error:
>   (EE) Caught signal 11 (Segmentation fault). Server aborting
>   (EE)
>   (EE)
>   Please consult the The X.Org Foundation support
>  at http://wiki.x.org
>for help.
>   (EE) Please also check the log file at "/var/log/Xorg.0.log" for
> additional information.
>   (EE)
>   (EE) Server terminated with error (1). Closing log file.
>   Aborted (core dumped)
>   ubuntu@ubuntu:~$
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+subscriptions
>


-- 
Zhanglei Mao
Solutions Architect, Sales and Business Development
Canonical Group Ltd.
zhanglei@canonical.com
+86-13625010929 (m)
+852-6700 6026 (m)
www.ubuntu.com
www.canonical.com

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver 

[Touch-packages] [Bug 1694989] [NEW] apt-mark overwrites existing held package info

[Matthew North]

Public bug reported:

Running apt-mark hold commands overwrites / nullifies any existing held
package data. Not sure if this is by design, but I assume it's meant to
be cumulative.

Ubuntu version: 16.04.2 LTS
Package version: apt 1.2.19 amd64

Expected behaviour:

apt-mark hold 3dchess
apt-mark hold 0ad
apt-mark showhold

3dchess
0ad

Actual behaviour:

apt-mark hold 3dchess
apt-mark hold 0ad
apt-mark showhold

0ad

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

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

Title:
  apt-mark overwrites existing held package info

Status in apt package in Ubuntu:
  New

Bug description:
  Running apt-mark hold commands overwrites / nullifies any existing
  held package data. Not sure if this is by design, but I assume it's
  meant to be cumulative.

  Ubuntu version: 16.04.2 LTS
  Package version: apt 1.2.19 amd64

  Expected behaviour:

  apt-mark hold 3dchess
  apt-mark hold 0ad
  apt-mark showhold

  3dchess
  0ad

  Actual behaviour:

  apt-mark hold 3dchess
  apt-mark hold 0ad
  apt-mark showhold

  0ad

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

-- 
Mailing list: https://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 1533631] Re: dhclient killed when DHCPv6 lease is out-of date

[Roman]

root@gw:~# cat /var/lib/dhcp/dhclient6.br1.leases
default-duid "\000\001\000\001 \302\271\313\000\002D\032>\251";
lease6 {
  interface "br1";
  ia-na 44:1a:3e:a9 {
starts 1496317261;
renew 900;
rebind 1500;
iaaddr 2a02:2168:82d:949::1 {
  starts 1496317261;
  preferred-life 1800;
  max-life 1800;
}
  }
  option dhcp6.client-id 0:1:0:1:20:c2:b9:cb:0:2:44:1a:3e:a9;
  option dhcp6.server-id 0:3:0:1:0:16:4d:7e:df:5c;
  option dhcp6.name-servers 2a02:2168:208:1::1,2a02:2168:208:2::1;
}

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

Title:
  dhclient killed when DHCPv6 lease is out-of date

Status in NetworkManager:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Network Manager summarily kills the IPv6 dhclient process when the
  DHCPv6 lease contained in the dhclient6-${UUID}.lease file is out-of
  date, leaving the IPv6 interface without a stateful IPv6 address, or,
  if the "require IPv6 address on this interface" option is enabled,
  causes NM to cycle continuously deactivating and reactivating the
  interface (including the IPv4 addresses).

  This is effectively a Denial Of Service. It can be trivially induced
  if, for example, the dhclient6-$(UUID}.lease file contains a lease
  that was issued before the user went away on vacation or the PC wasn't
  connected to the same network for a few days (depending on the lease
  renew/rebind/expiry times). Calculation on the old lease of

  start + preferred_lifetime < NOW

  triggers dhclient to 'DEPREFER6' the lease (withdraw the address
  record) and ask the DHCPv6 server for a new lease, but Network Manager
  will kill the dhclient because it only sees an 'EXPIRE6' state change.

  In summary, when the DHCPv6 state transitions from "bound" to
  "unknown" then "expire" to "done" Network Manager kills the 'dhclient'
  process before it has chance to request and bind a fresh lease, If
  'dhclient' is run manually with the same command-line options and
  allowed to continue running it correctly gains a new lease.

  Network Manager doesn't know how to handle "DEPREF6", which is sent
  from isc-dhcp dhclient to the helper script (set by "-sf" option).

  So it seems that to correctly solve this issue Network Manager must be
  taught how to handle DEPREF6.

  /var/log/syslog will show a message from dhclient of the form:

  dhclient: PRC: Address 2a02:8011:2007::2 depreferred.

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

-- 
Mailing list: https://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 1533631] Re: dhclient killed when DHCPv6 lease is out-of date

[Roman]

I have no Network Manager in Ubuntu server 16.04 LTS, but this bug present.
After booting where is no dhclient in the processes if accept_ra set to 2 and 
syslog contains 

Jun  1 13:55:33 gw dhclient[3663]: PRC: Prefix 2a02:2168:176b:4800::/56 
depreferred.
Jun  1 14:05:44 gw dhclient[2762]: PRC: Address 2a02:2168:82d:949::4 
depreferred.

if i remove setting accept_ra from sysctl on same leases all works fine
except of course DHCP-PD.

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

Title:
  dhclient killed when DHCPv6 lease is out-of date

Status in NetworkManager:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Network Manager summarily kills the IPv6 dhclient process when the
  DHCPv6 lease contained in the dhclient6-${UUID}.lease file is out-of
  date, leaving the IPv6 interface without a stateful IPv6 address, or,
  if the "require IPv6 address on this interface" option is enabled,
  causes NM to cycle continuously deactivating and reactivating the
  interface (including the IPv4 addresses).

  This is effectively a Denial Of Service. It can be trivially induced
  if, for example, the dhclient6-$(UUID}.lease file contains a lease
  that was issued before the user went away on vacation or the PC wasn't
  connected to the same network for a few days (depending on the lease
  renew/rebind/expiry times). Calculation on the old lease of

  start + preferred_lifetime < NOW

  triggers dhclient to 'DEPREFER6' the lease (withdraw the address
  record) and ask the DHCPv6 server for a new lease, but Network Manager
  will kill the dhclient because it only sees an 'EXPIRE6' state change.

  In summary, when the DHCPv6 state transitions from "bound" to
  "unknown" then "expire" to "done" Network Manager kills the 'dhclient'
  process before it has chance to request and bind a fresh lease, If
  'dhclient' is run manually with the same command-line options and
  allowed to continue running it correctly gains a new lease.

  Network Manager doesn't know how to handle "DEPREF6", which is sent
  from isc-dhcp dhclient to the helper script (set by "-sf" option).

  So it seems that to correctly solve this issue Network Manager must be
  taught how to handle DEPREF6.

  /var/log/syslog will show a message from dhclient of the form:

  dhclient: PRC: Address 2a02:8011:2007::2 depreferred.

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

-- 
Mailing list: https://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 972077] Re: apt repository disk format has race conditions

[Robie Basak]

On Thu, Jun 01, 2017 at 07:20:18AM -, Abhijith Gururaj wrote:
> @juliank I have configured the updater to use the main server.
> Downloading updates from the main server shouldn't cause such errors,
> right?

Some ISPs intercept their clients' downloads. The error is telling you
that the download appears to have been modified in transit, so isn't
safe to install. It cannot tell you why or where that happened,
unfortunately.

This bug was to track a known case of an index file appearing to have
been modified in transit due to a known race condition. That issue was
fixed, and it seems unlikely to me that you are affected by that
particular issue as your mismatch is on deb and not an index file.

If you need help, you're more likely to get it from a place dedicated to
that, since few people follow this particular bug. See
http://www.ubuntu.com/support/community for community support options.

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

Title:
  apt repository disk format has race conditions

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released

Bug description:
  Apt archives are accessed over HTTP; this has resulted in a cluster of
  bugs (reported here, and upstream) about problems behind intercepting
  caches, problems with squid etc.

  There are 3 interlocking issues:
  A - mirror networks may be out of sync with each other (e.g. a file named on 
one mirror may no longer exist, or may not yet exist, on another mirror)
  B - updating files on a single mirror is not atomic - and even small windows 
of inconsistency will, given enough clients, cause headaches.
  C - caches exacerbate race conditions - when one happens, until the cached 
data expires, all clients of the cache will suffer from the race

  Solving this requires one of several things:
   - file system transactions
   - an archive format that requires only weakly ordered updates to the files 
at particular urls with the assumption that only one file may be observed to 
change at a time (because a lookup of file A, then B, may get a cache miss on A 
and a cache hit on B, so even if all clients strictly go A, then B, updates may 
still see old files when paths are reused).
   - super robust clients that repeatedly retry with progressively less cache 
friendly headers until they have a consistent view. (This is very tricky to do).

  It may be possible to do a tweak to the apt repository format though,
  which would allow publishing a race-free format in parallel with the
  existing layout, while clients migrate. To be safe against issue (A)
  the mirror network would need some care around handling of dns round-
  robin mirrors [to minimise the situation where referenced data is not
  available], but this should be doable - or alternatively clients doing
  'apt-get update' may need to be willing to retry to accommodate round-
  robin skew.

  What would such an archive format look like?
  It would have only one well known file name (InRelease), which would be 
internally signed. Rather than signing e.g. Packages.gz, it would sign a 
uniquely named packages and sources file - e.g. Packages-$HASH.gz or 
Packages-$serialno.gz.

  Backwards compatibility is achieved by using the same filenames for
  deb's and the like. We need to keep writing Packages.gz though, and
  Releases, until we no longer worry about old apt clients. We can
  optimise disk space a little by making Packages.gz a symlink to a
  Packages-$HASH.gz (and so on for Sources..), but it may be simpler and
  less prone to unexpected behaviour to keep using regular files.

  tl;dr
   * Unique file names for all unique file content with one exception
   * InRelease, a self-signed file that provides hashes and names the index 
files (Packages, Sources, Translations etc)
   * Coexists with existing archive layout

  Related bugs:
   * bug 804252: Please support InRelease files
   * bug 1430011: support apt by-hash mirrors

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

-- 
Mailing list: https://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 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

[Elmar Isele]

my workaround is to switch from a2dp mode to headset, reconnect the
device to get a sink

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Incomplete
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

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

-- 
Mailing list: https://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 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

[Elmar Isele]

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename:   xenial

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Incomplete
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

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

-- 
Mailing list: https://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 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

[Daniel Axtens]

Ok, so I think part of the problem is that the kernel hibmc driver needs
to use a set_busid function from the drm core. I've simulated this
change in the debugger, and it seems to at least prevent the crash. (It
doesn't seem to be enough for the server to work, still working on
that.)

Here's a patch - we can discuss the best way to build and install it.

** Patch added: "0001-Use-standard-busid-function-from-drm-core.patch"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+attachment/4887275/+files/0001-Use-standard-busid-function-from-drm-core.patch

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

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

-- 
Mailing list: https://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 987003] Re: In Pangolin, a new administrator profile was not registred in the sudoer group (Lubuntu /Gnome environment)

[4tro]

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

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

Title:
  In Pangolin, a new administrator profile was not registred in the
  sudoer group (Lubuntu /Gnome environment)

Status in sudo package in Ubuntu:
  Invalid

Bug description:
  I recently installed Lubuntu 12.04 cause my old computer wasn't completly 
accepted by unfinity live-dvd due to its cd limit.
  So I installed Lubuntu-desktop-cd first quitly fine, with no matter.
  After that I installed Gnome 3. (perhaps this anomaly was in the lubuntu-sudo 
first ?)
  My first administrator was fine accepted as Sudoer.
  So I installed two new users and an another admin in the Gnome environment .
  But , when I tried a "sudo  aptitude" with this new "adm" profile, I 
discovered that the new administrator was not registred as sudoer : the message 
was "you are not a sudoer and I will make a report " and twice in synaptic or 
any command for admninistrator.

  So, I came back to verify these news status in the first admin's deskotp.
  In effect, the new admin was not registred in the "sudoer" group, but was 
registred in the "adm" group.

  First I put on the case for this new one in sudo and adm group.

  At the first try, the new admin sudoer registration "by hand" didn't took 
effect.
  I quitted and shutdown (as if in a simple ms boot-on system ;-) .
  And after reeboot, the new second admin was accepted as sudoer.
  So I thought I had to report this little anomaly before we have some newbes 
in trouble the D day.
  Perhaps wasn't due to succession of my manipulations or not ?
  So you have a part of answer, if it is.

  Good luck and long life for the Pangolin !

  Alter.md

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

-- 
Mailing list: https://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 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[MrGrummpy]

I have Blueman Bluetooth manager on my Ubuntu Mate laptop.
Is that the 'module' you were asking about?

On Wed, May 31, 2017 at 10:28 PM, Kai-Heng Feng  wrote:

> What Bluetooth module do you use?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1589008
>
> Title:
>   Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
>
> Status in linux package in Ubuntu:
>   Confirmed
> Status in pulseaudio package in Ubuntu:
>   Confirmed
>
> Bug description:
>   In 16.04 when a bluetooth audio device is connected it freezes video
>   playback and also no sound comes from online audio only streams. Issue
>   does not exist with a wired headset.
>
>   This issue does not exist with 15.10. All updates have been installed
>   on 16.04 including backports but they have not fixed the issue.
>
>   It is not browser specific and not website specific.
>
>   It is not hardware specific as it affects my laptop with an intel 7260
>   card and my pc with an intel 8260 card.
>
>   The issue exists on both ubuntu and kubuntu 16.04.
>
>   I have reported it on the ubuntu support forums and after
>   investigation a moderator noticed changed in the kernel from 4.4 and
>   4.2 that may becausing the issue and asked me to file a bug report.
>
>   The ubuntu forum thread can be found here.
>   http://ubuntuforums.org/showthread.php?t=2326672
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: linux-image-4.4.0-23-generic 4.4.0-23.41
>   ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
>   Uname: Linux 4.4.0-23-generic x86_64
>   NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
>   ApportVersion: 2.20.1-0ubuntu2.1
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  stephen1435 F pulseaudio
>/dev/snd/controlC0:  stephen1435 F pulseaudio
>   CurrentDesktop: KDE
>   Date: Fri Jun  3 23:50:00 2016
>   HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
>   InstallationDate: Installed on 2016-05-06 (28 days ago)
>   InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 003: ID 8087:0a2b Intel Corp.
>Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: MSI MS-7978
>   ProcFB: 0 EFI VGA
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed
> root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash
> vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-4.4.0-23-generic N/A
>linux-backports-modules-4.4.0-23-generic  N/A
>linux-firmware1.157
>   SourcePackage: linux
>   UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
>   dmi.bios.date: 05/16/2016
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: C.60
>   dmi.board.asset.tag: Default string
>   dmi.board.name: H170 GAMING M3 (MS-7978)
>   dmi.board.vendor: MSI
>   dmi.board.version: 2.0
>   dmi.chassis.asset.tag: Default string
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: MSI
>   dmi.chassis.version: 2.0
>   dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:
> pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
>   dmi.product.name: MS-7978
>   dmi.product.version: 2.0
>   dmi.sys.vendor: MSI
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1589008/+subscriptions
>


-- 
We do not err because truth is difficult to see. It is visible at a glance.
We err because this is more comfortable. -Alexander Solzhenitsyn, novelist,
Nobel laureate (1918-2008)

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

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

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug 

[Touch-packages] [Bug 1669601] Re: tracker-store crashed with SIGSEGV in tracker_db_interface_lock()

[Apport retracing service]

** Tags added: artful

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

Title:
  tracker-store crashed with SIGSEGV in tracker_db_interface_lock()

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  ok

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: tracker 1.11.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Thu Mar  2 19:16:52 2017
  ExecutablePath: /usr/lib/tracker/tracker-store
  InstallationDate: Installed on 2017-03-02 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: /usr/lib/tracker/tracker-store
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f294bba2210 
:   mov0xb0(%rdi),%esi
   PC (0x7f294bba2210) ok
   source "0xb0(%rdi)" (0x00b0) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   tracker_db_interface_execute_vquery () from 
/usr/lib/x86_64-linux-gnu/tracker-1.0/libtracker-data.so.0
   tracker_db_interface_execute_query () from 
/usr/lib/x86_64-linux-gnu/tracker-1.0/libtracker-data.so.0
   tracker_store_wal_checkpoint ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: tracker-store crashed with SIGSEGV in 
tracker_db_interface_execute_vquery()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 1694955] Re: tracker-store crashed with SIGSEGV in tracker_db_interface_execute_vquery()

[Apport retracing service]

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

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 #1669601, 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/1694955/+attachment/4887241/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1669601
   tracker-store crashed with SIGSEGV in tracker_db_interface_lock()

** 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 tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1694955

Title:
  tracker-store crashed with SIGSEGV in
  tracker_db_interface_execute_vquery()

Status in tracker package in Ubuntu:
  New

Bug description:
  tracker-store crashed with SIGSEGV in
  tracker_db_interface_execute_vquery()

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: tracker 1.12.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jun  1 10:36:30 2017
  ExecutablePath: /usr/lib/tracker/tracker-store
  InstallationDate: Installed on 2017-05-22 (10 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170521)
  ProcCmdline: /usr/lib/tracker/tracker-store
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f9d5ec57210 
:   mov0xb0(%rdi),%esi
   PC (0x7f9d5ec57210) ok
   source "0xb0(%rdi)" (0x00b0) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   tracker_db_interface_execute_vquery () from 
/usr/lib/x86_64-linux-gnu/tracker-1.0/libtracker-data.so.0
   tracker_db_interface_execute_query () from 
/usr/lib/x86_64-linux-gnu/tracker-1.0/libtracker-data.so.0
   tracker_store_wal_checkpoint ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: tracker-store crashed with SIGSEGV in 
tracker_db_interface_execute_vquery()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm lpadmin sambashare sudo

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

-- 
Mailing list: https://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 1694455] Re: Bluetooth: Cannot receive files, due to OBEX configuration

[Paul White]

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

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

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

Title:
  Bluetooth: Cannot receive files, due to OBEX configuration

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New

Bug description:
  # Use case

  Ubuntu 17.04, quite fresh installation, updated.

  Bluetooth file transmission

  I want to send files to my smartphone, and receive files sent by my
  smartphone via bluetooth. I pair both devices, initiate file transfer
  from one of the devices, and the other device asks me what to do.

  # Problems

  This is a mix from usability and technical issues.

  1. OBEX disabled

  The bluetooth file transmission service OBEX was not started. I started and 
enabled OBEX:
  `systemctl --user start obex`
  `systemctl --user enable obex`

  ```
  Mai 30 14:47:55 tp systemd[1661]: Starting Bluetooth OBEX service...
  Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43
  ```

  2. OBEX silently fails

  After having OBEX enabled, I was able to transmit files from laptop to
  smartphone, yet I could not receive files on the laptop. In the system
  log, you could see that OBEX fails (please note `FORBIDDEN`):

  ```
  Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43
  Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x)
  Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x0)
  Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), (null)(0x)
  Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), FORBIDDEN(0x43)
  Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), (null)(0x)
  Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20)
  Mai 30 14:48:04 tp obexd[8168]: disconnected: Transport got disconnected
  ```

  I did not receive a popup notification asking me to receive the file
  or not.

  In the file sharing preferences `gnome-file-share-properties`, there
  is a setting to automatically receive files via bluetooth. With this
  box checked, you're finally able to receive files from your
  smartphone.

  Successful log for comparison:
  ```
  Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x)
  Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x0)
  Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), (null)(0x)
  Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), CONTINUE(0x10)
  Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), (null)(0x)
  Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20)
  Mai 30 14:56:28 tp obexd[8168]: disconnected: Transport got disconnected
  ```

  # Expected behaviour

  OBEX is started by default to handle bluetooth file transfers.

  If no automatic file receipt is configured, a popup notification asks
  me if I want to receive the file or not.

  If this is not possible, there should be a notification pointing the
  user to the configuration.

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

-- 
Mailing list: https://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 1694455] [NEW] Bluetooth: Cannot receive files, due to OBEX configuration

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

# Use case

Ubuntu 17.04, quite fresh installation, updated.

Bluetooth file transmission

I want to send files to my smartphone, and receive files sent by my
smartphone via bluetooth. I pair both devices, initiate file transfer
from one of the devices, and the other device asks me what to do.

# Problems

This is a mix from usability and technical issues.

1. OBEX disabled

The bluetooth file transmission service OBEX was not started. I started and 
enabled OBEX:
`systemctl --user start obex`
`systemctl --user enable obex`

```
Mai 30 14:47:55 tp systemd[1661]: Starting Bluetooth OBEX service...
Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43
```

2. OBEX silently fails

After having OBEX enabled, I was able to transmit files from laptop to
smartphone, yet I could not receive files on the laptop. In the system
log, you could see that OBEX fails (please note `FORBIDDEN`):

```
Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43
Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x)
Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x0)
Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), (null)(0x)
Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), FORBIDDEN(0x43)
Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), (null)(0x)
Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20)
Mai 30 14:48:04 tp obexd[8168]: disconnected: Transport got disconnected
```

I did not receive a popup notification asking me to receive the file or
not.

In the file sharing preferences `gnome-file-share-properties`, there is
a setting to automatically receive files via bluetooth. With this box
checked, you're finally able to receive files from your smartphone.

Successful log for comparison:
```
Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x)
Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x0)
Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), (null)(0x)
Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), CONTINUE(0x10)
Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), (null)(0x)
Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20)
Mai 30 14:56:28 tp obexd[8168]: disconnected: Transport got disconnected
```

# Expected behaviour

OBEX is started by default to handle bluetooth file transfers.

If no automatic file receipt is configured, a popup notification asks me
if I want to receive the file or not.

If this is not possible, there should be a notification pointing the
user to the configuration.

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


** Tags: bot-comment zesty
-- 
Bluetooth: Cannot receive files, due to OBEX configuration
https://bugs.launchpad.net/bugs/1694455
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to bluez 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 1692315] Re: Package description is inaccurate

[Launchpad Bug Tracker]

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  Package description is inaccurate

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  unattended-upgrades 0.93.1ubuntu6

  "Description: automatic installation of security upgrades"

  This is now wrong for Ubuntu, since the default behaviour of the
  package is not restricted to security upgrades.

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

-- 
Mailing list: https://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 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows

[Julian Andres Klode]

OK, so 1.4.4 and friends actually enable debugging mode of unattended-
upgrade instead of a download-only mode. --dry-run is documented as only
doing downloads, but it also simulates the install and does verbose
logging, so that's not useful.

In 1.4.6, I modified apt.systemd.daily to check unattended-upgrade
--help for "download-only", and use that if it exists. This means that
with 1.4.6, everything should work once this is implemented in
unattended-upgrades.

I attached an early patch for unattended-upgrades (against the upstream
version), there might be issues with it other than missing translations
for --help.

** Patch added: "unattended-upgrade.diff"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+attachment/4887192/+files/unattended-upgrade.diff

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

Title:
  Apt updates that are uniformly spread across all timezones, with
  predictable application windows

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  Triaged
Status in unattended-upgrades source package in Xenial:
  Triaged
Status in apt source package in Yakkety:
  Triaged
Status in unattended-upgrades source package in Yakkety:
  Triaged
Status in apt source package in Zesty:
  Triaged
Status in unattended-upgrades source package in Zesty:
  Triaged
Status in apt source package in Artful:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Triaged
Status in apt package in Debian:
  New

Bug description:
  [ Impact ]

   * unattended-upgrades are enabled by default in Ubuntu 16.04 and
  later

   * Currently the following three things happen as a monolithic event:
     - metadata updates: apt update
     - download of updates: apt upgrade --download-only
     - application of updates: apt upgrade

   * For the long running instances, all of the above happens at random
     times throughout the day.

   * If systems were poweredoff / suspended, this happens on boot /
  resume

   * End-users would like to have predictable timing, and control over when
     the updates happen.

  Considering all of the above, the following new behavior is proposed
  which should address all concerns in question. It combines all the
  desired properties from both end-user and mirror perspectives.

  [ Proposed Default Behavior ]

   * Decouple unattended-upgrades application, from apt update

   * apt update:
     - shall be a systemd timer based unit, triggered every 12h with a
   random delay of 12h, therefore executed randomly twice a day.
     - if unattened-upgrades (default on), or download-upgreadaeble-packages
   are enabled, it should result in updates being downloaded aka
   `apt upgrade --download-only`

   * unattended-upgrades:
     - shall be a separate systemd timer based unit triggered at 6am local
   time with a random delay of 1h, therefore executed between 6am and
   7am local time.

   * On boot / resume:
     - if we have missed one, or more, apt update timers,
   apt update / download upgrades / unattended-upgrade will happen in
   sequence. This may result in mirror spikes, but we do want to secure
   cold/stale-booted systems as soon as possible.

  [Test Case]

   * Run system for more than 24h, and check that apt updates were
     automatically executed twice.

   * Check that unattended upgrades were triggered to be applied at
     6am..7am window, if any.

   * Poweroff the machine over the period when apt-get update was
     scheduled, poweron and observe that apt-get update / download / 
 unattended upgrade are all performed on boot.

  [Regression Potential]

   * The newly proposed behavior is a mix of Pre-xenial behavior of "do
     everything at 6am..6:30am window" and the xenial+ behavior of "do 
 everything at random times throughout the day". If there are specific 
 deployments that rely on the previous types of behaviour they will be 
 able to adjust manually the systemd timers with the overrides to be 
 executed exactly as they wish; or match the .0 release behaviour that 
 they preffer.

   * If timers behavior is coded wrongly the proposed behaviour might not be
     executed as intended, thus requiring further SRUs to bring us in-line
     with the great expectations.

  [Other Info]

    * Related bug reports and history:
  - bug #1615482
  - bug #1554848

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

-- 
Mailing list: https://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 660853] Re: [SigmaTel STAC9200] ALSA test tone not correctly played back

[madbiologist]

Official support for Ubuntu 10.10 "Maverick Meerkat" has ended.  If this
issue is still occurring on Ubuntu 17.04 "Zesty Zapus" please run
ubuntu-bug to file a new bug report so that we can get a fresh set of
log files and system information.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Invalid

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

Title:
  [SigmaTel STAC9200] ALSA test tone not correctly played back

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  After upgrading to Maverick, sound is not working at all

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: alsa-base 1.0.23+dfsg-1ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jota   1907 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 43'
 Mixer name : 'SigmaTel STAC9200'
 Components : 'HDA:83847690,10280201,00102201 
HDA:14f12c06,14f1000f,0010'
 Controls  : 12
 Simple ctrls  : 7
  CheckboxSubmission: 5b293c10f2841431018697f642f36e83
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  Date: Thu Oct 14 23:57:45 2010
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [SigmaTel STAC9200] ALSA test tone not correctly played back
  dmi.bios.date: 05/16/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0F331C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd05/16/2008:svnDellInc.:pnLatitudeD430:pvr:rvnDellInc.:rn0F331C:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D430
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1665322] Re: LDAP-based sudo roles stopped working in 16.04

[Oscar Carlberg]

I reported the same problem in #1682104, another way to work around this
is to use the sudo version in the release version of 16.04,
1.8.16-0ubuntu1. Would be very nice to get this resolved since we cannot
patch the sudo package right now in our systems.

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

Title:
  LDAP-based sudo roles stopped working in 16.04

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 14.04 LTS to 16.04 LTS, we noticed that LDAP-
  based sudo roles stopped working, meaning users that were able to use
  sudo in the past, are rejected now.

  After investigation, it turned out to be a known upstream bug:

  https://bugzilla.sudo.ws/show_bug.cgi?id=757

  which was introduced somewhere between 14.04 and 16.04 timelines.

  To cut the long story short, the code is trying to match FQDN host
  name (eg. "thehost.domain.com") against host name pattern provided in
  LDAP (eg. "sudoHost: thehost") using strcmpi, which will - obviously -
  fail.

  The fix is a single line change patch which found its way into sudo
  version 1.8.18:

  https://www.sudo.ws/repos/sudo/rev/605c03afc80f

  Unfortunately both 16.04 and 16.10 seem to only use 1.8.16 (17.04
  seemed to have jumped to 1.8.19) so will need to carry the patch
  mentioned above. Tested it locally and the re-built package with the
  patch added works fine. My debian/patches/series looks like this now:

  .../sudo-1.8.16$ cat debian/patches/series
  typo-in-classic-insults.diff
  paths-in-samples.diff
  keep_home_by_default.patch
  also_check_sudo_group.diff
  lp1565567.patch
  sssd-doesnt-handle-netgroups.diff
  sssd-fix-matching-loop.diff
  ldap-hostname.diff

  .../sudo-1.8.16$ cat debian/patches/ldap-hostname.diff
  # HG changeset patch
  # User Todd C. Miller 
  # Date 1473459982 21600
  # Node ID 605c03afc80f4c3f55bfae62fcf4974f18cd77e8
  # Parent  017866310d2486566cbde9f93486e788d0c046a8
  Fix typo that broke short host name matching when the fqdn
  flag is enabled.  Bug #757

  diff -r 017866310d24 -r 605c03afc80f plugins/sudoers/sudoers.c
  --- a/plugins/sudoers/sudoers.c   Thu Sep 08 16:38:08 2016 -0600
  +++ b/plugins/sudoers/sudoers.c   Fri Sep 09 16:26:22 2016 -0600
  @@ -1069,7 +1069,7 @@
    /* Not remote, just use user_host. */
    if ((lhost = strdup(user_host)) != NULL) {
    if (user_shost != user_host)
  - shost = strdup(lhost);
  + shost = strdup(user_shost);
    else
     shost = lhost;
    }

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

-- 
Mailing list: https://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 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

[Doug Morse]

I must unfortunately report that that the recently reported fix does not
work for me.  Ubuntu 16.04 LTS connecting to Amazon Echo.  Pulseaudio
1:8.0-0ubuntu3.3~xenial1, which is the latest presently available from
ppa:ubuntu-audio-dev/pulse-testing as of today.

The problem appears to result in the same conditions as I have comment
on in bug 1691556 and discussed at askubuntu.com
https://askubuntu.com/questions/871630/cant-send-audio-to-amazon-echo-
via-bluetooth

Here are the syslog entries from testing today after installing the
latest from pulseaudio-testing:

Jun  1 10:24:23 n1 bluetoothd[1031]: a2dp-source profile connect failed for 
50:F5:DA:A6:3F:EA: Device or resource busy
Jun  1 10:24:23 n1 kernel: [  423.337550] input: 50:F5:DA:A6:3F:EA as 
/devices/virtual/input/input22
Jun  1 10:24:26 n1 bluetoothd[1031]: /org/bluez/hci0/dev_50_F5_DA_A6_3F_EA/fd1: 
fd(23) ready
Jun  1 10:25:26 n1 pulseaudio[5001]: [pulseaudio] sink-input.c: Failed to 
create sink input: sink is suspended.
Jun  1 10:25:41 n1 kernel: [  500.946349] perf interrupt took too long (5021 > 
5000), lowering kernel.perf_event_max_sample_rate to 25000
Jun  1 10:25:28 n1 pulseaudio[5001]: message repeated 5 times: [ [pulseaudio] 
sink-input.c: Failed to create sink input: sink is suspended.]

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

Title:
  [xenial] Bluetooth device doesn't play any sound in A2DP mode unless
  set to HSP/HFP first

Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress

Bug description:
  [Impact]
  Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP 
first. A2DP is the high quality profile used for Bluetooth speakers and music 
in general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Verify in Sound settings you have it set to A2DP mode.
  3. Turn off and then on the Bluetooth device.
  4. Verify the device has reconnected and if not, force it to in the Bluetooth 
indicator menu.
  5. Open Sound settings again, select the device and verify it's reappeared in 
A2DP mode.
  6. Click 'Test Sound'.
  Expected: Sound can be heard from the Bluetooth device.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1438510. Possibly others too.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  I have a Sennheiser MM 450-X headset.

  In 15.10, connection & playback was straightforward.

  In 16.04, the headset connects, and shows up as default playback
  device on `pavucontrol`, but there is no sound.

  A functional workaround is to, after having connected it, to go the
  `Configuration` tab, and in the `Profile` dropdown, to choose `...
  HSP/HFP`, which will make them play as expected (but in low quality),
  then switch to `... A2DP Sink` (they will play in high quality).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  myuser2936 F pulseaudio
   /dev/snd/controlC2:  myuser2936 F pulseaudio
   /dev/snd/controlC0:  myuser2936 F pulseaudio
  Date: Mon May 16 14:18:58 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-11 (66 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No 

[Touch-packages] [Bug 1682104] Re: sudo rules based on group membership from freeipa does not work

[Launchpad Bug Tracker]

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

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

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

Title:
  sudo rules based on group membership from freeipa does not work

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  When upgrading sudo package in xenial from version 1.8.16-0ubuntu1 to
  1.8.16-0ubuntu1.3, our FreeIPA-based sudo rules suddenly stopped
  working. We have setup a group in FreeIPA called ldap_nopass, and
  configured hbac rules to allow users in this group to run sudo
  (without password / nopasswd). This have been working fine up until
  now when we upgraded the sudo package. Downgrading to 1.8.16-0ubuntu1
  resolves the issue. It also work with 1.8.16-0ubuntu1.3 if we set
  use_fully_qualified_names = False in /etc/sssd/sssd.conf, but this is
  not an option for us.

  This led me to believe this issue is related to upstream bug: 
  https://bugzilla.sudo.ws/show_bug.cgi?id=757

  And most likely is caused by the patchset from 1.3
  https://launchpad.net/ubuntu/+source/sudo/1.8.16-0ubuntu1.3

  Unfortunately, 1.8.16-0ubuntu1.2 binaries seems to be deleted from
  mirrors, so I cannot try this version.

  I've included the auth.log file showing the difference using sudo
  1.8.16-0ubuntu1 vs 1.8.16-0ubuntu1.3. Real username and domain has
  been redacted to user.name and example.com

  Please let me know if any additional information is required.

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

-- 
Mailing list: https://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 1617564] Re: [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is

[Altia011 Educación]

Thanks for the info Lasse Hansen,

it works!!!

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

Title:
  [master] package kaccounts-providers (not installed) failed to
  install/upgrade: trying to overwrite '/etc/signon-ui/webkit-
  options.d/www.facebook.com.conf', which is also in package account-
  plugin-facebook 0.12+16.04.20160126-0ubuntu1

Status in One Hundred Papercuts:
  Confirmed
Status in account-plugins package in Ubuntu:
  Confirmed
Status in kaccounts-providers package in Ubuntu:
  Confirmed

Bug description:
  showing this error when installing kde environment in ubuntu 16.04. it
  say kaccounts  niot installed. so i think it may cause some security
  issue

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kaccounts-providers (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Aug 27 18:11:18 2016
  DuplicateSignature:
   package:kaccounts-providers:(not installed)
   Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
 (--unpack):
    trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
  InstallationDate: Installed on 2016-08-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: kaccounts-providers
  Title: package kaccounts-providers (not installed) failed to install/upgrade: 
trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', 
which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1689796] Re: sudo + sssd does not work for IPA hostgroups

[Launchpad Bug Tracker]

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

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

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

Title:
  sudo + sssd does not work for IPA hostgroups

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  As discussed on this page:
  https://pagure.io/freeipa/issue/6139

  Sudo + SSSD doesn't work with hostgroups.
  As suggested, sudo upstream has a fix for this problem in 
https://www.sudo.ws/repos/sudo/rev/2eab4070dcf7

  It looks similar to the issue https://bugs.launchpad.net/bugs/1688034
  but is actually different.

  1) root@ipa:~# lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  2)
  root@ipa:~# apt-cache policy sudo
  sudo:
    Installed: 1.8.16-0ubuntu1.3
    Candidate: 1.8.16-0ubuntu1.3
    Version table:
   *** 1.8.16-0ubuntu1.3 500
  500 http://localapt/ubuntu xenial-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1.8.16-0ubuntu1 500
  500 http://localapt/ubuntu xenial/main amd64 Packages

  3) I expect to be able to grant sudo rights based on IPA hostgroups

  4) "testuser is not allowed to run sudo on host.ipa.example.com.  This
  incident will be reported."

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

-- 
Mailing list: https://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 1689796] Re: sudo + sssd does not work for IPA hostgroups

[4tro]

** Description changed:

  As discussed on this page:
  https://pagure.io/freeipa/issue/6139
  
  Sudo + SSSD doesn't work with hostgroups.
  As suggested, sudo upstream has a fix for this problem in 
https://www.sudo.ws/repos/sudo/rev/2eab4070dcf7
  
  It looks similar to the issue https://bugs.launchpad.net/bugs/1688034
  but is actually different.
  
- 1) root@ipa:~# lsb_release -rd 
+ 1) root@ipa:~# lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  
  2)
  root@ipa:~# apt-cache policy sudo
  sudo:
-   Installed: 1.8.16-0ubuntu1.3
-   Candidate: 1.8.16-0ubuntu1.3
-   Version table:
-  *** 1.8.16-0ubuntu1.3 500
- 500 http://localapt/ubuntu xenial-updates/main amd64 Packages
- 100 /var/lib/dpkg/status
-  1.8.16-0ubuntu1 500
- 500 http://localapt/ubuntu xenial/main amd64 Packages
+   Installed: 1.8.16-0ubuntu1.3
+   Candidate: 1.8.16-0ubuntu1.3
+   Version table:
+  *** 1.8.16-0ubuntu1.3 500
+ 500 http://localapt/ubuntu xenial-updates/main amd64 Packages
+ 100 /var/lib/dpkg/status
+  1.8.16-0ubuntu1 500
+ 500 http://localapt/ubuntu xenial/main amd64 Packages
  
  3) I expect to be able to grant sudo rights based on IPA hostgroups
  
- 4) "testuser is not allowed to run sudo on cw-st-ipa.catawiki.net.  This
+ 4) "testuser is not allowed to run sudo on host.ipa.example.com.  This
  incident will be reported."

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

Title:
  sudo + sssd does not work for IPA hostgroups

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  As discussed on this page:
  https://pagure.io/freeipa/issue/6139

  Sudo + SSSD doesn't work with hostgroups.
  As suggested, sudo upstream has a fix for this problem in 
https://www.sudo.ws/repos/sudo/rev/2eab4070dcf7

  It looks similar to the issue https://bugs.launchpad.net/bugs/1688034
  but is actually different.

  1) root@ipa:~# lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  2)
  root@ipa:~# apt-cache policy sudo
  sudo:
    Installed: 1.8.16-0ubuntu1.3
    Candidate: 1.8.16-0ubuntu1.3
    Version table:
   *** 1.8.16-0ubuntu1.3 500
  500 http://localapt/ubuntu xenial-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1.8.16-0ubuntu1 500
  500 http://localapt/ubuntu xenial/main amd64 Packages

  3) I expect to be able to grant sudo rights based on IPA hostgroups

  4) "testuser is not allowed to run sudo on host.ipa.example.com.  This
  incident will be reported."

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

-- 
Mailing list: https://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 1694916] [NEW] package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Stef Servaes]

Public bug reported:

Issues updating apport:

sudo dpkg --configure -a
dpkg: error processing package apport (--configure):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting configuration
Errors were encountered while processing:
 apport
ssr@PC3248 ~/gdrive-local/mgmt/admin/info $ sudo apt-get install apport
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
  apport
1 upgraded, 0 newly installed, 0 to remove and 23 not upgraded.
1 not fully installed or removed.
Need to get 0 B/121 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 430429 files and directories currently installed.)
Preparing to unpack .../apport_2.20.4-0ubuntu4.1_all.deb ...
  File "/usr/bin/pyclean", line 63
except (IOError, OSError), e:
 ^
SyntaxError: invalid syntax
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
  File "/usr/bin/pyclean", line 63
except (IOError, OSError), e:
 ^
SyntaxError: invalid syntax
dpkg: error processing archive 
/var/cache/apt/archives/apport_2.20.4-0ubuntu4.1_all.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1
Traceback (most recent call last):
  File "/usr/bin/pycompile", line 35, in 
from debpython.version import SUPPORTED, debsorted, vrepr, \
  File "/usr/share/python/debpython/version.py", line 24, in 
from ConfigParser import SafeConfigParser
ImportError: No module named 'ConfigParser'
*** Error in `/usr/bin/dpkg': munmap_chunk(): invalid pointer: 
0x56449feb52e8 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x7908b)[0x7ff8ca09608b]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x1f8)[0x7ff8ca0a32d8]
/usr/bin/dpkg(+0x20cd0)[0x56449dd54cd0]
/usr/bin/dpkg(+0x21119)[0x56449dd55119]
/usr/bin/dpkg(+0x283cd)[0x56449dd5c3cd]
/usr/bin/dpkg(+0x17737)[0x56449dd4b737]
/usr/bin/dpkg(+0x17915)[0x56449dd4b915]
/usr/bin/dpkg(+0x17b5d)[0x56449dd4bb5d]
/usr/bin/dpkg(+0xaed7)[0x56449dd3eed7]
/usr/bin/dpkg(+0x20c0b)[0x56449dd54c0b]
/usr/bin/dpkg(+0x20e01)[0x56449dd54e01]
/usr/bin/dpkg(+0xa962)[0x56449dd3e962]
/usr/bin/dpkg(+0x72fd)[0x56449dd3b2fd]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7ff8ca03d3f1]
/usr/bin/dpkg(+0x743a)[0x56449dd3b43a]
=== Memory map: 
56449dd34000-56449dd79000 r-xp  fd:00 4718628
/usr/bin/dpkg
56449df79000-56449df7c000 r--p 00045000 fd:00 4718628
/usr/bin/dpkg
56449df7c000-56449df7d000 rw-p 00048000 fd:00 4718628
/usr/bin/dpkg
56449df7d000-56449e191000 rw-p  00:00 0 
56449f79-5644a454c000 rw-p  00:00 0  [heap]
7ff8c8879000-7ff8c888f000 r-xp  fd:00 6816526
/lib/x86_64-linux-gnu/libgcc_s.so.1
7ff8c888f000-7ff8c8a8e000 ---p 00016000 fd:00 6816526
/lib/x86_64-linux-gnu/libgcc_s.so.1
7ff8c8a8e000-7ff8c8a8f000 r--p 00015000 fd:00 6816526
/lib/x86_64-linux-gnu/libgcc_s.so.1
7ff8c8a8f000-7ff8c8a9 rw-p 00016000 fd:00 6816526
/lib/x86_64-linux-gnu/libgcc_s.so.1
7ff8c8a9-7ff8c8e1c000 rw-p  00:00 0 
7ff8c8e1c000-7ff8c8e27000 r-xp  fd:00 6817463
/lib/x86_64-linux-gnu/libnss_files-2.24.so
7ff8c8e27000-7ff8c9026000 ---p b000 fd:00 6817463
/lib/x86_64-linux-gnu/libnss_files-2.24.so
7ff8c9026000-7ff8c9027000 r--p a000 fd:00 6817463
/lib/x86_64-linux-gnu/libnss_files-2.24.so
7ff8c9027000-7ff8c9028000 rw-p b000 fd:00 6817463
/lib/x86_64-linux-gnu/libnss_files-2.24.so
7ff8c9028000-7ff8c902e000 rw-p  00:00 0 
7ff8c902e000-7ff8c9039000 r-xp  fd:00 6817465
/lib/x86_64-linux-gnu/libnss_nis-2.24.so
7ff8c9039000-7ff8c9238000 ---p b000 fd:00 6817465
/lib/x86_64-linux-gnu/libnss_nis-2.24.so
7ff8c9238000-7ff8c9239000 r--p a000 fd:00 6817465
/lib/x86_64-linux-gnu/libnss_nis-2.24.so
7ff8c9239000-7ff8c923a000 rw-p b000 fd:00 6817465
/lib/x86_64-linux-gnu/libnss_nis-2.24.so
7ff8c923a000-7ff8c925 r-xp  fd:00 6817460
/lib/x86_64-linux-gnu/libnsl-2.24.so
7ff8c925-7ff8c944f000 ---p 00016000 fd:00 6817460
/lib/x86_64-linux-gnu/libnsl-2.24.so
7ff8c944f000-7ff8c945 r--p 00015000 fd:00 6817460
/lib/x86_64-linux-gnu/libnsl-2.24.so
7ff8c945-7ff8c9451000 rw-p 00016000 fd:00 6817460
/lib/x86_64-linux-gnu/libnsl-2.24.so
7ff8c9451000-7ff8c9453000 rw-p  00:00 0 
7ff8c9453000-7ff8c945b000 r-xp  fd:00 6817461
/lib/x86_64-linux-gnu/libnss_compat-2.24.so
7ff8c945b000-7ff8c965a000 ---p 8000 

[Touch-packages] [Bug 972077] Re: apt repository disk format has race conditions

[Abhijith Gururaj]

@juliank I have configured the updater to use the main server.
Downloading updates from the main server shouldn't cause such errors,
right?

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

Title:
  apt repository disk format has race conditions

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released

Bug description:
  Apt archives are accessed over HTTP; this has resulted in a cluster of
  bugs (reported here, and upstream) about problems behind intercepting
  caches, problems with squid etc.

  There are 3 interlocking issues:
  A - mirror networks may be out of sync with each other (e.g. a file named on 
one mirror may no longer exist, or may not yet exist, on another mirror)
  B - updating files on a single mirror is not atomic - and even small windows 
of inconsistency will, given enough clients, cause headaches.
  C - caches exacerbate race conditions - when one happens, until the cached 
data expires, all clients of the cache will suffer from the race

  Solving this requires one of several things:
   - file system transactions
   - an archive format that requires only weakly ordered updates to the files 
at particular urls with the assumption that only one file may be observed to 
change at a time (because a lookup of file A, then B, may get a cache miss on A 
and a cache hit on B, so even if all clients strictly go A, then B, updates may 
still see old files when paths are reused).
   - super robust clients that repeatedly retry with progressively less cache 
friendly headers until they have a consistent view. (This is very tricky to do).

  It may be possible to do a tweak to the apt repository format though,
  which would allow publishing a race-free format in parallel with the
  existing layout, while clients migrate. To be safe against issue (A)
  the mirror network would need some care around handling of dns round-
  robin mirrors [to minimise the situation where referenced data is not
  available], but this should be doable - or alternatively clients doing
  'apt-get update' may need to be willing to retry to accommodate round-
  robin skew.

  What would such an archive format look like?
  It would have only one well known file name (InRelease), which would be 
internally signed. Rather than signing e.g. Packages.gz, it would sign a 
uniquely named packages and sources file - e.g. Packages-$HASH.gz or 
Packages-$serialno.gz.

  Backwards compatibility is achieved by using the same filenames for
  deb's and the like. We need to keep writing Packages.gz though, and
  Releases, until we no longer worry about old apt clients. We can
  optimise disk space a little by making Packages.gz a symlink to a
  Packages-$HASH.gz (and so on for Sources..), but it may be simpler and
  less prone to unexpected behaviour to keep using regular files.

  tl;dr
   * Unique file names for all unique file content with one exception
   * InRelease, a self-signed file that provides hashes and names the index 
files (Packages, Sources, Translations etc)
   * Coexists with existing archive layout

  Related bugs:
   * bug 804252: Please support InRelease files
   * bug 1430011: support apt by-hash mirrors

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

-- 
Mailing list: https://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 972077] Re: apt repository disk format has race conditions

[Julian Andres Klode]

Switch to a different mirror. Hash sum mismatches on .deb file should
not happen on any well-built mirror.

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

Title:
  apt repository disk format has race conditions

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released

Bug description:
  Apt archives are accessed over HTTP; this has resulted in a cluster of
  bugs (reported here, and upstream) about problems behind intercepting
  caches, problems with squid etc.

  There are 3 interlocking issues:
  A - mirror networks may be out of sync with each other (e.g. a file named on 
one mirror may no longer exist, or may not yet exist, on another mirror)
  B - updating files on a single mirror is not atomic - and even small windows 
of inconsistency will, given enough clients, cause headaches.
  C - caches exacerbate race conditions - when one happens, until the cached 
data expires, all clients of the cache will suffer from the race

  Solving this requires one of several things:
   - file system transactions
   - an archive format that requires only weakly ordered updates to the files 
at particular urls with the assumption that only one file may be observed to 
change at a time (because a lookup of file A, then B, may get a cache miss on A 
and a cache hit on B, so even if all clients strictly go A, then B, updates may 
still see old files when paths are reused).
   - super robust clients that repeatedly retry with progressively less cache 
friendly headers until they have a consistent view. (This is very tricky to do).

  It may be possible to do a tweak to the apt repository format though,
  which would allow publishing a race-free format in parallel with the
  existing layout, while clients migrate. To be safe against issue (A)
  the mirror network would need some care around handling of dns round-
  robin mirrors [to minimise the situation where referenced data is not
  available], but this should be doable - or alternatively clients doing
  'apt-get update' may need to be willing to retry to accommodate round-
  robin skew.

  What would such an archive format look like?
  It would have only one well known file name (InRelease), which would be 
internally signed. Rather than signing e.g. Packages.gz, it would sign a 
uniquely named packages and sources file - e.g. Packages-$HASH.gz or 
Packages-$serialno.gz.

  Backwards compatibility is achieved by using the same filenames for
  deb's and the like. We need to keep writing Packages.gz though, and
  Releases, until we no longer worry about old apt clients. We can
  optimise disk space a little by making Packages.gz a symlink to a
  Packages-$HASH.gz (and so on for Sources..), but it may be simpler and
  less prone to unexpected behaviour to keep using regular files.

  tl;dr
   * Unique file names for all unique file content with one exception
   * InRelease, a self-signed file that provides hashes and names the index 
files (Packages, Sources, Translations etc)
   * Coexists with existing archive layout

  Related bugs:
   * bug 804252: Please support InRelease files
   * bug 1430011: support apt by-hash mirrors

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

-- 
Mailing list: https://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 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough free handles to register service" at start

[@pjf]

Encountered today on Ubuntu 16.04 quite surprisingly, as bluetooth is
usually problematic (with https://bugs.launchpad.net/bugs/1577197 ), but
not broken.

Disabling LE did not resolve issue. I'm expecting (hoping) rebooting
will, since it worked before.

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

Title:
  15:10 and 16.04: bluetoothd reports "Not enough free handles to
  register service" at start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

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

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