Feedback that is critical or not complimentary is still honest and useful feedback. Indeed, no helpdesk should ever remove critical feedback as that would be a confirmation bias and censorship.
Post #7 above balances a very fine line. This post was flagged by the community due to its criticality being a bit over the top.
However, since it also contains the solution and only very narrowly fits as still "within the guidelines" I have chosen to take the unusual step of annotating a Moderator Action publicly rather than resolving the issue and annotating it in the moderator forum.
@ulao, please read this Introduction.
Specifically:
Please bear in mind that this is a Community Forum populated with Forum Members and Volunteers. We are not the staff nor are we part of the Zorin Group Company. We are peers.
Members may offer suggestions or solutions to posted problems. A suggestion may not always be helpful, but please always remember that the Poster is still being a helpful member. It can take many attempts, sometimes, to successfully diagnose an issue. While a person asking for advice on solving a problem may prioritize the problem they need solved, your peers must also prioritize keeping the forum a welcoming place.
Certainly, you were frustrated as the clock was ticking. But there are important elements missing in the troubleshooting.
Certainly, trying the older kernel and even defaulting to it are suggested swiftly on this forum - I have even written standing guides on this in the Tutorials & Guides Forum. As have others.
The initial posts describing the problem, but also the timing of the problem and any recent events like updates and upgrades can be instrumental in determining the direction of troubleshooting.
Beware the X - Y Problem. Focus on the actual issue, rather than asking how to perform an assumed fix.
The Public Community Forum support is all volunteer supplied. This allows volunteers to learn as they go honing their skills and increasing their knowledge.
By taking the initiative and researching your issue, you were able to find a neat and simple solution as well as where the likely cause was. This allows you to contribute as a community member and file a kernel bug report or rely on that experience to help other members in future.
@freshjeff really said this well: It can take a lot of narrowing to troubleshoot an issue and while something may seem simple in hindsight, having key information at the outset can make all the difference in how the problem is approached and considered.
Post #7 remains for the record, but Ulao has the option of editing the post and reconsidering whether the frustration of the moment made the post more critical than necessary.