[Touch-packages] [Bug 1968154] Re: Only keep 2 kernels
So I did some more digging, and I guess the 5.15.0-82 kernel is there because it's required by linux-image-generic: $ dpkg -l | grep linux-image | grep ^ii ii linux-image-5.15.0-82-generic 5.15.0-82.91 amd64Signed kernel image generic ii linux-image-5.19.0-50-generic 5.19.0-50.50 amd64Signed kernel image generic ii linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 amd64Signed kernel image generic ii linux-image-6.2.0-31-generic 6.2.0-31.31~22.04.1 amd64Signed kernel image generic ii linux-image-generic5.15.0.82.78 amd64Generic Linux kernel image ii linux-image-generic-hwe-22.04 6.2.0.31.31~22.04.8 Although even after uninstalling linux-image-generic, sudo apt autoremove still doesn't remove any additional kernels. I guess somehow the logic that apt uses to remove unused kernels doesn't account for when multiple linux-image-generic packages are installed because of HWE. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1968154 Title: Only keep 2 kernels Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Impish: Fix Released Bug description: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. We remove the requirement to keep the most recently installed version, previously recorded in APT::LastInstalledKernel, to achieve this, as we had 3 hard requirements so far: 1. keep booted kernel 2. keep highest version 3. keep most recently installed 1 can't be removed as it would break running systems, 2 is what you definitely want to keep. During normal system lifetime, the most recently installed kernel is the same as the highest version, so 2==3, and there are no changes to behavior. Likewise, if you most recently installed an older kernel manually for debugging, it would be manually installed and not subject to removal, even if the rule is dropped. The behavior really only changes if you install an older kernel, and then mark it auto - that older kernel becomes automatically removable immediately after it is marked as auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1968154] Re: Only keep 2 kernels
Am I running into this bug or a different one? apt dist-upgrade started failing for me today. In particular, linux- firmware is failing to install because /boot is full. But it looks like I have 4 kernels installed: $ dpkg -l | grep linux-image-.*-generic | grep ^ii ii linux-image-5.15.0-82-generic 5.15.0-82.91 amd64Signed kernel image generic ii linux-image-5.19.0-50-generic 5.19.0-50.50 amd64Signed kernel image generic ii linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 amd64Signed kernel image generic ii linux-image-6.2.0-31-generic 6.2.0-31.31~22.04.1 amd64Signed kernel image generic I tried running sudo apt-get autoremove --purge but it doesn't work, due to the failed linux-firmware installation. Should I file a new bug for this? I'm running Ubuntu 22.04 but that doesn't seem to be listed for this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1968154 Title: Only keep 2 kernels Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Impish: Fix Released Bug description: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. We remove the requirement to keep the most recently installed version, previously recorded in APT::LastInstalledKernel, to achieve this, as we had 3 hard requirements so far: 1. keep booted kernel 2. keep highest version 3. keep most recently installed 1 can't be removed as it would break running systems, 2 is what you definitely want to keep. During normal system lifetime, the most recently installed kernel is the same as the highest version, so 2==3, and there are no changes to behavior. Likewise, if you most recently installed an older kernel manually for debugging, it would be manually installed and not subject to removal, even if the rule is dropped. The behavior really only changes if you install an older kernel, and then mark it auto - that older kernel becomes automatically removable immediately after it is marked as auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1470235] Re: PolicyKit high memory usage
I don't seem to have this issue on 18.04 either, so it seems to be
limited to 14.04.
$ ps aux | grep [p]olkit
root 1453 0.0 0.0 292924 8796 ?Ssl Oct12 0:01
/usr/lib/policykit-1/polkitd --no-debug
bmaupin 16637 0.0 0.1 323808 19996 ?Sl 08:10 0:00
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
$ lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
In response to other comments, I never used Multi-Core System Monitor
but I've used indicator-multiload ("System Load Indicator") the last 5+
years.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1470235
Title:
PolicyKit high memory usage
Status in policykit-1 package in Ubuntu:
Confirmed
Bug description:
Periodically I install updates on my computer and reboot without
logging in. When I come back to my computer and log in, polkitd is
using a large chunk of memory. At the moment it's using > 2.3 GiB of
memory on a machine with 8 GB RAM:
$ ps aux | grep polkit
root 1229 0.4 29.8 2652532 2420916 ? Sl Jun19 67:38
/usr/lib/policykit-1/polkitd --no-debug
Killing the process frees the memory until I reboot again.
I'm currently using the latest version of policykit-1:
$ apt-file search /usr/lib/policykit-1/polkitd
policykit-1: /usr/lib/policykit-1/polkitd
$ apt-cache policy policykit-1
policykit-1:
Installed: 0.105-4ubuntu2.14.04.1
Candidate: 0.105-4ubuntu2.14.04.1
Version table:
*** 0.105-4ubuntu2.14.04.1 0
500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
0.105-4ubuntu2 0
500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
$ sudo apt-get upgrade policykit-1
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
policykit-1 is already the newest version.
Other information:
$ lsb_release -rd
Description: Ubuntu 14.04.2 LTS
Release: 14.04
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: policykit-1 0.105-4ubuntu2.14.04.1
ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11
Uname: Linux 3.16.0-41-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Tue Jun 30 16:14:51 2015
InstallationDate: Installed on 2014-08-25 (309 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140723)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: policykit-1
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1470235/+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 1470235] Re: PolicyKit high memory usage
For what it's worth, I don't seem to have had this issue after upgrading to Ubuntu 16.04. I recently just upgraded to 18.04 so I'll continue to keep an eye on things. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1470235 Title: PolicyKit high memory usage Status in policykit-1 package in Ubuntu: Confirmed Bug description: Periodically I install updates on my computer and reboot without logging in. When I come back to my computer and log in, polkitd is using a large chunk of memory. At the moment it's using > 2.3 GiB of memory on a machine with 8 GB RAM: $ ps aux | grep polkit root 1229 0.4 29.8 2652532 2420916 ? Sl Jun19 67:38 /usr/lib/policykit-1/polkitd --no-debug Killing the process frees the memory until I reboot again. I'm currently using the latest version of policykit-1: $ apt-file search /usr/lib/policykit-1/polkitd policykit-1: /usr/lib/policykit-1/polkitd $ apt-cache policy policykit-1 policykit-1: Installed: 0.105-4ubuntu2.14.04.1 Candidate: 0.105-4ubuntu2.14.04.1 Version table: *** 0.105-4ubuntu2.14.04.1 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.105-4ubuntu2 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ sudo apt-get upgrade policykit-1 Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done policykit-1 is already the newest version. Other information: $ lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Tue Jun 30 16:14:51 2015 InstallationDate: Installed on 2014-08-25 (309 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1470235/+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 1612951] Re: /etc/default/keyboard ignored after upgrade to 16.04
For what it's worth, I recently upgraded to 18.04 and this no longer seems to be an issue. I removed my ~/.xprofile and the compose key seems to work with the /etc/default/keyboard setting alone. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1612951 Title: /etc/default/keyboard ignored after upgrade to 16.04 Status in console-setup package in Ubuntu: New Bug description: I just upgraded Xubuntu 14.04 to 16.04, and I noticed my compose key wasn't working in any application in X. I verified my compose key was still set up in /etc/default/keyboard: XKBOPTIONS="compose:ralt" I googled around and ran these two commands: sudo dpkg-reconfigure keyboard-configuration sudo update-initramfs -u But the problem persists. I notice that the compose key works fine in the console, but it doesn't work in any X application, including the terminal. Here's my current workaround: echo "setxkbmap -option compose:ralt" >> ~/.xprofile It looks like I'm not the only one experiencing this, and it doesn't seem limited to Xfce: https://ubuntu-mate.community/t/setxkbmap-option-in-etc-default- keyboard-not-working/4054 $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.108ubuntu15.2 Candidate: 1.108ubuntu15.2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 13 09:04:10 2016 InstallationDate: Installed on 2014-05-08 (827 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: Upgraded to xenial on 2016-08-05 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1612951/+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 1612951] Re: /etc/default/keyboard ignored after upgrade to 16.04
I'm game. 1. $ head -n 1 /etc/default/keyboard # Check /usr/share/doc/keyboard-configuration/README.Debian for 2. In /usr/share/doc/keyboard-configuration/README.Debian, I see this: "While it will be safe to edit directly the configuration files (/etc/default/keyboard and /etc/default/console-setup) perhaps it will be easier to use dpkg-reconfigure keyboard-configuration dpkg-reconfigure console-setup" Hmm, to me that implies that I should only run those commands if I don't want to edit /etc/default/keyboard directly. In addition: "console-setup This package is responsible for the actual configuration of the console (font and keyboard). It is responsible for the configuration file /etc/default/console-setup." implies that console-setup doesn't even have anything to do with /etc/default/keyboard. I had already run the first command as previously mentioned, so I ran the second command. Removed my fix from ~/.xprofile, rebooted. Didn't work. Am I missing something? I've attached the whole file just in case I'm missing something. ** Attachment added: "/usr/share/doc/keyboard-configuration/README.Debian" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1612951/+attachment/4724216/+files/README.Debian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1612951 Title: /etc/default/keyboard ignored after upgrade to 16.04 Status in console-setup package in Ubuntu: New Bug description: I just upgraded Xubuntu 14.04 to 16.04, and I noticed my compose key wasn't working in any application in X. I verified my compose key was still set up in /etc/default/keyboard: XKBOPTIONS="compose:ralt" I googled around and ran these two commands: sudo dpkg-reconfigure keyboard-configuration sudo update-initramfs -u But the problem persists. I notice that the compose key works fine in the console, but it doesn't work in any X application, including the terminal. Here's my current workaround: echo "setxkbmap -option compose:ralt" >> ~/.xprofile It looks like I'm not the only one experiencing this, and it doesn't seem limited to Xfce: https://ubuntu-mate.community/t/setxkbmap-option-in-etc-default- keyboard-not-working/4054 $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.108ubuntu15.2 Candidate: 1.108ubuntu15.2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 13 09:04:10 2016 InstallationDate: Installed on 2014-05-08 (827 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: Upgraded to xenial on 2016-08-05 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1612951/+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 1612951] Re: /etc/default/keyboard ignored after upgrade to 16.04
** Summary changed: - XKBOPTIONS ignored after upgrade to 16.04 + /etc/default/keyboard ignored after upgrade to 16.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1612951 Title: /etc/default/keyboard ignored after upgrade to 16.04 Status in console-setup package in Ubuntu: New Bug description: I just upgraded Xubuntu 14.04 to 16.04, and I noticed my compose key wasn't working in any application in X. I verified my compose key was still set up in /etc/default/keyboard: XKBOPTIONS="compose:ralt" I googled around and ran these two commands: sudo dpkg-reconfigure keyboard-configuration sudo update-initramfs -u But the problem persists. I notice that the compose key works fine in the console, but it doesn't work in any X application, including the terminal. Here's my current workaround: echo "setxkbmap -option compose:ralt" >> ~/.xprofile It looks like I'm not the only one experiencing this, and it doesn't seem limited to Xfce: https://ubuntu-mate.community/t/setxkbmap-option-in-etc-default- keyboard-not-working/4054 $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.108ubuntu15.2 Candidate: 1.108ubuntu15.2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 13 09:04:10 2016 InstallationDate: Installed on 2014-05-08 (827 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: Upgraded to xenial on 2016-08-05 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1612951/+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 1612951] Re: XKBOPTIONS ignored after upgrade to 16.04
** Description changed: I just upgraded Xubuntu 14.04 to 16.04, and I noticed my compose key wasn't working in any application in X. I verified my compose key was still set up in /etc/default/keyboard: XKBOPTIONS="compose:ralt" I googled around and ran these two commands: sudo dpkg-reconfigure keyboard-configuration sudo update-initramfs -u But the problem persists. I notice that the compose key works fine in the console, but it doesn't work in any X application, including the terminal. + Here's my current workaround: + echo "setxkbmap -option compose:ralt" >> ~/.xprofile + It looks like I'm not the only one experiencing this, and it doesn't seem limited to Xfce: https://ubuntu-mate.community/t/setxkbmap-option-in-etc-default- keyboard-not-working/4054 - $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 $ apt-cache policy keyboard-configuration keyboard-configuration: - Installed: 1.108ubuntu15.2 - Candidate: 1.108ubuntu15.2 + Installed: 1.108ubuntu15.2 + Candidate: 1.108ubuntu15.2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 13 09:04:10 2016 InstallationDate: Installed on 2014-05-08 (827 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: Upgraded to xenial on 2016-08-05 (7 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1612951 Title: XKBOPTIONS ignored after upgrade to 16.04 Status in console-setup package in Ubuntu: New Bug description: I just upgraded Xubuntu 14.04 to 16.04, and I noticed my compose key wasn't working in any application in X. I verified my compose key was still set up in /etc/default/keyboard: XKBOPTIONS="compose:ralt" I googled around and ran these two commands: sudo dpkg-reconfigure keyboard-configuration sudo update-initramfs -u But the problem persists. I notice that the compose key works fine in the console, but it doesn't work in any X application, including the terminal. Here's my current workaround: echo "setxkbmap -option compose:ralt" >> ~/.xprofile It looks like I'm not the only one experiencing this, and it doesn't seem limited to Xfce: https://ubuntu-mate.community/t/setxkbmap-option-in-etc-default- keyboard-not-working/4054 $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.108ubuntu15.2 Candidate: 1.108ubuntu15.2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 13 09:04:10 2016 InstallationDate: Installed on 2014-05-08 (827 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: Upgraded to xenial on 2016-08-05 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1612951/+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 1612951] Re: XKBOPTIONS ignored after upgrade to 16.04
** Attachment added: "/etc/default/keyboard" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1612951/+attachment/4720184/+files/keyboard -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1612951 Title: XKBOPTIONS ignored after upgrade to 16.04 Status in console-setup package in Ubuntu: New Bug description: I just upgraded Xubuntu 14.04 to 16.04, and I noticed my compose key wasn't working in any application in X. I verified my compose key was still set up in /etc/default/keyboard: XKBOPTIONS="compose:ralt" I googled around and ran these two commands: sudo dpkg-reconfigure keyboard-configuration sudo update-initramfs -u But the problem persists. I notice that the compose key works fine in the console, but it doesn't work in any X application, including the terminal. It looks like I'm not the only one experiencing this, and it doesn't seem limited to Xfce: https://ubuntu-mate.community/t/setxkbmap-option-in-etc-default- keyboard-not-working/4054 $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.108ubuntu15.2 Candidate: 1.108ubuntu15.2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 13 09:04:10 2016 InstallationDate: Installed on 2014-05-08 (827 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: Upgraded to xenial on 2016-08-05 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1612951/+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 1612951] [NEW] XKBOPTIONS ignored after upgrade to 16.04
Public bug reported: I just upgraded Xubuntu 14.04 to 16.04, and I noticed my compose key wasn't working in any application in X. I verified my compose key was still set up in /etc/default/keyboard: XKBOPTIONS="compose:ralt" I googled around and ran these two commands: sudo dpkg-reconfigure keyboard-configuration sudo update-initramfs -u But the problem persists. I notice that the compose key works fine in the console, but it doesn't work in any X application, including the terminal. It looks like I'm not the only one experiencing this, and it doesn't seem limited to Xfce: https://ubuntu-mate.community/t/setxkbmap-option-in-etc-default- keyboard-not-working/4054 $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.108ubuntu15.2 Candidate: 1.108ubuntu15.2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 13 09:04:10 2016 InstallationDate: Installed on 2014-05-08 (827 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: Upgraded to xenial on 2016-08-05 (7 days ago) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1612951 Title: XKBOPTIONS ignored after upgrade to 16.04 Status in console-setup package in Ubuntu: New Bug description: I just upgraded Xubuntu 14.04 to 16.04, and I noticed my compose key wasn't working in any application in X. I verified my compose key was still set up in /etc/default/keyboard: XKBOPTIONS="compose:ralt" I googled around and ran these two commands: sudo dpkg-reconfigure keyboard-configuration sudo update-initramfs -u But the problem persists. I notice that the compose key works fine in the console, but it doesn't work in any X application, including the terminal. It looks like I'm not the only one experiencing this, and it doesn't seem limited to Xfce: https://ubuntu-mate.community/t/setxkbmap-option-in-etc-default- keyboard-not-working/4054 $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.108ubuntu15.2 Candidate: 1.108ubuntu15.2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 13 09:04:10 2016 InstallationDate: Installed on 2014-05-08 (827 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: Upgraded to xenial on 2016-08-05 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1612951/+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 1470235] Re: PolicyKit high memory usage
I looked into those dbus messages and didn't find anything helpful. My system is fully up to date and I still have this issue. Here's my current workaround: sudo sh -c 'echo "#!/bin/bash /usr/bin/killall /usr/lib/policykit-1/polkitd" > /etc/cron.daily/kill-polkitd' sudo chmod +x /etc/cron.daily/kill-polkitd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1470235 Title: PolicyKit high memory usage Status in policykit-1 package in Ubuntu: Confirmed Bug description: Periodically I install updates on my computer and reboot without logging in. When I come back to my computer and log in, polkitd is using a large chunk of memory. At the moment it's using > 2.3 GiB of memory on a machine with 8 GB RAM: $ ps aux | grep polkit root 1229 0.4 29.8 2652532 2420916 ? Sl Jun19 67:38 /usr/lib/policykit-1/polkitd --no-debug Killing the process frees the memory until I reboot again. I'm currently using the latest version of policykit-1: $ apt-file search /usr/lib/policykit-1/polkitd policykit-1: /usr/lib/policykit-1/polkitd $ apt-cache policy policykit-1 policykit-1: Installed: 0.105-4ubuntu2.14.04.1 Candidate: 0.105-4ubuntu2.14.04.1 Version table: *** 0.105-4ubuntu2.14.04.1 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.105-4ubuntu2 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ sudo apt-get upgrade policykit-1 Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done policykit-1 is already the newest version. Other information: $ lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Tue Jun 30 16:14:51 2015 InstallationDate: Installed on 2014-08-25 (309 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1470235/+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 1470235] Re: PolicyKit high memory usage
As I mentioned in my last comment, yesterday I logged into my computer after it had been up for 3 days at the login screen. Upon logging in, polkitd was using nearly 1 GB of memory: $ uptime 09:09:38 up 3 days, 15:57, 1 user, load average: 0.06, 0.05, 0.05 $ ps aux | grep polkitd | grep -v grep root 1034 0.4 11.2 1137788 912732 ? Sl Jul02 23:23 /usr/lib/policykit-1/polkitd --no-debug $ date Mon Jul 6 09:11:17 EDT 2015 After nearly 8 hours of being logged in, polkitd memory usage had barely gone up: $ date; uptime; ps aux | grep polkitd | grep -v grep Mon Jul 6 17:04:42 EDT 2015 17:04:42 up 3 days, 23:52, 4 users, load average: 0.36, 0.25, 0.26 root 1034 0.4 11.2 1148092 913328 ? Sl Jul02 23:24 /usr/lib/policykit-1/polkitd --no-debug Then I added some commands to /etc/rc.local to log polkitd memory usage as well as output from dbus-monitor --system, rebooted my machine, and left it at the login prompt. I checked it this morning, after about 16 hours of being left at the login prompt. The output log from dbus- monitor --system was over 100 MB and nearly entirely full of messages like this, with new messages being constantly added: signal sender=org.freedesktop.DBus - dest=(null destination) serial=44 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string :1.252082 string :1.252082 string signal sender=org.freedesktop.DBus - dest=(null destination) serial=45 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string :1.252083 string string :1.252083 signal sender=org.freedesktop.DBus - dest=(null destination) serial=46 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string :1.252083 string :1.252083 string signal sender=org.freedesktop.DBus - dest=(null destination) serial=47 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string :1.252084 string string :1.252084 signal sender=org.freedesktop.DBus - dest=(null destination) serial=48 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string :1.252084 string :1.252084 string The polkitd memory usage seems to have increased about 10 MB every hour: Mon Jul 6 17:07:37 EDT 2015 17:07:37 up 0 min, 0 users, load average: 2.65, 0.71, 0.24 root 1234 0.0 0.0 279764 7748 ?Sl 17:07 0:00 /usr/lib/policykit-1/polkitd --no-debug Mon Jul 6 18:07:38 EDT 2015 18:07:38 up 1:00, 0 users, load average: 0.02, 0.02, 0.05 root 1234 0.4 0.2 287188 18908 ?Sl 17:07 0:16 /usr/lib/policykit-1/polkitd --no-debug Mon Jul 6 19:07:38 EDT 2015 19:07:38 up 2:00, 0 users, load average: 0.03, 0.05, 0.05 root 1234 0.4 0.3 293920 29112 ?Sl 17:07 0:34 /usr/lib/policykit-1/polkitd --no-debug Mon Jul 6 20:07:38 EDT 2015 20:07:38 up 3:00, 0 users, load average: 0.08, 0.03, 0.05 root 1234 0.4 0.4 300784 39328 ?Sl 17:07 0:51 /usr/lib/policykit-1/polkitd --no-debug Mon Jul 6 21:07:38 EDT 2015 21:07:38 up 4:00, 0 users, load average: 0.00, 0.01, 0.05 root 1234 0.4 0.6 307516 49816 ?Sl 17:07 1:09 /usr/lib/policykit-1/polkitd --no-debug Mon Jul 6 22:07:38 EDT 2015 22:07:38 up 5:00, 0 users, load average: 0.00, 0.01, 0.05 root 1234 0.4 0.7 314380 60040 ?Sl 17:07 1:26 /usr/lib/policykit-1/polkitd --no-debug Mon Jul 6 23:07:38 EDT 2015 23:07:38 up 6:00, 0 users, load average: 0.00, 0.01, 0.05 root 1234 0.4 0.8 321112 70520 ?Sl 17:07 1:44 /usr/lib/policykit-1/polkitd --no-debug Tue Jul 7 00:07:38 EDT 2015 00:07:38 up 7:00, 0 users, load average: 0.00, 0.02, 0.05 root 1234 0.4 0.9 327976 80756 ?Sl Jul06 2:01 /usr/lib/policykit-1/polkitd --no-debug Tue Jul 7 01:07:38 EDT 2015 01:07:38 up 8:00, 0 users, load average: 0.00, 0.03, 0.05 root 1234 0.4 1.1 334708 91244 ?Sl Jul06 2:19 /usr/lib/policykit-1/polkitd --no-debug Tue Jul 7 02:07:38 EDT 2015 02:07:38 up 9:00, 0 users, load average: 0.03, 0.04, 0.05 root 1234 0.4 1.2 341440 101472 ? Sl Jul06 2:36 /usr/lib/policykit-1/polkitd --no-debug Tue Jul 7 03:07:38 EDT 2015 03:07:38 up 10:00, 0 users, load average: 0.02, 0.05, 0.05 root 1234 0.4 1.3 348304 111700 ? Sl Jul06 2:54 /usr/lib/policykit-1/polkitd --no-debug Tue Jul 7 04:07:38 EDT 2015 04:07:38 up 11:00, 0 users, load average: 0.16, 0.06, 0.06 root 1234 0.4 1.5 355036 122176 ? Sl Jul06 3:11 /usr/lib/policykit-1/polkitd --no-debug Tue Jul 7 05:07:38 EDT 2015 05:07:38 up 12:00, 0 users, load average: 0.00, 0.01, 0.05 root 1234 0.4 1.6 361900 132400 ? Sl Jul06 3:29 /usr/lib/policykit-1/polkitd --no-debug Tue Jul 7 06:07:38 EDT 2015 06:07:38 up 13:00, 0 users, load average: 0.00, 0.01, 0.05 root 1234 0.4 1.7 368632 142876 ? Sl Jul06
[Touch-packages] [Bug 1470235] Re: PolicyKit high memory usage
A couple more data points: Last week, I rebooted my machine and logged in right away. polkitd was only using 7 MB of memory: $ ps aux | grep polkitd | grep -v grep root 1219 0.1 0.0 281164 7244 ?Sl 16:36 0:00 /usr/lib/policykit-1/polkitd --no-debug Two days later, polkitd was using only marginally more memory: $ uptime 17:08:55 up 2 days, 32 min, 2 users, load average: 1.42, 0.78, 0.37 $ ps aux | grep polkitd | grep -v grep root 1219 0.0 0.0 291208 7664 ?Sl Jun30 0:00 /usr/lib/policykit-1/polkitd --no-debug On Friday, I installed updates and then rebooted without logging in. This morning, before logging in, polkitd was already using nearly 1 GB of memory: $ uptime 09:09:38 up 3 days, 15:57, 1 user, load average: 0.06, 0.05, 0.05 $ ps aux | grep polkitd | grep -v grep root 1034 0.4 11.2 1137788 912732 ? Sl Jul02 23:23 /usr/lib/policykit-1/polkitd --no-debug $ date Mon Jul 6 09:11:17 EDT 2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1470235 Title: PolicyKit high memory usage Status in policykit-1 package in Ubuntu: Confirmed Bug description: Periodically I install updates on my computer and reboot without logging in. When I come back to my computer and log in, polkitd is using a large chunk of memory. At the moment it's using 2.3 GiB of memory on a machine with 8 GB RAM: $ ps aux | grep polkit root 1229 0.4 29.8 2652532 2420916 ? Sl Jun19 67:38 /usr/lib/policykit-1/polkitd --no-debug Killing the process frees the memory until I reboot again. I'm currently using the latest version of policykit-1: $ apt-file search /usr/lib/policykit-1/polkitd policykit-1: /usr/lib/policykit-1/polkitd $ apt-cache policy policykit-1 policykit-1: Installed: 0.105-4ubuntu2.14.04.1 Candidate: 0.105-4ubuntu2.14.04.1 Version table: *** 0.105-4ubuntu2.14.04.1 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.105-4ubuntu2 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ sudo apt-get upgrade policykit-1 Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done policykit-1 is already the newest version. Other information: $ lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Tue Jun 30 16:14:51 2015 InstallationDate: Installed on 2014-08-25 (309 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1470235/+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 1470235] [NEW] PolicyKit high memory usage
Public bug reported: Periodically I install updates on my computer and reboot without logging in. When I come back to my computer and log in, polkitd is using a large chunk of memory. At the moment it's using 2.3 GiB of memory on a machine with 8 GB RAM: $ ps aux | grep polkit root 1229 0.4 29.8 2652532 2420916 ? Sl Jun19 67:38 /usr/lib/policykit-1/polkitd --no-debug Killing the process frees the memory until I reboot again. I'm currently using the latest version of policykit-1: $ apt-file search /usr/lib/policykit-1/polkitd policykit-1: /usr/lib/policykit-1/polkitd $ apt-cache policy policykit-1 policykit-1: Installed: 0.105-4ubuntu2.14.04.1 Candidate: 0.105-4ubuntu2.14.04.1 Version table: *** 0.105-4ubuntu2.14.04.1 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.105-4ubuntu2 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ sudo apt-get upgrade policykit-1 Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done policykit-1 is already the newest version. Other information: $ lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Tue Jun 30 16:14:51 2015 InstallationDate: Installed on 2014-08-25 (309 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1470235 Title: PolicyKit high memory usage Status in policykit-1 package in Ubuntu: New Bug description: Periodically I install updates on my computer and reboot without logging in. When I come back to my computer and log in, polkitd is using a large chunk of memory. At the moment it's using 2.3 GiB of memory on a machine with 8 GB RAM: $ ps aux | grep polkit root 1229 0.4 29.8 2652532 2420916 ? Sl Jun19 67:38 /usr/lib/policykit-1/polkitd --no-debug Killing the process frees the memory until I reboot again. I'm currently using the latest version of policykit-1: $ apt-file search /usr/lib/policykit-1/polkitd policykit-1: /usr/lib/policykit-1/polkitd $ apt-cache policy policykit-1 policykit-1: Installed: 0.105-4ubuntu2.14.04.1 Candidate: 0.105-4ubuntu2.14.04.1 Version table: *** 0.105-4ubuntu2.14.04.1 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.105-4ubuntu2 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ sudo apt-get upgrade policykit-1 Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done policykit-1 is already the newest version. Other information: $ lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Tue Jun 30 16:14:51 2015 InstallationDate: Installed on 2014-08-25 (309 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1470235/+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 955675] Re: openssl s_client's '-ssl2' option no longer works in 12.04
Looks like this is the cause: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589706 ** Bug watch added: Debian Bug tracker #589706 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589706 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/955675 Title: openssl s_client's '-ssl2' option no longer works in 12.04 Status in openssl package in Ubuntu: Confirmed Bug description: the s_client(1) man page describes -tls1, -ssl3 and -ssl2. The latter isn't recognised by openssl in 12.04: aj@aj-Vostro-260:~$ openssl version OpenSSL 1.0.0g 18 Jan 2012 aj@aj-Vostro-260:~$ openssl s_client -ssl2 unknown option -ssl2 usage: s_client args snipped aj@aj-Vostro-260:~$ openssl s_client -ssl3 connect: Connection refused connect:errno=111 aj@aj-Vostro-260:~$ openssl s_client -tls1 connect: Connection refused connect:errno=111 aj@aj-Vostro-260:~$ This option should still continue to work, please do not leave disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/955675/+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
