That is what I ran. It vanished itself. In spite of running that command, and shcekcing it later (wit was still there) today - it is gone. I never ran the Unhold command. (Until today to test it.)
1 Like
Hum.
The command that expires in one day.
We could set a Cron job to run this at 3AM everyday. 
Hearing about this bothers me too. When you put a hold on a package, it should be on hold until you release it. Also, shouldn't even need terminal to put holds on packages. The software and updates section should have checkboxes to do that sort of thing. Uggg 
2 Likes
Synaptic has it.
I cannot find any information that would account for apt-mark releasing a hold on its own, or for dpkg configure causing it, either...
2 Likes
I might- hard to tell because I don't know what the Japanese parts say.
Basically they are arranged in the same order as in English.
[Package] [Installed version] [Latest version]
Ah, if you click Package on the menubar, then in the menu, move to Lock Version, that will place a hold on the package.
1 Like
Like this?
So it looks like that hold command did nothing 
The only way to hold the kernel is through Synaptic.
I wonder if it is safe for me to take that pending update.
2 Likes
OK update on machine with Zorin on it...
Currently installed kernels already on system and functioning perfectly on my machine...
Kernels not installed that I have put a lock on...
Thanks to Aravisian & FrenchPress for figuring this stuff out. I don't need no more kernel updates to this old machine, this machine is so old it could probably run on the version 3 kernel from years ago. Don't even need 5.11.34, but certainly aint gonna need no freaking 5.13!
[Progress report]
After locking the kernel packages, several strange things happened.
- Gdebi crashes immediately after clicking "install" button.
- Synaptic cannot be opened in Application menu. It had to be run from terminal.
- Updater still complains about some missing elements and suggests "partial upgrade". But when clicking "install" it immediately said "the system is up to date".
- I no longer can select Nouveau in Additional Driver.
Since I made a Clonezilla image just 2 days ago, I decided to venture out and take this -34 kernel. I unlock the packages and run
sudo apt dist-upgrade
It required a cold boot thereafter, but all went well.
Now I am using 470 NVidia driver with -34 kernel 
The output of uname -a:
5.11.0-34-generic #36~20.04.1-Ubuntu SMP Fri Aug 27 08:06:32 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Now this makes me wonder what that initial hiccup was all about 
1 Like
What the bloody freaky heck? I mean seriously? Locking kernels from being installed, which are not even currently installed, caused all that business? Hopefully, that don't happen on my OS 16 install.
But now that I think about it, I don't remember clicking on APPLY after setting the packages to lock. If I forgot to click on APPLY, then the changes I might are not really changed.
I still don't get it though, why would software need access to kernel packages which are not even installed on the system? Not a thing about that makes any lick of sense to me.
I sware, some days Linux can be truly a wonderful thing. Other times, it can be a real nightmare.
I am probably not understanding you correctly but here goes . . . are you saying that after the dist-upgrade command everythings is back to normal? That is Synaptic opens in the Application menu, and you can again select Nouveau in Additional Driver. I have been holding back on all updates. BTW, thanks to all of you for finding this and helping me know to avoid this current update.
1 Like
Thats what we are here for! We are here to help in any way that we can. I humbly believe, when knowledge is shared, everyone benefits.
Also, thank you for being a Zorin OS 16 PRO user. Supporting the dev's and getting extra goodies for it, is the way to go! 
1 Like
I have been keeping up on all updates, since mine unlocked as well and went ahead with the update from days ago. I also did some more updates today,
again, so far so good, no hangups and pc is rebooting with no glitching at all.
5.11.0-34-generic #36~20.04.1-Ubuntu SMP Fri Aug 27 08:06:32 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Since the original hangup with the NVIDIA issue, once i re-installed the OS i have not run into the original issue again. < fingers crossed >
1 Like
A few points...
- The 5.11.0-34 kernel issue appears to only affect some Nvidia users. I have been unable to confirm if it affects AMD users or not.
- It affects all Ubuntu derivitives, including Mint - it is not exclusive to Zorin OS
- Time has passed since this was first reported - ZorinGroup may have had time to work on it- There is no official word or update on this issue.
-
I Do not recommend avoiding all updates. There have been recent update releases with Security updates and and other software updates.
This is why the O.P. focuses on only confronting the 5.11.0-34 kernel if you have Nvidia and if you experience problems.
3 Likes
I agree 100%
NEVER avoid all updates, thats setting yourself up for disaster. Only put a lock on future kernels from getting installed, at least until they work out the bugs on them.
Yes to all.
But this morning the system failed to wake up from suspend.
So I am still watching this newer -34 kernel.
You are welcome.
That what the forum is for.
Learning from other people's mistakes and misery 
1 Like
Changed from General to Tutorial.