Re: [Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[Luke Yelavich]

Ok, could you again get a log from PulseAudio as per
https://wiki.ubuntu.com/PulseAudio/Log.

Thanks.

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3
Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29 
  Device 44:5E:F3:B4:07:29
Name: BlueBuds X
Alias: BlueBuds X
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

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

[Touch-packages] [Bug 1606501] Re: initial app surface size wrong

[Emanuele Antonio Faraone]

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

I've the same problem

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

Title:
  initial app surface size wrong

Status in Canonical System Image:
  Confirmed
Status in QtMir:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 16.10 - unity8.13+16.10.20160714+fix1-0ubuntu2~1

  initial app surface size wrong
  i don't know how to better describe this bug, PLEASE see the attached 
screenshot

  note: if you resize the windows the app recovers and scales fine
  however if you reopen the app you get the same bug

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

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

[Touch-packages] [Bug 1441253] Re: hanging suspend job prevents shutdown

[berend]

Same here, also system76 laptop. I think I get it after a failed
suspend. I.e. close laptop lid, and it won't suspend. When I open the
lid again, I have no network. Then I can't reboot. Factors that may
impact is that I have nfs directories mounted (using autofs, so
hopefully not mounted), and a bluetooth headset.

I noticed that when typing "sync" the terminal hangs.

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

Title:
  hanging suspend job prevents shutdown

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  poweroff (systemd poweroff) and reboot no longer work

  running sudo sytemd poweroff generates this:

  Failed to start poweroff.target: Transaction is destructive.

  journal log also shows:

  Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Registered 
Authentication Agent for unix-process:32412:2895609 (system bus name :1.194 
[/usr/bin/pkttyagent --notify-fd 5 --fallback], object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
  Apr 07 18:30:12 alice systemd[1]: Requested transaction contradicts existing 
jobs: Transaction is destructive.
  Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Unregistered 
Authentication Agent for unix-process:32412:2895609 (system bus name :1.194, 
object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale 
en_US.UTF-8) (disconnected from bus)

  
  Output of systemctl list-jobs
   JOB UNITTYPE  STATE  
  6009 suspend.target  start waiting
  6010 systemd-suspend.service start running
  6014 anacron-resume.service  start waiting

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  Date: Tue Apr  7 18:32:27 2015
  MachineType: Hewlett-Packard HP EliteBook 8560w
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-12-generic 
root=UUID=90fa42f5-708d-4432-9241-315b9c08ba98 ro nomodeset rootflags=subvol=@
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to vivid on 2015-03-02 (36 days ago)
  dmi.bios.date: 08/04/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.50
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.3D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8560w
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1620496] [NEW] Calendar widget gets confused with October

[Michał Sawicz]

Public bug reported:

I can see two October 30ths on my phone, see attachment.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: qml-module-ubuntu-settings-components 0.9+15.04.20160818.1-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.17.2-0ubuntu1.3touch1
Architecture: armhf
Date: Tue Sep  6 09:24:34 2016
InstallationDate: Installed on 2016-09-03 (3 days ago)
InstallationMedia: Ubuntu 15.04 - armhf (20160903-020304)
SourcePackage: ubuntu-settings-components
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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


** Tags: apport-bug armhf vivid

** Attachment added: "screenshot20160906_092448645.png"
   
https://bugs.launchpad.net/bugs/1620496/+attachment/4735305/+files/screenshot20160906_092448645.png

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  Calendar widget gets confused with October

Status in Canonical System Image:
  New
Status in ubuntu-settings-components package in Ubuntu:
  New

Bug description:
  I can see two October 30ths on my phone, see attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: qml-module-ubuntu-settings-components 0.9+15.04.20160818.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Tue Sep  6 09:24:34 2016
  InstallationDate: Installed on 2016-09-03 (3 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160903-020304)
  SourcePackage: ubuntu-settings-components
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1535335] Re: [App permissions] Change prompt "wants to record audio" to "wants to access microphone"

[Matthew Paul Thomas]

This is not a design bug: the design already specifies that the text is
supposed to be “wants to use the microphone”.


** No longer affects: ubuntu-ux

** Summary changed:

- [App permissions] Change prompt "wants to record audio" to "wants to access 
microphone"
+ [App permissions] Change prompt "wants to record audio" to "wants to use the 
microphone"

** Description changed:

  The prompt when the camera wants to access the hardware to record audio
  is currently "wants to record audio". This is not really accurate since
  an app can request access to the microphone without actually recording
  anything. furthermore the direct translation to French as an example is
  not really meaningful.
  
- 
- Something like "wants to access the microphone." would be more accurate since 
it's actually what the application requests access to.
- 
  "Microphone" is also consistent with the word used in system-
  settings/security & privacy/app permissions
+ 
+ : “Prompt text
+ … wants to use the microphone”

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

** Tags added: string-fix

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

Title:
  [App permissions] Change prompt "wants to record audio" to "wants to
  use the microphone"

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  The prompt when the camera wants to access the hardware to record
  audio is currently "wants to record audio". This is not really
  accurate since an app can request access to the microphone without
  actually recording anything. furthermore the direct translation to
  French as an example is not really meaningful.

  "Microphone" is also consistent with the word used in system-
  settings/security & privacy/app permissions

  : “Prompt
  text … wants to use the microphone”

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

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

[Touch-packages] [Bug 1502173] Re: Python warnings: modules imported without specifying a version first

[anatoly techtonik]

Thanks Numan for the patch. Inline text helped me gain inspiration to
get into launchpad patch submission process -
https://askubuntu.com/questions/372654/how-do-i-submit-a-patch-to-a
-launchpad-project

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

Title:
  Python warnings: modules imported without specifying a version first

Status in apport package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  here is the problem:

  $ /usr/share/apport/apport-gtk
  /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
  /usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without 
specifying a version first. Use gi.require_version('GdkX11', '3.0') before 
import to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: apport-gtk 2.19-0ubuntu1
  Uname: Linux 4.2.2-040202-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Oct  2 16:17:14 2015
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to wily on 2015-10-02 (0 days ago)

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

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

[Touch-packages] [Bug 1620496] Re: Calendar widget gets confused with October

[Jean-Baptiste Lallement]

same in october 2017 (29th is duplicated) but not Oct 2014,2015 and
2018.

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

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

** Changed in: canonical-devices-system-image
Milestone: None => 14

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

Title:
  Calendar widget gets confused with October

Status in Canonical System Image:
  Confirmed
Status in ubuntu-settings-components package in Ubuntu:
  New

Bug description:
  I can see two October 30ths on my phone, see attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: qml-module-ubuntu-settings-components 0.9+15.04.20160818.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Tue Sep  6 09:24:34 2016
  InstallationDate: Installed on 2016-09-03 (3 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160903-020304)
  SourcePackage: ubuntu-settings-components
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1620495] Re: unity8 crashed with SIGSEGV in qtmir::ApplicationManager::updateFocusedApplication()

[Daniel van Vugt]

** Information type changed from Private to Public

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

Title:
  unity8 crashed with SIGSEGV in
  qtmir::ApplicationManager::updateFocusedApplication()

Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  After using unity8 in my laptop and test some password changes and
  work normally with it I log out unity8 and entered unity7, the auto
  bug report appeared.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160826-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Sep  6 08:43:59 2016
  Disassembly: => 0xa:  Cannot access memory at address 0xa
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2016-08-10 (27 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20160806)
  ProcCmdline: unity8 --mode=full-shell
  SegvAnalysis:
   Segfault happened at: 0xa:   Cannot access memory at address 
0xa
   PC (0xa) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? ()
   qtmir::ApplicationManager::updateFocusedApplication() () from 
/usr/lib/x86_64-linux-gnu/qt5/qml/Unity/Application/libunityapplicationplugin.so
   QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QCoreApplication::notifyInternal2(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? ()
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: unity8 crashed with SIGSEGV in 
qtmir::ApplicationManager::updateFocusedApplication()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1620192] [NEW] Sound over HDMI is 2x as slow after resuming from standby

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have an extremely frustrating problem with Ubuntu 16.04.1 LTS 64-bits
on my Dell E7450 laptop: when I connect a TV over HDMI afater resuming
from standby, the sound is 2x as slow, and everything else, e.g. video
playback, is dragged down to slow-motion.

For example, testing audio via Speaker Testing goes "Frooont Leeeft" in
a low-pitch male voice (the normal is a crisp "Front Left" in a female
voice").

Reproduction steps:

1. Connect laptop to TV over HDMI cable
2. Go to All Settings -> Sound and select to "Play sound through" 
HDMI/DisplayPort audio
3. Play a video and ensure the playback is at normal speed and the sound comes 
out of the TV.
4. Suspend the laptop.
5. Resume the laptop.
6. Play the same video again.

Actual results: the sound and video look slow-motion, at about 50%
speed. Go to Test Sound, and Front Left will sound like "Frooont
Leeeft".

This is super annoying because I have to close all my applications and
reboot every time I want to watch a movie through my TV.

Asked at http://askubuntu.com/questions/805355/sound-over-hdmi-is-2x-as-
slow-after-resuming-from-standby, no luck.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Sep  4 22:31:04 2016
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2016-09-04 (1 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: unity-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial
-- 
Sound over HDMI is 2x as slow after resuming from standby
https://bugs.launchpad.net/bugs/1620192
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio 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 1619593] Re: pkcon Fatal ERROR: MIME type not supported. when installing clicks in unity8 on a laptop

[Michał Sawicz]

** Also 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/1619593

Title:
  pkcon Fatal ERROR: MIME type not supported. when installing clicks in
  unity8 on a laptop

Status in click package in Ubuntu:
  New
Status in packagekit package in Ubuntu:
  New

Bug description:
  A week ago I had no problem to install
  clicks(filemanager,music,terminal) but this week I came across with
  this pkcon error. Could it be caused by a packagekit update?

  Enviroment: Desktop running unity8 on 16.10
  HW: intel graphics+intel processor

  Preconditions: download some clicks of core/non core apps to install

  Steps to reproduce:

  1º Open terminal and run $ pkon install-local --allow-untrusted /path

  Current result: pkcon command returns the error given at the bottom

  Expected result: pkcon command should run with out any issue and
  clicks should be installed

  Reproducibility 100%

  -
  output

  11:59:57PackageKit  Verbose debugging enabled (on console 1)
  11:59:57PackageKit  filter=(null), filters=0
  11:59:57PackageKit  adding state 0x562f87db10d0
  11:59:57PackageKit  doing install files
  11:59:57PackageKit  role now install-files
  Installing files  [=] :59:57  
  PackageKit  using frontend diaFinished  
[=] :59:57PackageKit  remove 
state 0x562Fatal error: MIME type 'application/x-click' not supported 
/home/users/Downloads/com.ubuntu.calendar_0.4.757_all.click

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

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

[Touch-packages] [Bug 1620192] Re: Sound over HDMI is 2x as slow after resuming from standby

[Sebastien Bacher]

** Package changed: unity-control-center (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  Sound over HDMI is 2x as slow after resuming from standby

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have an extremely frustrating problem with Ubuntu 16.04.1 LTS
  64-bits on my Dell E7450 laptop: when I connect a TV over HDMI afater
  resuming from standby, the sound is 2x as slow, and everything else,
  e.g. video playback, is dragged down to slow-motion.

  For example, testing audio via Speaker Testing goes "Frooont Leeeft"
  in a low-pitch male voice (the normal is a crisp "Front Left" in a
  female voice").

  Reproduction steps:

  1. Connect laptop to TV over HDMI cable
  2. Go to All Settings -> Sound and select to "Play sound through" 
HDMI/DisplayPort audio
  3. Play a video and ensure the playback is at normal speed and the sound 
comes out of the TV.
  4. Suspend the laptop.
  5. Resume the laptop.
  6. Play the same video again.

  Actual results: the sound and video look slow-motion, at about 50%
  speed. Go to Test Sound, and Front Left will sound like "Frooont
  Leeeft".

  This is super annoying because I have to close all my applications and
  reboot every time I want to watch a movie through my TV.

  Asked at http://askubuntu.com/questions/805355/sound-over-hdmi-is-2x-
  as-slow-after-resuming-from-standby, no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep  4 22:31:04 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-09-04 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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/pulseaudio/+bug/1620192/+subscriptions

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

[Touch-packages] [Bug 1620380] Re: software-properties-gtk crashed with IndexError in list(): list index out of range

[Sebastien Bacher]

** Information type changed from Private to Public

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

Title:
  software-properties-gtk crashed with IndexError in list(): list index
  out of range

Status in software-properties package in Ubuntu:
  New

Bug description:
  Not sure what happened

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: software-properties-gtk 0.96.24.4
  Uname: Linux 4.8.0-rc4-haswell x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Mon Sep  5 18:14:59 2016
  ExecutablePath: /usr/bin/software-properties-gtk
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk -n -t 49190
  PythonArgs: ['/usr/bin/software-properties-gtk', '-n', '-t', '49190']
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with IndexError in list(): list index 
out of range
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1616422] Re: [trusty SRU/FFE] Add systemd binary package for snapd

[Martin Pitt]

Status update:

> linked units from /etc/systemd/system are still being read. This needs
a bigger hammer.

Fixed in git.

> reboot is hanging

This was due to /lib/lsb/init-functions.d/40-systemd which diverted SysV
init scripts to systemctl which then ignored those as we want to disable
SysV support for deputy systemd. Fixed in git.

> I haven't tested dist-upgrade to 16.04 yet.

Done now. It mostly works except for a two-minute hang in grub-
common.postinst when trying to start grub-common.service. This gets into
a deadlock due to the LSB hook reappearing while the deputy systemd is
still running, and after the timeout grub-common is in a failed state.
What works is to manually do "sudo initctl stop systemd; sudo rm -r
/run/systemd/system; sudo apt-get -f install". After the dist-upgrade
you need to run "sudo reboot -f".

I updated https://launchpad.net/~pitti/+archive/ubuntu/systemd to
systemd 204-5ubuntu20.19pitti3 with the recent fixes, and this should
now work reasonably well except for upgrades. Please test with snapd!

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

Title:
  [trusty SRU/FFE] Add systemd binary package for snapd

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Trusty:
  In Progress

Bug description:
  Rationale: For backporting snapd to 14.04 LTS, we need to provide
  systemd's service manager (not just logind and auxiliary services like
  logind or timesyncd). upstart will continue to do the actual booting,
  and systemd will act as a "deputy init" which by default does not ship
  with/start any services by itself. We will only support this on server
  (at the first iteration at least), not on desktops.

  Regression potential: This is a new binary package in universe, so
  existing systems are unaffected (provided that we ensure that the
  other binary packages do not change and there are no code changes that
  affect processes other than the "deputy pid 1" service manager). So
  for plain upgrades the regression potential is very low. However,
  there is a medium potential for breakage when actually installing the
  new systemd package, as it might interfere with upstart jobs or other
  running processes, cause boot/shutdown hangs, etc.

  Test plan:
   1. Dist-upgrade a trusty installation to the proposed versions. Ensure this 
does not pull in "systemd", and that booting, shutdown, desktop startup, 
suspend on lid close, resume, logout, and user switching all still work.

   2. Install the "systemd" binary package (this will replace/remove
  systemd-shim). Verify that you can talk to the service manager with
  "sudo systemctl status". Check that booting and shutdown continues to
  work without (significant) delays.

   3. Ensure that "sudo journalctl" works and that "sudo systemctl
  status systemd-journald" is running and has a few lines of log at the
  end (unlike what you get when you run systemctl as user).

   4. Install a package that ships a systemd .service file, such as
  "haveged". Ensure that the service file is ignored, "pgrep -af
  haveged" should only have *one* process and "systemctl status haveged"
  should not be running (it should not exist, or not be enabled and be
  inactive).

     The only services that are running are expected to be systemd-
  journald.service and systemd-journald.socket.

   5. Ensure that the standard targets are active, as that is where
  third-party/snap services hook into:

  systemctl status sysinit.target multi-user.target default.target

   6. Install snapd (not in trusty yet, e. g. from Thomas' PPA) and
  ensure you can install a snap, and its services start after installing
  the snap and after rebooting.

   7. Run "sudo apt-get install --reinstall systemd" to ensure that
  upgrades to newer systemd trusty versions work.

   8. Dist-upgrade to 16.04 to ensure that there are no file conflicts,
  dependency issues, etc.

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

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

[Touch-packages] [Bug 1585996] Re: UITK gallery: can't open subpages on Qt 5.6 because of TypeError

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui-
toolkit/incubateAPLinternals

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

Title:
  UITK gallery: can't open subpages on Qt 5.6 because of TypeError

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  On Qt 5.6 I can't seem to be able to open subpages in UITK Gallery
  (installed from Store). In logs I have:

  qml: sourcePage must be added to the view to add new page.

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

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

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

[Touch-packages] [Bug 1616422] Re: [trusty SRU/FFE] Add systemd binary package for snapd

[Martin Pitt]

** Description changed:

  Rationale: For backporting snapd to 14.04 LTS, we need to provide
  systemd's service manager (not just logind and auxiliary services like
  logind or timesyncd). upstart will continue to do the actual booting,
  and systemd will act as a "deputy init" which by default does not ship
  with/start any services by itself. We will only support this on server
  (at the first iteration at least), not on desktops.
  
  Regression potential: This is a new binary package in universe, so
  existing systems are unaffected (provided that we ensure that the other
  binary packages do not change and there are no code changes that affect
  processes other than the "deputy pid 1" service manager). So for plain
  upgrades the regression potential is very low. However, there is a
  medium potential for breakage when actually installing the new systemd
  package, as it might interfere with upstart jobs or other running
  processes, cause boot/shutdown hangs, etc.
  
  Test plan:
   1. Dist-upgrade a trusty installation to the proposed versions. Ensure this 
does not pull in "systemd", and that booting, shutdown, desktop startup, 
suspend on lid close, resume, logout, and user switching all still work.
  
   2. Install the "systemd" binary package (this will replace/remove
  systemd-shim). Verify that you can talk to the service manager with
  "sudo systemctl status". Check that booting and shutdown continues to
  work without (significant) delays.
  
   3. Ensure that "sudo journalctl" works and that "sudo systemctl status
  systemd-journald" is running and has a few lines of log at the end
  (unlike what you get when you run systemctl as user).
  
   4. Install a package that ships a systemd .service file, such as
  "haveged". Ensure that the service file is ignored, "pgrep -af haveged"
  should only have *one* process and "systemctl status haveged" should not
  be running (it should not exist, or not be enabled and be inactive).
  
     The only services that are running are expected to be systemd-
  journald.service and systemd-journald.socket.
  
-  5. Ensure that the standard targets are active, as that is where third-
+  5. Ensure that the standard targets are active, as that is where third-
  party/snap services hook into:
  
- systemctl status sysinit.target multi-user.target default.target
+ systemctl status sysinit.target multi-user.target default.target
  
   6. Install snapd (not in trusty yet, e. g. from Thomas' PPA) and ensure
  you can install a snap, and its services start after installing the snap
  and after rebooting.
  
-  7. Dist-upgrade to 16.04 to ensure that there are no file conflicts,
+  7. Run "sudo apt-get install --reinstall systemd" to ensure that
+ upgrades to newer systemd trusty versions work.
+ 
+  8. Dist-upgrade to 16.04 to ensure that there are no file conflicts,
  dependency issues, etc.

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

Title:
  [trusty SRU/FFE] Add systemd binary package for snapd

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Trusty:
  In Progress

Bug description:
  Rationale: For backporting snapd to 14.04 LTS, we need to provide
  systemd's service manager (not just logind and auxiliary services like
  logind or timesyncd). upstart will continue to do the actual booting,
  and systemd will act as a "deputy init" which by default does not ship
  with/start any services by itself. We will only support this on server
  (at the first iteration at least), not on desktops.

  Regression potential: This is a new binary package in universe, so
  existing systems are unaffected (provided that we ensure that the
  other binary packages do not change and there are no code changes that
  affect processes other than the "deputy pid 1" service manager). So
  for plain upgrades the regression potential is very low. However,
  there is a medium potential for breakage when actually installing the
  new systemd package, as it might interfere with upstart jobs or other
  running processes, cause boot/shutdown hangs, etc.

  Test plan:
   1. Dist-upgrade a trusty installation to the proposed versions. Ensure this 
does not pull in "systemd", and that booting, shutdown, desktop startup, 
suspend on lid close, resume, logout, and user switching all still work.

   2. Install the "systemd" binary package (this will replace/remove
  systemd-shim). Verify that you can talk to the service manager with
  "sudo systemctl status". Check that booting and shutdown continues to
  work without (significant) delays.

   3. Ensure that "sudo journalctl" works and that "sudo systemctl
  status systemd-journald" is running and has a few lines of log at the
  end (unlike what you get when you run systemctl as user).

   4. Install a package that ships a systemd .service file, such as
  "haveged". Ensure 

[Touch-packages] [Bug 1620297] Re: First scope not rendered until unlocked

[Launchpad Bug Tracker]

** Branch linked: lp:~saviq/qtubuntu/revert-occlude-lp1620297

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

Title:
  First scope not rendered until unlocked

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

Bug description:
  The pre-populating of first scope on startup (before the screen is
  unlocked) doesn't seem to be fully working.

  My early investigation shows that the shell plugin correctly pre-
  populates scope model on startup when the screen is still locked, but
  after unlocking scope view is white for 1-2 seconds and only then the
  page is rendered and all the images are requested, so the perception
  is as if pre-population didn't work. The perceived performance depends
  on whether the 1st scope is a local scope (such as Apps) or a scope
  which needs remote images (and whether the images are already cached
  by the thumbnailer in the latter case).

  This might be caused by https://bugs.launchpad.net/qtmir/+bug/1475678

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

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

[Touch-packages] [Bug 1619593] Re: pkcon Fatal ERROR: MIME type not supported. when installing clicks in unity8 on a laptop

[Michał Sawicz]

I'm afraid support for clicks was dropped in Y, we're working on
replacing them with snaps in this release.

The problem is that packagekit 1.0 doesn't allow plugins any more, so
the plugin was dropped in yakkety.

See
https://launchpad.net/ubuntu/+source/click/0.4.44+16.10.20160809.1-0ubuntu1
for the relevant changelog entry.

** Changed in: click (Ubuntu)
   Status: New => Won't Fix

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

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

Title:
  pkcon Fatal ERROR: MIME type not supported. when installing clicks in
  unity8 on a laptop

Status in click package in Ubuntu:
  Won't Fix
Status in packagekit package in Ubuntu:
  Invalid

Bug description:
  A week ago I had no problem to install
  clicks(filemanager,music,terminal) but this week I came across with
  this pkcon error. Could it be caused by a packagekit update?

  Enviroment: Desktop running unity8 on 16.10
  HW: intel graphics+intel processor

  Preconditions: download some clicks of core/non core apps to install

  Steps to reproduce:

  1º Open terminal and run $ pkon install-local --allow-untrusted /path

  Current result: pkcon command returns the error given at the bottom

  Expected result: pkcon command should run with out any issue and
  clicks should be installed

  Reproducibility 100%

  -
  output

  11:59:57PackageKit  Verbose debugging enabled (on console 1)
  11:59:57PackageKit  filter=(null), filters=0
  11:59:57PackageKit  adding state 0x562f87db10d0
  11:59:57PackageKit  doing install files
  11:59:57PackageKit  role now install-files
  Installing files  [=] :59:57  
  PackageKit  using frontend diaFinished  
[=] :59:57PackageKit  remove 
state 0x562Fatal error: MIME type 'application/x-click' not supported 
/home/users/Downloads/com.ubuntu.calendar_0.4.757_all.click

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

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

[Touch-packages] [Bug 1620297] Re: First scope not rendered until unlocked

[Michał Sawicz]

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) => Michał Sawicz (saviq)

** Changed in: canonical-devices-system-image
   Importance: Undecided => Low

** Changed in: canonical-devices-system-image
   Importance: Low => High

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

** Changed in: qtubuntu (Ubuntu)
   Importance: Critical => High

** Changed in: canonical-devices-system-image
Milestone: None => 13

** Changed in: canonical-devices-system-image
   Importance: High => Critical

** Changed in: qtubuntu (Ubuntu)
   Importance: High => Critical

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

Title:
  First scope not rendered until unlocked

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

Bug description:
  The pre-populating of first scope on startup (before the screen is
  unlocked) doesn't seem to be fully working.

  My early investigation shows that the shell plugin correctly pre-
  populates scope model on startup when the screen is still locked, but
  after unlocking scope view is white for 1-2 seconds and only then the
  page is rendered and all the images are requested, so the perception
  is as if pre-population didn't work. The perceived performance depends
  on whether the 1st scope is a local scope (such as Apps) or a scope
  which needs remote images (and whether the images are already cached
  by the thumbnailer in the latter case).

  This might be caused by https://bugs.launchpad.net/qtmir/+bug/1475678

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

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

[Touch-packages] [Bug 976124] Re: lightdm multiseat: no login possible

[Alberts Muktupāvels]

** Changed in: lightdm
   Status: Confirmed => Fix Released

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

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

Title:
  lightdm multiseat: no login possible

Status in Light Display Manager:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Confirmed

Bug description:
  I am testing a multiseat setup with precise:

  One XServer is running on intel graphics card, a second one is running
  on a DisplayLink (usb video) device.

  The two greeters are displayed, but without password fields shown so
  it is not possible to login. If auto-login is enabled in lightdm.conf
  multiseat works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sat Apr  7 20:35:52 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1595989] Re: Ubuntu 15.10 crashes with Kernel later than 4.2.0_30

[Bret Curtis]

Not sure how this has to do with openal-soft.

** Package changed: openal-soft (Ubuntu) => ubuntu

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

Title:
  Ubuntu 15.10 crashes with Kernel later than 4.2.0_30

Status in Ubuntu:
  New

Bug description:
  Since the installation of the kernel 4.2.0_34 and later, my Ubuntu does not 
work properly.
  It hangs during start, or short after login. I found this message in the 
system.log:

  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970170] 
[ cut here ]
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970188] WARNING: 
CPU: 0 PID: 3142 at /build/linux-qsdjht/linux-4.2.0/fs/block_dev.c:57 
__blkdev_put+0xbf/0x250()
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970191] Modules 
linked in: nls_iso8859_1 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) drbg ansi_cprng ctr ccm binfmt_misc rfcomm bnep snd_hrtimer 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common ath3k 
btusb arc4 ath9k videodev btrtl btbcm ath9k_common btintel bluetooth ath9k_hw 
media intel_rapl ath snd_hda_codec_hdmi mac80211 intel_soc_dts_iosf 
intel_powerclamp snd_hda_codec_realtek snd_hda_codec_generic coretemp 
snd_hda_intel snd_hda_codec punit_atom_debug cfg80211 snd_hda_core 
crct10dif_pclmul snd_hwdep hp_wmi sparse_keymap crc32_pclmul snd_pcm 
snd_seq_midi snd_seq_midi_event input_leds joydev snd_rawmidi serio_raw cryptd 
snd_seq kvm_intel snd_seq_device snd_timer kvm snd mei_txe lpc_ich soundcore 
shpchp mei wmi hp_wireless intel_smartconnect mac_hid parport_pc ppdev lp 
parport autofs4 uas usb_storage i915 psmouse i2c_algo_bit drm_kms_helper r8169 
drm mii ahci libahci video
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970290] CPU: 0 
PID: 3142 Comm: umount Tainted: G   OE   4.2.0-38-generic #45-Ubuntu
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970293] Hardware 
name: Hewlett-Packard HP 250 G2 Notebook PC/2190, BIOS F.1A 12/04/2014
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970297]  
0286 e8188e49 880178d97d98 817f250e
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970303]  
 81cbfce8 880178d97dd8 8107cae6
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970308]  
 880078dd5380 880078dd54f8 880078dd5470
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970313] Call 
Trace:
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970323]  
[] dump_stack+0x63/0x81
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970331]  
[] warn_slowpath_common+0x86/0xc0
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970335]  
[] warn_slowpath_null+0x1a/0x20
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970339]  
[] __blkdev_put+0xbf/0x250
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970344]  
[] blkdev_put+0x50/0x120
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970350]  
[] kill_block_super+0x41/0x70
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970354]  
[] deactivate_locked_super+0x43/0x70
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970358]  
[] deactivate_super+0x64/0x70
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970364]  
[] cleanup_mnt+0x43/0x90
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970368]  
[] __cleanup_mnt+0x12/0x20
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970373]  
[] task_work_run+0x73/0x90
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970381]  
[] do_notify_resume+0x69/0x70
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970386]  
[] int_signal+0x12/0x17
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970390] ---[ end 
trace 427c1d4aa86831c9 ]---

  With the Kernel 4.2.0_30 I can work without any problems.

  Here some additional Informations: 
  florian@florian-HP-250-G2-Notebook-PC:~$ lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  Hardware: HP-250-G2-Notebook

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

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

[Touch-packages] [Bug 1616422] Re: [trusty SRU/FFE] Add systemd binary package for snapd

[Martin Pitt]

** Description changed:

  Rationale: For backporting snapd to 14.04 LTS, we need to provide
  systemd's service manager (not just logind and auxiliary services like
  logind or timesyncd). upstart will continue to do the actual booting,
  and systemd will act as a "deputy init" which by default does not ship
  with/start any services by itself. We will only support this on server
  (at the first iteration at least), not on desktops.
  
  Regression potential: This is a new binary package in universe, so
  existing systems are unaffected (provided that we ensure that the other
  binary packages do not change and there are no code changes that affect
  processes other than the "deputy pid 1" service manager). So for plain
  upgrades the regression potential is very low. However, there is a
  medium potential for breakage when actually installing the new systemd
  package, as it might interfere with upstart jobs or other running
  processes, cause boot/shutdown hangs, etc.
  
  Test plan:
   1. Dist-upgrade a trusty installation to the proposed versions. Ensure this 
does not pull in "systemd", and that booting, shutdown, desktop startup, 
suspend on lid close, resume, logout, and user switching all still work.
  
   2. Install the "systemd" binary package (this will replace/remove
  systemd-shim). Verify that you can talk to the service manager with
  "sudo systemctl status". Check that booting and shutdown continues to
  work without (significant) delays.
  
   3. Ensure that "sudo journalctl" works and that "sudo systemctl status
  systemd-journald" is running and has a few lines of log at the end
  (unlike what you get when you run systemctl as user).
  
   4. Install a package that ships a systemd .service file, such as
  "haveged". Ensure that the service file is ignored, "pgrep -af haveged"
  should only have *one* process and "systemctl status haveged" should not
  be running (it should not exist, or not be enabled and be inactive).
  
     The only services that are running are expected to be systemd-
  journald.service and systemd-journald.socket.
  
   5. Ensure that the standard targets are active, as that is where third-
  party/snap services hook into:
  
  systemctl status sysinit.target multi-user.target default.target
  
   6. Install snapd (not in trusty yet, e. g. from Thomas' PPA) and ensure
  you can install a snap, and its services start after installing the snap
  and after rebooting.
  
-  7. Run "sudo apt-get install --reinstall systemd" to ensure that
- upgrades to newer systemd trusty versions work.
+  7. Run "sudo apt-get install --reinstall systemd" to ensure that
+ upgrades to newer systemd trusty versions work. The running systemd
+ should *not* be restarted as that would disrupt snapd and its services
+ (verify that the pid in "initctl status systemd" is the same before and
+ after the upgrade).
  
   8. Dist-upgrade to 16.04 to ensure that there are no file conflicts,
  dependency issues, etc.

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

Title:
  [trusty SRU/FFE] Add systemd binary package for snapd

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Trusty:
  In Progress

Bug description:
  Rationale: For backporting snapd to 14.04 LTS, we need to provide
  systemd's service manager (not just logind and auxiliary services like
  logind or timesyncd). upstart will continue to do the actual booting,
  and systemd will act as a "deputy init" which by default does not ship
  with/start any services by itself. We will only support this on server
  (at the first iteration at least), not on desktops.

  Regression potential: This is a new binary package in universe, so
  existing systems are unaffected (provided that we ensure that the
  other binary packages do not change and there are no code changes that
  affect processes other than the "deputy pid 1" service manager). So
  for plain upgrades the regression potential is very low. However,
  there is a medium potential for breakage when actually installing the
  new systemd package, as it might interfere with upstart jobs or other
  running processes, cause boot/shutdown hangs, etc.

  Test plan:
   1. Dist-upgrade a trusty installation to the proposed versions. Ensure this 
does not pull in "systemd", and that booting, shutdown, desktop startup, 
suspend on lid close, resume, logout, and user switching all still work.

   2. Install the "systemd" binary package (this will replace/remove
  systemd-shim). Verify that you can talk to the service manager with
  "sudo systemctl status". Check that booting and shutdown continues to
  work without (significant) delays.

   3. Ensure that "sudo journalctl" works and that "sudo systemctl
  status systemd-journald" is running and has a few lines of log at the
  end (unlike what you get when you run systemctl as user).

[Touch-packages] [Bug 1562208] Re: OpenAL Software Silent/Freezes

[Bret Curtis]

Not an OpenAL-Soft issue, but a Pulseaudio one.

** Package changed: openal-soft (Ubuntu) => ubuntu

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

Title:
  OpenAL Software Silent/Freezes

Status in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following an update I made this week to the system, I have attempted
  to play a number of games, including "X Rebirth" from gog.com,
  "Minecraft," downloaded from Mojang.  In those games making use of the
  OpenAL library, no sound is coming through PulseAudio; there is a
  stream listed in Pulse, but there is no sound, and the meter does not
  indicate that PulseAudio is even receiving any audio.  I am also
  noticing the problem in Blender, but in this case, the issue seems to
  cause the VSE to stick to the frame it's at when set to "A/V Sync"

  To make matters worse, once the stream shows in "pavucontrol," the
  program won't end.  If the audio is integral to the software, such as
  the case of Blender, the software itself will freeze when I attempt to
  close it; I will have to kill the program to make it shut down
  completely.  Other programs that use a sound server with OpenAL seem
  to close, but the stream is still showing in pavucontrol, and the
  process is still shown as running in "ps x".  Killing the frozen app
  makes it go away; and so far, the normal kill command will work;
  there's no need to "-9" it.

  Even openal-info freezes, after displaying the following:

  ---

  Available playback devices:
  CM106 Like Sound Device Analog Stereo
  Available capture devices:
  M-Audio Fast Track MKII Analog Stereo
  Monitor of CM106 Like Sound Device Analog Stereo
  Default playback device: CM106 Like Sound Device Analog Stereo
  Default capture device: CM106 Like Sound Device Analog Stereo
  ALC version: 1.1

  ** Info for device "CM106 Like Sound Device Analog Stereo" **
  ALC version: 1.1
  ALC extensions:
  ALC_ENUMERATE_ALL_EXT, ALC_ENUMERATION_EXT, ALC_EXT_CAPTURE,
  ALC_EXT_DEDICATED, ALC_EXT_disconnect, ALC_EXT_EFX,
  ALC_EXT_thread_local_context, ALC_SOFTX_device_clock, ALC_SOFTX_HRTF,
  ALC_SOFT_loopback, ALC_SOFTX_midi_interface, ALC_SOFT_pause_device
  OpenAL vendor string: OpenAL Community
  OpenAL renderer string: OpenAL Soft
  OpenAL version string: 1.1 ALSOFT 1.16.0
  OpenAL extensions:
  AL_EXT_ALAW, AL_EXT_DOUBLE, AL_EXT_EXPONENT_DISTANCE, AL_EXT_FLOAT32,
  AL_EXT_IMA4, AL_EXT_LINEAR_DISTANCE, AL_EXT_MCFORMATS, AL_EXT_MULAW,
  AL_EXT_MULAW_MCFORMATS, AL_EXT_OFFSET, AL_EXT_source_distance_model,
  AL_LOKI_quadriphonic, AL_SOFT_block_alignment, AL_SOFT_buffer_samples,
  AL_SOFT_buffer_sub_data, AL_SOFT_deferred_updates, 
AL_SOFT_direct_channels,
  AL_SOFT_loop_points, AL_SOFT_MSADPCM, AL_SOFT_source_latency,
  AL_SOFT_source_length
  EFX version: 1.0
  Max auxiliary sends: 4
  Supported filters:
  Low-pass, High-pass, Band-pass
  Supported effects:
  EAX Reverb, Reverb, Chorus, Distortion, Echo, Flanger, Ring Modulator,
  Compressor, Equalizer, Dedicated Dialog, Dedicated LFE

  ---

  This problem persisted, even following a clean installation with no
  PPAs installed.  I'm assuming the problem is in OpenAL, because
  programs not making use of that library (YouTube, VLC, etc.) don't
  seem to have the problem.  The update that seemed to be the breaking
  point was an update to kernel 4.2.0-34 (I no longer have the original
  system, thinking a full restore would fix things), so there might be
  something in the new kernel that's interfering with OpenAL.

  ---

  The required information:

  Description:  Ubuntu 15.10
  Release:  15.10

  libopenal1:
Installed: 1:1.16.0-3
Candidate: 1:1.16.0-3
Version table:
   *** 1:1.16.0-3 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

  ---

  Please let me know if there's any additional information that I will
  need to provide.

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

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

[Touch-packages] [Bug 1612767] Re: Drop appmenu-qt5 from default installations

[Timo Jyrinki]

Yes the global menus seemed to be working fine both with and without
appmenu-qt5 now.

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

Title:
  Drop appmenu-qt5 from default installations

Status in indicator-appmenu package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  Currently we are using appmenu-qt5 as our platform theme on desktop,
  however it has many disadvantages, which make me want to get rid of
  it:

  1) Its design is a hack: instead of the using normal QPA API for
  getting the menu, it retrieves the menu bar using QWidget::findChild,
  and then casts the pointer to QMenu*. The normal methods (which are
  getting called by Qt) remain empty stubs.

  2) It is preventing applications from using GTK+ theme integration,
  such as dialogs (I reported this as bug 1378935, but there is no easy
  way to fix that).

  3) It is not working with Qt Quick applications (because it expects a
  QtWidgets window; see also bug 1323853). The standard implementation
  will work with i.e. Qt Quick Controls 2 using apps (implemented in
  https://codereview.qt-project.org/142733).

  4) It breaks other environments such as Plasma or GNOME when
  installed: see bug 1434516, bug 1307619.

  5) Finally, it is mostly unmaintained: most patches since 2014 are
  authored by me, however I see no point continuing to develop that
  code.

  Recently, Shawn Rutledge and I have written a native implementation of
  what appmenu-qt5 provides (global menu and system tray), which is part
  of Qt. That code uses the normal API, is well maintained, and works
  better than appmenu-qt5 (or at least not worse).

  So I propose to drop appmenu-qt5 from default Ubuntu installations,
  and maybe later from archive too.

  Unfortunately we use Qt 5.6, and some of the needed patches are only
  in Qt 5.7, so I would like to backport them to our packaging:

  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f199bb9133fe0446 (will be in 
5.6.2 / 5.7.0)
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=488cf78e44947eff (will be in 
5.7.0)
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=b6a824d0a3b4fabd (will be in 
5.7.0)
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e4d79e1fdeb6b26b (will be in 
5.7.0)

  Timo: if you have no objections, I will commit those patches to the
  packaging Git.

  After we do that, I will remove the appmenu-qt5 recommendation from
  indicator-appmenu (that is the only package referring to it).

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

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

[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[Joakim Koed]

Hey Luke, sorry for the delay, was at school :)

See attachment.

** Attachment added: "pulseverbose.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+attachment/4735345/+files/pulseverbose.log

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3
Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29 
  Device 44:5E:F3:B4:07:29
Name: BlueBuds X
Alias: BlueBuds X
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

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

[Touch-packages] [Bug 1608822] Re: signon fails tests on Qt 5.6

[Timo Jyrinki]

qtbase-opensource-src (5.6.1+dfsg-3ubuntu3~3) yakkety; urgency=medium

  [ Timo Jyrinki ]
  * debian/patches/QDBusServer-delay-processing-of-D-Bus-messages.patch:
- Fix DBus message processing (LP: #1608822)
  * debian/patches/xcb-Send-also-text-plain-when-a-text-uri-list-is-dro.patch:
- Fix drag and drop from Qt to skype (LP: #1586857)
  * debian/patches/qt5-qmake-arm-linux-gnueabihf:
- Support cross-compilation inside chroot using pkg-config (LP: #1580981)
  * debian/patches/Make-sure-connection-is-not-null-before-using-it.patch:
- Fix unity8 crasher (LP: #1612309)
  * Update symbols with pkgkde-mark-qt5-private-symbols.
  * Disable printsupport tests that started failing but only on builders,
possibly with new glibc. See LP: #1612767 for details.

  [ Dmitry Shachnev ]
  * Backport some upstream patches to add support for D-Bus global menus,
and improve support for D-Bus tray icons (LP: #1612767):
+ dbustray_use_separate_connections.diff (fix for multiple tray icons)
+ dbusmenu_exclusive_groups.diff (fix for radio actions)
+ qplatformmenubar_createmenu.diff (adding a method to QPlatformMenuBar)
+ dbusmenu_global_menu.diff (add support for D-Bus global menus)
  * Add a distro patch to stop setting AA_DontUseNativeMenuBar unconditionally
(allow_native_menubar.diff): we want this attribute to be false by default,
but applications should be able to override it.

 -- Timo Jyrinki  Sat, 03 Sep 2016 13:58:20
+

** Also affects: qtbase-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Fix Released

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

Title:
  signon fails tests on Qt 5.6

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in signon package in Ubuntu:
  In Progress

Bug description:
  See build logs at:

  https://launchpadlibrarian.net/276197217/buildlog_ubuntu-yakkety-
  
amd64.signon_8.58+16.04.20151106-0ubuntu2~~testrebuild1~~testrebuild1~1_BUILDING.txt.gz

  Qt 5.6 aims to be landed to the xenial-overlay so this should be
  fixed.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1608822/+subscriptions

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

[Touch-packages] [Bug 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

There was a hack put into Mir around the end of June 2015 as linked by
Daniel
(https://code.launchpad.net/~vanvugt/mir/fix-1391976/+merge/262678). As
the comment suggests this was pending "a proper fix will come from
libprotobuf itself but this way we don't need to wait for that".

This "hack" was removed at the end of July 2015. I don't see a
corresponding change to protobuf. So I suspect I have been chasing the
wrong fix. I found some differences that look related and tried patching
them locally. I still have to figure out why patching things seems to
work locally - especially with the typo in the patch file. Clearly I'm
doing something wrong. :(

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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

[Touch-packages] [Bug 1616422] Re: [trusty SRU/FFE] Add systemd binary package for snapd

[Martin Pitt]

git/PPA updated to 204-5ubuntu20.19pitti4 which now also fixes the hang
during dist-upgrading to 16.04 LTS. "reboot -f" after the upgrade is
still needed, though.

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

Title:
  [trusty SRU/FFE] Add systemd binary package for snapd

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Trusty:
  In Progress

Bug description:
  Rationale: For backporting snapd to 14.04 LTS, we need to provide
  systemd's service manager (not just logind and auxiliary services like
  logind or timesyncd). upstart will continue to do the actual booting,
  and systemd will act as a "deputy init" which by default does not ship
  with/start any services by itself. We will only support this on server
  (at the first iteration at least), not on desktops.

  Regression potential: This is a new binary package in universe, so
  existing systems are unaffected (provided that we ensure that the
  other binary packages do not change and there are no code changes that
  affect processes other than the "deputy pid 1" service manager). So
  for plain upgrades the regression potential is very low. However,
  there is a medium potential for breakage when actually installing the
  new systemd package, as it might interfere with upstart jobs or other
  running processes, cause boot/shutdown hangs, etc.

  Test plan:
   1. Dist-upgrade a trusty installation to the proposed versions. Ensure this 
does not pull in "systemd", and that booting, shutdown, desktop startup, 
suspend on lid close, resume, logout, and user switching all still work.

   2. Install the "systemd" binary package (this will replace/remove
  systemd-shim). Verify that you can talk to the service manager with
  "sudo systemctl status". Check that booting and shutdown continues to
  work without (significant) delays.

   3. Ensure that "sudo journalctl" works and that "sudo systemctl
  status systemd-journald" is running and has a few lines of log at the
  end (unlike what you get when you run systemctl as user).

   4. Install a package that ships a systemd .service file, such as
  "haveged". Ensure that the service file is ignored, "pgrep -af
  haveged" should only have *one* process and "systemctl status haveged"
  should not be running (it should not exist, or not be enabled and be
  inactive).

     The only services that are running are expected to be systemd-
  journald.service and systemd-journald.socket.

   5. Ensure that the standard targets are active, as that is where
  third-party/snap services hook into:

  systemctl status sysinit.target multi-user.target default.target

   6. Install snapd (not in trusty yet, e. g. from Thomas' PPA) and
  ensure you can install a snap, and its services start after installing
  the snap and after rebooting.

   7. Run "sudo apt-get install --reinstall systemd" to ensure that
  upgrades to newer systemd trusty versions work. The running systemd
  should *not* be restarted as that would disrupt snapd and its services
  (verify that the pid in "initctl status systemd" is the same before
  and after the upgrade).

   8. Dist-upgrade to 16.04 to ensure that there are no file conflicts,
  dependency issues, etc.

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

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

[Touch-packages] [Bug 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

I'm very suspicious of my laptop running yakkety - even with "proposed"
purged it is now crashing every few minutes (which makes keeping track
of things a PITA).

The root cause is probably a failure in protobuf to re-initalise static
data when clients call google::protobuf::ShutdownProtobufLibrary(). This
leads to a failure when if the whole .so isn't unloaded before the next
"GOOGLE_PROTOBUF_VERIFY_VERSION;"

Which is why the change I picked up looks relevant.

The "hack" mentioned above did appear to workaround the problem for Mir
(i.e. the test passes). (But it will probably recur with other Qt
plugins that use protobuf.)

So I'm going to reinstall and start over.

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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

[Touch-packages] [Bug 1618390] Re: dbus-cpp crash on arm64 in core::dbus::Object::get_property

[Timo Jyrinki]

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

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

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

Title:
  dbus-cpp crash on arm64 in core::dbus::Object::get_property

Status in Canonical System Image:
  In Progress
Status in dbus-cpp package in Ubuntu:
  Confirmed
Status in location-service package in Ubuntu:
  Confirmed
Status in mtp package in Ubuntu:
  Confirmed

Bug description:
  Requests to location service cause crashes on arm64:

  $ system-image-cli -i
  current build number: 23
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-08-30 09:13:12
  version version: 23
  version ubuntu: 20160830
  version device: 20160824.0
  version custom: 20160830

  Steps:
  * flash the above channel (remember --device frieza_arm64)
  * go to a scope using location
  * refresh

  == Stacktrace =
  #0  0x007f978d4328 in 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, 
__mem=0x29) at /usr/include/c++/5/ext/atomicity.h:49
  __val = -1
  __mem = 0x29
  #1  0x007f978d4328 in 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, 
__mem=0x29) at /usr/include/c++/5/ext/atomicity.h:82
  __val = -1
  __mem = 0x29
  #2  0x007f978d4328 in 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (this=0x21) at 
/usr/include/c++/5/bits/shared_ptr_base.h:147
  #3  0x007f97922a28 in 
std::__shared_count<(__gnu_cxx::_Lock_policy)2>::operator=(std::__shared_count<(__gnu_cxx::_Lock_policy)2>
 const&) (this=this@entry=0x8b34558, __r=...) at 
/usr/include/c++/5/bits/shared_ptr_base.h:678
  __tmp = 0x8b34ba0
  #4  0x007f9792cc64 in 
core::dbus::Object::get_property()
 (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr_base.h:867
  property = 
  #5  0x007f9792cc64 in 
core::dbus::Object::get_property()
 (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr.h:93
  property = 
  #6  0x007f9792cc64 in 
core::dbus::Object::get_property()
 (this=0x8b342c0) at /usr/include/core/dbus/impl/object.h:162
  property = 
  #7  0x007f97931c08 in 
com::ubuntu::location::service::Stub::Stub(std::shared_ptr 
const&) (object=warning: can't find linker symbol for virtual table for 
`std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value
  warning: can't find linker symbol for virtual table for 
`std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libubuntu-location-service3 3.0.0+16.04.20160811-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: arm64
  Date: Tue Aug 30 09:39:24 2016
  SourcePackage: location-service
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: arm64
  DistroRelease: Ubuntu 16.04
  Package: mtp-server 0.0.4+16.04.20160413-0ubuntu2 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  PackageArchitecture: arm64
  Tags: third-party-packages xenial
  Uname: Linux 3.10.93+ aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip plugdev sudo tty video
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1620522] Re: online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New

Bug description:
  Online accounts are broken in unity8 on dekstop, there is no way to
  add any account right now. The auto bug report appeared once I was
  back in u7 from u8

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-system-settings-online-accounts 0.7+16.10.20160718-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Sep  6 10:19:06 2016
  ExecutablePath: /usr/bin/online-accounts-ui
  InstallationDate: Installed on 2016-08-10 (27 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20160806)
  ProcCmdline: /usr/bin/online-accounts-ui --socket 
/run/user/1000/online-accounts-ui/ui-1-ubuntuone --profile unconfined
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
  Signal: 6
  SourcePackage: ubuntu-system-settings-online-accounts
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, 
char const*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () from 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   QPlatformIntegrationFactory::create(QString const&, QStringList const&, 
int&, char**, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1620522/+subscriptions

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

[Touch-packages] [Bug 1585996] Re: UITK gallery: can't open subpages on Qt 5.6 because of TypeError

[Christian Dywan]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: Christian Dywan (kalikiana) => (unassigned)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

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

Title:
  UITK gallery: can't open subpages on Qt 5.6 because of TypeError

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  On Qt 5.6 I can't seem to be able to open subpages in UITK Gallery
  (installed from Store). In logs I have:

  qml: sourcePage must be added to the view to add new page.

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

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

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

[Touch-packages] [Bug 1620313] Re: stop using hardening-wrapper, obsoleted by recent dpkg-dev

[Matthias Klose]

see dpkg-buildflags(1) about setting DEB_BUILD_MAINT_OPTIONS.

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

Title:
  stop using hardening-wrapper, obsoleted by recent dpkg-dev

Status in firefox package in Ubuntu:
  New
Status in gtk2-engines-murrine package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  New
Status in hardening-wrapper package in Debian:
  New

Bug description:
  stop using hardening-wrapper, obsoleted by recent dpkg-dev.

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

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

[Touch-packages] [Bug 1620192] Re: Sound over HDMI is 2x as slow after resuming from standby

[Luke Yelavich]

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

** This bug has been marked a duplicate of bug 1580882
   [, Intel Broadwell HDMI, Digital Out, HDMI] Sound like half speed

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

Title:
  Sound over HDMI is 2x as slow after resuming from standby

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have an extremely frustrating problem with Ubuntu 16.04.1 LTS
  64-bits on my Dell E7450 laptop: when I connect a TV over HDMI afater
  resuming from standby, the sound is 2x as slow, and everything else,
  e.g. video playback, is dragged down to slow-motion.

  For example, testing audio via Speaker Testing goes "Frooont Leeeft"
  in a low-pitch male voice (the normal is a crisp "Front Left" in a
  female voice").

  Reproduction steps:

  1. Connect laptop to TV over HDMI cable
  2. Go to All Settings -> Sound and select to "Play sound through" 
HDMI/DisplayPort audio
  3. Play a video and ensure the playback is at normal speed and the sound 
comes out of the TV.
  4. Suspend the laptop.
  5. Resume the laptop.
  6. Play the same video again.

  Actual results: the sound and video look slow-motion, at about 50%
  speed. Go to Test Sound, and Front Left will sound like "Frooont
  Leeeft".

  This is super annoying because I have to close all my applications and
  reboot every time I want to watch a movie through my TV.

  Asked at http://askubuntu.com/questions/805355/sound-over-hdmi-is-2x-
  as-slow-after-resuming-from-standby, no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep  4 22:31:04 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-09-04 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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/pulseaudio/+bug/1620192/+subscriptions

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

[Touch-packages] [Bug 1620553] [NEW] [Krillin] Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable

[Andrea Bernabei]

Public bug reported:

Krillin, rc-proposed/bq_aquaris.en r422

Description:
All at once taps have become incredibly delayed, by 1 or 2 secs.
Gestures still work ok, no delay there.
Swiping the greeter -> no delay. Tapping numbers to input code on the greeter 
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to 
only be a problem of unity8 clients, but also unity8 itself.
I have no idea why horizontal/vertical swipes would be unaffected, though.

The virtual keyboard is also completely unusable because of the huge
delay that each tap has.

Also noticed that the vibration is gone, taps don't trigger vibration
anymore.

Webview also seemed to be unaffected by the delays (although I'm not
entirely sure, the bug is now gone)

I also restarted unity8 and unity8-dash with Mir input logging enabled. That 
showed that the touch events were being delivered as expected, no delay.
restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log

Restarting lightdm (that forces the restart of unity-system-compositor)
fixed the issue.

Additional info: I had Mir touchspots visualization enabled, which are
known to cause more stuttering, but I think they're unlikely to be the
cause of this bug, I had them enabled for 2 weeks and haven't noticed
any problem like this before.

This is the log from a tap on an icon in the shell:
[2016-09-06 10:52:51.876400]  input-receiver: Received 
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0, 
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963, 
minor=0, size=19.963}, modifiers=1)
[2016-09-06 10:52:51.953821]  input-receiver: Received 
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0, 
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137, 
major=19.963, minor=0, size=19.963}, modifiers=1)
[2016-09-06 10:52:51.954343]  input-receiver: Received 
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0, 
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963, 
minor=0, size=19.963}, modifiers=1)


SEE VIDEO ATTACHMENT BELOW

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

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

Title:
  [Krillin] Taps are delayed by 1-2seconds, although gestures are not.
  Keyboard is thus unusable

Status in unity8 package in Ubuntu:
  New

Bug description:
  Krillin, rc-proposed/bq_aquaris.en r422

  Description:
  All at once taps have become incredibly delayed, by 1 or 2 secs.
  Gestures still work ok, no delay there.
  Swiping the greeter -> no delay. Tapping numbers to input code on the greeter 
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to 
only be a problem of unity8 clients, but also unity8 itself.
  I have no idea why horizontal/vertical swipes would be unaffected, though.

  The virtual keyboard is also completely unusable because of the huge
  delay that each tap has.

  Also noticed that the vibration is gone, taps don't trigger vibration
  anymore.

  Webview also seemed to be unaffected by the delays (although I'm not
  entirely sure, the bug is now gone)

  I also restarted unity8 and unity8-dash with Mir input logging enabled. That 
showed that the touch events were being delivered as expected, no delay.
  restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
  restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log

  Restarting lightdm (that forces the restart of unity-system-
  compositor) fixed the issue.

  Additional info: I had Mir touchspots visualization enabled, which are
  known to cause more stuttering, but I think they're unlikely to be the
  cause of this bug, I had them enabled for 2 weeks and haven't noticed
  any problem like this before.

  This is the log from a tap on an icon in the shell:
  [2016-09-06 10:52:51.876400]  input-receiver: Received 
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0, 
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963, 
minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.953821]  input-receiver: Received 
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0, 
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137, 
major=19.963, minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.954343]  input-receiver: Received 
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0, 
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963, 
minor=0, size=19.963}, modifiers=1)

  
  SEE VIDEO ATTACHMENT BELOW

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

-- 
Mailing list:

[Touch-packages] [Bug 1620553] Re: [Krillin] Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable

[Andrea Bernabei]

** Attachment added: "video showing the sympthoms"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1620553/+attachment/4735390/+files/video_2016-09-06_10-48-11.mov

** Description changed:

  Krillin, rc-proposed/bq_aquaris.en r422
  
- Description: 
+ Description:
  All at once taps have become incredibly delayed, by 1 or 2 secs.
- Gestures still work ok, no delay there. 
+ Gestures still work ok, no delay there.
  Swiping the greeter -> no delay. Tapping numbers to input code on the greeter 
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to 
only be a problem of unity8 clients, but also unity8 itself.
  I have no idea why horizontal/vertical swipes would be unaffected, though.
  
  The virtual keyboard is also completely unusable because of the huge
  delay that each tap has.
  
  Also noticed that the vibration is gone, taps don't trigger vibration
  anymore.
  
  Webview also seemed to be unaffected by the delays (although I'm not
  entirely sure, the bug is now gone)
  
  I also restarted unity8 and unity8-dash with Mir input logging enabled. That 
showed that the touch events were being delivered as expected, no delay.
- restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and 
+ restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
  restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log
  
  Restarting lightdm (that forces the restart of unity-system-compositor)
  fixed the issue.
  
  Additional info: I had Mir touchspots visualization enabled, which are
  known to cause more stuttering, but I think they're unlikely to be the
  cause of this bug, I had them enabled for 2 weeks and haven't noticed
  any problem like this before.
  
  This is the log from a tap on an icon in the shell:
  [2016-09-06 10:52:51.876400]  input-receiver: Received 
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0, 
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963, 
minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.953821]  input-receiver: Received 
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0, 
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137, 
major=19.963, minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.954343]  input-receiver: Received 
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0, 
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963, 
minor=0, size=19.963}, modifiers=1)
+ 
+ 
+ SEE VIDEO ATTACHMENT BELOW

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

Title:
  [Krillin] Taps are delayed by 1-2seconds, although gestures are not.
  Keyboard is thus unusable

Status in unity8 package in Ubuntu:
  New

Bug description:
  Krillin, rc-proposed/bq_aquaris.en r422

  Description:
  All at once taps have become incredibly delayed, by 1 or 2 secs.
  Gestures still work ok, no delay there.
  Swiping the greeter -> no delay. Tapping numbers to input code on the greeter 
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to 
only be a problem of unity8 clients, but also unity8 itself.
  I have no idea why horizontal/vertical swipes would be unaffected, though.

  The virtual keyboard is also completely unusable because of the huge
  delay that each tap has.

  Also noticed that the vibration is gone, taps don't trigger vibration
  anymore.

  Webview also seemed to be unaffected by the delays (although I'm not
  entirely sure, the bug is now gone)

  I also restarted unity8 and unity8-dash with Mir input logging enabled. That 
showed that the touch events were being delivered as expected, no delay.
  restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
  restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log

  Restarting lightdm (that forces the restart of unity-system-
  compositor) fixed the issue.

  Additional info: I had Mir touchspots visualization enabled, which are
  known to cause more stuttering, but I think they're unlikely to be the
  cause of this bug, I had them enabled for 2 weeks and haven't noticed
  any problem like this before.

  This is the log from a tap on an icon in the shell:
  [2016-09-06 10:52:51.876400]  input-receiver: Received 
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0, 
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963, 
minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.953821]  input-receiver: Received 
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0, 
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137, 
major=19.963, minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.954343]  input-receiver: Received 
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0, 

[Touch-packages] [Bug 1620553] Re: [Krillin] Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable

[Andrea Bernabei]

I think I know that it could be! 
I think it's the vibration handler!

After inputting the passcode in the greeter, unity8 prints the following lines 
*after* the 2 secs delay:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.


And as noted in the bug description, one of the sympthoms was that vibration 
stopped working.

I think what happened is that the vibrator handler crashed, and on every
tap that requires vibration the system is waiting some timeout for the
vibrator to reply to the DBus call before timing out.

Those calls are probably synchronous, hence blocking the UI until a
reply is received (do we really have to block the UI to vibrate?). But
since the other end is probably dead, the phone stalls until the NoReply
answer is received, and only then the UI thread gets back in control
again.

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

Title:
  [Krillin] Taps are delayed by 1-2seconds, although gestures are not.
  Keyboard is thus unusable

Status in unity8 package in Ubuntu:
  New

Bug description:
  Krillin, rc-proposed/bq_aquaris.en r422

  Description:
  All at once taps have become incredibly delayed, by 1 or 2 secs.
  Gestures still work ok, no delay there.
  Swiping the greeter -> no delay. Tapping numbers to input code on the greeter 
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to 
only be a problem of unity8 clients, but also unity8 itself.
  I have no idea why horizontal/vertical swipes would be unaffected, though.

  The virtual keyboard is also completely unusable because of the huge
  delay that each tap has.

  Also noticed that the vibration is gone, taps don't trigger vibration
  anymore.

  Webview also seemed to be unaffected by the delays (although I'm not
  entirely sure, the bug is now gone)

  I also restarted unity8 and unity8-dash with Mir input logging enabled. That 
showed that the touch events were being delivered as expected, no delay.
  restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
  restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log

  Restarting lightdm (that forces the restart of unity-system-
  compositor) fixed the issue.

  Additional info: I had Mir touchspots visualization enabled, which are
  known to cause more stuttering, but I think they're unlikely to be the
  cause of this bug, I had them enabled for 2 weeks and haven't noticed
  any problem like this before.

  This is the log from a tap on an icon in the shell:
  [2016-09-06 10:52:51.876400]  input-receiver: Received 
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0, 
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963, 
minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.953821]  input-receiver: Received 
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0, 
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137, 
major=19.963, minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.954343]  input-receiver: Received 
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0, 
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963, 
minor=0, size=19.963}, modifiers=1)

  
  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1620557] [NEW] weather.noaa.gov was shut down

[Dmitry Shachnev]

Public bug reported:

The provider which libgweather was using was shut down in August.

We need to update libgweather in Xenial to new upstream micro release,
3.18.2, which switched to a new METAR data provider.

Impact: this affects all libgweather-using applications, makes them
unable to retrieve weather data.

Test Case: make sure Weather applet in gnome-applets is able to display
weather information.

** Affects: libgweather
 Importance: Unknown
 Status: Unknown

** Affects: libgweather (Ubuntu)
 Importance: High
 Status: Fix Released

** Affects: libgweather (Ubuntu Xenial)
 Importance: High
 Assignee: Dmitry Shachnev (mitya57)
 Status: In Progress


** Tags: xenial

** Also affects: libgweather (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

** Changed in: libgweather (Ubuntu Xenial)
 Assignee: (unassigned) => Dmitry Shachnev (mitya57)

** Changed in: libgweather (Ubuntu)
 Assignee: Dmitry Shachnev (mitya57) => (unassigned)

** Changed in: libgweather (Ubuntu)
   Status: In Progress => Fix Released

** Bug watch added: GNOME Bug Tracker #770321
   https://bugzilla.gnome.org/show_bug.cgi?id=770321

** Also affects: libgweather via
   https://bugzilla.gnome.org/show_bug.cgi?id=770321
   Importance: Unknown
   Status: Unknown

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

Title:
  weather.noaa.gov was shut down

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  In Progress

Bug description:
  The provider which libgweather was using was shut down in August.

  We need to update libgweather in Xenial to new upstream micro release,
  3.18.2, which switched to a new METAR data provider.

  Impact: this affects all libgweather-using applications, makes them
  unable to retrieve weather data.

  Test Case: make sure Weather applet in gnome-applets is able to
  display weather information.

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

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

[Touch-packages] [Bug 1620559] [NEW] /etc/resolv.conf is empty on snappy

[Oliver Grawert]

Public bug reported:

we currently have no working resolver on snappy installs,
/etc/resolv.conf is the boilerplate one.

on the low level we seem to have DNS from the DHCP server though

ogra@localhost:~$ grep -r DNS= /run/systemd/netif
/run/systemd/netif/leases/3:DNS=217.237.150.115 217.237.151.205
/run/systemd/netif/links/3:DNS=217.237.150.115 217.237.151.205
/run/systemd/netif/links/3:MDNS=no
ogra@localhost:~$

** Affects: snappy
 Importance: Critical
 Status: New

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

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

** Changed in: snappy
   Importance: Undecided => Critical

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

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

Title:
  /etc/resolv.conf is empty on snappy

Status in Snappy:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  we currently have no working resolver on snappy installs,
  /etc/resolv.conf is the boilerplate one.

  on the low level we seem to have DNS from the DHCP server though

  ogra@localhost:~$ grep -r DNS= /run/systemd/netif
  /run/systemd/netif/leases/3:DNS=217.237.150.115 217.237.151.205
  /run/systemd/netif/links/3:DNS=217.237.150.115 217.237.151.205
  /run/systemd/netif/links/3:MDNS=no
  ogra@localhost:~$

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

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

[Touch-packages] [Bug 1598920] Re: MainView intercepts MouseArea's cursorShape property

[Christian Dywan]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Dubstar_04 (dubstar-04)

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

Title:
  MainView intercepts MouseArea's cursorShape property

Status in Canonical System Image:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The MouseArea CursorShape doesnt have any effect.

  Docs Here: http://doc.qt.io/qt-5/qml-qtquick-mousearea.html

  Expected Behavour:
  Mouse image shows selected Qt cursor

  Experienced Behavour:
  The regular arrow is displayed.

  Example Code:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  MainView {
  objectName: "mainView"
  applicationName: "mouseTest"

  width: units.gu(100)
  height: units.gu(75)

  Rectangle{
  anchors.fill: parent
  color: UbuntuColors.coolGrey

  MouseArea{
  anchors.fill: parent
  cursorShape: Qt.CrossCursor
  hoverEnabled: true
  onClicked: console.log("In MouseArea")
  }
  }
  }

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

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

[Touch-packages] [Bug 1618390] Re: dbus-cpp crash on arm64 in core::dbus::Object::get_property

[Timo Jyrinki]

** Changed in: dbus-cpp (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: location-service (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: mtp (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: location-service (Ubuntu)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

** Changed in: mtp (Ubuntu)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

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

Title:
  dbus-cpp crash on arm64 in core::dbus::Object::get_property

Status in Canonical System Image:
  In Progress
Status in dbus-cpp package in Ubuntu:
  Invalid
Status in location-service package in Ubuntu:
  In Progress
Status in mtp package in Ubuntu:
  In Progress

Bug description:
  Requests to location service cause crashes on arm64:

  $ system-image-cli -i
  current build number: 23
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-08-30 09:13:12
  version version: 23
  version ubuntu: 20160830
  version device: 20160824.0
  version custom: 20160830

  Steps:
  * flash the above channel (remember --device frieza_arm64)
  * go to a scope using location
  * refresh

  == Stacktrace =
  #0  0x007f978d4328 in 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, 
__mem=0x29) at /usr/include/c++/5/ext/atomicity.h:49
  __val = -1
  __mem = 0x29
  #1  0x007f978d4328 in 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, 
__mem=0x29) at /usr/include/c++/5/ext/atomicity.h:82
  __val = -1
  __mem = 0x29
  #2  0x007f978d4328 in 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (this=0x21) at 
/usr/include/c++/5/bits/shared_ptr_base.h:147
  #3  0x007f97922a28 in 
std::__shared_count<(__gnu_cxx::_Lock_policy)2>::operator=(std::__shared_count<(__gnu_cxx::_Lock_policy)2>
 const&) (this=this@entry=0x8b34558, __r=...) at 
/usr/include/c++/5/bits/shared_ptr_base.h:678
  __tmp = 0x8b34ba0
  #4  0x007f9792cc64 in 
core::dbus::Object::get_property()
 (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr_base.h:867
  property = 
  #5  0x007f9792cc64 in 
core::dbus::Object::get_property()
 (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr.h:93
  property = 
  #6  0x007f9792cc64 in 
core::dbus::Object::get_property()
 (this=0x8b342c0) at /usr/include/core/dbus/impl/object.h:162
  property = 
  #7  0x007f97931c08 in 
com::ubuntu::location::service::Stub::Stub(std::shared_ptr 
const&) (object=warning: can't find linker symbol for virtual table for 
`std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value
  warning: can't find linker symbol for virtual table for 
`std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libubuntu-location-service3 3.0.0+16.04.20160811-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: arm64
  Date: Tue Aug 30 09:39:24 2016
  SourcePackage: location-service
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: arm64
  DistroRelease: Ubuntu 16.04
  Package: mtp-server 0.0.4+16.04.20160413-0ubuntu2 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  PackageArchitecture: arm64
  Tags: third-party-packages xenial
  Uname: Linux 3.10.93+ aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip plugdev sudo tty video
  _MarkForUpload: True

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

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

Re: [Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[Luke Yelavich]

Ok thanks, pretty much the same failure as the original log shows.

So, for my and others record, the patch that makes things fail for you
is 0503-bluetooth-bluez5-ofono-add-support-for-spekaer-micro.patch. The
patch that reduces quality and makes A2DP unusuable is probably 0502
-bluetooth-bluez5-bring-back-SCO-over-PCM-support.patch.

Ill start looking at these tomorrow. I'll first see about fixing the
assertion error, then look into why A2DP is not working properly. Based
on what I find, I'll reply again once I think I have a fix for you to
test.

Thanks again for your help.

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3
Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29 
  Device 44:5E:F3:B4:07:29
Name: BlueBuds X
Alias: BlueBuds X
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

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

[Touch-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

[Wilson]

Similar problem with my Anker SoundBuds AK-A3233011: as the phone
(Aquaris E4.5) connect with the BT device the BT cease to function: I
cannot set BT of or set Airplane Mode; even a reboot will never
complete, I must force a full shutdown.

The device has some glitch with Ubuntu for desktop, also: sometimes it
will not switch from the headset mode to A2DP.

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

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

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

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

[Touch-packages] [Bug 1620553] Re: [Krillin] Taps are delayed by 1-2seconds, although gestures are not. Keyboard is thus unusable

[Michał Sawicz]

** Package changed: unity8 (Ubuntu) => ubuntu-ui-toolkit (Ubuntu)

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

Title:
  [Krillin] Taps are delayed by 1-2seconds, although gestures are not.
  Keyboard is thus unusable

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

Bug description:
  Krillin, rc-proposed/bq_aquaris.en r422

  Description:
  All at once taps have become incredibly delayed, by 1 or 2 secs.
  Gestures still work ok, no delay there.
  Swiping the greeter -> no delay. Tapping numbers to input code on the greeter 
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to 
only be a problem of unity8 clients, but also unity8 itself.
  I have no idea why horizontal/vertical swipes would be unaffected, though.

  The virtual keyboard is also completely unusable because of the huge
  delay that each tap has.

  Also noticed that the vibration is gone, taps don't trigger vibration
  anymore.

  Webview also seemed to be unaffected by the delays (although I'm not
  entirely sure, the bug is now gone)

  I also restarted unity8 and unity8-dash with Mir input logging enabled. That 
showed that the touch events were being delivered as expected, no delay.
  restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
  restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log

  Restarting lightdm (that forces the restart of unity-system-
  compositor) fixed the issue.

  Additional info: I had Mir touchspots visualization enabled, which are
  known to cause more stuttering, but I think they're unlikely to be the
  cause of this bug, I had them enabled for 2 weeks and haven't noticed
  any problem like this before.

  This is the log from a tap on an icon in the shell:
  [2016-09-06 10:52:51.876400]  input-receiver: Received 
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0, 
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963, 
minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.953821]  input-receiver: Received 
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0, 
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137, 
major=19.963, minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.954343]  input-receiver: Received 
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0, 
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963, 
minor=0, size=19.963}, modifiers=1)

  
  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1620297] Re: First scope not rendered until unlocked

[Paweł Stołowski]

Yep, the attached MP fixes the problem.

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

Title:
  First scope not rendered until unlocked

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

Bug description:
  The pre-populating of first scope on startup (before the screen is
  unlocked) doesn't seem to be fully working.

  My early investigation shows that the shell plugin correctly pre-
  populates scope model on startup when the screen is still locked, but
  after unlocking scope view is white for 1-2 seconds and only then the
  page is rendered and all the images are requested, so the perception
  is as if pre-population didn't work. The perceived performance depends
  on whether the 1st scope is a local scope (such as Apps) or a scope
  which needs remote images (and whether the images are already cached
  by the thumbnailer in the latter case).

  This might be caused by https://bugs.launchpad.net/qtmir/+bug/1475678

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

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

[Touch-packages] [Bug 1620567] [NEW] Avahi mistakenly detects a .local domain and disables itself

[Sulka Haro]

Public bug reported:

I have an issue where a mobile Intel Edison rig that uses Avahi switches
between WiFi hotspots using WPA Supplicant and the switch causing Avahi
to mistakenly detect the new network serves the .local domain when it
actually doesn't.

Steps to reproduce on in my case:

1) Configure a linux box to connect to the local wifi networks using
wpa_supplicant process, with multiple WPA networks being supported.

2) Shut down the primary network, so the box connects to the secondary
network (which is not connected to the primary and uses different DNS
servers).

3) Avahi randomly outputs the following following the switch and
requires the box to be rebooted. Following the reboot avahi has no issue
with the new network:

"Avahi detected that your currently configured local DNS server serves
a domain .local. This is inherently incompatible with Avahi and thus
Avahi disabled itself. If you want to use Avahi in this network, please
contact your administrator and convince him to use a different DNS domain,
since .local should be used exclusively for Zeroconf technology.
For more information, see http://avahi.org/wiki/AvahiAndUnicastDotLocal";

The issue also occurs upon switching from the secondary to the primary
network without a full reboot.

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

** Description changed:

  I have an issue where a mobile Intel Edison rig that uses Avahi switches
  between WiFi hotspots using WPA Supplicant and the switch causing Avahi
  to mistakenly detect the new network serves the .local domain when it
  actually doesn't.
  
  Steps to reproduce on in my case:
  
- 1) Configure a debian box to connect to the local wifi networks using
+ 1) Configure a linux box to connect to the local wifi networks using
  wpa_supplicant process, with multiple WPA networks being supported.
  
  2) Shut down the primary network, so the box connects to the secondary
  network (which is not connected to the primary and uses different DNS
  servers).
  
  3) Avahi randomly outputs the following following the switch and
  requires the box to be rebooted. Following the reboot avahi has no issue
  with the new network:
  
  "Avahi detected that your currently configured local DNS server serves
  a domain .local. This is inherently incompatible with Avahi and thus
  Avahi disabled itself. If you want to use Avahi in this network, please
  contact your administrator and convince him to use a different DNS domain,
  since .local should be used exclusively for Zeroconf technology.
  For more information, see http://avahi.org/wiki/AvahiAndUnicastDotLocal";
  
  The issue also occurs upon switching from the secondary to the primary
  network without a full reboot.

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

Title:
  Avahi mistakenly detects a .local domain and disables itself

Status in avahi package in Ubuntu:
  New

Bug description:
  I have an issue where a mobile Intel Edison rig that uses Avahi
  switches between WiFi hotspots using WPA Supplicant and the switch
  causing Avahi to mistakenly detect the new network serves the .local
  domain when it actually doesn't.

  Steps to reproduce on in my case:

  1) Configure a linux box to connect to the local wifi networks using
  wpa_supplicant process, with multiple WPA networks being supported.

  2) Shut down the primary network, so the box connects to the secondary
  network (which is not connected to the primary and uses different DNS
  servers).

  3) Avahi randomly outputs the following following the switch and
  requires the box to be rebooted. Following the reboot avahi has no
  issue with the new network:

  "Avahi detected that your currently configured local DNS server serves
  a domain .local. This is inherently incompatible with Avahi and thus
  Avahi disabled itself. If you want to use Avahi in this network, please
  contact your administrator and convince him to use a different DNS domain,
  since .local should be used exclusively for Zeroconf technology.
  For more information, see http://avahi.org/wiki/AvahiAndUnicastDotLocal";

  The issue also occurs upon switching from the secondary to the primary
  network without a full reboot.

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

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

[Touch-packages] [Bug 1620570] [NEW] Setting scale for menu and title bars > 1 makes window titles disappear.

[Lily Rivers]

Public bug reported:

If the value of the menu and title bars scale is set to anything higher
than 1 on any resolution then all window titles become invisible unless
they are in the unity top bar. The bug takes immediate affect and is
also applied to every login.

https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1332947 details
some information about the text scaling being doubled, I'm unsure if it
is related.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.6.0-040600-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
CurrentDesktop: Unity
Date: Tue Sep  6 11:46:22 2016
DistUpgraded: 2016-07-29 14:06:42,947 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
 virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed
 virtualbox, 5.0.24, 4.6.0-040600-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] 
(prog-if 00 [VGA controller])
   Subsystem: Hightech Information System Ltd. Juniper XT [Radeon HD 5770] 
[1787:200b]
InstallationDate: Installed on 2015-11-04 (306 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: MSI MS-7788
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.6.0-040600-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-07-29 (38 days ago)
dmi.bios.date: 09/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V3.6
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-P31/W8 (MS-7788)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.6:bd09/29/2013:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7788
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-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.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Sep  6 11:39:47 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB Optical MouseMOUSE, id 8
 inputLogitech USB Keyboard KEYBOARD, id 9
 inputLogitech USB Keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.3
xserver.video_driver: radeon

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


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

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

Title:
  Setting scale for menu and title bars > 1 makes window titles
  disappear.

Status in xorg package in Ubuntu:
  New

Bug description:
  If the value of the menu and title bars scale is set to anything
  higher than 1 on any resolution then all window titles become
  invisible unless they are in the unity top bar. The bug takes
  immediate affect and is also applied to every login.

  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1332947 details
  some information about the text scaling being doubled, I'm unsure if
  it is related.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600-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
  CurrentDesktop: Unity
  Date: Tue Sep  6 11:46:22 2016
  DistUpgraded: 2016-07-29 14:06:42,947 DEBUG icon theme changed, re-reading
  DistroCodename: xeni

[Touch-packages] [Bug 1584575] Re: /lib/systemd/system/lightdm.service file has no [Install] clause

[Launchpad Bug Tracker]

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

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

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

Title:
  /lib/systemd/system/lightdm.service file has no [Install] clause

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  This concerns lightdm 1.18.1-0ubuntu1 in Xenial.

  The /lib/systemd/system/lightdm.service file lacks an [Install]
  clause. Meaning, that if you do

  # systemctl disable display-manager

  to prevent LightDM from starting, running

  # systemctl enable lightdm

  does not restore the /etc/systemd/system/display-manager.service
  symlink, and thus does not re-enable LightDM to run at the next boot
  as intended.

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

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

[Touch-packages] [Bug 1573786] Re: gdb Process record does not support instruction 0xc5

[Launchpad Bug Tracker]

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

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

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

Title:
  gdb Process record does not support instruction 0xc5

Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  the 'process record' feature of gdb allows reverse debugging.  neato.
  but on Ubuntu-16.04 it fails to work, complaining about an unhandled
  instruction.

  % gdb simple 
  GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from simple...done.
  (gdb) b main
  Breakpoint 1 at 0x400db7: file 
/home/robl/work/mpich/src/mpi/romio/test/simple.c, line 26.
  (gdb) run
  Starting program: /home/robl/work/build/mpich-logfs/src/mpi/romio/test/simple 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

  Breakpoint 1, main (argc=1, argv=0x7fffd698)
  at /home/robl/work/mpich/src/mpi/romio/test/simple.c:26
  26  {
  (gdb) record
  (gdb) continue
  Continuing.
  Process record does not support instruction 0xc5 at address 0x77dee6e7.
  Process record: failed to record execution log.

  Program stopped.
  _dl_runtime_resolve_avx () at ../sysdeps/x86_64/dl-trampoline.h:81
  81  ../sysdeps/x86_64/dl-trampoline.h: No such file or directory.

  
  If we examine the address we see this:

  (gdb) x/i 0x77dee6e7
  => 0x77dee6e7 <_dl_runtime_resolve_avx+71>: vmovdqa %ymm0,(%rsp)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdb 7.11-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 15:34:03 2016
  InstallationDate: Installed on 2015-09-10 (225 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: gdb
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

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

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

[Touch-packages] [Bug 1620559] Re: /etc/resolv.conf is empty on snappy

[Martin Pitt]

This is a bug in systemd-networkd-resolvconf-update.service, apparently
/run/systemd/netif/state does not always get the received DNS servers.
This does not affect yakkety any more as this hackish thing is gone
entirely and replaced by resolved.

But it is still relevant for xenial which snappy is based on, so we need
to SRU it there.

Quick fix for snappy image builds until this is SRUed:

   sed '/^ExecStart=/ s!netif/state!& /run/systemd/netif/leases/* | sort
-u!' /lib/systemd/system/systemd-networkd-resolvconf-update.service

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  /etc/resolv.conf is empty on snappy

Status in Snappy:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress

Bug description:
  we currently have no working resolver on snappy installs,
  /etc/resolv.conf is the boilerplate one.

  on the low level we seem to have DNS from the DHCP server though

  ogra@localhost:~$ grep -r DNS= /run/systemd/netif
  /run/systemd/netif/leases/3:DNS=217.237.150.115 217.237.151.205
  /run/systemd/netif/links/3:DNS=217.237.150.115 217.237.151.205
  /run/systemd/netif/links/3:MDNS=no
  ogra@localhost:~$

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

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

[Touch-packages] [Bug 1543344] Re: QML Flickables scrolling with mouse wheel insanely fast

[Timo Jyrinki]

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

I think this bug can now be marked as duplicate of the better described
bug #1607240 which also has a ubuntu-system-settings sub-task.

** This bug has been marked a duplicate of bug 1607240
   Unity8 default mouse wheel speed seen by Mir clients is 7.0 (it should be 
1.0)

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

Title:
  QML Flickables scrolling with mouse wheel insanely fast

Status in Canonical System Image:
  Incomplete
Status in Canonical Pocket Desktop:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Scrolling QML Flickables with mouse wheel is way too fast.

  Steps:
  * connect a mouse to your device
  * scroll the wheel over the dash

  Expected:
  * scrolling sane

  Current:
  * scrolling insane

  The same can be observed with two-finger scrolling when using the
  virtual touchpad when you connect your device to an external screen.

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

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

[Touch-packages] [Bug 1590737] Re: Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1,

[Launchpad Bug Tracker]

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

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Failed to create OpenGL context for format QSurfaceFormat(version 2.0,
  options QFlags(), depthBufferSize 24, redBufferSize -1,
  greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1,
  stencilBufferSize 8, samples -1, swapBehavior 2, swapInterval 1,
  profile  0)  Aborted (core dumped)

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 + nvidia proprietary 340.96 drivers
  webbbrowser crashes with

  Failed to create OpenGL context for format QSurfaceFormat(version 2.0, 
options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, 
blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, 
swapBehavior 2, swapInterval 1, profile  0) 
  Aborted (core dumped)

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

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

[Touch-packages] [Bug 1580882] Re: [Intel Broadwell HDMI, Digital Out] Sound like half speed after suspend

[Dan Dascalescu]

** Summary changed:

- [, Intel Broadwell HDMI, Digital Out, HDMI] Sound like half speed
+ [Intel Broadwell HDMI, Digital Out] Sound like half speed after suspend

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

Title:
  [Intel Broadwell HDMI, Digital Out] Sound like half speed after
  suspend

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 all updates applied.

  Playback to headphones is just fine. If I switch output to one of my monitor, 
connected by HDMI, the soudn comes out there, but with half speed. That sounds 
kinda funny, but weird and not as it should.
  Maybe it is somehow related to suspend mode as it was fine a few days ago 
(after a reboot? Can't reboot now to test, sorry).

  I already tried sudo /sbin/alsa force-reload but that didn't do
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jott   3698 F pulseaudio
   /dev/snd/pcmC0D3p:   jott   3698 F...m pulseaudio
   /dev/snd/controlC0:  jott   3698 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 12 08:42:46 2016
  InstallationDate: Installed on 2016-04-25 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Internes Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [, Intel Broadwell HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 337321] Re: sfdisk doesn't accept blank for start value with -uS

[Ayan George]

** Changed in: util-linux (Ubuntu)
 Assignee: (unassigned) => Ayan George (ayan)

** Changed in: util-linux (Ubuntu)
   Status: New => Fix Released

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

Title:
  sfdisk doesn't accept blank for start value with -uS

Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: util-linux

  Release: 8.10
  util-linux: 2.14-1ubuntu2

  According to the man-page this should work:
  sfdisk -uS /dev/sdb << EOF
  63,546147,82,-
  ,512000
  EOF

  I got these values by creating the 256MB partition in fdisk, then list the 
values with sfdisk -l /dev/sdb and then deleting all partitions again in fdisk.
  The first line creates a 256MB Swap partition as /dev/sdb1. The second line 
should create a partition 512000 sectors large right behind that. The problem 
is that
  ,
  isn't being accepted, the problem seems to be omitting the starting point.
  The first line on it's own works.
  Only when I enter the correct starting point (546210) at the beginning of the 
second line it works.
  The problem seems to be -uS specific, -uM works.

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

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

[Touch-packages] [Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window

[Michael Thayer]

Just did a quick test after upgrading to 16.10.  I (still) see double
menus (both local and global) in a single window machine.  Should I
remove appmenu-qt* and try again?

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

Title:
  Empty menus in global app-menu in VirtualBox second window

Status in libdbusmenu-qt package in Ubuntu:
  New

Bug description:
  Reporting this following this IRC discussion:

  https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00

  The basic summary: when I run a two-screen/two-window virtual machine
  with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu,
  the menus are empty when the second screen window has the input focus.
  During start-up I get a number (55) of these messages on the console:

  Qt WARNING: void
  DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*,
  int, int, const QStringList&): No id for action

  and a number (7) of these:

  Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const
  QStringList&, DBusMenuLayoutItem&): Condition failed: menu

  Then another 55 of the first and two of the second.

  Looking at the interesting parts of the VirtualBox source code, I see
  that the menu items for the first window (menu displayed correctly)
  and the second (not displayed) share the same QAction objects.  A very
  quick guess is that this might be triggering the condition in
  DBusMenuExporterPrivate::addMenu().

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 18 15:44:00 2016
  Dependencies:
   gcc-5-base 5.4.0-6ubuntu1~16.04.1
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
   libstdc++6 5.4.0-6ubuntu1~16.04.1
  InstallationDate: Installed on 2016-05-31 (48 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libdbusmenu-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1532358] Re: flaky autopkgtests cause migration issues

[Marcus Tomlinson]

** Changed in: unity-scopes-shell (Ubuntu)
 Assignee: Pete Woods (pete-woods) => Marcus Tomlinson (marcustomlinson)

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

Title:
  flaky autopkgtests cause migration issues

Status in Canonical System Image:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  Triaged

Bug description:
  A few times recently when unity8 got into xenial-proposed for
  migration, unity-scope-click's autopkgtest failed on the first run,
  having passed on the next:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/u/unity-scope-click/20160105_174239@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/u/unity-scope-click/20160108_185317@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ci-train-ppa-service-landing-030/xenial/armhf/u/unity-scope-click/20160111_213558@/log.gz

  This delays migration until someone notices the failure and asks for a
  re-run, which usually passes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-scope-click 0.1.1+16.04.20151216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jan  9 00:29:21 2016
  SourcePackage: unity-scope-click
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (72 days ago)

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

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

[Touch-packages] [Bug 1620559] Re: /etc/resolv.conf is empty on snappy

[Martin Pitt]

** Tags added: hw-specific

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

Title:
  /etc/resolv.conf is empty on snappy

Status in Snappy:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress

Bug description:
  we currently have no working resolver on snappy installs,
  /etc/resolv.conf is the boilerplate one.

  on the low level we seem to have DNS from the DHCP server though

  ogra@localhost:~$ grep -r DNS= /run/systemd/netif
  /run/systemd/netif/leases/3:DNS=217.237.150.115 217.237.151.205
  /run/systemd/netif/links/3:DNS=217.237.150.115 217.237.151.205
  /run/systemd/netif/links/3:MDNS=no
  ogra@localhost:~$

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

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

[Touch-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by lo

[Paolo Pelloni]

Same issue here on a Dell Vostro 1700 with Ubuntu 16.04.

Linux briga-laptop 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

[ 3125.120019] iwl3945 :0c:00.0: Queue 4 stuck for 2500 ms.
[ 3125.120026] iwl3945 :0c:00.0: On demand firmware reload
[ 3125.125835] ieee80211 phy0: Hardware restart was requested
[ 3125.173756] iwl3945 :0c:00.0: BSM uCode verification failed at addr 
0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020
[ 3125.173761] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5
[ 3125.220478] iwl3945 :0c:00.0: BSM uCode verification failed at addr 
0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020
[ 3125.220481] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5
[ 3125.267181] iwl3945 :0c:00.0: BSM uCode verification failed at addr 
0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020
[ 3125.267185] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5
[ 3125.313896] iwl3945 :0c:00.0: BSM uCode verification failed at addr 
0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020
[ 3125.313900] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5
[ 3125.360606] iwl3945 :0c:00.0: BSM uCode verification failed at addr 
0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020
[ 3125.360614] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5
[ 3125.397069] iwl3945 :0c:00.0: Unable to initialize device after 5 
attempts.
[ 3125.397077] [ cut here ]
[ 3125.397139] WARNING: CPU: 0 PID: 4936 at 
/build/linux-a2WvEb/linux-4.4.0/net/mac80211/util.c:1818 
ieee80211_reconfig+0x1e0/0xf80 [mac80211]()
[ 3125.397141] Hardware became unavailable during restart.
[ 3125.397143] Modules linked in: drbg ansi_cprng ctr ccm binfmt_misc 
nvidia_uvm(POE) gpio_ich dell_wmi sparse_keymap dell_laptop dcdbas coretemp 
dell_smm_hwmon kvm_intel kvm irqbypass input_leds serio_raw nvidia(POE) lpc_ich 
uvcvideo arc4 iwl3945 videobuf2_vmalloc videobuf2_memops iwlegacy 
videobuf2_v4l2 videobuf2_core joydev snd_hda_codec_hdmi v4l2_common mac80211 
videodev r852 sm_common media nand snd_hda_codec_idt snd_hda_codec_generic 
nand_ecc nand_bch bch snd_hda_intel nand_ids r592 snd_hda_codec mtd cfg80211 
memstick snd_hda_core snd_hwdep snd_pcm drm snd_seq_midi snd_seq_midi_event 
snd_rawmidi wmi mac_hid snd_seq snd_seq_device snd_timer snd soundcore shpchp 
parport_pc ppdev lp parport autofs4 ses enclosure hid_generic psmouse usbhid 
hid firewire_ohci firewire_core uas crc_itu_t b44 ssb sdhci_pci
[ 3125.397226]  mii sdhci pata_acpi usb_storage video
[ 3125.397235] CPU: 0 PID: 4936 Comm: kworker/0:2 Tainted: P   OE   
4.4.0-36-generic #55-Ubuntu
[ 3125.397238] Hardware name: Dell Inc. Vostro 1700 
/0HX767, BIOS A07 04/21/2008
[ 3125.397261] Workqueue: events_freezable ieee80211_restart_work [mac80211]
[ 3125.397264]  0286 122297b0 88006c84fcf0 
813f13b3
[ 3125.397269]  88006c84fd38 c0410930 88006c84fd28 
810810f2
[ 3125.397273]  8800b8c70700 fffb 8800b8c70700 

[ 3125.397277] Call Trace:
[ 3125.397288]  [] dump_stack+0x63/0x90
[ 3125.397294]  [] warn_slowpath_common+0x82/0xc0
[ 3125.397298]  [] warn_slowpath_fmt+0x5c/0x80
[ 3125.397325]  [] ? drv_start+0x44/0x110 [mac80211]
[ 3125.397358]  [] ieee80211_reconfig+0x1e0/0xf80 [mac80211]
[ 3125.397364]  [] ? mutex_lock+0x12/0x30
[ 3125.397389]  [] ieee80211_restart_work+0x6b/0xa0 [mac80211]
[ 3125.397395]  [] process_one_work+0x165/0x480
[ 3125.397399]  [] worker_thread+0x4b/0x4c0
[ 3125.397403]  [] ? process_one_work+0x480/0x480
[ 3125.397406]  [] ? process_one_work+0x480/0x480
[ 3125.397410]  [] kthread+0xd8/0xf0
[ 3125.397414]  [] ? kthread_create_on_node+0x1e0/0x1e0
[ 3125.397419]  [] ret_from_fork+0x3f/0x70
[ 3125.397422]  [] ? kthread_create_on_node+0x1e0/0x1e0
[ 3125.397425] ---[ end trace fba2cc789462e954 ]---
[ 3125.397489] wlp12s0: deauthenticating from f4:f2:6d:98:6d:a4 by local choice 
(Reason: 3=DEAUTH_LEAVING)
[ 3125.397503] [ cut here ]
[ 3125.397526] WARNING: CPU: 0 PID: 4936 at 
/build/linux-a2WvEb/linux-4.4.0/net/mac80211/driver-ops.h:12 
ieee80211_bss_info_change_notify+0x1be/0x1d0 [mac80211]()
[ 3125.397529] wlp12s0:  Failed check-sdata-in-driver check, flags: 0x4
[ 3125.397530] Modules linked in: drbg ansi_cprng ctr ccm binfmt_misc 
nvidia_uvm(POE) gpio_ich dell_wmi sparse_keymap dell_laptop dcdbas coretemp 
dell_smm_hwmon kvm_intel kvm irqbypass input_leds serio_raw nvidia(POE) lpc_ich 
uvcvideo arc4 iwl3945 videobuf2_vmalloc videobuf2_memops iwlegacy 
videobuf2_v4l2 videobuf2_core joydev snd_hda_codec_hdmi v4l2_common mac80211 
videodev r852 sm_common media nand snd_hda_codec_idt snd_hda_codec_generic 
nand_ecc nand_bch bch snd_hda_intel nand_ids r592 snd_hda_codec mtd cfg80211 
memstick snd_hda_core snd_hwdep snd_pcm drm snd_seq_midi snd_seq_midi_event 
snd_rawmidi wmi mac_hid snd_seq snd_seq_device s

[Touch-packages] [Bug 1565804] Re: ifup of vlan interfaces failing during networking start - RTNETLINK answers: File exists

[Kees Hoekzema]

I had/have sort of the same problem, when running the network startup it
somehow wants to set up my vlans twice; i think when i do the 'master'
interface, and once when it sets up the normal interface.

The first time it just sets up the vlan and assigns an address. The
second time it tries to add that address again, but that obviously fails
with an 'RTNETLINK answers: File exists'

And because the default (since 2014?) is to treat any error as fatal it
just stops configuring the interface even tho it would be perfectly ok
to at least try to set, for example, the default route or the 'up'
statements. But no, a small step failed so it's better to leave the
interface half configured.

On Ubuntu 16.04 this can be worked around by adding
"EXCLUDE_INTERFACES=' --ignore-errors' " to /etc/default/networking so
ifupdown does the sensible thing and tries to continue after an error
instead of leaving a half configured interface.

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

Title:
  ifup of vlan interfaces failing during networking start - RTNETLINK
  answers: File exists

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  /e/n/i:

  auto lo
  iface lo inet loopback
  dns-nameservers 10.245.168.2
  dns-search dellstack
  auto eth0
  iface eth0 inet static
  gateway 10.245.168.1
  address 10.245.168.17/21
  dns-nameservers 10.245.168.2
  mtu 1500

  auto eth1
  iface eth1 inet manual
  mtu 1500

  auto eth1.2667
  iface eth1.2667 inet static
  address 10.245.184.20/24
  vlan-raw-device eth1
  mtu 9000
  vlan_id 2667

  output from networking startup:

  ● networking.service - Raise network interfaces
 Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor 
preset: enabled)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
 Active: failed (Result: exit-code) since Mon 2016-04-04 12:14:26 UTC; 1h 
33min ago
   Docs: man:interfaces(5)
Process: 1255 ExecStart=/sbin/ifup -a --read-environment (code=exited, 
status=1/FAILURE)
Process: 868 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && 
[ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle 
(code=exited, 
   Main PID: 1255 (code=exited, status=1/FAILURE)

  Apr 04 12:14:25 reflecting-attraction systemd[1]: Starting Raise network 
interfaces...
  Apr 04 12:14:26 reflecting-attraction ifup[1255]: Set name-type for VLAN 
subsystem. Should be visible in /proc/net/vlan/config
  Apr 04 12:14:26 reflecting-attraction ifup[1255]: RTNETLINK answers: File 
exists
  Apr 04 12:14:26 reflecting-attraction ifup[1255]: Failed to bring up 
eth1.2667.
  Apr 04 12:14:26 reflecting-attraction systemd[1]: networking.service: Main 
process exited, code=exited, status=1/FAILURE
  Apr 04 12:14:26 reflecting-attraction systemd[1]: Failed to start Raise 
network interfaces.
  Apr 04 12:14:26 reflecting-attraction systemd[1]: networking.service: Unit 
entered failed state.
  Apr 04 12:14:26 reflecting-attraction systemd[1]: networking.service: Failed 
with result 'exit-code'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1
  ProcVersionSignature: User Name 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Mon Apr  4 13:42:48 2016
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1620559] Re: /etc/resolv.conf is empty on snappy

[Martin Pitt]

** Description changed:

  we currently have no working resolver on snappy installs,
  /etc/resolv.conf is the boilerplate one.
  
  on the low level we seem to have DNS from the DHCP server though
  
  ogra@localhost:~$ grep -r DNS= /run/systemd/netif
  /run/systemd/netif/leases/3:DNS=217.237.150.115 217.237.151.205
  /run/systemd/netif/links/3:DNS=217.237.150.115 217.237.151.205
  /run/systemd/netif/links/3:MDNS=no
  ogra@localhost:~$
+ 
+ SRU INFORMATION
+ ===
+ Test case:
+ 
+ I cannot reproduce this in a VM or normal laptop, this is somehow
+ specific to the reporter's hardware/DHCP server config.
+ 
+  * Configure systemd-networkd for an ethernet interface, either directly or 
via netplan; remove it from /etc/network/interfaces{,.d}
+  * Reboot.
+  * With current xenial's systemd, if /run/systemd/netif/state does not have 
"DNS=" then /etc/resolv.conf will not have any nameserver.
+  * With the proposed update, /etc/resolv.conf should have the DHCP-provided 
nameserver.
+ 
+ Regression potential: Low; in 16.04 LTS we do not configure networkd by
+ any Ubuntu tool, so networkd is not widely used there yet. For systems
+ which do use it it could happen that interface-specific DNS servers now
+ appear in resolv.conf that should not be global -- but we do not have
+ anything that would configure or obey this setup in 16.04.

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

Title:
  /etc/resolv.conf is empty on snappy

Status in Snappy:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress

Bug description:
  we currently have no working resolver on snappy installs,
  /etc/resolv.conf is the boilerplate one.

  on the low level we seem to have DNS from the DHCP server though

  ogra@localhost:~$ grep -r DNS= /run/systemd/netif
  /run/systemd/netif/leases/3:DNS=217.237.150.115 217.237.151.205
  /run/systemd/netif/links/3:DNS=217.237.150.115 217.237.151.205
  /run/systemd/netif/links/3:MDNS=no
  ogra@localhost:~$

  SRU INFORMATION
  ===
  Fix: 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=0a96feb1561

  
  Test case:

  I cannot reproduce this in a VM or normal laptop, this is somehow
  specific to the reporter's hardware/DHCP server config.

   * Configure systemd-networkd for an ethernet interface, either directly or 
via netplan; remove it from /etc/network/interfaces{,.d}
   * Reboot.
   * With current xenial's systemd, if /run/systemd/netif/state does not have 
"DNS=" then /etc/resolv.conf will not have any nameserver.
   * With the proposed update, /etc/resolv.conf should have the DHCP-provided 
nameserver.

  Regression potential: Low; in 16.04 LTS we do not configure networkd
  by any Ubuntu tool, so networkd is not widely used there yet. For
  systems which do use it it could happen that interface-specific DNS
  servers now appear in resolv.conf that should not be global -- but we
  do not have anything that would configure or obey this setup in 16.04.

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

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

[Touch-packages] [Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window

[Dmitry Shachnev]

Yes, please remove appmenu-qt5 or unset QT_QPA_PLATFORMTHEME env
variable.

This needs today’s qtbase 5.6.1+dfsg-3ubuntu3~3 which may be not yet
available on your mirrors.

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

Title:
  Empty menus in global app-menu in VirtualBox second window

Status in libdbusmenu-qt package in Ubuntu:
  New

Bug description:
  Reporting this following this IRC discussion:

  https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00

  The basic summary: when I run a two-screen/two-window virtual machine
  with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu,
  the menus are empty when the second screen window has the input focus.
  During start-up I get a number (55) of these messages on the console:

  Qt WARNING: void
  DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*,
  int, int, const QStringList&): No id for action

  and a number (7) of these:

  Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const
  QStringList&, DBusMenuLayoutItem&): Condition failed: menu

  Then another 55 of the first and two of the second.

  Looking at the interesting parts of the VirtualBox source code, I see
  that the menu items for the first window (menu displayed correctly)
  and the second (not displayed) share the same QAction objects.  A very
  quick guess is that this might be triggering the condition in
  DBusMenuExporterPrivate::addMenu().

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 18 15:44:00 2016
  Dependencies:
   gcc-5-base 5.4.0-6ubuntu1~16.04.1
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
   libstdc++6 5.4.0-6ubuntu1~16.04.1
  InstallationDate: Installed on 2016-05-31 (48 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libdbusmenu-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1620559] Re: /etc/resolv.conf is empty on snappy

[Martin Pitt]

** Description changed:

  we currently have no working resolver on snappy installs,
  /etc/resolv.conf is the boilerplate one.
  
  on the low level we seem to have DNS from the DHCP server though
  
  ogra@localhost:~$ grep -r DNS= /run/systemd/netif
  /run/systemd/netif/leases/3:DNS=217.237.150.115 217.237.151.205
  /run/systemd/netif/links/3:DNS=217.237.150.115 217.237.151.205
  /run/systemd/netif/links/3:MDNS=no
  ogra@localhost:~$
  
  SRU INFORMATION
  ===
+ Fix: 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=0a96feb1561
+ 
+ 
  Test case:
  
  I cannot reproduce this in a VM or normal laptop, this is somehow
  specific to the reporter's hardware/DHCP server config.
  
-  * Configure systemd-networkd for an ethernet interface, either directly or 
via netplan; remove it from /etc/network/interfaces{,.d}
-  * Reboot.
-  * With current xenial's systemd, if /run/systemd/netif/state does not have 
"DNS=" then /etc/resolv.conf will not have any nameserver.
-  * With the proposed update, /etc/resolv.conf should have the DHCP-provided 
nameserver.
+  * Configure systemd-networkd for an ethernet interface, either directly or 
via netplan; remove it from /etc/network/interfaces{,.d}
+  * Reboot.
+  * With current xenial's systemd, if /run/systemd/netif/state does not have 
"DNS=" then /etc/resolv.conf will not have any nameserver.
+  * With the proposed update, /etc/resolv.conf should have the DHCP-provided 
nameserver.
  
  Regression potential: Low; in 16.04 LTS we do not configure networkd by
  any Ubuntu tool, so networkd is not widely used there yet. For systems
  which do use it it could happen that interface-specific DNS servers now
  appear in resolv.conf that should not be global -- but we do not have
  anything that would configure or obey this setup in 16.04.

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

Title:
  /etc/resolv.conf is empty on snappy

Status in Snappy:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress

Bug description:
  we currently have no working resolver on snappy installs,
  /etc/resolv.conf is the boilerplate one.

  on the low level we seem to have DNS from the DHCP server though

  ogra@localhost:~$ grep -r DNS= /run/systemd/netif
  /run/systemd/netif/leases/3:DNS=217.237.150.115 217.237.151.205
  /run/systemd/netif/links/3:DNS=217.237.150.115 217.237.151.205
  /run/systemd/netif/links/3:MDNS=no
  ogra@localhost:~$

  SRU INFORMATION
  ===
  Fix: 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial&id=0a96feb1561

  
  Test case:

  I cannot reproduce this in a VM or normal laptop, this is somehow
  specific to the reporter's hardware/DHCP server config.

   * Configure systemd-networkd for an ethernet interface, either directly or 
via netplan; remove it from /etc/network/interfaces{,.d}
   * Reboot.
   * With current xenial's systemd, if /run/systemd/netif/state does not have 
"DNS=" then /etc/resolv.conf will not have any nameserver.
   * With the proposed update, /etc/resolv.conf should have the DHCP-provided 
nameserver.

  Regression potential: Low; in 16.04 LTS we do not configure networkd
  by any Ubuntu tool, so networkd is not widely used there yet. For
  systems which do use it it could happen that interface-specific DNS
  servers now appear in resolv.conf that should not be global -- but we
  do not have anything that would configure or obey this setup in 16.04.

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

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

[Touch-packages] [Bug 1620599] [NEW] package libcurl3-gnutls 7.47.0-1ubuntu2 failed to install/upgrade: sub-processo comando rm para limpar retornou estado de saída de erro 2

[Laiali]

Public bug reported:

eu não sei que erro é esse, mas aparece uma janelinha toda hora dizendo
pra relatar o problema

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libcurl3-gnutls 7.47.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
AptOrdering:
 curl: Install
 libcurl3-gnutls: Install
 libcurl3-gnutls: Configure
 curl: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Sun Sep  4 21:41:30 2016
ErrorMessage: sub-processo comando rm para limpar retornou estado de saída de 
erro 2
InstallationDate: Installed on 2016-05-11 (117 days ago)
InstallationMedia: It
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: curl
Title: package libcurl3-gnutls 7.47.0-1ubuntu2 failed to install/upgrade: 
sub-processo comando rm para limpar retornou estado de saída de erro 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libcurl3-gnutls 7.47.0-1ubuntu2 failed to install/upgrade:
  sub-processo comando rm para limpar retornou estado de saída de erro 2

Status in curl package in Ubuntu:
  New

Bug description:
  eu não sei que erro é esse, mas aparece uma janelinha toda hora
  dizendo pra relatar o problema

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libcurl3-gnutls 7.47.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   curl: Install
   libcurl3-gnutls: Install
   libcurl3-gnutls: Configure
   curl: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Sep  4 21:41:30 2016
  ErrorMessage: sub-processo comando rm para limpar retornou estado de saída de 
erro 2
  InstallationDate: Installed on 2016-05-11 (117 days ago)
  InstallationMedia: It
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: curl
  Title: package libcurl3-gnutls 7.47.0-1ubuntu2 failed to install/upgrade: 
sub-processo comando rm para limpar retornou estado de saída de erro 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1620338] Re: Ubuntu One account page is blank

[Alberto Mardegan]

Adding U1 project; given that the other plugins work, it's possible that
the problem is in U1.

** Also affects: ubuntuone-credentials (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Ubuntu One account page is blank

Status in Canonical System Image:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in ubuntuone-credentials package in Ubuntu:
  New

Bug description:
  current build number: 31
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

  The U1 account page is blank with just a title.

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

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

[Touch-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by lo

[Christopher M. Penalver]

Peter Ullinger, thank you for taking the time to report this bug and helping to 
make Ubuntu better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1408963

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Tags added: trusty utopic vivid

** No longer affects: linux-firmware (Ubuntu)

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
  :03:00.0: BSM uCode verification failed at addr ...; wlan0:
  deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1600124] Re: Adjust KBL PCI-ID's

[Martin Pitt]

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

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

Title:
  Adjust KBL PCI-ID's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in libdrm source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Released

Bug description:
  Current list of KBL PCI-ID's is incomplete, there are a few that are
  should not be listed and few that are missing. To fix this, adjust the
  list in kernel/libdrm/mesa/ddx to match upstream.

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

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

[Touch-packages] [Bug 1577735] Update Released

[Martin Pitt]

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

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

Title:
  Add missing SKL/BXT PCI-ID's

Status in libdrm package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Trusty:
  Fix Released
Status in libdrm source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Some GPU PCI-ID's are missing from libdrm (SKL, BXT) & mesa (BXT),
  these need to be added.

  [Test case]

  own such hw, run a desktop session and check that it's using native
  drivers

  [Regression potential]

  none

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

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

[Touch-packages] [Bug 1603175] Re: No resolution configuration available

[Matthew Paul Thomas]

** Description changed:

  In my desktop unity8 is clearly in the wrong resolution:
-  - the font in the titlebar is quite pixelated
-  - the cursor is huge
+  - the font in the titlebar is quite pixelated
+  - the cursor is huge
  
  It would be required to have a setting like the one in unity7 to set the
  correct resolution of the screen.
+ 
+ : “
+ ‘Resolution:’ radio menu should have options for each available
+ resolution for the display…”

** Changed in: ubuntu-ux
   Status: New => Fix Committed

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Confirmed => 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/1603175

Title:
  No resolution configuration available

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  In my desktop unity8 is clearly in the wrong resolution:
   - the font in the titlebar is quite pixelated
   - the cursor is huge

  It would be required to have a setting like the one in unity7 to set
  the correct resolution of the screen.

  : “
  ‘Resolution:’ radio menu should have options for each available
  resolution for the display…”

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

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

[Touch-packages] [Bug 1615474] Re: Wifi networking no longer possible, network indicator broken

[Matthew Exon]

Hi Alejandro, sorry I only just noticed your reply.

It's a little hard to get data off my phone at the moment.  But
indicator network is running:

2479 ? Ssl 0:00 
/usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-secret-agent
2539 ? Ssl 0:07 
/usr/lib/arm-linux-dnueabihf/indicator-network/indicator-network-service

I've been trying to use wpa_supplicant as you suggested but it
continually fails to connect, complaining about authentication timeouts.
I'm not sure if I'e got the right device driver.  I'm running:

sudo wpa_supplicant -Dwext -iwlan0 -cwpa.conf

It does understand the network's MAC and frequency, so I guess it's
talking to the driver OK.  This is with two different access points.

Also, wpa_supplicant is already running.  I can kill it but it just
comes back.

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

Title:
  Wifi networking no longer possible, network indicator broken

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

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

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

[Touch-packages] [Bug 1577735] Re: Add missing SKL/BXT PCI-ID's

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 11.2.0-1ubuntu2.2

---
mesa (11.2.0-1ubuntu2.2) xenial; urgency=medium

  * bxt-add-2x6-variant.diff:
Update BXT pciids. (LP: #1577735)
  * add-more-kbl-pciids.diff,
remove-obsolete-kbl-pciids.diff:
Update i965 pciids. (LP: #1600124)

 -- Timo Aaltonen   Wed, 03 Aug 2016 11:45:31 +0300

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

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

Title:
  Add missing SKL/BXT PCI-ID's

Status in libdrm package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Trusty:
  Fix Released
Status in libdrm source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Some GPU PCI-ID's are missing from libdrm (SKL, BXT) & mesa (BXT),
  these need to be added.

  [Test case]

  own such hw, run a desktop session and check that it's using native
  drivers

  [Regression potential]

  none

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

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

[Touch-packages] [Bug 1600124] Re: Adjust KBL PCI-ID's

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 11.2.0-1ubuntu2.2

---
mesa (11.2.0-1ubuntu2.2) xenial; urgency=medium

  * bxt-add-2x6-variant.diff:
Update BXT pciids. (LP: #1577735)
  * add-more-kbl-pciids.diff,
remove-obsolete-kbl-pciids.diff:
Update i965 pciids. (LP: #1600124)

 -- Timo Aaltonen   Wed, 03 Aug 2016 11:45:31 +0300

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

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

Title:
  Adjust KBL PCI-ID's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in libdrm source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Released

Bug description:
  Current list of KBL PCI-ID's is incomplete, there are a few that are
  should not be listed and few that are missing. To fix this, adjust the
  list in kernel/libdrm/mesa/ddx to match upstream.

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

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

[Touch-packages] [Bug 1471998] Re: [enhancement] Support copy-paste between X and Mir

[Launchpad Bug Tracker]

** Branch linked: lp:libertine

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

Title:
  [enhancement] Support copy-paste between X and Mir

Status in Canonical System Image:
  Fix Committed
Status in Libertine:
  Fix Committed
Status in Libertine devel series:
  Fix Committed
Status in Libertine trunk series:
  Fix Committed
Status in Mir:
  Fix Released
Status in content-hub package in Ubuntu:
  In Progress
Status in libertine package in Ubuntu:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  X applications should be able to paste from Mir applications and vice
  versa.

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

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

[Touch-packages] [Bug 1615449] Update Released

[Martin Pitt]

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

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

Title:
  Use upstream manpages instead of stub Debian-provided man page

Status in p11-kit package in Ubuntu:
  Fix Released
Status in p11-kit source package in Xenial:
  Fix Released

Bug description:
  Impact
  ==
  The Debian provided stub manpage is not very useful. Now that upstream 
includes manpages, we should build and ship those instead.

  This replaces p11-kit1. with the much more verbose and useful
  trust.1, pkcs11.conf.5 and p11-kit.8

  Test Case
  
  Run man p11-kit, man trust and man pkcs11.conf

  Regression Potential
  
  For yakkety, please sync p11-kit 0.23.2-5.

  For xenial, I am including a debdiff to backport the changes from
  0.23.2-4 and 0.23.2-5 with the exception of enabling all hardening
  flags since I think the SRU policy discourages making changes like
  that.

  0.23.2-4 updates the package descriptions in debian/control.

  Please sync p11-kit 0.23.2-5 (main) from Debian unstable (main)

  Changelog entries since current yakkety version 0.23.2-4:

  p11-kit (0.23.2-5) unstable; urgency=medium

* Build and ship upstream manpages. (Thanks, Julien Cristau)
  + Add b-d on gtk-doc-tools.
  + Pass --enable-doc to ./configure.
  + Drop minimal debian/p11-kit.1 manpage.
  Closes: #834992

   -- Andreas Metzler   Sun, 21 Aug 2016 16:03:45
  +0200

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

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

[Touch-packages] [Bug 1615449] Re: Use upstream manpages instead of stub Debian-provided man page

[Launchpad Bug Tracker]

This bug was fixed in the package p11-kit - 0.23.2-5~ubuntu16.04.1

---
p11-kit (0.23.2-5~ubuntu16.04.1) xenial-proposed; urgency=medium

  * Backport to Ubuntu 16.04 LTS for improved manpages (LP: #1615449)
  * Don't enable hardening flags to keep this change minimal.

p11-kit (0.23.2-5) unstable; urgency=medium

  * Build and ship upstream manpages. (Thanks, Julien Cristau)
+ Add b-d on gtk-doc-tools.
+ Pass --enable-doc to ./configure.
+ Drop minimal debian/p11-kit.1 manpage.
Closes: #834992

p11-kit (0.23.2-4) unstable; urgency=medium

  * Move Vcs-* from git/http to https.
  * Improved package description by Justin B Rye. Closes: #822860
  * Build with hardening=+all.

 -- Jeremy Bicha   Sun, 21 Aug 2016 20:43:56 -0400

** Changed in: p11-kit (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Use upstream manpages instead of stub Debian-provided man page

Status in p11-kit package in Ubuntu:
  Fix Released
Status in p11-kit source package in Xenial:
  Fix Released

Bug description:
  Impact
  ==
  The Debian provided stub manpage is not very useful. Now that upstream 
includes manpages, we should build and ship those instead.

  This replaces p11-kit1. with the much more verbose and useful
  trust.1, pkcs11.conf.5 and p11-kit.8

  Test Case
  
  Run man p11-kit, man trust and man pkcs11.conf

  Regression Potential
  
  For yakkety, please sync p11-kit 0.23.2-5.

  For xenial, I am including a debdiff to backport the changes from
  0.23.2-4 and 0.23.2-5 with the exception of enabling all hardening
  flags since I think the SRU policy discourages making changes like
  that.

  0.23.2-4 updates the package descriptions in debian/control.

  Please sync p11-kit 0.23.2-5 (main) from Debian unstable (main)

  Changelog entries since current yakkety version 0.23.2-4:

  p11-kit (0.23.2-5) unstable; urgency=medium

* Build and ship upstream manpages. (Thanks, Julien Cristau)
  + Add b-d on gtk-doc-tools.
  + Pass --enable-doc to ./configure.
  + Drop minimal debian/p11-kit.1 manpage.
  Closes: #834992

   -- Andreas Metzler   Sun, 21 Aug 2016 16:03:45
  +0200

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

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

[Touch-packages] [Bug 1471998] Re: [enhancement] Support copy-paste between X and Mir

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: In Progress => Fix Committed

** Changed in: libertine/devel
   Status: In Progress => Fix Committed

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

Title:
  [enhancement] Support copy-paste between X and Mir

Status in Canonical System Image:
  Fix Committed
Status in Libertine:
  Fix Committed
Status in Libertine devel series:
  Fix Committed
Status in Libertine trunk series:
  Fix Committed
Status in Mir:
  Fix Released
Status in content-hub package in Ubuntu:
  In Progress
Status in libertine package in Ubuntu:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  X applications should be able to paste from Mir applications and vice
  versa.

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

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

[Touch-packages] [Bug 1618390] Re: dbus-cpp crash on arm64 in core::dbus::Object::get_property

[Timo Jyrinki]

location-service (3.0.0+16.04.20160811-0ubuntu2~xenialoverlay1) xenial;
urgency=medium

  * No change rebuild for xenial (LP: #1618390)

 -- Timo Jyrinki   Tue, 06 Sep 2016 12:23:11
+0300


mtp (0.0.4+16.04.20160413-0ubuntu3~xenialoverlay1) xenial; urgency=medium

  * No change rebuild for xenial (LP: #1618390)

 -- Timo Jyrinki   Tue, 06 Sep 2016 12:23:37
+0300

https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-
phone-overlay/+sourcepub/6859582/+listing-archive-extra

https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-
phone-overlay/+sourcepub/6859583/+listing-archive-extra

** Changed in: mtp (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: location-service (Ubuntu)
   Status: In Progress => Fix Released

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

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

Title:
  dbus-cpp crash on arm64 in core::dbus::Object::get_property

Status in Canonical System Image:
  Fix Committed
Status in dbus-cpp package in Ubuntu:
  Invalid
Status in location-service package in Ubuntu:
  Fix Released
Status in mtp package in Ubuntu:
  Fix Released

Bug description:
  Requests to location service cause crashes on arm64:

  $ system-image-cli -i
  current build number: 23
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-08-30 09:13:12
  version version: 23
  version ubuntu: 20160830
  version device: 20160824.0
  version custom: 20160830

  Steps:
  * flash the above channel (remember --device frieza_arm64)
  * go to a scope using location
  * refresh

  == Stacktrace =
  #0  0x007f978d4328 in 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, 
__mem=0x29) at /usr/include/c++/5/ext/atomicity.h:49
  __val = -1
  __mem = 0x29
  #1  0x007f978d4328 in 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, 
__mem=0x29) at /usr/include/c++/5/ext/atomicity.h:82
  __val = -1
  __mem = 0x29
  #2  0x007f978d4328 in 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (this=0x21) at 
/usr/include/c++/5/bits/shared_ptr_base.h:147
  #3  0x007f97922a28 in 
std::__shared_count<(__gnu_cxx::_Lock_policy)2>::operator=(std::__shared_count<(__gnu_cxx::_Lock_policy)2>
 const&) (this=this@entry=0x8b34558, __r=...) at 
/usr/include/c++/5/bits/shared_ptr_base.h:678
  __tmp = 0x8b34ba0
  #4  0x007f9792cc64 in 
core::dbus::Object::get_property()
 (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr_base.h:867
  property = 
  #5  0x007f9792cc64 in 
core::dbus::Object::get_property()
 (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr.h:93
  property = 
  #6  0x007f9792cc64 in 
core::dbus::Object::get_property()
 (this=0x8b342c0) at /usr/include/core/dbus/impl/object.h:162
  property = 
  #7  0x007f97931c08 in 
com::ubuntu::location::service::Stub::Stub(std::shared_ptr 
const&) (object=warning: can't find linker symbol for virtual table for 
`std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value
  warning: can't find linker symbol for virtual table for 
`std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libubuntu-location-service3 3.0.0+16.04.20160811-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: arm64
  Date: Tue Aug 30 09:39:24 2016
  SourcePackage: location-service
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: arm64
  DistroRelease: Ubuntu 16.04
  Package: mtp-server 0.0.4+16.04.20160413-0ubuntu2 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  PackageArchitecture: arm64
  Tags: third-party-packages xenial
  Uname: Linux 3.10.93+ aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip plugdev sudo tty video
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1620338] Re: Ubuntu One account page is blank

[Marcus Tomlinson]

For reference, here's our conversation from #ubuntu-touch last week:

15:43 mardy: marcustomlinson: can you get the logs with OAU_LOGGING_LEVEL=2 
OAU_DAEMON_TIMEOUT= online-accounts-service?
16:04 marcustomlinson: mardy: https://pastebin.canonical.com/164515/
16:14 marcustomlinson: mardy: my ~/.local/share/accounts/qml-plugins/ folder is 
empty, is that bad?
16:14 marcustomlinson: mardy: line 50 of that log: 
file:///home/marcustomlinson/.local/share/accounts/qml-plugins/ubuntuone/Main.qml:
 File not found
16:14 mardy: marcustomlinson: no, it just means that you have not any plugins 
installed from click packages
16:15 mardy: marcustomlinson, dobey: the error is in the last line of the logs
16:18 mardy: marcustomlinson: can you edit 
/usr/share/accounts/qml-plugins/ubuntuone/Main.qml and print the Loader's 
"status" as it changes?
16:19 mardy: marcustomlinson: also try commenting out line 45, it looks 
suspicious
16:19 mardy: (the sourceComponent one)
16:28 marcustomlinson: mardy: did what you said. log is exactly the same: 
https://pastebin.canonical.com/164524/
16:32 mardy: marcustomlinson: is it Qt 5.6 or 5.5?
16:33 dobey: oh yeah, maybe you need to dist-upgrade
16:36 mardy: dobey: the last line of marcustomlinson's logs doesn't appear on 
the phone
16:37 mardy: dobey: I suspect that that property binding happens to work in qt 
5.5, but broke with 5.6
16:37 dobey: mardy: weren't you trying to land 5.6 to vivid too?
16:37 mardy: dobey: indeed it's a bit surprising that it works at all... it 
requires the loader to have completed before the binding has evaluated, which 
is not a given
16:38 mardy: dobey: unless marcustomlinson is already running yakkety, which 
AFAIK has qt 5.6 already
16:38 dobey: mardy: xenial-overlay has 5.6 too
16:39 mardy: dobey: right, so I suspect that it works on the phones because 
there we have 5.5, but it doesnt't work with 5.6
16:39 mardy: just guessing
16:42 marcustomlinson: mardy: I'm on Xenial + overlay
16:44 marcustomlinson: mardy, dobey: yeah 5.6
16:44 mardy: marcustomlinson: try changing line 26 to   contentHeight: 
(editPageLoader.status == Loader.Ready ? editPageLoader.item.height : 0) + 
keyboardSize
16:45 mardy: marcustomlinson: or maybe just   contentHeight: 
(editPageLoader.item ? editPageLoader.item.height : 0) + keyboardSize
16:48 marcustomlinson: mardy: after that change: 
https://pastebin.canonical.com/164526/
16:48 marcustomlinson: still blank
16:53 dobey: marcustomlinson: change that ": 0" to ": units.gu(60)" and see 
what happens
16:56 marcustomlinson: dobey: no difference
16:57 marcustomlinson: mardy: here's how to easily test this. Run normal unity7 
desktop on Xenial+overlay. run "start smart-scopes-proxy", then "unity8-dash 
--mousetouch"

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

Title:
  Ubuntu One account page is blank

Status in Canonical System Image:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New
Status in ubuntuone-credentials package in Ubuntu:
  New

Bug description:
  current build number: 31
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

  The U1 account page is blank with just a title.

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

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

[Touch-packages] [Bug 1595177] Re: [SRU] Update apt/xenial to 1.2.14

[Martin Pitt]

Hello Julian, or anyone else affected,

Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.14 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  [SRU] Update apt/xenial to 1.2.14

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

Bug description:
  (This is a template for now, so I can close the bug in the 1.2.14
  upload)

  [Impact]
  We intend to upload APT 1.2.14 to xenial under the new "micro upstream 
release" policy.

  Apart from fixing bug 1573547, it also updates translations fixes the
  following other bugs:

  [[1.2.13]]

  Segmentation fault fixes:
  * fail instead of segfault on unreadable config files (Closes: 824503)

  Fixes for 3rd party programs using libapt and C++ locale API:
  * prevent C++ locale number formatting in text APIs (Closes: #825396)

  Fix for hurd (not really affecting us here, but upstream):
  * apt-key: change to / before find to satisfy its CWD needs.
    Thanks to Samuel Thibault for 'finding' the culprit! (Closes: 826043)

  Leak fixes:
  * do not hang on piped input in PipedFileFdPrivate
  * don't leak an FD in lz4 (de)compression
  * don't leak FD in AutoProxyDetect command return parsing

  [[1.2.14]]
  Regression fix from 1.2.13:
    * do not error if auto-detect-proxy cmd has no output (Closes: 827713)
  Huge apt-ftparchive performance regression fix from 1.1:
    * Reinstate caching of file hashes in apt-ftparchive (Closes: #806924)
  Tiny bug fixes, about 2 lines each:
    * source: if download is skipped, don't try to unpack
    * ensure filesize of deb is included in the hashes list

  [Test case]
  The releases follow new upstream micro release rule and thus are assumed to 
be tested by our integration test suite. There are two exceptions which cannot 
be tested:

  * prevent C++ locale number formatting in text APIs
  * apt-key: change to / before find to satisfy its CWD needs

  The first has no affected code in the archive (but maybe 3rd party
  code), the second only affects hurd.

  [Regression Potential]
  Very low. The release has been tested by a thorough integration test suite on 
Travis CI, Debian autopkgtests, and has been in Debian unstable since 
2016-06-22.

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

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

[Touch-packages] [Bug 1595177] Re: [SRU] Update apt/xenial to 1.2.14

[Martin Pitt]

For verifying this we should run a (manual or automatic) dist-upgrade,
to verify that this works in "big" scenarios.

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

Title:
  [SRU] Update apt/xenial to 1.2.14

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

Bug description:
  (This is a template for now, so I can close the bug in the 1.2.14
  upload)

  [Impact]
  We intend to upload APT 1.2.14 to xenial under the new "micro upstream 
release" policy.

  Apart from fixing bug 1573547, it also updates translations fixes the
  following other bugs:

  [[1.2.13]]

  Segmentation fault fixes:
  * fail instead of segfault on unreadable config files (Closes: 824503)

  Fixes for 3rd party programs using libapt and C++ locale API:
  * prevent C++ locale number formatting in text APIs (Closes: #825396)

  Fix for hurd (not really affecting us here, but upstream):
  * apt-key: change to / before find to satisfy its CWD needs.
    Thanks to Samuel Thibault for 'finding' the culprit! (Closes: 826043)

  Leak fixes:
  * do not hang on piped input in PipedFileFdPrivate
  * don't leak an FD in lz4 (de)compression
  * don't leak FD in AutoProxyDetect command return parsing

  [[1.2.14]]
  Regression fix from 1.2.13:
    * do not error if auto-detect-proxy cmd has no output (Closes: 827713)
  Huge apt-ftparchive performance regression fix from 1.1:
    * Reinstate caching of file hashes in apt-ftparchive (Closes: #806924)
  Tiny bug fixes, about 2 lines each:
    * source: if download is skipped, don't try to unpack
    * ensure filesize of deb is included in the hashes list

  [Test case]
  The releases follow new upstream micro release rule and thus are assumed to 
be tested by our integration test suite. There are two exceptions which cannot 
be tested:

  * prevent C++ locale number formatting in text APIs
  * apt-key: change to / before find to satisfy its CWD needs

  The first has no affected code in the archive (but maybe 3rd party
  code), the second only affects hurd.

  [Regression Potential]
  Very low. The release has been tested by a thorough integration test suite on 
Travis CI, Debian autopkgtests, and has been in Debian unstable since 
2016-06-22.

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

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

[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

[Martin Pitt]

Hello Dan, or anyone else affected,

Accepted isc-dhcp into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.3.3-5ubuntu12.2 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  Fix Committed
Status in isc-dhcp source package in Precise:
  In Progress
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in isc-dhcp package in Debian:
  Fix Released

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

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

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

[Touch-packages] [Bug 1620338] Re: Ubuntu One account page is blank

[Alberto Mardegan]

** No longer affects: ubuntu-system-settings-online-accounts (Ubuntu)

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

Title:
  Ubuntu One account page is blank

Status in Canonical System Image:
  New
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed

Bug description:
  current build number: 31
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

  The U1 account page is blank with just a title.

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

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

[Touch-packages] [Bug 1620338] Re: Ubuntu One account page is blank

[Alberto Mardegan]

The bug is indeed in the Loader of

/usr/share/accounts/qml-plugins/ubuntuone/Main.qml

To fix this bug, edit that file and:

1) remove the "sourceComponent:" line
2) remove the outer condition from the "source:" like, so that it looks like 
this:

   source: account.accountId != 0 ? existingAccountUrl : newAccountUrl


It's likely that Loader's behaviour changed slightly in Qt 5.6, triggering this 
bug.

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

Title:
  Ubuntu One account page is blank

Status in Canonical System Image:
  New
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed

Bug description:
  current build number: 31
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

  The U1 account page is blank with just a title.

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

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

[Touch-packages] [Bug 1620338] Re: Ubuntu One account page is blank

[Launchpad Bug Tracker]

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

** Changed in: ubuntuone-credentials (Ubuntu)
   Status: New => Confirmed

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

Title:
  Ubuntu One account page is blank

Status in Canonical System Image:
  New
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed

Bug description:
  current build number: 31
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

  The U1 account page is blank with just a title.

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

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

[Touch-packages] [Bug 1619600] Please test proposed package

[Martin Pitt]

Hello Iain, or anyone else affected,

Accepted gst-plugins-bad1.0 into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gst-
plugins-bad1.0/1.8.3-1ubuntu0.1 in a few hours, and then in the
-proposed repository.

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

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

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

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

Title:
  [SRU] New stable release 1.8.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Committed
Status in gstreamer-vaapi source package in Xenial:
  Incomplete
Status in gstreamer1.0 source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+subscriptions

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

[Touch-packages] [Bug 1619600] Re: [SRU] New stable release 1.8.3

[Martin Pitt]

Hello Iain, or anyone else affected,

Accepted gstreamer1.0 into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/gstreamer1.0/1.8.3-1~ubuntu0.1 in a
few hours, and then in the -proposed repository.

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

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

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

** Changed in: gstreamer1.0 (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

** Changed in: gst-plugins-bad1.0 (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Changed in: gst-plugins-good1.0 (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  [SRU] New stable release 1.8.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Committed
Status in gstreamer-vaapi source package in Xenial:
  Incomplete
Status in gstreamer1.0 source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+subscriptions

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

[Touch-packages] [Bug 1619600] Please test proposed package

[Martin Pitt]

Hello Iain, or anyone else affected,

Accepted gst-plugins-base1.0 into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/gst-
plugins-base1.0/1.8.3-1ubuntu0.1 in a few hours, and then in the
-proposed repository.

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

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

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

** Changed in: gst-plugins-ugly1.0 (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  [SRU] New stable release 1.8.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Committed
Status in gstreamer-vaapi source package in Xenial:
  Incomplete
Status in gstreamer1.0 source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+subscriptions

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

[Touch-packages] [Bug 1619600] Please test proposed package

[Martin Pitt]

Hello Iain, or anyone else affected,

Accepted gst-plugins-good1.0 into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/gst-
plugins-good1.0/1.8.3-1ubuntu0.1 in a few hours, and then in the
-proposed repository.

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

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

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

** Changed in: gst-plugins-base1.0 (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  [SRU] New stable release 1.8.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Committed
Status in gstreamer-vaapi source package in Xenial:
  Incomplete
Status in gstreamer1.0 source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+subscriptions

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

[Touch-packages] [Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window

[Michael Thayer]

Removed appmenu-qt5 and checked that I am on 5.6.1+dfsg-3ubuntu3~3, but
still no joy.  I would not rule out user error though (and I have not
yet rebooted since upgrading from 16.04, so there might be something
stale in memory).

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

Title:
  Empty menus in global app-menu in VirtualBox second window

Status in libdbusmenu-qt package in Ubuntu:
  New

Bug description:
  Reporting this following this IRC discussion:

  https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00

  The basic summary: when I run a two-screen/two-window virtual machine
  with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu,
  the menus are empty when the second screen window has the input focus.
  During start-up I get a number (55) of these messages on the console:

  Qt WARNING: void
  DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*,
  int, int, const QStringList&): No id for action

  and a number (7) of these:

  Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const
  QStringList&, DBusMenuLayoutItem&): Condition failed: menu

  Then another 55 of the first and two of the second.

  Looking at the interesting parts of the VirtualBox source code, I see
  that the menu items for the first window (menu displayed correctly)
  and the second (not displayed) share the same QAction objects.  A very
  quick guess is that this might be triggering the condition in
  DBusMenuExporterPrivate::addMenu().

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 18 15:44:00 2016
  Dependencies:
   gcc-5-base 5.4.0-6ubuntu1~16.04.1
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
   libstdc++6 5.4.0-6ubuntu1~16.04.1
  InstallationDate: Installed on 2016-05-31 (48 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libdbusmenu-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1614840] [NEW] Fontcaching takes long and cache seems damaged

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After last update on my 14.04 trusty machine, it takes a long time to
regenrate the fonts cache. Now after that, most graphical applications
take about 30 seconda to start with 100% CPU load. It is impossible to
work with my system in this state.

I already tried purging and reinstallong all fontconfig-related packages
and completely deleted and rebuildt my font cache, but the problem
persists. Before the update everything was fine.

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

-- 
Fontcaching takes long and cache seems damaged
https://bugs.launchpad.net/bugs/1614840
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to fontconfig 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 1619600] Please test proposed package

[Martin Pitt]

Hello Iain, or anyone else affected,

Accepted gst-plugins-ugly1.0 into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/gst-
plugins-ugly1.0/1.8.3-1ubuntu0.1 in a few hours, and then in the
-proposed repository.

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

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

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

** Changed in: gst-libav1.0 (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  [SRU] New stable release 1.8.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Committed
Status in gstreamer-vaapi source package in Xenial:
  Incomplete
Status in gstreamer1.0 source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+subscriptions

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

[Touch-packages] [Bug 1619600] Please test proposed package

[Martin Pitt]

Hello Iain, or anyone else affected,

Accepted gst-libav1.0 into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gst-
libav1.0/1.8.3-1ubuntu0.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

Title:
  [SRU] New stable release 1.8.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Committed
Status in gstreamer-vaapi source package in Xenial:
  Incomplete
Status in gstreamer1.0 source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+subscriptions

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

[Touch-packages] [Bug 1620338] Re: Ubuntu One account page is blank

[Jean-Baptiste Lallement]

I confirm that after these modifications the page works fine and user
can log into U1.

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

Title:
  Ubuntu One account page is blank

Status in Canonical System Image:
  New
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed

Bug description:
  current build number: 31
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

  The U1 account page is blank with just a title.

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

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

[Touch-packages] [Bug 1614840] Re: Fontcaching takes long and cache seems damaged

[Mathieu Trudel-Lapierre]

** Package changed: grub2 (Ubuntu) => fontconfig (Ubuntu)

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

Title:
  Fontcaching takes long and cache seems damaged

Status in fontconfig package in Ubuntu:
  New

Bug description:
  After last update on my 14.04 trusty machine, it takes a long time to
  regenrate the fonts cache. Now after that, most graphical applications
  take about 30 seconda to start with 100% CPU load. It is impossible to
  work with my system in this state.

  I already tried purging and reinstallong all fontconfig-related
  packages and completely deleted and rebuildt my font cache, but the
  problem persists. Before the update everything was fine.

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

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

[Touch-packages] [Bug 1620496] Re: Calendar widget gets confused with October

[Lukáš Tinkl]

** Changed in: ubuntu-settings-components (Ubuntu)
 Assignee: (unassigned) => Lukáš Tinkl (lukas-kde)

** Changed in: ubuntu-settings-components (Ubuntu)
   Status: New => In Progress

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

Title:
  Calendar widget gets confused with October

Status in Canonical System Image:
  Confirmed
Status in ubuntu-settings-components package in Ubuntu:
  In Progress

Bug description:
  I can see two October 30ths on my phone, see attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: qml-module-ubuntu-settings-components 0.9+15.04.20160818.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Tue Sep  6 09:24:34 2016
  InstallationDate: Installed on 2016-09-03 (3 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160903-020304)
  SourcePackage: ubuntu-settings-components
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1620338] Re: Ubuntu One account page is blank

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => David Barth (dbarth)

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

Title:
  Ubuntu One account page is blank

Status in Canonical System Image:
  In Progress
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed

Bug description:
  current build number: 31
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

  The U1 account page is blank with just a title.

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

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

[Touch-packages] [Bug 1620634] [NEW] Hangs to build on ppc64el

[Timo Jyrinki]

Public bug reported:

It seems impossible to get ppc64el build to finish on yakkety:

--
gdk_pixbuf-2.0 -lapparmor 
-Wl,-rpath,/<>/content-hub-0.2+16.10.20160830/build/src/com/ubuntu/content:
make[3]: Leaving directory '/<>/content-hub-0.2+16.10.20160830/build'
[100%] Built target content-hub-send
make[2]: Leaving directory '/<>/content-hub-0.2+16.10.20160830/build'
/usr/bin/cmake -E cmake_progress_start 
/<>/content-hub-0.2+16.10.20160830/build/CMakeFiles 0
make[1]: Leaving directory '/<>/content-hub-0.2+16.10.20160830/build'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>/content-hub-0.2+16.10.20160830'
dbus-test-runner -t make -p "-C" -p "build/tests/acceptance-tests" -p test
DBus daemon: 
unix:abstract=/tmp/dbus-O9sC0cCtE9,guid=19a0b33017166ee2a4c9d4ff57cec6e9
task-0: Started with PID: 11044
task-0: make[2]: Entering directory 
'/<>/content-hub-0.2+16.10.20160830/build/tests/acceptance-tests'
task-0: Running tests...
task-0: /usr/bin/ctest --force-new-ctest-process
task-0: Test project 
/<>/content-hub-0.2+16.10.20160830/build/tests/acceptance-tests
task-0: Start 1: app_hub_communication_default_source
task-0: 1/10 Test #1: app_hub_communication_default_source ... Passed 0.03 sec
task-0: Start 2: app_hub_communication_known_sources
task-0: 2/10 Test #2: app_hub_communication_known_sources  Passed 0.03 sec
task-0: Start 3: app_hub_communication_stores

** (dbus-test-runner:11039): WARNING **: Timing out at maximum wait of
30 seconds.

(dbus-test-runner:11039): libdbustest-CRITICAL **: dbus_test_service_run: 
assertion 'all_tasks(service, all_tasks_finished_helper, NULL)' failed
task-0: Shutting down
DBus daemon: Shutdown
debian/rules:15: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 255
make[1]: Leaving directory '/<>/content-hub-0.2+16.10.20160830'
debian/rules:7: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

--

This happens despite 5+ retries. Also i386 and armhf needed a retry but
they did eventually finish.

This prevents getting any content-hub landing to yakkety properly.

** Affects: content-hub (Ubuntu)
 Importance: Critical
 Status: New

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

Title:
  Hangs to build on ppc64el

Status in content-hub package in Ubuntu:
  New

Bug description:
  It seems impossible to get ppc64el build to finish on yakkety:

  --
  gdk_pixbuf-2.0 -lapparmor 
-Wl,-rpath,/<>/content-hub-0.2+16.10.20160830/build/src/com/ubuntu/content:
  make[3]: Leaving directory 
'/<>/content-hub-0.2+16.10.20160830/build'
  [100%] Built target content-hub-send
  make[2]: Leaving directory 
'/<>/content-hub-0.2+16.10.20160830/build'
  /usr/bin/cmake -E cmake_progress_start 
/<>/content-hub-0.2+16.10.20160830/build/CMakeFiles 0
  make[1]: Leaving directory 
'/<>/content-hub-0.2+16.10.20160830/build'
 debian/rules override_dh_auto_test
  make[1]: Entering directory '/<>/content-hub-0.2+16.10.20160830'
  dbus-test-runner -t make -p "-C" -p "build/tests/acceptance-tests" -p test
  DBus daemon: 
unix:abstract=/tmp/dbus-O9sC0cCtE9,guid=19a0b33017166ee2a4c9d4ff57cec6e9
  task-0: Started with PID: 11044
  task-0: make[2]: Entering directory 
'/<>/content-hub-0.2+16.10.20160830/build/tests/acceptance-tests'
  task-0: Running tests...
  task-0: /usr/bin/ctest --force-new-ctest-process
  task-0: Test project 
/<>/content-hub-0.2+16.10.20160830/build/tests/acceptance-tests
  task-0: Start 1: app_hub_communication_default_source
  task-0: 1/10 Test #1: app_hub_communication_default_source ... Passed 0.03 sec
  task-0: Start 2: app_hub_communication_known_sources
  task-0: 2/10 Test #2: app_hub_communication_known_sources  Passed 0.03 sec
  task-0: Start 3: app_hub_communication_stores

  ** (dbus-test-runner:11039): WARNING **: Timing out at maximum wait of
  30 seconds.

  (dbus-test-runner:11039): libdbustest-CRITICAL **: dbus_test_service_run: 
assertion 'all_tasks(service, all_tasks_finished_helper, NULL)' failed
  task-0: Shutting down
  DBus daemon: Shutdown
  debian/rules:15: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 255
  make[1]: Leaving directory '/<>/content-hub-0.2+16.10.20160830'
  debian/rules:7: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

  --

  This happens despite 5+ retries. Also i386 and armhf needed a retry
  but they did eventually finish.

  This prevents getting any content-hub landing to yakkety properly.

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

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

[Touch-packages] [Bug 1620338] Re: Ubuntu One account page is blank

[Marcus Tomlinson]

Ack, this change fixes the issue on unity8 desktop session as well.
Thanks mardy

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

Title:
  Ubuntu One account page is blank

Status in Canonical System Image:
  In Progress
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed

Bug description:
  current build number: 31
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

  The U1 account page is blank with just a title.

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

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

[Touch-packages] [Bug 1620631] [NEW] Lightdm crashes on bootup after installing Virtualbox guest addition tools on Ubuntu Desktop 16.04.1

[Ian]

Public bug reported:

After a clean install of Ubuntu 16.04.1 on Virtualbox, when I install
the guest additions to it and reboot the lightdm display manager
continually restarts and then errors out. I'm left the other tty
terminals which sometimes do not work. Uninstalling the guest addition
tools in /opt and rebooting fixes the issue.

Virtualbox version: 5.1.4 r1110228
VBoxGuestAdditions-5.1.4


ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm (not installed)
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Tue Sep  6 08:38:03 2016
InstallationDate: Installed on 2016-09-02 (3 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

What I've tried for troubleshooting -

Removing .Xauthority
Verifying permissions on various lightdm system folders.
Upgrading virtualbox
Purging / uninstalling and reinstalling lightdm
dpkg-reconfigure lightdm

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Status: Opinion


** Tags: amd64 apport-bug xenial

** Summary changed:

- Lightdm crashes after installing Virtualbox guest addition tools
+ Lightdm crashes after installing Virtualbox guest addition tools on Ubuntu 
Desktop 16.04.1

** Description changed:

  After a clean install of Ubuntu 16.04.1 on Virtualbox, when I install
  the guest additions to it and reboot the lightdm display manager
  continually restarts and then errors out. I'm left the other tty
  terminals which sometimes do not work. Uninstalling the guest addition
  tools in /opt and rebooting fixes the issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Sep  6 08:38:03 2016
  InstallationDate: Installed on 2016-09-02 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
-  TERM=linux
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=linux
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
+ 
+ 
+ What I've tried for troubleshooting -
+ 
+ Removing .Xauthority
+ Verifying permissions on various lightdm system folders.
+ Upgrading virtualbox
+ Purging / uninstalling and reinstalling lightdm
+ dpkg-reconfigure lightdm

** Summary changed:

- Lightdm crashes after installing Virtualbox guest addition tools on Ubuntu 
Desktop 16.04.1
+ Lightdm crashes on bootup after installing Virtualbox guest addition tools on 
Ubuntu Desktop 16.04.1

** Description changed:

  After a clean install of Ubuntu 16.04.1 on Virtualbox, when I install
  the guest additions to it and reboot the lightdm display manager
  continually restarts and then errors out. I'm left the other tty
  terminals which sometimes do not work. Uninstalling the guest addition
  tools in /opt and rebooting fixes the issue.
+ 
+ Virtualbox version: 5.1.4 r1110228
+ VBoxGuestAdditions-5.1.4
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Sep  6 08:38:03 2016
  InstallationDate: Installed on 2016-09-02 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  
- 
  What I've tried for troubleshooting -
  
  Removing .Xauthority
  Verifying permissions on various lightdm system folders.
  Upgrading virtualbox
  Purging / uninstalling and reinstalling lightdm
  dpkg-reconfigure lightdm

** Changed in: lightdm (Ubuntu)
   Status: New => Opinion

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

Title:
  Lightdm crashes on bootup after installing Virtualbox guest addition
  tools on Ubuntu Desktop 16.04.1

Status in lightdm package in Ubuntu:
  Opinion

Bug description:
  After a clean install of Ubuntu 16.04.1 on Virtualbox, when I install
  the guest additions to it and reboot the lightdm display manager
  continually restarts and then errors out. I'm left the other tty
  terminals which sometimes do not work. Uninstalling the guest addition
  tools in /opt and rebooting fixes the issue.

  Virtualbox version: 5.1.4 r1110228
  VBoxGue

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

[Jim Hodapp]

Public bug reported:

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/

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

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

Title:
  Fails to pair with Bose QC35 headphones

Status in bluez package in Ubuntu:
  New

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/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+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 1389333] Re: Can't send vcard via sms

[antisa]

This problem also occurs when you are in messaging app and then try to
send a contact by selecting from the address book. Using BQ Aquaris E5.

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

Title:
  Can't send vcard via sms

Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  * Open address book
  * Open a contact
  * click on "Share"
  * In the content hub popup, select messages
  * enter recipient
  * click "Send"

  => The messages fails to send immediately (shows up in conversation
  history with the red failed text and the retry icon). Pressing the
  retry icon keeps failing.

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

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

[Touch-packages] [Bug 1389333] Re: Can't send vcard via sms

[Launchpad Bug Tracker]

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

** Changed in: messaging-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Can't send vcard via sms

Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  * Open address book
  * Open a contact
  * click on "Share"
  * In the content hub popup, select messages
  * enter recipient
  * click "Send"

  => The messages fails to send immediately (shows up in conversation
  history with the red failed text and the retry icon). Pressing the
  retry icon keeps failing.

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

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