date:20161128

** Branch unlinked: lp:mir/0.25

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

Title:
  googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
  cannot create target "gmock" ...]

Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Fix Committed
Status in cmake-extras package in Ubuntu:
  Fix Released
Status in content-hub package in Ubuntu:
  In Progress
Status in googletest package in Ubuntu:
  Won't Fix
Status in mir package in Ubuntu:
  Triaged

Bug description:
  After upgrading to 1.8.0-2 (from 1.7.0-4), our previously-working
  builds break:

  CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
 add_library cannot create target "gmock" because another target with the
 same name already exists.  The existing target is a static library created
 in source directory "/usr/src/googletest/googlemock".  See documentation
 for policy CMP0002 for more details.
   Call Stack (most recent call first):
 /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
 /usr/src/gmock/CMakeLists.txt:84 (cxx_library)


   CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
 add_library cannot create target "gmock_main" because another target with
 the same name already exists.  The existing target is a static library
 created in source directory "/usr/src/googletest/googlemock".  See
 documentation for policy CMP0002 for more details.
   Call Stack (most recent call first):
 /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
 /usr/src/gmock/CMakeLists.txt:89 (cxx_library)


   CMake Error at /usr/src/gmock/CMakeLists.txt:106 (install):
 install TARGETS given target "gmock" which does not exist in this
 directory.

  The CMakeLists.txt in our project that triggers this error does this:

  set(old_cxx_flags ${CMAKE_CXX_FLAGS})
  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -g -Wno-old-style-cast 
-Wno-missing-field-initializers")
  find_package(GMock)
  set(CMAKE_CXX_FLAGS ${old_cxx_flags})

  This used to work fine, but no breaks on zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644062/+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 1644062] Re: googletest 1.8.0-2 (on zesty) breaks existing builds [add_library cannot create target "gmock" ...]

Fix committed to lp:mir/0.25 at revision 3819, scheduled for release in
Mir 0.25.1 (or 0.25.0 ... not sure which one yet).

** Also affects: mir/0.25
   Importance: Undecided
   Status: New

** Changed in: mir/0.25
   Importance: Undecided => Critical

** Changed in: mir/0.25
 Assignee: (unassigned) => Chris Halse Rogers (raof)

** Changed in: mir/0.25
   Status: New => Fix Committed

** Changed in: mir/0.25
Milestone: None => 0.25.1

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

** Changed in: mir (Ubuntu)
   Importance: Undecided => Critical

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

** Changed in: mir/0.25
Milestone: 0.25.1 => 0.25.0

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

Title:
  googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
  cannot create target "gmock" ...]

Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Fix Committed
Status in cmake-extras package in Ubuntu:
  Fix Released
Status in content-hub package in Ubuntu:
  In Progress
Status in googletest package in Ubuntu:
  Won't Fix
Status in mir package in Ubuntu:
  Triaged

Bug description:
  After upgrading to 1.8.0-2 (from 1.7.0-4), our previously-working
  builds break:

  CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
 add_library cannot create target "gmock" because another target with the
 same name already exists.  The existing target is a static library created
 in source directory "/usr/src/googletest/googlemock".  See documentation
 for policy CMP0002 for more details.
   Call Stack (most recent call first):
 /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
 /usr/src/gmock/CMakeLists.txt:84 (cxx_library)


   CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
 add_library cannot create target "gmock_main" because another target with
 the same name already exists.  The existing target is a static library
 created in source directory "/usr/src/googletest/googlemock".  See
 documentation for policy CMP0002 for more details.
   Call Stack (most recent call first):
 /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
 /usr/src/gmock/CMakeLists.txt:89 (cxx_library)


   CMake Error at /usr/src/gmock/CMakeLists.txt:106 (install):
 install TARGETS given target "gmock" which does not exist in this
 directory.

  The CMakeLists.txt in our project that triggers this error does this:

  set(old_cxx_flags ${CMAKE_CXX_FLAGS})
  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -g -Wno-old-style-cast 
-Wno-missing-field-initializers")
  find_package(GMock)
  set(CMAKE_CXX_FLAGS ${old_cxx_flags})

  This used to work fine, but no breaks on zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644062/+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 1644062] Re: googletest 1.8.0-2 (on zesty) breaks existing builds [add_library cannot create target "gmock" ...]

** Branch linked: lp:mir/0.25

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

Title:
  googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
  cannot create target "gmock" ...]

Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Fix Committed
Status in cmake-extras package in Ubuntu:
  Fix Released
Status in content-hub package in Ubuntu:
  In Progress
Status in googletest package in Ubuntu:
  Won't Fix
Status in mir package in Ubuntu:
  Triaged

Bug description:
  After upgrading to 1.8.0-2 (from 1.7.0-4), our previously-working
  builds break:

  CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
 add_library cannot create target "gmock" because another target with the
 same name already exists.  The existing target is a static library created
 in source directory "/usr/src/googletest/googlemock".  See documentation
 for policy CMP0002 for more details.
   Call Stack (most recent call first):
 /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
 /usr/src/gmock/CMakeLists.txt:84 (cxx_library)


   CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
 add_library cannot create target "gmock_main" because another target with
 the same name already exists.  The existing target is a static library
 created in source directory "/usr/src/googletest/googlemock".  See
 documentation for policy CMP0002 for more details.
   Call Stack (most recent call first):
 /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
 /usr/src/gmock/CMakeLists.txt:89 (cxx_library)


   CMake Error at /usr/src/gmock/CMakeLists.txt:106 (install):
 install TARGETS given target "gmock" which does not exist in this
 directory.

  The CMakeLists.txt in our project that triggers this error does this:

  set(old_cxx_flags ${CMAKE_CXX_FLAGS})
  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -g -Wno-old-style-cast 
-Wno-missing-field-initializers")
  find_package(GMock)
  set(CMAKE_CXX_FLAGS ${old_cxx_flags})

  This used to work fine, but no breaks on zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644062/+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 1597642] Re: Unattended-upgrades not showing in apt

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Unattended-upgrades not showing in apt

Status in unattended-upgrades package in Ubuntu:
  Expired

Bug description:
  Even though the updates are installed using unattended upgrades, apt
  still shows them as not installed.

  abhishek unattended-upgrades $ tail unattended-upgrades.log 
  2016-06-30 10:42:57,264 DEBUG applying set ['libkf5i18n-data', 
'kde-l10n-engb', 'libkf5i18n5']
  2016-06-30 10:42:58,640 DEBUG left to upgrade 
{'libreoffice-style-galaxy', 'libreoffice-java-common', 
'libreoffice-avmedia-backend-gstreamer', 'libreoffice-style-breeze', 
'libreoffice-kde', 'libreoffice-impress', 'libreoffice-sdbc-firebird', 
'libreoffice-base-drivers', 'libreoffice-common', 'libreoffice-pdfimport', 
'libreoffice-sdbc-hsqldb', 'libreoffice-base-core', 'libreoffice-draw', 
'libreoffice-math', 'libreoffice-writer', 'libreoffice-calc', 
'libreoffice-help-en-us', 'libreoffice-style-oxygen', 'python3-uno', 
'libreoffice-base', 'libreoffice-core', 'libreoffice-style-tango'}
  2016-06-30 10:42:59,635 DEBUG found partition of size 9 
(['libreoffice-style-breeze', 'libkf5i18n-data', 'libreoffice-java-common', 
'libreoffice-style-oxygen', 'libreoffice-style-galaxy', 'libreoffice-common', 
'kde-l10n-engb', 'libreoffice-style-tango', 'libkf5i18n5'])
  2016-06-30 10:43:01,561 DEBUG found partition of size 6 
(['libreoffice-style-breeze', 'libreoffice-java-common', 
'libreoffice-style-oxygen', 'libreoffice-style-galaxy', 'libreoffice-common', 
'libreoffice-style-tango'])
  2016-06-30 10:43:38,648 DEBUG applying set ['libreoffice-style-breeze', 
'libreoffice-java-common', 'libreoffice-style-oxygen', 
'libreoffice-style-galaxy', 'libreoffice-common', 'libreoffice-style-tango']
  2016-06-30 10:43:40,040 DEBUG left to upgrade {'libreoffice-draw', 
'libreoffice-avmedia-backend-gstreamer', 'libreoffice-kde', 
'libreoffice-impress', 'libreoffice-math', 'libreoffice-writer', 
'libreoffice-base-drivers', 'libreoffice-sdbc-firebird', 'libreoffice-calc', 
'libreoffice-pdfimport', 'libreoffice-sdbc-hsqldb', 'libreoffice-help-en-us', 
'python3-uno', 'libreoffice-base', 'libreoffice-core', 'libreoffice-base-core'}
  2016-06-30 10:44:09,210 DEBUG applying set {'libreoffice-draw', 
'libreoffice-avmedia-backend-gstreamer', 'libreoffice-kde', 
'libreoffice-impress', 'libreoffice-math', 'libreoffice-writer', 
'libreoffice-base-drivers', 'libreoffice-sdbc-firebird', 'libreoffice-calc', 
'libreoffice-pdfimport', 'libreoffice-sdbc-hsqldb', 'libreoffice-help-en-us', 
'python3-uno', 'libreoffice-base', 'libreoffice-core', 'libreoffice-base-core'}
  2016-06-30 10:44:10,574 DEBUG left to upgrade set()
  2016-06-30 10:44:10,574 INFO All upgrades installed
  2016-06-30 10:44:12,511 DEBUG InstCount=0 DelCount=0 BrokenCount=0
  
  
  
  abhishek unattended-upgrades $ apt list --upgradable
  Listing... Done
  
fonts-opensymbol/xenial-updates,xenial-updates,xenial-security,xenial-security 
2:102.7+LibO5.1.4-0ubuntu1 all [upgradable from: 2:102.7+LibO5.1.3-0ubuntu1]
  kde-l10n-engb/xenial,xenial 4:15.12.3-0ubuntu1.2~ubuntu16.04~ppa3 all 
[upgradable from: 4:15.12.3-0ubuntu1.2~ubuntu16.04~ppa2]
  libkf5i18n-data/xenial,xenial 5.23.0-0ubuntu1~ubuntu16.04~ppa2 all 
[upgradable from: 5.23.0-0ubuntu1~ubuntu16.04~ppa1]
  libkf5i18n5/xenial 5.23.0-0ubuntu1~ubuntu16.04~ppa2 amd64 [upgradable 
from: 5.23.0-0ubuntu1~ubuntu16.04~ppa1]
  libreoffice-avmedia-backend-gstreamer/xenial-updates,xenial-security 
1:5.1.4-0ubuntu1 amd64 [upgradable from: 1:5.1.3-0ubuntu1]
  libreoffice-base/xenial-updates,xenial-security 1:5.1.4-0ubuntu1 amd64 
[upgradable from: 1:5.1.3-0ubuntu1]
  libreoffice-base-core/xenial-updates,xenial-security 1:5.1.4-0ubuntu1 
amd64 [upgradable from: 1:5.1.3-0ubuntu1]
  libreoffice-base-drivers/xenial-updates,xenial-security 1:5.1.4-0ubuntu1 
amd64 [upgradable from: 1:5.1.3-0ubuntu1]
  libreoffice-calc/xenial-updates,xenial-security 1:5.1.4-0ubuntu1 amd64 
[upgradable from: 1:5.1.3-0ubuntu1]
  
libreoffice-common/xenial-updates,xenial-updates,xenial-security,xenial-security
 1:5.1.4-0ubuntu1 all [upgradable from: 1:5.1.3-0ubuntu1]
  libreoffice-core/xenial-updates,xenial-security 1:5.1.4-0ubuntu1 amd64 
[upgradable from: 1:5.1.3-0ubuntu1]
  libreoffice-draw/xenial-updates,xenial-security 1:5.1.4-0ubuntu1 amd64 
[upgradable from: 1:5.1.3-0ubuntu1]
  
libreoffice-help-en-us/xenial-updates,xenial-updates,xenial-security,xenial-security
 1:5.1.4-0ubuntu1 all [upgradable from: 1:5.1.3-0ubuntu1]
  libreoffice-impress/xenial-updates,xenial-security 1:5.1.4-0ubuntu1

[Touch-packages] [Bug 1610293] Re: mic cartoon voice

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

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

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

Title:
  mic cartoon voice

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  I have one sort of typical problem, and one very strange problem, both 
related to the audio. 
  First the typical one, because, clearly, the strange one is the headlining 
act here. 

  Typical kind of problem:  My system keeps changing from audio line
  out, to hdmi out as the default choice, and I have to keep moving it
  back by hand from systemsettings.  It seems to be related to
  squeezelite, but am not sure.

  Strange problem:  After updating to 16.04, my microphone transmits
  only a strange, helium inflected  cartoon voice when I speak.  This
  strange transmission works with arecord or ffmpeg from command line,
  and with skype testing service.  The latter convinces me that it is
  not a recording issue, but really a sound capture issue.  Pulseaudio
  will not allow me to select my external microphone jack, though there
  is a microphone plugged in.  It appears to use my webcam (logitech
  C310) mic.  There was no such problem last week under 14.04.  I cannot
  think of any other tests to perform.  If it were allowed, I would
  upload a short recording of my voice, primarily for your amusement.

  A few details:

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1610293/+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 1621246] Re: Bluetooth A2DP audio stops after reconnecting headset

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

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

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

Title:
  Bluetooth A2DP audio stops after reconnecting headset

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Ubuntu 16.04.1 64-bit. DELL E7450 laptop, connected to an LG HBS900
  headset.

  1. Pair the headset
  2. All Settings -> Sound, set the mode to High Fidelity Playback (A2DP Sink) 
(otherwise the sound is horrible)
  3. Test, ensure "Front Left" and "Front Right" sound as they should.
  4. Disconnect the headset via the Bluetooth indicator in the system tray.
  5. Connect the headset to another device and play audio through it (I took a 
call).
  6. Connect back the headset to the laptop.
  7. Attempt to play audio, say in SMPlayer.

  No audio comes through. SMPlayer doesn't advance the seek button.

  8. Run `pulseaudio --kill`.
  9. Reconnect the headset a bunch of times.
  10. In Settings -> Sound, try to set the mode to High Fidelity. Only the 
Headset mode worked, with mono sound. When I'd change the value to High 
Fidelity, the active sound device moved to the internal sound card.

  After a couple more reconnections, I could finally get A2DP sound
  again.

  However, the sound SKIPS randomly a couple times a minute (bug
  405294). Playing the exact same MP3 with the exact same player
  (SMPlayer) on Kubuntu 16.04.1 doesn't reproduce this problem, despite
  presumably using the same Bluetooth stack.

  Super frustrating.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1621246/+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 1641549] Re: migrate lxc android container to lxd

2016-11-28 Thread Vicamo Yang

** Description changed:

  Several things to do here:
  * include lxd, lxd-client in default installation,
  * writable path for lxd: lxd resides at /var/lib/lxd and it takes write 
permission to fully function,
  * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, 
etc.,
  * migrate systemd service definitions, etc.
  
  [Steps to reproduce current setup]
  
  0. rebuild avila kernel with additional patches from
  https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849
  , or just use the prebuilt one in the attachments.
  
  1. follow bug 1641505 and https://bugs.launchpad.net/canonical-devices-
  system-image/+bug/1641505/comments/2 to enable adbd emergency mode and
  disable current lxc-based android container.
  
  2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and
  then reboot the device so that writable path may take effect.
  
  3. initialize lxd. This can take a while (2 minutes for me).
  
    $ sudo lxd init --auto
  
- 4. run lxd image create script to create the android lxd image.
- 
-   $ ./lxd-image-create.sh
- 
- 5. create an ephemeral container for debug:
- 
-   $ lxc init -e -p android android armhf
-   $ lxc start armhf
+ 4. apply changes from https://code.launchpad.net/~vicamo/lxc-android-
+ config/lxd-migration/+merge/311103 . This cause the system to
+ automatically import android initrd as an lxd image and to start it up
+ on boot.

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

Title:
  migrate lxc android container to lxd

Status in Canonical System Image:
  Confirmed
Status in lxc-android-config package in Ubuntu:
  New
Status in urfkill package in Ubuntu:
  New

Bug description:
  Several things to do here:
  * include lxd, lxd-client in default installation,
  * writable path for lxd: lxd resides at /var/lib/lxd and it takes write 
permission to fully function,
  * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, 
etc.,
  * migrate systemd service definitions, etc.

  [Steps to reproduce current setup]

  0. rebuild avila kernel with additional patches from
  https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849
  , or just use the prebuilt one in the attachments.

  1. follow bug 1641505 and https://bugs.launchpad.net/canonical-
  devices-system-image/+bug/1641505/comments/2 to enable adbd emergency
  mode and disable current lxc-based android container.

  2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and
  then reboot the device so that writable path may take effect.

  3. initialize lxd. This can take a while (2 minutes for me).

    $ sudo lxd init --auto

  4. apply changes from https://code.launchpad.net/~vicamo/lxc-android-
  config/lxd-migration/+merge/311103 . This cause the system to
  automatically import android initrd as an lxd image and to start it up
  on boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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 1004256] Re: No Sound

2016-11-28 Thread Worik

this is also effecting me on 14.04 on a MythtV client.

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

Title:
  No Sound

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  sudo lshw -c sound 
   *-multimedia:0 UNCLAIMED
 description: Audio device
 product: Wrestler HDMI Audio [Radeon HD 6250/6310]
 vendor: ATI Technologies Inc
 physical id: 1.1
 bus info: pci@:00:01.1
 version: 00
 width: 32 bits
 clock: 33MHz
 capabilities: pm pciexpress msi bus_master cap_list
 configuration: latency=0
 resources: memory:90444000-90447fff
*-multimedia:1 UNCLAIMED
 description: Audio device
 product: SBx00 Azalia (Intel HDA)
 vendor: ATI Technologies Inc
 physical id: 14.2
 bus info: pci@:00:14.2
 version: 40
 width: 64 bits
 clock: 33MHz
 capabilities: pm bus_master cap_list
 configuration: latency=0
 resources: memory:9044-90443fff

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 2012-05-25 05:46 seq
   crw-rw 1 root audio 116, 33 2012-05-25 05:46 timer
  AplayDevices: aplay: device_list:240: no soundcards found...
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices: arecord: device_list:240: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri May 25 07:37:53 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseSinks: Error: command ['pacmd', 'list-sinks'] failed with exit code 1: 
No PulseAudio daemon running, or not running as session daemon.
  PulseSources: Error: command ['pacmd', 'list-sources'] failed with exit code 
1: No PulseAudio daemon running, or not running as session daemon.
  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/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.12
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE10-BZ
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.12
  dmi.modalias: 
dmi:bvnAcer:bvrV1.12:bd06/08/2011:svnAcer:pnAspireOne522:pvrV1.12:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.12:
  dmi.product.name: Aspire One 522
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1004256/+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 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'

2016-11-28 Thread Aibara Iduas

Not sure if I'm commenting on the right bug, since I'm using Unity not
XFCE, but I get this problem on two computers with Intel cards (both
Intel Corporation Centrino Ultimate-N 6300). It happens maybe 1/10 times
after resuming from suspend. This is on Ubuntu 16.04; there were no
problems back with 14.04.

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

Title:
  wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The Wifi network can't connect after the wake up from suspend. Xubuntu
  15.04

  I'll post more useful details (journalctl log) as a comment to this
  bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dbus 1.8.12-1ubuntu5
  Uname: Linux 4.0.0-04rc5-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr  2 18:18:56 2015
  InstallationDate: Installed on 2015-03-27 (5 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+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 1645548] [NEW] click cannot correctly install clicks that have special version format

2016-11-28 Thread Zhang Enwei

Public bug reported:

I am using click 0.4.43+16.04.20160203-0ubuntu2 in arm64 environment
while building arm 64bit custom tarball(https://jenkins.canonical.com
/ues-phone/job/arm64-custom-tarball-test/)

I found this click cannot install below click correctly.
com.ubuntu.scopes.youtube_1.5.1-154_arm64.click

The apparmor profile it generated is
click_com.ubuntu.scopes.youtube_youtube_1.5.1-
while the expected should be 
click_com.ubuntu.scopes.youtube_youtube_1.5.1-154

The apparmor json file is generated as
com.ubuntu.scopes.youtube_youtube_1.5.1-.json
while the expected should be
com.ubuntu.scopes.youtube_youtube_1.5.1-154.json

We don't have this issue on armhf(vivid).
Thanks.

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

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

Title:
  click cannot correctly install clicks that have special version format

Status in click package in Ubuntu:
  New

Bug description:
  I am using click 0.4.43+16.04.20160203-0ubuntu2 in arm64 environment
  while building arm 64bit custom tarball(https://jenkins.canonical.com
  /ues-phone/job/arm64-custom-tarball-test/)

  I found this click cannot install below click correctly.
  com.ubuntu.scopes.youtube_1.5.1-154_arm64.click

  The apparmor profile it generated is
  click_com.ubuntu.scopes.youtube_youtube_1.5.1-
  while the expected should be 
  click_com.ubuntu.scopes.youtube_youtube_1.5.1-154

  The apparmor json file is generated as
  com.ubuntu.scopes.youtube_youtube_1.5.1-.json
  while the expected should be
  com.ubuntu.scopes.youtube_youtube_1.5.1-154.json

  We don't have this issue on armhf(vivid).
  Thanks.

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

2016-11-28 Thread Yu Ning

Cool, thanks very much.

-- 
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:
  In Progress

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 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

@osomon The reason you are seeing this not work correctly, is because
the value for countChanged signal is named 'devices' in the declarative
class, and not 'count' like what is in the base class and that you are
using in your qml example.

This should probably get changed in the declarative class to match the
base class.

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

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+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 1628478] Re: Mir servers crash when using the Nvidia driver

We always try to keep the oldest bug open unless for some reason there
is dramatically better information in the newer duplicate. So this one
stays the main bug. Bug 1643420 is 'closed' by simply being a duplicate
of this one.

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

Title:
  Mir servers crash when using the Nvidia driver

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Triaged

Bug description:
  I select Unity8 from the log in screen, type in my credentials and it
  just hangs.

  Intel® Core™ i7-4710HQ CPU @ 2.50GHz × 8 
  GeForce GTX 860M/PCIe/SSE2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1628478/+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 1645352] Re: No HDMI output after upgrade to 16.04!

2016-11-28 Thread EDEMPCO

Thanks Brian for the suggestion.

Sorry, the only "package" that I can guess that it could be xorg. I have
attempted to get help in the IRC chat at FreeNode, but instead I got
just questions. I asked for assistance to identify a package name three
times during a 30 minute session and got no help. So, I'm stuck.

If Ubuntu 16.04 includes the Intel driver and, I've insured that the
driver is correct and, loaded using the Intel Graphics Tool and, checked
the status above ... I don't know what else to do.

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

Title:
  No HDMI output after upgrade to 16.04!

Status in xorg package in Ubuntu:
  New

Bug description:
  Running Ubuntu 16.04 64bit, 4.4.8 Kernel on an ASUS Trio with Intel® Haswell 
graphics card and using i915 driver. After upgrade there is no HDMI output to 
the external screen that I use daily. 
  I did the following:
  - Upgraded to  4.4.8 Kernel hoping that the issue would be resolved.
  - Checked for other reports of this issue and followed advise to use NVIDIA 
364 drivers. 
  - Checked Intel for the most recent driver which is already packaged with 
16.04;  it is the i915 driver which is in use.
  - Used Intel driver update tool to ensure that update is correct.
  - Purchased a HDMI adapter to use mini-display port; works and reports HDMI1 
is in use, but HDMI2 is not recognized (when monitor is plugged in to HDMI2)
  - Someone has assisted and has confirmed that there seems to be no hardware 
issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645352/+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 1628478] Re: Mir servers crash when using the Nvidia driver

2016-11-28 Thread Ivan D. Sanders

This is indeed a duplicate of my new bug:
https://bugs.launchpad.net/bugs/1643420

Please close one of them,  I believe the one I linked is newer.

Confirmed again today with newest updates and proprietary  driver 375...

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

Title:
  Mir servers crash when using the Nvidia driver

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Triaged

Bug description:
  I select Unity8 from the log in screen, type in my credentials and it
  just hangs.

  Intel® Core™ i7-4710HQ CPU @ 2.50GHz × 8 
  GeForce GTX 860M/PCIe/SSE2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1628478/+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 1485752] Re: drop oneiric /run compatibility link

2016-11-28 Thread Scott Moser

** Also affects: cloud-initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cloud-initramfs-tools (Ubuntu)
   Status: New => Fix Released

** Changed in: cloud-initramfs-tools (Ubuntu)
   Importance: Undecided => Medium

** Also affects: initramfs-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: cloud-initramfs-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: cloud-initramfs-tools (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: cloud-initramfs-tools (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: cloud-initramfs-tools (Ubuntu Xenial)
 Assignee: (unassigned) => Scott Moser (smoser)

** No longer affects: initramfs-tools (Ubuntu Xenial)

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

Title:
  drop oneiric /run compatibility link

Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  In Progress

Bug description:
  Drop: Maintain compatibility with pre- /run configurations -- this was
  for compatibility with oneiric which is now long gone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1485752/+subscriptions

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

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

** Tags removed: raring

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  
  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient   
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+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 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].

2016-11-28 Thread Luke Yelavich

Hui, could you please add relevant information about the regression
potential of this bug fix, and anything else you feel is important for
the SRU? I'm ok with it and will upload, but think a little more
information is needed.


** Also affects: pulseaudio (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  There is no entry in 'Play sound through' list when plug in headset
  jack [8086:9d70].

Status in pulseaudio package in Ubuntu:
  New
Status in pulseaudio source package in Trusty:
  New

Bug description:
  1. Install 14.04.5 image on P50s
  2. Login system
  3. $ sudo apt-get update
  4. $ apt-get dist-upgrade
  sudo apt-get install --install-recommends linux-generic-lts-xenial 
xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial 
xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial 
libwayland-egl1-mesa-lts-xenial
  5. Reboot the system
  6. Login system
  7. Open Sound setting window
  8. Plug headset jack, unplug headset jack.

  The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643812/+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 1645372] Re: support display scaling slider in unity8

This missing piece (if any) in Mir is a 'mir_output_set_scale_factor'
function, to match the existing 'mir_output_get_scale_factor'.

Although Unity8 is a server so might be able to skip that requirement
and just modify the server structure directly.

** Also affects: mir
   Importance: Undecided
   Status: New

** Changed in: mir
   Importance: Undecided => High

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

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

Title:
  support display scaling slider in unity8

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  We need to be able to scale the display in unity8, via ubuntu-system-
  settings Display->Scaling slider. This will need backend support in
  Mir and unity8, filing this bug to track.

  Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1645372/+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 1644062] Re: googletest 1.8.0-2 (on zesty) breaks existing builds [add_library cannot create target "gmock" ...]

Probably "Won't Fix" the googletest package itself, since this is its
original form from Debian and we can work around it.

** Also affects: content-hub (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: content-hub (Ubuntu)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

** Changed in: content-hub (Ubuntu)
   Importance: Undecided => Critical

** Changed in: content-hub (Ubuntu)
   Status: New => In Progress

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

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

Title:
  googletest 1.8.0-2 (on zesty) breaks existing builds [add_library
  cannot create target "gmock" ...]

Status in Mir:
  Fix Committed
Status in cmake-extras package in Ubuntu:
  Fix Released
Status in content-hub package in Ubuntu:
  In Progress
Status in googletest package in Ubuntu:
  Won't Fix

Bug description:
  After upgrading to 1.8.0-2 (from 1.7.0-4), our previously-working
  builds break:

  CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
 add_library cannot create target "gmock" because another target with the
 same name already exists.  The existing target is a static library created
 in source directory "/usr/src/googletest/googlemock".  See documentation
 for policy CMP0002 for more details.
   Call Stack (most recent call first):
 /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
 /usr/src/gmock/CMakeLists.txt:84 (cxx_library)


   CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
 add_library cannot create target "gmock_main" because another target with
 the same name already exists.  The existing target is a static library
 created in source directory "/usr/src/googletest/googlemock".  See
 documentation for policy CMP0002 for more details.
   Call Stack (most recent call first):
 /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
 /usr/src/gmock/CMakeLists.txt:89 (cxx_library)


   CMake Error at /usr/src/gmock/CMakeLists.txt:106 (install):
 install TARGETS given target "gmock" which does not exist in this
 directory.

  The CMakeLists.txt in our project that triggers this error does this:

  set(old_cxx_flags ${CMAKE_CXX_FLAGS})
  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -g -Wno-old-style-cast 
-Wno-missing-field-initializers")
  find_package(GMock)
  set(CMAKE_CXX_FLAGS ${old_cxx_flags})

  This used to work fine, but no breaks on zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644062/+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 1497806] Re: Mirrored display broken in Xubuntu

2016-11-28 Thread Saúl

I use Ubuntu Studio 16.04 with XFCE4 4.12 and I had that problem too,
but exploring the "Extend to the right" option and then returning to
"Displays", "Mirror Displays" option is already accessible.
Unfortunately, unplugging the another monitor and plugging it again, may
recquire select first "Extend to the right" to make "Mirror Displays"
accesible again.

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

Title:
  Mirrored display broken in Xubuntu

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Mirrored displays is not accessible (grayed out) when trying to
  activate this feature for multi-monitor support.  I am not sure which
  specific package to nominate for this bug, but it seems to only be
  happening on systems with XFCE4 installed and running (Including
  Xubuntu, Mint, and Debian).

  It maybe an error with the package xfce4-display-settings, but I am
  not sure.

  This bug is being reported from:
  Description:  Linux Mint 17.2 Rafaela
  Release:  17.2

  Here is a copy of this Bug Report on Bugzilla:  
https://bugzilla.xfce.org/show_bug.cgi?id=11712
  This bug report also has a picture attachment which is exactly what I am 
seeing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1497806/+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 1638836] Re: resolv.conf for resolved stub server should have a comment how to see the actual servers

2016-11-28 Thread Steve Langasek

** Changed in: network-manager (Ubuntu)
 Assignee: Canonical Foundations Team (canonical-foundations) => Steve 
Langasek (vorlon)

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

Title:
  resolv.conf for resolved stub server should have a comment how to see
  the actual servers

Status in network-manager package in Ubuntu:
  Triaged
Status in resolvconf package in Ubuntu:
  In Progress

Bug description:
  resolv.conf currently just has

nameserver 127.0.0.53

  with resolved (its local stub resolver). We should have an extra
  comment on top of that that says

# systemd-resolved stub resolver; run "systemd-resolve --status" to
  see the actual name servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638836/+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 1380480] Re: network disabled after suspend - resume

2016-11-28 Thread Seth Arnold

Michalje, Kristijian, note that this bug was opened before systemd was
used as a system init. If you're still having trouble please file a new
bug.

Thanks.

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

Title:
  network disabled after suspend - resume

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

Bug description:
  Background: 
  this started to happen after the upgrade to Utopic Beta 1

  3) When I close the laptop's lid and open, the wifi should reconnect
  4) Wifi does not reconnect. It says "Wi-Fi networks" - "disconnected" when I 
left-click on NM icon in notif area. However the context menu (right-click) has 
items "Enable networking" and "Enable Wi-Fi" both with checkmarks.

  Workarounds: 
  switch off - on the physical switch on laptop OR  two times go and select 
"Enable networking" in the NM context menu (after first time it removes 
checkmark and the  "Enable Wi-Fi" item - visual feedback of being disabled).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu27
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 11 22:33:06 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-21 (447 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  IpRoute:
   default via 192.168.10.1 dev wlan0  proto static 
   10.9.9.0/24 dev vboxnet0  proto kernel  scope link  src 10.9.9.1 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.239  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-07-19T15:03:44.847279
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380480/+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 1638836] Re: resolv.conf for resolved stub server should have a comment how to see the actual servers

2016-11-28 Thread Steve Langasek

I have a fix for resolvconf here, but it's inaccurate for the desktop
because Network Manager is still doing dnsmasq by default.  Opening a
task for NM.

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

** Changed in: network-manager (Ubuntu)
   Status: New => Triaged

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

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

Title:
  resolv.conf for resolved stub server should have a comment how to see
  the actual servers

Status in network-manager package in Ubuntu:
  Triaged
Status in resolvconf package in Ubuntu:
  In Progress

Bug description:
  resolv.conf currently just has

nameserver 127.0.0.53

  with resolved (its local stub resolver). We should have an extra
  comment on top of that that says

# systemd-resolved stub resolver; run "systemd-resolve --status" to
  see the actual name servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638836/+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 1631365] Re: unity8 greeter does not save the last used session

2016-11-28 Thread Josh Arenson

** Branch linked: lp:~josharenson/unity8/backported-session-icon-fix

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

Title:
  unity8 greeter does not save the last used session

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  How to reproduce:
   * Have both unity7 and unity8 sessions installed
   * Log in to unity8
   * Log out
   * The greeter suggests unity7 as the session to log in 

  It should save the last session and suggest that one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1631365/+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 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

Got this working on my laptop w/ unity8...
Except it does work, still see that thread message, except the count is 
opposite of what it should be.

When I disconnect the keyboard (usb as well as bt) it says count: 2, and
when I connect it count: 1

When I first run the test qml, it reports count: 0
when it should report 1, as the laptop has a keyboard.
The first time I connect a keyboard there is no report, or when I first 
disconnect it.
Subsequent connection I see count: 1 (should be 2)
...

So it does seem to work regardless of the thread message, just not as it
should.

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

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+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 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

2016-11-28 Thread Dave Chiluk

1. So this indicates to me that the kernel is unable to control the usb
device. When you mentioned earlier that you were able to investigate
the usb-c device with a 16.04.1 machine, what exact kernel version was
that machine running. uname -a output should be sufficient.

2. Can you similarly provide the exact kernel version that you are using
during commissioning, when dropped to shell?

3. Were you able to utilize the device under this kernel or did it
simply load the kernel driver there as well? I.e. do you see a device
for the usb device in /sys/class/net/?

4. Also can you please provide the lsusb -vv output from that machine as
well. I'd like to look up the device id's against the cdc_ether driver
to see if the device id was added to one of the later 4.4 kernels.

5. Also are you using stable images or daily images. If you haven't done so
already can you enable the daily images, and check using those?
Instructions are available here
http://maas.io/docs/en/installconfig-images
The images I'm referring to are available here
https://images.maas.io/ephemeral-v2/daily/

Thank you,

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

Title:
Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
Invalid
Status in maas-images:
New
Status in initramfs-tools package in Ubuntu:
New
Status in linux package in Ubuntu:
Invalid

Bug description:
After upgrade from MAAS 2.0 to MAAS 2.1:

Cannot enlist/commission client machines via network boot (or pre-
staging machine) when using usb-c network adapter D59GG (e.g.
Precision 5510). This was working ok with MAAS 2.0.

Using the Xenial 16.04 base image for enlist/commission (no minimum
kernel set).

Enlist/Commission/Deploy works fine with other laptop and desktop
models which have a built in NIC.

From an already deployed Precision 5510 system (16.04.1) I can see the
following module is loaded when the usb-c adapter is connected (and
working):

$ lsmod
usbnet45056 1 cdc_ether

Errors received on client during enlisting with MAAS:

no /run/net-bootif.conf
lvmetad is not activated
...invalid path for logical volume.
gave up waiting for root device
common problems: boot args (cat /proc/cmdline)
check rootdelay = (did system wait long enough)
check root = (did the system wait for the right device?)
missing modules (cat /proc/modules)
ALERT!
/dev/disk/by-path/ip-:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1
does not exist. Dropping to shell!
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver

- cat /proc/cmdline shows mac address that of usb-c network adapter.
- cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xc009c000”
- cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

I've tried enlisting with older boot image and different kernel versions
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

It seems like the usb-c network adapter isn't loading properly or
maybe just not quickly enough?

Please let me know if you require any more info. I can provide info
from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1639202/+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 1278223] Re: Mouse Flickering after adding 3rd Monitor

2016-11-28 Thread psylem

I disabled compositing and the flicker went away, but I now get some
funky mouse trails that don't get cleaned up when crossing the edge
between monitor 1 and monitor 2.

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+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 1380480] Re: network disabled after suspend - resume

2016-11-28 Thread Kristijan Žic 

Confirming the presence of this bug in 16.10

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

Title:
  network disabled after suspend - resume

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

Bug description:
  Background: 
  this started to happen after the upgrade to Utopic Beta 1

  3) When I close the laptop's lid and open, the wifi should reconnect
  4) Wifi does not reconnect. It says "Wi-Fi networks" - "disconnected" when I 
left-click on NM icon in notif area. However the context menu (right-click) has 
items "Enable networking" and "Enable Wi-Fi" both with checkmarks.

  Workarounds: 
  switch off - on the physical switch on laptop OR  two times go and select 
"Enable networking" in the NM context menu (after first time it removes 
checkmark and the  "Enable Wi-Fi" item - visual feedback of being disabled).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu27
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 11 22:33:06 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-21 (447 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  IpRoute:
   default via 192.168.10.1 dev wlan0  proto static 
   10.9.9.0/24 dev vboxnet0  proto kernel  scope link  src 10.9.9.1 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.239  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-07-19T15:03:44.847279
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380480/+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 1573296] Re: obsolete conffiles not cleaned up on upgrade

2016-11-28 Thread Mathew Hodson

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

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

Title:
  obsolete conffiles not cleaned up on upgrade

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  Impact:

  When upgrading to xenial from earlier releases, some files are left on
  the user's system. They are not used, but may otherwise be mistaken
  for being used by the user if they are attempting to fix a problem.

  Regression potential:

  Low to none, as the relevant files are not used, and are being removed
  when the updated version of Pulseaudio is installed. These files are
  already removed in yakkety and later.

  Test case:

  When updating from trusty to xenial, one will note the presence of the
  below listed files on the system. Updating from pulseaudio in xenial
  or pulseaudio in trusty to what is in xenial-proposed shoudl delete
  the listed files. The /etc/init.d/pulseaudio script should also be
  unregistered.

  
  Original bug report:

  The following files are marked obsolete after the upgrade to 16.04:

   /etc/init/pulseaudio.conf 6244f8d452b29be7d17219b2db34138f obsolete
   /etc/init.d/pulseaudio df2873ee4f4673d53e3562a0de6e8aa0 obsolete
   /etc/default/pulseaudio 777f75f5521eab11c647da5c55544b1b obsolete
   /etc/bash_completion.d/pulseaudio df1f94a6b961900162bd18532c3c4c22 obsolete

  
  Those files should be cleaned up and the sysv init script properly 
deregistered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1573296/+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 1629009] Re: Does not work inside a snap due to hardcoded paths

2016-11-28 Thread Michael Sheldon

We've added a patch to maliit to support this via the MALIIT_PLUGIN_PATH
environment variable.

** Changed in: maliit-framework (Ubuntu)
   Status: New => Fix Released

** Changed in: maliit-framework (Ubuntu)
 Assignee: (unassigned) => Michael Sheldon (michael-sheldon)

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  In Progress
Status in address-book-service package in Ubuntu:
  In Progress
Status in dialer-app package in Ubuntu:
  In Progress
Status in history-service package in Ubuntu:
  New
Status in indicator-bluetooth package in Ubuntu:
  In Progress
Status in indicator-display package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  In Progress
Status in indicator-location package in Ubuntu:
  In Progress
Status in indicator-messages package in Ubuntu:
  In Progress
Status in indicator-network package in Ubuntu:
  In Progress
Status in indicator-power package in Ubuntu:
  In Progress
Status in indicator-session package in Ubuntu:
  In Progress
Status in indicator-sound package in Ubuntu:
  In Progress
Status in indicator-transfer package in Ubuntu:
  In Progress
Status in maliit-framework package in Ubuntu:
  Fix Released
Status in mediascanner2 package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress
Status in pay-service package in Ubuntu:
  New
Status in policykit-unity8 package in Ubuntu:
  Fix Released
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  In Progress
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  In Progress
Status in unity-scope-scopes package in Ubuntu:
  Won't Fix
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1638836] Re: resolv.conf for resolved stub server should have a comment how to see the actual servers

2016-11-28 Thread Steve Langasek

** Changed in: resolvconf (Ubuntu)
 Assignee: Canonical Foundations Team (canonical-foundations) => Steve 
Langasek (vorlon)

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

Title:
  resolv.conf for resolved stub server should have a comment how to see
  the actual servers

Status in resolvconf package in Ubuntu:
  In Progress

Bug description:
  resolv.conf currently just has

nameserver 127.0.0.53

  with resolved (its local stub resolver). We should have an extra
  comment on top of that that says

# systemd-resolved stub resolver; run "systemd-resolve --status" to
  see the actual name servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1638836/+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 1579580] Re: ureadahead reports relative path errors in journalctl output

2016-11-28 Thread Seth Arnold

xb5i70, ureadahead gets a list of files accessed during boot using the
debugfs filesystem and the linux kernel's tracing mechanism. You can see
the sources at http://bazaar.launchpad.net/~canonical-
scott/ureadahead/trunk/view/head:/src/trace.c#L115 for the raw details.

Thanks

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

Title:
  ureadahead reports relative path errors in journalctl output

Status in ureadahead package in Ubuntu:
  Confirmed

Bug description:
  ureadahead reports relative path errors in my journalctl output.

  This is currently 4368 lines of useless annoyances in my logs.

  To see if you have this problem, run: journalctl -b | grep ureadahead
  | grep relative | wc -l

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ureadahead 0.100.0-19
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May  8 15:55:18 2016
  InstallationDate: Installed on 2016-04-04 (34 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ureadahead
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+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 1645501] [NEW] corefiles not created in armhf chroot on arm64 porter

Public bug reported:

I'm filing this about gdb per Steve's suggestion, although this could be
an issue somewhere else.

I recently discovered that the apport-test-crash
(https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment
/test-crashes) crash files produced for armhf are crash files without
CoreDumps.  This happened sometime between 20160531 and 20161025.  I've
recreated this on the porter-arm64 box with the following minimal test
case (generate-sigsegv-crash.py is from apport-test-crashes):

schroot -c yakkety-armhf
python generate-sigsegv-crash.py cat

Running this on both armhf and arm64 we can see the following different
output.

armhf chroot on porter-armhf:

  47 Program received signal SIGSEGV, Segmentation fault.
  48 0xb6f599e4 in read () at ../sysdeps/unix/syscall-template.S:84
  49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
  50 (gdb) Saved corefile /tmp/tmp840s08i1/my.core

armhf chroot on porter-arm64:

  47 Program received signal SIGSEGV, Segmentation fault.
  48 0xf772f9e4 in read () at ../sysdeps/unix/syscall-template.S:84
  49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
  50 (gdb) Unable to fetch the floating point registers.: Invalid argument.

Notice how there is no core file save on porter-arm64.

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

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

Title:
  corefiles not created in armhf chroot on arm64 porter

Status in gdb package in Ubuntu:
  New

Bug description:
  I'm filing this about gdb per Steve's suggestion, although this could
  be an issue somewhere else.

  I recently discovered that the apport-test-crash
  (https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment
  /test-crashes) crash files produced for armhf are crash files without
  CoreDumps.  This happened sometime between 20160531 and 20161025.
  I've recreated this on the porter-arm64 box with the following minimal
  test case (generate-sigsegv-crash.py is from apport-test-crashes):

  schroot -c yakkety-armhf
  python generate-sigsegv-crash.py cat

  Running this on both armhf and arm64 we can see the following
  different output.

  armhf chroot on porter-armhf:

47 Program received signal SIGSEGV, Segmentation fault.
48 0xb6f599e4 in read () at ../sysdeps/unix/syscall-template.S:84
49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
50 (gdb) Saved corefile /tmp/tmp840s08i1/my.core

  armhf chroot on porter-arm64:

47 Program received signal SIGSEGV, Segmentation fault.
48 0xf772f9e4 in read () at ../sysdeps/unix/syscall-template.S:84
49 84  ../sysdeps/unix/syscall-template.S: No such file or directory.
50 (gdb) Unable to fetch the floating point registers.: Invalid argument.

  Notice how there is no core file save on porter-arm64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1645501/+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 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

I can reproduce this on turbo.
Does not happen when running the inputinfo console app in qtsystem examples.

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

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+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 1576424] Re: Gimp crashes with text tool & caps lock

This bug was fixed in the package gtk+2.0 - 2.24.30-4ubuntu3

---
gtk+2.0 (2.24.30-4ubuntu3) yakkety; urgency=medium

  * debian/patches/lp1576424-explicitly-disconnect-keymap-signals.patch
- GtkEntry: Explicitly disconnect keymap signals. (LP: #1576424)

 -- Martin Wimpress   Tue, 04 Oct 2016
17:07:26 +0100

** Changed in: gtk+2.0 (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  Gimp crashes with text tool & caps lock

Status in GTK+:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Xenial:
  Fix Committed
Status in gtk+2.0 source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Gimp crashes with a segfault when I use caps lock while renaming a
  layer. It is possible Caps lock causes crashes in other events also.

  [Test Case]

  Steps to reproduce:

  1. Open a new blank gimp document
  2. select the text tool
  3. type a couple of words of text (gimp will create a text layer above the 
background layer)
  4. with the text tool still selected, click on the background layer (just to 
move away from the text layer)
  5. now double click on the text layer to rename the layer (layer name gets 
highlighted)
  6. press the caps lock key
  7. click on the background layer again (without renaming or doing anything to 
the text layer)
  Now repeat steps 5 and 6.
  Gimp crashes.

  [Regression Potential]

  None expected. The patch used has been taken from upstream
  development.

  
https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad

  Packages for Xenial and Yakkety have been built in a PPA and
  regression tested.

  [ Other Info ]

  I can force this to happen every time I launch Gimp. Rebooting makes
  no difference. It seems to be the second time I press caps lock that
  forces the crash. I tried launching Gimp with caps lock on vs caps
  lock off, but I don't believe it made any difference. I can force a
  crash every time following the above sequence.

  I deleted my gimp preferences folder then rebooted for good measure.
  Gimp created a fresh preferences folder, but it hasn't solved the
  problem. I was originally in single window mode, but the new
  preferences folder put me back to multi window, but it crashes either
  way.

  I ran dmesg | tail after the crash and got the following line:

  gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0
  error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000]

  I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver
  (available from the Additional Drivers tab). In that same tab, I also
  have enabled Processor microcode firmware for Intel CPUs. Terminal
  tells me Gimp version is 2.8.16-1ubuntu1

  I'm not very experienced with bug reporting and not sure what other
  information I need to supply. Gimp was absolutely rock solid on this
  machine with 15.10, so it may be a Xubuntu issue.

  Hope someone can take a look at this. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1576424/+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 1576424] Re: Gimp crashes with text tool & caps lock

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

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

Title:
  Gimp crashes with text tool & caps lock

Status in GTK+:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Xenial:
  Fix Committed
Status in gtk+2.0 source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Gimp crashes with a segfault when I use caps lock while renaming a
  layer. It is possible Caps lock causes crashes in other events also.

  [Test Case]

  Steps to reproduce:

  1. Open a new blank gimp document
  2. select the text tool
  3. type a couple of words of text (gimp will create a text layer above the 
background layer)
  4. with the text tool still selected, click on the background layer (just to 
move away from the text layer)
  5. now double click on the text layer to rename the layer (layer name gets 
highlighted)
  6. press the caps lock key
  7. click on the background layer again (without renaming or doing anything to 
the text layer)
  Now repeat steps 5 and 6.
  Gimp crashes.

  [Regression Potential]

  None expected. The patch used has been taken from upstream
  development.

  
https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad

  Packages for Xenial and Yakkety have been built in a PPA and
  regression tested.

  [ Other Info ]

  I can force this to happen every time I launch Gimp. Rebooting makes
  no difference. It seems to be the second time I press caps lock that
  forces the crash. I tried launching Gimp with caps lock on vs caps
  lock off, but I don't believe it made any difference. I can force a
  crash every time following the above sequence.

  I deleted my gimp preferences folder then rebooted for good measure.
  Gimp created a fresh preferences folder, but it hasn't solved the
  problem. I was originally in single window mode, but the new
  preferences folder put me back to multi window, but it crashes either
  way.

  I ran dmesg | tail after the crash and got the following line:

  gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0
  error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000]

  I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver
  (available from the Additional Drivers tab). In that same tab, I also
  have enabled Processor microcode firmware for Intel CPUs. Terminal
  tells me Gimp version is 2.8.16-1ubuntu1

  I'm not very experienced with bug reporting and not sure what other
  information I need to supply. Gimp was absolutely rock solid on this
  machine with 15.10, so it may be a Xubuntu issue.

  Hope someone can take a look at this. Thanks.

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

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

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

> But perhaps it would be simpler to provide users a way to disable this
functionality manually? Is there any kind of runtime configuration
available?

At runtime, it doesn't seem to have a way, for instance, I already tried
the following without success: do-forward-updates false;

# man dhclient.conf
   If  you  want  to  do  DNS  updates  in the DHCP client script (see 
dhclient-script(8)) rather than having the DHCP client do the update directly 
(for example, if you want to use SIG(0) authentication, which is not supported 
directly by the DHCP client, you can
   instruct the client not to do the update using the do-forward-updates 
statement.  Flag should be true if you want the DHCP client to do the update, 
and false if you don't want the DHCP client to do the update.  By default,  the 
 DHCP  client  will  do  the  DNS
   update.

To disable the functionality at the moment for Trusty, manipulation in
the source package is required.

Undefine NSUPDATE in includes/site.h :

-#define NSUPDATE
+/* #define NSUPDATE */

and disabled failover and tracing in debian/rules :

./configure \
--prefix=/usr \
--sysconfdir=/etc/dhcp \
+   --disable-tracing \
+   --disable-failover \


Eric

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  
  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient   
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+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 1645485] [NEW] very old display driver bug?

2016-11-28 Thread gregrwm

Public bug reported:

the most bothersome, most notable, and most curious symptom of this bug
is the absolute degree to which the display locks up.  xclock's seconds
are no longer changing, the mouse cursor won't move, and even ctl-alt-F1
does nothing.

meanwhile mplayer, playing in a hidden tmux window, is still playing
merrily along.

i logged in via sshd and copied this from htop:
0  [|100.0%] Tasks: 68; 3 running
1  [|| 1.3%] Load average: 1.00 0.91 
0.53
Mem[|973M/1.91G] Time: 14:26:17
Swp[   0K/1.86G]
  PID START USER   VIRT   RES  NI CPU%   TIME+  S Command
 1714 12:50 g 1713M  789M   0  0.0  6:37.92 S /usr/lib/firefox/firefox
 2368 14:07 g  661M 57252   0  0.0  0:03.33 S /usr/bin/python3 
/usr/bin/blueman-manager
  794 12:49 root   269M 54988   0 99.3 10:12.88 R /usr/lib/xorg/Xorg -core 
:0 -seat seat0 -auth /var/
 2385 14:07 g  583M 53524   0  0.0  0:00.39 S /usr/bin/python3 
/usr/bin/blueman-applet
 2397 14:07 g  555M 42968   0  0.0  0:10.68 S pavucontrol
 1926 12:57 g  282M 37752   0  0.7  0:02.46 S 
/usr/lib/firefox/plugin-container /opt/google/talkp
 1933 12:57 g  512M 36404   0  0.0  0:02.96 S 
/opt/google/talkplugin/GoogleTalkPlugin
 2403 14:07 g  823M 30352   0  0.0  0:03.52 S mplayer -ao pulse -af 
channels=2 -framedrop -msgcol
F1Help  F2Setup F3SearchF4FilterF5Tree  F6SortByF7Nice -F8Nice +F9Kill  F10Quit

ps also attached, taken before killing xorg.

i've filed this under xorg merely because xorg is the one stuck eating
all the CPU.  i really suspect the display driver, and don't know how to
find or identify that.

i much more commonly saw these very same symptoms when i used to run
xscreensaver.  i stopped running xscreensaver just to stop beating my
head against that wall.  but many years and many releases later, it
looks like this display driver bug is still lurking around.

there was hardly anything running when this froze.  i already mentioned
mplayer (sound only) and tmux, twm's the window manager, firefox was
running but iconized and idle tho running gmail and the googletalk
plugin, not that i suspect any of them in any way.  xterm was occupying
most of the screen, showing tmux, and idle.  the ones i'd more suspect
would be xclock & pavucontrol.  pavucontrol was hidden but busily
showing it's audio level bar, xclock was visible and displaying the time
of day including seconds, so the most likely one to have tripped a
display driver bug.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Nov 28 14:36:38 2016
InstallationDate: Installed on 2016-10-15 (43 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "ps taken before xorg killed"
   https://bugs.launchpad.net/bugs/1645485/+attachment/4784403/+files/ps

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

Title:
  very old display driver bug?

Status in xorg package in Ubuntu:
  New

Bug description:
  the most bothersome, most notable, and most curious symptom of this
  bug is the absolute degree to which the display locks up.  xclock's
  seconds are no longer changing, the mouse cursor won't move, and even
  ctl-alt-F1 does nothing.

  meanwhile mplayer, playing in a hidden tmux window, is still playing
  merrily along.

  i logged in via sshd and copied this from htop:
  0  [|100.0%] Tasks: 68; 3 running
  1  [|| 1.3%] Load average: 1.00 0.91 
0.53
  Mem[|973M/1.91G] Time: 14:26:17
  Swp[   0K/1.86G]
PID START USER   VIRT   RES  NI CPU%   TIME+  S Command
   1714 12:50 g 1713M  789M   0  0.0  6:37.92 S /usr/lib/firefox/firefox
   2368 14:07 g  661M 57252   0  0.0  0:03.33 S /usr/bin/python3 
/usr/bin/blueman-manager
794 12:49 root   269M 54988   0 99.3 10:12.88 R /usr/lib/xorg/Xorg 
-core :0 -seat seat0 -auth /var/
   2385 14:07 g  583M 53524   0  0.0  0:00.39 S /usr/bin/python3 
/usr/bin/blueman-applet
   2397 14:07 g  555M 42968   0  0.0  0:10.68 S pavucontrol
   1926 12:57 g  282M 37752   0  0.7  0:02.46 S 
/usr/lib/firefox/plugin-container /opt/google/talkp
   1933 12:57 g  512M 36404   0  0.0  0:02.96 S 
/opt/google/talkplugin/GoogleTalkPlugin

[Touch-packages] [Bug 1644468] Re: pull to refresh text to bright on scopes with new theme

2016-11-28 Thread Michał Sawicz

** Branch linked: lp:~cimi/unity8/fix-pull-to-refresh-text-color

** Changed in: canonical-devices-system-image
   Status: Confirmed => In Progress

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

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

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => High

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Andrea Cimitan (cimi)

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

Title:
  pull to refresh text to bright on scopes with new theme

Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  the rc-proposed images recently got new scopes and a brighter theme.
  with this theme the "pull to refresh" text in the scopes became
  unreadable bright (see attached screenshot). the grey tone of the font
  is only very minimally brighter than the background. if we want to
  keep the text there it should be changed to have more contrast so it
  is readable.

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

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

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

2016-11-28 Thread Robie Basak

> Will ask the SRU team if it would be acceptable to split up the binary
package in two to include changes (already applied in Xenial) to trusty.

I think that it's important that existing Trusty users can continue to
use this DDNS functionality after the SRU without any necessary
intervention. They may be depending on this functionality. If they have
to do something (such as install the additional package manually), then
that would be a regression and not acceptable in an SRU.

If there's a way to do the split such that users will automatically get
isc-dhcp-client-ddns installed but users bothered by this bug then have
the option to switch to the one without it, then that might work. But
perhaps it would be simpler to provide users a way to disable this
functionality manually? Is there any kind of runtime configuration
available?

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  
  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient   
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+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 1629009] Re: Does not work inside a snap due to hardcoded paths

2016-11-28 Thread Michael Terry

** Also affects: maliit-framework (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  In Progress
Status in address-book-service package in Ubuntu:
  In Progress
Status in dialer-app package in Ubuntu:
  In Progress
Status in history-service package in Ubuntu:
  New
Status in indicator-bluetooth package in Ubuntu:
  In Progress
Status in indicator-display package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  In Progress
Status in indicator-location package in Ubuntu:
  In Progress
Status in indicator-messages package in Ubuntu:
  In Progress
Status in indicator-network package in Ubuntu:
  In Progress
Status in indicator-power package in Ubuntu:
  In Progress
Status in indicator-session package in Ubuntu:
  In Progress
Status in indicator-sound package in Ubuntu:
  In Progress
Status in indicator-transfer package in Ubuntu:
  In Progress
Status in maliit-framework package in Ubuntu:
  New
Status in mediascanner2 package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress
Status in pay-service package in Ubuntu:
  New
Status in policykit-unity8 package in Ubuntu:
  Fix Released
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  In Progress
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  In Progress
Status in unity-scope-scopes package in Ubuntu:
  Won't Fix
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-28 Thread Olivier Tilloy

I don’t know where that code lives.
https://code.launchpad.net/ubuntu/+source/qtsystems-opensource-src/ doesn’t 
have the latest changes it seems. Timo would know.

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

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+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 1323837] Re: [phone] Sim toolkit is not available on UT

2016-11-28 Thread taiebot65

By reporting it to bq or meizu. I have not purchased a supported phone
but if I had I would have highlighted this.

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

Title:
  [phone] Sim toolkit is not available on UT

Status in Canonical System Image:
  Incomplete
Status in Ubuntu UX:
  Triaged
Status in ofono package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  E.g. of SIm toolkit is http://support.vodafone.com.au/articles/FAQ
  /SIM-Toolkit

  While a lot of those addons are completely crap and useless, the SIm
  toolkit is sometimes used by some phone provider to set your sim card
  to roaming mode when you are abroad which makes it a must have.

  For the moment i need to borrow a second phone put my sim card in it,
  go to the Sim-toolkit, enable my sim card for roaming and put the sim
  card back in my UT to get my phone working while i am abroad. I need
  to do the same when i go back home.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1323837/+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 1610517] Re: package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade triggers looping

2016-11-28 Thread EdwardDyer

A number of errors of this type occurred during upgrade to 16.4.1 LTS

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

Title:
  package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade
  triggers looping

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

Bug description:
  While running a `do-release-upgrade` from Xubuntu 15.10 to 16.04
  something like a post-install hook apparently triggered looping.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hicolor-icon-theme 0.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-38.45-generic 4.2.8-ckt10
  Uname: Linux 4.2.0-38-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sat Aug  6 11:48:42 2016
  Dependencies:
   
  DuplicateSignature: package:hicolor-icon-theme:0.15-0ubuntu1:triggers 
looping, abandoned
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-02-24 (893 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-08-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1610517/+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 1610517] Re: package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade triggers looping

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

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

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

Title:
  package hicolo-icon-theme 0.15-ubuntu1 failed to install: upgrade
  triggers looping

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

Bug description:
  While running a `do-release-upgrade` from Xubuntu 15.10 to 16.04
  something like a post-install hook apparently triggered looping.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hicolor-icon-theme 0.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-38.45-generic 4.2.8-ckt10
  Uname: Linux 4.2.0-38-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sat Aug  6 11:48:42 2016
  Dependencies:
   
  DuplicateSignature: package:hicolor-icon-theme:0.15-0ubuntu1:triggers 
looping, abandoned
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-02-24 (893 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-08-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1610517/+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 1577596] Re: ntpd not started when using ntpdate

2016-11-28 Thread Ubuntu Foundations Team Bug Bot

The attachment "ntpdate_HH is a revised version of  /etc/network/if-
up.d/ntpdate" seems to be a patch.  If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Won't Fix

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+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 1643901] Re: flxdec security update tracking bug

2016-11-28 Thread Mathew Hodson

** No longer affects: gst-plugins-good0.10 (Ubuntu Yakkety)

** No longer affects: gst-plugins-good0.10 (Ubuntu Zesty)

** Changed in: gst-plugins-good0.10 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gst-plugins-good0.10 (Ubuntu)
   Status: Invalid => Fix Released

** No longer affects: gst-plugins-good1.0 (Ubuntu Precise)

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

Title:
  flxdec security update tracking bug

Status in gst-plugins-good0.10 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Confirmed
Status in gst-plugins-good0.10 source package in Precise:
  Fix Released
Status in gst-plugins-good0.10 source package in Trusty:
  Fix Released
Status in gst-plugins-good1.0 source package in Trusty:
  Fix Released
Status in gst-plugins-good0.10 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Yakkety:
  Fix Released
Status in gst-plugins-good1.0 source package in Zesty:
  Confirmed

Bug description:
  This bug is to track the security update to fix the flxdec out-of-
  bounds write.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1643901/+subscriptions

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

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

So long story short, starting with Xenial you have the possibility to
install "isc-dhcp-client" which doesn't include the 2 extra port
bindings, but if you need it for Dynamic DNS (DDNS) you can optionally
install "isc-dhcp-client-ddns".

On Trusty, "isc-dhcp-client" combine both.

Will ask the SRU team if it would be acceptable to split up the binary
package in two to include changes (already applied in Xenial) to trusty.

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  
  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient   
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

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

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

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

So long story short, starting with Xenial you have the possibility to
install "isc-dhcp-client" which doesn't include the 2 extra port
bindings, but if you need it for Dynamic DNS (DDNS) you can optionally
install "isc-dhcp-client-ddns".

On Trusty, "isc-dhcp-client" combine both, and AFAIK, I don't think the
SRU process will allow the source package to be re-designed just like
Xenial to add this new binary package "isc-dhcp-client-ddns" in Trusty
archive, since this according to me falls under a feature request more
than fixing a bug.

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  
  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient   
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

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

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

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

I was able to identify from where the port range list is initialize, and the 
decision is taken by binary package "libdns162" (source package "bind9")[1] 
which dhclient relies on.
Basically, it randomly takes any port available between 1024 and 65535[2]

So there is a port randomization mechanism made by the library that take
the decision instead of, for instance in some other cases, where the
decision is leave it to the kernel[3].

In this particular case both sysctl options :
net.ipv4.ip_local_port_range
net.ipv4.ip_local_reserved_ports

have no effect on port assignation decision.

[1] - 
https://github.com/wklaebe/bind9/blob/ac1dcdd124a5abdec4969e2c33836d863bf73aa7/lib/dns/dispatch.c#L1921
[2] - https://tools.ietf.org/html/rfc6335
[3] - Example : net.ipv4.ip_local_port_range = 32768 60999

Regards,

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  
  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient   
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+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 1645437] [NEW] Problem appear like Xorg

2016-11-28 Thread Cyrilux

Public bug reported:

In first, i working ubuntu16.04 on VirtualBox machine.Host is linux Mint
Cinnamon 17.3. I trying custom Ubuntu for Yosemite style whith help of
Noob's Lab. Lot of commands line don't work ! Maybe problem with Gtk3 ?

For examples: Gnome-Screenshot'captures are all black or back of screen
not the windows... During splash you can see a destroy picture like lot
of rays! and little others...

Sorry for my english (i'm french!!!) et thank you very much for you
work.

Cyril

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Nov 28 19:28:04 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2016-11-19 (9 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=17e79935-2f42-4abb-8d15-2246144b6d53 ro drm.debug=0xe quiet 
vesafb.invalid=1 nopat splash plymouth:debug
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
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: Mon Nov 28 19:26:22 2016
xserver.configfile: default
xserver.errors:
 AIGLX error: vboxvideo does not export required DRI extension
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
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/1645437

Title:
  Problem appear like Xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  In first, i working ubuntu16.04 on VirtualBox machine.Host is linux
  Mint Cinnamon 17.3. I trying custom Ubuntu for Yosemite style whith
  help of Noob's Lab. Lot of commands line don't work ! Maybe problem
  with Gtk3 ?

  For examples: Gnome-Screenshot'captures are all black or back of
  screen not the windows... During splash you can see a destroy picture
  like lot of rays! and little others...

  Sorry for my english (i'm french!!!) et thank you very much for you
  work.

  Cyril

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Nov 28 19:28:04 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

I meant latest repo for qtsystems-opensource-src.

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

Title:
  Mir-backed InputDeviceModel doesn’t work on touch device

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  I’ve prepared a branch of webbrowser-app that makes use of the latest
  qml-module-qtsysteminfo for input device detection
  (https://code.launchpad.net/~osomon/webbrowser-app/use-
  qtsystems/+merge/309667), and when I test it on arale, I’m seeing the
  following error in the logs when connecting a bluetooth keyboard/mouse
  combo to the device:

  QObject: Cannot create children for a parent that is in a different thread.
  (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is 
QThread(0x1fba0b8), current thread is QThread(0xb08612d8)

  This looks like a threading issue in the implementation of the Mir
  backend for InputInfo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+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 1645352] Re: No HDMI output after upgrade to 16.04!

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

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

Title:
  No HDMI output after upgrade to 16.04!

Status in xorg package in Ubuntu:
  New

Bug description:
  Running Ubuntu 16.04 64bit, 4.4.8 Kernel on an ASUS Trio with Intel® Haswell 
graphics card and using i915 driver. After upgrade there is no HDMI output to 
the external screen that I use daily. 
  I did the following:
  - Upgraded to  4.4.8 Kernel hoping that the issue would be resolved.
  - Checked for other reports of this issue and followed advise to use NVIDIA 
364 drivers. 
  - Checked Intel for the most recent driver which is already packaged with 
16.04;  it is the i915 driver which is in use.
  - Used Intel driver update tool to ensure that update is correct.
  - Purchased a HDMI adapter to use mini-display port; works and reports HDMI1 
is in use, but HDMI2 is not recognized (when monitor is plugged in to HDMI2)
  - Someone has assisted and has confirmed that there seems to be no hardware 
issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645352/+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 1645415] [NEW] Earphones not working on Ubuntu 16.04.1 after resume from suspend

2016-11-28 Thread Tapo

Public bug reported:

I am a new Ubuntu user and installed 16.04.1 LTS dual boot with Windows 10.
Recently I discovered that my earphones have a pulsating white noise after the 
machine is resumed from suspend. The laptop speakers are fine though. On reboot 
everything works fine.

I have tried restarting pulseaudio using following commands:
pulseaudio -k
pulseaudio --start

Also tried this:
/usr/bin/pasuspender /bin/true

But the pulsating sound persists.

My laptop model is ASUS ROG G501VW F1034T.

I have updated my system using commands:
sudo apt update
sudo apt upgrade

Please let me know if I need to provide outputs of commands or any
system logs.

Here is the "lsb_release -rd" command output: 
Description:Ubuntu 16.04.1 LTS
Release:16.04

** Affects: ubuntu
 Importance: Undecided
 Status: New

** Package changed: alsa-driver (Ubuntu) => ubuntu

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

Title:
  Earphones not working on Ubuntu 16.04.1 after resume from suspend

Status in Ubuntu:
  New

Bug description:
  I am a new Ubuntu user and installed 16.04.1 LTS dual boot with Windows 10.
  Recently I discovered that my earphones have a pulsating white noise after 
the machine is resumed from suspend. The laptop speakers are fine though. On 
reboot everything works fine.

  I have tried restarting pulseaudio using following commands:
  pulseaudio -k
  pulseaudio --start

  Also tried this:
  /usr/bin/pasuspender /bin/true

  But the pulsating sound persists.

  My laptop model is ASUS ROG G501VW F1034T.

  I have updated my system using commands:
  sudo apt update
  sudo apt upgrade

  Please let me know if I need to provide outputs of commands or any
  system logs.

  Here is the "lsb_release -rd" command output: 
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1645415/+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 1613949] Re: vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu 16.04.1 Xenial

I suspect you don't have -updates enabled for universe in your
/etc/apt/sources.list file.  If you did you'd see the following:

 $ apt-cache policy vim-gtk3
vim-gtk3:
  Installed: (none)
  Candidate: 2:7.4.1689-3ubuntu1.1
  Version table:
 2:7.4.1689-3ubuntu1.1 500
500 http://192.168.10.7/ubuntu xenial-updates/universe amd64 Packages
 2:7.4.1689-3ubuntu1 500
500 http://192.168.10.7/ubuntu xenial/universe amd64 Packages

vim-common and vim-runtime are in main and you seem to have -updates
enabled for that pocket.

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

Title:
  vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu
  16.04.1 Xenial

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  I have a fresh install of Ubuntu v16.04.1, then I did an `apt-get
  upgrade` and it only had a few seemingly-minor packages to upgrade
  (don't remember the list, sorry).

  Apparently all the core vim packages have been upgraded to
  2:7.4.1689-3ubuntu1.1 but vim-gtk3 (and all the other gvim-providing
  packages I tested) are still held back to 2:7.4.1689-3ubuntu1 so there
  is a version mis-match.

  Now I get the following error:

  [[[ BEGIN PASTE ]]]

  root@machine:/# apt-get install vim-gtk3
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   vim-gtk3 : Depends: vim-common (= 2:7.4.1689-3ubuntu1) but 
2:7.4.1689-3ubuntu1.1 is to be installed
  Depends: vim-runtime (= 2:7.4.1689-3ubuntu1) but 
2:7.4.1689-3ubuntu1.1 is to be installed
  E: Unable to correct problems, you have held broken packages.

  [[[ END PASTE ]]]

  
  However I can still get gvim working if I force the installation of the 
vim-gtk3 package using dpkg.  Of course this is not a good solution, because it 
leaves my system in a state of seemingly-broken packages!

  
  [[[ BEGIN PASTE ]]]

  root@machine:/# dpkg -i --force-depends ./vim-gtk3_7.4.1689-3ubuntu1_amd64.deb
  Selecting previously unselected package vim-gtk3.
  (Reading database ... 251539 files and directories currently installed.)
  Preparing to unpack .../vim-gtk3_7.4.1689-3ubuntu1_amd64.deb ...
  Unpacking vim-gtk3 (2:7.4.1689-3ubuntu1) ...
  dpkg: vim-gtk3: dependency problems, but configuring anyway as you requested:
   vim-gtk3 depends on vim-common (= 2:7.4.1689-3ubuntu1); however:
Version of vim-common on system is 2:7.4.1689-3ubuntu1.1.
   vim-gtk3 depends on vim-runtime (= 2:7.4.1689-3ubuntu1); however:
Version of vim-runtime on system is 2:7.4.1689-3ubuntu1.1.

  Setting up vim-gtk3 (2:7.4.1689-3ubuntu1) ...
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vim (vim) in 
auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vimdiff 
(vimdiff) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rvim (rvim) 
in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rview 
(rview) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vi (vi) in 
auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/view (view) 
in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/ex (ex) in 
auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/editor 
(editor) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvim (gvim) 
in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gview 
(gview) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgview 
(rgview) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgvim 
(rgvim) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/evim (evim) 
in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/eview 
(eview) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvimdiff 
(gvimdiff) in auto mode

  [[[ END PASTE ]]]

  
  And yes, I can confirm that gvim actually works using this method.  We just 
need to upgrade the package versioning so that we don't have a problem with the 
apt-get packaging dependency system.

  Thanks for all your hard work.  Ubuntu is #1!!!  :-)

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

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

[Touch-packages] [Bug 1645352] [NEW] No HDMI output after upgrade to 16.04!

You have been subscribed to a public bug:

Running Ubuntu 16.04 64bit, 4.4.8 Kernel on an ASUS Trio with Intel® Haswell 
graphics card and using i915 driver. After upgrade there is no HDMI output to 
the external screen that I use daily. 
I did the following:
- Upgraded to  4.4.8 Kernel hoping that the issue would be resolved.
- Checked for other reports of this issue and followed advise to use NVIDIA 364 
drivers. 
- Checked Intel for the most recent driver which is already packaged with 
16.04;  it is the i915 driver which is in use.
- Used Intel driver update tool to ensure that update is correct.
- Purchased a HDMI adapter to use mini-display port; works and reports HDMI1 is 
in use, but HDMI2 is not recognized (when monitor is plugged in to HDMI2)
- Someone has assisted and has confirmed that there seems to be no hardware 
issues.

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


** Tags: bot-comment
-- 
No HDMI output after upgrade to 16.04!
https://bugs.launchpad.net/bugs/1645352
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

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

After more investigation, it seems like the 2 extra port-bindings port
assignation decision is made by "libdns" itself.

https://github.com/wklaebe/bind9/blob/ac1dcdd124a5abdec4969e2c33836d863bf73aa7/lib/dns/dispatch.c#L1921

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

Title:
isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
In Progress

Bug description:
Ubuntu 13.04 Server 64-bit. Fresh install. Only one network adapter.

dhclient process is listening on two randomly chosen udp ports in
addition to the usual port 68. This appears to be a bug in the
discovery code for probing information on interfaces in the system.

Initial research of the code also suggested omapi, but adding omapi
port to /etc/dhcp/dhclient.conf only opened a forth port with the
two random udp ports still enabled.

Version of included distro dhclient was 4.2.4. I also tested with the
latest isc-dhclient-4.2.5-P1 and got the same results.

Debian has the same bug:
http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

One impact of these random ports is that security hardening becomes
more difficult. The purpose of these random ports and security
implications are unknown.

Example netstat -lnp output:

udp0 0 0.0.0.0:21117 0.0.0.0:*
2659/dhclient
udp0 0 0.0.0.0:68 0.0.0.0:*
2659/dhclient
udp6 0 0 :::45664:::*
2659/dhclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+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 1644541] Re: Update stuck at “configuring unattended-upgrades”

It'd be helpful to see /var/log/apt/term.log from a system that
encounters this issue.

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

Title:
  Update stuck at “configuring unattended-upgrades”

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  On basically fresh install from ubuntu-16.04.1-desktop-amd64.iso; no
  updates or installs had been applied since installing the OS from the
  media.

  During execution of "Software Updater", it freezes indefinitely while
  "Installing updates..." at the step marked "Configuring unattended-
  upgrades."

  It appears that this happens if System Settings->Software &
  Updates->Updates, "Automatically check for updates" has been set to
  "Never."

  If that is instead set to "Daily" and the following are then set in
  /etc/apt/apt.conf.d/10periodic then the update succeeds:

  APT::Periodic::Update-Package-Lists "1";
  APT::Periodic::Download-Upgradeable-Packages "1";
  APT::Periodic::AutocleanInterval "7";
  APT::Periodic::Unattended-Upgrade "1";

  Someone else had asked about this issue at AskUbuntu.  Their question
  along with my answer (from Kevin) provide some further details:

  http://askubuntu.com/questions/851371/update-stuck-at-configuring-
  unattended-upgrades-software-updater-turned-black/852110#852110

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1644541/+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 1577596] Re: ntpd not started when using ntpdate

2016-11-28 Thread Heinrich Hartl

Please do not blame me too hard if I provided a "patch" not in the
correct format - but the script does the job for me. ntpd is started and
continues to run, ntpdate seems to be invoked twice. The first
invocation is too early and failes. The next one does its job but
doesn't do a very impressive correction of the system time.

And here is an excerpt from my reboot log:
$ grep -i ntp syslog_1743
Nov 28 17:33:49 localhost kernel: [0.076562] Mountpoint-cache hash table 
entries: 2048 (order: 1, 8192 bytes)
Nov 28 17:33:49 localhost ntpdate[781]: no servers can be used, exiting
Nov 28 17:34:01 localhost systemd[1]: Starting LSB: Start NTP daemon...
Nov 28 17:34:02 localhost ntp[1285]:  * Starting NTP server ntpd
Nov 28 17:34:02 localhost ntpd[1306]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:48 
UTC 2016 (1): Starting
Nov 28 17:34:02 localhost ntpd[1306]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 116:125
Nov 28 17:34:02 localhost ntp[1285]:...done.
Nov 28 17:34:02 localhost systemd[1]: Started LSB: Start NTP daemon.
Nov 28 17:34:02 localhost ntpd[1309]: proto: precision = 0.129 usec (-23)
Nov 28 17:34:02 localhost ntpd[1309]: restrict 0.0.0.0: KOD does nothing 
without LIMITED.
Nov 28 17:34:02 localhost ntpd[1309]: restrict ::: KOD does nothing without 
LIMITED.
Nov 28 17:34:02 localhost ntpd[1309]: Listen and drop on 0 v6wildcard [::]:123
Nov 28 17:34:02 localhost ntpd[1309]: Listen and drop on 1 v4wildcard 
0.0.0.0:123
Nov 28 17:34:02 localhost ntpd[1309]: Listen normally on 2 lo 127.0.0.1:123
Nov 28 17:34:02 localhost ntpd[1309]: Listen normally on 3 eth0 192.168.0.12:123
Nov 28 17:34:02 localhost ntpd[1309]: Listen normally on 4 lo [::1]:123
Nov 28 17:34:02 localhost ntpd[1309]: Listen normally on 5 eth0 
[fe80::221:9bff:fe4c:d684%2]:123
Nov 28 17:34:02 localhost ntpd[1309]: Listening on routing socket on fd #22 for 
interface updates
Nov 28 17:34:05 localhost ntpdate[1154]: adjust time server 172.26.195.1 offset 
-0.28 sec

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Won't Fix

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions

-- 
Mailing

[Touch-packages] [Bug 1323837] Re: [phone] Sim toolkit is not available on UT

2016-11-28 Thread Alien911

is there any way to get this to work, som workaround? this is the one
ting that makes Ubuntu phone usless as my main phone.

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

Title:
  [phone] Sim toolkit is not available on UT

Status in Canonical System Image:
  Incomplete
Status in Ubuntu UX:
  Triaged
Status in ofono package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  E.g. of SIm toolkit is http://support.vodafone.com.au/articles/FAQ
  /SIM-Toolkit

  While a lot of those addons are completely crap and useless, the SIm
  toolkit is sometimes used by some phone provider to set your sim card
  to roaming mode when you are abroad which makes it a must have.

  For the moment i need to borrow a second phone put my sim card in it,
  go to the Sim-toolkit, enable my sim card for roaming and put the sim
  card back in my UT to get my phone working while i am abroad. I need
  to do the same when i go back home.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1323837/+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 1577596] Re: ntpd not started when using ntpdate

2016-11-28 Thread Heinrich Hartl

attached version of ntpdate solves the problem for me and hopefully for 
everybody.
I do not mind if comments are removed.
The attached version avoids the conflict between ntpd and ntpdate and also 
makes the skript simpler.


** Attachment added: "ntpdate_HH is a revised version of  
/etc/network/if-up.d/ntpdate"
   
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596/+attachment/4784298/+files/ntpdate_HH

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Won't Fix

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+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 1645384] [NEW] package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida d

2016-11-28 Thread José Andrade Méndez Julián

Public bug reported:

el problema se genero cuando intentaba descargar unos programas, no se
completo la descarga  y la tuve que reiniciar y posterior al reinicio
aparecio el  mensaje de error.

ProblemType: Package
DistroRelease: elementary 0.4
Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Nov 28 09:10:05 2016
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 128
InstallationDate: Installed on 2016-11-26 (1 days ago)
InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to 
install/upgrade: el subproceso instalado el script post-installation devolvió 
el código de salida de error 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package loki third-party-packages

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

Title:
  package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to
  install/upgrade: el subproceso instalado el script post-installation
  devolvió el código de salida de error 128

Status in gconf package in Ubuntu:
  New

Bug description:
  el problema se genero cuando intentaba descargar unos programas, no se
  completo la descarga  y la tuve que reiniciar y posterior al reinicio
  aparecio el  mensaje de error.

  ProblemType: Package
  DistroRelease: elementary 0.4
  Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Nov 28 09:10:05 2016
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 128
  InstallationDate: Installed on 2016-11-26 (1 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to 
install/upgrade: el subproceso instalado el script post-installation devolvió 
el código de salida de error 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1645384/+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 1645363] Re: slow sbuild Debian package builds (schroot calls are slow)

2016-11-28 Thread Martin Pitt

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

Thanks for confirming!

** This bug has been marked a duplicate of bug 1626436
   [4.8 regression] boot has become very slow

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

Title:
  slow sbuild Debian package builds (schroot calls are slow)

Status in sbuild package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade to Ubuntu 16.10, building packages with sbuild takes
  much more time than previously. sbuild creates a schroot session for
  building Debian packages and calls sbuild --run-session several times.
  Entering the sessions takes norally 10 ms, but entering the session
  from sbuild takes several seconds now:

  time schroot -d / -c $session --run-session -q -u root -p -- true
  real0m2.098s
  user0m0.008s
  sys 0m0.000s

  This causes a drastic build time increase for small packages. Example
  package build time on my affected Ubuntu workstation:

  Build-Time: 9 s
  Install-Time: 115 s
  Package-Time: 195 s (= 00:03:15)

  compared to the build bot running Debian stable (having a slower
  processor):

  Build-Time: 9 s
  Install-Time: 24 s
  Package-Time: 41 s

  /var/log/syslog shows many entries about starting and stopping D-Bus
  services:

  Nov 28 16:27:34 konstrukt systemd[1]: Created slice User Slice of root.
  Nov 28 16:27:34 konstrukt systemd[1]: Starting User Manager for UID 0...
  Nov 28 16:27:34 konstrukt systemd[1]: Started Session 2 of user root.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Timers.
  Nov 28 16:27:34 konstrukt systemd[21965]: Starting D-Bus User Message Bus 
Socket.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Paths.
  Nov 28 16:27:34 konstrukt systemd[21965]: Listening on D-Bus User Message Bus 
Socket.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Sockets.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Basic System.
  Nov 28 16:27:34 konstrukt systemd[21965]: Starting Run Click user-level 
hooks...
  Nov 28 16:27:34 konstrukt systemd[21965]: Started D-Bus User Message Bus.
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Error parsing manifest for 
package 'com.ubuntu.gallery': com.ubuntu.gallery does not exist in any database 
for user root
  Nov 28 16:27:34 konstrukt /usr/lib/snapd/snapd[1086]: daemon.go:174: DEBUG: 
uid=0;@ GET /v2/snaps/com.ubuntu.gallery 40.327µs 404
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Unable to get snap 
information for 'com.ubuntu.gallery': Status code is: 404
  Nov 28 16:27:34 konstrukt dbus-daemon[22004]: Activating service 
name='ca.desrt.dconf'
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Error parsing manifest for 
package 'com.ubuntu.gallery': com.ubuntu.gallery does not exist in any database 
for user root
  Nov 28 16:27:34 konstrukt /usr/lib/snapd/snapd[1086]: daemon.go:174: DEBUG: 
uid=0;@ GET /v2/snaps/com.ubuntu.gallery 23.455µs 404
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Unable to get snap 
information for 'com.ubuntu.gallery': Status code is: 404
  Nov 28 16:27:34 konstrukt dbus-daemon[22004]: Successfully activated service 
'ca.desrt.dconf'
  Nov 28 16:27:35 konstrukt dbus-daemon[22004]: Activating via systemd: service 
name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
  Nov 28 16:27:35 konstrukt systemd[21965]: Starting Virtual filesystem 
service...
  Nov 28 16:27:35 konstrukt dbus-daemon[22004]: Successfully activated service 
'org.gtk.vfs.Daemon'
  Nov 28 16:27:35 konstrukt systemd[21965]: Started Virtual filesystem service.
  Nov 28 16:27:35 konstrukt click[21997]: 
/usr/lib/ubuntu-push-client/click-hook:15: PyGIWarning: Click was imported 
without specifying a version first. Use gi.require_version('Click', '0.4') 
before import to ensure that the right version gets loaded.
  Nov 28 16:27:35 konstrukt click[21997]:   from gi.repository import Click
  Nov 28 16:27:35 konstrukt click[21997]: hooks.vala:1216: User-level hook 
push-helper failed: Hook command 
'/usr/lib/ubuntu-push-client/click-hook-wrapper' failed: Child process exited 
with code 1
  Nov 28 16:27:35 konstrukt click[21997]: Some user-level hooks failed: 
push-helper
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Main 
process exited, code=exited, status=1/FAILURE
  Nov 28 16:27:35 konstrukt systemd[21965]: Failed to start Run Click 
user-level hooks.
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Unit 
entered failed state.
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Failed 
with result 'exit-code'.
  Nov 28 16:27:35 konstrukt systemd[21965]: Reached target Default. 
  Nov 28 16:27:35 konstrukt systemd[21965]: Startup finished in 497ms.
  Nov 28 16:27:35 konstrukt systemd[1]: Started User Manager for

[Touch-packages] [Bug 1642863] Re: Upgrading unattended-upgrades gives errors and a warning

** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Upgrading unattended-upgrades gives errors and a warning

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Ubuntu release
  ==

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  Package version
  ===

  unattended-upgrades:
Installed: 0.90ubuntu0.2
Candidate: 0.90ubuntu0.2
Version table:
   *** 0.90ubuntu0.2 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages

  What I expected to happen
  =

  No error or warning messages during a software upgrade.

  What happened instead
  =

  When an updated version of unattended-upgrades is installed, the
  following error messages appear because /tmp is mounted noexec for
  security reasons (see the Securing Debian Manual, section 4.10 at
  https://www.debian.org/doc/manuals/securing-debian-
  howto/ch4.en.html#s4.10):

  Preconfiguring packages ...
  Can't exec "/tmp/unattended-upgrades.config.5svL0F": Permission denied at 
/usr/share/perl/5.22/IPC/Open3.pm line 178.
  open2: exec of /tmp/unattended-upgrades.config.5svL0F configure 
0.90ubuntu0.1 failed at /usr/share/perl5/Debconf/ConfModule.pm line 59.

  Also, the following warning occurs later on:

  Setting up unattended-upgrades (0.90ubuntu0.2) ...
  update-rc.d: warning: start and stop actions are no longer supported; 
falling back to defaults

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 18 02:36:54 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-01 (17 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "0";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-11-07T13:58:08.805628

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1642863/+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 1644541] Re: Update stuck at “configuring unattended-upgrades”

** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Update stuck at “configuring unattended-upgrades”

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  On basically fresh install from ubuntu-16.04.1-desktop-amd64.iso; no
  updates or installs had been applied since installing the OS from the
  media.

  During execution of "Software Updater", it freezes indefinitely while
  "Installing updates..." at the step marked "Configuring unattended-
  upgrades."

  It appears that this happens if System Settings->Software &
  Updates->Updates, "Automatically check for updates" has been set to
  "Never."

  If that is instead set to "Daily" and the following are then set in
  /etc/apt/apt.conf.d/10periodic then the update succeeds:

  APT::Periodic::Update-Package-Lists "1";
  APT::Periodic::Download-Upgradeable-Packages "1";
  APT::Periodic::AutocleanInterval "7";
  APT::Periodic::Unattended-Upgrade "1";

  Someone else had asked about this issue at AskUbuntu.  Their question
  along with my answer (from Kevin) provide some further details:

  http://askubuntu.com/questions/851371/update-stuck-at-configuring-
  unattended-upgrades-software-updater-turned-black/852110#852110

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1644541/+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 1645362] Re: Calculator example is broken

** Also affects: ubuntu-ui-toolkit-examples
   Importance: Undecided
   Status: New

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

Title:
  Calculator example is broken

Status in ubuntu-ui-toolkit-examples:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  When I start the calculator example, I only see a header with
  'Calculator' as the title, and a '0' as a result for calculations, but
  there is no input field where I can enter new calculations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit-examples/+bug/1645362/+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 1645365] Re: customtheme example broken in the deb package

** Also affects: ubuntu-ui-toolkit-examples
   Importance: Undecided
   Status: New

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

Title:
  customtheme example broken in the deb package

Status in ubuntu-ui-toolkit-examples:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  The theme/ directory that contains the custom theme is missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit-examples/+bug/1645365/+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 1645363] Re: slow sbuild Debian package builds (schroot calls are slow)

2016-11-28 Thread Benjamin Drung

Yes! With linux 4.8.0-29-generic #31~lp1626436ProposedWithTwoPatches the
build is fast again:

Build-Time: 5
Install-Time: 18
Package-Time: 36

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

Title:
  slow sbuild Debian package builds (schroot calls are slow)

Status in sbuild package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade to Ubuntu 16.10, building packages with sbuild takes
  much more time than previously. sbuild creates a schroot session for
  building Debian packages and calls sbuild --run-session several times.
  Entering the sessions takes norally 10 ms, but entering the session
  from sbuild takes several seconds now:

  time schroot -d / -c $session --run-session -q -u root -p -- true
  real0m2.098s
  user0m0.008s
  sys 0m0.000s

  This causes a drastic build time increase for small packages. Example
  package build time on my affected Ubuntu workstation:

  Build-Time: 9 s
  Install-Time: 115 s
  Package-Time: 195 s (= 00:03:15)

  compared to the build bot running Debian stable (having a slower
  processor):

  Build-Time: 9 s
  Install-Time: 24 s
  Package-Time: 41 s

  /var/log/syslog shows many entries about starting and stopping D-Bus
  services:

  Nov 28 16:27:34 konstrukt systemd[1]: Created slice User Slice of root.
  Nov 28 16:27:34 konstrukt systemd[1]: Starting User Manager for UID 0...
  Nov 28 16:27:34 konstrukt systemd[1]: Started Session 2 of user root.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Timers.
  Nov 28 16:27:34 konstrukt systemd[21965]: Starting D-Bus User Message Bus 
Socket.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Paths.
  Nov 28 16:27:34 konstrukt systemd[21965]: Listening on D-Bus User Message Bus 
Socket.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Sockets.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Basic System.
  Nov 28 16:27:34 konstrukt systemd[21965]: Starting Run Click user-level 
hooks...
  Nov 28 16:27:34 konstrukt systemd[21965]: Started D-Bus User Message Bus.
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Error parsing manifest for 
package 'com.ubuntu.gallery': com.ubuntu.gallery does not exist in any database 
for user root
  Nov 28 16:27:34 konstrukt /usr/lib/snapd/snapd[1086]: daemon.go:174: DEBUG: 
uid=0;@ GET /v2/snaps/com.ubuntu.gallery 40.327µs 404
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Unable to get snap 
information for 'com.ubuntu.gallery': Status code is: 404
  Nov 28 16:27:34 konstrukt dbus-daemon[22004]: Activating service 
name='ca.desrt.dconf'
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Error parsing manifest for 
package 'com.ubuntu.gallery': com.ubuntu.gallery does not exist in any database 
for user root
  Nov 28 16:27:34 konstrukt /usr/lib/snapd/snapd[1086]: daemon.go:174: DEBUG: 
uid=0;@ GET /v2/snaps/com.ubuntu.gallery 23.455µs 404
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Unable to get snap 
information for 'com.ubuntu.gallery': Status code is: 404
  Nov 28 16:27:34 konstrukt dbus-daemon[22004]: Successfully activated service 
'ca.desrt.dconf'
  Nov 28 16:27:35 konstrukt dbus-daemon[22004]: Activating via systemd: service 
name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
  Nov 28 16:27:35 konstrukt systemd[21965]: Starting Virtual filesystem 
service...
  Nov 28 16:27:35 konstrukt dbus-daemon[22004]: Successfully activated service 
'org.gtk.vfs.Daemon'
  Nov 28 16:27:35 konstrukt systemd[21965]: Started Virtual filesystem service.
  Nov 28 16:27:35 konstrukt click[21997]: 
/usr/lib/ubuntu-push-client/click-hook:15: PyGIWarning: Click was imported 
without specifying a version first. Use gi.require_version('Click', '0.4') 
before import to ensure that the right version gets loaded.
  Nov 28 16:27:35 konstrukt click[21997]:   from gi.repository import Click
  Nov 28 16:27:35 konstrukt click[21997]: hooks.vala:1216: User-level hook 
push-helper failed: Hook command 
'/usr/lib/ubuntu-push-client/click-hook-wrapper' failed: Child process exited 
with code 1
  Nov 28 16:27:35 konstrukt click[21997]: Some user-level hooks failed: 
push-helper
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Main 
process exited, code=exited, status=1/FAILURE
  Nov 28 16:27:35 konstrukt systemd[21965]: Failed to start Run Click 
user-level hooks.
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Unit 
entered failed state.
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Failed 
with result 'exit-code'.
  Nov 28 16:27:35 konstrukt systemd[21965]: Reached target Default. 
  Nov 28 16:27:35 konstrukt systemd[21965]: Startup finished in 497ms.
  Nov 28 16:27:35 konstrukt systemd[1]: Started User Manager for UID 0.
  Nov 28 16:27:35 konstrukt schroot[22084]:

[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

2016-11-28 Thread Jim Hodapp

@Robin: Yeah I've been able to get mine working as well. Were you trying
with Ubuntu desktop or on Ubuntu Touch? The choppiness seems to be bluez
doing other device scans. So on Touch, if you make sure that system
settings is in the background, it should remain nearly chop-free. On the
desktop, it stopped scanning if I closed system settings and then got a
lot better quality.

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

Title:
  Fails to pair with Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+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 1645372] Re: support display scaling slider in unity8

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

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

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

Title:
  support display scaling slider in unity8

Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  We need to be able to scale the display in unity8, via ubuntu-system-
  settings Display->Scaling slider. This will need backend support in
  Mir and unity8, filing this bug to track.

  Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1645372/+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 1645372] Re: support display scaling slider in unity8

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

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

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

Title:
  support display scaling slider in unity8

Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  We need to be able to scale the display in unity8, via ubuntu-system-
  settings Display->Scaling slider. This will need backend support in
  Mir and unity8, filing this bug to track.

  Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1645372/+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 1645372] Re: support display scaling slider in unity8

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

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

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

Title:
  support display scaling slider in unity8

Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  We need to be able to scale the display in unity8, via ubuntu-system-
  settings Display->Scaling slider. This will need backend support in
  Mir and unity8, filing this bug to track.

  Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1645372/+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 1645372] Re: support display scaling slider in unity8

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

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

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

Title:
  support display scaling slider in unity8

Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  We need to be able to scale the display in unity8, via ubuntu-system-
  settings Display->Scaling slider. This will need backend support in
  Mir and unity8, filing this bug to track.

  Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1645372/+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 1645375] [NEW] Xorg freeze when starting chromium-browser

2016-11-28 Thread Richard

Public bug reported:

I get messages like the following in the journal:

kernel: nouveau :0a:00.0: fifo: CACHE_ERROR - ch 7 [chromium-
browse[6657]] subc 3 mthd 15ec data 


I can still SSH in.

Chromium Version 53.0.2785.143 Built on Ubuntu , running on Ubuntu 16.10
(64-bit)

lsb_release -rd:

  Description:  Ubuntu 16.10
  Release:  16.10

apt-cache policy xserver-xorg-video-nouveau:

xserver-xorg-video-nouveau:
  Installed: 1:1.0.12-2
  Candidate: 1:1.0.12-2
  Version table:
 *** 1:1.0.12-2 500
500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
100 /var/lib/dpkg/status

What you expected to happen:

  Chrome Browser window to open.

What happened instead:

  Outline of Chrome Browser window appeared and then Xorg froze. Mouse
point could be moved on one display but between displays. Nothing was
responsive on the UI.

Running Chromium with:

chromium-browser -gpu

works and does not freeze.

Regards

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Nov 28 15:49:47 2016
DistUpgraded: 2016-10-19 16:07:29,098 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.6, 4.8.0-26-generic, x86_64: installed
 virtualbox, 5.1.6, 4.8.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: This is the first time
GraphicsCard:
 NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company GT218 [NVS 300] [103c:0862]
InstallationDate: Installed on 2016-01-05 (327 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
MachineType: Dell Inc. PowerEdge T320
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-27-generic 
root=UUID=0f94436a-b93a-4750-b0f1-08be2c4b2188 ro rootflags=subvol=@
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to yakkety on 2016-10-19 (40 days ago)
dmi.bios.date: 01/29/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.2
dmi.board.name: 0FDT3J
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 17
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.2:bd01/29/2015:svnDellInc.:pnPowerEdgeT320:pvr:rvnDellInc.:rn0FDT3J:rvrA02:cvnDellInc.:ct17:cvr:
dmi.product.name: PowerEdge T320
dmi.sys.vendor: Dell Inc.
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.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Mon Nov 28 15:43:48 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu yakkety

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

Title:
  Xorg freeze when starting chromium-browser

Status in xorg package in Ubuntu:
  New

Bug description:
  I get messages like the following in the journal:

  kernel: nouveau :0a:00.0: fifo: CACHE_ERROR - ch 7 [chromium-
  browse[6657]] subc 3 mthd 15ec data 

  
  I can still SSH in.

  Chromium Version 53.0.2785.143 Built on Ubuntu , running on Ubuntu
  16.10 (64-bit)

  lsb_release -rd:

Description:Ubuntu 16.10
Release:16.10

  apt-cache policy xserver-xorg-video-nouveau:

  xserver-xorg-video-nouveau:
Installed: 1:1.0.12-2
Candidate: 1:1.0.12-2
Version table:
   *** 1:1.0.12-2 500
  500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  What you expected to

[Touch-packages] [Bug 1645372] [NEW] support display scaling slider in unity8

2016-11-28 Thread Bill Filler

Public bug reported:

We need to be able to scale the display in unity8, via ubuntu-system-
settings Display->Scaling slider. This will need backend support in Mir
and unity8, filing this bug to track.

Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

** Affects: mir (Ubuntu)
 Importance: High
 Status: New

** Affects: qtmir (Ubuntu)
 Importance: High
 Status: New

** Affects: ubuntu-system-settings (Ubuntu)
 Importance: High
 Assignee: Jonas G. Drange (jonas-drange)
 Status: New

** Affects: unity8 (Ubuntu)
 Importance: High
 Status: New

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

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

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

** Changed in: ubuntu-system-settings (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: (unassigned) => Jonas G. Drange (jonas-drange)

** Changed in: mir (Ubuntu)
   Importance: Undecided => High

** Changed in: qtmir (Ubuntu)
   Importance: Undecided => High

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => High

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

Title:
  support display scaling slider in unity8

Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  We need to be able to scale the display in unity8, via ubuntu-system-
  settings Display->Scaling slider. This will need backend support in
  Mir and unity8, filing this bug to track.

  Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1645372/+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 1645363] Re: slow sbuild Debian package builds (schroot calls are slow)

2016-11-28 Thread Martin Pitt

At least for me the reason was bug 1626436. Can you try the test kernel
there and see if that helps?

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

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

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

Title:
  slow sbuild Debian package builds (schroot calls are slow)

Status in sbuild package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade to Ubuntu 16.10, building packages with sbuild takes
  much more time than previously. sbuild creates a schroot session for
  building Debian packages and calls sbuild --run-session several times.
  Entering the sessions takes norally 10 ms, but entering the session
  from sbuild takes several seconds now:

  time schroot -d / -c $session --run-session -q -u root -p -- true
  real0m2.098s
  user0m0.008s
  sys 0m0.000s

  This causes a drastic build time increase for small packages. Example
  package build time on my affected Ubuntu workstation:

  Build-Time: 9 s
  Install-Time: 115 s
  Package-Time: 195 s (= 00:03:15)

  compared to the build bot running Debian stable (having a slower
  processor):

  Build-Time: 9 s
  Install-Time: 24 s
  Package-Time: 41 s

  /var/log/syslog shows many entries about starting and stopping D-Bus
  services:

  Nov 28 16:27:34 konstrukt systemd[1]: Created slice User Slice of root.
  Nov 28 16:27:34 konstrukt systemd[1]: Starting User Manager for UID 0...
  Nov 28 16:27:34 konstrukt systemd[1]: Started Session 2 of user root.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Timers.
  Nov 28 16:27:34 konstrukt systemd[21965]: Starting D-Bus User Message Bus 
Socket.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Paths.
  Nov 28 16:27:34 konstrukt systemd[21965]: Listening on D-Bus User Message Bus 
Socket.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Sockets.
  Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Basic System.
  Nov 28 16:27:34 konstrukt systemd[21965]: Starting Run Click user-level 
hooks...
  Nov 28 16:27:34 konstrukt systemd[21965]: Started D-Bus User Message Bus.
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Error parsing manifest for 
package 'com.ubuntu.gallery': com.ubuntu.gallery does not exist in any database 
for user root
  Nov 28 16:27:34 konstrukt /usr/lib/snapd/snapd[1086]: daemon.go:174: DEBUG: 
uid=0;@ GET /v2/snaps/com.ubuntu.gallery 40.327µs 404
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Unable to get snap 
information for 'com.ubuntu.gallery': Status code is: 404
  Nov 28 16:27:34 konstrukt dbus-daemon[22004]: Activating service 
name='ca.desrt.dconf'
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Error parsing manifest for 
package 'com.ubuntu.gallery': com.ubuntu.gallery does not exist in any database 
for user root
  Nov 28 16:27:34 konstrukt /usr/lib/snapd/snapd[1086]: daemon.go:174: DEBUG: 
uid=0;@ GET /v2/snaps/com.ubuntu.gallery 23.455µs 404
  Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Unable to get snap 
information for 'com.ubuntu.gallery': Status code is: 404
  Nov 28 16:27:34 konstrukt dbus-daemon[22004]: Successfully activated service 
'ca.desrt.dconf'
  Nov 28 16:27:35 konstrukt dbus-daemon[22004]: Activating via systemd: service 
name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
  Nov 28 16:27:35 konstrukt systemd[21965]: Starting Virtual filesystem 
service...
  Nov 28 16:27:35 konstrukt dbus-daemon[22004]: Successfully activated service 
'org.gtk.vfs.Daemon'
  Nov 28 16:27:35 konstrukt systemd[21965]: Started Virtual filesystem service.
  Nov 28 16:27:35 konstrukt click[21997]: 
/usr/lib/ubuntu-push-client/click-hook:15: PyGIWarning: Click was imported 
without specifying a version first. Use gi.require_version('Click', '0.4') 
before import to ensure that the right version gets loaded.
  Nov 28 16:27:35 konstrukt click[21997]:   from gi.repository import Click
  Nov 28 16:27:35 konstrukt click[21997]: hooks.vala:1216: User-level hook 
push-helper failed: Hook command 
'/usr/lib/ubuntu-push-client/click-hook-wrapper' failed: Child process exited 
with code 1
  Nov 28 16:27:35 konstrukt click[21997]: Some user-level hooks failed: 
push-helper
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Main 
process exited, code=exited, status=1/FAILURE
  Nov 28 16:27:35 konstrukt systemd[21965]: Failed to start Run Click 
user-level hooks.
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Unit 
entered failed state.
  Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Failed 
with result 'exit-code'.
  Nov 28 16:27:35 konstrukt systemd[21965]: Reached target Default. 
  Nov 28 16:27:35 konstrukt systemd[21965]: Startup finished in 497ms.
  Nov 28 16:27:35 konstrukt systemd[1]: Started User

[Touch-packages] [Bug 1645362] Re: Calculator example is broken

** Tags added: examples snap

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

Title:
  Calculator example is broken

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  When I start the calculator example, I only see a header with
  'Calculator' as the title, and a '0' as a result for calculations, but
  there is no input field where I can enter new calculations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1645362/+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 1645365] [NEW] customtheme example broken in the deb package

Public bug reported:

The theme/ directory that contains the custom theme is missing.

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


** Tags: examples snap

** Tags added: examples snap

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

Title:
  customtheme example broken in the deb package

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  The theme/ directory that contains the custom theme is missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1645365/+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 1645363] [NEW] slow sbuild Debian package builds (schroot calls are slow)

2016-11-28 Thread Benjamin Drung

Public bug reported:

Since the upgrade to Ubuntu 16.10, building packages with sbuild takes
much more time than previously. sbuild creates a schroot session for
building Debian packages and calls sbuild --run-session several times.
Entering the sessions takes norally 10 ms, but entering the session from
sbuild takes several seconds now:

time schroot -d / -c $session --run-session -q -u root -p -- true
real0m2.098s
user0m0.008s
sys 0m0.000s

This causes a drastic build time increase for small packages. Example
package build time on my affected Ubuntu workstation:

Build-Time: 9 s
Install-Time: 115 s
Package-Time: 195 s (= 00:03:15)

compared to the build bot running Debian stable (having a slower
processor):

Build-Time: 9 s
Install-Time: 24 s
Package-Time: 41 s

/var/log/syslog shows many entries about starting and stopping D-Bus
services:

Nov 28 16:27:34 konstrukt systemd[1]: Created slice User Slice of root.
Nov 28 16:27:34 konstrukt systemd[1]: Starting User Manager for UID 0...
Nov 28 16:27:34 konstrukt systemd[1]: Started Session 2 of user root.
Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Timers.
Nov 28 16:27:34 konstrukt systemd[21965]: Starting D-Bus User Message Bus 
Socket.
Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Paths.
Nov 28 16:27:34 konstrukt systemd[21965]: Listening on D-Bus User Message Bus 
Socket.
Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Sockets.
Nov 28 16:27:34 konstrukt systemd[21965]: Reached target Basic System.
Nov 28 16:27:34 konstrukt systemd[21965]: Starting Run Click user-level hooks...
Nov 28 16:27:34 konstrukt systemd[21965]: Started D-Bus User Message Bus.
Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Error parsing manifest for 
package 'com.ubuntu.gallery': com.ubuntu.gallery does not exist in any database 
for user root
Nov 28 16:27:34 konstrukt /usr/lib/snapd/snapd[1086]: daemon.go:174: DEBUG: 
uid=0;@ GET /v2/snaps/com.ubuntu.gallery 40.327µs 404
Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Unable to get snap 
information for 'com.ubuntu.gallery': Status code is: 404
Nov 28 16:27:34 konstrukt dbus-daemon[22004]: Activating service 
name='ca.desrt.dconf'
Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Error parsing manifest for 
package 'com.ubuntu.gallery': com.ubuntu.gallery does not exist in any database 
for user root
Nov 28 16:27:34 konstrukt /usr/lib/snapd/snapd[1086]: daemon.go:174: DEBUG: 
uid=0;@ GET /v2/snaps/com.ubuntu.gallery 23.455µs 404
Nov 28 16:27:34 konstrukt content-hub-pee[22023]: Unable to get snap 
information for 'com.ubuntu.gallery': Status code is: 404
Nov 28 16:27:34 konstrukt dbus-daemon[22004]: Successfully activated service 
'ca.desrt.dconf'
Nov 28 16:27:35 konstrukt dbus-daemon[22004]: Activating via systemd: service 
name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
Nov 28 16:27:35 konstrukt systemd[21965]: Starting Virtual filesystem service...
Nov 28 16:27:35 konstrukt dbus-daemon[22004]: Successfully activated service 
'org.gtk.vfs.Daemon'
Nov 28 16:27:35 konstrukt systemd[21965]: Started Virtual filesystem service.
Nov 28 16:27:35 konstrukt click[21997]: 
/usr/lib/ubuntu-push-client/click-hook:15: PyGIWarning: Click was imported 
without specifying a version first. Use gi.require_version('Click', '0.4') 
before import to ensure that the right version gets loaded.
Nov 28 16:27:35 konstrukt click[21997]:   from gi.repository import Click
Nov 28 16:27:35 konstrukt click[21997]: hooks.vala:1216: User-level hook 
push-helper failed: Hook command 
'/usr/lib/ubuntu-push-client/click-hook-wrapper' failed: Child process exited 
with code 1
Nov 28 16:27:35 konstrukt click[21997]: Some user-level hooks failed: 
push-helper
Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Main 
process exited, code=exited, status=1/FAILURE
Nov 28 16:27:35 konstrukt systemd[21965]: Failed to start Run Click user-level 
hooks.
Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Unit 
entered failed state.
Nov 28 16:27:35 konstrukt systemd[21965]: click-user-hooks.service: Failed with 
result 'exit-code'.
Nov 28 16:27:35 konstrukt systemd[21965]: Reached target Default. 
Nov 28 16:27:35 konstrukt systemd[21965]: Startup finished in 497ms.
Nov 28 16:27:35 konstrukt systemd[1]: Started User Manager for UID 0.
Nov 28 16:27:35 konstrukt schroot[22084]: 
[pb-jessie-93c04c41-79af-4e32-addb-09a186998122 chroot] (bdrung->root) Running 
command: "getent group sbuild"
Nov 28 16:27:35 konstrukt systemd[1]: Stopping User Manager for UID 0...
Nov 28 16:27:35 konstrukt systemd[21965]: Stopping D-Bus User Message Bus...
Nov 28 16:27:35 konstrukt systemd[21965]: Stopped target Default.
Nov 28 16:27:35 konstrukt systemd[21965]: Stopping Virtual filesystem service...
Nov 28 16:27:35 konstrukt systemd[21965]: Stopped D-Bus User Message Bus.
Nov 28 16:27:35 konstrukt systemd[1]: Started Session 2 of user root.
Nov 28 16:27:36 konstrukt systemd[21965]: Stopped Virtual filesystem

[Touch-packages] [Bug 1645362] [NEW] Calculator example is broken