I can confirm that I've been seeing this the past couple of days too:
W:
gpgv:/var/lib/apt/lists/ppa.launchpad.net_noobslab_themes_ubuntu_dists_xenial_InRelease:
The repository is insufficiently signed by key
4FA44A478284A18C1BA4A9CAD530E028F59EAE4D (weak digest)
W:
This is working as it should work now. Is there any timeline on when it will be
put out to the masses?
I install a kernel and before rebooting I purge the 3rd kernel back like I've
always done.
If you autoremove the kernel it leaves the residual config files, which have to
purged with a command
Today when updating via cli 4.4.0-2-generic kernel was waiting to be
autoremoved. So after getting the updates I autoremoved that kernel.
This left me with 2 kernels 4.4.0-4-generic and 4.4.0-6-generic which is
precisely how it is supposed to work.
I think this is working great now.
--
You
I let 3 kernels remain on my Xubuntu 16.04 pc: 4.3.0-7-generic, 4.4.0-2-generic
and 4.4.0-4-generic. Just to see what would happen.
Today when 4.4.0-6-generic kernel came through in regular updates and
when it installed and I rebooted.
I again checked for updates via cli and it wanted to
The installation of the 4.4.0-2-generic in Xenial 16.04 went well, It
left 3 kernels in 01autoremove-kernels so I manually purged the 3rd
oldest one. Now there are 2 there. I updated my /etc/kernel/postinst.d
/apt-auto-removal with version 5 above.
--
You received this bug notification because
Got the 4.3.0-7-generic kernel on Xubuntu 16.04 in today's updates and the
01autoremove-kernels file
contains the last 3 kernels, which I'm fine with. I'll purge the 3rd oldest
one. I prefer purging them
manually instead of using autoremove because autoremove leaves the "Residual
Config"
Manually purged the 4.3.0-5-generic kernel and that left the
4.3.0-6-generic and 4.3.0-7-generic kernels in the 01autoremove-kernels
file. Which is great.
My only question is why does it require a reboot when the 3rd oldest
kernel is deleted? I don't think this should be happening either.
--
Jarno, I did notice that those commands were in the original script after I
posted that.
I got the 4.3.0-6-generic installed in Xubuntu 16.04 just a while ago and your
script worked flawlessly.
I had 3 kernels: 4.3.0-2-generic, 4.3.0-5-generic and 4.3.0-6-generic after
installation and the
Then I performed a sudo apt autoremove and the 4.3.0-2-generic was removed.
The 01autoremove-kernels did not change and still contains the last 2 kernels,
which is good.
The output is attached.
It gave an erroneous error about the kernel header for 4.3.0-2-generic
not being found but since it
Thanks for the attention to this issue that effects every debian version
including Mint back to Trusty 14.04.
I copied your version 4 script into my /etc/kernel/postinst.d/apt-auto-removal.
I will post the entire output resulting from the next kernel that gets added.
I have a 64 bit version of
Jarnos, I have always had a text file with the kernels listed on it and when I
have 3 I delete the 3rd one leaving me 2.
This has been good since 2009. Since it wasn't asking me to autoremove anything
I just entered:
sudo apt-get purge linux-headers-4.3.0-1 linux-headers-4.3.0-1-generic
Jarnos, I can confirm that your /etc/kernel/postinst.d/apt-auto-removal and
adding the cron job resolves this problem.
I installed the 4.3.0-5-generic kernel and rebooted and then manually purged
the 4.3.0-1-generic and it gave some erroneous errors about not being able to
find the DKMS
Thanks! I did that.
We'll see when the next kernel comes through in updates.
--
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/1440608
Title:
I run an alias to do my updating and it's this:
sudo apt-get update && sudo apt-get upgrade && sudo apt-get autoclean
When the update happens and there is a kernel waiting to be dist-upgraded I
believe the
/etc/apt/apt.conf.d/01autoremovekernels file has been manipulated to include
parts of the
I've been getting this error about libjpeg-progs for a while now.
I removed the package and left libjpeg-turbo-progs installled. It also took
xscreensaver-data-extra with it when purged.
I re-installed libjpeg-turbo-progs and xscreensaver-data-extra.
setup an alias so the other updates would
I also found a work around: once the new kernel is installed and it's
wanting to reboot, delete the 3rd oldest kernel or autoremove it before
rebooting and then the /etc/apt/apt.conf.d/01autoremovekernels file will
contain the 3 kernels, which is better than having one.
--
You received this bug
*** This bug is a duplicate of bug 1051935 ***
https://bugs.launchpad.net/bugs/1051935
Had this twice on Xubuntu 15.10 without doing anything.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
*** This bug is a duplicate of bug 1051935 ***
https://bugs.launchpad.net/bugs/1051935
If the fix was released for bug #1051935 this is definitely not a
duplicate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This just happened to me on Xubuntu 15.10 when 4.2.0-11-generic was installed.
It wanted to leave me with one kernel.
You can refer to these two posts for the detail:
http://ubuntuforums.org/showthread.php?t=2251168=4=13361806#post13361806
** Tags added: utopic wily
--
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/1440608
Title:
/etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels
except the
How can you run that when
'''
/etc/kernel/postinst.d/apt-auto-removal
'''
is automagically run at the end of
'''
entering sudo apt-get purge 4 kernel modules.
...
let alone when auto-remove is run.
'''
you will never get the chance.
--
You received this bug notification because you are a
This continues on even in Linux Mint as well as Ubuntu.
I don't think /etc/kernel/postinst.d/apt-auto-removal should be triggered when
you delete a kernel no matter if it's the17th, 3rd, or 2nd to last kernel.
It is triggered when you just manually delete kernels:
sudo apt-get purge
Since this happens on every version from 14.04 to 15.10 is the problem
that it think my PC is a phone? There should be a way to distinguish
whether the system is a phone or a pc/laptop. Maybe phones should keep
one kernel but I believe PC/laptops should be able to retain 2 kernels.
The
This just happened on Trusty 14.04.2 LTS when 3.13.0-52-generic was
installed on my computer.
** Tags added: trusty
--
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/1440608
I agree you should not have too many kernels on your system but, you
should always have 2 regardless. One for backup and one to use. I would
expect autoremove to remove the 3rd oldest kernel but not the only other
kernel on the system. Which is the case as the last 2 kernel installs
did the exact
Please mark the bug as affecting you then.
--
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/1440608
Title:
/etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels
** Attachment added: the contents of /etc/apt/apt.conf.d/01autoremove-kernels
after the 3rd oldest kernel is removed.
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1440608/+attachment/4367067/+files/after%20autoremoval%20of%203%20oldest%20kernel
--
You received this bug notification
The workaround to keep the latest two kernels is to edit the
/etc/apt/apt.conf.d/01autoremove-kernels file and change it to list the
latest 2 kernels.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
After rebooting and autoremoving the 2nd oldest kernel the
/etc/apt/apt.conf.d/01autoremove-kernels file reverts to listing the
3.19.0-11-generic and 3.19.0-12-generic kernels. So only one kernel, the
latest 3.19.0-12-generic is left.
--
You received this bug notification because you are a
Public bug reported:
After installing a 3rd kernel currently 3.19.0-12-generic, the
/etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the
3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed to
be autoremoved. But once autoremove is completed the machine requests
This has been happening on 3 different Vivid installs and 2 different
flavors vanilla Ubuntu and Ubuntu Mate. It happens every time a new
kernel is added without fail.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
I got this errror at boot this morning.
** Attachment added: My /etc/cups/cups-browsed.conf file
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1431041/+attachment/4356970/+files/cups-browsed.conf
--
You received this bug notification because you are a member of Ubuntu
Touch
*** This bug is a duplicate of bug 1377258 ***
https://bugs.launchpad.net/bugs/1377258
I booted into Vivid with systemd and the time is ahead by 5 hours exactly.
I thought it was fixed with yesterday's update but I guess not.
cavsfan@cavsfan-MS-7529:~$ apt-cache policy systemd
systemd
settings and the ability to check get time
Automatically from the internet is greyed out.
Even though it knows I am in US Eastern Standard time this does not fix it:
cavsfan@cavsfan-MS-7529:~$ sudo dpkg-reconfigure tzdata
Current default time zone: 'America/New_York'
Local time is now
it knows I am in US Eastern Standard time this does not fix it:
cavsfan@cavsfan-MS-7529:~$ sudo dpkg-reconfigure tzdata
Current default time zone: 'America/New_York'
Local time is now: Tue Sep 30 08:09:32 EDT 2014.
Universal Time is now: Tue Sep 30 12:09:32 UTC 2014.
The only thing
This is still broken on my system I boot and I see a message systemd-
fcsk detects that the system time is 4 hours behind due probably to a
hardware bios setting and it says it corrected it but when it comes up
it is still 4 hours behind.
--
You received this bug notification because you are a
I booted using systemd with Gnome Flashback (with Compiz).
Today I got the same 4 hours behind US ET.
I had to enter sudo ntpdate ntp.ubuntu.com to correct the time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux
Public bug reported:
This bug is identical to
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1377698
except it only happens when booting with systemd.
Even with UTC=no, Ubuntu stores the time as UTC at shutdown. But since UTC=no,
it expects the time as local, thus applies no
I also have Utopic Mate Remix installed and it was also happening to
this system when booting with systemd too but that seems to be
intermittent.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
am in US Eastern Standard time this does not fix it:
cavsfan@cavsfan-MS-7529:~$ sudo dpkg-reconfigure tzdata
Current default time zone: 'America/New_York'
Local time is now: Tue Sep 30 08:09:32 EDT 2014.
Universal Time is now: Tue Sep 30 12:09:32 UTC 2014.
The only thing
this does not fix it:
cavsfan@cavsfan-MS-7529:~$ sudo dpkg-reconfigure tzdata
Current default time zone: 'America/New_York'
Local time is now: Tue Sep 30 08:09:32 EDT 2014.
Universal Time is now: Tue Sep 30 12:09:32 UTC 2014.
The only thing that will fix it is sudo ntpdate ntp.ubuntu.com
Public bug reported:
I booted with systemd and got a bunch of updates. Went to reboot to
finalize the update as kernel 3.16.0-10-generic was added. The system
would not compete the reboot and failed to shutdown. I had to press the
reset button and booted back in with systemd. Not sure why upstart
I enabled Pre-Release updates and got just the following:
libpam-systemd (version 204-14ubuntu2) will be upgraded to version 208-6ubuntu2
libsystemd-daemon0 (version 204-14ubuntu2) will be upgraded to version
208-6ubuntu2
libsystemd-journal0 (version 204-14ubuntu2) will be upgraded to version
43 matches
Mail list logo
