[Bug 1458204] Re: removing kernels should not require a restart afterward

[Launchpad Bug Tracker]

This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2

---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium

  * Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
  * test/test_blacklisted_wrong_origin.py: Fix and enable test
  * Filter out progress indicator from dpkg log (LP: #1599646)
  * Clear cache when autoremoval fails (LP: #1779157)
  * Find autoremovable kernel packages using the patterns in APT's way
(LP: #1815494)

unattended-upgrades (1.1ubuntu1.18.04.7~16.04.1) xenial; urgency=medium

  * Start service after systemd-logind.service to be able to take inhibition
lock (LP: #1806487)
  * Handle gracefully when logind is down (LP: #1806487)

unattended-upgrades (1.1ubuntu1.18.04.7~16.04.0) xenial; urgency=medium

  * Backport to Xenial (LP: #1702793)
  * Revert to build-depending on debhelper (>= 9~) and dh-systemd
  * Revert configuration example changes to avoid triggering a debconf question
  * debian/postinst: Update recovery to be triggered on Xenial's package 
versions

unattended-upgrades (1.1ubuntu1.18.04.7) bionic; urgency=medium

  * Trigger unattended-upgrade-shutdown actions with PrepareForShutdown()
Performing upgrades in service's ExecStop did not work when the upgrades
involved restarting services because systemd blocked other stop/start
actions making maintainer scripts time out and be killed leaving a broken
system behind.
Running unattended-upgrades.service before shutdown.target as a oneshot
service made it run after unmounting filesystems and scheduling services
properly on shutdown is a complex problem and adding more services to the
mix make it even more fragile.
The solution of monitoring PrepareForShutdown() signal from DBus
allows Unattended Upgrade to run _before_ the jobs related to shutdown are
queued thus package upgrades can safely restart services without
risking causing deadlocks or breaking part of the shutdown actions.
Also ask running unattended-upgrades to stop when shutdown starts even in
InstallOnShutdown mode and refactor most of unattended-upgrade-shutdown to
UnattendedUpgradesShutdown class. (LP: #1778219)
  * Increase logind's InhibitDelayMaxSec to 30s. (LP: #1778219)
This allows more time for unattended-upgrades to shut down gracefully
or even install a few packages in InstallOnShutdown mode, but is still a
big step back from the 30 minutes allowed for InstallOnShutdown previously.
Users enabling InstallOnShutdown node are advised to increase
InhibitDelayMaxSec even further possibly to 30 minutes.
- Add NEWS entry about increasing InhibitDelayMaxSec and InstallOnShutdown
  changes
  * Ignore "W503 line break before binary operator"
because it will become the best practice and breaks the build
  * Stop using ActionGroups, they interfere with apt.Cache.clear()
causing all autoremovable packages to be handled as newly autoremovable
ones and be removed by default. Dropping ActionGroup usage does not slow
down the most frequent case of not having anything to upgrade and when
there are packages to upgrade the gain is small compared to the actual
package installation.
Also collect autoremovable packages before adjusting candidates because that
also changed .is_auto_removable attribute of some of them. (LP: #1803749)
(Closes: #910874)

unattended-upgrades (1.1ubuntu1.18.04.6) bionic; urgency=medium

  * Unlock for dpkg operations with apt_pkg.pkgsystem_unlock_inner() when it is
available. Also stop running when reacquiring the lock fails.
Thanks to Julian Andres Klode for original partial patch (LP: #1789637)
  * Skip rebuilding python-apt in upgrade autopkgtests.
Python-apt has a new build dependency making the rebuilding as is failing
and the reference handling issue is worked around in unattended-upgrades
already. (LP: #1781586)
  * Stop trying when no adjustment could be made and adjust package candidates
only to lower versions (LP: #1785093)
  * Skip already adjusted packages from being checked for readjusting.
This makes it clearer that the recursion ends and can also be a bit quicker.
(LP: #1785093)

unattended-upgrades (1.1ubuntu1.18.04.5) bionic; urgency=medium

  * Stop updating the system when reacquiring the dpkg system lock fails.
(LP: #1260041)

unattended-upgrades (1.1ubuntu1.18.04.4) bionic; urgency=medium

  * Redirect stderr output in upgrade-between-snapshots, too, otherwise it
breaks the test sometimes (LP: #1781446)

unattended-upgrades (1.1ubuntu1.18.04.3) bionic; urgency=medium

  * Redirect stderr output in upgrade-all-security, otherwise it breaks the
test (LP: #1781446)

unattended-upgrades (1.1ubuntu1.18.04.2) bionic; urgency=medium

  [ Balint Reczey ]
  * Clear cache when autoremoval is invalid for a package set marked for
removal and 

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Mathew Hodson]

** Tags removed: rls-aa-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Balint Reczey]

Tested 1.1ubuntu1.18.04.7~16.04.2 on Xenial.


root@x-uu-lp-1260041:~# yes no |apt-get autoremove 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED:
  linux-image-4.8.0-53-generic linux-image-extra-4.8.0-53-generic
0 upgraded, 0 newly installed, 2 to remove and 10 not upgraded.
After this operation, 234 MB disk space will be freed.
Do you want to continue? [Y/n] Abort.
root@x-uu-lp-1260041:~# ls /var/run/reboot*
ls: cannot access '/var/run/reboot*': No such file or directory
root@x-uu-lp-1260041:~# apt-get autoremove
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED:
  linux-image-4.8.0-53-generic linux-image-extra-4.8.0-53-generic
0 upgraded, 0 newly installed, 2 to remove and 10 not upgraded.
After this operation, 234 MB disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 53554 files and directories currently installed.)
Removing linux-image-extra-4.8.0-53-generic (4.8.0-53.56~16.04.1) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.8.0-53-generic 
/boot/vmlinuz-4.8.0-53-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.8.0-53-generic 
/boot/vmlinuz-4.8.0-53-generic
update-initramfs: Generating /boot/initrd.img-4.8.0-53-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.8.0-53-generic /boot/vmlinuz-4.8.0-53-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.8.0-53-generic 
/boot/vmlinuz-4.8.0-53-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.8.0-53-generic 
/boot/vmlinuz-4.8.0-53-generic
Removing linux-image-4.8.0-53-generic (4.8.0-53.56~16.04.1) ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.8.0-53-generic 
/boot/vmlinuz-4.8.0-53-generic
update-initramfs: Deleting /boot/initrd.img-4.8.0-53-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.8.0-53-generic 
/boot/vmlinuz-4.8.0-53-generic
root@x-uu-lp-1260041:~# ls /var/run/reboot*
ls: cannot access '/var/run/reboot*': No such file or directory
root@x-uu-lp-1260041:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  unattended-upgrades 1.1ubuntu1.18.04.7~16.04.2 all  automatic 
installation of security upgrades


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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Balint Reczey]

@bhkolts: Yes, not sending an email when only kernel autoremovals took
place is a regression - or an incomplete part of the kernel autoremoval.
It is fixed in 19.04, but the fix is somewhat intrusive thus it may not
be back-ported.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Mathew Hodson]

** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu Artful)

** Project changed: unattended-upgrades => ubuntu-translations

** No longer affects: ubuntu-translations

** Project changed: update-notifier => ubuntu-translations

** No longer affects: ubuntu-translations

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: update-notifier (Ubuntu Xenial)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Łukasz Zemczak]

Hello Daniel, or anyone else affected,

Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.2 in a few hours, and then
in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Launchpad Bug Tracker]

This bug was fixed in the package update-notifier - 3.168.10

---
update-notifier (3.168.10) xenial; urgency=medium

  [ Julian Andres Klode ]
  * Do not notify-reboot-required on linux-image-extra removal (LP: #1458204)

 -- Balint Reczey   Fri, 07 Dec 2018 11:14:24 +0100

** Changed in: update-notifier (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Barry Kolts]

I also can verify 1.1ubuntu1.18.04.7~16.04.1. Yesterday new kernels were
installed and a reboot performed. Today old kernel was removed and no
reboot performed. This test also used the new update-notifier-common
version 3.168.10.

Yesterday I received an email telling me that new kernels had been
installed and a reboot was performed, as it should, but today I received
no email stating the old kernel had been removed. I expected one. Is
this a new bug?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Jarno Suni]

Verified unattended-upgrades 1.1ubuntu1.18.04.7~16.04.1

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Jarno Suni]

I can verify the update-notifier 3.168.10
Did not test unattended-upgrades
Did not change the tag since it is the same for unattended-upgrades 
unfortunately.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Balint Reczey]

@bhkolts

Please just upgrade update-notifier-common. Timo's automated
notification email referred to the source package from which both binary
packages are built.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Barry Kolts]

@tjaalton

My 16.04 server doesn't have update-notifier installed but does have
update-notifier-common installed. If I install update-notifier from
propose it will install a slew of other packages. If I install update-
notifier-common from propose it just installs the new update-notifier-
common version 3.168.10. So should i test update-notifier-common instead
of update-notifier?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Timo Aaltonen]

Hello Daniel, or anyone else affected,

Accepted update-notifier into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/update-
notifier/3.168.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: update-notifier (Ubuntu Xenial)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Balint Reczey]

It looks like Brian can't do it either, but I uploaded the fix for
update-notifier in Xenial.


** Description changed:

+ [Impact]
+ 
+ The rationale behind the SRU to Xenial is that with latest unattended-
+ upgrades SRU it starts removing unused kernels, but all older kernels
+ are not removed in a single run. With update-notifier and u-u not fixed
+ they place /var/run/reboot-required asking for a reboot when it is not
+ needed.
+ 
+ 
+ [Test Case]
+ 
  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.
  
  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.
+ 
+ [ Regression Potential ]
+ 
+ If the check for skipping placing the /var/run/reboot-required file is too 
broad it may make kernel upgrades fail to ask for reboot. The fix changes a 
hook called by maintainer scripts and a failure in the hook can make kernel 
package installations fail.
+ The fix is simple and was tested in several releases thus regressing in these 
ways is unlikely.
+ 
+ [ Original Bug Text ]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
- --- 
+ ---
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
-  linux-restricted-modules-3.13.0-53-generic N/A
-  linux-backports-modules-3.13.0-53-generic  N/A
-  linux-firmware 1.127.12
+  linux-restricted-modules-3.13.0-53-generic N/A
+  linux-backports-modules-3.13.0-53-generic  N/A
+  linux-firmware 1.127.12
  RfKill:
-  
+ 
  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:
-  
+ 
  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Balint Reczey]

@bhkolts: Thank you for your feedback. Linux-image-
extra-4.4.0-138-generic.postrm still runs /etc/kernel/postinst.d/update-
notifier that places /var/run/reboot-required, the file u-u acts upon
and reboots.

Update-notifier is fixed in Bionic, but I'm hereby nominating the fix
for Xenial.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Balint Reczey]

No, I can't nominate it. :-)
Brian, could you please do nominate this for u-n in Xenial?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Barry Kolts]

Brian,

On Dec 3rd I installed from xenial-proposed version 1.1ubuntu1.18.04.7~16.04.0.
On Dec 4th unattended-upgrades installed new kernel and rebooted, as it should.
Today, Dec 5 unattended-upgrades removed old kernels, which it should do, and 
then rebooted which it shouldn't do. I have attached unattended-upgrades.log 
for the relevant days.

On a side note unattended-upgrades emailed me after it installed the new
kernel on Dec 4th, as it should, but did not email me after removing old
kernels on Dec 5th. It should have.

Let me know if I can provide any other information or do any further
testing. My system is Ubuntu 16.04.5 LTS server.

Barry

** Attachment added: "unattended-upgrades.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/5219447/+files/unattended-upgrades.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Brian Murray]

Hello Daniel, or anyone else affected,

Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.0 in a few hours, and then
in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Brian Murray]

** Changed in: unattended-upgrades (Ubuntu Artful)
   Status: Confirmed => Won't Fix

** Changed in: update-notifier (Ubuntu Artful)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Launchpad Bug Tracker]

This bug was fixed in the package update-notifier - 3.189

---
update-notifier (3.189) bionic; urgency=medium

  * Do not notify-reboot-required on linux-image-extra removal (LP:
#1458204)

 -- Julian Andres Klode   Fri, 12 Jan 2018 09:51:27
+0100

** Changed in: update-notifier (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Launchpad Bug Tracker]

This bug was fixed in the package unattended-upgrades - 0.98ubuntu4

---
unattended-upgrades (0.98ubuntu4) bionic; urgency=medium

  * Cherry pick from git:
- Fix version of test package in test_remove_unused_dependencies (Closes: 
#886803)

 -- Julian Andres Klode   Fri, 12 Jan 2018 10:10:29
+0100

** Changed in: unattended-upgrades (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Julian Andres Klode]

Fixed that for now in unattended-upgrades and update-notifier by adding

case "$DPKG_MAINTSCRIPT_PACKAGE::$DPKG_MAINTSCRIPT_NAME" in
linux-image-extra*::postrm)
exit 0;;
esac

We can then still decide if we want to run postinst.d scripts in linux-
image-extra removals or not, but let's use bug 1501884 for that.

** Changed in: update-notifier (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: unattended-upgrades (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Francis Ginther]

** Tags added: id-597a82bd36308ac7a63cff29

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Dave Chiluk]

** Tags added: indeed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Brian Murray]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Also affects: update-notifier (Ubuntu Artful)
   Importance: Low
   Status: Confirmed

** Also affects: unattended-upgrades (Ubuntu Artful)
   Importance: Low
   Status: Confirmed

** Also affects: linux (Ubuntu Artful)
   Importance: Low
 Assignee: Adam Conrad (adconrad)
   Status: Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Brian Murray]

** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => Low

** Changed in: update-notifier (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Jarno Suni]

Because the code can be applied in many kernel post-installation
scripts, I have attached it in Bug #1501884 and further updates go
there.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Jarno Suni]

** Attachment added: "code to add in probably all post-installation scripts 
except initramfs-tools and dkms to exit them before their job in case removing 
linux-image-extra"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/4883521/+files/addition2

** Patch removed: "code to add before touching /var/run/reboot-required in 
post-installation scripts ;  ver. 2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/4882547/+files/addition

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Jarno Suni]

** Patch removed: "code to add before touching /var/run/reboot-required in 
post-installation scripts"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/4881881/+files/addition

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Jarno Suni]

The code could be added to /etc/kernel/postinst.d/zz-update-grub, too,
to avoid unnecessarily updating grub.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Jarno Suni]

An exception for linux-image-extra packages can be added in
/etc/kernel/postinst.d/update-notifier and in /etc/kernel/postinst.d
/unattended-upgrades

Also escape '+' characters, as package name may contain those:
https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Source


** Attachment added: "code to add before touching /var/run/reboot-required in 
post-installation scripts ;  ver. 2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/4882547/+files/addition

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Brian Murray]

** Tags added: rls-aa-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Ubuntu Foundations Team Bug Bot]

The attachment "code to add before touching /var/run/reboot-required in
post-installation scripts" seems to be a patch.  If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Jarno Suni]

An exception for linux-image-extra packages can be added in
/etc/kernel/postinst.d/update-notifier and in /etc/kernel/postinst.d
/unattended-upgrades

** Attachment added: "code to add before touching /var/run/reboot-required in 
post-installation scripts"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/4881881/+files/addition

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: update-notifier (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Jarno Suni]

Steve Langasek, such a bug has been reported (Bug #1501884)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Jarno Suni]

Yes, it is odd. I think the post-installation scripts will be run
because the depending linux-image- package might not get
removed (and is present at the time anyway), thus initramfs-tools is
used to create /boot/initrd.img- without the extra kernel
modules provided by linux-image-extra-. I guess that exception
could be handled in /etc/kernel/postrm.d/initramfs-tools alternatively.

Nowadays also /etc/kernel/postinst.d/unattended-upgrades touches
/var/run/reboot-required so, that should be modified, as well (if post-
installation script will be run).

BTW running the post-installation scripts then may cause other problem,
too: Bug #1678187



** Also affects: unattended-upgrades (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Steve Langasek]

Why does *removing* a linux-image-extra package cause
post-*installation* scripts to be run? This sounds like a bug on the
kernel side, to me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/update-notifier/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Jarno Suni]

When removing a linux-image-extra package, kernel post-installation
scripts including /etc/kernel/postinst.d/update-notifier will be run.
That is a symbolic link to /usr/share/update-notifier/notify-reboot-
required, which can be modified to fix this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/update-notifier/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Jarno Suni]

** Also affects: update-notifier (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: update-notifier
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/update-notifier/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Cavsfan]

I could not successfully run the command.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Christopher M. Penalver]

** Changed in: linux (Ubuntu)
   Importance: Undecided = Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1458204] Re: removing kernels should not require a restart afterward

[Daniel Barrett]

apport information

** Tags added: apport-collected

** Description changed:

  1. Perform a kernel upgrade normally via apt-get dist-upgrade.
  2. Reboot.
  3. Run apt-get autoremove to delete the old kernel packages.
  4. System Notification Helper now reports that the computer requires a 
reboot.
  
  The autoremove operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.11
+ Architecture: amd64
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
+ InstallationDate: Installed on 2013-08-31 (632 days ago)
+ InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
+ MachineType: System manufacturer System Product Name
+ Package: linux (not installed)
+ ProcFB: 0 nouveaufb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
+ RelatedPackageVersions:
+  linux-restricted-modules-3.13.0-53-generic N/A
+  linux-backports-modules-3.13.0-53-generic  N/A
+  linux-firmware 1.127.12
+ RfKill:
+  
+ Tags:  trusty
+ Uname: Linux 3.13.0-53-generic x86_64
+ UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
+ UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
+ WifiSyslog:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 08/12/2013
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 4210
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: P9X79
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev 1.xx
+ dmi.chassis.asset.tag: Asset-1234567890
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Chassis Manufacture
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
+ dmi.product.name: System Product Name
+ dmi.product.version: System Version
+ dmi.sys.vendor: System manufacturer

** Attachment added: AlsaInfo.txt
   
https://bugs.launchpad.net/bugs/1458204/+attachment/4404953/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs