[Desktop-packages] [Bug 1890939] Re: [snap] The SUID sandbox helper binary was found, but is not configured correctly.
The current version (1284) works OK and the SUID bits are back: ``` $ ls -l /snap/chromium/current/usr/lib/chromium-browser/chrome-sandbox -r-sr-xr-x 1 root root 333952 Aug 29 14:43 /snap/chromium/current/usr/lib/chromium-browser/chrome-sandbox $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: today at 09:06 CEST channels: latest/stable:85.0.4183.83 2020-08-29 (1284) 169MB - latest/candidate: 85.0.4183.83 2020-08-29 (1284) 169MB - latest/beta: 85.0.4183.76 2020-08-24 (1271) 167MB - latest/edge: 86.0.4240.8 2020-08-27 (1278) 168MB - installed: 85.0.4183.83(1284) 169MB - ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1890939 Title: [snap] The SUID sandbox helper binary was found, but is not configured correctly. Status in chromium-browser package in Ubuntu: Incomplete Bug description: The chromium snap version 1260 has the wrong mode for chrome-sandbox, as it happened also in bug #1854091: ``` $ /snap/bin/chromium [4009:4009:0809/115259.781182:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /snap/chromium/1260/usr/lib/chromium-browser/chrome-sandbox is owned by root and has mode 4755. Trace/breakpoint trap $ [4134:4134:0100/00.834554:ERROR:zygote_linux.cc(653)] write: Broken pipe (32) ``` I have reverted it to the previous version (1244) and this one works (and has the right mode for chromium-sandbox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890939] [NEW] [snap] The SUID sandbox helper binary was found, but is not configured correctly.
Public bug reported: The chromium snap version 1260 has the wrong mode for chrome-sandbox, as it happened also in bug #1854091: ``` $ /snap/bin/chromium [4009:4009:0809/115259.781182:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /snap/chromium/1260/usr/lib/chromium-browser/chrome-sandbox is owned by root and has mode 4755. Trace/breakpoint trap $ [4134:4134:0100/00.834554:ERROR:zygote_linux.cc(653)] write: Broken pipe (32) ``` I have reverted it to the previous version (1244) and this one works (and has the right mode for chromium-sandbox). ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: snap ** Tags added: snap ** Summary changed: - The SUID sandbox helper binary was found, but is not configured correctly. + [snap] The SUID sandbox helper binary was found, but is not configured correctly. ** Description changed: The chromium snap version 1260 has the wrong mode for chrome-sandbox, as - it happened also in bug #1854091): - + it happened also in bug #1854091: ``` $ /snap/bin/chromium [4009:4009:0809/115259.781182:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /snap/chromium/1260/usr/lib/chromium-browser/chrome-sandbox is owned by root and has mode 4755. Trace/breakpoint trap $ [4134:4134:0100/00.834554:ERROR:zygote_linux.cc(653)] write: Broken pipe (32) ``` I have reverted it to the previous version (1244) and this one works (and has the right mode for chromium-sandbox). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1890939 Title: [snap] The SUID sandbox helper binary was found, but is not configured correctly. Status in chromium-browser package in Ubuntu: New Bug description: The chromium snap version 1260 has the wrong mode for chrome-sandbox, as it happened also in bug #1854091: ``` $ /snap/bin/chromium [4009:4009:0809/115259.781182:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /snap/chromium/1260/usr/lib/chromium-browser/chrome-sandbox is owned by root and has mode 4755. Trace/breakpoint trap $ [4134:4134:0100/00.834554:ERROR:zygote_linux.cc(653)] write: Broken pipe (32) ``` I have reverted it to the previous version (1244) and this one works (and has the right mode for chromium-sandbox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1455097] Re: /etc/pm/sleep.d/ is no more processed
Hi Brian,
I can't help testing this new package since I'm not running Ubuntu on my
laptop anymore.
Cheers!
Alex
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1455097
Title:
/etc/pm/sleep.d/ is no more processed
Status in aiccu package in Ubuntu:
Invalid
Status in ceph package in Ubuntu:
Fix Released
Status in grub2 package in Ubuntu:
New
Status in ifplugd package in Ubuntu:
New
Status in lizardfs package in Ubuntu:
New
Status in oss4 package in Ubuntu:
New
Status in pm-utils package in Ubuntu:
Won't Fix
Status in toshset package in Ubuntu:
New
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Fix Committed
Bug description:
[Impact (unattended-upgrades)]
* Unattended-upgrades does not gracefully stop installing updates
when the system goes to hibernation potentially letting the system to
hibernate in a state where the system can't resume from.
[Test Case (unattended-upgrades)]
* Configure the system to have several 20+ packages upgradable by
unattended-upgrades. One easy way of setting this up is starting with
a system where packages from -security are installed but packages from
-updates are not and enabling -updates in u-u:
# echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' > /etc/apt/apt.conf.d
/51unattended-upgrades-updates-too
* Pre-download upgrades
# unattended-upgraded --download-only
* Trigger unattended-upgrades run:
# service apt-daily-upgrade start
* Hibernate, then resume the system and watch unattended-upgrades
being gracefully stopped, checking /var/log/unattended-upgrades
/unattended-upgrades.log. There should be packages left to be
upgraded.
[Regression Potential (unattended-upgrades)]
* The added hook for unattended-upgrades may block the system from
hibernation for 25 minutes if unattended-upgrades (or most likely a
package upgrades) hangs. There is a better solution proposed based on
systemd's inhibitor interface at https://github.com/mvo5/unattended-
upgrades/issues/162 .
[Original Bug Text]
I added a new script in /etc/pm/sleep.d/ that worked fine before the
upgrade to vivid. I was wondering why it doesn't work and I find out
that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last
logs from pm-suspend were on Apr 28, when I upgraded from utopic to
vivid.
The laptop suspends and wakes fine, it just seems that no pm scripts
are run after suspend/powersave.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: pm-utils 1.4.1-15
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 14 15:36:26 2015
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-precise-amd64-20120703-2
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-03-12 (792 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary
20120703-15:08
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/aiccu/+bug/1455097/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 974912] Re: net_gateway adds route on wrong interface
** Also affects: network-manager-openvpn via https://bugzilla.gnome.org/show_bug.cgi?id=673636 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/974912 Title: net_gateway adds route on wrong interface Status in NetworkManager-OpenVPN: Unknown Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: When using push route on server side to bypass the vpn for a specific subnet : push "route 1.2.3.0 255.255.255.0 net_gateway" The network manager registers the route on tun0 instead of net_gateway interface : NetworkManager[1149]: Static Route: 1.2.3.0/24 Next Hop: 1.2.3.0 See the route in kernel : 1.2.3.0 192.168.0.1 255.255.255.0 UG0 0 0 tun0 192.168.0.1 is on eth2 but route is registered on tun0 and traffic to 1.2.3.0/24 is sent to tun0 instead of eth2 When I launch openvpn in command line I get the correct route : us=482299 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dns bypass-dhcp,route 1.2.3.0 255.255.255.0 net_gateway,comp-lzo yes,route-gateway x.x.x.x,topology subnet,ping 10,ping-restart 120,ifconfig x.x.x.y 255.255.255.0' us=490292 /sbin/route add -net 1.2.3.0 netmask 255.255.255.0 gw 192.168.0.1 and the route appears on eth2 1.2.3.0 192.168.0.1 255.255.255.0 UG0 0 0 eth2 then traffic to 1.2.3.0/24 flows through eth2 as expected To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/974912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!
Just a quick note to confirm that removing and installing previous failing DKMS modules for kernel 4.4.0-116 as explained in comment 30, worked wonders for our issue with vboxdrv issue and retpoline. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler! Status in gcc: New Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1750937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 75850] Re: Pidgin should support OS keyrings
pidgin-gnome-keyring is available since xenial, shouldn't this bug report be fix released already? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/75850 Title: Pidgin should support OS keyrings Status in Gaim: Won't Fix Status in Pidgin: New Status in gaim package in Ubuntu: Invalid Status in pidgin package in Ubuntu: Fix Committed Bug description: Pidgin should support GNOME Keyring, KWallet, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/gaim/+bug/75850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1455097] Re: pm-suspend.log and pm-powersave.log not updated since upgrade to vivid
On the other side I removed pm-utils from the system and there are a couple of remaining scripts in /etc/pm/sleep.d that are worth mentioning: * 10_grub-common * 10_unattended-upgrades-hibernate Thus, those packages are also affected by this bug I guess. ** Also affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - pm-suspend.log and pm-powersave.log not updated since upgrade to vivid + pm-suspend no longer run since upgrade to vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1455097 Title: pm-suspend no longer run since upgrade to vivid Status in grub2 package in Ubuntu: New Status in pm-utils package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: New Bug description: I added a new script in /etc/pm/sleep.d/ that worked fine before the upgrade to vivid. I was wondering why it doesn't work and I find out that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last logs from pm-suspend were on Apr 28, when I upgraded from utopic to vivid. The laptop suspends and wakes fine, it just seems that no pm scripts are run after suspend/powersave. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pm-utils 1.4.1-15 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 14 15:36:26 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-12 (792 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120703-15:08 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/grub2/+bug/1455097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1455097] Re: pm-suspend.log and pm-powersave.log not updated since upgrade to vivid
I moved my script to systemd, adapted it following Martin's instructions in comment #5 and it just works as expected. Thanks a lot :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1455097 Title: pm-suspend no longer run since upgrade to vivid Status in grub2 package in Ubuntu: New Status in pm-utils package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: New Bug description: I added a new script in /etc/pm/sleep.d/ that worked fine before the upgrade to vivid. I was wondering why it doesn't work and I find out that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last logs from pm-suspend were on Apr 28, when I upgraded from utopic to vivid. The laptop suspends and wakes fine, it just seems that no pm scripts are run after suspend/powersave. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pm-utils 1.4.1-15 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 14 15:36:26 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-12 (792 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120703-15:08 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/grub2/+bug/1455097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1455097] [NEW] pm-suspend.log and pm-powersave.log not updated since upgrade to vivid
Public bug reported: I added a new script in /etc/pm/sleep.d/ that worked fine before the upgrade to vivid. I was wondering why it doesn't work and I find out that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last logs from pm-suspend were on Apr 28, when I upgraded from utopic to vivid. The laptop suspends and wakes fine, it just seems that no pm scripts are run after suspend/powersave. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pm-utils 1.4.1-15 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 14 15:36:26 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-12 (792 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120703-15:08 PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1455097 Title: pm-suspend.log and pm-powersave.log not updated since upgrade to vivid Status in pm-utils package in Ubuntu: New Bug description: I added a new script in /etc/pm/sleep.d/ that worked fine before the upgrade to vivid. I was wondering why it doesn't work and I find out that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last logs from pm-suspend were on Apr 28, when I upgraded from utopic to vivid. The laptop suspends and wakes fine, it just seems that no pm scripts are run after suspend/powersave. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pm-utils 1.4.1-15 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 14 15:36:26 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-12 (792 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120703-15:08 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/1455097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
