[Touch-packages] [Bug 1172692]

[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/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:
  Won't Fix
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:
  Fix Released

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 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook

[Dirk F]

"So the fix could be what is proposed, or/and moving the packagekit hook
to the right place."

I'd say both.

I understand that, per
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1548480/comments/8,
the PackageKit side of the issue would be fixed if Ubuntu shipped
version 0.8.14 or later, which has been true since Xenial as Andreas
observes in comment #10.

Regarding the pm-utils fix, the problems seem to be that no-one is
prepared to own and update pm-utils, and the systemd versions of Ubuntu
don't need pm-utils (in fact, could be seriously confused by it).
Consequently the fix should be implemented in Debian, as Christian says
in comment #7, where pm-utils has been recognised as orphaned and is
still being updated despite Debian using systemd.

-- 
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:
  Unknown
Status in pm-utils package in Ubuntu:
  Confirmed

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/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 1763611] Re: Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs

[Dirk F]

Please see my comments at https://bugs.launchpad.net/ubuntu/+source
/initramfs-tools/+bug/1644975/comments/12 and
https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/1644975/comments/10.

In summary, /etc/initramfs-tools/conf.d/resume is obsolete.

The resume process is supposed to be driven by kernel command-line
parameters resume and (optionally) resume_offset (which can be set by a
script during update-grub) and the script /etc/initramfs-tools/scripts
/local-premount/resume.

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

Title:
  Lubuntu bionic boots slower than the other Ubuntu flavours with some
  SSDs

Status in initramfs-tools package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Fix Released

Bug description:
  See this thread at the Ubuntu Forums:

  https://ubuntuforums.org/showthread.php?t=2388799

  How come the ultra light Lubuntu Bionic needs 40 seconds from the grub
  menu to the log in screen, while the corresponding Kubuntu and Xubuntu
  Bionic can do it in 10 seconds in my Toshiba laptop?

  All the operating systems were installed from the Bionic Beta-2
  desktop 64-bit iso files and made up to date today (and reside in a
  new SSD connected via the internal SATA bay).

  -o-

  and to summarize the conclusion

  
https://ubuntuforums.org/showthread.php?t=2388799=2=13756324#post13756324

  This supports the assumption, that there are problems for Lubuntu to
  manage SSDs with 4096 byte size physical sectors. But the other
  flavours of Ubuntu can manage it.

  Let us hope that this can help the Lubuntu developer to find and
  squash the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lubuntu-desktop 0.93
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Apr 13 09:59:42 2018
  InstallationDate: Installed on 2018-04-06 (7 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180405)
  SourcePackage: lubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1763611/+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 1644975] Re: Resume from disk (swapfile) fails

[Dirk F]

In the related bug #1763611, it is concluded that the Ubiquity installer
incorrectly set up /etc/initramfs-tools/conf.d/resume to reference a
non-existent disk UUID, causing a 30-40s delay in startup.

Surely that file is obsolete (because it doesn't help resume from
swapfile, eg) and should be removed from the installation?

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

Title:
  Resume from disk (swapfile) fails

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Debian:
  Incomplete

Bug description:
  Well, hibernation with swap file doesn't work while hibernation with
  swap partition works perfectly fine with the exactly same
  configuration and hardware.

  The reason is that when resuming from swap file, initramfs script
  can't correctly detect the machine are hibernated from the last shut
  down.

  And I investigated the issue and found this patch solved
  https://bugs.launchpad.net/ubuntu/+source/initramfs-
  tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the
  hibernate to work.

  And it isn't applied to the package. I'd like to help this is really
  applied to the official package.

  In short, my setup is swapfile inside the system filesystem (LUKS +
  LVM2 + ext4).

  Also, I roughly followed this tutorial to prepare this configurartion
  that: https://ubuntuforums.org/showthread.php?t=1042946

  I've opening this bug because the original bug report is closed and
  getting no response...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1644975/+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 1644975] Re: Resume from disk (swapfile) fails

[Dirk F]

If the swapfile is available as the initrd is handing over to the real
system, then it should work (in Bionic and fixed versions back probably
beyond Xenial).

What would happen is something like this:

- Grub[2] is loaded from yr /boot, an unencrypted partition or perhaps a
USB stick

- Grub loads the initial ram disk (named initrd* but an initramfs in
recent Linuxes) image which is responsible for loading the actual system

- the initrd discovers your physical, logical and encrypted disk devices
and will attempt to chain to the "actual" boot device as specified in
/boot/grub/grub.cfg ("the system disk")

- in this process you have to supply your passphrase or keyfile or token
to allow the encrypted system disk to be mounted

- finally the initrd morphs into the system on the system disk.

When resuming from hybrid-sleep (s2both) or hibernation, it is the
initrd script /scripts/local-premount/resume, copied to the initrd from
/usr/share/initramfs-tools by update-initramfs, that parses the resume
and resume_offset kernel parameters from the grub.cfg linux command
line. Those parameters may have been entered by hand or by an add-on
script in /etc/default/grub (in which case update-grub would be needed
to add the parameters).

The initrd resume script, which runs in a environment where all the
kernel command-line parameters are available as shell variables, has to
translate the resume parameters into a major:minor[:offset] format that
is understood by the kernel when written to /sys/power/resume.

If the resume parameters are set, the resume script will have to mount
the system disk to verify whether there is a resumable image, and that
should trigger the password prompt/use of keyfile or token. You can
debug the resume script using the break=premount kernel command-line
setting, which leaves you in a limited Busybox shell just before the
script would run (Ctrl+D to continue booting).

If the initrd kernel succeeds in loading the resumable image, it will be
directly overlaid by the image and you will get a running system as it
was when hibernated/hybrid-slept. If not, it will become a newly started
system from the root of the encrypted system disk.

When initiating hibernate or hybrid-sleep, the kernel knows about your
swapfile and will use it automatically (if it's big enough and there is
enough free memory to prepare the image) through the sys/power
interface. If your swapfile is on the encrypted system disk (or another
encrypted disk), it will automatically be protected.

In systemd versions, a small binary (why?) invokes the necessary
commands (printf "suspend|platform|shutdown"> /sys/power/disk; printf
"disk"> /sys/power/state) driven by sleep.conf(5); before that the pm-
utils kernel method attempted to do the same. It might seem logical to
stash the resume info at this point, but that's not what happens: would
you want a failed hibernation to destroy your grub.cfg?

This series of processes doesn't seem to be clearly laid out anywhere
but I thought it worth recording in case anyone wanted to implement
swapfile hibernation on pre-Bionic versions.

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

Title:
  Resume from disk (swapfile) fails

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Debian:
  Incomplete

Bug description:
  Well, hibernation with swap file doesn't work while hibernation with
  swap partition works perfectly fine with the exactly same
  configuration and hardware.

  The reason is that when resuming from swap file, initramfs script
  can't correctly detect the machine are hibernated from the last shut
  down.

  And I investigated the issue and found this patch solved
  https://bugs.launchpad.net/ubuntu/+source/initramfs-
  tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the
  hibernate to work.

  And it isn't applied to the package. I'd like to help this is really
  applied to the official package.

  In short, my setup is swapfile inside the system filesystem (LUKS +
  LVM2 + ext4).

  Also, I roughly followed this tutorial to prepare this configurartion
  that: https://ubuntuforums.org/showthread.php?t=1042946

  I've opening this bug because the original bug report is closed and
  getting no response...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1644975/+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 1644975] Re: Resume from disk (swapfile) fails

[Dirk F]

In the latest upstream version 0.130
, the faulty script has been rewritten, with
supporting sourced scripts.

Perhaps a better solution would be for Ubuntu to pull in this version,
and repackage it for Aardvark and LTS releases.

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

Title:
  Resume from disk (swapfile) fails

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Debian:
  New

Bug description:
  Well, hibernation with swap file doesn't work while hibernation with
  swap partition works perfectly fine with the exactly same
  configuration and hardware.

  The reason is that when resuming from swap file, initramfs script
  can't correctly detect the machine are hibernated from the last shut
  down.

  And I investigated the issue and found this patch solved
  https://bugs.launchpad.net/ubuntu/+source/initramfs-
  tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the
  hibernate to work.

  And it isn't applied to the package. I'd like to help this is really
  applied to the official package.

  In short, my setup is swapfile inside the system filesystem (LUKS +
  LVM2 + ext4).

  Also, I roughly followed this tutorial to prepare this configurartion
  that: https://ubuntuforums.org/showthread.php?t=1042946

  I've opening this bug because the original bug report is closed and
  getting no response...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1644975/+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 1644975] Re: Resume from disk (swapfile) fails

[Dirk F]

Bug 983805 also applies to the /usr/share/initramfs-tools/scripts/local-
premount/resume script.

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

Title:
  Resume from disk (swapfile) fails

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Debian:
  New

Bug description:
  Well, hibernation with swap file doesn't work while hibernation with
  swap partition works perfectly fine with the exactly same
  configuration and hardware.

  The reason is that when resuming from swap file, initramfs script
  can't correctly detect the machine are hibernated from the last shut
  down.

  And I investigated the issue and found this patch solved
  https://bugs.launchpad.net/ubuntu/+source/initramfs-
  tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the
  hibernate to work.

  And it isn't applied to the package. I'd like to help this is really
  applied to the official package.

  In short, my setup is swapfile inside the system filesystem (LUKS +
  LVM2 + ext4).

  Also, I roughly followed this tutorial to prepare this configurartion
  that: https://ubuntuforums.org/showthread.php?t=1042946

  I've opening this bug because the original bug report is closed and
  getting no response...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1644975/+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 1644975] Re: Resume from disk (swapfile) fails

[Dirk F]

** Also affects: initramfs-tools (Debian)
   Importance: Undecided
   Status: New

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

Title:
  Resume from disk (swapfile) fails

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Debian:
  New

Bug description:
  Well, hibernation with swap file doesn't work while hibernation with
  swap partition works perfectly fine with the exactly same
  configuration and hardware.

  The reason is that when resuming from swap file, initramfs script
  can't correctly detect the machine are hibernated from the last shut
  down.

  And I investigated the issue and found this patch solved
  https://bugs.launchpad.net/ubuntu/+source/initramfs-
  tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the
  hibernate to work.

  And it isn't applied to the package. I'd like to help this is really
  applied to the official package.

  In short, my setup is swapfile inside the system filesystem (LUKS +
  LVM2 + ext4).

  Also, I roughly followed this tutorial to prepare this configurartion
  that: https://ubuntuforums.org/showthread.php?t=1042946

  I've opening this bug because the original bug report is closed and
  getting no response...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1644975/+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 1644975] Re: Resume from disk (swapfile) fails

[Dirk F]

Reviewing the patch from bug 554009, I have the following comments:

- as the patch sets SWAPTYPE, no need to set it in line 24 of the
original script immediately before the patch: just run wait-for-root (if
that is actually needed);

- the test for $resume_offset would be safer if it looked for a number, eg:
[ "${resume_offset}" -ge 0] 2>/dev/null

- lines 63-67 of the original script can be replaced by line 64 only: no
need for a separate resume_offset case.

I confirm that the patch enables hibernation and hybrid-sleep to a
/swapfile using uswsusp with LXLE 16.04 identifying as "4.4.0-96-generic
#119-Ubuntu SMP Tue Sep 12 14:58:51 UTC 2017 i686 i686 i686 GNU/Linux",
and also with the above changes.

Why is no-one picking this up? Still 3.5 years of support for Ubuntu
16.04 LTS.

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

Title:
  Resume from disk (swapfile) fails

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Well, hibernation with swap file doesn't work while hibernation with
  swap partition works perfectly fine with the exactly same
  configuration and hardware.

  The reason is that when resuming from swap file, initramfs script
  can't correctly detect the machine are hibernated from the last shut
  down.

  And I investigated the issue and found this patch solved
  https://bugs.launchpad.net/ubuntu/+source/initramfs-
  tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the
  hibernate to work.

  And it isn't applied to the package. I'd like to help this is really
  applied to the official package.

  In short, my setup is swapfile inside the system filesystem (LUKS +
  LVM2 + ext4).

  Also, I roughly followed this tutorial to prepare this configurartion
  that: https://ubuntuforums.org/showthread.php?t=1042946

  I've opening this bug because the original bug report is closed and
  getting no response...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1644975/+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

[Dirk F]

Per the original report:

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

Which might have an effect worse than just disconcerting a reader of
/var/log/pm-suspend.log.

Anyhow, even if it's not worth it for the remaining 18 months of 14.04
LTS, the means to pay off the technical debt is there.

-- 
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:
  Fix Released

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

[Dirk F]

Thanks Matthias, Amr.

I reported this against Trusty LTS and the Fix would mean back-porting
or otherwise introducing 0.8.17 over 0.8.12, probably not going to
happen.

So that the unnecessary, wrongly named and wrongly located file might be
removed (though I suppose anyone who cares can actually do so
themselves), a patch is needed against the packaging of PackageKit in
Trusty.

I can't see a way to file a bug against a particular release's packaging
of a package, so I've linked this to the Trusty branches with a
suggested distribution patch for /contrib/pm-utils/Makefile.am that
should omit the redundant file and remove it if present.


** Attachment added: "Suggested change to 
"
   
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1548480/+attachment/4956761/+files/Makefile.am.dif

-- 
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:
  Fix Released

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

[Dirk F]

If you are going to mark this as Fix Released let's see:

what is the fix?

which supported Ubuntu versions are fixed?

** Changed in: packagekit (Ubuntu)
   Status: Fix Released => Incomplete

** Changed in: packagekit (Ubuntu)
   Status: Incomplete => Confirmed

-- 
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:
  Confirmed

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

Re: [Touch-packages] [Bug 1548486] Sleep hook in a subdirectory ignored but causes double execution of previous hook

[Dirk F]

On 2017-07-14 09:58, Christian Ehrhardt wrote:
> I revisit dormant bugs on a regular scheduling following our triaging policy.
> It seems nothing happened upstream still.
> 
> For the Debian reporting you can do so through the mail interface - you don't 
> need a Debian system.
> Usually it is preferred that the reporter does so, but if you need help or 
> want me to do that please ping here and I'll do so.

Happy for you to do that, as Debian still seems to be interested in 
pm-utils. Not sure what stops Debian package maintainers from checking 
the upstream bug tracker, however.

/df

-- 
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:
  Unknown
Status in pm-utils package in Ubuntu:
  Confirmed

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/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 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook

[Dirk F]

Christian, thanks for looking at this.

I'd definitely encourage someone with a relevant Debian installation to
reportbug this, and indeed any of the bugs that I've reported in pm-
utils but remain ignored upstream.

-- 
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:
  Unknown
Status in pm-utils package in Ubuntu:
  Confirmed

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/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 1415039] Re: laptop unresponsive after suspend

[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 1548392] Re: Fix for 1172692 fails to restore hibernation mode with suspend-hybrid

[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 1394388] Re: pm-suspend not restoring /sys/power/disk with /bin/dash

[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 1580223] [NEW] 'gdbus call' can't handle arguments containing '&' (XML escaping failure) failure

[Dirk F]

Public bug reported:

When gdbus is used with the call subcommand, string arguments passed to
the called method that contain the character '&' are treated as empty
"". Presumably this also affects the emit subcommand.

The problem appears to be that internally the arguments are processed as
XML but not safely escaped, as shown in the tests below.

>From the gdbus man page, try this example:

gdbus call --session --dest org.freedesktop.Notifications \
   --object-path /org/freedesktop/Notifications \
   --method org.freedesktop.Notifications.Notify \
   my_app_name \
   42 \
   gtk-dialog-info \
   "The Summary" \
   "Here's the body of the notification" \
   [] {} 5000

A notification is displayed with the information icon, the summary and
the body.

Now try

gdbus call --session --dest org.freedesktop.Notifications \
   --object-path /org/freedesktop/Notifications \
   --method org.freedesktop.Notifications.Notify \
   my_app_name \
   42 \
   gtk-dialog-info \
   "The Summary" \
   "Here's the body containing '&' of the notification" \
   [] {} 5000

A notification is displayed with the information icon, the summary and
*no* body.

Now try

gdbus call --session --dest org.freedesktop.Notifications \
   --object-path /org/freedesktop/Notifications \
   --method org.freedesktop.Notifications.Notify \
   my_app_name \
   42 \
   gtk-dialog-info \
   "The Summary" \
   "Here's the body containing '' of the notification" \
   [] {} 5000

A notification is displayed with the information icon, the summary and
this body

"Here's the body containing '&' of the notification"

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libglib2.0-bin 2.40.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-36.41~14.04.1-generic 4.2.8-ckt8
Uname: Linux 4.2.0-36-generic i686
ApportVersion: 2.14.1-0ubuntu3.20
Architecture: i386
CurrentDesktop: LXDE
Date: Tue May 10 15:56:44 2016
InstallationDate: Installed on 2016-02-21 (78 days ago)
InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1)
SourcePackage: glib2.0
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  'gdbus call' can't handle arguments containing '&' (XML escaping
  failure) failure

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  When gdbus is used with the call subcommand, string arguments passed
  to the called method that contain the character '&' are treated as
  empty "". Presumably this also affects the emit subcommand.

  The problem appears to be that internally the arguments are processed
  as XML but not safely escaped, as shown in the tests below.

  From the gdbus man page, try this example:

  gdbus call --session --dest org.freedesktop.Notifications \
 --object-path /org/freedesktop/Notifications \
 --method org.freedesktop.Notifications.Notify \
 my_app_name \
 42 \
 gtk-dialog-info \
 "The Summary" \
 "Here's the body of the notification" \
 [] {} 5000

  A notification is displayed with the information icon, the summary and
  the body.

  Now try

  gdbus call --session --dest org.freedesktop.Notifications \
 --object-path /org/freedesktop/Notifications \
 --method org.freedesktop.Notifications.Notify \
 my_app_name \
 42 \
 gtk-dialog-info \
 "The Summary" \
 "Here's the body containing '&' of the notification" \
 [] {} 5000

  A notification is displayed with the information icon, the summary and
  *no* body.

  Now try

  gdbus call --session --dest org.freedesktop.Notifications \
 --object-path /org/freedesktop/Notifications \
 --method org.freedesktop.Notifications.Notify \
 my_app_name \
 42 \
 gtk-dialog-info \
 "The Summary" \
 "Here's the body containing '' of the notification" \
 [] {} 5000

  A notification is displayed with the information icon, the summary and
  this body

  "Here's the body containing '&' of the notification"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libglib2.0-bin 2.40.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-36.41~14.04.1-generic 4.2.8-ckt8
  Uname: Linux 4.2.0-36-generic i686
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Tue May 10 15:56:44 2016
  InstallationDate: Installed on 2016-02-21 (78 days ago)
  InstallationMedia: Lubuntu 

[Touch-packages] [Bug 1548392]

[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 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook

[Dirk F]

Upstream bug with patch at


** 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 1548480] Re: 95packagekit sleep hook weirdly installed in a subdirectory is ignored

[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 1172692]

[Dirk F]

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 1172692]

[Dirk F]

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]

[Dirk F]

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 1548853] [NEW] 00powersave sleep hook misses claimed patch

[Dirk F]

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 1414110] Re: Wireless powersave doesn't work (pm-utils)

[Dirk F]

*** 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 1443249] Re: After kernel-3.13.0-41, wireless script checks wrong sys file.

[Dirk F]

*** 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 1548480] Re: 95packagekit sleep hook weirdly installed in a subdirectory is ignored

[Dirk F]

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 1548480] Re: 95packagekit sleep hook weirdly installed in a subdirectory is ignored

[Dirk F]

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 1548486] [NEW] Sleep hook in a subdirectory ignored but causes double execution of previous hook

[Dirk F]

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 i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

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

[Dirk F]

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 1548392] [NEW] Fix for 1172692 fails to restore hibernation mode with suspend-hybrid

[Dirk F]

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 1544612] Re: Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

[Dirk F]

Confirmed fix with 1.4.1-13ubuntu0.2, other details per original report.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

Status in pm-utils package in Ubuntu:
  Fix Released
Status in pm-utils source package in Trusty:
  Fix Committed
Status in pm-utils package in Debian:
  Fix Released

Bug description:
  The patch debian/patches/17-fix-wireless-hook.patch for bug 1299975 is
  supposed to be applied in pm-utils (1.4.1-13ubuntu0.1) but is not
  installed in that version from trusty-updates.

  The file /usr/lib/pm-utils/power.d/wireless dated 2014-07-15 16:15 (attached) 
supposedly installed by the updated package still contains line 23
 [ "$(cat /sys/class/net/$1/device/enabled)" = "1" ] || return 1
  which should be 
 [ "$(cat /sys/class/net/$1/device/enable)" = "1" ] || return 1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 3.13.0-78.122-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-78-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Thu Feb 11 15:10:05 2016
  InstallationDate: Installed on 2014-07-15 (576 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.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/1544612/+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 1544612] Re: Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

[Dirk F]

Thanks, Martin.

But, the absence of the enable[d] file is apparently a legitimate case,
and your patch as it stands causes an undesirable error message in the
PM log in that case, such as:

cat: /sys/class/net/wlan0/device/enable*: No such file or directory

Hence my original proposed test for the file's existence.

As an alternative you could have $(cat  2>/dev/null) but that would
risk masking a genuine error.

Incidentally, with a fix similar to the one you committed in place, I've
observed that the b43 driver, which gets the default power-save command
(lines 41-2 of wireless script)  currently fails to respect the command,
eg:

# iwconfig wlan0 power on
Error for wireless request "Set Power Management" (8B2C) :
SET failed on device wlan0 ; Operation not supported.

Although the script has special cases for certain Intel drivers and you
could add eg new line 41 before the default case

b43) return1;;

I wouldn't recommend doing so both to avoid complexity (don't want it to
end up like pmutils video quirks) and more importantly in case a future
version of the driver fixes the lack of power-saving support.

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

Title:
  Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

Status in pm-utils package in Ubuntu:
  Fix Released
Status in pm-utils source package in Trusty:
  In Progress
Status in pm-utils package in Debian:
  Fix Released

Bug description:
  The patch debian/patches/17-fix-wireless-hook.patch for bug 1299975 is
  supposed to be applied in pm-utils (1.4.1-13ubuntu0.1) but is not
  installed in that version from trusty-updates.

  The file /usr/lib/pm-utils/power.d/wireless dated 2014-07-15 16:15 (attached) 
supposedly installed by the updated package still contains line 23
 [ "$(cat /sys/class/net/$1/device/enabled)" = "1" ] || return 1
  which should be 
 [ "$(cat /sys/class/net/$1/device/enable)" = "1" ] || return 1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 3.13.0-78.122-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-78-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Thu Feb 11 15:10:05 2016
  InstallationDate: Installed on 2014-07-15 (576 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.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/1544612/+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 1544612] Re: Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

[Dirk F]

Actually, this is more tricky than I thought. The validity of the bug
1299975 patch depends on which wireless driver is in use, apparently
reflecting some crufty aspects of sysfs and its driver implementations.

In bug 1299975, on rereading, the reporter (savage) says that with an
Intel wireless device the virtual file presented in
/sys/class/net/$device/device was named "enabled" whereas the script
/usr/lib/pm-utils/power.d/wireless referenced "enable".

Whereas I observe that, if present, the virtual file presented in
/sys/class/net/$device/device is named "enable", just as in the
directory listing in comment #3.

In a Toshiba Tecra 8200 with wlan1 identified as Qualcomm Atheros
ARS212/5213/2414 (driver "ath5k"), it's present as "enable".

In a Dell Inspiron 1721 with wlan0 identified as Broadcom Corporation
BCM4321 (driver "b43-pci-bridge"), it's not present at all in
/sys/class/net/$device/device, but there is a corresponding
/sys/bus/pci/drivers/b43-pci-bridge/:0b:00.0/enable (and writing 0
to this file disables the driver). However the test in the wireless
script assumes that the device is disabled if the
/sys/class/net/$device/device/enable* file doesn't exist, so the script
fails in this case.

Presumably

a) the presence of the /sys/class/net/$device/device/enable* file
depends on whether the ability to disable the device via
/sys/class/net/$device/device is supported by the device+driver
combination,

b) if the file is present its exact name depends on some details of the
driver's sysfs interface and installation procedure, but it is either
"enable" or "enabled" (and both are never present together), and

c) if the file is not present the wireless script should assume the
device is enabled.

If these assumptions are valid, the following might be a better bet for
lines 22-23 of /usr/lib/pm-utils/power.d/wireless:

# Assume device is disabled if enable or enabled file exists containing 0; 
then skip
[ -f /sys/class/net/$1/device/enable* ] && [ "$(cat 
/sys/class/net/$1/device/enable*)" = "0" ] && return 1

Obviously there are multiline options that could be more precise.

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

Title:
  Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

Status in pm-utils package in Ubuntu:
  New

Bug description:
  The patch debian/patches/17-fix-wireless-hook.patch for bug 1299975 is
  supposed to be applied in pm-utils (1.4.1-13ubuntu0.1) but is not
  installed in that version from trusty-updates.

  The file /usr/lib/pm-utils/power.d/wireless dated 2014-07-15 16:15 (attached) 
supposedly installed by the updated package still contains line 23
 [ "$(cat /sys/class/net/$1/device/enabled)" = "1" ] || return 1
  which should be 
 [ "$(cat /sys/class/net/$1/device/enable)" = "1" ] || return 1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 3.13.0-78.122-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-78-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Thu Feb 11 15:10:05 2016
  InstallationDate: Installed on 2014-07-15 (576 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.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/1544612/+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 1544612] [NEW] Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

[Dirk F]

Public bug reported:

The patch debian/patches/17-fix-wireless-hook.patch for bug 1299975 is
supposed to be applied in pm-utils (1.4.1-13ubuntu0.1) but is not
installed in that version from trusty-updates.

The file /usr/lib/pm-utils/power.d/wireless dated 2014-07-15 16:15 (attached) 
supposedly installed by the updated package still contains line 23
   [ "$(cat /sys/class/net/$1/device/enabled)" = "1" ] || return 1
which should be 
   [ "$(cat /sys/class/net/$1/device/enable)" = "1" ] || return 1

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pm-utils 1.4.1-13ubuntu0.1 [modified: usr/lib/pm-utils/pm-functions]
ProcVersionSignature: Ubuntu 3.13.0-78.122-generic 3.13.11-ckt33
Uname: Linux 3.13.0-78-generic i686
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
CurrentDesktop: LXDE
Date: Thu Feb 11 15:10:05 2016
InstallationDate: Installed on 2014-07-15 (576 days ago)
InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
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 regression-update trusty

** Attachment added: "/usr/lib/pm-utils/power.d/wireless 2014-07-15 16:15"
   https://bugs.launchpad.net/bugs/1544612/+attachment/4569338/+files/wireless

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

Title:
  Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

Status in pm-utils package in Ubuntu:
  New

Bug description:
  The patch debian/patches/17-fix-wireless-hook.patch for bug 1299975 is
  supposed to be applied in pm-utils (1.4.1-13ubuntu0.1) but is not
  installed in that version from trusty-updates.

  The file /usr/lib/pm-utils/power.d/wireless dated 2014-07-15 16:15 (attached) 
supposedly installed by the updated package still contains line 23
 [ "$(cat /sys/class/net/$1/device/enabled)" = "1" ] || return 1
  which should be 
 [ "$(cat /sys/class/net/$1/device/enable)" = "1" ] || return 1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 3.13.0-78.122-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-78-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Thu Feb 11 15:10:05 2016
  InstallationDate: Installed on 2014-07-15 (576 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.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/1544612/+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 1544612] Re: Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

[Dirk F]

NB The mod identified in the line from the automated package report  
Package: pm-utils 1.4.1-13ubuntu0.1 [modified: 
usr/lib/pm-utils/pm-functions]
arises from my manually applied fix for 
https://bugs.freedesktop.org/show_bug.cgi?id=52572.

It would be good to get that into the repos too.

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

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

Title:
  Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

Status in pm-utils package in Ubuntu:
  New

Bug description:
  The patch debian/patches/17-fix-wireless-hook.patch for bug 1299975 is
  supposed to be applied in pm-utils (1.4.1-13ubuntu0.1) but is not
  installed in that version from trusty-updates.

  The file /usr/lib/pm-utils/power.d/wireless dated 2014-07-15 16:15 (attached) 
supposedly installed by the updated package still contains line 23
 [ "$(cat /sys/class/net/$1/device/enabled)" = "1" ] || return 1
  which should be 
 [ "$(cat /sys/class/net/$1/device/enable)" = "1" ] || return 1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 3.13.0-78.122-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-78-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Thu Feb 11 15:10:05 2016
  InstallationDate: Installed on 2014-07-15 (576 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.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/1544612/+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 1299975] Re: wireless script checks wrong sys file

[Dirk F]

See regression bug 1544612.

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

Title:
  wireless script checks wrong sys file

Status in pm-utils package in Ubuntu:
  Fix Released
Status in pm-utils source package in Trusty:
  Fix Released

Bug description:
  TEST CASE: 
  - on a machine with a wireless interface, run:  
PM_FUNCTIONS=/usr/lib/pm-utils/functions sh -ex  
/usr/lib/pm-utils/power.d/wireless true
and verify that it fails with /sys/class/net/wlan0/device/enable: No such 
file or directory
  - install the update and run the command again and verify that the script 
continue beyond the point it stopped earlier, i.e. that it stops at a later 
point when running e.g. iwconfig 
  - now powersaving for wireless via pm-utils should work as intended from the 
script

  REGRESSION POTENTIAL:
  - the functionality in the script was completely broken before, by fixing 
this bug any bug in the power management that were previously hidden may now be 
uncovered. 

  On Trusty (beta), while trying to diagnose an issue with the wireless
  not connecting upon resume from standby, I discovered an invalid check
  in '/usr/lib/pm-utils/power.d/wireless'.  The script checks
  '/sys/class/net/$1/device/enable' to see if the wireless device is
  enabled, failing to perform any configuration if this sys file does
  not exist.  That happens to be the case for me (intel wireless), which
  the actual location is '/sys/class/net/$1/device/enabled' (enable ->
  enabled).

  Changing the script to use the correct location has not fixed my
  wireless resume issue, but perhaps it is contributing to wireless
  issues for others.  My wireless power-saving is correctly turned off
  upon resume now, though (it would get stuck in power-saving mode
  sometimes).

  $> lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  $> apt-cache policy pm-utils
  pm-utils:
    Installed: 1.4.1-13
    Candidate: 1.4.1-13
    Version table:
   *** 1.4.1-13 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1299975/+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 209018] Re: thinkpad R30 resolution problem / trident cyberblade 1l

[Dirk F]

Result for Lubuntu 14.04 on Toshiba Tecra 8200 (Trident CyberBlade/XP):

- 1024x768 is available with both trident and vesa drivers, at least if
specified in the Monitor and Screen sections of xorg.conf (as previously
attached for 10.10.)

xorg-server 2:1.15.1-0ubuntu2.6

Module vesa: vendor=X.Org Foundation, compiled for 1.15.0, module version = 
2.3.3
Module trident: vendor=X.Org Foundation, compiled for 1.15.0, module version 
= 1.3.6

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

Title:
  thinkpad R30 resolution problem / trident cyberblade 1l

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I installed Gutsy, xorg was able to give me 1024x768 resolution.

  I installed Hardy Beta and my max resolution is only 800x600.

  There should be one more option for 1024x768 for my ThinkPad R30

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/209018/+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 1367386] [NEW] Xorg crash with Trident driver after Xubuntu upgrade to Trusty

[Dirk F]

Public bug reported:

After upgrading Xubuntu 12.04 LTS - 14.04.1 LTS, system boots to black
screen instead of desktop environment,  but single user command line
works fine. Problem traced to xorg-server segfault crash in the Trident
driver as below (summary of details already uploaded). The code attempts
a call to an offset against eax which is a null pointer.

After changing the acceleration architecture from XAA to EXA with 
Option AccelMethodexa
in the Trident Device section of xorg.conf, the desktop environment loaded 
successfully.

Maybe this option should now be the default for Trident?

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Sep  9 13:26:36 2014
DistroRelease: Ubuntu 14.04
ExecutablePath: /usr/bin/Xorg
ExecutableTimestamp: 1406679727
ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nol
isten tcp vt7 -novtswitch
ProcCwd: /etc/X11
ProcEnviron: 

Disassembly:
 = 0xb6cb39d1: call   *0x6c(%eax)
0xb6cb39d4: jmp0xb6cb3979
0xb6cb39d6: lea0x0(%esi),%esi
0xb6cb39d9: lea0x0(%edi,%eiz,1),%edi
0xb6cb39e0: push   %ebp
0xb6cb39e1: mov%eax,%ebp
0xb6cb39e3: push   %edi
0xb6cb39e4: xor%edi,%edi
0xb6cb39e6: push   %esi
0xb6cb39e7: mov$0x2,%esi
0xb6cb39ec: push   %ebx
0xb6cb39ed: sub$0x1c,%esp
0xb6cb39f0: mov0x18(%eax),%eax
0xb6cb39f3: call   0xb6caa4f0
0xb6cb39f8: add$0x14608,%ebx
0xb6cb39fe: sub$0x17,%eax
Package: xserver-xorg-core 2:1.15.1-0ubuntu2.1
PackageArchitecture: i386
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Registers:
 eax0x0 0
 ecx0x0 0
 edx0xb96d7cb0  -1184006992
 ebx0xb6cc8000  -1228111872
 esp0xbf887300  0xbf887300
 ebp0xb96d5688  0xb96d5688
 esi0xb96d3f98  -1184022632
 edi0xb96d43f8  -1184021512
 eip0xb6cb39d1  0xb6cb39d1
 eflags 0x213202[ IF #12 #13 RF ID ]
 cs 0x73115
 ss 0x7b123
 ds 0x7b123
 es 0x7b123
 fs 0x0 0
 gs 0x3351
SegvAnalysis:
 Segfault happened at: 0xb6cb39d1:  call   *0x6c(%eax)
 PC (0xb6cb39d1) ok
 source *0x6c(%eax) ok
 destination (%esp) (0xbf887300) ok
 SP (0xbf887300) ok
 Reason could not be automatically determined.
SourcePackage: xorg-server
...
Title: Xorg crashed with SIGSEGV in xf86VTSwitch()
UpgradeStatus: Upgraded to trusty on 2014-09-07 (2 days ago)
_MarkForUpload: True

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic i686
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: i386
CurrentDesktop: XFCE
Date: Tue Sep  9 18:09:01 2014
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-09-07 (2 days ago)

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

Title:
  Xorg crash with Trident driver after Xubuntu upgrade to Trusty

Status in “xorg” package in Ubuntu:
  New

Bug description:
  After upgrading Xubuntu 12.04 LTS - 14.04.1 LTS, system boots to
  black screen instead of desktop environment,  but single user command
  line works fine. Problem traced to xorg-server segfault crash in the
  Trident driver as below (summary of details already uploaded). The
  code attempts a call to an offset against eax which is a null pointer.

  After changing the acceleration architecture from XAA to EXA with 
  Option AccelMethodexa
  in the Trident Device section of xorg.conf, the desktop environment loaded 
successfully.

  Maybe this option should now be the default for Trident?

  ProblemType: Crash
  Architecture: i386
  CrashCounter: 1
  Date: Tue Sep  9 13:26:36 2014
  DistroRelease: Ubuntu 14.04
  ExecutablePath: /usr/bin/Xorg
  ExecutableTimestamp: 1406679727
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nol
  isten tcp vt7 -novtswitch
  ProcCwd: /etc/X11
  ProcEnviron: 

  Disassembly:
   = 0xb6cb39d1:   call   *0x6c(%eax)
  0xb6cb39d4:   jmp0xb6cb3979
  0xb6cb39d6:   lea0x0(%esi),%esi
  0xb6cb39d9:   lea0x0(%edi,%eiz,1),%edi
  0xb6cb39e0:   push   %ebp
  0xb6cb39e1:   mov%eax,%ebp
  0xb6cb39e3:   push   %edi
  0xb6cb39e4:   xor%edi,%edi
  0xb6cb39e6:   push   %esi
  0xb6cb39e7:   mov$0x2,%esi
  0xb6cb39ec:   push   %ebx
  0xb6cb39ed:   sub$0x1c,%esp
  0xb6cb39f0:   mov0x18(%eax),%eax
  0xb6cb39f3:   call   0xb6caa4f0
  0xb6cb39f8:   add$0x14608,%ebx
  0xb6cb39fe:   sub$0x17,%eax
  

[Touch-packages] [Bug 1367386] Re: Xorg crash with Trident driver after Xubuntu upgrade to Trusty

[Dirk F]

Whereas in 10.10, the reverse problem occurred (bug 209018): XAA worked
and EXA crashed.

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

Title:
  Xorg crash with Trident driver after Xubuntu upgrade to Trusty

Status in “xorg” package in Ubuntu:
  New

Bug description:
  After upgrading Xubuntu 12.04 LTS - 14.04.1 LTS, system boots to
  black screen instead of desktop environment,  but single user command
  line works fine. Problem traced to xorg-server segfault crash in the
  Trident driver as below (summary of details already uploaded). The
  code attempts a call to an offset against eax which is a null pointer.

  After changing the acceleration architecture from XAA to EXA with 
  Option AccelMethodexa
  in the Trident Device section of xorg.conf, the desktop environment loaded 
successfully.

  Maybe this option should now be the default for Trident?

  ProblemType: Crash
  Architecture: i386
  CrashCounter: 1
  Date: Tue Sep  9 13:26:36 2014
  DistroRelease: Ubuntu 14.04
  ExecutablePath: /usr/bin/Xorg
  ExecutableTimestamp: 1406679727
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nol
  isten tcp vt7 -novtswitch
  ProcCwd: /etc/X11
  ProcEnviron: 

  Disassembly:
   = 0xb6cb39d1:   call   *0x6c(%eax)
  0xb6cb39d4:   jmp0xb6cb3979
  0xb6cb39d6:   lea0x0(%esi),%esi
  0xb6cb39d9:   lea0x0(%edi,%eiz,1),%edi
  0xb6cb39e0:   push   %ebp
  0xb6cb39e1:   mov%eax,%ebp
  0xb6cb39e3:   push   %edi
  0xb6cb39e4:   xor%edi,%edi
  0xb6cb39e6:   push   %esi
  0xb6cb39e7:   mov$0x2,%esi
  0xb6cb39ec:   push   %ebx
  0xb6cb39ed:   sub$0x1c,%esp
  0xb6cb39f0:   mov0x18(%eax),%eax
  0xb6cb39f3:   call   0xb6caa4f0
  0xb6cb39f8:   add$0x14608,%ebx
  0xb6cb39fe:   sub$0x17,%eax
  Package: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Registers:
   eax0x0   0
   ecx0x0   0
   edx0xb96d7cb0-1184006992
   ebx0xb6cc8000-1228111872
   esp0xbf8873000xbf887300
   ebp0xb96d56880xb96d5688
   esi0xb96d3f98-1184022632
   edi0xb96d43f8-1184021512
   eip0xb6cb39d10xb6cb39d1
   eflags 0x213202  [ IF #12 #13 RF ID ]
   cs 0x73  115
   ss 0x7b  123
   ds 0x7b  123
   es 0x7b  123
   fs 0x0   0
   gs 0x33  51
  SegvAnalysis:
   Segfault happened at: 0xb6cb39d1:call   *0x6c(%eax)
   PC (0xb6cb39d1) ok
   source *0x6c(%eax) ok
   destination (%esp) (0xbf887300) ok
   SP (0xbf887300) ok
   Reason could not be automatically determined.
  SourcePackage: xorg-server
  ...
  Title: Xorg crashed with SIGSEGV in xf86VTSwitch()
  UpgradeStatus: Upgraded to trusty on 2014-09-07 (2 days ago)
  _MarkForUpload: True

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic i686
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Sep  9 18:09:01 2014
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-09-07 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1367386/+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