[Touch-packages] [Bug 1575191] Re: plus.google.com re-layouts horizontally when the top bar shows/hides

2016-04-28 Thread Daniel Bull
Actually I agree, it seems the correct solution is not to hide the
location bar on larger screens (which would be a UI improvement anyway
IMHO).

James the Google UI elements auto-hiding won't change the viewport size
or the width so that won't affect the scaling so that should be fine.

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

Title:
  plus.google.com re-layouts horizontally when the top bar shows/hides

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  Invalid
Status in Ubuntu UX:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Some sites have a menu bar at the top, which appears or disappears
  depending if you scroll up or down... the presence or absence of this
  bar causes the browser app to change it's scaling, and this means that
  scrolling up/down while browsing results in the device continually re-
  rendering as it re-scales the page...

  This badly afffects google+ and presumably other google properties...

  See example here:-

  https://www.youtube.com/watch?v=uYhu9v4aX6w

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

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


[Touch-packages] [Bug 1575191] Re: plus.google.com re-layouts horizontally when the top bar shows/hides

2016-04-27 Thread Daniel Bull
I can understand why google is changing the width based on the viewport height, 
there is some logic behind it... 
They want the page to render in a way that prevents posts being vertically 
cropped too much (which would result in the user only being able to view a 
small part of the post and having to scroll back and forth to read it or 
missing the picture or whatever). The way they are doing this is by changing 
the width of the contech which scales the overall page on most mobile browsers.

It looks like the issue is when you scroll down the browser
automatically hides the tab and location bar which then changes the
viewport size which then triggers the page to rescale. This wont only
happen on G+ this will happen on lost of sites. Sites don't expect the
viewport size to change unless the browser is actually being resized.

I'm not sure what the correct solution is but I would say one potential
(but perhaps not very clean solution) would be not to change the
viewport size when the tab/location bar is hidden if its a website which
requires a vertical scroll bar. Essentially pretend the viewport stays a
constant size even though in reality it has got larger. Like I said this
is not an ideal solution but chances are if you are on a website with a
vertical scroll bar the exact height shouldn't be hugely relevant
anyway.

The other option is as was mentioned to see how Android deals with it.
The location bar in Chrome on Android DOES hide but interestingly enough
only under certain circumstances. I noticed when looking at Google
results it didn't hide until I first tried to scroll up beyond the
limit.

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

Title:
  plus.google.com re-layouts horizontally when the top bar shows/hides

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  Invalid
Status in Ubuntu UX:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Some sites have a menu bar at the top, which appears or disappears
  depending if you scroll up or down... the presence or absence of this
  bar causes the browser app to change it's scaling, and this means that
  scrolling up/down while browsing results in the device continually re-
  rendering as it re-scales the page...

  This badly afffects google+ and presumably other google properties...

  See example here:-

  https://www.youtube.com/watch?v=uYhu9v4aX6w

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

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


[Touch-packages] [Bug 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting

2015-10-20 Thread Daniel Bull
I can confirm the same as what Stephen just said.
Servers rebooted overnight for the security patch and none of the LXC 
containers restarted or can be started.

lxc-start: conf.c: setup_pts: 1772 Permission denied - mount failed
'/dev/pts/ptmx'->'/dev/ptmx'

This is on a live 14.04 LTS server

Again I can confirm modifying the start-container file does not work

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

Title:
  lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66:
  AppArmor denies /dev/ptmx mounting

Status in linux package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed
Status in lxc source package in Trusty:
  Fix Committed

Bug description:
  We are seeing test suite failures under ADT testing with linux, linux-
  lts-utopic and linux-lts-vivid kernels:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_103318@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_103325@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151009_085841@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151009_091723@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_105332@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_114021@/log.gz

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

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


[Touch-packages] [Bug 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting

2015-10-20 Thread Daniel Bull
This seems to explain it, currently trying to teach myself apparmor to
find a temporary fix...

apps kernel: [  707.036112] audit: type=1400 audit(1445331859.865:41):
apparmor="DENIED" operation="mount" info="failed type match" error=-13
profile="/usr/bin/lxc-start" name="/dev/ptmx" pid=2746 comm="lxc-start"
srcname="/dev/pts/ptmx" flags="rw, bind"

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

Title:
  lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66:
  AppArmor denies /dev/ptmx mounting

Status in linux package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed
Status in lxc source package in Trusty:
  Fix Committed

Bug description:
  We are seeing test suite failures under ADT testing with linux, linux-
  lts-utopic and linux-lts-vivid kernels:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_103318@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_103325@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151009_085841@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151009_091723@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_105332@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_114021@/log.gz

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

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