[Touch-packages] [Bug 1614576] Re: Upgrade from xenial to yakkety fails when install policykit-1

[Max Brustkern]

The end of /var/log/dist-upgrade/main.log is showing a unicode decode error:
2016-09-09 14:21:30,594 DEBUG linux-image-4.4.0-9136-generic (new-install) 
added with 45669149 to boot space
2016-09-09 14:21:31,638 DEBUG dir '/var/cache/apt/archives' needs '180762526' 
of '' (21087518720.00)
2016-09-09 14:21:31,638 DEBUG dir '/usr' needs '354729984' of 
'' (20906756194.00)
2016-09-09 14:21:31,639 DEBUG dir '/usr' needs '52428800' of 
'' (20552026210.00)
2016-09-09 14:21:31,639 DEBUG dir '/boot' needs '91338298' of 
'' (20499597410.00)
2016-09-09 14:21:31,639 DEBUG dir '/tmp' needs '5242880' of 
'' (20408259112.00)
2016-09-09 14:21:31,639 DEBUG dir '/' needs '10485760' of 
'' (20403016232.00)
2016-09-09 14:21:31,640 DEBUG dir '/tmp' needs '0.0' of 
'' (20392530472.00)
2016-09-09 14:21:31,640 DEBUG dir '/usr' needs '0.0' of 
'' (20392530472.00)
2016-09-09 14:21:31,643 DEBUG demoted: 'makedev'
2016-09-09 14:21:31,643 DEBUG found components: {'yakkety-security': set(), 
'yakkety': {'multiverse', 'universe', 'restricted', 'main'}, 'yakkety-updates': 
{'multiverse', 'universe', 'restricted', 'main'}
}
2016-09-09 14:21:31,810 DEBUG toinstall: '['btrfs-progs', 'dirmngr', 
'gnupg-agent', 'gnupg-l10n', 'libassuan0', 'libicu57', 'libip4tc0', 
'libip6tc0', 'libiptc0', 'libjson-c3', 'libksba8', 'libnpth0', 'libpng16-16', 
'libprocps6', 'linux-headers-4.4.0-9136', 'linux-headers-4.4.0-9136-generic', 
'linux-image-4.4.0-9136-generic', 'linux-image-extra-4.4.0-9136-generic', 
'pinentry-curses', 'python3-crypto', 'python3-distro-info', 'python3-httplib2', 
'python3-keyring', 'python3-keyrings.alt', 'python3-launchpadlib', 
'python3-lazr.restfulclient', 'python3-lazr.uri', 'python3-oauth', 
'python3-secretstorage', 'python3-setuptools', 'python3-simplejson', 
'python3-wadllib', 'python3-zope.interface']'
2016-09-09 14:21:31,811 DEBUG toupgrade: '['apparmor', 'apport', 'apt', 
'apt-transport-https', 'apt-utils', 'base-files', 'base-passwd', 'bash', 
'bash-completion', 'bind9-host', 'bsdutils', 'btrfs-tools', 
'busybox-initramfs', 'busybox-static', 'byobu', 'bzip2', 'cloud-guest-utils', 
'cloud-initramfs-copymods', 'cloud-initramfs-dyn-netconf', 'console-setup', 
'console-setup-linux', 'cryptsetup-bin', 'curl', 'dash', 'dbus', 'debconf', 
'debconf-i18n', 'debianutils', 'dh-python', 'distro-info-data', 'dmidecode', 
'dmsetup', 'dnsmasq-base', 'dnsutils', 'dosfstools', 'dpkg', 'e2fslibs', 
'e2fsprogs', 'ed', 'ethtool', 'file', 'findutils', 'friendly-recovery', 'fuse', 
'gcc-5-base', 'gcc-6-base', 'geoip-database', 'gettext-base', 
'gir1.2-glib-2.0', 'git-man', 'gnupg', 'gpgv', 'grep', 'groff-base', 
'grub-common', 'grub-legacy-ec2', 'grub-pc', 'grub-pc-bin', 'grub2-common', 
'haveged', 'hdparm', 'hostname', 'ifupdown', 'info', 'init', 
'init-system-helpers', 'initramfs-tools', 'initramfs-tools-bin', 
 'initramfs-tools-core', 'install-info', 'iptables', 'iputils-ping', 
'iputils-tracepath', 'isc-dhcp-client', 'isc-dhcp-common', 'iso-codes', 'kbd', 
'keyboard-configuration', 'klibc-utils', 'kmod', 'krb5-locales', 'less', 
'libaccountsservice0', 'libapparmor-perl', 'libapparmor1', 'libapt-inst2.0', 
'libapt-pkg5.0', 'libasprintf0v5', 'libatm1', 'libaudit-common', 'libaudit1', 
'libbind9-140', 'libblkid1', 'libbsd0', 'libbz2-1.0', 'libc-bin', 'libc6', 
'libcap-ng0', 'libcap2', 'libcap2-bin', 'libcomerr2', 'libcryptsetup4', 
'libcurl3-gnutls', 'libdb5.3', 'libdbus-1-3', 'libdebconfclient0', 
'libdevmapper-event1.02.1', 'libdevmapper1.02.1', 'libdns-export162', 
'libdns162', 'libdrm2', 'libelf1', 'liberror-perl', 'libestr0', 'libexpat1', 
'libfdisk1', 'libfreetype6', 'libfuse2', 'libgcc1', 'libgcrypt20', 'libgdbm3', 
'libgeoip1', 'libgirepository-1.0-1', 'libglib2.0-0', 'libglib2.0-data', 
'libgmp10', 'libgnutls-openssl27', 'libgnutls30', 'libgpg-error0', 'libgpm2', 
'libgssapi-krb5-2', 'libhavege1
 ', 'libidn11', 'libisc-export160', 'libisc160', 'libisccc140', 'libisccfg140', 
'libk5crypto3', 'libkeyutils1', 'libklibc', 'libkmod2', 'libkrb5-3', 
'libkrb5support0', 'libldap-2.4-2', 'liblocale-gettext-perl', 'liblvm2app2.2', 
'liblwres141', 'liblzma5', 'libmagic1', 'libmnl0', 'libmount1', 'libmpfr4', 
'libncurses5', 'libncursesw5', 'libnewt0.52', 'libnuma1', 'libp11-kit0', 
'libpam-systemd', 

[Touch-packages] [Bug 1614576] Re: Upgrade from xenial to yakkety fails when install policykit-1

[Max Brustkern]

This only appears to occur on unattended upgrades. Additional logs are
attached, and I'll attach some more shortly.

** Attachment added: "dpkg.log"
   
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1614576/+attachment/4737861/+files/dpkg.log

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

Title:
  Upgrade from xenial to yakkety fails when install policykit-1

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  When doing an automated upgrade from xenial to yakkey, I get:
  Preparing to unpack .../policykit-1_0.105-16_amd64.deb ...
  Created symlink /run/systemd/system/polkitd.service auto-upgrade [10:48:43]: 
ERROR: ERROR: Something went wrong with the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: policykit-1 0.105-16
  ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Thu Aug 18 11:02:06 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to yakkety on 2016-08-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1614576/+subscriptions

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

[Touch-packages] [Bug 1614576] Re: Upgrade from xenial to yakkety fails when install policykit-1

[Max Brustkern]

** Attachment added: "var-log-dist-upgrade.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1614576/+attachment/4737863/+files/var-log-dist-upgrade.tgz

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

Title:
  Upgrade from xenial to yakkety fails when install policykit-1

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  When doing an automated upgrade from xenial to yakkey, I get:
  Preparing to unpack .../policykit-1_0.105-16_amd64.deb ...
  Created symlink /run/systemd/system/polkitd.service auto-upgrade [10:48:43]: 
ERROR: ERROR: Something went wrong with the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: policykit-1 0.105-16
  ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Thu Aug 18 11:02:06 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to yakkety on 2016-08-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1614576/+subscriptions

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

[Touch-packages] [Bug 1614576] [NEW] Upgrade from xenial to yakkety fails when install policykit-1

[Max Brustkern]

Public bug reported:

When doing an automated upgrade from xenial to yakkey, I get:
Preparing to unpack .../policykit-1_0.105-16_amd64.deb ...
Created symlink /run/systemd/system/polkitd.service auto-upgrade [10:48:43]: 
ERROR: ERROR: Something went wrong with the upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: policykit-1 0.105-16
ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Thu Aug 18 11:02:06 2016
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: policykit-1
UpgradeStatus: Upgraded to yakkety on 2016-08-18 (0 days ago)

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

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

Title:
  Upgrade from xenial to yakkety fails when install policykit-1

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  When doing an automated upgrade from xenial to yakkey, I get:
  Preparing to unpack .../policykit-1_0.105-16_amd64.deb ...
  Created symlink /run/systemd/system/polkitd.service auto-upgrade [10:48:43]: 
ERROR: ERROR: Something went wrong with the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: policykit-1 0.105-16
  ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Thu Aug 18 11:02:06 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to yakkety on 2016-08-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1614576/+subscriptions

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

[Touch-packages] [Bug 1574969] Re: Regression: "lxc-create -B best" stopped working

[Max Brustkern]

** Also affects: auto-upgrade-testing
   Importance: Undecided
   Status: New

** Changed in: auto-upgrade-testing
 Assignee: (unassigned) => Max Brustkern (nuclearbob)

** Changed in: auto-upgrade-testing
   Importance: Undecided => Medium

** Changed in: auto-upgrade-testing
   Status: New => Triaged

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

Title:
  Regression: "lxc-create -B best" stopped working

Status in Auto Upgrade Testing:
  Triaged
Status in lxc:
  New
Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  I want to use btrfs storage if available, otherwise the plain old
  directory/copies. Until not too long ago, this worked:

$ sudo lxc-create -B best --name=adt-xenial -t ubuntu -- -r xenial

  But now in final xenial it fails with "best is not a valid backing
  storage type.".

  But the manpage still documents it:

If backingstore is 'best', then lxc will try, in order, btrfs, 
zfs, lvm, and finally a  di‐
rectory backing store.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: i3
  Date: Tue Apr 26 08:33:14 2016
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  dnsmasq.conf:
   enable-tftp
   tftp-root=/tmp/tftp
   dhcp-boot=pxelinux.0
  lxc.conf: lxc.lxcpath = /srv/lxc

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-upgrade-testing/+bug/1574969/+subscriptions

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

[Touch-packages] [Bug 1554266] Re: sshd does not start on newly installed desktop system

[Max Brustkern]

Sorry, upgrade-tester is the user, I mistyped it before.

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

Title:
  sshd does not start on newly installed desktop system

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  When I preseed a desktop install using utah for daily iso testing, the
  ssh service is not running when it starts up. journalctl -u ssh shows
  no entries. If I manually start the ssh service, it seems to work. If
  I reboot, sshd is running. On the first boot, however, it is not. This
  problem appears to have started on the March 5 image.

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

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

[Touch-packages] [Bug 1554266] Re: sshd does not start on newly installed desktop system

[Max Brustkern]

I've created some VMs to recreate this on venonat.ubuntu-ci (accessible
via the vpn.) The user is upgrade-test, and I've added ssh keys for
pitti and cyphermox. The problem only occurs on the first boot, so once
we start a VM, we'll need to clone another if we want to recreate again.
As such, please do not start max-ssh-recreate-base. max-ssh-recreate-
base-clone should work, and we can clone the base VM again if needed.

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

Title:
  sshd does not start on newly installed desktop system

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  When I preseed a desktop install using utah for daily iso testing, the
  ssh service is not running when it starts up. journalctl -u ssh shows
  no entries. If I manually start the ssh service, it seems to work. If
  I reboot, sshd is running. On the first boot, however, it is not. This
  problem appears to have started on the March 5 image.

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

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

[Touch-packages] [Bug 1554266] Re: sshd does not start on newly installed desktop system

[Max Brustkern]

If I use the default server preseed:
lp:ubuntu-test-cases/server/preseeds/default.preseed
it starts ssh on server images, but not on desktop images.

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

Title:
  sshd does not start on newly installed desktop system

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  When I preseed a desktop install using utah for daily iso testing, the
  ssh service is not running when it starts up. journalctl -u ssh shows
  no entries. If I manually start the ssh service, it seems to work. If
  I reboot, sshd is running. On the first boot, however, it is not. This
  problem appears to have started on the March 5 image.

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

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

[Touch-packages] [Bug 1554266] Re: sshd does not start on newly installed desktop system

[Max Brustkern]

My attempts at manual recreation so far have failed. I'm going to see if
I can narrow down what potential elements of a preseed might be causing
this.

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

Title:
  sshd does not start on newly installed desktop system

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  When I preseed a desktop install using utah for daily iso testing, the
  ssh service is not running when it starts up. journalctl -u ssh shows
  no entries. If I manually start the ssh service, it seems to work. If
  I reboot, sshd is running. On the first boot, however, it is not. This
  problem appears to have started on the March 5 image.

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

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

[Touch-packages] [Bug 1554266] Re: sshd does not start on newly installed desktop system

[Max Brustkern]

The actual command running on venonat under jenkins is this:
sudo -u utah -i 
UTAH_CONFIG_DIR=/var/lib/jenkins-utah-iso/workspace/ubuntu-xenial-desktop-amd64-smoke-default/config
 run_utah_tests.py -i /var/cache/utah/iso/xenial-desktop-amd64.iso -p 
lp:ubuntu-test-cases/desktop/preseeds/default.cfg 
lp:ubuntu-test-cases/desktop/runlists/default.run -f /var/log/installer -f 
/var/log/installer -x /etc/utah/bridged-network-vm.xml --outputpreseed

But most of that is superfluous and specific to the job.
sudo -u utah -i run_utah_tests.py -i 
/var/cache/utah/iso/xenial-desktop-amd64.iso -p 
lp:ubuntu-test-cases/desktop/preseeds/default.cfg 
lp:ubuntu-test-cases/desktop/runlists/default.run -x 
/etc/utah/bridged-network-vm.xml
should be sufficient. I'm working on a manual recreate now. The thing that 
remains interesting to me is that the problem doesn't occur on server or if oem 
config is enabled.

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

Title:
  sshd does not start on newly installed desktop system

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  When I preseed a desktop install using utah for daily iso testing, the
  ssh service is not running when it starts up. journalctl -u ssh shows
  no entries. If I manually start the ssh service, it seems to work. If
  I reboot, sshd is running. On the first boot, however, it is not. This
  problem appears to have started on the March 5 image.

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

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

[Touch-packages] [Bug 1554266] Re: sshd does not start on newly installed desktop system

[Max Brustkern]

If we enable oem config in the preseed, this problem doesn't occur.

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

Title:
  sshd does not start on newly installed desktop system

Status in openssh package in Ubuntu:
  New

Bug description:
  When I preseed a desktop install using utah for daily iso testing, the
  ssh service is not running when it starts up. journalctl -u ssh shows
  no entries. If I manually start the ssh service, it seems to work. If
  I reboot, sshd is running. On the first boot, however, it is not. This
  problem appears to have started on the March 5 image.

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

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

[Touch-packages] [Bug 1554266] Re: sshd does not start on newly installed desktop system

[Max Brustkern]

I've confirmed that openssh-server is installed on the system, and can
be started manually after the first reboot. I previously saw that it
started automatically after the second reboot, but I haven't confirmed
that this week.

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

Title:
  sshd does not start on newly installed desktop system

Status in openssh package in Ubuntu:
  New

Bug description:
  When I preseed a desktop install using utah for daily iso testing, the
  ssh service is not running when it starts up. journalctl -u ssh shows
  no entries. If I manually start the ssh service, it seems to work. If
  I reboot, sshd is running. On the first boot, however, it is not. This
  problem appears to have started on the March 5 image.

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

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

[Touch-packages] [Bug 1554266] Re: sshd does not start on newly installed desktop system

[Max Brustkern]

This is blocking current image promotions. Is there something I can do
to provide more data for getting it fixed?

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

Title:
  sshd does not start on newly installed desktop system

Status in openssh package in Ubuntu:
  New

Bug description:
  When I preseed a desktop install using utah for daily iso testing, the
  ssh service is not running when it starts up. journalctl -u ssh shows
  no entries. If I manually start the ssh service, it seems to work. If
  I reboot, sshd is running. On the first boot, however, it is not. This
  problem appears to have started on the March 5 image.

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

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

[Touch-packages] [Bug 1554266] Re: sshd does not start on newly installed desktop system

[Max Brustkern]

FWIW, this doesn't happen on current server installs, just desktop.

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

Title:
  sshd does not start on newly installed desktop system

Status in openssh package in Ubuntu:
  New

Bug description:
  When I preseed a desktop install using utah for daily iso testing, the
  ssh service is not running when it starts up. journalctl -u ssh shows
  no entries. If I manually start the ssh service, it seems to work. If
  I reboot, sshd is running. On the first boot, however, it is not. This
  problem appears to have started on the March 5 image.

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

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

Re: [Touch-packages] [Bug 1554266] Re: sshd does not start on newly installed desktop system

[Max Brustkern]

I re-ran this job:
https://platform-qa-jenkins.ubuntu.com/view/smoke-default/job/ubuntu-xenial-desktop-amd64-smoke-default/
It installs from the daily iso using utah. It uses a preseed here:
http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/desktop/view/head:/preseeds/default.cfg
that installs openssh-server via pkgsel.

To verify what was going on, I connected virt-manager to the jenkins
executor node (venonat) and opened a console on the VM while it was waiting
to time out. If you need assistance setting up this recreate method, I can
provide that.

On Wed, Mar 9, 2016 at 11:24 AM, Martin Pitt 
wrote:

> I tried to purge and reinstall openssh-server on today's cloud image
> (with i-s-h 1.29ubuntu1) and ssh.service does start up right away as
> expected. So this naïve reproducer doesn't work. Max, how does openssh-
> server get installed in your case? Sorry for my ignorance, I don't know
> much about preseeding -- is this just translated into some apt-get
> install calls? Do they happen in a chroot with a policy-rc.d or similar?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1554266
>
> Title:
>   sshd does not start on newly installed desktop system
>
> Status in openssh package in Ubuntu:
>   New
>
> Bug description:
>   When I preseed a desktop install using utah for daily iso testing, the
>   ssh service is not running when it starts up. journalctl -u ssh shows
>   no entries. If I manually start the ssh service, it seems to work. If
>   I reboot, sshd is running. On the first boot, however, it is not. This
>   problem appears to have started on the March 5 image.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1554266/+subscriptions
>

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

Title:
  sshd does not start on newly installed desktop system

Status in openssh package in Ubuntu:
  New

Bug description:
  When I preseed a desktop install using utah for daily iso testing, the
  ssh service is not running when it starts up. journalctl -u ssh shows
  no entries. If I manually start the ssh service, it seems to work. If
  I reboot, sshd is running. On the first boot, however, it is not. This
  problem appears to have started on the March 5 image.

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

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

[Touch-packages] [Bug 1554266] Re: sshd does not start on newly installed desktop system

[Max Brustkern]

Can I pin i-s-h during install or is there some other way I can help
verify this?

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

Title:
  sshd does not start on newly installed desktop system

Status in openssh package in Ubuntu:
  New

Bug description:
  When I preseed a desktop install using utah for daily iso testing, the
  ssh service is not running when it starts up. journalctl -u ssh shows
  no entries. If I manually start the ssh service, it seems to work. If
  I reboot, sshd is running. On the first boot, however, it is not. This
  problem appears to have started on the March 5 image.

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

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

[Touch-packages] [Bug 1554266] [NEW] sshd does not start on newly installed desktop system

[Max Brustkern]

Public bug reported:

When I preseed a desktop install using utah for daily iso testing, the
ssh service is not running when it starts up. journalctl -u ssh shows no
entries. If I manually start the ssh service, it seems to work. If I
reboot, sshd is running. On the first boot, however, it is not. This
problem appears to have started on the March 5 image.

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

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

Title:
  sshd does not start on newly installed desktop system

Status in openssh package in Ubuntu:
  New

Bug description:
  When I preseed a desktop install using utah for daily iso testing, the
  ssh service is not running when it starts up. journalctl -u ssh shows
  no entries. If I manually start the ssh service, it seems to work. If
  I reboot, sshd is running. On the first boot, however, it is not. This
  problem appears to have started on the March 5 image.

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

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

[Touch-packages] [Bug 1546688] [NEW] Upgrades to xenial fail when installing initscripts

[Max Brustkern]

Public bug reported:

We're running daily tests upgrading cloud images to xenial. The basic wily 
images started failing to install initscripts as part of the upgrade on 
February 12 in qemu. Trusty images are showing the same issue, where the 
relevant parts of the output are:
Setting up initscripts (2.88dsf-59.3ubuntu2) ...
Installing new version of config file /etc/init.d/halt ...
Installing new version of config file /etc/init.d/killprocs ...
Installing new version of config file /etc/init.d/ondemand ...
Installing new version of config file /etc/init.d/rc.local ...
Installing new version of config file /etc/init.d/reboot ...
Installing new version of config file /etc/init.d/sendsigs ...
Installing new version of config file /etc/init.d/single ...
Installing new version of config file /etc/init.d/umountfs ...
Installing new version of config file /etc/init.d/umountnfs.sh ...
Installing new version of config file /etc/init.d/umountroot ...

Configuration file '/etc/default/rcS'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** rcS (Y/I/N/O/D/Z) [default=N] ?

One example job is here:
https://platform-qa-jenkins.ubuntu.com/view/Upgrade/job/upgrade_ubuntu-wily-xenial-basic-amd64_qemu/97/console

The issues does not appear to occur during lxc upgrades, only qemu.

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

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

Title:
  Upgrades to xenial fail when installing initscripts

Status in sysvinit package in Ubuntu:
  New

Bug description:
  We're running daily tests upgrading cloud images to xenial. The basic wily 
images started failing to install initscripts as part of the upgrade on 
February 12 in qemu. Trusty images are showing the same issue, where the 
relevant parts of the output are:
  Setting up initscripts (2.88dsf-59.3ubuntu2) ...
  Installing new version of config file /etc/init.d/halt ...
  Installing new version of config file /etc/init.d/killprocs ...
  Installing new version of config file /etc/init.d/ondemand ...
  Installing new version of config file /etc/init.d/rc.local ...
  Installing new version of config file /etc/init.d/reboot ...
  Installing new version of config file /etc/init.d/sendsigs ...
  Installing new version of config file /etc/init.d/single ...
  Installing new version of config file /etc/init.d/umountfs ...
  Installing new version of config file /etc/init.d/umountnfs.sh ...
  Installing new version of config file /etc/init.d/umountroot ...

  Configuration file '/etc/default/rcS'
   ==> Modified (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** rcS (Y/I/N/O/D/Z) [default=N] ?

  One example job is here:
  
https://platform-qa-jenkins.ubuntu.com/view/Upgrade/job/upgrade_ubuntu-wily-xenial-basic-amd64_qemu/97/console

  The issues does not appear to occur during lxc upgrades, only qemu.

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

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

Re: [Touch-packages] [Bug 1269578] Re: Autopilot cannot access MediaPlayer component

[Max Brustkern]

It appears to have landed more than a year ago. If the problem remains in
current versions, we may want to open a new bug.

On Sat, Jan 2, 2016 at 1:06 PM, Andrew Hayzen <1269...@bugs.launchpad.net>
wrote:

> Did this fix ever land? As I am unable to access things such as the
> following in QML from autopilot.
>
> Item {
>   property var currentMeta: ({})
> }
>
> --
> You received this bug notification because you are a member of Autopilot
> Hackers, which is subscribed to Autopilot Qt Support.
> https://bugs.launchpad.net/bugs/1269578
>
> Title:
>   Autopilot cannot access MediaPlayer component
>
> Status in Autopilot Qt Support:
>   Confirmed
> Status in autopilot-qt package in Ubuntu:
>   Fix Released
>
> Bug description:
>   When trying to access properties off a MediaPlayer while writing an
>   autopilot test it became apparent that autopilot cannot find the
>   MediaPlayer component.
>
>   I have made an example application which is the SimpleUI with the
> addition of a MediaPlayer component. Within the autopilot tests it attempts
> to access the property currentIndex but fails to find the MediaPlayer with
> the following error:
>   StateNotFoundError: State not found for class '*' and filters
> {'objectName': 'player'}
>
>   I have linked two branches to this bug report, one being the example
>   application and one being the MP for the music-app in which this issue
>   was found.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/autopilot-qt/+bug/1269578/+subscriptions
>

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

Title:
  Autopilot cannot access MediaPlayer component

Status in Autopilot Qt Support:
  Confirmed
Status in autopilot-qt package in Ubuntu:
  Fix Released

Bug description:
  When trying to access properties off a MediaPlayer while writing an
  autopilot test it became apparent that autopilot cannot find the
  MediaPlayer component.

  I have made an example application which is the SimpleUI with the addition of 
a MediaPlayer component. Within the autopilot tests it attempts to access the 
property currentIndex but fails to find the MediaPlayer with the following 
error:
  StateNotFoundError: State not found for class '*' and filters {'objectName': 
'player'}

  I have linked two branches to this bug report, one being the example
  application and one being the MP for the music-app in which this issue
  was found.

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

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

[Touch-packages] [Bug 1497002] Re: Recent Wily i386 live DVDs load with no launcher, top bar, desktop icons, etc.

[Max Brustkern]

When I tried to just run unity, it told me it couldn't find the glib module. I 
did install python-gtk2, but I still got a different error:
root@ubuntu:~# sudo apt-get install python-gtk2
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following extra packages will be installed:
  python-gobject-2
Suggested packages:
  python-gobject-2-dbg python-gtk2-doc
The following NEW packages will be installed:
  python-gobject-2 python-gtk2
0 upgraded, 2 newly installed, 0 to remove and 122 not upgraded.
Need to get 764 kB of archives.
After this operation, 4,287 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu/ wily/main python-gobject-2 i386 
2.28.6-12build1 [166 kB]
Get:2 http://archive.ubuntu.com/ubuntu/ wily/main python-gtk2 i386 
2.24.0-4ubuntu1 [598 kB]
Fetched 764 kB in 0s (1,676 kB/s)
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another 
process: Resource temporarily unavailable
Selecting previously unselected package python-gobject-2.
(Reading database ... 191248 files and directories currently installed.)
Preparing to unpack .../python-gobject-2_2.28.6-12build1_i386.deb ...
Unpacking python-gobject-2 (2.28.6-12build1) ...
Selecting previously unselected package python-gtk2.
Preparing to unpack .../python-gtk2_2.24.0-4ubuntu1_i386.deb ...
Unpacking python-gtk2 (2.24.0-4ubuntu1) ...
Setting up python-gobject-2 (2.28.6-12build1) ...
Setting up python-gtk2 (2.24.0-4ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu4) ...
root@ubuntu:~# unity
WARNING: no DISPLAY variable set, setting it to :0
stop: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
start: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
compiz (core) - Info: Loading plugin: core
compiz (core) - Info: Starting plugin: core
compiz (core) - Info: Loading plugin: ccp
compiz (core) - Info: Starting plugin: ccp

(process:7286): GLib-WARNING **: In call to g_spawn_sync(), exit status
of a child process was requested but ECHILD was received by waitpid().
Most likely the process is ignoring SIGCHLD, or some other thread is
invoking waitpid() with a nonpositive first argument; either behavior
can break applications that use g_spawn_sync either directly or
indirectly.

(process:7286): dconf-WARNING **: failed to commit changes to dconf:
Error spawning command line 'dbus-launch
--autolaunch=59fd0781664149b081a9d5cf54f3ef1a --binary-syntax --close-
stderr': Child process killed by signal 57

(process:7286): dconf-WARNING **: failed to commit changes to dconf:
Error spawning command line 'dbus-launch
--autolaunch=59fd0781664149b081a9d5cf54f3ef1a --binary-syntax --close-
stderr': Child process killed by signal 57

(process:7286): dconf-WARNING **: failed to commit changes to dconf:
Error spawning command line 'dbus-launch
--autolaunch=59fd0781664149b081a9d5cf54f3ef1a --binary-syntax --close-
stderr': Child process killed by signal 57

(process:7286): dconf-WARNING **: failed to commit changes to dconf:
Error spawning command line 'dbus-launch
--autolaunch=59fd0781664149b081a9d5cf54f3ef1a --binary-syntax --close-
stderr': Child process killed by signal 57

(process:7286): dconf-WARNING **: failed to commit changes to dconf:
Error spawning command line 'dbus-launch
--autolaunch=59fd0781664149b081a9d5cf54f3ef1a --binary-syntax --close-
stderr': Child process killed by signal 57

(process:7286): dconf-WARNING **: failed to commit changes to dconf:
Error spawning command line 'dbus-launch
--autolaunch=59fd0781664149b081a9d5cf54f3ef1a --binary-syntax --close-
stderr': Child process killed by signal 57

(process:7286): dconf-WARNING **: failed to commit changes to dconf:
Error spawning command line 'dbus-launch
--autolaunch=59fd0781664149b081a9d5cf54f3ef1a --binary-syntax --close-
stderr': Child process killed by signal 57

(process:7286): dconf-WARNING **: failed to commit changes to dconf:
Error spawning command line 'dbus-launch
--autolaunch=59fd0781664149b081a9d5cf54f3ef1a --binary-syntax --close-
stderr': Child process killed by signal 57

(process:7286): dconf-WARNING **: failed to commit changes to dconf:
Error spawning command line 'dbus-launch
--autolaunch=59fd0781664149b081a9d5cf54f3ef1a --binary-syntax --close-
stderr': Child process killed by signal 57

(process:7286): dconf-WARNING **: failed to commit changes to dconf:
Error spawning command line 'dbus-launch
--autolaunch=59fd0781664149b081a9d5cf54f3ef1a --binary-syntax --close-
stderr': Child process killed by signal 57

(process:7286): dconf-WARNING **: failed to commit changes to dconf:
Error spawning command line 'dbus-launch
--autolaunch=59fd0781664149b081a9d5cf54f3ef1a --binary-syntax --close-
stderr': Child process killed by signal 57

(process:7286): dconf-WARNING **: failed to commit changes to dconf:
Error spawning command line 'dbus-launch

[Touch-packages] [Bug 1497002] Re: Recent Wily i386 live DVDs load with no launcher, top bar, desktop icons, etc.

[Max Brustkern]

I also tried on a variety of qemu graphics drivers, with roughly the
same outcome each time. Sometimes the ubiquity icon or part of the
ubiquity icon appears.

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

Title:
  Recent Wily i386 live DVDs load with no launcher, top bar, desktop
  icons, etc.

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Recent Wily i386 live DVD images running in qemu should the background
  and a cursor, which moves as expected, but no launcher, desktop icons,
  top bar, etc. amd64 images do not show this issue. I am attempting to
  reproduce the issue on physical hardware.

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

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

[Touch-packages] [Bug 1497002] Re: Recent Wily i386 live DVDs load with no launcher, top bar, desktop icons, etc.

[Max Brustkern]

compiz is not running. What else can I check?

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

Title:
  Recent Wily i386 live DVDs load with no launcher, top bar, desktop
  icons, etc.

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Recent Wily i386 live DVD images running in qemu should the background
  and a cursor, which moves as expected, but no launcher, desktop icons,
  top bar, etc. amd64 images do not show this issue. I am attempting to
  reproduce the issue on physical hardware.

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

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

[Touch-packages] [Bug 1475523] Re: frequent unity8 crashes during power tests

[Max Brustkern]

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

I can update my jobs to make sure I'm saving those files and get back to
you. Selene, can you see the spinning circle of friends when it crashes?

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

Title:
  frequent unity8 crashes during power tests

Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8 crashes fairly often while running power usage tests.  I don't
  know what causes it, but I've collected a lot of data during the test
  runs and I hope someone will be able to make sense of the crash dumps
  and other logs.

  Here are some of the 162 instances I've seen so far...  inside each
  are numbered directories for each test run, and the crash dumps are
  inside of those under var-crash/ .

  Arale rc-proposed 61, runs 3 and 4:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-16_18:21:18-arale-61-power_usage_display_on/

  Arale devel-proposed 61, runs 1, 2, and 5:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-16_21:58:20-arale-61-power_usage_idle/

  Krillin rc-proposed 65, runs 2 and 7:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/

  Krillin devel-proposed, runs 1 and 7:
  
http://people.canonical.com/~platform-qa/power-results/2015-07-13_22:02:04-krillin-132-power_usage_display_on/

  These are merely samples from recent test runs.  I've been seeing the
  crashes regularly ever since I started tracking crash dump files on
  July 3.

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

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

[Touch-packages] [Bug 1435871] Re: Only clock shows after reboot

[Max Brustkern]

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


** Attachment added: ps auxw
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1435871/+attachment/4354511/+files/ps

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

Title:
  Only clock shows after reboot

Status in unity8 package in Ubuntu:
  New

Bug description:
  Sometimes when I reboot my device, I see a darkened screen with only
  the clock visible, and no interaction seems to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity (not installed)
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: armhf
  Date: Tue Mar 24 13:57:01 2015
  InstallationDate: Installed on 2015-03-24 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150324-020203)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1435871] Re: Only clock shows after reboot

[Max Brustkern]

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


** Attachment added: syslog
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1435871/+attachment/4354509/+files/syslog

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

Title:
  Only clock shows after reboot

Status in unity8 package in Ubuntu:
  New

Bug description:
  Sometimes when I reboot my device, I see a darkened screen with only
  the clock visible, and no interaction seems to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity (not installed)
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: armhf
  Date: Tue Mar 24 13:57:01 2015
  InstallationDate: Installed on 2015-03-24 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150324-020203)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1435871] [NEW] Only clock shows after reboot

[Max Brustkern]

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

Public bug reported:

Sometimes when I reboot my device, I see a darkened screen with only the
clock visible, and no interaction seems to work.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity (not installed)
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.16.2-0ubuntu4
Architecture: armhf
Date: Tue Mar 24 13:57:01 2015
InstallationDate: Installed on 2015-03-24 (0 days ago)
InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150324-020203)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf vivid

** Attachment added: /home/phablet/.cache/upstart
   
https://bugs.launchpad.net/bugs/1435871/+attachment/4354506/+files/upstart.tgz

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

Title:
  Only clock shows after reboot

Status in unity8 package in Ubuntu:
  New

Bug description:
  Sometimes when I reboot my device, I see a darkened screen with only
  the clock visible, and no interaction seems to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity (not installed)
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: armhf
  Date: Tue Mar 24 13:57:01 2015
  InstallationDate: Installed on 2015-03-24 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150324-020203)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1377332] Re: [TOPBLOCKER] UI randomly freezes

[Max Brustkern]

Here's a stacktrace from a mako.

** Attachment added: gdb.txt
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377332/+attachment/4263969/+files/gdb.txt

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

Title:
  [TOPBLOCKER] UI randomly freezes

Status in “cgmanager” package in Ubuntu:
  Incomplete
Status in “ubuntu-app-launch” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Opinion
Status in “ubuntu-app-launch” package in Ubuntu RTM:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Opinion

Bug description:
  Summary
  UI randomly freezes

  steps:
  1. unlock greeter
  2. open app
  3. pull down random indicator
  4. close indicator
  5. open app
  6. swipe to view all open apps
  7. open launcher
  8. close some open apps
  9. repeat until ui freezes

  device info:
  [service]
  base: system-image.ubuntu.com
  http_port: 80
  https_port: 443
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  device: krillin
  build_number: 79
  version_detail: 
ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79

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

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

[Touch-packages] [Bug 1377332] Re: [TOPBLOCKER] UI randomly freezes

[Max Brustkern]

The mako stracktrace is from build 25 devel-proposed build 25.

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

Title:
  [TOPBLOCKER] UI randomly freezes

Status in “cgmanager” package in Ubuntu:
  Incomplete
Status in “ubuntu-app-launch” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Opinion
Status in “ubuntu-app-launch” package in Ubuntu RTM:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Opinion

Bug description:
  Summary
  UI randomly freezes

  steps:
  1. unlock greeter
  2. open app
  3. pull down random indicator
  4. close indicator
  5. open app
  6. swipe to view all open apps
  7. open launcher
  8. close some open apps
  9. repeat until ui freezes

  device info:
  [service]
  base: system-image.ubuntu.com
  http_port: 80
  https_port: 443
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  device: krillin
  build_number: 79
  version_detail: 
ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79

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

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

[Touch-packages] [Bug 1391283] [NEW] ubuntu-device-flash 0.4+15.04.20141104.1-0ubuntu1 frequently leaves makos with adb off

[Max Brustkern]

Public bug reported:

I have been repeatedly running this command on a couple of makos in the 
bootloader:
sudo ubuntu-device-flash touch --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed 
--developer-mode --serial=$ANDROID_SERIAL --password=1234 --wipe --bootstrap
On version 0.4+14.10.20141002-0ubuntu1, it generally works as expected.  On 
version 0.4+15.04.20141104.1-0ubuntu1, it usually boots to the welcome screen 
without adb running, requiring manual intervention to get the device running 
again.

** Affects: android-tools (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  ubuntu-device-flash 0.4+15.04.20141104.1-0ubuntu1 frequently leaves
  makos with adb off

Status in “android-tools” package in Ubuntu:
  New

Bug description:
  I have been repeatedly running this command on a couple of makos in the 
bootloader:
  sudo ubuntu-device-flash touch 
--channel=ubuntu-touch/ubuntu-rtm/14.09-proposed --developer-mode 
--serial=$ANDROID_SERIAL --password=1234 --wipe --bootstrap
  On version 0.4+14.10.20141002-0ubuntu1, it generally works as expected.  On 
version 0.4+15.04.20141104.1-0ubuntu1, it usually boots to the welcome screen 
without adb running, requiring manual intervention to get the device running 
again.

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

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

[Touch-packages] [Bug 1391283] Re: ubuntu-device-flash 0.4+15.04.20141104.1-0ubuntu1 frequently leaves makos with adb off

[Max Brustkern]

Cool, thanks.  I'll have to check when that lands on mako.

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

Title:
  ubuntu-device-flash 0.4+15.04.20141104.1-0ubuntu1 frequently leaves
  makos with adb off

Status in “android-tools” package in Ubuntu:
  New

Bug description:
  I have been repeatedly running this command on a couple of makos in the 
bootloader:
  sudo ubuntu-device-flash touch 
--channel=ubuntu-touch/ubuntu-rtm/14.09-proposed --developer-mode 
--serial=$ANDROID_SERIAL --password=1234 --wipe --bootstrap
  On version 0.4+14.10.20141002-0ubuntu1, it generally works as expected.  On 
version 0.4+15.04.20141104.1-0ubuntu1, it usually boots to the welcome screen 
without adb running, requiring manual intervention to get the device running 
again.

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

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

Re: [Touch-packages] [Bug 1361836] Re: Cannot click on anything

[Max Brustkern]

I tried using xfce, and that worked, but crashed a lot.  I created a
different user, and that seems to work.  Removing most of my .files in the
home directory on my original user didn't seem to help.

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

Title:
  Cannot click on anything

Status in Unity:
  New
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  When I start a unity 7 session in utopic, the system switches to my
  previously defined configuration for external monitors, then stops
  accepting input.  I can move the mouse across both displays, but I
  cannot click on anything, and keyboard shortcuts don't seem to bring
  up anything either.  Sometimes the cursor changes to the hand or the
  arrow for resizing a window, and sometimes if I click I get the
  spinning cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20140811-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
  Uname: Linux 3.16.0-10-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: XFCE
  Date: Tue Aug 26 15:31:02 2014
  InstallationDate: Installed on 2013-05-31 (452 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to utopic on 2014-02-18 (189 days ago)

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

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

[Touch-packages] [Bug 1378847] Re: Top Crasher: /usr/bin/autopilot3:TypeError:/usr/bin/autopilot3@9:main:run:run_tests:run:__call__:run:run:run:run:_run_one:_run_prepared_result:_report_failure:addFai

[Max Brustkern]

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

** This bug has been marked a duplicate of bug 1377169
   Top Crasher: 
/usr/bin/autopilot3:TypeError:/usr/bin/autopilot3@9:main:run:run_tests:run:__call__:run:run:run:_run_one:_run_prepared_result:_report_failure:addFailure:addFailure:addFailure:addError:_convert:status:status:_gather_test:_fail:_details_to_str:as_text:_iter_text:decode

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

Title:
  Top Crasher:
  
/usr/bin/autopilot3:TypeError:/usr/bin/autopilot3@9:main:run:run_tests:run:__call__:run:run:run:run:_run_one:_run_prepared_result:_report_failure:addFailure:addFailure:addFailure:addError:_convert:status:status:_gather_test:_fail:_details_to_str:as_text:_iter_text:decode

Status in “autopilot” package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding autopilot.  This problem was most recently seen with version
  1.5.0+14.10.20140812-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/c9740169500491679aa83ec1dd221ac7611e6213
  contains more details.

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

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

[Touch-packages] [Bug 1377169] Re: Top Crasher: /usr/bin/autopilot3:TypeError:/usr/bin/autopilot3@9:main:run:run_tests:run:__call__:run:run:run:_run_one:_run_prepared_result:_report_failure:addFailure

[Max Brustkern]

This bug and
https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1378847 are
both cases where Content objects are created with strict validation to
ensure that an appropriate callback returning a bytes object is coming
from.  Thomi is working on an update to testtools to allow us to locate
the problem.

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

Title:
  Top Crasher:
  
/usr/bin/autopilot3:TypeError:/usr/bin/autopilot3@9:main:run:run_tests:run:__call__:run:run:run:_run_one:_run_prepared_result:_report_failure:addFailure:addFailure:addFailure:addError:_convert:status:status:_gather_test:_fail:_details_to_str:as_text:_iter_text:decode

Status in “autopilot” package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding autopilot.  This problem was most recently seen with version
  1.5.0+14.10.20140812-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/f293befd9513bb3f7a21b730cf9026f38d43e8e1
  contains more details.

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

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

[Touch-packages] [Bug 1361825] [NEW] package click-apparmor 0.2.9 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Max Brustkern]

Public bug reported:

Got this when I started an xubuntu session on utopic.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: click-apparmor 0.2.9
ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
Uname: Linux 3.16.0-10-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
Date: Mon Aug 25 11:20:50 2014
DuplicateSignature: package:click-apparmor:0.2.9:subprocess new pre-removal 
script returned error exit status 1
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2013-05-31 (452 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
SourcePackage: click-apparmor
SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli'
Title: package click-apparmor 0.2.9 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
UpgradeStatus: Upgraded to utopic on 2014-02-18 (189 days ago)

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


** Tags: amd64 apport-package utopic

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

Title:
  package click-apparmor 0.2.9 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in “click-apparmor” package in Ubuntu:
  New

Bug description:
  Got this when I started an xubuntu session on utopic.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: click-apparmor 0.2.9
  ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
  Uname: Linux 3.16.0-10-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  Date: Mon Aug 25 11:20:50 2014
  DuplicateSignature: package:click-apparmor:0.2.9:subprocess new pre-removal 
script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2013-05-31 (452 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: click-apparmor
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  Title: package click-apparmor 0.2.9 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to utopic on 2014-02-18 (189 days ago)

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

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

[Touch-packages] [Bug 1361836] [NEW] Cannot click on anything

[Max Brustkern]

Public bug reported:

When I start a unity 7 session in utopic, the system switches to my
previously defined configuration for external monitors, then stops
accepting input.  I can move the mouse across both displays, but I
cannot click on anything, and keyboard shortcuts don't seem to bring up
anything either.  Sometimes the cursor changes to the hand or the arrow
for resizing a window, and sometimes if I click I get the spinning
cursor.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: unity 7.3.1+14.10.20140811-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
Uname: Linux 3.16.0-10-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: XFCE
Date: Tue Aug 26 15:31:02 2014
InstallationDate: Installed on 2013-05-31 (452 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
SourcePackage: unity
SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli'
UpgradeStatus: Upgraded to utopic on 2014-02-18 (189 days ago)

** Affects: unity (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 unity in Ubuntu.
https://bugs.launchpad.net/bugs/1361836

Title:
  Cannot click on anything

Status in “unity” package in Ubuntu:
  New

Bug description:
  When I start a unity 7 session in utopic, the system switches to my
  previously defined configuration for external monitors, then stops
  accepting input.  I can move the mouse across both displays, but I
  cannot click on anything, and keyboard shortcuts don't seem to bring
  up anything either.  Sometimes the cursor changes to the hand or the
  arrow for resizing a window, and sometimes if I click I get the
  spinning cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20140811-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
  Uname: Linux 3.16.0-10-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: XFCE
  Date: Tue Aug 26 15:31:02 2014
  InstallationDate: Installed on 2013-05-31 (452 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to utopic on 2014-02-18 (189 days ago)

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

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