date:20150821

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

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

** Changed in: libffi (Ubuntu)
   Status: New = Confirmed

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

Title:
  package libffi6:i386 3.2.1-2 failed to install/upgrade: package
  libffi6:i386 is already installed and configured

Status in libffi package in Ubuntu:
  Confirmed

Bug description:
  Install error

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: libffi6:i386 3.2.1-2
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.2
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu3.1
  Architecture: amd64
  Date: Thu Aug 13 22:54:39 2015
  Dependencies:
   gcc-5-base 5.1~rc1-0ubuntu1
   libc6 2.21-0ubuntu4
   libgcc1 1:5.1~rc1-0ubuntu1
   multiarch-support 2.21-0ubuntu4
  DuplicateSignature: package:libffi6:i386:3.2.1-2:package libffi6:i386 is 
already installed and configured
  ErrorMessage: package libffi6:i386 is already installed and configured
  InstallationDate: Installed on 2015-08-13 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: libffi
  Title: package libffi6:i386 3.2.1-2 failed to install/upgrade: package 
libffi6:i386 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1467267] Re: Please sync to 1.0.2-2 from Debian (main)

2015-08-21 Thread dino99

hm, some builts have been done, but some others have failed. So we does
not get yet the packages into wily archive

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

Title:
  Please sync to 1.0.2-2 from Debian (main)

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager-applet package in Ubuntu:
  Triaged
Status in network-manager-pptp package in Ubuntu:
  Triaged

Bug description:
  Lot of bug fixes with the latest stable release
  
http://metadata.ftp-master.debian.org/changelogs//main/n/network-manager/network-manager_1.0.2-2_changelog

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 0.9.10.0-4ubuntu16
  ProcVersionSignature: Ubuntu 4.0.0-2.4-generic 4.0.5
  Uname: Linux 4.0.0-2-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Jun 21 16:56:40 2015
  IpRoute:
   default via 192.168.1.1 dev eth1  proto static  metric 100 
   169.254.0.0/16 dev eth1  scope link  metric 1000 
   192.168.1.0/24 dev eth1  proto kernel  scope link  src 192.168.1.3
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-06-13T08:56:31.598901
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH  
  
   Wired connection 1  7086b2ff-1446-45fe-b8f3-cd333cd4cee1  802-3-ethernet  
1434898501  dim. 21 juin 2015 16:55:01 CEST  yes  no
/org/freedesktop/NetworkManager/Settings/0  yes eth1activated  
/org/freedesktop/NetworkManager/ActiveConnection/0
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eth1ethernet  connected/org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  7086b2ff-1446-45fe-b8f3-cd333cd4cee1  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1480478] Re: /usr/lib/arm-linux-gnueabihf/ubuntu-ui-toolkit/launcher:6:qt_message_fatal:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientInte

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

** This bug has been marked a duplicate of bug 1365673
   
/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:6:qt_message_fatal:QMessageLogger::fatal:
 
UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlugin::create:loadIntegration

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

Title:
  /usr/lib/arm-linux-gnueabihf/ubuntu-ui-
  
toolkit/launcher:6:qt_message_fatal:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlugin::create:loadIntegration

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding ubuntu-ui-toolkit.  This problem was most recently seen with
  version 1.3.1549+15.10.20150710.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6583aaf67ce138329306335c7449ddf617933d67
  contains more details.

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

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

[Touch-packages] [Bug 1486872] Re: Can skip wizard steps after you tap on notificationStorage device detected

2015-08-21 Thread Dave Morley

This is not a regression the same effect can be triggered in OTA5's
image.

I guess we should block ota7 on this as there is no
user/pin/password/wifi etc setup.

** Tags added: qa-regression-testing

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

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

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

Title:
  Can skip wizard steps after you tap on notificationStorage device
  detected

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

Bug description:
  $ system-image-cli -i
  current build number: 104
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-08-20 03:24:50
  version version: 104
  version ubuntu: 20150819
  version device: 20150817-3879cb2
  version custom: 20150814-887-30-30-vivid

  Reproduce steps:
  1,Boot the phone with SD card inserted
  2,Wait a while on wizard page 
   notification ¨Storage device deteced¨ pops up for SD card
  3.Tap on the notification
   external storage opens
  4.Exit external storage

  Actual= it backs to today scope

  Expect=Can't skip wizard steps

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

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

[Touch-packages] [Bug 1486008] Re: leading actions width is too small making it very difficult to press on Nexus 4 (mako)

2015-08-21 Thread Nekhelesh Ramananthan

Indeed it is not a design issue, more a implementation/environment issue
specific to Nexus 4.

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

Title:
  leading actions width is too small making it very difficult to press
  on Nexus 4 (mako)

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

Bug description:
  Since a recent update to the ListItem leading actions in
  Ubuntu.Components 1.2, where the width of the action was clamped, the
  width is too small to press comfortably on a phone resulting in it
  missing 9 out of 10 tries. It affects the usability of the action and
  may be become a release blocker for apps that have recently switched
  over to the new list items.

  Sample App

  import QtQuick 2.4
  import Ubuntu.Components 1.2

  MainView {
  applicationName: testdelete.nik90
  width: units.gu(100)
  height: units.gu(75)

  Page {
  title: Swipe to Delete
  ListItem {
  id: listItem
  anchors.top: parent.top

  Label {
  text: Swipe me right to delete this listitem
  wrapMode: Text.WordWrap
  anchors { left: parent.left; leftMargin: units.gu(2); right: 
parent.right; verticalCenter: parent.verticalCenter }
  }

  
  leadingActions: ListItemActions {
  actions: [
  Action {
  iconName: delete
  onTriggered: listItem.destroy()
  }
  ]
  }
  }
  }
  }

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

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

[Touch-packages] [Bug 1191700] Re: [saucy] software-properties-gtk crashed with Exception NameHasNoOwner: Could not get owner of name 'com.ubuntu.SoftwareProperties'

2015-08-21 Thread Jos Geluk

This bug still occurs repeatably in Vivid. The traceback at the top of
this bug report is still accurate, including line numbers.

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

Title:
  [saucy] software-properties-gtk crashed with Exception NameHasNoOwner:
  Could not get owner of name 'com.ubuntu.SoftwareProperties'

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  software-properties-gtk is crashing every time it is run with
  Exception NameHasNoOwner: Could not get owner of name
  'com.ubuntu.SoftwareProperties'

  Traceback (most recent call last):
  File /usr/bin/software-properties-gtk, line 104, in module
 app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  /usr/lib/python3/dist-packages/dbus/bus.py, line 175, in activate_name_owner
  /usr/lib/python3/dist-packages/dbus/bus.py, line 361, in get_name_owner
  /usr/lib/python3/dist-packages/dbus/connection.py, line 651, in call_blocking

  dbus.exceptions.DBusException:
  org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name
  'com.ubuntu.SoftwareProperties': no such name

  This is software-properties-gtk-0.92.19 in Ubuntu 13.04 Saucy

  
  This issue is preventing any further software updates using either the Ubuntu 
Software Center or apt itself directly.

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

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

[Touch-packages] [Bug 1483210] Re: drop unity-voice dependency from HUD, remove unity-voice from archives

** Branch linked: lp:ubuntu/wily-proposed/hud

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

Title:
  drop unity-voice dependency from HUD, remove unity-voice from archives

Status in hud package in Ubuntu:
  New

Bug description:
  It'd be useful for hud not to depend on unity-voice anymore.
  Optionally, unity-voice could be removed from archives and kept only
  as a code repository on Launchpad until it's needed again.

   pete-woods Mirv: unity-voice technically isn't used any more
   pete-woods unity-voice has a dependency, though
   pete-woods so would need to remove that from HUD first
   pete-woods then you will also get space savings from the voice definition 
files
   pete-woods Mirv: it's not used, because there is no UI to invoke the voice 
recognition any more
   pete-woods after HUD was pulled from the phone

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

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

[Touch-packages] [Bug 1487414] [NEW] recordmydesktop should be a dependency of ubuntu-ui-toolkit-autopilot

2015-08-21 Thread Christian Dywan

Public bug reported:

Attempting to debug an issue with local test runs I removed
recordmydesktop (as it was spiking at 100% CPU and tests got stuck) and
it turns out I could no longer run tests - yet it's not a dependency of
ubuntu-ui-toolkit-autopilot.

Error: The application 'recordmydesktop' needs to be installed to record
failing jobs.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Critical
 Status: New

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

Title:
  recordmydesktop should be a dependency of ubuntu-ui-toolkit-autopilot

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

Bug description:
  Attempting to debug an issue with local test runs I removed
  recordmydesktop (as it was spiking at 100% CPU and tests got stuck)
  and it turns out I could no longer run tests - yet it's not a
  dependency of ubuntu-ui-toolkit-autopilot.

  Error: The application 'recordmydesktop' needs to be installed to
  record failing jobs.

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

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

[Touch-packages] [Bug 1191700] Re: [saucy] software-properties-gtk crashed with Exception NameHasNoOwner: Could not get owner of name 'com.ubuntu.SoftwareProperties'

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

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

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

Title:
  [saucy] software-properties-gtk crashed with Exception NameHasNoOwner:
  Could not get owner of name 'com.ubuntu.SoftwareProperties'

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  software-properties-gtk is crashing every time it is run with
  Exception NameHasNoOwner: Could not get owner of name
  'com.ubuntu.SoftwareProperties'

  Traceback (most recent call last):
  File /usr/bin/software-properties-gtk, line 104, in module
 app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  /usr/lib/python3/dist-packages/dbus/bus.py, line 175, in activate_name_owner
  /usr/lib/python3/dist-packages/dbus/bus.py, line 361, in get_name_owner
  /usr/lib/python3/dist-packages/dbus/connection.py, line 651, in call_blocking

  dbus.exceptions.DBusException:
  org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name
  'com.ubuntu.SoftwareProperties': no such name

  This is software-properties-gtk-0.92.19 in Ubuntu 13.04 Saucy

  
  This issue is preventing any further software updates using either the Ubuntu 
Software Center or apt itself directly.

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

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

[Touch-packages] [Bug 1348954] Re: update Python3 for trusty

2015-08-21 Thread Mathew Hodson

** No longer affects: python3.4 (Ubuntu)

** No longer affects: python3-stdlib-extensions (Ubuntu)

** No longer affects: python3-defaults (Ubuntu)

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

Title:
  update Python3 for trusty

Status in python3-defaults source package in Trusty:
  Confirmed
Status in python3-stdlib-extensions source package in Trusty:
  Fix Committed
Status in python3.4 source package in Trusty:
  Fix Committed
Status in ubiquity source package in Trusty:
  New

Bug description:
  update Python3 for trusty.

  Rationale: the LTS was released with 3.4.0, the first 3.4 release
  which certainly had some issues. The idea is to update the python3.4
  packages to the version found in 15.04 (vivid), which currently
  doesn't have any outstanding issues.  A test rebuild of the trusty
  main component was done without showing any regressions during the
  package builds.

  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150317-trusty.html
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150501-updates-trusty.html

  To validate this SRU, I'm proposing to use the results from the test
  rebuild, plus evaluating the testsuite results of the python3.4
  package itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/trusty/+source/python3-defaults/+bug/1348954/+subscriptions

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

[Touch-packages] [Bug 1487426] [NEW] package util-linux 2.25.2-4ubuntu3 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

2015-08-21 Thread Vsevolod

Public bug reported:

Следующие пакеты устанавливались автоматически и больше не требуются:
  libssh2-1 linux-headers-3.19.0-15 linux-headers-3.19.0-15-generic
  linux-image-3.19.0-15-generic linux-image-extra-3.19.0-15-generic mc-data
Для их удаления используйте «apt-get autoremove».
обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 55 
пакетов не обновлено.
не установлено до конца или удалено 1 пакетов.
После данной операции, объём занятого дискового пространства возрастёт на 0 B.
Настраивается пакет util-linux (2.25.2-4ubuntu3) …
insserv: warning: script 'K01smfpd' missing LSB tags and overrides
insserv: warning: script 'smfpd' missing LSB tags and overrides
insserv: There is a loop between service rc.local and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: There is a loop at service rc.local if started
insserv: There is a loop between service smfpd and rc.local if started
insserv:  loop involving service rc.local at depth 2
insserv:  loop involving service smfpd at depth 1
insserv:  loop involving service rsyslog at depth 1
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: There is a loop between service smfpd and hwclock if started
insserv:  loop involving service hwclock at depth 1
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv:  loop involving service networking at depth 4
insserv: There is a loop between service rc.local and urandom if started
insserv:  loop involving service urandom at depth 4
insserv:  loop involving service mountdevsubfs at depth 2
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends

[Touch-packages] [Bug 1433324] Re: provide whl packages in trusty to enable pyvenv in python3.4

2015-08-21 Thread Mathew Hodson

** No longer affects: python-scripttest (Ubuntu Trusty)

** No longer affects: python-scripttest (Ubuntu)

** No longer affects: chardet-whl (Ubuntu)

** No longer affects: distlib (Ubuntu)

** No longer affects: html5lib (Ubuntu)

** No longer affects: python-colorama (Ubuntu)

** No longer affects: python-pip (Ubuntu)

** No longer affects: python-setuptools (Ubuntu)

** No longer affects: python-urllib3 (Ubuntu)

** No longer affects: requests (Ubuntu)

** No longer affects: six (Ubuntu)

** No longer affects: wheel (Ubuntu)

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

Title:
  provide whl packages in trusty to enable pyvenv in python3.4

Status in chardet-whl source package in Trusty:
  Fix Released
Status in distlib source package in Trusty:
  Fix Released
Status in html5lib source package in Trusty:
  Fix Released
Status in python-colorama source package in Trusty:
  Fix Released
Status in python-pip source package in Trusty:
  Fix Released
Status in python-setuptools source package in Trusty:
  Fix Released
Status in python-urllib3 source package in Trusty:
  Fix Released
Status in requests source package in Trusty:
  Fix Released
Status in six source package in Trusty:
  Fix Released
Status in wheel source package in Trusty:
  Fix Released

Bug description:
  to enable pyvenv in trusty, we need a number of -whl packages in
  trusty. For the normal case, this is just adding a new separate binary
  package, sometimes the build system needs to use setuptools. Other
  needed changes are described below. The python3.4 update is tracked in
  lp: #1348954.

  test criterium for accepting these packages should be a successful
  build, a check that the original packages are not modified, and the
  new packages are not empty.

  The version number may be sometimes odd looking. Packages were
  prepared in the ubuntu-toolchain-r/ppa, and I'd like to use version
  number higher than in this PPA.

  wheel: wheel is not part of trusty, so just take the first upload to
  utopic.

  six: Build a -whl package (setuptools is needed to build the wheel
  package).

  chardet: 2.0.1 in trusty is not ready for Python3. Backport the
  package from utopic (source name chardet-whl), and just build the
  python3-chardet and python-chardet-whl packages (both new in trusty).

  distlib: Build a -whl package (setuptools is needed to build the wheel
  package).

  html5lib: Build a -whl package (setuptools is needed to build the
  wheel package). Just use the packaging of the next Debian version.

  python-colorama: Build a -whl package (setuptools is needed to build
  the wheel package).

  python-urllib3: Build using setuptools and build a wheel package.
  Additional patch to not rely on ssl.PROTOCOL_SSLv3 being defined.

  requests: Build a -whl package

  python-setuptools: Build a -whl package, and fix an issue with
  installing the documentation.

  python-pip: Build a -whl package, don't require the new version of
  python-scripttest, build succeeds without it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/trusty/+source/chardet-whl/+bug/1433324/+subscriptions

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

[Touch-packages] [Bug 1356033] Re: package initramfs-tools 0.99ubuntu13.5 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

2015-08-21 Thread auxbuss

As with #4, I was/am trying to upgrade from 12.04 LTS to 14.04 LTS.

It appears that the 14.04 upgrade is trying to do:

  update-initramfs: Generating /boot/initrd.img-3.2.0-89-generic-pae

which is the my kernel from 12.04. Whether or not it should be doing
this, I don't know.

The files it can't find (libpango1.0-0.modules and pango-basic-fc.so)
were in the libpango1.0-0 package for 12.04, but are no longer present
in later versions. See:

http://packages.ubuntu.com/search?suite=precisearch=anymode=exactfilenamesearchon=contentskeywords=libpango1.0-0.modules

In any case, by this point in the upgrade the package has been removed:

  p   libpango-1.0-0

I'm SOL at this point.

I'd appreciate a suggestion for  workaround to this in lieu of a fix.

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

Title:
  package initramfs-tools 0.99ubuntu13.5 failed to install/upgrade:
  ErrorMessage: subprocess installed post-installation script returned
  error exit status 1

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Occurred during do-release-upgrade from 12.04.4 to 14.04.1

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: initramfs-tools 0.99ubuntu13.5
  ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46
  Uname: Linux 3.2.0-48-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  Date: Tue Aug 12 15:21:16 2014
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.99ubuntu13.5 failed to install/upgrade: 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
  UpgradeStatus: Upgraded to precise on 2014-08-12 (0 days ago)

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

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

[Touch-packages] [Bug 1446108] Re: Location tagging doesn't work for photos

** Changed in: camera-app (Ubuntu)
   Status: New = Fix Released

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

Title:
  Location tagging doesn't work for photos

Status in camera-app package in Ubuntu:
  Fix Released

Bug description:
  arale device, r178, ubuntu-touch/vivid-proposed

  Steps
  1. Make sure GPS works in Browser(maps.google.com) and App(both Here Maps
Google Maps)
  2. Launch Camera app
  3. Enable location-tagging
  4. Take a picture
  5. Transfer to desktop
  6. (install exiftool) Run exiftool -gpslatitude -gpslongitude image_name

  Result
  There is no location information

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

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

[Touch-packages] [Bug 1487500] Re: package dbus 1.9.20-1ubuntu2 failed to install/upgrade: triggers looping, abandoned

2015-08-21 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package dbus 1.9.20-1ubuntu2 failed to install/upgrade: triggers
  looping, abandoned

Status in dbus package in Ubuntu:
  New

Bug description:
  After clean installation of Ubuntu-MATE Whily got this error.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: dbus 1.9.20-1ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Fri Aug 21 14:33:14 2015
  DuplicateSignature: package:dbus:1.9.20-1ubuntu2:triggers looping, abandoned
  ErrorMessage: triggers looping, abandoned
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu1
   apt  1.0.9.10ubuntu6
  SourcePackage: dbus
  Title: package dbus 1.9.20-1ubuntu2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1487500] [NEW] package dbus 1.9.20-1ubuntu2 failed to install/upgrade: triggers looping, abandoned

2015-08-21 Thread Alex Wakizashi

Public bug reported:

After clean installation of Ubuntu-MATE Whily got this error.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: dbus 1.9.20-1ubuntu2
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu7
Architecture: amd64
Date: Fri Aug 21 14:33:14 2015
DuplicateSignature: package:dbus:1.9.20-1ubuntu2:triggers looping, abandoned
ErrorMessage: triggers looping, abandoned
RelatedPackageVersions:
 dpkg 1.18.2ubuntu1
 apt  1.0.9.10ubuntu6
SourcePackage: dbus
Title: package dbus 1.9.20-1ubuntu2 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package wily

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

Title:
  package dbus 1.9.20-1ubuntu2 failed to install/upgrade: triggers
  looping, abandoned

Status in dbus package in Ubuntu:
  New

Bug description:
  After clean installation of Ubuntu-MATE Whily got this error.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: dbus 1.9.20-1ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Fri Aug 21 14:33:14 2015
  DuplicateSignature: package:dbus:1.9.20-1ubuntu2:triggers looping, abandoned
  ErrorMessage: triggers looping, abandoned
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu1
   apt  1.0.9.10ubuntu6
  SourcePackage: dbus
  Title: package dbus 1.9.20-1ubuntu2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1487469] [NEW] Several rated apps are shown * 0.0 rate

2015-08-21 Thread Matti Rinta-Nikkola

Public bug reported:

Navigate for example to: Ubuntu Store - Communication - App Internet the 
most popular...
All the apps are displayed * 0.0 rates although they all have rated, see 
attachment.

** Affects: unity-scope-click (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: screenshot20150821_151722003.png
   
https://bugs.launchpad.net/bugs/1487469/+attachment/4450233/+files/screenshot20150821_151722003.png

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

Title:
  Several rated apps are shown * 0.0 rate

Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  Navigate for example to: Ubuntu Store - Communication - App Internet the 
most popular...
  All the apps are displayed * 0.0 rates although they all have rated, see 
attachment.

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

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

[Touch-packages] [Bug 1389771] Re: [wizard] 4-digit passcode code gets set incorrectly as passphrase on first run when flashing with --password

Yep, certainly not a priority, just nice to have.

** Changed in: unity8 (Ubuntu)
   Importance: Undecided = Wishlist

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

Title:
  [wizard] 4-digit passcode code gets set incorrectly as passphrase on
  first run when flashing with --password

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  After setting the 4-digit passcode on the first run, the user
  encounters she needs to type the passcode with the normal qwerty
  keyboard instead every time when unlocking the phone, instead of the
  easy passcode entering.

  Reproduced once again after flashing my mako with --bootstrap from
  mako rtm 120 (=krillin rtm 143).

  Workaround: go to Lock security settings, change to 4-digit passcode
  manually.

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

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

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

right, so looking a bit more into the issue

the state saver code is

http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
toolkit/trunk/view/head:/src/Ubuntu/Components/plugin/statesaverbackend_p.cpp#L44

only sig2/15 are handled by unix handlers, the state saver triggers on sigkill 
(which Didier is using for testing) through the 
QObject::connect(QuickUtils::instance(), QuickUtils::deactivated, signal

summary of the issues
- is sigkill supposed to be handled directly like e.g sigint?
- ContentStore somehow makes the deactivated signal stop being triggered
- the documentation doesn't list the handled signals

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

Title:
  Using ContentStore disables silently any StateSaver capability

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

Bug description:
  1. Create the default template project
  2. Add on the page (with an id):
  TextField {
  id: foo
  StateSaver.properties: text
  }
  3. run the app, type something in the field, xkill it, restart
  - the TextField content is restored by the StateSaver.
  4. import Ubuntu.Content 1.1
  - StateSaver still works
  5. add anywhere on the page:
  ContentStore {
  id: appContentStore
  scope: ContentScope.App
  }
  - The state is not restored anymore (note that it may be the first time, 
restoring when there was no ContentStore at kill time), then it constantly 
fails to restore.

  There is no warning or anything that reported an issue.

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

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

[Touch-packages] [Bug 1487469] Re: Several rated apps are shown * 0.0 rate

2015-08-21 Thread Matti Rinta-Nikkola

** Description changed:

  Navigate for example to: Ubuntu Store - Communication - App Internet the 
most popular...
- All the apps are displayed * 0.0 rates although they all have rated, see 
attachment.
+ All the apps are displayed * 0.0 rates although they all have been rated, 
see attachment.

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

Title:
  Several rated apps are shown * 0.0 rate

Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  Navigate for example to: Ubuntu Store - Communication - App Internet the 
most popular...
  All the apps are displayed * 0.0 rates although they all have been rated, 
see attachment.

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

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

[Touch-packages] [Bug 1486714] Re: Unable to Cancel Purchase from Apps Scope

2015-08-21 Thread Rodney Dawes

** Changed in: unity-scope-click (Ubuntu)
   Status: Triaged = In Progress

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

Title:
  Unable to Cancel Purchase from Apps Scope

Status in unity-scope-click package in Ubuntu:
  In Progress

Bug description:
  When attempting to cancel a purchase from the Apps scope, rather than
  the Store scope, an exception is raised and the scope crashes.

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

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

[Touch-packages] [Bug 1435776] Re: NM does not activate ofono Inet contexts w/Username but no Password ( eg. giffgaff )

Changing the Status to FixReleased for Ubuntu ( ie. Wily ) task as this
wasn't recorded properly in the changelog.  This was fixed in version:
0.9.10.0-4ubuntu19.

** Changed in: network-manager (Ubuntu)
   Status: In Progress = Fix Released

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

Title:
  NM does not activate ofono Inet contexts w/Username but no Password (
  eg. giffgaff )

Status in Canonical System Image:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Fix Released

Bug description:
  Device: Krillin
  Software:  Vivid r157

  NM does not activate a valid ofono context which is present in the
  gprs file (context_1 in this case)

  I was able to activate the context manually using ./activate-context
  /ril_0 1

  You can find syslog, list-modems and list-contexts attached

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

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

[Touch-packages] [Bug 1471716] Re: counting down can not be stopped in camera app after taping power key .

Thanks for your report. Are you still able to reproduce this issue on
OTA6. I tried with krillin #104 and it worked fine. I could stop the
timer.

** Changed in: camera-app (Ubuntu)
   Status: New = Incomplete

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

Title:
  counting down can not be stopped  in camera app after  taping power
  key .

Status in camera-app package in Ubuntu:
  Incomplete

Bug description:
  system-image-cli -i
  current build number: 56
  device name: krillin
  plast update: 2015-07-06 04:16:52
  version version: 56
  version ubuntu: 20150703
  version device: 20150529-8e13c5f
  version custom: 20150528-722-29-15-vivid

  step by step
  1. Open camera app
  2.Set counting down to 15s /5s
  3.Tap camera key
  4.Tap power key during counting  down
  5.Tap power key again.
  Expected result
  After step 5, Counting down stopped.
  Actual result
  After step 5, Counting down can not be stopped.

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

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

[Touch-packages] [Bug 1389771] Re: [wizard] 4-digit passcode code gets set incorrectly as passphrase on first run

Nowadays the wizard lets you select the 4-digit pin code and set it, but
it's actually still the passphrase set during flashing. For ease of use
purposes, I now everytime go to system settings to really switch from
 passphrase to  4-digit passcode manually.

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

Title:
  [wizard] 4-digit passcode code gets set incorrectly as passphrase on
  first run

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  After setting the 4-digit passcode on the first run, the user
  encounters she needs to type the passcode with the normal qwerty
  keyboard instead every time when unlocking the phone, instead of the
  easy passcode entering.

  Reproduced once again after flashing my mako with --bootstrap from
  mako rtm 120 (=krillin rtm 143).

  Workaround: go to Lock security settings, change to 4-digit passcode
  manually.

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

-- 
Mailing list: https://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 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

2015-08-21 Thread Gene Soo

I believe I have discovered the cause of the problem.
Your prompting me to look at the Open Issues for VirtualBox pointed out
that I was on V5.0.0 and when I went to the Downloads Page, V5.0.2 was
currently available.
VirtualBox will send a push notification when the team indicates and
important release is available and is displayed when you start VirtualBox.
Although 5.0.2 is generally available, they did not mark it for Push
Notification.

I upgraded to 5.0.2 and also followed through with a process called Install
Guest Additions, that led to more serious errors.
The Guest Additions Scripting installs custom support for a variety of
system dependent things including advanced Video capabilities like Screen
resizing.
I had noticed this issue before but was not zoned in on it because it is a
critical failure for the new KDE Distro and not with the other Desktops.

I decided to backoff to VBox V4.33 which is the latest release for V4 of
VirtualBox.

Spot checking all of the 15.10 Distros having this audio problem, just
getting into alsamixer and adjusting the Volume Slider, they seem to work
correctly with VBox V4.33.

The VirtualBox Team had a V5.0.3 release that hasn't been finalized but is
available for users to manually install. I have not tried that release to
see if the Audio issues are resolved.

I need to turn my attention to reporting both this Audio Issue and the
Video issue to the respective Virtual Box teams.

I believe you can mark this issues as Closed.

Thanks for all of the help in getting this issue sorted out.

On Fri, Aug 21, 2015 at 7:00 AM, Raymond 1487...@bugs.launchpad.net
wrote:


 https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/intel8x0.c?id=4235a31784f59c9be5ff71534743c055091f9735

 the real ac97 controller 8086:2415 does not support 6 channels

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   Incomplete

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox
   dmi.board.vendor: Oracle Corporation
   dmi.board.version: 1.2
   dmi.chassis.type: 1
   dmi.chassis.vendor: Oracle Corporation
   dmi.modalias:
 dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
   dmi.product.name: VirtualBox
   dmi.product.version: 1.2
   dmi.sys.vendor: innotek GmbH

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions


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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Volume Slider is only controlling PCM channel and is not controlling
  Master. In effect, Master is restricting the audio level to the
  default of approximately 45 Percent. In order to raise the Master
  Volume Level, alsamixer is capable of changing Master. Without
  manually raising Master to Max Volume, Volume Slider can only control
  volume from 0-45% which is the default level of Master.

  Description:  Ubuntu Wily Werewolf (development branch)

[Touch-packages] [Bug 1486008] Re: leading actions width is too small making it very difficult to press on Nexus 4 (mako)

2015-08-21 Thread Jamie Young

** Changed in: ubuntu-ux
   Status: Incomplete = Confirmed

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

Title:
  leading actions width is too small making it very difficult to press
  on Nexus 4 (mako)

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

Bug description:
  Since a recent update to the ListItem leading actions in
  Ubuntu.Components 1.2, where the width of the action was clamped, the
  width is too small to press comfortably on a phone resulting in it
  missing 9 out of 10 tries. It affects the usability of the action and
  may be become a release blocker for apps that have recently switched
  over to the new list items.

  Sample App

  import QtQuick 2.4
  import Ubuntu.Components 1.2

  MainView {
  applicationName: testdelete.nik90
  width: units.gu(100)
  height: units.gu(75)

  Page {
  title: Swipe to Delete
  ListItem {
  id: listItem
  anchors.top: parent.top

  Label {
  text: Swipe me right to delete this listitem
  wrapMode: Text.WordWrap
  anchors { left: parent.left; leftMargin: units.gu(2); right: 
parent.right; verticalCenter: parent.verticalCenter }
  }

  
  leadingActions: ListItemActions {
  actions: [
  Action {
  iconName: delete
  onTriggered: listItem.destroy()
  }
  ]
  }
  }
  }
  }

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

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

[Touch-packages] [Bug 1425379] Re: touch browser crashes when invoking contextual menu in landscape orientation

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress = Fix Released

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

Title:
  touch browser crashes when invoking contextual menu in landscape
  orientation

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  copy text works fine in portrait, crashes in landscape..

  to reproduce exactly, was looking up how to sync my google calendar on
  https://help.ubuntu.com/community/SyncEvolution

  tried to copy one of the text boxes containing terminal commands -
  crashes every time in landscape mode

  TEST CASE
  1. Launch the web browser and open the amazon.com
  2. Rotate the device to landscape orientation
  3. Tap on the screen and hold your finger for a while

  ACTUAL RESULT
  Observe that webbrowser-app disappeared (closed or crashed)

  EXPECTED RESULT 
  No Crash

  ---

  1 - OS version 15.04 r111 (has been occurring over several updates though)
  1a- installed on nexus 4 via multirom

  2 - webbrowser-app version 0.23+15.04.20150217.1-0ubuntu1

  3 - i expected to get the selected text copied to the clipboard so i
  could paste it into the terminal

  4 - browser shut down and i was returned to the apps launcher

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

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

[Touch-packages] [Bug 1388201] Re: Toggling wifi on/off causes media playback to hiccup

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

Title:
  Toggling wifi on/off causes media playback to hiccup

Status in Canonical System Image:
  Confirmed
Status in Network Menu:
  Invalid
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  1. Play a song with music-app
  2. Switch wifi off, notice that music-app playback pauses for a moment
  3. Switch wifi on, notice that music-app playback pauses for a moment
  4. Watch the CPU usage with top while toggling wifi and notice that the usage 
spikes to 100%

  Expected results:

  Music or video keeps playing without pausing while toggling wifi
  on/off

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

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

[Touch-packages] [Bug 1487361] Re: 6.9 stopped respecting User in previous stanzas

2015-08-21 Thread Martin Pitt

Ah, thanks! I indeed had it after a Host block with indentation /
paragraph, so I was misled in thinking of them as actual paragraphs.
Putting CanonicalizeHostname at the top of the file indeed works.

So it seems this was a deliberate change, or just accidentally happened
to work before. So I guess we can close this. Thank you for your help!


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

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

Title:
  6.9 stopped respecting User in previous stanzas

Status in openssh package in Ubuntu:
  Won't Fix

Bug description:
  My ~/.ssh/config has

  Host *.canonical.com
  User pitti

  and some convenience aliases as the actual host names change from time
  to time:

  Host cdimage
  HostName nusakan.canonical.com

  Host langpack
  HostName macquarie.canonical.com

  For years, until the previous Wily version 6.7 this was working as
  expected. But since today with 6.9 trying to ssh to e. g. langpack
  stopped taking the User pitti into account:

  $ ssh -v cdimage
  [...]
  debug1: Authenticating to nusakan.canonical.com:22 as 'martin'
  [...]
  Permission denied (publickey).

  martin is my local user name at my laptop, i. e. the  default when
  User isn't set.

  If I don't use the alias and do ssh nusakan.canonical.com it does
  apply the User setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: openssh-client 1:6.9p1-1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 21 10:14:46 2015
  EcryptfsInUse: Yes
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:6.9p1-1
  SSHClientVersion: OpenSSH_6.9p1 Ubuntu-1, OpenSSL 1.0.2d 9 Jul 2015
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1444408] Re: Gallery App: loading full-screen preview forever after tap on a video from Gallery

** Changed in: gallery-app (Ubuntu)
   Status: New = Fix Released

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

Title:
  Gallery App: loading full-screen preview forever after tap on a video
  from Gallery

Status in gallery-app:
  New
Status in gallery-app package in Ubuntu:
  Fix Released

Bug description:
  arale, r170, ubuntu-touch/vivid-proposed

  Steps
  1. record a video with camera
  2. launch gallery
  3. tap (only one time) on video 

  Result
  It's trying to load a full-screen preview of the video forever.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gallery-app/+bug/108/+subscriptions

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

[Touch-packages] [Bug 1487361] Re: 6.9 stopped respecting User in previous stanzas

2015-08-21 Thread Colin Watson

It makes a difference for me, but CanonicalizeHostname has to be in the
right part of the file (not inside an inapplicable Host block; note that
indentation doesn't actually matter).  Perhaps I could see your whole
.ssh/config?

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

Title:
  6.9 stopped respecting User in previous stanzas

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  My ~/.ssh/config has

  Host *.canonical.com
  User pitti

  and some convenience aliases as the actual host names change from time
  to time:

  Host cdimage
  HostName nusakan.canonical.com

  Host langpack
  HostName macquarie.canonical.com

  For years, until the previous Wily version 6.7 this was working as
  expected. But since today with 6.9 trying to ssh to e. g. langpack
  stopped taking the User pitti into account:

  $ ssh -v cdimage
  [...]
  debug1: Authenticating to nusakan.canonical.com:22 as 'martin'
  [...]
  Permission denied (publickey).

  martin is my local user name at my laptop, i. e. the  default when
  User isn't set.

  If I don't use the alias and do ssh nusakan.canonical.com it does
  apply the User setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: openssh-client 1:6.9p1-1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 21 10:14:46 2015
  EcryptfsInUse: Yes
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:6.9p1-1
  SSHClientVersion: OpenSSH_6.9p1 Ubuntu-1, OpenSSL 1.0.2d 9 Jul 2015
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

2015-08-21 Thread Raymond

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/intel8x0.c?id=4235a31784f59c9be5ff71534743c055091f9735

the real ac97 controller 8086:2415 does not support 6 channels

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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Volume Slider is only controlling PCM channel and is not controlling
  Master. In effect, Master is restricting the audio level to the
  default of approximately 45 Percent. In order to raise the Master
  Volume Level, alsamixer is capable of changing Master. Without
  manually raising Master to Max Volume, Volume Slider can only control
  volume from 0-45% which is the default level of Master.

  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1330 F pulseaudio
gene   1922 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Aug 20 13:00:57 2015
  InstallationDate: Installed on 2015-08-19 (1 days ago)
  InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64 (20150819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_Type: Volume slider, or mixer problems
  Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Touch-packages] [Bug 1486953] Re: Power-off dialog doesn't appear if power key press begins when screen is off

** Branch linked: lp:~aacid/unity8/shutdown_from_off_screen

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

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

Title:
  Power-off dialog doesn't appear if power key press begins when screen
  is off

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  On arale with rc.proposed:

  1. Ensure the screen is off
  2. Press the power button and keep it pressed

  Expected result:
  The screen should turn on and the power-off dialog should appear after a few 
seconds.

  Actual result:
  The screen turns on but the power-off dialog doesn't appear. Eventually the 
phone reboots. I assume that this is because of hard reboot caused by pressing 
the power button for long enough, but more investigation is needed.

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

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

[Touch-packages] [Bug 1487471] [NEW] Udev rule for MTP with nvidia Shield

2015-08-21 Thread Jaufré Aligé

Public bug reported:

Hello,

Nvidia shield tab won't connect with mtp protocol on Ubuntu 14.04.3
It's a big trouble, many users tell me cameras or Svidia Shield are not 
supported.

To fix it for Nvidia Shield, we need to add the following Udev rule :

in file /lib/udev/rules.d/69-libmtp.rules

add this line :
ATTR{idVendor}==0955, ATTR{idProduct}==cf07, SYMLINK+=libmtp-%k, 
MODE=660, GROUP=audio, ENV{ID_MTP_DEVICE}=1, ENV{ID_MEDIA_PLAYER}=1

then of course restart udev service :
sudo service udev restart

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: udev 204-5ubuntu20.13
ProcVersionSignature: Ubuntu 3.13.0-62.101-generic 3.13.11-ckt24
Uname: Linux 3.13.0-62-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.12
Architecture: amd64
CurrentDesktop: Unity
CustomUdevRuleFiles: 60-vboxdrv.rules
Date: Fri Aug 21 15:20:08 2015
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=e057ab66-ce6b-4072-9fdb-59d76882e7cd ro quiet splash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/17/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1503
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H77-M PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1503:bd03/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug trusty

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

Title:
  Udev rule for MTP with nvidia Shield

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello,

  Nvidia shield tab won't connect with mtp protocol on Ubuntu 14.04.3
  It's a big trouble, many users tell me cameras or Svidia Shield are not 
supported.

  To fix it for Nvidia Shield, we need to add the following Udev rule :

  in file /lib/udev/rules.d/69-libmtp.rules

  add this line :
  ATTR{idVendor}==0955, ATTR{idProduct}==cf07, SYMLINK+=libmtp-%k, 
MODE=660, GROUP=audio, ENV{ID_MTP_DEVICE}=1, ENV{ID_MEDIA_PLAYER}=1

  then of course restart udev service :
  sudo service udev restart

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu20.13
  ProcVersionSignature: Ubuntu 3.13.0-62.101-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 60-vboxdrv.rules
  Date: Fri Aug 21 15:20:08 2015
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic 
root=UUID=e057ab66-ce6b-4072-9fdb-59d76882e7cd ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1503:bd03/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1461861] Re: Cannot dismiss 'No network' dialog

** Changed in: canonical-devices-system-image
   Status: Confirmed = Fix Committed

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

Title:
  Cannot dismiss 'No network' dialog

Status in Canonical System Image:
  Fix Committed
Status in messaging-app package in Ubuntu:
  Fix Released

Bug description:
  current build number: 24
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-06-03 23:14:51
  version version: 24
  version ubuntu: 20150603
  version device: 20150529-8e13c5f
  version custom: 20150528-722-29-15-vivid

  Test Case:
  Requires a SIM with no service

  1. Boot a freshly flashed device
  2. Don't unlock the SIM or use a SIM without credit
  3. Open the messaging app, select the SIM without service as default
  4. Enter a message and send it

  EXPECTED BEHAVIOUR
  The 'No network' dialog is displayed and can be dismissed

  ACTUAL RESULT
  The 'No network' dialog is displayed and cannot be dismissed
  Note that the 'swipe message' demo is displayed behind the 'no network' dialog

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

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

[Touch-packages] [Bug 1458694] Re: [vivid-overlay] unity8 fails to start on the emulator

2015-08-21 Thread Tim Peeters

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  [vivid-overlay] unity8 fails to start on the emulator

Status in Canonical System Image:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 140
  device name: generic_x86
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-05-25 12:02:10
  version version: 140
  version ubuntu: 20150525
  version device: 20150210
  version custom: 20150525

  When starting unity8 (this started at image 136, probably when mir
  0.13 landed):

  phablet@ubuntu-phablet:~$ cat ./.cache/upstart/unity8.log
  ()
  [1432595001.896139] mirplatform: Found graphics driver: dummy
  [1432595001.898447] mirplatform: Found graphics driver: android
  qtmir.mir: MirServer created
  [1432595003.675225] Server: Starting
  [1432595003.679331] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/server-platform
  [1432595003.679501] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-dummy.so
  [1432595003.680673] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so
  [1432595003.681107] WARNING Loader: Failed to load module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so (error 
was:/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so: undefined 
symbol: _ZN3mir6events10make_eventExx17MirKeyboardActionjij)
  [1432595003.684868] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-android.so.2
  [1432595003.685014] mirplatform: Found graphics driver: dummy
  [1432595003.685211] mirplatform: Found graphics driver: android
  [1432595003.685416] Platform Loader: Selected driver: android (version 0.13.0)
  qtmir.mir: PromptSessionListener::PromptSessionListener - this= 
PromptSessionListener(0x9679764)
  qtmir.mir: SessionListener::SessionListener - this= SessionListener(0x9676d24)
  qtmir.mir: MirShell::MirShell
  [1432595003.883766] DisplayServer: Mir version 0.13.0
  QtCompositor::setAllWindowsExposed true
  qtmir.clipboard: D-Bus registration successful.
  Mode argument was not provided or was set to an illegal value. Using default 
value of --mode= full-greeter
  Cannot create window: no screens available

  With version 135 it starts fine, but not fully functional, giving this
  error:

  QOpenGLShader::compile(Fragment): 0:2(12): warning: extension 
`GL_OES_standard_derivatives' unsupported in fragment shader
  0:2(1): error: #extension directive is not allowed in the middle of a shader

  *** Problematic Fragment shader source code ***
  #extension GL_OES_standard_derivatives : enable  // Enable dFdy() on OpenGL 
ES 2.
  #define lowp
  #define mediump
  #define highp

  // Copyright Â© 2015 Canonical Ltd.
  //
  // This program is free software; you can redistribute it and/or modify
  // it under the terms of the GNU Lesser General Public License as published by
  // the Free Software Foundation; version 3.
  //
  // This program is distributed in the hope that it will be useful,
  // but WITHOUT ANY WARRANTY; without even the implied warranty of
  // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  // GNU Lesser General Public License for more details.
  //
  // You should have received a copy of the GNU Lesser General Public License
  // along with this program.  If not, see http://www.gnu.org/licenses/.
  //
  // Author: LoÃ¯c Molinari loic.molin...@canonical.com

  // Static flow control (branching on a uniform value) is fast on most GPUs 
(including ultra-low
  // power ones) because it allows to use the same shader execution path for an 
entire draw call. We
  // rely on that technique here (also known as uber-shader solution) to 
avoid the complexity of
  // dealing with a multiple shaders solution.
  // FIXME(loicm) Validate GPU behavior with regards to static flow control.

  uniform sampler2D shapeTexture;
  uniform sampler2D sourceTexture;
  uniform lowp vec2 dfdtFactors;
  uniform lowp vec2 opacityFactors;
  uniform lowp float sourceOpacity;
  uniform lowp float distanceAA;
  uniform bool textured;
  uniform mediump int aspect;

  varying mediump vec2 shapeCoord;
  varying mediump vec4 sourceCoord;
  varying lowp vec4 backgroundColor;

  const mediump int FLAT  = 0x08;  // 1  3
  const mediump int INSET = 0x10;  // 1  4

  void main(void)
  {
  lowp vec4 shapeData = texture2D(shapeTexture, shapeCoord);
  lowp vec4 color = backgroundColor;

  // FIXME(loicm) Would be better to use a bitfield but bitwise ops have 
only been integrated in
  // GLSL 1.3 (OpenGL 3) and GLSL ES 3 (OpenGL ES 3).
  if (textured) {
  // Blend the source over the current color.
  //

[Touch-packages] [Bug 1458694] Re: [vivid-overlay] unity8 fails to start on the emulator

As per QA report:
Needs a fix in unity8 so we can get past edges demo and confirm there are no 
further issues with the silo before landing.

This is now fixed from UITK and Mir points of view. The remaining issue
is that Unity 8 needs to automatically skip the edges demo when used
inside the emulator.

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

Title:
  [vivid-overlay] unity8 fails to start on the emulator

Status in Canonical System Image:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed
Status in unity8 package in Ubuntu:
  New

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 140
  device name: generic_x86
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-05-25 12:02:10
  version version: 140
  version ubuntu: 20150525
  version device: 20150210
  version custom: 20150525

  When starting unity8 (this started at image 136, probably when mir
  0.13 landed):

  phablet@ubuntu-phablet:~$ cat ./.cache/upstart/unity8.log
  ()
  [1432595001.896139] mirplatform: Found graphics driver: dummy
  [1432595001.898447] mirplatform: Found graphics driver: android
  qtmir.mir: MirServer created
  [1432595003.675225] Server: Starting
  [1432595003.679331] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/server-platform
  [1432595003.679501] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-dummy.so
  [1432595003.680673] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so
  [1432595003.681107] WARNING Loader: Failed to load module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so (error 
was:/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so: undefined 
symbol: _ZN3mir6events10make_eventExx17MirKeyboardActionjij)
  [1432595003.684868] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-android.so.2
  [1432595003.685014] mirplatform: Found graphics driver: dummy
  [1432595003.685211] mirplatform: Found graphics driver: android
  [1432595003.685416] Platform Loader: Selected driver: android (version 0.13.0)
  qtmir.mir: PromptSessionListener::PromptSessionListener - this= 
PromptSessionListener(0x9679764)
  qtmir.mir: SessionListener::SessionListener - this= SessionListener(0x9676d24)
  qtmir.mir: MirShell::MirShell
  [1432595003.883766] DisplayServer: Mir version 0.13.0
  QtCompositor::setAllWindowsExposed true
  qtmir.clipboard: D-Bus registration successful.
  Mode argument was not provided or was set to an illegal value. Using default 
value of --mode= full-greeter
  Cannot create window: no screens available

  With version 135 it starts fine, but not fully functional, giving this
  error:

  QOpenGLShader::compile(Fragment): 0:2(12): warning: extension 
`GL_OES_standard_derivatives' unsupported in fragment shader
  0:2(1): error: #extension directive is not allowed in the middle of a shader

  *** Problematic Fragment shader source code ***
  #extension GL_OES_standard_derivatives : enable  // Enable dFdy() on OpenGL 
ES 2.
  #define lowp
  #define mediump
  #define highp

  // Copyright Â© 2015 Canonical Ltd.
  //
  // This program is free software; you can redistribute it and/or modify
  // it under the terms of the GNU Lesser General Public License as published by
  // the Free Software Foundation; version 3.
  //
  // This program is distributed in the hope that it will be useful,
  // but WITHOUT ANY WARRANTY; without even the implied warranty of
  // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  // GNU Lesser General Public License for more details.
  //
  // You should have received a copy of the GNU Lesser General Public License
  // along with this program.  If not, see http://www.gnu.org/licenses/.
  //
  // Author: LoÃ¯c Molinari loic.molin...@canonical.com

  // Static flow control (branching on a uniform value) is fast on most GPUs 
(including ultra-low
  // power ones) because it allows to use the same shader execution path for an 
entire draw call. We
  // rely on that technique here (also known as uber-shader solution) to 
avoid the complexity of
  // dealing with a multiple shaders solution.
  // FIXME(loicm) Validate GPU behavior with regards to static flow control.

  uniform sampler2D shapeTexture;
  uniform sampler2D sourceTexture;
  uniform lowp vec2 dfdtFactors;
  uniform lowp vec2 opacityFactors;
  uniform lowp float sourceOpacity;
  uniform lowp float distanceAA;
  uniform bool textured;
  uniform mediump int aspect;

  varying mediump vec2 shapeCoord;
  varying mediump vec4 sourceCoord;
  varying lowp vec4 backgroundColor;

  const mediump int FLAT  = 0x08;  // 1  3
  const mediump int INSET = 0x10;  // 1  4

  void main(void)
  {
  lowp vec4 shapeData =

[Touch-packages] [Bug 1395724] Re: Cannot type into account login input boxes

Marking this as fix released for unity8 since we're under the vivid OTA
now.

** Changed in: unity8 (Ubuntu)
   Status: Triaged = Fix Released

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

Title:
  Cannot type into account login input boxes

Status in Canonical System Image:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu RTM:
  Confirmed

Bug description:
  1. Open system settings and go to accounts.
  2. tap on 'Google' to add a google account
  3. When the login page opens drag down the indicator bar from the top
  4. Now try to type into the username/password boxes.

  What happens:
  OSK does not appear to type in there.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: ubuntu-system-settings-online-accounts 
0.5+14.10.20141029~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Mon Nov 24 13:29:58 2014
  InstallationDate: Installed on 2014-11-21 (2 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141121-220606)
  SourcePackage: ubuntu-system-settings-online-accounts
  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/1395724/+subscriptions

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

[Touch-packages] [Bug 1487513] [NEW] Empty space in Photos page

2015-08-21 Thread Víctor R . Ruiz

Public bug reported:

Test case.
- Flash the phone.
- Take some pictures with the camera.
- Open the gallery app.
- Go to Photos view.

Expected result.
- Photos page displays the photos right below the title bar.

Actual result.
- An empty row is displayed. Scrolling makes the photos to move up.

current build number: 104
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en

** Affects: gallery-app (Ubuntu)
Importance: Undecided
Status: New

** Tags: qa-regression

** Attachment added: screenshot20150821_145831771.png

https://bugs.launchpad.net/bugs/1487513/+attachment/4450276/+files/screenshot20150821_145831771.png

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

Title:
Empty space in Photos page

Status in gallery-app package in Ubuntu:
New

Bug description:
Test case.
- Flash the phone.
- Take some pictures with the camera.
- Open the gallery app.
- Go to Photos view.

Expected result.
- Photos page displays the photos right below the title bar.

Actual result.
- An empty row is displayed. Scrolling makes the photos to move up.

current build number: 104
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en

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

--
Mailing list: https://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 1486696] [NEW] lxc-create -B btrfs fails if lxc.lxcpath is not on the same filesystem as /var/cache/lxc (not a configurable option)

2015-08-21 Thread Serge Hallyn

Indeed this is expected behavior.  Since there is no way to
create a btrfs subvolume in this instance, and you explicitly
asked for a btrfs subvolume, it should error.  A simple directory
copy must be used.

I think it might be reasonable to say that even if it has to
do a full directory copy, it could still create a new subvolume
so that clones can be done as snapshots.  Patches for either that
or for documentation improvement are welcome, so leaving this bug
open

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

Title:
  lxc-create -B btrfs fails if lxc.lxcpath is not on the same filesystem
  as /var/cache/lxc (not a configurable option)

Status in lxc package in Ubuntu:
  Triaged

Bug description:
  ## Version
  Description:Ubuntu 15.04
  Release:15.04
  lxc:
Installed: 1.1.2-0ubuntu3.1
Candidate: 1.1.2-0ubuntu3.1
Version table:
   *** 1.1.2-0ubuntu3.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.2-0ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

  ## Config changes from default
  cat /etc/lxc/lxc.conf 
  lxc.lxcpath = /srv/vservers/lxc

  ## Mount details
  /var/cache/lxc in on root filesystem
  /srv/vservers/lxc is a btrfs mount point

  ## Command used (sample)
   sudo lxc-create -B btrfs --name test-bt -t ubuntu -- -r trusty

  ## Error (sample)
  Copy /var/cache/lxc/trusty/rootfs-amd64 to /srv/vservers/lxc/test-bt/rootfs 
... 
  Copying rootfs to /srv/vservers/lxc/test-bt/rootfs ...
  Transaction commit: none (default)
  Delete subvolume '/srv/vservers/lxc/test-bt/rootfs'
  Create a snapshot of '/var/cache/lxc/trusty/rootfs-amd64' in 
'/srv/vservers/lxc/test-bt/rootfs'
  ERROR: cannot snapshot '/var/cache/lxc/trusty/rootfs-amd64' - Invalid 
cross-device link
  lxc_container: lxccontainer.c: create_run_template: 1108 container creation 
template for test-bt failed
  lxc_container: lxccontainer.c: container_destroy: 2056 Error destroying 
rootfs for test-bt
  lxc_container: lxc_create.c: main: 274 Error creating container test-bt

  ## Thoughts
  Maybe this is the expected behavior, if so a Documentation update stating 
something to the effect of If you change the lxcpath to a different filesystem 
than the one where /var/cache/lxc livs you cannot create a btrfs backed 
container.
  -or-
  Let /var/cache/lxc be configured via lxc.conf and have the documentation note 
that they should reside on the same filesystem.

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

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

[Touch-packages] [Bug 1474435] Re: [dialler] Smart dialing is not supported

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

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

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

Title:
  [dialler] Smart dialing is not supported

Status in Ubuntu UX:
  Triaged
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  In Android, Windows phone, and older platforms (meaning, everywhere
  but iOS and apparently Jolla) you can  use the T9 letters in the
  dialer app to type the beginning of names and get suggested phone
  numbers.

  For example, if Mom is a contact, then typing 66 will suggest
  contacts that start with / contain mo, even if the number doesn't
  include 66.

  I swear that Mom being 666 in this context is purely a coincidence, my
  mom is a perfectly lovely person :-)

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

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

[Touch-packages] [Bug 1478723] Re: Predictive Dialing

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

thanks, that's somewhat related to bug #1449691

** Changed in: dialer-app (Ubuntu)
   Importance: Undecided = Low

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

Title:
  Predictive Dialing

Status in dialer-app package in Ubuntu:
  New

Bug description:
  Hello everyone.

  I think it would be useful to introduce the predictive dialing
  keyboard, already equipped with alphabetic characters.

  In practice, by dialing the name of the person in your address book,
  using the letters on the keyboard, the phone should display the
  contacts that match the series of letters that you have typed.

  It might be added a button to change from normal composition to
  predictive dialing.

  g

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

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

[Touch-packages] [Bug 1478723] Re: Predictive Dialing

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

or rather bug #1474435

** This bug has been marked a duplicate of bug 1474435
   [dialler] Smart dialing is not supported

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

Title:
  Predictive Dialing

Status in dialer-app package in Ubuntu:
  New

Bug description:
  Hello everyone.

  I think it would be useful to introduce the predictive dialing
  keyboard, already equipped with alphabetic characters.

  In practice, by dialing the name of the person in your address book,
  using the letters on the keyboard, the phone should display the
  contacts that match the series of letters that you have typed.

  It might be added a button to change from normal composition to
  predictive dialing.

  g

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

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

[Touch-packages] [Bug 1389771] Re: [wizard] 4-digit passcode code gets set incorrectly as passphrase on first run

2015-08-21 Thread Michael Terry

Timo, looks like I never actually explained what's going on behind the
scenes in this bug.  There are two things going on in your workflow:

1) ubuntu-device-flash treats the --password argument as a passphrase
always.  Ideally it would inspect and see if it looks like a PIN, then
set it as such.

2) The wizard can't override an existing password for the user.  Ideally
if a password was already set, those pages would be skipped or grayed
out or something.

So that's two poor usability issues combining to be confusing when
flashing with --password.  But it's not a bug normal users see, just
developers.  I'd argue both could/should be fixed.  But they just
haven't been a priority.

** Summary changed:

- [wizard] 4-digit passcode code gets set incorrectly as passphrase on first 
run
+ [wizard] 4-digit passcode code gets set incorrectly as passphrase on first 
run when flashing with --password

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

Title:
  [wizard] 4-digit passcode code gets set incorrectly as passphrase on
  first run when flashing with --password

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  After setting the 4-digit passcode on the first run, the user
  encounters she needs to type the passcode with the normal qwerty
  keyboard instead every time when unlocking the phone, instead of the
  easy passcode entering.

  Reproduced once again after flashing my mako with --bootstrap from
  mako rtm 120 (=krillin rtm 143).

  Workaround: go to Lock security settings, change to 4-digit passcode
  manually.

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

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

[Touch-packages] [Bug 1487469] Re: Several rated apps are shown * 0.0 rate

2015-08-21 Thread Martin Albisetti

** Package changed: unity-scope-click (Ubuntu) = software-center-agent

** Changed in: software-center-agent
   Importance: Undecided = High

** Changed in: software-center-agent
   Status: New = In Progress

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

Title:
  Several rated apps are shown * 0.0 rate

Status in Software Center Agent:
  In Progress

Bug description:
  Navigate for example to: Ubuntu Store - Communication - App Internet the 
most popular...
  All the apps are displayed * 0.0 rates although they all have been rated, 
see attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/software-center-agent/+bug/1487469/+subscriptions

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

[Touch-packages] [Bug 1462489] Re: Allow apps to keep the screen on

I'm going to set this as fix released for unity8 since it's already
working for apps and i don't see what could be missing from unity8.

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

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

Title:
  Allow apps to keep the screen on

Status in Canonical System Image:
  Fix Released
Status in Canonical Click Reviewers tools:
  Fix Released
Status in Ubuntu Developer Portal:
  New
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  Fix Released
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  Support an interface in QML and HTML to allow an app to keep the
  screen on while the app is active. This has come up in several
  scenarios, such as an ebook reader, a clock in night mode.

  First step is to hook up QtSystemInfo screenSaverEnabled

  One solution to inhibit the screen blanking:

  Add a new dbus rule to the default template
  Provide a mediator (unity8) to control this, so it can restore the screen 
blanking when the app is not active or has been closed
  Prompt the user for confirmation the first time the app accesses it
  use the trust store to avoid prompts each time
  add to the System settings Other app access panel an entry for Screen or 
Display so the setting could be revoked

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

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

[Touch-packages] [Bug 1486996] Re: “Call” icon does not actually place a call

2015-08-21 Thread Magdalena Mirowicz

** Changed in: ubuntu-ux
   Importance: Undecided = Low

** Changed in: ubuntu-ux
   Status: New = Triaged

** Changed in: ubuntu-ux
 Assignee: (unassigned) = Olga Kemmet (olga-kemmet)

** Summary changed:

- “Call” icon does not actually place a call
+ [Dialer] [Address Book] “Call” icon does not actually place a call

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

Title:
  [Dialer] [Address Book] “Call” icon does not actually place a call

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Triaged
Status in address-book-app package in Ubuntu:
  New
Status in dialer-app package in Ubuntu:
  New

Bug description:
  Reproduce:
  Open address-book-app, choose contact. Press the phone-off-the-hook icon to 
place a call

  What happens:
  The dialer-app opens with a number pre-filled.

  What I expected would happen:
  I expected the call to be placed.

  Rationale:
  The phone-off-the-hook icon in dialer-app represents placing a call, but not 
in address-book-app. Why the inconsistency?

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

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

[Touch-packages] [Bug 1487157] Re: mako and flo should have hotspot disabled

** Branch linked: lp:~unity-api-team/indicator-network/hotspot-cellular-
enabled-properties

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

Title:
  mako and flo should have hotspot disabled

Status in indicator-network package in Ubuntu:
  New

Bug description:
  METABUG FOR OTA6:

  Mako has an issue with wpa-supplicant that use 100% of the cpu and stops the 
phone from functioning as expected when hotspot is in use.
  Mako currently has hotspot installed, it can be enabled but devices can not 
connect to it.
  https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1429314

  Flo only has one modem wifi which is turn into the outgoing source for 
hotspot therefore disabling wifi.
  https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1487158

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

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

[Touch-packages] [Bug 1483127] Re: Proximity does not turn screen on during a call

2015-08-21 Thread Łukasz Zemczak

** Tags added: lt-category-visible

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

Title:
  Proximity does not turn screen on during a call

Status in Canonical System Image:
  New
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  This has regressed a week or two ago. It's not reliably reproducible,
  but bites me almost every time I want to end a call. It might be
  incoming calls only, or maybe only after a minute.

  Steps:
  * go on a call
  * cover the proximity sensor
  * uncover the proximity sensor

  Expected:
  * screen goes off/on as you cover/uncover the sensor

  Current:
  * screen goes off but not back on

  $ system-image-cli -i
  current build number: 90
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-08-08 21:08:55
  version version: 90
  version ubuntu: 20150807.1
  version device: 20150716-fb60d96
  version custom: 20150717-820-30-25-vivid

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

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

[Touch-packages] [Bug 1478257] Re: [MX4] phone does not ring and call can not be picked up

could be a duplicate of bug #1471338 that should be fixed with the
coming ota update

** Changed in: dialer-app (Ubuntu)
   Importance: Undecided = High

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

Title:
  [MX4] phone does not ring and call can not be picked up

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I noticed that sometimes I can not answer a call on the Meizu MX4 (OTA-5 
installed). Symptoms when someone tries to call:
  - no ringtone (even though the phone is not set to silent)
  - the display wakes, now on the first attempt the red and green buttons 
appear. I accept the call, but I can hear nothing and the person who is calling 
still gets the ringtone on his side - so the call actually was never picked 
up.
  - if immediately called again the screen wakes, but this time the red/green 
buttons to answer the call do not appear anymore at all
  - the call is registered as missed call in the notifications

  I observed this behavior already two times so far. So it keeps
  reappearing, although it is not exactly reproducible in the sense that
  it would happen always. I have accepted calls with the phone, which
  was not powered off between the time when it did work and now that it
  doesn't work.

  Please let me know, if you need further details and I will try to
  provide them.

  release: ubuntu 15.04 (r3)

  Thomas

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

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

[Touch-packages] [Bug 1477146] Re: [inconsistency] Contacts list opened from the Dialer shows + Create New on the first place

** Package changed: dialer-app (Ubuntu) = address-book-app (Ubuntu)

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

Title:
  [inconsistency] Contacts list opened from the Dialer shows + Create
  New on the first place

Status in Ubuntu UX:
  New
Status in address-book-app package in Ubuntu:
  New

Bug description:
  When You open Contacts from the Dialer, a + Create New item is shown
  as the first in the list. This takes too much space and is pretty
  obtrusive, especially in the Favourites tab, which is supposed to
  contain already existing contacts only. The solution could be to
  change this item to a draggable  +  in the bottom of the screen, the
  same way as it works in the stand-alone Contacts app already.

  Version: 0.1+15.04.20150415.2-0ubuntu1

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

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

[Touch-packages] [Bug 1474319] Re: app spread only shows shadows of apps, no content

2015-08-21 Thread Daniel d'Andrada

So we got a fix for it in untiy8.
The terminal case from comment #3 is actually bug 1485608

** Branch linked: lp:~gerboland/unity8/fixGhostAppsWithRotatino

** Branch unlinked: lp:~dandrader/unity8/ghostApps2

** Changed in: unity8 (Ubuntu)
   Status: Invalid = Confirmed

** Changed in: qtmir (Ubuntu)
   Status: In Progress = Invalid

** Changed in: qtmir (Ubuntu)
 Assignee: Daniel d'Andrada (dandrader) = (unassigned)

** Changed in: qtmir
 Assignee: Daniel d'Andrada (dandrader) = (unassigned)

** Changed in: qtmir
   Status: In Progress = Invalid

** Description changed:

  on arale rc-proposed i'm hitting a bug in the spread since a while where
  apps do not have any content in the spread overview anymore but only
  show their shadow ...
  
  the image at http://i.imgur.com/r7tnyym.png shows the issue, as you can
  see the two front apps do not have any content but show only their
  shadow ... tapping on such an app to foreground it restarts it properly
  and the content is visible in the spread again.
  
  i do not see this behavior on krillin..
- 
- 
- 
- One way to reproduce:
- * open terminal
- * tap on Ctrl+D
- 
- Terminal's gone, but ghost remains.

** Changed in: unity8 (Ubuntu)
 Assignee: Daniel d'Andrada (dandrader) = Gerry Boland (gerboland)

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

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

Title:
  app spread only shows shadows of apps, no content

Status in QtMir:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  on arale rc-proposed i'm hitting a bug in the spread since a while
  where apps do not have any content in the spread overview anymore but
  only show their shadow ...

  the image at http://i.imgur.com/r7tnyym.png shows the issue, as you
  can see the two front apps do not have any content but show only their
  shadow ... tapping on such an app to foreground it restarts it
  properly and the content is visible in the spread again.

  i do not see this behavior on krillin..

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

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

[Touch-packages] [Bug 1480088] Re: Improper message if dial without SIM card inserted

Thanks, a guess it's slightly confusing but it's not that common that
users try to use a phone without SIM to do calls

** Changed in: dialer-app (Ubuntu)
   Importance: Undecided = Low

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

Title:
  Improper message if dial without SIM card inserted

Status in Canonical System Image:
  New
Status in dialer-app package in Ubuntu:
  New

Bug description:
  Test Environment:

  current build number: 72
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-09-28 04:55:39
  version version: 72
  version ubuntu: 20150729
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  Steps to reproduce:
  1.Get a phone without SIM card
  2.Open dial app
  3.Dial a valid number
  4.Observe the result

  Actual result:
  Improper message displays ¨No network: There is currently no network¨, see 
attached pic.

  Expected result:
  It should be ¨No SIM card¨

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

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

[Touch-packages] [Bug 1486004] Re: Cannot import contacts from sim card ( ofono crash )

** Changed in: address-book-app (Ubuntu)
   Status: New = Incomplete

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

Title:
  Cannot import contacts from sim card ( ofono crash )

Status in Canonical System Image:
  New
Status in address-book-app package in Ubuntu:
  Incomplete
Status in ofono package in Ubuntu:
  Confirmed

Bug description:
  I open a new bug as asked from this bug (last comment #14) :
  https://bugs.launchpad.net/ubuntu/+source/address-book-
  app/+bug/1331346?comments=all

  I've got a meizu mx4 ubuntu phone, but i cannot import contacts from
  the sim card, it makes some wierd messages but never stop, and no
  contact is imported.

  As asked in the previous bug repport, the /var/log/syslog file attached and 
the output :
  Warning: Permanently added '[127.0.0.1]:1' (RSA) to the list of known 
hosts.
  Welcome to Ubuntu 15.04 (GNU/Linux 3.10.35+ armv7l)

   * Documentation:  https://help.ubuntu.com/
  Last login: Mon Jul 20 17:05:07 2015 from localhost.localdomain
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/test-phonebook /ril_0
  Traceback (most recent call last):
File /usr/share/ofono/scripts/test-phonebook, line 23, in module
  print(phonebook.Import(timeout=100))
File /usr/lib/python3/dist-packages/dbus/proxies.py, line 70, in __call__
  return self._proxy_method(*args, **keywords)
File /usr/lib/python3/dist-packages/dbus/proxies.py, line 145, in __call__
  **keywords)
File /usr/lib/python3/dist-packages/dbus/connection.py, line 651, in 
call_blocking
  message, timeout)
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
did not receive a reply (timeout by message bus)
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/test-phonebook /ril_1
  Traceback (most recent call last):
File /usr/share/ofono/scripts/test-phonebook, line 23, in module
  print(phonebook.Import(timeout=100))
File /usr/lib/python3/dist-packages/dbus/proxies.py, line 70, in __call__
  return self._proxy_method(*args, **keywords)
File /usr/lib/python3/dist-packages/dbus/proxies.py, line 145, in __call__
  **keywords)
File /usr/lib/python3/dist-packages/dbus/connection.py, line 651, in 
call_blocking
  message, timeout)
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownObject: 
Method Import with signature  on interface org.ofono.Phonebook doesn't 
exist

  phablet@ubuntu-phablet:~$

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

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

[Touch-packages] [Bug 1487129] Re: camera-app mic permission item blank

2015-08-21 Thread Allan LeSage

@mpt, lp:1487152 also relevant to two-perms schema.

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

Title:
  camera-app mic permission item blank

Status in Canonical System Image:
  In Progress
Status in pulseaudio package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  Working through camera/mic trust issues, discovering that the camera-
  app's mic item under Other app access is blank, will attach a
  screenie.

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

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

[Touch-packages] [Bug 1431328] Re: build.sh --setup doesn't install build dependencies

I think we should close this bug, build.sh --setup doesn't install the
dependencies, it's the first run of build that does.

** Changed in: unity8 (Ubuntu)
   Status: Triaged = Incomplete

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

Title:
  build.sh --setup doesn't install build dependencies

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  DISTRO
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  EXPECTED
  after build.sh -s completes I am able to build unity8 with build.sh

  ACTUAL
  build.sh -s doesn't install libsystemsettings-dev so the compilation 
afterwards fails with 

  -- Could NOT find Lcov (missing:  LCOV_EXECUTABLE GENHTML_EXECUTABLE) 
  -- Could NOT find gcovr (missing:  GCOVR_EXECUTABLE) 
  Package SystemSettings was not found in the pkg-config search path.
  Perhaps you should add the directory containing `SystemSettings.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'SystemSettings' found
  CMake Error at CMakeLists.txt:67 (message):
Could not determine USS private plugin installation dir.

  MORE INFORMATION
  You can find the build.sh -s output at http://pastebin.ubuntu.com/10585178/

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

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

[Touch-packages] [Bug 1471695] Re: [indicators] Too dark, invisible icons

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

** This bug has been marked a duplicate of bug 1457098
   [Indicators] Expanded indicators are not visible in direct sunlight

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

Title:
  [indicators] Too dark, invisible icons

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  What I already wrote on the ubuntu-phone mailing list and what many people 
found also as a problem is the visibility of the icons in the panel. I attached 
a photo from my bq. One of the photos was taken in a quite dark room so we are 
able to see the icons more or less clearly but then outside I'm only able to 
clearly see the active icon even with the brightness set on 100%. How could 
anyone create grey icons on a grey background?! My proposition is all icons 
white, and the active one alien-green like #12ed0d or light orange. Yellow will 
also be not the very best idea. In my opinion the best solution is light-green 
and white and then the background can stay as it is now.
  The other member of Polish Translators Team has a MX4 with the same problem 
so it is not only bq.

  
  -

  Desired resolution:

  Highlighted text in #FF
  Adjust the colour value to #88

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

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

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

2015-08-21 Thread Ken VanDine

** Branch linked: lp:~ken-vandine/content-hub/dont_swallow_deactivate

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

Title:
  Using ContentStore disables silently any StateSaver capability

Status in content-hub package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  1. Create the default template project
  2. Add on the page (with an id):
  TextField {
  id: foo
  StateSaver.properties: text
  }
  3. run the app, type something in the field, xkill it, restart
  - the TextField content is restored by the StateSaver.
  4. import Ubuntu.Content 1.1
  - StateSaver still works
  5. add anywhere on the page:
  ContentStore {
  id: appContentStore
  scope: ContentScope.App
  }
  - The state is not restored anymore (note that it may be the first time, 
restoring when there was no ContentStore at kill time), then it constantly 
fails to restore.

  There is no warning or anything that reported an issue.

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

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

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

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

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

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

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

Title:
  Using ContentStore disables silently any StateSaver capability

Status in content-hub package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  1. Create the default template project
  2. Add on the page (with an id):
  TextField {
  id: foo
  StateSaver.properties: text
  }
  3. run the app, type something in the field, xkill it, restart
  - the TextField content is restored by the StateSaver.
  4. import Ubuntu.Content 1.1
  - StateSaver still works
  5. add anywhere on the page:
  ContentStore {
  id: appContentStore
  scope: ContentScope.App
  }
  - The state is not restored anymore (note that it may be the first time, 
restoring when there was no ContentStore at kill time), then it constantly 
fails to restore.

  There is no warning or anything that reported an issue.

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

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

[Touch-packages] [Bug 1487158] Re: Hot-spot should only be available when there is a modem to support it.

** Branch linked: lp:~unity-api-team/indicator-network/hotspot-cellular-
enabled-properties

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

Title:
  Hot-spot should only be available when there is a modem to support it.

Status in indicator-network package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Install the latest rc-proposed image on flo

  EXPECTED:
  I expect to see no hotspot mode as there is only wifi available on flo

  ACTUAL:
  Hotspot is available and when enabled disabled the wifi.

  USER CASE:
  If at all possible it should be made that only when there is a 2/3/4g 
connection available that hotspot is available.  popey pointed out correctly 
that on flo there is no modem right now, but if it were docked or a 3g modem 
plugged in it then would have.

  POTENTIAL SOLUTION:
  The enable disable button in hotspot mode should only be pressable when the 
circumstances are true, this way there is no need to hid the option just make 
it so it can not be enabled if the circumstances are false.

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

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

[Touch-packages] [Bug 1388201] Re: Toggling wifi on/off causes media playback to hiccup

This bug is specific to arale, krillin, and most likely vegatta (
although as I don't have once, I haven't been able to test ).  It's
related to the fact that on devices using MTK's Wi-Fi driver, we're
forced to use hybris for power control of the Wi-Fi radios.  This
leverages the Android HAL functions wifi_load/unload_driver().  On
systems configured without kernel modules, this results in a driver
command to start/stop Wi-Fi ( this is accomplished by writing the string
0 or 1 to the character device ( /dev/wmtWiFi ).

I just checked mako ( rc-proposed, #222 ) and no stuttering occurs when
Wi-Fi is enabled or disabled.

Also re-checked arale ( rc-proposed, #88 ) and krillin ( rc-proposed,
#104 ) and both still skip/stutter when Wi-Fi is toggled.

Bug #1487529 reported for arale.

** Summary changed:

- Toggling wifi on/off causes media playback to hiccup
+ [arale/krillin] Toggling wifi on/off causes media playback to hiccup

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

Title:
  [arale/krillin] Toggling wifi on/off causes media playback to hiccup

Status in Canonical System Image:
  Confirmed
Status in Network Menu:
  Invalid
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  1. Play a song with music-app
  2. Switch wifi off, notice that music-app playback pauses for a moment
  3. Switch wifi on, notice that music-app playback pauses for a moment
  4. Watch the CPU usage with top while toggling wifi and notice that the usage 
spikes to 100%

  Expected results:

  Music or video keeps playing without pausing while toggling wifi
  on/off

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

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

[Touch-packages] [Bug 1487534] [NEW] Unable to set Alt+Shift for switching keyboard layout

2015-08-21 Thread anatoly techtonik

Public bug reported:

I used to Alt+Shift combination for switching keyboard layouts. but I
can't find where to do this. Right clicking on language indicator and
choosing Preferences open IBus configuration window. But when I set
Alt+Shift, it just hangs.

** Affects: ubuntustudio
 Importance: Undecided
 Status: New

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

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

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

Title:
  Unable to set Alt+Shift for switching keyboard layout

Status in Ubuntu Studio:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  I used to Alt+Shift combination for switching keyboard layouts. but I
  can't find where to do this. Right clicking on language indicator and
  choosing Preferences open IBus configuration window. But when I set
  Alt+Shift, it just hangs.

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

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

[Touch-packages] [Bug 1423382] Re: unable to use apport to report a bug from point release Live CDs

2015-08-21 Thread Brian Murray

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

** This bug has been marked a duplicate of bug 1471903
   -updates, -security missing from apt lists

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

Title:
  unable to use apport to report a bug from point release Live CDs

Status in apport package in Ubuntu:
  New

Bug description:
  Running apt-cache policy apport on an Ubuntu 14.04.2 Live CD returns
  the following:

  apport:
Installed: 2.14.1-0ubuntu3.7
Candidate: 2.14.1-0ubuntu3.7
Version table:
   *** 2.14.1-0ubuntu3.7 0
  100 /var/lib/dpkg/status
   2.14.1-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  Because there is no record of where the package came from, the package
  is considered unofficial and its not possible to use ubuntu-bug
  apport to report a bug about apport or any other package.

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

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

[Touch-packages] [Bug 1483127] Re: Proximity does not turn screen on during a call

confirmed, it doesn't turn the screen off when you remove the phone from
your ear to hang up, quite annoying

** Changed in: telephony-service (Ubuntu)
   Importance: Undecided = High

** Changed in: telephony-service (Ubuntu)
   Status: New = Confirmed

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

Title:
  Proximity does not turn screen on during a call

Status in Canonical System Image:
  New
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  This has regressed a week or two ago. It's not reliably reproducible,
  but bites me almost every time I want to end a call. It might be
  incoming calls only, or maybe only after a minute.

  Steps:
  * go on a call
  * cover the proximity sensor
  * uncover the proximity sensor

  Expected:
  * screen goes off/on as you cover/uncover the sensor

  Current:
  * screen goes off but not back on

  $ system-image-cli -i
  current build number: 90
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-08-08 21:08:55
  version version: 90
  version ubuntu: 20150807.1
  version device: 20150716-fb60d96
  version custom: 20150717-820-30-25-vivid

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

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

[Touch-packages] [Bug 1483127] Re: Proximity does not turn screen on during a call

** Changed in: telephony-service (Ubuntu)
   Importance: High = Critical

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

Title:
  Proximity does not turn screen on during a call

Status in Canonical System Image:
  New
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  This has regressed a week or two ago. It's not reliably reproducible,
  but bites me almost every time I want to end a call. It might be
  incoming calls only, or maybe only after a minute.

  Steps:
  * go on a call
  * cover the proximity sensor
  * uncover the proximity sensor

  Expected:
  * screen goes off/on as you cover/uncover the sensor

  Current:
  * screen goes off but not back on

  $ system-image-cli -i
  current build number: 90
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-08-08 21:08:55
  version version: 90
  version ubuntu: 20150807.1
  version device: 20150716-fb60d96
  version custom: 20150717-820-30-25-vivid

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

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

[Touch-packages] [Bug 1486889] Re: no message aboutnot an emergency number popup, when call a non-emergency number with no SIM card

thanks, settings as low, it's a bit confusing but trying to call from a
phone without SIM is not the most frequent things users do

** Changed in: dialer-app (Ubuntu)
   Importance: Undecided = Low

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

Title:
  no message aboutnot an emergency number popup,when call a non-
  emergency number  with no SIM card

Status in dialer-app package in Ubuntu:
  New

Bug description:
  system-image-cli -i
  current build number: 95
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-08-20 14:03:45
  version version: 95
  version ubuntu: 20150819
  version device: 20150818-0b38025
  version custom: 20150814-887-8-46

  reproduce steps:
  1.Setup:no SIM card inserted
  2. Lock device 
  3. Swipe away greeter and press Emergency call option 
  4. Enter a non-emergency number 
  5. Tap on the call button
  6.observe the result

  expect result:
  step 5, there will be a message display about not an emergency number
  actual result:
  no not an emergency number message display,while after a few seconds the 
call fail message display.

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

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

[Touch-packages] [Bug 1486492] Re: Keyboard appears during call and does not disappear unless reboot

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

** Also affects: ubuntu-keyboard (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Keyboard appears during call and does not disappear unless reboot

Status in dialer-app package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  OS Ubutnu 15.04(r3) on MX4

  0.1+15.04.20150615-0ubuntu1

  Only occurs if the phone is locked. When answering the call via
  slider, once answered the Keyboard appears, and then does not
  disappear even when calls ended. Calls can also only end by remote end
  hanging up, due to keyboard obscuring the hang up button.

  Unfortunately keyboard is non responsive and phone has to be rebooted
  for any continued use. Sometimes keyboard half appears but effect is
  still the same.

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

-- 
Mailing list: https://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 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

2015-08-21 Thread Gene Soo

Correction to last comments concerning problem resolution.

I inadvertently referred to backing off from Version 5.0.2  to VirtualBox
Release 4.33.
The correct backoff release number is 4.3.30-101610.

On Fri, Aug 21, 2015 at 8:36 AM, Gene Soo genesoo77...@gmail.com
wrote:

 I believe I have discovered the cause of the problem.
 Your prompting me to look at the Open Issues for VirtualBox pointed out
 that I was on V5.0.0 and when I went to the Downloads Page, V5.0.2 was
 currently available.
 VirtualBox will send a push notification when the team indicates and
 important release is available and is displayed when you start VirtualBox.
 Although 5.0.2 is generally available, they did not mark it for Push
 Notification.

 I upgraded to 5.0.2 and also followed through with a process called
 Install Guest Additions, that led to more serious errors.
 The Guest Additions Scripting installs custom support for a variety of
 system dependent things including advanced Video capabilities like Screen
 resizing.
 I had noticed this issue before but was not zoned in on it because it is a
 critical failure for the new KDE Distro and not with the other Desktops.

 I decided to backoff to VBox V4.33 which is the latest release for V4 of
 VirtualBox.

 Spot checking all of the 15.10 Distros having this audio problem, just
 getting into alsamixer and adjusting the Volume Slider, they seem to work
 correctly with VBox V4.33.

 The VirtualBox Team had a V5.0.3 release that hasn't been finalized but is
 available for users to manually install. I have not tried that release to
 see if the Audio issues are resolved.

 I need to turn my attention to reporting both this Audio Issue and the
 Video issue to the respective Virtual Box teams.

 I believe you can mark this issues as Closed.

 Thanks for all of the help in getting this issue sorted out.

 On Fri, Aug 21, 2015 at 7:00 AM, Raymond 1487...@bugs.launchpad.net
 wrote:


 https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/intel8x0.c?id=4235a31784f59c9be5ff71534743c055091f9735

 the real ac97 controller 8086:2415 does not support 6 channels

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1487168

 Title:
   [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
   problem

 Status in alsa-driver package in Ubuntu:
   Incomplete

 Bug description:
   Volume Slider is only controlling PCM channel and is not controlling
   Master. In effect, Master is restricting the audio level to the
   default of approximately 45 Percent. In order to raise the Master
   Volume Level, alsamixer is capable of changing Master. Without
   manually raising Master to Max Volume, Volume Slider can only control
   volume from 0-45% which is the default level of Master.

   Description:  Ubuntu Wily Werewolf (development branch)
   Release:  15.10

   ProblemType: Bug
   DistroRelease: Ubuntu 15.10
   Package: alsa-base 1.0.25+dfsg-0ubuntu5
   ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
   Uname: Linux 4.1.0-3-generic x86_64
   ApportVersion: 2.18-0ubuntu7
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  gene   1330 F pulseaudio
 gene   1922 F alsamixer
   CurrentDesktop: Unity
   Date: Thu Aug 20 13:00:57 2015
   InstallationDate: Installed on 2015-08-19 (1 days ago)
   InstallationMedia: Edubuntu 15.10 Wily Werewolf - Alpha amd64
 (20150819)
   PackageArchitecture: all
   SourcePackage: alsa-driver
   Symptom: audio
   Symptom_Card: Built-in Audio - Intel 82801AA-ICH
   Symptom_Type: Volume slider, or mixer problems
   Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 12/01/2006
   dmi.bios.vendor: innotek GmbH
   dmi.bios.version: VirtualBox
   dmi.board.name: VirtualBox
   dmi.board.vendor: Oracle Corporation
   dmi.board.version: 1.2
   dmi.chassis.type: 1
   dmi.chassis.vendor: Oracle Corporation
   dmi.modalias:
 dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
   dmi.product.name: VirtualBox
   dmi.product.version: 1.2
   dmi.sys.vendor: innotek GmbH

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1487168/+subscriptions




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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Volume Slider is only controlling PCM channel and is not controlling
  Master. In effect, Master is restricting the audio level to the
  default of

[Touch-packages] [Bug 1407928] Re: [phone] Does not auto-switch to available, known WiFi

@Michael

Can you please re-test when OTA6 is released ( or flash the latest rc-
proposed )?

@march

Please re-test when OTA6 is released ( should be out within the next
week or so ).   In general this should work much better when recent
fixes to NM land with OTA6.

That said, there may still be issues with re-connecting to a roaming
style network ( ie. an ESSID configuration where multiple access points
exist with the the same SSID ).

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

Title:
  [phone] Does not auto-switch to available, known WiFi

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  This might not be the place for this bug, please reassign as
  appropriate.

  I was only able to reproduce this on mako/rtm, krillin/vivid seems to
  behave better (but I do remember the same issue there).

  Steps:
  * connect to a password-protected WiFi network
  * go out of range
  * make sure a GSM connection is established
  * go back in the WiFi range

  Expected:
  * phone connects to the known WiFi automatically

  Current:
  * phone does not connect to WiFi

  Please find attached network-test-session logs from when I toggled
  WiFi and Plane mode to get some data on the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Tue Jan  6 12:01:55 2015
  InstallationDate: Installed on 2014-12-18 (18 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141218-163635)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)
  indicator-network.log:
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
  upstart.indicator-network.log:
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered

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

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

[Touch-packages] [Bug 1409906] Re: landscape loses the addressee text box

** Changed in: messaging-app (Ubuntu RTM)
   Status: New = Won't Fix

** Changed in: messaging-app (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  landscape loses the addressee text box

Status in messaging-app package in Ubuntu:
  Fix Released
Status in messaging-app package in Ubuntu RTM:
  Won't Fix

Bug description:
  apologies if this is a specific subset of bug 1379421
  seeing this on ubuntu-rtm/krillin # 191
  also seeing on vivid/mako last week

  1. go to message app
  2. swipe up from bottom to begin writing a message
  3. rotate to landscape

  result - rotation occurs for message body with addressee To: block 
disappearing
  expected, the to: block to remain available for selecting/editing
  rotating back to portrait returns the to: text block

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

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

[Touch-packages] [Bug 1474940] Re: phone call ends after 2 hours

** Package changed: dialer-app (Ubuntu) = telephony-service (Ubuntu)

** Changed in: telephony-service (Ubuntu)
   Importance: Undecided = Low

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

Title:
  phone call ends after 2 hours

Status in telephony-service package in Ubuntu:
  New

Bug description:
  My calls will be finished after exactly 2:00:00 hours.

  Device: nexus 4 mako
  System: All up to date (stable)

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

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

[Touch-packages] [Bug 941826] Re: dlopen(libGL.so) resolves to mesa rather than nvidia

2015-08-21 Thread Peter Würtz

*sigh* late 2015, still not fixed in Ubuntu

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

Title:
  dlopen(libGL.so) resolves to mesa rather than nvidia

Status in NVIDIA Drivers Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in pyqt5 package in Ubuntu:
  Invalid
Status in python-qt4 package in Ubuntu:
  Invalid

Bug description:
  I'm having trouble with a combination of NVIDIA + Python + Qt +
  Opengl.

  I tried using a QGraphicsView on a QGLWidget. I'm getting a white window and 
errors like this these:
  QGLShader: could not create shader
  Vertex shader for simpleShaderProg (MainVertexShader 
PositionOnlyVertexShader) failed to compile

  This is an example application triggering the problem:
  http://pastebin.com/R0aa8ejs

  The 'same' program works flawlessly when using C++/Qt. I'm seeing the exact 
behavior when using PySide instead of PyQt4 by the way. I'm also seeing this 
error when trying the original demo application from python-qt4-doc. Also, 
calling
  QtGui.QApplication.setGraphicsSystem(opengl)
  produces the same errors.

  I'm experiencing this problems on 11.10 and 12.04 with the ubuntu-
  provided nvidia drivers (where 12.04 includes the most recent driver
  for now). After installing the driver using the original NVidia
  installer, the applications work as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/941826/+subscriptions

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

[Touch-packages] [Bug 1480088] Re: Improper message if dial without SIM card inserted

** 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 dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1480088

Title:
  Improper message if dial without SIM card inserted

Status in Canonical System Image:
  New
Status in dialer-app package in Ubuntu:
  New

Bug description:
  Test Environment:

  current build number: 72
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-09-28 04:55:39
  version version: 72
  version ubuntu: 20150729
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  Steps to reproduce:
  1.Get a phone without SIM card
  2.Open dial app
  3.Dial a valid number
  4.Observe the result

  Actual result:
  Improper message displays ¨No network: There is currently no network¨, see 
attached pic.

  Expected result:
  It should be ¨No SIM card¨

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

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

[Touch-packages] [Bug 1388988] Re: [webapp-container] html5 applications should use the container as a launcher

2015-08-21 Thread Alexandre Abreu

** Changed in: qtcreator-plugin-ubuntu (Ubuntu)
   Status: In Progress = Fix Released

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

Title:
  [webapp-container] html5 applications should use the container as a
  launcher

Status in Canonical Click Reviewers tools:
  Fix Released
Status in Ubuntu HTML5 UI SDK:
  Fix Released
Status in webbrowser-app:
  Fix Released
Status in qtcreator-plugin-ubuntu package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  HTML5 apps are currently using a specific container/launcher as their
  runtime. They should use the webapp container instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1388988/+subscriptions

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

[Touch-packages] [Bug 1485222] Re: Using ContentStore disables silently any StateSaver capability

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New = Invalid

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided = High

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

Title:
  Using ContentStore disables silently any StateSaver capability

Status in content-hub package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  1. Create the default template project
  2. Add on the page (with an id):
  TextField {
  id: foo
  StateSaver.properties: text
  }
  3. run the app, type something in the field, xkill it, restart
  - the TextField content is restored by the StateSaver.
  4. import Ubuntu.Content 1.1
  - StateSaver still works
  5. add anywhere on the page:
  ContentStore {
  id: appContentStore
  scope: ContentScope.App
  }
  - The state is not restored anymore (note that it may be the first time, 
restoring when there was no ContentStore at kill time), then it constantly 
fails to restore.

  There is no warning or anything that reported an issue.

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

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

[Touch-packages] [Bug 1478637] Re: X-Ubuntu-Supported-Orientations=landscape causes app to be upside down on devices with nativeOrientation=landscape

** Branch unlinked: lp:~josharenson/unity8/fix_upside_down_apps

** Branch linked: lp:~josharenson/unity8/new_fix_upsidedown

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

Title:
  X-Ubuntu-Supported-Orientations=landscape causes app to be upside down
  on devices with nativeOrientation=landscape

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  As the title says. There is probably a +/- issue with Landscape vs
  InvertedLandscape.

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

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

[Touch-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

2015-08-21 Thread Alberto Salvia Novella

** Changed in: telephony-service (Ubuntu RTM)
   Status: Confirmed = Triaged

** Changed in: telephony-service (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: ofono (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: bluez (Ubuntu)
   Status: Confirmed = Triaged

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

Title:
  Calling from car using bluetooth, call is placed on ril_0, even though
  ril_1 is default

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Triaged
Status in ofono package in Ubuntu:
  Triaged
Status in telephony-service package in Ubuntu:
  Triaged
Status in telephony-service package in Ubuntu RTM:
  Triaged

Bug description:
  What happened
  Placed call from car over bluetooth
  Call was placed on my first SIM card, even though I selected my second SIM as 
default for calls

  What should have happened
  The call should have been placed on my second SIM

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: telephony-service 0.1+15.04.20150124-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: armhf
  Date: Wed Feb  4 14:25:44 2015
  InstallationDate: Installed on 2015-02-02 (2 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150202-020204)
  SourcePackage: telephony-service
  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/1418040/+subscriptions

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

[Touch-packages] [Bug 1467473] Re: Nexus 7 with shellRotation sometimes ends up with broken lockscreen

** Branch linked: lp:~dandrader/unity8/fixOrientedShellTests

** Changed in: unity8 (Ubuntu)
   Status: Confirmed = Fix Committed

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

Title:
  Nexus 7 with shellRotation sometimes ends up with broken lockscreen

Status in unity8 package in Ubuntu:
  Fix Committed

Bug description:
  Since shellRotation the Nexus7 sometimes ends up with a lockscreen
  state where it can't be unlocked because the PinLockScreen is squeezed
  into landscape format. To reproduce open some apps that allow rotating
  and play around with rotating and locking/unlocking.

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

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

[Touch-packages] [Bug 1487589] [NEW] package dbus 1.9.20-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2015-08-21 Thread Yotam Benshalom

Public bug reported:

No more info.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: dbus 1.9.20-1ubuntu2
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.18-0ubuntu7
Architecture: amd64
Date: Thu Aug 13 16:08:47 2015
DuplicateSignature: package:dbus:1.9.20-1ubuntu2:dependency problems - leaving 
triggers unprocessed
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2014-05-26 (452 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu1
 apt  1.0.9.10ubuntu6
SourcePackage: dbus
Title: package dbus 1.9.20-1ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to wily on 2015-08-08 (13 days ago)

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


** Tags: amd64 apport-package wily

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

Title:
  package dbus 1.9.20-1ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in dbus package in Ubuntu:
  New

Bug description:
  No more info.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: dbus 1.9.20-1ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Thu Aug 13 16:08:47 2015
  DuplicateSignature: package:dbus:1.9.20-1ubuntu2:dependency problems - 
leaving triggers unprocessed
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2014-05-26 (452 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu1
   apt  1.0.9.10ubuntu6
  SourcePackage: dbus
  Title: package dbus 1.9.20-1ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to wily on 2015-08-08 (13 days ago)

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

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

[Touch-packages] [Bug 1487111] Re: camera app unresponsive if trusted prompt left for some time

2015-08-21 Thread Florian Boucault

Not being a Pulseaudio expert I am not sure it is relevant but I see the
following define in its code:

 #define DEFAULT_TIMEOUT (30)

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

Title:
  camera app unresponsive if trusted prompt left for some time

Status in camera-app package in Ubuntu:
  New

Bug description:
  image95/arale (also on mako)
  i see this for both the audio trust prompt and the video trust prompt
  steps
  1. launch camera
  2. don't touch trust prompt - set phone down for 5 min
  3. after time, select accept
  (alternately - select accept on camera, hit record and wait for audio prompt, 
step2)

  expected - app continues
  result - app is frozen, shell is still responsive, camera service spinning 
50% cpu

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

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

[Touch-packages] [Bug 1487588] [NEW] Xorg freeze

2015-08-21 Thread eezacque

Public bug reported:

Every month or so, accessing the System Settings-Network panel, or
clicking my network in the wifi menu, freezes Ubuntu. The only way out
is a hard reset

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
Uname: Linux 4.2.0-040200rc6-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.2
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: Fri Aug 21 21:42:49 2015
DistUpgraded: 2015-05-05 01:44:42,463 DEBUG enabling apt cron job
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 3.19.0-26-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.1.0-040100-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.2.0-040200rc6-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Very infrequently
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
InstallationDate: Installed on 2014-10-24 (300 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-040200rc6-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to vivid on 2015-05-04 (108 days ago)
dmi.bios.date: 06/24/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-PRO(Wi-Fi ac)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd06/24/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Fri Aug 21 18:52:54 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4121 
 vendor WAC
xserver.version: 2:1.17.1-0ubuntu3

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


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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Every month or so, accessing the System Settings-Network panel, or
  clicking my network in the wifi menu, freezes Ubuntu. The only way out
  is a hard reset

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  Uname: Linux 4.2.0-040200rc6-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.2
  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: Fri Aug 21 21:42:49 2015
  DistUpgraded: 2015-05-05 01:44:42,463 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.19.0-26-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.1.0-040100-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.2.0-040200rc6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
  InstallationDate:

[Touch-packages] [Bug 1458694] Re: [vivid-overlay] unity8 fails to start on the emulator

2015-08-21 Thread Michael Terry

 Sorry, but why do we need to disable the edge demo?

We disabled the tutorial in desktop mode only.  We had in the past
disabled part of it on the desktop (because certain drag-widgets didn't
work with mice).  But this change drops the whole thing (which was at
this point, just the left-edge drag).  To my knowledge, we're still
waiting on design for visuals for a desktop tutorial.

The real bug is that the emulator is starting in desktop mode.  And
seems to have some issues with using -mousetouch to emulate a touch
device.

But at least disabling the tutorial in desktop mode gets *some* sort of
emulator functionality in the short term.

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

Title:
  [vivid-overlay] unity8 fails to start on the emulator

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Committed

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 140
  device name: generic_x86
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-05-25 12:02:10
  version version: 140
  version ubuntu: 20150525
  version device: 20150210
  version custom: 20150525

  When starting unity8 (this started at image 136, probably when mir
  0.13 landed):

  phablet@ubuntu-phablet:~$ cat ./.cache/upstart/unity8.log
  ()
  [1432595001.896139] mirplatform: Found graphics driver: dummy
  [1432595001.898447] mirplatform: Found graphics driver: android
  qtmir.mir: MirServer created
  [1432595003.675225] Server: Starting
  [1432595003.679331] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/server-platform
  [1432595003.679501] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-dummy.so
  [1432595003.680673] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so
  [1432595003.681107] WARNING Loader: Failed to load module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so (error 
was:/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so: undefined 
symbol: _ZN3mir6events10make_eventExx17MirKeyboardActionjij)
  [1432595003.684868] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-android.so.2
  [1432595003.685014] mirplatform: Found graphics driver: dummy
  [1432595003.685211] mirplatform: Found graphics driver: android
  [1432595003.685416] Platform Loader: Selected driver: android (version 0.13.0)
  qtmir.mir: PromptSessionListener::PromptSessionListener - this= 
PromptSessionListener(0x9679764)
  qtmir.mir: SessionListener::SessionListener - this= SessionListener(0x9676d24)
  qtmir.mir: MirShell::MirShell
  [1432595003.883766] DisplayServer: Mir version 0.13.0
  QtCompositor::setAllWindowsExposed true
  qtmir.clipboard: D-Bus registration successful.
  Mode argument was not provided or was set to an illegal value. Using default 
value of --mode= full-greeter
  Cannot create window: no screens available

  With version 135 it starts fine, but not fully functional, giving this
  error:

  QOpenGLShader::compile(Fragment): 0:2(12): warning: extension 
`GL_OES_standard_derivatives' unsupported in fragment shader
  0:2(1): error: #extension directive is not allowed in the middle of a shader

  *** Problematic Fragment shader source code ***
  #extension GL_OES_standard_derivatives : enable  // Enable dFdy() on OpenGL 
ES 2.
  #define lowp
  #define mediump
  #define highp

  // Copyright Â© 2015 Canonical Ltd.
  //
  // This program is free software; you can redistribute it and/or modify
  // it under the terms of the GNU Lesser General Public License as published by
  // the Free Software Foundation; version 3.
  //
  // This program is distributed in the hope that it will be useful,
  // but WITHOUT ANY WARRANTY; without even the implied warranty of
  // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  // GNU Lesser General Public License for more details.
  //
  // You should have received a copy of the GNU Lesser General Public License
  // along with this program.  If not, see http://www.gnu.org/licenses/.
  //
  // Author: LoÃ¯c Molinari loic.molin...@canonical.com

  // Static flow control (branching on a uniform value) is fast on most GPUs 
(including ultra-low
  // power ones) because it allows to use the same shader execution path for an 
entire draw call. We
  // rely on that technique here (also known as uber-shader solution) to 
avoid the complexity of
  // dealing with a multiple shaders solution.
  // FIXME(loicm) Validate GPU behavior with regards to static flow control.

  uniform sampler2D shapeTexture;
  uniform sampler2D sourceTexture;
  uniform lowp vec2 dfdtFactors;
  uniform lowp vec2 opacityFactors;
  uniform lowp float sourceOpacity;
  uniform lowp float distanceAA;
  uniform bool textured;

[Touch-packages] [Bug 1487589] Re: package dbus 1.9.20-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2015-08-21 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package dbus 1.9.20-1ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in dbus package in Ubuntu:
  New

Bug description:
  No more info.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: dbus 1.9.20-1ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Thu Aug 13 16:08:47 2015
  DuplicateSignature: package:dbus:1.9.20-1ubuntu2:dependency problems - 
leaving triggers unprocessed
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2014-05-26 (452 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu1
   apt  1.0.9.10ubuntu6
  SourcePackage: dbus
  Title: package dbus 1.9.20-1ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to wily on 2015-08-08 (13 days ago)

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

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

[Touch-packages] [Bug 1487159] Re: revoking mic permission in system-settings, camera appears to record but video is unplayable

2015-08-21 Thread Jim Hodapp

** Branch unlinked: lp:~fboucault/qtubuntu-camera/trust_fixes

** Branch linked: lp:~phablet-team/qtubuntu-camera/fix-trust-prompt-bugs

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

Title:
  revoking mic permission in system-settings, camera appears to record
  but video is unplayable

Status in Canonical System Image:
  New
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  with silo 16 on arale

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

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

[Touch-packages] [Bug 1487126] Re: Camera/mic trust: initial video corrupt

2015-08-21 Thread Jim Hodapp

** Branch unlinked: lp:~fboucault/qtubuntu-camera/trust_fixes

** Branch linked: lp:~phablet-team/qtubuntu-camera/fix-trust-prompt-bugs

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

Title:
  Camera/mic trust: initial video corrupt

Status in Canonical System Image:
  Confirmed
Status in QtMir:
  Incomplete
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  After granting camera and mic permission, able to record a video but
  the video is unplayable in media-player, media-player has to be
  killed.

  TEST CASE
  1. Open camera, camera trust prompt appears
  2. Grant camera permission
  3. Switch to video
  4. Press record button, mic trust prompt appears
  5. Grant mic permission
  6. Record video, press stop
  7. Swipe to photo roll, see video (preview being generated)
  8. Press play to watch video
  9. Media player opens
  EXPECTED
  Video plays
  ACTUAL
  Black screen

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

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

[Touch-packages] [Bug 1324602] Re: [split] unity8-greeter doesn't run on desktop configurations

Also have a ppa that will allow easily testing this on desktop, but its
not working quite right yet.

** Branch linked: lp:~josharenson/unity8/slim_greeter_real_lightdm

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

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

Title:
  [split] unity8-greeter doesn't run on desktop configurations

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Installing unity8-greeter, from the split greeter silo, on an
  unity8-mir desktop configuration leads to a non working lightdm

  * installing unity8-greeter leads to an empty screen with a cursor
  (looking like a Mir one), which runs for some seconds and do what
  looks like a respawn

  - editing the unity8-greeter-wrapper to set the qpa to mirclient
  corrected the respawn issue but giving an empty screen still

  * install ubuntu-touch-session gives a working greeter but unlocking
  doesn't start the session

  * GreeterShell.qml has an issue and does unlock only in when autologin
  is enabled, editing that makes unlock dismiss the greeter

  but the session still doesn't start, unlocking the greeter gives a
  screen looking like the phone one ... that needs extra debugging

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

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

[Touch-packages] [Bug 1487111] Re: camera app unresponsive if trusted prompt left for some time

2015-08-21 Thread kevin gunn

is there a power reason for making a choice for the user ?

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

Title:
  camera app unresponsive if trusted prompt left for some time

Status in camera-app package in Ubuntu:
  New

Bug description:
  image95/arale (also on mako)
  i see this for both the audio trust prompt and the video trust prompt
  steps
  1. launch camera
  2. don't touch trust prompt - set phone down for 5 min
  3. after time, select accept
  (alternately - select accept on camera, hit record and wait for audio prompt, 
step2)

  expected - app continues
  result - app is frozen, shell is still responsive, camera service spinning 
50% cpu

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

-- 
Mailing list: https://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 1458694] Re: [vivid-overlay] unity8 fails to start on the emulator

2015-08-21 Thread Ricardo Salveti

On Fri, Aug 21, 2015 at 6:52 AM, Timo Jyrinki
timo.jyri...@canonical.com wrote:
 As per QA report:
 Needs a fix in unity8 so we can get past edges demo and confirm there are no 
 further issues with the silo before landing.

Sorry, but why do we need to disable the edge demo? It's still useful
during the first boot. If needed we could extend the flashing tool to
offer an option for that.

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

Title:
  [vivid-overlay] unity8 fails to start on the emulator

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Committed

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 140
  device name: generic_x86
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-05-25 12:02:10
  version version: 140
  version ubuntu: 20150525
  version device: 20150210
  version custom: 20150525

  When starting unity8 (this started at image 136, probably when mir
  0.13 landed):

  phablet@ubuntu-phablet:~$ cat ./.cache/upstart/unity8.log
  ()
  [1432595001.896139] mirplatform: Found graphics driver: dummy
  [1432595001.898447] mirplatform: Found graphics driver: android
  qtmir.mir: MirServer created
  [1432595003.675225] Server: Starting
  [1432595003.679331] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/server-platform
  [1432595003.679501] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-dummy.so
  [1432595003.680673] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so
  [1432595003.681107] WARNING Loader: Failed to load module: 
/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so (error 
was:/usr/lib/i386-linux-gnu/mir/server-platform/input-stub.so: undefined 
symbol: _ZN3mir6events10make_eventExx17MirKeyboardActionjij)
  [1432595003.684868] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/server-platform/graphics-android.so.2
  [1432595003.685014] mirplatform: Found graphics driver: dummy
  [1432595003.685211] mirplatform: Found graphics driver: android
  [1432595003.685416] Platform Loader: Selected driver: android (version 0.13.0)
  qtmir.mir: PromptSessionListener::PromptSessionListener - this= 
PromptSessionListener(0x9679764)
  qtmir.mir: SessionListener::SessionListener - this= SessionListener(0x9676d24)
  qtmir.mir: MirShell::MirShell
  [1432595003.883766] DisplayServer: Mir version 0.13.0
  QtCompositor::setAllWindowsExposed true
  qtmir.clipboard: D-Bus registration successful.
  Mode argument was not provided or was set to an illegal value. Using default 
value of --mode= full-greeter
  Cannot create window: no screens available

  With version 135 it starts fine, but not fully functional, giving this
  error:

  QOpenGLShader::compile(Fragment): 0:2(12): warning: extension 
`GL_OES_standard_derivatives' unsupported in fragment shader
  0:2(1): error: #extension directive is not allowed in the middle of a shader

  *** Problematic Fragment shader source code ***
  #extension GL_OES_standard_derivatives : enable  // Enable dFdy() on OpenGL 
ES 2.
  #define lowp
  #define mediump
  #define highp

  // Copyright Â© 2015 Canonical Ltd.
  //
  // This program is free software; you can redistribute it and/or modify
  // it under the terms of the GNU Lesser General Public License as published by
  // the Free Software Foundation; version 3.
  //
  // This program is distributed in the hope that it will be useful,
  // but WITHOUT ANY WARRANTY; without even the implied warranty of
  // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  // GNU Lesser General Public License for more details.
  //
  // You should have received a copy of the GNU Lesser General Public License
  // along with this program.  If not, see http://www.gnu.org/licenses/.
  //
  // Author: LoÃ¯c Molinari loic.molin...@canonical.com

  // Static flow control (branching on a uniform value) is fast on most GPUs 
(including ultra-low
  // power ones) because it allows to use the same shader execution path for an 
entire draw call. We
  // rely on that technique here (also known as uber-shader solution) to 
avoid the complexity of
  // dealing with a multiple shaders solution.
  // FIXME(loicm) Validate GPU behavior with regards to static flow control.

  uniform sampler2D shapeTexture;
  uniform sampler2D sourceTexture;
  uniform lowp vec2 dfdtFactors;
  uniform lowp vec2 opacityFactors;
  uniform lowp float sourceOpacity;
  uniform lowp float distanceAA;
  uniform bool textured;
  uniform mediump int aspect;

  varying mediump vec2 shapeCoord;
  varying mediump vec4 sourceCoord;
  varying lowp vec4 backgroundColor;

  const mediump int FLAT  = 0x08;  // 1  3
  const mediump int INSET = 0x10;  // 1  4

  void main(void)
  {
  lowp

[Touch-packages] [Bug 1487111] Re: camera app unresponsive if trusted prompt left for some time

2015-08-21 Thread Bill Filler

Note, we've added a workaround in qtubuntu-camera (in silo 40) to make
this problem better (no hang) but does not fix it completely.

The following will occur:

1) try to record a video
2) don't press the trust prompt
3) let your phone go to sleep
4) wake it up and open camera
5) press on trust prompt (either decision)
6) now you'll have to press record button again as we detected the timeout and 
did not record the video
7) the videos after this will have no audio until you reboot regardless of 
prompt choice or settings change, as pulse is in a messed up state

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

Title:
  camera app unresponsive if trusted prompt left for some time

Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  image95/arale (also on mako)
  i see this for both the audio trust prompt and the video trust prompt
  steps
  1. launch camera
  2. don't touch trust prompt - set phone down for 5 min
  3. after time, select accept
  (alternately - select accept on camera, hit record and wait for audio prompt, 
step2)

  expected - app continues
  result - app is frozen, shell is still responsive, camera service spinning 
50% cpu

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

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

[Touch-packages] [Bug 1360307] Re: Logging in to the desktop session brings up the lock screen

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

** This bug has been marked a duplicate of bug 1324602
   [split] unity8-greeter doesn't run on desktop configurations

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

Title:
  Logging in to the desktop session brings up the lock screen

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  When logging in to the desktop session from LightDM, the lock screen
  is then brought up and requires typing the password again to unlock.
  The desired behavior should be to just go to the Dash as having to
  type another password is redundant.

  This occurs with version 8.00+14.10.20140822-0ubuntu1.

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

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

[Touch-packages] [Bug 1483558] Re: Content-Hub crash with an invalid app-id after transfer and doesn't clean up temp files

2015-08-21 Thread Ken VanDine

Is it the content-hub-service that crashes?  Or the app?  If the service
doesn't crash, the cached file should still get cleaned up with the
service exits.

The problem with APP_ID=fake is we need the APP_ID to be parse-able by
libubuntu-app-launch, plus it needs to be unique.  I wish setting
applicationName in the MainView would be enough to set the runtime
APP_ID, but it isn't.

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

Title:
  Content-Hub crash with an invalid app-id after transfer and doesn't
  clean up temp files

Status in content-hub package in Ubuntu:
  New

Bug description:
  The idea would to have at least a fake APP_ID for developping and
  testing/iterating on desktop. The import functionality itself works,
  but the crash doesn't give a good developer experience.

  Maybe we can decide on having an APP_ID=fake in the developer default
  template, and then, content-hub let that ID pass even if not
  installed?

  Note that one of the side effect of this crash after transfer is that
  the tmeporary files under HubIncoming aren't cleaned up.

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

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

[Touch-packages] [Bug 1487111] Re: camera app unresponsive if trusted prompt left for some time

2015-08-21 Thread Bill Filler

The desired behavior should be

1) pulse should not timeout after 30 seconds

or
2) if we keep the 30 second timeout, the trust-prompt should be removed after 
that period with the DENY choice selected

Currently, the trust-prompt stays on the screen even though silently
access has been denied.

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

Title:
  camera app unresponsive if trusted prompt left for some time

Status in camera-app package in Ubuntu:
  New

Bug description:
  image95/arale (also on mako)
  i see this for both the audio trust prompt and the video trust prompt
  steps
  1. launch camera
  2. don't touch trust prompt - set phone down for 5 min
  3. after time, select accept
  (alternately - select accept on camera, hit record and wait for audio prompt, 
step2)

  expected - app continues
  result - app is frozen, shell is still responsive, camera service spinning 
50% cpu

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

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

[Touch-packages] [Bug 1487131] Re: Camera/mic trust: mic denial in camera-app freezes camera

2015-08-21 Thread Jim Hodapp

** Branch unlinked: lp:~fboucault/qtubuntu-camera/trust_fixes

** Branch linked: lp:~phablet-team/qtubuntu-camera/fix-trust-prompt-bugs

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

Title:
  Camera/mic trust: mic denial in camera-app freezes camera

Status in camera-app:
  In Progress
Status in Canonical System Image:
  New
Status in QtMir:
  Invalid
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  Similar, related to lp:1487126 , recording separately for the sake of
  thoroughness :) :

  TEST CASE
  1. Open camera, camera trust prompt appears
  2. Grant camera permission
  3. Switch to video
  4. Press record button, mic trust prompt appears from qtubuntu-camera
  5. *Deny* mic permission
  EXPECTED
  Returned to live preview
  ACTUAL
  Preview freezes

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1487131/+subscriptions

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

[Touch-packages] [Bug 1482608] Re: ssh-add fails to add ed25519 keys