[Touch-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

2017-02-09 Thread Nicholas Skaggs
I can confirm this works on xenial after installing squashfuse.

root@clean-lark:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:   xenial
root@clean-lark:~# uname -a
Linux clean-lark 4.4.0-63-generic #84-Ubuntu SMP Wed Feb 1 17:20:32 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
root@clean-lark:~# dpkg -l | grep -i 'apparmor\|snap\|squash'
ii  apparmor 2.10.95-0ubuntu2.5 amd64   
 user-space parser utility for AppArmor
ii  libapparmor-perl 2.10.95-0ubuntu2.5 amd64   
 AppArmor library Perl bindings
ii  libapparmor1:amd64   2.10.95-0ubuntu2.5 amd64   
 changehat AppArmor library
ii  snap-confine 2.21   amd64   
 Support executable to apply confinement for snappy apps
ii  snapd2.21   amd64   
 Tool to interact with Ubuntu Core Snappy.
ii  squashfs-tools   1:4.3-3ubuntu2 amd64   
 Tool to create and append to squashfs filesystems
ii  ubuntu-core-launcher 2.21   amd64   
 Launcher for ubuntu-core (snappy) apps
root@clean-lark:~# snap list
Name Version  Rev  Developer  Notes
core 16.04.1  888  canonical  -
hello-world  6.3  27   canonical  -

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in lxd source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

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

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

[Touch-packages] [Bug 1552773] Re: _optionselector.py looks for Label delegates instead of UCLabel

2016-03-03 Thread Nicholas Skaggs
To confirm the fix, checkout rev 763 of lp:ubuntu-calendar-app, and run
the
calendar_app.tests.test_new_event.NewEventTestCase.test_new_event_must_start_with_default_values.
It's a short test, and should fail without the change, and work with it.

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

Title:
  _optionselector.py looks for Label delegates instead of UCLabel

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

Bug description:
  The autopilot helper for optionselector seeks Label delegates, rather than 
UCLabel delegates.
 
  --
 def get_selected_text(self):
  """gets the text of the currently selected item"""
  option_selector_delegate = self.select_single(
  'OptionSelectorDelegate', focus='True')
  current_label = option_selector_delegate.select_single(
  'Label', visible='True')
  return current_label.text

  def get_current_label(self):
  """gets the text of the currently selected item"""
  option_selector_delegate = self.select_single(
  'OptionSelectorDelegate', focus='True')
  current_label = option_selector_delegate.select_single(
  'Label', visible='True')
  return current_label
  --

  Those select_single calls should use UCLabel.

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

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


[Touch-packages] [Bug 1552773] [NEW] _optionselector.py looks for Label delegates instead of UCLabel

2016-03-03 Thread Nicholas Skaggs
Public bug reported:

The autopilot helper for optionselector seeks Label delegates, rather than 
UCLabel delegates.
   
--
   def get_selected_text(self):
"""gets the text of the currently selected item"""
option_selector_delegate = self.select_single(
'OptionSelectorDelegate', focus='True')
current_label = option_selector_delegate.select_single(
'Label', visible='True')
return current_label.text

def get_current_label(self):
"""gets the text of the currently selected item"""
option_selector_delegate = self.select_single(
'OptionSelectorDelegate', focus='True')
current_label = option_selector_delegate.select_single(
'Label', visible='True')
return current_label
--

Those select_single calls should use UCLabel.

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


** Tags: autopilot-helper

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

Title:
  _optionselector.py looks for Label delegates instead of UCLabel

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

Bug description:
  The autopilot helper for optionselector seeks Label delegates, rather than 
UCLabel delegates.
 
  --
 def get_selected_text(self):
  """gets the text of the currently selected item"""
  option_selector_delegate = self.select_single(
  'OptionSelectorDelegate', focus='True')
  current_label = option_selector_delegate.select_single(
  'Label', visible='True')
  return current_label.text

  def get_current_label(self):
  """gets the text of the currently selected item"""
  option_selector_delegate = self.select_single(
  'OptionSelectorDelegate', focus='True')
  current_label = option_selector_delegate.select_single(
  'Label', visible='True')
  return current_label
  --

  Those select_single calls should use UCLabel.

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

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


[Touch-packages] [Bug 1534807] Re: Cannot run "sudo chroot ." in Terminal

2016-02-25 Thread Nicholas Skaggs
Jamie, I thought we had dropped all the fakeenv rules for autopilot?
Indeed we did switch to the notion of having dedicated devices that we
manually curate into known states before testing.

So all rules that support faking envs or mocking for autopilot can be
removed.

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

Title:
  Cannot run "sudo chroot ." in Terminal

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  The Terminal app is being denied to exec the shell inside a chroot
  when attempting to run sudo chroot .:

  Jan 15 15:09:22 ubuntu-phablet kernel: [66337.301777] type=1400
  audit(1452888562.238:76): apparmor="DENIED" operation="exec"
  profile="com.ubuntu.terminal_terminal_0.7.140" name="/home/phablet
  /vivid-chroot/bin/bash" pid=30547 comm="chroot" requested_mask="x"
  denied_mask="x" fsuid=0 ouid=0

  It would be nice to fix this so that sudo chroot . will work, so that
  people can use a chroot to install additional console apps and tools,
  rather than using writable images, following the instructions on
  AskUbuntu at http://bit.ly/1RLv3g9

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

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


[Touch-packages] [Bug 1536361] Re: When using the sdk helper for the keyboard to type in autopilot, it reports "Keyboard is not on screen"

2016-02-09 Thread Nicholas Skaggs
See also: https://bugs.launchpad.net/ubuntu/+source/ubuntu-
keyboard/+bug/1542224

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

Title:
  When using the sdk helper for the keyboard to type in autopilot, it
  reports "Keyboard is not on screen"

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

Bug description:
  When using the sdk helper for the keyboard to type in autopilot, it
  reports "Keyboard is not on screen".

  I have seen this both with the music-app and weather-app, and on
  jenkins it was failing around 3/4 attempts but not failing on a mako.
  It feels like there isn't a wait in the correct place.

  An example traceback [0], in some cases you can see in the screenshot
  that the keyboard is not on the screen, however I have seen one cast
  where the keyboard was shown in the screenshot [1] (look at the
  subunit output for test_create_playlist_from_songs_tab).

  0 - http://pastebin.ubuntu.com/14585218/
  1 - https://core-apps-jenkins.ubuntu.com/job/run-ap-tests-ci/131/

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

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


[Touch-packages] [Bug 1524000] Re: PyGIWarning: UbuntuAppLaunch was imported without specifying a version first

2015-12-08 Thread Nicholas Skaggs
** Branch linked: lp:~canonical-platform-
qa/autopilot/fix_vuild_for_x_incl_datetime

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

** Changed in: autopilot
   Status: New => In Progress

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

Title:
  PyGIWarning: UbuntuAppLaunch was imported without specifying a version
  first

Status in Autopilot:
  In Progress
Status in Ubuntu Music App:
  Invalid
Status in pygobject package in Ubuntu:
  New

Bug description:
  When launching Autopilot tests for Music App you get an error indicating that 
UbuntuAppLaunch was imported without specifying a version first.
  This is the error:

  autopilot run music_app
  /usr/lib/python2.7/dist-packages/autopilot/application/_launcher.py:23: 
PyGIWarning: UbuntuAppLaunch was imported without specifying a version first. 
Use gi.require_version('UbuntuAppLaunch', '2') before import to ensure that the 
right version gets loaded.
from gi.repository import GLib, UbuntuAppLaunch
  Loading tests from: /home/victor/Development/music-app/tests/autopilot

  Failed to import test module: music_app.tests.test_music
  Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
  module = self._get_module_from_name(name)
File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
  __import__(name)
File 
"/home/victor/Development/music-app/tests/autopilot/music_app/__init__.py", 
line 9, in 
  from ubuntuuitoolkit import (
  ImportError: No module named ubuntuuitoolkit

  Tests running...
  ==
  ERROR: unittest.loader.ModuleImportFailure.music_app.tests.test_music
  --
  Traceback (most recent call last):
  ImportError: Failed to import test module: music_app.tests.test_music
  Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
  module = self._get_module_from_name(name)
File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
  __import__(name)
File 
"/home/victor/Development/music-app/tests/autopilot/music_app/__init__.py", 
line 9, in 
  from ubuntuuitoolkit import (
  ImportError: No module named ubuntuuitoolkit

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

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


[Touch-packages] [Bug 1435324] Re: qtbase5-dev not installable on Ubuntu 14.04 LTS

2015-09-11 Thread Nicholas Skaggs
For those who might come across this issue, I was able to workaround it
and install things by manually specifying all the needed dependencies.

sudo apt-get install libgles2-mesa-dev libegl1-mesa-dev libwayland-dev
qtbase5-dev

Should this occur in the future, you  likely can build a similar string
of depends that apt isn't picking up on and install them together.

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

Title:
  qtbase5-dev not installable on Ubuntu 14.04 LTS

Status in apt package in Ubuntu:
  Confirmed
Status in mesa-lts-vivid package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  I discovered the problem when I tried to compile a Qt5 QML program firstly.
  I have an Ubuntu 14.04.2 LTS with all updates, no significant PPAs (only 
nodejs and owncloud, not affecting this problem here) and with all the 
-lts-utopic upgrade packages installed.

  With that system, I tried to install qtbase5-dev, and apt told me:

  [...]
  The following packages have unmet dependencies:
   qtbase5-dev : Depends: libgles2-mesa-dev or
  libgles2-dev but it is not installable
   unity-control-center : Depends: libcheese-gtk23 (>= 3.4.0) but it is not 
going to be installed
  Depends: libcheese7 (>= 3.0.1) but it is not going to 
be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  So this package seems to be not installable. This tried in synaptic,
  it tries to uninstall all -lts-utopic packages (inclusive all
  xserver*.deb) and install the "old" ones instead of them.

  So the problem somewhere lies within the new lts packages that seem
  not to be compatible with qtbase5-dev (and its dependency: libgles2
  -mesa-dev - but I am not able to find out further.

  The problem is: Qt5 development on an Ubuntu 14.04.2 LTS machine is
  NOT possible without a fix. The make process always complains about
  not finding gl libraries.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: qtbase5-dev (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 23 14:01:20 2015
  InstallationDate: Installed on 2015-02-25 (26 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1464341] Re: Denial when running binaries in terminal app

2015-06-12 Thread Nicholas Skaggs
** Branch linked: lp:~nskaggs/dbus-property-service/remove-fakeenv

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

Title:
  Denial when running binaries in terminal app

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Triaged
Status in dbus-property-service package in Ubuntu:
  Triaged

Bug description:
  Open terminal on device
  Make a typical bash shell script in your home directory
  Try and run it
  Get this:-

  bash: foo.sh: Permission denied.

  Apparmor denial in dmesg:-

  
  [26531.600286] type=1400 audit(1434040394.724:247): apparmor=DENIED 
operation=exec profile=com.ubuntu.terminal_terminal_0.7.74 
name=/home/phablet/bin/in.sh pid=11131 comm=bash requested_mask=x 
denied_mask=x fsuid=32011 ouid=32011

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

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


[Touch-packages] [Bug 1464341] Re: Denial when running binaries in terminal app

2015-06-12 Thread Nicholas Skaggs
None of the coreapps are using this; tests work fine without it. We
should be safe to remove.

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

Title:
  Denial when running binaries in terminal app

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Triaged
Status in dbus-property-service package in Ubuntu:
  Triaged

Bug description:
  Open terminal on device
  Make a typical bash shell script in your home directory
  Try and run it
  Get this:-

  bash: foo.sh: Permission denied.

  Apparmor denial in dmesg:-

  
  [26531.600286] type=1400 audit(1434040394.724:247): apparmor=DENIED 
operation=exec profile=com.ubuntu.terminal_terminal_0.7.74 
name=/home/phablet/bin/in.sh pid=11131 comm=bash requested_mask=x 
denied_mask=x fsuid=32011 ouid=32011

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

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


[Touch-packages] [Bug 1464341] Re: Denial when running binaries in terminal app

2015-06-11 Thread Nicholas Skaggs
The apparmor click rules have moved from under autopilot-touch to dbus-
property-service. I believe the old fakenv rules can be removed
completely. I'll test this to be sure.

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

Title:
  Denial when running binaries in terminal app

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Triaged
Status in dbus-property-service package in Ubuntu:
  Triaged

Bug description:
  Open terminal on device
  Make a typical bash shell script in your home directory
  Try and run it
  Get this:-

  bash: foo.sh: Permission denied.

  Apparmor denial in dmesg:-

  
  [26531.600286] type=1400 audit(1434040394.724:247): apparmor=DENIED 
operation=exec profile=com.ubuntu.terminal_terminal_0.7.74 
name=/home/phablet/bin/in.sh pid=11131 comm=bash requested_mask=x 
denied_mask=x fsuid=32011 ouid=32011

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

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


[Touch-packages] [Bug 1433370] Re: Autopilot helpers documentation is blank

2015-05-18 Thread Nicholas Skaggs
** Changed in: developer-ubuntu-com
   Status: Fix Committed = 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/1433370

Title:
  Autopilot helpers documentation is blank

Status in Ubuntu App Developer site:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  The ubuntu-ui-toolkit-autopilot package now generates json and html
  documentation as part of package creation. However, the resulting
  files are missing the actual API methods they intend to document.

To manage notifications about this bug go to:
https://bugs.launchpad.net/developer-ubuntu-com/+bug/1433370/+subscriptions

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


[Touch-packages] [Bug 1433370] Re: Autopilot helpers documentation is blank

2015-04-09 Thread Nicholas Skaggs
It seems a further update has corrected this issue.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New = Invalid

** Changed in: developer-ubuntu-com
   Status: Triaged = 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/1433370

Title:
  Autopilot helpers documentation is blank

Status in Ubuntu App Developer site:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  The ubuntu-ui-toolkit-autopilot package now generates json and html
  documentation as part of package creation. However, the resulting
  files are missing the actual API methods they intend to document.

To manage notifications about this bug go to:
https://bugs.launchpad.net/developer-ubuntu-com/+bug/1433370/+subscriptions

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


[Touch-packages] [Bug 1433370] Re: Autopilot helpers documentation is blank

2015-04-09 Thread Nicholas Skaggs
** Also affects: developer-ubuntu-com
   Importance: Undecided
   Status: New

** Changed in: developer-ubuntu-com
   Status: New = Triaged

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

Title:
  Autopilot helpers documentation is blank

Status in Ubuntu App Developer site:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  The ubuntu-ui-toolkit-autopilot package now generates json and html
  documentation as part of package creation. However, the resulting
  files are missing the actual API methods they intend to document.

To manage notifications about this bug go to:
https://bugs.launchpad.net/developer-ubuntu-com/+bug/1433370/+subscriptions

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


[Touch-packages] [Bug 1437047] Re: Scopes API Import missing some testing docs

2015-04-09 Thread Nicholas Skaggs
** Changed in: developer-ubuntu-com
   Status: Incomplete = Confirmed

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

Title:
  Scopes API Import missing some testing docs

Status in Ubuntu App Developer site:
  Confirmed
Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  I don't see

  unity::scopes::testing::TypedScopeFixture
  unity::scopes::testing::MockSearchReply
  unity::scopes::testing::MockPreviewReply

  under
  https://developer.ubuntu.com/api/scopes/sdk-14.10/unity.scopes.testing/

  This was available before:

  https://developer.ubuntu.com/api/devel/ubuntu-14.10/cplusplus/unity-
  scopes/dir_4a2a62c60bd6f2d5db6599a21d12fb4a.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/developer-ubuntu-com/+bug/1437047/+subscriptions

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


[Touch-packages] [Bug 1409778] Re: autopilot and autopilot sdk helper documentation needs API website integration

2015-03-17 Thread Nicholas Skaggs
** Changed in: autopilot (Ubuntu)
   Status: New = Fix Released

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

Title:
  autopilot and autopilot sdk helper documentation needs API website
  integration

Status in Autopilot:
  Fix Released
Status in Ubuntu API Website:
  In Progress
Status in autopilot package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  autopilot and autopilot sdk helper documentation currently lives as
  static html pages on the site here:

  https://developer.ubuntu.com/api/devel/ubuntu-14.10/python/

  As such, the docs are hard to find, hard to update and aren't included
  when searching, etc. They should be integrated into the site in the
  same way as other API docs.

  The API docs website can import json, so the sphinx builds for AP docs
  should be updated to include a json output.

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

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


[Touch-packages] [Bug 1433370] [NEW] Autopilot helpers documentation is blank

2015-03-17 Thread Nicholas Skaggs
Public bug reported:

The ubuntu-ui-toolkit-autopilot package now generates json and html
documentation as part of package creation. However, the resulting files
are missing the actual API methods they intend to document.

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


** Tags: autopilot-helper

** Tags added: autopilot-helper

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

Title:
  Autopilot helpers documentation is blank

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

Bug description:
  The ubuntu-ui-toolkit-autopilot package now generates json and html
  documentation as part of package creation. However, the resulting
  files are missing the actual API methods they intend to document.

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

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


[Touch-packages] [Bug 1423342] Re: SDCard fake needed for filemanager autopilot tests

2015-02-19 Thread Nicholas Skaggs
It's unclear to me where this helper should lie; presumably it's above
both autopilot and the toolkit, but ?

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

** Tags added: autopilot-helper

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

Title:
  SDCard fake needed for filemanager autopilot tests

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

Bug description:
  Faking SDCard is needed for writing autopilot tests for filemanager
  app: https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1406988.

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

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


[Touch-packages] [Bug 1417718] [NEW] Autopilot helper documentation is hidden inside chroot

2015-02-03 Thread Nicholas Skaggs
Public bug reported:

Currently the autopilot helper documentation is shipped in the ubuntu-
ui-toolkit-autopilot package. This means the local documentation for
developers exists in a chroot behind the SDK tools. This can cause
confusion and potential issue as the local installed version (if any)
does correspond / make sense for what is being used inside the chroot.

Support should be added for viewing documentation for the chroot target
you are developing against.

** Affects: qtcreator-plugin-ubuntu (Ubuntu)
 Importance: High
 Assignee: Zoltan Balogh (bzoltan)
 Status: 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/1417718

Title:
  Autopilot helper documentation is hidden inside chroot

Status in qtcreator-plugin-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  Currently the autopilot helper documentation is shipped in the ubuntu-
  ui-toolkit-autopilot package. This means the local documentation for
  developers exists in a chroot behind the SDK tools. This can cause
  confusion and potential issue as the local installed version (if any)
  does correspond / make sense for what is being used inside the chroot.

  Support should be added for viewing documentation for the chroot
  target you are developing against.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu/+bug/1417718/+subscriptions

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


[Touch-packages] [Bug 1409778] Re: autopilot and autopilot sdk helper documentation needs API website integration

2015-01-28 Thread Nicholas Skaggs
** Changed in: autopilot
   Status: New = In Progress

** Changed in: ubuntu-api-website
   Status: New = In Progress

** Changed in: autopilot
 Assignee: (unassigned) = Nicholas Skaggs (nskaggs)

** Branch linked: lp:~nskaggs/autopilot/add-json-build

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

Title:
  autopilot and autopilot sdk helper documentation needs API website
  integration

Status in Autopilot:
  In Progress
Status in Ubuntu API Website:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  autopilot and autopilot sdk helper documentation currently lives as
  static html pages on the site here:

  https://developer.ubuntu.com/api/devel/ubuntu-14.10/python/

  As such, the docs are hard to find, hard to update and aren't included
  when searching, etc. They should be integrated into the site in the
  same way as other API docs.

  The API docs website can import json, so the sphinx builds for AP docs
  should be updated to include a json output.

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

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


[Touch-packages] [Bug 1410477] Re: ubuntu-ui-toolkit-autopilot documentation is not buildable

2015-01-14 Thread Nicholas Skaggs
** Branch linked: lp:~nskaggs/ubuntu-ui-toolkit/aphelperdocs-staging

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

Title:
  ubuntu-ui-toolkit-autopilot documentation is not buildable

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

Bug description:
  The current ubuntu-ui-toolkit-autopilot documentation for the SDK
  autopilot helpers is written using sphinx. However, it is not built
  during package creation and is thus unavailable. This was due to main
  archive policy (packages in main must not require a package outside of
  main for compilation or execution (thus, the package must not declare
  a Depends, Recommends, or Build-Depends relationship on a non-
  main package))).  Since sphinx is outside of the main archive,
  packages inside main cannot depend on it.

  The documentation needs to be moved to a separate package outside of
  main, or chose a documentation builder that can be included as part of
  the build without violating policy.

  See https://code.launchpad.net/~didrocks/ubuntu-ui-toolkit/unblock-
  proposed/+merge/211267 for information on the removal.

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

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


[Touch-packages] [Bug 1409778] Re: autopilot and autopilot sdk helper documentation needs API website integration

2015-01-14 Thread Nicholas Skaggs
** Branch linked: lp:~nskaggs/ubuntu-ui-toolkit/aphelperdocs-staging

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

** Description changed:

  autopilot and autopilot sdk helper documentation currently lives as
  static html pages on the site here:
  
  https://developer.ubuntu.com/api/devel/ubuntu-14.10/python/
  
  As such, the docs are hard to find, hard to update and aren't included
  when searching, etc. They should be integrated into the site in the same
  way as other API docs.
+ 
+ The API docs website can import json, so the sphinx builds for AP docs
+ should be updated to include a json output.

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

Title:
  autopilot and autopilot sdk helper documentation needs API website
  integration

Status in Autopilot:
  New
Status in Ubuntu API Website:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  autopilot and autopilot sdk helper documentation currently lives as
  static html pages on the site here:

  https://developer.ubuntu.com/api/devel/ubuntu-14.10/python/

  As such, the docs are hard to find, hard to update and aren't included
  when searching, etc. They should be integrated into the site in the
  same way as other API docs.

  The API docs website can import json, so the sphinx builds for AP docs
  should be updated to include a json output.

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

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


[Touch-packages] [Bug 1410477] [NEW] ubuntu-ui-toolkit-autopilot documentation is not buildable

2015-01-13 Thread Nicholas Skaggs
Public bug reported:

The current ubuntu-ui-toolkit-autopilot documentation for the SDK
autopilot helpers is written using sphinx. However, it is not built
during package creation and is thus unavailable. This was due to main
archive policy (packages in main must not require a package outside of
main for compilation or execution (thus, the package must not declare a
Depends, Recommends, or Build-Depends relationship on a non-main
package))).  Since sphinx is outside of the main archive, packages
inside main cannot depend on it.

The documentation needs to be moved to a separate package outside of
main, or chose a documentation builder that can be included as part of
the build without violating policy.

See https://code.launchpad.net/~didrocks/ubuntu-ui-toolkit/unblock-
proposed/+merge/211267 for information on the removal.

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

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

** No longer affects: autopilot (Ubuntu)

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

Title:
  ubuntu-ui-toolkit-autopilot documentation is not buildable

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

Bug description:
  The current ubuntu-ui-toolkit-autopilot documentation for the SDK
  autopilot helpers is written using sphinx. However, it is not built
  during package creation and is thus unavailable. This was due to main
  archive policy (packages in main must not require a package outside of
  main for compilation or execution (thus, the package must not declare
  a Depends, Recommends, or Build-Depends relationship on a non-
  main package))).  Since sphinx is outside of the main archive,
  packages inside main cannot depend on it.

  The documentation needs to be moved to a separate package outside of
  main, or chose a documentation builder that can be included as part of
  the build without violating policy.

  See https://code.launchpad.net/~didrocks/ubuntu-ui-toolkit/unblock-
  proposed/+merge/211267 for information on the removal.

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

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


[Touch-packages] [Bug 1410477] Re: ubuntu-ui-toolkit-autopilot documentation is not buildable

2015-01-13 Thread Nicholas Skaggs
** Branch linked: lp:~nskaggs/ubuntu-ui-toolkit/aphelperdocs

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

Title:
  ubuntu-ui-toolkit-autopilot documentation is not buildable

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

Bug description:
  The current ubuntu-ui-toolkit-autopilot documentation for the SDK
  autopilot helpers is written using sphinx. However, it is not built
  during package creation and is thus unavailable. This was due to main
  archive policy (packages in main must not require a package outside of
  main for compilation or execution (thus, the package must not declare
  a Depends, Recommends, or Build-Depends relationship on a non-
  main package))).  Since sphinx is outside of the main archive,
  packages inside main cannot depend on it.

  The documentation needs to be moved to a separate package outside of
  main, or chose a documentation builder that can be included as part of
  the build without violating policy.

  See https://code.launchpad.net/~didrocks/ubuntu-ui-toolkit/unblock-
  proposed/+merge/211267 for information on the removal.

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

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


[Touch-packages] [Bug 1398104] [NEW] Support multi-arch click build (single fat click package)

2014-12-01 Thread Nicholas Skaggs
Public bug reported:

It should be possible for click build to target more than one
architecture so that I can build a single package that will support
multi-architectures. This is useful for providing a single package in
the click store instead of maintaining separate packages.

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

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

Title:
  Support multi-arch click build (single fat click package)

Status in click package in Ubuntu:
  New

Bug description:
  It should be possible for click build to target more than one
  architecture so that I can build a single package that will support
  multi-architectures. This is useful for providing a single package in
  the click store instead of maintaining separate packages.

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

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


[Touch-packages] [Bug 1396611] Re: Can't install click packages with pkcon

2014-11-26 Thread Nicholas Skaggs
As a workaround for now, you install the packages using click install as
suggested. You will also then need to use click register to register
them under your user.

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

Title:
  Can't install click packages with pkcon

Status in “click” package in Ubuntu:
  Confirmed

Bug description:
  Trying to install a click package using pkcon I get the following
  error. Apparently this is the reason why installing packages from the
  Ubuntu Store fails on my laptop.

  
  mzanetti@noneyet ~/.local/share/ubuntu-download-manager  $  pkcon 
install-local Downloads/com.ubuntu.developer.robert-ancell.dotty_2_all.click 
  Installing files  [=] 
  Loading cache [=] 
  Resolving dependencies[=] 
  Finished  [=] 
  Installing files  [=] 
  Loading cache [=] 
  Resolving dependencies[=] 
  Waiting for authentication[=] 
  Loading cache [=] 
  Resolving dependencies[=] 
  Committing changes[=] 
  Finished  [=] 
  (Reading database ... 588050 files and directories currently installed.)
  Preparing to unpack .../com.ubuntu.developer.robert-ancell.dotty_2_all.click 
...
  Click packages may not be installed directly using dpkg.
  Use 'click install' instead.
  dpkg: error processing archive 
/home/mzanetti/.local/share/ubuntu-download-manager/Downloads/com.ubuntu.developer.robert-ancell.dotty_2_all.click
 (--install):
   subprocess new pre-installation script returned error exit status 1
  Errors were encountered while processing:
   
/home/mzanetti/.local/share/ubuntu-download-manager/Downloads/com.ubuntu.developer.robert-ancell.dotty_2_all.click

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

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


[Touch-packages] [Bug 1311370] Re: One or more needed GStreamer elements are missing: cluttervideosink

2014-11-26 Thread Nicholas Skaggs
Seb, this seems to me like cheese itself is simply missing a declared
dependency on gstreamer1.0-clutter. Cheese doesn't work without it, and
installing it fixes the issue.

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

Title:
  One or more needed GStreamer elements are missing: cluttervideosink

Status in “gstreamer1.0” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04 fresh install.
  When launching cheese this error message is displayed
  One or more needed GStreamer elements are missing: cluttervideosink.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cheese 3.10.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 22 23:32:11 2014
  InstallationDate: Installed on 2014-04-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: cheese
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1311370/+subscriptions

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


[Touch-packages] [Bug 1394063] [NEW] Inspiron 3137 brightness keys aren't recognized

2014-11-18 Thread Nicholas Skaggs
Public bug reported:

Hardware keys on an inspirion 3137 for brightness don't work. Manually setting 
the backlight via /sys/class/backlight/intel_backlight/brightness
 works properly. This worked properly in vivid and has been broken since 
upgrade.

Xev doesn't show a keypress event. Scan codes from evtest are shown
below:

Event: time 1416367751.898584, -- EV_SYN 
Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
Event: time 1416367754.952917, type 1 (EV_KEY), code 224 (KEY_BRIGHTNESSDOWN), 
value 1
Event: time 1416367754.952917, -- EV_SYN 
Event: time 1416367754.952946, type 1 (EV_KEY), code 224 (KEY_BRIGHTNESSDOWN), 
value 0
Event: time 1416367754.952946, -- EV_SYN 
Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
Event: time 1416367756.898936, -- EV_SYN 
Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: udev 215-5ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu10
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Nov 18 22:16:25 2014
InstallationDate: Installed on 2014-06-04 (167 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
MachineType: Dell Inc. Inspiron 3137
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
dmi.bios.date: 12/25/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0PRDX0
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Inspiron 3137
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug vivid

** Attachment added: udev-db.txt
   
https://bugs.launchpad.net/bugs/1394063/+attachment/4263436/+files/udev-db.txt

** Description changed:

- Hardware keys on an inspirion 3138 for brightness don't work. Xev
- doesn't show a keypress event.
+ Hardware keys on an inspirion 3137 for brightness don't work. Manually 
setting the backlight via /sys/class/backlight/intel_backlight/brightness
+  works properly. This worked properly in vivid and has been broken since 
upgrade.
  
- Scan codes from evtest are shown below
+ Xev doesn't show a keypress event. Scan codes from evtest are shown
+ below:
  
  Event: time 1416367751.898584, -- EV_SYN 
  Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1416367754.952917, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 1
  Event: time 1416367754.952917, -- EV_SYN 
  Event: time 1416367754.952946, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 0
  Event: time 1416367754.952946, -- EV_SYN 
  Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
  Event: time 1416367756.898936, -- EV_SYN 
  Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 215-5ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 18 22:16:25 2014
  InstallationDate: Installed on 2014-06-04 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 3137
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PRDX0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 3137
  dmi.sys.vendor: Dell Inc.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1394063] Re: intel_backlight brightness keys fail

2014-11-18 Thread Nicholas Skaggs
** Attachment added: lsinput.log
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1394063/+attachment/4263449/+files/lsinput.log

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

Title:
  Inspiron 3137 brightness keys aren't recognized

Status in “systemd” package in Ubuntu:
  New

Bug description:
  Hardware keys on an inspirion 3137 for brightness don't work. Manually 
setting the backlight via /sys/class/backlight/intel_backlight/brightness
   works properly. This worked properly in vivid and has been broken since 
upgrade.

  Xev doesn't show a keypress event. Scan codes from evtest are shown
  below:

  Event: time 1416367751.898584, -- EV_SYN 
  Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1416367754.952917, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 1
  Event: time 1416367754.952917, -- EV_SYN 
  Event: time 1416367754.952946, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 0
  Event: time 1416367754.952946, -- EV_SYN 
  Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
  Event: time 1416367756.898936, -- EV_SYN 
  Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 215-5ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 18 22:16:25 2014
  InstallationDate: Installed on 2014-06-04 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 3137
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PRDX0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 3137
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1394063] Re: intel_backlight brightness keys fail

2014-11-18 Thread Nicholas Skaggs
** Attachment added: xkbmap.txt
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1394063/+attachment/4263451/+files/xkbmap.txt

** Summary changed:

- intel_backlight brightness keys fail 
+ Inspiron 3137 brightness keys aren't recognized

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

Title:
  Inspiron 3137 brightness keys aren't recognized

Status in “systemd” package in Ubuntu:
  New

Bug description:
  Hardware keys on an inspirion 3137 for brightness don't work. Manually 
setting the backlight via /sys/class/backlight/intel_backlight/brightness
   works properly. This worked properly in vivid and has been broken since 
upgrade.

  Xev doesn't show a keypress event. Scan codes from evtest are shown
  below:

  Event: time 1416367751.898584, -- EV_SYN 
  Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1416367754.952917, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 1
  Event: time 1416367754.952917, -- EV_SYN 
  Event: time 1416367754.952946, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 0
  Event: time 1416367754.952946, -- EV_SYN 
  Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
  Event: time 1416367756.898936, -- EV_SYN 
  Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 215-5ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 18 22:16:25 2014
  InstallationDate: Installed on 2014-06-04 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 3137
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PRDX0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 3137
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1394063] Re: Inspiron 3137 brightness keys aren't recognized

2014-11-18 Thread Nicholas Skaggs
Looks like potentially another bug, as apport things I upgraded on my
original install date;

UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)

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

Title:
  Inspiron 3137 brightness keys aren't recognized

Status in “systemd” package in Ubuntu:
  New

Bug description:
  Hardware keys on an inspirion 3137 for brightness don't work. Manually 
setting the backlight via /sys/class/backlight/intel_backlight/brightness
   works properly. This worked properly in vivid and has been broken since 
upgrade.

  Xev doesn't show a keypress event. Scan codes from evtest are shown
  below:

  Event: time 1416367751.898584, -- EV_SYN 
  Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1416367754.952917, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 1
  Event: time 1416367754.952917, -- EV_SYN 
  Event: time 1416367754.952946, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 0
  Event: time 1416367754.952946, -- EV_SYN 
  Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
  Event: time 1416367756.898936, -- EV_SYN 
  Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 215-5ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 18 22:16:25 2014
  InstallationDate: Installed on 2014-06-04 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 3137
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PRDX0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 3137
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1394063] Re: intel_backlight brightness keys fail

2014-11-18 Thread Nicholas Skaggs
** Attachment added: xkbcomp.txt
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1394063/+attachment/4263450/+files/xkbcomp.txt

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

Title:
  Inspiron 3137 brightness keys aren't recognized

Status in “systemd” package in Ubuntu:
  New

Bug description:
  Hardware keys on an inspirion 3137 for brightness don't work. Manually 
setting the backlight via /sys/class/backlight/intel_backlight/brightness
   works properly. This worked properly in vivid and has been broken since 
upgrade.

  Xev doesn't show a keypress event. Scan codes from evtest are shown
  below:

  Event: time 1416367751.898584, -- EV_SYN 
  Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1416367754.952917, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 1
  Event: time 1416367754.952917, -- EV_SYN 
  Event: time 1416367754.952946, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 0
  Event: time 1416367754.952946, -- EV_SYN 
  Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
  Event: time 1416367756.898936, -- EV_SYN 
  Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 215-5ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 18 22:16:25 2014
  InstallationDate: Installed on 2014-06-04 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 3137
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PRDX0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 3137
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1394063] Re: intel_backlight brightness keys fail

2014-11-18 Thread Nicholas Skaggs
** Attachment added: dmesg.log
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1394063/+attachment/4263448/+files/dmesg.log

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

Title:
  Inspiron 3137 brightness keys aren't recognized

Status in “systemd” package in Ubuntu:
  New

Bug description:
  Hardware keys on an inspirion 3137 for brightness don't work. Manually 
setting the backlight via /sys/class/backlight/intel_backlight/brightness
   works properly. This worked properly in vivid and has been broken since 
upgrade.

  Xev doesn't show a keypress event. Scan codes from evtest are shown
  below:

  Event: time 1416367751.898584, -- EV_SYN 
  Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1416367754.952917, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 1
  Event: time 1416367754.952917, -- EV_SYN 
  Event: time 1416367754.952946, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 0
  Event: time 1416367754.952946, -- EV_SYN 
  Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
  Event: time 1416367756.898936, -- EV_SYN 
  Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 215-5ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 18 22:16:25 2014
  InstallationDate: Installed on 2014-06-04 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 3137
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PRDX0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 3137
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1394063] Re: Inspiron 3137 brightness keys aren't recognized

2014-11-18 Thread Nicholas Skaggs
Ahh, that's https://bugs.launchpad.net/ubuntu/+source/apport/+bug/788936

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

Title:
  Inspiron 3137 brightness keys aren't recognized

Status in “systemd” package in Ubuntu:
  New

Bug description:
  Hardware keys on an inspirion 3137 for brightness don't work. Manually 
setting the backlight via /sys/class/backlight/intel_backlight/brightness
   works properly. This worked properly in vivid and has been broken since 
upgrade.

  Xev doesn't show a keypress event. Scan codes from evtest are shown
  below:

  Event: time 1416367751.898584, -- EV_SYN 
  Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1416367754.952917, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 1
  Event: time 1416367754.952917, -- EV_SYN 
  Event: time 1416367754.952946, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 0
  Event: time 1416367754.952946, -- EV_SYN 
  Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
  Event: time 1416367756.898936, -- EV_SYN 
  Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 215-5ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 18 22:16:25 2014
  InstallationDate: Installed on 2014-06-04 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 3137
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PRDX0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 3137
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1327419] Re: Infographic's language not updated until the metric value is changed

2014-11-07 Thread Nicholas Skaggs
This is still in effect. I noticed this without the music application,
but changing language causes the infographic to stay in the original
language (seemingly until it's value would be changed)

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

Title:
  Infographic's language not updated until the metric value is changed

Status in Ubuntu Translations:
  Triaged
Status in “libusermetrics” package in Ubuntu:
  Confirmed

Bug description:
  1) Start the music app
  2) Play a track for more than 10 seconds to trigger the metric update
  3) Lock and unlock to show the infographic
  4) Note, for example, 1 song played today appears (double tap to cycle 
through to find music if required)
  5) Goto system settings and change the language
  6) Restart the device
  7) Note the infographic's language has not been updated and it still states 
'1 song played today'
  8) Start the music app
  9) Play a track for more than 10 seconds to trigger the metric update
  10) Lock and unlock to show the infographic
  11) Now notice the infographic's language is now correct, for example 2 
Morceaux joues aujourd'hui

  It was expected that step 7 the infographic would show the correct
  language.

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

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


[Touch-packages] [Bug 1383479] [NEW] Remove autopilot from touch images

2014-10-20 Thread Nicholas Skaggs
Public bug reported:

Autopilot should be removed from the image. We intend to ship a consumer
image, testing and debugging packages such as autopilot should not be
needed.

The ramfications affect app developers and CI who depend and assume
autopilot exists on the image. To fix this, CI will migrate to adt-run.
In the interim, autopilot will be added as a dependency so the current
CI setup continues to run properly.

phablet-test-run will also migrate to a wrapper for adt-run so users who
have not already switched will have a seamless experience.

** Affects: ubuntu-touch-meta (Ubuntu)
 Importance: Critical
 Assignee: Oliver Grawert (ogra)
 Status: Confirmed


** Tags: rtm14

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

Title:
  Remove autopilot from touch images

Status in “ubuntu-touch-meta” package in Ubuntu:
  Confirmed

Bug description:
  Autopilot should be removed from the image. We intend to ship a
  consumer image, testing and debugging packages such as autopilot
  should not be needed.

  The ramfications affect app developers and CI who depend and assume
  autopilot exists on the image. To fix this, CI will migrate to adt-
  run. In the interim, autopilot will be added as a dependency so the
  current CI setup continues to run properly.

  phablet-test-run will also migrate to a wrapper for adt-run so users
  who have not already switched will have a seamless experience.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1383479/+subscriptions

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


[Touch-packages] [Bug 1383479] Re: Remove autopilot from touch images

2014-10-20 Thread Nicholas Skaggs
** Tags removed: rtm-14
** Tags added: rtm14

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

Title:
  Remove autopilot from touch images

Status in “ubuntu-touch-meta” package in Ubuntu:
  Confirmed

Bug description:
  Autopilot should be removed from the image. We intend to ship a
  consumer image, testing and debugging packages such as autopilot
  should not be needed.

  The ramfications affect app developers and CI who depend and assume
  autopilot exists on the image. To fix this, CI will migrate to adt-
  run. In the interim, autopilot will be added as a dependency so the
  current CI setup continues to run properly.

  phablet-test-run will also migrate to a wrapper for adt-run so users
  who have not already switched will have a seamless experience.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1383479/+subscriptions

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


[Touch-packages] [Bug 1379836] Re: dialer and messaging app show unlocked pin as locked

2014-10-10 Thread Nicholas Skaggs
** Summary changed:

- dialer and messaging app say pin locked when it isn't on mako
+ dialer and messaging app show unlocked pin as locked

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

Title:
  dialer and messaging app show unlocked pin as locked

Status in “indicator-network” package in Ubuntu:
  Invalid
Status in “telepathy-ofono” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu System Settings and ofono say it's unlocked but trying to use
  the dialer and messaging app is blocked by thinking the PIN is locked.

  $ system-image-cli -i
  current build number: 81
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-10-10 15:33:48
  version version: 81
  version ubuntu: 20141010.1
  version device: 20140929.1
  version custom: mako-0.7

  $ phablet-shell 
  /home/sergiusens/.ssh/known_hosts updated.
  Original contents retained as /home/sergiusens/.ssh/known_hosts.old
  Warning: Permanently added '[localhost]:' (RSA) to the list of known 
hosts.
  Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 3.4.0-5-mako 
armv7l)

   * Documentation:  https://help.ubuntu.com/
  Last login: Fri Oct 10 15:37:40 2014 from localhost.localdomain
  phablet@ubuntu-phablet:~$ lis^C
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems 
  [ /ril_0 ]
  Features = gprs ussd net sms rat sim 
  Model = Fake Modem Model
  Powered = 1
  Emergency = 0
  Online = 1
  Interfaces = org.ofono.ConnectionManager org.ofono.CallBarring 
org.ofono.CallSettings org.ofono.SupplementaryServices 
org.ofono.NetworkRegistration org.ofono.CallForwarding org.ofono.SmartMessaging 
org.ofono.PushNotification org.ofono.MessageManager org.ofono.NetworkTime 
org.ofono.MessageWaiting org.ofono.RadioSettings org.ofono.SimManager 
org.ofono.CallVolume org.ofono.VoiceCallManager 
  Revision = M9615A-CEFWMAZM-2.0.1701.03
  Type = hardware
  Manufacturer = Fake Manufacturer
  Serial = 355136052657866
  Lockdown = 0
  [ org.ofono.ConnectionManager ]
  Bearer = hspa
  RoamingAllowed = 0
  Suspended = 0
  Powered = 1
  Attached = 1
  [ org.ofono.CallBarring ]
  VoiceIncoming = disabled
  VoiceOutgoing = disabled
  [ org.ofono.CallSettings ]
  CallingLineRestriction = off
  HideCallerId = default
  ConnectedLinePresentation = unknown
  ConnectedLineRestriction = unknown
  CallingLinePresentation = enabled
  CallingNamePresentation = unknown
  CalledLinePresentation = disabled
  VoiceCallWaiting = enabled
  [ org.ofono.SupplementaryServices ]
  State = idle
  [ org.ofono.NetworkRegistration ]
  Mode = auto
  Name = Personal
  LocationAreaCode = 394
  Status = registered
  CellId = 14122637
  MobileCountryCode = 722
  Technology = umts
  Strength = 61
  MobileNetworkCode = 34
  [ org.ofono.CallForwarding ]
  VoiceNotReachable = +541151009255
  VoiceNoReplyTimeout = 25
  VoiceUnconditional = 
  VoiceNoReply = +541151009255
  ForwardingFlagOnSim = 0
  VoiceBusy = +541151009255
  [ org.ofono.SmartMessaging ]
  [ org.ofono.PushNotification ]
  [ org.ofono.MessageManager ]
  Alphabet = default
  UseDeliveryReports = 0
  ServiceCenterAddress = +541151740055
  Bearer = cs-preferred
  [ org.ofono.NetworkTime ]
  [ org.ofono.MessageWaiting ]
  VoicemailWaiting = 0
  VoicemailMailboxNumber = *555
  VoicemailMessageCount = 0
  [ org.ofono.RadioSettings ]
  TechnologyPreference = umts
  ModemTechnologies = gsm umts 
  FastDormancy = 0
  [ org.ofono.SimManager ]
  CardIdentifier = 89543421113404033941
  ServiceNumbers = [Llam. a su Cargo] = '11' [Club Personal] = 
'*2582' [Personal] = '+810' [At. Clientes] = '*111' 
  Retries = 
  FixedDialing = 0
  SubscriberIdentity = 722341240403394
  MobileCountryCode = 722
  BarredDialing = 0
  PinRequired = none
  LockedPins = 
  SubscriberNumbers = 
  Present = 1
  PreferredLanguages = es en pt it 
  MobileNetworkCode = 34
  [ org.ofono.CallVolume ]
  MicrophoneVolume = 0
  Muted = 1
  SpeakerVolume = 0
  [ org.ofono.VoiceCallManager ]
  EmergencyNumbers = 112 911

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

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

[Touch-packages] [Bug 1378927] [NEW] Applications that fail to launch persist in right edge app switcher

2014-10-08 Thread Nicholas Skaggs
Public bug reported:

Applications that fail to launch are still shown in the app switcher.
They currently displays as blank screens, with the spinner animation.
It's been over 10 minutes and the console log shows clearly the
application failed to launch. This was encountered during testing, so I
have 15 instances of filemanager via 15 failed tests.

There seem to be a couple failures:
multiple loading screens are generated for a single application
application loading screens persist indefinitely in the event of an error 
during load

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


** Tags: avengers

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

Title:
  Applications that fail to launch persist in right edge app switcher

Status in “unity8” package in Ubuntu:
  New

Bug description:
  Applications that fail to launch are still shown in the app switcher.
  They currently displays as blank screens, with the spinner animation.
  It's been over 10 minutes and the console log shows clearly the
  application failed to launch. This was encountered during testing, so
  I have 15 instances of filemanager via 15 failed tests.

  There seem to be a couple failures:
  multiple loading screens are generated for a single application
  application loading screens persist indefinitely in the event of an error 
during load

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

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


[Touch-packages] [Bug 1341681] Re: Autopilot tests should stop using deprecated emulators module

2014-09-22 Thread Nicholas Skaggs
** Changed in: ubuntu-filemanager-app
 Assignee: (unassigned) = Nicholas Skaggs (nskaggs)

** Branch linked: lp:~ubuntu-filemanager-dev/ubuntu-filemanager-app
/force-authentication-parameter

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

Title:
  Autopilot tests should stop using deprecated emulators module

Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Dropping Letters:
  New
Status in Music application for Ubuntu devices:
  Fix Released
Status in Notes App:
  New
Status in Ubuntu Reminders app:
  Fix Released
Status in Sudoku game for Ubuntu Touch:
  New
Status in Calculator application for Ubuntu devices:
  Fix Committed
Status in Calendar application for Ubuntu devices:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in Document Viewer application for Ubuntu devices:
  New
Status in File Manager application for Ubuntu devices:
  New
Status in RSS Feed Reader application for Ubuntu devices:
  New
Status in Terminal application for Ubuntu devices:
  Fix Released
Status in Weather application for Ubuntu devices:
  New
Status in “dialer-app” package in Ubuntu:
  Fix Released

Bug description:
  Autopilot tests should stop using deprecated emulators module. Instead
  the new custom_proxy_objects modules should be used and called
  directly.

  Please note until https://bugs.launchpad.net/ubuntu-ui-
  toolkit/+bug/1341679 is fixed, the deprecation warning will still
  appear.

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

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


[Touch-packages] [Bug 1341681] Re: Autopilot tests should stop using deprecated emulators module

2014-09-15 Thread Nicholas Skaggs
** Also affects: ubuntu-docviewer-app
   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/1341681

Title:
  Autopilot tests should stop using deprecated emulators module

Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Dropping Letters:
  New
Status in Music application for Ubuntu devices:
  Fix Released
Status in Notes App:
  New
Status in Ubuntu Reminders app:
  Fix Released
Status in Sudoku game for Ubuntu Touch:
  New
Status in Calculator application for Ubuntu devices:
  Fix Committed
Status in Calendar application for Ubuntu devices:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in Document Viewer application for Ubuntu devices:
  New
Status in File Manager application for Ubuntu devices:
  New
Status in RSS Feed Reader application for Ubuntu devices:
  New
Status in Terminal application for Ubuntu devices:
  Fix Released
Status in Weather application for Ubuntu devices:
  New
Status in “dialer-app” package in Ubuntu:
  Fix Released

Bug description:
  Autopilot tests should stop using deprecated emulators module. Instead
  the new custom_proxy_objects modules should be used and called
  directly.

  Please note until https://bugs.launchpad.net/ubuntu-ui-
  toolkit/+bug/1341679 is fixed, the deprecation warning will still
  appear.

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

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


[Touch-packages] [Bug 1365336] Re: Lightdm update=No desktop

2014-09-08 Thread Nicholas Skaggs
** Also affects: xserver-xorg-video-vesa (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xserver-xorg-video-vesa (Ubuntu)
   Status: New = Confirmed

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

Title:
  Lightdm update=No desktop

Status in “fglrx-installer” package in Ubuntu:
  In Progress
Status in “fglrx-installer-updates” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released
Status in “xserver-xorg-video-vesa” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-vmware” package in Ubuntu:
  Confirmed

Bug description:
  Update to lightdm from 1.11.7-0ubuntu1 to 1.11.8-0ubuntu1 leaves me
  with no desktop on normal boot.

  Machine boots directly to tty1.

  Logged in at tty1 and then startx leads to a desktop that requires
  password to start properly and with themes unapplied.

  Password required to reboot machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.11.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep  4 08:20:14 2014
  InstallationDate: Installed on 2014-07-17 (48 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140717)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1365336/+subscriptions

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


[Touch-packages] [Bug 1358413] Re: Emulator locks up 30 seconds after boot

2014-09-05 Thread Nicholas Skaggs
As of today this is working again. I'll file a new bug if it regresses.

** Changed in: mir (Ubuntu)
   Status: New = Invalid

** Changed in: android (Ubuntu)
   Status: New = Invalid

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

Title:
  Emulator locks up 30 seconds after boot

Status in “android” package in Ubuntu:
  Invalid
Status in “mir” package in Ubuntu:
  Invalid

Bug description:
  Currently booting the devel-proposed image:

  devel-proposed  ubuntu=20140818,device=20140811.1,version=198

  I am able to boot the image and interact with it for less than 30
  seconds before the UI and emulator locks and must be closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-emulator 0.3+14.10.20140807-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.6-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 18 13:34:20 2014
  InstallationDate: Installed on 2013-12-19 (242 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131218)
  SourcePackage: goget-ubuntu-touch
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to utopic on 2014-05-09 (101 days ago)

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

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


[Touch-packages] [Bug 1341681] Re: Autopilot tests should stop using deprecated emulators module

2014-09-05 Thread Nicholas Skaggs
** Branch linked: lp:~nskaggs/ubuntu-calculator-app/ap-fix-missing-
keypress

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

Title:
  Autopilot tests should stop using deprecated emulators module

Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Dropping Letters:
  New
Status in Music application for Ubuntu devices:
  Fix Committed
Status in Notes App:
  New
Status in Ubuntu Reminders app:
  Fix Released
Status in Sudoku game for Ubuntu Touch:
  New
Status in Calculator application for Ubuntu devices:
  In Progress
Status in Calendar application for Ubuntu devices:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in File Manager application for Ubuntu devices:
  New
Status in RSS Feed Reader application for Ubuntu devices:
  New
Status in Terminal application for Ubuntu devices:
  Fix Released
Status in Weather application for Ubuntu devices:
  New
Status in “dialer-app” package in Ubuntu:
  Fix Released

Bug description:
  Autopilot tests should stop using deprecated emulators module. Instead
  the new custom_proxy_objects modules should be used and called
  directly.

  Please note until https://bugs.launchpad.net/ubuntu-ui-
  toolkit/+bug/1341679 is fixed, the deprecation warning will still
  appear.

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

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


[Touch-packages] [Bug 1341681] Re: Autopilot tests should stop using deprecated emulators module

2014-09-05 Thread Nicholas Skaggs
** Changed in: ubuntu-terminal-app
   Status: Fix Committed = Fix Released

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

Title:
  Autopilot tests should stop using deprecated emulators module

Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Dropping Letters:
  New
Status in Music application for Ubuntu devices:
  Fix Committed
Status in Notes App:
  New
Status in Ubuntu Reminders app:
  Fix Released
Status in Sudoku game for Ubuntu Touch:
  New
Status in Calculator application for Ubuntu devices:
  In Progress
Status in Calendar application for Ubuntu devices:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in File Manager application for Ubuntu devices:
  New
Status in RSS Feed Reader application for Ubuntu devices:
  New
Status in Terminal application for Ubuntu devices:
  Fix Released
Status in Weather application for Ubuntu devices:
  New
Status in “dialer-app” package in Ubuntu:
  New

Bug description:
  Autopilot tests should stop using deprecated emulators module. Instead
  the new custom_proxy_objects modules should be used and called
  directly.

  Please note until https://bugs.launchpad.net/ubuntu-ui-
  toolkit/+bug/1341679 is fixed, the deprecation warning will still
  appear.

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

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


[Touch-packages] [Bug 1341681] Re: Autopilot tests should stop using deprecated emulators module

2014-09-04 Thread Nicholas Skaggs
** Changed in: ubuntu-calendar-app
   Status: Fix Committed = Fix Released

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

Title:
  Autopilot tests should stop using deprecated emulators module

Status in Dialer app for Ubuntu Touch:
  In Progress
Status in Dropping Letters:
  New
Status in Music application for Ubuntu devices:
  Fix Committed
Status in Notes App:
  New
Status in Ubuntu Reminders app:
  Fix Released
Status in Sudoku game for Ubuntu Touch:
  New
Status in Calculator application for Ubuntu devices:
  In Progress
Status in Calendar application for Ubuntu devices:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in File Manager application for Ubuntu devices:
  New
Status in RSS Feed Reader application for Ubuntu devices:
  New
Status in Terminal application for Ubuntu devices:
  Fix Committed
Status in Weather application for Ubuntu devices:
  New
Status in “dialer-app” package in Ubuntu:
  New

Bug description:
  Autopilot tests should stop using deprecated emulators module. Instead
  the new custom_proxy_objects modules should be used and called
  directly.

  Please note until https://bugs.launchpad.net/ubuntu-ui-
  toolkit/+bug/1341679 is fixed, the deprecation warning will still
  appear.

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

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


[Touch-packages] [Bug 1317639] Re: Add /home patching to autopilot helper

2014-09-02 Thread Nicholas Skaggs
I'll note that the music implementation does not give apparmor errors,
and properly mocks on both the desktop and the device. I think we can
utilize it for the helper.

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

Title:
  Add /home patching to autopilot helper

Status in Ubuntu UI Toolkit:
  In Progress
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  In Progress

Bug description:
  Add the ability to properly setup /home with a fake env instead so
  tests can run in a pristine environment without messing with the real
  system.

  See calendar __init__.py for an example implementation using fixtures.

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

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


[Touch-packages] [Bug 1358436] [NEW] Indicator sound missing

2014-08-18 Thread Nicholas Skaggs
Public bug reported:

Indicator sound is missing from the panel. Restarting the panel service
doesn't bring it up. Neither does a reboot.

The menu reappeared only after toggling the dconf setting:

gsettings set com.canonical.indicator.sound visible false
gsettings set com.canonical.indicator.sound visible true

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
Uname: Linux 3.16.0-9-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.6-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Aug 18 14:31:05 2014
InstallationDate: Installed on 2013-12-19 (242 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131218)
SourcePackage: indicator-sound
SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli'
UpgradeStatus: Upgraded to utopic on 2014-05-09 (101 days ago)
upstart.indicator-sound.log:
 (process:7458): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
 
 ** (process:12518): CRITICAL **: volume_control_set_volume_internal: assertion 
'_tmp1_ == PA_CONTEXT_READY' failed

** Affects: indicator-sound (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug utopic

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

Title:
  Indicator sound missing

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  Indicator sound is missing from the panel. Restarting the panel
  service doesn't bring it up. Neither does a reboot.

  The menu reappeared only after toggling the dconf setting:

  gsettings set com.canonical.indicator.sound visible false
  gsettings set com.canonical.indicator.sound visible true

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.6-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 18 14:31:05 2014
  InstallationDate: Installed on 2013-12-19 (242 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131218)
  SourcePackage: indicator-sound
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to utopic on 2014-05-09 (101 days ago)
  upstart.indicator-sound.log:
   (process:7458): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
   
   ** (process:12518): CRITICAL **: volume_control_set_volume_internal: 
assertion '_tmp1_ == PA_CONTEXT_READY' failed

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

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


[Touch-packages] [Bug 1358436] Re: Indicator sound missing from unity panel

2014-08-18 Thread Nicholas Skaggs
** Summary changed:

- Indicator sound missing
+ Indicator sound missing from unity panel

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

Title:
  Indicator sound missing from unity panel

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  Indicator sound is missing from the panel. Restarting the panel
  service doesn't bring it up. Neither does a reboot.

  The menu reappeared only after toggling the dconf setting:

  gsettings set com.canonical.indicator.sound visible false
  gsettings set com.canonical.indicator.sound visible true

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.6-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 18 14:31:05 2014
  InstallationDate: Installed on 2013-12-19 (242 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131218)
  SourcePackage: indicator-sound
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to utopic on 2014-05-09 (101 days ago)
  upstart.indicator-sound.log:
   (process:7458): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
   
   ** (process:12518): CRITICAL **: volume_control_set_volume_internal: 
assertion '_tmp1_ == PA_CONTEXT_READY' failed

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

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


[Touch-packages] [Bug 1317639] Re: Add /home patching to autopilot helper

2014-07-15 Thread Nicholas Skaggs
** Tags added: autopilot-helper

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

Title:
  Add /home patching to autopilot helper

Status in Ubuntu UI Toolkit:
  In Progress
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  In Progress

Bug description:
  Add the ability to properly setup /home with a fake env instead so
  tests can run in a pristine environment without messing with the real
  system.

  See calendar __init__.py for an example implementation using fixtures.

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

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