[Touch-packages] [Bug 1968154] Re: Only keep 2 kernels

2023-08-31 Thread bmaupin
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

[Touch-packages] [Bug 1968154] Re: Only keep 2 kernels

2023-08-31 Thread bmaupin
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

[Touch-packages] [Bug 1470235] Re: PolicyKit high memory usage

2018-10-15 Thread bmaupin
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

[Touch-packages] [Bug 1470235] Re: PolicyKit high memory usage

2018-10-09 Thread bmaupin
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

[Touch-packages] [Bug 1612951] Re: /etc/default/keyboard ignored after upgrade to 16.04

2018-07-15 Thread bmaupin
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,

[Touch-packages] [Bug 1612951] Re: /etc/default/keyboard ignored after upgrade to 16.04

2016-08-19 Thread bmaupin
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

[Touch-packages] [Bug 1612951] Re: /etc/default/keyboard ignored after upgrade to 16.04

2016-08-14 Thread bmaupin
** 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.

[Touch-packages] [Bug 1612951] Re: XKBOPTIONS ignored after upgrade to 16.04

2016-08-13 Thread bmaupin
** 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:

[Touch-packages] [Bug 1612951] Re: XKBOPTIONS ignored after upgrade to 16.04

2016-08-13 Thread bmaupin
** 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

[Touch-packages] [Bug 1612951] [NEW] XKBOPTIONS ignored after upgrade to 16.04

2016-08-13 Thread bmaupin
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

[Touch-packages] [Bug 1470235] Re: PolicyKit high memory usage

2015-09-25 Thread bmaupin
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

[Touch-packages] [Bug 1470235] Re: PolicyKit high memory usage

2015-07-07 Thread bmaupin
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

[Touch-packages] [Bug 1470235] Re: PolicyKit high memory usage

2015-07-06 Thread bmaupin
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

[Touch-packages] [Bug 1470235] [NEW] PolicyKit high memory usage

2015-06-30 Thread bmaupin
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

[Touch-packages] [Bug 955675] Re: openssl s_client's '-ssl2' option no longer works in 12.04

2015-02-12 Thread bmaupin
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