[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2017-04-30 Thread Jarno Suni
*** This bug is a duplicate of bug 1458204 *** https://bugs.launchpad.net/bugs/1458204 ** This bug has been marked a duplicate of bug 1458204 removing kernels should not require a restart afterward -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-10-12 Thread Barry Kolts
And the after autoremove log ** Attachment added: "after_history.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+attachment/4760020/+files/after_history.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-10-12 Thread Barry Kolts
Brian, Yesterday we had kernel updates. My server, which is set to automatically reboot, reboot fine and no /var/run/reboot-required. This morning there was no second reboot, so everything was as expected. The I ran autoremove to remove the stale kernel. Then I had /var/run/reboot- required and

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-26 Thread Barry Kolts
Brian, This weekend we had updates for libssl and a libssl regression. Both required a reboot and no second reboot. In other words worked as expected. Perhaps the bug only occurs for kernel updates. I have had this happen a few times in the past. So the next time it happens I will not run

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-26 Thread Alexandre Cavaco
Sure Brian, here it is. I think my case was exactly the same, as I also did a 'apt-get autoremove'. But, the strange think is that the reboot file vanished and the system is no longer asking me for reboots (probably since yesterday), but I didn't do anything specific to try to solve the problem.

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-26 Thread Brian Murray
@Alexandre - Could you add your /var/log/apt/history.log entries from before the reboot-required.pkgs file was created? In Barry's case I believe the reboot-required was created because of running 'apt autoremove' which removed older kernels and triggered a run of update-initramfs. ** Changed

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-26 Thread Alberto Salvia Novella
** Changed in: unattended-upgrades (Ubuntu) Importance: Undecided => High ** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Status: New => Confirmed ** Changed in: hundredpapercuts Importance: Undecided => High -- You

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-24 Thread Alexandre Cavaco
** Changed in: unattended-upgrades (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1626345 Title: After

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-23 Thread Alexandre Cavaco
Hello, Brian, I do have that '/var/run/reboot-required.pkgs', it's contents are simply: linux-base -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1626345

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-22 Thread Barry Kolts
Brian, I don't have that file as it was removed by the reboot, but I do believe it said "Linux base", same as the day before. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu.

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-22 Thread Brian Murray
The autoremove would have created the reboot-required file. Start-Date: 2016-09-20 06:56:26 Commandline: apt autoremove Requested-By: barry (1000) Remove: linux-image-extra-4.4.0-34-generic:amd64 (4.4.0-34.53), linux-headers-4.4.0-34-generic:amd64 (4.4.0-34.53), linux-headers-4.4.0-34:amd64

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-22 Thread Barry Kolts
Brian, File attached. ** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+attachment/4746383/+files/history.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-22 Thread Brian Murray
The file /var/log/apt/history.log might be useful in sorting out why the file still exists. Could you please add it as an attachment? ** Changed in: unattended-upgrades (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-22 Thread Brian Murray
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1626345 Title: After rebooting for updates, reboot is still required. Status in