linuxmint / mintupdate

The Linux Mint Update Manager
309 stars 152 forks source link

Install Kernel upgrades are not becoming active automatically #734

Open Camzl1 opened 2 years ago

Camzl1 commented 2 years ago

Describe the bug When installing optional kernels via update manager they do not become active after restart. You have to go into the terminal and do "sudo update-grub" for the newly installed kernel to become active on the next reboot

Screenshots If applicable, add screenshots to help explain your problem, you can just drag & drop them here.

To Reproduce Install a kernel and reboot.
Go the the Update Manager and choose "View Kernels" You will see your requested kernel installed, but not active.

Expected behavior After que-ing and performing an install of the newest kernel, I expect it to become active upon the next reboot, without having to go into terminal to initiate the commands to update grub. If this is expected behavior then it needs to be documented.

Distribution:

Software version: 5.8.1

Logs: 05.13@12:02 ++ Launching Update Manager 05.13@12:02 ++ Changes to the package cache detected, triggering refresh 05.13@12:02 ++ Starting refresh (local only) 05.13@12:02 ++ Initial refresh will happen in 0 day(s), 0 hour(s) and 10 minute(s) 05.13@12:02 ++ System is up to date 05.13@12:02 ++ Refresh finished 05.13@12:12 ++ Update Manager is in tray mode, performing initial refresh 05.13@12:12 ++ Starting refresh (retrieving lists of updates from remote servers) 05.13@12:12 ++ Refreshing available Cinnamon updates from the server 05.13@12:12 ++ System is up to date 05.13@12:12 ++ Refresh finished 05.13@12:12 ++ Recurring refresh will happen in 0 day(s), 1 hour(s) and 59 minute(s)

Crash report: No crashes just unexpected behavior

smurphos commented 2 years ago

I think you'd might be better asking for help with this in the Mint forums - it's not expected behaviour, neither it is universal behaviour, hence it's a issue with your specific system that needs troubleshooting. The terminal output from your last kernel update from /var/log/apt/term.log would be a good stating point.