[Touch-packages] [Bug 1660832] Re: unix domain socket cross permission check failing with nested namespaces

[John Johansen]

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

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

Title:
  unix domain socket cross permission check failing with nested
  namespaces

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Confirmed
Status in linux source package in Yakkety:
  Fix Released
Status in apparmor source package in Zesty:
  Confirmed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  When using nested namespaces policy within the nested namespace is trying 
  
  to cross validate with policy outside of the namespace that is not
  
  visible to it. This results the access being denied and with no way to
  
  add a rule to policy that would allow it.

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

-- 
Mailing list: https://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 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"

[John Johansen]

Please describe the failure, including the logs so I can analyze. Just
because the container fails to start does not mean that the fix is bad.
There can be other issues that result in the failure.

Specifically this bug is for the denial message seen in comment #5 and
not the denied messages (unlink) in comment #9, which are a separate
issue.

It appears to be working for me, with yakkety and zesty

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

Title:
  tor in lxd: apparmor="DENIED" operation="change_onexec"
  namespace="root//CONTAINERNAME_" profile="unconfined"
  name="system_tor"

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in tor package in Ubuntu:
  New
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Released
Status in tor source package in Xenial:
  New
Status in apparmor source package in Yakkety:
  New
Status in linux source package in Yakkety:
  Confirmed
Status in tor source package in Yakkety:
  New

Bug description:
  Environment:
  

  Distribution: ubuntu
  Distribution version: 16.10
  lxc info:
  apiextensions:

  storage_zfs_remove_snapshots
  container_host_shutdown_timeout
  container_syscall_filtering
  auth_pki
  container_last_used_at
  etag
  patch
  usb_devices
  https_allowed_credentials
  image_compression_algorithm
  directory_manipulation
  container_cpu_time
  storage_zfs_use_refquota
  storage_lvm_mount_options
  network
  profile_usedby
  container_push
  apistatus: stable
  apiversion: "1.0"
  auth: trusted
  environment:
  addresses:
  163.172.48.149:8443
  172.20.10.1:8443
  172.20.11.1:8443
  172.20.12.1:8443
  172.20.22.1:8443
  172.20.21.1:8443
  10.8.0.1:8443
  architectures:
  x86_64
  i686
  certificate: |
  -BEGIN CERTIFICATE-
  -END CERTIFICATE-
  certificatefingerprint: 
3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b
  driver: lxc
  driverversion: 2.0.5
  kernel: Linux
  kernelarchitecture: x86_64
  kernelversion: 4.8.0-27-generic
  server: lxd
  serverpid: 32694
  serverversion: 2.4.1
  storage: btrfs
  storageversion: 4.7.3
  config:
  core.https_address: '[::]:8443'
  core.trust_password: true

  Container: ubuntu 16.10

  
  Issue description
  --

  
  tor can't start in a non privileged container

  
  Logs from the container:
  -

  Dec 7 15:03:00 anonymous tor[302]: Configuration was valid
  Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step 
APPARMOR spawning /usr/bin/tor: No such file or directory
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process 
exited, code=exited, status=231/APPARMOR
  Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay 
network for TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed 
state.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 
'exit-code'.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off 
time over, scheduling restart.
  Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for 
TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset 
devices.list: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to 
set devices.allow on /system.slice/system-tor.slice/tor@default.service: 
Operation not permitted]
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/chr
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/blk
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted


  Logs from the host
  

  audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" 
operation="change_onexec" info="label not found" error=-2 
namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" 
  pid=12164 comm="(tor)"

  
  Steps to reproduce
  -

  install ubuntu container 16.10 on a ubuntu 16.10 host
  install tor in the container
  Launch tor

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

-- 
Mailing 

[Touch-packages] [Bug 1479524] Re: Totem Crashes at launch from missing libwayland-egl

[Timo Aaltonen]

closing trusty tasks as wontfix

** Changed in: mesa-lts-vivid (Ubuntu Trusty)
   Status: Confirmed => Won't Fix

** Changed in: mesa (Ubuntu Wily)
   Status: Confirmed => Won't Fix

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

Title:
  Totem Crashes at launch from missing libwayland-egl

Status in System76:
  New
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Trusty:
  Fix Released
Status in mesa source package in Trusty:
  Invalid
Status in mesa-lts-vivid source package in Trusty:
  Won't Fix
Status in livecd-rootfs source package in Wily:
  Invalid
Status in mesa source package in Wily:
  Won't Fix

Bug description:
  When trying to open a video file from Ubuntu 14.04.3 Daily Image
  (2015-07-29), it will not open. If totem is manually run from the
  terminal, this error occurs:

  totem: error while loading shared libraries: libwayland-egl.so.1:
  cannot open shared object file: No such file or directory

  Using Ubuntu 14.04.3 LTS (Daily Image from: 2015-07-29) 64-bit
  Totem version: 3.10.1-1ubuntu4

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: totem 3.10.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 29 15:11:30 2015
  InstallationDate: Installed on 2015-07-29 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150729)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1278871] Re: please consider making libgl1-mesa-dri to not be pulled into ubuntu-touch seed

[Timo Aaltonen]

libgbm1 doesn't depend on libgl1-mesa-dri anymore, and things seem to
work fine still

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

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

Title:
  please consider making libgl1-mesa-dri to not be pulled into ubuntu-
  touch seed

Status in mesa package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  From mesa package: libgbm1 depends on libgl1-mesa-dri

  From qtdeclarative-opensource-src: qtdeclarative5-qtquick2-plugin
  depends on libgl1-mesa-dri

  Mesa is available on our default installations by virtue of 
ubuntu-drivers-common, seeds or manual package selection.
  Above two dependencies, result in nvidia & radion packages pulled into 
ubuntu-touch seed which is undesired.

  Talking on IRC mlankhorst provided a solution, which i'd like to try out:
   depend on libgl1-mesa-dri  | libgl1
   and include libhybris first so libgl1-mesa-dri doesn't end up 
being installed

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

-- 
Mailing list: https://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 1655803] Re: x-staging problem report

[Timo Aaltonen]

closing, if xenial has this issue still with mesa 12.0.6, reopen.

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

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

Title:
  x-staging problem report

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  I added the x-staging ppa and upgraded my 16.04 system (equipped with
  AMD W9000) to use the mesa drivers in the upcoming release.  After
  about 15 minutes of emacs, terminal, and chrome usage the screen
  blanks to grey with blue squares, then to grey, then powers off.  I'm
  logging this here in hopes it will help the upcoming release.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  BootLog:
   
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Jan 11 18:09:18 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-53-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-57-generic, x86_64: installed
   nvidia-375, 375.26, 4.4.0-53-generic, x86_64: installed
   nvidia-375, 375.26, 4.4.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT GL [FirePro W9000] 
[1002:6780] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT GL [FirePro 
W9000] [1002:031e]
  MachineType: Dell Inc. Precision WorkStation T7500
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic 
root=UUID=4bb35b69-210e-445c-b815-725f1bb7e010 ro radeon.msi=0 quiet splash 
nouveau.blacklist=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06FW8P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/21/2011:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn06FW8P:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T7500
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.2-1ubuntu1~xenial0
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.2-1ubuntu1~xenial0
  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: Wed Jan 11 17:55:07 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

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

-- 
Mailing list: https://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 1430888] Re: DRI_PRIME with radeon/intel windows do not draw

[Timo Aaltonen]

I'm going to assume this is fixed with mesa 12.0.6 and if you enable
DRI3 or uninstall xserver-xorg-video-intel (which lets it fall back  on
-modeset which uses DRI3)

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  DRI_PRIME with radeon/intel windows do not draw

Status in X.Org X server:
  New
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  I'm using Ubuntu 15.04 and Xorg version 1:7.7+7ubuntu2

  Step to reproduce:
  start "DRI_PRIME=1 steam" (or any other complex 3D program like minecraft)

  What is expected:
  the program should show it's window(s), those should have the same content as 
if started without "DRI_PRIME".

  What actually happens:
  most times the program just shows a "freezed" version of the background the 
window appeared on.

  Additional Informations:
  I have the newest BIOS version.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu2
  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
  Date: Wed Mar 11 17:01:13 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.18.0-13-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-7-generic, x86_64: installed
   virtualbox, 4.3.24, 3.19.0-7-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1486]
   Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 
5430/5450/5470] [1002:68e0] (rev ff) (prog-if ff)
  MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=35d0b52c-aa5e-48d2-9eec-f7a6036f2a56 ro splash drm.rnodes=1 
vt.handoff=7
  SourcePackage: xorg
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2011
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1486
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 83.20
  dmi.chassis.asset.tag: CNU0250216
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd02/18/2011:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr048920252A2000122:rvnHewlett-Packard:rn1486:rvr83.20:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP TouchSmart tm2 Notebook PC
  dmi.product.version: 048920252A2000122
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Mar 10 10:39:26 2015
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   38164 
   vendor AUO
  xserver.version: 2:1.16.2.901-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1430888/+subscriptions

-- 
Mailing list: https://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 1551028] Re: glGenFramebuffers fails when linked with OSMesa AND X11

[Timo Aaltonen]

mesa in 16.04 will get proper backports and not renamed like before, so
this should not happen anymore.. sorry that there's no way to fix it in
14.04 lts

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  glGenFramebuffers fails  when linked with OSMesa AND X11

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Hi.

  In latest update for Ubuntu Desktop 14.04.4 LTS, there is a serious
  problem when calling glGenFramebuffers() in a program that links both
  libOSMesa and libX11.

  Attached is a test program that can verify this. If the program is
  compiled with the following

  gcc check_glgenframebuffer.c -lGL -lX11 -lOSMesa

  then glGenFramebuffers() will fail when current context is set to GLX
  and the program will dump core upon exit. This is from gdb:

  Program received signal SIGSEGV, Segmentation fault.
  0x72ef930e in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so

  If the program is compiled with the following, then it works.

  gcc check_glgenframebuffer.c -lGL -lX11

  This is a problem if you have a program that needs both libs such as
  the Open Source Video Mixer Snowmix.

  Best regards
  Peter Maersk-Moller

  Installed libs:
  ls -l /usr/lib/x86_64-linux-gnu/libOSMesa*
  lrwxrwxrwx 1 root root  18 Jan 12 21:03 
/usr/lib/x86_64-linux-gnu/libOSMesa.so -> libOSMesa.so.6.5.3
  lrwxrwxrwx 1 root root  18 Jan 12 21:03 
/usr/lib/x86_64-linux-gnu/libOSMesa.so.6 -> libOSMesa.so.6.5.3
  -rw-r--r-- 1 root root 3708216 Jan 12 21:03 
/usr/lib/x86_64-linux-gnu/libOSMesa.so.6.5.3

  ls -l /usr/lib/x86_64-linux-gnu/libX11*
  -rw-r--r-- 1 root root 2188236 Dec  4  2013 /usr/lib/x86_64-linux-gnu/libX11.a
  lrwxrwxrwx 1 root root  15 Dec  4  2013 
/usr/lib/x86_64-linux-gnu/libX11.so -> libX11.so.6.3.0
  lrwxrwxrwx 1 root root  15 Dec  4  2013 
/usr/lib/x86_64-linux-gnu/libX11.so.6 -> libX11.so.6.3.0
  -rw-r--r-- 1 root root 1265072 Dec  4  2013 
/usr/lib/x86_64-linux-gnu/libX11.so.6.3.0

  ls -l /usr/lib/x86_64-linux-gnu/libGL.*
  lrwxrwxrwx 1 root root 13 Jan 12 21:03 /usr/lib/x86_64-linux-gnu/libGL.so -> 
mesa/libGL.so

  ls -l /usr/lib/x86_64-linux-gnu/mesa/*
  -rw-r--r-- 1 root root 31 Jan 12 21:03 
/usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
  lrwxrwxrwx 1 root root 14 Jan 12 21:03 
/usr/lib/x86_64-linux-gnu/mesa/libGL.so -> libGL.so.1.2.0
  lrwxrwxrwx 1 root root 14 Jan 12 21:03 
/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 -> libGL.so.1.2.0
  -rw-r--r-- 1 root root 413968 Jan 12 21:03 
/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2.0

  ldd /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
linux-vdso.so.1 =>  (0x7ffe885cf000)
libdrm_intel.so.1 => /usr/lib/x86_64-linux-gnu/libdrm_intel.so.1 
(0x7fdb85bac000)
libdrm_nouveau.so.2 => /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 
(0x7fdb859a5000)
libdrm_radeon.so.1 => /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 
(0x7fdb85799000)
libdrm.so.2 => /usr/lib/x86_64-linux-gnu/libdrm.so.2 
(0x7fdb8558c000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 
(0x7fdb85362000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fdb85144000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fdb84f4)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fdb84c3c000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fdb84936000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdb84571000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fdb8435b000)
libpciaccess.so.0 => /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(0x7fdb84152000)
/lib64/ld-linux-x86-64.so.2 (0x7fdb8652a000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fdb83f39000)

  ldd /usr/lib/x86_64-linux-gnu/libOSMesa.so
linux-vdso.so.1 =>  (0x7ffc773d)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f3c1cdce000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f3c1cbca000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f3c1c8c6000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f3c1c5c)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f3c1c1fb000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f3c1bfe5000)
/lib64/ld-linux-x86-64.so.2 (0x7f3c1d57f000)

  ldd /usr/lib/x86_64-linux-gnu/libX11.so
linux-vdso.so.1 =>  (0x7ffe4328d000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 
(0x7f572a94c000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f572a748000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 

[Touch-packages] [Bug 1670269] [NEW] Add com.ubuntu.usbcreator.format for usb creator action

[Khurshid Alam]

Public bug reported:

Usb creator still asks for password when formatting or trying to install
boot-loader. If user doesn't respond within a sepecific time, it fails
and user has to start the process all over again.

Adding "com.ubuntu.usbcreator.format" to Action solves the issue.

### PATCH
-

--- a/com.ubuntu.desktop.pkla
+++ b/com.ubuntu.desktop.pkla
@@ -25,7 +25,7 @@
 
 [usb-creator]
 Identity=unix-group:admin;unix-group:sudo
-Action=com.ubuntu.usbcreator.mount;com.ubuntu.usbcreator.image
+Action=com.ubuntu.usbcreator.mount;com.ubuntu.usbcreator.image;com.ubuntu.usbcreator.format
 ResultActive=yes
 
 [Printer administration]

** Affects: policykit-desktop-privileges (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: patch zesty

** Attachment added: "patch"
   
https://bugs.launchpad.net/bugs/1670269/+attachment/4832131/+files/policykit-usb-creator-action-format.patch

** Summary changed:

- Add com.ubuntu.usbcreator.format for usb creator
+ Add com.ubuntu.usbcreator.format for usb creator action

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

Title:
  Add com.ubuntu.usbcreator.format for usb creator action

Status in policykit-desktop-privileges package in Ubuntu:
  New

Bug description:
  Usb creator still asks for password when formatting or trying to
  install boot-loader. If user doesn't respond within a sepecific time,
  it fails and user has to start the process all over again.

  Adding "com.ubuntu.usbcreator.format" to Action solves the issue.

  ### PATCH
  -

  --- a/com.ubuntu.desktop.pkla
  +++ b/com.ubuntu.desktop.pkla
  @@ -25,7 +25,7 @@
   
   [usb-creator]
   Identity=unix-group:admin;unix-group:sudo
  -Action=com.ubuntu.usbcreator.mount;com.ubuntu.usbcreator.image
  
+Action=com.ubuntu.usbcreator.mount;com.ubuntu.usbcreator.image;com.ubuntu.usbcreator.format
   ResultActive=yes
   
   [Printer administration]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1670269/+subscriptions

-- 
Mailing list: https://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 1640970] Re: 16.10: VPN Connections -> Configure VPN grayed out

[Noel Bowland]

At least within Compiz anyway... Haven't tried it in Unity

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

Title:
  16.10: VPN Connections -> Configure VPN grayed out

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10, in the nm applet menu, VPN
  Connections -> Configure VPN is grayed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 10 16:04:49 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-04 (951 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  IpRoute:
   default via 172.28.77.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.28.77.0/24 dev wlan0  proto kernel  scope link  src 172.28.77.23  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-11-07 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-03-07T11:36:55.286063
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0   wifi  connected /org/freedesktop/NetworkManager/Devices/0  
BlueCedar-GUEST  f7b79954-9427-47eb-adba-875b5b152f37  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/1  
--   ----   
  
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/2  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: https://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 1640970] Re: 16.10: VPN Connections -> Configure VPN grayed out

[Noel Bowland]

This problem also seems to affect the "Disconnect VPN" button. It just
disappears... :(

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

Title:
  16.10: VPN Connections -> Configure VPN grayed out

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10, in the nm applet menu, VPN
  Connections -> Configure VPN is grayed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 10 16:04:49 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-04 (951 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  IpRoute:
   default via 172.28.77.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.28.77.0/24 dev wlan0  proto kernel  scope link  src 172.28.77.23  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-11-07 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-03-07T11:36:55.286063
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0   wifi  connected /org/freedesktop/NetworkManager/Devices/0  
BlueCedar-GUEST  f7b79954-9427-47eb-adba-875b5b152f37  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/1  
--   ----   
  
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/2  
--   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: https://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 989184] Re: Firefox 12's launcher script is not allowed in abstractions/ubuntu-browsers

[Robert Brindza]

** Changed in: apparmor (Ubuntu Lucid)
 Assignee: Micah Gersten (micahg) => (unassigned)

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

Title:
  Firefox 12's launcher script is not allowed in abstractions/ubuntu-
  browsers

Status in apparmor package in Ubuntu:
  Invalid
Status in apparmor source package in Lucid:
  Fix Released
Status in apparmor source package in Natty:
  Fix Released
Status in apparmor source package in Oneiric:
  Fix Released

Bug description:
  WORKAROUND: Change /usr/lib/firefox-*/firefox.sh PUx, in
  /etc/apparmor.d/abstractions/ubuntu-browsers to
  /usr/lib/firefox*/firefox.sh PUx,

  TEST CASE: Launch Firefox from evince

  

  Since Firefox was updated to version 12, the launcher script is
  installed as "/usr/lib/firefox/firefox.sh" instead of the old name
  that included the version in it : "/usr/lib/firefox-11.0/firefox.sh".

  $ lsb_release -rd
  Description:  Ubuntu 11.10
  Release:  11.10

  $ apt-cache policy apparmor
  apparmor:
    Installed: 2.7.0~beta1+bzr1774-1ubuntu2
    Candidate: 2.7.0~beta1+bzr1774-1ubuntu2
    Version table:
   *** 2.7.0~beta1+bzr1774-1ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: BugDistroRelease: Ubuntu 11.10
  Package: apparmor 2.7.0~beta1+bzr1774-1ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-19.33-generic 3.0.27
  Uname: Linux 3.0.0-19-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Thu Apr 26 15:43:20 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.0.0-19-generic 
root=/dev/mapper/crypt-root ro quiet splash vt.handoff=7SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apparmor.d.abstractions.aspell: [modified]
  mtime.conffile..etc.apparmor.d.abstractions.aspell: 2012-01-18T13:58:44.963987

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

-- 
Mailing list: https://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 541595] Re: [Master] package failed to install/upgrade: package is already installed and configured

[dino99]

** Tags removed: lucid

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

Title:
  [Master] package failed to install/upgrade: package is already
  installed and configured

Status in dpkg:
  New
Status in apt package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: dpkg

  For yet unknown reasons packages fail to install with an error like:

  dpkg: error processing flashplugin-installer (--configure):
   package flashplugin-installer is already installed and configured

  without further error.
  This is a "one time" failure. Another run of the installation doesn't produce 
any error.

  Users reporting this error are also experiencing bug 545790 and bug
  545738 .

  ProblemType: Bug
  Architecture: i386
  Date: Fri Mar 19 00:09:06 2010
  DistroRelease: Ubuntu 10.04
  EcryptfsInUse: Yes
  Package: dpkg 1.15.5.6ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
  SourcePackage: dpkg
  Uname: Linux 2.6.32-16-generic i686

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

-- 
Mailing list: https://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 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Bluetooth headset HSP/HFP mode not working in Xenial

Status in HWE Next:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Using the 2/14 Xenial daily build, paired bluetooth headsets' do not
  work in HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. In the laptop, go to sound settings > output tab > try switching mode to 
HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  [Details]
  BT wireless module:
   * Intel 3160
  BT headset:
   * Jabra CLI
  Xenial: 2/14 daily build:
   * Kernel: 4.4.0-6
   * bluez: 5.36-0ubuntu1
   * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1
   * pulseaudio: 1:8.0-0ubuntu2
   * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2

  [Note]
  Also double checked with same set of hardware, but with 15.10 installed.
  Bluetooth headset HSP/HFP mode worked correctly in 15.10.

  15.10 details:
   * kernel: 4.2.0-19
   * bluez: 5.35-0ubuntu2
   * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1
   * pulseaudio: 1:6.0-0ubuntu13
   * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549163/+subscriptions

-- 
Mailing list: https://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 1620118] Re: [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all

[Launchpad Bug Tracker]

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

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

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

Title:
  [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  I am new with ubuntu, I bought a new laptop it came with ubuntu 14.04
  LTs installed on it and I decided to use it like that. Initially it
  was working correctly, but later I realized there is no sound when
  using any browser or playing video. So I upgraded to ubuntu 16.04 and
  the sound is working with firefox browser, but if I plug speaker it
  stop. Then I opened the sound setting and click output and there is
  mode of sound and I try to select so mode but then the tab disappeared
  and there is no sound at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jhashim4153 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Sep  4 23:19:46 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2016-02-11 (206 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jhashim4153 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2016-09-04 (0 days ago)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 05T1GT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn05T1GT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  Fix Released
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged--

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

  fix need landing LP: #1645698

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1647283/+subscriptions

-- 
Mailing list: https://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 1645698] Re: [SRU] Upgrade network-manager to latest point release

[Aron Xu]

** Tags added: verification-done

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

  needed by:
  lp #1647283

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

-- 
Mailing list: https://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 1670216] [NEW] Cannot load radeon drivers

[Mário João Gonçalves Ferreiro]

Public bug reported:

lsb_release -rd
Description:Ubuntu 16.04.2 LTS
Release:16.04

apt-cache policy xorg
xorg:
  Instalado: 1:7.7+13ubuntu3
  Candidato: 1:7.7+13ubuntu3
  Tabela de Versão:
 *** 1:7.7+13ubuntu3 500
500 http://pt.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

The following error occurs at genymotion start
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast

it occurs to in android AVD emulator before applying the following workaround, 
a bit different now since the folders names changed:
cd $ANDROID_HOME/android-sdk-linux_x86/tools/lib64/libstdc++
$ mv libstdc++.so.6 libstdc++.so.6.bak
$ ln -s /usr/lib64/libstdc++.so.6 
$ANDROID_HOME/android-sdk-linux_x86/tools/lib64/libstdc++
seen in here 
http://stackoverflow.com/questions/36554322/cannot-start-emulator-in-android-studio-2-0

It seems to be something about hardware acceleration since if it is
disabled in android AVD emulator the emulator work fine. If is started
from the command line with the option -use-system-lib: emulator -use-
system-libs -avd YOUR_VIRTUAL_DEVICE_NAME it work too.

A process to replicate the bug is install Ubuntu 16.04.1 LTS, then
virtualbox with apt and then install genymotion-2.8.1_x64.bin, at least
it was that I used. This way the emulator works. After this if you
update the Ubuntu with sudo apt update | sudo apt upgrade the error
appears.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Mar  5 23:29:14 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.0.32, 4.4.0-64-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832] 
(prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Kabini [Radeon HD 8330] [1179:fa34]
InstallationDate: Installed on 2017-03-05 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: TOSHIBA SATELLITE C50D-A-110
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=e9ba2d60-3ce1-4aab-aa2c-62d55f0ad0ad ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/21/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: PT10AN
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.30:bd05/21/2014:svnTOSHIBA:pnSATELLITEC50D-A-110:pvrPSCH2E-00700GEP:rvnAMD:rnPT10AN:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE C50D-A-110
dmi.product.version: PSCH2E-00700GEP
dmi.sys.vendor: TOSHIBA
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: Sun Mar  5 23:27:21 2017
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  Cannot load radeon drivers

Status in xorg package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy xorg
  xorg:

[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

[Jose Valencia]

Same issue on ubuntu 16.10 yakkety too.

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Expired
Status in openvpn package in Ubuntu:
  Expired

Bug description:
  [Triage Notes]

  This bug can no longer make progress. Please see comment 50 for
  details and further instructions.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

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

-- 
Mailing list: https://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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Iiro Laiho]

I ran this test. The machine was a 64-bit Ubuntu 16.04.2 on a VirtualBox
VM. Before running the command I enabled -proposed and ensured that CUPS
will not shut down by having a stuck job in the queue. The upgrade
completed correctly.

Console output of the "apt update && apt install cups-daemon" command
attached.

** Attachment added: "Console output for the package upgrade"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+attachment/4832058/+files/virtualbox-updatelog.log

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

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

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 659438] Re: news from me

[ankit anand]

Greetings,


I've got some news for you, you are going to be pleasantly surprised,  read it 
here please http://ahead.ocyrt.com/0809

Sent from my iPhone, ankitanand

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

Title:
  Installation/Removal fails because of package which could not be
  located (failure in apt.Cache.required_download)

Status in Aptdaemon:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in aptdaemon package in Ubuntu:
  Fix Released
Status in python-apt package in Ubuntu:
  Fix Released
Status in apt source package in Maverick:
  Invalid
Status in aptdaemon source package in Maverick:
  Fix Released
Status in python-apt source package in Maverick:
  Invalid

Bug description:
  Steps to reproduce:

  1. Run apt-get nstall ms-ttcorefonts-installer in a terminal
  2. Close the terminal window at the EULA question (apt-get/dpkg/debconf) will 
sting hang in the background and lock the system)
  3. Reboot


  Traceback (most recent call last):
    File "/usr/lib/python2.6/dist-packages/aptdaemon/worker.py", line 768, in 
simulate
  return self._simulate_helper(trans, status_path)
    File "/usr/lib/python2.6/dist-packages/aptdaemon/worker.py", line 936, in 
_simulate_helper
  return depends, status, self._cache.required_download, \
    File "/usr/lib/python2.6/dist-packages/apt/cache.py", line 218, in 
required_download
  pm.get_archives(fetcher, self._list, self._records)
  SystemError: E:I wasn't able to locate file for the liblua50 package. This 
might mean you need to manually fix this package.

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

-- 
Mailing list: https://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 1670193] [NEW] No audio on headphone ubuntu 16.04

[Raúl Vidal]

Public bug reported:

I upgraded from Ubuntu 14.04 LTS to Ubuntu 16.04 and I lost audio on the 
headphone jack. Speakers work fine though.
I installed pavucontrol and that program has a sound level bar which moves 
while playing sound with the headphones plugged in. So, PulseAudio effectively 
detects sound. In addition to the files attached by the ubuntu-bug program I 
have attached the output of alsa-info.sh.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.2
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  antonio2172 F pulseaudio
 /dev/snd/controlC1:  antonio2172 F pulseaudio
CurrentDesktop: Unity
Date: Sun Mar  5 21:39:08 2017
InstallationDate: Installed on 2012-07-22 (1687 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to xenial on 2017-03-01 (4 days ago)
dmi.bios.date: 10/23/2007
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.90
dmi.board.name: ISRAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.90:bd10/23/2007:svnTOSHIBA:pnSatelliteProP200:pvrPSPB7E-00Q00HCE:rvnTOSHIBA:rnISRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite Pro P200
dmi.product.version: PSPB7E-00Q00HCE
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug xenial

** Attachment added: "alsa-info.txt"
   
https://bugs.launchpad.net/bugs/1670193/+attachment/4831990/+files/alsa-info.txt

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

Title:
  No audio on headphone ubuntu 16.04

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I upgraded from Ubuntu 14.04 LTS to Ubuntu 16.04 and I lost audio on the 
headphone jack. Speakers work fine though.
  I installed pavucontrol and that program has a sound level bar which moves 
while playing sound with the headphones plugged in. So, PulseAudio effectively 
detects sound. In addition to the files attached by the ubuntu-bug program I 
have attached the output of alsa-info.sh.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antonio2172 F pulseaudio
   /dev/snd/controlC1:  antonio2172 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  5 21:39:08 2017
  InstallationDate: Installed on 2012-07-22 (1687 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to xenial on 2017-03-01 (4 days ago)
  dmi.bios.date: 10/23/2007
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.90
  dmi.board.name: ISRAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.90:bd10/23/2007:svnTOSHIBA:pnSatelliteProP200:pvrPSPB7E-00Q00HCE:rvnTOSHIBA:rnISRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite Pro P200
  dmi.product.version: PSPB7E-00Q00HCE
  dmi.sys.vendor: TOSHIBA

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

-- 
Mailing list: https://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 1609546] Re: nslookup doesn't works

[Colin Law]

@Gannet, I don't understand why you have changed the description. For me
I see a slow lookup, it does eventually resolve. Does the workaround in
#6 fix it? If not then it is a different bug.

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

Title:
  nslookup doesn't works

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://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 1609546] Re: nslookup not working

[Gannet]

** Summary changed:

- Slow DNS lookup through Netgear DG834G V4 router
+ nslookup not working

** Summary changed:

- nslookup not working
+ nslookup doesn't resolves

** Summary changed:

- nslookup doesn't resolves
+ nslookup doesn't works

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

Title:
  nslookup doesn't works

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://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 1670178] Re: ModemManager crashed with SIGSEGV in g_closure_invoke()

[Apport retracing service]

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

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 #1594799, 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/1670178/+attachment/4831933/+files/CoreDump.gz

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

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

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

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

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

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

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

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

Title:
  ModemManager crashed with SIGSEGV in g_closure_invoke()

Status in modemmanager package in Ubuntu:
  New

Bug description:
  modprobe mt7610u_sta

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: modemmanager 1.6.4-1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Sun Mar  5 14:19:19 2017
  ExecutablePath: /usr/sbin/ModemManager
  InstallationDate: Installed on 2015-10-01 (521 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150930)
  ProcCmdline: /usr/sbin/ModemManager
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x55abb8b0fab7:repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x55abb8b0fab7) ok
   source "%es:(%rdi)" (0x55abb8ba23fa) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: modemmanager
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ModemManager crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to zesty on 2017-01-01 (63 days ago)
  UserGroups:

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

-- 
Mailing list: https://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 1670177] [NEW] Cannot reconnect to my hidden network with plasma-nm on KUbuntu Trusty 14.04.5 LTS

[Seb Bonnard]

Public bug reported:

Hi,

After my ISP home router is being rebooted, my KUbuntu Trusty 14.04.5
LTS does neighter reconnect to my hidden wifi network automatically nor
manually with the Plasma NM applet.

The ONLY workaround I have found so far is by typing the following
command :

$ nmcli con up id MyWifi

knowing that "MyWifi" is my hidden wifi connection name in the applet
(my "ESSID" is different)

Btw, I'm using kernel "4.4.0-64-generic" and "plasma-nm" version
"0.9.3.3-0ubuntu1" :

$ lsb_release -sd
Ubuntu 14.04.5 LTS
$ uname -r
4.4.0-64-generic
$ apt-cache policy plasma-nm
plasma-nm:
  Installed: 0.9.3.3-0ubuntu1
  Candidate: 0.9.3.3-0ubuntu1
  Version table:
 *** 0.9.3.3-0ubuntu1 0
500 http://fr.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
100 /var/lib/dpkg/status


Can you please have a look and try and fix this bug ?

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7.3
ProcVersionSignature: Ubuntu 4.4.0-64.85~14.04.1-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Mar  5 19:47:51 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-09-22 (163 days ago)
InstallationMedia: Kubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
IpRoute:
 default via 192.168.0.254 dev eth0  proto static 
 192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.14  metric 1 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 wlan0  802-11-wireless   disconnected  
/org/freedesktop/NetworkManager/Devices/1  
 eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

** Affects: plasma-nm (Ubuntu)
 Importance: Undecided
 Status: New


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

** Package changed: network-manager (Ubuntu) => plasma-nm (Ubuntu)

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

Title:
  Cannot reconnect to my hidden network with plasma-nm on KUbuntu Trusty
  14.04.5 LTS

Status in plasma-nm package in Ubuntu:
  New

Bug description:
  Hi,

  After my ISP home router is being rebooted, my KUbuntu Trusty 14.04.5
  LTS does neighter reconnect to my hidden wifi network automatically
  nor manually with the Plasma NM applet.

  The ONLY workaround I have found so far is by typing the following
  command :

  $ nmcli con up id MyWifi

  knowing that "MyWifi" is my hidden wifi connection name in the applet
  (my "ESSID" is different)

  Btw, I'm using kernel "4.4.0-64-generic" and "plasma-nm" version
  "0.9.3.3-0ubuntu1" :

  $ lsb_release -sd
  Ubuntu 14.04.5 LTS
  $ uname -r
  4.4.0-64-generic
  $ apt-cache policy plasma-nm
  plasma-nm:
Installed: 0.9.3.3-0ubuntu1
Candidate: 0.9.3.3-0ubuntu1
Version table:
   *** 0.9.3.3-0ubuntu1 0
  500 http://fr.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages
  100 /var/lib/dpkg/status

  
  Can you please have a look and try and fix this bug ?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.3
  ProcVersionSignature: Ubuntu 4.4.0-64.85~14.04.1-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Mar  5 19:47:51 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-09-22 (163 days ago)
  InstallationMedia: Kubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  IpRoute:
   default via 192.168.0.254 dev eth0  proto static 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.14  metric 
1 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   disconnected  

[Touch-packages] [Bug 1670161] Re: systemd-udevd crashed with SIGABRT in ioctl()

[Apport retracing service]

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

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 #1497641, 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/1670161/+attachment/4831869/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-udevd crashed with SIGABRT in ioctl()

Status in systemd package in Ubuntu:
  New

Bug description:
  updated rebooted and this was presented to me

  lsb_release -rd;apt-cache policy systemd;uptime
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  systemd:
Installed: 232-18ubuntu1
Candidate: 232-18ubuntu1
Version table:
   *** 232-18ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status
   11:49:09 up 10 min,  1 user,  load average: 0.14, 0.90, 0.76

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: udev 232-18ubuntu1
  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
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Sun Mar  5 11:43:54 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2017-02-25 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170225)
  MachineType: Dell Inc. OptiPlex 5040
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-9-generic.efi.signed 
root=UUID=3fa02928-1c90-4941-b883-d04c86b76603 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ioctl () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-udevd crashed with SIGABRT in ioctl()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0T7D40
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd12/04/2015:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0T7D40:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 5040
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1421718] Re: [Ubuntu Phone Store] No message when no applications found

[Norbert]

Same on M10 with rc-proposed r268.

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

Title:
  [Ubuntu Phone Store] No message when no applications found

Status in Ubuntu UX:
  Won't Fix
Status in unity-scope-click package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Won't Fix

Bug description:
  Hi!

  Steps:
  1. Open Store.
  2. Search RRS (Not RSS).
  3. Bug: Nothing found, but you can't see a message for this.
  4. Search RSS.
  5. OK: You see 5 applications found message.

  Thanks in advance!

  --
  Desired resolution:

  This is part of a bigger redesign project (Scopes toolkit) and it
  can't be fixed as a single bug. The description and specs will be
  updated as soon as they are available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1421718/+subscriptions

-- 
Mailing list: https://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 1629541] Re: Ubuntu Touch should indicate that battery is charging with LED indicator on device

[Norbert]

Same on M10 with rc-proposed r268.

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

Title:
  Ubuntu Touch should indicate that battery is charging with LED
  indicator on device

Status in indicator-power package in Ubuntu:
  New

Bug description:
  I have BQ M10 FHD Ubuntu Edition with OTA-13.
  This device has LED indicator.

  Steps to reproduce:
  1. Boot device.
  2. Connect microusb charger.
  3. Device will start to charge (tray indicator becomes green with zigzag, but 
device's LED is off).

  Expected result:
  Device LED indicates charge level as on Android devices:
  * red for critical level
  * orange for middle
  * yellow for low 
  * green for almost charged).

  Actual result:
  Device LED is off.

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

-- 
Mailing list: https://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 1609546] Re: Slow DNS lookup through Netgear DG834G V4 router

[Gannet]

Hello. I'm recently upgraded to Zesty and the same messages in
journalctl (too many):

бер 05 14:33:56 p5q3 systemd-resolved[1223]: Using degraded feature set
(UDP) for DNS server 127.0.1.1.

Also:

~$ nslookup google.com
;; connection timed out; no servers could be reached

But:

~$ systemd-resolve google.com
google.com: 216.58.209.174
2a00:1450:400d:802::200e

-- Information acquired via protocol DNS in 65.9ms.
-- Data is authenticated: no

Also, I'm experiencing some difficulties connecting by some software,
for example teamviewer can't connect at all.

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

Title:
  Slow DNS lookup through Netgear DG834G V4 router

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://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 1623418] Re: gcc-as-needed.diff patch broke mpx support in GCC

[Launchpad Bug Tracker]

This bug was fixed in the package gcc-5 - 5.4.1-8ubuntu1

---
gcc-5 (5.4.1-8ubuntu1) zesty; urgency=medium

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

gcc-5 (5.4.1-8) unstable; urgency=medium

  * Update to SVN 20170304 (r245892, 5.4.1) from the gcc-5-branch.
- Fix PR libstdc++/79789, PR target/79514 (x86), PR target/79544 (PPC),
  PR lto/79579, PR target/79749 (sparc).
  * Build-depend on gnat-5 again.

 -- Matthias Klose   Sat, 04 Mar 2017 13:16:08 +0100

** Changed in: gcc-5 (Ubuntu)
   Status: New => Fix Released

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

Title:
  gcc-as-needed.diff patch broke mpx support in GCC

Status in gcc:
  Unknown
Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-6 package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Committed
Status in gcc-5 source package in Xenial:
  New
Status in binutils source package in Yakkety:
  Fix Committed
Status in gcc-5 source package in Yakkety:
  New
Status in gcc-6 source package in Yakkety:
  New

Bug description:
  [SRU Justification]
  gcc-5 from Ubuntu is configured with MPX support, but it is broken due
  to always-added linker option "-as-needed".

  [Test case]
  1. Pass -mmpx to gcc when building an arbitrary project on x86.
  2. Verify with ldd that the resulting executable is not linked against 
libmpx.so because the -as-needed flag has discarded the mpx library from being 
linked in.
  3. Install binutils and gcc-5 from -proposed.
  4. Rebuild the target, again with -mmpx.
  5. Verify with ldd that the new executable is linked against libmpx.so.
  6. Verify that there are no regressions in the binutils testsuite on any 
architectures, by manually checking the results in the build log.

  [Regression potential]
  This binutils patch implements new --push-state / --pop-state options which 
will not be used in the common case, only when -mmpx is passed.  When these 
flags are not in use, which is the default, it should have no effect on the 
behavior of the toolchain, so risk of regression is minimal.


  Here is the GCC upstream bug & fix

  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267

  https://gcc.gnu.org/viewcvs/gcc?view=revision=240057

  Would it be possible to backport this fix to Ubuntu gcc-5 build?

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

-- 
Mailing list: https://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 1663794] Re: Poweroff/Reboot Hangs :: Ubuntu 16.04

[Renê Barbosa]

Not so fast.. =(

Current status:

Reboot: Hang for a few seconds and ok, rebooting;
Shutdown: Hang forever until I push the power button;

I just give up, downgrading to 14.04 right now.

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

Title:
  Poweroff/Reboot Hangs :: Ubuntu 16.04

Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading my laptop (Dell Inspiron 5447) to Ubuntu 16.04 I saw
  that I can not shut down or restart after a few hours using the
  system. It hangs in Plymouth and stays that way until I force the
  shutdown by pressing the On / Off button.

  As this is a common bug (there are tons of questions on the Internet)
  I tried to fix it, but none of my attempts were effective. Already
  tried:

  1. Boot with acpi=force, acpi=noirq and pci=noacpi
  2. Disable Swap
  3. Run 'sync' before reboot or shutdown
  4. Use another kernel version (4.7, 4.8, 4.9 and 4.10 from mainline)
  5. Disabling USB 3.0
  6. Disabling TLP

  The most interesting thing is: I can shutdown/reboot normally using
  14.04 and the kernel from Xenial HWE and it's because of that I
  believe this is a systemd bug.

  The problem can also be reached just running "halt" of "systemctl
  halt" after booting 16.04 in this machine. Running these commands with
  "force" option is working fine.

  My Machine Specs:

  Dell Inspiron 5447 - BIOS A10
  Intel Core i5-4210 Processor
  8 GB RAM
  480 SSD Sandisk
  Hybrid Graphics (i915/amdgpu - Radeon R7 M265)

  --- BUG Information 

  Reproducible:
  Always

  Steps to Reproduce:
  1.Power on the machine
  2.Do something, anything or nothing for a few hours
  3.Try to shutdown/reboot using halt, shutdown, reboot, etc

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off/rebooting the machine.
  ---
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-10 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 5447
  Package: systemd 229-4ubuntu16
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=d725c86b-f9f7-4ae9-8cd8-7c27f3a8a06a ro quiet xhci_hcd.quirks=270336 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf

   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0MHP6R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/25/2016:svnDellInc.:pnInspiron5447:pvrA10:rvnDellInc.:rn0MHP6R:rvrA00:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Inspiron 5447
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.systemd.logind.conf: 2017-02-11T01:12:03.22
  mtime.conffile..etc.systemd.system.conf: 2017-02-09T22:18:49.885303
  mtime.conffile..etc.systemd.timesyncd.conf: 2017-02-09T22:19:05.646455

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

-- 
Mailing list: https://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 1670139] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: 子程序 新的 pre-removal script 傳回了錯誤退出狀態 1

[engho]

Public bug reported:

unable to upsate

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
Uname: Linux 4.4.0-49-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Sun Mar  5 10:02:43 2017
DpkgHistoryLog:
 Start-Date: 2017-03-05  10:02:35
 Commandline: apt-get -f install
 Requested-By: khu (1000)
 Upgrade: libcups2:i386 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-common:i386 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), libcupsmime1:i386 (2.1.3-4ubuntu0.1, 
2.1.3-4ubuntu0.2), libcupsppdc1:i386 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), 
cups-bsd:i386 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-core-drivers:i386 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-daemon:i386 (2.1.3-4, 
2.1.3-4ubuntu0.2), libcupsimage2:i386 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), 
libcupscgi1:i386 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-client:i386 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2)
ErrorMessage: 子程序 新的 pre-removal script 傳回了錯誤退出狀態 1
InstallationDate: Installed on 2016-02-26 (373 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Gigabyte Technology Co., Ltd. GA-880GM-D2H
Papersize: letter
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=ce7aed43-63d9-4820-92d4-b0d57fe1e06c ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=ce7aed43-63d9-4820-92d4-b0d57fe1e06c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: cups
Title: package cups-daemon 2.1.3-4 failed to install/upgrade: 子程序 新的 
pre-removal script 傳回了錯誤退出狀態 1
UpgradeStatus: Upgraded to xenial on 2016-08-13 (204 days ago)
dmi.bios.date: 08/31/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6
dmi.board.name: GA-880GM-D2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GM-D2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GM-D2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-880GM-D2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
modified.conffile..etc.default.cups:
 # Cups configure options
 
 # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
 # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
 # LOAD_LP_MODULE=yes
mtime.conffile..etc.default.cups: 2015-08-05T01:18:48

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


** Tags: apport-package i386 need-duplicate-check xenial

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: 子程序 新的 pre-
  removal script 傳回了錯誤退出狀態 1

Status in cups package in Ubuntu:
  New

Bug description:
  unable to upsate

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Sun Mar  5 10:02:43 2017
  DpkgHistoryLog:
   Start-Date: 2017-03-05  10:02:35
   Commandline: apt-get -f install
   Requested-By: khu (1000)
   Upgrade: libcups2:i386 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), 
cups-common:i386 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), libcupsmime1:i386 
(2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), libcupsppdc1:i386 (2.1.3-4ubuntu0.1, 
2.1.3-4ubuntu0.2), cups-bsd:i386 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), 
cups-core-drivers:i386 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), cups-daemon:i386 
(2.1.3-4, 2.1.3-4ubuntu0.2), libcupsimage2:i386 (2.1.3-4ubuntu0.1, 
2.1.3-4ubuntu0.2), libcupscgi1:i386 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2), 
cups-client:i386 (2.1.3-4ubuntu0.1, 2.1.3-4ubuntu0.2)
  ErrorMessage: 子程序 新的 pre-removal script 傳回了錯誤退出狀態 1
  InstallationDate: Installed on 2016-02-26 (373 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Gigabyte Technology Co., Ltd. GA-880GM-D2H
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=ce7aed43-63d9-4820-92d4-b0d57fe1e06c ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=ce7aed43-63d9-4820-92d4-b0d57fe1e06c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: 子程序 新的 
pre-removal script 傳回了錯誤退出狀態 1
  UpgradeStatus: Upgraded to xenial on 2016-08-13 (204 days ago)
  

[Touch-packages] [Bug 1670134] [NEW] problems starting computer

[Sara]

Public bug reported:

I have to log on several times before the main screen appears.  I see a
series of tests, all OK, and then at the end something about a start
manager still running.  I have no idea what that means.  But I'm happy
to do anything from my end that might help.  Best regards to you all.
Ubuntu is wonderful.  Sara

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
Uname: Linux 4.4.0-65-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Mar  5 15:43:30 2017
DistUpgraded: 2016-04-26 00:52:22,634 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 82G33/G31 Express Integrated Graphics 
Controller [103c:2a6f]
InstallationDate: Installed on 2015-12-18 (442 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
MachineType: HP-Pavilion FK484AV-ABA m9400t
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-65-generic 
root=UUID=15cff27c-2c62-4856-8f12-9cff492af8d2 ro vesafb.invalid=1 
plymouth:debug nopat drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-25 (313 days ago)
dmi.bios.date: 10/23/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.32
dmi.board.name: Benicia
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.01
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.32:bd10/23/2008:svnHP-Pavilion:pnFK484AV-ABAm9400t:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: FK484AV-ABA m9400t
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
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: Sun Mar  5 15:42:08 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 input USB OPTICAL MOUSE   MOUSE, id 8
 inputUSB USB Keykoard KEYBOARD, id 9
 inputUSB USB Keykoard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id9894 
 vendor HWP
xserver.version: 2:1.18.4-0ubuntu0.2

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


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

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

Title:
  problems starting computer

Status in xorg package in Ubuntu:
  New

Bug description:
  I have to log on several times before the main screen appears.  I see
  a series of tests, all OK, and then at the end something about a start
  manager still running.  I have no idea what that means.  But I'm happy
  to do anything from my end that might help.  Best regards to you all.
  Ubuntu is wonderful.  Sara

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
  Uname: Linux 4.4.0-65-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Mar  5 15:43:30 2017
  DistUpgraded: 2016-04-26 00:52:22,634 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 02) (prog-if 00 

[Touch-packages] [Bug 1670131] [NEW] package ca-certificates 20160104ubuntu0.14.04.1 failed to install/upgrade: eindeloze triggerlus; afgebroken

[Ofloo]

Public bug reported:

during do-release-upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ca-certificates 20160104ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Sun Mar  5 15:25:33 2017
DuplicateSignature: package:ca-certificates:20160104ubuntu0.14.04.1:eindeloze 
triggerlus; afgebroken
ErrorMessage: eindeloze triggerlus; afgebroken
InstallationDate: Installed on 2016-11-02 (122 days ago)
InstallationMedia: Ubuntu-Server 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: ca-certificates
Title: package ca-certificates 20160104ubuntu0.14.04.1 failed to 
install/upgrade: eindeloze triggerlus; afgebroken
UpgradeStatus: Upgraded to xenial on 2017-03-05 (0 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package ca-certificates 20160104ubuntu0.14.04.1 failed to
  install/upgrade: eindeloze triggerlus; afgebroken

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  during do-release-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Sun Mar  5 15:25:33 2017
  DuplicateSignature: package:ca-certificates:20160104ubuntu0.14.04.1:eindeloze 
triggerlus; afgebroken
  ErrorMessage: eindeloze triggerlus; afgebroken
  InstallationDate: Installed on 2016-11-02 (122 days ago)
  InstallationMedia: Ubuntu-Server 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu0.14.04.1 failed to 
install/upgrade: eindeloze triggerlus; afgebroken
  UpgradeStatus: Upgraded to xenial on 2017-03-05 (0 days ago)

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

-- 
Mailing list: https://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 1636573] Re: xinit flooding syslog

[Rahul Borkar]

Tried option mentioned in #11 but seems it has left broken packages.

When I try to fix the broken packages it is trying to remove all below
packages, but these are required ex. letsencrypt is required for my
Apache SSL certificates.

Please help

sudo apt-get install -f
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  augeas-lenses libaugeas0 python-augeas python-cffi-backend
  python-configargparse python-configobj python-cryptography python-dialog
  python-enum34 python-funcsigs python-idna python-ipaddress python-mock
  python-parsedatetime python-pbr python-psutil python-pyasn1 python-pyicu
  python-requests python-rfc3339 python-tz python-urllib3
  python-zope.component python-zope.event python-zope.hookable
  python-zope.interface
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED
  letsencrypt python-acme python-letsencrypt python-letsencrypt-apache
  python-ndg-httpsclient python-openssl
0 to upgrade, 0 to newly install, 6 to remove and 0 not to upgrade.
1 not fully installed or removed.
After this operation, 1,639 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

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

Title:
  xinit flooding syslog

Status in pyOpenSSL:
  Fix Released
Status in pyopenssl package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in pyopenssl source package in Yakkety:
  Triaged
Status in xorg source package in Yakkety:
  Invalid

Bug description:
  I am using xinit (1.3.4-3ubuntu1) to start an X11 session as follows
  (kodi is a media center):

  /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-
  standalone -- :1 -nolisten tcp vt8

  This used to work fine with Ubuntu 16.04, but since the upgrade to
  16.10 lots of log messages are sent to syslog. They are all
  repetitions of the following two lines:

  Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function 
Cryptography_rand_bytes() called, but @ffi.def_extern() was not called in the 
current subinterpreter.  Returning 0.
  Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function 
Cryptography_rand_status() called, but @ffi.def_extern() was not called in the 
current subinterpreter.  Returning 0.

  These messages amount to >200 GB per day, so this is eating up all the
  disk space.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Oct 25 18:41:22 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-06 (1753 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (11 days ago)

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

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

[lagerimsi]

Hi there!

still got this problem with the KDE Neon distribution based upon Ubuntu
16.04.

Solved this problem with a little shell-script based on this thread:
http://askubuntu.com/questions/765233/pulseaudio-fails-to-set-card-
profile-to-a2dp-sink-how-can-i-see-the-logs-and

The script is attached.


FIRST OF ALL:
Change the devices MAC-address in the variable inside the script! (can be found 
with "bluetoothctl" --> Device)


- Made a "chmod a-x bluetooth_headphone_reactivation.sh" to make it executable.


For automatic execution _at startup_ (only works if headset is already turned 
on):

- Added the script to the start/shutdown scripts in KDEs' control panel


For fast manual execution:
- Added an entry to the application-starter (you can also set a keyboad 
shortcut like "CTRL+ALT+H" and/or pin this starter to the window bar)


** Attachment added: "kde bluetooth headphone set a2dp_sink profile script 
workaround"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1577197/+attachment/4831629/+files/bluetooth_headphone_reactivation.sh

-- 
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:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

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:

[Touch-packages] [Bug 1670096] [NEW] objdump fails to disassemble rdrand

[Jeffrey Walton]

Public bug reported:

`objdump --disassemble` is not producing expected output for the rdrand
instruction. The same test using rdseed appears to be ok.

$ cat test.S
globalNASM_RDRAND
section   .text
align 16

NASM_RDRAND:
rdrand rax
jnc NASM_RDRAND
ret

$ nasm -f elf64 test.S -o test.o

$ objdump --disassemble test.o

test.o: file format elf64-x86-64

Disassembly of section .text:

 :
   0:   48 0f 07sysretq
   3:   f0 73 falock jae 0 
   6:   c3  retq



$ objdump -v
GNU objdump (GNU Binutils for Ubuntu) 2.26.1
Copyright (C) 2015 Free Software Foundation, Inc.

$ uname -a
Linux qotom 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

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



$ apt-cache show binutils
Package: binutils
Priority: optional
Section: devel
Installed-Size: 13328
Maintainer: Ubuntu Developers 
Original-Maintainer: Matthias Klose 
Architecture: amd64
Version: 2.26.1-1ubuntu1~16.04.3
Replaces: binutils-gold (<< 2.20.51.20100415), binutils-mingw-w64-i686 (<< 
2.23.52.20130612-1+3), binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3)
Provides: binutils-gold, elf-binutils
Depends: libc6 (>= 2.14), zlib1g (>= 1:1.2.0)
Suggests: binutils-doc (>= 2.26.1-1ubuntu1~16.04.3)
Conflicts: binutils-gold (<< 2.20.51.20100415), binutils-mingw-w64-i686 (<< 
2.23.52.20130612-1+3), binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3), 
elf-binutils, gas, modutils (<< 2.4.19-1)
Breaks: binutils-mingw-w64-i686 (<< 2.23.52.20130612-1+3), 
binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3)
Filename: pool/main/b/binutils/binutils_2.26.1-1ubuntu1~16.04.3_amd64.deb
Size: 2310310
MD5sum: 04b00c4b3ba1d86afbb679b63476d05a
SHA1: d15740302cd64dea8d4d853aa660b0bba3bb9105
SHA256: 1db714433416a0d9bd49f1174e85b55f65597fe337116267ad5ad16fc7f3e2dd
Description-en: GNU assembler, linker and binary utilities
 The programs in this package are used to assemble, link and manipulate
 binary and object files.  They may be used in conjunction with a compiler
 and various libraries to build programs.
Description-md5: fde49b4cfeaad346a6e094f973da28d7
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Build-Essential: yes
Origin: Ubuntu
Supported: 5y
Task: ubuntu-desktop, ubuntu-usb, kubuntu-desktop, kubuntu-full, 
edubuntu-desktop, edubuntu-usb, xubuntu-core, xubuntu-desktop, 
mythbuntu-frontend, mythbuntu-desktop, mythbuntu-backend-slave, 
mythbuntu-backend-master, mythbuntu-backend-master, lubuntu-live, 
ubuntustudio-desktop-core, ubuntustudio-desktop, ubuntu-gnome-desktop, 
ubuntu-touch, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, 
ubuntu-mate-cloudtop

Package: binutils
Priority: optional
Section: devel
Installed-Size: 13332
Maintainer: Ubuntu Core developers 
Original-Maintainer: Matthias Klose 
Architecture: amd64
Version: 2.26-8ubuntu2
Replaces: binutils-gold (<< 2.20.51.20100415), binutils-mingw-w64-i686 (<< 
2.23.52.20130612-1+3), binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3)
Provides: binutils-gold, elf-binutils
Depends: libc6 (>= 2.14), zlib1g (>= 1:1.2.0)
Suggests: binutils-doc (>= 2.26-8ubuntu2)
Conflicts: binutils-gold (<< 2.20.51.20100415), binutils-mingw-w64-i686 (<< 
2.23.52.20130612-1+3), binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3), 
elf-binutils, gas, modutils (<< 2.4.19-1)
Breaks: binutils-mingw-w64-i686 (<< 2.23.52.20130612-1+3), 
binutils-mingw-w64-x86-64 (<< 2.23.52.20130612-1+3)
Filename: pool/main/b/binutils/binutils_2.26-8ubuntu2_amd64.deb
Size: 2302996
MD5sum: 94899981678c27e438f85e554746deff
SHA1: 3197b042645a7ee607391f873a4f7012d888bf3c
SHA256: 053b01a92bdb39329c199e85a621910a9d81ad4ec9d65d9e7e59ff4ab2709d55
Description-en: GNU assembler, linker and binary utilities
 The programs in this package are used to assemble, link and manipulate
 binary and object files.  They may be used in conjunction with a compiler
 and various libraries to build programs.
Description-md5: fde49b4cfeaad346a6e094f973da28d7
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Build-Essential: yes
Origin: Ubuntu
Supported: 5y
Task: ubuntu-desktop, ubuntu-usb, kubuntu-desktop, kubuntu-full, 
edubuntu-desktop, edubuntu-usb, xubuntu-core, xubuntu-desktop, 
mythbuntu-frontend, mythbuntu-desktop, mythbuntu-backend-slave, 
mythbuntu-backend-master, mythbuntu-backend-master, lubuntu-live, 
ubuntustudio-desktop-core, ubuntustudio-desktop, ubuntu-gnome-desktop, 
ubuntu-touch, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, 
ubuntu-mate-cloudtop

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

-- 
You received this bug 

[Touch-packages] [Bug 1670093] [NEW] WWAN card connection failed if ipv6 is enabled

[Jan Kozusznik]

Public bug reported:

I installed WWAN card to a laptop and there was problem with connection.
After debugging, I found that it crash on event “failed to open
'/proc/sys/net/ipv6/conf/cdc-wdm0//use_tempaddr”. Disable ipv6 for
broadband connection helped but it is not the right bugfix. Problem is
that network interface for wwan card is registered as wwp0s20f0u2i12 –
and exists file /proc/sys/net/ipv6/conf/wwp0s20f0u2i12/use_tempaddr. On
the other hand network manager sees device (according to “nmcli device”)
cdc-wdm0. Disabling consistent network device naming did not help – wwan
interface had name wwan0 after that. HW: Dell Latitude e5570, WWAN –
MDM,WRLES,DW5811E,E7,4G,HF. OS: Ubuntu 16.04.2 64bit, Kernel
4.4.0-64-generic

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.2-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
Uname: Linux 4.4.0-65-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Mar  5 10:59:33 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-10-26 (130 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 100.85.58.157 dev wwp0s20f0u2i12  proto static  metric 700 
 100.85.58.152/29 dev wwp0s20f0u2i12  proto kernel  scope link  src 
100.85.58.156  metric 700 
 169.254.0.0/16 dev wwp0s20f0u2i12  scope link  metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
 [connection]
 wifi.powersave = 0
mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2016-11-24T19:51:44.546944
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
 cdc-wdm0   gsm   connected /org/freedesktop/NetworkManager/Devices/3  
T-Mobile Default  e45dd5e2-7424-4403-adae-4defe6c707b7  
/org/freedesktop/NetworkManager/ActiveConnection/3 
 wlp2s0 wifi  disconnected  /org/freedesktop/NetworkManager/Devices/1  
------  
   
 enp0s31f6  ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/2  
------  
   
 lo loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
------
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug xenial

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

Title:
  WWAN card connection failed if ipv6 is enabled

Status in network-manager package in Ubuntu:
  New

Bug description:
  I installed WWAN card to a laptop and there was problem with
  connection. After debugging, I found that it crash on event “failed to
  open '/proc/sys/net/ipv6/conf/cdc-wdm0//use_tempaddr”. Disable ipv6
  for broadband connection helped but it is not the right bugfix.
  Problem is that network interface for wwan card is registered as
  wwp0s20f0u2i12 – and exists file
  /proc/sys/net/ipv6/conf/wwp0s20f0u2i12/use_tempaddr. On the other hand
  network manager sees device (according to “nmcli device”) cdc-wdm0.
  Disabling consistent network device naming did not help – wwan
  interface had name wwan0 after that. HW: Dell Latitude e5570, WWAN –
  MDM,WRLES,DW5811E,E7,4G,HF. OS: Ubuntu 16.04.2 64bit, Kernel
  4.4.0-64-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
  Uname: Linux 4.4.0-65-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar  5 10:59:33 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-26 (130 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 100.85.58.157 dev wwp0s20f0u2i12  proto static  metric 700 
   100.85.58.152/29 dev wwp0s20f0u2i12  proto kernel  scope link  src 
100.85.58.156  metric 700 
   169.254.0.0/16 dev wwp0s20f0u2i12  scope link  metric 

[Touch-packages] [Bug 1670036] Re: 4.0.6-2ubuntu01 has problems reading and writing JPEG compressed images

[John Cupitt]

Even Rouault on the libtiff mailing list has looked into this as well --
he says the cause is a misapplied patch.

Unfortunately i can't link to his mail as the libtiff mailing list
archive index has stopped being updated, but I copy-paste his mail
below:

---
Even Rouault 
to tiff, me

On samedi 4 mars 2017 18:51:20 CET jcup...@gmail.com wrote:
> tar xf tiff_4.0.6-2ubuntu0.1.debian.tar.xz
> tar xf tiff_4.0.6.orig.tar.gz
> cd tiff-4.0.6
> for i in ../debian/patches/*.patch; do patch -p1 < $i; done

Actually to reproduce, you need to apply the patches in a precise order
with

for i in `cat ../debian/patches/series`; do \
patch -p1 <../debian/patches/$i; done

I've then compared the patched libtiff/tif_dirread.c with the official
one from CVS, and I understand now what happens in Debian/Ubuntu.

It appears that the following snippet

  if( dp->tdir_count > 0 && data[dp->tdir_count-1] !=
'\0' )

{

TIFFWarningExt(tif->tif_clientdata,module,"ASCII value for tag \"%s\"
does not end in null byte. Forcing it to be null",fip->field_name);

data[dp->tdir_count-1] = '\0';

}

that in official libtiff is applied in the TIFF_SETGET_C16_ASCII cases
(line 5017 in HEAD) and in the TIFF_SETGET_C32_ASCII cases (line 5194 in
CVS HEAD) has been wrongly applied in Debian in the
TIFF_SETGET_C16_UINT8 case (line 5008) and TIFF_SETGET_C32_UINT8 case
(line 5180)...

This explains the warning about the JPEGTables...

Unfortunately "make check" in the Debian patched libtiff still passes,
so they have some excuse. Not so surprised since the test suite is
rather small.

Even
-- 
Spatialys - Geospatial professional services
http://www.spatialys.com

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

Title:
  4.0.6-2ubuntu01 has problems reading and writing JPEG compressed
  images

Status in tiff package in Ubuntu:
  New

Bug description:
  The patches applied to libtiff 4.0.6 in 4.0.6-2ubuntu01 seem to break
  JPEG tiff read and write.

  To reproduce:

  $ tiffcp -c jpeg k2a.tif x.tif

  (where k2a.tif is a simple uncompressed RGB strip tiff) appears to
  work. However, x.tif, the output, will now not read without warnings:

  $ tiffcp x.tif y.tif
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it to be null.
  JPEGLib: Warning, Premature end of JPEG file.

  This was working fine until a couple of days ago, so I guess it's one
  of the most recent patches.

  Some packages using libtiff seem to be broken too. For example,
  openslide, which uses libtiff to load jp2k-compressed slide images, is
  no longer working:

  $ openslide-write-png CMU-1-Small-Region.svs 0 0 0 100 100 x.png
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it to be null.
  TIFFFetchNormalTag: Warning, ASCII value for tag "JPEGTables" does not end in 
null byte. Forcing it ... repeats 8 more times
  openslide-write-png: Premature end of JPEG file

  and x.png is not a valid PNG image.  The test .svs image may be
  downloaded here:

  http://openslide.cs.cmu.edu/download/openslide-testdata/Aperio/

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

-- 
Mailing list: https://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 1670091] [NEW] pointeur

[chabert]

Public bug reported:

Bonjour
dernièremment sous ubuntu 16.10 mo pointeur est invisible dans la moitié 
inférieure de mon écran 
si je démare avec option avancé ubuntu ancienne version linux cela ne le fait 
pas
cordialement YC

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

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

Title:
  pointeur

Status in xorg package in Ubuntu:
  New

Bug description:
  Bonjour
  dernièremment sous ubuntu 16.10 mo pointeur est invisible dans la moitié 
inférieure de mon écran 
  si je démare avec option avancé ubuntu ancienne version linux cela ne le fait 
pas
  cordialement YC

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

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