from:"F"

Hi,
I don't know if this is useful, but on my netbook the worst performance comes 
from black and transparent overlays, like when the Terminal asks for a password 
or when you want to turn off your computer. In those cases the frame time is 
more than 1s, sometimes 2s. I have to hard reboot every time because I can't 
click :(

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

Title:
  Unity8 on Intel Atoms performs poorly (falls back to software
  rendering more than non-Atoms do)

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

Bug description:
  (problem forked from bug 1549455)

  Unity8 on Intel Pineview performs very poorly. Frame times appears to
  be up to 900ms, Qt's renderer thread using 100% CPU.

  Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA 
errors:
  http://paste.ubuntu.com/16344427/

  Quoting @vanvugt "Those Mesa errors "Mesa: User error:" all look like
  OpenGL features that Unity8 is hitting but mir-demos don't. So those
  gl calls are also good candidates for explaining poor performance,
  especially if Mesa is falling back to software rendering for them."

  Since Qt tends to perform just fine on that hardware in X11, something
  isn't right.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580792/+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 1580792] Re: Unity8 on Intel Atoms performs poorly (falls back to software rendering more than non-Atoms do)

Did a few tests, dialogs with a black/transparent backgrounds are
definitely the worst (Terminal password prompt, shut down dialog, set a
code or password in System Settings, connect to a hidden wifi network).
The dialog can take up to 20s to fully open. Even then, they remain
slow, for example when you type your password to unlock the Terminal
(30s from the end of the splash screen to a workable terminal).

Other dialogs also perform very poorly, for example the "new VPN
connection" form, or the calendar-app's bottom edge (tested with the
snap version) in which you can't really type anything.

The alt-tab switcher is also very (very) laggy and completely unusable.
The pointer only move every 1 or 2 seconds which makes it hard to aim
correctly at anything. In all those examples, there is some kind of
transparency layer involved. Could it be the cause?

As noted in the title, performance is generally slow, so it might also
be interesting to see what does work well. For example, tab switching in
the browser (bottom-edge style) animates quite nicely once it's opened
(though it's a bit slow to open). Moving around in the calendar-app is
also quite smooth.

I would have liked to test lists as well, but the address-book-app snap
won't work and Dekko isn't in the repos (neither deb nor snap)…

Let me know if there's any kind of test I can do or log I can provide.
And let me know if I do have to file another bug!

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

Title:
  Unity8 on Intel Atoms performs poorly (falls back to software
  rendering more than non-Atoms do)

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

Bug description:
  (problem forked from bug 1549455)

  Unity8 on Intel Pineview performs very poorly. Frame times appears to
  be up to 900ms, Qt's renderer thread using 100% CPU.

  Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA 
errors:
  http://paste.ubuntu.com/16344427/

  Quoting @vanvugt "Those Mesa errors "Mesa: User error:" all look like
  OpenGL features that Unity8 is hitting but mir-demos don't. So those
  gl calls are also good candidates for explaining poor performance,
  especially if Mesa is falling back to software rendering for them."

  Since Qt tends to perform just fine on that hardware in X11, something
  isn't right.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580792/+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 1634412] Re: Unity8 session fails to start due to unity-system-compositor

Is there any more log I can provide that could shed a light on this?
This bug is very easily reproducible on my computer, so I should be able
to provide relevant logs!

My computer is not a fresh install and has been upgraded every step of
the way since 14.10. I'll try a LiveUSB of 16.10 to see if the problem
persists.

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

Title:
  Unity8 session fails to start due to unity-system-compositor

Status in Light Display Manager:
  New
Status in Unity System Compositor:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Hi,

  I've upgraded to 16.10 to try out the latest and the greatest.
  Unfortunately, the Unity8 session does not work anymore. It was
  working as expected on 16.04 with the overlay PPA.

  When I select "Unity8" in lightdm and enter my password, the password
  box disappears, and nothing else happens. I can still access all the
  indicators, so lightdm is not completely frozen. I then have to reboot
  or restart lightdm in tty1 to log in Unity 7.

  I do have a "system problem detected" warning and I did send the
  report, but I can't find it on Launchpad, that's why I'm filing this
  bug manually.

  I'm using Ubuntu 16.10 64bits, with the opensource radeon driver.

  Further info from the automatic bug report:
  Title : unity-system-compositor crashed with SIGABRT in 
__gnu_cxx::__verbose_terminate_handler()

  I'm attaching some logs that might be useful.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1634412/+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 1580792] Re: Unity8 on Intel Atoms performs poorly (falls back to software rendering more than non-Atoms do)

Here is my unity8.log with INTEL_DEBUG=perf. It's quite obscure for me
as I'm not a developer, but I did find the problems you mentioned it
your comments. I'll let you check!

** Attachment added: "unity8.log"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1580792/+attachment/4763298/+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/1580792

Title:
  Unity8 on Intel Atoms performs poorly (falls back to software
  rendering more than non-Atoms do)

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

Bug description:
  (problem forked from bug 1549455)

  Unity8 on Intel Pineview performs very poorly. Frame times appears to
  be up to 900ms, Qt's renderer thread using 100% CPU.

  Running unity8 with MESA_DEBUG=1 EGL_LOG_LEVEL=debug reveals a few MESA 
errors:
  http://paste.ubuntu.com/16344427/

  Quoting @vanvugt "Those Mesa errors "Mesa: User error:" all look like
  OpenGL features that Unity8 is hitting but mir-demos don't. So those
  gl calls are also good candidates for explaining poor performance,
  especially if Mesa is falling back to software rendering for them."

  Since Qt tends to perform just fine on that hardware in X11, something
  isn't right.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580792/+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 1548392] [NEW] Fix for 1172692 fails to restore hibernation mode with suspend-hybrid

Public bug reported:

The patch provided in upstream bug
 and implemented
through 28-suspend-hybrid.patch causes error messages "sh: I/O error"
when resuming with suspend-hybrid and hibernate kernel methods.

With suspend-hybrid it also forces the hibernation mode, as shown in
/sys/power/disk, to "suspend" instead of restoring the original mode
which is what the patch tried to do.

Please see the upstream bug for a review of the provided patch with
proposed fixes.

Affects all Ubuntu and derived versions with pm-utils
1.4.1-9fix.ubuntu12.10 or later.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
Uname: Linux 4.2.0-29-generic i686
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
Date: Mon Feb 22 16:44:52 2016
InstallationDate: Installed on 2016-02-21 (0 days ago)
InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1)
PackageArchitecture: all
SourcePackage: pm-utils
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pm-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 package-from-proposed regression-update trusty

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

Title:
  Fix for 1172692 fails to restore hibernation mode with suspend-hybrid

Status in pm-utils package in Ubuntu:
  New

Bug description:
  The patch provided in upstream bug
   and implemented
  through 28-suspend-hybrid.patch causes error messages "sh: I/O error"
  when resuming with suspend-hybrid and hibernate kernel methods.

  With suspend-hybrid it also forces the hibernation mode, as shown in
  /sys/power/disk, to "suspend" instead of restoring the original mode
  which is what the patch tried to do.

  Please see the upstream bug for a review of the provided patch with
  proposed fixes.

  Affects all Ubuntu and derived versions with pm-utils
  1.4.1-9fix.ubuntu12.10 or later.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 16:44:52 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1548392/+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 1548480] [NEW] 95packagekit sleep hook weirdly installed in a subdirectory is ignored

Public bug reported:

The 95packagekit sleep hook provided by packagekit is installed in a 
subdirectory: 
/usr/lib/pm-utils/sleep.d/95packagekit/95packagekit

This has two effects:

1the hook is not run;

2owing to a bug in pm-utils, separately reported, the previous hook
is run for a second time instead.

If #1 was actually the desired effect, the hook should have been stored
as /usr/lib/pm-utils/sleep.d/95packagekit~ or just omitted.

If the hook is manually installed as /usr/lib/pm-
utils/sleep.d/95packagekit, it runs as expected (although the nature of
the hook's operation means that it may have no obvious effect).

This issue was observed in 14.04, packagekit 0.8.12-1ubuntu5; apparently
was OK in 12.04. A packaging bug seems to have appeared when
95packagekit was updated in revision 1.2.10.

Additionally, the hook 95packagekit is incorrectly numbered according to
the pm-utils HOWTO.hooks convention and should apparently be eg
45packagekit.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: packagekit 0.8.12-1ubuntu5
ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
Uname: Linux 4.2.0-29-generic i686
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
Date: Mon Feb 22 19:12:48 2016
InstallationDate: Installed on 2016-02-21 (0 days ago)
InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1)
SourcePackage: packagekit
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 trusty

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

Title:
  95packagekit sleep hook weirdly installed in a subdirectory is ignored

Status in packagekit package in Ubuntu:
  New

Bug description:
  The 95packagekit sleep hook provided by packagekit is installed in a 
subdirectory: 
  /usr/lib/pm-utils/sleep.d/95packagekit/95packagekit

  This has two effects:

  1the hook is not run;

  2owing to a bug in pm-utils, separately reported, the previous
  hook is run for a second time instead.

  If #1 was actually the desired effect, the hook should have been
  stored as /usr/lib/pm-utils/sleep.d/95packagekit~ or just omitted.

  If the hook is manually installed as /usr/lib/pm-
  utils/sleep.d/95packagekit, it runs as expected (although the nature
  of the hook's operation means that it may have no obvious effect).

  This issue was observed in 14.04, packagekit 0.8.12-1ubuntu5;
  apparently was OK in 12.04. A packaging bug seems to have appeared
  when 95packagekit was updated in revision 1.2.10.

  Additionally, the hook 95packagekit is incorrectly numbered according
  to the pm-utils HOWTO.hooks convention and should apparently be eg
  45packagekit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: packagekit 0.8.12-1ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 19:12:48 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  SourcePackage: packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1548480/+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 1548486] [NEW] Sleep hook in a subdirectory ignored but causes double execution of previous hook

Public bug reported:

The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes
one (95packagekit/95packagekit) that is stored in a subdirectory. This
has two effects:

1the hook is not run;

2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is
run for a second time instead.

Presumably #1 is wrong, and results from an installation fault in
packagekit,  separately reported as bug 1548480.

#2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm-
functions computes a list of to-be-executed hooks that includes
directories but neither fully validates each such hook as a regular file
nor handles a set of to-be-executed hooks in a subdirectory.

At lines 243 on, there is  a code path with no else clause through which
the $hook from the previous iteration can be accidentally reused:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
    elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
fi

An easy fix is to insert the missing else clause before the fi line so
that the script skips the subdirectory or other non-regular file and
carries on with the next correctly specified hook:

if [ -f "$syshooks/$base" ]; then
    hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
else 
continue
fi

Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2. However
the relevant pm-utils code dates back to 2008, pm-utils upstream version
1.1.0.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
Uname: Linux 4.2.0-29-generic i686
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
Date: Mon Feb 22 17:10:53 2016
InstallationDate: Installed on 2016-02-21 (0 days ago)
InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1)
PackageArchitecture: all
SourcePackage: pm-utils
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pm-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 package-from-proposed trusty

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

Title:
  Sleep hook in a subdirectory ignored but causes double execution of
  previous hook

Status in pm-utils package in Ubuntu:
  New

Bug description:
  The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes
  one (95packagekit/95packagekit) that is stored in a subdirectory. This
  has two effects:

  1the hook is not run;

  2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is
  run for a second time instead.

  Presumably #1 is wrong, and results from an installation fault in
  packagekit,  separately reported as bug 1548480.

  #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm-
  functions computes a list of to-be-executed hooks that includes
  directories but neither fully validates each such hook as a regular
  file nor handles a set of to-be-executed hooks in a subdirectory.

  At lines 243 on, there is  a code path with no else clause through
  which the $hook from the previous iteration can be accidentally
  reused:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
fi

  An easy fix is to insert the missing else clause before the fi line so
  that the script skips the subdirectory or other non-regular file and
  carries on with the next correctly specified hook:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
else 
continue
fi

  Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2.
  However the relevant pm-utils code dates back to 2008, pm-utils
  upstream version 1.1.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 17:10:53 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i3

[Touch-packages] [Bug 1548480] Re: 95packagekit sleep hook weirdly installed in a subdirectory is ignored

Related pm-utils bug is bug 1548486.

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

Title:
  95packagekit sleep hook weirdly installed in a subdirectory is ignored

Status in packagekit package in Ubuntu:
  New

Bug description:
  The 95packagekit sleep hook provided by packagekit is installed in a 
subdirectory: 
  /usr/lib/pm-utils/sleep.d/95packagekit/95packagekit

  This has two effects:

  1the hook is not run;

  2owing to a bug in pm-utils, separately reported, the previous
  hook is run for a second time instead.

  If #1 was actually the desired effect, the hook should have been
  stored as /usr/lib/pm-utils/sleep.d/95packagekit~ or just omitted.

  If the hook is manually installed as /usr/lib/pm-
  utils/sleep.d/95packagekit, it runs as expected (although the nature
  of the hook's operation means that it may have no obvious effect).

  This issue was observed in 14.04, packagekit 0.8.12-1ubuntu5;
  apparently was OK in 12.04. A packaging bug seems to have appeared
  when 95packagekit was updated in revision 1.2.10.

  Additionally, the hook 95packagekit is incorrectly numbered according
  to the pm-utils HOWTO.hooks convention and should apparently be eg
  45packagekit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: packagekit 0.8.12-1ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 19:12:48 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  SourcePackage: packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1548480/+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 1548480] Re: 95packagekit sleep hook weirdly installed in a subdirectory is ignored

So if I understand correctly, the upstream version 0.8.17 currently
packaged in 16.04 is "prehistoric"  (and my version in 14.04 LTS even
more so) but the active branch based on upstream version 1.1.0-1 that
you (Matthias) are working on is not?

In that case for 16.04 Ubuntu could do one of these:

a) add a patch to move /usr/lib/pm-
utils/sleep.d/95packagekit/95packagekit to /usr/lib/pm-
utils/sleep.d/95packagekit (or /usr/lib/pm-utils/sleep.d/45packagekit)
(NB check it gets marked executable), or

b) pull in a less prehistoric version of Packagekit that doesn't have
that file, or

c) fix pm-utils bug 1548486 and ignore this bug until (b), or

d) add a patch to remove /usr/lib/pm-
utils/sleep.d/95packagekit/95packagekit.

The value of the 95packagekit hook (which tries to provoke PackageKit to
refresh its cache on resuming) seems questionable, since it doesn't
appear to have been working for several years and isn't in the later
versions.

So (c) or (d) seem like the best options, with (c) requiring no work at
all for PackageKit.

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

Title:
  95packagekit sleep hook weirdly installed in a subdirectory is ignored

Status in packagekit package in Ubuntu:
  New

Bug description:
  The 95packagekit sleep hook provided by packagekit is installed in a 
subdirectory: 
  /usr/lib/pm-utils/sleep.d/95packagekit/95packagekit

  This has two effects:

  1the hook is not run;

  2owing to a bug in pm-utils, separately reported, the previous
  hook is run for a second time instead.

  If #1 was actually the desired effect, the hook should have been
  stored as /usr/lib/pm-utils/sleep.d/95packagekit~ or just omitted.

  If the hook is manually installed as /usr/lib/pm-
  utils/sleep.d/95packagekit, it runs as expected (although the nature
  of the hook's operation means that it may have no obvious effect).

  This issue was observed in 14.04, packagekit 0.8.12-1ubuntu5;
  apparently was OK in 12.04. A packaging bug seems to have appeared
  when 95packagekit was updated in revision 1.2.10.

  Additionally, the hook 95packagekit is incorrectly numbered according
  to the pm-utils HOWTO.hooks convention and should apparently be eg
  45packagekit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: packagekit 0.8.12-1ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 19:12:48 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  SourcePackage: packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1548480/+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 1443249] Re: After kernel-3.13.0-41, wireless script checks wrong sys file.

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

** This bug is no longer a duplicate of bug 1414110
   Wireless powersave doesn't work (pm-utils)
** This bug has been marked a duplicate of bug 1544612
   Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

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

Title:
  After kernel-3.13.0-41, wireless script checks wrong sys file.

Status in pm-utils package in Ubuntu:
  New

Bug description:
  [TEST CASE]
  * on a laptop machine with a ac adapter connect & wireless interface run:
  1. ac adapter disconnect
  2. $ tail /var/log/pm-powersave.log & $ iwconfig

  [Actual Result]
  * wireless power management does not "ON"

  $ tail /var/log/pm-powersave.log
  --->---> snip --->---> snip --->---> snip --->---> snip --->--->
  Running hook /usr/lib/pm-utils/power.d/wireless true:
  cat: /sys/class/net/wlan0/device/enabled: No such file or directory
  /usr/lib/pm-utils/power.d/wireless true: success.
  --->---> snip --->---> snip --->---> snip --->---> snip --->--->

  $ iwconfig
  wlan0 IEEE 802.11bgn  ESSID:"x"  
  --->---> snip --->---> snip --->---> snip --->---> snip --->--->
Power Management:off
  --->---> snip --->---> snip --->---> snip --->---> snip --->--->

  [Expected Result]
  $ tail /var/log/pm-powersave.log
  --->---> snip --->---> snip --->---> snip --->---> snip --->--->
  Running hook /etc/pm/power.d/wireless true:
  Turning powersave for wlan0 on...Done.
  /etc/pm/power.d/wireless true: success.
  --->---> snip --->---> snip --->---> snip --->---> snip --->--->

  $ iwconfig
  wlan0 IEEE 802.11bgn  ESSID:"x"  
  --->---> snip --->---> snip --->---> snip --->---> snip --->--->
Power Management:on
  --->---> snip --->---> snip --->---> snip --->---> snip --->--->

  
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04
  Codename: trusty

  $ uname -a
  Linux xxx 3.13.0-49-generic #81-Ubuntu SMP Tue Mar 24 19:29:48 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  $ cat /etc/modprobe.d/ath9k_powersave.conf 
  options ath9k ps_enable=1

  $ apt-cache policy pm-utils
  pm-utils:
インストールされているバージョン: 1.4.1-13ubuntu0.1
候補:   1.4.1-13ubuntu0.1
バージョンテーブル:
   *** 1.4.1-13ubuntu0.1 0
  500 http://www.ftp.ne.jp/Linux/packages/ubuntu/archive/ 
trusty-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1.4.1-13 0
  500 http://www.ftp.ne.jp/Linux/packages/ubuntu/archive/ trusty/main 
amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1443249/+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 1414110] Re: Wireless powersave doesn't work (pm-utils)

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

Should be fixed along with bug 1544612. Marking as duplicate...

** This bug has been marked a duplicate of bug 1544612
   Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

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

Title:
  Wireless powersave doesn't work (pm-utils)

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I notice a bug about wireless powersave (pm-utils 1.4.1-13ubuntu0.1 on
  Ubuntu 14.04.1 LTS using kernel 3.13.0-44-generic) :

  # PM_FUNCTIONS="/usr/lib/pm-utils/functions" 
/usr/lib/pm-utils/power.d/wireless true
  cat: /sys/class/net/wlan0/device/enabled: No such file or directory

  If I replace '/sys/class/net/wlan0/device/enabled' by
  '/sys/class/net/wlan0/device/enable' in '/usr/lib/pm-
  utils/power.d/wireless', it seems to work fine :

  # PM_FUNCTIONS="/usr/lib/pm-utils/functions" 
/usr/lib/pm-utils/power.d/wireless true
  Turning powersave for wlan0 on...Done.

  Is it possible to fix this bug ?

  Thanks :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1414110/+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 1548853] [NEW] 00powersave sleep hook misses claimed patch

Public bug reported:

The pm-utils sleep hook installed at /usr/lib/pm-
utils/sleep.d/00powersave was supposed to have been patched to prevent
it running on ARM architectures. However a new case was added without
deleting the preceding existing one (lines 12 on):

case $1 in
suspend|hibernate) pm-powersave false ;;
suspend|hibernate) [ "$ARCH" != "${ARCH#arm}" ] || pm-powersave false ;;
resume|thaw)   pm-powersave ;;
*) exit $NA ;;
esac

Observed in and affects 14.04.3,4.; seems to be OK in 14.10-15.10.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
Uname: Linux 4.2.0-29-generic i686
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
Date: Tue Feb 23 13:51:14 2016
InstallationDate: Installed on 2016-02-21 (1 days ago)
InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1)
PackageArchitecture: all
SourcePackage: pm-utils
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pm-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 package-from-proposed trusty

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

Title:
  00powersave sleep hook misses claimed patch

Status in pm-utils package in Ubuntu:
  New

Bug description:
  The pm-utils sleep hook installed at /usr/lib/pm-
  utils/sleep.d/00powersave was supposed to have been patched to prevent
  it running on ARM architectures. However a new case was added without
  deleting the preceding existing one (lines 12 on):

  case $1 in
  suspend|hibernate) pm-powersave false ;;
  suspend|hibernate) [ "$ARCH" != "${ARCH#arm}" ] || pm-powersave false ;;
  resume|thaw)   pm-powersave ;;
  *) exit $NA ;;
  esac

  Observed in and affects 14.04.3,4.; seems to be OK in 14.10-15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Tue Feb 23 13:51:14 2016
  InstallationDate: Installed on 2016-02-21 (1 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1548853/+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 1172692]

In comment #2 I wrote:
> Comment on attachment 68712 [details] [review]
>...
> Although you could make the penultimate line as follows I don't recommend it
> because it would hide any problems like the escaping issue that could cause
> HIBERNATE_MODE_SAVE to be invalid:
> 
>   [ -n "$HIBERNATE_MODE_SAVE" ] && echo -n "$HIBERNATE_MODE_SAVE" 
> >
> /sys/power/disk

In fact there are 2 cases as the code is used now:

1HIBERNATE_MODE unset => normal hibernate

2HIBERNATE_MODE = suspend => suspend-hybrid

Given which, I've revised my comment above and propose a new version of
the modified do_hibernate() as follows:

do_hibernate()
{
local hibernate_mode_save ret

[ -n "${HIBERNATE_MODE}" ] && \
 grep -qw "${HIBERNATE_MODE}" /sys/power/disk && \
 hibernate_mode_save=$(cat /sys/power/disk) && \
 hibernate_mode_save="${hibernate_mode_save##*\[}" && \
 hibernate_mode_save="${hibernate_mode_save%%\]*}" && \
 [ "$hibernate_mode_save" != "${HIBERNATE_MODE}" ]  || \
 hibernate_mode_save=""
[ -n "$hibernate_mode_save" ] && \
 echo -n "${HIBERNATE_MODE}" > /sys/power/disk
echo -n "disk" > /sys/power/state
ret=$?
[ -n "$hibernate_mode_save" ] && \
 echo -n "$hibernate_mode_save" > /sys/power/disk
return $ret
}

The key points:
- hibernate_mode_save is only set if the current HIBERNATE_MODE is being 
changed (which only happens, if it does, in the suspend-hybrid case);
- on resume the hibernate mode is only restored if hibernate_mode_save was set.

This fixes:
- the failure to restore the hibernate mode with suspend-hybrid;
- "sh: I/O error" on resume from suspend-hybrid
- "sh: I/O error" on resume from hibernate.

Finally, the pm_functions script uses "echo -n" (from line 318,
including the above patch) and local declarations while the comment
against function log() implies that the script is aiming for POSIX
conformance and yet other functions use non-POSIX local declarations.
local and "echo -n" usages are fine for Debian and derived environments.
To achieve POSIX conformance such usages would have to be reviewed and
modified; "echo -n" could be replaced with printf (the parameters to be
echoed in each case being plain text not containing formatting
commands); or a shell function echo() can be added based on log().

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

Title:
  Please implement in-kernel suspend to both

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project precise series:
  Fix Released
Status in pm-utils:
  Confirmed
Status in pm-utils package in Ubuntu:
  Fix Released
Status in pm-utils source package in Precise:
  Fix Released
Status in pm-utils source package in Quantal:
  Fix Released
Status in pm-utils source package in Trusty:
  Fix Released
Status in pm-utils package in CentOS:
  Unknown

Bug description:
  From kernel-3.6 there is in-kernel support for suspend to both (AKA
  hybrid suspend). Working patches can be found at
  https://bugs.freedesktop.org/show_bug.cgi?id=52572 (or links).

  [Impact] 

   * Ubuntu 12.04 implements hybrid suspend differently. It suspends first and 
wakes up
 the computer for hibernation 15 minutes later. This is risky since the 
computer may be
 carried when the wakeup happens. The hard disk may experience physical 
shocks and get
 damaged.

   * Thus, it is desirable to have a real hybrid suspend implementation. 
In-kernel hybrid
 suspend has been supported since kernel 3.6+. pm-utils only needs a small 
patch to
 enable this feature. 

  [Test Case]

   * Ensure all Ubuntu 12.04 packages are up-to-date in the test environment.
 Install pm-utils 1.4.1-9ubuntu1
 Install linux-image-lts-raring

   * Reboot the computer with lts-raring kernel. Run the command: 
'pm-suspend-hybrid' from a 
 terminal. After the computer suspends, press the power button. It should 
be able to
 resume from suspension correctly. 

   * Run the command above again. After it suspends, remove and reconnect its 
power supply 
 (or its battery). Press the power button. It should be able to resume from 
hibernation
 correctly.

   * Reboot with the default 3.2 kernel, Run the command above. 
 The computer should be able to suspend and then wake up for hibernation 15 
minutes
 later.

  [Regression Potential] 

   * This patch won't affect users who still use 3.2 kernel. It only enables 
in-kernel
 hybrid suspend if the option 'suspend' is available from /sys/power/disk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1172692/+subscriptions

-- 
Mailing list:

[Touch-packages] [Bug 1172692]

In comment #3 I wrote:
>...
> Finally, the pm_functions script uses "echo -n" (from line 318, including
> the above patch) ...

See also bug 91497.

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

Title:
  Please implement in-kernel suspend to both

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project precise series:
  Fix Released
Status in pm-utils:
  Confirmed
Status in pm-utils package in Ubuntu:
  Fix Released
Status in pm-utils source package in Precise:
  Fix Released
Status in pm-utils source package in Quantal:
  Fix Released
Status in pm-utils source package in Trusty:
  Fix Released
Status in pm-utils package in CentOS:
  Unknown

Bug description:
  From kernel-3.6 there is in-kernel support for suspend to both (AKA
  hybrid suspend). Working patches can be found at
  https://bugs.freedesktop.org/show_bug.cgi?id=52572 (or links).

  [Impact] 

   * Ubuntu 12.04 implements hybrid suspend differently. It suspends first and 
wakes up
 the computer for hibernation 15 minutes later. This is risky since the 
computer may be
 carried when the wakeup happens. The hard disk may experience physical 
shocks and get
 damaged.

   * Thus, it is desirable to have a real hybrid suspend implementation. 
In-kernel hybrid
 suspend has been supported since kernel 3.6+. pm-utils only needs a small 
patch to
 enable this feature. 

  [Test Case]

   * Ensure all Ubuntu 12.04 packages are up-to-date in the test environment.
 Install pm-utils 1.4.1-9ubuntu1
 Install linux-image-lts-raring

   * Reboot the computer with lts-raring kernel. Run the command: 
'pm-suspend-hybrid' from a 
 terminal. After the computer suspends, press the power button. It should 
be able to
 resume from suspension correctly. 

   * Run the command above again. After it suspends, remove and reconnect its 
power supply 
 (or its battery). Press the power button. It should be able to resume from 
hibernation
 correctly.

   * Reboot with the default 3.2 kernel, Run the command above. 
 The computer should be able to suspend and then wake up for hibernation 15 
minutes
 later.

  [Regression Potential] 

   * This patch won't affect users who still use 3.2 kernel. It only enables 
in-kernel
 hybrid suspend if the option 'suspend' is available from /sys/power/disk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1172692/+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 1172692]

Comment on attachment 68712
Improved patch to save previous hibernation method

Review of attachment 68712:
-

In do_hibernate() the attempt to save and restore the active mode in
/sys/power/disk fails, causing "sh: I/O error" message in pm log
(attempting to write something that isn't one of the modes in
/sys/power/disk, namely an empty string). Instrumenting the function I
found that HIBERNATE_MODE_SAVE was never set.

The characters [] are special in a shell pattern (which is what follows
the ## and %% shell variable expansion modifiers) and have to be
escaped: \[ \].

The following works as you intended:

do_hibernate()
{
[ -n "${HIBERNATE_MODE}" ] && \
grep -qw "${HIBERNATE_MODE}" /sys/power/disk && \
#df 2016-02-07 Shell patterns have to be escaped \[ \]! Fixes 
sh: I/O error when -z $HIBERNATE_MODE_SAVE 
HIBERNATE_MODE_SAVE=$(cat /sys/power/disk) && \
HIBERNATE_MODE_SAVE="${HIBERNATE_MODE_SAVE##*\[}" && \
HIBERNATE_MODE_SAVE="${HIBERNATE_MODE_SAVE%%\]*}" && \
echo -n "${HIBERNATE_MODE}" > /sys/power/disk
echo -n "disk" > /sys/power/state
RET=$?
echo -n "$HIBERNATE_MODE_SAVE" > /sys/power/disk
return "$RET"
}

Although you could make the penultimate line as follows I don't
recommend it because it would hide any problems like the escaping issue
that could cause HIBERNATE_MODE_SAVE to be invalid:

[ -n "$HIBERNATE_MODE_SAVE" ] && echo -n
"$HIBERNATE_MODE_SAVE" > /sys/power/disk

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

Title:
  Please implement in-kernel suspend to both

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project precise series:
  Fix Released
Status in pm-utils:
  Confirmed
Status in pm-utils package in Ubuntu:
  Fix Released
Status in pm-utils source package in Precise:
  Fix Released
Status in pm-utils source package in Quantal:
  Fix Released
Status in pm-utils source package in Trusty:
  Fix Released
Status in pm-utils package in CentOS:
  Unknown

Bug description:
  From kernel-3.6 there is in-kernel support for suspend to both (AKA
  hybrid suspend). Working patches can be found at
  https://bugs.freedesktop.org/show_bug.cgi?id=52572 (or links).

  
  [Impact] 

   * Ubuntu 12.04 implements hybrid suspend differently. It suspends first and 
wakes up
 the computer for hibernation 15 minutes later. This is risky since the 
computer may be
 carried when the wakeup happens. The hard disk may experience physical 
shocks and get
 damaged.

   * Thus, it is desirable to have a real hybrid suspend implementation. 
In-kernel hybrid
 suspend has been supported since kernel 3.6+. pm-utils only needs a small 
patch to
 enable this feature. 

  
  [Test Case]

   * Ensure all Ubuntu 12.04 packages are up-to-date in the test environment.
 Install pm-utils 1.4.1-9ubuntu1
 Install linux-image-lts-raring

   * Reboot the computer with lts-raring kernel. Run the command: 
'pm-suspend-hybrid' from a 
 terminal. After the computer suspends, press the power button. It should 
be able to
 resume from suspension correctly. 

   * Run the command above again. After it suspends, remove and reconnect its 
power supply 
 (or its battery). Press the power button. It should be able to resume from 
hibernation
 correctly.

   * Reboot with the default 3.2 kernel, Run the command above. 
 The computer should be able to suspend and then wake up for hibernation 15 
minutes
 later.

  
  [Regression Potential] 

   * This patch won't affect users who still use 3.2 kernel. It only enables 
in-kernel
 hybrid suspend if the option 'suspend' is available from /sys/power/disk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1172692/+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 1548480] Re: 95packagekit sleep hook weirdly installed in a subdirectory is ignored

2016-02-25 Thread Dirk F

In order for (b) (PackageKit update) to happen for Ubuntu, I suppose
someone knowledgeable would have to identify likely issues from doing so
and communicate with someone like xnox

...

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

Title:
  95packagekit sleep hook weirdly installed in a subdirectory is ignored

Status in packagekit package in Ubuntu:
  New

Bug description:
  The 95packagekit sleep hook provided by packagekit is installed in a 
subdirectory: 
  /usr/lib/pm-utils/sleep.d/95packagekit/95packagekit

  This has two effects:

  1the hook is not run;

  2owing to a bug in pm-utils, separately reported, the previous
  hook is run for a second time instead.

  If #1 was actually the desired effect, the hook should have been
  stored as /usr/lib/pm-utils/sleep.d/95packagekit~ or just omitted.

  If the hook is manually installed as /usr/lib/pm-
  utils/sleep.d/95packagekit, it runs as expected (although the nature
  of the hook's operation means that it may have no obvious effect).

  This issue was observed in 14.04, packagekit 0.8.12-1ubuntu5;
  apparently was OK in 12.04. A packaging bug seems to have appeared
  when 95packagekit was updated in revision 1.2.10.

  Additionally, the hook 95packagekit is incorrectly numbered according
  to the pm-utils HOWTO.hooks convention and should apparently be eg
  45packagekit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: packagekit 0.8.12-1ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 19:12:48 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  SourcePackage: packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1548480/+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 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook

2016-02-27 Thread Dirk F

Upstream bug with patch at
<https://bugs.freedesktop.org/show_bug.cgi?id=94323>

** Bug watch added: freedesktop.org Bugzilla #94323
   https://bugs.freedesktop.org/show_bug.cgi?id=94323

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

Title:
  Sleep hook in a subdirectory ignored but causes double execution of
  previous hook

Status in pm-utils package in Ubuntu:
  New

Bug description:
  The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes
  one (95packagekit/95packagekit) that is stored in a subdirectory. This
  has two effects:

  1the hook is not run;

  2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is
  run for a second time instead.

  Presumably #1 is wrong, and results from an installation fault in
  packagekit,  separately reported as bug 1548480.

  #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm-
  functions computes a list of to-be-executed hooks that includes
  directories but neither fully validates each such hook as a regular
  file nor handles a set of to-be-executed hooks in a subdirectory.

  At lines 243 on, there is  a code path with no else clause through
  which the $hook from the previous iteration can be accidentally
  reused:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
fi

  An easy fix is to insert the missing else clause before the fi line so
  that the script skips the subdirectory or other non-regular file and
  carries on with the next correctly specified hook:

if [ -f "$syshooks/$base" ]; then
    hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
else 
continue
fi

  Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2.
  However the relevant pm-utils code dates back to 2008, pm-utils
  upstream version 1.1.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 17:10:53 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1548486/+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 1548392]

2016-02-28 Thread Dirk F

Created attachment 122010
patch based on review of patch 68712, taken from running pm-functions

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

Title:
  Fix for 1172692 fails to restore hibernation mode with suspend-hybrid

Status in pm-utils:
  Confirmed
Status in pm-utils package in Ubuntu:
  New

Bug description:
  The patch provided in upstream bug
   and implemented
  through 28-suspend-hybrid.patch causes error messages "sh: I/O error"
  when resuming with suspend-hybrid and hibernate kernel methods.

  With suspend-hybrid it also forces the hibernation mode, as shown in
  /sys/power/disk, to "suspend" instead of restoring the original mode
  which is what the patch tried to do.

  Please see the upstream bug for a review of the provided patch with
  proposed fixes.

  Affects all Ubuntu and derived versions with pm-utils
  1.4.1-9fix.ubuntu12.10 or later.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 16:44:52 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1548392/+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 1634412] Re: Unity8 session fails to start due to unity-system-compositor

2016-10-27 Thread Guillaume F

Here is a copy of my unity-system-compositor.sleep.

A failed upgrade is possible: before I upgraded to 16.10, I tried
purging a few PPAs because they are often problematic and purging the
overlay-ppa proved very difficult (ended up chasing the word "overlay"
in Synaptic to completely remove any trace).

Currently, my version of unity-system-compositor is
0.7.1+16.10.20160909.1-0ubuntu1 and Synaptic marks it as the latest
version.

** Attachment added: "unity-system-compositor.sleep"

https://bugs.launchpad.net/unity-system-compositor/+bug/1634412/+attachment/4768090/+files/unity-system-compositor.sleep

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

Title:
Unity8 session fails to start due to unity-system-compositor

Status in Light Display Manager:
Incomplete
Status in Unity System Compositor:
Incomplete
Status in lightdm package in Ubuntu:
Incomplete

Bug description:
Hi,

I've upgraded to 16.10 to try out the latest and the greatest.
Unfortunately, the Unity8 session does not work anymore. It was
working as expected on 16.04 with the overlay PPA.

When I select "Unity8" in lightdm and enter my password, the password
box disappears, and nothing else happens. I can still access all the
indicators, so lightdm is not completely frozen. I then have to reboot
or restart lightdm in tty1 to log in Unity 7.

I do have a "system problem detected" warning and I did send the
report, but I can't find it on Launchpad, that's why I'm filing this
bug manually.

I'm using Ubuntu 16.10 64bits, with the opensource radeon driver.

Further info from the automatic bug report:
Title : unity-system-compositor crashed with SIGABRT in
__gnu_cxx::__verbose_terminate_handler()

I'm attaching some logs that might be useful.

Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1634412/+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 1634412] Re: Unity8 session fails to start due to unity-system-compositor

2016-10-27 Thread Guillaume F

Also, I don't know if there is an overlay-ppa for 16.10, but if there
is, I did not install it on my machine, so I should be using pure 16.10
repos.

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

Title:
  Unity8 session fails to start due to unity-system-compositor

Status in Light Display Manager:
  Incomplete
Status in Unity System Compositor:
  Incomplete
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I've upgraded to 16.10 to try out the latest and the greatest.
  Unfortunately, the Unity8 session does not work anymore. It was
  working as expected on 16.04 with the overlay PPA.

  When I select "Unity8" in lightdm and enter my password, the password
  box disappears, and nothing else happens. I can still access all the
  indicators, so lightdm is not completely frozen. I then have to reboot
  or restart lightdm in tty1 to log in Unity 7.

  I do have a "system problem detected" warning and I did send the
  report, but I can't find it on Launchpad, that's why I'm filing this
  bug manually.

  I'm using Ubuntu 16.10 64bits, with the opensource radeon driver.

  Further info from the automatic bug report:
  Title : unity-system-compositor crashed with SIGABRT in 
__gnu_cxx::__verbose_terminate_handler()

  I'm attaching some logs that might be useful.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1634412/+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 1607291] Re: Dual SIM devices show "No SIM" icon in indicators if there is only one SIM installed

2016-09-22 Thread Guillaume F

I've been looking at screenshots of dual-SIM Android phones (bq Aquaris 4.5, bq 
Aquaris X5, Oneplus 3…) and find none that had an empty SIM icons in the panel. 
Pictures on their respective websites show two (working) network icons, to 
emphasize the fact that those phones are capable of doing this. But if you look 
at reviews, hands-on etc, sometimes there is no SIM inserted (you only see the 
WiFi icon) and most of the time there's only one. And I could not find any 
picture with an empty SIM in the top panel. 
Maybe someone who owns such a phone could confirm?
If I'm not mistaken, then how could Android not meet carrier certification 
requirements?
And how could carriers require an operating system to display useless 
information like that? Dual-SIM is just a feature that's becoming fairly 
standard, but it doesn't mean you have to use it. It would be just as silly to 
always display a Bluetooth icon when you just don't use it, a WiFi icon so that 
you are reminded that your phone is capable of Wifi, an icon for your GPU 
saying "hey, you're not using me right now!", etc. The top panel is small and 
should not be cluttered.

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

Title:
  Dual SIM devices show "No SIM" icon in indicators if there is only one
  SIM installed

Status in indicator-network package in Ubuntu:
  Invalid

Bug description:
  rc-proposed, since about a week I have 2 SIM icons in the indicators
  panel. One that shows the signal strength for the installed SIM card
  (which is fine), and then a second one which shows the "no SIM card"
  icon.

  When there is a SIM card installed, the indicator should not show a
  "no SIM installed" icon, even though there would be a second free slot
  available.

  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1607291/+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 1607291] Re: Dual SIM devices show "No SIM" icon in indicators if there is only one SIM installed

2016-09-22 Thread Guillaume F

@Ivo Xavier Very good idea! Same as SD cards. I find it annoying to have
a notification for my SD card every time I boot my phone, but if I
really don't want them, I can easily disable them in the notifications
panel.

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

Title:
  Dual SIM devices show "No SIM" icon in indicators if there is only one
  SIM installed

Status in Ubuntu UX:
  New
Status in indicator-network package in Ubuntu:
  Invalid

Bug description:
  rc-proposed, since about a week I have 2 SIM icons in the indicators
  panel. One that shows the signal strength for the installed SIM card
  (which is fine), and then a second one which shows the "no SIM card"
  icon.

  When there is a SIM card installed, the indicator should not show a
  "no SIM installed" icon, even though there would be a second free slot
  available.

  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1607291/+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 1616342] Re: Empty SIM slot indicator unnecessary for second SIM

2016-09-22 Thread Guillaume F

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

** This bug has been marked a duplicate of bug 1607291
   Dual SIM devices show "No SIM" icon in indicators if there is only one SIM 
installed

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

Title:
  Empty SIM slot indicator unnecessary for second SIM

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

Bug description:
  Pro 5 on rc-proposed 164

  My phone has dual SIM support. A while back, an indicator was
  introduced showing that one of the SIM slots (in my case slot 1, which
  instead holds the SD card) is empty. I feel this is unnecessary
  "clutter" in the top bar and would like the ability disable it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1616342/+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 1583802] Re: Keyboard layout is not respected in some places

2016-07-01 Thread Guillaume F

Well, I seem to be alone with this problem, but today I found that the
password prompt for connecting to a WiFi source is also affected and
stuck in QWERTY. Strangely enough, it is not the case with the whole
"hidden network" form: there, I can type my password in AZERTY quite
normally. (I was forced to cheat and connect to my network with the
"hidden network" feature, since the regular password prompt didn't work.
Probably another bug though).

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

Title:
  Keyboard layout is not respected in some places

Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Incomplete

Bug description:
  I'm trying Unity8 on my desktop (and reporting bugs from there,
  cool!), I've followed Michael Hall's how to, so I have the same PPAs
  on my system.

  The keyboard layout is not the same everywhere in the OS. I switched
  to French and it works in most places, but in some others, an English
  keyboard persists. These other places include the greeter and the
  Online Accounts (the rest of the System Settings app seems fine). I'm
  not sure where else but I'll keep searching.

  I have to say, it has its advantages, since alt-gr does not work and I
  have to copy/paste things like "@"!

  Thanks for your great work, it's really exciting to see the progress!

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1583802/+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 1394388] Re: pm-suspend not restoring /sys/power/disk with /bin/dash

2016-08-12 Thread Dirk F

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

** This bug has been marked a duplicate of bug 1548392
   Fix for 1172692 fails to restore hibernation mode with suspend-hybrid

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

Title:
  pm-suspend not restoring /sys/power/disk with /bin/dash

Status in pm-utils package in Ubuntu:
  New

Bug description:
  Ubuntu 14.04LTS 
  pm-utils  1.4.1-13ubuntu0.1

  When issuing the pm-suspend command, the scripts set the HIBERNATE_MODE in 
/sys/power/disk to "suspend".
  There is some shell magic to save the previous setting in variable 
HIBERNATE_MODE_SAVE, but this fails under
  the default shell /bin/dash (works correctly with /bin/bash).

  Effect: if you use pm-suspend once, the effective HIBERNATE_MODE in 
/sys/power/disk stays in "suspend", and
  any subsequent pm-hibernate will also just do a suspend instead of "platform" 
or "shutdown".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1394388/+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 1548392] Re: Fix for 1172692 fails to restore hibernation mode with suspend-hybrid

2016-08-12 Thread Dirk F

Marked bug 1394388 as duplicate of this. The bug report points out an
additional related symptom, as follows.

When issuing the pm-suspend command, the scripts set the HIBERNATE_MODE
in /sys/power/disk to "suspend".

There is some shell magic to save the previous setting in variable
HIBERNATE_MODE_SAVE, but this fails under the default shell /bin/dash
(works correctly with /bin/bash).

Effect: if you use pm-suspend once, the effective HIBERNATE_MODE in
/sys/power/disk stays in "suspend", and any subsequent pm-hibernate will
also just do a suspend instead of "platform" or "shutdown".

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

Title:
  Fix for 1172692 fails to restore hibernation mode with suspend-hybrid

Status in pm-utils:
  Confirmed
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  The patch provided in upstream bug
   and implemented
  through 28-suspend-hybrid.patch causes error messages "sh: I/O error"
  when resuming with suspend-hybrid and hibernate kernel methods.

  With suspend-hybrid it also forces the hibernation mode, as shown in
  /sys/power/disk, to "suspend" instead of restoring the original mode
  which is what the patch tried to do.

  Please see the upstream bug for a review of the provided patch with
  proposed fixes.

  Affects all Ubuntu and derived versions with pm-utils
  1.4.1-9fix.ubuntu12.10 or later.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 16:44:52 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1548392/+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 1415039] Re: laptop unresponsive after suspend

2016-08-12 Thread Dirk F

The message in /var/log/pm-suspend.log quoted in the report

"Failed to connect to non-global ctrl_ifname: (null) error: No such file
or directory"

comes from the wpa_supplicant sleep hook. This hook shouldn't be run
when NetworkManager is operating, since NM handles sleep and resume DBus
notifications itself. More often than not, the result of the race
between the two is a half-working network that appears from the GUI to
be working but actually isn't and has to be fixed by disabling and re-
enabling Networking.

At any rate it isn't connected with the original problem.

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

Title:
  laptop unresponsive after suspend

Status in pm-utils package in Ubuntu:
  New

Bug description:
  After suspend, the system becomes unresponsive. Fan keeps running,
  full reboot needed.

  In /var/log/pm-suspend.log the only error is:

  "Failed to connect to non-global ctrl_ifname: (null)  error: No such
  file or directory"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 27 14:40:12 2015
  InstallationDate: Installed on 2015-01-26 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1415039/+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 1589220] [NEW] Launching a sidestage app in portrait and spreading, app won't focus

Public bug reported:

Steps to reproduce:
- tablet in portrait view
- launch an app that you know to be in sidestage mode
- spread apps with a right swipe
- turn the tablet back in landscape view
- try to focus on the recently opened sidestage app

Expected result:
The app goes in the foreground, in sidestage.

Current result:
I don't know exactly: if you spread slowly, you can glimpse the "use three 
fingers" screen that you get when no app is in sidestage, and selecting the 
newly opened app won't work and focuses on another one. Switching to yet 
another app, the sidestage app finally shows.

Not sure my description is very clear but hopefully it will be easy to
reproduce!

** 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/1589220

Title:
  Launching a sidestage app in portrait and spreading, app won't focus

Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  - tablet in portrait view
  - launch an app that you know to be in sidestage mode
  - spread apps with a right swipe
  - turn the tablet back in landscape view
  - try to focus on the recently opened sidestage app

  Expected result:
  The app goes in the foreground, in sidestage.

  Current result:
  I don't know exactly: if you spread slowly, you can glimpse the "use three 
fingers" screen that you get when no app is in sidestage, and selecting the 
newly opened app won't work and focuses on another one. Switching to yet 
another app, the sidestage app finally shows.

  Not sure my description is very clear but hopefully it will be easy to
  reproduce!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1589220/+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 1589234] [NEW] Items in the launcher don't move with the mouse

Public bug reported:

When in desktop mode with a mouse and a launcher full of apps, hovering
the cursor on top of the launcher doesn't do anything. It should reveal
stacked icons top and bottom, just like in Unity7.

** 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/1589234

Title:
  Items in the launcher don't move with the mouse

Status in unity8 package in Ubuntu:
  New

Bug description:
  When in desktop mode with a mouse and a launcher full of apps,
  hovering the cursor on top of the launcher doesn't do anything. It
  should reveal stacked icons top and bottom, just like in Unity7.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1589234/+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 1440065] Re: [Address book] Contacts with accent on first letter are not ordered properly

Any news on this? This bug has been present for more than a year and
still no news.

I have no idea how difficult it is to implement, but an address-book
which is incapable of alphabetically sorting contacts is not a very
useful address-book. I understand that in English, this bug might seem
of low priority, but not in other languages!

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

Title:
  [Address book] Contacts with accent on first letter are not ordered
  properly

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

Bug description:
  My contact list is a bit strange when it comes to the "E" letter. I
  have six different categories, three "E"s and three "É"s. Also, when I
  search for a contact, "E" and "É" are not the same, which is
  inconvenient.

  My contacts come from two Google accounts but it does not seem to be
  the problem, since contacts from both accounts may appear under one
  "E" occurrence.

  This is on the retail bq phone, r20, French locale.

  UX comment--

  My recommendation is not to create new sections for the accent letters but 
accommodate them under their parent letter. This would mean:
  - "É," is in the "E" section, "Ç" is under the "C", "Å" is under the "A" 
section and so on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1440065/+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 1589242] [NEW] Turning the mouse on or off unlocks the greeter

Public bug reported:

Steps to reproduce:
- Ensure you have "no security/swiping" enabled for unlocking.
- Switch the screen off and on, you get the greeter.
- If your bluetooth mouse in off, turn it on. If it's on, turn it off.

Expected result:
Nothing in particular, the UX of the greeter does not change between desktop 
and staged mode.

What actually happens:
The greeter unlocks.

** 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/1589242

Title:
  Turning the mouse on or off unlocks the greeter

Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  - Ensure you have "no security/swiping" enabled for unlocking.
  - Switch the screen off and on, you get the greeter.
  - If your bluetooth mouse in off, turn it on. If it's on, turn it off.

  Expected result:
  Nothing in particular, the UX of the greeter does not change between desktop 
and staged mode.

  What actually happens:
  The greeter unlocks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1589242/+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 1583802] Re: Keyboard layout is not respected in some places

I've just realised that this is extremely problematic on the tablet:
when you set a password to unlock, it will seem to not work in the
greeter because the greeter is stuck in QWERTY...

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

Title:
  Keyboard layout is not respected in some places

Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Incomplete

Bug description:
  I'm trying Unity8 on my desktop (and reporting bugs from there,
  cool!), I've followed Michael Hall's how to, so I have the same PPAs
  on my system.

  The keyboard layout is not the same everywhere in the OS. I switched
  to French and it works in most places, but in some others, an English
  keyboard persists. These other places include the greeter and the
  Online Accounts (the rest of the System Settings app seems fine). I'm
  not sure where else but I'll keep searching.

  I have to say, it has its advantages, since alt-gr does not work and I
  have to copy/paste things like "@"!

  Thanks for your great work, it's really exciting to see the progress!

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1583802/+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 1589242] Re: Turning the mouse on or off unlocks the greeter