[Touch-packages] [Bug 1654817] [NEW] package libgtk2.0-bin 2.24.30-4ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 2

2017-01-07 Thread Christopher Morrow
Public bug reported:

When I attempted to install libgtk2.0-0 it said something along the
lines of needing to remove the old package 2.24.30-4ubuntu2 (I think, I
closed the terminal window), and I was getting a permission denied
despite running as root. Putting SELinux into permissive mode allowed
the install to take place. I think this might be an issue with SELinux
policy for Ubuntu.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libgtk2.0-bin 2.24.30-4ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Sun Jan  8 00:54:30 2017
ErrorMessage: subprocess new pre-removal script returned error exit status 2
InstallationDate: Installed on 2017-01-06 (2 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: gtk+2.0
Title: package libgtk2.0-bin 2.24.30-4ubuntu3 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check selinux yakkety

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

Title:
  package libgtk2.0-bin 2.24.30-4ubuntu3 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 2

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  When I attempted to install libgtk2.0-0 it said something along the
  lines of needing to remove the old package 2.24.30-4ubuntu2 (I think,
  I closed the terminal window), and I was getting a permission denied
  despite running as root. Putting SELinux into permissive mode allowed
  the install to take place. I think this might be an issue with SELinux
  policy for Ubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libgtk2.0-bin 2.24.30-4ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Sun Jan  8 00:54:30 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 2
  InstallationDate: Installed on 2017-01-06 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gtk+2.0
  Title: package libgtk2.0-bin 2.24.30-4ubuntu3 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1654817/+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 1576215] Re: Network Manager regularly thinks my wifi is a wired device

2017-01-07 Thread intuiter
*** This bug is a duplicate of bug 1574347 ***
https://bugs.launchpad.net/bugs/1574347

I started having this problem after a regular package upgrade. 
Ubuntu 16.04.1 LTS
Current Network Manager version in my system: 1.2.2 

I hope it gets fixed in future versions. For now the workaround is to
run "systemctl restart network-manager.service" after every reboot.

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

Title:
  Network Manager regularly thinks my wifi is a wired device

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When I boot up my network doesn't automatically connect.  I instead
  see when I click the network manager applet that it's got no Wifi
  devices listed.  It thinks my wireless card is an ethernet device.
  This isn't true and I have no ethernet devices in my system.

  When this situation happens if I issue /etc/init.d/network-manager
  restart it comes back up thinking it's a wireless device and happily
  associates with my saved SSID.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 28 09:03:13 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160406-0
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-13 (14 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160406-07:32
  IpRoute:
   
  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  
CONNECTION  CON-UUID
  CON-PATH   
   wlp58s0  ethernet  connecting (getting IP configuration)  
/org/freedesktop/NetworkManager/Devices/1  Wired connection 1  
1c8c4cab-09d7-4a42-bfc4-aed14caf6a46  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo   loopback  unmanaged  
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576215/+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 1637731] Re: [SRU] Update to 2.48.2 in Xenial

2017-01-07 Thread Mathew Hodson
** Tags added: upgrade-software-version

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

Title:
  [SRU] Update to 2.48.2 in Xenial

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Committed

Bug description:
  [Description]
  Upstream have released a new bugfix release 2.48.2.

  [Changes]
  https://git.gnome.org/browse/glib/tree/NEWS?h=glib-2-48

  Bugs fixed:
   547200 g_utf8_find_next_char() issues
   673101 resource compiler dependency generation not working for generated 
files
   700756 GFile.new_for_path arguments misses (type filename) annotation
   725902 build: simplify dtrace configuration
   728207 gsocketservice: Documentation does not mention that is already 
active...
   730187 glocalfileoutputstream: Fix an FD leak in an error path
   746685 Doc: clarify that g_variant_get_data() can be used instead of 
g_varia...
   750257 GSettings changed signal should clearly state the order required
   753231 Memory is potentially used after free
   755439 Memory leak in gdbusproxy.c
   760115 gtestutils: add missing dash in seed argument's --help documentation
   760423 gio-querymodules prints error messages as question marks on some 
locales
   761810 gio: Support using GDBusObjectManagerServer at path ‘/’
   766211 Fix the upper bound in g_unichar_iswide_bsearch
   766899 Superflous HTML/XML comments in GDBusProxyTypeFunc documentation 
string
   766933 GSocketAddress leaks in 
gnetworkmonitornetlink.c:read_netlink_messages()
   767172 docs: Move GIO_USE_VFS to "okay for production" section
   767218 Remove a UTF-8 ellipsis from gsignal.h
   767824 Some UTC timezones incorrectly recognized on Windows 7
   767949 Typos in glib docs
   768453 Gdbus test: compilation fails due to -Werror=format-y2k errors
   768504 keyfile: g_key_file_get_double behavior doesn't follow documentation
   768551 Test failure: test_socket_address_to_string
   768560 gio/tests/gsettings: fix GSettings reference leaks in some tests
   768806 gdbus tool must swallow -- argument
   769027 Docs misleadingly imply G_CHECKSUM_SHA512 is available since 2.16

  Translations updated:
   Indonesian
   Portuguese
   Turkish

  [QA, testing, regression potential]
  Under the GNOME MRE, you can believe all bugs upstream says are fixed are 
really fixed. Just test the system and make sure there are no regressions (e.g. 
look at errors.ubuntu.com).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1637731/+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 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service

2017-01-07 Thread Mathew Hodson
** Changed in: ido (Ubuntu Xenial)
   Importance: Undecided => Medium

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

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

Title:
  Using calendar with keys might cause Indicator-datetime to crash
  unity-panel-service

Status in ido package in Ubuntu:
  Fix Released
Status in ido source package in Xenial:
  Fix Committed
Status in ido source package in Yakkety:
  Fix Committed

Bug description:
  [Impact] 
  Unity panel service crashes (removing indicators from panel) when calendar 
menu is opened and there are some key presses.

  [Test Case]
  This is a quite random bug that is not easy to reproduce, it happens 
sometimes that you open the indicator-datetime and after a keypress the panel 
crashes.

  [Regression Potential]
  Nothing expected, but calendar item in datetime might behave differently on 
key-presses.
  Although the fix is quite safe since we're just ensuring that we disconnect 
from parent widget signals on menuitem destruction.

  ===

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity.  This problem was most recently seen with version
  7.3.2+15.10.20151002.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 1562344] Re: Not working hotkeys for brightness in HP ProBook 640 G2

2017-01-07 Thread Mathew Hodson
** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  Not working hotkeys for brightness in HP ProBook 640 G2

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Committed

Bug description:
  Description
  =

  It seems like a new HP laptops are using new vendor string which brokes
  hotkeys.

  
  Workaround
  ==

  Just to put following lines to fix hotkeys for brithness.

  evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
   KEYBOARD_KEY_92=brightnessdown
   KEYBOARD_KEY_97=brightnessup

  
  Proposed solution
  ===

  The issue was already solved by upstream systemd[1] developers 25 days
  ago, so resync of hwdb/60-keyboard.hwdb should be enough.

[1]: commit 325de0ac23596209c252ebcc934dd5f5926fe2b6

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 26 17:20:25 2016
  InstallationDate: Installed on 2016-02-25 (30 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:7053 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 0a5c:640b Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 640 G2
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-34-generic 
root=UUID=4bccba3c-0c3c-430f-bfef-b033d9fcd45c ro 
cryptopts=target=root,source=/dev/disk/by-uuid/9108c404-6977-4914-afd8-40b3e8824d30
 quiet splash vt.handoff=7
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: HP
  dmi.bios.version: N76 Ver. 01.00
  dmi.board.name: 80FD
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 22.36
  dmi.chassis.asset.tag: 5CG605253R
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN76Ver.01.00:bd12/07/2015:svnHP:pnHPProBook640G2:pvr:rvnHP:rn80FD:rvrKBCVersion22.36:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 640 G2
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1562344/+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 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives

2017-01-07 Thread Mathew Hodson
** Changed in: systemd (Ubuntu Xenial)
   Importance: Undecided => Wishlist

** Changed in: systemd (Ubuntu Trusty)
   Importance: Undecided => Wishlist

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

Title:
  introduce disk/by-id (model_serial) symlinks for NVMe drives

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

Bug description:
  [Impact]

  NVMe drives can't be identified/accessed via /dev/disk/by-id/nvme-
  SERIAL symlinks.

  [Test Case]

  On a system with an NVMe drive, check the /dev/disk/by-id/ directory;
  with the patch, it will contain link(s) named by the drive serial
  number. This should be the *only* change in `ls -l /dev/disk/*/*`.

  On a system without NVMe, verify that `ls -l /dev/disk/*/*` is
  identical (aside from dates, of course) before and after the upgrade
  to the -proposed version.

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or  clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This patch is already included upstream and in zesty systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1642903/+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 1654814] [NEW] package gstreamer1.0-plugins-bad:amd64 1.8.2-1ubuntu0.1 failed to install/upgrade: pakket bevindt zich in een erg slechte en inconsistente staat; u zou het opnieu

2017-01-07 Thread BJC2014
Public bug reported:

The plugins where marked as corrupt or bad, and had to be removed, as
far as I can see they could not be completely removed, this was because
my system went bad after a large update which could not be upgraded
because of the bad packages like gstreamer. Now my ubuntu 16.04 is
looking bad.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gstreamer1.0-plugins-bad:amd64 1.8.2-1ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Sun Jan  8 06:28:37 2017
DpkgTerminalLog:
 dpkg: fout bij verwerken van pakket gstreamer1.0-plugins-bad:amd64 (--remove):
  pakket bevindt zich in een erg slechte en inconsistente staat; u zou het
  opnieuw moeten installeren alvorens het te proberen verwijderen.
ErrorMessage: pakket bevindt zich in een erg slechte en inconsistente staat; u 
zou het  opnieuw moeten installeren alvorens het te proberen verwijderen.
InstallationDate: Installed on 2016-08-04 (156 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: gst-plugins-bad1.0
Title: package gstreamer1.0-plugins-bad:amd64 1.8.2-1ubuntu0.1 failed to 
install/upgrade: pakket bevindt zich in een erg slechte en inconsistente staat; 
u zou het  opnieuw moeten installeren alvorens het te proberen verwijderen.
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gst-plugins-bad1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package gstreamer1.0-plugins-bad:amd64 1.8.2-1ubuntu0.1 failed to
  install/upgrade: pakket bevindt zich in een erg slechte en
  inconsistente staat; u zou het  opnieuw moeten installeren alvorens
  het te proberen verwijderen.

Status in gst-plugins-bad1.0 package in Ubuntu:
  New

Bug description:
  The plugins where marked as corrupt or bad, and had to be removed, as
  far as I can see they could not be completely removed, this was
  because my system went bad after a large update which could not be
  upgraded because of the bad packages like gstreamer. Now my ubuntu
  16.04 is looking bad.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gstreamer1.0-plugins-bad:amd64 1.8.2-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Sun Jan  8 06:28:37 2017
  DpkgTerminalLog:
   dpkg: fout bij verwerken van pakket gstreamer1.0-plugins-bad:amd64 
(--remove):
pakket bevindt zich in een erg slechte en inconsistente staat; u zou het
opnieuw moeten installeren alvorens het te proberen verwijderen.
  ErrorMessage: pakket bevindt zich in een erg slechte en inconsistente staat; 
u zou het  opnieuw moeten installeren alvorens het te proberen verwijderen.
  InstallationDate: Installed on 2016-08-04 (156 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: gst-plugins-bad1.0
  Title: package gstreamer1.0-plugins-bad:amd64 1.8.2-1ubuntu0.1 failed to 
install/upgrade: pakket bevindt zich in een erg slechte en inconsistente staat; 
u zou het  opnieuw moeten installeren alvorens het te proberen verwijderen.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1654814/+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 1640330] Re: I don't know

2017-01-07 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  I don't know

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I'm sorry I do't know

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Tue Nov  8 20:31:22 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C79 [GeForce 9300] [10de:0864] (rev b1) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company C79 [GeForce 9300] [103c:2a7c]
  InstallationDate: Installed on 2016-08-24 (75 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: Compaq-Presario NQ918AA-ABZ CQ5023IT
  ProcEnviron:
   LANGUAGE=it_IT
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug=1 quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.04
  dmi.board.name: Newark
  dmi.board.vendor: FOXCONN
  dmi.board.version: HP P/N
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd01/16/2009:svnCompaq-Presario:pnNQ918AA-ABZCQ5023IT:pvr:rvnFOXCONN:rnNewark:rvrHPP/N:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: NQ918AA-ABZ CQ5023IT
  dmi.sys.vendor: Compaq-Presario
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Nov  8 19:35:43 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1640330/+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 1640345] Re: Please check about these issues

2017-01-07 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Please check about these issues

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Please check about these issues

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Wed Nov  9 00:18:36 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation C79 [GeForce 9300] [10de:0864] (rev b1) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company C79 [GeForce 9300] [103c:2a7c]
  InstallationDate: Installed on 2016-08-24 (76 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: Compaq-Presario NQ918AA-ABZ CQ5023IT
  ProcEnviron:
   LANGUAGE=it_IT
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug=1 quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.04
  dmi.board.name: Newark
  dmi.board.vendor: FOXCONN
  dmi.board.version: HP P/N
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd01/16/2009:svnCompaq-Presario:pnNQ918AA-ABZCQ5023IT:pvr:rvnFOXCONN:rnNewark:rvrHPP/N:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: NQ918AA-ABZ CQ5023IT
  dmi.sys.vendor: Compaq-Presario
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Nov  8 19:35:43 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1640345/+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 1504688] Re: fsck runs on every boot (clean install, single ext4 filesystem)

2017-01-07 Thread owise1
Hi, I also appear to have this bug.  Does not materially impact boot
time as is only involves the EFI system partition but it is a pain as
when I switch to any virtual terminal I see that boot message but do not
get a cmd prompt.

Clean install of 16.04 on an Intel NUC with ssd drive.

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

Title:
  fsck runs on every boot (clean install, single ext4 filesystem)

Status in upstart package in Ubuntu:
  Invalid

Bug description:
  fsck runs early on *every* boot (and always says "/dev/sda1: clean ...")
  The system was always shut down using the regular Unity mechanism (Gear->Shut 
Down...)

  Strangely, the "Last checked" time shown by "sudo dumpe2fs /dev/sda1"
  shows the date of installation and never changes.

  This system is a brand new, clean install from the 15.10 beta2 iso, with 
subsequent updates.
  I took all the installer defaults, which created a single ext4 file system.

  Please see attached:
bootscreen.png - screen shot of fsck output at start of bootup (from VM 
window)
dumpe2fs_out.txt - output from "sudo dumpe2fs /dev/sda1"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: upstart 1.13.2-0ubuntu16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  9 15:10:05 2015
  InstallationDate: Installed on 2015-10-07 (2 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=5944d29d-f058-4836-a160-4da2d77554e3 ro quiet splash
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemJobs:
   Error: command ['initctl', '--system', 'list'] failed with exit code 1: 
initctl: Name "com.ubuntu.Upstart" does not exist
  UpstartRunningSystemVersion: Error: command ['initctl', '--system', 
'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not 
exist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1504688/+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 1651518] Comment bridged from LTC Bugzilla

2017-01-07 Thread bugproxy
--- Comment From cdead...@us.ibm.com 2017-01-07 21:22 EDT---
cde00 (cdead...@us.ibm.com) added native attachment 
/tmp/AIXOS06698101/systemd_infinity.debdiff on 2017-01-07 20:22:29
cde00 (cdead...@us.ibm.com) added native attachment 
/tmp/AIXOS06698101/systemd_229.patch on 2017-01-07 20:22:29

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

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

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Yakkety:
  New

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

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

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

  htxubuntu-425

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

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

  root@busybee:~# cat /tmp/htxerr

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

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

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

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

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

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

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

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

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

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

  No errors logged in syslog after starting HTX:

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

  lpar: yellowbee

  root@yellowbee:~# cat /tmp/htxerr

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

 

[Touch-packages] [Bug 1651518] infinity parsing patch

2017-01-07 Thread bugproxy
--- Comment on attachment From ru...@us.ibm.com 2017-01-07 21:12 EDT---


It looks like the commit referenced earlier also builds upon the addition of 
the config_parse_tasks_max() function added in commit 6300502b .

The following example patch (based on systemd_229-4ubuntu14) focuses on
just the UserTasksMax "infinity" parsing.

** Attachment added: "infinity parsing patch"
   
https://bugs.launchpad.net/bugs/1651518/+attachment/4801480/+files/systemd_229.patch

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

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

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Yakkety:
  New

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

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

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

  htxubuntu-425

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

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

  root@busybee:~# cat /tmp/htxerr

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

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

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

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

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

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

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

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

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

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

  No errors logged in syslog after starting HTX:

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

  lpar: yellowbee

  root@yellowbee:~# cat /tmp/htxerr

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  # cat 

[Touch-packages] [Bug 1651518] debdiff between systemd_229-4ubuntu14 and test build systemd_229-4ubuntu15

2017-01-07 Thread bugproxy
--- Comment on attachment From ru...@us.ibm.com 2017-01-07 21:15 EDT---


A test build of systemd with the previous patch applied resolved the parsing 
issue in my testing.

# cat /etc/systemd/logind.conf.d/usertasks.conf
[Login]
UserTasksMax=infinity

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

** Attachment added: "debdiff between systemd_229-4ubuntu14 and test build 
systemd_229-4ubuntu15"
   
https://bugs.launchpad.net/bugs/1651518/+attachment/4801481/+files/systemd_infinity.debdiff

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

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

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Yakkety:
  New

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

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

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

  htxubuntu-425

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

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

  root@busybee:~# cat /tmp/htxerr

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

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

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

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

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

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

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

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

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

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

  No errors logged in syslog after starting HTX:

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

  lpar: yellowbee

  root@yellowbee:~# cat /tmp/htxerr

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1579760] Re: Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

2017-01-07 Thread Jord Swart
Since this is an old bug: I confirm the issue is still there.

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

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

Title:
  Protocol RC-6 no longer available for soundgraph imon (15c2:ffdc)

Status in linux package in Ubuntu:
  Confirmed
Status in v4l-utils package in Ubuntu:
  New

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

  $ apt-cache policy ir-keytable
  ir-keytable:
Installed: 1.10.0-1
Candidate: 1.10.0-1
Version table:
   *** 1.10.0-1 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  == What used to happen in older releases:
  In older versions of ir-keytable I was able to set my soundgraph imon 
(15c2:ffdc) to use protocol RC-6.

  The way I did it was by changing the file:
  /lib/udev/rc_keymaps/imon_pad
   
  and make the first line look like:
  # table imon_pad, type: RC-6

  == What actually happens in the current release:
  In the 16.04 release of Ubuntu this is no longer possible. The output of 
ir-keytable also doesn't list the RC-6 protocol as available.

  $ sudo ir-keytable
  Found /sys/class/rc/rc0/ (/dev/input/event4) with:
Driver imon, table rc-imon-pad
Supported protocols: other
Enabled protocols:
Name: iMON Remote (15c2:ffdc)
bus: 3, vendor/product: 15c2:ffdc, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms

  With the "other" protocol enabled my arrow keys deliver double key
  clicks, so clicking up once actually moves the cursor two lines up (in
  kodi that is).

  Forcing the device to RC-6 with:
  $ sudo echo RC-6 > /sys/class/rc/rc0/protocols

  fixes the double clicks.

  == What should happen in the current release:
  IMHO ir-keytable should actually list RC-6 as a protocol for this (specific) 
device and it should be relatively easy to assign this protocol. Either by 
using ir-keytable, or updating the imon_pad file.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josw   1067 F kodi.bin
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8e04b16f-858f-47e3-a693-18e5f068e95b
  InstallationDate: Installed on 2014-08-24 (664 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  Package: v4l-utils
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=5bfca808-2f63-4d92-90f6-724797c6b2dc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (41 days ago)
  UserGroups: adm audio cdrom dip fuse lpadmin plugdev pulse sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-205
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-205:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579760/+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 1577494] Re: application dies with 'VMware: vmw_ioctl_command error Invalid argument.'

2017-01-07 Thread Slava
Sorry, I have just spotted that this thread is for Stellarium but I run
Gazebo simulator and encountered the same issue. The solution fixed the
issue for me with Gazebo.

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

Title:
  application dies with 'VMware: vmw_ioctl_command error Invalid
  argument.'

Status in ROS:
  New
Status in Stellarium:
  Incomplete
Status in blender package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  running stellarium in ubuntu 16.04 in a VMWare 12.1.1 virtual machine.
  thanks.

  


  jstokes@ubuntu1604:~$ stellarium

  ** (stellarium:1768): WARNING **: Couldn't connect to accessibility bus: 
Failed to connect to socket /tmp/dbus-6Rt5CAvHFy: Connection refused
   ---
  [ This is Stellarium 0.14.3 - http://www.stellarium.org ]
  [ Copyright (C) 2000-2016 Fabien Chereau et al. ]
   ---
  Writing log file to: "/home/jstokes/.stellarium/log.txt"
  File search paths:
0 .  "/home/jstokes/.stellarium"
1 .  "/usr/share/stellarium"
  Config file is:  "/home/jstokes/.stellarium/config.ini"
  Detected: OpenGL "3.0"
  Driver version string: "3.0 Mesa 11.2.0"
  GL vendor is "VMware, Inc."
  GL renderer is "Gallium 0.4 on SVGA3D; build: RELEASE;  LLVM;"
  GL Shading Language version is "1.30"
  MESA Version Number detected:  11.2
  Mesa version is fine, we should not see a graphics problem.
  GLSL Version Number detected:  1.3
  GLSL version is fine, we should not see a graphics problem.
  Cache directory is:  "/home/jstokes/.cache/stellarium/stellarium"
  Sky language is  "en_US"
  Application language is  "en_US"
  Loading Solar System data ...
  Loading star data ...
  "Loading \"/usr/share/stellarium/stars/default/stars_0_0v0_5.cat\": 0_0v0_2; 
4963"
  "Loading \"/usr/share/stellarium/stars/default/stars_1_0v0_5.cat\": 1_0v0_2; 
21598"
  "Loading \"/usr/share/stellarium/stars/default/stars_2_0v0_5.cat\": 2_0v0_2; 
150090"
  "Loading \"/usr/share/stellarium/stars/default/stars_3_1v0_3.cat\": 3_1v0_3; 
428466"
  Finished loading star catalogue data, max_geodesic_level:  3
  navigation/preset_sky_time is a double - treating as jday: "2451514.25001"
  Reloading DSO data...
  Loaded 10756 DSO records
  Loading DSO name data ...
  Loaded 221 / 297 DSO name records successfully
  Loading star names from 
"/usr/share/stellarium/skycultures/western/star_names.fab"
  Loaded 339 / 339 common star names
  Loading star names from "/usr/share/stellarium/stars/default/name.fab"
  Loaded 4506 / 4506 scientific star names
  Loading variable stars from 
"/usr/share/stellarium/stars/default/gcvs_hip_part.dat"
  Loaded 6916 / 6916 variable stars
  Loading cross-index data from 
"/usr/share/stellarium/stars/default/cross-index.dat"
  Loaded 108279 / 108279 cross-index data records
  Loaded 88 / 88 constellation records successfully for culture "western"
  Loaded 85 / 85 constellation art records successfully for culture "western"
  Loaded 88 / 88 constellation names
  Loading constellation boundary data ... 
  Loaded 782 constellation boundary segments
  Initializing basic GL shaders... 
  Creating GUI ...
  Loaded plugin "Exoplanets"
  Exoplanets: version of the format of the catalog: 1
  Exoplanets: loading catalog file: 
"/home/jstokes/.stellarium/modules/Exoplanets/exoplanets.json"
  Loaded plugin "FOV"
  Loaded plugin "MeteorShowers"
  MeteorShowersMgr: Loading catalog file: 
"/home/jstokes/.stellarium/modules/MeteorShowers/showers.json"
  Loaded plugin "Novae"
  Novae: version of the catalog: 1
  Novae: loading catalog file: 
"/home/jstokes/.stellarium/modules/Novae/novae.json"
  Loaded plugin "Oculars"
  Ocular plugin - press Command-O to toggle eyepiece view mode. Press ALT-o for 
configuration.
  Oculars::validateIniFile ocular.ini exists at:  
"/home/jstokes/.stellarium/modules/Oculars/ocular.ini" . Checking version...
  Oculars::validateIniFile found existing ini file version  3
  Loaded plugin "Satellites"
  Satellites: loading catalog file: 
"/home/jstokes/.stellarium/modules/Satellites/satellites.json"
  Satellite has invalid orbit: "FLOCK 1B-27" "40422"
  Satellite has invalid orbit: "FLOCK 1B-22" "40428"
  Satellite has invalid orbit: "FLOCK 1B-10" "40429"
  Satellite has invalid orbit: "FLOCK 1B-5" "40453"
  Satellite has invalid orbit: "FLOCK 1B-6" "40454"
  Satellite has invalid orbit: "FLOCK 1B-12" "40460"
  Loaded plugin "SolarSystemEditor"
  Using the ssystem.ini file that already exists in the user directory...
  Unable to find module called "TimeZoneConfiguration"
  Loaded plugin "TimeZoneConfiguration"
  VMware: vmw_ioctl_command error Invalid argument.
  Aborted (core dumped)

To manage 

[Touch-packages] [Bug 1577494] Re: application dies with 'VMware: vmw_ioctl_command error Invalid argument.'

2017-01-07 Thread Slava
Hugo Roddes solutions works for me.

Thanks!

Info:

Ubuntu 16.04
VMware Fusion 8.5.3

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

Title:
  application dies with 'VMware: vmw_ioctl_command error Invalid
  argument.'

Status in ROS:
  New
Status in Stellarium:
  Incomplete
Status in blender package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  running stellarium in ubuntu 16.04 in a VMWare 12.1.1 virtual machine.
  thanks.

  


  jstokes@ubuntu1604:~$ stellarium

  ** (stellarium:1768): WARNING **: Couldn't connect to accessibility bus: 
Failed to connect to socket /tmp/dbus-6Rt5CAvHFy: Connection refused
   ---
  [ This is Stellarium 0.14.3 - http://www.stellarium.org ]
  [ Copyright (C) 2000-2016 Fabien Chereau et al. ]
   ---
  Writing log file to: "/home/jstokes/.stellarium/log.txt"
  File search paths:
0 .  "/home/jstokes/.stellarium"
1 .  "/usr/share/stellarium"
  Config file is:  "/home/jstokes/.stellarium/config.ini"
  Detected: OpenGL "3.0"
  Driver version string: "3.0 Mesa 11.2.0"
  GL vendor is "VMware, Inc."
  GL renderer is "Gallium 0.4 on SVGA3D; build: RELEASE;  LLVM;"
  GL Shading Language version is "1.30"
  MESA Version Number detected:  11.2
  Mesa version is fine, we should not see a graphics problem.
  GLSL Version Number detected:  1.3
  GLSL version is fine, we should not see a graphics problem.
  Cache directory is:  "/home/jstokes/.cache/stellarium/stellarium"
  Sky language is  "en_US"
  Application language is  "en_US"
  Loading Solar System data ...
  Loading star data ...
  "Loading \"/usr/share/stellarium/stars/default/stars_0_0v0_5.cat\": 0_0v0_2; 
4963"
  "Loading \"/usr/share/stellarium/stars/default/stars_1_0v0_5.cat\": 1_0v0_2; 
21598"
  "Loading \"/usr/share/stellarium/stars/default/stars_2_0v0_5.cat\": 2_0v0_2; 
150090"
  "Loading \"/usr/share/stellarium/stars/default/stars_3_1v0_3.cat\": 3_1v0_3; 
428466"
  Finished loading star catalogue data, max_geodesic_level:  3
  navigation/preset_sky_time is a double - treating as jday: "2451514.25001"
  Reloading DSO data...
  Loaded 10756 DSO records
  Loading DSO name data ...
  Loaded 221 / 297 DSO name records successfully
  Loading star names from 
"/usr/share/stellarium/skycultures/western/star_names.fab"
  Loaded 339 / 339 common star names
  Loading star names from "/usr/share/stellarium/stars/default/name.fab"
  Loaded 4506 / 4506 scientific star names
  Loading variable stars from 
"/usr/share/stellarium/stars/default/gcvs_hip_part.dat"
  Loaded 6916 / 6916 variable stars
  Loading cross-index data from 
"/usr/share/stellarium/stars/default/cross-index.dat"
  Loaded 108279 / 108279 cross-index data records
  Loaded 88 / 88 constellation records successfully for culture "western"
  Loaded 85 / 85 constellation art records successfully for culture "western"
  Loaded 88 / 88 constellation names
  Loading constellation boundary data ... 
  Loaded 782 constellation boundary segments
  Initializing basic GL shaders... 
  Creating GUI ...
  Loaded plugin "Exoplanets"
  Exoplanets: version of the format of the catalog: 1
  Exoplanets: loading catalog file: 
"/home/jstokes/.stellarium/modules/Exoplanets/exoplanets.json"
  Loaded plugin "FOV"
  Loaded plugin "MeteorShowers"
  MeteorShowersMgr: Loading catalog file: 
"/home/jstokes/.stellarium/modules/MeteorShowers/showers.json"
  Loaded plugin "Novae"
  Novae: version of the catalog: 1
  Novae: loading catalog file: 
"/home/jstokes/.stellarium/modules/Novae/novae.json"
  Loaded plugin "Oculars"
  Ocular plugin - press Command-O to toggle eyepiece view mode. Press ALT-o for 
configuration.
  Oculars::validateIniFile ocular.ini exists at:  
"/home/jstokes/.stellarium/modules/Oculars/ocular.ini" . Checking version...
  Oculars::validateIniFile found existing ini file version  3
  Loaded plugin "Satellites"
  Satellites: loading catalog file: 
"/home/jstokes/.stellarium/modules/Satellites/satellites.json"
  Satellite has invalid orbit: "FLOCK 1B-27" "40422"
  Satellite has invalid orbit: "FLOCK 1B-22" "40428"
  Satellite has invalid orbit: "FLOCK 1B-10" "40429"
  Satellite has invalid orbit: "FLOCK 1B-5" "40453"
  Satellite has invalid orbit: "FLOCK 1B-6" "40454"
  Satellite has invalid orbit: "FLOCK 1B-12" "40460"
  Loaded plugin "SolarSystemEditor"
  Using the ssystem.ini file that already exists in the user directory...
  Unable to find module called "TimeZoneConfiguration"
  Loaded plugin "TimeZoneConfiguration"
  VMware: vmw_ioctl_command error Invalid argument.
  Aborted (core dumped)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

2017-01-07 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: update-notifier (Ubuntu)
   Status: New => Confirmed

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  New
Status in apt package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1522675] Re: Warning messages about unsandboxed downloads

2017-01-07 Thread Steve Langasek
>From what I gathered, msttcorefonts and flashplugin-nonfree
> (flashplugin-installer) are affected by this, hence adding tasks for
> them.

These packages invoke update-notifier for the downloading; reassigning.

I don't see what value this sandbox user is providing, however, and why
apt needs to be so noisy about it.  Is this about not running the
network client code as root?  Clearly, anything downloaded is going to
be handled as root once it's there.

** Package changed: flashplugin-nonfree (Ubuntu) => update-notifier
(Ubuntu)

** No longer affects: msttcorefonts (Ubuntu)

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  New
Status in apt package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1522675] Re: Warning messages about unsandboxed downloads

2017-01-07 Thread Jeremy Bicha
Julian, I see this warning every time I run

sudo apt install ./example.deb

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in msttcorefonts package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in apt package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1653323] Re: Severe screen flicker on Unity when terminal maximized

2017-01-07 Thread Damon Lynch
I just tried the nouveau driver in 4.9.0-11-generic. Now while it didn't
flicker, what it did do was exhibit the very start of the problem, which
manifests as subtle vertical bars in the top panel's dark brown bar. So
it may not be an Nvidia problem, but a kernel problem, that may have
been fixed in 4.10.

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

Title:
  Severe screen flicker on Unity  when terminal maximized

Status in xorg package in Ubuntu:
  New

Bug description:
  The screen experiences severe flicker when using Nvidia 375.26 on a
  GTX 1070 in 16.10, Unity Desktop -- but only when the terminal is in
  the top left of the screen or maximized, and is full of text.

  I made a video illustrating the problem: http://damonlynch.net/share
  /Ubuntu1610screen-flicker.mp4

  Driver is from the "graphics-drivers" PPA.

  At this point I don't know if it's a hardware problem or software
  problem -- I've never seen anything like it before. I've ruled out the
  DisplayPort cable as a problem, because it exhibits the same problem
  with two different cables.

  The LCD is a Dell UP3017.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.26  Thu Dec  8 18:36:43 
PST 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 340580/915712 files, 2047147/3661865 blocks
  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: Fri Dec 30 23:05:25 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed
   nvidia-375, 375.26, 4.8.0-30-generic, x86_64: installed
   nvidia-375, 375.26, 4.8.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3701]
  InstallationDate: Installed on 2016-10-09 (82 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic 
root=UUID=b2cca22d-b1af-498e-84e2-4f06fd41880d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd03/01/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: 

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

2017-01-07 Thread Julian Andres Klode
>From what I gathered, msttcorefonts and flashplugin-nonfree
(flashplugin-installer) are affected by this, hence adding tasks for
them.

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in flashplugin-nonfree package in Ubuntu:
  New
Status in msttcorefonts package in Ubuntu:
  New
Status in apt package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1522675] Re: Needless scary warning: Download is performed unsandboxed as root: _apt user not allowed

2017-01-07 Thread Julian Andres Klode
The message won't be removed. It's worded as good as it can be now.

Maintainer scripts using apt-helper to download stuff (or clients using
libapt-pkg) should be fixed to use proper permissions on the directories
so the _apt user can write files (best create a temporary directory I'd
say owned by _apt, download to that).

For interactive use, the message appears in a very limited set of
circumstances. Namely, "download" and "source" run as root (maybe
"changelog", depending on your tmpfs setup, not sure).  Running these
commands as root does not make that much sense anyway, especially
source.

So if users can reproduce this with a specific package that uses our
tools, please add a task for that tool. From the apt side, this is
working as intended.

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

** Summary changed:

- Needless scary warning: Download is performed unsandboxed as root: _apt user 
not allowed
+ Warning messages about unsandboxed downloads

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

** Also affects: flashplugin-nonfree (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in flashplugin-nonfree package in Ubuntu:
  New
Status in msttcorefonts package in Ubuntu:
  New
Status in apt package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1653323] Re: Severe screen flicker on Unity when terminal maximized

2017-01-07 Thread Damon Lynch
Running the mainline kernel 4.10-rc2 and the nouveau driver on 17.04
means the bug does not appear; it does appear with the Nvidia 375 driver
in the regular 17.04 kernel. The 4.10-rc2 kernel is significant because
in the 4.9 and earlier kernels, the mouse cursor does not move from the
top left corner of the screen.

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

Title:
  Severe screen flicker on Unity  when terminal maximized

Status in xorg package in Ubuntu:
  New

Bug description:
  The screen experiences severe flicker when using Nvidia 375.26 on a
  GTX 1070 in 16.10, Unity Desktop -- but only when the terminal is in
  the top left of the screen or maximized, and is full of text.

  I made a video illustrating the problem: http://damonlynch.net/share
  /Ubuntu1610screen-flicker.mp4

  Driver is from the "graphics-drivers" PPA.

  At this point I don't know if it's a hardware problem or software
  problem -- I've never seen anything like it before. I've ruled out the
  DisplayPort cable as a problem, because it exhibits the same problem
  with two different cables.

  The LCD is a Dell UP3017.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.26  Thu Dec  8 18:36:43 
PST 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 340580/915712 files, 2047147/3661865 blocks
  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: Fri Dec 30 23:05:25 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed
   nvidia-375, 375.26, 4.8.0-30-generic, x86_64: installed
   nvidia-375, 375.26, 4.8.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3701]
  InstallationDate: Installed on 2016-10-09 (82 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic 
root=UUID=b2cca22d-b1af-498e-84e2-4f06fd41880d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd03/01/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD3-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD3
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  

[Touch-packages] [Bug 1654782] Re: Can not pair with bluetooth headphones

2017-01-07 Thread DimanNe
** Description changed:

  I can not pair computer and Bluetooth headset (sennheiser momentum 2.0 
wireless aebt).
  (If it matters, I *CAN* pair and use it on another laptop with Linux and with 
my android smartphone. So headset itself is working well.)
  
  Here is how I try to pair:
  $ bluetoothctl
  [NEW] Controller 54:27:1E:33:4B:85 impedance [default]
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 54:27:1E:33:4B:85 Discovering: yes
  [bluetooth]# scan on
  
  I tried to put my headset in pairing mode just before and after issuing
  "scan on" command. It ends up with nothing - I waited for 3-5 minutes.
- For example, my smartphone pairs with the headset in 5-15 seconds, my
- laptop pairs with the headset in about 30 seconds.
+ For example, my smartphone pairs with the headset within 5-15 seconds,
+ my laptop pairs with the headset within about 30 seconds.
  
  =
  
  Here is info
  
  $ hciconfig -a
  hci0:   Type: Primary  Bus: USB
- BD Address: 54:27:1E:33:4B:85  ACL MTU: 1021:8  SCO MTU: 64:1
- UP RUNNING PSCAN ISCAN 
- RX bytes:4475 acl:0 sco:0 events:565 errors:0
- TX bytes:7214 acl:0 sco:0 commands:487 errors:0
- Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
- Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
- Link policy: RSWITCH SNIFF 
- Link mode: SLAVE ACCEPT 
- Name: 'impedance'
- Class: 0x1c0104
- Service Classes: Rendering, Capturing, Object Transfer
- Device Class: Computer, Desktop workstation
- HCI Version: 4.0 (0x6)  Revision: 0x1000
- LMP Version: 4.0 (0x6)  Subversion: 0x220e
- Manufacturer: Broadcom Corporation (15)
+ BD Address: 54:27:1E:33:4B:85  ACL MTU: 1021:8  SCO MTU: 64:1
+ UP RUNNING PSCAN ISCAN
+ RX bytes:4475 acl:0 sco:0 events:565 errors:0
+ TX bytes:7214 acl:0 sco:0 commands:487 errors:0
+ Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
+ Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
+ Link policy: RSWITCH SNIFF
+ Link mode: SLAVE ACCEPT
+ Name: 'impedance'
+ Class: 0x1c0104
+ Service Classes: Rendering, Capturing, Object Transfer
+ Device Class: Computer, Desktop workstation
+ HCI Version: 4.0 (0x6)  Revision: 0x1000
+ LMP Version: 4.0 (0x6)  Subversion: 0x220e
+ Manufacturer: Broadcom Corporation (15)
  
  =
  
  rfkill list
  0: hci0: Bluetooth
- Soft blocked: no
- Hard blocked: no
+ Soft blocked: no
+ Hard blocked: no
  
  =
  
  Bluez packages installed:
  $ dpkg -l | grep bluez
  ii  bluez
  ii  bluez-btsco
  ii  bluez-cups
  ii  bluez-hcidump
  ii  bluez-obexd
  ii  bluez-tools
  ii  libkf5bluezqt-data
  ii  libkf5bluezqt6:amd64
  ii  qml-module-org-kde-bluezqt:amd64
  
  =
  
  $ dmesg | grep -i blue
  [4.632406] Bluetooth: Core ver 2.21
  [4.632414] Bluetooth: HCI device and connection manager initialized
  [4.632416] Bluetooth: HCI socket layer initialized
  [4.632417] Bluetooth: L2CAP socket layer initialized
  [4.632420] Bluetooth: SCO socket layer initialized
  [4.644619] Bluetooth: hci0: BCM: chip id 63
  [4.660554] Bluetooth: hci0: impedance
  [4.661552] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [4.661798] bluetooth hci0: Direct firmware load for 
brcm/BCM20702A1-0b05-17cf.hcd failed with error -2
  [4.661799] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not 
found
  [   15.061603] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.061604] Bluetooth: BNEP filters: protocol multicast
  [   15.061606] Bluetooth: BNEP socket layer initialized
  [   48.001553] Bluetooth: RFCOMM TTY layer initialized
  [   48.001558] Bluetooth: RFCOMM socket layer initialized
  [   48.001562] Bluetooth: RFCOMM ver 1.11
  [  615.404052] Modules linked in: rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
nf_nat nf_conntrack rpcsec_gss_krb5 nfnetlink_queue nfsv4 nfnetlink xt_tcpudp 
bridge xt_NFQUEUE nfs xt_owner iptable_filter fscache cmac bnep binfmt_misc 
nls_iso8859_1 intel_rapl edac_core x86_pkg_temp_thermal coretemp btrfs xor 
snd_hda_codec_hdmi eeepc_wmi asus_wmi sparse_keymap video mxm_wmi raid6_pq 
btusb btrtl btbcm btintel bluetooth kvm_intel kvm irqbypass crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper 
ablk_helper 

[Touch-packages] [Bug 1654783] [NEW] package libxatracker2:amd64 11.2.0-1ubuntu2 failed to install/upgrade: package libxatracker2:amd64 is not ready for configuration cannot configure (current status

2017-01-07 Thread daol
Public bug reported:

At to install

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libxatracker2:amd64 11.2.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.4
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: Sat Jan  7 16:46:51 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ErrorMessage: package libxatracker2:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1659]
 Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] 
[1002:6760] (rev ff) (prog-if ff)
InstallationDate: Installed on 2017-01-07 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=6612b251-bfdc-45dd-a8b0-a31a76c9008f ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: mesa
Title: package libxatracker2:amd64 11.2.0-1ubuntu2 failed to install/upgrade: 
package libxatracker2:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/05/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.1B
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1659
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 10.31
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.1B:bd10/05/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058E1124471620100:rvnHewlett-Packard:rn1659:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion dv7 Notebook PC
dmi.product.version: 058E1124471620100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
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
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Jan  7 16:36:06 2017
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5913 
 vendor CMO
xserver.version: 2:1.18.4-0ubuntu0.2

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


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

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

Title:
  package libxatracker2:amd64 11.2.0-1ubuntu2 failed to install/upgrade:
  package libxatracker2:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in mesa package in Ubuntu:
  New

Bug description:
  At to install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libxatracker2:amd64 11.2.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  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: Sat Jan  7 16:46:51 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ErrorMessage: package libxatracker2:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 

[Touch-packages] [Bug 1654782] [NEW] Can not pair with bluetooth headphones

2017-01-07 Thread DimanNe
Public bug reported:

I can not pair computer and Bluetooth headset (sennheiser momentum 2.0 wireless 
aebt).
(If it matters, I *CAN* pair and use it on another laptop with Linux and with 
my android smartphone. So headset itself is working well.)

Here is how I try to pair:
$ bluetoothctl
[NEW] Controller 54:27:1E:33:4B:85 impedance [default]
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller 54:27:1E:33:4B:85 Discovering: yes
[bluetooth]# scan on

I tried to put my headset in pairing mode just before and after issuing
"scan on" command. It ends up with nothing - I waited for 3-5 minutes.
For example, my smartphone pairs with the headset in 5-15 seconds, my
laptop pairs with the headset in about 30 seconds.

=

Here is info

$ hciconfig -a
hci0:   Type: Primary  Bus: USB
BD Address: 54:27:1E:33:4B:85  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:4475 acl:0 sco:0 events:565 errors:0
TX bytes:7214 acl:0 sco:0 commands:487 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH SNIFF 
Link mode: SLAVE ACCEPT 
Name: 'impedance'
Class: 0x1c0104
Service Classes: Rendering, Capturing, Object Transfer
Device Class: Computer, Desktop workstation
HCI Version: 4.0 (0x6)  Revision: 0x1000
LMP Version: 4.0 (0x6)  Subversion: 0x220e
Manufacturer: Broadcom Corporation (15)

=

rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

=

Bluez packages installed:
$ dpkg -l | grep bluez
ii  bluez
ii  bluez-btsco
ii  bluez-cups
ii  bluez-hcidump
ii  bluez-obexd
ii  bluez-tools
ii  libkf5bluezqt-data
ii  libkf5bluezqt6:amd64
ii  qml-module-org-kde-bluezqt:amd64

=

$ dmesg | grep -i blue
[4.632406] Bluetooth: Core ver 2.21
[4.632414] Bluetooth: HCI device and connection manager initialized
[4.632416] Bluetooth: HCI socket layer initialized
[4.632417] Bluetooth: L2CAP socket layer initialized
[4.632420] Bluetooth: SCO socket layer initialized
[4.644619] Bluetooth: hci0: BCM: chip id 63
[4.660554] Bluetooth: hci0: impedance
[4.661552] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
[4.661798] bluetooth hci0: Direct firmware load for 
brcm/BCM20702A1-0b05-17cf.hcd failed with error -2
[4.661799] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not 
found
[   15.061603] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   15.061604] Bluetooth: BNEP filters: protocol multicast
[   15.061606] Bluetooth: BNEP socket layer initialized
[   48.001553] Bluetooth: RFCOMM TTY layer initialized
[   48.001558] Bluetooth: RFCOMM socket layer initialized
[   48.001562] Bluetooth: RFCOMM ver 1.11
[  615.404052] Modules linked in: rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
nf_nat nf_conntrack rpcsec_gss_krb5 nfnetlink_queue nfsv4 nfnetlink xt_tcpudp 
bridge xt_NFQUEUE nfs xt_owner iptable_filter fscache cmac bnep binfmt_misc 
nls_iso8859_1 intel_rapl edac_core x86_pkg_temp_thermal coretemp btrfs xor 
snd_hda_codec_hdmi eeepc_wmi asus_wmi sparse_keymap video mxm_wmi raid6_pq 
btusb btrtl btbcm btintel bluetooth kvm_intel kvm irqbypass crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper 
ablk_helper cryptd intel_cstate input_leds intel_rapl_perf 8021q garp mrp stp 
serio_raw llc b43 mac80211 snd_hda_codec_realtek snd_hda_codec_generic

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: bluez 5.41-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Jan  7 22:36:22 2017
InstallationDate: Installed on 2014-07-05 (917 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed 
root=UUID=6cdd6da7-49a5-4892-8a76-48d290860bcf ro acpi=force apm=power_off 
quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to yakkety on 2016-10-09 (89 days ago)
dmi.bios.date: 01/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0701
dmi.board.asset.tag: To be 

[Touch-packages] [Bug 1654772] [NEW] Lost one screen from triple multi monitor radeon setup.

2017-01-07 Thread Ewano
Public bug reported:

I have been running a stock Ubuntu 16.04 LTS with three monitors from a
single Radeon HD 7770 card with no problems.

Description:Ubuntu 16.04.1 LTS
Release:16.04

After not having used my system since approximately 20/12/2016, I used a
simple script on 03/01/2017 to run updates then shut down the system as
follows:

apt-get update
apt-get -y dist-upgrade
apt-get -y autoremove
shutdown -P now

Upon next start up, one of my screens remains dark in power saving mode.
This screen is connected using a displayport cable.

At boot the BIOS splash screen is shown on the affected screen. During
the boot process the screen is active until the login screen is
presented - at which point the screen enters power saving mode.

Using the print screen to capture an image of my desktop, I can see that
desktop is active and application windows are being created just fine.
The monitor screen in question remains in power saving mode, and is
unusable.

I tested with an alternate existing install on different hard drive
which had also not been updated for some time. I swapped over the hard
drive to this machine, let it boot through to a correctly functioning
desktop to verify that there was no hardware fault. Once I had verified
that the hardware functioned correctly, I again ran updates and rebooted
the machine. After update this installation also exhibited the fault.

I can only assume that a bug has been introduced during the updates
supplied between 20/12/2016 and 03/01/2017.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: 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: 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: Sat Jan  7 17:22:02 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 
250X] [1002:683d] (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710]
InstallationDate: Installed on 2016-09-28 (101 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed 
root=UUID=d1a7c988-d3b8-474e-ab61-437925f4454e ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.00
dmi.board.name: A75M
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd07/06/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA75M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
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: Sat Jan  7 16:26:58 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

** 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/1654772

Title:
  Lost one screen from triple multi monitor radeon setup.

Status in xorg package in Ubuntu:
  New

Bug description:
  I have been running a stock Ubuntu 16.04 LTS with three monitors from
  a single Radeon HD 7770 card with no problems.

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  After not having used my system since approximately 20/12/2016, I used
  

[Touch-packages] [Bug 1654759] [NEW] package libpulse0 (not installed) failed to install/upgrade: Versuch, gemeinsam benutztes »/etc/pulse/client.conf« zu überschreiben, welches verschieden von andere

2017-01-07 Thread Reiner Plonka
Public bug reported:

I had also problems after new installation of LTS 16.04 with audio. With 14.04 
it worksbut not with 16.04 (same hardware)
I found the BugTracker: 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643847
and made the chages like clement describes.but it dosen't work.
Chrash after new start. I made no reboot!

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpulse0 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Sat Jan  7 17:41:24 2017
ErrorMessage: Versuch, gemeinsam benutztes »/etc/pulse/client.conf« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libpulse0:amd64 ist
InstallationDate: Installed on 2016-12-24 (14 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulse.so.0: cannot open shared object 
file: No such file or directory
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: pulseaudio
Title: package libpulse0 (not installed) failed to install/upgrade: Versuch, 
gemeinsam benutztes »/etc/pulse/client.conf« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libpulse0:amd64 ist
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/28/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: P55-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd04/28/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P55-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-package xenial

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

Title:
  package libpulse0 (not installed) failed to install/upgrade: Versuch,
  gemeinsam benutztes »/etc/pulse/client.conf« zu überschreiben, welches
  verschieden von anderen Instanzen des Paketes libpulse0:amd64 ist

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I had also problems after new installation of LTS 16.04 with audio. With 
14.04 it worksbut not with 16.04 (same hardware)
  I found the BugTracker: 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643847
  and made the chages like clement describes.but it dosen't work.
  Chrash after new start. I made no reboot!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpulse0 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Sat Jan  7 17:41:24 2017
  ErrorMessage: Versuch, gemeinsam benutztes »/etc/pulse/client.conf« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libpulse0:amd64 ist
  InstallationDate: Installed on 2016-12-24 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: 
error while loading shared libraries: libpulse.so.0: cannot open shared object 
file: No such file or directory
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: pulseaudio
  Title: package libpulse0 (not installed) failed to install/upgrade: Versuch, 
gemeinsam benutztes »/etc/pulse/client.conf« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libpulse0:amd64 ist
  UpgradeStatus: No 

[Touch-packages] [Bug 1647133] Re: dns=dnsmasq does not work any more

2017-01-07 Thread Harry
This bug is now solved with the latest network-manager v. 1.4.2-3ubuntu2 in 
Zesty.
Here: 
https://launchpad.net/ubuntu/+source/network-manager/1.4.2-3ubuntu2


** Changed in: network-manager (Ubuntu)
   Status: Triaged => 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/1647133

Title:
  dns=dnsmasq does not work any more

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Network-manager will make my network connection immediately lost after 
updating to the newest version 1.4.2-2ubuntu4.
  However, downgrading to the previous version 1.4.2-2ubuntu3 the network 
connection is back again and fine. If, with this version, I remove the file 
(link) /etc/resolv.conf the network is broken again. Rebooting solves this, as 
network-manager creates a new resolv.conf file.

  The newest version 1.4.2-2ubuntu4 also creates the very same kind of
  file, but no network.

  I have the latest (Gnome-shell DE) updates installed and of course all 
packages that network-manager depends on. But not the ones it only recommends 
or suggests.
  Should I have resolvconf installed? I think not, as isc-dhcp-client only 
suggests it.

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

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


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

2017-01-07 Thread Bug Watch Updater
** Changed in: systemd (Debian)
   Status: Fix Committed => Fix Released

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

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

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

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

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

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

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

  #!/bin/sh
  service smbd restart

  #!/bin/sh
  systemctl restart smbd.service

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

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

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

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


[Touch-packages] [Bug 1654416] Re: Requesting 2.4.44 build which includes fix for ITS#8185

2017-01-07 Thread Kartik Subbarao
Understood, thanks for the responses Ryan and Hans.

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

Title:
  Requesting 2.4.44 build which includes fix for ITS#8185

Status in openldap package in Ubuntu:
  New

Bug description:
  I reported ITS#8185 to OpenLDAP which was fixed in the 2.4.43 release.
  There have been no OpenLDAP releases since 2.4.44 in February 2016, so
  it looks like things have been stable for a while. I'd like to request
  a refreshed slapd package for 2.4.44 (the most recent slapd package
  available on Ubuntu is 2.4.42 which dates back to August 2015). This
  would help me remove a manual workaround for the ITS#8185 issue, and
  users would also benefit from the number of fixes in 2.4.43 and
  2.4.44.

  http://www.openldap.org/software/release/changes.html

  purging stale pwdFailureTime attributes:
  
http://www.openldap.org/its/index.cgi/Software%20Enhancements?id=8185;selectid=8185

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1654416/+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 1630884] Re: Xorg freeze; mouse moves, but no mouse click or keyboard response

2017-01-07 Thread Nuno Monteiro
Hi, I also have the same issue, also a Dell Latitude e6420. Did you
solve the issue?

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

Title:
  Xorg freeze; mouse moves, but no mouse click or keyboard response

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I've encountered this issue on several fresh installations of Ubuntu
  16.04.1 on different machines. Typically, the machine becomes
  unresponsive to the keyboard presses or to mouse clicks; however, it
  does respond to mouse movement. I am unable to open a text console to
  manipulate processes, and I am forced to hard restart the machine.
  During the most recent instance, I noticed that the mouse cursor would
  change in response to its location on the screen while

  The issue most often occurs about 3-5 minutes after Chromium has been
  opened, but it has also occurred without Chromium being installed.
  Moreover, it as occurred while using Xfce and GNOME 3 and while using
  open source and proprietary video drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Oct  6 00:04:47 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Dell GF119M [NVS 4200M] [1028:0493]
  InstallationDate: Installed on 2016-10-06 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E6420
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=3c7f4e14-5817-44b1-adbb-1666f8c29348 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A23
  dmi.board.asset.tag: TSI3251
  dmi.board.name: 032T9K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.asset.tag: TSI3251
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA23:bd01/04/2016:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn032T9K:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1630884/+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 1654744] [NEW] Upon booting was prompted with a message about reporting a graphics issues bug

2017-01-07 Thread Barry Aishton
Public bug reported:

I'm new, and too tired to learn how to look into the bug.  I hope the
info the message said would automatically be sent with this is helpful.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname: Linux 4.4.0-53-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.4
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: Sat Jan  7 09:17:25 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [1028:01c2]
   Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics 
Controller [1028:01c2]
InstallationDate: Installed on 2016-09-19 (109 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Latitude D620
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-53-generic 
root=/dev/mapper/ubuntu--vg-root ro splash quiet
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0FT292
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd12/18/2006:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0FT292:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D620
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.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Jan  7 03:46:53 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16980 
 vendor SEC
xserver.version: 2:1.18.4-0ubuntu0.2

** 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/1654744

Title:
  Upon booting was prompted with a message about reporting a graphics
  issues bug

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm new, and too tired to learn how to look into the bug.  I hope the
  info the message said would automatically be sent with this is
  helpful.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  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: Sat Jan  7 09:17:25 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [1028:01c2]
 Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated 
Graphics Controller [1028:01c2]
  InstallationDate: Installed on 2016-09-19 (109 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude D620
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-53-generic 

[Touch-packages] [Bug 1630884] Re: Xorg freeze; mouse moves, but no mouse click or keyboard response

2017-01-07 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Xorg freeze; mouse moves, but no mouse click or keyboard response

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I've encountered this issue on several fresh installations of Ubuntu
  16.04.1 on different machines. Typically, the machine becomes
  unresponsive to the keyboard presses or to mouse clicks; however, it
  does respond to mouse movement. I am unable to open a text console to
  manipulate processes, and I am forced to hard restart the machine.
  During the most recent instance, I noticed that the mouse cursor would
  change in response to its location on the screen while

  The issue most often occurs about 3-5 minutes after Chromium has been
  opened, but it has also occurred without Chromium being installed.
  Moreover, it as occurred while using Xfce and GNOME 3 and while using
  open source and proprietary video drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Oct  6 00:04:47 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Dell GF119M [NVS 4200M] [1028:0493]
  InstallationDate: Installed on 2016-10-06 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E6420
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=3c7f4e14-5817-44b1-adbb-1666f8c29348 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A23
  dmi.board.asset.tag: TSI3251
  dmi.board.name: 032T9K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.asset.tag: TSI3251
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA23:bd01/04/2016:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn032T9K:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1630884/+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 1597681] Re: [CTA] Enable WAPI support

2017-01-07 Thread John McAleely
** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => (unassigned)

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

Title:
  [CTA] Enable WAPI support

Status in Canonical System Image:
  In Progress
Status in indicator-network package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  The phone does not currently support WAPI [1]

  It should do so. As part of this, support for the SMS4 [2] cipher is
  also required.

  
  [1] 
https://en.wikipedia.org/wiki/WLAN_Authentication_and_Privacy_Infrastructure
  [2]: https://en.wikipedia.org/wiki/SMS4

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597681/+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 1654707] Re: Cant upgrade: "add stricter shlib dependencies " ends with supposed broken dependencies

2017-01-07 Thread Julian Taylor
this issue is fixed in 3.3.5-3

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

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

Title:
  Cant upgrade: "add stricter shlib dependencies " ends with supposed
  broken dependencies

Status in fftw3 package in Ubuntu:
  Fix Released

Bug description:
  The upgrade to 3.3.5-2 is impossible: warns about broken dependecies,
  but they are not identified.

  fftw3 (3.3.5-2) unstable; urgency=medium

    * add stricter shlib dependencies for partial upgrades (Closes: #849593)
    * mark libfft3-mpi-dev m-a same and libfftw3-doc m-a foreign

   -- Julian Taylor   Fri, 06 Jan 2017
  18:44:49 +0100

  Looks like that " add stricter shlib dependencies for partial upgrades
  " is the root cause of the upgrade failure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libfftw3-double3 3.3.5-1
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jan  7 06:02:28 2017
  Dependencies:
   gcc-6-base 6.3.0-2ubuntu1
   libc6 2.24-7ubuntu2
   libgcc1 1:6.3.0-2ubuntu1
   libgomp1 6.3.0-2ubuntu1
  SourcePackage: fftw3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1654707/+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 1654730] [NEW] Resuming from suspend, network manager can only see 1 WiFi network

2017-01-07 Thread mthurston
Public bug reported:

Hardware:
Dell XPS15 9550
Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter

Software:
Ubuntu 16.04.1 LTS 4.4.0-58-generic
network-manager 1.2.4-0ubuntu0.16.04.1
network-manager-gnome 1.2.0-0ubuntu0.16.04.4


02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network 
Adapter (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
Flags: bus master, fast devsel, latency 0, IRQ 136
Memory at dd20 (64-bit, non-prefetchable) [size=2M]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=8/8 Maskable+ 64bit-
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Virtual Channel
Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [178] Latency Tolerance Reporting
Capabilities: [180] L1 PM Substates
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci


When resuming from suspend, network-manager only displays one random network 
(random/different one each time).

Switching WiFi off and on does not fix it.  iwlist scanning does not fix
it.

After running "sudo iwlist scanning", network manager works normally
again immediately.

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

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

Title:
  Resuming from suspend, network manager can only see 1 WiFi network

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hardware:
  Dell XPS15 9550
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter

  Software:
  Ubuntu 16.04.1 LTS 4.4.0-58-generic
  network-manager 1.2.4-0ubuntu0.16.04.1
  network-manager-gnome 1.2.0-0ubuntu0.16.04.4

  
  02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
Flags: bus master, fast devsel, latency 0, IRQ 136
Memory at dd20 (64-bit, non-prefetchable) [size=2M]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=8/8 Maskable+ 64bit-
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Virtual Channel
Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [178] Latency Tolerance Reporting
Capabilities: [180] L1 PM Substates
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci

  
  When resuming from suspend, network-manager only displays one random network 
(random/different one each time).

  Switching WiFi off and on does not fix it.  iwlist scanning does not
  fix it.

  After running "sudo iwlist scanning", network manager works normally
  again immediately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1654730/+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 1654707] Re: Cant upgrade: "add stricter shlib dependencies " ends with supposed broken dependencies

2017-01-07 Thread Hans Joachim Desserud
Thanks for taking your time to report this issue and help making Ubuntu
better.

>From what I can see was this package version only in -proposed, it
didn't migrate to the regular release archives (possibly automatically
blocked by this issue?) There's a new upload now in -proposed,
https://bugs.launchpad.net/ubuntu/+source/fftw3/3.3.5-3, which claims to
fix a typo related to shlibs. Could you please check whether this
resolves your issue or if it is an unrelated problem?

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

Title:
  Cant upgrade: "add stricter shlib dependencies " ends with supposed
  broken dependencies

Status in fftw3 package in Ubuntu:
  New

Bug description:
  The upgrade to 3.3.5-2 is impossible: warns about broken dependecies,
  but they are not identified.

  fftw3 (3.3.5-2) unstable; urgency=medium

    * add stricter shlib dependencies for partial upgrades (Closes: #849593)
    * mark libfft3-mpi-dev m-a same and libfftw3-doc m-a foreign

   -- Julian Taylor   Fri, 06 Jan 2017
  18:44:49 +0100

  Looks like that " add stricter shlib dependencies for partial upgrades
  " is the root cause of the upgrade failure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libfftw3-double3 3.3.5-1
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jan  7 06:02:28 2017
  Dependencies:
   gcc-6-base 6.3.0-2ubuntu1
   libc6 2.24-7ubuntu2
   libgcc1 1:6.3.0-2ubuntu1
   libgomp1 6.3.0-2ubuntu1
  SourcePackage: fftw3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1654707/+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 1522675] Re: Needless scary warning: Download is performed unsandboxed as root: _apt user not allowed

2017-01-07 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Needless scary warning: Download is performed unsandboxed as root:
  _apt user not allowed

Status in apt package in Ubuntu:
  Confirmed
Status in apt package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives

2017-01-07 Thread Andy Whitcroft
Hello Dan, or anyone else affected,

Accepted systemd into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.21 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Tags removed: verification-done

** Tags added: verification-needed

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

Title:
  introduce disk/by-id (model_serial) symlinks for NVMe drives

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

Bug description:
  [Impact]

  NVMe drives can't be identified/accessed via /dev/disk/by-id/nvme-
  SERIAL symlinks.

  [Test Case]

  On a system with an NVMe drive, check the /dev/disk/by-id/ directory;
  with the patch, it will contain link(s) named by the drive serial
  number. This should be the *only* change in `ls -l /dev/disk/*/*`.

  On a system without NVMe, verify that `ls -l /dev/disk/*/*` is
  identical (aside from dates, of course) before and after the upgrade
  to the -proposed version.

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or  clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This patch is already included upstream and in zesty systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1642903/+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 1654726] [NEW] PCI/internal sound card not detected

2017-01-07 Thread Anmol Deep
Public bug reported:

the sounds tab in settings does not show inbuilt speakers or earphones

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic i686
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D3p:   anmol  1704 F...m pulseaudio
 /dev/snd/controlC0:  anmol  1704 F pulseaudio
CurrentDesktop: Unity
Date: Sat Jan  7 15:30:24 2017
InstallationDate: Installed on 2017-01-05 (2 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.1
dmi.board.name: 07JM0H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/08/2016:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn07JM0H:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5559
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-bug i386 xenial

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  the sounds tab in settings does not show inbuilt speakers or earphones

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic i686
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D3p:   anmol  1704 F...m pulseaudio
   /dev/snd/controlC0:  anmol  1704 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Jan  7 15:30:24 2017
  InstallationDate: Installed on 2017-01-05 (2 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 07JM0H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/08/2016:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn07JM0H: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/alsa-driver/+bug/1654726/+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 1562344] Re: Not working hotkeys for brightness in HP ProBook 640 G2

2017-01-07 Thread Andy Whitcroft
Hello dlh, or anyone else affected,

Accepted systemd into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.21 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  Not working hotkeys for brightness in HP ProBook 640 G2

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Committed

Bug description:
  Description
  =

  It seems like a new HP laptops are using new vendor string which brokes
  hotkeys.

  
  Workaround
  ==

  Just to put following lines to fix hotkeys for brithness.

  evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
   KEYBOARD_KEY_92=brightnessdown
   KEYBOARD_KEY_97=brightnessup

  
  Proposed solution
  ===

  The issue was already solved by upstream systemd[1] developers 25 days
  ago, so resync of hwdb/60-keyboard.hwdb should be enough.

[1]: commit 325de0ac23596209c252ebcc934dd5f5926fe2b6

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 26 17:20:25 2016
  InstallationDate: Installed on 2016-02-25 (30 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:7053 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 0a5c:640b Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 640 G2
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-34-generic 
root=UUID=4bccba3c-0c3c-430f-bfef-b033d9fcd45c ro 
cryptopts=target=root,source=/dev/disk/by-uuid/9108c404-6977-4914-afd8-40b3e8824d30
 quiet splash vt.handoff=7
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: HP
  dmi.bios.version: N76 Ver. 01.00
  dmi.board.name: 80FD
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 22.36
  dmi.chassis.asset.tag: 5CG605253R
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN76Ver.01.00:bd12/07/2015:svnHP:pnHPProBook640G2:pvr:rvnHP:rn80FD:rvrKBCVersion22.36:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 640 G2
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1562344/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

2017-01-07 Thread Henrik Langli
#51 doesn't work on 16.10:

# killall pulseaudio; rm -r ~/.config/pulse/* ; pulseaudio -k
E: [pulseaudio] main.c: Failed to kill daemon: No such process
#

But at least I got rid of my pulseaudio config :-)

This bug will soon have its 2 year anniversary - are anybody preparing
celebrations?

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1654722] Re: Ubuntu Touch: No sound on speakers but OK on headset

2017-01-07 Thread Walter Garcia-Fontes
ubuntu-phablet-stream-volumes.tdb file as it was before removing
.config/pulse and restarting

** Attachment added: "ubuntu-phablet-stream-volumes.tdb"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+attachment/4801147/+files/ubuntu-phablet-stream-volumes.tdb

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

Title:
  Ubuntu Touch: No sound on speakers but OK on headset

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since a couple of days ago I have lost all sound on the speakers of the phone 
(no application plays any sound, no ringtones, notifications), but sounds can 
be heard normally with a headset. Sound
  configuration looks OK, and restarting does not help.

  I tried to remove .config/pulse completely and restart, but no progress. I 
attach the file 
  ubuntu-phablet-stream-volumes.tdb
  which was there before removing the folder and restarting.

  BQ E5, OTA 14.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:6.0-0ubuntu9.25
  Uname: Linux 3.4.67 armv7l
  AlsaInfo: This script requires lspci. Please install it, and re-run this 
script.
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sat Jan  7 09:30:00 2017
  InstallationDate: Installed on 2016-11-18 (49 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20161118-171123)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+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 1654722] [NEW] Ubuntu Touch: No sound on speakers but OK on headset

2017-01-07 Thread Walter Garcia-Fontes
Public bug reported:

Since a couple of days ago I have lost all sound on the speakers of the phone 
(no application plays any sound, no ringtones, notifications), but sounds can 
be heard normally with a headset. Sound
configuration looks OK, and restarting does not help.

I tried to remove .config/pulse completely and restart, but no progress. I 
attach the file 
ubuntu-phablet-stream-volumes.tdb
which was there before removing the folder and restarting.

BQ E5, OTA 14.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: pulseaudio 1:6.0-0ubuntu9.25
Uname: Linux 3.4.67 armv7l
AlsaInfo: This script requires lspci. Please install it, and re-run this script.
ApportVersion: 2.17.2-0ubuntu1.3touch1
Architecture: armhf
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Sat Jan  7 09:30:00 2017
InstallationDate: Installed on 2016-11-18 (49 days ago)
InstallationMedia: Ubuntu 15.04 - armhf (20161118-171123)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf vivid

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

Title:
  Ubuntu Touch: No sound on speakers but OK on headset

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since a couple of days ago I have lost all sound on the speakers of the phone 
(no application plays any sound, no ringtones, notifications), but sounds can 
be heard normally with a headset. Sound
  configuration looks OK, and restarting does not help.

  I tried to remove .config/pulse completely and restart, but no progress. I 
attach the file 
  ubuntu-phablet-stream-volumes.tdb
  which was there before removing the folder and restarting.

  BQ E5, OTA 14.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:6.0-0ubuntu9.25
  Uname: Linux 3.4.67 armv7l
  AlsaInfo: This script requires lspci. Please install it, and re-run this 
script.
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sat Jan  7 09:30:00 2017
  InstallationDate: Installed on 2016-11-18 (49 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20161118-171123)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+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