date:20160602

** Changed in: desktop-file-utils (Ubuntu Xenial)
   Importance: Undecided => Wishlist

** Changed in: desktop-file-utils (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: gnome-software (Ubuntu Xenial)
   Importance: Undecided => Wishlist

** Changed in: gnome-software (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: desktop-file-utils (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: gnome-software (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Support squashfs / .snap packages

Status in File Roller:
  Confirmed
Status in shared-mime-info:
  Unknown
Status in desktop-file-utils package in Ubuntu:
  Fix Committed
Status in file-roller package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in shared-mime-info package in Ubuntu:
  Fix Released
Status in desktop-file-utils source package in Xenial:
  Triaged
Status in file-roller source package in Xenial:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in shared-mime-info source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  There is no registered MIME types for sqhuashfs/snap files. Thus nothing 
knows how to open them. You cannot browse the contents in file-roller.

  [Test Case]
  1. Download/make a .snap
  2. Run 'gnome-open NAME.snap' or click on it in Nautilus

  Expected result:
  The snap is opened in an appropriate program (file-roller and/or GNOME 
Software).

  Observed result:
  The file cannot be opened.

  [Regression Potential]
  Low. This change registers two new MIME types and adds new functionality to 
file-roller. Existing behaviours should be unchanged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1585867/+subscriptions

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

[Touch-packages] [Bug 1574429] Re: keyboard suggestion

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

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

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

Title:
   keyboard suggestion

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  The touch keyboard could do with:
  * a tab key, to make it easier to move to the next field on forms
  * a right hand shift key
  * keys for copy/paste
  * arrow keys to move the insertion point.  shiftlock-arrow to make selection 
highlight.

  You can file these under 'wishlist' & 'accessibility'  -the little
  blue insertion point handle is too fiddly for someone with Parkinsons
  or poor eyesight, for example.

  That said the phone/tablet keyboard is far better than stock IOS if
  you have shakey hands.  Still keep presssing p for backspace, mind.

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

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

[Touch-packages] [Bug 1585867] Re: Support squashfs / .snap packages

** Also affects: gnome-software (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: desktop-file-utils (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: desktop-file-utils (Ubuntu)
   Importance: Undecided => Medium

** Changed in: desktop-file-utils (Ubuntu)
   Status: New => Triaged

** Changed in: desktop-file-utils (Ubuntu)
   Importance: Medium => Wishlist

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: gnome-software (Ubuntu)
   Status: New => Triaged

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

Title:
  Support squashfs / .snap packages

Status in File Roller:
  Confirmed
Status in shared-mime-info:
  Unknown
Status in desktop-file-utils package in Ubuntu:
  Triaged
Status in file-roller package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Triaged
Status in shared-mime-info package in Ubuntu:
  Fix Released
Status in desktop-file-utils source package in Xenial:
  New
Status in file-roller source package in Xenial:
  Fix Committed
Status in gnome-software source package in Xenial:
  New
Status in shared-mime-info source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  There is no registered MIME types for sqhuashfs/snap files. Thus nothing 
knows how to open them. You cannot browse the contents in file-roller.

  [Test Case]
  1. Download/make a .snap
  2. Run 'gnome-open NAME.snap' or click on it in Nautilus

  Expected result:
  The snap is opened in an appropriate program (file-roller and/or GNOME 
Software).

  Observed result:
  The file cannot be opened.

  [Regression Potential]
  Low. This change registers two new MIME types and adds new functionality to 
file-roller. Existing behaviours should be unchanged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1585867/+subscriptions

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

[Touch-packages] [Bug 1577795] Re: Ubuntu touch Frieza ota-10.1 dropping connection to logitech k810

2016-06-02 Thread Paul Spain

I have just updated my M10 to Ubuntu 15.04 OTA-11 and the bug remains:
* I can connect my logitech k810 keyboard and it works ok
* As soon as I connect the Ultrathin mouse, I lose the keyboard, but the mouse 
works fine.
* As soon as I disconnect the mouse, the keyboard works again.

I am happy to provide more diagnostics if somebody would please advise
on what and how I should collect.

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

Title:
  Ubuntu touch Frieza ota-10.1 dropping connection to logitech k810

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I can successfully pair the k810 to my BQ Aquaris M10 FHD tablet.
  The connection state flips every few seconds between connected and 
disconected and the signal strength between excellent and none.
  I have tried forgetting the connection and repairing, and power-cycling then 
repeating the process, to no avail.
  Both the tablet and keyboard have a full charge.
  I have successfully paired and am using a Logitech Ultrathin mouse with the 
tablet.
  I have succesfully paired and use the k810 keyboard with several Android 
devices across multiple versions of Android.
  I have also paired and use the keyboard with Ubuntu 14.04 LTS.

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

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

[Touch-packages] [Bug 1588594] Re: mountall: potential problem with fuse.ceph

2016-06-02 Thread Francois Lafont

In fact, the problem is not really embarassing in Ubuntu Xenial because
mountall is not used by default to mount the filesystems from fstab.
But, for instance, it's really embarassing in Ubuntu Trusty because:

1. the problem is present in Ubuntu Trusty too (the code C is the same on this 
part),
2. by default, mountall is used in Ubuntu Trusty to mount the file system from 
fstab at boot.


PS: of course, a workaround possible is to _not_ put "client_mountpoint=/" at 
the end like in:

id=cfs,client_mountpoint=/,keyring=/etc/ceph/keyring /mnt/ fuse.ceph
defaults,_netdev 0 0

which is a valid fstab line too.

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

Title:
  mountall: potential problem with fuse.ceph

Status in mountall package in Ubuntu:
  New

Bug description:
  Hi,

  Here is a perfectly valid fstab line to mount a fuse.ceph filesystem
  (it's a distributed file system but no importance here):

  id=cfs,keyring=/etc/ceph/keyring,client_mountpoint=/ /mnt/
  fuse.ceph defaults,_netdev   0   0

  But here are the arguments given to /sbin/mount.fuse.ceph by mountall:

  id=cfs,keyring=/etc/ceph/keyring,client_mountpoint= /mnt -o
  rw,_netdev

  As you can see, I have "client_mountpoint=" but it should be
  "client_mountpoint=/" (with the / at the end). The trailing "/" has
  been removed and in this case it's a bad idea. The mount at boot just
  fails because "client_mountpoint=" is not correct.

  In fact, the problem is in src/mountall.c around line 569:

  char *colon;
  dequote (mnt->device);
  /* If our device name is in host:/path format, as is
   * commonly used for network filesystems, don't strip
   * trailing slashes if this is the entire path.  We
   * look for the colon starting from the end, so that
   * we correctly handle IPv6 addresses for the host
   * part.
   */
  if ((colon = strrchr (mnt->device,':')) != NULL
  && colon[1] == '/')
  strip_slashes (colon + 2);
  else
  strip_slashes (mnt->device);  // < bad idea in the specific case 
of fuse.ceph filesystem

  
  It's Ubuntu Xenial with mountall version 2.54ubuntu1.

  Regards

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

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

[Touch-packages] [Bug 1588598] [NEW] Unit tests are not executed

2016-06-02 Thread Zoltan Balogh

Public bug reported:

Due to a recent change in the debian/rules file the tests got accidentally 
skipped on all but the latest series.
The bug can be fixed with a simple s/ifneq/ifeq/ change.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Critical
 Assignee: Zoltan Balogh (bzoltan)
 Status: Confirmed

** Branch linked: lp:~bzoltan/ubuntu-ui-
toolkit/ifeq_is_better_than_ifneq

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

Title:
  Unit tests are not executed

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

Bug description:
  Due to a recent change in the debian/rules file the tests got accidentally 
skipped on all but the latest series.
  The bug can be fixed with a simple s/ifneq/ifeq/ change.

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

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

[Touch-packages] [Bug 1588597] [NEW] Some ads permanetly block webpages, even unrelated pages.

2016-06-02 Thread W Mauldin

Public bug reported:

This is a strange intermittent problem. It seems that full page, or
perhaps page covering ads on web pages will not only block the web page
underneath in opaque black, but block everything in the browser. This
includes other web pages and hitting the back button to escape the
screen. When this happens, there will also be slim white rectangles on
the right-side edge of the screen when scrolling. Screenshots are
attached.

http://imgur.com/a/yLWGj

I'm using a Meizu Pro 5 (turbo) OTA 11 from the stable "meizu.en"
channel. I can attest that this same behavior appeared in OTA 10.2 as
well.

EXPECTATIONS:
1 - When an ad or other element blocks the web page, I expect to be able to 
close or hide it.
2 - If I go back a page, I expect the element to be stop blocking the webpages.

REALITY:
A - They are unclosable.
B - Even hitting back or navigating to a different web page doesn't make the 
black overlay disappear.

webbrowser app is 0.23+15.04.20160509.3-0ubuntu1

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

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

Title:
  Some ads permanetly block webpages, even unrelated pages.

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  This is a strange intermittent problem. It seems that full page, or
  perhaps page covering ads on web pages will not only block the web
  page underneath in opaque black, but block everything in the browser.
  This includes other web pages and hitting the back button to escape
  the screen. When this happens, there will also be slim white
  rectangles on the right-side edge of the screen when scrolling.
  Screenshots are attached.

  http://imgur.com/a/yLWGj

  I'm using a Meizu Pro 5 (turbo) OTA 11 from the stable "meizu.en"
  channel. I can attest that this same behavior appeared in OTA 10.2 as
  well.

  EXPECTATIONS:
  1 - When an ad or other element blocks the web page, I expect to be able to 
close or hide it.
  2 - If I go back a page, I expect the element to be stop blocking the 
webpages.

  REALITY:
  A - They are unclosable.
  B - Even hitting back or navigating to a different web page doesn't make the 
black overlay disappear.

  webbrowser app is 0.23+15.04.20160509.3-0ubuntu1

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

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

[Touch-packages] [Bug 1585867] Re: Support squashfs / .snap packages

** Changed in: file-roller (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Changed in: shared-mime-info (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

Title:
  Support squashfs / .snap packages

Status in File Roller:
  Confirmed
Status in shared-mime-info:
  Unknown
Status in file-roller package in Ubuntu:
  Fix Released
Status in shared-mime-info package in Ubuntu:
  Fix Released
Status in file-roller source package in Xenial:
  Fix Committed
Status in shared-mime-info source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  There is no registered MIME types for sqhuashfs/snap files. Thus nothing 
knows how to open them. You cannot browse the contents in file-roller.

  [Test Case]
  1. Download/make a .snap
  2. Run 'gnome-open NAME.snap' or click on it in Nautilus

  Expected result:
  The snap is opened in an appropriate program (file-roller and/or GNOME 
Software).

  Observed result:
  The file cannot be opened.

  [Regression Potential]
  Low. This change registers two new MIME types and adds new functionality to 
file-roller. Existing behaviours should be unchanged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1585867/+subscriptions

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

[Touch-packages] [Bug 1588596] [NEW] package libc6-dev-i386 (not installed) failed to install/upgrade: trying to overwrite '/usr/include/bits', which is also in package libc6-dev-amd64 2.19-0ubuntu6.9

2016-06-02 Thread Mario

Public bug reported:

$ lsb_release -a
LSB Version:
core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
Distributor ID: Ubuntu
Description:Ubuntu 14.04.4 LTS
Release:14.04
Codename:   trusty


$ sudo apt-cache policy
Package files:
 100 /var/lib/dpkg/status
 release a=now
 500 https://deb.opera.com/opera-stable/ stable/non-free i386 Packages
 release o=Opera Software ASA,a=stable,n=stable,l=The Opera web 
browser,c=non-free
 origin deb.opera.com
 500 https://deb.opera.com/opera-stable/ stable/non-free amd64 Packages
 release o=Opera Software ASA,a=stable,n=stable,l=The Opera web 
browser,c=non-free
 origin deb.opera.com
 500 http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages
 release v=1.0,o=Google, Inc.,a=stable,n=stable,l=Google,c=main
 origin dl.google.com
 500 https://apt.dockerproject.org/repo/ ubuntu-trusty/main i386 Packages
 release o=Docker,a=ubuntu-trusty,n=ubuntu-trusty,l=Docker APT 
Repository,c=main
 origin apt.dockerproject.org
 500 https://apt.dockerproject.org/repo/ ubuntu-trusty/main amd64 Packages
 release o=Docker,a=ubuntu-trusty,n=ubuntu-trusty,l=Docker APT 
Repository,c=main
 origin apt.dockerproject.org
 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/universe Translation-en
 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/restricted Translation-en
 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main Translation-en
 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/universe i386 Packages
 release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=universe
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/restricted i386 Packages
 release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=restricted
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages
 release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=main
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages
 release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=universe
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/restricted amd64 Packages
 release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=restricted
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
 release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=main
 origin archive.ubuntu.com
 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe Translation-en
 500 http://security.ubuntu.com/ubuntu/ trusty-security/restricted 
Translation-en
 500 http://security.ubuntu.com/ubuntu/ trusty-security/main Translation-en
 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe i386 Packages
 release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=universe
 origin security.ubuntu.com
 500 http://security.ubuntu.com/ubuntu/ trusty-security/restricted i386 Packages
 release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=restricted
 origin security.ubuntu.com
 500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 Packages
 release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=main
 origin security.ubuntu.com
 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 Packages
 release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=universe
 origin security.ubuntu.com
 500 http://security.ubuntu.com/ubuntu/ trusty-security/restricted amd64 
Packages
 release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=restricted
 origin security.ubuntu.com
 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
 release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=main
 origin security.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu/ trusty/universe Translation-en
 500 http://archive.ubuntu.com/ubuntu/ trusty/restricted Translation-en
 500 http://archive.ubuntu.com/ubuntu/ trusty/main Translation-en
 500 http://archive.ubuntu.com/ubuntu/ trusty/restricted i386 Packages
 release v=14.04,o=Ubuntu,a=trusty,n=trusty,l=Ubuntu,c=restricted
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages
 release v=14.04,o=Ubuntu,a=trusty,n=trusty,l=Ubuntu,c=universe
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
 release v=14.04,o=Ubuntu,a=trusty,n=trusty,l=Ubuntu,c=main
 origin archive.ubuntu.com
 500 http://archive.ubuntu.com/ubuntu/ trusty/restricted amd64 Packages
 release

[Touch-packages] [Bug 1574347] Re: [SRU] Re-read the link type if the name changed

2016-06-02 Thread Cip Man

Actually, this bug, WAS a different issue until you (plus Aron Xu and
others) changed the title, description, [wrongly] marked this and other
bugs as duplicate, changed the testcase, you name it. Look at the
original description in the activity log of this bug at 2016-05-12
08:41:52 change.

File my own bug?! I was the 1st to confirm this bug the same day OP
filed it 5 weeks ago, look at #3. What would I do it again for?!

Practically, this is now a bug that was "fixed" to match a released NM
version.

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

Title:
  [SRU] Re-read the link type if the name changed

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

  ---

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

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

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

[Touch-packages] [Bug 1579130] Re: need to support renaming of devices in container and on first boot

2016-06-02 Thread Scott Moser

I have fixes for this in cloud-init in my branch at 
https://launchpad.net/~smoser/+archive/ubuntu/cloud-init-dev/+packages
that is available in the ppa at 
https://launchpad.net/~smoser/+archive/ubuntu/cloud-init-dev/+packages

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

Title:
  need to support renaming of devices in container and on first boot

Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  We're interested in supporting network configuration of cloud
  instances including lxc containers via maas/cloud-init yaml format.

  For Containers, the end goal is to do:
  $ lxc init xenial x1
  $ ncpath=/var/lib/cloud/seed/nocloud-net/network-config
  $ sudo tee /var/lib/lxd/containers/x1/rootfs/$ncpath < 
into 'eth0').
   That is implemented by check of 
/sys/devices/virtual/net/eth0/name_assign_type . Value of 4 means renamed.

   c.) systemd.link will not attempt to rename a device that does not have a 
driver.
     To see that run: udevadm test-builtin net_setup_link /sys/class/net/eth0
     http://paste.ubuntu.com/16261974/

   d.) on first boot of a cloud instance, the systemd.link files in the
  initramfs are either pristine or from the previous instance.  The
  devices will leave the initramfs either named incorrectly or named
  with standard persistent naming and will have already been renamed.

  To force these systemd.link files to run in spite of 'b' on kvm guests
  or bare metal, we have found that unbind and rebind of the device will
  clear the state and rename would occur.  that can be done as shown in
  https://bugs.launchpad.net/ubuntu/+source/cloud-
  init/+bug/1577844/comments/3 but since there is no 'driver' we cannot
  unbind and rebind veth devices.

  To do this right, we need to support:
   1.) renaming on first boot with initramfs and with 'stale' initramfs
   2.) renaming in lxc containers
   3.) user updating whatever files or mechanism is used post first boot.  For 
example, if the user wrote a 25-my-rules.link after first boot, a reboot should 
prefer their provided names to whatever were originally there.
   4.) if cloud-init networking is disabled, the renaming should not occur.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu4
  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
  Date: Fri May  6 15:42:52 2016
  MachineType: LENOVO 33672B7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=19ac97d5-6973-4193-9a09-2e6bbfa38262 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G8ET96WW (2.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 33672B7
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG8ET96WW(2.56):bd12/18/2013:svnLENOVO:pn33672B7:pvrThinkPadX131e:rvnLENOVO:rn33672B7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 33672B7
  dmi.product.version: ThinkPad X131e
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1588594] [NEW] mountall: potential problem with fuse.ceph

2016-06-02 Thread Francois Lafont

Public bug reported:

Hi,

Here is a perfectly valid fstab line to mount a fuse.ceph filesystem
(it's a distributed file system but no importance here):

id=cfs,keyring=/etc/ceph/keyring,client_mountpoint=/ /mnt/ fuse.ceph
defaults,_netdev   0   0

But here are the arguments given to /sbin/mount.fuse.ceph by mountall:

id=cfs,keyring=/etc/ceph/keyring,client_mountpoint= /mnt -o
rw,_netdev

As you can see, I have "client_mountpoint=" but it should be
"client_mountpoint=/" (with the / at the end). The trailing "/" has been
removed and in this case it's a bad idea. The mount at boot just fails
because "client_mountpoint=" is not correct.

In fact, the problem is in src/mountall.c around line 569:

char *colon;
dequote (mnt->device);
/* If our device name is in host:/path format, as is
 * commonly used for network filesystems, don't strip
 * trailing slashes if this is the entire path.  We
 * look for the colon starting from the end, so that
 * we correctly handle IPv6 addresses for the host
 * part.
 */
if ((colon = strrchr (mnt->device,':')) != NULL
&& colon[1] == '/')
strip_slashes (colon + 2);
else
strip_slashes (mnt->device);  // < bad idea in the specific case of 
fuse.ceph filesystem


It's Ubuntu Xenial with mountall version 2.54ubuntu1.

Regards

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

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

Title:
  mountall: potential problem with fuse.ceph

Status in mountall package in Ubuntu:
  New

Bug description:
  Hi,

  Here is a perfectly valid fstab line to mount a fuse.ceph filesystem
  (it's a distributed file system but no importance here):

  id=cfs,keyring=/etc/ceph/keyring,client_mountpoint=/ /mnt/
  fuse.ceph defaults,_netdev   0   0

  But here are the arguments given to /sbin/mount.fuse.ceph by mountall:

  id=cfs,keyring=/etc/ceph/keyring,client_mountpoint= /mnt -o
  rw,_netdev

  As you can see, I have "client_mountpoint=" but it should be
  "client_mountpoint=/" (with the / at the end). The trailing "/" has
  been removed and in this case it's a bad idea. The mount at boot just
  fails because "client_mountpoint=" is not correct.

  In fact, the problem is in src/mountall.c around line 569:

  char *colon;
  dequote (mnt->device);
  /* If our device name is in host:/path format, as is
   * commonly used for network filesystems, don't strip
   * trailing slashes if this is the entire path.  We
   * look for the colon starting from the end, so that
   * we correctly handle IPv6 addresses for the host
   * part.
   */
  if ((colon = strrchr (mnt->device,':')) != NULL
  && colon[1] == '/')
  strip_slashes (colon + 2);
  else
  strip_slashes (mnt->device);  // < bad idea in the specific case 
of fuse.ceph filesystem

  
  It's Ubuntu Xenial with mountall version 2.54ubuntu1.

  Regards

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

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

[Touch-packages] [Bug 1565245] Re: package dbus 1.10.6-1ubuntu3 failed to install/upgrade: triggers looping, abandoned

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

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

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

Title:
  package dbus 1.10.6-1ubuntu3 failed to install/upgrade: triggers
  looping, abandoned

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  package dbus 1.10.6-1ubuntu3 failed to install/upgrade: triggers
  looping, abandoned

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Sat Apr  2 17:51:32 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-03-18 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.9
  SourcePackage: dbus
  Title: package dbus 1.10.6-1ubuntu3 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

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

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

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

Title:
  graphic system freezes after a while, can still ssh into machine

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 desktop with all updates up to date
  Gigagyte GA-Z170 motherboard, Intel i7-6700 3.4gHz, 64GB RAM, Samsung 840 
SSD, Gigabyte GEForce GT710 graphics (nvidia chipset)

  Very light load. A few terminal windows, a few Firefox pages,
  Thunderbird, and VirtualBox (with the extension pack loaded) running
  one small Linux VM with 512Mb memory (very lightly loaded as it's only
  running bind9). I think (but don't have perfect certainty on this)
  that some of the crashes have happened without VirtualBox running.
  Also running rsync so that backuppc on a separate machine can back it
  up over the network (backuppc has been a real lifesaver with all the
  reinstallations!)

  After booting the system runs happily for a while then the GUI
  freezes. This can take a few hours or up to a day or two. You can
  still ssh into the system, and if you do "top" it typically shows 100%
  CPU load on systemd-timesync.

  The same happens whether I use nouveau or the proprietary nvidia driver (361)
  I have tried a complete reinstallation (4 times already, starting to get 
quite frustrating) using the proprietary drivers and NOT using the proprietary 
drivers and the same still happens. The most recent time was with nouveau, and 
Xorg.log has a number of entries like this:
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x5652cde325ce]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x5652cde14083]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x5652cdcec662]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x61f3) 
[0x7f31f98621f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x6a5d) 
[0x7f31f9862a5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x5652cdc8+0x94228) [0x5652cdd14228]
  (EE) 6: /usr/lib/xorg/Xorg (0x5652cdc8+0xb96f2) [0x5652cdd396f2]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
  (EE) 8: /usr/lib/xorg/Xorg (GiveUp+0x0) [0x5652cde37330]
  (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
  (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f3202debcf3]
  (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x1d7) [0x5652cde2f307]
  (EE) 12: /usr/lib/xorg/Xorg (0x5652cdc8+0x539ee) [0x5652cdcd39ee]
  (EE) 13: /usr/lib/xorg/Xorg (0x5652cdc8+0x57c33) [0x5652cdcd7c33]
  (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f3202d0f830]
  (EE) 15: /usr/lib/xorg/Xorg (_start+0x29) [0x5652cdcc1f59]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
   
  Then at the end the last few are:

  [  6265.543] [mi] Increasing EQ size to 1024 to prevent dropped events.
  [  6265.543] [mi] EQ processing has resumed after 1070 dropped events.
  [  6265.543] [mi] This may be caused by a misbehaving driver monopolizing the 
server's resources.

  What cna the problem possibly be, especially as 16.04 is meant to be a
  stable release and an Nvidia GT710 card is hardly bleeding-edge? Help
  greatly appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jun  1 13:22:13 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation Device [10de:128b] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:36ec]
  InstallationDate: Installed on 2016-06-01 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. Z170-D3H
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic

Re: [Touch-packages] [Bug 1584348] app blocked after suspend

2016-06-02 Thread Thomas Meyssonnier

Hi,

I just upgraded to OTA-11 and it seems to get worse.
I was surprised so I didn't think to ps|grep at first but here is the unity 
log.

What happened was that Dekko freezed (I think), was still running according 
to Launcher but wouldn't focus if selected and not visible with right 
swipe. I had to kill it with long press in Launcher and then restart.

I'll try to get the right PID next time, but if the misbehaviour shows up 
in unity log it should be within 5mins before the end.

Thanks,
TM

Le mercredi 1 juin 2016 09:32:17 CEST, Michał Sawicz 
 a écrit :
> When anyone encounters this again, please post the output of:
> 
> $ ps aux | grep -i 
> 
> Where app_name is part of the frozen app.
> 
> Please also attach ~/.cache/upstart/unity8.log
> 
> ** Changed in: unity8 (Ubuntu)
>Status: New => Incomplete
> 
> ** Changed in: canonical-devices-system-image
>Status: Confirmed => Incomplete
> 


** Attachment added: "unity8.log"
   https://bugs.launchpad.net/bugs/1584348/+attachment/4675597/+files/unity8.log

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

Title:
  app blocked after suspend

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

Bug description:
  When you let an app opened after a while (about hours) and after that you try 
to work with it the app sometimes does not respond.
  I saw it with a lot of apps (camera, dialer, facebook, telegram, webbrowser...

  Atached you'll find a video where you can see me trying to use camera
  app without any result.

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

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

[Touch-packages] [Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

2016-06-02 Thread Artem

Have the similar issue under lubuntu 16.04. Virtualbox 5.20. i5 GTX 960
Freez in firefox/libreoffice/chromium..
It helps to switch terminals CtrlAlt-F1 and back CtrlAlt-F7

Usaly I killall firefox from CtrlAlt-F1 (terminal alway works)
But today I have just switched to new terminal and back and it helps.

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

Title:
  graphic system freezes after a while, can still ssh into machine

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 desktop with all updates up to date
  Gigagyte GA-Z170 motherboard, Intel i7-6700 3.4gHz, 64GB RAM, Samsung 840 
SSD, Gigabyte GEForce GT710 graphics (nvidia chipset)

  Very light load. A few terminal windows, a few Firefox pages,
  Thunderbird, and VirtualBox (with the extension pack loaded) running
  one small Linux VM with 512Mb memory (very lightly loaded as it's only
  running bind9). I think (but don't have perfect certainty on this)
  that some of the crashes have happened without VirtualBox running.
  Also running rsync so that backuppc on a separate machine can back it
  up over the network (backuppc has been a real lifesaver with all the
  reinstallations!)

  After booting the system runs happily for a while then the GUI
  freezes. This can take a few hours or up to a day or two. You can
  still ssh into the system, and if you do "top" it typically shows 100%
  CPU load on systemd-timesync.

  The same happens whether I use nouveau or the proprietary nvidia driver (361)
  I have tried a complete reinstallation (4 times already, starting to get 
quite frustrating) using the proprietary drivers and NOT using the proprietary 
drivers and the same still happens. The most recent time was with nouveau, and 
Xorg.log has a number of entries like this:
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x5652cde325ce]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x5652cde14083]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x5652cdcec662]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x61f3) 
[0x7f31f98621f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x6a5d) 
[0x7f31f9862a5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x5652cdc8+0x94228) [0x5652cdd14228]
  (EE) 6: /usr/lib/xorg/Xorg (0x5652cdc8+0xb96f2) [0x5652cdd396f2]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
  (EE) 8: /usr/lib/xorg/Xorg (GiveUp+0x0) [0x5652cde37330]
  (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
  (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f3202debcf3]
  (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x1d7) [0x5652cde2f307]
  (EE) 12: /usr/lib/xorg/Xorg (0x5652cdc8+0x539ee) [0x5652cdcd39ee]
  (EE) 13: /usr/lib/xorg/Xorg (0x5652cdc8+0x57c33) [0x5652cdcd7c33]
  (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f3202d0f830]
  (EE) 15: /usr/lib/xorg/Xorg (_start+0x29) [0x5652cdcc1f59]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
   
  Then at the end the last few are:

  [  6265.543] [mi] Increasing EQ size to 1024 to prevent dropped events.
  [  6265.543] [mi] EQ processing has resumed after 1070 dropped events.
  [  6265.543] [mi] This may be caused by a misbehaving driver monopolizing the 
server's resources.

  What cna the problem possibly be, especially as 16.04 is meant to be a
  stable release and an Nvidia GT710 card is hardly bleeding-edge? Help
  greatly appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jun  1 13:22:13 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation Device [10de:128b] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:36ec]
  InstallationDate: Installed on 2016-06-01 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. Z170-D3H

[Touch-packages] [Bug 1573168] Re: [Frieza] Location service fails to start cleanly, entering restart loop - service crashes on start

2016-06-02 Thread Bob Harvey

Seems to be working fine in OTA11.

Well done!

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

Title:
  [Frieza] Location service fails to start cleanly, entering restart
  loop - service crashes on start

Status in The Avila project:
  Fix Committed
Status in Canonical System Image:
  Fix Released
Status in frieza:
  Fix Released
Status in krillin:
  Fix Released
Status in platform-api:
  In Progress
Status in vegetahd:
  Fix Released
Status in location-service package in Ubuntu:
  Invalid

Bug description:
  See http://makeagif.com/i/QlHXU7 for further details.

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

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

[Touch-packages] [Bug 1546733] Re: Update of today screen messes up scopes layout.

2016-06-02 Thread Anupam

just experienced once again, even after updating to OTA-11

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

Title:
  Update of today screen messes up scopes layout.

Status in Today Scope:
  New
Status in unity-scopes-shell package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  BQ4.5, OTA9, official channel.

  Observed the following:
  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1546733/+subscriptions

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

[Touch-packages] [Bug 1588562] Re: Please add ~/.local/bin to the default $PATH

2016-06-02 Thread Bug Watch Updater

** Changed in: bash (Debian)
   Status: Unknown => New

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

Title:
  Please add ~/.local/bin to the default $PATH

Status in bash package in Ubuntu:
  New
Status in bash source package in Xenial:
  New
Status in bash package in Debian:
  New

Bug description:
  Starting in Xenial, 'pip install' by default places executables into
  ~/.local/bin. This is the de-facto standard place to put per-user
  executables -- for example, Fedora/Redhat puts it on the $PATH by
  default, and PEP 370 makes it the standard place for unprivileged
  installs of Python packages to put their scripts.

  But unfortunately, Ubuntu's does *not* add this directory to $PATH by
  default, which means that 'pip install' doesn't actually work -- any
  scripts that are installed are inaccessible, and every user has to
  manually add this to their PATH.

  Ubuntu should put ~/.local/bin onto PATH by default.

  Minor details (discussed with @doko at the PyCon sprints):

  - this should go at the beginning of PATH rather than the end, in accordance 
with Debian policy saying that more-local paths go before more-upstream paths. 
(This is inconsistent with how Fedora/RH do it, but consistent with how Python 
itself searches for packages.)
  - this will be added to /etc/skel/profile, so that it won't change any 
existing user accounts; it will only be applied to user accounts created 
*after* this change lands
  - unlike ~/bin (which Debian/Ubuntu have supported for ages), it will be 
added to PATH unconditionally, even if the directory doesn't exist. This is 
important to avoid a nasty trap for new users, where the first time they try to 
install a Python package they have to restart their shell. Since this only 
applies to new accounts, the directory will always start out nonexistent/empty, 
so having it in $PATH won't cause any unexpected changes in behavior.
  - possibly it would make sense to set this in /etc/environment or 
/etc/skel/.gnomerc or similar, so that it would also apply to non-shell 
processes (e.g. if the user wants to add a global key-binding to launch a 
Python program, then generally ~/.profile *doesn't* affect the environment 
where this command gets executed, and that can frustrate and confuse users if a 
command works fine from the terminal but not from a keybinding). But we should 
defer this discussion for the future, because even if this is a good idea, it 
isn't a good idea in a Xenial stable update.

  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856

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

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

[Touch-packages] [Bug 1588500] Re: Applications with permission for location claim they don't

2016-06-02 Thread Bob Harvey

Tried the metvoffice example in Firefox.. Had to grant 'always'
permission in the dialogue, but then it worked.. Going back to the app
permissions for location I could not find Firefox listed.

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

Title:
  Applications with permission for location claim they don't

Status in location-service package in Ubuntu:
  New

Bug description:
  OTA11 - same problem on BQ4.5phone & M10 tablet.

  Hurray! Location works on the tablet at last.. HERE maps can get a
  position.

  But I can't use the location in the browser or a browser-like web
  app.. It used to work on the phone in OTA10.1

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

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

[Touch-packages] [Bug 1389215] Re: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver.

2016-06-02 Thread Christopher M. Penalver

** Tags removed: needs-vivid-test
** Tags added: xenial

** No longer affects: xorg (Ubuntu)

** Project changed: nvidia => nvidia-graphics-drivers-340 (Ubuntu)

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Brightness controls are not working in Unity / Xorg because of Nvidia
  proprietary driver.

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  Affects: Ubuntu 16.04 and 14.04.
  Occurs only with Nvidia proprietary driver.  Nouveau works well.

  Brightness controls are not working in Unity / Xorg.  When pressing
  the keys  and  on my Lenovo W510, I see the
  indicator on the screen showing the level of brightness changing, so
  key mapping is not the problem.  However, the brightness is not
  changing.

  On the kernel level, I have the single following device:

  # cd /sys/class/backlight
  # ls -l
  total 0
  lrwxrwxrwx 1 root root 0 Nov  3 17:16 acpi_video0 -> 
../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0

  When playing with the  and , the value of
  /sys/class/backlight/brightness changes accordingly.  The screen
  brightness does not change.

  Performing:

  # echo 10 >brightness

  ...does not have any effect (regardless of the value provided, 10
  being just an example).

  WORKAROUND

  There is an odd workaround.  Simply go to the console using
   and using the  and  keys,
  brightness then changes.  Return to Unity / Xorg with 
  and the selected brightness persists.

  NON WORKING WORKAROUND

  On the web, I read that adding:

  Option "RegistryDwords" "EnableBrightnessControl=1"'

  in xorg.conf might fix the problem.  I do not have an xorg and when I
  let the proprietary Nvidia driver generate one and add this option, X
  does not start anymore.

  Ubuntu 14.04.1 LTS with latest updates as of this writing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Nov  4 07:38:59 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed
   tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:2145]
  InstallationDate: Installed on 2014-11-01 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 4318CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic 
root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6NET84WW (1.45 )
  dmi.board.name: 4318CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4318CTO
  dmi.product.version: ThinkPad W510
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.nvidia-graphics-drivers:

[Touch-packages] [Bug 1585867] Re: Support squashfs / .snap packages

** Description changed:

- Support squashfs / .snap pacakges
+ [Impact]
+ There is no registered MIME types for sqhuashfs/snap files. Thus nothing 
knows how to open them. You cannot browse the contents in file-roller.
+ 
+ [Test Case]
+ 1. Download/make a .snap
+ 2. Run 'gnome-open NAME.snap' or click on it in Nautilus
+ 
+ Expected result:
+ The snap is opened in an appropriate program (file-roller and/or GNOME 
Software).
+ 
+ Observed result:
+ The file cannot be opened.

** Description changed:

  [Impact]
  There is no registered MIME types for sqhuashfs/snap files. Thus nothing 
knows how to open them. You cannot browse the contents in file-roller.
  
  [Test Case]
  1. Download/make a .snap
  2. Run 'gnome-open NAME.snap' or click on it in Nautilus
  
  Expected result:
  The snap is opened in an appropriate program (file-roller and/or GNOME 
Software).
  
  Observed result:
  The file cannot be opened.
+ 
+ [Regression Potential]
+ Low. This change registers two new MIME types and adds new functionality to 
file-roller. Existing behaviours should be unchanged.

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

Title:
  Support squashfs / .snap packages

Status in File Roller:
  Confirmed
Status in shared-mime-info:
  Unknown
Status in file-roller package in Ubuntu:
  Fix Released
Status in shared-mime-info package in Ubuntu:
  Fix Released
Status in file-roller source package in Xenial:
  Triaged
Status in shared-mime-info source package in Xenial:
  Triaged

Bug description:
  [Impact]
  There is no registered MIME types for sqhuashfs/snap files. Thus nothing 
knows how to open them. You cannot browse the contents in file-roller.

  [Test Case]
  1. Download/make a .snap
  2. Run 'gnome-open NAME.snap' or click on it in Nautilus

  Expected result:
  The snap is opened in an appropriate program (file-roller and/or GNOME 
Software).

  Observed result:
  The file cannot be opened.

  [Regression Potential]
  Low. This change registers two new MIME types and adds new functionality to 
file-roller. Existing behaviours should be unchanged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1585867/+subscriptions

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

[Touch-packages] [Bug 1586938] Re: mcloud sso plugin(qml-plugins) can be merged into Account plugins

2016-06-02 Thread Gary.Wang

** Also affects: account-plugins (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: account-plugins (Ubuntu)
 Assignee: (unassigned) => Gary.Wang (gary-wzl77)

** Changed in: account-plugins (Ubuntu)
   Status: New => In Progress

** Branch linked: lp:~gary-wzl77/account-plugins/mcloud-plugin-lp1587282

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

Title:
  mcloud sso plugin(qml-plugins) can be merged into Account plugins

Status in mcloud:
  New
Status in account-plugins package in Ubuntu:
  In Progress

Bug description:
  Currently, mcloud library doesn't cover authentication, which should be 
considered to be implemented in proper way(ubuntu sso).
  So we need to mcloud sso plugin merged into account plugins projects so that 
it can be used by any apps and scopes.

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

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

[Touch-packages] [Bug 1588252] Re: [File Manager] Display issue: big white gap below header (portrait) & top gets cut off (landscape) after OTA-11

2016-06-02 Thread Anupam

Here's the screenshot in landscape mode. My phone is E5.

** Attachment added: "landscape screenshot"
   
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1588252/+attachment/4675575/+files/screenshot20160603_060545745.png

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

Title:
  [File Manager] Display issue: big white gap below header (portrait) &
  top gets cut off (landscape) after OTA-11

Status in Canonical System Image:
  Confirmed
Status in Ubuntu File Manager App:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  After the OTA-11 update, File Manager shows a big white space just below the 
header in portrait mode.
  https://launchpadlibrarian.net/262898404/screenshot20160602_150103754.png

  And also as Davide mentioned, top part goes off the display in landscape mode.
  https://launchpadlibrarian.net/262958275/screenshot20160602_184130460.png

  This only happens on E4.5 and E5, not on MX4 or M10
  0.4.525 of file manager

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

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

[Touch-packages] [Bug 1588562] Re: Please add ~/.local/bin to the default $PATH

2016-06-02 Thread Matthias Klose

** Bug watch added: Debian Bug tracker #820856
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856

** Also affects: bash (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856
   Importance: Unknown
   Status: Unknown

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

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

Title:
  Please add ~/.local/bin to the default $PATH

Status in bash package in Ubuntu:
  New
Status in bash source package in Xenial:
  New
Status in bash package in Debian:
  Unknown

Bug description:
  Starting in Xenial, 'pip install' by default places executables into
  ~/.local/bin. This is the de-facto standard place to put per-user
  executables -- for example, Fedora/Redhat puts it on the $PATH by
  default, and PEP 370 makes it the standard place for unprivileged
  installs of Python packages to put their scripts.

  But unfortunately, Ubuntu's does *not* add this directory to $PATH by
  default, which means that 'pip install' doesn't actually work -- any
  scripts that are installed are inaccessible, and every user has to
  manually add this to their PATH.

  Ubuntu should put ~/.local/bin onto PATH by default.

  Minor details (discussed with @doko at the PyCon sprints):

  - this should go at the beginning of PATH rather than the end, in accordance 
with Debian policy saying that more-local paths go before more-upstream paths. 
(This is inconsistent with how Fedora/RH do it, but consistent with how Python 
itself searches for packages.)
  - this will be added to /etc/skel/profile, so that it won't change any 
existing user accounts; it will only be applied to user accounts created 
*after* this change lands
  - unlike ~/bin (which Debian/Ubuntu have supported for ages), it will be 
added to PATH unconditionally, even if the directory doesn't exist. This is 
important to avoid a nasty trap for new users, where the first time they try to 
install a Python package they have to restart their shell. Since this only 
applies to new accounts, the directory will always start out nonexistent/empty, 
so having it in $PATH won't cause any unexpected changes in behavior.
  - possibly it would make sense to set this in /etc/environment or 
/etc/skel/.gnomerc or similar, so that it would also apply to non-shell 
processes (e.g. if the user wants to add a global key-binding to launch a 
Python program, then generally ~/.profile *doesn't* affect the environment 
where this command gets executed, and that can frustrate and confuse users if a 
command works fine from the terminal but not from a keybinding). But we should 
defer this discussion for the future, because even if this is a good idea, it 
isn't a good idea in a Xenial stable update.

  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856

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

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

[Touch-packages] [Bug 1581480] Re: [SRU] New stable release 2.48.2

2016-06-02 Thread Bartosz Kosiorek

** Changed in: glib-networking (Ubuntu Xenial)
 Assignee: (unassigned) => Bartosz Kosiorek (gang65)

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

Title:
  [SRU] New stable release 2.48.2

Status in glib-networking package in Ubuntu:
  Fix Released
Status in glib-networking source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  Upstream have released a new bugfix release.

  [ Changes ]

  From NEWS:

* gnutls: Fixed an infinite loop if a server sent two identical
  copies of its CA certificate [#765317, Carlos Garcia Campos]

  
  [ QA, testing, regression potential ]

  Under the GNOME MRE, you can believe all bugs upstream says are fixed
  are really fixed. Just test the system and make sure there are no
  regressions (e.g. look at errors.ubuntu.com).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1581480/+subscriptions

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

[Touch-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

@cyphermox

Here's the debug output we worked on today.  I removed most everything
from before I suspended the machine.  Everything remaining is either
from the suspend or the resume.

The output was achieved by adding --log-level=debug to
/lib/systemd/system/NetworkManager.service at the ExecStart= line, and
then restarting.

** Attachment added: "syslog debug output."
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576747/+attachment/4675543/+files/syslog

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678]

[Touch-packages] [Bug 1586538] Re: certutils from libnss3-tools - man page contradicts Mozilla's

2016-06-02 Thread Bug Watch Updater

** Changed in: nss
   Status: Unknown => New

** Changed in: nss
   Importance: Unknown => Medium

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

Title:
  certutils from libnss3-tools - man page contradicts Mozilla's

Status in NSS:
  New
Status in nss package in Ubuntu:
  New

Bug description:
  Description of certuitls here:
  
https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/tools/NSS_Tools_certutil#Options_and_Arguments

  contradicts the man page here:
  http://manpages.ubuntu.com/manpages/wily/man1/certutil.1.html

  In the former "-t p" is "prohibited (explicitly distrusted)".  In the
  latter, it's "Valid peer".

  I'm listing it as a security vuln, because someone could do mistakenly
  do the wrong thing.

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

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

[Touch-packages] [Bug 1588524] Re: FIPS_mode_set reports incorrect error message

2016-06-02 Thread Joy Latten

Will definitely remove clearing the error as we continue completing the
code.

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

Title:
  FIPS_mode_set reports incorrect error message

Status in openssl package in Ubuntu:
  New

Bug description:
  Hi! Some integration tests we run attempt to enable FIPS mode in
  OpenSSL, and assert that either our software continues to work, or
  that the error message emitted by OpenSSL is related to missing the
  FIPS module.

  On Ubuntu 14.10, running FIPS_mode_set fails and produces an error like:
  140225357260448:error:0F06D065:common libcrypto routines:FIPS_mode_set:fips 
mode not supported:o_fips.c:92:

  On Ubuntu 16.04 running OpenSSL/libssl1.0.0 version 1.0.2g-1ubuntu4.1,
  FIPS_mode_set fails, but does not produce an error message.

  I have attached a C file which, when executed on both these platforms,
  will demonstrate this behavior.

  I believe this may have been introduced by this ticket: 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1553309
  It provides a patch called openssl-1.0.2g-ubuntu-fips-cleanup.patch which 
includes this statement:
  +@@ -443,6 +430,7 @@ int FIPS_module_mode_set(int onoff, const char *auth)
  + fips_selftest_fail = 0;
  + ret = 1;
  +  end:
  ++ERR_clear_error(); /* clear above err msg; fips mode disabled for now */
  + fips_clear_owning_thread();
  + fips_w_unlock();
  + return ret;

  This appears to be clearing the error messages we're asserting on
  before returning from FIPS_module_mode_set.

  For reference, here is our ticket where we are tracking this issue:
  https://jira.mongodb.org/browse/SERVER-24350

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

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

[Touch-packages] [Bug 1588562] [NEW] Please add ~/.local/bin to the default $PATH

2016-06-02 Thread Nathaniel Smith

Public bug reported:

Starting in Xenial, 'pip install' by default places executables into
~/.local/bin. This is the de-facto standard place to put per-user
executables -- for example, Fedora/Redhat puts it on the $PATH by
default, and PEP 370 makes it the standard place for unprivileged
installs of Python packages to put their scripts.

But unfortunately, Ubuntu's does *not* add this directory to $PATH by
default, which means that 'pip install' doesn't actually work -- any
scripts that are installed are inaccessible, and every user has to
manually add this to their PATH.

Ubuntu should put ~/.local/bin onto PATH by default.

Minor details (discussed with @doko at the PyCon sprints):

- this should go at the beginning of PATH rather than the end, in accordance 
with Debian policy saying that more-local paths go before more-upstream paths. 
(This is inconsistent with how Fedora/RH do it, but consistent with how Python 
itself searches for packages.)
- this will be added to /etc/skel/profile, so that it won't change any existing 
user accounts; it will only be applied to user accounts created *after* this 
change lands
- unlike ~/bin (which Debian/Ubuntu have supported for ages), it will be added 
to PATH unconditionally, even if the directory doesn't exist. This is important 
to avoid a nasty trap for new users, where the first time they try to install a 
Python package they have to restart their shell. Since this only applies to new 
accounts, the directory will always start out nonexistent/empty, so having it 
in $PATH won't cause any unexpected changes in behavior.
- possibly it would make sense to set this in /etc/environment or 
/etc/skel/.gnomerc or similar, so that it would also apply to non-shell 
processes (e.g. if the user wants to add a global key-binding to launch a 
Python program, then generally ~/.profile *doesn't* affect the environment 
where this command gets executed, and that can frustrate and confuse users if a 
command works fine from the terminal but not from a keybinding). But we should 
defer this discussion for the future, because even if this is a good idea, it 
isn't a good idea in a Xenial stable update.

Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856

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

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

Title:
  Please add ~/.local/bin to the default $PATH

Status in bash package in Ubuntu:
  New

Bug description:
  Starting in Xenial, 'pip install' by default places executables into
  ~/.local/bin. This is the de-facto standard place to put per-user
  executables -- for example, Fedora/Redhat puts it on the $PATH by
  default, and PEP 370 makes it the standard place for unprivileged
  installs of Python packages to put their scripts.

  But unfortunately, Ubuntu's does *not* add this directory to $PATH by
  default, which means that 'pip install' doesn't actually work -- any
  scripts that are installed are inaccessible, and every user has to
  manually add this to their PATH.

  Ubuntu should put ~/.local/bin onto PATH by default.

  Minor details (discussed with @doko at the PyCon sprints):

  - this should go at the beginning of PATH rather than the end, in accordance 
with Debian policy saying that more-local paths go before more-upstream paths. 
(This is inconsistent with how Fedora/RH do it, but consistent with how Python 
itself searches for packages.)
  - this will be added to /etc/skel/profile, so that it won't change any 
existing user accounts; it will only be applied to user accounts created 
*after* this change lands
  - unlike ~/bin (which Debian/Ubuntu have supported for ages), it will be 
added to PATH unconditionally, even if the directory doesn't exist. This is 
important to avoid a nasty trap for new users, where the first time they try to 
install a Python package they have to restart their shell. Since this only 
applies to new accounts, the directory will always start out nonexistent/empty, 
so having it in $PATH won't cause any unexpected changes in behavior.
  - possibly it would make sense to set this in /etc/environment or 
/etc/skel/.gnomerc or similar, so that it would also apply to non-shell 
processes (e.g. if the user wants to add a global key-binding to launch a 
Python program, then generally ~/.profile *doesn't* affect the environment 
where this command gets executed, and that can frustrate and confuse users if a 
command works fine from the terminal but not from a keybinding). But we should 
defer this discussion for the future, because even if this is a good idea, it 
isn't a good idea in a Xenial stable update.

  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856

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

-- 
Mailing list:

[Touch-packages] [Bug 1497625] Re: /etc/security/namespace.init always fails with default /bin/sh

2016-06-02 Thread Bug Watch Updater

** Changed in: pam (Debian)
   Status: Confirmed => Fix Released

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

Title:
  /etc/security/namespace.init always fails with default /bin/sh

Status in pam package in Ubuntu:
  Triaged
Status in pam package in Debian:
  Fix Released

Bug description:
  Ubuntu 15.04 uses dash as its default /bin/sh. dash does not support
  the -p option wihch is used by /etc/security/namespace.init. As a
  result any attempt to use pam_namespace fails:

  # su iws
  /bin/sh: 0: Illegal option -p

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

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

[Touch-packages] [Bug 1588126] Re: [OTA-11] Wifi never connects since installing OTA-11

2016-06-02 Thread Daniel van Vugt

Yep, ubuntu-device-flash touch --wipe --bootstrap ... I can't tell you
the network config now as I'm not near it.

Same failure on two unrelated devices while the rest of the wifi network
kept working. The same devices were previously happy on OTA-10.1

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

Title:
  [OTA-11] Wifi never connects since installing OTA-11

Status in Canonical System Image:
  New
Status in indicator-network package in Ubuntu:
  New

Bug description:
  I've just flashed clean images of OTA-11 from the stable channel onto
  a BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the
  phones can see the wifi networks but can't connect to any of them any
  more.

  The wifi networks continue to work for non-Ubuntu devices.

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

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

[Touch-packages] [Bug 1588524] Re: FIPS_mode_set reports incorrect error message

2016-06-02 Thread Joy Latten

I purposely cleared this error message from the queue so that no one would be 
distracted or thwarted by the addition of the fips code while it is a work in 
progress and not complete. FIPS_module_mode_set() at this point will always 
fail and return an error code. 
But yes, I see in your test program that you also want to print the error 
message if
you get an error code.

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

Title:
  FIPS_mode_set reports incorrect error message

Status in openssl package in Ubuntu:
  New

Bug description:
  Hi! Some integration tests we run attempt to enable FIPS mode in
  OpenSSL, and assert that either our software continues to work, or
  that the error message emitted by OpenSSL is related to missing the
  FIPS module.

  On Ubuntu 14.10, running FIPS_mode_set fails and produces an error like:
  140225357260448:error:0F06D065:common libcrypto routines:FIPS_mode_set:fips 
mode not supported:o_fips.c:92:

  On Ubuntu 16.04 running OpenSSL/libssl1.0.0 version 1.0.2g-1ubuntu4.1,
  FIPS_mode_set fails, but does not produce an error message.

  I have attached a C file which, when executed on both these platforms,
  will demonstrate this behavior.

  I believe this may have been introduced by this ticket: 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1553309
  It provides a patch called openssl-1.0.2g-ubuntu-fips-cleanup.patch which 
includes this statement:
  +@@ -443,6 +430,7 @@ int FIPS_module_mode_set(int onoff, const char *auth)
  + fips_selftest_fail = 0;
  + ret = 1;
  +  end:
  ++ERR_clear_error(); /* clear above err msg; fips mode disabled for now */
  + fips_clear_owning_thread();
  + fips_w_unlock();
  + return ret;

  This appears to be clearing the error messages we're asserting on
  before returning from FIPS_module_mode_set.

  For reference, here is our ticket where we are tracking this issue:
  https://jira.mongodb.org/browse/SERVER-24350

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

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

[Touch-packages] [Bug 1588557] [NEW] Nexus 4 cannot restore to phone mode after disconnecting HDMI connection

2016-06-02 Thread XiaoGuo, Liu

Public bug reported:

After flashing the convergence software for Nexus 4:

https://system-image.ubuntu.com/ubuntu-touch/rc-proposed/ubuntu-pd/mako/

I connect Bluetooth mouse and keyboard, and everything works fine.

- connect to a DELL monitor, it enters to the desktop mode
- disconnect it to the DELL monitor, it stays in the desktop mode (mouse and 
keyboard are still connected to the phone).

My understanding is that phone should restore to the phone mode. The
software I flashed was from the following channel:

https://system-image.ubuntu.com/ubuntu-touch/rc-proposed/ubuntu-pd/mako/

Thanks & best regards,
XiaoGuo

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

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

Title:
  Nexus 4 cannot restore to phone mode after disconnecting HDMI
  connection

Status in unity8 package in Ubuntu:
  New

Bug description:
  After flashing the convergence software for Nexus 4:

  https://system-image.ubuntu.com/ubuntu-touch/rc-proposed/ubuntu-
  pd/mako/

  I connect Bluetooth mouse and keyboard, and everything works fine.

  - connect to a DELL monitor, it enters to the desktop mode
  - disconnect it to the DELL monitor, it stays in the desktop mode (mouse and 
keyboard are still connected to the phone).

  My understanding is that phone should restore to the phone mode. The
  software I flashed was from the following channel:

  https://system-image.ubuntu.com/ubuntu-touch/rc-proposed/ubuntu-
  pd/mako/

  Thanks & best regards,
  XiaoGuo

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

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

[Touch-packages] [Bug 1588252] Re: [File Manager] Display issue: big white gap below header (portrait) & top gets cut off (landscape) after OTA-11

2016-06-02 Thread Pat McGowan

There is a lot of special case code on whether to show the sidebar or use the 
bottom edge. The case with the issue is without the sidebar by default.
However, given its triggering on > 50 GUs I am unclear why the sidebar is shown 
on MX4 which should be the same GUs as the BQs but is not.

** Changed in: canonical-devices-system-image
 Assignee: Zoltan Balogh (bzoltan) => Alan Pope  (popey)

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

Title:
  [File Manager] Display issue: big white gap below header (portrait) &
  top gets cut off (landscape) after OTA-11

Status in Canonical System Image:
  Confirmed
Status in Ubuntu File Manager App:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  After the OTA-11 update, File Manager shows a big white space just below the 
header in portrait mode.
  https://launchpadlibrarian.net/262898404/screenshot20160602_150103754.png

  And also as Davide mentioned, top part goes off the display in landscape mode.
  https://launchpadlibrarian.net/262958275/screenshot20160602_184130460.png

  This only happens on E4.5 and E5, not on MX4 or M10
  0.4.525 of file manager

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

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

[Touch-packages] [Bug 1585709] Re: Xorg freeze

2016-06-02 Thread dualBootLaptop

2016June2: I just installed the latest round of updates, and it seems to
have fixed the problem. At least, I've switched user several times
without a freeze.

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

Title:
Xorg freeze

Status in xorg package in Ubuntu:
New

Bug description:
Ubuntu 14.04 LTS
I boot the machine, log in to user A, and start no programs. Instead, I
immediately switch user to user B. I then switch back to user A.
After entering (again) the password for user A, the system freezes.
It freezes in one of two ways: either it goes to a black screen with no mouse
cursor visible, or it goes to a staticy purple banded background with the mouse
cursor visible and usable but nothing on the screen is responsive.
Very rarely, it will successfully log in, but if I then repeat the process id
est switch user to user B and back again, it will freeze.

This began around perhaps May 15--20.
I have been using Ubuntu 14.04 for a year without problems prior to this.
Ubuntu Software Center History shows a ton of updates installed 17 May, 18
May, 19 May, and 22 May.
The only one that jumps out as possibly X-related is libgtk, but I have no
idea what most of the updates do, they're all things like libmm-glib0 (I mean,
I can Google that *one*, but they're all like that and I can't copy-paste out
of the Software Center). Hopefully that was included in the info reported by
Apport.
I'm guessing that's what you mean by the question "Is this a regression?"?
Since it doesn't involve any applications and it never happened until a week
ago, it would almost have to be caused by an update.
However, I am unable to undo these updates, and the Internet is telling me
that undoing updates can only be done via weird hacks that will almost
definitely make the problem worse.

I am unable to recreate the freeze on the Ctrl+Alt+F1 console, so I would
guess it has to do with the X window server.
When the freeze occurs, Alt+SysRq+1 does nothing.

I only have one machine, so I don't know how to ssh into the machine
while it is frozen.

P.S. There was a part of the instructions that would definitely by very
useful but which I am unable to follow:
https://wiki.ubuntu.com/X/Troubleshooting/Freeze says If you updated your
system and it started to freeze, start reverting package updates backwards
until the freezes stop occurring.
Reverting package updates backwards would almost definitely fix my problem,
as noted above.
Software Updater provides no option to do this, Ubuntu Software Center
History -> Updates provides no option to do this, and it is not mentioned at
https://wiki.ubuntu.com/SoftwareUpdates. AskUbuntu and UbuntuForums tell me
that no such feature exists:

http://askubuntu.com/questions/34888/is-there-any-way-to-roll-back-the-most-recent-upgrade
http://ubuntuforums.org/showthread.php?t=1804985
So I don't know what this instruction is talking about.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-86.131-generic 3.13.11-ckt39
Uname: Linux 3.13.0-86-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3.20
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed May 25 10:53:39 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
fglrx-updates-core, 15.201, 3.13.0-85-generic, x86_64: installed
fglrx-updates-core, 15.201, 3.13.0-86-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last week or two
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8550G]
[1002:990d] (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device [103c:1984]
InstallationDate: Installed on 2014-06-06 (719 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-86-generic.efi.signed
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.35
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1984
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 01.15
dmi.chassis.type: 10
dmi.chassis.vendor:

[Touch-packages] [Bug 1588252] Re: [File Manager] Display issue: big white gap below header (portrait) & top gets cut off (landscape) after OTA-11

2016-06-02 Thread Anupam

** Description changed:

  After the OTA-11 update, File Manager shows a big white space just below the 
header in portrait mode.
  https://launchpadlibrarian.net/262898404/screenshot20160602_150103754.png
  
  And also as Davide mentioned, top part goes off the display in landscape mode.
  https://launchpadlibrarian.net/262958275/screenshot20160602_184130460.png
  
- This only happens on E4.5, not on MX4 or M10
+ This only happens on E4.5 and E5, not on MX4 or M10
  0.4.525 of file manager

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

Title:
  [File Manager] Display issue: big white gap below header (portrait) &
  top gets cut off (landscape) after OTA-11

Status in Canonical System Image:
  Confirmed
Status in Ubuntu File Manager App:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  After the OTA-11 update, File Manager shows a big white space just below the 
header in portrait mode.
  https://launchpadlibrarian.net/262898404/screenshot20160602_150103754.png

  And also as Davide mentioned, top part goes off the display in landscape mode.
  https://launchpadlibrarian.net/262958275/screenshot20160602_184130460.png

  This only happens on E4.5 and E5, not on MX4 or M10
  0.4.525 of file manager

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

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

[Touch-packages] [Bug 1544754] Re: implement the HTML5 pointer lock API

2016-06-02 Thread Chris Coulson

** Changed in: oxide
Milestone: branch-1.16 => branch-1.17

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

Title:
  implement the HTML5 pointer lock API

Status in Oxide:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The internet archive just released a collection of Win 3.1 games, using the 
DosBox emulator to run them on the website. On Chrome this triggers a 
"Allow/Deny archive.org to disable your mouse cursor" popup. Games are only 
playable using mouse or touch after accepting this.
  In the browser app/ Oxide there's no such popup and mouse input doesn't work.

  https://archive.org/details/win3_Mono3Dlx

  Another (more lightweight) example page: https://mdn.github.io
  /pointer-lock-demo/

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

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

[Touch-packages] [Bug 1587141] Re: systemd-resolved crashed with SIGABRT: Assertion 'p->n_ref > 0' failed at ../src/resolve/resolved-dns-packet.c:184, function dns_packet_unref(

This is fixed/worked around in
https://launchpad.net/ubuntu/+source/systemd/230-2git1, but I typoed the
bug number.


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

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

Title:
  systemd-resolved crashed with SIGABRT: Assertion 'p->n_ref > 0' failed
  at ../src/resolve/resolved-dns-packet.c:184, function
  dns_packet_unref(

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  i cant use strg alt F2 to open terminal, wlan connection is lost, i
  cnat find programs with search, i dont know what i shoud do, can i
  reste the sudo /admin account ?

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 230-1git1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Mon May 30 16:08:01 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2012-11-14 (1292 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-6650
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=6b242581-6652-4194-b9c3-7cf42dd727ae ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Title: systemd-resolved crashed with SIGABRT
  UpgradeStatus: Upgraded to yakkety on 2015-11-07 (205 days ago)
  UserGroups:
   
  dmi.bios.date: 10/20/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7459
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd10/20/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-6650:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7459:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-6650
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Touch-packages] [Bug 1588252] Re: [File Manager] Display issue: big white gap below header (portrait) & top gets cut off (landscape) after OTA-11

2016-06-02 Thread Pat McGowan

@zoltan can we check that this isnt a toolkit issue

** Description changed:

  After the OTA-11 update, File Manager shows a big white space just below the 
header in portrait mode.
  https://launchpadlibrarian.net/262898404/screenshot20160602_150103754.png
  
  And also as Davide mentioned, top part goes off the display in landscape mode.
  https://launchpadlibrarian.net/262958275/screenshot20160602_184130460.png
+ 
+ This only happens on E4.5, not on MX4 or M10
+ 0.4.525 of file manager

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

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

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

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

Title:
  [File Manager] Display issue: big white gap below header (portrait) &
  top gets cut off (landscape) after OTA-11

Status in Canonical System Image:
  Confirmed
Status in Ubuntu File Manager App:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  After the OTA-11 update, File Manager shows a big white space just below the 
header in portrait mode.
  https://launchpadlibrarian.net/262898404/screenshot20160602_150103754.png

  And also as Davide mentioned, top part goes off the display in landscape mode.
  https://launchpadlibrarian.net/262958275/screenshot20160602_184130460.png

  This only happens on E4.5, not on MX4 or M10
  0.4.525 of file manager

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

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

[Touch-packages] [Bug 1586991] Re: systemd-resolved crashed with SIGSEGV in dns_transaction_cache_answer()

This is fixed/worked around in
https://launchpad.net/ubuntu/+source/systemd/230-2git1, but I typoed the
bug number.

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

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

Title:
  systemd-resolved crashed with SIGSEGV in
  dns_transaction_cache_answer()

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Got that crash with the newer network-manager 1.2.2-0ubuntu3 upgrade with a 
gnome-shell session.
  Reinstalling network-manager also ends with that crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 230-1git1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Mon May 30 11:58:58 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf

   3 overridden configuration files found.
  Title: systemd-resolved crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Touch-packages] [Bug 1573782] Re: Virtual display output configuration is set to LVDS

** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005

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

Title:
  Virtual display output configuration is set to LVDS

Status in Mir:
  Fix Committed
Status in Mir 0.22 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  The display output type associated with a virtual display is set to
  mir_display_output_type_lvds.

  Ideally a new type "mir_display_output_type_virtual" should be added
  and the virtual output should use it to as its type.

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

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

[Touch-packages] [Bug 1447886] Re: mir_demo_server(_minimal): Window movement/resizing stops responding when the cursor leaves the surface, and can lead to windows 1px wide and unrecoverable.

** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005

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

Title:
  mir_demo_server(_minimal): Window movement/resizing stops responding
  when the cursor leaves the surface, and can lead to windows 1px wide
  and unrecoverable.

Status in Mir:
  Fix Committed
Status in MirAL:
  In Progress
Status in mir package in Ubuntu:
  Triaged

Bug description:
  mir_demo_server(_minimal) version 0.13 and later: Window
  movement/resizing stops responding when the cursor leaves the surface.

  If you move or resize a surface with Alt+(button1/button3) then it's
  very easy to get the shell into a state where the window stops
  responding to movement/resizing and even becomes unrecoverable (window
  1px wide).

  Essentially the problem is the shell is only looking at the current
  cursor position and doesn't do anything if it's outside of the
  surface. This is frustrating as waiving the mouse around a bit it's
  very easy to reach this situation.

  It should be looking at the gesture as a whole and only doing position
  checking at the start of the move/resize gesture (ie. mouse button
  down). Thereafter the gesture should be continuous until the button is
  released, regardless of whether the cursor is still inside the
  surface/titlebar. You will find this is how all real desktops work,
  and mir_proving_server tries to too. Surfaces should always "own"
  input regardless of cursor position, just so long as the gesture
  (mouse down) began on that surface.

  The "unrecoverable" bit: This happens if you resize a surface too
  small/thin and it becomes impossible to resize it bigger again.

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

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

[Touch-packages] [Bug 1553549] Re: Mir crashes with useless backtrace when mg::Platform methods throw

** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005

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

Title:
  Mir crashes with useless backtrace when mg::Platform methods throw

Status in Mir:
  Fix Committed
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Triaged
Status in unity-system-compositor package in Ubuntu:
  Invalid

Bug description:
  So, the problem that causes unity-system-compositor to crash (rather
  than fail to start with a helpful error message) is that when methods
  on mg::Platform throw we unload the platform DSO before exception
  processing is completed, so libstdc++ goes merrily along trying to
  execute code that is longer mapped.

  Original report below:
  unity-system-co[5574]: segfault at 7f8056ee2490 ip 7f805c592c3b sp 
7fffd6b871a0 error 4 in libstdc++.so.6.0.21[7f805c506000+172000]

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-system-compositor 0.4.2+16.04.20160219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Mar  5 19:03:39 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  ExecutableTimestamp: 1455894356
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor 
Integrated Graphics Controller [1462:1102]
     Subsystem: Micro-Star International Co., Ltd. [MSI] GM204M [GeForce GTX 
970M] [1462:1102]
  InstallationDate: Installed on 2015-02-25 (374 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file 
/run/lightdm-mir-0 --from-dm-fd 11 --to-dm-fd 20 --vt 8
  ProcCwd: /
  ProcEnviron:

  SegvAnalysis:
   Segfault happened at: 0x7f805c592c3b:mov(%rsi),%rax
   PC (0x7f805c592c3b) ok
   source "(%rsi)" (0x7f8056ee2490) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __gxx_personality_v0 () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   _Unwind_RaiseException () from /lib/x86_64-linux-gnu/libgcc_s.so.1
   _Unwind_Resume_or_Rethrow () from /lib/x86_64-linux-gnu/libgcc_s.so.1
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0()
  UpgradeStatus: Upgraded to xenial on 2015-11-03 (122 days ago)
  UserGroups:

  version.libdrm: libdrm2 2.4.67-1
  version.lightdm: lightdm 1.17.5-0ubuntu2
  version.mesa: libegl1-mesa-dev N/A

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

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

[Touch-packages] [Bug 1575192] Re: Mir-on-X11 breaks mir_proving_server resize logic

** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005

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

Title:
  Mir-on-X11 breaks mir_proving_server resize logic

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  $ mir_proving_server&
  $ mir_demo_client_egltriangle

  Alt+drag with middle mouse button

  Expect: client is resized
  Actual: Nothing happens

  A bit of investigation shows that the mouse-button-down event isn't
  being received. (The movement event is received.)

  (The problem doesn't occur on other platforms.)

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

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

[Touch-packages] [Bug 1573572] Re: Virtual output is not removed when screencast client disappears

** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005

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

Title:
  Virtual output is not removed when screencast client disappears

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.22 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  With WiFi Display we're using the screencast API from our management
  service aethercast to create an virtual display which is then used by
  Unity 8. If aethercast crashes the virtual output seems to stay as
  Unity 8 never switches back from the virtual touchpad its displaying
  since the virtual output is use.

  When aethercast terminates the screencast connection Unity 8 switches
  correctly back to the phone interface.

  I suspect this is reproducible with mirscreencast too.

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

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

[Touch-packages] [Bug 1575765] Re: Mir-on-X11 doesn't pass Alt+primary button drag to Mir

** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005

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

Title:
  Mir-on-X11 doesn't pass Alt+primary button drag to Mir

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  $ mir_demo_server --launch mir_demo_client_egltriangle

  Expected: "Alt+primary drag" on the client surface drags the spinning 
triangle.
  Observed: "Alt+primary drag" on the client surface drags the whole Mir-on-X 
window.

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

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

[Touch-packages] [Bug 1575211] Re: Resizing windows can crash mir_demo_server [std::exception::what: unexpected release: no buffers were given to client]

** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005

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

Title:
  Resizing windows can crash mir_demo_server [std::exception::what:
  unexpected release: no buffers were given to client]

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  $ mir_demo_server --launch mir_demo_client_egltriangle

  Repeatedly Alt+drag middle button to make the surface as narrow as
  possible leads to:

  Resized to 1x289
  Surface occluded
  Signal 1 received. Good night.
  ERROR: 
/build/mir-pkdHET/mir-0.21.0+16.04.20160330/src/server/compositor/buffer_queue.cpp(259):
 Throw in function virtual void 
mir::compositor::BufferQueue::client_release(mir::graphics::Buffer*)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: unexpected release: no buffers were given to client

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

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

[Touch-packages] [Bug 1576260] Re: Can't VT switch from mir_demo_server (any more)

** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005

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

Title:
  Can't VT switch from mir_demo_server (any more)

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New
Status in mir source package in Xenial:
  New

Bug description:
  I can't VT switch from mir_demo_server. This turns out to be an issue
  that occurred in 16.04 where /dev/console no longer works with VT
  switching. Using /dev/tty0 work. See bug 1566073 for associated change
  in LightDM.

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

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

[Touch-packages] [Bug 1579076] Re: [regression] NBS causes sudden loss of performance after surface resizes

** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005

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

Title:
  [regression] NBS causes sudden loss of performance after surface
  resizes

Status in Mir:
  Fix Committed
Status in Mir 0.23 series:
  Fix Committed
Status in Mir 0.24 series:
  Fix Committed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Seems that the dash gets resized() very shortly after its created.
  This seems to cause a degradation from "triple-buffered" operation to
  "double-buffered" operation. On some device loads (eg, krillin+dash,
  where the rendering needs to be triple buffering to stay at vsync
  rate), this can cause the performance to dip

  tagging as critical, as it should block 0.23.

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

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

[Touch-packages] [Bug 1580774] Re: mouse is getting stuck on a phantom edge

** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005

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

Title:
  mouse is getting stuck on a phantom edge

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.22 series:
  Fix Released
Status in Mir 0.23 series:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  frieza build 101/rc-proposed

  Steps:
  1. connect mouse & keyboard to M10
  2. launch xchat
  3. go full screen
  4. mouse move around across the entirety of the screen (landscape)

  expected: mouse can range over entire screen
  actual: gets stuck moving right

  note: i noticed it happening on xchat, but when changing focus to dash
  it was also continuing to happen

  So, i kinda suspect this may be related to rotation maybe.
  I do admit i did the full OOBE in portrait mode

  Problem is also persisting across reboot.

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

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

[Touch-packages] [Bug 1578159] Re: Performance loss with NBS and overlays on

** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005

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

Title:
  Performance loss with NBS and overlays on

Status in Mir:
  Fix Committed
Status in Mir 0.23 series:
  Fix Committed
Status in Mir 0.24 series:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  If you run a server with overlays enabled on android devices with a
  client, sporadically, the performance will dip between 1/2 vsync rate
  and vsync rate. The dip is dependent on load, (it seems loads that tax
  the system at near-vsync rates seem to cause the problem).

  Should be fixed before 0.23 is published, so tagging as critical.

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

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

[Touch-packages] [Bug 1581368] Re: [regression] MIR_CLIENT_PERF_REPORT is showing bogus render times and buffer lag

** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005

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

Title:
  [regression] MIR_CLIENT_PERF_REPORT is showing bogus render times and
  buffer lag

Status in Mir:
  Fix Committed
Status in Mir 0.23 series:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  MIR_CLIENT_PERF_REPORT is showing bogus render times:

  $ env MIR_CLIENT_PERF_REPORT=log bin/mir_demo_client_egltriangle
  ...
  [2016-05-13 16:20:12.972236] perf: mir_demo_client_egltriangle.bin: 62.68 
FPS, render time 23216586.29ms, buffer lag 0.00ms (3 buffers)
  [2016-05-13 16:20:13.973084] perf: mir_demo_client_egltriangle.bin: 60.00 
FPS, render time 23217610.93ms, buffer lag 0.00ms (3 buffers)
  [2016-05-13 16:20:14.973926] perf: mir_demo_client_egltriangle.bin: 60.00 
FPS, render time 23218611.88ms, buffer lag 0.00ms (3 buffers)
  ^CSignal 2 received. Good night.

  I haven't bisected it yet but know:
  FAULTY: Mir 0.24 lp:mir
  WORKING: Mir 0.21 (xenial)

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

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

[Touch-packages] [Bug 1584603] Re: [ FAILED ] ClientLogging.reports_performance (Value of: nbuffers)

** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005

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

Title:
  [ FAILED ] ClientLogging.reports_performance (Value of: nbuffers)

Status in Mir:
  Fix Committed
Status in Mir 0.23 series:
  Fix Committed
Status in mir package in Ubuntu:
  Invalid

Bug description:
  10:23:22 [ RUN ] ClientLogging.reports_performance
  10:23:22 [2016-05-20 10:18:25.500861] mirserver: Starting
  10:23:22 [2016-05-20 10:18:25.504499] mirserver: Selected driver: dummy 
(version 0.23.0)
  10:23:22 [2016-05-20 10:18:25.548064] mirserver: Using software cursor
  10:23:22 [2016-05-20 10:18:25.552896] mirserver: Initial display 
configuration:
  10:23:22 [2016-05-20 10:18:25.553212] mirserver: 1.1: VGA 0.0" 0x0mm
  10:23:22 [2016-05-20 10:18:25.553415] mirserver: Current mode 1600x1600 
60.00Hz
  10:23:22 [2016-05-20 10:18:25.553592] mirserver: Preferred mode 1600x1600 
60.00Hz
  10:23:22 [2016-05-20 10:18:25.553758] mirserver: Logical position +0+0
  10:23:22 [2016-05-20 10:18:25.580332] mirserver: Selected input driver: 
mir:stub-input (version: 0.23.0)
  10:23:22 [2016-05-20 10:18:25.581448] mirserver: Mir version 0.23.0
  10:23:22 
/��BUILDDIR��/mir-0.23.0+xenial1136bzr3514/tests/acceptance-tests/test_client_logging.cpp:116:
 Failure
  10:23:22 Value of: nbuffers
  10:23:22 Expected: is equal to 3
  10:23:22 Actual: 2 (of type int)
  10:23:22 
/��BUILDDIR��/mir-0.23.0+xenial1136bzr3514/tests/acceptance-tests/test_client_logging.cpp:117:
 Failure
  10:23:22 Value of: Test::HasFailure()
  10:23:22 Actual: true
  10:23:22 Expected: false
  10:23:22 Log line = {[StringStreamLogger] perf: Rumpelstiltskin: 8.77 FPS, 
render time 3.51ms, buffer lag 120.30ms (2 buffers)}
  10:23:22 [ FAILED ] ClientLogging.reports_performance (4266 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial/1107/consoleFull

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

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

[Touch-packages] [Bug 1583970] Re: [testsfail] ClientLogging.reports_performance [Value of: lag]

** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005

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

Title:
  [testsfail] ClientLogging.reports_performance [Value of: lag]

Status in Mir:
  Fix Committed
Status in Mir 0.23 series:
  Fix Committed
Status in mir package in Ubuntu:
  Invalid

Bug description:
  Doesn't seem to be quite the same thing as lp:1563148 (although
  probably related to the same underlying dependence on realtime).

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/1095/consoleFull

  17:18:25 13: [ RUN ] ClientLogging.reports_performance
  17:18:25 13: [2016-05-19 17:18:25.480624] mirserver: Starting
  17:18:25 13: [2016-05-19 17:18:25.483906] mirserver: Selected driver: dummy 
(version 0.23.0)
  17:18:25 13: [2016-05-19 17:18:25.517901] mirserver: Using software cursor
  17:18:25 13: [2016-05-19 17:18:25.523291] mirserver: Initial display 
configuration:
  17:18:25 13: [2016-05-19 17:18:25.523635] mirserver: 1.1: VGA 0.0" 0x0mm
  17:18:25 13: [2016-05-19 17:18:25.523889] mirserver: Current mode 1600x1600 
60.00Hz
  17:18:25 13: [2016-05-19 17:18:25.524090] mirserver: Preferred mode 1600x1600 
60.00Hz
  17:18:25 13: [2016-05-19 17:18:25.524267] mirserver: Logical position +0+0
  17:18:25 13: [2016-05-19 17:18:25.551303] mirserver: Selected input driver: 
mir:stub-input (version: 0.23.0)
  17:18:25 13: [2016-05-19 17:18:25.552840] mirserver: Mir version 0.23.0
  17:18:29 13: 
/��BUILDDIR��/mir-0.23.0+xenial1124bzr3512/tests/acceptance-tests/test_client_logging.cpp:115:
 Failure
  17:18:29 13: Value of: lag
  17:18:29 13: Expected: is > 50
  17:18:29 13: Actual: 20.89 (of type float)
  17:18:29 13: 
/��BUILDDIR��/mir-0.23.0+xenial1124bzr3512/tests/acceptance-tests/test_client_logging.cpp:117:
 Failure
  17:18:29 13: Value of: Test::HasFailure()
  17:18:29 13: Actual: true
  17:18:29 13: Expected: false
  17:18:29 13: Log line = {[StringStreamLogger] perf: Rumpelstiltskin: 8.56 
FPS, render time 3.67ms, buffer lag 20.89ms (3 buffers)}
  17:18:29 13: [ FAILED ] ClientLogging.reports_performance (4524 ms)

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

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

[Touch-packages] [Bug 1584784] Re: Using NBS, X apps under Unity8 need interaction to start in pocket-desktop

** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005

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

Title:
  Using NBS, X apps under Unity8 need interaction to start in pocket-
  desktop

Status in Mir:
  In Progress
Status in Mir 0.23 series:
  In Progress
Status in Mir 0.24 series:
  In Progress
Status in QtMir:
  Invalid
Status in mir package in Ubuntu:
  In Progress
Status in qtmir package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  With Mir 0.23.0, X apps under Unity8 need some interaction to get the
  applications to start. 0.23.0 is blocked pending fix.

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

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

[Touch-packages] [Bug 1584605] Re: [ FAILED ] ClientLogging.reports_performance (Value of: render)

** Branch linked: lp:~untrusted-ci-dev-bot/mir/mir-ubuntu-yakkety-
landing-005

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

Title:
  [ FAILED ] ClientLogging.reports_performance (Value of: render)

Status in Mir:
  Fix Committed
Status in Mir 0.23 series:
  Fix Committed
Status in mir package in Ubuntu:
  Invalid

Bug description:
  10:32:32 9: [ RUN ] ClientLogging.reports_performance
  10:32:32 9: [2016-05-20 10:32:32.094437] mirserver: Starting
  10:32:32 9: [2016-05-20 10:32:32.101512] mirserver: Selected driver: dummy 
(version 0.23.0)
  10:32:32 9: [2016-05-20 10:32:32.146166] mirserver: Initial display 
configuration:
  10:32:32 9: [2016-05-20 10:32:32.146653] mirserver: 1.1: VGA 0.0" 0x0mm
  10:32:32 9: [2016-05-20 10:32:32.146953] mirserver: Current mode 1600x1600 
60.00Hz
  10:32:32 9: [2016-05-20 10:32:32.147272] mirserver: Preferred mode 1600x1600 
60.00Hz
  10:32:32 9: [2016-05-20 10:32:32.147527] mirserver: Logical position +0+0
  10:32:32 9: [2016-05-20 10:32:32.151831] mirserver: Using software cursor
  10:32:32 9: [2016-05-20 10:32:32.188313] mirserver: Selected input driver: 
mir:stub-input (version: 0.23.0)
  10:32:32 9: [2016-05-20 10:32:32.190056] mirserver: Mir version 0.23.0
  10:32:43 9: 
/��BUILDDIR��/mir-0.23.0+vivid1136bzr3514/tests/acceptance-tests/test_client_logging.cpp:114:
 Failure
  10:32:46 9: Value of: render
  10:32:47 9: Expected: is < 100
  10:32:47 9: Actual: 696.43 (of type float)
  10:32:47 9: 
/��BUILDDIR��/mir-0.23.0+vivid1136bzr3514/tests/acceptance-tests/test_client_logging.cpp:115:
 Failure
  10:32:47 9: Value of: lag
  10:32:47 9: Expected: is > 50
  10:32:47 9: Actual: 0 (of type float)
  10:32:47 9: 
/��BUILDDIR��/mir-0.23.0+vivid1136bzr3514/tests/acceptance-tests/test_client_logging.cpp:117:
 Failure
  10:32:47 9: Value of: Test::HasFailure()
  10:32:47 9: Actual: true
  10:32:47 9: Expected: false
  10:32:47 9: Log line = {[StringStreamLogger] perf: Rumpelstiltskin: 1.41 FPS, 
render time 696.43ms, buffer lag 0.00ms (3 buffers)}
  10:32:47 9: [ FAILED ] ClientLogging.reports_performance (8692 ms)

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/1107/consoleFull

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

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

[Touch-packages] [Bug 1388743] Re: iOS 8.1 - Could not start com.apple.mobile.installation_proxy!

2016-06-02 Thread ehcpdeveloper

How can I test it from xenial-proposed, while I use Ubuntu 15.10 ?
I can test it, if you tell in brief, how to do..

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

Title:
  iOS 8.1 - Could not start com.apple.mobile.installation_proxy!

Status in libimobiledevice package in Ubuntu:
  Fix Released
Status in libimobiledevice source package in Xenial:
  Fix Committed

Bug description:
  * Impact
  When running ideviceinstaller -l, I get the following error:
  Could not start com.apple.mobile.installation_proxy!

  * Test case
  connect an iOS >8 device and try to use ideviceinstaller

  * Regression potential
  It's fixing code that was not working before, should create any new issue

  
  

  
  Pairing works and I can mount the phone using iFuse. iPhone 4S, iOS 8.1
  libimobiledevice is probably outdated.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ideviceinstaller 1.0.1-0.2build1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Nov  3 09:33:21 2014
  InstallationDate: Installed on 2014-11-02 (0 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: ideviceinstaller
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1583624] Re: Mir cannot open a tty when started by lightdm

2016-06-02 Thread Josh Arenson

Here is mir-greeter.log using your instrumented lightdm and changing the
unity8 seat type to unity.

http://pastebin.ubuntu.com/16932129/

Thoughts?

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

Title:
  Mir cannot open a tty when started by lightdm

Status in Light Display Manager:
  In Progress
Status in Light Display Manager 1.18 series:
  In Progress
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Xenial:
  Triaged

Bug description:
  From mir-greeter.log (and with minor instrumentation from RAOF)

  ERROR: QMirServer - Mir failed to start
  qtmir.screens: ScreenController::ScreenController
  qtmir.mir: MirServer created
  qtmir.mir: Command line arguments passed to Qt: ("/usr/bin/unity8", 
"--mode=greeter")
  ERROR: 
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/server/graphics/default_configuration.cpp(133):
 Throw in function 
mir::DefaultServerConfiguration::the_graphics_platform()::
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Exception while creating graphics platform
  ERROR: 
/home/josh/Documents/mir/verbose-error-for-vt-finding/src/platforms/mesa/server/kms/linux_virtual_terminal.cpp(238):
 Throw in function int 
mir::graphics::mesa::LinuxVirtualTerminal::find_active_vt_number()
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Failed to find the current VT. Tried:
/dev/tty0:
Failed to open read-only: Permission denied
Failed to open write-only: Permission denied
/dev/tty:
Failed to open read-only: No such device or address
Failed to open write-only: No such device or address

  
  This occurs when trying to start the unity8 greeter under unity system 
compositor

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

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

[Touch-packages] [Bug 1549733] Re: SystemSettings Language view: hitting Space on HW keyboard triggers switch even when it (or its list item) does not show any visual focus frame

There's (currently) no bi-directional connection between keyboard input
and the focus ring - the focus ring shows in response to (Shift)Tab and
arrows in context of a *ListView. As the most basic example, any
(Abstract)Button can be clicked, thus have activeFocus and receive
keyboard input as described here, this was true even before the focus
ring existed.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  SystemSettings Language view: hitting Space on HW keyboard
  triggers switch even when it (or its list item) does not show any
  visual focus frame

Status in Canonical System Image:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Confirmed

Bug description:
  Nexus7, rc-proposed, r373

  Ubuntu UI Toolkit version r1795

  How to reproduce:
  1) Connect bluetooth keyboard
  2) Open system settings
  3) Open Language & Text view
  4) Press tab until the n-th switch shows its focus frame
  5) Now tap (using touchscreen) on the m-th list item, with  m < n (tap on the 
list item, not on the switch of that list item)
  NOTE: It is important that m < n, the bug will not trigger on listitems that 
have not been focused at least once!
  6) At this point the focus frame around the n-th switch has disappeared
  7) Now press Space on the keyboard

  Expected outcome:
  Nothing, because there is no focus frame anywhere on the screen

  Actual outcome:
  The switch of the m-th list item is triggered, even though that list item or 
switch were not showing any focus frame

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

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

[Touch-packages] [Bug 1583543] Re: Scrollbars overlap TextArea frame

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Scrollbars overlap TextArea frame

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  As bug 1526726 was merged prematurely staging has working scrollbars
  in TextArea but most importantly the scrollbars overlap the frame of
  the TextArea. This needs to be fixed asap - worst case it needs to be
  reverted before the next OTA.

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

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

[Touch-packages] [Bug 1585625] Re: Text fields must change mouse pointer

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Text fields must change mouse pointer

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Switch to desktop mode.
  - Open webbrowser app.
  - Move the mouse to the address bar.

  Expected result.
  - Entering a text field, the mouse changes to "finger" pointer.

  Actual result.
  - Mouse icon remains.

  Mouse icon changes when going over a link with latest rc-proposed.

  Setting the mouse icon was enabled in Unity8 in this silo
  https://launchpad.net/bugs/1447839

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

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

[Touch-packages] [Bug 1587762] Re: systemd-networkd-resolvconf-update.service incorrectly published domain limited DNS servers to /etc/resolv.conf

This bug was fixed in the package systemd - 230-2git1

---
systemd (230-2git1) yakkety; urgency=medium

  [ Martin Pitt ]
  * debian/tests/boot-and-services: Adjust test_tmp_mount() for fixed
systemctl exit code for "unit not found" in upstream commit ca473d57.
  * debian/tests/boot-and-services, test_no_failed(): Show journal of failed
units.
  * debian/extra/init-functions.d/40-systemd: Adjust to changed systemctl
show behaviour in 231: now this fails for nonexisting units instead of
succeeding with "not-found". Make the code compatible to both for now.
  * resolved: Disable DNSSEC by default again, until the various crashes get
fixed. (LP: #1587727, #1587740, #1587762, #1587740)
  * Fix networkd integration with resolvconf for domain-limited DNS servers,
so that these don't appear as global nameservers in resolv.conf. Thanks
Andy Whitcroft for the initial fix! Add corresponding test case to
debian/tests/networkd. (LP: #1587762)

  [ Michael Biebl ]
  * Add "systemctl daemon-reload" to lsb init-functions hook if the LoadState
of a service is "not-found". This will run systemd-sysv-generator, so SysV
init scripts that aren't installed by the package manager should be picked
up automatically. (Closes: #825913)

 -- Martin Pitt   Thu, 02 Jun 2016 11:18:32
+0200

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

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

Title:
  systemd-networkd-resolvconf-update.service incorrectly published
  domain limited DNS servers to /etc/resolv.conf

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  When configuring networkd to supply DNS information for resolved for a
  DNS server which is to only be used for specific domains only (routed
  DNS) the DNS server incorrectly gets added to /etc/resolv.conf as a
  global DNS server.

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

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

[Touch-packages] [Bug 1587740] Re: systemd-resolved crashed: Assertion '*_head == _item' failed at ../src/resolve/resolved-dns-transaction.c:94, function dns_transaction_free().

This bug was fixed in the package systemd - 230-2git1

---
systemd (230-2git1) yakkety; urgency=medium

  [ Martin Pitt ]
  * debian/tests/boot-and-services: Adjust test_tmp_mount() for fixed
systemctl exit code for "unit not found" in upstream commit ca473d57.
  * debian/tests/boot-and-services, test_no_failed(): Show journal of failed
units.
  * debian/extra/init-functions.d/40-systemd: Adjust to changed systemctl
show behaviour in 231: now this fails for nonexisting units instead of
succeeding with "not-found". Make the code compatible to both for now.
  * resolved: Disable DNSSEC by default again, until the various crashes get
fixed. (LP: #1587727, #1587740, #1587762, #1587740)
  * Fix networkd integration with resolvconf for domain-limited DNS servers,
so that these don't appear as global nameservers in resolv.conf. Thanks
Andy Whitcroft for the initial fix! Add corresponding test case to
debian/tests/networkd. (LP: #1587762)

  [ Michael Biebl ]
  * Add "systemctl daemon-reload" to lsb init-functions hook if the LoadState
of a service is "not-found". This will run systemd-sysv-generator, so SysV
init scripts that aren't installed by the package manager should be picked
up automatically. (Closes: #825913)

 -- Martin Pitt   Thu, 02 Jun 2016 11:18:32
+0200

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

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

Title:
  systemd-resolved crashed: Assertion '*_head == _item' failed at
  ../src/resolve/resolved-dns-transaction.c:94, function
  dns_transaction_free().

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Reached desktop when error came up. System was just started up

  https://github.com/systemd/systemd/issues/2942

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 230-1git1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Wed Jun  1 08:48:49 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2016-05-31 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160529)
  MachineType: Hewlett-Packard HPE-520sc
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=d38e5967-3b2c-43c7-965f-e90d52f4bb3d ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf

   3 overridden configuration files found.
  Title: systemd-resolved crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/04/2011
  dmi.bios.vendor: AMI
  dmi.bios.version: 7.13
  dmi.board.name: 2AB6
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.04
  dmi.chassis.asset.tag: CZC122BR03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr7.13:bd05/04/2011:svnHewlett-Packard:pnHPE-520sc:pvr1.04:rvnPEGATRONCORPORATION:rn2AB6:rvr1.04:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HPE-520sc
  dmi.product.version: 1.04
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1581027] Re: UCListItem doesn't handle Enter/Return/Space to click/trigger

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

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

Title:
  UCListItem doesn't handle Enter/Return/Space to click/trigger

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  Just like UCAbstractButton, it should be possible to press Enter,
  Return or Space to invoke the clicked signal or trigger the action
  equivalent to a tap or click on the item.

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

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

[Touch-packages] [Bug 1581026] Re: UCAbstractButton doesn't accept key events

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

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

Title:
  UCAbstractButton doesn't accept key events

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  UCAbstractButton does supporting Enter, Return and Space to emit
  clicked and trigger respectively. However it never accepts the event
  which means in a composited component such as a ComboButton the parent
  handles the same event as well.

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

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

[Touch-packages] [Bug 1587727] Re: systemd-resolved assert failure: * Error in `/lib/systemd/systemd-resolved': double free or corruption (!prev): 0x82072e88 *

This bug was fixed in the package systemd - 230-2git1

---
systemd (230-2git1) yakkety; urgency=medium

  [ Martin Pitt ]
  * debian/tests/boot-and-services: Adjust test_tmp_mount() for fixed
systemctl exit code for "unit not found" in upstream commit ca473d57.
  * debian/tests/boot-and-services, test_no_failed(): Show journal of failed
units.
  * debian/extra/init-functions.d/40-systemd: Adjust to changed systemctl
show behaviour in 231: now this fails for nonexisting units instead of
succeeding with "not-found". Make the code compatible to both for now.
  * resolved: Disable DNSSEC by default again, until the various crashes get
fixed. (LP: #1587727, #1587740, #1587762, #1587740)
  * Fix networkd integration with resolvconf for domain-limited DNS servers,
so that these don't appear as global nameservers in resolv.conf. Thanks
Andy Whitcroft for the initial fix! Add corresponding test case to
debian/tests/networkd. (LP: #1587762)

  [ Michael Biebl ]
  * Add "systemctl daemon-reload" to lsb init-functions hook if the LoadState
of a service is "not-found". This will run systemd-sysv-generator, so SysV
init scripts that aren't installed by the package manager should be picked
up automatically. (Closes: #825913)

 -- Martin Pitt   Thu, 02 Jun 2016 11:18:32
+0200

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

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

Title:
  systemd-resolved assert failure: *** Error in `/lib/systemd/systemd-
  resolved': double free or corruption (!prev): 0x82072e88 ***

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  please give me solution

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 230-1git1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic i686
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: i386
  AssertionMessage: *** Error in `/lib/systemd/systemd-resolved': double free 
or corruption (!prev): 0x82072e88 ***
  Date: Wed Jun  1 03:14:27 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2016-03-25 (68 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MachineType: BIOSTAR Group A55MLV
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=663bc6f5-848e-4927-a48a-de6b72885f64 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __libc_message (do_abort=2, fmt=0xb75cde28 "*** Error in `%s': %s: 0x%s 
***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (action=, str=0xb75cde98 "double free or 
corruption (!prev)", ptr=, ar_ptr=0xb7620780 ) at 
malloc.c:5007
   _int_free (av=0xb7620780 , p=, have_lock=0) at 
malloc.c:3868
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Title: systemd-resolved assert failure: *** Error in 
`/lib/systemd/systemd-resolved': double free or corruption (!prev): 0x82072e88 
***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 02/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: None
  dmi.board.name: A55MLV
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd02/20/2012:svnBIOSTARGroup:pnA55MLV:pvr:rvnBIOSTARGroup:rnA55MLV:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: A55MLV
  dmi.sys.vendor: BIOSTAR Group

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

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

[Touch-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

I went tested the patches for 1585863, but still saw the issue.

** This bug is no longer a duplicate of bug 1585863
   WiFi malfunction after suspend & resume stress

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change:

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress

The above patches do not resolve this issue for my machine.  de-duping
1576747.

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

Title:
  WiFi malfunction after suspend & resume stress

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)   

 
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2

 
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=10 --s3-max-delay=10 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

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

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

[Touch-packages] [Bug 1574347] Re: [SRU] Re-read the link type if the name changed

2016-06-02 Thread Mathieu Trudel-Lapierre

Cip Man, you're seeing a different issue with the wireless device. This
isn't the same bug.

What gets fixed here is that wireless devices may be seen as *ethernet*
rather than wireless, because of confusion in NM in detecting the device
type -- it doesn't mean you definitely would have a list of wireless
networks if the wireless device doesn't do the scanning properly.

The correct way to verify this bug here is to use 'nmcli dev' and to see
whether a device that is supposed to be a wireless device is being
listed as "ethernet".

Ideally, please file your own, separate bug so we can fix that as well.

** Description changed:

  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet
  
- Steps to reproduce: -
+ [Testcase]
+ 1. Boot the system. It should include a wireless device.
+ 2. In a terminal, run 'nmcli dev'.
+ 3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".
  
- 1. Connect to a WiFi AP.
- 2. Switch off the AP OR switch off the wifi in the computer.
- 3. Switch point (2) back on.
- 4. The network will get connected to the AP it was connected to in point (1).
+ After upgrading to the new version, the repeating the above steps should
+ give expected behavior.
+ 
+ [Regression Potential]
+ Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.
+ 
+ ---
  
  Problems:-
  
  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.
  
  Temporary Workaround:-
  Log out and again log back in.
- 
- [Testcase]
- 
- After upgrading to the new version, the repeating the above steps should
- give expected behavior.
- 
- [Regression Potential]
- Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

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

Title:
  [SRU] Re-read the link type if the name changed

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

  ---

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

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

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

[Touch-packages] [Bug 1477350] Re: Rgression building sbsigntool with binutils >= 2.22-6ubuntu1.2 in precise

2016-06-02 Thread Steve Beattie

I've pushed a version of binutils that in local testing fixes the
segfault in objcopy on pecoff binaries, addressing the sbsigntool FTBFS,
to the ubuntu-security-proposed ppa https://launchpad.net/~ubuntu-
security-proposed/+archive/ubuntu/ppa/+packages . If people could test
these to confirm and verify they're not seeing any weirdness, I'll push
it to precise-security next week.

Thanks!

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

Title:
  Rgression building sbsigntool with binutils >= 2.22-6ubuntu1.2 in
  precise

Status in binutils package in Ubuntu:
  Invalid
Status in binutils source package in Precise:
  Confirmed

Bug description:
  objcopy segfaults in precise when running the sbsigntool testsuite on
  i386 with binutils >= 2.22-6ubuntu1.2

  See the attachment for output and downgrade iterations to show that
  1.1 works, while 1.2 and 1.3 don't.

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

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

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

2016-06-02 Thread Jamie Strandboge

Adding xenial task and marking triaged since a fix is available in
yakkety. Who will be providing this update?

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

Title:
  Deny audio recording for all snap applications

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

Bug description:
  Until we have a proper trust-store implementation with snappy and on
  the desktop/ubuntu core we want pulseaudio to simply deny any audio
  recording request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

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

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

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

2016-06-02 Thread Jamie Strandboge

Thanks for working on this! Per the snappy team, this will also need a
SRU for xenial.

** Also affects: pulseaudio (Ubuntu Yakkety)
   Importance: High
 Assignee: Luke Yelavich (themuso)
   Status: Fix Released

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

** Tags added: snapd-interface

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

Title:
  Deny audio recording for all snap applications

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

Bug description:
  Until we have a proper trust-store implementation with snappy and on
  the desktop/ubuntu core we want pulseaudio to simply deny any audio
  recording request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

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

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

[Touch-packages] [Bug 1588533] [NEW] Mobile Data Network not working after screen is off for more then 2 min

2016-06-02 Thread siucdude

Public bug reported:

With OTA-11 the Mobile Network 3G and H do not come back into working
mode after MX4 comes back from turning off the screen.

Example:
I reboot the MX4 and when it powers up all is working I get WiFi and Mobile 
Network 3G working great.
I press the button to turn off the screen and leave it off for 2 or more 
minutes, when I turn it back on and unlock the device the Data network is not 
working. 

I can make calls and SMS but MMS and Data has no connection, at this
point i can toggle the Data switch in the mobile configuration or put
the phone into airplane mode and back into active and it works until
next time.

Thank You

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

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

Title:
  Mobile Data Network not working after screen is off for more then 2
  min

Status in indicator-network package in Ubuntu:
  New

Bug description:
  With OTA-11 the Mobile Network 3G and H do not come back into working
  mode after MX4 comes back from turning off the screen.

  Example:
  I reboot the MX4 and when it powers up all is working I get WiFi and Mobile 
Network 3G working great.
  I press the button to turn off the screen and leave it off for 2 or more 
minutes, when I turn it back on and unlock the device the Data network is not 
working. 

  I can make calls and SMS but MMS and Data has no connection, at this
  point i can toggle the Data switch in the mobile configuration or put
  the phone into airplane mode and back into active and it works until
  next time.

  Thank You

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

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

[Touch-packages] [Bug 1582947] Re: Issue with Multiple Displays (AMD Cards / 16.04)

2016-06-02 Thread Tom Winter

** Description changed:

  I have two identical AMD Cards and whichever card I name in the BIOS as
  primary correctly displays the desktop and allows me to orient the
  desktop directly (landscape, portrait, etc).
  
  The secondary card will not allow the settings to be changed in anyway.
  Performance is not ideal although the displays on the secondary card do
  work and applications will run on them.
  
  While I am a relatively new user to Ubuntu I am quite willing to help
  provide further information for de-bugging purposes.
  
  Please note that I had the same issue in 14.04 even after installing the
  FGLRX drivers.
  
  I appreciate any help that can be provided.
  
  LSPCI Info:
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Caicos XTX [Radeon HD 8490 / R5 235X OEM] (prog-if 00 [VGA controller])
-   Subsystem: Dell Caicos XTX [Radeon HD 8490 / R5 235X OEM]
-   Flags: bus master, fast devsel, latency 0, IRQ 32
-   Memory at e000 (64-bit, prefetchable) [size=256M]
-   Memory at f7d2 (64-bit, non-prefetchable) [size=128K]
-   I/O ports at e000 [size=256]
-   Expansion ROM at f7d0 [disabled] [size=128K]
-   Capabilities: 
-   Kernel driver in use: radeon
-   Kernel modules: radeon
+  Subsystem: Dell Caicos XTX [Radeon HD 8490 / R5 235X OEM]
+  Flags: bus master, fast devsel, latency 0, IRQ 32
+  Memory at e000 (64-bit, prefetchable) [size=256M]
+  Memory at f7d2 (64-bit, non-prefetchable) [size=128K]
+  I/O ports at e000 [size=256]
+  Expansion ROM at f7d0 [disabled] [size=128K]
+  Capabilities: 
+  Kernel driver in use: radeon
+  Kernel modules: radeon
  
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI 
Audio [Radeon HD 6400 Series]
-   Subsystem: Dell Caicos HDMI Audio [Radeon HD 6400 Series]
-   Flags: bus master, fast devsel, latency 0, IRQ 37
-   Memory at f7d4 (64-bit, non-prefetchable) [size=16K]
-   Capabilities: 
-   Kernel driver in use: snd_hda_intel
-   Kernel modules: snd_hda_intel
+  Subsystem: Dell Caicos HDMI Audio [Radeon HD 6400 Series]
+  Flags: bus master, fast devsel, latency 0, IRQ 37
+  Memory at f7d4 (64-bit, non-prefetchable) [size=16K]
+  Capabilities: 
+  Kernel driver in use: snd_hda_intel
+  Kernel modules: snd_hda_intel
  
  03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Caicos XTX [Radeon HD 8490 / R5 235X OEM] (prog-if 00 [VGA controller])
-   Subsystem: Dell Caicos XTX [Radeon HD 8490 / R5 235X OEM]
-   Flags: bus master, fast devsel, latency 0, IRQ 34
-   Memory at d000 (64-bit, prefetchable) [size=256M]
-   Memory at f7c2 (64-bit, non-prefetchable) [size=128K]
-   I/O ports at d000 [size=256]
-   Expansion ROM at f7c0 [disabled] [size=128K]
-   Capabilities: 
-   Kernel driver in use: radeon
-   Kernel modules: radeon
+  Subsystem: Dell Caicos XTX [Radeon HD 8490 / R5 235X OEM]
+  Flags: bus master, fast devsel, latency 0, IRQ 34
+  Memory at d000 (64-bit, prefetchable) [size=256M]
+  Memory at f7c2 (64-bit, non-prefetchable) [size=128K]
+  I/O ports at d000 [size=256]
+  Expansion ROM at f7c0 [disabled] [size=128K]
+  Capabilities: 
+  Kernel driver in use: radeon
+  Kernel modules: radeon
  
  03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI 
Audio [Radeon HD 6400 Series]
-   Subsystem: Dell Caicos HDMI Audio [Radeon HD 6400 Series]
-   Flags: bus master, fast devsel, latency 0, IRQ 38
-   Memory at f7c4 (64-bit, non-prefetchable) [size=16K]
-   Capabilities: 
-   Kernel driver in use: snd_hda_intel
-   Kernel modules: snd_hda_intel
+  Subsystem: Dell Caicos HDMI Audio [Radeon HD 6400 Series]
+  Flags: bus master, fast devsel, latency 0, IRQ 38
+  Memory at f7c4 (64-bit, non-prefetchable) [size=16K]
+  Capabilities: 
+  Kernel driver in use: snd_hda_intel
+  Kernel modules: snd_hda_intel
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May 17 19:57:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  InstallationDate: Installed on 2016-05-05 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex 9020
  ProcEnviron:
-  LANGUAGE=en_US
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US
+

[Touch-packages] [Bug 1586539] Re: Major screen flickering in Chromium and Google Chrome

2016-06-02 Thread Vasya Pupkin

** Description changed:

  On a fresh installation of Ubuntu 16.04 I noticed major screen
  flickering issues in Chromium and Google Chrome browsers. Since this
  never happened in Ubuntu 15.10 with exactly the same Google Chrome
  binary, I believe, bug is caused by something that was added/updated in
  16.04. I came across some discussions where different people suggested
  that it is related to new X.Org version.
  
  Here's a video to show what is happening:
  https://youtu.be/l21WsKz3fZc?t=45s
  
  I could fix this flickering with --disable-gpu-compositing switch, but
  this slows down page drawing significantly so it can't be considered a
  workaround. There is also a Chromium bug report:
  https://bugs.chromium.org/p/chromium/issues/detail?id=606152, but I
  don't think they will fix an Ubuntu-specific bug.
  
+ Update: this indeed happens only when browser window is maximized.
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
-  
+ 
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 28 00:01:20 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
-  vboxhost, 5.0.20, 4.4.0-22-generic, x86_64: installed
-  vboxhost, 5.0.20, 4.6.0-040600-generic, x86_64: installed
+  vboxhost, 5.0.20, 4.4.0-22-generic, x86_64: installed
+  vboxhost, 5.0.20, 4.6.0-040600-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13bd]
+  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13bd]
  InstallationDate: Installed on 2016-05-01 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-040600-generic 
root=UUID=172b2d49-444a-466b-ab91-b74605125b29 ro quiet splash rootfstype=ext4 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun May 22 23:28:15 2016
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id5126 
-  vendor SHP
+  product id5126
+  vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

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

Title:
  Major screen flickering in Chromium and Google Chrome

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  On a fresh installation of Ubuntu 16.04 I noticed major screen
  flickering issues in Chromium and Google Chrome browsers. Since this
  never happened in Ubuntu 15.10 with exactly the same Google Chrome
  binary, I believe, bug is

[Touch-packages] [Bug 1563398] Re: Set the front camera as the default for video media requests

2016-06-02 Thread Peter Bittner

I had the impression that this feature/change would make it into OTA-11.
I updated yesterday and the rear camera is still the default.

Canonical could have cheering from technology press with sweet working
video chat via the Appear.in webapp. You guys don't seem to want that.
Why? What's wrong?

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

Title:
  Set the front camera as the default for video media requests

Status in Canonical System Image:
  In Progress
Status in webapps-sprint:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  At the moment, the selected camera (in form factors having multiple
  ones) defaults to the back camera which does not work very well for
  cases like hangouts, the container and the browser should default to
  the front camera.

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

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

[Touch-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

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

This appears to be getting some progress via 1585863, so I'm marking it
as a dupe, even though this one is older.

** This bug has been marked a duplicate of bug 1585863
   WiFi malfunction after suspend & resume stress

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress

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

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

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

Title:
  WiFi malfunction after suspend & resume stress

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)   

 
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2

 
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=10 --s3-max-delay=10 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

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

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

[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress

This really should have been worked via one of the myriad of other older
open bugs related to this, like 1576747.  I'll start duping against this
bug.

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

Title:
  WiFi malfunction after suspend & resume stress

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)   

 
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2

 
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=10 --s3-max-delay=10 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

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

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

[Touch-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fctix, ...)

2016-06-02 Thread Brian Murray

Hello Sebastien, or anyone else affected,

Accepted snapd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/snapd/2.0.6 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: snapd (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags removed: verification-failed

** Tags added: verification-needed

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

Title:
  Snap blocks access to system input methods (ibus, fctix, ...)

Status in apparmor package in Ubuntu:
  In Progress
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Triaged
Status in im-config source package in Xenial:
  In Progress
Status in snapd source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  In Progress
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Confirmed

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in progress. Currently the change should not
  regress snapdsbehavior due to other issues surrounding using ibus
  unrelated to security policy.

  = Original description =
  Currently snaps can't access ibus/fcitx from the system, do we need a 
interface for input methods there?

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

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

[Touch-packages] [Bug 1588524] [NEW] FIPS_mode_set reports incorrect error message

2016-06-02 Thread Spencer Jackson

Public bug reported:

Hi! Some integration tests we run attempt to enable FIPS mode in
OpenSSL, and assert that either our software continues to work, or that
the error message emitted by OpenSSL is related to missing the FIPS
module.

On Ubuntu 14.10, running FIPS_mode_set fails and produces an error like:
140225357260448:error:0F06D065:common libcrypto routines:FIPS_mode_set:fips 
mode not supported:o_fips.c:92:

On Ubuntu 16.04 running OpenSSL/libssl1.0.0 version 1.0.2g-1ubuntu4.1,
FIPS_mode_set fails, but does not produce an error message.

I have attached a C file which, when executed on both these platforms,
will demonstrate this behavior.

I believe this may have been introduced by this ticket: 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1553309
It provides a patch called openssl-1.0.2g-ubuntu-fips-cleanup.patch which 
includes this statement:
+@@ -443,6 +430,7 @@ int FIPS_module_mode_set(int onoff, const char *auth)
+ fips_selftest_fail = 0;
+ ret = 1;
+  end:
++ERR_clear_error(); /* clear above err msg; fips mode disabled for now */
+ fips_clear_owning_thread();
+ fips_w_unlock();
+ return ret;

This appears to be clearing the error messages we're asserting on before
returning from FIPS_module_mode_set.

For reference, here is our ticket where we are tracking this issue:
https://jira.mongodb.org/browse/SERVER-24350

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

** Attachment added: "openssl_fips_test.c"
   
https://bugs.launchpad.net/bugs/1588524/+attachment/4675503/+files/openssl_fips_test.c

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

Title:
  FIPS_mode_set reports incorrect error message

Status in openssl package in Ubuntu:
  New

Bug description:
  Hi! Some integration tests we run attempt to enable FIPS mode in
  OpenSSL, and assert that either our software continues to work, or
  that the error message emitted by OpenSSL is related to missing the
  FIPS module.

  On Ubuntu 14.10, running FIPS_mode_set fails and produces an error like:
  140225357260448:error:0F06D065:common libcrypto routines:FIPS_mode_set:fips 
mode not supported:o_fips.c:92:

  On Ubuntu 16.04 running OpenSSL/libssl1.0.0 version 1.0.2g-1ubuntu4.1,
  FIPS_mode_set fails, but does not produce an error message.

  I have attached a C file which, when executed on both these platforms,
  will demonstrate this behavior.

  I believe this may have been introduced by this ticket: 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1553309
  It provides a patch called openssl-1.0.2g-ubuntu-fips-cleanup.patch which 
includes this statement:
  +@@ -443,6 +430,7 @@ int FIPS_module_mode_set(int onoff, const char *auth)
  + fips_selftest_fail = 0;
  + ret = 1;
  +  end:
  ++ERR_clear_error(); /* clear above err msg; fips mode disabled for now */
  + fips_clear_owning_thread();
  + fips_w_unlock();
  + return ret;

  This appears to be clearing the error messages we're asserting on
  before returning from FIPS_module_mode_set.

  For reference, here is our ticket where we are tracking this issue:
  https://jira.mongodb.org/browse/SERVER-24350

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

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

[Touch-packages] [Bug 1586991] Re: systemd-resolved crashed with SIGSEGV in dns_transaction_cache_answer()

Yes, it's reported upstream
(https://github.com/systemd/systemd/issues/2942) and the package
currently waiting in yakkety-proposed fixes this (or rather, works
around this by disabling DNSSEC again for the time being).

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

Title:
  systemd-resolved crashed with SIGSEGV in
  dns_transaction_cache_answer()

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Got that crash with the newer network-manager 1.2.2-0ubuntu3 upgrade with a 
gnome-shell session.
  Reinstalling network-manager also ends with that crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 230-1git1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  Date: Mon May 30 11:58:58 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf

   3 overridden configuration files found.
  Title: systemd-resolved crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Touch-packages] [Bug 1447395] Re: [browser] Zoom needed for better readability

** Branch linked: lp:~oxide-developers/oxide/packaging.yakkety

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

Title:
  [browser] Zoom needed for better readability

Status in Canonical System Image:
  In Progress
Status in Canonical Pocket Desktop:
  New
Status in Oxide:
  Fix Released
Status in Ubuntu UX:
  New
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Missing: Many people need a customizable zoom or at least text size
  for websites because they need bigger text (and pictures) for easy
  reading. The zoom should not result in horizontal scrolling but wrap
  text on the end of line.

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

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

[Touch-packages] [Bug 1556764] Re: WebView.TouchSelectionController needs a hide() method

** Branch linked: lp:~oxide-developers/oxide/packaging.yakkety

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

Title:
  WebView.TouchSelectionController needs a hide() method

Status in Canonical System Image:
  In Progress
Status in Oxide:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Typically, when a touch selection is active, a quick menu with 
selectall/copy/paste options is displayed.
  Per design request, we need to hide that menu when one of its actions is 
tapped, only to show it again when the selection is tapped again. We need the 
touch selection controller to expose an additional method for that.

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

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

[Touch-packages] [Bug 1565063] Re: Update the chromium version in the user agent

** Branch linked: lp:~oxide-developers/oxide/packaging.yakkety

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

Title:
  Update the chromium version in the user agent

Status in Canonical System Image:
  In Progress
Status in Oxide:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  We have never updated the version, which is 35, and now we are based on 49
  While this may not have any impact it does reflect the core support we have, 
and its possible some sites may check it.

  Ideally we would query oxide for this dynamically.

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

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

[Touch-packages] [Bug 1556762] Re: WebView.TouchSelectionController needs a 'handleDragInProgress' property

** Branch linked: lp:~oxide-developers/oxide/packaging.yakkety

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

Title:
  WebView.TouchSelectionController needs a 'handleDragInProgress'
  property

Status in Oxide:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Typically, when a touch selection is active, a quick menu with 
selectall/copy/paste options is displayed.
  Per design request, we need to temporarily hide that menu while a handle drag 
is in progress to resize the selection. We need the touch selection controller 
to expose an additional property for that.

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

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

[Touch-packages] [Bug 1556658] Re: beforeunload handlers can't specify message text in Chromium 51

** Branch linked: lp:~oxide-developers/oxide/packaging.yakkety

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

Title:
  beforeunload handlers can't specify message text in Chromium 51

Status in Oxide:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Chromium has dropped the ability for beforeunload handlers to set the
  dialog message text. Instead, Chromium will display a stock message,
  making it behave the same as Firefox. This will affect Oxide too -
  beforeunload dialog components will be created with an empty message
  string.

  I assume webbrowser-app already handles an empty message string by
  displaying its own text, but given that this API exists in Oxide, I
  wonder whether we should specify a stock message in Oxide and expose
  it via the existing API.

  See:
  
https://chromium.googlesource.com/chromium/src.git/+/141dbc132f8aa2588fad4cf50fbfd7a319234b61
  https://bugs.chromium.org/p/chromium/issues/detail?id=587940

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

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

[Touch-packages] [Bug 1565685] Re: Ubuntu-emulator: Crash in new welcome wizard / browser

** Branch linked: lp:~oxide-developers/oxide/packaging.yakkety

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

Title:
  Ubuntu-emulator: Crash in new welcome wizard / browser

Status in Canonical System Image:
  Fix Released
Status in Oxide:
  Fix Released
Status in Oxide 1.14 series:
  Fix Released
Status in oxide-qt package in Ubuntu:
  Fix Released
Status in phablet-tools package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. Install ubuntu-emulator
  2. sudo ubuntu-emulator create --channel ubuntu-touch/rc-proposed/ubuntu 
rc-test
  3. ubuntu-emulator run rc-test
  4. Doesn't complete the welcome wizard

  Also, in emulator:
  1. mkdir ~/.config/ubuntu-system-settings/
  2. touch ~/.config/ubuntu-system-settings/wizard-has-run
  3. launch webbrowser-app
  4. crashes on start up

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

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

[Touch-packages] [Bug 1568889] Re: OTA and u-d-f fail if image is too big for the system partition

2016-06-02 Thread Pat McGowan

@alan I did get 1GB back with a simple flash, wipe and bootstrap did not
really improve on that on this device. Lets see the results for df -h
when you do. I have 1.7GB installed in that partition.

You could also poke around in places like /var/log to see if there are
old files remaining.

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

Title:
  OTA and u-d-f fail if image is too big for the system partition

Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  New
Status in system-image package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  On Meizu MX4 upgrade from OTA-9.1 to OTA-10 fails.
  Upgrade downloads normally, phone restarts and starts system upgrade and 
after a while it freezes with strange icon (small microchip with red sign on it)

  When you turn off the phone and start it again it still presents itself as 
OTA-9.1 and again it founds and offer upgrade.
  Anyway some changes from OTA-10 seems to be applied, because I can see design 
changes, copy function in web browser etc.

  It's reproducible on my phone any time I try to upgrade. If I can help
  with output of some log, or anything else, please let me know.

  Well described here by Lars Kristian Wichmann Hansen:
  
http://askubuntu.com/questions/754963/upgrade-meizu-mx4-ubuntu-edition-to-ota-10-fails

  * u-d-f case described in bug 1582325

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

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

[Touch-packages] [Bug 1570511] Re: Select All shows up when replying to gmail message

** Branch linked: lp:~oxide-developers/oxide/packaging.yakkety

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

Title:
  Select All shows up when replying to gmail message

Status in Canonical System Image:
  In Progress
Status in Oxide:
  Fix Released
Status in Oxide 1.15 series:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  open gmail webapp (or in browser), try to reply to a mail
  scroll to the top of the message and tap to begin typing

  expected result:
  - can start typing, no menu

  actual result:
  - can start typing but Select All menu is incorrectly displayed

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

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

[Touch-packages] [Bug 1588477] Re: regression-update: systemd init behavior change

This is a direct consequence of bug 1575572. In particular this part:

runcmd:
- [ systemctl, start, dcos-docker-install.service ]

In 16.04 final this was not actually working. I. e. you asked for
starting this service, but it wasn't actually started. This got fixed in
bug 1575572, so that packages that you install in "packages:" or
"runcmd:" (which start services) or direct start requests like your's
from above now actually do what you asked it to.

So this is indeed a behaviour change, but I fail to see how it is a
regression and not a bug fix? I. e. can you clarify why you would expect
docker not to start despite your explicit runcmd to do so?

** Changed in: init-system-helpers (Ubuntu)
   Status: New => Incomplete

** Changed in: init-system-helpers (Ubuntu Xenial)
   Status: New => Incomplete

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

Title:
  regression-update: systemd init behavior change

Status in init-system-helpers package in Ubuntu:
  Incomplete
Status in init-system-helpers source package in Xenial:
  Incomplete

Bug description:
  regression-update for 1575572.

  After the time 1575572 was checked in we observed a behavior change in
  the systemd init.

  We have been able to repro the issue and can observe that dpkg seems
  to start docker on “16.04.201605310 Daily”, but not “16.04.201605280
  Daily”.

  The problem seems to be that in 16.04.201605310.Daily after  “dcos-
  docker-install.service” runs “Job for docker.service” can be seen
  trying to start docker.  On 16.04.0-LTS, it does not try to start
  docker while running “dcos-docker-install.service”.  Why is the binary
  being started now and not before?

  Below are the Contents of the cloud-init, with the 3 docker
  installation files that fail:

  Contents of Cloud-Init, show relationship between Systemd files
  #cloud-config

  write_files:
  - path: /etc/systemd/system/dcos-docker-install.service
    permissions: "0644"
    content: |
  [Unit]
  After=network-online.target
  Wants=network-online.target
  [Service]
  Type=oneshot
  Environment=DEBIAN_FRONTEND=noninteractive
  StandardOutput=journal+console
  StandardError=journal+console
  ExecStartPre=/usr/bin/curl -fLsSv --retry 20 -Y 10 -y 60 -o 
/tmp/d.deb 
https://az837203.vo.msecnd.net/dcos-deps/docker-engine_1.11.0-0~xenial_amd64.deb
  ExecStart=/usr/bin/bash -c "try=1;until dpkg -D3 -i /tmp/d.deb || ((try > 
5));do echo retry $((try++));sleep 120;done;systemctl --now start docker"
  - path: /etc/systemd/system/docker.service.d/execstart.conf
    permissions: "0644"
    content: |
  [Service]
  Restart=always
  StartLimitInterval=0
  RestartqSec=15
  ExecStart=
  ExecStart=/usr/bin/docker daemon -H fd:// --storage-driver=overlay
  - path: /etc/systemd/system/docker.socket
    permissions: "0644"
    content: |
  [Unit]
  PartOf=docker.service
  [Socket]
  ListenStream=/var/run/docker.sock
  SocketMode=0660
  SocketUser=root
  SocketGroup=docker
  ListenStream=2375
  BindIPv6Only=both
  [Install]
  WantedBy=sockets.target
  runcmd:
  - [ ln, -s, /bin/rm, /usr/bin/rm ]
  - [ ln, -s, /bin/mkdir, /usr/bin/mkdir ]
  - [ ln, -s, /bin/tar, /usr/bin/tar ]
  - [ ln, -s, /bin/ln, /usr/bin/ln ]
  - [ ln, -s, /bin/cp, /usr/bin/cp ]
  - [ ln, -s, /bin/systemctl, /usr/bin/systemctl ]
  - [ ln, -s, /bin/mount, /usr/bin/mount ]
  - [ ln, -s, /bin/bash, /usr/bin/bash ]
  - [ systemctl, stop, resolvconf.service ]
  - [ systemctl, disable, resolvconf.service ]
  - [ systemctl, stop, lxc-net.service ]
  - [ systemctl, disable, lxc-net.service ]
  - [ systemctl, mask, lxc-net.service ]
  - [ systemctl, start, dcos-docker-install.service ]

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

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

[Touch-packages] [Bug 1586968] Re: Touch selection menu initially empty when focusing a text field

** Branch linked: lp:~oxide-developers/oxide/packaging.yakkety

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

Title:
  Touch selection menu initially empty when focusing a text field

Status in Oxide:
  Fix Released
Status in Oxide 1.15 series:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  This appears to be 100% reproducible when the device has just been rebooted 
(not always reproducible otherwise).
  Steps to reproduce:
   1) browse to e.g. http://pastebin.ubuntu.com
   2) long press on one of the text fields ("Poster:" or "Content:")
   3) wait for the touch selection menu to appear next to the insertion handle 
(note that at the moment there is a bug in oxide which also triggers the page 
context menu, dismissing it will get you the touch selection menu)

  Expected result: assuming the clipboard is empty (device just
  rebooted), the "Select All" action is the only one visible in the
  touch selection menu.

  Current result: no action is visible, the menu is empty (see attached
  screenshot).

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

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

[Touch-packages] [Bug 1586968] Re: Touch selection menu initially empty when focusing a text field

** Branch linked: lp:~oxide-developers/oxide/packaging.vivid.overlay

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

Title:
  Touch selection menu initially empty when focusing a text field

Status in Oxide:
  Fix Released
Status in Oxide 1.15 series:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  This appears to be 100% reproducible when the device has just been rebooted 
(not always reproducible otherwise).
  Steps to reproduce:
   1) browse to e.g. http://pastebin.ubuntu.com
   2) long press on one of the text fields ("Poster:" or "Content:")
   3) wait for the touch selection menu to appear next to the insertion handle 
(note that at the moment there is a bug in oxide which also triggers the page 
context menu, dismissing it will get you the touch selection menu)

  Expected result: assuming the clipboard is empty (device just
  rebooted), the "Select All" action is the only one visible in the
  touch selection menu.

  Current result: no action is visible, the menu is empty (see attached
  screenshot).

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

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

[Touch-packages] [Bug 1570511] Re: Select All shows up when replying to gmail message

** Branch linked: lp:~oxide-developers/oxide/packaging.vivid.overlay

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

Title:
  Select All shows up when replying to gmail message

Status in Canonical System Image:
  In Progress
Status in Oxide:
  Fix Released
Status in Oxide 1.15 series:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  open gmail webapp (or in browser), try to reply to a mail
  scroll to the top of the message and tap to begin typing

  expected result:
  - can start typing, no menu

  actual result:
  - can start typing but Select All menu is incorrectly displayed

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

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

[Touch-packages] [Bug 1588500] Re: Applications with permission for location claim they don't

2016-06-02 Thread Bob Harvey

Non-browser based app is absolutely fine (Réaltai)

** Attachment added: "screenshot20160602_204540291.png"
   
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1588500/+attachment/4675502/+files/screenshot20160602_204540291.png

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

Title:
  Applications with permission for location claim they don't

Status in location-service package in Ubuntu:
  New

Bug description:
  OTA11 - same problem on BQ4.5phone & M10 tablet.

  Hurray! Location works on the tablet at last.. HERE maps can get a
  position.

  But I can't use the location in the browser or a browser-like web
  app.. It used to work on the phone in OTA10.1

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

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

[Touch-packages] [Bug 1556658] Re: beforeunload handlers can't specify message text in Chromium 51